00:04 <dos1> ZetaR: as a temporary workaround, when you encounter some broken link, try again via https

00:20 <ZetaR> dos1: Thanks, that works. It is actually a forbidden error and not a page not found error.

00:26 <ZetaR> dos1: It does not work for https://neo900.org/stuff/werner/scans/ because the images try to load as http and not https.

00:27 <dos1> ZetaR: argh... thanks for reporting, I definitely need to do something with that asap :)

00:28 <ZetaR> Looks like it is a filetype permissions issue.

00:28 <ZetaR> PDF and HTML are permitted, but directories, images, etc. are not.

15:47 <DocScrutinizer05> ZetaR: ((What do you think about antiresonance of power decoupling caps?)) Pretty hard to calculate amything from it for real life, since the true virtual circuit is way more complex than just two parallel capacitors. There are also inductivity and capacitance if traces, and basically each capacitor itself has a resonance freq already. You can't always reach ideal circuit properties in real life, and as long as the notches in frequency

15:47 <DocScrutinizer05> filer plot are not in critical frequency ranges, we prolly have to live with them anyway

15:57 <ZetaR> DocScrutinizer05: Er, departure from models in the real world is exactly what I was referring to in Issue 686. One of the links I provided reproduces these effects on a PCB. I have been working most of today and yesterday on this problem, going through all of the datasheets gathering information and calculating values. But I see that the issue has now been closed as WontFix, so I guess my efforts to help with this are probably unwant

16:00 <ZetaR> (not to mention the time I spent on the literature review)

16:01 <ZetaR> I guess I'll just go do something else now...

17:10 <DocScrutinizer05> ZetaR: sorry I am not responsible for what Nikolaus does

17:12 <ZetaR> DocScrutinizer05: Well, I will finish the last bits of what I have done and post it there, but I am a bit upset at the abruptness of this. I was intending to do most of the work for EMI/RFI throughout the development process so that the other devs could do other things.

17:15 <DocScrutinizer05> what can I say

17:16 <DocScrutinizer05> what you see there happens to me all the time

17:19 <DocScrutinizer05> of 40 change requests 25 got postponed or rejected "not needed" or "why?"

17:19 <DocScrutinizer05> please keep in mind this is work in progress

17:23 <DocScrutinizer05> and re buffer capacitors your own papers quote that much depends on actual PCB layout, and since we don't have any such layout your bug ticket is against, I think a "wontfix" is prolly actually correct. Nikolaus said he's aware and will take it into account but there are other aspects that also need to get considered, and many of them are related to layout which is not even done yet

17:28 <DocScrutinizer05> generally the bugtracker's purpose and definition is a tad fuzzy, but generally we do general design considerations rather on our ML than in bug tacker. BT topics should generally be verifiable and fixable, turning BT into a forum to discuss stuff doesn't work too well

17:46 <wpwrak> mmh. xchat acting suicidal :(

18:25 <DocScrutinizer05> hmm

18:28 <DocScrutinizer05> and while I managed to tell dang grub2 to use 1920x1080, the desktop in linux still looks like 320*200. The wonders of gforce graphics cards

18:28 <DocScrutinizer05> LMS my a*

18:29 <DocScrutinizer05> KMS even

19:29 <ilon> http://xkcd.com/1508/

19:29 <ilon> :D

19:48 <Wizzup> DocScrutinizer05: if you use nvidia proprietary drivers, they do not do KMS

19:48 <Wizzup> yet

20:09 <Pali> Wizzup: I bet they will never support *proper* KMS

20:10 <Pali> even they i2c bus support (in kernel) has dependency in running X Server...

20:10 <Pali> i2c bus support via HDMI, DVI, DP, ... cables

20:11 <Pali> and also for connected temperature, fan sensors on GPU (via i2c)

20:11 <Wizzup> Pali: they are working on a seperate module

20:12 <Pali> so I bet if they support kernel KMS API it will be implemented similar as their kernel i2c bus support (kernel hook which will forward that to running X server or other userspace)

20:12 <Pali> separate module ==> does not mean that it will not be another loopback hook

20:12 <Pali> like i2c

20:13 <Pali> and in kernel, one module (file.ko) can contains more kernel drivers

20:13 <Pali> and also one kernel driver can be splitted into more kernel modules

20:13 <Pali> and normally you can decide at build/programming time how kernel linker will link code into .ko files

20:14 <Pali> also you can static link all object files into one big vmlinuz image...

20:14 <Pali> so separate module does not mean anything...

20:15 <Pali> and btw, I saw that nvidia source code on github...

20:58 <Wizzup> Pali: a seperate module that complies with the gpl

20:58 <Wizzup> (kms is gpl or lgpl I think)

20:58 <Wizzup> iow they need a helper module of some kind

21:34 <DocScrutinizer05> Suse linux and GTX970? --> http://software.opensuse.org/package/x11-video-nvidia. And boom, suddenly the weirdest resolutions (2560*1080) work after next boot, no adjusting, no fiddling

21:36 <wpwrak> so much about not giving in to the dark side ...

21:40 <DocScrutinizer05> meh, this is a winDoesNotWork PC with ab auxiliary 50GB dedicated to a emergency linux

21:49 <xxxxx> http://privatepaste.com/3ac3c3d23a

21:50 <xxxxx> sorry for nick

21:51 <DocScrutinizer05> before it was "maximum 1024 x 768"

21:54 <DocScrutinizer05> now if only I had the faintest idea what windows means by "error=0xc000000f" and refusing to boot and zo repair the installation

21:56 <ds2> it probally was due to a bug in spelling 0xuaref00c

21:56 <ds2> :D

22:01 <DocScrutinizer05> I guess it didn't like the (EFI?)boot in MBR getting replaced by FRUB2

22:01 <DocScrutinizer05> GRUB, though what difference?

22:02 <DocScrutinizer05> I disabled dang EFI boot in BIOS and I think I heard I have to reinstall windows when type of boot changed

22:03 <DocScrutinizer05> (disabled EFI) *after* I installed Linux and GRUB2 wasn't able to boot windows into a working state

22:04 <DocScrutinizer05> so the "Windows error, please inset install CD and fix System Startup" was even before that EFI change, simply from GRUB in MBR

22:05 <DocScrutinizer05> if only I hadn't wasted 5h already to install apps n stuff in that windows

23:52 <docScr> http://privatepaste.com/60d4048448 could sombodz help with forensics?

23:53 <docScr> ntfs seems OK. sda2 is weird though, and no ida what it might be and howto recover it, or why it has yhat weird fat16 type

23:54 <docScr> idea}