What does the following command tell you
sudo modprobe -v r8169
1 Like
insmod /lib/modules/5.15.21-1-MANJARO/kernel/drivers/net/phy/libphy.ko.xz
insmod /lib/modules/5.15.21-1-
MANJARO/kernel/drivers/net/phy/mdio_devres.ko.xz
insmod /lib/modules/5.15.21-1-MANJARO/kernel/drivers/net/phy/realtek.ko.xz
insmod /lib/modules/5.15.21-1-
MANJARO/kernel/drivers/net/ethernet/realtek/r8169.ko.xz
Sorry if the formating is incorrect but im doing this from mobile.
Oh internet is back again…
I didnt do anything, yet now
Inxi -Fayz tells me that driver r8169 is running.
So i guess we are done with that? Ill test it out and reach out to you tomorrow.
oh but you did load the driver using the command
modprobe -v r8169
1 Like
I hope the issue solved but it almost looks like the internet modem or the router is resetting.
Oh ok i thought it was supposed to give information!
Anyways thanks…
I’ll keep this thread open until tomorrow to see how it goes.
But all other devices stay connected.
I also have a Gigabyte board but mine is the Gigabyte 970A-UD3P, I’ve always needed to add iommu=soft to be able to use my wifi card and usb3 ports, however I noticed you suggest to put iommu=soft in GRUB_CMDLINE_LINUX_DEFAULT=, whereas I was instructed to have it in the next line, so I have it like this: GRUB_CMDLINE_LINUX="iommu=soft", and that’s where I’ve had it for years without issue, does it make a difference?
quick google:
GRUB_CMDLINE_LINUX
Entries on this line are added to the end of the ‘linux’ command line (GRUB legacy’s “kernel” line) for both normal and recovery modes. It is used to pass options to the kernel.
GRUB_CMDLINE_LINUX_DEFAULT
This line imports any entries to the end of the ‘linux’ line (GRUB legacy’s “kernel” line). The entries are appended to the end of the normal mode only.
1 Like
See @omano’s post:
So, I think GRUB_CMDLINE_LINUX is safer. Or both. Both might also be good. More than that,
1 Like
Ok, yesterday was fine. No problems with my connection at all. But today i boot up i load the driver ( seems like i have to load it manually at boot) and then inxi -Fayztells me that kernel module r8168 instead of r8169, r8168 that was yesterday. I have also blacklisted r8168 in etc/ modprobe.d/blacklist.conf.
How is it possible that this changed overnight?
So im noticing that when i reboot i see both r8169 and r8168 as active kernel modules but dont have any drivers activated. So when i do modeprobe -v r8169 the driver gets activated but then only r8168 kernel module is shown…
Go in Manjaro Settings, and uninstall the 8168 driver.
I did. I rebboted and now inxi -Fayz shows me that r8169 is driver is loaded but no kernel modules.
Am i doing something wrong?
It is still trying to connect without a kernel module tho…
It is impossible to say - suffice to say - we have done what we could possibly do to help you mitigate this issue.
Ulimately is is out of our hands because we do not have hands-on and the mixing of advise from here and there - makes it impossible to get a definitive answer.
Therefore the topic is closed.
I’d strongly advise to run a live system to verify what is working an what is not - then if necessary reinstall the system using the gained knowledge.
Over and out.