Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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 tried to add those lines to the modules.conf but it still doesn't load up the Xserver. I get the same install screen as BlinkEye. Does that mean it is not installing correctly? Also do you use the external agpgart module when you run the fglrxconfig? It ask you if you want to use it. default is not to. Any more ideas are appreciated.
The readme that ships with the driver states that it will use the external AGPGART if it's available. As there seems to be extremely limited support (i.e. it isn't) for the SiS648 AGP chipset the only way I can get AGPGART to initialise is to use these statements.
Tell me, does AGPGART actually seem to load when you have these lines ?. su to root and try to 'modprobe agpgart' without loading the XServer, does it load or throw errors ?
Oh and BTW: do you know what chipset your motherboard is using ?
HINT: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find info in sys log or the output file from dmesg.
Checking which OS you're running...
uname reports 'Linux' version '2.4.20-4GB-athlon', architecture 'i686'.
Object format is 'ELF'.
libc version is '6.3'.
XFree86 Version 4.3.0 is installed.
No package available for glibc 2.3. Try fglrx-glibc22.tgz
Binary package name is 'fglrx-glibc21.tgz'
--
And when I run './install_make.sh', I get this error:
" warning: loading /lib/modules/2.4.20-4GB-athlon/kernel/drivers/char/drm/fglrx.o will taint the kernel.
more info see: www.tux.org/lkml/#export-tainted "
Kos, iamasmith, E-razoor, etc... I have these problems too. "AGP cant init" seems to be the core of the problem (cant find agp aperture size)... I've heard the problem is because kernel 2.4 doesnt support agp 3.0 (8x).. I havent figured out a way to slow it down to 4x (my bios wont do it)... I have VIA chipset KT400/radeon 9500 np .. i've tried to upgrade to kernel 2.5.x or 2.6 but i keep getting compilation erros.. any help would be appreciated!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
E-razor, the warning about the module tainting the kernel is a bit of a red herring, I think I'm pretty safe in saying that we all get this (works on my machine).
I would say that the problem is more likely to be related to neither the internal AGP or kernel based AGPGART being able to support the MOBO AGP chipset.
I guess I was lucky being able to simply use the agp_try_unsupported option. I still only get 4X AGP though, this seems to be somewhat related to the fact that without special initialisation to status register of the MOBO doesn't advertise 8X as an option :-(.
Ah well it's still better than my previous video card.
Actually the 4X speed that you mention is also AGP3, this is not quite the same as the AGP2 4X.
With AGP2 the status register reports speed in 3 bits (r to l) as 1, 2 or 4 speed.
Essentially the AGP3 spec sets some additional bits in the status register (spec available from the developer.intel.com website) but only uses two bits for speed that originally specified 1x and 2x AGP rate and uses them for 4x and 8x instead.
In my experience though the AGPGART seems to be used to gain a stable handle to teh hardware and rate initialisation is carried out by the video driver talking to AGPGART.
I would see if you have the latest driver revision because there seems to be some support in the source in /lib/modules/fglrx/build_mod for the KT400 chipset on my rev.
I'm using RH9 with RPM fglrx-glc22-4.3.0-2.9.13.i586.rpm.
I didnt know that about agp3 vs. agp2.. i just thought 3 was 8x.. either way.. mine isnt working.. I was using Mandrake 9.1 (kernel 2.4.13-mdk) and I have tried 3 or 4 different fglrx rpms (including the one you just mentioned).. maybe the built in agpgart wasn't being added by fglrxconfig or initialised in the XF86Config-4 file... I'm about to format and start over because i hosed up my kernel trying to install 2.6.0 test kernel... so.. i beleive i'll need to slow my vid card down to 4x for agp to initialise.. maybe i'm wrong.. i dont think there is any advantage of 8x vs. 4x, anyway (i benchmarked both under windows and they seemed to be about the same... apparently bandwidth to the mb isnt my bottleneck for 3d performance)... suggestions from starting from scratch?
Don't want to state the obvious here but try going to the latest 'supported' kernel - preferrably via the update service that Mandrake provides. There have been some enhancements including additional chipset support added to AGPGART since 2.4.13.
I think that I would try getting it to work with the internal AGPGART stuff first though. Don't know how much of it is actually implemented (some comments about bits not working yet in the source) but there's definitely additional stuff to handle extra AGP3 specific initialisation.
i had 2D stuff working fine.. it was using those crappy mesa driver thingies.. i cant beleive the kernel is so far behind that it doesnt already support 8x agp... it has been out for a long time.. this would be easier to get working on windows 98.. linux is retarded for workstations and gaming
I think the big problem is really with getting hold of the programming guides to the chipsets. MOBO vendors simply aren't that interested in supporting Linux and if you ever tried to get a data sheet out of a Chipset vendor... well it's difficult unless you have a commercial relationship.
Information takes a while to leak out from places to people adding chipset support to various things like the AGP chipsets. In theory they should all follow the programmers guide that Intel published for the AGP3 spec but it seems that some require some additional initialisation.
Anyone out there with an SiS648 programmers datasheet ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.