Not really. Fedora 12's kernel gets stuff from drm-next which means it's closer to 2.6.32 than 2.6.31.
Announcement
Collapse
No announcement yet.
Linux 2.6.32 To Get R600 KMS Along With 3D
Collapse
X
-
Originally posted by nanonyme View PostNot really. Fedora 12's kernel gets stuff from drm-next which means it's closer to 2.6.32 than 2.6.31.
I can't wait to go from F10 to F12 then
In worst case, would Fedora 12 users be able to install the Catalyst driver, which by the time Ubuntu 9.10 ships, should support 2.6.31?
Comment
-
I just updated libdrm, mesa and xf86-video-ati to latest git master and compiled the drm-next branch of airlied's kernel tree.
I'm currently using xorg-server version 1.6.3.901-r1.
Compilation of all the git packages and the kernel worked smoothly and I didn't encounter anything suspicious.
What is working so far. I have tested this on my integrated Radeon HD 3200, a RS780 chipset.
Snip from dmesg:
Code:Sep 9 22:25:14 voodoomaster [drm] Initialized drm 1.1.0 20060810 Sep 9 22:25:15 voodoomaster [drm] radeon kernel modesetting enabled. Sep 9 22:25:15 voodoomaster radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Sep 9 22:25:15 voodoomaster radeon 0000:01:05.0: setting latency timer to 64 Sep 9 22:25:15 voodoomaster [drm] radeon: Initializing kernel modesetting. Sep 9 22:25:15 voodoomaster [drm] register mmio base: 0xFE9F0000 Sep 9 22:25:15 voodoomaster [drm] register mmio size: 65536 Sep 9 22:25:15 voodoomaster ATOM BIOS: ASROCK Sep 9 22:25:15 voodoomaster [drm] Clocks initialized ! Sep 9 22:25:15 voodoomaster [TTM] Zone kernel: Available graphics memory: 1899092 kiB. Sep 9 22:25:15 voodoomaster [drm] radeon: 384M of VRAM memory ready Sep 9 22:25:15 voodoomaster [drm] radeon: 512M of GTT memory ready. Sep 9 22:25:15 voodoomaster [drm] Loading RS780 CP Microcode Sep 9 22:25:15 voodoomaster platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin Sep 9 22:25:15 voodoomaster platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin Sep 9 22:25:15 voodoomaster [drm] GART: num cpu pages 131072, num gpu pages 131072 Sep 9 22:25:15 voodoomaster [drm] ring test succeeded in 0 usecs Sep 9 22:25:15 voodoomaster [drm] radeon: ib pool ready. Sep 9 22:25:15 voodoomaster [drm] ib test succeeded in 0 usecs Sep 9 22:25:15 voodoomaster [drm] Radeon Display Connectors Sep 9 22:25:15 voodoomaster [drm] Connector 0: Sep 9 22:25:15 voodoomaster [drm] VGA Sep 9 22:25:15 voodoomaster [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c Sep 9 22:25:15 voodoomaster [drm] Encoders: Sep 9 22:25:15 voodoomaster [drm] CRT1: INTERNAL_KLDSCP_DAC1 Sep 9 22:25:15 voodoomaster [drm] Connector 1: Sep 9 22:25:15 voodoomaster [drm] DVI-D Sep 9 22:25:15 voodoomaster [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c Sep 9 22:25:15 voodoomaster [drm] Encoders: Sep 9 22:25:15 voodoomaster [drm] DFP3: INTERNAL_KLDSCP_LVTMA Sep 9 22:25:15 voodoomaster [drm] fb mappable at 0xD0141000 Sep 9 22:25:15 voodoomaster [drm] vram apper at 0xD0000000 Sep 9 22:25:15 voodoomaster [drm] size 7680000 Sep 9 22:25:15 voodoomaster [drm] fb depth is 24 Sep 9 22:25:15 voodoomaster [drm] pitch is 6400 Sep 9 22:25:15 voodoomaster executing set pll Sep 9 22:25:15 voodoomaster executing set crtc timing Sep 9 22:25:15 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:25:15 voodoomaster Console: switching to colour frame buffer device 200x75 Sep 9 22:25:15 voodoomaster fb0: radeondrmfb frame buffer device Sep 9 22:25:15 voodoomaster registered panic notifier Sep 9 22:25:15 voodoomaster [drm] radeon: kernel modesetting successfully initialized. Sep 9 22:25:15 voodoomaster [drm] Initialized radeon 2.0.0 20080528 for 0000:01:05.0 on minor 0 Sep 9 22:26:17 voodoomaster executing set pll Sep 9 22:26:17 voodoomaster executing set crtc timing Sep 9 22:26:17 voodoomaster [drm] TV-5: set mode 1280x1024 20 Sep 9 22:26:21 voodoomaster executing set pll Sep 9 22:26:21 voodoomaster executing set crtc timing Sep 9 22:26:21 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:26:38 voodoomaster executing set pll Sep 9 22:26:38 voodoomaster executing set crtc timing Sep 9 22:26:38 voodoomaster [drm] TV-5: set mode 1280x1024 21 Sep 9 22:27:05 voodoomaster executing set pll Sep 9 22:27:05 voodoomaster executing set crtc timing Sep 9 22:27:05 voodoomaster [drm] TV-5: set mode 1024x768 22 Sep 9 22:27:22 voodoomaster executing set pll Sep 9 22:27:22 voodoomaster executing set crtc timing Sep 9 22:27:22 voodoomaster [drm] TV-5: set mode 1280x1024 24 Sep 9 22:33:35 voodoomaster executing set pll Sep 9 22:33:35 voodoomaster executing set crtc timing Sep 9 22:33:35 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:33:40 voodoomaster executing set pll Sep 9 22:33:40 voodoomaster executing set crtc timing Sep 9 22:33:40 voodoomaster [drm] TV-5: set mode 640x480 26 Sep 9 22:34:13 voodoomaster executing set pll Sep 9 22:34:13 voodoomaster executing set crtc timing Sep 9 22:34:13 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:35:54 voodoomaster executing set pll Sep 9 22:35:54 voodoomaster executing set crtc timing Sep 9 22:35:54 voodoomaster [drm] TV-5: set mode 640x480 27 Sep 9 22:36:08 voodoomaster executing set pll Sep 9 22:36:08 voodoomaster executing set crtc timing Sep 9 22:36:08 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:36:09 voodoomaster executing set pll Sep 9 22:36:09 voodoomaster executing set crtc timing Sep 9 22:36:09 voodoomaster [drm] TV-5: set mode 1280x1024 28 Sep 9 22:36:14 voodoomaster executing set pll Sep 9 22:36:14 voodoomaster executing set crtc timing Sep 9 22:36:14 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:36:34 voodoomaster executing set pll Sep 9 22:36:34 voodoomaster executing set crtc timing Sep 9 22:36:34 voodoomaster [drm] TV-5: set mode 1280x1024 29 Sep 9 22:37:38 voodoomaster executing set pll Sep 9 22:37:38 voodoomaster executing set crtc timing Sep 9 22:37:38 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:37:38 voodoomaster Unpin not necessary for ffff88010078a200 ! Sep 9 22:37:39 voodoomaster executing set pll Sep 9 22:37:39 voodoomaster executing set crtc timing Sep 9 22:37:39 voodoomaster [drm] TV-5: set mode 1280x1024 2a Sep 9 22:37:45 voodoomaster executing set pll Sep 9 22:37:45 voodoomaster executing set crtc timing Sep 9 22:37:45 voodoomaster [drm] TV-5: set mode 1600x1200 1e Sep 9 22:38:24 voodoomaster Unpin not necessary for ffff88011ae62c00 ! Sep 9 22:39:38 voodoomaster pci 0000:00:14.4: transparent bridge Sep 9 22:39:38 voodoomaster pci 0000:00:14.4: bridge io port: [0xc000-0xefff] Sep 9 22:39:38 voodoomaster pci 0000:00:14.4: bridge 32bit mmio: [0xfeb00000-0xfebfffff] Sep 9 22:39:38 voodoomaster pci_bus 0000:00: on NUMA node 0
Well, KMS works to the extend, that this works:
- System boots, not loading radeon module by default
- Triggering radeon module load switches to higher resolution
- Starting X works fine
- Switching back between terminals and X also works
- Xv works
- OpenGL works to some extend
Some things that I couldn't figure out:
- The resolution the DRM module switches to is 1600x1200, however my X resolution is 1280x1024 and I also would like to have this res for the console. Oh yes, my display is a CRT, detected as VGA-0. xrandr shows all common resolutions both in KMS and UMS mode. Having different res for X and console defeats the advantages of KMS since the CRT eletronics has to switch res, which takes a while. Is it possible to switch res of the console, and if yes, how? I failed trying it with fbset...
- Playing back HD (720p) material with mplayer through Xv (textured video) works OK and also when using the OpenGL vo backend, however here the CPU usage by X is greater than with Xv. That is unexpected since it should be the other way round. Anyway, what does not work is calling the OpenGL vo backend with this parameters (gl:yuv=2:rectangle=2:force-pbo), which usually give a huge speed boost with HD material. Probably doesn't work because the driver is missing PBOs and ARB_npot.
I also tried starting quake3, but this only results in a black screen. I can hear the game starting in the background and when I blindly exit the app again, the usual desktop returns. Well, at least it doesn't crash X nor it doesn't hang the system.
Since 3D still seems to be very rudimentary I didn't try any other OpenGL apps.
Now, to the crashing part which only brings X down (I didn't manage to hang the kernel):
- Letting mplayer run for a extended period (both Xv and GL output do it)
- Opening phoronix.com in seamonkey (mozilla browser) - however this doesm't work all the time
I lost the backtrace when restarting the system (I'm writing this with above setup, with KMS switched off). Going to attach the backtrace later.
Oh yeah, I'm also getting the "no rrb" message when calling anything with GL: glxinfo e.g. and mplayer with GL vo backend really spams the console with this message
Greets,
liquidLast edited by LiquidAcid; 10 September 2009, 08:54 AM.
Comment
-
Originally posted by agd5f View PostBetter power management is next on our list once r6xx/r7xx 3D support stabilizes a bit more.
I am on one of those funny Thinkpad W500 with both Intel GMA and AMD/ATi chips. I can tell you that when I enable the AMD chip in the BIOS over the Intel chip, most temperature sensors for, or close to, the CPU and GPU report a 10-20?C increase in temperatures and I lose something around 45-60 minutes (or so, I need to test this properly) of battery life. I am really looking forward to using this chip though and will be cheering from the side lines.
I am running Archlinux atm but have room for a second distro to track graphics developments and report bugs. Is Fedora Rawhide the way to go to make this as easy as possible for everyone?
Comment
-
Originally posted by Louise View PostIn worst case, would Fedora 12 users be able to install the Catalyst driver, which by the time Ubuntu 9.10 ships, should support 2.6.31?
Comment
-
Originally posted by nanonyme View PostProbably not. Fedora is one step forward of more conservative distros like Ubuntu not only in features but also in changing (and in one point of view breaking) API's. You don't probably want to really use Fedora if you want proprietary drivers.
Comment
-
Multiple GPU support
Originally posted by bridgman View PostI imagine the driver code needs to know about multiple GPUs even if it is only using one of them.
multi-GPU - driver can support multiple GPUs with different screens on each GPU
Comment
-
Comment