Bug 445419 - Assorted video drivers (mga/r128/?) broken on ppc
Assorted video drivers (mga/r128/?) broken on ppc
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati (Show other bugs)
powerpc Linux
low Severity low
: ---
: ---
Assigned To: Dave Airlie
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-05-06 15:33 EDT by Kevin Fenzi
Modified: 2018-04-11 04:47 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 13:29:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Xorg.0.log file (10.68 KB, text/plain)
2008-05-06 15:33 EDT, Kevin Fenzi
no flags Details
Xorg 'startx -- -logverbose 255' log file with mga driver and usefbdev true (6.75 KB, text/plain)
2008-05-12 11:44 EDT, Jarod Wilson
no flags Details
Xorg 'startx -- -logverbose 255' log file with mga driver and usefbdev false (17.50 KB, text/plain)
2008-05-12 11:47 EDT, Jarod Wilson
no flags Details

  None (edit)
Description Kevin Fenzi 2008-05-06 15:33:31 EDT
ppc32 box (a g4 tower) with: 

0000:00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP

X won't start. 


The end of the /var/log/Xorg.0.log (will attach the entire thing): 
(II) R128(0): PCI bus 0 card 16 func 0
(**) R128(0): Depth 24, (--) framebuffer bpp 32
(II) R128(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) R128(0): Default visual is TrueColor
(**) R128(0): Option "UseFBDev" "true"
(II) R128(0): VGAAccess option set to FALSE, VGA module load skipped
(==) R128(0): RGB weight 888
(II) R128(0): Using 8 bits per RGB (8 bit DAC)
(**) R128(0): Using framebuffer device
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"

(II) Loading /usr/lib/xorg/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
        compiled for, module version = 0.0.2
        ABI class: X.Org Video Driver, version 4.0
(WW) open /dev/fb2: No such file or directory
(WW) open /dev/fb3: No such file or directory
(WW) open /dev/fb4: No such file or directory
(WW) open /dev/fb5: No such file or directory
(WW) open /dev/fb6: No such file or directory
(WW) open /dev/fb7: No such file or directory
(EE) Unable to find a valid framebuffer device
(EE) R128(0): Failed to open framebuffer device, consult warnings and/or errors
above for possible reasons
        (you may have to look at the server log to see warnings)
(II) UnloadModule: "r128"
(II) UnloadModule: "fbdevhw"
(II) Unloading /usr/lib/xorg/modules/linux//libfbdevhw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Happy to provide more info, or access to the machine (it's a test box).
Comment 1 Kevin Fenzi 2008-05-06 15:33:31 EDT
Created attachment 304678 [details]
Xorg.0.log file
Comment 2 David Woodhouse 2008-05-08 14:54:39 EDT
Hm, why isn't it using /dev/fb0? Does it work if you remove the UseFbdev option?
Comment 3 Kevin Fenzi 2008-05-08 15:28:24 EDT
Well, it's at least opening it. 
/dev/fb0 does exist. 

If you remove the 'UseFbdev' option it tries to use it anyhow, as its default on
ppc apparently. If you set it to "false" it blows up like so: 

(II) R128(0): initializing int10
(II) R128(0): No legacy BIOS found -- trying PCI

0: /usr/bin/Xorg(xf86SigHandler+0x94) [0x10082e34]
1: [0x100364]
2: /usr/lib/xorg/modules//libint10.so(LockLegacyVGA+0x50) [0xf09ec50]
3: /usr/lib/xorg/modules//libint10.so(xf86ExtendedInitInt10+0x1e4) [0xf0a2f84]
4: /usr/lib/xorg/modules//libint10.so(xf86InitInt10+0x28) [0xf09eac8]
5: /usr/lib/xorg/modules/drivers//r128_drv.so(R128PreInit+0x65c) [0xf14e49c]
6: /usr/bin/Xorg(InitOutput+0xa00) [0x10066140]
7: /usr/bin/Xorg(main+0x288) [0x10022178]
8: /lib/libc.so.6 [0x481618f0]
9: /lib/libc.so.6 [0x48161ab0]

Fatal server error:
Caught signal 7.  Server aborting

If you use 'driver "fbdev"' it works and brings up X. 

Not sure where the fail is here... r128 driver? installer not defaulting to
'fbdev' ? /dev/fb0 not working?

Comment 4 Jarod Wilson 2008-05-09 11:29:43 EDT
I've got a powerbook g3 here has the same problem (also r128). I've threatened
to take it downstairs and slap it in front of ajax, but haven't got around to it
Comment 5 Jarod Wilson 2008-05-09 16:26:41 EDT
The mga driver is equally broken on a ppc64 box I've got (Matrox G450 card).
Comment 6 David Woodhouse 2008-05-10 05:51:35 EDT
Interesting. It's working fine here with a G550 on Efika. What machine?
Comment 7 Kevin Fenzi 2008-05-10 11:47:10 EDT
Mine is a G4 tower... 
smolt profile: 

Comment 8 Jarod Wilson 2008-05-12 01:30:14 EDT
My ppc64 box is an IBM IntelliStation something or other, dual PPC970... Can dig
up further details in the morning.
Comment 9 Jarod Wilson 2008-05-12 10:05:31 EDT
# cat /proc/cpuinfo 
processor       : 0
cpu             : PPC970MP, altivec supported
clock           : 2519.967993MHz
revision        : 1.1 (pvr 0044 0101)

processor       : 1
cpu             : PPC970MP, altivec supported
clock           : 2519.967993MHz
revision        : 1.1 (pvr 0044 0101)

