heya, well.. are you sure that your kernel compile compiled those as modules when you made your kernel? (a quick way to check is to grep through the /boot/config-<version>) if so, try re-installing your kernel package .deb(s). there's a y/n question in the process that might keeps you from accidentally nuking your old drivers that might have kept you from putting in your new ones. if not, try insmod'ing them from where they are and see if nothing complains. if they really are the modules made with your kernel, they should slip in and out without any fuss, but if not there should be a good deal of said fuss (specifically, whining about unresolved symbols) hth, because all series suck after part III (just look at rocky, superman...) sean On Sun, Jan 05, 2003 at 12:05:04PM +0800, Robert Storey wrote: > Hi all, > > Part 3 of my "kernel compile saga." > > My new kernel compiles OK, it boots OK, but there are no modules. Typing > lsmod shows no modules loaded, even though /etc/modules says: > > msdos > via-rhine > ide-scsi > sg > agpgart > es1370 > parport > parport_pc > > A look in directory /lib/modules/2.4.19/kernel/drivers confirms that the > directory is empty. I can find compiled drivers in > /usr/src/linux-2.4.19/drivers, but I don't know how to get these to > install. Can I get away with just copying them one by one into their > proper location? Seems like a very Micky Mouse solution - I'd like to > know why they didn't install when I installed the kernel. > > Hoping someone can enlighten me. > > best regards, > Robert > > > > -- > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org >
Attachment:
pgpfGBR8pdoWS.pgp
Description: PGP signature