8.04 Misidentifies Wirelesscard - AR242x

Bug #254972 reported by bass_girl09
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

1. Ubuntu 8.04
2. NA
3. This may get a little long winded, but bear with me. I have been trying to get the wireless to work with my Lenovo R61e Thinkpad (it works now) and when I typed into terminal lspci my wireless card was identified as an AR242x, but Windows identifies it as an AR5211...at least it got the driver manufacturer right. This has caused so many problems when I tried to get my wireless working...I have a thread that is 8pages long on ubuntu forums here http://ubuntuforums.org/showthread.php?t=873980 if you would like all of the code and information, at the end is a guide to get on wireless with an R61e Thinkpad so that other users will not have the same issues that I did...about page three is where it actually starts after I installed a fresh load of ubuntu, some of the old madwifi drivers just wouldn't quit haha. So, bottom line the Terminal said that my wireless card was an AR242x when it was in fact an AR5211 card. Thanks.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
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 . Thanks in advance!

Changed in linux:
status: New → Incomplete
Revision history for this message
bass_girl09 (bass-girl09) wrote :
Download full text (45.7 KiB)

1. output of 'uname -a':
melissafrench@melissafrench-laptop:~$ uname -a
Linux melissafrench-laptop 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux
melissafrench@melissafrench-laptop:~$
2.dmesg > dmesg.log output: yeilds nothing, no file of any kind it just seems to swallow the command...
   dmesg output is:
[ 18.308177] AppArmor: AppArmor initialized
[ 18.308181] Failure registering capabilities with primary security module.
[ 18.308188] Mount-cache hash table entries: 512
[ 18.308315] Initializing cgroup subsys ns
[ 18.308320] Initializing cgroup subsys cpuacct
[ 18.308331] CPU: After generic identify, caps: afebfbff 20100000 00000000 00000000 0000e31d 00000000 00000001 00000000
[ 18.308338] monitor/mwait feature present.
[ 18.308340] using mwait in idle threads.
[ 18.308344] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 18.308346] CPU: L2 cache: 1024K
[ 18.308348] CPU: After all inits, caps: afebfbff 20100000 00000000 00003940 0000e31d 00000000 00000001 00000000
[ 18.308357] Compat vDSO mapped to ffffe000.
[ 18.308370] Checking 'hlt' instruction... OK.
[ 18.324498] SMP alternatives: switching to UP code
[ 18.325995] Freeing SMP alternatives: 11k freed
[ 18.326088] Early unpacking initramfs... done
[ 18.650477] ACPI: Core revision 20070126
[ 18.650535] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 18.690275] CPU0: Intel(R) Celeron(R) CPU 540 @ 1.86GHz stepping 01
[ 18.690301] Total of 1 processors activated (3729.84 BogoMIPS).
[ 18.690486] ENABLING IO-APIC IRQs
[ 18.690689] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 18.835266] Brought up 1 CPUs
[ 18.835288] CPU0 attaching sched-domain:
[ 18.835291] domain 0: span 01
[ 18.835292] groups: 01
[ 18.835430] net_namespace: 64 bytes
[ 18.835437] Booting paravirtualized kernel on bare hardware
[ 18.835857] Time: 21:44:16 Date: 08/05/08
[ 18.835878] NET: Registered protocol family 16
[ 18.836044] EISA bus registered
[ 18.836049] ACPI: bus type pci registered
[ 18.836569] PCI: PCI BIOS revision 3.00 entry at 0xfde37, last bus=24
[ 18.836571] PCI: Using configuration type 1
[ 18.836579] Setting up standard PCI resources
[ 18.839893] ACPI: EC: EC description table is found, configuring boot EC
[ 18.843806] ACPI: BIOS _OSI(Linux) query honored via DMI
[ 18.844424] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 18.919719] ACPI: Interpreter enabled
[ 18.919721] ACPI: (supports S0 S3 S4 S5)
[ 18.919735] ACPI: Using IOAPIC for interrupt routing
[ 18.924830] ACPI: EC: GPE = 0x12, I/O: command/status = 0x66, data = 0x62
[ 18.924833] ACPI: EC: driver started in poll mode
[ 18.924961] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 18.926754] PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
[ 18.926759] PCI quirk: region 1180-11bf claimed by ICH6 GPIO
[ 18.928366] PCI: Transparent bridge - 0000:00:1e.0
[ 18.928504] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 18.928668] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT]
[ 18.928774] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
[ 18.928880] AC...

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ralph Janke (txwikinger) wrote :

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

Changed in linux:
status: Triaged → Incomplete
Revision history for this message
bass_girl09 (bass-girl09) wrote :

Yeah, it still misidentifies the chipset as AR242x in intrepid.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi bass_girl09,

Can you try installing the linux-backports-modules-intrepid package and see if it helps. Please let us know your results. Thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Amit Kucheria (amitk) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
importance: Medium → Undecided
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.