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.
Alright, I have freshly compiled my kernel. Anyway, I compiled AGP Gart as a module with the VIA chipset.
To make a long story short, when I reboot into my new kernel or even the stock kernel I get errors.
Code:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Trying generic Via routines for device id: 3205
agpgart: unable to determine aperture size.
I'm 99% positive I have VIA chipset. I disabled the onboard video. I have a Radeon 9600.
Basically, if someone can help me troubleshoot this and get it working, I will greatly appreciate it.
NOTE: This error occurs under ALL kernels: 2.4.29/2.4.30/2.6.11.7
Strange, because it seems you did everything exactly the way it should be, AGPGART should if I'm not mistakem be compiled as a module and not directly into the kernel. One possible thing you can try, I hope you kept your original kernel 2.4, boot into that and look through the syslog and dmesg, and see exactly what it says about AGPGART, there might be something else you have missed, but I am trying to rack my brain and figure out what, because really it sounds like you compiled AGPGART as a module, and thats usually a good way to go....
Also, here is my syslog. It's partial to stuff I'm getting errors on.
Code:
May 5 12:51:34 bigp kernel: agpgart: Trying generic Via routines for device id: 3205
May 5 12:51:34 bigp kernel: agpgart: unable to determine aperture size.
May 5 12:51:34 bigp hal.hotplug[121]: could not get mountpoint for sysfs
May 5 12:51:34 bigp hal.hotplug[165]: could not get mountpoint for sysfs
May 5 12:51:35 bigp hal.hotplug[223]: could not get mountpoint for sysfs
May 5 12:51:36 bigp hal.hotplug[280]: could not get mountpoint for sysfs
May 5 12:51:36 bigp hal.hotplug[294]: could not get mountpoint for sysfs
May 5 12:51:36 bigp hal.hotplug[308]: could not get mountpoint for sysfs
May 5 12:51:36 bigp hal.hotplug[329]: could not get mountpoint for sysfs
May 5 12:51:36 bigp kernel: shpchp: shpc_init : shpc_cap_offset == 0
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: 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
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: 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
May 5 12:51:36 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
May 5 12:51:36 bigp hal.hotplug[428]: could not get mountpoint for sysfs
May 5 12:51:37 bigp kernel: shpchp: shpc_init : shpc_cap_offset == 0
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: 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
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: 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
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
May 5 12:51:37 bigp hal.hotplug[603]: could not get mountpoint for sysfs
May 5 12:51:37 bigp kernel: shpchp: shpc_init : shpc_cap_offset == 0
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: 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
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: 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
May 5 12:51:37 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
May 5 12:51:37 bigp hal.hotplug[778]: could not get mountpoint for sysfs
May 5 12:51:37 bigp kernel: shpchp: shpc_init : shpc_cap_offset == 0
May 5 12:51:43 bigp insmod: /lib/modules/2.4.30/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed
May 5 12:52:25 bigp smbd[3235]: [2005/05/05 12:52:25, 0] param/loadparm.c:lp_do_parameter(3162)
May 5 12:52:25 bigp smbd[3235]: Global parameter client signing found in service section!
May 5 12:52:25 bigp smbd[3235]: [2005/05/05 12:52:25, 0] printing/print_cups.c:cups_cache_reload(85)
May 5 12:52:25 bigp smbd[3235]: Unable to connect to CUPS server localhost - Connection refused
May 5 12:52:25 bigp smbd[3235]: [2005/05/05 12:52:25, 0] printing/print_cups.c:cups_cache_reload(85)
May 5 12:52:25 bigp smbd[3235]: Unable to connect to CUPS server localhost - Connection refused
May 5 12:52:26 bigp /usr/sbin/gpm[3241]: imps2: PS/2 mouse failed init
May 5 12:52:26 bigp /usr/sbin/gpm[3241]: oops() invoked from gpm.c(1003)
May 5 12:52:26 bigp /usr/sbin/gpm[3241]: mouse initialization failed: Inappropriate ioctl for device
May 5 13:16:27 bigp nmbd[3239]: [2005/05/05 13:16:27, 0] nmbd/nmbd.c:terminate(56)
May 5 13:16:27 bigp nmbd[3239]: Got SIGTERM: going down...
May 5 13:17:02 bigp kernel: Linux version 2.4.30 (root@bigp) (gcc version 3.3.5) #1 Thu May 5 13:12:15 EDT 2005
May 5 13:17:02 bigp kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
May 5 13:17:02 bigp kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
May 5 13:17:02 bigp kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
May 5 13:17:02 bigp kernel: BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
May 5 13:17:02 bigp kernel: BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
May 5 13:17:02 bigp kernel: BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
May 5 13:17:02 bigp kernel: BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
May 5 13:17:02 bigp kernel: BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
May 5 13:17:02 bigp kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
do you have a /sys directory ?
if not, you should do a " #mkdir /sys " as root.
then logout of X and rerun /etc/rc.d/rc.S
and do a " #modprobe agpgart "
mayby it also solves your agp-prob.
( do a " #modprobe agpgart " to check )
Testing root filesystem status: read-write filesystem
*** ERROR: Root partition has already been mounted read-write. Cannot check!
For filesystem checking to work properly, your system must initially mount
the root partition as read only. Please modify your kernel with 'rdev' so that
it does this. If you're booting with LILO, add a line:
read-only
to the Linux section in your /etc/lilo.conf and type 'lilo' to reinstall it.
If you boot from a kernel on a floppy disk, put it in the drive and type:
rdev -R /dev/fd0 1
If you boot from a bootdisk, or with Loadlin, you can add the 'ro' flag.
This will fix the problem *AND* eliminate this annoying message. :^)
Press ENTER to continue. Setting system time from the hardware clock (localtime).
Module dependencies up to date (no new kernel modules found).
Checking non-root filesystems:
fsck 1.35 (28-Feb-2004)
Using /etc/random-seed to initialize /dev/urandom.
I ran it two times. First time, It got an error with AGP, second...I guess it didn't record it or it didn't happen heh.
root@bigp:~# modprobe agpgart
/lib/modules/2.4.30/kernel/drivers/char/agp/agpgart.o: init_module: Invalid argument
/lib/modules/2.4.30/kernel/drivers/char/agp/agpgart.o: 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.30/kernel/drivers/char/agp/agpgart.o: insmod /lib/modules/2.4.30/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.30/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed
Also, when I compile my kernel, at the end of 'make modules_install', I get the following line -- it just seems a bit suspicious to me.
Code:
d /lib/modules/2.4.30; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.30; fi
I am not sure if the 'if' statement is supposed to be there. It might be causing the kernel's modules to prematurely quit compiling, thus causing me to not have agpgart?
yeah....some errors were to expect there.
( rc.S is the startupscript and it tries to check the filesystems, but they are mounted rw already )
but i thought /sys was missing. and that wasn't the case.
maybe check your bios-settings for agp.
should be enabled with aperture of 64 mb ( that's from my memory, not sure )
EDIT: that last message from modules_install is normal.
well....i don't know if aperture size has to equal the cards memory-size.
but the only thing i can think of right now would be the bios settings,
as that agp-error appears with every kernel you tried.
maybe just try it and see ?
btw: i have 64 mb on my graph-card, so you might be right.
I don't know any BIOS settings that could possibly effect this other than that. Everything is basically default in my bios with the exception of the setting to change from onboard video to agp.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.