Kernel 2.6.27-11 in 8.10 has no WiFi support

[Karl Larsen]

        This bug is reported for the 8.10 version and is on the latest updated kernel which is "2.6.27-11 generic". It has been found that all the people using WiFi before getting this update were happy with it. I was one of them.

        On the Ubuntu technical list I asked when my WiFi quit why it did and a nice person said try booting with -9, the previous kernel. I did so and the wiFi started working again.

        Today I was asked to check all the meta things for version -11 and I did so and the backplain was not loaded. I loaded that and rebooted but it had no effect on the WiFi.

Karl Larsen

[Karl Larsen (klarsen1)]

Wouter Stomp wrote:
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
>
>
    How did you know that? I tried kernel 2.6.27-11 and it said error
not good. I think linux is kind of general in a big way too :-)

Karl

--

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

[TJ (tj)]

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!

[Karl Larsen (klarsen1)]

TJ 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!
>
>
3 data files added to the bug as requested. Thank you!

Karl

--

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

[TJ (tj)]

There are two ath5k module changes. I'll look into whether it is them that are causing this.

git log Ubuntu-2.6.27-9.19..Ubuntu-2.6.27-11.27 --pretty=format:"%h %ci %s" | grep ath5k
1e2bc95 2008-11-20 18:35:12 -0700 ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular
8875bb4 2008-11-20 18:35:12 -0700 ath5k: fix suspend-related oops on rmmod

[TJ (tj)]

There is also a change to mac80211 to fix a problem with ath9k that might cause this since both ath5k and ath9k depend on mac80211:

git log Ubuntu-2.6.27-9.19..Ubuntu-2.6.27-11.27 --pretty=format:"%h %ci %s" | egrep 'ath5k|mac80211'
1e2bc95 2008-11-20 18:35:12 -0700 ath5k: Fix reset sequence for AR5212 in general and RF5111 in particular
8875bb4 2008-11-20 18:35:12 -0700 ath5k: fix suspend-related oops on rmmod
dd65cef 2008-11-05 07:55:55 -0700 ath9k/mac80211: disallow fragmentation in ath9k, report to userspace

commit dd65cef34f8174db9e9353946cd06bc9d6ffe078
Author: Johannes Berg <email address hidden>
Date: Thu Oct 16 19:05:12 2008 +0000

    ath9k/mac80211: disallow fragmentation in ath9k, report to userspace

[TJ (tj)]

From dmesg.log:

[ 13.812844] ath_hal: module license 'Proprietary' taints kernel.
[ 13.814201] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 13.863078] wlan: 0.9.4
[ 13.876291] ath_pci: 0.9.4
[ 13.913152] ath_pci 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 13.913166] ath_pci 0000:02:00.0: setting latency timer to 64
[ 13.961656] wifi%d: unable to attach hardware: 'Hardware revision not supported' (HAL status 13)
[ 13.961668] ath_pci 0000:02:00.0: PCI INT A disabled
[ 14.212093] cfg80211: Using static regulatory domain info
[ 14.212096] cfg80211: Regulatory domain: US
[ 14.212098] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.212101] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 14.212103] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.212106] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.212108] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.212111] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 14.212113] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 14.212115] cfg80211: Calling CRDA for country: US
[ 14.359454] ath5k 0000:02:00.0: enabling device (0000 -> 0002)
[ 14.359463] ath5k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 14.359480] ath5k 0000:02:00.0: setting latency timer to 64
[ 14.359506] ath5k 0000:02:00.0: registered as 'phy0'
[ 14.369540] ath5k phy0: failed to wakeup the MAC Chip
[ 14.369555] ath5k 0000:02:00.0: PCI INT A disabled
[ 14.375044] ath5k: probe of 0000:02:00.0 failed with error -5

[TJ (tj)]

Notes:

We discussed this in #ubuntu-kernel on Friday (13th February 2009) and it looks as if the problem is related to blacklisting the 'madwifi' (ath_pci, ath_hal) driver (in the linux-restricted-modules package) to stop it conflicting.

[Karl Larsen (klarsen1)]

    Hi TJ, interesting. If there is anything else I can do to help
please write.

Karl

TJ wrote:
> Notes:
>
> We discussed this in #ubuntu-kernel on Friday (13th February 2009) and
> it looks as if the problem is related to blacklisting the 'madwifi'
> (ath_pci, ath_hal) driver (in the linux-restricted-modules package) to
> stop it conflicting.
>
>

--

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

[^_Pepe_^ (jose-angel-fernandez-freire)]

This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest Karmic 9.10 release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .

If the issue remains, could you run the following command from a
Terminal (Applications->Accessories->Terminal) while running Karmic. It
will automatically gather and attach updated debug information to this
report.

apport-collect -p linux 327237

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]