[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#571035: [squeeze alpha1] installationsreport: grub2: machine doesn't boot



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!

> 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.

Otavio, perhaps the default value of
base-installer/initramfs-tools/driver-policy should be 'dep' on small
machines (say, less than 120MB RAM)?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: