Bug#571035: [squeeze alpha1] installationsreport: grub2: machine doesn't boot
Hello,
Ben Hutchings <ben@decadent.org.uk> wrote:
> On Sat, 2010-09-11 at 23:18 +0200, Holger Wansing wrote:
> [...]
> > Summary: I have a kernel, but no initrd. And with this constellation,
> > the kernel boots, until he comes to the point where the root filesystem
> > is to be found, what fails:
> > "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
> > But this is not a problem in this case, important is, that the kernel itself
> > boots, right?
>
> Yes, though that is not that much of a test!
I'm unsure if I understand what you mean here.
> > So, maybe there is a problem with the initrd?
> > Maybe with the size of it? (remember that this is a lowmem machine)
>
> I think you are right. A typical initramfs would use nearly the whole
> of your 32MB RAM. It is possible to build a smaller initramfs
> containing only the drivers needed for the current hardware, but this is
> not the default because it can fail if you change hardware. If you run
> the installer with the extra parameter 'priority=medium' you will be
> given this option.
Ok, I will try a new installation and choose the customized initrd.
> Otavio, perhaps the default value of
> base-installer/initramfs-tools/driver-policy should be 'dep' on small
> machines (say, less than 120MB RAM)?
Or at least add a hint on that screen, that it is recommended to not
choose the full initrd on lowmem systems?
Holger
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Reply to: