> Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > Plan A
> > ~~~~~~
> > Make sure that all programs copied to your USB-stick have their
> libraries
> > copied there also. As in 'ldd /sbin/losetup
>
> Yes, ldd is the program for it:-) I never knew that command before.
Ok, now it works! It was file /lib64/ld-2.3.4.so that missed.
build-initrd.sh couldn´t get that file because insmod and losetup need file
/lib64/ld-linux-x86-64.so.2. But this file is only a link to above
/lib64/ld-2.3.4.so! So you could call that braindamage. I don´t see why they
make it more complicated this way but I guess they have their reasons.
Kernel changes on SuSE 9.3 are bigger than on 9.2. Maybe that´s why the
bootup shows so many silly error messages.
Below is a sequence from /var/log/boot.msg
<6>Uniform CD-ROM driver Revision: 3.20
<6>hdb: ATAPI 40X CD-ROM CD-R/RW drive, 4096kB Cache, DMA
<6>cdrom: open failed.
<4>ide-floppy driver 0.99.newide
<3>hdc: No disk in drive
<6>hdc: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm
<3>hdc: No disk in drive
<4>kobject_register failed for scsi_mod (-17)
<4>
<4>Call Trace:<ffffffff802220b6>{kobject_register+70}
<ffffffff8014ab27>{sys_init_module+5687}
<4> <ffffffff801557f7>{__generic_file_aio_read+423}
<ffffffff80146b00>{autoremove_wake_function+0}
<4> <ffffffff80167b30>{do_mremap+944} <ffffffff80172e44>{vfs_read+244}
<4> <ffffffff80172fb3>{sys_read+83}
<ffffffff8010e6fe>{system_call+126}
<4>
<7>load_module: err 0xffffffffffffffef (dont worry)
<4>register_blkdev: cannot get major 8 for sd
<4>register_blkdev: cannot get major 65 for sd
<4>register_blkdev: cannot get major 66 for sd
<4>register_blkdev: cannot get major 67 for sd
<4>register_blkdev: cannot get major 68 for sd
<4>register_blkdev: cannot get major 69 for sd
<4>register_blkdev: cannot get major 70 for sd
<4>register_blkdev: cannot get major 71 for sd
<4>register_blkdev: cannot get major 128 for sd
<4>register_blkdev: cannot get major 129 for sd
<4>register_blkdev: cannot get major 130 for sd
<4>register_blkdev: cannot get major 131 for sd
<4>register_blkdev: cannot get major 132 for sd
<4>register_blkdev: cannot get major 133 for sd
<4>register_blkdev: cannot get major 134 for sd
<4>register_blkdev: cannot get major 135 for sd
<4>kobject_register failed for scsi_mod (-17)
<4>
<4>Call Trace:<ffffffff802220b6>{kobject_register+70}
<ffffffff8014ab27>{sys_init_module+5687}
<4> <ffffffff801557f7>{__generic_file_aio_read+423}
<ffffffff80146b00>{autoremove_wake_function+0}
<4> <ffffffff80167b30>{do_mremap+944} <ffffffff80172e44>{vfs_read+244}
<4> <ffffffff80172fb3>{sys_read+83}
<ffffffff8010e6fe>{system_call+126}
<4>
<7>load_module: err 0xffffffffffffffef (dont worry)
<4>register_blkdev: cannot get major 8 for sd
<4>register_blkdev: cannot get major 65 for sd
<4>register_blkdev: cannot get major 66 for sd
<4>register_blkdev: cannot get major 67 for sd
<4>register_blkdev: cannot get major 68 for sd
<4>register_blkdev: cannot get major 69 for sd
<4>register_blkdev: cannot get major 70 for sd
<4>register_blkdev: cannot get major 71 for sd
<4>register_blkdev: cannot get major 128 for sd
<4>register_blkdev: cannot get major 129 for sd
<4>register_blkdev: cannot get major 130 for sd
<4>register_blkdev: cannot get major 131 for sd
<4>register_blkdev: cannot get major 132 for sd
<4>register_blkdev: cannot get major 133 for sd
<4>register_blkdev: cannot get major 134 for sd
<4>register_blkdev: cannot get major 135 for sd
Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.
Boot logging started on /dev/tty1(/dev/console) at Sun Apr 24 22:59:30 2005
Mounting shared memory FS on /dev/shmdone
Configuring serial ports...
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
Configured serial ports
doneActivating swap-devices in /etc/fstab...
doneChecking root file system...
fsck 1.36 (05-Feb-2005)
/dev/sda2: clean, 161278/1050400 files, 1362802/2098490 blocks
doneActivating device mapper...
Creating /dev/mapper/control character device with major:10 minor:63.
done
modprobe: FATAL: Error inserting sd_mod
(/lib/modules/2.6.11.4-20a-default/kernel/drivers/scsi/sd_mod.ko): No such
device
modprobe: FATAL: Error inserting sd_mod
(/lib/modules/2.6.11.4-20a-default/kernel/drivers/scsi/sd_mod.ko): No such
device
Checking file systems...
fsck 1.36 (05-Feb-2005)
doneSetting up kernel module dependencies (if required)done
Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
nothing was mounted
doneSetting up the CMOS clockCreating /var/log/boot.msg
done
<notice>startproc: execve (/sbin/udevd) [ /sbin/udevd -d ], [
CONSOLE=/dev/console TERM=linux SHELL=/bin/sh UDEVD_EVENT_TIMEOUT=1
UDEVD_EXPECTED_SEQNUM=860 INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1
UDEVD_MAX_CHILDS=50 COLUMNS=128
PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin
UDEVD_PIDFILE=/dev/.udevdb/udevd.pid vga=0x317 DO_CONFIRM= RUNLEVEL=S PWD=/
SPLASHCFG= PREVLEVEL=N LINES=48 HOME=/ SHLVL=2 splash=silent SPLASH=no
UDEVD_THROTTLE=0 _=/sbin/startproc DAEMON=/sbin/udevd ]
Starting udevd done
Coldplug
Coldplug: cleaning /events hwup: Loading module 'lp' for device 'printer'
processing eventsumount: /lib/klibc/events: not mounted
done
Loading required kernel modules
doneSetting up hostname 'blue'done
Setting up loopback interface <notice>killproc: kill(868,29)
done lo
lo IP address: 127.0.0.1/8
done
Starting Firewall Initialization (phase 1 of 2) SuSEfirewall2: Warning:
ip6tables does not support state matching. Extended IPv6 support disabled.
done
Restore device permissionsdone
Activating remaining swap-devices in /etc/fstab...
I´d very much like to know how to tell the system that some modules are now
in the kernel and no longer to be looked for on the harddrive. Btw. I only
made absolutely needed changes to the standard kernel-config from SuSE. I
only ran make bzImage and did not compile all the various modules again. So
which command will resolve these little changes in module dependency? depmod
-???
And files like /boot/System.map-2.6.11.4-20a-default
or /boot/symvers-2.6.11.4-20a-x86_64-default.gz
what are they for? Should they be on my usb-stick too? What do they tell the
kernel to do?
Regards,
Peter
--
+++ GMX - Die erste Adresse für Mail, Message, More +++
1 GB Mailbox bereits in GMX FreeMail http://www.gmx.net/de/go/mail
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
