SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am on a laptop too, so there is no switching. ATI manages to fix most of the bugs when they release their new drivers, but then a kernel update throws them off again. They must have like 2 people or some similarly small group of people working on the drivers, judging by the updates we get. Given the small incentive for spending money on Linux, it's understandable.
I can run the 2d drivers fine if I just delete the fglrx module, just means I have to live without hardware acceleration for a while I guess.
Originally posted by v1_ad what does it mean "(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"" ?
Perhaps external agpgart (ati 8.14.13) is not compatible with 2.6.12 kernel !?
someone ???
X Fails to Load on Systems with Linux Kernel Version 2.6.x
This information applies to the following system configurations:
* Linux kernel version 2.6.x
* Any ATI Linux driver
A blank screen may appear momentarily when X starts to load. The following error message (or similar) may appear on the text console or in /var/log/XFree86.0.log:
(EE) fglrx(0): [agp] unable to acquire AGP, error ""xf86_ENODEV""xf86_ENODEV""
This is not a problem with the display driver.
Version 2.6 kernels require a second kernel module in addition to agpgart, which should be named similar to the manufacturer of your motherboard AGP chipset. This error message should occur if the other agp module is not loaded.
This issue can be worked around as follows:
1. First make sure that agpgart is loading properly.
2. To find out which AGP controller your motherboard uses, issue the following command: lspci | grep AGP
3. To find a list of AGP related kernel modules installed on your machine, issue the following command and look for a module (*.ko file) that suits your AGP Controller: ls /lib/modules/`uname -r`/kernel/drivers/char/agp
4. Use the modprobe command (as root) to load the module. For example: On a motherboard using a VIAŽ AGP Controller, you would load the via-agp.ko using modprobe as follows (notice that the trailing .ko is omitted): modprobe via-agp
Check the modprobe manpage for more information on loading kernel modules.
5. To verify that the AGP module is already loaded, run lsmod as root. With the X server running and the connection established, the usage count of this module must be greater than zero.
If you cannot find a suitable agp module for your motherboard, then you may want to upgrade to the latest version of the Linux kernel, or check your motherboard manufacturer's website for more information.
another
when I am working on 2.6.12.2 kernel
after startx computer works without dri
when I am trying to stratx again computer freezes sreen goes black and that all
What happens if you try to modprobe intel_mch_agp in 2.6.12.2? I'm completely new to this, but maybe you need that one as well in order to achieve full agp-support?
I found that in 2.6.11.12 kernel I have :
Intel 440LX/BX/GX, I8xx and E7x05 chipset support AGP_INTEL
This option gives you AGP support for the GLX component of XFree86 4.x
on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850, 860, 875,
E7205 and E7505 chipsets and full support for the 810, 815, 830M, 845G,
852GM, 855GM, 865G and I915 integrated graphics chipsets.
You should say Y here if you use XFree86 3.3.6 or 4.x and want to
use GLX or DRI, or if you have any Intel integrated graphics
chipsets. If unsure, say Y.
and
Intel i865 chipset support AGP_INTEL_MCH
This option gives you AGP support for the GLX component of XFree86 4.x
on Intel chipsets that support Intel EM64T processors.
You should say Y here if you use XFree86 3.3.6 or 4.x and want to
use GLX or DRI. If unsure, say Y.
and in 2.6.12.2
I only have:
ntel 440LX/BX/GX, I8xx and E7x05 chipset support AGP_INTEL
This option gives you AGP support for the GLX component of XFree86 4.x
on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850, 860, 875,
E7205 and E7505 chipsets and full support for the 810, 815, 830M, 845G,
852GM, 855GM, 865G and I915 integrated graphics chipsets.
You should say Y here if you use XFree86 3.3.6 or 4.x and want to
use GLX or DRI, or if you have any Intel integrated graphics
chipsets. If unsure, say Y.
Thanks, Erratio. However, I already fixed the compiler problems, it just seems now that the fglrx module wants to freeze X session attempts. It compiles but it makes the screen go black.
I was a little hasty in posting the last message, or at least should have added a disclaimer. I didn't have time to fully try it out myself, and it didn't end up working when I did...initially it installed without acceleration, and now I have a freezing with a black screen problem as well. Luckily? the problem remained when recompiling for 2.6.11, so it should allow for more controlled troubleshooting...
the dev->slot_name to pci_name(dev) conversion seems to work fine, but the 'inter_module_get_request' seems to be what's causing the problem, since when that was removed I regained acceleration in 2.6.11. I'll play with it a bit more later if I have time, but if anyone knows of a better substitute for 'inter_module_get', that's seems to be what's missing. Rather than replacing them I also just put a '#define inter_module_get(x) inter_module_get_request(x,"")' line in the file, which could be thrown into a preprocessor conditional for a more robust patch.
and just a slight addendum...glancing at the code all the occurences of the dev->slot_name call seem to be in printk() statements, so they shouldn't be causing much of any problems anyway.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.