Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: Mark Knecht wrote: Yes, this much was in place. I wondered later if the issue is that my current kernel has DRM selected so that I Can get the radeon driver from the kernel. Possibly for the ATI driver I need to completely deselect DRM, rebuild the kernel, and then emerge the ATI drivers? I'm pretty sure that's probably the problem. You might try compiling DRM as a module and listing the DRM module in /etc/hotplug/blacklist so it's easier to switch between fglrx and DRM. In any case, I have heard that the current R200 open-source driver is as good as the ATI driver - I'm running an R360 (9800XT) so I don't have the luxury of choice :( Manuel, Hi. I've been doing a number of experiements this morning to look into this a bit further. Basic results say that ati-drivers-8.14.13-r2 will build on 2.6.13-gentoo-r5 but will not build on any of the 2.6.14 variants I've tried so far. OK, so I've tried: 2.6.13-gentoo-r5 + ati-drivers-8.14.13-r2 - works: [EMAIL PROTECTED] ~ $ glxgears Xlib: extension XFree86-DRI missing on display :0.0. 2793 frames in 5.0 seconds = 558.600 FPS 3360 frames in 5.0 seconds = 672.000 FPS 2.6.14-gentoo 2.6.14-rt6 + ati-drivers-8.14.13-r2 - won't build 2.6.14-rt6 + ati-drivers- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/8/05, Mark Knecht [EMAIL PROTECTED] wrote: On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: Mark Knecht wrote: Yes, this much was in place. I wondered later if the issue is that my current kernel has DRM selected so that I Can get the radeon driver from the kernel. Possibly for the ATI driver I need to completely deselect DRM, rebuild the kernel, and then emerge the ATI drivers? I'm pretty sure that's probably the problem. You might try compiling DRM as a module and listing the DRM module in /etc/hotplug/blacklist so it's easier to switch between fglrx and DRM. In any case, I have heard that the current R200 open-source driver is as good as the ATI driver - I'm running an R360 (9800XT) so I don't have the luxury of choice :( Manuel, Hi. I've been doing a number of experiements this morning to look into this a bit further. Basic results say that ati-drivers-8.14.13-r2 will build on 2.6.13-gentoo-r5 but will not build on any of the 2.6.14 variants I've tried so far. OK, so I've tried: 2.6.13-gentoo-r5 + ati-drivers-8.14.13-r2 - works: [EMAIL PROTECTED] ~ $ glxgears Xlib: extension XFree86-DRI missing on display :0.0. 2793 frames in 5.0 seconds = 558.600 FPS 3360 frames in 5.0 seconds = 672.000 FPS 2.6.14-gentoo 2.6.14-rt6 + ati-drivers-8.14.13-r2 - won't build 2.6.14-rt6 + ati-drivers- PLEASE DISREAGARD this last message. I'm in the middle of things, the text isn't right and all the results are not included. I hit send instead of save. SORRY! More later. Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/8/05, Mark Knecht [EMAIL PROTECTED] wrote: On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: Mark Knecht wrote: Yes, this much was in place. I wondered later if the issue is that my current kernel has DRM selected so that I Can get the radeon driver from the kernel. Possibly for the ATI driver I need to completely deselect DRM, rebuild the kernel, and then emerge the ATI drivers? I'm pretty sure that's probably the problem. You might try compiling DRM as a module and listing the DRM module in /etc/hotplug/blacklist so it's easier to switch between fglrx and DRM. In any case, I have heard that the current R200 open-source driver is as good as the ATI driver - I'm running an R360 (9800XT) so I don't have the luxury of choice :( Manuel, Hi. OK, this is the email I meant to send this monring before I pushed the send button at the wrong time. I've been doing a number of experiements this morning to look into this a bit further. Basic results say that ati-drivers will build on gentoo-sources (both 2.6.13 and 2.6.14) but will not build on any of the -rt variants I've tried so far. There is no performance advantage to using the ATI drivers on PCI Express cards as DRI doesn't work yet. OK, so I've tried: 2.6.13-gentoo-r5 + ati-drivers-8.14.13-r2 - works: [EMAIL PROTECTED] ~ $ glxgears Xlib: extension XFree86-DRI missing on display :0.0. 2793 frames in 5.0 seconds = 558.600 FPS 3360 frames in 5.0 seconds = 672.000 FPS 2.6.14-gentoo + ati-drivers-8.14.13-r2 builds but won't modprobe. From dmesg: fglrx: Unknown symbol verify_area fglrx: Unknown symbol register_ioctl32_conversion fglrx: Unknown symbol unregister_ioctl32_conversion 2.6.14-gentoo + ati-drivers-8.18.8-r1 - works: [EMAIL PROTECTED] ~ $ glxgears Xlib: extension XFree86-DRI missing on display :0.0. 3388 frames in 5.0 seconds = 677.600 FPS 3538 frames in 5.0 seconds = 707.600 FPS So, down to here there is the ability to build the ATI drivers but no acceleration as DRI is not working for PCI Express cards yet. Note that the results above are the same when usign the radeon driver from the kernel or no driver at all. 2.6.14-rt6 + ati-drivers-8.14.13-r2 - won't build. (Might build if I rebuilt the kernel with DRI enabled...) * Found sources for kernel version: * 2.6.14-rt6 * Checking for MTRR support enabled ... [ ok ] * Checking for AGP support enabled ... [ ok ] * Checking for DRM support disabled ... [ !! ] * You have DRM support enabled, the direct rendering will not work. * X11 implementation is xorg-x11. make[1]: *** [/var/tmp/portage/ati-drivers-8.14.13-r2/work/lib/modules/fglrx/build_mod/firegl_public.o] Error 1 make: *** [_module_/var/tmp/portage/ati-drivers-8.14.13-r2/work/lib/modules/fglrx/build_mod] Error 2 make: Leaving directory `/usr/src/linux-2.6.14-rt6' * DRM module not built lightning ~ # modprobe fglrx FATAL: Module fglrx not found. lightning ~ # 2.6.14-rt6 + ati-drivers-8.18.8-r1 - won't build * /usr/src/linux * Found sources for kernel version: * 2.6.14-rt6 * Checking for MTRR support enabled ... [ ok ] * Checking for AGP support enabled ...[ ok ] * Checking for DRM support disabled ... [ ok ] * X11 implementation is xorg-x11. /var/tmp/portage/ati-drivers-8.18.8-r1/work/common/lib/modules/fglrx/build_mod/firegl_public.c:665: error: `SPIN_LOCK_UNLOCKED' undeclared (first use in this function) /var/tmp/portage/ati-drivers-8.18.8-r1/work/common/lib/modules/fglrx/build_mod/firegl_public.c:665: error: (Each undeclared identifier is reported only once /var/tmp/portage/ati-drivers-8.18.8-r1/work/common/lib/modules/fglrx/build_mod/firegl_public.c:665: error: for each function it appears in.) make[1]: *** [/var/tmp/portage/ati-drivers-8.18.8-r1/work/common/lib/modules/fglrx/build_mod/firegl_public.o] Error 1 make: *** [_module_/var/tmp/portage/ati-drivers-8.18.8-r1/work/common/lib/modules/fglrx/build_mod] Error 2 make: Leaving directory `/usr/src/linux-2.6.14-rt6' * DRM module not built lightning ~ # modprobe fglrx FATAL: Module fglrx not found. lightning ~ # So with the realtime kernels I cannot even built the ATI drivers at this time. I don't really know what to make of that. Maybe time will tell. Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
Mark Knecht wrote: So with the realtime kernels I cannot even built the ATI drivers at this time. I don't really know what to make of that. Maybe time will tell. I think you need the 8.18.8-r1 for 2.6.14-gentoo kernels, at least that's what the ChangeLog for ati-drivers says (apparently there was a change to the ebuild *after* it was released originally, so the 8.18.8-r1 that's there now is different from the one that was originally released.) -- Manuel A. McLure KE6TAW [EMAIL PROTECTED] http://www.mclure.org ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft -- gentoo-user@gentoo.org mailing list
[gentoo-user] two ati-drivers packages using --deep --update
Hi, Is the following expected with recent ati-drivers? Is this slotted? If so, and if I did the --deep --update command, then how do I know which one I'm using when I load fglrx? Thanks, Mark lightning ~ # emerge -pv ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] media-video/ati-drivers-8.18.8-r1 [8.14.13-r2] +opengl 52,237 kB [ebuild N] media-video/ati-drivers-extra-8.14.13 +qt 0 kB Total size of downloads: 52,237 kB lightning ~ # emerge -pv --deep --update ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] media-video/ati-drivers-8.18.8-r1 [8.14.13-r2] +opengl 52,237 kB [ebuild U ] media-video/ati-drivers-8.14.13-r5 [8.14.13-r2] -dlloader +opengl 0 kB [ebuild N] media-video/ati-drivers-extra-8.14.13 +qt 0 kB Total size of downloads: 52,237 kB lightning ~ # -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
Mark Knecht schreef: Hi, Is the following expected with recent ati-drivers? Is this slotted? No, and no. If so, and if I did the --deep --update command, then how do I know which one I'm using when I load fglrx? fglrxinfo would tell you the version of the ati-drivers in use. But... there can be only one (the package is not slotted). Thanks, Mark lightning ~ # emerge -pv ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] media-video/ati-drivers-8.18.8-r1 [8.14.13-r2] +opengl 52,237 kB [ebuild N] media-video/ati-drivers-extra-8.14.13 +qt 0 kB Total size of downloads: 52,237 kB lightning ~ # emerge -pv --deep --update ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] media-video/ati-drivers-8.18.8-r1 [8.14.13-r2] +opengl 52,237 kB [ebuild U ] media-video/ati-drivers-8.14.13-r5 [8.14.13-r2] -dlloader +opengl 0 kB [ebuild N] media-video/ati-drivers-extra-8.14.13 +qt 0 kB Problem here-- afaik-- is that the drivers-extra package is hooked to the drivers package of the same version. The --deep update of the drivers-extra package requires the 'same' version of the drivers package as it itself is numbered. What I don't understand is why you are not getting drivers-extra-8.18.8, but only 8.14.13. And I definitely don't know how the double upgrade would work, except that it would likely be an upgrade/downgrade (but not shown as such because the upgrade has not yet been performed). emerge -p ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.18.8-r1 [ebuild R ] media-video/ati-drivers-extra-8.18.8 Do you maybe have a mask on ati-drivers-extra? Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/7/05, Holly Bostick [EMAIL PROTECTED] wrote: Mark Knecht schreef: Problem here-- afaik-- is that the drivers-extra package is hooked to the drivers package of the same version. The --deep update of the drivers-extra package requires the 'same' version of the drivers package as it itself is numbered. What I don't understand is why you are not getting drivers-extra-8.18.8, but only 8.14.13. Nor I, also eix is only showing these: lightning ~ # eix ati-drivers-extra * media-video/ati-drivers-extra Available versions: 8.14.13 *8.16.20 Installed: none Homepage:http://www.ati.com Description: Ati precompiled drivers extra application Found 1 matches lightning ~ # I had been assuming 8.16.20 goes with ati-drivers-8.18.8, but maybe not... And I definitely don't know how the double upgrade would work, except that it would likely be an upgrade/downgrade (but not shown as such because the upgrade has not yet been performed). emerge -p ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.18.8-r1 [ebuild R ] media-video/ati-drivers-extra-8.18.8 Do you maybe have a mask on ati-drivers-extra? Holly No masking here. The only package I've masked is Wine as per your suggestion the other day. These are entries in /etc/portage/package.keywords. Nothing in portage.use. media-video/ati-drivers ~amd64 media-video/ati-drivers-extra ~amd64 From someone on the LKML I found out that the ATI binary drivers won't work on a 64-bit kernel so this is suddently not such an issue for me. Thanks Holly! Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
emerge -p ati-drivers ati-drivers-extra These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.18.8-r1 [ebuild R ] media-video/ati-drivers-extra-8.18.8 Do you maybe have a mask on ati-drivers-extra? Holly maybe -amd64 is reason: - media-video/ati-drivers-extra-8.18.8 (masked by: -amd64 keyword) martins -- Linux 2.6.13 AMD Athlon(tm) 64 Processor 3200+ 22:08:09 up 11:49, 5 users, load average: 0.10, 0.11, 0.40 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
Mark Knecht wrote: From someone on the LKML I found out that the ATI binary drivers won't work on a 64-bit kernel so this is suddently not such an issue for me. The 32-bit drivers won't work on a 64-bit kernel, but ATI does provide 64-bit binary drivers as well (and the ebuild should download the correct one depending on whether you're on a 64-bit or 32-bit Gentoo install.) -- Manuel A. McLure KE6TAW [EMAIL PROTECTED] http://www.mclure.org ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: Mark Knecht wrote: From someone on the LKML I found out that the ATI binary drivers won't work on a 64-bit kernel so this is suddently not such an issue for me. The 32-bit drivers won't work on a 64-bit kernel, but ATI does provide 64-bit binary drivers as well (and the ebuild should download the correct one depending on whether you're on a 64-bit or 32-bit Gentoo install.) -- Manuel, Hi. Are you able to make this work? I'm not. (so far...) 1) I emerged ati-drivers-8.18.8-r1. Is that new enough? lightning ~ # emerge -pv ati-drivers These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.18.8-r1 +opengl 0 kB Total size of downloads: 0 kB lightning ~ # 2) I ran the app referenced in the emerge output to set up xrog.config: aticonfig --initial --input=/etc/X11/xorg.conf 3) I looked at xorg.conf. It looks OK, if a bit confusing. Now it appears that the developers are attempting to make a single xorg.conf that works with either the radeon driver or the fglrx driver? That would be nice. 4) I switched to fglrx in /etc/modules.audtoload.d/kernel.2.6 and rebooted. 5) fglrx did not load: lightning ~ # lsmod | grep fglrx lightning ~ # 6) Xorg.0.log results: NOTE: There is no DRI for PCI Express cards yet. 2.6.15 I'm told. lightning ~ # cat /var/log/Xorg.0.log | grep EE Current Operating System: Linux lightning 2.6.14-rt6 #2 PREEMPT Fri Nov 4 15:49:09 PST 2005 x86_64 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER (EE) fglrx(0): === [R200DALSetControllerConfigForRemap] === CWDDC ControllerSetConfig failed: 6 - 1 lightning ~ # cat /var/log/Xorg.0.log | grep WW (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found (WW) fglrx(0): board is an unknown third party board, chipset is supported (WW) fglrx(0): *** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available* (WW) fglrx(0): * * (WW) fglrx(0): Failed to set up write-combining range (0xd700,0xff) (WW) fglrx(0): Failed to set up write-combining range (0xd600,0x1ff) (WW) fglrx(0): Failed to set up write-combining range (0xd400,0x3ff) (WW) fglrx(0): Failed to set up write-combining range (0xd000,0x7ff) (WW) Open APM failed (/dev/apm_bios) (No such file or directory) lightning ~ # 7) mtrr problems: dmesg SNIP mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available eth0: no IPv6 routers present lightning ~ # lightning ~ # cat /proc/mtrr reg00: base=0x ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd7fe (3455MB), size= 64KB: write-combining, count=1 reg02: base=0xd7fc (3455MB), size= 128KB: write-combining, count=1 reg03: base=0xd7f8 (3455MB), size= 256KB: write-combining, count=1 reg04: base=0xd7f0 (3455MB), size= 512KB: write-combining, count=1 reg05: base=0xd7e0 (3454MB), size= 1MB: write-combining, count=1 reg06: base=0xd7c0 (3452MB), size= 2MB: write-combining, count=1 reg07: base=0xd780 (3448MB), size= 4MB: write-combining, count=1 lightning ~ # -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
Mark Knecht wrote: On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: The 32-bit drivers won't work on a 64-bit kernel, but ATI does provide 64-bit binary drivers as well (and the ebuild should download the correct one depending on whether you're on a 64-bit or 32-bit Gentoo install.) -- Manuel, Hi. Are you able to make this work? I'm not. (so far...) 1) I emerged ati-drivers-8.18.8-r1. Is that new enough? I had this working with the 8.14.13 drivers and kernel 2.6.12-mumblemumbe. My Gentoo64 installation has gone byebye, so I haven't tested with newer versions. lightning ~ # emerge -pv ati-drivers Make sure that /usr/src/linux points to /usr/src/linux-version, where version is the exact version that uname -a reports. Also, when you upgrade kernels, you *must* remerge ati-drivers, since they need to build against the current kernel sources. These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.18.8-r1 +opengl 0 kB Total size of downloads: 0 kB lightning ~ # 2) I ran the app referenced in the emerge output to set up xrog.config: aticonfig --initial --input=/etc/X11/xorg.conf 3) I looked at xorg.conf. It looks OK, if a bit confusing. Now it appears that the developers are attempting to make a single xorg.conf that works with either the radeon driver or the fglrx driver? That would be nice. 4) I switched to fglrx in /etc/modules.audtoload.d/kernel.2.6 and rebooted. This shouldn't be needed - the fglrx X module should autoload the fglrx module for you. 5) fglrx did not load: lightning ~ # lsmod | grep fglrx lightning ~ # Any messages in /var/log/messages or dmesg output? 6) Xorg.0.log results: [SNIP] (WW) fglrx(0): Failed to set up write-combining range (0xd700,0xff) (WW) fglrx(0): Failed to set up write-combining range (0xd600,0x1ff) (WW) fglrx(0): Failed to set up write-combining range (0xd400,0x3ff) (WW) fglrx(0): Failed to set up write-combining range (0xd000,0x7ff) (WW) Open APM failed (/dev/apm_bios) (No such file or directory) lightning ~ # 7) mtrr problems: dmesg SNIP mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available eth0: no IPv6 routers present lightning ~ # lightning ~ # cat /proc/mtrr reg00: base=0x ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd7fe (3455MB), size= 64KB: write-combining, count=1 reg02: base=0xd7fc (3455MB), size= 128KB: write-combining, count=1 reg03: base=0xd7f8 (3455MB), size= 256KB: write-combining, count=1 reg04: base=0xd7f0 (3455MB), size= 512KB: write-combining, count=1 reg05: base=0xd7e0 (3454MB), size= 1MB: write-combining, count=1 reg06: base=0xd7c0 (3452MB), size= 2MB: write-combining, count=1 reg07: base=0xd780 (3448MB), size= 4MB: write-combining, count=1 lightning ~ # From what I see here, it looks like the MTRR stuff is the problem. Possibly some of the patchsets in the -rt kernels (as opposed to the -gentoo kernels) are causing problems. I'd try manually doing a modprobe fglrx and see if there are any useful messages. Also, you might try to use fglrxconfig instead of aticonfig to create the configuration. -- Manuel A. McLure KE6TAW [EMAIL PROTECTED] http://www.mclure.org ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: Mark Knecht wrote: On 11/7/05, Manuel McLure [EMAIL PROTECTED] wrote: The 32-bit drivers won't work on a 64-bit kernel, but ATI does provide 64-bit binary drivers as well (and the ebuild should download the correct one depending on whether you're on a 64-bit or 32-bit Gentoo install.) -- Manuel, Hi. Are you able to make this work? I'm not. (so far...) 1) I emerged ati-drivers-8.18.8-r1. Is that new enough? I had this working with the 8.14.13 drivers and kernel 2.6.12-mumblemumbe. My Gentoo64 installation has gone byebye, so I haven't tested with newer versions. Oh, sure. I have it working, to some extent anyway, with a 2.6.13 variant also. What I haven't accomplished was getting it going with 2.6.14. lightning ~ # emerge -pv ati-drivers Make sure that /usr/src/linux points to /usr/src/linux-version, where version is the exact version that uname -a reports. Also, when you upgrade kernels, you *must* remerge ati-drivers, since they need to build against the current kernel sources. Yes, this much was in place. I wondered later if the issue is that my current kernel has DRM selected so that I Can get the radeon driver from the kernel. Possibly for the ATI driver I need to completely deselect DRM, rebuild the kernel, and then emerge the ATI drivers? SNIP Any messages in /var/log/messages or dmesg output? Nothing major, but there were messages. I switched back to the radeon driver from the kernel and don't have that right now. If I don't find another answer I'll post it back later. 6) Xorg.0.log results: [SNIP] (WW) fglrx(0): Failed to set up write-combining range (0xd700,0xff) (WW) fglrx(0): Failed to set up write-combining range (0xd600,0x1ff) (WW) fglrx(0): Failed to set up write-combining range (0xd400,0x3ff) (WW) fglrx(0): Failed to set up write-combining range (0xd000,0x7ff) (WW) Open APM failed (/dev/apm_bios) (No such file or directory) lightning ~ # 7) mtrr problems: dmesg SNIP mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available eth0: no IPv6 routers present lightning ~ # lightning ~ # cat /proc/mtrr reg00: base=0x ( 0MB), size= 512MB: write-back, count=1 reg01: base=0xd7fe (3455MB), size= 64KB: write-combining, count=1 reg02: base=0xd7fc (3455MB), size= 128KB: write-combining, count=1 reg03: base=0xd7f8 (3455MB), size= 256KB: write-combining, count=1 reg04: base=0xd7f0 (3455MB), size= 512KB: write-combining, count=1 reg05: base=0xd7e0 (3454MB), size= 1MB: write-combining, count=1 reg06: base=0xd7c0 (3452MB), size= 2MB: write-combining, count=1 reg07: base=0xd780 (3448MB), size= 4MB: write-combining, count=1 lightning ~ # From what I see here, it looks like the MTRR stuff is the problem. Possibly some of the patchsets in the -rt kernels (as opposed to the -gentoo kernels) are causing problems. I'd try manually doing a modprobe fglrx and see if there are any useful messages. Also, you might try to use fglrxconfig instead of aticonfig to create the configuration. As I remember it the mtrr messages were the only thing that showed up in dmesg. They actually didn't show up until I modprobed fglrx. - Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] two ati-drivers packages using --deep --update
Mark Knecht wrote: Yes, this much was in place. I wondered later if the issue is that my current kernel has DRM selected so that I Can get the radeon driver from the kernel. Possibly for the ATI driver I need to completely deselect DRM, rebuild the kernel, and then emerge the ATI drivers? I'm pretty sure that's probably the problem. You might try compiling DRM as a module and listing the DRM module in /etc/hotplug/blacklist so it's easier to switch between fglrx and DRM. In any case, I have heard that the current R200 open-source driver is as good as the ATI driver - I'm running an R360 (9800XT) so I don't have the luxury of choice :( -- Manuel A. McLure KE6TAW [EMAIL PROTECTED] http://www.mclure.org ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft -- gentoo-user@gentoo.org mailing list
