Hi Matthew, On Tue, Sep 24, 2002 at 01:05:12PM +1000, Matthew Hannigan wrote: > > > On Tue, Sep 24, 2002 at 11:35:57AM +1000, Campbell McLeay wrote: > > Hi, > > > > I am having trouble booting a newly compiled kernel - > > (the old 2.2.19 kernel boots fine though) > > What version is the new kernel?
I tried 2.4.6 (it just hangs at 'freeing kernel memory') and 2.4.19 (that gives the libc error) It is currently running 2.2.19 kernel. I upgraded a machine with almost identical hardware running the same 2.2.19 kernel and it upgraded to the 2.4.19 kernel fine. I used identical compile options on both. They are both running the same version of glibc The only difference between the machines is that the PCI cards are differently laid out and the one that is having problems has one extra. I am not sure whether it is using a shared PCI interrupt - I can't see anything in the BIOS. I will try compiling the kernel with PCI access set to 'direct' rather than any. The problem is it is a production machine so I can't just reboot it at a whim.... Cheers, Campbell > > > it either hangs at > > > > 'VFS: Mounted root (ext2 filesystem) > > readonly. Freeing kernel memory (200k)' > > > > or > > > > init: error in loading shared libraries > > /lib/libc.so.6 Undefined symbol: > > __io_file_setbuf, version GLIBC_2.1 > > kernel panic: attempted to kill init' > > The second error message hints at kernel-libc > incompability. > > You can only jump so many kernel versions > without also upgrading libc. > > Regards, > > Matt -- ------o------ Campbell McLeay Systems Administrator Connect Infobahn Australia -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
