Not at all happy....

[blueworm]

Compiling the kernel is very daunting at first but it is really quite easy once you have done it a few times.

[TheOneKEA]

Originally posted by JeffShultz
Unfortunately this is what I get:
[root@master jbshultz]# modprobe agpgart
/lib/modules/2.4.21-0.25mdk/kernel/drivers/char/agp/agpgart.o.gz: init_module: No such device
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
modprobe: insmod /lib/modules/2.4.21-0.25mdk/kernel/drivers/char/agp/agpgart.o.gz failed
modprobe: insmod agpgart failed

As can sort of be seen from above, I do have a file agpgart.o.gz in the right place.

When I exit X (I boot up in init3) there are a bunch of errors that indicate that, quite simply, this thing isn't finding the AGP port.

Frustrating.

Can you post the tail end of the output of the command 'dmesg' IMMEDIATELY after attempting to load agpgart?

[JeffShultz]

Originally posted by TheOneKEA
Can you post the tail end of the output of the command 'dmesg' IMMEDIATELY after attempting to load agpgart?

The only thing in dmesg about agpgart is this:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.


It's repeated several times.

Thanks.

[TheOneKEA]

Edit your /etc/modules.conf file as root and add this line:

options agpgart agp_try_unsupported=1

Then run /sbin/depmod -a as root and try to load agpgart again. Post the output of dmesg immediately after load as well.

[JeffShultz]

Originally posted by TheOneKEA
Edit your /etc/modules.conf file as root and add this line:

options agpgart agp_try_unsupported=1

Then run /sbin/depmod -a as root and try to load agpgart again. Post the output of dmesg immediately after load as well.

probeall scsi_hostadapter ide-scsi
alias eth0 tulip
alias sound-slot-0 i810_audio
probeall usb-interface usb-ohci ehci-hcd
alias ieee1394-controller ohci1394
options agpgart agp_try_unsupported=1
~
is what my modules.conf looks like.

Using /lib/modules/2.4.21-0.25mdk/kernel/drivers/char/agp/agpgart.o.gz
/lib/modules/2.4.21-0.25mdk/kernel/drivers/char/agp/agpgart.o.gz: init_module: No such device
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

Is the response from insmod agpgart

and,
UDF-fs DEBUG lowlevel.c:57:udf_get_last_session: XA disk: no, vol_desc_start=0
UDF-fs DEBUG super.c:1426:udf_read_super: Multi-session=0
UDF-fs DEBUG super.c:415:udf_vrs: Starting at sector 16 (2048 byte sectors)
UDF-fs DEBUG super.c:442:udf_vrs: ISO9660 Primary Volume Descriptor found
UDF-fs DEBUG super.c:439:udf_vrs: ISO9660 Boot Record found
UDF-fs DEBUG super.c:445:udf_vrs: ISO9660 Supplementary Volume Descriptor found
UDF-fs DEBUG super.c:451:udf_vrs: ISO9660 Volume Descriptor Set Terminator found
UDF-fs: No VRS found
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.

Is the tail end of dmesg immediately afterwords.

Unfortunately... AGP just ain't talking on this mobo.

Jeff

[TheOneKEA]

Urk. All I can suggest now is to parse the MAINTAINERS file in the Linux kernel source and send an e-mail to the agpgart maintainer asking for help. Be sure to include all possible information, like hardware setup, kernel config, log snippets, everything.

[Zenikase]

Sorry to derail the current topic, but you don't need nvaudio anymore. Just get the latest ALSA driver and specify support for 'intel8x0' (which they indicate to use for nForce). Sound should work fine then.