You are not logged in.
Hello team:
I am aware that this could be a hardware malfunction, but I do not know how to test that. I have this relative old (but powerfull) Asus laptop (N76V). It has a Broadcomm wifi chipset. Recently, it begin to fail, and my efforts to turn it up again don't seem to do anything. I have tried with iwconfig, ip, rfkill and systemctl, and they simply seem to quietly ignore the command. ip link show reports the device (wlp3s0) as DOWN (I am reproducing from memory, as right now it is functioning). rfkill reports the device (type wlan, device phy0) as unblocked, iwconfig reports the device (wlp3s0) as having no access point.
The laptop has a light supposedly reporting the wifi as "on".
Moyocoyani, Tloque Nahuaque.
Offline
Please post your complete system journal for a boot where this happened, eg.
sudo journalctl -b -1 | nc termbin.com 9999for the previous ("-1") one.
Offline
Web search results say that N76V does not have Broadcomm, should be Intel or Qualcomm Atheros?
But if is replaced later somehow, that's different issue.
Some of firmware packages recently updated, of course can try downgrading if possible (if dates match about when malfunction first happened).
I have not had any issues with any updated firmware packages. So it's probably not the reason..but I guess nothing to loose here.
Last edited by euromatlox (2026-11-16 21:48:07)
Offline
Well, if its my luck. Since I posted this it hasn't failed, so I haven't been able to post the info text that seth asked.
I haven't updated anything since I posted.
euromatlox is right, I must have thinking about other machine: the wifi antena is an Atheros, namely, after lspci:
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)Another weird think is that this machine, as far as I know, doesn't have bluetooth devices, but rfkill does report one:
ID TYPE DEVICE SOFT HARD
0 wlan phy0 desbloqueado desbloqueado
1 bluetooth hci0 desbloqueado desbloqueadoMoyocoyani, Tloque Nahuaque.
Offline
for the previous ("-1") one
You can access older journals, there's no necessity to wait for this to happen again.
Offline
Okey, it did happen again, so I can give you the journal:
https://paste.c-net.org/RuledCairo
I did use paste.c-net.org because I had now this weird error where
nc termbindidn't return any link, and I couldn't find help on it.
Moyocoyani, Tloque Nahuaque.
Offline
The wifi didn't "go down" but didn't show up itfp
nov 20 21:53:30 monstruona systemd[1]: Expecting device /sys/subsystem/net/devices/wlp3s0...
nov 20 21:54:59 monstruona systemd[1]: sys-subsystem-net-devices-wlp3s0.device: Job sys-subsystem-net-devices-wlp3s0.device/start timed out.
nov 20 21:54:59 monstruona systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlp3s0.
nov 20 21:54:59 monstruona systemd[1]: Dependency failed for WPA supplicant daemon (for interface wlp3s0).
nov 20 21:54:59 monstruona systemd[1]: wpa_supplicant@wlp3s0.service: Job wpa_supplicant@wlp3s0.service/start failed with result 'dependency'.
nov 20 21:54:59 monstruona systemd[1]: sys-subsystem-net-devices-wlp3s0.device: Job sys-subsystem-net-devices-wlp3s0.device/start failed with result 'timeout'.Reason is
nov 20 21:53:46 monstruona kernel: alx 0000:04:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [50:46:5d:df:79:f2]
nov 20 21:53:46 monstruona kernel: ath9k 0000:03:00.0: enabling device (0000 -> 0002)
nov 20 21:53:46 monstruona kernel: ath: phy0: Disable PLL PowerSave
nov 20 21:53:46 monstruona kernel: ath: phy0: Failed to read SREV register
nov 20 21:53:46 monstruona kernel: ath: phy0: Could not read hardware revisions
nov 20 21:53:46 monstruona kernel: ath: phy0: Unable to initialize hardware; initialization status: -95
nov 20 21:53:46 monstruona kernel: ath9k 0000:03:00.0: Failed to initialize device
nov 20 21:53:46 monstruona kernel: ath9k 0000:03:00.0: probe with driver ath9k failed with error -95nov 20 21:53:15 archlinux kernel: sda: sda1 sda2 sda5 sda6 sda7 sda9 sda10How many parallel windows installations are there?
(Trick question, if the answer isn't "0" see the) 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Edit: in case you tried to upload the journal from the bad boot
nov 20 21:54:02 monstruona dhcpcd[595]: no interfaces have a carrier
nov 20 21:54:02 monstruona dhcpcd[595]: enp4s0: waiting for carrier you'd still have required internet connection at that time ![]()
Last edited by seth (Today 09:56:48)
Offline