Weird Behavior Of Wifi In Sl-6000

[insomniux]

Hi,
I want to report some weird behaviour of my sl-6000L. I am using the Sharp Rom 1.12 with no special tweaks.

The other day, suddenly wifi stopped working (small icon in systray showed red arrow)  . I had that once before and rebooting solved the problem. However not this time. I found out that starting the network applet did not load the modules (prism2_usb and p80211) and dmesg reported that 'hub.c could not attach devices' (cannot recall precise error messages). Becoming somewhat desperate I reflashed my 2-days-old nand backup: no effect. Flashed newly downloaded SHARP rom: no effect. Formatted in maintenance mode: no effect. Take out the battery for some time: no effect, etc, etc  .

Just before I was going to throw z6000 in the WindowsBin I tried the ZAURUS TEST option (10) of the maintenance mode (reset with d+p key, screen 4). This menu has a couple of scarying options, one of them being CheckWLAN (9). Running this option made the beautiful wifi-green led (had no seen it flashing ever since the problem started) blink at me and gave me hope. After closing the menu and resetting/rebooting the red arrow in the network applet has disappeared and wifi worked again (just in time)    .

I have no idea what caused the problem, and how to avoid it in future (or how to solve it in an easier way).

Hope this info is of some use for zauriers who run into the same problem.
Insomniux

[egg8178]

Hi,
I'm in the same kind of trouble.. can you elaborate more about going into the maintenance mode? after running CheckWLAN, what did the screen shows? Mine just displayed a line "WLAN attach" and stopped, pressing cancel or OK doesn't help, I have to reset..

Thanks in advance.
Egg

Hi,
I want to report some weird behaviour of my sl-6000L. I am using the Sharp Rom 1.12 with no special tweaks.

The other day, suddenly wifi stopped working (small icon in systray showed red arrow)  . I had that once before and rebooting solved the problem. However not this time. I found out that starting the network applet did not load the modules (prism2_usb and p80211) and dmesg reported that 'hub.c could not attach devices' (cannot recall precise error messages). Becoming somewhat desperate I reflashed my 2-days-old nand backup: no effect. Flashed newly downloaded SHARP rom: no effect. Formatted in maintenance mode: no effect. Take out the battery for some time: no effect, etc, etc  .

Just before I was going to throw z6000 in the WindowsBin I tried the ZAURUS TEST option (10) of the maintenance mode (reset with d+p key, screen 4). This menu has a couple of scarying options, one of them being CheckWLAN (9). Running this option made the beautiful wifi-green led (had no seen it flashing ever since the problem started) blink at me and gave me hope. After closing the menu and resetting/rebooting the red arrow in the network applet has disappeared and wifi worked again (just in time)    .

I have no idea what caused the problem, and how to avoid it in future (or how to solve it in an easier way).

Hope this info is of some use for zauriers who run into the same problem.
Insomniux
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78162\"][{POST_SNAPBACK}][/a][/div]

[tinyrooster]

I am having the same problem with my wifi now and would like to try this maintance menu trick. Can anyone elaborate?

[egg8178]

Dear all,

Does anybody here know how to test the wifi hardware whether it's functioning?
I can connect to my AP just fine all these while, recently it just stopped working for me. I tried the D+P trick, selected the "CHECKWLAN" under the zaurus test, only with "wlan0 attach" displayed back to me.. nothing else

Is there anyother way to test the hardware? I even disabled all WEP and resetting the router, nothing work..

installing kismet and set up the adhoc network will change the mac address and shows connected with wifi lights flashing, but can't detect any network even when i'm standing right infront of the router..

please, help~

Thanks in advance.

[systemparadox]

Help... I have the same problem now. Cannot get the wifi light to come on or the device to show up in "ifconfi g -a".
"CHECKWLAN" blinks the wifi light and shows "wlan0 attach"- left for 15 minutes with no change.

How do you start the wifi in the console?
I've modprobed p80211 and prism2_usb, and they show up in lsmod, but seem to make no difference.

Any suggestions?

Thanks
Simon

[sdjf]

We've been talking about how to do this in another thread:

 https://www.oesf.org/forums/index.php?showtopic=21828

Sounds like many of these problems may be related to how qtopia sends messages to the network channel.  See my discussion at:

http://www.sdjf.wordpress.com/qtopia

And I strongly recommend getting a copy of qcoptest for your ROM that would enable you to see what messages are getting sent to Qtopia's Network channel.  I give it's home and download page urls and discuss a little at:

http://www.sdjf.esmartdesign.com/ipks/qcoptest.html

HTH,
sdjf

[speculatrix]

have you tried removing the battery AND turning off the backup battery too, leaving it for a few minutes and then turning on the backup battery and reinserting the main battery?

I am wondering whether some bit of hardware locked up and simply rebooting didn't clear the fault?

Any damage or dirt in the usb connectors?

[sdjf]

Another thing to try is to see if there is a lock file on your port.

What's the name of your log file?  On the early Sharp ROMs it was /tmp/qpe-pppd-log, and sometimes the very first line or two would give very important information.

If you can find the file, post it's first few lines showing what happens the next time it dies.

sdjf

[sdjf]

I just found out from a friend that,  on some ROMs, the log must be enabled by the user instead of automatically being created.

Look at  /etc/syslog.conf if you have no logfile created when you attempt a network connection, and remove the # sign on the line that probably looks like:

# local2.*    /tmp/qpe-pppd-log

If you want to be able to see the network log and have access to valuable debugging information about failures such as this.

You can also route the info to the console by removing the # sign on the line that looks like:

# local2.*    /dev/console

HTH,
sdjf