Re: [gentoo-user] two ati-drivers packages using --deep --update

[Manuel McLure]

Mark Knecht wrote:
> On 11/7/05, Manuel McLure <manuel@××××××.org> 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 (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.

-- 
Manuel A. McLure KE6TAW <manuel@××××××.org> <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@g.o mailing list