--- In firstname.lastname@example.org
, Rod Whitby <rod@...> wrote:
> roy_anstee wrote:
> > I am sorry but I not use to posting messages to techincal groups such
> > as this one and if I have not used the correct protocol I apologise.
> Your protocol is fine.
> > What I was trying to achive in the previous posting is to confirm if I
> > had trashed nslu2 and I was trying to keep my question to a minimum.
> Yep, it's bricked. But you can recover it with JTAG (or have someone
> else do that for you).
> > That said, I find Wiki avery good source of information on this
> > subject and many other subjects. There is just too much information to
> > take in.
> Yes, we need people like yourself to write down the lessons learned, and
> summarise existing information (leaving out no longer relevant stuff),
> or marking incorrect or obsolete information as such. Have you done so?
I am noy sure how I update Wiki with my experiences? Will it not
confuse people with too much information as I found?
> (I didn't see your name in the wiki recent changes list ...)
> Many people complain about the wiki. Very few do something to
> > At the time I did try the Reset-Button, but I couldn't gain access to
> > the box through the network interface either directly using a cross
> > over cable or via a network switch. Nslu2 showed an amber
> > ready/status light without going through the normal sequence of
> > flashing leds on power up. The nslu2 just seem to have gone deaf &
> > dumb and read an article by Jim Buzbee who suggested there was a
> > problem with nslu2 not detecting the network interface.
> > At this time I came across another article saying I could see what was
> > happening on the nslu2 by connecting up the internal serial port.
> > I connected the serial interface and sure enough I could see the the
> > booting up of Redboot but it stopped at what I believe to be unpack of
> > the linux kernel. It didn't complete the uncompress the kernel.
> That's when you should have simply gone back into upgrade mode, and
> reflashed. With serial, you would have even been able to watch it
> reflash and reboot.
> > I panicked and just wanted to get it back to factory settings. I read
> > another article that I could achive this by setting Redboot to receive
> > the linksys binary file. I used a commands of 'recovering from a bad
> > flash' but real did understand what i was doing but at the time I
> > thought I did.
> Have you added the warnings to that page as I requested?
> > This is not how upgrade to SlugOSLe. What I didn't
> > appreciate how this little box holds its firmware in flash.
> > Anyway I have put this down to experience. I am hoping to purchase
> > another nslu2 and try again. I would like to see it working as a file
> > and print server.
> > Once again many thanks.
> The best way to show your thanks is to significantly improve the wiki.
> That's even better thanks than cash donations.
> -- Rod
I am still confused on how to load SlugOSLe with Intel driver. Do I
need to build a kernel with an updated NIC driver or can I just use
the binary as is?