On Wed, Feb 23, 2011 at 7:42 PM, Niels Mayer <[email protected]> wrote: > https://bugs.meego.com/show_bug.cgi?id=13778 > Bug 13778 - Wireless connection loses "router" setting for Static-IP > https://bugs.meego.com/show_bug.cgi?id=13780 > Bug 13780 - Wired connection stops working when transferring lots of data
According to the comments in the bugs, these issues are "hardware specific" and people aren't seeing this issue on their netbooks. However, my understanding is that the Lenovo S10-3t is a "reference platform" for MeeGo; therefore, testing should be done on this specific reference platform with its specific wireless interfaces: ath9k 65616 0 ath9k_common 1977 1 ath9k ath9k_hw 243231 2 ath9k,ath9k_common Anybody else having networking issues with the Lenovo S10-3t, or other netbooks with Atheros9K wireless drivers? I'm seeing the same kinds of problems in issues others have reported. This indicates the problem is more widespread than just a specific driver and points to some problems and instabilities in the applications and middleware layer: https://bugs.meego.com/show_bug.cgi?id=7529 https://bugs.meego.com/show_bug.cgi?id=11083 https://bugs.meego.com/show_bug.cgi?id=5202 Also, I set the issues I reported as "release blocker" because I don't think 1.2 should be released with networking not working correctly, unless we change the release name from "netbook" to "book" :-/ ; Alternately, if this isn't considered the "showstopper" that I believe it is, then the Lenovo S10-3t should be removed from the list of reference platforms for MeeGo 1.2, since the networking doesn't work correctly on the platform, either for wireless or wired connections. Niels http://nielsmayer.com PS: One hunch I have is that power-management is turning off the networking interfaces, even while they're being used. See, I rarely have a problem with a simple "outgoing connection" like browsing the web. The issue I'm seeing are with long-running connections, such as SSH sessions, SSH-based file transfers of 30gigs of media-files, etc. In fact, the network interface isn't visible to the outside world unless I make an outgoing conenction first (like browsing a web page). Then I can SSH in briefly before it appears like the network has disappeared again -- as if the networking hardware went to sleep between connections. Next time I reboot (which I don't like to do, because it's so iffy getting back online) I'll check the BIOS settings and see if the networking interfaces are being put to sleep to save power. At least on a desktop mobo (ASUS), such settings are available, I never even looked at the bios on the s10-3t to see if there's any obvious changes that need to be done before installing MeeGo. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
