Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/25/05, Mark Knecht [EMAIL PROTECTED] wrote: On 8/25/05, maxim wexler [EMAIL PROTECTED] wrote: --- Holly Bostick [EMAIL PROTECTED] wrote: What motherboard do you have? Asus K8N-E Deluxe skt 754 w/nVidia chipset hehe!! We're in this one together buddy! I managed to buy one of those motherboards today from NewEgg. I'll be building the machine next week. Here's my guess. If you look at 2.6.12-gentoo-r9 the NVidia AGP support clearly says Nforce/Nforce2. My suspicion is that the AGP chipset support for this chipset (NForce4) isn't in the kernel yet and that we need to find a patch, or possibly look at a kernel.org kernel for like 2.6.13/14/15, etc. and find one that does. Assuming that there isn't a patch then we get in line with the kernel developers and work to get one done. I had this problem with my laptop when I first got it and couldn't get DMA for the ATI cipset. It took between 30 and 60 days as I remember. Anyway, I bought one today so I'm in the life raft with ya! Cheers, Mark Maxim, I was looking at this some more since I need to deal with it next week. I found that in the 2.6.12-gentoo-r9 kernel there a kernel config option called 'AMD Opteron/Athlon64 on-CPU GART support' I suspect that this will address many of the issues you're seeing. I've talked with another Athlon64 user who says it's working fine for him. HTH, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Mark Knecht schreef: On 8/25/05, maxim wexler [EMAIL PROTECTED] wrote: --- Holly Bostick [EMAIL PROTECTED] wrote: What motherboard do you have? Asus K8N-E Deluxe skt 754 w/nVidia chipset hehe!! We're in this one together buddy! I managed to buy one of those motherboards today from NewEgg. I'll be building the machine next week. Here's my guess. If you look at 2.6.12-gentoo-r9 the NVidia AGP support clearly says Nforce/Nforce2. My suspicion is that the AGP chipset support for this chipset (NForce4) isn't in the kernel yet and that we need to find a patch, or possibly look at a kernel.org kernel for like 2.6.13/14/15, etc. and find one that does. Assuming that there isn't a patch then we get in line with the kernel developers and work to get one done. I had this problem with my laptop when I first got it and couldn't get DMA for the ATI cipset. It took between 30 and 60 days as I remember. Anyway, I bought one today so I'm in the life raft with ya! Cheers, Mark Have you guys looked at the nvidia site? They have 'drivers' (i.e., kernel modules) for their motherboard chipsets as well as their video cards. Perhaps that's what you both need. I know that nvidia-kernel and nvidia-glx exist in Portage for the video cards, but that's not of much use if your kernel doesn't have the ability to talk to the mobo in the first place (and we do know that an nForce board does speak its own language). http://www.nvidia.com/object/linux_nforce_1.0-0306.html -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/26/05, Holly Bostick [EMAIL PROTECTED] wrote: Mark Knecht schreef: Anyway, I bought one today so I'm in the life raft with ya! Cheers, Mark Have you guys looked at the nvidia site? They have 'drivers' (i.e., kernel modules) for their motherboard chipsets as well as their video cards. Perhaps that's what you both need. I know that nvidia-kernel and nvidia-glx exist in Portage for the video cards, but that's not of much use if your kernel doesn't have the ability to talk to the mobo in the first place (and we do know that an nForce board does speak its own language). http://www.nvidia.com/object/linux_nforce_1.0-0306.html I haven't. Thanks. However I talked to someone using (I think) the same MB under Gentoo. He said he's in gret shape with 2.6.12-gentoo-r9 and the AMD64 GART kernel option. We'll see. Either Maxim will report back in the next few days or I will next week. Thanks for the pointer. cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
--- Mark Knecht [EMAIL PROTECTED] wrote: On 8/25/05, maxim wexler [EMAIL PROTECTED] wrote: --- Holly Bostick [EMAIL PROTECTED] wrote: What motherboard do you have? Asus K8N-E Deluxe skt 754 w/nVidia chipset hehe!! We're in this one together buddy! I managed to buy one of those motherboards today from NewEgg. I'll be building the machine next week. Well, at least X works. What video card will you be using? Here's my guess. If you look at 2.6.12-gentoo-r9 the NVidia AGP support clearly says Nforce/Nforce2. My suspicion is that the AGP chipset support for this chipset (NForce4) isn't in Whoa! NForce4?! What about 2, 3? I'm looking at the Asus User Guide, p xi, in the box, Chipset: NVIDIA nForce3 250Gb the kernel yet and that we need to find a patch, or possibly look at a kernel.org kernel for like 2.6.13/14/15, etc. and find one that does. Assuming that there isn't a patch then we get in line with the kernel developers and work to get one done. I had this problem with my laptop when I first got it and couldn't get DMA for the ATI cipset. It took between 30 and 60 days as I remember. This is all new territory for me. Anyway, I bought one today so I'm in the life raft with ya! Cheers, Mark -- gentoo-user@gentoo.org mailing list UPDATE: did a sync and was able to emerge the new ati-drivers. This time fglrx.ko *was* generated and is loaded at boot. But now I get $startx (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found # faq says ignore (EE) fglrx(0): [agp] unable to acquire AGP, error xf86_ENODEV (EE) fglrx(0): cannot init AGP Could not init font path element /usr/share/fonts/local/, removing from list! The fix according to the faq: I need to clean up the sources make oldconfig etc, re-emerge the drivers. WRONG :( __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Have you guys looked at the nvidia site? They have 'drivers' (i.e., kernel modules) for their motherboard chipsets as well as their video cards. Perhaps that's what you both need. I know that nvidia-kernel and nvidia-glx exist in Portage for the video cards, but that's not of much use if your kernel doesn't have the ability to talk to the mobo in the first place (and we do know that an nForce board does speak its own language). http://www.nvidia.com/object/linux_nforce_1.0-0306.html Wow! Bleedin' edge! I'll try it out and get back to the list. -mw -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Maxim, I was looking at this some more since I need to deal with it next week. I found that in the 2.6.12-gentoo-r9 kernel there a kernel config option called 'AMD Opteron/Athlon64 on-CPU GART support' I suspect that this will address many of the issues you're seeing. I've talked with another Athlon64 user who says it's working fine for him. HTH, Mark Ah! But I'm running a Sempron3100(32bit) CPU. I purchased this board because, so I've been told, it's upgradeable to a 64bit without much fuss. -mw -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/26/05, maxim wexler [EMAIL PROTECTED] wrote: Well, at least X works. What video card will you be using? Contrary to many folks preferences I got an inexpensive PCI-E 1x Radeon to try out. I've had pretty good luck with ATI before. Anyway, I'm going right down the same path you're having trouble with so we're still in this together. It would be thread hijacking to start another conversation about why NVidia is considered 'more open source'. It seems to me that when I emerge nvidia-kernel it doesn't build the driver from source so what's the difference? I do agree from the one NVidia card I got last week (AGP 4X for about $40) that NVidia installed easily and works well, but since I got the ATI fglrx driver working on my laptop I'm getting about 2X the glxgears results (meaningly) vs. what I'm getting from the NVidia. Anyway, I'm not worried about that as my use is audio recording and 3D gaming is but a 30 minute break time occurance here. Here's my guess. If you look at 2.6.12-gentoo-r9 the NVidia AGP support clearly says Nforce/Nforce2. My suspicion is that the AGP chipset support for this chipset (NForce4) isn't in Whoa! NForce4?! What about 2, 3? I'm looking at the Asus User Guide, p xi, in the box, Chipset: NVIDIA nForce3 250Gb You're right. Sorry. This is all new territory for me. for us... ;-) UPDATE: did a sync and was able to emerge the new ati-drivers. This time fglrx.ko *was* generated and is loaded at boot. But now I get $startx (WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found # faq says ignore OK, since the device probably has two outputs for dual screens the system found them both. Look at lspci and you'll probably see devices at PCI:1:0:0 PCI:1:0:1 If the xorgconfig program put a line in somewhere in /etc/X11/xorg.conf telling the system that a screen or device was BusID 1:0:0 then (I guess...) that it's complaining because there isn't some similar version for the second device. Try commenting out the one that is there and then I think the system will accept the definition for both devices. (EE) fglrx(0): [agp] unable to acquire AGP, error xf86_ENODEV OK, so does this kernel have /dev/agpgart and AMD Opteron/Athlon64 on-CPU GART support built as modules? Have you loaded both of the modules? (modprobe agpgart and [[POSSIBLY - I'M GUESSING]] agp-amd64) (EE) fglrx(0): cannot init AGP Again because it's still not happy about the way the kernel part of the AGP stuff is built or installed apparently. Here's how I load the ATI stuff on my laptop: [EMAIL PROTECTED] ~ $ cat /etc/modules.autoload.d/kernel-2.6 # /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots.# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.6,v 1.1 SNIP snd_atiixp realtime gid=408 any=1 sbp2 agpgart ati-agp fglrx [EMAIL PROTECTED] ~ $ Could not init font path element /usr/share/fonts/local/, removing from list! The fix according to the faq: I need to clean up the sources make oldconfig etc, re-emerge the drivers. WRONG :( You'll get there. Search out the real name of the AMD agp-gart driver if you haven't already. good luck, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/26/05, maxim wexler [EMAIL PROTECTED] wrote: Maxim, I was looking at this some more since I need to deal with it next week. I found that in the 2.6.12-gentoo-r9 kernel there a kernel config option called 'AMD Opteron/Athlon64 on-CPU GART support' I suspect that this will address many of the issues you're seeing. I've talked with another Athlon64 user who says it's working fine for him. HTH, Mark Ah! But I'm running a Sempron3100(32bit) CPU. I purchased this board because, so I've been told, it's upgradeable to a 64bit without much fuss. -mw Ah, that's now info. Another processor heard from... Not sure what the right solution would be then... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
You'll get there. Search out the real name of the AMD agp-gart driver if you haven't already. Under dev drvrs-ATA support-AMD and nVidia IDE support * Click help to find it's called CONFIG_BLK_DEV_AMD74XX. I wanted to compile it in so DMA would come alive at boot. I must have done something right because not only did DMA start but the console began to report that it had found the nForce3-250 chipset: [ 30.825814] NFORCE3-250: IDE controller at PCI slot :00:08.0 [ 30.825841] NFORCE3-250: chipset revision 162 [ 30.825856] NFORCE3-250: not 100% native mode: will probe irqs later [ 30.825874] NFORCE3-250: BIOS didn't set cable bits correctly. Enabling worka round. [ 30.825901] NFORCE3-250: :00:08.0 (rev a2) UDMA133 controller [ 30.825921] ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DM A [ 30.825958] ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DM A [ 30.825994] Probing IDE interface ide0... : As far as agp goes CONFIG_AGP=m # CONFIG_AGP_ALI is not set # CONFIG_AGP_ATI is not set # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set # CONFIG_AGP_INTEL is not set CONFIG_AGP_NVIDIA=m # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set # CONFIG_AGP_VIA is not set # CONFIG_AGP_EFFICEON is not set did a search of my config and these are the only instances of the string, agp. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
--- 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? 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. A look at the log reaveals all sorts of errors: [32;01m*[0m Switching to ati OpenGL interface ... Regenerating /etc/ld.so.cache... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m To switch to ATI OpenGL, run opengl-update ati [32;01m*[0m To change your XF86Config you can use the bundled fglrxconfig [33;01m*[0m *** [33;01m*[0m If you are experiencing problems with memory allocation try to add [33;01m*[0m this line to in your X11 configuration file: [33;01m*[0m Option KernelModuleParm agplock=0 [33;01m*[0m That should solve the hangups you could have with Neverwinter Nights [33;01m*[0m *** [32;01m*[0m Determining the location of the kernel source code [32;01m*[0m Found kernel source directory: [32;01m*[0m /usr/src/linux [32;01m*[0m Found sources for kernel version: [32;01m*[0m 2.6.12-gentoo-r6 [32;01m*[0m Checking for MTRR support enabled ... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Checking for AGP support enabled ... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Checking for DRM support disabled ... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m X11 implementation is xorg-x11. Unpacking source... Unpacking fglrx_6_8_0-8.12.10-1.i386.rpm [32;01m*[0m Applying fglrx-2.6-pagetable.patch ... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 8.8.25-via-amd64.patch ... [A[73G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying 8.8.25-smp.patch ... [A[73G [34;01m[ [32;01mok[34;01m ][0m Source unpacked. [32;01m*[0m 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' [33;01m*[0m DRM module not built Test phase [not enabled]: media-video/ati-drivers-8.12.10 Install ati-drivers-8.12.10 into /var/tmp/portage/ati-drivers-8.12.10/image/ category media-video install: cannot stat `/var/tmp/portage/ati-drivers-8.12.10/work/lib/modules/fglrx/build_mod/fglrx.ko': No such file or directory man: making executable: /usr/lib/libfglrx_gamma.so.1.0 Completed installing ati-drivers-8.12.10 into /var/tmp/portage/ati-drivers-8.12.10/image/ http://forums.gentoo.org/viewtopic-t-353295-highlight-xf86enomem.html Seems that the problem might be resolved with latest ati-drivers* and latest gentoo-sources, YMMV, I haven't had the chance to play with it much lately. But what's the best way to proceed? emerge seems happy with the older(?) drivers. Shouldn't it be
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Another thing, http://forums.gentoo.org/viewtopic-t-353295-highlight-xf86enomem.html all seem to be complaining about DRM failure but according to the gentoo-radeon-faq: * Device drivers - Character Devices - Direct Rendering Manager (XFree86 4.1.0 and higher DRI support): DISABLED This option is not required, and will almost certainly prevent the driver from working if enabled. So in my config it's not set. Is the faq wrong? -mw Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
maxim wexler schreef: Another thing, http://forums.gentoo.org/viewtopic-t-353295-highlight-xf86enomem.html all seem to be complaining about DRM failure but according to the gentoo-radeon-faq: * Device drivers - Character Devices - Direct Rendering Manager (XFree86 4.1.0 and higher DRI support): DISABLED This option is not required, and will almost certainly prevent the driver from working if enabled. So in my config it's not set. Is the faq wrong? -mw Absolutely not. The fglrx driver will not run if the kernel DRM is enabled, and in fact these days, it won't even install (the install script checks for this, as well as two other kernel settings, explicitly, before building the DRI module). The DRM that people are referring to is presumably the DRM built by the fglrx driver install, which replaces the kernel module, and is completely incompatible with the kernel module (which is why the kernel module has to be disabled in order to run the fglrx driver). Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/25/05, maxim wexler [EMAIL PROTECTED] wrote: Another thing, http://forums.gentoo.org/viewtopic-t-353295-highlight-xf86enomem.html all seem to be complaining about DRM failure but according to the gentoo-radeon-faq: * Device drivers - Character Devices - Direct Rendering Manager (XFree86 4.1.0 and higher DRI support): DISABLED This option is not required, and will almost certainly prevent the driver from working if enabled. So in my config it's not set. Is the faq wrong? -mw Depends on which FAQ and which driver. For the fglrx driver I think/I'm sure it has to be disabled. As for ati-drivers it seems you are getting one older then I'm using: flash ~ # emerge -pv ati-drivers These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] media-video/ati-drivers-8.14.13-r2 +opengl 0 kB Total size of downloads: 0 kB flash ~ # Do an emerge sync I think. Good luck, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
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? 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 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
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
--- 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
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Perhaps you didn't select it (a lot of people make that === message truncated === sorry for posting twice I had to go re-read the truncated part. #eix ati-drivers Can't open database for file /var/cache/eix. that's because there ain't none. ditto /etc/portage/package.mask. something else I noticed. What's going on here? It's got the newer ebuild. [EMAIL PROTECTED] ~ $ ls -l /usr/portage/media-video/ati-drivers total 101 -rw-r--r-- 1 root root 17846 Aug 4 09:37 ChangeLog -rw-r--r-- 1 root root 2786 Aug 4 09:37 Manifest -rw-r--r-- 1 root root 5968 Apr 8 01:05 ati-drivers-8.10.19.ebuild -rw-r--r-- 1 root root 6746 May 7 19:05 ati-drivers-8.12.10.ebuild -rw-r--r-- 1 root root 6800 May 21 20:22 ati-drivers-8.13.3.ebuild -rw-r--r-- 1 root root 6916 Jun 25 09:19 ati-drivers-8.13.4.ebuild -rw-r--r-- 1 root root 6529 Jun 25 09:05 ati-drivers-8.14.13-r1.ebuild -rw-r--r-- 1 root root 6606 Jul 29 12:05 ati-drivers-8.14.13-r2.ebuild -rw-r--r-- 1 root root 7610 Aug 3 23:04 ati-drivers-8.14.13-r3.ebuild -rw-r--r-- 1 root root 6800 Jun 25 09:05 ati-drivers-8.14.13.ebuild -rw-r--r-- 1 root root 5753 Apr 18 07:05 ati-drivers-8.8.25-r3.ebuild drwxr-xr-x 2 root root 1280 Aug 4 09:37 files -rw-r--r-- 1 root root 227 Apr 25 06:05 metadata.xml -mw Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/25/05, maxim wexler [EMAIL PROTECTED] wrote: --- Holly Bostick [EMAIL PROTECTED] wrote: What motherboard do you have? Asus K8N-E Deluxe skt 754 w/nVidia chipset hehe!! We're in this one together buddy! I managed to buy one of those motherboards today from NewEgg. I'll be building the machine next week. Here's my guess. If you look at 2.6.12-gentoo-r9 the NVidia AGP support clearly says Nforce/Nforce2. My suspicion is that the AGP chipset support for this chipset (NForce4) isn't in the kernel yet and that we need to find a patch, or possibly look at a kernel.org kernel for like 2.6.13/14/15, etc. and find one that does. Assuming that there isn't a patch then we get in line with the kernel developers and work to get one done. I had this problem with my laptop when I first got it and couldn't get DMA for the ATI cipset. It took between 30 and 60 days as I remember. Anyway, I bought one today so I'm in the life raft with ya! Cheers, Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
On 8/23/05, Mark Knecht [EMAIL PROTECTED] wrote: Hi Maxim, An AGP support issue probably. Which kernel are you using? 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: http://forums.gentoo.org/viewtopic-t-353295-highlight-xf86enomem.html Seems that the problem might be resolved with latest ati-drivers* and latest gentoo-sources, YMMV, I haven't had the chance to play with it much lately. *I notice that ati-drivers-8.14.13-r2 has fglrx-8.14.13-alt-2.6.12-agp.patch added, might be apropos: http://gentoo-portage.com/media-video/ati-drivers/ChangeLog -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ati -- dreaded xf86-ENOMEM error
Hi Maxim, An AGP support issue probably. Which kernel are you using? My recommendation (which sounds like you've been doing so I'm not sure there's any value here.) would be: 1) Build your kernel with support for /dev/agpgart and the right chipset support under that section. Make them both modular. 2) Set UseInternalGART=no in xorg.conf 3) Add agpgart agp-XXX fglrx (where XXX is the chipset support you built in step #1) to /etc/modules.autoload/kernel-2.6 4) Do a complete reboot. 5) Check dmesg and make sure the agp support loaded 6) Re-emerge ati-drivers and ati-drivers-extra. Make sure they really build. 7) Do another reboot. 8) Check lsmod to make sure the modules 9) Check /var/log/xorg.0.log for warnings and errors. 10) Check glxinfo to see if you're getting acceleration support. 11) Grab a beer. Good luck, Mark On 8/23/05, maxim wexler [EMAIL PROTECTED] wrote: Hello everybody, Been chewing on this for weeks. So far have run opengl-update ati, added Option Kernel ModuleParm agplock=0 to xorg.conf, re-emerged ati-drivers, used both yes and no in xorg.conf re using internal drivers, juggled fglrx, agpgart, nvidia-agp in different order, configured kernel according to ati-FAQ. Here's the tail of startx and dmesg. $startx (EE) fglrx(0): [agp] unable to acquire AGP, error xf86_ENOMEM (EE) fglrx(0): cannot init AGP Could not init font path element /usr/share/fonts/local/, removing from list! $dmesg Linux agpgart interface v0.100 (c) Dave Jones [fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes. ACPI: PCI interrupt :01:00.0[A] - GSI 11 (level, low) - IRQ 11 [fglrx] module loaded - fglrx 8.12.10 [Apr 4 2005] on minor 0 [fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes. [fglrx] AGP detected, AgpState = 0x (hardware caps of chipset) [fglrx:firegl_unlock] *ERROR* Process 18737 using kernel context 0 Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
