0

PRETTY_NAME="Ubuntu 20.04.3 LTS"

Got a wireless chip in my HTPC and I can't get it to connect to the wireless in the house (2 android phones, 2 macs and 1 windows machine have no issues). Ubuntu 20. I bought this machine years ago but it's always had a wired connection. In the new house a wired connection means drilling and time in the crawlspace, so I'd like to get the wifi working. The onboard wireless is listed as "802.11AC + Bluetooth V4.0 or 802.11 BGN" in the machine specs. I am currently using a wired connection but that means a cable running across the floor.

The issue is that I can't get the wifi to come up at all. There is a very detailed wifi connection troubleshooter on this site. I've done many of the steps from it with no luck. Sorry, I can't find the link in my history. I think the issue I ran into with that troubleshooter was that my wifi list has no wifi listed:

$ nmcli dev wifi list
IN-USE  BSSID  SSID  MODE  CHAN  RATE  SIGNAL  BARS  SECURITY
$

Onboard chip info:

  *-network
       description: Wireless interface
       product: Wireless 3160
       vendor: Intel Corporation

Network configs:

$ cat /etc/netplan/*.yaml
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager
$ cat /etc/network/interfaces
cat: /etc/network/interfaces: No such file or directory

I think the issue is that the wifi protocol won't come up:

$ ip link show
1: lo: ...omitted
2: enp2s0: ...omitted
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 34:e6:ad:da:28:43 brd ff:ff:ff:ff:ff:ff

$ sudo ip link set wlp3s0 up


$ ip link show | grep wlp
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000

Still down.

Looking at this question here they suggest using killall dhcpcd but I think that might kill my connection (I'm using ssh as this is a HTPC and keyboard access is an issue). They also suggested looking at journalctl, but I don't see anything there.

$ journalctl -xe | grep -A 5 wlp
Sep 04 07:43:29 media-cube sudo[34355]:    media : TTY=pts/0 ; PWD=/home/media ; USER=root ; COMMAND=/usr/sbin/ifconfig wlp3s0 up
Sep 04 07:43:29 media-cube sudo[34355]: pam_unix(sudo:session): session opened for user root by media(uid=0)
Sep 04 07:43:29 media-cube sudo[34355]: pam_unix(sudo:session): session closed for user root
Sep 04 07:45:25 media-cube sudo[34433]:    media : TTY=pts/0 ; PWD=/home/media ; USER=root ; COMMAND=/usr/sbin/ip link set wlp3s0 up
Sep 04 07:45:25 media-cube sudo[34433]: pam_unix(sudo:session): session opened for user root by media(uid=0)
Sep 04 07:45:25 media-cube sudo[34433]: pam_unix(sudo:session): session closed for user root
Sep 04 07:48:40 media-cube sudo[34554]:    media : TTY=pts/0 ; PWD=/home/media ; USER=root ; COMMAND=/usr/sbin/ip link set wlp3s0 up
Sep 04 07:48:40 media-cube sudo[34554]: pam_unix(sudo:session): session opened for user root by media(uid=0)
Sep 04 07:48:40 media-cube sudo[34554]: pam_unix(sudo:session): session closed for user root

rfkill list all doesn't show any hard or soft blocks.

After hashing on this problem for a while I took a guess that the chip was defective so I bought a wifi adapter (edimax EW-7822UAC). Can't get it working either. I've installed the drivers but Ubuntu doesn't seem to see it, even after a reboot. The Ubuntu troubleshooter stops at "make sure your have working drivers installed", so I'm not sure where to go next.

Speed is important here, as this is a media player, so I suspect I will need to get the external adapter going but using onboard would be simpler and cheaper.

jcollum
  • 1,032

0 Answers0