Hello, On Tue, Nov 2, 2010 at 1:10 AM, Fernando Lemos <fernando...@gmail.com> wrote: > Thanks for your prompt response. Done, it's bug #31311: > > https://bugs.freedesktop.org/show_bug.cgi?id=31311
Chris Wilson's reply shed some light on this and I now understand what's going on. I commented up i915.powersave=0 to test if #580601 was gone in 2.6.36, and that made into the initrd, as I found out after examining it. Running update-initramfs -k all -u solved the issue. In 2.6.36, as Chris Wilson stated, /sys/modules/i915/parameters/powersave is 0400. I'm led to believe that at some point in initialization, after the root filesystem is mounted, modprobe goes over /etc/modprobe.d again to reset the options. This might be why leaving i915.powersave=0 commented out in the initrd worked before 2.6.36. If this is the case, then it might be nice to have the commit mentioned in the f.d.o bug report backported, perhaps. It could also be that my other initrds simply didn't have that option commented out. Anyways, the issue is now solved for me: ferna...@vostro:~$ sudo cat /sys/module/i915/parameters/powersave 0 ferna...@vostro:~$ uname -a Linux vostro 2.6.36-trunk-amd64 #1 SMP Wed Oct 27 14:28:29 UTC 2010 x86_64 GNU/Linux ferna...@vostro:~$ Please feel free to close/archive/invalidate this bug report. Sorry for any inconvenience and thanks for your time. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
