Panasonic CF-52 (Radeon X2100), and xorg does not work with F8T3

[Adam Jackson]

On Tue, 2007-10-30 at 09:41 -0500, Todd Denniston wrote:
> Adam Jackson wrote, On 10/30/2007 08:53 AM:
> > On Mon, 2007-10-29 at 18:06 -0500, Todd Denniston wrote:
> >> Folks,
> >> we just tried an install on a Panasonic CF-52 (TOUGHBOOK laptop) using an ATI
> >> Radeon X2100.
> >> 1) had to install in text mode because X is just black screen.
> >> 2) after install startx results in the same situation. (consistency is nice)
> >> 3) by default xorg.conf is pointing at vesa instead of an ati driver, so it
> >> does not do a PCI scan, it just hangs at a black screen.
> > 
> > The 'ati' driver in F8 does not support R600 chips.  You have an R600
> > chip.  It ain't gonna work.
> 
> Care to clue me on how you see it is an R600?
> No doubt it is, I just don't see how to figure that from the data I have.

The X2k series are generally R600 chips.  It's easier to define support
in terms of chip revision than marketing name because some of the
marketing names are just lies.

> > What does the X log look like when you use the vesa driver?
> 
> The Xorg.0.log (as opposed to the Xorg.0.log.ati) in my first email was a log 
> from the vesa driver, sorry I did not make that clear.

I missed it, for being too short!  Weird.  I have no idea why it'd fail
there.

> BTW, having SELinux on or off does not make a functional difference in xorg 
> working, but I did notice when I ran xorg with SELinux on the following 
> messages appeared in /var/log/messages:
> setroubleshoot: #012    SELinux is preventing /usr/bin/Xorg (xdm_xserver_t) 
> "use" to /dev/tty1 (local_login_t).#012     For complete SELinux messages. run 
> sealert -l cfd857e5-b182-431b-b9bf-acba1e48c0cc
> setroubleshoot: #012    SELinux is preventing /usr/bin/Xorg (xdm_xserver_t) 
> "signal" to <Unknown> (unconfined_t).#012     For complete SELinux messages. 
> run sealert -l b56c8443-e433-47c2-aa1a-b3a622cd66e1
> setroubleshoot: #012    SELinux is preventing /usr/bin/Xorg (xdm_xserver_t) 
> "getpgid" to <Unknown> (unconfined_t).#012     For complete SELinux messages. 
> run sealert -l d2960006-8d4a-4b08-abe6-9d4f6b780888
> I have ran the `sealert -l randnum` commands if you want/need to see the output.

Those should all be allowed actions, but if it still fails with selinux
off then I'm stumped.  I can't even think of where to begin looking.

Is your /usr/bin/Xorg not suid root for some reason?

- ajax