[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-27 Thread Ron3901
Thank you for the additional dirrection. [EMAIL PROTECTED]:~$ cat /proc/version_signature Ubuntu 2.6.27-9.19-generic [EMAIL PROTECTED]:~$ uname -a Linux ron-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux ** Attachment added: lspci-vvnn.log

[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-27 Thread 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. ** Attachment added: dmesg.log

[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-27 Thread 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. --

[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-27 Thread IanW
** Changed in: linux (Ubuntu) Sourcepackagename: None = linux Status: Incomplete = New -- Regression IBEX, no wireless since alpha 3 or 5 https://bugs.launchpad.net/bugs/301180 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-27 Thread IanW
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

[Bug 301180] Re: Regression IBEX, no wireless since alpha 3 or 5

2008-11-22 Thread IanW
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