Bug#465461: linux-image-2.6.24-1-686: linux-image-2.6.24-1.686 don't boot on Dell Inspiron 8500

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: root <jlrossiny@gmail.com>
To: Debian Bug Tracking System <465461@bugs.debian.org>
Subject: linux-image-2.6.24-1-686: linux-image-2.6.24-1.686 don't boot on
Dell
Inspiron 8500
Message-ID: <20080401083743.3210.3926.reportbug@Jupiter>
X-Mailer: reportbug 3.39
Date: Tue, 01 Apr 2008 10:37:43 +0200
X-Debbugs-Cc: [email]jlrossiny@gmail.com[/email]

Package: linux-image-2.6.24-1-686
Followup-For: Bug #465461



-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.24-1-686 depends on:
ii debconf [debconf-2.0] 1.5.20 Debian configuration management sy
ii initramfs-tools [linux-initr 0.91e tools for generating an initramfs
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.24-1-686 recommends:
ii libc6-i686 2.7-6 GNU C Library: Shared libraries [i

-- debconf information:
linux-image-2.6.24-1-686/preinst/overwriting-modules-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/bootloader-error-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/create-kimage-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/prerm/would-invalidate-boot-loader-2.6.24-1-686:
true
linux-image-2.6.24-1-686/preinst/initrd-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.24-1-686/preinst/abort-install-2.6.24-1-686:
linux-image-2.6.24-1-686/prerm/removing-running-kernel-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/abort-overwrite-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/bootloader-test-error-2.6.24-1-686:
linux-image-2.6.24-1-686/preinst/lilo-initrd-2.6.24-1-686: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.24-1-686/postinst/old-system-map-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/preinst/failed-to-move-modules-2.6.24-1-686:
linux-image-2.6.24-1-686/postinst/depmod-error-initrd-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/bootloader-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/old-dir-initrd-link-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/depmod-error-2.6.24-1-686: false
linux-image-2.6.24-1-686/preinst/elilo-initrd-2.6.24-1-686: true
linux-image-2.6.24-1-686/postinst/kimage-is-a-directory:


The last message was : Waiting for root file system.

The Linux-image boot until version Linux-image-2.6.23-2-686.

The version Linux-image-2.6.23-3-686 didn't boot with the same message as
the present version.

On Tue, Apr 01, 2008 at 10:49:00AM +0200, Jean-Luc Rossiny wrote:[color=blue]
> The last message was : Waiting for root file system.[/color]

use roodelay=7 as described and paste the real error.
[color=blue]
> The Linux-image boot until version Linux-image-2.6.23-2-686.
>
> The version Linux-image-2.6.23-3-686 didn't boot with the same message as
> the present version.[/color]

currently your report is pretty useless.
but the best assumption is that your root device name changed
from /dev/hdaX to /dev/sdaX or so
maybe you also just added some external usb disc that reoders the
devices.

and no that is not a bug, the kernel *never* guaranteed strict
device ordering. so use UUID in your bootloader config and fstab
and be happy.



--
To UNSUBSCRIBE, email to [email]debian-bugs-dist-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Hi

Do you know why the computer keep on booting on linux-image 2 6 18 4 686
with the same parameters : /dev/hda3 ro

Thanks and regards

Jean-Luc

2008/4/1, maximilian attems <max@stro.at>:[color=blue]
>
> On Tue, Apr 01, 2008 at 10:49:00AM +0200, Jean-Luc Rossiny wrote:[color=green]
> > The last message was : Waiting for root file system.[/color]
>
> use roodelay=7 as described and paste the real error.
>[color=green]
> > The Linux-image boot until version Linux-image-2.6.23-2-686.
> >
> > The version Linux-image-2.6.23-3-686 didn't boot with the same message[/color]
> as[color=green]
> > the present version.[/color]
>
> currently your report is pretty useless.
> but the best assumption is that your root device name changed
> from /dev/hdaX to /dev/sdaX or so
> maybe you also just added some external usb disc that reoders the
> devices.
>
> and no that is not a bug, the kernel *never* guaranteed strict
> device ordering. so use UUID in your bootloader config and fstab
> and be happy.
>[/color]

Hi,

I try rootdelay=7

Th system can't find /dev/hda3

and with UUID

The system can't find the disk

I entered in initramfs?

Regards

Jean-Luc Rossiny

2008/4/1, maximilian attems <max@stro.at>:[color=blue]
>
> On Tue, Apr 01, 2008 at 10:49:00AM +0200, Jean-Luc Rossiny wrote:[color=green]
> > The last message was : Waiting for root file system.[/color]
>
> use roodelay=7 as described and paste the real error.
>[color=green]
> > The Linux-image boot until version Linux-image-2.6.23-2-686.
> >
> > The version Linux-image-2.6.23-3-686 didn't boot with the same message[/color]
> as[color=green]
> > the present version.[/color]
>
> currently your report is pretty useless.
> but the best assumption is that your root device name changed
> from /dev/hdaX to /dev/sdaX or so
> maybe you also just added some external usb disc that reoders the
> devices.
>
> and no that is not a bug, the kernel *never* guaranteed strict
> device ordering. so use UUID in your bootloader config and fstab
> and be happy.
>[/color]