Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
lspci | grep -i network should give you the name of your network adapters. lshw -C network (may need to be run as root) will give you more detailed info about those adapters (ls - list hw - hardware).
lspci in general will give you info about the pci devices in your system. lsusb does the same for usb. there other helpful ls- commands like this. lscpu comes to mind. you can always check the man page (man lsusb for example) or info page (info lsusb) for helpful options like the -C i used with lshw.
lspci | grep -i network should give you the name of your network adapters. lshw -C network (may need to be run as root) will give you more detailed info about those adapters (ls - list hw - hardware).
lspci in general will give you info about the pci devices in your system. lsusb does the same for usb. there other helpful ls- commands like this. lscpu comes to mind. you can always check the man page (man lsusb for example) or info page (info lsusb) for helpful options like the -C i used with lshw.
looks like a bit more info might be needed from
Code:
lspci -vnn -d 14e4
(as seen here and here) which you would then compare to the chart by device id and chipset name.
Rightttt, appreciate the effort.
I had it running seconds after I posted the thread, the point wasn't to just get it working or relying on Google, but figuring out in general what steps I should take to try to figure out exactly what I needed. by doing the most narrowing down I can do in research.
Further:
Quote:
Drivers
There are multiple drivers supporting Broadcom wireless LAN chips.
Linux kernel drivers:
b43*(supported devices)
Introduced in Linux 2.6.24.Supports BCM4321 and BCM4322 as of Linux 2.6.38.
b43legacy*(supported devices)
For 802.11b-only devices and the BCM4306 revision 2.Introduced in Linux 2.6.24.
Awesome, I already had enabled contrib and non free sources for some other odds and ends. how did you find out that those files were included in the package? is there a way to tell that from the command line?
ultimately the only thing I did was:
Code:
sudo apt install broadcom-sta-dkms*
then ifconfig and the wireless interface was showing so I copied it over to wicd and bam. good to go.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.