John wrote:
These are the 2.4 files: 2450662 Jul 7 02:33 initrd.gz 1208 Jul 7 02:33 initrd.list 3686400 Jul 7 02:33 mini.iso 811877 Jul 7 02:33 vmlinuz
This produces numerous modprobe messages that it can't find /lib/modules/2.4.26-1-386/modules.dep and then stops.
The corresponding 2.6 kernel doesn't produce those messages: instead it locks up:
There's a VFS message it's mounted the root (ext2 filesystem) Then a VFS message it can't open root device "<NULL>" or unknown-block(8,3)
and a panic, VFS: unable to mount root fs on unknown-block(8,3)
I'm PXE-booting. Here's the stanza, the same in each case: label 4 kernel images/sarge/vmlinuz append initrd=images/sarge/net-initrd.gz vga=6
I doubt that it's loading the whole initrd in either case. Pass initrd_size=10000 or so.
10000 didn't work with either, so I tried 20000 with 2.6. No change.
I'm off to bed. If anyone thinks it worth while, I'll do a packet sniff or other checking in the morning to see how much it's downloading. There's nothing in syslog to suggest a problem.
ps I did an md5sum check to verify I'm using the daily kernel/initrd I've been claiming.
I was but .....
Jul 7 14:40:53 ns in.tftpd[12865]: RRQ from 192.168.9.133 filename /PXE/images/sarge/vmlinuz
Jul 7 14:40:54 ns in.tftpd[12866]: RRQ from 192.168.9.133 filename /PXE/images/sarge/net-initrd.gz
This is better:
Jul 7 14:47:18 ns in.tftpd[12889]: RRQ from 192.168.9.133 filename /PXE/images/sarge/vmlinuz
Jul 7 14:47:19 ns in.tftpd[12890]: RRQ from 192.168.9.133 filename /PXE/images/sarge/initrd.gz
I don't have the foggiest idea of what problems that caused: quite possibly all of them including the excessive downloads.
It's asking me if I speak English now. I'll finish it off in the morning. After I've had a further look at firewall rules.
Thanks all for your trouble.
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
