Booting the installation images

David Cantrell dcantrell at redhat.com
Fri Jul 10 19:33:19 UTC 2009


-----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 at redhat.com>
Red Hat / Honolulu, HI

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkpXl4AACgkQ5hsjjIy1VklFFwCeP4IWW0fu5OXrOT/mZqRdRIfh
ESMAoNGUV3pkvEeNT+tG8yIwf+iFmhcu
=PLe7
-----END PGP SIGNATURE-----



More information about the s390x mailing list