kernel module removal

Forum Forums New users New Users and General Questions kernel module removal

This topic contains 15 replies, has 5 voices, and was last updated by sleekmason Apr 19-8:10 am.

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
  • #9113

    I have disabled parport from my latest kernel build as I do not require Parallel ports. This leaves warning messages about failing to install ppdev, parport_pc, and lp (options related).

    How do I remove whatever is still activating the warning messages? (not the messages themselves, Don’t want to lose kernel log level)


    Root of the matter: Why am I getting info on boot about drivers failing if I have removed/unchecked the corresponding drivers in the kernel .config file using make menuconfig. Shouldn’t unchecking these drivers also remove any info printed?


    Narrowing it down further: Why is modprobe trying to load drivers that no longer are present in the kernel? and, how to get it to stop. Adding a file blacklist.conf to /etc/modprobe.d, and listing as “blacklist ModuleName” didnt have any affect. The file is being read – checked with another command.


    It appears that the other modules depend on paraport, e.g., ppdev, parport_pc, and lp. If you don’t need them then you will need to either remove them in the kernel, or remove them via:

    module -r
    On lsmod on my desktop shows:

    $ lsmod
    Module                  Size  Used by
    bnep                   20480  2
    pci_stub               16384  1
    vboxpci                28672  0
    vboxnetadp             28672  0
    vboxnetflt             32768  0
    vboxdrv               421888  3 vboxnetadp,vboxnetflt,vboxpci
    nfsd                  339968  2
    auth_rpcgss            61440  1 nfsd
    nfs_acl                16384  1 nfsd
    nfs                   241664  0
    lockd                  86016  2 nfsd,nfs
    grace                  16384  2 nfsd,lockd
    fscache                77824  1 nfs
    sunrpc                299008  6 auth_rpcgss,nfsd,nfs_acl,lockd,nfs
    ip6t_REJECT            16384  1
    nf_reject_ipv6         16384  1 ip6t_REJECT
    nf_log_ipv6            16384  5
    af_packet              45056  2
    xt_hl                  16384  22
    ip6t_rt                16384  3
    nf_conntrack_ipv6      16384  10
    nf_defrag_ipv6         32768  1 nf_conntrack_ipv6
    ipt_REJECT             16384  1
    nf_reject_ipv4         16384  1 ipt_REJECT
    xt_comment             16384  6
    nf_log_ipv4            16384  5
    nf_log_common          16384  2 nf_log_ipv6,nf_log_ipv4
    xt_LOG                 16384  10
    xt_recent              20480  4
    xt_limit               16384  13
    xt_tcpudp              16384  24
    xt_addrtype            16384  4
    nf_conntrack_ipv4      16384  10
    nf_defrag_ipv4         16384  1 nf_conntrack_ipv4
    xt_conntrack           16384  20
    ip6table_filter        16384  1
    ip6_tables             24576  1 ip6table_filter
    nf_conntrack_netbios_ns    16384  0
    nf_conntrack_broadcast    16384  1 nf_conntrack_netbios_ns
    nf_nat_ftp             16384  0
    nf_nat                 28672  1 nf_nat_ftp
    nf_conntrack_ftp       16384  1 nf_nat_ftp
    nf_conntrack          114688  8 nf_conntrack_ipv6,nf_conntrack_ftp,nf_conntrack_ipv4,nf_conntrack_broadcast,nf_nat_ftp,nf_conntrack_netbios_ns,xt_conntrack,nf_nat
    libcrc32c              16384  2 nf_conntrack,nf_nat
    iptable_filter         16384  1
    ip_tables              24576  1 iptable_filter
    x_tables               32768  15 xt_comment,xt_LOG,ipt_REJECT,ip_tables,iptable_filter,xt_tcpudp,xt_limit,ip6t_REJECT,xt_recent,ip6table_filter,xt_addrtype,ip6t_rt,xt_conntrack,ip6_tables,xt_hl
    parport_pc             45056  0
    ppdev                  20480  0
    lp                     20480  0
    parport                49152  3 lp,parport_pc,ppdev
    dm_crypt               40960  0
    dm_mod                131072  1 dm_crypt
    btusb                  45056  0
    btrtl                  16384  1 btusb
    btbcm                  16384  1 btusb
    btintel                16384  1 btusb
    bluetooth             385024  26 btrtl,btintel,bnep,btbcm,btusb
    ecdh_generic           24576  1 bluetooth
    iTCO_wdt               16384  0
    iTCO_vendor_support    16384  1 iTCO_wdt
    input_leds             16384  0
    isight_firmware        16384  0
    arc4                   16384  2
    usblp                  20480  0
    b43                   434176  0
    evdev                  24576  14
    bcma                   57344  1 b43
    mac80211              724992  1 b43
    radeon               1585152  3
    applesmc               24576  0
    cfg80211              622592  2 b43,mac80211
    input_polldev          16384  1 applesmc
    rfkill                 24576  3 bluetooth,cfg80211
    ttm                   106496  1 radeon
    drm_kms_helper        163840  1 radeon
    coretemp               16384  0
    drm                   393216  6 radeon,ttm,drm_kms_helper
    kvm_intel             221184  0
    fb_sys_fops            16384  1 drm_kms_helper
    syscopyarea            16384  1 drm_kms_helper
    lpc_ich                28672  0
    kvm                   610304  1 kvm_intel
    sysfillrect            16384  1 drm_kms_helper
    sysimgblt              16384  1 drm_kms_helper
    i2c_algo_bit           16384  1 radeon
    irqbypass              16384  1 kvm
    bfq                    61440  2
    rng_core               16384  1 b43
    apple_bl               16384  0
    shpchp                 36864  0
    snd_hda_codec_idt      53248  1
    snd_hda_codec_generic    77824  1 snd_hda_codec_idt
    snd_hda_intel          36864  1
    snd_hda_codec         118784  3 snd_hda_intel,snd_hda_codec_idt,snd_hda_codec_generic
    snd_hda_core           73728  4 snd_hda_intel,snd_hda_codec,snd_hda_codec_idt,snd_hda_codec_generic
    snd_hwdep              16384  1 snd_hda_codec
    snd_pcm                98304  3 snd_hda_intel,snd_hda_codec,snd_hda_core
    snd_timer              32768  1 snd_pcm
    snd                    81920  9 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_hda_codec_idt,snd_timer,snd_hda_codec_generic,snd_pcm
    soundcore              16384  1 snd
    intel_agp              20480  0
    intel_gtt              24576  1 intel_agp
    video                  40960  0
    button                 16384  0
    acpi_cpufreq           16384  1
    btrfs                1236992  0
    xor                    24576  1 btrfs
    zstd_decompress        86016  1 btrfs
    zstd_compress         188416  1 btrfs
    xxhash                 16384  2 zstd_compress,zstd_decompress
    raid6_pq              118784  1 btrfs
    hid_appleir            16384  0
    hid_generic            16384  0
    ssb_hcd                16384  0
    i2c_i801               32768  0
    i2c_core               61440  5 i2c_algo_bit,radeon,i2c_i801,drm_kms_helper,drm
    ssb                    73728  2 b43,ssb_hcd
    firewire_ohci          45056  0
    mmc_core              131072  2 b43,ssb
    firewire_core          69632  1 firewire_ohci
    pcmcia                 49152  1 ssb
    pcmcia_core            24576  1 pcmcia
    rtc_cmos               20480  1
    sky2                   655

    You see the used by:

    But I’m no expert.


    • This reply was modified 11 months, 1 week ago by ohh.
    • This reply was modified 11 months, 1 week ago by ohh.
    • This reply was modified 11 months, 1 week ago by ohh.

    Every matter requires prior knowledge.

    - Du Mu
    The Art of War


    Thank you for responding.

    The whole group was disabled. Parport is the parallel port driver, and the other three have functions related.

    The error message is saying that modprobe is searching for the drivers in /lib/modules/(my-current-kernel-version), and there is also a human readable copy of the list of modules to be activated/installed on boot named modules.dep in the same folder.
    None of the 4 modules exist in /modules.dep, – (parport_pc, ppdev, lp, and parport).
    My understanding is that modprobe reads from the list created there, and therefore shouldn’t be throwing messages. I also should note that I updated initramfs again just in case.


    I should say that this is by no means a huge deal and is a pretty obscure question to ask. Not exactly distro related. I have options like changing log levels or simply putting them back into the kernel. This is a furthering my education question. Seems like it might come in handy someday.


    Have you checked to make sure they are not listed in /etc/modules ?
    I believe lp gets added there during installation, possibly its dependencies also.


    Yes, Nothing listed in /etc/modules but loop. Could udev be finding the hardware and expects modprobe to find the drivers?


    Why not just blacklist them by creating a text file in /etc/modprobe.d/, say “my_blacklist” with the lines:

    blacklist parport_pc
    blacklist ppdev




    Why not just blacklist them by creating a text file in /etc/modprobe.d

    could, but the point is to remove the option entirely from the kernel without dealing with the messages. There is no significant benefit to disabling them. I wouldn’t advise anyone to bother. The point is to learn more about the system and how it works.

    Something, I’m guessing eudev/udev is showing the port and expecting drivers to be loaded. Shouldn’t eudev have a way to turn off those options?

    I’m guessing not at this point but don’t really know.

    The answer could be obvious in that modprobe.d (and associated) are what is being used for user interface, and no human usable file exists before then. If there was something further up the line (other than bios), we would be using that to set instructions for driver install instead.

    This is me guessing . . a lot.


    Did a little digging. This is probably what I am looking for.

    How to functionally edit a file in dev using the major/minor number for the driver is beyond my skill set. I don’t reckon I need to go any further if this is it. Just not worth the trouble, unless I’m missing something.

    │ │
    │ This creates a tmpfs/ramfs filesystem instance early at bootup. │
    │ In this filesystem, the kernel driver core maintains device │
    │ nodes with their default names and permissions for all │
    │ registered devices with an assigned major/minor number. │
    │ Userspace can modify the filesystem content as needed, add │
    │ symlinks, and apply needed permissions. │
    │ It provides a fully functional /dev directory, where usually │
    │ udev runs on top, managing permissions and adding meaningful │
    │ symlinks. │
    │ In very limited environments, it may provide a sufficient │
    │ functional /dev without any further help. It also allows simple │
    │ rescue systems, and reliably handles dynamic major/minor numbers.



    That’s very interesting, don’t think I’d personally try it on my main box.
    Definitely beyond my skill level.


    Every matter requires prior knowledge.

    - Du Mu
    The Art of War


    howdy ohh!

    I’ll probably mess with it again sometime but agree I don’t want to have reinstall anytime soon.

    Already lost udev in smxi yesterday piddling around. Did the cruft removal where it says “one by one” – Took that to mean “verify before each one” as there was already an option for “all”. I then watched it indeed remove the packages one by one all in a row. geez. There goes udev.

    Anyway, my laptop would still boot to fluxbox, but no mouse or keys, so I wound up attaching a cable from my router to get internet, booted into init 3, ran Ceni, installed udev, rebooted into fluxbox, then dist-upgraded using “dev” at the end of the repo line. Yikes!


    Howdy sleekmason,

    I try to keep my desktop stable, it is an older iMac 2006, but I do play around on my laptops as it is dead simple to reinstall if I foobar them!!
    Which does occasionally occur.
    But an education always requires payment of some kind.


    Every matter requires prior knowledge.

    - Du Mu
    The Art of War


    {ESL here}
    Had you modded the kernel in use?
    If yes, what were your objectives?
    If to optimize an old hardware, please provide main lines/directives, or you don’t have time, maybe a web tutorial suggestion.
    After default way upgrade, the system is 4.10.5-antix.3-amd64-smp . Have you notice any slow down? This netbook is Atom N450 dated Q1’10 with 2 GB [seems like there is a flat out uninvited mining daemon]
    off-topic: JFS, instead of ext4?
    attached a htop shot.

    • This reply was modified 11 months ago by nbah.
Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic.