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 (0xd7000000,0xff0000) > > (WW) fglrx(0): Failed to set up write-combining range (0xd6000000,0x1ff0000) > > (WW) fglrx(0): Failed to set up write-combining range (0xd4000000,0x3ff0000) > > (WW) fglrx(0): Failed to set up write-combining range (0xd0000000,0x7ff0000) > > (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=0x00000000 ( 0MB), size= 512MB: write-back, count=1 > > reg01: base=0xd7fe0000 (3455MB), size= 64KB: write-combining, count=1 > > reg02: base=0xd7fc0000 (3455MB), size= 128KB: write-combining, count=1 > > reg03: base=0xd7f80000 (3455MB), size= 256KB: write-combining, count=1 > > reg04: base=0xd7f00000 (3455MB), size= 512KB: write-combining, count=1 > > reg05: base=0xd7e00000 (3454MB), size= 1MB: write-combining, count=1 > > reg06: base=0xd7c00000 (3452MB), size= 2MB: write-combining, count=1 > > reg07: base=0xd7800000 (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
