You are not logged in.
I'm trying to install Arch on one of my other computers, but I need to get broadcom-wl which depends on linux-headers in order to get internet connection.
I have downloaded https://www.archlinux.org/packages/core … x-headers/ and https://aur.archlinux.org/packages/broadcom-wl/ onto the flash drive that I'm using to install arch, and I can untar broadcom-wl fine, but when I untar linux-headers I am left with a directory called usr and I can't find the pkgbuild. From my understanding I am supposed to build both packages on another computer and then install them on the live cd while on the computer I'm trying to install arch on.
Could someone help me figure this out?
Thanks
Last edited by zachdr1 (2017-04-21 02:19:31)
Offline
[...] but when I untar linux-headers I am left with a directory called usr and I can't find the pkgbuild. From my understanding I am supposed to build both packages on another computer and then install them on the live cd while on the computer I'm trying to install arch on.
The file you've downloaded was probably a .pkg.tar.xz, which is already a built package, so you can simply use `pacman -U` to install it.
Offline
You also don't need linux-headers installed on the iso unless you want to build broadcom-wl on the iso. If you can build the broadcom-wl on another computer you only need to get the broadcom-wl-*.pkg.tar.gz file to the usb and install it with `pacman -U`. Linux-headers are a build dep only.
You *will* however have to build broadcom-wl against the same kernel version as is used on the iso.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
You also don't need linux-headers installed on the iso unless you want to build broadcom-wl on the iso. If you can build the broadcom-wl on another computer you only need to get the broadcom-wl-*.pkg.tar.gz file to the usb and install it with `pacman -U`. Linux-headers are a build dep only.
Ohhh okay, so where in the installation process should I do this? This is the first time I've had to deal with firmware during an installation.
And just to make sure I'm doing this right, to build broadcom-wl, all I do is go into the directory with the pkgbuild and use the command makepkg right?
Last edited by zachdr1 (2017-04-21 15:38:01)
Offline
Ohhh okay, so where in the installation process should I do this?
At the beginning, so you can have a network connection. You'll likely also need to load the wl module (`modprobe wl`) and perhaps rmmod others as described in the wiki.
...all I do is go into the directory with the pkgbuild and use the command makepkg right?
Pretty much. `makepkg -s` would also install the dependencies before building the package.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
zachdr1 wrote:Ohhh okay, so where in the installation process should I do this?
At the beginning, so you can have a network connection. You'll likely also need to load the wl module (`modprobe wl`) and perhaps rmmod others as described in the wiki.
zachdr1 wrote:...all I do is go into the directory with the pkgbuild and use the command makepkg right?
Pretty much. `makepkg -s` would also install the dependencies before building the package.
So I got broadcom-wl installed on the iso and I entered the modprobe and rmmod commands, but I still can't access the internet. I think I'm probably just missing a step
Offline
So I got broadcom-wl installed on the iso and I entered the modprobe and rmmod commands, but I still can't access the internet. I think I'm probably just missing a step
Loading the module only made the system see the wireless network interface/card—you still have to configure the network (see https://wiki.archlinux.org/index.php/Wi … iguration).
Offline
zachdr1 wrote:So I got broadcom-wl installed on the iso and I entered the modprobe and rmmod commands, but I still can't access the internet. I think I'm probably just missing a step
Loading the module only made the system see the wireless network interface/card—you still have to configure the network (see https://wiki.archlinux.org/index.php/Wi … iguration).
Yeah I tried reading the wiki but it seems that my computer still isnt recognizing the interface. ip link only shows lo, and iw dev shows nothing. My network controller is BCM4360
Thanks for all the help btw
Last edited by zachdr1 (2017-04-21 22:04:05)
Offline
That's odd—what's the output of these commands?
lsmod | grep wl lsmod | grep b43
output of lsmod | grep wl
wl 6377472 o
cfg80211 524288 2 wl,mac80211
there is no output for b43
Offline
The output of the following please
$ dmesg | grep wl
$ ip link
Offline
The output of the following please
$ dmesg | grep wl $ ip link
I don't get anything with the first command, and for the second I get
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc no queue state UNKNOWN mode DEFAULT GROUP DEFAULT qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Offline
loqs wrote:The output of the following please
$ dmesg | grep wl $ ip link
I don't get anything with the first command
The wl module was loaded when you ran that command?
Offline
zachdr1 wrote:loqs wrote:The output of the following please
$ dmesg | grep wl $ ip link
I don't get anything with the first command
The wl module was loaded when you ran that command?
I haven't done anything after installing wl, but as far as I know it was loaded.
Offline
As long as it shows in the output of lsmod it is loaded it just seems odd there is no output in dmesg from the wl module. Would expect something similar to:
[ 7.937658] wl: loading out-of-tree module taints kernel.
[ 7.937661] wl: module license 'Mixed/Proprietary' taints kernel.
[ 7.986067] wl 0000:0a:00.0: enabling device (0100 -> 0102)
[ 8.014197] wlan0: Broadcom BCM4359 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
[ 8.015541] wl 0000:0a:00.0 wlp10s0: renamed from wlan0
What wireless adapter is it? You should be able to obtain the output from `lspci -nkk` for a pci device and `lsusb` for a usb device the VID:PID of the device is preferable to a device name. For broadcom the VID should be 14e4.
Offline
As long as it shows in the output of lsmod it is loaded it just seems odd there is no output in dmesg from the wl module. Would expect something similar to:
[ 7.937658] wl: loading out-of-tree module taints kernel. [ 7.937661] wl: module license 'Mixed/Proprietary' taints kernel. [ 7.986067] wl 0000:0a:00.0: enabling device (0100 -> 0102) [ 8.014197] wlan0: Broadcom BCM4359 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 8.015541] wl 0000:0a:00.0 wlp10s0: renamed from wlan0
What wireless adapter is it? You should be able to obtain the output from `lspci -nkk` for a pci device and `lsusb` for a usb device the VID:PID of the device is preferable to a device name. For broadcom the VID should be 14e4.
I actually don't see it in the output of lsmod, but I know I definitely installed it. And the VID:PID is 14e4:43a0.
Last edited by zachdr1 (2017-04-22 01:42:19)
Offline
As long as it shows in the output of lsmod it is loaded it just seems odd there is no output in dmesg from the wl module. Would expect something similar to:
[ 7.937658] wl: loading out-of-tree module taints kernel. [ 7.937661] wl: module license 'Mixed/Proprietary' taints kernel. [ 7.986067] wl 0000:0a:00.0: enabling device (0100 -> 0102) [ 8.014197] wlan0: Broadcom BCM4359 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 8.015541] wl 0000:0a:00.0 wlp10s0: renamed from wlan0
What wireless adapter is it? You should be able to obtain the output from `lspci -nkk` for a pci device and `lsusb` for a usb device the VID:PID of the device is preferable to a device name. For broadcom the VID should be 14e4.
Actually I just reinstalled wl and ran the dmesg command again and I got output
wl: loading out-of--tree module taints kernel.
wl: module license 'Mixed/Proprietary' taints kernel
but I still have the same output for ip link
EDIT: So I got it to work, but it was completely by mistake and I have no idea why it works but I have to go through this long process every time, so I'm hoping someone could tell me what I did to fix it so I don't have to go through this whole process every time.
Here's what I did to fix it:
I installed
dkms-2.3-2any.pkg.tar
gcc-6.3.1--2-x86_64.pkg.tar
guile-2.0.14-1-x86_64.pkg.tar
libmpc-1.0.3-2-x86.pkg.tar
make-4.2.1-1-x86_64.pkg.tar
patch-2.7.5-1-x86_64.pkg.tar
binutils-2.28.0-2-x86_64.pkg.tar.xz
libtool-2.4.6-7-x86_64.pkg.tar.xz
which were all dependents of
dkms-2.3-2-any.pkg.tar
I installed dkms then I installed
broadcom-wl-dkms-6.30.223.271-11-x86.pkg.tar
and ran the commands
rmmod b43 b43legacy ssb bcm43xx brcm80211 brcmfmac brcmsmac bcma wl
modprobe wl
but this DID NOT make the interface show up in ip link
So I replaced broadcom-wl-dkms with broadcom-wl using
pacman -U broadcom-wl-6.30.223.271-4-x86_64.pkg.tar.xz
modprobe wl
AND NOW IT WORKS
I just have no idea why and I don't want to have to do this every time I reboot my computer.
Last edited by zachdr1 (2017-04-22 03:06:44)
Offline
I just have no idea why and I don't want to have to do this every time I reboot my computer.
If I get it correctly, you're doing all of this in the installation ISO, so all of this just happens in RAM (no changes to the live system are persistent). So yes, everytime you reboot, you have to redo all of this.
However, once you've managed to install the system to a persistent storage (e.g. your computer's hard drive), there is no need to do this at every boot.
Offline
zachdr1 wrote:I just have no idea why and I don't want to have to do this every time I reboot my computer.
If I get it correctly, you're doing all of this in the installation ISO, so all of this just happens in RAM (no changes to the live system are persistent). So yes, everytime you reboot, you have to redo all of this.
However, once you've managed to install the system to a persistent storage (e.g. your computer's hard drive), there is no need to do this at every boot.
Cool, do you have any idea why this method worked, but installing broadcom-wl didn't? I said that the dkms variant didn't work, but thats just because I had no idea where to get the ARCH files from that I needed for dkms; I tried researching, and I downloaded linux headers, but I guess they weren't the right ones.
Offline