| Summary: | mobility radeon 7500 does not works with DRI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Xavier <xotazu> | ||||
| Component: | DRM/other | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | high | ||||||
| Version: | DRI git | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Xavier
2005-10-12 07:15:29 UTC
It sounds like the Radeon DRM isn't being loaded properly. What does 'lsmod' show? Is there anything interesting in /var/log/messages related to drm or radeon? I attach the /var/log/Xorg.0.log file I have similar problems with a radeon 9200 card (I create a new bug entry) lsmod tells: usb-storage 66848 1 radeon 110144 1 snd-pcm-oss 38016 0 (unused) snd-mixer-oss 13208 0 [snd-pcm-oss] ip_conntrack_irc 2960 0 (unused) ip_conntrack_ftp 3888 0 (unused) ipt_state 536 2 ipt_limit 888 0 (unused) ipt_LOG 3384 0 (unused) ip_conntrack 18628 2 [ip_conntrack_irc ip_conntrack_ftp ipt_state] iptable_filter 1708 1 (autoclean) ip_tables 12288 4 [ipt_state ipt_limit ipt_LOG iptable_filter] uhci 25404 0 (unused) usbcore 61452 1 [usb-storage uhci] snd-intel8x0 18848 2 snd-ac97-codec 64828 0 [snd-intel8x0] snd-pcm 58216 0 [snd-pcm-oss snd-intel8x0 snd-ac97-codec] snd-timer 14608 0 [snd-pcm] snd 34212 2 [snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-ac97-codec snd-pcm snd-timer] soundcore 3652 4 [snd] snd-page-alloc 4904 0 [snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd] slamrmo 155492 0 (unused) slmdm 1083936 0 [slamrmo] 3c59x 26864 0 (unused) orinoco_cs 4564 1 orinoco 34068 0 [orinoco_cs] hermes 6148 0 [orinoco_cs orinoco] ds 7092 2 [orinoco_cs] yenta_socket 10916 2 pcmcia_core 46148 0 [orinoco_cs ds yenta_socket] speedstep-lib 1456 0 (unused) p4-clockmod 1580 0 (unused) ide-scsi 10224 0 agpgart 29616 3 ntfs 54848 1 (autoclean) the 'lsmod' output I've posted before is for 6.8.2 version (when it works). That is the lsmod output when using 6.8.99.900 version uhci 25968 0 (unused) usbcore 62624 1 [uhci] 3c59x 27984 1 ds 6952 4 yenta_socket 10816 2 pcmcia_core 43104 0 [ds yenta_socket] ide-scsi 10320 0 agpgart 41976 0 (unused) ntfs 54336 1 (autoclean) Created attachment 3608 [details]
/var/log/Xorg.0.log file for 6.8.99.900 xorg version
there are no comments on the /var/log/messages file when radeon driver fails. There are only messages when in loads correctly. Where is the drm module? $ lsmod Module Size Used by radeon 108384 1 drm 68376 2 radeon grrr, can't mark fixed ... try reassigning to me grrr, can't mark fixed ... try reassigning to me Sorry for the mess, I did some bad manipulation with bugzilla. Since this problem is similar to bug 4850, I tried to locate de drm kernel module also in the machine with the radeon 7500. In this machine I also use the 2.4.31. This kernel does not have any drm module and it is not possible to compile a drm module. I instaled the 2.6.11 kernel, and in this kernel exists a drm module. Using this kernel, I can load dri module and the problem completely dissapears. Therefore, I guess that there is some compatibility problem of Xorg dri and/or radeon modules with 2.4.x kernels. Using 2.6.11 kernel there is another minor problem: If I activate both the compositor extension and the dri module, graphic environtment becomes extremely slow. If I activate either dri or compositor extension, if works fine. Hence, when simultaneously using compositor extension and dri module, it becomes very slow. The version of the DRM in production 2.4 kernels is not supported by recent DRI drivers. I don't believe there is any intention to support it again at this point. I'm not sure whether or not it's possible to build DRM CVS on 2.4.x. I'd like to get input from one of the other DRI developers (ajax? airlied?), but I suspect this is going to be closed either WONTFIX or NOTABUG. (In reply to comment #12) > The version of the DRM in production 2.4 kernels is not supported by recent DRI > drivers. I don't believe there is any intention to support it again at this > point. I'm not sure whether or not it's possible to build DRM CVS on 2.4.x. > In theory it shouldn't have broken but I think something else caused some collateral damage and took 2.4 drm out, a bit annoying, but unless someone really decided that this needs to be fixed I'm a bit over 2.4 kernels... It looks like the Bus ID changes made are probably what broke it, but in theory the fallback code should've worked unless we removed it.. So it'll be WONTFIX unless someone else decides to give it a go or I suddenly feel all 2.4 again... WONTFIX 2.4 DRM is dead to me. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.