Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65152 - Interface wlan0 cannot be enabled

Attached to Project: Arch Linux
Opened by Marcel Walk (Nyasaki) - Wednesday, 15 January 2020, 22:00 GMT
Last edited by freswa (frederik) - Thursday, 20 February 2020, 22:01 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Interface wlan0 cannot be started after recent update. This issue occurs with the live iso too.

Additional info:
00:14.3 Network controller: Intel Corporation Device 9df0 (rev 30)
Subsystem: Intel Corporation Device 2034
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

Steps to reproduce:
Set interface wlan0 to up
This task depends upon

Closed by  freswa (frederik)
Thursday, 20 February 2020, 22:01 GMT
Reason for closing:  Upstream
Comment by loqs (loqs) - Wednesday, 15 January 2020, 23:50 GMT
What was in the update? What was the last working version?
What is the contents of dmesg from both a boot with and without the issue?
Comment by Doug Newgard (Scimmia) - Thursday, 16 January 2020, 00:37 GMT
Since setting it up does nothing, what's the real issue here?
Comment by Marcel Walk (Nyasaki) - Thursday, 16 January 2020, 15:18 GMT
@loqs
General updates I cannot remember what excactly since it were a lot of updates.
Currently no version is working for me I assume that the problem lies somewhere in the linux-firmware package.

dmesg seems to be fine before my attemt to start the interface.
After my try it tells me:
FW error in SYNC CMD SCAN_CFG_CMD and
iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
Comment by Marcel Walk (Nyasaki) - Thursday, 16 January 2020, 15:22 GMT
@Scimmia
The attemt to set it up does something, it throws a error.
The issue is my pc only can be connected via W-Lan so even installing Arch isnt possible for me since i cannot download anything.
The messages I get after the attempt to start the interface is in the screenshot I attached and in my comment above
Comment by loqs (loqs) - Thursday, 16 January 2020, 15:36 GMT
pacman logs to /var/log/pacman.log so you can identify which packages were updated and the versions before and after update.
The journal contains kernel messages, journalctl allows filtering to only kernel messages and for only one boot [1].
You can downgrade a package to a previous version in the pacman cache [2].
Do you have another system with functioning internet access you can post the requested outputs from?

[1] https://wiki.archlinux.org/index.php/Systemd/Journal#Filtering_output
[2] https://wiki.archlinux.org/index.php/Downgrading_packages#Using_the_pacman_cache
Comment by Marcel Walk (Nyasaki) - Thursday, 16 January 2020, 17:02 GMT
Sadly this problem just occurs only on my Matebook. On my ThinkPad its working fine.
So i dont have any system where I can post them from
Comment by loqs (loqs) - Friday, 17 January 2020, 15:15 GMT
I would suggest using the forums or other support methods to diagnose / triage the issue.
There is nothing actionable [1] [2] in the bug report or indication it is a packaging issue [3].

[1] https://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html
[2] http://www.catb.org/~esr/faqs/smart-questions.html
[3] https://wiki.archlinux.org/index.php/Bug_reporting_guidelines#Upstream_or_Arch?

Loading...