Mailinglist Archive: opensuse-bugs (7117 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=350993

User hammett@xxxxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=350993#c8





--- Comment #8 from Quentin Sciascia <hammett@xxxxxxxxxxxx>  2008-01-07 
15:40:22 MST ---
Hi Again

Okay when I run mkinitrd this is the error output

imacg3:/boot # mkinitrd -v

Kernel image:   /boot/vmlinux-2.6.22.13-0.3-default
Initrd image:   /boot/initrd-2.6.22.13-0.3-default
Root device:    /dev/disk/by-id/scsi-SATA_QUANTUM_FIREBAL376904465598-part4
(/dev/sda4) (mounted on / as ext3)
[BLOCK] /dev/sda -> pata_cmd64x
[BLOCK] /dev/sda -> sd_mod
[MODULES]       02-start.sh: pata_cmd64x aic7xxx mesh
[MODULES]       11-block.sh: pata_cmd64x sd_mod
[MODULES]       11-usb.sh: usbcore
[MODULES]       11-usb.sh: ohci_hcd
[MODULES]       11-usb.sh: uhci-hcd
[MODULES]       11-usb.sh: ehci_hcd
[MODULES]       11-usb.sh: usbhid
[MODULES]       84-mount.sh: 
WARNING Cannot determine dependencies of kernel module 'ohci_hcd'.
        Does it exist? If it does, try depmod -a. Continuing without ohci_hcd.
Kernel Modules: scsi_mod libata pata_cmd64x scsi_transport_spi aic7xxx mesh
sd_mod uhci-hcd ehci-hcd 
[MOUNT] Root:   /dev/disk/by-id/scsi-SATA_QUANTUM_FIREBAL376904465598-part4
Features:       block usb resume.kernel
Shared libs:    /usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary
file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
/usr/bin/ldd: line 161: /lib64/ld64.so.1: cannot execute binary file
ldd: exited with unknown exit code (126)
lib/ld-2.6.1.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libblkid.so.1.0
lib/libcom_err.so.2.1 lib/libc-2.6.1.so lib/libdl-2.6.1.so lib/libext2fs.so.2.4
lib/libhistory.so.5.2 lib/libncurses.so.5.6 lib/libpthread-2.6.1.so
lib/libreadline.so.5.2 lib/librt-2.6.1.so lib/libutil-2.6.1.so
lib/libuuid.so.1.2 lib/libvolume_id.so.0.79.0 lib/libnss_files-2.6.1.so
lib/libnss_files.so.2 lib/libgcc_s.so.1 
12515 blocks


It seems to me that it is trying to use a 64-bit lib, and is getting nowhere. I
was wondering if you could contact the splashy script maintainer and ask him
how the splashy script sets up placing the splashy binaries from /usr/sbin/
into initrd? I can't find anything in the setup-splashy.sh script that does
this, and am "assuming" somewhere/somehow the init script in initrd is
dynamically linked to these binaries.

BTW - this mkinitrd was done on another fresh install of SuSE 10.3 PPC, not
carrying my modified setup-splashy.sh script. The same error is evident,
however, on a system carrying the modified script as well.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.