Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Andre Arapov, Thank you for the guide. I am attempting to replicate your results on my 14,3 Macbook Pro from a fresh install of Qubes4.1(built in mid May). I started by removing the wireless card 03:00.0 from sys-net in Qubes settings → Devices tab so that starting sys-net will not freeze the system. I am encountering an error when running “sudo xl pci-attach sys-net '03:00.0,permissive=1'” where Domain 1 is sys-net and the only other running domain is dom0. libxl: error: libxl_pci.c:1575:libxl__device_pci_add: Domain 1:PCI device :03:00.0 already assigned to a different guest? libxl: error: libxl_pci.c:1735:device_pci_add_done: Domain 1:libxl__device_pci_add failed for PCI device 0:3:0.0 (rc -1) libxl: error: libxl_device.c:1414:device_addrm_aocomplete: unable to add device I get this error despite "xl pci-assignable-list" showing 0003:00.0. I am not sure how it could already be assigned to a different guest because there are no others running. Am I doing something wrong? I even tried unbinding the pcieport by running “ echo :00:1c.0 | sudo tee /sys/bus/pci/drivers/pcieport/unbind” before I ran “sudo xl pci-attach sys-net '03:00.0,permissive=1'”? Any input would be appreciated. Thank you in advance, LinuxTom -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEQrH2d6g+R+ZjvOQ2QlvFAXINygUFAl7W46UACgkQQlvFAXIN ygW7VBAAncNa/K5PsvU1dzNE8H3MBSFTCBDIeOVNlgXGzppM7FXp8Pqnvj9XGJjE IGSRmjR6aYaj0sp1GOpvzNdXJpD/KO/xlXxNb3/uzUCrJGGYPkGxKq7jHxw1a6+J 5TJJfeISKEEDjXKnN3xz1E2b34z1Rx2TIWyOUNptz4NekkwBpZVUdWFde+cWq6nu /nVdu7jq8c4rxZVQ3Cs5DpG92SA1HIKrTH0QXCyGEh2yY6L0yZYOdj2j8XaV8g9F UDTelUFJyjM9sFgkqCTLM15jE3JhjuGpSeFQm5LhfCA9w3nF7fbgyDo3+f+PWPTH aHc+SktA1v4JvDhWHgF9z0g4/EpbYh6JbzyXvcScEIR23i3l00XGj+rwDkclchex 9/m+wSEgtVBgIy1pAFcHhzElNgBf76FMKDoa+fqJoHn0ZuokXBB0VQiPyzW8ZsYn NUiK1Aoe1hiW4HoQeXAnM4QtzwTVXsz14soMvnu/LaTLvJCxuklkXPDuncySb2sQ fquoDW/r+7atdc/XZ202Mi/r+T1byuop2oiToYZyAC1WzKLwZ2N/pBqXjLaoGOO6 ZQR43pow1ROxfxwFMg4THgJCowzwJcgy9LgWtrtsR18qjSatV6b3t129xxzVG8zV DzXyN31Sw/FUj0BAtdMwD1EH0BsrIk8uj9SiojhztLMeuuKsVnU= =boko -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/rVQAQtUiXZ8E_RlV7zRB4scGVY7KsQndtTyS0zm3255mNIjo0EXI5ngaN2YOwWEk9QoaZ5x_9duWDlNAp8XxV5PNtRzyIaNZrxrFBJ4mvCY%3D%40protonmail.ch.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 January 30, 2020 9:24 PM, "Andrey Arapov' via qubes-users" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi all, > > I've been having issues with making BCM43602 work and figured a sequence > which makes it working and > working well - meaning it connects to both 2.4GHz & 5GHz networks and is > working at its full speed > without any issue. > > Here is what helped me to make BCM43602 work again on my MacBookPro14,3 > (mid-2017). > > 1. start dom0 with ``qubes.skip_autostart``. > > 2. start ``sys-net`` in the following sequence: > > ``` > qvm-start sys-net > sleep 3 > sudo xl pci-attach sys-net '03:00.0,permissive=1' > qvm-run -p sys-net "sudo cp ~/brcmfmac43602-pcie.txt > /usr/lib/firmware/brcm/brcmfmac43602-pcie.txt" > qvm-run -p sys-net "echo 1 | sudo tee /sys/bus/pci/rescan" > ``` > > Enjoy your WiFi! > > The ``brcmfmac43602-pcie.txt`` file you can get here > https://bugzilla.kernel.org/show_bug.cgi?id=193121#c52 - see an "attachment > 285753" from Simon > Siebert on ``2019-11-02 16:41:15 UTC`` > > Make sure to set ``macaddr=00:90:4c:0d:f4:3e`` in that file! It's the default > mac address which is > coming from the firmware. > > Refs. > - - https://groups.google.com/forum/#!msg/qubes-users/DT_uIiiWJd8/cHFiFle1DQAJ > - - https://bugzilla.kernel.org/show_bug.cgi?id=193121#c52 > - - https://nixaid.com/linux-on-macbookpro > > Kind regards, > Andrey Arapov > > P.S. > 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 again. > I've tried resetting the PCI bus, removing the card, etc.. only reboot helps. > -BEGIN PGP SIGNATURE- > > iHUEARYIAB0WIQRDMZ/b1AtG/U4LjuKQdtXmsxrpnAUCXjM7VQAKCRCQdtXmsxrp > nKe2AP9EYxXcKGJ++NDlJta/DVT9mtSx6wvzfhLNKxBW+OfyOwEAxp9HN6umbCUD > vo5XYjB9Y31y5Noagb3K0s8sY45bzQI= > =5+io > -END PGP SIGNATURE- I have been tinkering more with the BCM43602 wireless adapter these days and have figured a way so I can restart ``sys-net`` without having to reboot. ``` $ sudo lspci -t -nn -v +-1c.0-[03]00.0 Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] ``` The whole trick was to **unbind** the parent PCI bridge off the ``pcieport`` (PCI Express Port Bus Driver), after which I could [restart](https://github.com/QubesOS/qubes-issues/issues/3734#issuecomment-580440403) ``sys-net`` as many times as I want without breaking BCM43602 adapter: ``` echo :00:1c.0 | sudo tee /sys/bus/pci/drivers/pcieport/unbind ``` What's more interesting and is related to [my previous observations](https://github.com/QubesOS/qubes-issues/issues/3734#issuecomment-580654893) is that if I don't unbind the parent PCI bridge off the ``pcieport`` and then restart the ``sys-net`` (attaching the ``03:00.0`` as [described before](https://github.com/QubesOS/qubes-issues/issues/3734#issuecomment-580440403)), the BCM43602 adapter's subsystem changes the device number from ``0x0173`` to ``0x0157`` ``` 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) Subsystem: Apple Inc. Device [106b:0173] ===>>> [106b:0157] !!! ``` But as soon as I **unbind** the parent PCI bridge off the ``pcieport`` again, restart ``sys-net``, the BCM43602 adapter is working back again, even despite that its subsystem device number is now ``0x0157`` instead of ``0x0173``. One more observation is that when I remove the BCM43602 adapter device ``echo 1 | sudo tee /sys/bus/pci/devices/\:00\:1c.0/\:03\:00.0/remove`` and issue a rescan command to its parent PCI bridge ``echo 1 | sudo tee /sys/bus/pci/devices/\:00\:1c.0/rescan`` the BCM43602 adapter (``03:00.0``) will become visible again **only** if the parent PCI bridge was **unbound** from the ``pcieport``. Refs. - - https://github.com/QubesOS/qubes-issues/issues/3734 Kind regards, Andrey Arapov -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRDMZ/b1AtG/U4LjuKQdtXmsxrpnAUCXj20EgAKCRCQdtXmsxrp nLE8AQC3DjkVD+K23MN0/aaz1027W/mVDRtklxaKh0wVvS8DoQEA+o+3qxs2likI ViGSy9UIE5wvcD3DEbIMTRPCyVjZDQw= =8nr8 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cd1a2aedd266f023d89f6b734fae74ca%40nixaid.com.
[qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, I've been having issues with making BCM43602 work and figured a sequence which makes it working and working well - meaning it connects to both 2.4GHz & 5GHz networks and is working at its full speed without any issue. Here is what helped me to make BCM43602 work again on my MacBookPro14,3 (mid-2017). 1. start dom0 with ``qubes.skip_autostart``. 2. start ``sys-net`` in the following sequence: ``` qvm-start sys-net sleep 3 sudo xl pci-attach sys-net '03:00.0,permissive=1' qvm-run -p sys-net "sudo cp ~/brcmfmac43602-pcie.txt /usr/lib/firmware/brcm/brcmfmac43602-pcie.txt" qvm-run -p sys-net "echo 1 | sudo tee /sys/bus/pci/rescan" ``` Enjoy your WiFi! The ``brcmfmac43602-pcie.txt`` file you can get here https://bugzilla.kernel.org/show_bug.cgi?id=193121#c52 - see an "attachment 285753" from Simon Siebert on ``2019-11-02 16:41:15 UTC`` Make sure to set ``macaddr=00:90:4c:0d:f4:3e`` in that file! It's the default mac address which is coming from the firmware. Refs. - - https://groups.google.com/forum/#!msg/qubes-users/DT_uIiiWJd8/cHFiFle1DQAJ - - https://bugzilla.kernel.org/show_bug.cgi?id=193121#c52 - - https://nixaid.com/linux-on-macbookpro/ Kind regards, Andrey Arapov P.S. 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 again. I've tried resetting the PCI bus, removing the card, etc.. only reboot helps. -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRDMZ/b1AtG/U4LjuKQdtXmsxrpnAUCXjM7VQAKCRCQdtXmsxrp nKe2AP9EYxXcKGJ++NDlJta/DVT9mtSx6wvzfhLNKxBW+OfyOwEAxp9HN6umbCUD vo5XYjB9Y31y5Noagb3K0s8sY45bzQI= =5+io -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ed3361ce02db931e0967571a01333aeb%40nixaid.com.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
On Wednesday, December 5, 2018 at 7:54:01 PM UTC+2, Greg wrote: > On my Macbook Pro I can successfully use the Broadcom BCM43602 wifi adapter > with a Fedora sys-net by using a short script to start sys-net manually after > boot (i.e. I disable sys-net auto start and then run the following script > manually after each boot to start sys-net): > > #!/bin/bash > qvm-start sys-net & > sleep 3 > sudo xl pci-attach sys-net '03:00.0,permissive=1' > > > --- > Basically what works (on my system), and what the script does is to attach > the Broadcom adapter to sys-net as soon as possible after starting sys-net > (but before the sys-net VM has fully booted), a 3 second delay works > reasonably reliably on my system. That's interesting... I just wanted to test it on my box, but it turned out I cannot stop sys-net anymore -- it just keeps starting all the time (https://groups.google.com/forum/#!topic/qubes-users/d0ypnUsg2kw)... I need to firstly fix that to be able to check this one out... > I also have the thunderbolt ethernet adapter working, I think the trick there > is that you have to attach it to the MacBook before booting Qubes, hot plug > didn't work when last I tested it. Yes, I confirm the Thunderbolt Ethernet only works when plugged in before booting Qubes. Also, it only works for me if the sys-net runs in PV mode (for HVM there are issues with the driver). Thanks, Mike -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ad7e56a0-ebf0-4322-9db5-2a9f5f3be5c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
On Tuesday, October 23, 2018 at 4:03:33 PM UTC, mike wrote: > Hi, > > On Wednesday, 25 July 2018 11:20:09 UTC+3, awokd wrote: > > > I am running Qubes 4.0 on MacBook Mid-2015 (exactly the same model > > > described here: https://www.qubes-os.org/doc/macbook-troubleshooting/). > > > The whole system crashes after attaching the Broadcom Wifi adapter to > > > sys-net VM. This behaviour is described in the troubleshooting article > > > mentioned above, however the workaround does not work for me. > > > When sys-net is not running I do: > > > [root@dom0 ~]# xl pci-assignable-list > > > :0b:00.0 > > > :04:00.0 > > > [root@dom0 ~]# lspci | grep 04:00 > > > 04:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless > > > LAN SoC (rev 01) > > > [root@dom0 ~]# echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive > > > [root@dom0 ~]# cat /sys/bus/pci/drivers/pciback/permissive > > > :04:00.0 > > > [root@dom0 ~]# qvm-start sys-net > > > [root@dom0 ~]# xl pci-attach sys-net 04:00.0 > > > [root@dom0 ~]# xl pci-assignable-list > > > [root@dom0 ~]# > > > After this I don't see the wifi card in lspci output of sys-net. > > > I don't see anything in sys-net's dmesg either. > > > If I now attach the wifi card using qvm-pci (or GUI) the system will > > > crash. > > > Any idea how I can handle it? > > Try using these newer steps for permissive mode in 4.0: > > https://www.qubes-os.org/doc/assigning-devices/#r40-1. Might help your > > Thunderbolt problem too. > > Many thanks for your answer. > The new way of managing devices does not help though. > Fails for both WiFi and Thunderbolt Ethernet, ie. WiFi crashes the whole > system and Thunderbolt Ethernet is not handled properly by tg3 driver. > > Any other ideas how I can move forward? > I don't have any networking available at the moment... if there was at least > one networking device available I could enjoy the Qubes... > > Is it possible that OS updates (dom0 and/or VM) would fix any of these > issues? I mean I run Qubes 4.0 from the ISO and cannot even install any > updates because of the lack of connectivity... > If so, how can I upgrade by downloading relevant packages on other system? > > > Thanks, > Mike On my Macbook Pro I can successfully use the Broadcom BCM43602 wifi adapter with a Fedora sys-net by using a short script to start sys-net manually after boot (i.e. I disable sys-net auto start and then run the following script manually after each boot to start sys-net): #!/bin/bash qvm-start sys-net & sleep 3 sudo xl pci-attach sys-net '03:00.0,permissive=1' --- Basically what works (on my system), and what the script does is to attach the Broadcom adapter to sys-net as soon as possible after starting sys-net (but before the sys-net VM has fully booted), a 3 second delay works reasonably reliably on my system. Things that don't work for me: - Attaching the adapter to sys-net before starting it causes my system to freeze when sys-net is started. - Attaching the adapter to sys-net too late in the sys-net VM boot process causes it to not be detected by sys-net (when last I tried anyway). - qvm-pci doesn't work to attach it (when last I tried anyway), hence using xl pci-attach. - I don't think a debian sys-net template worked for me with the BCM43602 when last I tried, at the moment I'm successfully using a fedora 28 template for sys-net . - It something goes wrong during the pci attachment on my system I sometimes have to reboot the whole system and try again before it will work... I also have the thunderbolt ethernet adapter working, I think the trick there is that you have to attach it to the MacBook before booting Qubes, hot plug didn't work when last I tested it. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d83364bc-71c5-44b5-af6f-cb50c50a6d49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
On Wednesday, 24 October 2018 09:37:25 UTC+3, awokd wrote: > >>> I am running Qubes 4.0 on MacBook Mid-2015 (exactly the same model > >>> described here: https://www.qubes-os.org/doc/macbook-troubleshooting/). > >>> The whole system crashes after attaching the Broadcom Wifi adapter to > >>> sys-net VM. This behaviour is described in the troubleshooting article > >>> mentioned above, however the workaround does not work for me. > >>> When sys-net is not running I do: > >>> [root@dom0 ~]# xl pci-assignable-list > >>> :0b:00.0 > >>> :04:00.0 > >>> [root@dom0 ~]# lspci | grep 04:00 > >>> 04:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless > >>> LAN SoC (rev 01) > >>> [root@dom0 ~]# echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive > >>> [root@dom0 ~]# cat /sys/bus/pci/drivers/pciback/permissive > >>> :04:00.0 > >>> [root@dom0 ~]# qvm-start sys-net > >>> [root@dom0 ~]# xl pci-attach sys-net 04:00.0 > >>> [root@dom0 ~]# xl pci-assignable-list > >>> [root@dom0 ~]# > >>> After this I don't see the wifi card in lspci output of sys-net. > >>> I don't see anything in sys-net's dmesg either. > >>> If I now attach the wifi card using qvm-pci (or GUI) the system will > >>> crash. > >>> Any idea how I can handle it? > >> Try using these newer steps for permissive mode in 4.0: > >> https://www.qubes-os.org/doc/assigning-devices/#r40-1. Might help your > >> Thunderbolt problem too. > > Many thanks for your answer. > > The new way of managing devices does not help though. > > Fails for both WiFi and Thunderbolt Ethernet, ie. WiFi crashes the whole > > system and Thunderbolt Ethernet is not handled properly by tg3 driver. > > Any other ideas how I can move forward? > > I don't have any networking available at the moment... if there was at > > least one networking device available I could enjoy the Qubes... > Try changing your sys-net's template to Debian instead. Might be able to > use a USB-Ethernet adapter as well, if there's an external port. Good advice -- thanks! I spun a debian qube and connected the WiFi card to it (in permissive mode) but it freezes the same way as fedora. As for the Thunderbold Ethernet I finally managed to get it to work -- will post on that thread... > > Is it possible that OS updates (dom0 and/or VM) would fix any of these > > issues? I mean I run Qubes 4.0 from the ISO and cannot even install any > > updates because of the lack of connectivity... > > If so, how can I upgrade by downloading relevant packages on other system? > Some have had luck installing and updating Qubes on a spare system, then > moving the entire hard drive. This has its own set of complications > though, if using EFI boot. I have tried updating fedora 26 and also installed 28, but still no joy. I'd still love to know how to do a 2 step Qubes upgrade though: 1. Download all packages and create local repo 2. Update Qubes locally from the filesystem Thanks, Mike -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5b497048-ef79-41b2-abc0-175a83bf1e87%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
mike: Hi, On Wednesday, 25 July 2018 11:20:09 UTC+3, awokd wrote: I am running Qubes 4.0 on MacBook Mid-2015 (exactly the same model described here: https://www.qubes-os.org/doc/macbook-troubleshooting/). The whole system crashes after attaching the Broadcom Wifi adapter to sys-net VM. This behaviour is described in the troubleshooting article mentioned above, however the workaround does not work for me. When sys-net is not running I do: [root@dom0 ~]# xl pci-assignable-list :0b:00.0 :04:00.0 [root@dom0 ~]# lspci | grep 04:00 04:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01) [root@dom0 ~]# echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive [root@dom0 ~]# cat /sys/bus/pci/drivers/pciback/permissive :04:00.0 [root@dom0 ~]# qvm-start sys-net [root@dom0 ~]# xl pci-attach sys-net 04:00.0 [root@dom0 ~]# xl pci-assignable-list [root@dom0 ~]# After this I don't see the wifi card in lspci output of sys-net. I don't see anything in sys-net's dmesg either. If I now attach the wifi card using qvm-pci (or GUI) the system will crash. Any idea how I can handle it? Try using these newer steps for permissive mode in 4.0: https://www.qubes-os.org/doc/assigning-devices/#r40-1. Might help your Thunderbolt problem too. Many thanks for your answer. The new way of managing devices does not help though. Fails for both WiFi and Thunderbolt Ethernet, ie. WiFi crashes the whole system and Thunderbolt Ethernet is not handled properly by tg3 driver. Any other ideas how I can move forward? I don't have any networking available at the moment... if there was at least one networking device available I could enjoy the Qubes... Try changing your sys-net's template to Debian instead. Might be able to use a USB-Ethernet adapter as well, if there's an external port. Is it possible that OS updates (dom0 and/or VM) would fix any of these issues? I mean I run Qubes 4.0 from the ISO and cannot even install any updates because of the lack of connectivity... If so, how can I upgrade by downloading relevant packages on other system? Some have had luck installing and updating Qubes on a spare system, then moving the entire hard drive. This has its own set of complications though, if using EFI boot. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/42144357-e5b6-db3a-6e65-ddc9131ce21f%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] MacBook + Broadcom BCM43602 system freeze on Qubes 4.0
Hi, On Wednesday, 25 July 2018 11:20:09 UTC+3, awokd wrote: > > I am running Qubes 4.0 on MacBook Mid-2015 (exactly the same model > > described here: https://www.qubes-os.org/doc/macbook-troubleshooting/). > > The whole system crashes after attaching the Broadcom Wifi adapter to > > sys-net VM. This behaviour is described in the troubleshooting article > > mentioned above, however the workaround does not work for me. > > When sys-net is not running I do: > > [root@dom0 ~]# xl pci-assignable-list > > :0b:00.0 > > :04:00.0 > > [root@dom0 ~]# lspci | grep 04:00 > > 04:00.0 Network controller: Broadcom Limited BCM43602 802.11ac Wireless > > LAN SoC (rev 01) > > [root@dom0 ~]# echo 04:00.0 > /sys/bus/pci/drivers/pciback/permissive > > [root@dom0 ~]# cat /sys/bus/pci/drivers/pciback/permissive > > :04:00.0 > > [root@dom0 ~]# qvm-start sys-net > > [root@dom0 ~]# xl pci-attach sys-net 04:00.0 > > [root@dom0 ~]# xl pci-assignable-list > > [root@dom0 ~]# > > After this I don't see the wifi card in lspci output of sys-net. > > I don't see anything in sys-net's dmesg either. > > If I now attach the wifi card using qvm-pci (or GUI) the system will > > crash. > > Any idea how I can handle it? > Try using these newer steps for permissive mode in 4.0: > https://www.qubes-os.org/doc/assigning-devices/#r40-1. Might help your > Thunderbolt problem too. Many thanks for your answer. The new way of managing devices does not help though. Fails for both WiFi and Thunderbolt Ethernet, ie. WiFi crashes the whole system and Thunderbolt Ethernet is not handled properly by tg3 driver. Any other ideas how I can move forward? I don't have any networking available at the moment... if there was at least one networking device available I could enjoy the Qubes... Is it possible that OS updates (dom0 and/or VM) would fix any of these issues? I mean I run Qubes 4.0 from the ISO and cannot even install any updates because of the lack of connectivity... If so, how can I upgrade by downloading relevant packages on other system? Thanks, Mike -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0f9fcca-3a3a-4299-bb91-8f5a04f64144%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
