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.
Does anyone know if VIA KT400 chipset's AGP works ?
I tried new 2.4.21-pre1 kernel because it's docment said to support KT400.
But it doesn't work with my A7V8X motherboard.
when I tried, I got a message like bellow. (in dmesg)
--command---------------------------------------------------
# insmod agpgart
Using /lib/modules/2.4.21-pre1/kernel/drivers/char/agp/agpgart.o
/lib/modules/2.4.21-pre1/kernel/drivers/char/agp/agpgart.o: init_module: Invalid argument
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
--dmesg------------------------------------------------------
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
---------------------------------------------------------------
I think agpgart module detected KT400 correctly.
Then I checked IRQ conflicting and found no problem.
(using APIC. is this a problem ?)
And my "lspci -v" is like bellow...
Sorry for long message...
--lspci -v----------------------------------------------------
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3189
Subsystem: Asustek Computer, Inc.: Unknown device 807f
Flags: bus master, 66Mhz, medium devsel, latency 0
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [80] AGP version 3.5
Capabilities: [c0] Power Management version 2
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b168 (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: ee000000-efdfffff
Prefetchable memory behind bridge: eff00000-f7ffffff
Capabilities: [80] Power Management version 2
00:09.0 Ethernet controller: Broadcom Corporation: Unknown device 4401 (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 80a8
Flags: bus master, fast devsel, latency 32, IRQ 10
Memory at ed800000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at efef0000 [disabled] [size=16K]
Capabilities: [40] Power Management version 2
00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Flags: bus master, medium devsel, latency 32, IRQ 4
Memory at ed000000 (32-bit, non-prefetchable) [size=512]
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, medium devsel, latency 32, IRQ 3
I/O ports at d800 [size=32]
Capabilities: [80] Power Management version 2
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, medium devsel, latency 32, IRQ 3
I/O ports at d400 [size=32]
Capabilities: [80] Power Management version 2
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 [UHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, medium devsel, latency 32, IRQ 3
I/O ports at d000 [size=32]
Capabilities: [80] Power Management version 2
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, medium devsel, latency 32, IRQ 3
Memory at ec800000 (32-bit, non-prefetchable) [size=256]
Capabilities: [80] Power Management version 2
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: [c0] Power Management version 2
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: Asustek Computer, Inc.: Unknown device 808c
Flags: bus master, medium devsel, latency 32
I/O ports at b800 [size=16]
Capabilities: [c0] Power Management version 2
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 50)
Subsystem: Asustek Computer, Inc.: Unknown device 8095
Flags: medium devsel, IRQ 7
I/O ports at e000 [size=256]
Capabilities: [c0] Power Management version 2
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0281 (rev
a1) (prog-if 00 [VGA])
Subsystem: Micro-star International Co Ltd: Unknown device 8497
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 11
Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at effe0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
------------------------------------------------------
The agp_try_unsupported helps when it's not a supported chipset. But with the 2.4.21-pre1 kernel it should be supported so I don't know how much difference that option will make, it might help though.
I still have a 2.4.20 kernel but I applied just the patch to add support for the KT400 chipsets which is also in the kernel you have. I have an MSI motherboard though and I do get different output.
lspci -v shows:
Code:
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3189
Subsystem: VIA Technologies, Inc.: Unknown device 0000
Flags: bus master, 66Mhz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [a0] AGP version 2.0
Capabilities: [c0] Power Management version 2
dmesg shows:
Code:
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: AGP aperture is 128M @ 0xe0000000
I don't get any errors or warnings when running insmod. I still get a suspicious message from dmesg which makes me doubt if everything is a 100% supported:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
I haven't had a lot of time to look into these things yet. And since it still works I've been working on getting other issues solved first.
I noticed that your PCI output mentions AGP 3.0 (AGP 8x) on that nVidia card; AGP8x is not currently supported except by very recent 2.5.x kernels. Try plopping an older non-8x card in this joker.
I have a KT400 with an ATI Radeon 9700, and I get the same problem of the apperture size not getting recognized. My motherboard also has the x8 AGP feature. Turning it from the BIOS to x4 did not help. Is there a way to force the kernel to use x4? Will this be of any help?
i've got the same Problem with this Asus Board and i think it's a little Bug in the " agp " Driver, because with the Development Kernel ( 2.5.66-ac2 ) works !!!
I also have the A7V8X which works fine here with a Matrox G550 video card. I have compiled in the agp support, not as a module. The fact that your card is 8x shouldn't bother, it's just an unused feature.
The newer boards with 8x architecture causes a problem for the older agpgart modules... (I have a via w/ P4X400 chipset that is not currently supported so I've been reading a lot in prepping to hack the kernel if I must). The 8x architecture has 16 bit registers as opposed to 8bits on the older boards. This is why the older agpgart modules cannot detect the aperture size... they can't read the aperture registers. agp 3.0 support (and support for the kt400) has been included into the 2.5 kernel series by Dave Jones.
In case I'm not the only person with a Via P4PB Ultra around here... if you're worried about support for your agp (I know I am... I want my radeon 9700 pro to work) keep in touch and I'll let you know what I do / don't get working.
I don't know if this is related, but I'm running an A7V8X with VIA KT400, and in a thread I posted someone told my to try:
modprobe agpgart agp_try_unsupported=1
I did this and got this error:
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: init_module: Invalid argument
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: insmod /lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.20-gentoo-r5/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed
the 2.4.20 will not (to the best of my knowledge) support the KT400 chipset in AGP 3.0 (8x). There have been reports of it working in 4x mode however. What type of video card are you running?
P.S. The 2.5.x and subsequent 2.6.x series linux kernel does support the KT400 however neither of these kernels are production at the moment.
Originally posted by jpbarto the 2.4.20 will not (to the best of my knowledge) support the KT400 chipset in AGP 3.0 (8x). There have been reports of it working in 4x mode however. What type of video card are you running?
It works fine for me as i said above. I have nvidia. i did recompile with the latest (2.4.20 series) kernal and all of Alan cox's patches though. They mentioned AGPGART in there so that may be good to try
ex0 I have a similiar situation. my mobo supports 2x, 4x, and 8x. the 9700 pro does 8x (and I think 4x). However the mobo detects that the card is capable of 8x and sets it to 8x without letting the user 'dumb-it-down'. Kinda a lack of configurability.
However the 9600 on KT400 should be supported via the Schneider Digital drivers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.