Re: Stalled Boot on NSLU2
Well... looks like there is something my slug doesn't like about the
install on my disc. Just created a fresh install on a new disk + fresh
flash of firmware, and the slug is now responsive. I'd still like to
figure out why the slug won't finish boot with my old disc. Any
recommendations, considering that the slug won't even get to boot
logging before stalling?
- jake
On 9/24/07, Jake McGraw <jmcgraw1@gmail.com> wrote:
> Looking at contents of my /boot dir:
>
> apex.flash
> config-2.6.18-4-ixp4xx
> initrd.img -> initrd.img-2.6.18-4-ixp4xx
> initrd.img-2.6.18-4-ixp4xx
> initrd.img-2.6.18-4-ixp4xx.bak
> System.map-2.6.18-4-ixp4xx
> vmlinuz -> vmlinuz-2.6.18-4-ixp4xx
> vmlinuz-2.6.18-4-ixp4xx
>
> I would take a guess and say my kernel version is 2.6.18-4? Can I just
> upload sda1-2.6.18.dfsg.1-12.bin to my upgrade mode slug?
>
> Once again, thanks for the help.
>
> - jake
>
> On 9/24/07, Martin Michlmayr <tbm@cyrius.com> wrote:
> > * Jake McGraw <jmcgraw1@gmail.com> [2007-09-24 14:01]:
> > > 1. Where do I get the .18 kernel image?
> >
> > Probably
> > http://cyrius.com/debian/nslu2/files/sda1-2.6.18.dfsg.1-12.bin
> > although that really depends on the kernel you were running before.
> > If you write the kernel in flash and on disk don't match, your system
> > will definitely not boot and you'll have to reinstall or something.
> > I suppose you don't know what version you were running?
> >
> > What does 'ls -l /boot' of your NSLU2 disk say? (Just connect it to a
> > PC and mount it there.)
> >
> > > 2. How should I go about flashing my slug (Reset Button/Upgrade mode
> > > + upslug2?)
> >
> > Yes.
> >
> > > 3. How can I make sure my slug doesn't auto-update or something like
> > > that in the future?
> >
> > Don't run "aptitude upgrade" or "apt-get upgrade", but really, an
> > upgrade should not stop your box from booting. Unfortunately, it's
> > pretty hard to say what might be going on when you don't have a serial
> > console.
> >
> > --
> > Martin Michlmayr
> > http://www.cyrius.com/
> >
>
Reply to: