OESF Portables Forum
Everything Else => Sharp Zaurus => Model Specific Forums => Distros, Development, and Model Specific Forums => Archived Forums => C1000/3x00 General discussions => Topic started by: xamindar on January 17, 2006, 08:45:20 am
-
If I suspend and then unsuspend my c3100 while it is connected to an access point networking doesnt work. the card still shows that it is connected to the ap in the network settings just that no data travels. I have to disconnect the card and then reconnect via the network applet to get it to work again.
Is this normal? I have tried two totally different wifi cards and the same thing happens with both.
My old 5600 always works right out of suspend. I notice that the wifi card's led blinks for a few seconds on my 5600 when i unsuspend it whereas the c3100 just brings the light on steady. No reinitialization?
Anyone have the same problem? Or know a fix? I am on the default japanese sharp rom with no english conversion.
-
I've noticed something similar too. If the card is in before suspend, then after it can not connect. It also reports failure to eject the card when I try to remove it. A reboot of qtopia usually clears it. I just noticed it yesterday.
-
It's not that bad. I just need to disconnect it and reconnect it to my AP to get it to work again.
Does yours usually work fine after a supend other than those few times?
-
If I suspend and then unsuspend my c3100 while it is connected to an access point networking doesnt work. the card still shows that it is connected to the ap in the network settings just that no data travels. I have to disconnect the card and then reconnect via the network applet to get it to work again.
Is this normal? I have tried two totally different wifi cards and the same thing happens with both.
My old 5600 always works right out of suspend. I notice that the wifi card's led blinks for a few seconds on my 5600 when i unsuspend it whereas the c3100 just brings the light on steady. No reinitialization?
Anyone have the same problem? Or know a fix? I am on the default japanese sharp rom with no english conversion.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111279\"][{POST_SNAPBACK}][/a][/div]
i just wrote a little script
#!/bin/bash
cardctl eject 0
sleep 2
cardctl insert 0
and put that in /usr/bin/cardreinsert.sh
and setup an icon in Network section in qpe "card restart"
JavaHack
-
i just wrote a little script
#!/bin/bash
cardctl eject 0
sleep 2
cardctl insert 0
and put that in /usr/bin/cardreinsert.sh
and setup an icon in Network section in qpe "card restart"
JavaHack
[div align=\"right\"][a href=\"index.php?act=findpost&pid=111779\"][{POST_SNAPBACK}][/a][/div]
Thanks I'll give it a try. But this way I still have to do something, I might as well stick with reconnecting to my AP. The network should continue to work right out of suspend just like my old 5600 does, shouldn't it? Am I an isolated case? Maybe I should reflash the thing and see if that fixes it? I would rather not though.
I like the fact that Sharp fixed the new rom so the time settings don't open up when I accidently click on the time in the task bar. But having network broken after a resume from suspend is a huge backstep.
-
Also, if I pull out the wireless card while it is connected the zaurus just hard locks and I have to reset it. Is this really normal? Maybe it is a problem with tetsu's kernel.
-
I have no problems. If suspend and then resume, the network just gets reestablished sometimes and if not, I just disconnect and reconnect. I only get your symptoms if I just pull out the card while connected to the network which is something that shouldn't be done anyway, so I was being bad and had to reset it.
-
I have a somewhat similar problem: I can only connect once per card insertion. If I disconnect I have to eject the card and replace it (or "cardctl eject 0; cardctl insert 0") before I can connect again, otherwise I just get "Network offline". Sometimes the connection is just lost as well, requireing the stated procedure before reconnection is possible. If I suspend the connection is still around when the Z wakes up though.
-
well I had another episode where it did the same thing and it turns out cardmgr died. Once I started it back up, things were cool. I was even able to suspend and resume without any problems. I wonder if cacko uses a different cardmgr or maybe uses some special switches (I just started cardmgr with no options).
-
Cacko 1.23 heavy here on an sl-c1000........and I always have to physically eject my Prism based card before suspending. If I don't it'll take forever telling me it's trying to connect, never does, and then I have to reboot, eject physically the card, then restart and insert the card again.
Something seems to be wrong somewhere.
-
I have the same problems with both my Belkin WIFi card and my Sandisk ConnectPlus on C1000 with Cacko 1.23. It's a real irritation.
Cacko 1.23 heavy here on an sl-c1000........and I always have to physically eject my Prism based card before suspending. If I don't it'll take forever telling me it's trying to connect, never does, and then I have to reboot, eject physically the card, then restart and insert the card again.
Something seems to be wrong somewhere.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115018\"][{POST_SNAPBACK}][/a][/div]
-
you cacko users are the ones having problems, notice meanie and I don't?
-
ummm..yep figured it was a cacko issue from the start.
-
you cacko users are the ones having problems, notice meanie and I don't?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115024\"][{POST_SNAPBACK}][/a][/div]
I wouldn't generalise it as a Cacko issue.
If you read xamindar's initial post he was on the default Sharp rom.
My Sony wifi card which I couldn't get the default ROM to even detect (but worked on my old C860 default ROM) works flawlessly on Cacko.
-
Yep! both have advantages and disadvantages.
-
you cacko users are the ones having problems, notice meanie and I don't?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115024\"][{POST_SNAPBACK}][/a][/div]
I wouldn't generalise it as a Cacko issue.
If you read xamindar's initial post he was on the default Sharp rom.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115029\"][{POST_SNAPBACK}][/a][/div]
It is a cacko issue. My first post was a completely different problem. On the sharp rom the whole Z hard locks if I eject a connected card and the network would not work after a suspend (but it was still showing as connected). These problems weren't show stoppers but they were annoyances that prevented me from being lazy and ejecting the card without disconnecting.
Now the cacko problem is entirely different. I can only connect once and will not be able to connect to a network again unless I reinsert the card. But the problems I had with the sharp rom above are all gone now. The cacko problem can be worked around by typing "cardctl reset" in a console so it isn't that bad. Sence so many people are having this problem it must be a bug.