F18 doesn't see full laptop screen resolution

Adam Williamson awilliam at redhat.com
Sat Feb 2 00:26:53 UTC 2013


On Fri, 2013-02-01 at 16:06 -0800, Per Bothner wrote:
> On 02/01/2013 03:51 PM, Adam Williamson wrote:
> > Well, no it isn't. You might not bother to configure wireless when you
> > install if you don't need it. But that just doesn't apply to this case
> > at all. 'basic graphics mode' is pretty clearly positioned as a
> > workaround for dealing with graphics problems. It is not offered as an
> > option very prominently, you have to go dig and find it. There's no
> > particular reason you'd do so unless you had an explicit reason to. It's
> > not like, on a 'normal' install path, you have a dialog that lets you
> > pick Basic or Not-Basic and some kind of compelling reason to pick
> > Not-Basic. Not-Basic is what 99% of people will see. Basic is something
> > you only see if you picked it explicitly from a fairly obscure place,
> > which is only going to happen if a) you figured or read that you needed
> > to do so to deal with a graphics problem you encountered when first
> > trying in Non-Basic, or b) you twiddle with stuff way more than is good
> > for you.
> >
> > I'm just not convinced we need to go to great lengths to deal with case
> > b), which is you. It happened to you. You complained. We told you what
> > happened. You now know. This seems like a perfectly appropriate way of
> > dealing with the problem, given the very small number of people who are
> > likely to encounter it.
> 
> Ok - fair enough.  I did the install a couple of weeks ago, so I don't
> remember exactly why I had to (or thought I had to use) Basic mode.
> (Using was F17 was an acceptable work-around which is one reason I
> didn't investigate earlier.  I'll now see if I can get F18 usable.

Just dropping 'nomodeset' from the cmdline should probably do the job.
It's actually also supposed to write an xorg.conf snippet which forces
use of the vesa driver, but I believe that mechanism's been broken for a
while, so you only have to kill 'nomodeset' and it should bounce back to
normal.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the test mailing list