Quote:
Originally Posted by grayfox
Ugh,
I spoke too soon.
I just rebooted and restarted wireless with dropbear.
I am lucky to get two or three commands before a lockup.
I have a "Ping" iLiad thingy that clears the stall, but who
wants to keep clicking the tablet every thirty seconds
|
I am having the very same problem although I don't know about fixing with pings. The symptoms are pretty similar:
I open a connection using either connectionMgr or wireless.sh (either directly or with alanine's scripts) with wpa encryption.
Then everything works well until I start doing something else on the GUI - like browse my books in the content lister. The more I browse, the more packages from my ping requests are dropped until at some point the connection is lost all toghether.
To me it seems like one of these 'issues with badly coded drivers which don't like having few cpu time' which Mathjes talked about a while ago.
But seriously, something is very wrong here and it is not the linux kernel. I had more stable lan connections on my 486dx2 with Windows 98. My iPAQ 3130 which doesn't have even half the computing power of an iLiad but had double the functionality (at least after I installed linux on it
was also a lot more stable.
I will do some further investigation on the correlation between system load and connection loss.
Just on a side note, for some reason wired.sh fails to open a wired connection. It brings up the ethernet device alright but the ethernet LED's on the travel hub aren't flashing and I can't ping into or out of the iLiad. Am I forgetting something?