On Friday, January 20, 2017 at 11:48:06 PM UTC-5, Gray Olson wrote:
> On Wednesday, December 21, 2016 at 12:17:52 PM UTC-5, Kent Davis wrote:
> > Maybe you could use sleep, e.g., sleep 30 at the beginning of your
> > rc.local? kinda hacky though...
> > 
> > On Wed, Dec 21, 2016 at 9:58 AM, Dave Cohen <qu...@dave-cohen.com> wrote:
> > >
> > >
> > > On Wed, Dec 21, 2016, at 08:53 AM, Kent Davis wrote:
> > >> I'm not certain, but based on when wireless comes up, I think it runs
> > >> towards the end of the boot process.
> > >>
> > >
> > > I mean rc.local.  Can I put some instruction in there and make sure it is 
> > > performed at the very end of startup?
> 
> I figured it out! The problem is that you ordered your rmmods wrong. I 
> figured this out because if I disabled the rc.local script and just ran it on 
> my own after boot, it would require to be run twice because two of the other 
> modules were being used by b43 and therefore could not be disabled with it 
> still running. So, you need to disable it first. This rc.local works 
> perfectly on Fedora 24:
> 
> ```
> # Unload conflicting modules.
> rmmod b43
> rmmod ssb
> rmmod bcma
> rmmod brcmsmac
> rmmod wl
> 
> # blacklist modules that may interfere with wl (broadcom)
> # Not sure if this matters, haven't tried without
> echo "blacklist b43" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist ssb" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist bcma" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist brcmsmac" >> /etc/modprobe.d/blacklist.conf
> 
> mount --bind /rw/modules /lib/modules
> systemctl restart systemd-udevd
> 
> modprobe wl
> 
> ```

Okay so I've found another issue. For some reason, when the system is 
hibernated (e.g. lid is closed), the module seems to unload itself and the 
whole netvm freezes, requiring a "kill vm" and restart for it to work again. 
Any ideas on the cause of this?

-- 
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/e1b2a779-792b-4705-afd7-04020266ede1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to