Opened 7 years ago

Closed 13 months ago

#8922 closed bug (fixed)

Atheroswifi doesn't connect anymore

Reported by: humdinger Owned by: nobody
Priority: normal Milestone: R1
Component: Drivers/Network/atheroswifi Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

This is hrev44584.

I just updated my Samsung N10 netbook with hrev44584. listdev says:

device Network controller (Ethernet controller) [2|0|0]
  vendor 168c: Atheros Communications Inc.
  device 001c: AR242x / AR542x Wireless Network Adapter (PCI-Express)

Can't connect to my WPA2 encrypted network when it worked before (can't remember what revision that was, however). Attached is the syslog that keeps growing and growing...

Attachments (2)

syslog.txt (376.9 KB) - added by humdinger 7 years ago.
growing syslog
atheros-logs.txt (20.3 KB) - added by kallisti5 4 years ago.

Download all attachments as: .zip

Change History (12)

Changed 7 years ago by humdinger

Attachment: syslog.txt added

growing syslog

comment:1 Changed 7 years ago by humdinger

DeadYak mentioned #8362 on IRC, that looks a bit similar. I'd also like to add that the thread ic_taskq is blocking one cpu every other second.

comment:2 Changed 7 years ago by TN-048

I also have this problem as of hrevr1alpha4-44576. My listdev is:

device Network controller [2|80|0]
  vendor 168c: Atheros Communications Inc.
  device 002a: AR928X Wireless Network Adapter (PCI-Express)

On the first boot with a fresh image on a USB stick it works absolutely fine with WPA2. After rebooting on the stick, or booting from the HD it fails. When connecting to an unsecured network it works fine, however when attempting to connect to any WPA2 encrypted connection, it simply does nothing. It does work fine on my Acer Aspire One 532h netbook with the same WPA2 network (which has an atheros card).

Last edited 7 years ago by TN-048 (previous) (diff)

comment:3 Changed 7 years ago by jackburton

Can you try with a recent nightly ?

comment:4 in reply to:  3 Changed 7 years ago by TN-048

Replying to jackburton:

Can you try with a recent nightly ?

I tried with the most recent (02/02) Nightly and nothing changed. The exact same symptoms still exist.

comment:5 Changed 7 years ago by ASoftwareHatingFurry

I can confirm similar behaviour on my system with Alpha 4.1, the first boot (or few boots?) the Atheros WiFi was working, and then it stopped. I don't remember the exact circumstances, but it was already installed on the hard drive by that point. The drive is the netbook's internal mechanical hard drive, probably SATA, in case that is relevant. Intel Atom with Intel chipset. Other partitions besides Haiku are an NTFS partition and an Ext3 partition. WiFi is the netbook's internal WiFi card, Devices reports this as "AR242x / AR542x Wireless Network Adapter (PCI-Express), Atheros, device/type=2 device/subtype=0 device/interface=0 device/vendor=0x168c device/id=0x1c

Typing ifconfig up /dev/net/atheroswifi/0 restored operation, and it continued to work forever after even between reboots. I have not needed to re-type that line.

This forum thread might be related: http://www.haiku-os.org/community/forum/just_when_i_thought_things_were_looking_good

comment:6 Changed 6 years ago by humdinger

After quite some time, I have now tried a current image with that atheros netbook. With hrev45956 it works again. No connection problem and the syslog isn't growing anymore either. I suggest the other guys that have expressed issues in this ticket try too. I'll close this ticket in a few days if there's no negative feedback.

comment:7 Changed 4 years ago by kallisti5

AR242x no longer functional again as of hrev49491 x86_64. Lots of errors in syslog about "ath_chan_set: unable to reset channel X" hal status 3.

Changed 4 years ago by kallisti5

Attachment: atheros-logs.txt added

comment:8 Changed 4 years ago by kallisti5

I pulled the card out to swap it. The exact model is AR5BXB63

comment:9 Changed 14 months ago by waddlesplash

Please retest after hrev52093.

comment:10 Changed 13 months ago by humdinger

Resolution: fixed
Status: newclosed

Works with the old Samasung NC10 after the FreeBSD11 updates. Closing ticket. Other commenters have to re-test their hardware and open new tickets for their specific setup.

Note: See TracTickets for help on using tickets.