Launchpad has imported 23 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=39550.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-07-26T11:35:11+00:00 Auke-n wrote: Created attachment 49565 vbios After a suspend/resume cycle, my brightness is stuck to some low value which can't be changed with the brightness buttons or nvapoke 0x61c084 0x80000200. Both of these do work before suspend. Output of "nvapeek 0x61c084" (both before and after suspend/resume): 0061c084: 00000401 Attached is /sys/kernel/debug/dri/0/vbios.rom. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/0 ------------------------------------------------------------------------ On 2011-07-26T12:19:43+00:00 Auke-n wrote: Created attachment 49572 dmesg|grep nouveau dmesg|nouveau after said suspend/resume cycle Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/1 ------------------------------------------------------------------------ On 2011-07-26T18:13:31+00:00 Emil-l-velikov wrote: Hi Auke Would you consider this as a regression ? Looking at your stripped log I can see "ACPI backlight interface available, not registering our own", thus I would say that the issue is not related to nouveau Although can you please try the following 1 Boot into runlevel 3 Append " 3" to your kernel command line 2 Make sure that nouveau is not loaded - "lsmod" will tell you if it is 2.1 Possible solution - blacklist nouveau 3 Try to adjust the brightness via acpi 3.1 Look for *brightness* in /sys/devices/ find /sys/devices -name "*bright*" 2>/dev/null 4 Suspend pm-suspend 5 Resume 6 Try to adjust the brightness again 7 Confirm/dismiss if it is a nouveau related issue I hope it helps Cheers, Emil Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/2 ------------------------------------------------------------------------ On 2011-07-26T18:24:37+00:00 Guido Trentalancia wrote: Please note that when I compared the openSUSE/jobermayr tree with mine from upstream, I found that the drm kernel module shipped by jobermayr and tagged as 20110721.2009-2.3 on openSUSE does ship separate and different ACPI bits (at least there should be differences in the include files). I do not know if that helps... Here it does not even specify the version or whether it something that suddenly stopped working or otherwise something that never worked. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/3 ------------------------------------------------------------------------ On 2011-07-26T19:06:17+00:00 Emil-l-velikov wrote: Correction 3.1 Look for brightness and/or backlight in /sys find /sys -name "*brightness*" -o -name "*backlight*" Most likely you will have files similar to ls /sys/devices/pci0000:00/0000:00:0c.0/0000:02:00.0/backlight/acpi_video0/ brightness actual_brightness max_brightness You will have /sys/class/backlight, as well Note that the /sys/class/backlight/acpi_video0 (or similar) should point to the above entry Cheers Emil Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/4 ------------------------------------------------------------------------ On 2011-07-26T20:00:34+00:00 Auke-n wrote: Emil: As you suggested, I booted without nouveau into a terminal. Indeed I have these interfaces in /sys, and before suspend/resume I could control brightness as usual. After suspend/resume, the screen stayed black (supposedly the backlight was completely off). Blindly starting X, which loaded nouveau, turned the screen on and gave me the fixed low brightness as described earlier. Seems like it's not a nouveau issue after all, so what do I do now? Guido: This is an Arch Linux install, with linux 2.6.39, nouveau-dri 7.10.3 and an xf86-video-nouveau driver that's said to be version 0.0.16_git20110531. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/5 ------------------------------------------------------------------------ On 2011-08-10T06:14:08+00:00 Skeggsb wrote: Can I get the output of the following, both before and after suspend/resume nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe100 8; nvapeek 0xe280 8 Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/6 ------------------------------------------------------------------------ On 2011-08-10T06:14:48+00:00 Skeggsb wrote: Correction: nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8 Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/7 ------------------------------------------------------------------------ On 2011-08-10T11:19:14+00:00 Auke-n wrote: Can't really say if it's a regression, but it hasn't worked for me in a while and I never bothered fixing it. # ./nvapeek 0xe100; ./nvapeek 0xe28c; ./nvapeek 0xe104 8; ./nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000180 0000e104: 72266640 0441474b 0000e280: 24444747 00000000 UPower suspend... # ./nvapeek 0xe100; ./nvapeek 0xe28c; ./nvapeek 0xe104 8; ./nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000180 0000e104: 72266240 0441474b 0000e280: 24444747 00000000 Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/8 ------------------------------------------------------------------------ On 2011-08-10T22:53:47+00:00 Skeggsb wrote: Heh. Okay.. Well, everything I know of on the GPU side that's relevant to the backlight level appears to be in order.. So, I'm out of ideas for the moment. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/9 ------------------------------------------------------------------------ On 2011-09-22T21:16:00+00:00 Emil-l-velikov wrote: Auke Can you try the following 1. Boot with "nouveau.force_post=1" appended to your kernel command like 2. Do not suspend, but simply try to change the brightness If it is stuck then the issue may be nouveau related, if not ... Btw have you tried the blob ? Does it have the same issue Cheers Emil Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/10 ------------------------------------------------------------------------ On 2011-09-25T10:13:15+00:00 Rick-hendricksen wrote: I have the exact same problem as Auke, for as long as I have the laptop (about 2 years). This problem used to occur with the blob as well (if I remember correctly) but it does work now. I am using an HP Elitebook 8530w (nVidia Corporation G96M [Quadro FX 770M] (rev a1)) on fedora 15. dmesg says: nouveau 0.0.16 20090420 yum says: xorg-x11-drv-nouveau.x86_64 1:0.0.16-24.20110324git8378443.fc15 mesa-dri-drivers: 7.11-1 (In reply to comment #10) > Auke > > Can you try the following > > 1. Boot with "nouveau.force_post=1" appended to your kernel command like > 2. Do not suspend, but simply try to change the brightness > > If it is stuck then the issue may be nouveau related, if not ... > > Btw have you tried the blob ? Does it have the same issue > > > Cheers > Emil Brightness control does not work with this option for me. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/11 ------------------------------------------------------------------------ On 2011-09-25T11:21:32+00:00 Emil-l-velikov wrote: Rik Can you please indicate what exactly do you mean with "Brightness control does not work with this option for me." Does it work before suspending the system? Can you please attach your dmesg log, as it is the one relevant in this case (whereas xf86-video-nouveau, mesa and libdrm are not) Auke, Rik AFAIK brightness/backlight is(can be) controlled via 1. ACPI 2. platform specific - (asus-laptop, samsung-laptop, thinkpad ...) 3. the gpu/card itself On various system different ones work correctly By default nouveau does not register it's device if an ACPI one exists Note that the blob has similar behaviour but they have an option to override it. If you suspect that the ACPI backlight control is buggy you can disable it by appending "acpi_backlight=vendor" to your kernel command line This will fall back to either 2. or 3. - dmesg will tell you which one Feel free to give it a try Cheers Emil Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/12 ------------------------------------------------------------------------ On 2011-09-25T12:08:35+00:00 Rick-hendricksen wrote: (In reply to comment #12) > Rik > > Can you please indicate what exactly do you mean with > > "Brightness control does not work with this option for me." > > Does it work before suspending the system? Brightness control does not work before suspend, I did not try suspending. So no. > Can you please attach your dmesg log, as it is the one relevant in this case > (whereas xf86-video-nouveau, mesa and libdrm are not) will post in a few minutes (need to get laptop) > > Auke, Rik > > AFAIK brightness/backlight is(can be) controlled via > 1. ACPI > 2. platform specific - (asus-laptop, samsung-laptop, thinkpad ...) > 3. the gpu/card itself > > On various system different ones work correctly > > By default nouveau does not register it's device if an ACPI one exists > Note that the blob has similar behaviour but they have an option to override > it. > > If you suspect that the ACPI backlight control is buggy you can disable it by > appending "acpi_backlight=vendor" to your kernel command line I tried that. It works exactly the same as without this option. Brightness control works fine before suspend, fails after. > This will fall back to either 2. or 3. - dmesg will tell you which one > > Feel free to give it a try > > Cheers > Emil Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/13 ------------------------------------------------------------------------ On 2011-09-25T12:22:14+00:00 Rick-hendricksen wrote: Created attachment 51586 Dmesg output for the various testcases dmesgbacklightisvendor.txt : using acpi_backlight=vendor dmesgforcepost.txt : using nouveau.force_post=1 dmesgnormal.txt : default Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/14 ------------------------------------------------------------------------ On 2011-09-26T19:16:29+00:00 Emil-l-velikov wrote: (In reply to comment #13) [snip] > Brightness control does not work before suspend, I did not try suspending. So > no. [snip] > I tried that. It works exactly the same as without this option. Brightness > control works fine before suspend, fails after. I see a bit of contradiction in here Firstly can you try nouveau kernel git tree [1], as it includes some patches regarding backlight/brightness Note: Fedora may have precompiled package that is up-to date (search for koji) If it still fails please record the following example "with option "xxxxx" (acpi_backlight=vendor, nouveau.force_post=1) before suspend - works, after - stuck" it may be worth checking the registers (see comment 7) in each case as well Cheers Emil [1] http://cgit.freedesktop.org/nouveau/linux-2.6/ Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/15 ------------------------------------------------------------------------ On 2011-09-27T14:05:55+00:00 Rick-hendricksen wrote: (In reply to comment #15) > (In reply to comment #13) > [snip] > > Brightness control does not work before suspend, I did not try suspending. > > So > > no. > [snip] > > I tried that. It works exactly the same as without this option. Brightness > > control works fine before suspend, fails after. > > I see a bit of contradiction in here > > Firstly can you try nouveau kernel git tree [1], as it includes some patches > regarding backlight/brightness > > Note: Fedora may have precompiled package that is up-to date (search for koji) I cloned the git repo you linked, and compiled my kernel (which works), but it has the exact same issues as before. $ uname -r 3.1.0-rc7+ > If it still fails please record the following > > example > "with option "xxxxx" (acpi_backlight=vendor, nouveau.force_post=1) > before suspend - works, after - stuck" > with option: none before suspend: works, after: stuck to low value with option: nouveau.force_post=1 before suspend: stuck to low value, after: stuck to low value with option: acpi_backlight=vendor before suspend: works, after: stuck to low value with option: acpi_backlight=vendor nouveau.force_post=1 before suspend: stuck to low value, after: stuck to low value > it may be worth checking the registers (see comment 7) in each case as well Maybe tomorrow, it took me long enough to get that kernel working. (I need envytools right?) > Cheers > Emil > > [1] http://cgit.freedesktop.org/nouveau/linux-2.6/ Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/16 ------------------------------------------------------------------------ On 2011-09-27T18:52:06+00:00 Emil-l-velikov wrote: (In reply to comment #16) > with option: none > before suspend: works, after: stuck to low value > with option: nouveau.force_post=1 > before suspend: stuck to low value, after: stuck to low value > with option: acpi_backlight=vendor > before suspend: works, after: stuck to low value > with option: acpi_backlight=vendor nouveau.force_post=1 > before suspend: stuck to low value, after: stuck to low value Thanks this is great > > > it may be worth checking the registers (see comment 7) in each case as well > > Maybe tomorrow, it took me long enough to get that kernel working. (I need > envytools right?) Yes you would need envytools Peeks for "none" and "nouveau.force_post=1" would be enough - before and after suspend Can you attach your vbios as well please [2] [2] $ nvagetvbios > vbios.rom Cheers Emil > > > Cheers > > Emil > > > > [1] http://cgit.freedesktop.org/nouveau/linux-2.6/ Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/17 ------------------------------------------------------------------------ On 2011-09-28T15:01:55+00:00 Rick-hendricksen wrote: (In reply to comment #17) > Peeks for "none" and "nouveau.force_post=1" would be enough - before and after > suspend normal boot: # nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266640 0441474b 0000e280: 44444747 00000000 # pm-suspend # nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266240 0441474b 0000e280: 44444747 00000000 using option: nouveau.force_post=1 # nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266240 0441474b 0000e280: 44444747 00000000 # pm-suspend # nvapeek 0xe100; nvapeek 0xe28c; nvapeek 0xe104 8; nvapeek 0xe280 8 0000e100: 001c1100 0000e28c: 00000100 0000e104: 72266240 0441474b 0000e280: 44444747 00000000 > Can you attach your vbios as well please [2] > > [2] $ nvagetvbios > vbios.rom nvagetvbios didnt exist, so I used nvagetbios (I assume you made a typo) > > Cheers > Emil > Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/18 ------------------------------------------------------------------------ On 2011-09-28T15:02:40+00:00 Rick-hendricksen wrote: Created attachment 51716 rick's vbios Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/19 ------------------------------------------------------------------------ On 2011-12-12T09:56:46+00:00 Auke-n wrote: Any updates regarding this bug? Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/20 ------------------------------------------------------------------------ On 2012-01-30T21:00:11+00:00 Jesse Brandeburg wrote: I am experiencing this bug as well, HP 8530W, brightness controls don't work after resume. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/24 ------------------------------------------------------------------------ On 2012-01-31T01:57:33+00:00 Jesse Brandeburg wrote: I tried force_post=1, screen is dark even before suspend (even before going into X, just loading frame buffer) - this is a clue the driver is forcing the brightness into this mode, right? Of course, the tip of tree nouveau won't even load now due to the MXM changes, so I haven't been able to test *it* yet, but that is another bug that I'm trying to help narrow down. Reply at: https://bugs.launchpad.net/nouveau/+bug/921321/comments/25 ** Changed in: nouveau Status: Unknown => Confirmed ** Changed in: nouveau Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
