You should be able to download the broadcom-wl package from rpmfusion onto a flash drive then once the initial install is done use that flash drive to install the driver onto the system. Then a reboot would enable the wifi driver. Yes, the needed packages can be downloaded using windows and placed onto the flash drive.
Descargar archivo https://lpoms.com/2yOOFd
A quick look at the packages on that site give at first glance 3 different broadcom packages, all from the nonfree repo. You would definitely need broadcom-wl & akmod-wl from rpmfusion, akmods, kernel-devel, and all the dependencies of those from fedora.
I had asked in the Fedora Discord what I would need to do, and a moderator helped me out by directing me a bit in that I would need to install the Nvidia akmod as that was called on by broadcom-wl, but to install the Nvidia akmod I would need to install the rpmfusions free and non-free repos.
Thank you for letting me know that I can in fact download what I need and install it from there instead of over the internet. Would you happen to know the inputs for the Konsole I should use to install from a specified location rather than from the internet?
Hi everyone! I'm glad and not so glad to be here at the same time... I'm glad because I finally decided to try out Arch Linux, and I'm not happy because if you see this post it means that something went wrong during the installation
those are the things i've tried so far... i've read that archlinux sometimes has a little trouble detecting these broadcom wifi cards, but I haven't found a concrete solution yet... Any help is greatly appreciated
Then follow the wiki here to identify the actual chipset on your card. You will also find links to information from that wiki page to identify the driver options for your card. There are - at least - two different chipsets in cards labeled BCM4352. Unfortunately, it seems the options for these are limited to bad and worse - but knowing which one you have will be important for knowing the next steps.
EDIT: oops, I missed that the wl module was already loaded. So that (mostly) rules out the "bad" option, and you may be left with "worse" of ndiswrapper, or just finding another wireless card to use. But still it would be good to get the actual chip information to be sure (as perhaps wl would work if you blacklist / unload any competing modules).
Yes, sorry, I had my terminology backwards. That's the chipset name, but I was looking for the PCI-ID which is 14e4:43b1. According to the docs, this card is not even expected to be supported by the 'wl' module (there is another BCM4352 which is). So you may be left just with ndiswrapper (which I've never had to use and it seems to even have been removed from the broadcom wiki page).
If you installed the wl driver and did not reboot afterwards, reboot (you can also try to remove the modules first)
If you did reboot after installing broadcom-wl, try to fully power down the system (remove the battery, if you can) and boot cold.
yes i also have windows on my pc, although i don't think it should interfere since arch linux isn't actually installed yet as i am still on archiso (and i installed a new SSD where i will have arch linux separate from windows)
Which is irrelevant to the matter at hand.
Typically the USB boot would prevent that, but also typically the wifi chip dropping out is the primary symptom.
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
What you need to do to get it working within the installation iso is first to follow seth's post, then either edit the kernel command line to blacklist all other broadcom modules while booting the iso, or `rmmod` those other modules once booted and (re)load the wl module. These are the steps I listed in post #4.
Note that in many ways getting this working in the iso may be harder than in a newly installed system (aside from broadcom-wl being preinstalled) as lots of *other* drivers are also installed and a bit tricker to blacklist which may be part of the problem. So following the advice below to install via ethernet or tether may be wise, then this should be easier to troubleshoot on an actual system.
shortly after that, pacstrap tried to install the packages. then i got hit with a whole wall of error messages where it basically says, that it failed to retrieve the file 'core.db' from a mirror. it looks like it tried dozens of mirrors.
(For anyone reading this with the same issue, just follow the tethering link that Seth sent and follow the usb instruction part. create the file and plug your phone in via cable and make sure that your iphone trusts the pc)
yesterday i used archinstall to install everything after setting up internet connection via tethering and got the same result from the journalctl command, so i thought i might need to do everything manually, which doesn't seem to be the case...
No. You should solve the problem. To do so, start a new thread and actually describe that problem including what it means that the bios "doesn't recognizes" your arch install while also including information about what boot loader you installed, how you installed it, and how you configured it.
d3342ee215