-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 06 September 2003 19:43, Mark Knecht wrote:
> At this point all the drivers that I seem to need are running without > errors. However, depmod is not happy about other things installed on my > system: > > Wizard root # depmod -a > depmod: *** Unresolved symbols in > /lib/modules/2.4.20-gentoo-r2/kernel/drivers/atm/atmtcp.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.20-gentoo-r2/kernel/drivers/block/loop.o > <SNIP> > depmod: *** Unresolved symbols in > /lib/modules/2.4.20-gentoo-r2/kernel/net/sched/sch_teql.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.20-gentoo-r2/kernel/net/sunrpc/sunrpc.o > Wizard root # > > There are about 50 failures like this. > > Here's the basic series of events as best I remember them them: > > 0) I tried running genkernel, but it started compiling without giving me > a chance to configure, so I Ctrl-C'ed out of it. > > 1) I needed USB support which was not built into my kernel. > > 2) I ran make xconfig to get USB turned on, but there were a lot of > things I wasn't sure about, and I had a working Redhat machine running a > 2.4.21 kernel, so I copied over that .config file into /usr/src/linux. > (Could this cause this sort of problem?) > > 3) I built the kernel using > > make dep clean bzImage install modules modules_install After changes of this magnitude, coupled with the aborted compile, you really should backup your .config (VERY important!), then run a 'make mrproper', copy the .config back and run either 'make oldconfig/menuconfig/xconfig' then your usual 'make dep clean .....'. 'make mrproper' puts the source tree back into a state as close to untouched as possible. > This morning I tried moving the existing lib/modules/gentoo* directory > out of the way and ran make modules_install again, and still get the > same depmod -a failures after a reboot. There is no need to move existing modules out of the way before module_install'ing, the make does that itself. > I notice that I have other gentoo-sources installed, but /usr/src/linux > is still pointing at 2.4.20-r2. Does this matter? Should I repoint to > 2.4.20-r6 and build from there? Why would this matter? You shouldn't *have* to, as to find the current running kernel, source tree and module location you can use 'uname -r'. But I'm pretty sure there are things in the portage tree which check for the symlink, so it's best to keep it current. > Can anyone venture a guess as to what I did wrong here? I ventured! Bet I didn't succeed tho :) - -- Mike Williams -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/WnDRInuLMrk7bIwRApfaAJ9Ug3blNS2VGbvw4AtM0+0UpJO8twCfXH96 VaobrmxDeqfMyy8NLYWX0aQ= =P4Zz -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
