toni wrote:what is the difference between compressed gzip modules (*.ko.gz) and not compressed (*.ko)? When is used ko.gz and when *.ko?
Well... one is compressed... and the other isn't.
I honestly can't think of a better answer to your question.
Arch has chosen to compress its modules, so we never use *.ko. The module management tools in the kmod package deal with this transparently.
Maybe the compressed option to save disk usage?
Thanks a lot.
]]>Do not remove it from kernel. Someone may need it.
+1 to blacklisting.
Cheers.
Andrzej
OK, I will take it into account. Thanks!
]]>what is the difference between compressed gzip modules (*.ko.gz) and not compressed (*.ko)? When is used ko.gz and when *.ko?
Well... one is compressed... and the other isn't.
I honestly can't think of a better answer to your question.
Arch has chosen to compress its modules, so we never use *.ko. The module management tools in the kmod package deal with this transparently.
]]>+1 to blacklisting.
Cheers.
Andrzej
]]>toni, I can't speak for anyone else, but your last post is not clear to me at all.
Blacklisting pcspkr as suggested by Army is the right way to go. This has now been confirmed by Graysky, Falconindy, and now me. This works / should work. Are you saying you have created the blacklist.conf file with that line, rebooted, yet you still have pcspkr loaded? If so, what is the full output from `lsmod | grep pcspkr`? Does pcspkr show as a dependency for another module (it shouldn't).
The .ko.gz files are normal.
What is it you want confirmed that has not already been confirmed?
I remember some days ago to blacklisting pcspkr using the two ways stated in the previous posts and lsmod was returning pcspkr (loaded) but I do not remember if it was being used by another module. Anyway, if all of you are saying this is the correct way to do it, I trust on you.
Regarding to kernel modules, what is the difference between compressed gzip modules (*.ko.gz) and not compressed (*.ko)? When is used ko.gz and when *.ko? In my case I wanted to delete pcspkr.ko but only existed pcspkr.ko.gz.
Thanks!
]]>Blacklisting pcspkr as suggested by Army is the right way to go. This has now been confirmed by Graysky, Falconindy, and now me. This works / should work. Are you saying you have created the blacklist.conf file with that line, rebooted, yet you still have pcspkr loaded? If so, what is the full output from `lsmod | grep pcspkr`? Does pcspkr show as a dependency for another module (it shouldn't).
The .ko.gz files are normal.
What is it you want confirmed that has not already been confirmed?
]]>toni wrote:graysky wrote:+1 for blacklist.
https://wiki.archlinux.org/index.php/Di … eaker_BeepBlacklisting in this way is not correct as pcspkr could be loaded by another non-blacklisted module depends on it. So be careful using this way when blacklisting modules.
Better adding below line to /etc/modprobe.d/blacklist.conf
... install module_name /bin/false ...
See below link:
https://wiki.archlinux.org/index.php/Ke … obe.d.2F_2This is a hack which leads to broken modules. Nothing depends on pcspkr. Blacklist it.
ok, thanks for the info as in that link it is not said that it leads to broken modules. Anyway, I think it would be good to indicate it in the link I have provided (The person in charge of maintaining it should provide this useful info).
Anyway, I would like to know if I am correct about that arch uses compressed gzip modules (*.ko.gz) instead of (*.ko). Could you confim it? and could you confirm me if what I have said in the first post is correct? So I can close this thread as solved. It was a doubt that I had.
Only one thing, about blacklisting despite it corresponds to another thread I opened some days aro: as you say, nothing depends on pcskpr, so why blacklisting it, it is loaded anyway and pc speaker emits a beep?
I remember to blacklisting it in the way you say, even doing what I have said, and systemd for some reason was loading it. I checked some days ago by doing:
lsmod | grep pcspkr
also, could you confirme that these two methods are effective for blacklisting? I am not sure at all. It would be good that someone could confirm it as well.
]]>graysky wrote:+1 for blacklist.
https://wiki.archlinux.org/index.php/Di … eaker_BeepBlacklisting in this way is not correct as pcspkr could be loaded by another non-blacklisted module depends on it. So be careful using this way when blacklisting modules.
Better adding below line to /etc/modprobe.d/blacklist.conf
... install module_name /bin/false ...
See below link:
https://wiki.archlinux.org/index.php/Ke … obe.d.2F_2
This is a hack which leads to broken modules. Nothing depends on pcspkr. Blacklist it.
]]>+1 for blacklist.
https://wiki.archlinux.org/index.php/Di … eaker_Beep
Blacklisting in this way is not correct as pcspkr could be loaded by another non-blacklisted module depends on it. So be careful using this way when blacklisting modules.
Better adding below line to /etc/modprobe.d/blacklist.conf
...
install module_name /bin/false
...
See below link:
https://wiki.archlinux.org/index.php/Ke … obe.d.2F_2
blacklist pcspkr
in it.
]]>/lib/modules/`uname -r`/kernel/drivers/input/misc/
and then I perform the following:
depmod -a
and finally, reboot the system, is it enough, right?
Thanks!
]]>