--- Holly Bostick <[EMAIL PROTECTED]> wrote:
> OK, now I have some time to look at this in detail:
>
> maxim wexler schreef:
> >
> > --- Ryan Sims <[EMAIL PROTECTED]> wrote:
> >
> >
> >>On 8/23/05, Mark Knecht <[EMAIL PROTECTED]>
> >>wrote:
> >>
> >>>Hi Maxim,
> >>> An AGP support issue probably. Which kernel
> are
> >>
> >>you using?
>
> Mark, I think you're right:
>
> >>
> >>I found that running with a 2.6.12 kernel gave me
> >>this error;
> >>downgrading to 2.6.11 fixed it. here's a relevant
> >>forum topic:
> >
> >
> > Actually, I *was* using 2.6.11. Now I've compiled
> the
> > 2.6.12 and re-emerged ati-drivers-8.12.10(Why so
> > out-dated, I just did a -uD world a few days
> ago?). It
> > seems to work OK but it fails to produce fglrx.ko.
>
> >
> > Checking for MTRR support enabled ...
> > (we really don't need the color codes, so I'm
> deleting them)
> > Checking for AGP support enabled ...
> >
> > Checking for DRM support disabled ...
> >
> > X11 implementation is xorg-x11.
>
> OK, so this is what I was saying in my other mail;
> the install script
> checks for certain kernel options to be enabled or
> disabled. The three
> options, as you can now see, are
>
> MTRR support must be enabled
>
> AGP support (/dev/agpgart) must be enabled (can be a
> module)
>
> DRM must be disabled
>
> So we got that far, then we get to this:
>
> >>>>Source unpacked.
> >
> > Building the DRM module...
> > make: Entering directory
> > `/usr/src/linux-2.6.12-gentoo-r6'
> > CC [M]
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agp3.o
> > CC [M]
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/nvidia-agp.o
> > CC [M]
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.o
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:
> > In function `agp_find_supported_device':
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7150:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7170:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7175:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7201:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7221:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7241:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:7246:
> > error: structure has no member named `slot_name'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:6542:
> > warning: unused variable `cap_ptr'
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:
> > At top level:
> >
>
/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.c:6523:
> > warning: `agp_check_supported_device' defined but
> not
> > used
> > make[1]: ***
> >
>
[/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/agpgart_be.o]
> > Error 1
> > make: ***
> >
>
[_module_/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod]
> > Error 2
> > make: Leaving directory
> > `/usr/src/linux-2.6.12-gentoo-r6'
> > DRM module not built
>
> Now, I would first think the most likely cause of
> this error is that the
> drivers don't support 2.6.12, and that could
> possibly well be involved.
>
> But the error is totally in agpgart, and I suspect
> that it is due to an
> incomplete kernel configuration.
>
> What motherboard do you have?
Asus K8N-E Deluxe skt 754 w/nVidia chipset
>
> You see, agpgart often doesn't exist on its own in
> the kernel. Many
> motherboard chipsets 'speak their own language' as
> it were, and while
> the kernel can speak to them, it needs to be told
> 'who' it is speaking
> to so that it knows how to be understood by the
> motherboard.
>
> So if I enable /dev/agpgart in my kernel (as I
> must), I also have to
> enable one of the options that becomes available
> when I enable
> /dev/agpgart-- the kernel will not be able to
> communicate with my VIA
> KT266 chipset motherboard, if I do not also enable
> the VIA chipset
> support option, which will compile the via-agp
> module.
>
> And if the kernel can't talk to my motherboard, the
> ati-driver can't
> talk to the kernel and ask it what kind of card is
> connected to that AGP
> slot (because the kernel doesn't know, because it
> can't communicate with
> the motherboard).
>
> In fact, I can't use the internal agpgart compiled
> by the fglrx drivers
> (I have to set UseInternalAGPGART to 'no' in my
done it both ways
> xorg.conf), because the
> kernel needs its own module to talk to my mobo's AGP
> slot (and if the
> kernel can't talk to the AGP slot, then the drivers
> for the card in that
> slot are SOL).
>
> It's possible that you did not compile support for
> your motherboard's
> AGP chipset into the kernel (I find it works best as
> a module, loaded
> with /etc/modules.autoload.d, but it might be doable
> either way). It's
> very possible you need such support as well,
> especially if your chipset
> is one of the following (as you'll see, it covers a
> lot of very common
> motherboard chipsets):
>
>
>
> ALI chipset support
>
> ATI chipset support (this refers to ATI
> motherboards, not video cards)
>
>
> AMD Irongate, 761, and 762 chipset support
>
> AMD Opteron/Athlon64 on-CPU GART support
>
> Intel 440LX/BX/GX, I8xx and E7x05 chipset support
>
> NVIDIA nForce/nForce2 chipset support
>
As it happens boot console warned me about DMA being
off and when I ran hdparm got "HDIO_SET_DMA failed:
operation not permitted". To solve the problem I
compiled support for my nVidia chipset into the
kernel.
ie CONFIG_DEV_AMD74XX=y
now $dmesg
[...]
[ 23.332850] NFORCE3-250: IDE controller at PCI slot
0000:00:08.0
[ 23.332876] NFORCE3-250: chipset revision 162
[ 23.332891] NFORCE3-250: not 100% native mode: will
probe irqs later
[ 23.332909] NFORCE3-250: BIOS didn't set cable bits
correctly. Enabling workaround.
[ 23.332936] NFORCE3-250: 0000:00:08.0 (rev a2)
UDMA133 controller
[ 23.332957] ide0: BM-DMA at 0xffa0-0xffa7, BIOS
settings: hda:DMA, hdb:DMA
[ 23.332994] ide1: BM-DMA at 0xffa8-0xffaf, BIOS
settings: hdc:DMA, hdd:DMA
[ 23.333030] Probing IDE interface ide0...
[...]
Which makes me wonder how nforce3-250 differs from the
nforce2 everybody else seems to be talking about.
I also compiled nvidia-agp as a module but not ati-agp
because the faq says not to, even though I have a
radeon-ati 9250 vid card.
-mw
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
--
gentoo-user@gentoo.org mailing list
