You are not logged in.
Hello,
I upgraded my system last night. But now my Wi-Fi adapter won't turn on at all. NetworkManager isn't even seeing the adapter. I think it might have to due systemd or maybe the drivers I got from the AUR are broken. I was wondering if any of you guys know what might be going on. My laptop is a Gateway LT2030u.
Thanks,
Jonathan
Last edited by rito25 (2013-01-27 15:57:17)
Offline
Hello,
I upgraded my system last night. But now my Wi-Fi adapter won't turn on at all. NetworkManager isn't even seeing the adapter. I think it might have to due systemd or maybe the drivers I got from the AUR are broken. I was wondering if any of you guys know what might be going on. My laptop is a Gateway LT2030u.
Thanks,
Jonathan
I am not really an advanced user, but I do have a little experience with wifi issues, and I am currently running the TP-LINK TL-WN821N USB without issues.
First, probably would help if you noted what adaptor chipset you have. Also is this internal or external? Probably internal...
You said you updated last night. I am curious when your previous update was? Were there any unusual messages during your update?
Next, did you check dmesg to see any info about card recognition? I also grep through the journalctl output.
Then, I would check the wiki https://wiki.archlinux.org/index.php/Wifi and follow the manual setup steps there, so you can get more of a hint as to what is causing your problem. From a prior life, I believe the utility rfkill helped with wifi internal adaptors.
For me, I run a simple set of scripts, for open and encrypted wifi access points. I don't use any netcfg or networkmanager type automation tools. My scripts work well for me under systemd. I don't use any AUR stuff. Mostly, I think the Atheros chipsets work well.
Hope this helps and have a good day.
Steve.
Arch - LVM - ext4 - gnome (T60p 14.1 1400p x86_64), (T60 15 flexview 1400p i686)
Offline
Internal sound card. My last update was about a month ago. Nothing unusual happened during update. I see a message about loading a module for my adapter when I boot up but it goes to fast for me to read. rfkill shows that the soft-block turns on and off if i flick the switch back and forth.
OK. start up screen says it's missing the b43 fireware. I'll try installing that and seeing if that makes a difference.
Last edited by rito25 (2013-01-27 15:13:20)
Offline
What is the result of `ip link`
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Without ethernet cable plugged in: [jon@localhost ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
link/ether 00:26:22:6f:57:2d brd ff:ff:ff:ff:ff:ff
With ethernet cable
[jon@localhost ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 00:26:22:6f:57:2d brd ff:ff:ff:ff:ff:ff
Offline
Fixed it. I was missing the b43-firmware from AUR. Installed it with yaourt and it worked fine.
Offline