Manually select your Broadcom wifi driver article in knowledge base!



  • Tony Baloney

    Article #360001514547 is missing from the "new & improved" KB & is needed for users of Broadcom 4321 & 4313 adapters. Can someone provide a link?

  • Bidwell Ely

    Forrest, your new KB site has eaten this post. How does one retrieve posts from the old site? Furthermore, the new site has very limited in the subject matter.

    Here is the old link.

    Manually select your Broadcom wifi driver 2

  • Tony Baloney


  • Tony Baloney

    Bidwell Ely do you remember the file path to edit?

  • Tony Baloney



  • Bidwell Ely

     I found it on Forrest Smith's articles but when I clicked on it I got the new page which has nothing.

  • Bidwell Ely

    Using "40-broadcom-override.rules", I found your original note. I hope that helps.

  • Tony Baloney

    Can't find the Powerwash by CLI post either ... what's going on?

  • Forrest Smith

    We're switching KBs and unfortunately we had to prioritize the move first for the EDU and Enterprise KB, and secondarily for Home-only help articles. We're working on moving the content over to a new home, but for now we'll need everyone to exercise some patience - sorry.


    Here's a copy/paste dump of this article:





    For some Broadcom wifi hardware, there are two available drivers in CloudReady which may behave somewhat differently. Though CloudReady tries to automatically select the best option, you may want to choose your driver manually and can do so, in the Home Edition, from the command line with the steps below.


    Affected Versions:

    All Versions


    Affected Editions:

    Home Edition



    If you'd like to target a specific broadcom driver, follow these steps:


    1) Log in

    2) Press ctl+alt+t to open a terminal

    3) Type in "shell" and hit enter

    4) Confirm that the yellow "crosh" prompt is now a green "chronos@localhost" prompt

    5) Disable rootfs verification by running:

    sudo disable_verity

    6) Once that finishes, reboot

    7) After rebooting, repeat steps 1 > 4

    8) Remount the root partition as editable:

    sudo mount -o rw,remount /

    9) Edit the file where Broadcom driver can be quirked:

    sudo vim /etc/udev/rules.d/40-broadcom-override.rules

    10) Inside vim, press esc, then press i to enter editing mode 

    11) Arrow down and delete the "#" from the beginning of one of the two lines that start with "ENV". You can target whichever driver you want, or if you're unsure just pick one and proceed.

    12) Once you've removed one of the "#"s, press "esc" and then type":wq!" and then hit enter

    13) You should now be returned to the command line. Assuming you are, you can reboot again to see the change you're hoping for is present.

    14) If you don't see the improvement you want, go back and repeat steps 7-13, but add back the "#" you originally erased and remove the other one.



    • If you want to undo these changes and go back to default-driver choice, simply follow these steps again, but add back a "#" to both driver lines.
    • If you make this change and want to keep it, you'll need to repeat these steps after each update.
    • If your device shows significant improvements when you make this change, please report the change and your hardware info in our forums so we can consider making the change permanent.
      • We cannot make all changes requested, as some improvements come at the cost of other functionality. We will still consider all suggestions.
  • Tony Baloney

    Thx, but I need access to the comment with adding the sed line to a file... need to know the file/path.

  • Forrest Smith

    The instructions up there manage it, it's just a different method than using sed. I'm confident you can get by with this option for the time being.

  • Tony Baloney

    sed for persistence .. I wanted to remove it for testing...

Please sign in to leave a comment.