<div>On 5/20/07, Robert P. J. Day <<a href="mailto:rpjday@mindspring.com">rpjday@mindspring.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Sun, 20 May 2007, dragoran wrote: > On 5/20/07, Robert P. J. Day <<a href="mailto:rpjday@mindspring.com">rpjday@mindspring.com</a>> wrote: > > > > On Sun, 20 May 2007, Will Woods wrote: > > > > > On Sat, 2007-05-19 at 23:27 -0400, David Kramer wrote: > > > > This is my first experience with a testing release, so I apologize if > > > > I'm not reporting this right, or not giving enough information. > > > > > > > > I just got a Lenovo Thinkpad T60p. It's got a 15.4" WSXGA+ > > > > TFT/1680x1050 (16:10) screen driven by a ATI Mobility Fire GL V5250 > > 256MB. > > > > > > > > When I attempt a graphical install of F7-test4, after the few initial > > > > "Loading..." screens, I get a few flashes with pretty patterns, then > > the > > > > screen turns all blue with no writing, and stays that way > > indefinitely. > > > > > > Hmm. Sounds like it could be this bug: > > > <a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239605"> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239605</a> > > > Have you tried putting "resolution=1680x1050" on the commandline when > > > you boot? (I think just need to hit 'Tab' to edit the boot line) > > > > does that "resolution=" boot option actually exist? it's not > > mentioned in the kernel doc file Documentation/kernel-parameters.txt. > > anaconda also parses the kernel commandline so it must not be a kernel > option but anaconda is the *installer*. what would anaconda have to do with command line options at *boot* time? or am i misunderstanding something here?</blockquote><div> the kernel commandline can be read from any app that can read /proc/cmdline anaconda abuses this to get options at boot time like "linux rescue" etc. </div> </div>