Problem booting Debian/NSLU2 after flashing
Dear Folks,
The short story:
After flashing my new NSLU2 with the latest Debian di-nslu2.bin
firmware, the device does not finish booting. It seems to stop
with the amber status light, no beeps.
The long story:
I confirmed, of course, that the unit works under the native firmware.
I changed the network configuration to correspond to my local subnet.
I checked the MD5 sum against the posted one, unzipped, and flashed
(via wireless) using upslug2 to the di-nslu2.bin firmware. After
packet timeouts, I attached my linux box via cat5. The device flashed
and verfied followed by a reboot. As mentioned above, it stopped with
the amber status light, no beeps.
After the first failure, I reflashed the unit using upslug2 and a
manual rest to the Linksys firmware. Everything was then fine: the
web config was back with the IP that I configured originally.
I tried flashing (via cat5) using the web page method (as outlined in
the Debian/NSLU2 web page). Still the same behavior ("hanging with
amber status light").
I followed the procedure to the letter, including pulling out the
devices prior to upslug2, I tried both hard disk (in a Venus enclosure
oxsemi chipset) and a usb stick, in the proscribed order and singly,
just to grab at straws.
One additional observation (may not be pertinent): I formatted my hard
disk with three partitions ext3, swap, ext3 for system, swap and data.
I noticed that the Linksys firmware sees my hard disk as "unformatted"
which seemed odd to me . . . I was tempted to try their formatting
(just to see) but I wanted my hard disk the way originally partitioned
so I didn't.
Any ideas? I'm hoping it's simple . . . but I have no idea what else
to try.
Thanks!!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem booting Debian/NSLU2 after flashing
On Sat, May 19, 2007 at 05:26:55PM +0200, Martin Michlmayr wrote: > * Martin Weinberg <[EMAIL PROTECTED]> [2007-05-18 10:54]: > > I confirmed, of course, that the unit works under the native firmware. > > I changed the network configuration to correspond to my local subnet. > ... > > Any ideas? I'm hoping it's simple . . . but I have no idea what else > > to try. > > Simple question first: are you sure that you configured your network > fully, e.g. including DNS servers? > So here is some more (anecdotal) information: it is only the newer Debian/NSLU2 firmware that has this problem. I tried both the Unslung and the older Debian SlugOS-3.10 linked to your site (thanks for the great site!!!). Both work fine. I want a Debian system, so last night, I performed a successful Debian install using the deprecated bootstrap method with the SlugOS-3.10 firmeware. It's working happily, following the deprecated instructions. But, back to Debian/NSLU2: no I did not specify a DNS. I flashed with a point-to-point connection to a laptop. My network is running off of a Netgear wireless/wired router and I specified a static IP and gateway. Afterwards, my intention was to plug it into the router. This worked fine with the SlugOS-3.10. Is a DNS necessary for a Debian/NSLU2 boot?? --Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem booting Debian/NSLU2 after flashing
On Sat, May 19, 2007 at 05:26:55PM +0200, Martin Michlmayr wrote: > * Martin Weinberg <[EMAIL PROTECTED]> [2007-05-18 10:54]: > > I confirmed, of course, that the unit works under the native firmware. > > I changed the network configuration to correspond to my local subnet. > ... > > Any ideas? I'm hoping it's simple . . . but I have no idea what else > > to try. > > Simple question first: are you sure that you configured your network > fully, e.g. including DNS servers? > On second thought, I may have configured with a DNS since I recall that the SlugOS boot came up with the correct resolv.conf for the router box (which does the DNS), although, perhaps it cloned this from the gateway. I can't recall precisely, sorry to say. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem booting Debian/NSLU2 after flashing
On Sat, May 19, 2007 at 06:31:57PM +0200, Martin Michlmayr wrote: > * Martin Weinberg <[EMAIL PROTECTED]> [2007-05-19 11:52]: > > But, back to Debian/NSLU2: no I did not specify a DNS. I flashed with > > a point-to-point connection to a laptop. My network is running off of > > a Netgear wireless/wired router and I specified a static IP and > > gateway. Afterwards, my intention was to plug it into the router. > > This worked fine with the SlugOS-3.10. Is a DNS necessary for a > > Debian/NSLU2 boot?? > > Yes, the installer needs DNS so it'll be able to find a mirror. Well, that makes sense eventually, but would the absense of the DNS hang the boot early on? I could not get past "continuous amber" and couldn't log on at any time and the device never responded to a ping. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem booting Debian/NSLU2 after flashing
Ah, ha! I get it . . . thanks. Using your excellent notes, I successfully upgraded my SlugOS to Debian/NSLU2 so I'm all set, I think. On Mon, May 21, 2007 at 09:53:42AM +0200, Martin Michlmayr wrote: > * Martin Weinberg <[EMAIL PROTECTED]> [2007-05-20 11:42]: > > > Yes, the installer needs DNS so it'll be able to find a mirror. > > > > Well, that makes sense eventually, but would the absense of the DNS > > hang the boot early on? > > Yes. I know that's not obvious but it's because of the way > debian-installer currently works. We need to get the network up > before we can start SSH, and getting the network up in d-i currently > means configuring *everything*, i.e. also DNS. When something is not > configured that's needed, d-i will prompt the user to add this > information - but because this is done before SSH is up, the user > doesn't see it and it appears as if the machine would simply hang. > -- > Martin Michlmayr > http://www.cyrius.com/ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