timebase        : 14318000
platform        : pSeries
machine         : CHRP IBM,7047-185
Comment 10 David Woodhouse 2008-05-12 11:02:11 EDT
Can you attach the logfile generated with '--logverbose 255'? We should probably
have a separate bug for the MGA failure.
Comment 11 Jarod Wilson 2008-05-12 11:44:37 EDT
Created attachment 305140 [details]
Xorg 'startx -- -logverbose 255' log file with mga driver and usefbdev true

Attached log output is from trying to fire up X via 'startx -- -logverbose 255'
with the below inlined xorg.conf. I'm pretty sure its identical to what I was
getting with r128 in my powerbook.

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen	    0  "Screen0" 0 0

Section "Device"
	Identifier  "Videocard0"
	Driver	    "mga"
	Option	    "UseFBDev" "true"

Section "Screen"
	Identifier "Screen0"
	Device	   "Videocard0"
	DefaultDepth	 24
	SubSection "Display"
		Viewport   0 0
		Depth	  24
Comment 12 Jarod Wilson 2008-05-12 11:47:57 EDT
Created attachment 305141 [details]
Xorg 'startx -- -logverbose 255' log file with mga driver and usefbdev false

If UseFBDev is set to false, the X log seems to suggest things started up okay,
but all I see is a blank screen. The light on the monitor is green though, not
orange, so it apparently thinks its getting a signal... However, running 'ps ax
|grep Xorg' doesn't show any running X server process.
Comment 13 Kevin Fenzi 2008-05-12 12:13:04 EDT
Oddly, trying --logverbose 255 here doesn't seem to get any additional output. 
It takes the argument, but just logs the same amount of stuff. ;( 

I will poke at it a bit more and see if I can get it to take it...
Comment 14 David Woodhouse 2008-05-13 12:27:22 EDT
Sorry, it should be just '-logverbose 255'. Not two dashes. And just 'Xorg
-logverbose 255' would be better than startx. Or even run it in GDB. If it
crashes, show the backtrace.
Comment 15 Jarod Wilson 2008-05-13 14:47:02 EDT
ajax has my powerbook in front of him. The primary problem is an altered path in
sysfs, so he's got r128 coming up on my powerbook now. Not sure when to expect
an updated package... ajax?
Comment 16 Bug Zapper 2008-05-14 06:44:17 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 17 Matěj Cepl 2008-06-12 10:15:31 EDT
(In reply to comment #15)
> ajax has my powerbook in front of him. The primary problem is an altered path in
> sysfs, so he's got r128 coming up on my powerbook now. Not sure when to expect
> an updated package... ajax?

Note, that putting bug in NEEDINFO against many developers is one of the most
secure ways how to get bug lost.
Comment 18 Robert Story 2008-06-12 11:06:25 EDT
I had to install F9 via text mode on my Powerbook (lspci reports 'Rage Mobility
M3' using driver 'aty128fb'), and system-config-display can't start either
9screen 'blooms').. Does this card fall under 'r128', or should I file a
separate bug?

(I tried F8 too, same result)
Comment 19 François Cami 2009-02-07 10:38:22 EST
Kevin, Jarod,
Does this still happen on F10 ?
Comment 20 Kevin Fenzi 2009-02-09 15:05:03 EST
Not sure. The machine is running rawhide now. 
I can see if it's ok in rawhide, and possibly do a f10 install on it to test if you like. 
Will come back with more info soon.
Comment 21 Kevin Fenzi 2009-02-12 18:25:27 EST
Yeah, it still blows up in rawhide:

(II) R128(0): Using 8 MB AGP aperture
(II) R128(0): Using 1 MB for the ring buffer
(II) R128(0): Using 2 MB for vertex/indirect buffers
(II) R128(0): Using 5 MB for AGP textures
(II) R128(0): Memory manager initialized to (0,0) (800,2457)
(II) R128(0): Reserved area from (0,600) to (800,602)
(II) R128(0): Largest offscreen area available: 800 x 1855
(II) R128(0): Reserved back buffer from (0,602) to (800,1202)
(II) R128(0): Reserved depth buffer from (0,1202) to (800,1803)
(II) R128(0): Reserved depth span from (0,1802) offset 0x57fd00
(II) R128(0): Reserved 8704 kb for textures at offset 0x77f880
(II) R128(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        Indirect CPU to Screen color expansion
        Solid Lines
        Dashed Lines
        Setting up tile and stipple cache:
                30 128x128 slots
(II) R128(0): Acceleration enabled
(==) R128(0): Backing store disabled
(==) R128(0): Silken mouse enabled
(II) R128(0): Using hardware cursor (scanline 7212)
(II) R128(0): Largest offscreen area available: 800 x 651
(II) R128(0): DPMS enabled

0: /usr/bin/Xorg(xorg_backtrace+0x50) [0x100ffda0]
1: /usr/bin/Xorg(xf86SigHandler+0xd8) [0x10085838]
2: [0x100364]
3: /usr/lib/xorg/modules/extensions//libdri.so(DRIFinishScreenInit+0x3c) [0xe6da27c]
4: /usr/lib/xorg/modules/drivers//r128_drv.so(R128DRIFinishScreenInit+0x60) [0xe65cab0]
5: /usr/lib/xorg/modules/drivers//r128_drv.so(R128ScreenInit+0x1064) [0xe658df4]
6: /usr/bin/Xorg(AddScreen+0x1ec) [0x1002129c]
7: /usr/bin/Xorg(InitOutput+0x83c) [0x1006a27c]
8: /usr/bin/Xorg(main+0x224) [0x10021a04]
9: /lib/libc.so.6 [0xfd6ec64]
10: /lib/libc.so.6 [0xfd6ee20]

Fatal server error:
Caught signal 11.  Server aborting

Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

I can try and provide more info, or try f10 on it soon.
Comment 22 Bug Zapper 2009-06-09 20:39:14 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 23 Bug Zapper 2009-07-14 13:29:19 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.