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

Bug#336519: marked as done (initramfs-tools: kernel does not recognize initramfs image)

Your message dated Mon, 13 Feb 2006 11:16:58 +0100
with message-id <20060213101658.GA14875@nancy>
and subject line Bug#336519: initramfs-tools: works with newer initramfs and kernel
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: initramfs-tools
Version: 0.37
Severity: important

when attempting to boot using an initramfs image generated by
initramfs-tools, i get:

Linux version 2.6.14-1-386 (Debian 2.6.14-1) (horms@debian.org) (gcc version 4.0.3 20051023 (prerelease) (Debian 4.0.2-3)) #1 Fri Oct 28 16:43:46 JST 2005
...snip...
Checking for popad bug... OK.
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd
Freeing initrd memory: 4678k freed
softlockup thread 0 started up.
...snip...
Using IPI Shortcut mode
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "nfs" or unknown-block(0,255)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,255)

the file /boot/initrd-img-2.6.14-1-386 appears to be a gzipped cpio
archive.

it's being loaded in a qemu environment, with:

qemu -m 64 -hda /dev/zero -user-net -nographic -kernel /home/vagrant/nobackup/sid-chroot/opt/ltsp/i386/boot/vmlinuz-2.6.14-1-386 -initrd /home/vagrant/nobackup/sid-chroot/opt/ltsp/i386/boot/initrd.img-2.6.14-1-386 -append "console=ttyS0 root=/dev/nfs"

in /etc/mkinitramfs/initramfs.conf:

BOOT=nfs

attached should be a full boot log.

live well,
  vagrant

Linux version 2.6.14-1-386 (Debian 2.6.14-1) (horms@debian.org) (gcc version 4.0.3 20051023 (prerelease) (Debian 4.0.2-3)) #1 Fri Oct 28 16:43:46 JST 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 0000000000100000 - 0000000004000000 (usable)
64MB LOWMEM available.
DMI not present.
ACPI: Unable to locate RSDP
Allocating PCI resources starting at 10000000 (gap: 04000000:fc000000)
Built 1 zonelists
Kernel command line: console=ttyS0 root=/dev/nfs
Local APIC disabled by BIOS -- you can enable it with "lapic"
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Detected 1397.780 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 57160k/65536k available (1636k kernel code, 7960k reserved, 553k data, 236k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2807.99 BogoMIPS (lpj=1403995)
Security Framework v1.0.0 initialized
SELinux:  Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 8K
CPU: L2 cache: 128K
mtrr: v2.0 (20020519)
CPU: Intel Pentium II (Klamath) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 4678k freed
softlockup thread 0 started up.
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xf9b60, last bus=0
PCI: Using configuration type 1
ACPI: Subsystem revision 20050902
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: PnP BIOS support was not detected.
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX/ICH [8086/7000] at 0000:00:01.0
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
audit: initializing netlink socket (disabled)
audit(1130706836.210:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
EISA: Probing bus 0 at eisa.0
EISA: Detected 0 cards.
NET: Registered protocol family 2
input: AT Translated Set 2 keyboard on isa0060/serio0
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI Shortcut mode
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Cannot open root device "nfs" or unknown-block(0,255)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,255)

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Fri, 10 Feb 2006, Vagrant Cascadian wrote:

> 
> i tested the following combination of initramfs-tools and linux-image,
> and they appear to work together just fine.
> 
> ii  initramfs-tools          0.51      tools for generating an initramfs
> ii  linux-image-2.6-486      2.6.15-5  Linux kernel 2.6 image on 486-class machines
> ii  linux-image-2.6.15-1-486 2.6.15-5  Linux kernel 2.6.15 image on 486-class machines
> 
> hurrah!
> 
> live well,
>   vagrant

thanks a lot for your tests :)

closing.

-- 
maks

ps still need to send aboves nice dannf patch upstream.

--- End Message ---
Reply to: