uname -a
Linux Lat-Lap 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686
GNU/Linux
dmesg.log attached
lspci-vvnn.log attached
Where s the problem?
When I first tried Gusty Tribe 3 wireless worked. I could both, connect to
the internet without a patch cable connected to my laptop, and I could
single-left-click on the network manager icon in the notification area of
the top panel. Once clicked, it showed several wireless networks which were
available.
Since wireless had been a problem in Feisty I quickly looked at the
interfaces file and found wlan0 and wlan was shown correctly in the
network-manager application and if I did a iwconfig.
Now, there are no wireless networks show in the network manager icon in the
notification area...
iwconfig reports wireless on eth3 with a nickname of broadcom 4306
and I cannot connect if the cable is disconnected.
So... the problem is both!<smile>
I really think that the wlan0 versus eth3 is part of the problem.
Wish I could go back to that wonderful time when it started working. But
alas, I do not know how.
Thanx for working this.
zeddock
PS. Just looked into those files. Wow! You know what all that means?!
On 8/8/07, Brian Murray <email address hidden> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
> Please include as attachments the following additional information, if you
> have not already done so (please 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' 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. Additionally, it is not quite clear to me where the bug lies. Is it that
> your wireless connection is not called wlan0 or that you are unable to
> connect to a wireless network? Thanks in advance!
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Sourcepackagename: None => linux-source-2.6.22
> Assignee: (unassigned) => Brian Murray
> Status: New => Incomplete
>
> --
> Gusty updates broke my wireless connectivity
> https://bugs.launchpad.net/bugs/130511
> You received this bug notification because you are a direct subscriber
> of the bug.
>
uname -a
Linux Lat-Lap 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686
GNU/Linux
dmesg.log attached
lspci-vvnn.log attached
Where s the problem?
When I first tried Gusty Tribe 3 wireless worked. I could both, connect to
the internet without a patch cable connected to my laptop, and I could
single-left-click on the network manager icon in the notification area of
the top panel. Once clicked, it showed several wireless networks which were
available.
Since wireless had been a problem in Feisty I quickly looked at the
interfaces file and found wlan0 and wlan was shown correctly in the
network-manager application and if I did a iwconfig.
Now, there are no wireless networks show in the network manager icon in the
notification area...
iwconfig reports wireless on eth3 with a nickname of broadcom 4306
and I cannot connect if the cable is disconnected.
So... the problem is both!<smile>
I really think that the wlan0 versus eth3 is part of the problem.
Wish I could go back to that wonderful time when it started working. But
alas, I do not know how.
Thanx for working this.
zeddock
PS. Just looked into those files. Wow! You know what all that means?!
On 8/8/07, Brian Murray <email address hidden> wrote: /wiki.ubuntu. com/KernelTeamB ugPolicies. Additionally, it is not quite clear to me where the bug lies. Is it that /bugs.launchpad .net/bugs/ 130511
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
> Please include as attachments the following additional information, if you
> have not already done so (please 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' 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:/
> your wireless connection is not called wlan0 or that you are unable to
> connect to a wireless network? Thanks in advance!
>
> ** Changed in: linux-source-2.6.22 (Ubuntu)
> Sourcepackagename: None => linux-source-2.6.22
> Assignee: (unassigned) => Brian Murray
> Status: New => Incomplete
>
> --
> Gusty updates broke my wireless connectivity
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>