<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [845G regression] on Linux 3.7/3.8: LED monitor "Auto Adjust in Progress" 6-10 seconds at boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=59572#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [845G regression] on Linux 3.7/3.8: LED monitor "Auto Adjust in Progress" 6-10 seconds at boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=59572">bug 59572</a> from <a class="email" href="mailto:mlsemon35@gmail.com" title="mlsemon35@gmail.com">mlsemon35@gmail.com</a> <pre>(In reply to <a href="show_bug.cgi?id=59572#c1">comment #1</a>) > I guess the timings of your resolution slightly changed due to the slightly > different video mode your now using. Which can take the screen longer to > adjust to. Questions to check: I guess it's best put this way: For kernels 3.6.11 and prior, the default fbcon boot goes like this: > - does the screen eventually show the console, or does that sometimes fail? I think I get the same results every time: A good cmdline leads to text on a screen at the specified resolution. A bad cmdline leads to no text on a blank console. Some settings of resolution and Hz seem to cause the driver to default to the monitor's native resolution. [Read more.] What seems to change is the "same results" from kernel to kernel, and I've forgotten what worked on my 3.6.11-EOL diaspora journey. I think it went 3.6.11 to 3.7.{0,1} to 3.8-rc{1,2,3,4}. > - if you have time, bisecting why the old video mode doesn't work on the > kernel cmdline would be interesting. Yes, that was interesting! I didn't get too scientific with it, but looks like the -8 switch leads to a blank screen each time. -15, -16, -24, and -32 work, though -24 seems to lead to the same results as -32. The @Hz works, so long as it matches a valid number for Hz. Resolutions work, too, so long as they match a valid number. I didn't see a difference between using "M" and not using "M", and really, I didn't notice it much when I thought it made a difference. [It's a holdover from my time using i810fb on an older PC.] As for blank times and such, it went like this: 1024x768-32: 10s delay, rgba 8/16,8/8,8/0,0/0 (fbset) 800x600-16: 2s "Auto Adjust in Progress" shows over unblanked screen, real blank time not noticed, rgba 5/11,6/5,5/0,0/0 800x600-8: booted to blank screen 640x480-8: booted to blank screen 640x480-15: 10s delay, rgba 5/10,5/5,5/0,1/15 1024x768M-16@75: OK, blank time was variable 1152x768-16: 2s blank -16: 1280x1024@60, 16bpp, blank time not noticed Hmmm...maybe my questions should include "What happened to 8bpp?"</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>