On Mon, 10 May 2004 07:26 pm, Adam Felix Bogacki wrote: > Thanks. I've been googling by the last line of the error message > > "Kernel panic: VFS: Unable to mount root fs on unknown-block (3,69)" > ===snip===
> > Another fix is based on the fact that if vmlinuz is not pointing to the > new kernel, > it is a waste of time. This can be fixed by using a live CD Knoppix > variant, booting, and mounting /usr/ and /var by hand to proper mount > points. I can boot from the rescue floppy using a 2.4* kernel, but cannot > access the net > *** how can Paradise static cable be configured here ? *** which might > allow me to > change '/etc/apt/sources.list' to 'testing' and 'dist-upgrade'. Well this is easy. (since I use to live in NZ and had a cable modem) Grab your ip and default gateway. Load the module that is your ethernet card. eg modprobe 8139too # this is a common module yours maybe different. Check lspci and try and figure out what driver is most suitable. other common 10/100 drivers are eepro100, tulip, 3c59x then once you can see eth0 (ifconfig -a), configure it and add the route. eg. ifconfig eth0 203.27.31.54 route add default 203.27.31.1 (IP addresses are examples only, yours will be different). then you should be able to ping kirsty and racheal (Paradises DNS servers) 203.96.152.12 203.96.152.4 > > I have tried > > mount /dev/hdb6 /mnt/hdb5/usr > mount /dev/hdb8 /mnt/hdb5/var > does /mnt/hdb5/usr exist, it needs to be a directory. why don't you mount root at /mnt eg mount /dev/hdb5 /mnt mount /dev/hdb6 /mnt/usr mount /dev/hdb8 /mnt/var mount /dev/hdb1 /boot (I am guessing here, replace 1 with what ever it should be) chroot /mnt now you are in your virtual root. > but keep getting the message that it is not a proper mount point. > > One is then supposed to > > chroot /mnt/hdb5 (whatever is correct), edit lilo.conf, and then run lilo. > > Another fix is to append > > root=/dev/hdb5/3,69 or /(3,69), or just /3 or > root=/dev/345/3 (?) > > but I'm not sure which option (if any) is correct here. > > The /boot partition is about 80% full at the moment and I don't think > that sizing is a factor right now. I don't know about this. I have not had any problems moving from 2.4 to 2.6. I think I ran into some little problems, but most things have gone pretty smooth. > > My notes show that within /boot > 'initrd.img-2.6.5-1-686' has gone from 4571136 to 4009984, > in other words it has decreased in size from my first (successful) > install of 'kernel-image-2.6.5-1-686' to after I did a dist-upgrade. > That's a change of 561152. I may have a partly installed package here. This could be correct. Less may have been built directly into the kernel, and instead built as modules. > > I have tried to move and resize /boot (within 1024 blocks), but Parted > keeps giving me a message along the lines that it is possible but may cause > trouble > in certain circumstances. I don't know how seriously to take this with > unstable. I don't know about moving and resizing partitions like that. I have used LVM and other OS, but not parted, so not much help. Good luck, Sorry I can't be of more help. Greg. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
