Failing to blacklist a module

Janom · 2022-02-06 13:54:56

So i am trying to blacklist the "r8169" module, since it doesn't work properly, and installed the "r8168".
These two modules are conflicting and it messes up with my network.
I tried blacklisting the first one in /etc/modprobe.d/blacklist.conf but it doesn't work.
The output of lspci -v:

08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16)
        Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
        Flags: bus master, fast devsel, latency 0, IRQ 58, IOMMU group 0
        I/O ports at f000 [size=256]
        Memory at fcd04000 (64-bit, non-prefetchable) [size=4K]
        Memory at fcd00000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8168
        Kernel modules: r8169, r8168

When I nano into the blacklist.conf file, the module i tried blacklisting is there, but it doesn't seem to have an effect.

Head_on_a_Stick · 2022-02-06 13:58:16

Try

install r8169 /bin/true

As per the Note on the ArchWiki "Kernel module" page.

Trilby · 2022-02-06 14:00:43

See the "Note" box here.

seth · 2022-02-06 14:03:13

The 8168 package ships a blacklisting config and the r8619 module isn't used per your lspci.
A general pitfall of blsacklisting are modules in the initramfs, but that does not appear to be a concern hete.

This is probably an xy-problem and you should seek assistance for your network issues rather than for an assumed cause.

Janom · 2022-02-06 14:05:28

Head_on_a_Stick wrote:

Try
install r8169 /bin/true
As per the Note on the ArchWiki "Kernel module" page.

I get the following:

install: cannot stat 'r8169': No such file or directory

Trilby · 2022-02-06 14:07:48

You are not suppose to enter that command in the shell - that's why HoaS referenced the wiki page that you should be reading, and it's the same very short section that I gave a direct link to.

Of course, Seth is likely right here that this is probably not what you want to do anyways.

Janom · 2022-02-06 14:12:46

My bad I misunderstood. I did read the note, before posting this.
I'm still not sure as to if i did this right yet.

I posted "install r8169 /bin/true" inside blacklist.conf .

Janom · 2022-02-06 14:18:32

Trilby wrote:

You are not suppose to enter that command in the shell - that's why HoaS referenced the wiki page that you should be reading, and it's the same very short section that I gave a direct link to.
Of course, Seth is likely right here that this is probably not what you want to do anyways.

What's something else that could be causing "wired connection deactivated"?

Trilby · 2022-02-06 14:29:22

Uh, what? First, if you want help troubleshooting a problem that has nothing to do with blacklisting a module, that should be in a separate thread. Second, in that thread you'll have to actually describe what the problem is before we could even possibly speculate on a cause. In that new thread, post a description of the symptoms, error output, and logs.

seth · 2022-02-06 14:37:42

Make sure to post your system journal there.

Arch Linux

#1 2022-02-06 13:54:56

Failing to blacklist a module

#2 2022-02-06 13:58:16

Re: Failing to blacklist a module

#3 2022-02-06 14:00:43

Re: Failing to blacklist a module

#4 2022-02-06 14:03:13

Re: Failing to blacklist a module

#5 2022-02-06 14:05:28

Re: Failing to blacklist a module

#6 2022-02-06 14:07:48

Re: Failing to blacklist a module

#7 2022-02-06 14:12:46

Re: Failing to blacklist a module

#8 2022-02-06 14:18:32

Re: Failing to blacklist a module

#9 2022-02-06 14:29:22

Re: Failing to blacklist a module

#10 2022-02-06 14:37:42

Re: Failing to blacklist a module

Board footer