-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In my continued effort to debug this booting issue, I rebuilt a new initrd based on the default lenny kernel (2.6.26-1-486).

My procedure was this:
* gunzip and extract the voyage inird cpio file
* delete /lib/modules/2.6.26-486-voyage
* copy over the /lib/modules/2.6.26-1-486 from lenny
* repack the cpio with find * | cpio -ov -H newc | gzip -c - > 
/mnt/cf/boot/initrd.img-2.6.26-1-486
* copy the vmlinuz-2.6.26-1-486 from lenny
* add an entry to grub
* copy the lib/moduels to the voyage real rootfs

I then booted voyage Feb 18 nightly build, which failed to boot properly.

I then booted with my test kernel/initrd which booted properly.

You can see the logs of my attempts at http://ben.nerp.net/voyage/

PS. It seems Punky Tse mail server is rejecting mail due to over quota. :(

- -ben

 "UNIX is user-friendly, it's just picky about its friends."

On Wed, 18 Feb 2009, Punky Tse wrote:

Hi Ben,

Since you are using serial console, I would suggest you put the console output for us to investigate.

Regards,
Punky


Ben Kochie wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry, I forgot to mention in my earlier mail. These blade servers do not have a console at all, they only support serial installs.

I'm not sure exactly what the issue is yet, because after waiting a long long time (10+min) it eventually gets past the serial driver loading, but it never completes boot. It fails somewhere in the initrd. I will try and log a boot sequence. Unfortunately, the voyage kernel disables the kernel message timestamps so it will be harder to debug the length of time it takes to boot. Can those timestamps be enabled via boot args?

- -ben

 "UNIX is user-friendly, it's just picky about its friends."

On Wed, 18 Feb 2009, Punky Tse wrote:

Hi Ben,

I suggest you to use console terminal option when installing, or remove ttyS0 option at grub prompt.

Regards,
Punky

Ben Kochie wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm trying to get voyage-current (as of yesterday) booted on a fairly old Trasmeta based blade server by RLX. I am able to boot Ubuntu hardy, but the 2.6.26-486-voyage kernel will not boot. It gets stuck after trying to load the serial drivers. I chose Generic PC for install, and serial console at 38400. (deafult for this system) I also had no problem booting lenny.

- -ben

 "UNIX is user-friendly, it's just picky about its friends."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJmbPrfYg2asD844oRAspbAJ9zBtdwqaSW547V/LhzMQLoWWm64QCgjMit
ZgGYG1iMwXJWJAjIw6IoaqE=
=VSrR
-----END PGP SIGNATURE-----

_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux

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

iD8DBQFJnCvRfYg2asD844oRAnBMAKCwLZmkRrKXL2BWr6LMADs++gvdeQCgsm6Y
Xns8dQEfWnoCMcTucVSdK30=
=k/pJ
-----END PGP SIGNATURE-----

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

iD8DBQFJnQEdfYg2asD844oRAiw2AKCbdItkSXXocM5sx8KmwsrYxQB/4wCfc9ZV
bck485fepzUdQ5MokSjFsPY=
=AWD3
-----END PGP SIGNATURE-----

_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux

Reply via email to