Updates ruin the wireless connect on Jaunty

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!

Philip Muskovac wrote:
> 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!
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
>
    Hello Phil, I got the three files on the launchpad at last :-)

I thought I was smart to put all three in a directory and upload that.
It does not work. Also tried w/o giving the world permission to read and
write. That just added to the fun :-)

Karl

--

 Karl F. Larsen, AKA K5DI
 Linux User
 #450462 http://counter.li.org.
   PGP 4208 4D6E 595F 22B9 FF1C ECB6 4A3C 2C54 FE23 53A7

I am looking for non-kernel problems and I draw your attention to the lspci from Jaunty. I have looked and the wireless hardware is NOT listed! On the same laptop I have 8.10 running and it gets wireless just fine.
Attached is the lspci from 8.10 and notice it lists an Atheros wireless and it says the ath driver is in the kernel.

It is my opinion the kernel is fine and we need to figure out why Jaunty will not use the wireless hardware.

   I deleted the Jaunty with 240 upgrades and re-loaded my Jaunty-beta and got quite a few updates while reloading when apt was loaded. I had wireless working on the LiveCD at this time. I got joe and thunderbird without problem and after 6 reboots the wireless continues to work! Here is the lspci -vvnn that I took after several reboots without the updates.

Looking at the attachments in this bug report, I noticed that "This is the kernel data requested." was flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug, since this was not one I've unchecked the patch flag for it. In the future keep in mind the definition of a patch. You can learn more about what qualifies as a patch at https://wiki.ubuntu.com/Bugs/Patches. Thanks!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Philip Muskovac wrote:
> ** Changed in: network-manager (Ubuntu)
> Status: Incomplete => New
>
 Well I can not help you. I have Jaunty on my laptop with every update
to yesterday and the WiFi is still perfect! But I did ditch network
manager and replaced it with Wicd. This is a superior software. Use it!

73 Karl

- --

 Karl F. Larsen, AKA K5DI
 Linux User
 #450462 http://counter.li.org.
        Key ID = 3951B48D

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKUr6zNuSIOjlRtI0RAhuNAJ4t32AhbeE0n1CfgzEn+ba8CLSkmQCgtryI
fewGgi3GgvfBB/XzgvdAFrQ=
=Mk7U
-----END PGP SIGNATURE-----

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 wrote:
> 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.
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Low
>
  Hi Pedro, I am now d/l Karmic Kola Alfa 5 PC(intelx86)desktop CD to
the same laptop that had the network manager problem with 9.04. Whether
wireless works or not, I will report at least the things I did last time.

Best Wishes Karl

--

 Karl F. Larsen, AKA K5DI
 Linux User
 #450462 http://counter.li.org.
         Key ID = 3951B48D

  Well I have Karmic installed on the laptop. When I was using the LiveCD I got the network manager working just fine after giving it the password for the wireless router. It was working while Karmic was loading and when apt was loaded it got about 5 minutes of updates from mirrors.

   When I got it up on the laptop hard drive, the wireless was not working. I clicked on the two monitor images and it came up wanting me to select which wireless signal to use (I have 3 that could be used). I selected my own and it asked for my password to the wireless router. I gave it that (nitalarsen) and then it put up another panel called a Key-chain!

   The Key-chain was new to me when I was doing 9.04 but since then I have learned to encrypt my emails to companies I am an owner. I am using pgp and the Key-chain thing makes sense here. But for the life of me I see NO REASON for my wireless stuff to need a Key-chain. I think it is VERY stupid!

    I did give the Key-chain a password and it then worked and network manager worked and I got wireless Internet. I re-booted several times and after it came back up, no wireless. I had to click on the two monitor images and selected my router and then had to give my password for the Key-chain thing and it works again.

   In my opinion, this stupid Key-chain use with network manager might have been what caused the original bug with 9.04. I think this because I just got wicd and my problems with 9.04 vanished. My experience now with pgp encryption now causes me to know about Key-chain used as it should be.

   Proper operation of network manager I think is that it gets the password to work with the wireless router and it works. Reboot and it comes up using the password and your wireless is up and working. The addition of the Key-chain is a major error and should be removed.

Best Wishes Karl

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]