Okay. This is getting really disjointed. Identifying your hardware before installing is the easiest way. The broadcom binary blobs are the same for Deb. Download the Deb package and save it as a Deb package to a separate USB in advance. The LL installer will often find it if you are installing from DVD or if you have two USB ports. If it doesn't you can still find it from LL afterwards on the USB. Pre-seeding Deb packages of firmware blobs is something we should add to the help manual, and an instruction on how to identify hardware on running Windows systems prior to Linux installs. I believe the bcm wifi support for this particular card has been in LL for a while, since late 2.8 or 3.0 in my experience. I'm betting that it was available to this questioner during installation and he/she simply opted not to connect, and the system info posted seems to be currently configured to attempt a wired connection. Also many many Netgear adapters are not compatible except through ndiswrapper. This particular questioner should also check the BIOS to make sure wifi is enabled and which key will enable it as this could also be a keyboard recognition issue. Also broadcom support in RHEL is very extensive. If there is no Deb available there is often RPM for OEM installations, and contrary to popular opinion they (being binary blobs) are installable via the terminal in Deb without alien and come with installation instructions.
TC
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.