| View previous topic :: View next topic |
| Author |
Message |
dobbs
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 105
Location: Wenatchee, WA
|
 Posted: Wed Aug 10, 2011 12:56 am Post subject: [SOLVED] PowerBook+radeon: DRI available, but not working? |
 |
|
I need help getting the DRI/DRM/OpenGL (hardware) running on my powerbook. I've tried everything I can think of or find online. No matter what, the following lines continue to plague my Xorg log: (full /var/log/Xorg.0.log)
| Code: | [ 69226.408] (WW) RADEON(0): Failed to read PCI ROM!
[ 69226.409] (WW) RADEON(0): Unrecognized BIOS signature, BIOS data will not be used
[ 69226.409] drmOpenDevice: node name is /dev/dri/card0
[ 69226.423] drmOpenByBusid: Searching for BusID pci:0000:00:10.0
[ 69226.423] drmOpenDevice: node name is /dev/dri/card0
[ 69226.427] drmOpenByBusid: drmOpenMinor returns -1
[ 69226.427] drmOpenDevice: node name is /dev/dri/card1
[ 69226.431] drmOpenByBusid: drmOpenMinor returns -1
[ 69226.431] drmOpenDevice: node name is /dev/dri/card2
[ 69226.435] drmOpenByBusid: drmOpenMinor returns -1
[ 69226.435] drmOpenDevice: node name is /dev/dri/card3
...
[ 69226.548] drmOpenDevice: node name is /dev/dri/card12
[ 69226.552] drmOpenDevice: node name is /dev/dri/card13
[ 69226.556] drmOpenDevice: node name is /dev/dri/card14
[ 69226.560] drmOpenDevice: node name is /dev/dri/card15
[ 69226.564] (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.
[ 69228.625] (II) AIGLX: Screen 0 is not DRI2 capable
[ 69228.625] (II) AIGLX: Screen 0 is not DRI capable |
I don't have a /dev/dri directory (does the DRI modules create one?). I find it strange that the first iteration opening the dri devices fails, but the second doesn't seem to give any error. Still, I end up with software rendering: (full glxinfo)
| Code: | dobbs@vertigo /usr/src/linux $ glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fragment_program, |
Xorg starts fine without an xorg.conf, albeit with software rendering. x11-base/xorg-drivers is built with VIDEO_CARDS="radeon fbdev v4l". I think it was the Gentoo DRI howtoo that said mobility chipsets might need a custom xorg.conf. I tried using xac to configure an xorg.conf, but it didn't help. Currently, I have no /etc/X11/xorg.conf and the following /etc/X11/xorg.conf.d/10-radeon.conf, but this has been modified A LOT:
| Code: | # /etc/X11/xorg.conf.d/10-radeon.conf
Section "Device"
Identifier "Card0"
Driver "radeon"
### Configured ATI Radeon 4e50 at PCI Bus ID:
# BusID "PCI:0:16:0"
### Set driver options:
Option "EnablePageFlip" "true" # Increases Performance
#Option "MergedFB" "false" # Set to true if you want mirrored monitor output
### Unchanged, default driver options:
Option "AccelMethod" "EXA" # XAA or EXA, but EXA is unstable"
Option "AGPMode" "4" # Set to the AGP bus speed, 1 = 1x
#Option "AGPFastWrite" "true" # Can be unstable
# Option "BackingStore" "false" # Currently broken
# Option "BIOSHotkeys" "false" # Enable this to switch outputs with a hotkey
#Option "BusType" "AGP" # Force Video Bus to PCI, AGP or PCIE
# Option "MonitorLayout" "auto" # Set to TMDS for some Apple Flat Panels
# Option "NoAccel" "false" # Disables ALL hardware acceleration
Option "RenderAccel" "true" # Hardware Render Acceleration"
# Option "ReverseDDC" "false" # Some G5s require this
# Option "SWcursor" "false"
# Option "UseFBDev" "false" # Try enabling this if it does not work
### See "man radeon" for more information and options
Option "ColorTiling" "true"
#Option "EXAPixmaps" "true" # "Not Used" from X log
#Option "SwapbuffersWait" "false"
#Option "ClockGating" "true" # enable for better power, possibly less performance
#Option "ForceLowPowerMode" "true" # low power mode == low performance mode
Option "DynamicPM" "true" # reduce power when idle
Option "DRI" "true"
#Option "MacModel" "powerbook-internal" # default is "powerbook-external"
EndSection
Section "DRI"
#Group 0 # video = 27; does it want root? (from xac)
Mode 0666
EndSection |
My card is a Mobility Radeon 9600 M10 (RV350):
| Code: | dobbs@vertigo /usr/src/linux $ sudo lspci -vvks 00:10.0
0000:00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] (prog-if 00 [VGA controller])
Subsystem: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 255 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 48
Region 0: Memory at b8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at 0400 [size=256]
Region 2: Memory at b0000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at b0020000 [size=128K]
Capabilities: [58] AGP version 2.0
Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: radeonfb |
I've tried building the DRM and radeon drivers as modules and as built-ins, because the docs tend to contradict each other on that point. My current kernel config: (see full config)
| Code: | Device Drivers --->
Graphics support --->
<*> /dev/agpgart (AGP Support) --->
<*> Apple UniNorth & U3 AGP support
-*- VGA Arbitration
(16) Maximum number of GPUs
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
<*> ATI Radeon
[*] Enable modesetting on radeon by default - NEW DRIVER
< > Intel GMA500 Stub Driver
<M> Lowlevel video output switch controls
-*- Support for frame buffer devices --->
[*] Enable firmware EDID
[ ] Framebuffer foreign endianness support --->
-*- Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
*** Frame buffer hardware drivers ***
<*> ATI Radeon display support
[*] DDC/I2C for ATI Radeon support
[*] Support for backlight control
[ ] Lots of debug output from Radeon driver
-*- Backlight & LCD device support --->
<M> Lowlevel LCD controls
<M> Platform LCD controls
-*- Lowlevel Backlight controls
<M> Generic (aka Sharp Corgi) Backlight Driver
< > Backlight Driver for ADP8860/ADP8861/ADP8863 using WLED
Display device support --->
<M> Display panel/monitor support
*** Display hardware drivers ***
Console display driver support --->
[ ] VGA text console
-*- Framebuffer Console support
-*- Map the console to the primary display device
[ ] Framebuffer Console Rotation
[ ] Select compiled-in fonts
[*] Bootup logo --->
[*] Standard 224-color Linux logo |
And full dmesg and emerge --info are available just in case. Uh, ignore the tap0 forwarding messages; I'm bridging an SSH tunnel. Curious lines are e.g.:
| Code: | Linux agpgart interface v0.103
agpgart-uninorth 0000:00:0b.0: Apple UniNorth/Intrepid2 chipset
agpgart-uninorth 0000:00:0b.0: configuring for size idx: 64
agpgart-uninorth 0000:00:0b.0: AGP aperture is 256M @ 0x0
radeonfb 0000:00:10.0: enabling device (0006 -> 0007)
radeonfb 0000:00:10.0: Invalid ROM contents
radeonfb (0000:00:10.0): Invalid ROM signature 8383 should be 0xaa55
radeonfb: Retrieved PLL infos from Open Firmware
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=240.00 Mhz, System=446.00 MHz
radeonfb: PLL min 12000 max 35000
i2c i2c-2: unable to read EDID block.
i2c i2c-2: unable to read EDID block.
i2c i2c-2: unable to read EDID block.
radeonfb: Monitor 1 type LCD found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
radeonfb: Using Firmware dividers 0x00040089 from PPLL 0
radeonfb: Dynamic Clock Power Management enabled
Console: switching to colour frame buffer device 180x60
radeonfb (0000:00:10.0): ATI Radeon 4e50 "NP" |
Please help; I don't know what else to try.
Last edited by dobbs on Fri Aug 12, 2011 2:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
chithanh
Developer
Joined: 05 Aug 2006
Posts: 2158
Location: Berlin, Germany
|
| Posted: Thu Aug 11, 2011 8:43 pm Post subject: |
|
|
radeonfb doesn't work with modern DRI. For 3D acceleration, disable radeonfb in the kernel and configure kernel modesetting as in http://www.gentoo.org/doc/en/xorg-config.xml
Unfortunately, there is a problem with radeon KMS and suspend on PPC, so you will have to live without 3D acceleration or without proper working suspend. |
|
| Back to top |
|
|
dobbs
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 105
Location: Wenatchee, WA
|
| Posted: Fri Aug 12, 2011 2:03 pm Post subject: [SOLVED] PowerBook+radeon: DRI available, but not working? |
|
|
Thank you, chithanh, that did the trick! I rebuilt radeonfb as a module and blacklisted it. Now I get:
| Code: | dobbs@vertigo ~ $ glxinfo | grep -i render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 (RV350 4E50) 20090101 PowerPC/Altivec TCL DRI2 |
Suspend never really worked for me anyway; I'll play with 3D for a while. :) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on PPC
