I have installed kamikaze on a new wrt54gl version 1.1
---------- here is the output of the cat /proc/cpuinfo
root@OpenWrt:~# cat /proc/cpuinfo
system type             : Broadcom BCM5352 chip rev 0
processor               : 0
cpu model               : BCM3302 V0.8
BogoMIPS                : 199.47
wait instruction        : no
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : no
hardware watchpoint     : no
VCED exceptions         : not available
VCEI exceptions         : not available
root@OpenWrt:~#
---------------------
It seems that it is working well, but when I use wifi it becomes unstable and it resets itself unpredictably. It could be after a few hours of working. It reboots and therefore I cannot check log or dmesg. However once I set up remote logining and no message regarding reboot came up. Any idea what I can do? I did some research on the net to no avail.

khodam

same issue here. I got a WRT54G v3.1
don't know, why it reboots yet, waiting for the next reboot to hopefully find something in my just set up remote log...

Never had any trouble on white russian though... considering switsching back.... these reboots are unacceptable...

did you find a solution?

I still have the problem, but I am sure that wifi is the source of problem. If you have it disabled you would not run into trouble.

khodam

can definitely confirm this...

have disabled wifi for some hours now and not have had a reboot since...
remote logging gave no result (i.e. no output to syslog before reboot) and i don't have yet a serial port attached to this device...

would be nice, if some dev could give a hint, what could be wrong with wifi, or even better someone knows changes concerning it
between white russian and kamikaze... as said before it is the regular broadcom from linksys wrt54g v3.1

could some old orphaned entries from white russian in nvram cause this?

ps: just came to my mind... do you like me have the wlan in a separate vlan? i "broke" up the bridge so to say and have a sperate net now...
i also had this setup without any flaws in my old WR release candidate without any trouble though....

(Last edited by kanne on 16 Mar 2008, 21:29)

solved it...

did:
1) mtd -r erase nvram
2) get fresh openwrt (with x-wrt extensions) image dated by march 16th from x-wrt page
3) flashed the trx to device with mtd -r write image.trx linux
4) configured image as it was before, except for not breaking the bridge between wifi and 802.3

i bet the trouble came from the faulty relicts in nvram from white russian days, but cannot say for sure...
the bridge thing would also be possible, but i had the bridge broke up on white russian without trouble, so i kinda doubt it...
will try the next days, whether bridge broke up does bring the reboots back...
you are welcome to try the steps as above and maybe even solve the question, which of the point is causing the solution...

cheers
kanne

thanks kanne for the input. Please keep us posted.

well, actually after two days of continues uptime, the wrt just rebootet...
well, i will test my other linksys which is still running white russian soon with kamikaze...
on that device i already have a serial port mounted... if it should fail, i might find some new track...
but time is running very short at the moment...