--- Begin Message ---
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-3
Severity: important
Hi,
the kernel in unstable doesn't boot for some reason. The last message it
prints is "Begin: Waiting for root filesystem... ...". I do think that
this has something to do with the initramfs. According to google the
initramfs is too large to be loaded, or something.
I've already tried to downgrade the initramfs-tools to the old
etch-version, but that didn't change a thing.
I've also tried to rebuild a smaller initramfs by changing
"MODULES=most" to "MODULES=dep" in /etc/initramfs-tools/initramfs.conf
running "update-initramfs -k 2.6.25-2-amd64 -u -v". But the bootprocess
still hung.
Please tell me, if you have any ideas what the problem is, or what I
could do, to get additional informations.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.18-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.25-2-amd64 recommends no packages.
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false
linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true
linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64:
linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true
--- End Message ---
--- Begin Message ---
On Sun, 25 May 2008, Jesus Christus wrote:
> maximilian attems wrote:
>> On Sun, May 25, 2008 at 12:39:16AM +0200, Jesus Christus wrote:
>>
>>> Package: linux-image-2.6.25-2-amd64
>>> Version: 2.6.25-3
>>> Severity: important
>>>
>>>
>>> Hi,
>>> the kernel in unstable doesn't boot for some reason. The last message
>>> it prints is "Begin: Waiting for root filesystem... ...". I do think
>>> that this has something to do with the initramfs. According to google
>>> the initramfs is too large to be loaded, or something.
>>>
>>> I've already tried to downgrade the initramfs-tools to the old
>>> etch-version, but that didn't change a thing. I've also tried to
>>> rebuild a smaller initramfs by changing "MODULES=most" to
>>> "MODULES=dep" in /etc/initramfs-tools/initramfs.conf running
>>> "update-initramfs -k 2.6.25-2-amd64 -u -v". But the bootprocess
>>> still hung.
>>>
>>> Please tell me, if you have any ideas what the problem is, or what I
>>> could do, to get additional informations.
>>>
>>
>> checkout http://wiki.debian.org/InitramfsDebug
>> and give info according to those points.
>>
>> thanks
>>
>>
> I have managed to get the new kernel running. The problem has been, that
> for some reason all hda* devices become sda* devices, when I'm using the
> recent kernel.
> When I change every hda entry in the boot patameters and /etc/fstab to
> sda, the system runs fine. Additionally I made a "sudo dpkg-reconfigure
> uswsusp" to get rid of a error message.
>
> However, I think that there still is a problem, because I have got an
> IDE disk which is labeled as if it were SCSI, and thats at least unusual.
>
> According to lsmod the IDE modules have been loaded:
>
> squish@Blub:~$ lsmod | grep ide
> ide_pci_generic 9476 0 [permanent]
> ide_core 138160 2 ide_pci_generic,sis5513
>
>
> And I haven't found anything of interest in the output of dmesg, but
> maybe I'm just clueless:
>
> [ 2.029502] pata_sis 0000:00:02.5: version 0.5.2
> [ 2.029502] scsi0 : pata_sis
> [ 2.029502] scsi1 : pata_sis
> [ 2.029502] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0
> irq 14
> [ 2.029502] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xffa8
> irq 15
> [ 2.029503] udev: renamed network interface eth0 to eth2
> [ 2.181536] usb 1-1: device not accepting address 2, error -62
> [ 2.193639] ata1.00: ATA-6: ST9120821A, 3.06, max UDMA/100
> [ 2.193639] ata1.00: 234441648 sectors, multi 16: LBA48
> [ 2.209703] ata1.00: configured for UDMA/100
> [ 2.237704] hub 1-0:1.0: unable to enumerate USB device on port 1
> [ 2.529730] firewire_core: created device fw0: GUID 00e018000371f17c,
> S400
> [ 2.545733] ata2.00: ATAPI: TSSTcorpCD/DVDW TS-L632D, AS05, max UDMA/33
> [ 2.549300] hub 4-0:1.0: unable to enumerate USB device on port 1
> [ 2.733758] ata2.00: configured for UDMA/33
> [ 2.733758] scsi 0:0:0:0: Direct-Access ATA ST9120821A
> 3.06 PQ: 0 ANSI: 5
> [ 2.742947] scsi 1:0:0:0: CD-ROM TSSTcorp CD/DVDW TS-L632D
> AS05 PQ: 0 ANSI: 5
> [ 2.746947] Uniform Multi-Platform E-IDE driver
> [ 2.746947] ide: Assuming 33MHz system bus speed for PIO modes;
> override with idebus=xx
> [ 2.770948] Driver 'sd' needs updating - please use bus_type methods
> [ 2.770948] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors
> (120034 MB)
> [ 2.770948] sd 0:0:0:0: [sda] Write Protect is off
> [ 2.770948] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 2.770948] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 2.770948] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors
> (120034 MB)
> [ 2.770948] sd 0:0:0:0: [sda] Write Protect is off
> [ 2.770948] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 2.770948] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [ 2.770948] sda: sda1 sda2 sda3 <<4>Driver 'sr' needs updating -
> please use bus_type methods
> [ 2.812814] sda5 sda6 sda7 sda8 >
> [ 2.856906] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 2.860906] usb 1-1: new low speed USB device using ohci_hcd and
> address 4
> [ 2.898296] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw
> xa/form2 cdda tray
> [ 2.898296] Uniform CD-ROM driver Revision: 3.20
> [ 2.898296] sr 1:0:0:0: Attached scsi CD-ROM sr0
> [ 2.904512] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 2.904512] sr 1:0:0:0: Attached scsi generic sg1 type 5
> [ 3.101328] usb 1-1: configuration #1 chosen from 1 choice
as suspected, kernel does not guarantee stable device names.
userspace policy for stable device names use UUID.
--
maks
--- End Message ---