Skip to main content ↑ ↓
Topic: Networking Error (Read 3104 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Networking Error

For the past couple of months my artix has been plagued with networking issues. Usually a restart would do the trick, but I have to restart more now. Disconnecting and reconnecting from networks doesnt do anything. Opening firefox it just gets stuck loading the page forever, and for some reason re-opening firefox doesn't work when the system is like this. I don't see anything in the error log that would be related. What can I do to diagnose this issue?

Re: Networking Error

Reply #1 –
 what does dmesg say about your ethernet connection?  You are not giving any detail here of what networking you are doing so I am assuming is it ethernet wire.

Re: Networking Error

Reply #2 –
Quote from: mrbrklyn – on
what does dmesg say about your ethernet connection?  You are not giving any detail here of what networking you are doing so I am assuming is it ethernet wire.
Yeah, I'm on ethernet.

I'm not sure what you are asking regarding dmesg, do I run it on a bad reboot or a good one? I'm unfamiliar with much

Re: Networking Error

Reply #3 –
run sudo dmesg

Re: Networking Error

Reply #4 –
Quote from: mrbrklyn – on
run sudo dmesg

Does it depend on if I run it when the networking works or when its not working? And the output is quite long, is there a certain part I'm looking for?

Re: Networking Error

Reply #5 –
Simply put, dmesg shows kernel-related messages from boot time until now. It will give the most useful information after you've experienced a disconnect. You can search for "eth" for starters, but depending on the problem something else might be relevant, too. On my reliable connection I just get
Code: [Select]
$ sudo dmesg | grep eth
[    9.052586] r8169 0000:03:00.0 eth0: RTL8168h/8111h, 1c:69:7a:0a:80:07, XID 541, IRQ 133
[    9.052599] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[   14.070129] r8169 0000:03:00.0 eth0: Link is Down
[   20.067480] r8169 0000:03:00.0 eth0: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx
After a disconnect, I would expect to see some messages as to why, and right after a disconnect they would be among the most recent messages at the bottom.

Re: Networking Error

Reply #6 –
Quote from: lotuskip – on
Simply put, dmesg shows kernel-related messages from boot time until now. It will give the most useful information after you've experienced a disconnect. You can search for "eth" for starters, but depending on the problem something else might be relevant, too. On my reliable connection I just get
Code: [Select]
$ sudo dmesg | grep eth
[    9.052586] r8169 0000:03:00.0 eth0: RTL8168h/8111h, 1c:69:7a:0a:80:07, XID 541, IRQ 133
[    9.052599] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[   14.070129] r8169 0000:03:00.0 eth0: Link is Down
[   20.067480] r8169 0000:03:00.0 eth0: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx
After a disconnect, I would expect to see some messages as to why, and right after a disconnect they would be among the most recent messages at the bottom.


I happen to have an unstable ethernet device with a broken kernel modules and it does go preidoically down unless it is set up in a stable way.  So that is one level of problem that needs to be checked.

Re: Networking Error

Reply #7 –
Quote from: mrbrklyn – on
Quote from: lotuskip – on
Simply put, dmesg shows kernel-related messages from boot time until now. It will give the most useful information after you've experienced a disconnect. You can search for "eth" for starters, but depending on the problem something else might be relevant, too. On my reliable connection I just get
Code: [Select]
$ sudo dmesg | grep eth
[    9.052586] r8169 0000:03:00.0 eth0: RTL8168h/8111h, 1c:69:7a:0a:80:07, XID 541, IRQ 133
[    9.052599] r8169 0000:03:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[   14.070129] r8169 0000:03:00.0 eth0: Link is Down
[   20.067480] r8169 0000:03:00.0 eth0: Link is Up - 100Mbps/Full (downshifted) - flow control rx/tx
After a disconnect, I would expect to see some messages as to why, and right after a disconnect they would be among the most recent messages at the bottom.


I happen to have an unstable ethernet device with a broken kernel modules and it does go preidoically down unless it is set up in a stable way.  So that is one level of problem that needs to be checked.
How do I check for this? Or is it relevant to me? Windows networking is fine, just artix is acting up

Re: Networking Error

Reply #8 –
Quote from: SalamiMommy – on
Quote from: mrbrklyn – on



I happen to have an unstable ethernet device with a broken kernel modules and it does go preidoically down unless it is set up in a stable way.  So that is one level of problem that needs to be checked.
How do I check for this? Or is it relevant to me? Windows networking is fine, just artix is acting up

windows networking is irrelevant.  They often have drivers that get around broken hardware or, in the old days, software to emulate  hardware - aka software modems...

look at dmesg and hdinfo to see what your exact hardware IS and if it is doing strange and unexpected things.  There is a lot of stuff made in asia which is, FWIW, broken in that it doesn't follow the design correctly, or is just broken out of the box because of poor quality control.  That is why you burn in servers before deploying them.

Also, components over time just burn out... like light bulbs.  They don't last forever.

Re: Networking Error

Reply #9 –
Quote from: mrbrklyn – on
Quote from: SalamiMommy – on

How do I check for this? Or is it relevant to me? Windows networking is fine, just artix is acting up

windows networking is irrelevant.  They often have drivers that get around broken hardware or, in the old days, software to emulate  hardware - aka software modems...

look at dmesg and hdinfo to see what your exact hardware IS and if it is doing strange and unexpected things.  There is a lot of stuff made in asia which is, FWIW, broken in that it doesn't follow the design correctly, or is just broken out of the box because of poor quality control.  That is why you burn in servers before deploying them.

Also, components over time just burn out... like light bulbs.  They don't last forever.
okay, here is what I got today
Code: [Select]
[    4.650013] r8169 0000:04:00.0 eth0: RTL8168h/8111h, a8:a1:59:46:c5:f2, XID 541, IRQ 73
[    4.650017] r8169 0000:04:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[    6.745387] r8169 0000:04:00.0 eth0: Link is Down
[    9.651361] r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[    9.652468] r8169 0000:04:00.0 eth0: Link is Down
[   13.204333] r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   77.764932] r8169 0000:04:00.0 eth0: Link is Down
[   81.319600] r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   83.138878] r8169 0000:04:00.0 eth0: Link is Down
[   86.767834] r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx

Re: Networking Error

Reply #10 –
why is it going up and down?  Are you connecting and disconnecting it?

Re: Networking Error

Reply #11 –


see if this makes it stable

ethtool -K eth0 tso off