Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 455468

Summary: >x11-base/xorg-server-1.12.1 non-functional on PPC
Product: Gentoo Linux Reporter: Jean-Claude Gervais <progman3k>
Component: [OLD] UnspecifiedAssignee: Gentoo X packagers <x11>
Status: RESOLVED DUPLICATE    
Severity: normal CC: gseanmcg, ppc
Priority: Normal    
Version: unspecified   
Hardware: PPC   
OS: Linux   
See Also: https://bugs.gentoo.org/show_bug.cgi?id=446253
Whiteboard:
Package list:
Runtime testing required: ---

Description Jean-Claude Gervais 2013-02-04 17:14:02 UTC
Ever since xorg-server 1.12.1 was removed from portage, I have not been able to get X working.

The initial forum post:
https://forums.gentoo.org/viewtopic-p-7237602.html

The bug eventually posted in the freedesktop.org Xorg database
https://bugs.freedesktop.org/show_bug.cgi?id=60180

The investigator from the xorg team suggested that the problem may be with a gentoo-specific modification.


Reproducible: Always

Steps to Reproduce:
1.Install xorg-server > 1.12.1
2.run startx

Actual Results:  
Server terminates with

[  7084.295] (II) [KMS] Kernel modesetting enabled.
[  7084.295] (EE) No devices detected.
[  7084.295]
Fatal server error:
[  7084.295] no screens found
[  7084.296] (EE)
Comment 1 Chí-Thanh Christopher Nguyễn gentoo-dev 2013-02-04 17:47:35 UTC
I vaguely remember that the ppc issue was udev related. But I don't have a link right now.

Anyway, the only Gentoo patch to xorg-server-1.12.4 is the patch to not build ACPI code. ACPI does not even exist on ppc systems, so this is unlikely to cause your problems.
Comment 2 Jean-Claude Gervais 2013-02-04 17:54:02 UTC
udev does seem to be functioning but the X server reports no devices found when run from startx or crashes if Xorg -configure is run.

What can I do to help?
Comment 3 Chí-Thanh Christopher Nguyễn gentoo-dev 2013-02-04 17:56:26 UTC
That X -configure crashes is expected with KMS.

You can check qlop -lu output which other packages were upgraded at the same time as xorg-server.

Old ebuilds can be retrieved from CVS http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-base/xorg-server/ (click on show dead files) and copied to a local overlay.
Comment 4 Jean-Claude Gervais 2013-02-04 18:41:45 UTC
I originally noticed the problem around October/November (or whenever xorg-server > 1.12.1 went stable) and would downgraded xorg-server back to 1.12.1 and exclude xorg-server from every world-update subsequently.

But eventually I performed a world update that broke things (including X) which revdep-rebuild fixed but at the same time xorg-server 1.12.1 had been removed from portage, so I couldn't go back.

Here's the output of qlop -lu
http://gentoo.pastebin.ca/2310682
Comment 5 Jean-Claude Gervais 2013-02-04 21:33:52 UTC
cd /usr/portage/x11-base/xorg-server/
wget http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-base/xorg-server/xorg-server-1.12.1.ebuild?revision=1.1

ebuild xorg-server-1.12.1.ebuild digest

added the line 
=x11-base/xorg-server-1.12.1 ~ppc
to /etc/portage/package.keywords

emerge -vD =x11-base/xorg-server-1.12.1

qlist -I -C x11-drivers/

emerge -vD xf86-input-evdev xf86-video-ati

startx now takes a long time to run, even blinking up to 3 times during 35-45 seconds and then 3 graphical-mode xterms appear. X is running!

I re-added xdm to the default runlevel and issued the shutdown command

When the computer booted back up, it took it about 4-5 minutes and 3-4 blinks but at the end a message came up saying gdm could not start, even though the Xorg.0.log file says everything worked!

Xorg.0.log:
http://gentoo.pastebin.ca/2310724
Comment 6 Joe Jezak (RETIRED) gentoo-dev 2013-03-28 13:45:08 UTC
I'd guess that this is the same bug as the one I'm marking it as a duplicate of. Basically, the PCI device detection seems broken. You can work around this by specifying the BusID of the device. Also remember that the driver needs to support KMS to work with this version of X, the older UMS drivers no longer seem to work.

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