Hello,
It took me a while, but I've finally figured out the pungi problems where almost no libraries got copied into the installation initrd. I'll prepare a patch and will send it to David
So far I run into several problems with those images:
- all parameters given in the parm file are ignored and I had to enter the whole network configuration again - insmod doesn't load any modules, which means that the linuxrc can't load required modules. I currently have to drop to a shell and load them manually with modprobe - dbus-daemon doesn't start automatically, but the loader relies on it - the loader doesn't get started automatically and hangs at the first screen when started manually. - wpa_supplicant gets started ?!
Karsten
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 10 Jul 2009, Karsten Hopp wrote:
Hello,
It took me a while, but I've finally figured out the pungi problems where almost no libraries got copied into the installation initrd. I'll prepare a patch and will send it to David
So far I run into several problems with those images:
- all parameters given in the parm file are ignored and I had to enter the
whole network configuration again
That's strange, but that would all be in linuxrc.s390 I would think.
- insmod doesn't load any modules, which means that the linuxrc can't load
required modules. I currently have to drop to a shell and load them manually with modprobe
Are we copying in the correct insmod and not the busybox one?
- dbus-daemon doesn't start automatically, but the loader relies on it
This is launched by init.c on all platforms except s390. Since we have linuxrc.s390 on s390, we'll need to modify it to start dbus-daemon for us.
- the loader doesn't get started automatically and hangs at the first screen
when started manually.
linuxrc.s390 is responsible for this.
- wpa_supplicant gets started ?!
Because of NetworkManager, which is started by loader. So that tells me loader is starting, but failing to get going.
- -- David Cantrell dcantrell@redhat.com Red Hat / Honolulu, HI