[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-07-05 Thread dominic
I'm having this problem too, since around Wednesday 2nd July. For no reason (that I can see) wireless will drop, and sometimes reconnect, sometimes not. dmesg below. The part from eth1:disassociate through many eth1: RX disassociation back to eth1: associated repeats over and over. [11176.520580

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-05-08 Thread Hippoman
I have exactly the same lines on my logs, i can associate with my AP, but the performance of the wireless connection is very very bad, before updating to Hardy, i did have about 10 times the throughput i have now.., i think this bug should be reopened. -- iwl3945 does not associate in Hardy htt

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-22 Thread Greg Grossmeier
Closing bug as per discussion with the reporter in IRC. There will be a new bug about the actual underlying problem. Thanks! ** Changed in: linux (Ubuntu) Status: New => Invalid -- iwl3945 does not associate in Hardy https://bugs.launchpad.net/bugs/217809 You received this bug notificat

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-21 Thread Derek
Addendum. The reason I might not have noticed 'till hardy and blamed iwl3945 is that I may have initially suffered from other iwl3945 bugs - I believe my initial dmesg output was quite different. In working things over I ripped out my usage of hand-coded wpa-supplicant and switched it over to /

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-20 Thread Derek
This was an enormous waste of time. I'm not sure at what level the issue was, but it centred around having single quote and space in passphrase (which was a real phrase). When I removed these, and made passphrase pure alphanumeric, it worked fine. I only discovered this after switching to WEP and

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-20 Thread Derek
Still failing with linux-backports-modules-2.6.24-16-generic Restored the udev rule for the hell of it since it seemed to do nothing of any significance, but that's the reason it is "eth1" below. Results of ifup - a few new lines, but same old routine. [ 8692.475252] ADDRCONF(NETDEV_UP): eth1: l

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-19 Thread Bart Heinsius
linux-backports-modules-2.6.24-16-generic solved it for me. -- iwl3945 does not associate in Hardy https://bugs.launchpad.net/bugs/217809 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubun

[Bug 217809] Re: iwl3945 does not associate in Hardy

2008-04-15 Thread Bart Heinsius
I experience the same behaviour. -- iwl3945 does not associate in Hardy https://bugs.launchpad.net/bugs/217809 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu