#Fresh install wifi not working (continued from support channel)
1 messages · Page 1 of 1 (latest)
Here you go @merry river apologies for ping
But yeah as far as I know, and I see no errors in dmesg. That means it shouldn't be a kernel or firmware issue right?
That looks pretty ok. iwlwifi is the right driver
What about dmesg | grep -E wlo1\|wlp0
Should filter for lines with those strings in it, so the wifi messages
Hmm
It's annoying because I'm pretty certain that it being DOWN is the problem. Why no ip link set <dev> up work? 
Idk if it is only down because it failed to set up an initial connection for whatever reason
And so it gets kicked into a down/dorman state
The "DORMANT" part is normal, even for a connected device
What you could do, is get back into the iso, connect up there, and see what is different
I have the live gui iso, I assume that is fine
I mean first difference is it has networkmanager but I assume this is partially due to it being a KDE gui
Checking if the device responds to UP and DOWN there would be my first step
So you are running just wpa_supplicant alone on this machine?
Dhcpcd and netifrc
As well*
Ip link set wlo1 up did not work in livedisk
Used nmtui to connect to network and it then shows up
Can set it down but not back up
And despite being down is can still ping gentoo.org?
Fucking hell im even more confused
Ill read through this one sec
If you're using netifrc then openrc could be setting the device back down immediately after you set it up manually
Hmm so delete the net.wlo1 default service and then try?
Or use netifrc to manage your devices directly
This implies the symlink in between the net.lo and net.wlo1 step no?
And then setting net.wlo1 as service at default?
In which case I did this as part of the installation
Wpa was installed and is initialized by my netifrc config I believe
Said config /etc/conf.d/net
Does it appear OK in rc-status default?
Yup net.wlo1 and netmount
Hmm, maybe try stopping that service and see if the ip link thing works with it stopped
Nope
Would using sysklogd maybe help find some errors or something?
Only other thing I've tried is running wpa for debugging as I've mentioned idk if that might help?
Never a bad idea, but if there were errors then I expect dmesg would have found them
Ill try out a few wpa configs from the wiki page see if any work out XD
I think the wpa stuff is a red-herring. Your device is not UP, until it's UP wpa is not involved as no connection is possible
Ill probably be away from my computer for a bit but I'll continue researching later
Fixed it