Or maybe not

[torquill]

I can't get the wireless connection up anymore. It keeps coming up with "TX timeout" errors a second or so after associating and starting the DHCP request... there's very little out there about this, except that I found a recent discussion on a kernel mailing list about it. Apparently it is a known bug, and they're still hashing out why it happens; the symptom is that the timeouts crop up after a random amount of time, or after reawakening a hibernated system. Not entirely sure that mine failing every time on startup is quite the same, but I'll keep looking.

Frustrating. This might be fixed in the next stable kernel -- but I keep thinking that it was working fine last night!

Comments

[foogod.livejournal.com]

Just a quick thought.. have you restarted your system since last night?

If so, it's possible there was something in the hardware being set up by the NDIS driver (before the 4K stacks screwed it up) which is required for stable operation, which isn't set now that the system is restarted..

[luna-torquill.livejournal.com]

I hadn't restarted it when the trouble started, no... I left it overnight with both interfaces up. eth1 was still up when I disconnected eth0 and tried to use the wireless, and couldn't connect to the server. The weird thing was that I could ping, but not ssh... I fiddled with it, and after a couple of ups and downs, and reloading the module, it has that timeout problem and can't even negotiate an IP. I haven't tried static yet.

I've rebooted since then (a website wedged my system by causing Firefox to gobble memory) and it's still the same problem.