[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#343674: arm/netwinder: nobootloader gives wrong kernel path

On Sat, 7 Jan 2006, Martin Michlmayr wrote:

* Jurij Smakov <jurij@wooyd.org> [2005-12-24 17:46]:
Second, in the end of installation a screen comes up with the
recommended settings for the firmware environment variables,
required to make the machine bootable from the hard drive. Among
other things, it advises the user to set the kernel filename
(kernfile) variable to /vmlinuz.  However, in the installation
process the kernel is placed into /boot/vmlinuz-2.4.27-netwinder and
no /vmlinuz symlink is created, so the system is unbootable with
this setting. Either this screen should be corrected, or /vmlinuz ->
/boot/vmlinuz-2.4.27-netwinder symlink should be created.

What does
   ls -l /boot
Martin Michlmayr

Hi Martin,

Sorry for the delay, I've had some hardware failures to deal with. Here's the output of ls -l /boot on a freshly-installed netwinder:

jurij@debian:~$ ls -l /boot/
total 2740
-rw-r--r--  1 root root   43446 2005-10-29 11:52 config-2.4.27-netwinder
-rw-r--r--  1 root root      45 2005-10-29 12:50 patches-2.4.27-netwinder
-rw-r--r--  1 root root  559227 2005-10-29 12:50 System.map-2.4.27-netwinder
lrwxr-xr-x  1 root root      24 2005-07-18 10:50 vmlinuz -> vmlinuz-2.4.27-netwinder
-rw-r--r--  1 root root 2183240 2005-10-29 12:49 vmlinuz-2.4.27-netwinder

Please let me know if you need any other information.

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

Reply to: