© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Message-ID: <email address hidden>
Date: Mon, 17 Jan 2005 13:29:52 +0900
From: Horms <email address hidden>
To: Olivier Lecarme <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#290474: kernel-
disk
reassign 290474 initrd-tools
thanks
On Fri, Jan 14, 2005 at 11:37:46AM +0100, Olivier Lecarme wrote:
> Package: kernel-
> Version: 2.6.10-3
> Severity: critical
> Justification: breaks the whole system
>
>
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.27-2-686
> Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=
>
> Versions of packages kernel-
> ii coreutils [fileutils] 5.2.1-2 The GNU core utilities
> ii initrd-tools 0.1.76 tools to create initrd image for p
> ii module-init-tools 3.1-rel-2 tools for managing Linux kernel mo
>
> -- no debconf information
> I have a Dell Optiplex computer with a SATA hard drive. Kernel 2.4 works
> OK with the disk in non-SATA mode. Kernel 2.6 panics on booting with
> the message /dev/console not found, preceded by a message from pivot_root
> which does not found the root partition.
> I tried both SATA modes in the BIOS: combination, or normal.
> I tried root=/dev/hda5 or root=/dev/sda5 in the Grub menu.lst file.
> I tried to omit initrd in this file.
This almost certainly won't work, as the kernel-image doesn't
have enough drivers to boot more or less any system. These are
provided by the initrd image.
I would suspect that the prblem is that mkinitrd is not adding
the drivers that are needed for your system to the initrd image.
With this in mind I am reassigning the bug to initrd-tools.
Do you have any idea what modules are required for your system.
Do you have a working 2.6 debian kernel image. If so could
you provide the output of lsmod. Ditto for 2.4, though that is probably
less useful.
--
Horms