Author Topic: [SOLVED] atheros wless identified differently  (Read 2028 times)

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
[SOLVED] atheros wless identified differently
« on: March 24, 2011, 05:34:07 PM »
pclos 2009.1 on presarioCQ50 - not updated/can't update/cant upgrade

Wireless working fine in home network  for 6 mo using WPA

yesterday tried to connect at school network -no go
back home -no connect tried everything/deleted interface reset-no go

back at school tried 2009.1 Live CD - connected

Noticed wless adapter being identified differently by LiveCD and HD install (both same version)


wireless adapter in PCC
Code: [Select]
wireless adapter shows up in PCC (running LiveCD) as

Vendor: ‎Atheros Communications Inc.

Description: ‎AR242x 802.11abg Wireless PCI Express Adapter

Media class: ‎Ethernet controller

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎2

PCI device #: ‎0

PCI function #: ‎0

Vendor ID: ‎0x168c

Device ID: ‎0x001c

Sub vendor ID: ‎0x103c

Sub device ID: ‎0x137a

Misc
Module: ‎ath_pci
________________________________
Running on HD install as:

Identification
Vendor: ‎Atheros Communications Inc.

Description: ‎AR5001 Wireless Network Adapter

Media class: ‎Ethernet controller

Connection
Bus: ‎PCI

PCI domain: ‎0

Bus PCI #: ‎2

PCI device #: ‎0

PCI function #: ‎0

Vendor ID: ‎0x168c

Device ID: ‎0x001c

Sub vendor ID: ‎0x103c

Sub device ID: ‎0x137a

Misc
Module: ‎ath_pci


lspci
Quote
lspci

livecd-
[guest@localhost guest]$ lspci
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

hard disk-
[remoteuser@localhost remoteuser]$ lspci
CI Express Fast Ethernet controller (rev 02)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)


iwconfig
Code: [Select]
iwconfig-

livecd-
[guest@localhost guest]$ iwconfig
lo        no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:"XXXXX"  Nickname:"localhost"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:22:0C:27:FB:80
          Bit Rate:24 Mb/s   Tx-Power:16 dBm   Sensitivity=1/1
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=38/70  Signal level=-56 dBm  Noise level=-94 dBm
          Rx invalid nwid:26942  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

 hard drive-
[remoteuser@laptop ~]$ iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wifi0     no wireless extensions.

ath0      IEEE 802.11g  ESSID:"saki"  Nickname:"laptop"
          Mode:Managed  Frequency:2.452 GHz  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power:16 dBm   Sensitivity=1/1
          Retry:off   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=0/70  Signal level=-96 dBm  Noise level=-96 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
cat /etc/modprobe.preload

Code: [Select]
liveCD
[guest@localhost guest]$ cat /etc/modprobe.preload
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules
capability
yenta_socket
floppy
bttv
ohci1394
8250_pci
sdhci
mmc_core
mmc_block
slamr
amd64-agp
amd64_agp
amd64_agp
amd64_agp
nvram
intel_agp
evdev

hard drive-
[remoteuser@laptop ~]$ cat /etc/modprobe.preload
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with
# a `#', and everything on the line after them are ignored.
# this file is for module-init-tools (kernel 2.5 and above) ONLY
# for old kernel use /etc/modules
capability
yenta_socket
floppy
bttv
ohci1394
8250_pci
sdhci
mmc_core
mmc_block
slamr
amd64-agp
amd64_agp
amd64_agp
amd64_agp
nvram
intel_agp
evdev


cat /etc/sysconfig/network-scripts/ifcfg-ath0
Code: [Select]
[root@localhost network-scripts]# cat /etc/sysconfig/network-scripts/ifcfg-ath0
DEVICE=ath0
BOOTPROTO=dhcp
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=SCHOOL
WIRELESS_ENC_KEY=776972656c657373746563686e6f6c6f67796973746865746f6f6c666f726d65
WIRELESS_WPA_DRIVER=madwifi
IPV6INIT=no
IPV6TO4INIT=no
DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=yes
PEERYP=yes
PEERNTPD=no

hard drive-

[root@laptop remoteuser]# cat /etc/sysconfig/network-scripts/ifcfg-ath0
DEVICE=ath0
BOOTPROTO=dhcp
ONBOOT=yes
METRIC=35
MII_NOT_SUPPORTED=no
USERCTL=yes
RESOLV_MODS=no
WIRELESS_MODE=Managed
WIRELESS_ESSID=SCHOOL
WIRELESS_ENC_KEY=776972656c657373746563686e6fc6f67796973746865746f6f6c666f726d65
WIRELESS_WPA_DRIVER=madwifi
WIRELESS_WPA_REASSOCIATE=no
IPV6INIT=no
IPV6TO4INIT=no
DHCP_CLIENT=dhclient
NEEDHOSTNAME=no
PEERDNS=yes
PEERYP=yes
PEERNTPD=no

Quote
cat /etc/modprobe.d/blacklist

liveCD-

[guest@localhost guest]$ cat /etc/modprobe.d/blacklist
blacklist snd-usb-audio

blacklist ath5k
blacklist mac80211

hard drive-

[root@laptop remoteuser]# cat /etc/modprobe.d/blacklist
blacklist snd-usb-audio

blacklist ath5k
blacklist mac80211
blacklist ssb
blacklist hsfmodem
blacklist alsa-driver-linuxant

Postin from LiveCD so I know wless working, but why not from install. It was working fine for 6 mos.

Any help appreciated
Thanks



« Last Edit: March 27, 2011, 12:48:23 AM by Trio3b »

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #1 on: March 24, 2011, 05:48:41 PM »
Hi,

there has been a recent update about pciids, which explain the different device description, but it should be irrelevant because of the device identifiers are the same,
but there has been also a kernel-firmware update, which may be it's the source of your issue.

Try to identify the firmware file from liveCD: dmesg | grep firmware, and then check about the same file in installation in dir /lib/firmware.

AS

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #2 on: March 24, 2011, 05:52:41 PM »
[guest@localhost guest]$ dmesg | grep firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
aic94xx: Unknown symbol release_firmware
aic94xx: Unknown symbol request_firmware
ipr: Unknown symbol release_firmware
ipr: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
qla2xxx: Unknown symbol release_firmware
qla2xxx: Unknown symbol request_firmware

The HD install (one year ago) came from the very same  LiveCD  I am using to post this, and  I did not catch the 2009 repos before they got pulled so did no updating  /  upgrading
« Last Edit: March 24, 2011, 05:55:26 PM by Trio3b »

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #3 on: March 24, 2011, 05:54:33 PM »
and where did you get new description of the wireless device ?

AS

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #4 on: March 24, 2011, 05:59:03 PM »
From same LiveCD used to install ( about one year ago). I don't think I did any updates b/c I always test updates on an old Thinkpad before I do Anything to my daily lappy.

Updates went well on TP. Just as I was getting ready to update CQ50, YouCanToo lost 2009 repos so I don't think I touched original CQ50 install, but I distinctly remember wless has always been ID'd as AR5001. This is first time I ever see the other designation.

It's entirely possible I'm wrong about updating the CQ50 install but nothing pops out at me. I remember I was P O'd b/c I missed the 2009 repos.

Thanks
« Last Edit: March 24, 2011, 06:52:07 PM by Trio3b »

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #5 on: March 24, 2011, 06:23:57 PM »
used module look like to the same (ath_pci, identifiers look like the same, modules files doesn't show nothing relevant,
but in your post I don't see the line related to firmware loading:

from liveCD -> PCC -> System > Administrator console type the following commands:
service network stop
rmmod -f atk_pci
lsmod | grep atk_pci
modprobe atk_pci
dmesg | grep firmware
tail -30 /var/log/messages
service network restart

post here the output of the commands in bold

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #6 on: March 24, 2011, 06:46:57 PM »
[root@localhost guest]# service network stop
Shutting down interface ath0:                                   [  OK  ]
Shutting down interface eth0:                                   [  OK  ]
Shutting down loopback interface:                               [  OK  ]

[root@localhost guest]# rmmod -f atk_pci
ERROR: Removing 'atk_pci': No such file or directory
[root@localhost guest]# lsmod | grep atk_pci
[root@localhost guest]# modprobe atk_pci
FATAL: Module atk_pci not found.

[root@localhost guest]# dmesg | grep firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
aic94xx: Unknown symbol release_firmware
aic94xx: Unknown symbol request_firmware
ipr: Unknown symbol release_firmware
ipr: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
qla2xxx: Unknown symbol release_firmware
qla2xxx: Unknown symbol request_firmware

[root@localhost guest]# tail -30 /var/log/messages
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /dev/pts (and parents if necessary)
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: writing /etc/fstab
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda5 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda6 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda7 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory / (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /dev/pts (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created file /etc/fstab
Mar  9 05:53:05 localhost diskdrake[7339]: ### Program is exiting ###
Mar  9 05:53:09 localhost drakconf.real[7328]: modified file /etc/sysconfig/system
Mar  9 05:53:15 localhost kernel: kjournald starting.  Commit interval 5 seconds
Mar  9 05:53:15 localhost kernel: EXT3 FS on hda7, internal journal
Mar  9 05:53:15 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Mar  9 05:54:12 localhost kdm_greet[7548]: Can't open default user face
Mar  9 05:54:23 localhost net_applet[7791]: ### Program is starting ###
Mar  9 05:55:16 localhost drakconf.real[7888]: ### Program is starting ###
Mar  9 05:55:25 localhost drakxservices[7905]: ### Program is starting ###
Mar  9 05:55:25 localhost drakxservices[7905]: running: /sbin/chkconfig --list
Mar  9 05:55:25 localhost drakxservices[7905]: running: /sbin/chkconfig --list
Mar  9 05:55:30 localhost drakxservices[7905]: GP_LANG="UTF-8" service atd stop
Mar  9 05:55:35 localhost drakxservices[7905]: GP_LANG="UTF-8" service dkms stop
Mar  9 05:55:44 localhost drakxservices[7905]: GP_LANG="UTF-8" service anacron stop
Mar  9 05:55:50 localhost drakxservices[7905]: GP_LANG="UTF-8" service syslog stop
Mar  9 05:55:50 localhost kernel: Kernel logging (proc) stopped.
Mar  9 05:55:50 localhost kernel: Kernel log daemon terminating.
Mar  9 05:55:52 localhost exiting on signal 15

[root@localhost guest]# service network restart
Shutting down loopback interface:                               [  OK  ]
Bringing up loopback interface:                                 [  OK  ]
Bringing up interface ath0:  Error for wireless request "Set Encode" (8B2A) :
    SET failed on device ath0 ; Argument list too long.
                                                                [  OK  ]
Bringing up interface eth0:                                     [  OK  ]


Hope this helps

Thanks
« Last Edit: March 24, 2011, 07:10:53 PM by Trio3b »

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #7 on: March 24, 2011, 06:53:55 PM »
my bad, sorry, the module name is ath_pci not atk_pci:

used module look like to the same (ath_pci, identifiers look like the same, modules files doesn't show nothing relevant,
but in your post I don't see the line related to firmware loading:

from liveCD -> PCC -> System > Administrator console type the following commands:
service network stop
rmmod -f ath_pci
lsmod | grep ath_pci
modprobe ath_pci
dmesg | grep firmware
tail -30 /var/log/messages
service network restart

post here the output of the commands in bold

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #8 on: March 24, 2011, 07:25:15 PM »
[root@localhost guest]# service network stop
Shutting down interface ath0:                                   [  OK  ]
Shutting down interface eth0:                                   [  OK  ]
Shutting down loopback interface:                               [  OK  ]

[root@localhost guest]# rmmod -f ath_pci

[root@localhost guest]# lsmod | grep ath_pci

[root@localhost guest]# modprobe ath_pci

[root@localhost guest]# dmesg | grep firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
aic94xx: Unknown symbol release_firmware
aic94xx: Unknown symbol request_firmware
ipr: Unknown symbol release_firmware
ipr: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
libsas: Unknown symbol release_firmware
libsas: Unknown symbol request_firmware
qla2xxx: Unknown symbol release_firmware
qla2xxx: Unknown symbol request_firmware

[root@localhost guest]# tail -30 /var/log/messages
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /dev/pts (and parents if necessary)
Mar  9 05:53:04 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: writing /etc/fstab
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda5 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda6 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /mnt/hda7 (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory / (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /dev/pts (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created directory /proc (and parents if necessary)
Mar  9 05:53:05 localhost diskdrake[7339]: created file /etc/fstab
Mar  9 05:53:05 localhost diskdrake[7339]: ### Program is exiting ###
Mar  9 05:53:09 localhost drakconf.real[7328]: modified file /etc/sysconfig/system
Mar  9 05:53:15 localhost kernel: kjournald starting.  Commit interval 5 seconds
Mar  9 05:53:15 localhost kernel: EXT3 FS on hda7, internal journal
Mar  9 05:53:15 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Mar  9 05:54:12 localhost kdm_greet[7548]: Can't open default user face
Mar  9 05:54:23 localhost net_applet[7791]: ### Program is starting ###
Mar  9 05:55:16 localhost drakconf.real[7888]: ### Program is starting ###
Mar  9 05:55:25 localhost drakxservices[7905]: ### Program is starting ###
Mar  9 05:55:25 localhost drakxservices[7905]: running: /sbin/chkconfig --list
Mar  9 05:55:25 localhost drakxservices[7905]: running: /sbin/chkconfig --list
Mar  9 05:55:30 localhost drakxservices[7905]: GP_LANG="UTF-8" service atd stop
Mar  9 05:55:35 localhost drakxservices[7905]: GP_LANG="UTF-8" service dkms stop
Mar  9 05:55:44 localhost drakxservices[7905]: GP_LANG="UTF-8" service anacron stop
Mar  9 05:55:50 localhost drakxservices[7905]: GP_LANG="UTF-8" service syslog stop
Mar  9 05:55:50 localhost kernel: Kernel logging (proc) stopped.
Mar  9 05:55:50 localhost kernel: Kernel log daemon terminating.
Mar  9 05:55:52 localhost exiting on signal 15

[root@localhost guest]# service network restart
Shutting down loopback interface:                               [  OK  ]
Bringing up loopback interface:                                 [  OK  ]
Bringing up interface ath0:  Error for wireless request "Set Encode" (8B2A) :
    SET failed on device ath0 ; Argument list too long.
                                                                [  OK  ]
Bringing up interface eth0:                                     [  OK  ]

[root@localhost guest]# 

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #9 on: March 24, 2011, 07:43:29 PM »
maybe HD install lets kernel decide which module to use- but still it was working as AR5001.

Several threads talk about AR242x

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #10 on: March 24, 2011, 07:48:12 PM »
please try:

modinfo ath_pci

(this module is not present on current PCLinuxOS)

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #11 on: March 24, 2011, 07:50:26 PM »
maybe HD install lets kernel decide which module to use- but still it was working as AR5001.

Several threads talk about AR242x

Your reports are actually showing that ath_pci is the module currently configured and working in your liveCD, and the same is configured but not working on HD install.

Offline AS

  • Hero Member
  • *****
  • Posts: 4111
  • Have a nice ... night!
Re: atheros wless identified differently
« Reply #12 on: March 24, 2011, 08:07:12 PM »
maybe HD install lets kernel decide which module to use- but still it was working as AR5001.

Several threads talk about AR242x


Your first message:
Quote
yesterday tried to connect at school network -no go
back home -no connect tried everything/deleted interface reset-no go

other than names, HD install currently connect or not ?

smcs_steve

  • Guest
Re: atheros wless identified differently
« Reply #13 on: March 24, 2011, 11:32:01 PM »
Did you try ath9k ?
>Steve

some scribbled notes from way back when!>
Ath9k wireless>
From testing repo> install kernel 2.6.32.2 > reboot >
in terminal as a root > $ modprobe ath9k
> in pcc configure wifi connection > reboot
> enjoy!

« Last Edit: March 24, 2011, 11:36:49 PM by _steve »

Offline Trio3b

  • Sr. Member
  • ****
  • Posts: 365
Re: atheros wless identified differently
« Reply #14 on: March 25, 2011, 12:14:52 AM »
OK, back home -noticed during boot something about madwifi (version can't read) already installed on this kernel . Force with blah. This gets me to think that maybe I did tinker with wifi packages, but still, it's been working.

OK, more important. boot says something about ath0 /etc/wpa_supplicant string too long. Opened the file (it is huge) and commenedt out two sections that contained WEP string that I originally tried. They are 64 digit strings that netapplet has been complaining is too long. School told me that they were accepting either WEP or WPA. Couldn't get WPA to work so tried long string in WEP and that's when complaining started.

Anyway, restarted x and am now connected and posting via HD install. I could post that file if interested.

Boot info still complains about madwifi version and some argument list too long but ath0 seems to be working. Can't wait for YouCanToo 2009 repos to be back up. I bet that's where my troubles lie.

Thanks