macsat.com OpenWrt and ASUS WL Forum
January 08, 2009, 18:15:40 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?
Login with username, password and session length
News: Back to macsat.com
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: WRTSL54GS - Serial Console UnBrick  (Read 1358 times)
0 Members and 1 Guest are viewing this topic.
Unstable Connection
Newbie
*
Offline Offline

Posts: 13


View Profile
« on: August 07, 2007, 08:41:57 AM »

I just received my new WRTSL54GS. Ordered it from eBay, coz it is not sold here. Royally messed it up. Pls help. Here is what I did


1) Connected Power Adapter and booted router. Router Booted and everything was fine.
2) Few seconds later there was smoke from the Power Adapter. Switched off router and well realized 120V != 220V. DOH!!
3) Plugged in another compatible power adapter of my old Netgear HUB.
4) Booted up router but it stays on "Blinky Power LED mode"

Now I started panicing as it has no warranty and S***. Tried the Linksys TFTP Method as well as the OpenWRT TFTP Method.

Finally had brains enough to attach a Serial Cable. Turns out I have Kernel Panic for some reason. Here is the output

Code:

ufsd: address 0xc001d060                       
modules[0]=et buf=[et ]                       
modules[1]=ctmisc buf=[et ctmisc ]                                 
modules[2]=wl buf=[et ctmisc wl ]                                 
modules[3]=sec buf=[et ctmisc wl sec ]                                     
modules[4]=bcm_se buf=[et ctmisc wl sec bcm_se ]                                               
Needed modules: et ctmisc wl sec bcm_se                                       
Using /lib/modules/2.4.20/kernel/drivers/net/et/et.o                                                   
eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.                                                           
eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.38.0                                                               
Using /lib/modules/2.4.20/kernel/drivers/net/ctmisc/ctmisc.o                                                           
Register /dev/ctmisc device, major:250 minor:0                                             
Using /lib/modules/2.4.20/kernel/drivers/net/wl/wl.o                                                   
PCI: Enabling device 01:01.0 (0004 -> 0006)                                           
Data bus error, epc == 8013eb94, ra == 8013f244                                               
Oops in traps.c::do_be, line 492:                                 
$0 : 00000000 1000fc00 00000000 c00c4000 81e81280 0000039a 81e8dbd8 00000001                                                                           
$8 : 0c020083 00000000 00000000 00000000 fffffffe ffffffff 00000010 00000000                                                                           
$16: c00c4ffc 81e81280 00000000 00000011 00000001 00000002 c00c4000 00004318                                                                           
$24: 81e8dc50 00000001                   81e8c000 81e8dbc8 810c68e0 8013f244                                                                           
Hi : 00040666             
Lo : 90ea0000             
epc  : 8013eb94    Not tainted                             
Status: 1000fc03               
Cause : 0000001c               
Process insmod (pid: 31, stackpage=81e8c000)                                           
Stack:    c00c4000 00004318 8013faf4 00000011 8013f360 00000000 c00c4000                                                                       
 81e81280 00000001 8013f244 00000001 81e81280 00000001 00000011 8013efb0                                                                       
 810c68e0 c00c4000 00004318 8002d478 00000000 81059860 00000020 81e81280       
 810c68e0 c00c4000 00004318 00000001 00000000 00004318 810c68e0 81e81180
 8013edbc 8002d478 00000001 802bff36 00000081 00000001 00000000 81bc50a4
 81bc50a8 ...
Call Trace:   [<8013faf4>] [<8013f360>] [<8013f244>] [<8013efb0>] [<8002d478>]
 [<8013edbc>] [<8002d478>] [<c0072af8>] [<8000a2a8>] [<8000a288>] [<8002d478>]
 [<80010d5c>] [<80240960>] [<8000a4e8>] [<80240960>] [<c00a7d68>] [<800113fc>]
 [<801710dc>] [<8024ba14>] [<80288eb4>] [<80170006>] [<8024bb48>] [<801702b4>]
 [<80002478>] [<c00c16ec>] [<c00a7fe4>] [<c006fc40>] [<c00c1694>] [<8017098c>]
 [<c00c16ec>] [<80170a74>] [<c00c16ec>] [<c00a839c>] [<80030e60>] [<800123c0>]
 [<800125ac>] [<8002377c>] [<c006e060>] [<800085a4>] [<c00c2232>] ...

Code: 2405039a  27a60010  24070001 <8e100000> 54400008  8e240018  02001021  8fbf
0024  8fb20020
Using /lib/modules/2.4.20/security/sec.o
BCM582x driver v1.85:
 <BCM4718, Bus 0, Slot 7, IRQ 2> ubSec: enabling Interrupt.
BCM582x: Selftest flag not set. Not doing Selftest
BCM582x: 4708: part number 00000000

Using /lib/modules/2.4.20/kernel/drivers/se/bcm_se.o
Loading Broadcom streaming encryption device module...
SE driver version 1.0, maximum 256 SE devices
Checking to see that USB initialization is done...
Hit enter to continue...
At this point I cant ping the router or use TFTP or Telnet

I managed to get the CFE prompt by holding down CTRL+C at bootup, but I am really scared to try anything, unless I am sure of it.

I went to http://wiki.openwrt.org/OpenWrtDocs/Troubleshooting and checked out the serial console method.

I have an original Linksys Firmware. Does it have "boot_wait=on" by default or do I have to set it??

Also will these commands be safe to try on my WRTSL54GS?? It seems like they are meant for the WRT54G.

Code:
CFE> ifconfig eth0 -addr=192.168.1.1 -mask=255.255.255.0
CFE> et up
CFE> flash -noheader : flash1.trx

So pls if you could help me out with the commands and what image to use. I would prefer to use an OpenWRT image, but the original Linksys firmware would be great too.

Thanks

BTW this is the CJK0 version.
« Last Edit: August 07, 2007, 10:49:35 AM by Unstable Connection » Logged
Unstable Connection
Newbie
*
Offline Offline

Posts: 13


View Profile
« Reply #1 on: August 07, 2007, 09:59:12 AM »

I set "boot_wait=on" by using the nvram commands, as given here http://wiki.openwrt.org/OpenWrtDocs/Troubleshooting

Then using the Linksys TFTP Utility even flashed the original Linksys firmware. But it still keeps crashing with the same error.

What should I do? Any Ideas??
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

English Steel 1.6 © Saxon North Technologies
Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2008, Simple Machines LLC
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.093 seconds with 24 queries.