[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] request for k12ltsp kernel .config file....was linuxprogress patch



My appologies on the kernel...
Glad to have you helping...

In order to cut down on confusion, I moved my /usr/src/linux-2.4.18-ltsp to /usr/src/linux-2.4.18
and told buildk to use that as the source directory.

then, I copied the original bzImage to /tftpboot/lts/pxe/vmlinuz-2.4.18
and the new initrd to the same place(initrd-2.4.18)
same error, so...

so I changed the debug line.

I went to /lib/modules/2.4.18
and there was a modules.dep file there
the contents match what was in my previous modules.dep file from the initrd I copied to my root /lib/modules/2.4.18 directory, so I can copy and paste it here:

does it matter that some entries start right after the : ?
should this be one per line, or is it o.k. this way?

I still don't understand why it can't find the modules.dep file, when it is clearly there...
this also looks to be missing a bunch of the modules the error messages are trying to find...
I will take some snapshots of the errors I'm getting on the clients tommorrow, and post them on a web page
so we can try to figure this out...

#####################modules.dep file################################################
/lib/modules/2.4.18/kernel/drivers/net/3c503.o:	/lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/3c505.o:

/lib/modules/2.4.18/kernel/drivers/net/3c507.o:

/lib/modules/2.4.18/kernel/drivers/net/3c509.o:

/lib/modules/2.4.18/kernel/drivers/net/3c515.o:

/lib/modules/2.4.18/kernel/drivers/net/3c59x.o:

/lib/modules/2.4.18/kernel/drivers/net/8139cp.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/8139too.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/8390.o:

/lib/modules/2.4.18/kernel/drivers/net/acenic.o:

/lib/modules/2.4.18/kernel/drivers/net/at1700.o:

/lib/modules/2.4.18/kernel/drivers/net/cs89x0.o:

/lib/modules/2.4.18/kernel/drivers/net/de4x5.o:

/lib/modules/2.4.18/kernel/drivers/net/depca.o:

/lib/modules/2.4.18/kernel/drivers/net/dl2k.o:

/lib/modules/2.4.18/kernel/drivers/net/dmfe.o:

/lib/modules/2.4.18/kernel/drivers/net/e2100.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/eepro.o:

/lib/modules/2.4.18/kernel/drivers/net/eepro100.o:

/lib/modules/2.4.18/kernel/drivers/net/eexpress.o:

/lib/modules/2.4.18/kernel/drivers/net/epic100.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/eth16i.o:

/lib/modules/2.4.18/kernel/drivers/net/ewrk3.o:

/lib/modules/2.4.18/kernel/drivers/net/hamachi.o:

/lib/modules/2.4.18/kernel/drivers/net/hp-plus.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/hp.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/hp100.o:

/lib/modules/2.4.18/kernel/drivers/net/lance.o:

/lib/modules/2.4.18/kernel/drivers/net/lp486e.o:

/lib/modules/2.4.18/kernel/drivers/net/mii.o:

/lib/modules/2.4.18/kernel/drivers/net/natsemi.o:

/lib/modules/2.4.18/kernel/drivers/net/ne.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/ne2k-pci.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/ns83820.o:

/lib/modules/2.4.18/kernel/drivers/net/pcnet32.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/sis900.o:

/lib/modules/2.4.18/kernel/drivers/net/sk98lin/sk98lin.o:

/lib/modules/2.4.18/kernel/drivers/net/smc-ultra.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/smc9194.o:

/lib/modules/2.4.18/kernel/drivers/net/tlan.o:

/lib/modules/2.4.18/kernel/drivers/net/tulip/tulip.o:

/lib/modules/2.4.18/kernel/drivers/net/via-rhine.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/wd.o: /lib/modules/2.4.18/kernel/drivers/net/8390.o

/lib/modules/2.4.18/kernel/drivers/net/winbond-840.o: /lib/modules/2.4.18/kernel/drivers/net/mii.o

/lib/modules/2.4.18/kernel/drivers/net/yellowfin.o:




jam McQuil com wrote:


On Tue, 12 Nov 2002, Barry Smoke wrote:



here's what's happening for us.....

setting up loopback device
modprobe: Can't open Dependencies file /lib/modules/2.4.18/modules.dep (no such file or directory)


then all hell breaks out from there ...

so, I went back to the buildk script, and commented out where it unmounts the initrd.
then I went to /mnt/initrd, and looked in lib/modules/2.4.18
and there is a modules.dep file there...
Just for fun, I copied that modules.dep file to the root filesystem(/lib/modules/2.4.18/)
but no change, still the above error.


So, since the modules.dep file is there, but the kernel can't find it...
what is going on?

here my pxelinux.cfg/default file:

label linux
kernel vmlinuz-2.4.18-ltsp-nolpp
append root=/dev/ram0 rw init=/linuxrc initrd=initrd-2.4.18-ltsp-nolpp



When you build your kernel, have you modified your Makefile to have '-ltsp-nolpp' in the EXTRAVERSIONS ?

if so, then your modules should be in "/lib/modules/2.4.18-ltsp-nolpp"



and the client lists that kernel as the one booting.....
the 3c59x module loads previously to this, from /lib/modules/2.4.18, I'm guessing because it is called directly



modprobe looks in /proc/version to see the name of the current kernel. It then uses that to figure out which directory to get the modules from '/lib/modules/2.4.18.



This is very frustrating....
We don't understand why this is not working, yet the default kernel from k12ltsp works fine.
That's why I wanted the config file from the k12ltsp kernel, because we thought we might be missing something hardware wise.


I guess I need the complete steps Eric uses for his client kernels.



Eric doesn't build the kernels. I do, and i've provided you with the ltsp_initrd_kit, which includes the scripts that I use, and the .config files for my kernels.


Try adding 'INITRD_DBG=1' to your 'append' line for your kernel in the pxelinux.cfg/default file.

Then, you'll get a shell prompt as soon as the /linuxrc script
starts executing.

From there, you can poke around a bit, and see if your
modules.dep file is there.

You won't have 'ls', but you'll have 'echo', so you can do
things like this:

 cd /lib/modules/2.4.18
 echo *

and it should list any files in that directory.

I think you'll have 'cat' at that point, so you could
cat out the contents of modules.dep.

You can also do this:    cat /proc/version
to see what version of the kernel you are really running.

See what that shows you, and report back.

Jim McQuillan
jam Ltsp org



_______________________________________________
K12OSN mailing list
K12OSN redhat com
https://listman.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>








[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]