AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01) not working in Ubuntu 8.10

Asked by Jim Starr

Wireless adapter on VGN-NR120E sony laptop cant find driver

Still not able to find an ini file that the system wants

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
will (drummer4mds) said :
#1

the driver is on the laptop, if you installed a wifi package then you screwed up. i can fix that do you have a lan cable if so do this...

part one
( wireless problem solving specialist here )

Please first connect your network card to the wireless router using a LAN cable.

Then please follow this procedure (in order to gather troubleshooting info):

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following commands (copy-paste each line below to the Terminal then hit <enter> after each line)

sudo aptitude install hwinfo
hwinfo --netcard
sudo iwlist scanning
sudo lshw -C network
lspci -nn
lsusb
uname -a
dmesg | grep ound
dmesg | grep witch
iwconfig

Part Two

# Please try this Atheros driver installation procedure:

# First under System/Administration/HardwareDrivers, disable both the Atheros HAL and the Atheros wireless thing and then reboot.

# Then from a terminal type (press enter key after each line)

sudo aptitude update

sudo aptitude install build-essential subversion

cd ~

mkdir madwifi

cd madwifi

svn co https://217.24.1.142/madwifi/branches/madwifi-hal-0.10.5.6

cd madwifi-hal-0.10.5.6

make

sudo make install

sudo gedit /etc/modules

# Now add the Atheros kernel module ath_pci to the list of modules to be automatically loaded at boot by adding

ath_pci

# to the end of the /etc/modules file. (Gedit editor automatically opens)

sudo gedit /etc/modprobe.d/blacklist

# Now add the following line at the end of the /etc/modprobe.d/blacklist file:

ndiswrapper

Now you can reboot and reactivate your wireless driver and reboot again and it should work.

Hope this helps,

Regards,

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#2

Hi,

It is too early to tell if you need the madwifi drivers or not. It depends on the wireless chipset you are using.

Please first connect your network card to the wireless router using an ethernet cable (also known as a LAN cable).

In order to gather essential troubleshooting information about your wireless card, please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following commands (copy-paste each line below to the Terminal then hit <enter> after each line)

sudo aptitude install hwinfo
hwinfo --netcard
sudo iwlist scanning
sudo lshw -C network
lspci -nn
lsusb
uname -a
dmesg | grep ound
dmesg | grep witch
iwconfig

Step 3: Please post results (copy/paste terminal output from each command) on this thread

Regards,

Mark

Revision history for this message
Jim Starr (jimmiestarr) said :
#3

Here is the results:

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

jim@ubuntu:~$ sudo aptitude install hwinfo
[sudo] password for jim:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Initializing package states... Done
Writing extended state information... Done
The following NEW packages will be installed:
  hwinfo libhd14{a}
0 packages upgraded, 2 newly installed, 0 to remove and 226 not upgraded.
Need to get 717kB of archives. After unpacking 1978kB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Get:1 http://us.archive.ubuntu.com intrepid/universe libhd14 14.19-2ubuntu1 [672kB]
Get:2 http://us.archive.ubuntu.com intrepid/universe hwinfo 14.19-2ubuntu1 [44.7kB]
Fetched 717kB in 2s (269kB/s)
Selecting previously deselected package libhd14.
(Reading database ... 86425 files and directories currently installed.)
Unpacking libhd14 (from .../libhd14_14.19-2ubuntu1_i386.deb) ...
Selecting previously deselected package hwinfo.
Unpacking hwinfo (from .../hwinfo_14.19-2ubuntu1_i386.deb) ...
Processing triggers for man-db ...
Setting up libhd14 (14.19-2ubuntu1) ...

Setting up hwinfo (14.19-2ubuntu1) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done

jim@ubuntu:~$ hwinfo --netcard
10: PCI 600.0: 0282 WLAN controller
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_168c_1c
  Unique ID: vTuk.WtwmchAxg+A
  Parent ID: hoOk.0O_DsNnPKTD
  SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:06:00.0
  SysFS BusID: 0000:06:00.0
  Hardware Class: network
  Model: "Atheros AR242x 802.11abg Wireless PCI Express Adapter"
  Vendor: pci 0x168c "Atheros Communications, Inc."
  Device: pci 0x001c "AR242x 802.11abg Wireless PCI Express Adapter"
  SubVendor: pci 0x105b "Foxconn International, Inc."
  SubDevice: pci 0xe000
  Revision: 0x01
  Features: WLAN
  Memory Range: 0xfa000000-0xfa00ffff (rw,non-prefetchable,disabled)
  IRQ: 18 (no events)
  Module Alias: "pci:v0000168Cd0000001Csv0000105Bsd0000E000bc02sc00i00"
  Driver Info #0:
    Driver Status: ath_pci is active
    Driver Activation Cmd: "modprobe ath_pci"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #21 (PCI bridge)

