Announcement
Collapse
No announcement yet.
R600/r700 kms + 3d dri1/dri2
Collapse
X
-
Without radeon.modeset=1 on boot-line everything works great but with user-modesetting. If I put radeon.modeset=1 on boot line I cannot get anymore to boot because I get great corruption on login screen. It happened suddenly, I did not change anything, and as You can see from my previous post it work the first time I tried, there was corruption but somehow I got trough it and got the dmesg excerpt I wrote above. But the progress is great. There might be a slight difference between 2.6.32-rc and 2.6.32.999 (I'm using now and I have removed 2.6.32-rc1 so I can not try that again) that makes that problem more visible. Days ahead will clear that I'm sure.
-
I installed the new kernel with the latest xorge-edgers, and everything works like a charm, with one visible problem only though: I have minor corruption when entering text in gnome-terminal or gvim.
I also tried WoW on wine, and it works, but the frame rate is crazy slow, I couldn't get past the login screen. However I could see no corruption or anything, which by itself is big.
Other than that everything works perfectly, compiz, 720p on totem etc.
Leave a comment:
-
Originally posted by tormod View PostNow that there is a 2.6.32-rc1 kernel package in the Mainline PPA, use that instead of drm-modules-source.
1. without radeon.modeset=1 in boot line
Code:~$ dmesg |grep radeon [ 23.223050] [drm] radeon defaulting to userspace modesetting. [ 23.223830] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0 [ 23.539384] platform r600_cp.0: firmware: requesting radeon/RV635_pfp.bin [ 23.673745] platform r600_cp.0: firmware: requesting radeon/RV635_me.bin
Code:~$ dmesg|grep radeon [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-999-generic root=UUID=...(erased) ro radeon.modeset=1 [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-999-generic root=UUID=...(erased) ro radeon.modeset=1 [ 0.000000] Unknown boot option `radeon.modeset=1': ignoring [ 23.658291] [drm] radeon kernel modesetting enabled. [ 23.658471] radeon 0000:01:00.0: setting latency timer to 64 [ 23.661268] [drm] radeon: Initializing kernel modesetting. [ 23.663186] [drm] radeon: 256M of VRAM memory ready [ 23.663188] [drm] radeon: 512M of GTT memory ready. [ 23.663335] platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin [ 23.756642] platform radeon_cp.0: firmware: requesting radeon/RV635_me.bin [ 23.805087] [drm] radeon: ib pool ready. [ 23.805149] [drm] radeon: kernel modesetting successfully initialized. [ 23.988365] fb0: radeondrmfb frame buffer device [ 23.988373] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
Last edited by zika; 02 October 2009, 03:59 PM.
Leave a comment:
-
kernel for Ubuntu
Now that there is a 2.6.32-rc1 kernel package in the Mainline PPA, use that instead of drm-modules-source.
Leave a comment:
-
Originally posted by tormod View PostNo, do not rename or delete the files manually. You should uninstall the built module package using apt-get purge, so that everything is restored to how it was before. This is one advantage of using deb packages because they keep track of which files have been installed and which have been diverted.
Never mind, I've removed all that with "Complete removal" inside Synaptic. Now I'm on 2.6.32-rc1 and I hope that is just history. Any hints or tweaks with that kernel? It looks promising ...
Leave a comment:
-
Originally posted by zika View PostP.S. I did that and nothing changed. I will erase that file just for the sake of some new upgrade ...
Leave a comment:
-
Originally posted by tvelocity View PostYes, I noticed that too but forgot to mention it. Indeed there was an old radeon.ko renamed to radeon.ko.linux in the radeon directory. I tried copying the new radeon.ko in radeon/ and updating the initramfs, but after a reboot nothing had changed. However I did this "experiment" before yesterday's update to drm-modules-source, so maybe something is changed now (the directory listing is from the new drm-modules-source though, I just didn't try to repeat the same trick)
I'm back on fglrx now, but I could try it again today, or if you need any specific log files etc.
Leave a comment:
-
With new 2.6.32-rc1 3D acceleration and modesetting work. I get:Code:~$ dmesg |grep radeon [ 23.806662] [drm] radeon defaulting to userspace modesetting. [ 23.807872] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:00.0 on minor 0 [ 24.157436] platform r600_cp.0: firmware: requesting radeon/RV635_pfp.bin [ 24.298390] platform r600_cp.0: firmware: requesting radeon/RV635_me.bin
Leave a comment:
-
I've forced it now to reinstall everything and I get:Code:~$ modinfo radeon filename: /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/radeon.ko license: GPL and additional rights description: ATI Radeon author: Gareth Hughes, Keith Whitwell, others. srcversion: 231A65D0AB952D19417FCF9 depends: drm vermagic: 2.6.31-11-generic SMP mod_unload modversions parm: no_wb:Disable AGP writeback for scratch registers (int) ~$ modinfo drm filename: /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/drm.ko license: GPL and additional rights description: DRM shared core routines author: Gareth Hughes, Leif Delgass, Jos? Fonseca, Jon Smirl srcversion: 427746F29520C420EBE2FDE depends: vermagic: 2.6.31-11-generic SMP mod_unload modversions parm: debug:Enable debug output (int) zika@zika-desktop:~$ dmesg|grep radeon [ 24.613654] radeon 0000:01:00.0: setting latency timer to 64 [ 24.613797] [drm] Initialized radeon 1.29.0 20080613 on minor 0 ~$ ls /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/radeon -alt total 892 drwxr-xr-x 13 root root 4096 2009-09-30 14:50 .. drwxr-xr-x 2 root root 4096 2009-09-30 14:49 . -rw-r--r-- 1 root root 904712 2009-09-25 10:24 radeon.ko.linux ~$ locate radeon.ko /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/radeon.ko /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/radeon/radeon.ko.linux /lib/modules/2.6.31-999-generic/kernel/drivers/gpu/drm/radeon/radeon.ko ~$ ls -alt /lib/modules/2.6.31-11-generic/kernel/drivers/gpu/drm/ total 1124 drwxr-xr-x 13 root root 4096 2009-09-30 14:50 . -rw-r--r-- 1 root root 304274 2009-09-30 14:50 drm.ko -rw-r--r-- 1 root root 486474 2009-09-30 14:50 radeon.ko drwxr-xr-x 2 root root 4096 2009-09-30 14:49 via drwxr-xr-x 2 root root 4096 2009-09-30 14:49 tdfx drwxr-xr-x 2 root root 4096 2009-09-30 14:49 sis drwxr-xr-x 2 root root 4096 2009-09-30 14:49 savage drwxr-xr-x 2 root root 4096 2009-09-30 14:49 radeon drwxr-xr-x 2 root root 4096 2009-09-30 14:49 r128 drwxr-xr-x 2 root root 4096 2009-09-30 14:49 mga drwxr-xr-x 2 root root 4096 2009-09-30 14:49 i915 drwxr-xr-x 2 root root 4096 2009-09-30 14:49 i810 drwxr-xr-x 2 root root 4096 2009-09-27 15:45 ttm drwxr-xr-x 2 root root 4096 2009-09-27 15:45 i830 drwxr-xr-x 3 root root 4096 2009-09-26 03:30 .. -rw-r--r-- 1 root root 299392 2009-09-25 10:24 drm.ko.linux
P.S. I did that and nothing changed. I will erase that file just for the sake of some new upgrade ...Last edited by zika; 30 September 2009, 09:05 AM.
Leave a comment:
-
Originally posted by tormod View PostThanks, there was some useful information in your file listing. It seems the new radeon.ko module has been installed to gpu/drm/ and not to gpu/drm/radeon/. Is there an old radeon.ko inside gpu/drm/radeon/ ? It should have been renamed radeon.ko.linux.
I'm back on fglrx now, but I could try it again today, or if you need any specific log files etc.
Leave a comment:
Leave a comment: