You are not logged in.
Pages: 1
Lenovo T410
LTS kernel.
I have TP-Link TL-WN772N wifi dongle.
When I do lsusb system can see it
It's:
Qualcomm Atheros Communications AR9271 802.11n
But when I do ip a there is only laptop Wi-Fi device. Even if I disable it with hardware switch.
I like to use inxi to list my hardware and Wi-Fi dongle is there:
Network: Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e v: 3.2.6-k port: 1820
bus ID: 00:19.0 chip ID: 8086:10ea
IF: enp0s25 state: down mac: <filter>
Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel port: 1880 bus ID: 03:00.0
chip ID: 8086:4238
IF: wlp3s0 state: up mac: <filter>
Device-3: Qualcomm Atheros AR9271 802.11n type: USB driver: usb-network bus ID: 1-1.1:9
chip ID: 0cf3:9271 serial: <filter>
I wanted to use this dongle inside Virtualbox guest with USB pass trough. On another computer (different host system) it works flawlessly but there is no build in Wi-Fi so may this is the reason. On my laptop with Arch as a host there is en error message in guest that says that usb can't be connecetd.
Last edited by 860lacov (2020-06-28 16:52:57)
Offline
Please post the complete system journal ("sudo journalctl -b") and "ip a" and rfkill output.
For clarification: we're only concerned w/ the host atm., are we?
Offline
Please post the complete system journal ("sudo journalctl -b") and "ip a" and rfkill output.
For clarification: we're only concerned w/ the host atm., are we?
journal:
-- Logs begin at Mon 2020-05-04 16:17:55 CEST, end at Tue 2020-06-23 11:42:58 CEST. --
cze 23 11:40:12 tango kernel: microcode: microcode updated early to revision 0x11, date = 2018-05-08
cze 23 11:40:12 tango kernel: Linux version 5.4.47-1-lts (linux-lts@archlinux) (gcc version 10.1.0 (GCC)) #1 SMP>
cze 23 11:40:12 tango kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts root=UUID=dea507c7-9c16-4bc7-bc>
cze 23 11:40:12 tango kernel: KERNEL supported cpus:
cze 23 11:40:12 tango kernel: Intel GenuineIntel
cze 23 11:40:12 tango kernel: AMD AuthenticAMD
cze 23 11:40:12 tango kernel: Hygon HygonGenuine
cze 23 11:40:12 tango kernel: Centaur CentaurHauls
cze 23 11:40:12 tango kernel: zhaoxin Shanghai
cze 23 11:40:12 tango kernel: x86/fpu: x87 FPU will use FXSAVE
cze 23 11:40:12 tango kernel: BIOS-provided physical RAM map:
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x00000000000d2000-0x00000000000d3fff] reserved
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bb27bfff] usable
cze 23 11:40:12 tango kernel: BIOS-e820: [mem 0x00000000bb27c000-0x00000000bb281fff] reserved
ip:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 5c:ff:35:0f:42:51 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet 192.168.43.44/24 brd 192.168.43.255 scope global dynamic noprefixroute wlp3s0
valid_lft 3422sec preferred_lft 3422sec
inet6 fe80::9983:676a:5873:734a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
rfkill:
ID TYPE DEVICE SOFT HARD
0 bluetooth tpacpi_bluetooth_sw aktywna nieaktywna
1 wlan phy0 nieaktywna nieaktywna
2 bluetooth hci0 aktywna nieaktywna
Offline
That's only the head of the journal - and it's capped.
See the tip in the first link in my signature.
Why are you using the lts kernel?
Offline
That's only the head of the journal - and it's capped.
See the tip in the first link in my signature.Why are you using the lts kernel?
About lts kernel. It's something like a habit. It was my first Arch install on hardware (not a virtual machine). To install Arch I used Arch wiki and I checked many tips just to be sure that I won't miss anything important. One of those tips was to use LTS.
Offline
cze 23 11:42:37 tango kernel: usb 1-1.1: USB disconnect, device number 3
cze 23 11:42:38 tango kernel: ath: phy1: Reading Magic # failed
cze 23 11:42:38 tango kernel: ath: phy1: Unable to initialize hardware; initialization status: -5
cze 23 11:42:38 tango kernel: ath: phy1: Unable to initialize hardware; initialization status: -5
cze 23 11:42:38 tango kernel: ath9k_htc: Failed to initialize the device
cze 23 11:42:38 tango kernel: usb 1-1.1: ath9k_htc: USB layer deinitialized
…
cze 23 11:47:16 tango kernel: ath9k_htc: Failed to initialize the device
cze 23 11:47:16 tango kernel: usb 1-1.1: ath9k_htc: USB layer deinitialized
For clarification: we're only concerned w/ the host atm., are we?
If this is the guest system, you're gonna need https://wiki.archlinux.org/index.php/Vi … nsion_pack to enable usb 2.0
Otherwise there's the less-than-promising https://bugzilla.kernel.org/show_bug.cgi?id=28492 from 2011 … and some kernel messages around 2013 about the chip and this error.
What's the host on the other system? Windows?
Offline
For clarification: we're only concerned w/ the host atm., are we?
If this is the guest system, you're gonna need https://wiki.archlinux.org/index.php/Vi … nsion_pack to enable usb 2.0
Otherwise there's the less-than-promising https://bugzilla.kernel.org/show_bug.cgi?id=28492 from 2011 … and some kernel messages around 2013 about the chip and this error.
What's the host on the other system? Windows?
This is Arch host.
Dongle is working without a problem on Manjaro (Manjaro LTS kernel) and Windows.
Last edited by 860lacov (2020-06-23 14:42:55)
Offline
Is this a dual boot system as well?
(In case see the 3rd link in my signature…)
Post the manjaro journal for comparism and try a different USB port. (compare "lsusb -tv" to see whether one system is on an usb2 and the other a usb3 port or so)
Offline
Is this a dual boot system as well?
(In case see the 3rd link in my signature…)Post the manjaro journal for comparism and try a different USB port. (compare "lsusb -tv" to see whether one system is on an usb2 and the other a usb3 port or so)
It is single boot system. I did tests on two other machines . One with windows and one with manjaro .
On windows I checked only scenario with linux as a guest machine.
On manjaro it's a single boot and manjaro is a host. And dongle works.
I'll upload manjaro journal but it will be next week.
Offline
It is a known regression in 5.4.47 (does also affect 5.7.3+):
https://bugzilla.kernel.org/show_bug.cgi?id=208251
Downgrading to an older version of the kernel should fix it until this gets resolved upstream.
Best regards
Johannes
Offline
It is a known regression in 5.4.47 (does also affect 5.7.3+):
https://bugzilla.kernel.org/show_bug.cgi?id=208251Downgrading to an older version of the kernel should fix it until this gets resolved upstream.
Best regards
Johannes
So if I did (quite recently) pacman -Scc then I'll have to wait till kernel upgrade or use ALA right?
Last edited by 860lacov (2020-06-25 13:43:02)
Offline
https://wiki.archlinux.org/index.php/Do … ux_Archive
The kernel is the only package that you can downgrade relatively safely in isolation (though watch out for kernel modules like the nvidia package etc.)
Edit: "yes"
Last edited by seth (2020-06-25 13:45:14)
Offline
I used automation way (downgrade from AUR).
Dongle is working.
And for the future. How Can I check if the problem is resolved?
I checked Bugzilla.
When I search there for AR9271 and then do sorting by date I can find
ath9k: broken after changes in 5.4.47
Do I have to check it every day just to be sure that I won't miss the resolution to the problem?
Or it will be published somewhere else and not on bugzilla?
Offline
If you have/create a kernel bugzilla account, you can CC yourself to the bug and get a mail when it's closed (what does not mean that the resolving kernel version is already in the arch repos)
Offline
On bugzilla one user said:
I can confirm it for TP-Link TL-WN722N:
Bus 001 Device 007: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
Reverting the commit solves the problem for 5.7.6-arch1-1.
What does it mean?
I can upgrade kernel and then somehow revert changes made only to atheros driver?
Offline
https://stackoverflow.com/questions/874 … nel-module
You will have to fetch and build at least part of the kernel sources and you should apply patch and config from https://git.archlinux.org/svntogit/pack … ages/linux
Then "patch -R" the bad patch.
You can use the kernel git repo, checkout the used version and git revert the bad commit, but the https://git.archlinux.org/svntogit/pack … ages/linux stuff still needs to be used.
Offline
Has anyone submitted the revert upstream https://lore.kernel.org/netdev/87lfkff9 … urora.org/ ?
Offline
Has anyone submitted the revert upstream https://lore.kernel.org/netdev/87lfkff9 … urora.org/ ?
It probably won't be surprise but I don't even understand what is in the link you gave. (what is important and what's not)
I wonder...
Is this a normal thing for Arch newbie to deal with problems like that?
Or maybe a little different question. Does Arch not newbies - maybe not admins but long term users know immediately how to solve problems like this?
Offline
I wonder...
Is this a normal thing for Arch newbie to deal with problems like that?
Random chance that a kernel module you use experienced a regression.
Or maybe a little different question. Does Arch not newbies - maybe not admins but long term users know immediately how to solve problems like this?
They could be expected to find downgrade link seth provided or patching packages.
Offline
Pages: 1