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

Bug#432817: marked as done (Harddisc changed from /dev/hda to sda from 2.6.18)

Your message dated Sun, 12 Aug 2007 23:02:55 +0200
with message-id <20070812210255.GA13135@stro.at>
and subject line Bug#432650: Sigh...
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: linux-image-2.6.21-2-k7
Version: 2.6.21-5
Severity: normal

--- Please enter the report below this line. ---

Dear Kernel-maintainers,

Today I tried to boot the new-in-testing linux-image-2.6.21-2-k7.
Before that I always booted linux-image-2.6.18-4-k7.

Unfortunately the boot process did not succeed, instead the following error message appeared:

        Begin: Mounting root file system... ...
        Begin: Running /scripts/localo-top ...
        ide0: I/O resource 0x3F6-0x3F6 not free.
        ide0: ports already in use, skipping probe
        ide1: I/O resource 0x376-0x376 not free.
        ide1: ports already in use, skipping probe
        Begin: Waiting for root file system... ...
>From this point on, the harddisc was active, but the boot process did not continue.

I found out that all I had to do was changing 'hda' into 'sda' in /etc/fstab and on the grub command line to boot this kernel.
Strangely the device names for my harddisc partitions seem to have changed from /dev/hda* to /dev/sda* during the kernel transition.
I consider this strange, because my machine has no SATA harddisc or similar (AFAICT), but only an ordinary IDE harddisc.

This is the output of lspci:

        00:00.0 Host bridge: Silicon Integrated Systems [SiS] 746 Host (rev 10)
        00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
        00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
        00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
        00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
        00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
        00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
        00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
        00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
        00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)
        00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
        01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

Problems like these should either be avoided or at least get documented somewhere.

Thanks for your effort!


--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.18-4-k7

Debian Release: lenny/sid
  500 testing         ftp2.de.debian.org 
  400 unstable        ftp2.de.debian.org 

--- Package information. ---
Depends                       (Version) | Installed
module-init-tools           (>= 0.9.13) | 3.3-pre11-1
initramfs-tools              (>= 0.55)  | 0.88
 OR yaird                (>= 0.0.12-8)  | 
 OR linux-initramfs-tool                | 

--- End Message ---
--- Begin Message ---
On Sun, 12 Aug 2007, Julien Puydt wrote:

> After reading 
> http://forums.debian.net/viewtopic.php?p=85884&sid=a6fc79f42fe51951ccc6bd77f6a74882
> which is pointed to by duplicate
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432971
> I can confirm that I'm running 2.6.22 -- and I didn't notice anything wrong 
> until now...

ok closing.

thanks for feedback.


--- End Message ---

Reply to: