Bug#638068: Re : initramfs-tools generates unbootable initrd.img on IA-64

2012-06-15 Thread maximilian attems
Sorry for the time it took.

According to your bug report klibc dash on ia64 has a working echo,
so it's basic functionality should be good.

It is not clear to me why the initramfs won't boot without busybox?
It does here very well on x86 platforms.

could you please list all the hooks that are shipped:
 ls /usr/share/initramfs-tools/hooks/

Also could you have a look at boot with the nont working initrmafs
with supplied bootargument: debug=vc and no quiet please.
It should show where in the boot process the initramfs hangs.

thank you.


-- 
maks




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#638068: Re : initramfs-tools generates unbootable initrd.img on IA-64

2012-06-15 Thread Aníbal Monsalve Salazar
On Fri, Jun 15, 2012 at 10:54:35AM +, maximilian attems wrote:
Sorry for the time it took.

According to your bug report klibc dash on ia64 has a working echo,
so it's basic functionality should be good.

It is not clear to me why the initramfs won't boot without busybox?
It does here very well on x86 platforms.

could you please list all the hooks that are shipped:
 ls /usr/share/initramfs-tools/hooks/

Also could you have a look at boot with the nont working initrmafs
with supplied bootargument: debug=vc and no quiet please.
It should show where in the boot process the initramfs hangs.

thank you.

-- 
maks

# uname -a
Linux debian 3.3.0-trunk-itanium #1 SMP Wed May 2 08:06:30 UTC 2012 ia64 
GNU/Linux

# ls /usr/share/initramfs-tools/hooks/
busybox  dmsetup  keymap  klibc  kmod  thermal  udev

The photo at the web address below shows the output without the debug=vc
kernel boot parameter.

http://people.debian.org/~anibal/p1010539.jpg

With the debug=vc kernel boot parameter there is no additional output.

Just before the load of vmlinuz (at the ELILO boot prompt), I hit the
tab key and typed LinuxOLD followed by debug=vc and it was ignored
apparently.

The prompt was:

 ELILO boot:
 Linux
 LinuxOLD
 (or a kernel file name: [[dev_name:/]path/]kernel_image cmdline options)

 ELILO boot:

The machine is Dell PowerEdge 7250. I need to find out what's the
dev_name of the EFI boot partition of the logical drive of the raid5.

I tried debug=vc in elilo.conf and the system wouldn't boot and
complained about that extra line in elilo.conf.

My elilo.conf is below.

## elilo configuration file generated by elilo 3.12-4

# install=/usr/lib/elilo/elilo.efi
# boot=/dev/sda1
# boot=/dev/disk/by-uuid/4DBC-29A7

delay=20
default=Linux

relocatable


image=/EFI/debian/vmlinuz
 label=Linux

# root = /dev/sda2
root = UUID=e662a93c-2b14-46bc-82aa-5d29cc2b4db1

 read-only
 initrd=/EFI/debian/initrd.img

image=/EFI/debian/vmlinuz.old
 label=LinuxOLD

# root = /dev/sda2
root = UUID=e662a93c-2b14-46bc-82aa-5d29cc2b4db1

 read-only
 initrd=/EFI/debian/initrd.img.old



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#638068: Re : initramfs-tools generates unbootable initrd.img on IA-64

2012-06-15 Thread Émeric Maschino
Hello,

To pass parameters to kernel, add an append= line in your elilo.conf
file, just below the initrd= line. In the present case:

 append=debug=vc

Please find attached the log that I've just recorded on a serial
console passing debug=vc to kernel.
Well, I don't see anything useful or different than without debug=vc.

 Emeric



2012/6/15 Aníbal Monsalve Salazar ani...@debian.org:
 On Fri, Jun 15, 2012 at 10:54:35AM +, maximilian attems wrote:
Sorry for the time it took.

According to your bug report klibc dash on ia64 has a working echo,
so it's basic functionality should be good.

It is not clear to me why the initramfs won't boot without busybox?
It does here very well on x86 platforms.

could you please list all the hooks that are shipped:
 ls /usr/share/initramfs-tools/hooks/

Also could you have a look at boot with the nont working initrmafs
with supplied bootargument: debug=vc and no quiet please.
It should show where in the boot process the initramfs hangs.

thank you.

--
maks

 # uname -a
 Linux debian 3.3.0-trunk-itanium #1 SMP Wed May 2 08:06:30 UTC 2012 ia64 
 GNU/Linux

 # ls /usr/share/initramfs-tools/hooks/
 busybox  dmsetup  keymap  klibc  kmod  thermal  udev

 The photo at the web address below shows the output without the debug=vc
 kernel boot parameter.

 http://people.debian.org/~anibal/p1010539.jpg

 With the debug=vc kernel boot parameter there is no additional output.

 Just before the load of vmlinuz (at the ELILO boot prompt), I hit the
 tab key and typed LinuxOLD followed by debug=vc and it was ignored
 apparently.

 The prompt was:

  ELILO boot:
  Linux
  LinuxOLD
  (or a kernel file name: [[dev_name:/]path/]kernel_image cmdline options)

  ELILO boot:

 The machine is Dell PowerEdge 7250. I need to find out what's the
 dev_name of the EFI boot partition of the logical drive of the raid5.

 I tried debug=vc in elilo.conf and the system wouldn't boot and
 complained about that extra line in elilo.conf.

 My elilo.conf is below.

 ## elilo configuration file generated by elilo 3.12-4

 # install=/usr/lib/elilo/elilo.efi
 # boot=/dev/sda1
 # boot=/dev/disk/by-uuid/4DBC-29A7

 delay=20
 default=Linux

 relocatable


 image=/EFI/debian/vmlinuz
  label=Linux

 # root = /dev/sda2
 root = UUID=e662a93c-2b14-46bc-82aa-5d29cc2b4db1

  read-only
  initrd=/EFI/debian/initrd.img

 image=/EFI/debian/vmlinuz.old
  label=LinuxOLD

 # root = /dev/sda2
 root = UUID=e662a93c-2b14-46bc-82aa-5d29cc2b4db1

  read-only
  initrd=/EFI/debian/initrd.img.old
Uncompressing Linux... done
Loading file \EFI\debian\initrd.img...done
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.2.0-2-mckinley (Debian 3.2.19-1) (debian-kernel@l
ists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Fri Jun 1 22:37:41
 UTC 2012
[0.00] EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=
0x3fb3a000 HCDP=0x3fb2c000
[0.00] booting generic kernel on platform hpzx1
[0.00] PCDP: v0 at 0x3fb2c000
[0.00] Explicit console=; ignoring PCDP
[0.00] ACPI: RSDP 3fb2e000 00028 (v02 HP)
[0.00] ACPI: XSDT 3fb2e02c 00094 (v01 HP   zx6000 
 HP )
[0.00] ACPI: FACP 3fb36800 000F4 (v03 HP   zx6000 
 HP )
[0.00] ACPI Warning: 32/64X length mismatch in Gpe0Block: 32/16 (2011062
3/tbfadt-529)
[0.00] ACPI Warning: 32/64X length mismatch in Gpe1Block: 32/16 (2011062
3/tbfadt-529)
[0.00] ACPI: DSDT 3fb2e0e0 05781 (v01 HP   zx6000 0007 I
NTL 02012044)
[0.00] ACPI: FACS 3fb368f8 00040
[0.00] ACPI: SPCR 3fb36938 00050 (v01 HP   zx6000 
 HP )
[0.00] ACPI: DBGP 3fb36988 00034 (v01 HP   zx6000 
 HP )
[0.00] ACPI: APIC 3fb36a48 000B0 (v01 HP   zx6000 
 HP )
[0.00] ACPI: SPMI 3fb369c0 00050 (v04 HP   zx6000 
 HP )
[0.00] ACPI: CPEP 3fb36a10 00034 (v01 HP   zx6000 
 HP )
[0.00] ACPI: SSDT 3fb33870 001D6 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb33a50 00342 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb33da0 00A16 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb347c0 00A16 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb351e0 00A16 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb35c00 00A16 (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb36620 000EB (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: SSDT 3fb36710 000EF (v01 HP   zx6000 0006 I
NTL 02012044)
[0.00] ACPI: Local APIC address c000fee0
[0.00] 2 CPUs