Slackware 12.0 on 64 MB
in [Slackware]
|
Prev: Web Cam
Next: sound problem in 12.1
From: Arun Dev on 31 Jan 2008 11:43 Hi all I just tried my luck on an old P-II, 233 MHz, 64 MB laptop. Booting huge.s I could finish the installation. But I can't start the installation. It gives no file system could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) Am I correct in assuming that the initrd is too big for the 64 MB? The root device is accoding to lilo.conf /dev/hda2 Kernel was 2.6.22 "generic". Arun
From: Douglas Mayne on 31 Jan 2008 12:17 On Wed, 30 Jan 2008 17:43:44 +0100, Arun Dev wrote: > Hi all > > I just tried my luck on an old P-II, 233 MHz, 64 MB laptop. > > Booting huge.s I could finish the installation. But I can't start > the installation. It gives > > no file system could mount root, tried: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,2) > > Am I correct in assuming that the initrd is too big for the 64 MB? > > The root device is accoding to lilo.conf /dev/hda2 > > Kernel was 2.6.22 "generic". > > Arun > Caveat: I do not know the specific system requiremens for Slackware 12.0. My guess is that 64M is enough to be able to /*run*/ Slack 12 (probably via command line only). However, the Slackware /*setup*/ environment may require more memory than that. If you could get around that catch-22, then you could use that computer with Slack 12. I have used various methods to setup Slack 12, including cloning a preset image with the baseline set of packages. If you elect to go this route, be aware that Slackware's recent kernels require an initrd and that can be a stumbling block when setting up using a non-traditional method. It might just be the easiest course to break down and use the "screw driver" method. You could swapout the disk to a computer with the resources necessary, then swap it back into the older computer when done. -- Douglas Mayne
From: Olive on 31 Jan 2008 12:18 Arun Dev wrote: > Hi all > > I just tried my luck on an old P-II, 233 MHz, 64 MB laptop. > > Booting huge.s I could finish the installation. But I can't start > the installation. It gives > > no file system could mount root, tried: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,2) > > Am I correct in assuming that the initrd is too big for the 64 MB? No the initrd is quite small and you won't have this kind of message if it were the case. The problem is (most probably); you do not include the right modules for your root filesystem or do not have specified it correctly. See man mkinitrd. If you use ext3 on /dev/hda2 you should generate a good initrd by mkinitrd -c -r /dev/hda2 -f ext3 -m ext3 -o initrd.img (boot first with the huge kernel and make the initrd once the system is booted; then you can boot with another kernel). Olive
From: Olive on 31 Jan 2008 12:19 Arun Dev wrote: > Hi all > > I just tried my luck on an old P-II, 233 MHz, 64 MB laptop. > > Booting huge.s I could finish the installation. But I can't start > the installation. It gives > > no file system could mount root, tried: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,2) > > Am I correct in assuming that the initrd is too big for the 64 MB? No the initrd is quite small and you won't have this kind of message if it were the case. The problem is (most probably); you do not include the right modules for your root filesystem or do not have specified it correctly. See man mkinitrd. If you use ext3 on /dev/hda2 you should generate a good initrd by mkinitrd -c -r /dev/hda2 -f ext3 -m ext3 -o initrd.img (boot first with the huge kernel and make the initrd once the system is booted; then you can boot with another kernel). Olive
From: Helmut Hullen on 31 Jan 2008 12:36
Hallo, Arun, Du meintest am 30.01.08: > I just tried my luck on an old P-II, 233 MHz, 64 MB laptop. > Booting huge.s I could finish the installation. But I can't start > the installation. It gives > no file system could mount root, tried: > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(8,2) May not help you: I find this message on 1 of my machines with many kernels (Compaq 500, 498 MB RAM), I don't find it on my (many) other machines. Some kernels have no problems - I haven't found why. I'd found this message under Slackware 11.x too. Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me". |