Bug 649973 - radeon: KMS not being the default on LiveCD/X crashes with radeonhd driver during start
Summary: radeon: KMS not being the default on LiveCD/X crashes with radeonhd driver du...
Status: RESOLVED DUPLICATE of bug 609607
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Factory
Hardware: i686 Other
: P3 - Medium : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-28 18:38 UTC by Gabriel Burt
Modified: 2010-10-28 22:27 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Xorg.0.log (48.32 KB, text/plain)
2010-10-28 18:59 UTC, Gabriel Burt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel Burt 2010-10-28 18:38:47 UTC
I installed the recent openSUSE 11.4 GNOME live cd on a Lenovo T60p w/ ATI graphics, and then changed the zypper repos to the factory ones, and did zypper dup.  I believe this worked for a day or two, but then another dup seemed to break things.  If I boot up in failsafe mode, and run `startx` on the command line, I get:

<snip>
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "fglrx"
</snip>

I don't know if the Live CD comes with fglrx and running `zypper dup` removed it, or what.  I can't see that fglrx is explicitly mentioned in any config file, so I'm not sure how to solve this.
Comment 1 Gabriel Burt 2010-10-28 18:59:01 UTC
Created attachment 397636 [details]
Xorg.0.log
Comment 2 Stefan Dirsch 2010-10-28 22:25:48 UTC
fglrx is just the first driver, which is tried. Then radeonhd. If that fails due to KMS being enabled it is radeon. The issue here is 

1) The use of radeonhd results in a Segfault (see end of logfile). This happens
   deep in EXA if I recall correctly.
2) KMS not being the default on LiveCDs. This is Bug #609607

Closing as dup of Bug #609607.

*** This bug has been marked as a duplicate of bug 609607 ***