Wine (?) spoiling F12 boot : MITIGATED
beartooth at comcast.net
Mon Dec 28 14:56:50 UTC 2009
On Sun, 27 Dec 2009 17:22:17 +0000, I BeartoothHOS wrote:
> Between your post and Tom Horsley's, I happened to think of
> changing the driver -- and did, from nv to vesa. I don't now recall
> exactly what all else I did, but I do remember an oddity.
> At one point, I tried again to edit xorg.conf, and got a message
> saying it didn't exist. I ran system-config-display instead to create
> one -- and it did, with vesa instead of nv.
> After all that, I can still only set the display up to 1280x1024,
> not 1680x1050 (which this machine, I'm sure, did support before). But
> that's within the monitor's own ability to adapt to.
The same thing happened last night and this morning with my #1
machine, and the same mitigation worked : vesa instead of nv, and
1280x1024 instead of 1680x1050, with at leas one stage having been done
with ssh from another machine. (I didn't think soon enough to try booting
it into init 3; my guess is that that'd've worked too.)
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
More information about the users