Mailinglist Archive: opensuse-factory (517 mails)

< Previous Next >
Re: [opensuse-factory] i915.modeset=0 worked with a 2.6.34-RC3 kernel, but not with RC2
  • From: Guido Berhoerster <guido+opensuse.org@xxxxxxxxxxxxxxxx>
  • Date: Sat, 10 Jul 2010 11:07:48 +0200
  • Message-id: <20100710090748.GD15670@xxxxxxxxxxxxxxxxxx>
* Greg Freemyer <greg.freemyer@xxxxxxxxx> [2010-07-09 23:11]:
On Fri, Jul 9, 2010 at 4:33 PM, Guido Berhoerster
<guido+opensuse.org@xxxxxxxxxxxxxxxx> wrote:
* Greg Freemyer <greg.freemyer@xxxxxxxxx> [2010-07-09 20:57]:
All,

I filed https://bugzilla.novell.com/show_bug.cgi?id=594542  a couple
months ago and was given a workaround of booting with i915.modeset=0
which was fine.

I've just upgraded to RC2 and that workaround is no longer working,
which is a pretty serious bug if there is not an alternate workaround
for this fairly common GPU.

Can any one give me a suggestion?

fyi: I updated the bug with this info as well as Xorg.conf and
Xorg.0.log, so if anyone is curious, check the bug.

Use nomodeset instead. And you need to manually switch to the
"intellegacy" X.org driver or you will get the VESA one by default.
--
Guido Berhoerster

Thanks Guido, it works. (At least I have X. Not sure about what
happens after it sleeps yet, but no reason to doubt the legacy
driver.)

If you or anyone knows where to document this fix in the wiki, I'd be
happy to do so.

Can you file a bug against the release notes instead? It should
contain something along the lines "if you experience problems
with Intel graphics hardware you can try disabling KMS by adding
'nomodeset' to the kernel parameters and adding 'Driver
"intellegacy"' to /etc/X11/xorg.conf.d/50-device.conf".

I can't use KMS either due to two other bugs and probably a lot
of people using Intel hardware will run into bugs/regressions
which might be worked around by disabling KMS and/or using the
2.9.1 driver.
--
Guido Berhoerster
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >