-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Attach BCM43602 to a VM cause system freeze and shutdown #3734
Comments
Based on our issue reporting guidelines, this appears to be too localized for |
If a search engine will bring you here, then here is what helped me to make BCM43602 work again on my MacBookPro14,3 (mid-2017).
Enjoy your Wifi card at its full speed! 2.4GHz & 5GHz wifi networks are working :-) The Make sure to set Refs.
I've also noticed that if I remove brcmfmac kernel driver from the sys-net (domU), and modprobe it back again => the card will never work. |
If that helps, it may be easier to:
I'd recommend checking for the mac address first, what really should be set there - if two users with the same mac address set meet, it will mean duplicated MAC address in the network, which basically means it won't work for either of them. |
I've tried booting with domU logs the first time 03:00.0 initializes there
Sometimes:
lspci tree
lspci of 03:00.0
PCI register configuration of 03:00.0
Before passing it to domU, the parameter
After which, I cannot make the 03:00.0 card working again.. tried removing it, pci bus rescanning it. It would never appear back again and only the reboot would help. Do you have any suggestions/ideas what else could I try so there is a way to restart I have been trying this script to perform a hot reset of the 1b.0-[03] (see above lspci tree), but without success. The card doesn't appear back again. |
That MAC address is in the firmware. Even if I do not set
There is also some interesting section |
First thing I'd check is what MAC address you see there. |
I have been tinkering more with the BCM43602 wireless adapter these days and have figured a way so I can restart
The whole trick was to unbind the parent PCI bridge off the
What's more interesting and is related to my previous observations is that if I don't unbind the parent PCI bridge off the
But as soon as I unbind the parent PCI bridge off the One more observation is that when I remove the BCM43602 adapter device Does this all make any sense, @marmarek ? 🤓 |
I see a different MAC address in macOS. So I've taken it from there and replaced the |
One more thing is that it seem to be impossible to attach any device using
Additionally, I had this question on my mind few days ago, is that there seem to be no way to pass |
I don't know what pcieport driver does on unbind...
Make sure
The strictreset is libvirt-only thing. xl doesn't care about missing reset. |
Thanks for the hint on
I there a way to make sure |
Adding these parameters didn't do any better. I've also tried adding the
|
Is anyone still working on this? None of the listed workarounds seem to work for me.
as reported similarly in a previous comment but I seem to have the problem from the first start of sys-net not only upon restart. |
This issue is being closed because:
If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment. |
Qubes OS version:
R4.0rc5
Affected component(s):
Steps to reproduce the behavior:
run
qvm-pci attach <vmname> <backend>:<bdf>
, I've tried every combination with permissive and no-strict-reset option.Expected behavior:
VM(especially
sys-net
) is attached to the adapter so I can make the wifi work.Actual behavior:
System freeze immediately when attach to a running VM or the VM attached to the adapter start, then shutdown after a few seconds.
General notes:
The system-freeze will happen in the setup step so I have to detach the adapter from the sys-net to finish installation.
Some one suggested to use
sudo xl pci-attach <vmname> <bdf>
to attach the adapter directly to a VM, the command seemed to work, butqvm-pci
shows that the adapter is still not used by any VM, and the network manager didn't show any wifi device.Related issues:
The text was updated successfully, but these errors were encountered: