You are not logged in.
Hi everyone,
I'm installing arch on an MSI GS43VR 7RE Phantom Pro.
Everything seemed to go well until I rebooted into the newly installed system and found that I couldn't connect to the internet.
I tried to connect through wifi-menu as I did from the installation image and rather than seeing the network selection menu,
I was greeted by the following error:
# wifi-menu
Invalid Interface Specification
Usage: wifi-menu [-h | --help] [-o | --obscure] [INTERFACE]
Interactively connect to a wireless network on INTERFACE using netctl,
If only one wireless interface is available, INTERFACE can be omitted,
Arguments:
-h, --help Show this help
-o, --obscure Show asterisks for the characters of the password
and store the password as a hexadecimal string
Clearly something wrong with the interface so I looked at what interfaces ip link shows me:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
So it only sees loopback... not even my ethernet controller.
lspci shows:
# lspci -k | grep Network
lspci: Unable to load libkmod resources: error -12
3e:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
It seems like there are some firmware drivers in the installation media that aren't getting copied over by pacstrap,
but everything I've read on the arch-wiki indicates that my wireless driver should be included in the linux-firmware package.
What am I missing?
for reference, this is what the installation media outputs when I run ip link:
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp61s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc nq state DOWN mode DEFAULT group default qlen 1000
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
3: wlp62s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether **:**:**:**:**:** brd ff:ff:ff:ff:ff:ff
Thanks in advance for your help
Last edited by Zatael (2019-05-26 14:13:57)
Offline
It seems like there are some firmware drivers in the installation media that aren't getting copied over by pacstrap
`pacstrap` does not "copy over" anything; it installs a new base system which indeed is not what is on the iso. This is specifically noted in the installation guide for networking.
So we just need to figure out what is needed for your hardware and get it installed.
Have you worked through this yet?
Can you check what module is in use in the live system for your wireless card?
Last edited by Trilby (2019-05-26 13:04:10)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Online
Your installed kernel may be different then the booted one, like in [1]
please post
$ pacman -Q linux
$ uname -a
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Have you worked through this yet?
Can you check what module is in use in the live system for your wireless card?
I did and as I have a qualcomm 802.11ac it would appear I need the ath10k driver but I cant seem to find that in the pacman list. In fact theres nothing for qualcomm or atheros at all
Last edited by Zatael (2019-05-26 13:31:58)
Offline
Your installed kernel may be different then the booted one, like in [1]
please post
$ pacman -Q linux $ uname -a
#pacman -Q linux
linux 5.1.4.arch1-1
#uname -a
Linux archiso 5.0.10-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 27 20:06:45 UTC 2019 x86_64 GNU/Linux
Offline
Your installed kernel may be different then the booted one, like in [1]
please post
$ pacman -Q linux $ uname -a
I read through the link at the bottom of your post and realized I also forgot to mount /boot before installing the kernel... I feel like an idiot bit that fixed it. I can access my wifi card now. Thank you so much
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline