Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

2.6.29 custom kernel

2 views
Skip to first unread message

Raffaele Morelli

unread,
May 19, 2009, 10:40:12 AM5/19/09
to
Hi you all,

I am experiencing serious troubles in compiling kernel 2.6.29 backport to lenny

Compiling with make-kpkg goes well and ends up with the linux-image deb file, I create initrd.img using

update-initramfs -c 2.6.29

but at boot I got these messages

kinit: No resume image, doing normal boot
mount: Mounting /dev/hda1 on /root failed: Device or resource busy
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: no such file or directory
Target filesystem doesn't have /sbin/init

if I get a grub shell I can't see /dev/sda1 and passing kernel and initrd options (correct ones, vmlinuz-2.6.29 and initrd.img-2.6.29) ends up in a

Failure: failed to load module dm-emc
...
...
mount: cannot read /etc/fstab: No such file or directory
....
No init found. Try passing init= bootarg


Can someone help?

debian testing here
the box is a sony vaio VGN-AW21Z... owned by my company, so help would be very appreciated.

regards
-r

Chris Bannister

unread,
May 23, 2009, 4:50:16 AM5/23/09
to
On Tue, May 19, 2009 at 04:12:19PM +0200, Raffaele Morelli wrote:
> kinit: No resume image, doing normal boot
> mount: Mounting /dev/hda1 on /root failed: Device or resource busy
^^^^^^^^^

> mount: Mounting /root/dev on /dev/.static/dev failed: No such file or
> directory
> mount: Mounting /sys on /root/sys failed: No such file or directory
> mount: Mounting /proc on /root/proc failed: no such file or directory
> Target filesystem doesn't have /sbin/init
>
> if I get a grub shell I can't see /dev/sda1 and passing kernel and initrd

^^^^^^^^^

So what should it be? (/dev/hda1 or /dev/sda1)

> Can someone help?
>
> debian testing here

And you are compiling a lenny backport on a testing box?

> the box is a sony vaio VGN-AW21Z... owned by my company, so help would be
> very appreciated.

You probably need to give some more detailed information.
Example:

What was the exact command you gave to kernel-package?

Did you run update-grub?

What is the contents of "/boot/grub/menu.lst


Sorry I can't be of any more help.

--
Chris.
======
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will understand why I dismiss yours.
-- Stephen F Roberts


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Raffaele Morelli

unread,
May 25, 2009, 5:00:24 AM5/25/09
to


2009/5/23 Chris Bannister <mocki...@earthlight.co.nz>

On Tue, May 19, 2009 at 04:12:19PM +0200, Raffaele Morelli wrote:
> kinit: No resume image, doing normal boot
> mount: Mounting /dev/hda1 on /root failed: Device or resource busy
                 ^^^^^^^^^

> mount: Mounting /root/dev on /dev/.static/dev failed: No such file or
> directory
> mount: Mounting /sys on /root/sys failed: No such file or directory
> mount: Mounting /proc on /root/proc failed: no such file or directory
> Target filesystem doesn't have /sbin/init
>
> if I get a grub shell I can't see /dev/sda1 and passing kernel and initrd
                                   ^^^^^^^^^

So what should it be?  (/dev/hda1 or /dev/sda1)

> Can someone help?
>
> debian testing here

And you are compiling a lenny backport on a testing box?

Yes, because I always prefer debian patched deb or src, 2.6.29 is a recent kernel.
 


> the box is a sony vaio VGN-AW21Z... owned by my company, so help would be
> very appreciated.

You probably need to give some more detailed information.
Example:

       What was the exact command you gave to kernel-package?

       Did you run update-grub?

       What is the contents of "/boot/grub/menu.lst


Sorry I can't be of any more help.

--
Chris.

I solved running a debian dvd in rescue mode and coping the /etc/mtab file into the /etc/fstab. I guess it was a kernel config option which enables the now "deprecated sysfs layout for older userspace tools".

My kernel-package conf files are ok, I usually compile custom kernels every time a new RT patch is released.

cheers
-r
0 new messages