Sven Luther wrote:
On Sun, Nov 13, 2005 at 07:01:28PM -0800, wolftales wrote:Jonas Smedegaard wrote:I can not install a 2.6 kernel because of these boot issues. The 2.4 kernel has been the only one I can successfully boot off from. So it appears to be a kind of a catch-22.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 13 Nov 2005 12:38:35 -0800 Wolftales <wolftales@wolftales.org> wrote:I had no luck running this with yaird as I showed below.Do I understand correctly that your running kernel is 2.4.27? If so, then you can't install yaird as it requires sysfs on the running kernel. To install using yaird you must first install and boot a kernel between 2.6.8 (oldest kernel supported by yaird) and 2.6.12 (newest kernel supported by initrd-tools). - Jonas- -- * Jonas Smedegaard - idealist og Internet-arkitekt* Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDd+3Dn7DbMsAkQLgRAsa1AJ4vQYbOaWfe4d8EW0b+3uJILCnPEgCfTBAs n/b+RK0yVDQJFKaop9A5oAg= =OBAT -----END PGP SIGNATURE-----You have two choices :1) install 2.6.8 from sarge or 2.6.12 from etch, and then install 2.6.14 after reboot. You will be forced to do something similar because of udev anyway. 2) install initramfs-tools and then install the 2.6.14 kernel. Things are still in flux, and 2.6.14 will not enter etch until these upgrade paths are solved. Friendly, Sven Luther
Hi,I am not sure how to accomplish installing yaird inorder to install 2.6.14. The only 2.6 kernel that works is the di kernel. I do not know how to use rescue mode to make this installation successful. However, Any version of the 2.6 kernel I have tried beyond that di kernel panics on boot. I _can_ get them installed. If I could get a normal version of 2.6 to work, I am thinking my issue would be solved.
Said differently, I have attempted to boot 2.6.10, 2.6.12, 2.6.13 and 2.6.14 (rc5 & 2). All version fail on boot. Only the di kernel hasn't paniced on boot . . . or knoppix kernel, that worked as well.
I do not know how to install yaird because I do not have a working 2.6.x environment to leverage. Secondly, I have installed 2.6.14 with initramfs-tools and provided the output. The issue while ordering changed with the modification of udevsynthesize from 2 to 20 was functionally the same. Device does not exist, /dev/sda1.
I may not be following where this e-mail thread is going, but I have accomplished both 1 & 2 of this last message. I just haven't been able to install 2.6.14 using yaird to create the initrd.img.
Please let me know if I am missing something about these instructions. Are we now troubleshooting yaird or trying to get 2.6.14 to install? yaird seems to be a catch-22 while 2.6.14 was installed and a boot was successfully tried a couple of times, it just ends with the kernel panic before reaching a usable level.
What should I do next? Thank you, Ken