On Sat, Aug 6, 2011 at 7:09 AM, Tom Gundersen <teg@xxxxxxx> wrote: > On Sat, Aug 6, 2011 at 6:07 AM, C Anthony Risinger <anthony@xxxxxxx> wrote: >> On Fri, Jul 29, 2011 at 3:35 PM, Tom Gundersen <teg@xxxxxxx> wrote: >>> On Fri, Jul 29, 2011 at 10:43 AM, Meyithi <mail@xxxxxxxxxxx> wrote: >>>> It appears that the quiet kernel parameter also sets a quiet flag in >>>> Syslinux as well, which is doing something horrible to early framebuffers. >>>> As to the original question, it seems that "quiet" and "loglevel=4" are >>>> identical indeed, unless you use Syslinux. >>> >>> For what it's worth: I'm using syslinux with quiet without seeing this >>> problem (using i915). >>> >>> Also, the last kernel commit I pointed to in a previous email shows a >>> place in the boot code where "quiet" is indeed different from >>> "loglevel=4", just in case someone came across a different problem. >> >> i finally got around to trying this; it eliminated the "white box" >> effect for me, on these two machines anyway (nvidia/radeon) > > Sorry, what did you try? Revert the commit? beh sorry about that -- completely wrong context no i only removed `quiet` and added `loglevel=4` ... this alone eliminated the artifacts. -- C Anthony
