Bug 3295

Summary: Using radeon driver causes next boot of vesa driver to fail!
Product: xorg Reporter: Torfinn Ingolfsen <tingo>
Component: Driver/RadeonAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: high    
Version: 6.8.99.5   
Hardware: x86 (IA32)   
OS: FreeBSD   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log file (vesa driver) after reboot
none
Xorg log file (vesa driver) after using the radeon driver
none
Xorg log file (radeon driver). After using this, the vesa driver changes none

Description Torfinn Ingolfsen 2005-05-15 02:35:42 UTC
After a reboot of the machine, the vesa driver can do 1280x1024. After using the
radeon driver, the vesa driver complains that the mode 1280x1024 doesn't exist,
and tries to do 1400x1050 instead. This looks a lot like bug no. 1345, except
for the fact that I'm using 6.8.99.5. Hardware is Athlon 64 on a MSI RS480M2-IL
mainboard, which have onboard ATI radeon Xpress 200 grahics. Bug 3242 explains
why I can't use the radeon driver.
Comment 1 Torfinn Ingolfsen 2005-05-15 02:37:18 UTC
Created attachment 2680 [details]
Xorg log file (vesa driver) after reboot
Comment 2 Torfinn Ingolfsen 2005-05-15 02:38:14 UTC
Created attachment 2681 [details]
Xorg log file (vesa driver) after using the radeon driver
Comment 3 Torfinn Ingolfsen 2005-05-15 02:39:22 UTC
Created attachment 2682 [details]
Xorg log file (radeon driver). After using this, the vesa driver changes
Comment 4 T. Hood 2005-09-26 04:13:11 UTC
This must also be a bug in the vesa driver.
Comment 5 Erik Andren 2006-07-28 09:54:39 UTC
Is this bug still an issue?
Comment 6 Torfinn Ingolfsen 2006-07-28 11:06:33 UTC
(In reply to comment #5)
> Is this bug still an issue?

No, I can change back and forth between the vesa driver and the radeon driver
now without problem.
I'm using 
FreeBSD 6.1-stabel from May 10th, 2006
and 
Xorg 6.9.0
Comment 7 Erik Andren 2006-07-28 12:22:21 UTC
Closing.

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.