3945ABG cannot connect to WEP

[Ron3901]

The one fix in the IBEX release i wanted for use at home and it regresses :( really upset about it. thanks to all those that work to fix it.

2-Wire
Home Portal 1000HW

on a T61 thinkpad.

I had reported the bug under Gutsy, was asked if it was still an issue, and was asked to refile the bug report if the alpha 5 release didnt fix it, well here we are post alpha 5 and the problem persists.

I will say the wireless manager does it with more class now, as it dosn't actually connect, but it dosn't cause my router to reboot (power cycle) like it did under heron.

Damn.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[Ron3901 (ron3901)]

Thank you for the additional dirrection.

ron@ron-laptop:~$ cat /proc/version_signature
Ubuntu 2.6.27-9.19-generic

ron@ron-laptop:~$ uname -a
Linux ron-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

[Ron3901 (ron3901)]

ok thats retarded, I can only post one attachment at a time but you asked for four.

thanks again i look frward to a potential fix in the future, i haven't had stable wireless since gutsy, which is why i went to linux.

[Ron3901 (ron3901)]

And not to clutter this bug report with message after message of my own doing, but that dmesg output was after a fresh restart, but NM acted really weird, and the restart was one prompted by a update requiring restart. Hope that isn't an issue, but i will post another if you need so.

[Ian Weisser (ian-weisser)]

Thanks for the information.
According to the dmesg, Network Manager successfully associated, then disassociated, then reassociated, then redisassociated, then crashed.

So the next step is for you to take a look at the 'Debugging Crashes' section of https://wiki.ubuntu.com/DebuggingNetworkManager , and replicate the crash while the debugger is running.
1) Please attach the backtrace of the crash to this bug report.
2) Please attach the /var/log/syslog file showing the crash to this bug report.

Again, thanks in advance.

[Ron3901 (ron3901)]

OK, thanks for all the help, i havn't a clue what i have been doing nuts and bolts wise, but i did screw it up a few times process and order of operation wise, hope that didnt make the syslog too long.

[Ron3901 (ron3901)]

OK i did it again just to see if my lack of attention to detail played a part in too long a syslog. so i restarted and did the steps again,

[Ian Weisser (ian-weisser)]

Ah, the syslog shows the associating/disassociating - the first problem you mentioned. Good.
Syslog does not seem to show the crash, so that should be a separate bug if it ever recurs.

Assigning to package network-manager, edited title to describe the apparent problem.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release the Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.