How to avoid kernel module i8k gets loaded

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

How to avoid kernel module i8k gets loaded

Postby bertaerts » Feb 23rd, '15, 22:03

I don't want the kernel module i8k to be loaded as it interrupts the sound on my Dell Inspiron 17R SE 7720.
I reported about this in every detail in the forum Advanced Support https://forums.mageia.org/en/viewtopic.php?f=8&t=8531&p=53579&hilit=i8k#p53579.

Now in Mageia 5 I want to avoid that this module gets loaded.
So I removed it from /etc/modprobe.preload
Code: Select all
# /etc/modprobe.preload: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line.  Comments begin with                                                     
# a `#', and everything on the line after them are ignored.                                                         
# this file is for module-init-tools (kernel 2.5 and above) ONLY                                                     
# for old kernel use /etc/modules                                                                                   
                                                                                                                     
# i8k
# cat /proc/i8k causes sound interrupt of 400 milliseconds
# i8k is special module for Dell Inspiron Notebooks,
# but is not up to date for 17R SE 7720
nvram
dvb_usb_dib0700
evdev
evdev


But it is still loaded.

Then I tried to blacklist it in /etc/modprobe.d/blacklist_i8k.conf:

Code: Select all
[bert@Dell7720Mageia5 modprobe.d]$ cat blacklist_i8k.conf
# cat /proc/i8k causes sound interrupt of 400 milliseconds
# i8k is special module for Dell Inspiron Notebooks,
# but is not up to date for 17R SE 7720
# Do not load the 'i8k' module on boot.
blacklist i8k


That does not work either.
How should I do it then?
bertaerts
 
Posts: 181
Joined: Apr 6th, '11, 12:19

Re: How to avoid kernel module i8k gets loaded

Postby pete910 » Feb 23rd, '15, 22:14

Make sure its not specified in modules.conf, or anywhere else for that matter.

You may need to rebuild the initrd image as I don't know if its a module that's loaded on initial boot
User avatar
pete910
 
Posts: 357
Joined: Jan 8th, '12, 18:53

Re: How to avoid kernel module i8k gets loaded

Postby doktor5000 » Feb 23rd, '15, 22:20

pete910 wrote:You may need to rebuild the initrd image as I don't know if its a module that's loaded on initial boot

Code: Select all
lsinitrd /boot/some-initrd.img | grep i8k
should help with finding out if it's inside initrd.
And via kernel option rdblacklist=i8k it can be blacklisted by being loaded from initrd - temporarily for testing :)
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18052
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: How to avoid kernel module i8k gets loaded

Postby bertaerts » Feb 23rd, '15, 23:28

Code: Select all
lsinitrd /boot/some-initrd.img | grep i8k

gave back nothing.
So conclusion is i8k is not loaded on initial boot.

I commented out i8k in /etc/modprobe.preload and blacklisted it in /etc/modprobe.d/blacklist_i8k.conf
For the moment the module is not loaded at boot.
I first thought that blacklisting would overrule the loading in modprobe.preload.
Apparantly not...
bertaerts
 
Posts: 181
Joined: Apr 6th, '11, 12:19

Re: How to avoid kernel module i8k gets loaded

Postby doktor5000 » Feb 23rd, '15, 23:38

bertaerts wrote:
Code: Select all
lsinitrd /boot/some-initrd.img | grep i8k

I first thought that blacklisting would overrule the loading in modprobe.preload.

The only thing that blacklisting does is prevent automatic module load.
You could still manually do modprobe modulename to load it, or as in your example modprobe.preload would load it.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18052
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany


Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron