Sven Luther wrote:
I was able to install the 2.6.8 sarge kernel and get a working system afterwards.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
I installed "linux-image-2.6.14-2-686-smp 2.6.14-3" using yarid instead of initramfs with similar results.
console output: io schedluer cfg registered NET: Registered poto family 2 IP TCP: Hash tables configured (established 262144 bind 65536 TCP reno registered TCP bic registered NET: Registered protocol family 8 20 Using IPI shortcut mode Freeing unused kernel memory: 208k freed input: AT Translated set 2 keyboard on isa0060/serio0 mice: PS/2 mouse device common for all mice SCSI subsystem initialized /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 1 seconds for /ses/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 2 seconds for /ses/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 4 seconds for /ses/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 8 seconds for /ses/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Waiting 16 seconds for /ses/block/sda/dev to show up /bin/cat: /sys/block/sda/dev: No such file or directory Device /sys/block/sda/dev seems to be down. Debugging opportunity, type ^D to continue. /bin/dash: can't access tty; job control turned off #