**** BEGIN LOGGING AT Mon Jul 21 02:59:56 2008 Jul 21 14:56:47 Hi Jul 21 14:58:13 Do you know whether Eisfair under the NSLU2 is running? Jul 21 14:58:24 sry my english is very bad^^ Jul 21 14:59:28 hmm, anyone here? Jul 21 15:22:16 hi, i flashed my slug with the SlugOS/BE firmware, now when i'm trying to flash it with another firmware it keeps crashing at around 83% Jul 21 15:50:57 Frigolit: i have not tried that before Jul 21 15:51:06 Frigolit: http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash might have some info Jul 21 16:08:42 chrisb: thanks, i'll check it out Jul 21 16:09:05 hi all Jul 21 16:09:37 i need some help with .mk file variables Jul 21 16:10:07 what should I set for CC= Jul 21 16:15:04 ok, found it Jul 21 16:15:24 chrisb: upslug2 gives me "flash programming error [N12NSLU2Upgrade10FlashErrorE]" Jul 21 16:15:42 and that it could be a hardware error, but i mean, it worked the first time i flashed it :\ Jul 21 17:36:07 okay somethings seems to be very wrong Jul 21 17:36:12 something* Jul 21 17:36:45 i even tried doing it the hard way through Redboot, but it gave me "Can't erase region at 0x506e0000: Error trying to erase" Jul 21 17:39:47 which seems to be the same location it crashes on when using upslug2 Jul 21 17:46:06 Frigolit: You can try another power supply -- but that message seems to indicate a hardware failure of the flash chip on the NSLU2. Jul 21 17:46:29 yea, the only thing is that it worked earlier when i flashed it with the SlugOS/LE firmware :/ Jul 21 17:46:50 which was about 2-3 hours ago now Jul 21 17:46:59 At the redboot level, you could have flashed it with all zeros, it doesn't know or care. Jul 21 17:47:27 There's abolutely nothing in the flash image that can affect the ability of redboot to reflash or erase the flash. Jul 21 17:47:27 yea, but it shouldn't have crashed Jul 21 17:47:35 exactly Jul 21 17:47:49 Right - so it seems to be a hardware problem. Jul 21 17:48:00 on the other hand i haven't done anything to make the hardware fail :P Jul 21 17:48:12 so it seems a bit weird Jul 21 17:48:36 Hardware fails... and the power supply is the most common failure on the NSLU2s, at least that's been reported to the mailing lists. Jul 21 17:49:14 not that i expect the power supply to fail the same day i get it :P but i could try with another power supply Jul 21 17:49:17 anything that might work Jul 21 17:49:23 It may seem weird, but there's absolutely no way that upslug can break redboot; upslug will not overwrite redboot even if you told it to. Jul 21 17:49:33 redboot works Jul 21 17:50:17 i can get into redboot and upgrade mode, it just keeps failing when writing/erasing 0x506e0000 on the flash Jul 21 17:52:01 Frigolit: Yes. Jul 21 17:52:42 the power supply gives me 5.4V Jul 21 17:53:18 What I'm trying to say is that redboot is managing your flash -- it reads commands if you are telnetted into redboot, or if you are using upslug2 to reflash, it reads information from the network. Either way, redboot erases and rewrites the flash, so if redboot cannot erase your flash, the contents that you last flashed into that flash cannot matter anymore. Jul 21 17:53:34 Frigolit: 5.4 when the NSLU2 is powered up and running? Jul 21 17:53:50 no, just the PSU plugged in Jul 21 17:53:58 Oh. That's meaningless. Jul 21 17:54:17 The reported failures all involve low voltage under load. Jul 21 17:54:24 hm okay Jul 21 17:54:37 (Personally, I think Linksys got a bad batch of power supplies at some point) Jul 21 17:54:40 it'll be tough to measure that :q Jul 21 17:54:59 Not so tough -- check the voltage on the USB port sockets. Jul 21 17:55:24 hm okay Jul 21 17:55:31 The outer two contacts on a USB socket are power and ground. Jul 21 17:55:59 P . . G ? Jul 21 17:56:22 Doesn't matter, if the needle goes the wrong way, just reverse the probes. ;) Jul 21 17:56:29 true Jul 21 17:57:14 Or you can put the ground probe on the shield around the ethernet socket, then touch the outer contacts on the USB socket, one will give you a positive voltage. Jul 21 17:59:14 bah, probes are to thick, it short-circuits the pins and the shield on the USB-port :P Jul 21 17:59:21 sec Jul 21 17:59:26 Ouch. Jul 21 18:00:15 i have a cut-off USB-cable i'm gonna use instead, just gotta fix it a bit Jul 21 18:03:32 5.35 when in upgrade mode, gonna start upslug2 and measure it Jul 21 18:08:15 5.33 when upgrading, no drop when it crashed Jul 21 18:08:59 seems more like the flash just... broke :\ Jul 21 18:09:24 gonna try a stronger PSU though, one that can deliver 800mA instead of 500 Jul 21 18:20:49 nope, that's not it :( seems it seriously IS broken Jul 21 18:32:29 Frigolit: :( You might send an email to the list to see if anyone else has suggestions. I had one with similar problems, and tried to replace the flash chip -- the original chip is out of production, and I damaged the PCB when trying to solder in different one. Jul 21 18:33:28 considering i bought it recently (i got it today) and i could flash it ONCE, i should just get the whole device replaced Jul 21 18:35:23 also, when i first configed it and set the IP and rebooted it, it just hung flashing green (original firmware) Jul 21 18:35:38 then when i pressed reset it started beeping twice every second Jul 21 18:35:48 and after a while it booted so i could get to the web interface Jul 21 18:36:06 that's also a bit weird tbh Jul 21 18:36:57 Frigolit: you have a serial console where you can see redboot running? Jul 21 18:37:17 no i used telnet Jul 21 18:37:50 Frigolit: how do you do that? Jul 21 18:38:18 when it's booting normally, after about 10 sec you can telnet to 192.168.0.1 port 9000 for a short while Jul 21 18:38:22 otherwise it'll boot normally Jul 21 18:38:31 ... i think mine just booted, something Jul 21 18:38:38 it beeped and now the led is lit green Jul 21 18:39:00 Frigolit: cool, thanks Jul 21 18:39:06 np Jul 21 18:39:43 well, it should have 83% of the linksys firmware in it so :\ Jul 21 18:45:28 cool, i can get to the webinterface Jul 21 18:45:39 "Firmware version: V" :) Jul 21 18:52:14 but no, it seriously seems to be broken, i'll guess i should just have it replaced Jul 21 20:14:16 this has got to be a broken flash, i'm incrementally trying to add the image using redboot, so when it crashes i attempt to erase and start from the position where it crashed Jul 21 20:14:34 the thing is that at 0x506a0000, the erase succeeds most of the times Jul 21 20:14:44 but like every 4th erase it fails Jul 21 20:15:03 that must be a broken flash chip, right? Jul 21 20:43:19 live demo of the smallest commercial laptop in the world http://www.ustream.tv/channel/3667 **** BEGIN LOGGING AT Mon Jul 21 22:24:27 2008 **** ENDING LOGGING AT Tue Jul 22 02:59:57 2008