Bug 1675

Summary:	[Intel/i830] VBERestore broken in kernel i915 with 6.8.1 830 driver
Product:	xorg	Reporter:	Martin van Es <mrvanes>
Component:	Driver/intel	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	high
Version:	6.8.1
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Martin van Es 2004-10-20 04:57:24 UTC

I wasn't complete sure where to file this bug... hope this helps anyway.

2.6.9 i915 DRM driver with x.org 6.8.1 i830 breaks VBERestore functionality.

2.6.9-i830 DRM with 6.8.0-i830: Restore Ok, DRM ok
2.6.9-i830 DRM with 6.8.1-i830: crashes on startup
2.6.9-i915 DRM with 6.8.0-i830: Restore ok, dri fails: kernel module version 1.3
or greater needed
2.6.9-i915 DRM with 6.8.1-i830: Restore broken, DRM ok.

Further I noticed that Options "VBERestore" "TRUE" disables vberestore according
to the logfile and "FALSE" enables it??

Even if I set VBERestore to "FALSE" and so 'enable' vberestore for the
6.8.1-i830 driver, Restore remains broken. If I do the same for the 6.8.0-i830
driver, Restore is broken as well.

I'm a bit confused to say the least...
The main problem now is that I can't get my system working properly with the
announced replacement driver for my i830 (915) so I fear a future broken system
in the long run when I can't fall back on the 830 DRM kernel driver and/or
6.8.0-810 driver.

Platform: Laptop i830M, TFT

I'd be happy to supply more info, it's just that I don't where to start.

Martin

Comment 1 Alan Hourihane 2005-02-07 06:57:21 UTC

Have you got a logfile which shows it crashes on startup ?

Comment 2 Martin van Es 2005-02-07 07:14:23 UTC

I have no longer access to this hardware since my laptop with the i830 chipset
was stolen. I have an i855 now and all is well...
I'm VERY sorry I can't help anymore.

Comment 3 Alan Hourihane 2005-02-17 06:01:26 UTC

No problem. I'll close this.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.