Skip to main content ↑ ↓
Topic: no internet after motherboard change (Read 811 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

no internet after motherboard change

Today, i have changed my motherboard and processor, and now the internet stopped working, i've seen countless tutorials, but nothing helps. Connman tells me that i have wifi, but its not true, as firefox doesn't work. I have tried changing the nameserver in resolv.conf, but everytime i reboot, it resets. Please help.

Re: no internet after motherboard change

Reply #1 –
Perhaps post the output of some commands like:
Code: [Select]
$ ip link show
$ ip route
$ iw dev
# lspci -vvv
(Network controller section of lspci output, you might need to use lsusb instead for usb adapters)
If you still haven't got it working, this might help to narrow things down a bit for further suggestions.

Re: no internet after motherboard change

Reply #2 –
ip link show:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc state UNKNOWN mode DEFAULT group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST, MULTICAST, DYNAMIC> mtu 1500 qdisk fq_codel state DOWN mode DEFAULT group default qlen 1000
     link/ether 00:0b:0e:0f:00:ed brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST, MULTICAST, DYNAMIC, UP, LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
     link/ether c0:25:e9:23:de:91 brd ff:ff:ff:ff:ff:ff

ip route:
default via 192.168.0.1 dev wlan0
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.108
192.168.0.1 dev wlan0 scope link

iw dev:
phy#0
    Interface wlan0
        ifindex 3
        wdev 0x1
        addr c0:25:e9:23:de:91
        type managed
        channel 6 (2437 MHz), width: 40 MHz, center1: 2427 MHz
        txpower 15.00 dBm
        multicast TXQ:
                qzs-byt qzs-pkt flows drops marks overmlt hashcol tx-bytes tx-packets
                0            0            0        0         0          0             0            0             0

Re: no internet after motherboard change

Reply #3 –
Do you have a router which requires opening up specific MAC addresses?

Re: no internet after motherboard change

Reply #4 –
Try something lower level to test if you have internet.
Can you ping ?
Code: [Select]
❯ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=6.11 ms
Code: [Select]
❯ ping cloudflare.com
PING cloudflare.com (104.16.133.229) 56(84) bytes of data.
64 bytes from 104.16.133.229 (104.16.133.229): icmp_seq=1 ttl=56 time=6.55 ms
 

Re: no internet after motherboard change

Reply #5 –
lspci -vvv will also reveal the model number of the wifi chipset and what kernel driver is being loaded, so you can check if the correct driver is being used. But from that output it looks like the wifi adapter is probably being found by the system, but is not being brought up correctly by Connman. I'm not familiar with using that app, usually using CLI methods myself, but as a general suggestion you could try deleting your wifi entry in Connman and recreating it again, possibly something like a MAC address or other device identifier has changed with the new motherboard. If that doesn't help, you could also additionally try to find out if Connmann stores any local config in somewhere like ~/.local or ~/.cache and removing that to force it to update it's info.

Re: no internet after motherboard change

Reply #6 –
Quote from: gripped – on
Try something lower level to test if you have internet.
Can you ping ?
Code: [Select]
❯ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=6.11 ms
Code: [Select]
❯ ping cloudflare.com
PING cloudflare.com (104.16.133.229) 56(84) bytes of data.
64 bytes from 104.16.133.229 (104.16.133.229): icmp_seq=1 ttl=56 time=6.55 ms
Yes, i can ping.
Quote from: ####### – on
lspci -vvv will also reveal the model number of the wifi chipset and what kernel driver is being loaded, so you can check if the correct driver is being used. But from that output it looks like the wifi adapter is probably being found by the system, but is not being brought up correctly by Connman. I'm not familiar with using that app, usually using CLI methods myself, but as a general suggestion you could try deleting your wifi entry in Connman and recreating it again, possibly something like a MAC address or other device identifier has changed with the new motherboard. If that doesn't help, you could also additionally try to find out if Connmann stores any local config in somewhere like ~/.local or ~/.cache and removing that to force it to update it's info.
Can you please tell me the name of the file or its location?

Re: no internet after motherboard change

Reply #7 –
Ok, i found the entries, though deleting them didn't help.

Re: no internet after motherboard change

Reply #8 –
Quote from: johnson69 – on
Yes, i can ping.
Well if you can ping you have internet.
You need to start investigating why firefox cannot use it?

I'd suggest both installing another browser for now so you can search but also checking the proxy and DNS settings of firefox.
You could start with a clean slate for firefox by renaming ~/.mozilla after first closing all open firefox windows. Once renamed starting firefox will create a clean default ~/.mozilla .

If you can get the internet working with the new firefox profile but for some reason cannot fix the old one this may help save you some time setting up.
https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

Re: no internet after motherboard change

Reply #9 –
You could also check:
Code: [Select]
$ rfkill
BIOS menu settings related to wireless
Wifi on / off switch - (laptops have these, if you swap the mobo you sometimes have to make sure the toggle lines up with the external slider properly)
Those above are less likely as the wifi card is detected.
Try changing the hostname - strange problems can occur regarding hostnames, it might also make your router create a new entry if it had cached some data that was causing trouble.
Try to connect to the router HTML web management page to see if local connections are working, you usually type a numerical IP address into a browser to do this. The address might be 192.168.0.1 from your ip link output, your router user manual will probably tell you. The router interface might have some connection status info and logs too.
Check firewall settings if you have a firewall installed.

Re: no internet after motherboard change

Reply #10 –
Ok, i discovered something weird. Pacman, discord and other programs say that they cant set up /etc/ssl/certs/ca-certificates.crt. So, i generated the file using the arch wiki tutorial, it stills doesn't work though (with the same error!).

The error is:
error setting up certificate file: /etc/ssl/certs/ca-certificates.crt

Re: no internet after motherboard change

Reply #11 –
I get that you may be new to this but when asking for help you'll have more success if you are as descriptive as possible as to what you have tried.
Commands used.
Output received.

Not "I tried some stuff, didn't work"

You started the thread "no internet" but you did have internet.
If you have followed a guide link to it or at least post the commands you used.

Anyway /etc/ssl/certs/ca-certificates.crt is not a 'generated' file. It's part of package ca-certificates-utils
See if that package is in /var/cache/pacman/pkg

The version in my cache is /var/cache/pacman/pkg/ca-certificates-utils-20220905-1-any.pkg.tar.zst

You can reinstall it with
Code: [Select]
sudo pacman -U /var/cache/pacman/pkg/ca-certificates-utils-20220905-1-any.pkg.tar.zst
If necessary change the version to match what you have in your cache.

Otherwise you'll need to download it from a mirror.

This may not fix your issue entirely but will hopefully take you a step closer.

Re: no internet after motherboard change

Reply #12 –
If the wireless card is an internal type you could check it's seated correctly and the antenna wires are properly connected and the metal connectors are not touching each other or any other metal part, and that they are connected to the correct terminals on the card - if there was a poor quality signal it might give the symptoms you describe.