New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qubes 3.2 and 4.9 kernel breaks Acer wifi #3222

Closed
dballard opened this Issue Oct 27, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@dballard

dballard commented Oct 27, 2017

Qubes OS version:

3.2 with the 4.9 kernel

Affected TemplateVMs:

dom0 fedora-24 net


Steps to reproduce the behavior:

Install updates and get 4.9 kernel, reboot

Expected behavior:

Wifi works

Actual behavior:

Wifi does not work
Using the command
rfkill list all
I can see that the wifi is hard off, and pressing fn-f3 (the wifi function button) as many times as I can changes nothing

General notes:

As per
https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill
it appears something is bad in the acer-wmi module, adding it to /etc/modules.d/blacklist.conf and rebooting solves the problem and wifi works again

It's an Atheros wifi chip in an Acer TravelMate 8172-6643 netbook

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 28, 2017

Member

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

Member

andrewdavidwong commented Oct 28, 2017

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment