Ok really wasn't sure where to put this. So I guess it's here but let me describe the situation. Odd but here goes.Note: Read through the whole thread:
Ok so I started a long time ago with LM10, still really like this distro and community and occasionally return just to see where it's at or dork around in the forums. I installed LM 19 Cinnamon but even checking the box for enable proprietary software in the installer wouldn't get my problem Broadcom wireless card working. At the moment I only have wifi (no wired) access, so this left me with an LM operating system that couldn't connect to the wifi here, no internet !!!
To fix this I turned to a great and powerful method of fixing problems with an ailing gnu/Linux install. Works for a dizzying array of problems and guarantee used with common sense can save a nixer massive amounts of time + pain, in fixing a broken install they cant boot normally.
You can reinstall a bootloader, edit files ( to fix them if you've messed them up.) Install, remove, reconfig or fix broken software packages. Tons of stuff you can do with this, so here goes.
Not going to reinvent the wheel, I've done this many times before. To fix my problem, I used a different distro in live session to chroot and install the software LM 19 was missing. In this case it's a Bunsenlabs linux iso, which supports my problem wireless card out-of-box. I downloaded the iso from their site and for convenience followed this how-to, as noted in some of the other posts in that thread (BLizgreat! is my username on that forum.) I didn't need to install the debootstrap package while in BL live session to get this to work and also note the tip about using Ctrl + D to exit the chroot prior to rebooting after I'd installed the packages I needed to the LM OS.
While running in live session with the Bunsenlabs iso. I installed the binutils package to it with ...
Code: Select all
sudo apt-get update && sudo apt-get install binutils
Ok wanted to see which kernel module I needed, that was loaded in the BL's iso live session, I was missing in LM 19, did so by popping open a terminal in the BL live session and using the cmd "lsmod". In my case for this problem card it was using the b43 module. Ok so next up what packages were present in the BL iso (live session) related to the b43 software I needed, found this with "dpkg -l |grep b43". It listed out several ... ok. So followed that how-to, chrooted my LM install on sda7 and searched the LM software repositories for the b43 packages I was missing with "apt-cache search b43".
In my case turns out I needed the following and these are the one's I installed while in BL live-session.
While chroot'ed in the BL live-session installed them with.ii b43-fwcutter 1:019-3 i386 utility for extracting Broadcom 43xx firmware
ii firmware-b43-installer 1:019-3 all firmware installer for the b43 driver
ii firmware-b43legacy-installer 1:019-3 all firmware installer for the b43legacy driver
Code: Select all
sudo apt-get install b43-fwcutter firmware-b43-installer firmware-b43legacy-installer
Just for the sake of being thorough in case someone else has this issue. After doing this, I used "Ctrl + D" to exit the chroot in the BL live-session and then rebooted the system with "sudo reboot".Broadcom Limited BCM4312 802.11b/g LP-PHY
Everything's working great "lsmod" shows the b43 wireless module loading as expected to support my wifi, so am happy and typing away right now on LM19 via wireless connection.
Anyway, there is plenty of info on chroot via live session, know others that work fine too but for convenience did this one, trust the guy who wrote it and just verified 100% works as described here, so rather than rewrite or compile a massive chroot how-to, just linked to it. Also note, if you have more than one gnu/Linux install on a system and one breaks, you can also chroot and fix that broken install from the working OS on that pc. Not going into that just noting it.
Also just to state the obvious, here I used a Debian Stable based iso (Bunsenlabs) to fix a LM 19 OS installed. Have also done that many and for a long time. ie: Used xyz-iso to save a messed up Arch install I'd messed, or an Mint iso to save a borked gnu/Linux Arch install. Chroot is a very powerful, kickbutt and versatile way to fix a broken Nix operating system. Without having to reinstall or restore a backup etc.