11: PCI 200.0: 0200 Ethernet controller
  [Created at pci.310]
  UDI: /org/freedesktop/Hal/devices/pci_11ab_4353
  Unique ID: rBUF.6jcu8J_XFvA
  Parent ID: z8Q3.yjCEx5JbDxB
  SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Marvell 88E8039 PCI-E Fast Ethernet Controller"
  Vendor: pci 0x11ab "Marvell Technology Group Ltd."
  Device: pci 0x4353 "88E8039 PCI-E Fast Ethernet Controller"
  SubVendor: pci 0x104d "Sony Corporation"
  SubDevice: pci 0x902d
  Revision: 0x14
  Driver: "sky2"
  Driver Modules: "sky2"
  Device File: eth0
  Memory Range: 0xf6000000-0xf6003fff (rw,non-prefetchable)
  I/O Ports: 0x2000-0x2fff (rw)
  IRQ: 220 (8202 events)
  HW Address: 00:1a:80:1a:20:0e
  Link detected: yes
  Module Alias: "pci:v000011ABd00004353sv0000104Dsd0000902Dbc02sc00i00"
  Driver Info #0:
    Driver Status: sky2 is active
    Driver Activation Cmd: "modprobe sky2"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #23 (PCI bridge)
jim@ubuntu:~$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

pan0 Interface doesn't support scanning.

jim@ubuntu:~$ sudo lshw -C network
  *-network
       description: Ethernet interface
       product: 88E8039 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 14
       serial: 00:1a:80:1a:20:0e
       size: 100MB/s
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.22 duplex=full firmware=N/A ip=192.168.1.108 latency=0 link=yes module=sky2 multicast=yes port=twisted pair speed=100MB/s
  *-network UNCLAIMED
       description: Ethernet controller
       product: AR242x 802.11abg Wireless PCI Express Adapter
       vendor: Atheros Communications Inc.
       physical id: 0
       bus info: pci@0000:06:00.0
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
  *-network DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: pan0
       serial: 0e:c4:0f:4e:73:6e
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes
jim@ubuntu:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03)
00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03)
00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03)
00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 03)
02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller [11ab:4353] (rev 14)
06:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
08:03.0 CardBus bridge [0607]: Texas Instruments PCIxx12 Cardbus Controller [104c:8039]
08:03.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a]
08:03.2 Mass storage controller [0180]: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [104c:803b]
jim@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c044 Logitech, Inc. LX3 Optical Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jim@ubuntu:~$ uname -a
Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux
jim@ubuntu:~$ dmesg | grep ound
[ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[ 0.000000] found SMP MP-table at [c00f8090] 000f8090
[ 0.760126] pnp: PnP ACPI: found 10 devices
[ 1.777775] pcieport-driver 0000:00:1c.0: found MSI capability
[ 1.778145] pcieport-driver 0000:00:1c.1: found MSI capability
[ 1.778512] pcieport-driver 0000:00:1c.2: found MSI capability
[ 2.133334] isapnp: No Plug & Play device found
[ 2.190667] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 3.012259] hub 1-0:1.0: USB hub found
[ 3.085717] No dock devices found.
[ 3.116688] hub 2-0:1.0: USB hub found
[ 3.217675] hub 3-0:1.0: USB hub found
[ 3.344312] hub 4-0:1.0: USB hub found
[ 3.553408] hub 5-0:1.0: USB hub found
[ 3.760691] hub 6-0:1.0: USB hub found
[ 3.864644] hub 7-0:1.0: USB hub found
[ 13.854975] Yenta: CardBus bridge found at 0000:08:03.0 [104d:902d]
[ 13.927071] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
[ 16.127723] lp: driver loaded but no devices found
[ 24.113323] apm: BIOS not found.
jim@ubuntu:~$ dmesg | grep witch
[ 0.638570] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 0.768045] Switched to high resolution mode on CPU 0
[ 0.768494] Switched to high resolution mode on CPU 1
[ 12.837087] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
[ 12.838148] ACPI: Lid Switch [LID0]
jim@ubuntu:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

pan0 no wireless extensions.

jim@ubuntu:~$

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#4

Hi Jim,

Will correctly guessed your wireless chipset and chose the right solution:

# Please try this Atheros driver installation procedure:

# First under System/Administration/HardwareDrivers, disable both the Atheros HAL and the Atheros wireless thing and then reboot.

# Then from a terminal type (press enter key after each line)

sudo aptitude update

sudo aptitude install build-essential subversion

cd ~

mkdir madwifi

cd madwifi

svn co https://217.24.1.142/madwifi/branches/madwifi-hal-0.10.5.6

cd madwifi-hal-0.10.5.6

make

sudo make install

sudo gedit /etc/modules

# Now add the Atheros kernel module ath_pci to the list of modules to be automatically loaded at boot by adding

ath_pci

# to the end of the /etc/modules file. (Gedit editor automatically opens)

sudo gedit /etc/modprobe.d/blacklist

# Now add the following line at the end of the /etc/modprobe.d/blacklist file:

ndiswrapper

Now you can reboot and it should work.

Hope this helps,

Regards,

Mark

Revision history for this message
Jim Starr (jimmiestarr) said :
#5

Nothing seemed to happen...is there another step...what do i use to
configure wireless...new to linux

On Wed, Mar 25, 2009 at 12:52 AM, Mark Rijckenberg <
<email address hidden>> wrote:

> Your question #65123 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/65123
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Hi Jim,
>
> Will correctly guessed your wireless chipset and chose the right
> solution:
>
> # Please try this Atheros driver installation procedure:
>
> # First under System/Administration/HardwareDrivers, disable both the
> Atheros HAL and the Atheros wireless thing and then reboot.
>
> # Then from a terminal type (press enter key after each line)
>
> sudo aptitude update
>
> sudo aptitude install build-essential subversion
>
> cd ~
>
> mkdir madwifi
>
> cd madwifi
>
> svn co https://217.24.1.142/madwifi/branches/madwifi-hal-0.10.5.6
>
> cd madwifi-hal-0.10.5.6
>
> make
>
> sudo make install
>
> sudo gedit /etc/modules
>
> # Now add the Atheros kernel module ath_pci to the list of modules to be
> automatically loaded at boot by adding
>
> ath_pci
>
> # to the end of the /etc/modules file. (Gedit editor automatically
> opens)
>
> sudo gedit /etc/modprobe.d/blacklist
>
> # Now add the following line at the end of the /etc/modprobe.d/blacklist
> file:
>
> ndiswrapper
>
> Now you can reboot and it should work.
>
> Hope this helps,
>
> Regards,
>
> Mark
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/65123/+confirm?answer_id=3
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/65123
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#6

Hi,

After following the madwifi procedure and rebooting the pc, I think you just
need to connect using the NetworkManager icon, which is in the top right
corner of the Ubuntu desktop.

See the link below for a screenshot of the NetworkManager icon:

http://en.wikipedia.org/wiki/NetworkManager

Right-click on the Networkmanager icon and then choose the wireless
network you want to connect to. You might need to create a new
connection on eth1 or wlan0 first, or click on "edit network connection"
to see the list of available networks.

Regards,

Mark

Revision history for this message
Jim Starr (jimmiestarr) said :
#7

Thanks that worked

On Wed, Mar 25, 2009 at 2:10 AM, Mark Rijckenberg <
<email address hidden>> wrote:

> Your question #65123 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/65123
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Hi,
>
> After following the madwifi procedure and rebooting the pc, I think you
> just
> need to connect using the NetworkManager icon, which is in the top right
> corner of the Ubuntu desktop.
>
> See the link below for a screenshot of the NetworkManager icon:
>
> http://en.wikipedia.org/wiki/NetworkManager
>
> Right-click on the Networkmanager icon and then choose the wireless
> network you want to connect to. You might need to create a new
> connection on eth1 or wlan0 first, or click on "edit network connection"
> to see the list of available networks.
>
> Regards,
>
> Mark
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/65123/+confirm?answer_id=5
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/65123
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#8

Hi,

Glad it worked out. :-) If this issue is solved, can you please set the thread to status "solved"?

Regards,

Mark

Revision history for this message
PhilF (philfreedman) said :
#9

I stumbled upon this thread while looking for a answer to similar problem with new Asus Eee PC 1000HA. Followed Will's intructions exactly (not having a clue what I was doing) and came to the happy ending of my computer now connecting to my home network perfectly. I don't know where you guys get this knowledge, but thank you for responding to those of us with little technical know how!

Can you help with this problem?

Provide an answer of your own, or ask Jim Starr for more information if necessary.

To post a message you must log in.