-
Notifications
You must be signed in to change notification settings - Fork 19
keep some /etc/network/interfaces lines #15
Comments
Hmmmm... this seems like the sort of thing that shouldn't be necessary these days, what with udev being able to automatically load the necessary drivers. At first I thought maybe we broke something but I went poking around inside of my Raspbian .img files and it's the same way in there. My off-the-cuff thought is that it should be possible to write a script that runs at boot-time, parses the output of |
This looks like a good place to start: http://packages.debian.org/source/squeeze/firmware-nonfree It's a meta-package, so by putting that in the manifest, we get all of them at once. |
Well, I'm on crack. I just logged into my node and you can't just Added all of the wireless chipset firmware packages to manifest in commit f74747a. |
Has anybody tried a b43 (Broadcom) wireless adapter with ByzPi? We've got three options (firmware-b43-installer, firmware-b43-lpphy-installer, firmware-b43legacy-installer) but I don't have one to test with so I can't do compatibility tests. |
and added all of the firmware packages that I didn't have in the Puppet manifest from the previous commit. This references issue #15. Signed-off-by: The Doctor <[email protected]>
some chipsets need help getting the right drivers and the lines like:
may be required for the wireless to work.
other lines may need to be preserved but i don't know what they are at the moment
The text was updated successfully, but these errors were encountered: