Bug#343674: arm/netwinder: nobootloader gives wrong kernel path
- To: Jurij Smakov <jurij@wooyd.org>
- Cc: 343674@bugs.debian.org, kmuto@debian.org
- Subject: Bug#343674: arm/netwinder: nobootloader gives wrong kernel path
- From: Martin Michlmayr <tbm@cyrius.com>
- Date: Sat, 7 Jan 2006 19:42:08 +0000
- Message-id: <[🔎] 20060107194208.GA3955@deprecation.cyrius.com>
- Reply-to: Martin Michlmayr <tbm@cyrius.com>, 343674@bugs.debian.org
- In-reply-to: <20051230144335.GE25261@deprecation.cyrius.com>
- References: <Pine.LNX.4.63.0512161831430.3428@bobcat> <20051218184736.GB16162@kitenet.net> <Pine.LNX.4.63.0512181122050.3833@bobcat> <20051218201308.GG16162@kitenet.net> <Pine.LNX.4.63.0512181336050.4514@bobcat> <20051218230254.GA1715@kitenet.net> <20051224160206.GB4737@deprecation.cyrius.com> <Pine.LNX.4.63.0512241730450.3523@bobcat> <20051230144335.GE25261@deprecation.cyrius.com>
> * 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
say?
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: