Re: [arch-general] arch-general Digest, Vol 48, Issue 10
Hey, I am new on the mailing-lists, but i try to behave! Well since i've upgraded to the next kernel, i am having some issues with modules, and since i wanted to try out the mailinglists, this seems to be the perfect opportunity for that. Since i've upgraded to 2.6.27 (testing repository) my pcspkr module is being loaded again, and i cant remove it (rmmod pcspkr) is the module-name differrent now? Please reply! thank you On Fri, Oct 10, 2008 at 12:01:00PM -0400, arch-general-request@archlinux.org wrote:
Send arch-general mailing list submissions to arch-general@archlinux.org
To subscribe or unsubscribe via the World Wide Web, visit http://archlinux.org/mailman/listinfo/arch-general or, via email, send a message with subject or body 'help' to arch-general-request@archlinux.org
You can reach the person managing the list at arch-general-owner@archlinux.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of arch-general digest..."
Today's Topics:
1. New udev (128-5) and Blacklisting Modules (Attila) 2. Re: New udev (128-5) and Blacklisting Modules (Attila)
----------------------------------------------------------------------
Message: 1 Date: Fri, 10 Oct 2008 09:04:40 +0200 From: Attila <attila@invalid.invalid> Subject: [arch-general] New udev (128-5) and Blacklisting Modules To: arch-general@archlinux.org Message-ID: <8db3s5xmfn.ln2@news.arcor.de> Content-Type: text/plain; charset=us-ascii
Hello together,
i recognized that the new udev package has a file framebuffer_blacklist in /etc/modprobe.d which blacklist the framebuffer modules.
So my question is about what is the best way to blacklist modules: Is it rc.conf or should i create my own file under /etc/modprobe.d?
For an example i print over the net and therefore i blacklist all modules for the parallel device in my rc.conf with "lp !parport !parport_p". Should i now better create a file /etc/modprobe.d/attilas_blacklist with this lines:
# Comment: No need for the parallel device blacklist lp blacklist parport blacklist parport_p
My next little question is that the point about Blacklisting in the file /usr/share/udev/readme-udev-arch.txt says that i can use MOD_BLACKLIST too but i have changed my rc.conf to use !modul because i think this way is depreceated?
Sorry if i oversee some informations but i'm a little bit confused about what is for archlinux the best way in the future to blacklist modules.
Last not least there is no question about that using !modul in the rc.conf works fine as before and there is no pressure for me to change it. But for myself a file with comments lines in modprobe.d would be more fine to separate blacklisting informations.
See you, Attila
------------------------------
Message: 2 Date: Fri, 10 Oct 2008 10:09:46 +0200 From: Attila <attila@invalid.invalid> Subject: Re: [arch-general] New udev (128-5) and Blacklisting Modules To: arch-general@archlinux.org Message-ID: <a7f3s5xqoq.ln2@news.arcor.de> Content-Type: text/plain; charset=us-ascii
On Freitag, 10. Oktober 2008 09:04 Attila wrote:
Sorry for answering myself but the reason is that udev 130 is out and i give it a little test.
For an example i print over the net and therefore i blacklist all modules for the parallel device in my rc.conf with "lp !parport !parport_p". Should i now better create a file /etc/modprobe.d/attilas_blacklist with this lines:
# Comment: No need for the parallel device blacklist lp blacklist parport blacklist parport_p
This does not work because all this modules get loaded and it seems that blacklisting works only in the rc.conf.
See you, Attila
------------------------------
_______________________________________________ arch-general mailing list arch-general@archlinux.org http://archlinux.org/mailman/listinfo/arch-general
End of arch-general Digest, Vol 48, Issue 10 ********************************************
On Saturday 11 October 2008 15:36, Wiegand Sergej wrote:
Hey, I am new on the mailing-lists, but i try to behave!
Well since i've upgraded to the next kernel, i am having some issues with modules, and since i wanted to try out the mailinglists, this seems to be the perfect opportunity for that. Since i've upgraded to 2.6.27 (testing repository) my pcspkr module is being loaded again, and i cant remove it (rmmod pcspkr) is the module-name differrent now? Please reply! thank you
Hi Wiegand, and welcome to the list. I don't have the 2.6.27 kernel, but something that does work (usually), is to add the following line to /etc/modprobe.conf. install pcspkr /bin/true Reboot, and the pcspkr module will be installed to /bin/true, which is like sending it to nowhere land. This list is low volume, and it may be better not to use the digest mode to receive postings from the list. Digest mode often creates problems, as many folks who use it just click on reply, which results in the whole of the digest being sent back to the list, and the subject line doesn't say anything about the subject they are replying to, or in your case, where this is a new thread, what exactly you are wanting to find out. A few well thought out words in a subject line, usually gets someones attention. It's better when asking a new question to just click on the "To" line on the latest digest you've received, (which in my case will open Kmails composer) fill in the subject line for your question, and compose your question. I hope that installing pcspkr to /bin/true resolves your problem, but if not, post back, preferably by starting a new thread, as above, and not using the "Digest " subject line. All the best. Nigel.
On Sat, 11 Oct 2008, Wiegand Sergej wrote:
Hey, I am new on the mailing-lists, but i try to behave!
Well since i've upgraded to the next kernel, i am having some issues with modules, and since i wanted to try out the mailinglists, this seems to be the perfect opportunity for that. Since i've upgraded to 2.6.27 (testing repository) my pcspkr module is being loaded again, and i cant remove it (rmmod pcspkr) is the module-name differrent now? Please reply! thank you
With the new kernel, you also need to blacklist snd_pcsp. The loading of this module can cause sound problems. If that's the case, blacklist the module and reboot. That's the easiest way to fix it.
On Fri, Oct 10, 2008 at 12:01:00PM -0400, arch-general-request@archlinux.org wrote:
Send arch-general mailing list submissions to arch-general@archlinux.org
To subscribe or unsubscribe via the World Wide Web, visit http://archlinux.org/mailman/listinfo/arch-general or, via email, send a message with subject or body 'help' to arch-general-request@archlinux.org
You can reach the person managing the list at arch-general-owner@archlinux.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of arch-general digest..."
Today's Topics:
1. New udev (128-5) and Blacklisting Modules (Attila) 2. Re: New udev (128-5) and Blacklisting Modules (Attila)
----------------------------------------------------------------------
Message: 1 Date: Fri, 10 Oct 2008 09:04:40 +0200 From: Attila <attila@invalid.invalid> Subject: [arch-general] New udev (128-5) and Blacklisting Modules To: arch-general@archlinux.org Message-ID: <8db3s5xmfn.ln2@news.arcor.de> Content-Type: text/plain; charset=us-ascii
Hello together,
i recognized that the new udev package has a file framebuffer_blacklist in /etc/modprobe.d which blacklist the framebuffer modules.
So my question is about what is the best way to blacklist modules: Is it rc.conf or should i create my own file under /etc/modprobe.d?
For an example i print over the net and therefore i blacklist all modules for the parallel device in my rc.conf with "lp !parport !parport_p". Should i now better create a file /etc/modprobe.d/attilas_blacklist with this lines:
# Comment: No need for the parallel device blacklist lp blacklist parport blacklist parport_p
My next little question is that the point about Blacklisting in the file /usr/share/udev/readme-udev-arch.txt says that i can use MOD_BLACKLIST too but i have changed my rc.conf to use !modul because i think this way is depreceated?
Sorry if i oversee some informations but i'm a little bit confused about what is for archlinux the best way in the future to blacklist modules.
Last not least there is no question about that using !modul in the rc.conf works fine as before and there is no pressure for me to change it. But for myself a file with comments lines in modprobe.d would be more fine to separate blacklisting informations.
See you, Attila
------------------------------
Message: 2 Date: Fri, 10 Oct 2008 10:09:46 +0200 From: Attila <attila@invalid.invalid> Subject: Re: [arch-general] New udev (128-5) and Blacklisting Modules To: arch-general@archlinux.org Message-ID: <a7f3s5xqoq.ln2@news.arcor.de> Content-Type: text/plain; charset=us-ascii
On Freitag, 10. Oktober 2008 09:04 Attila wrote:
Sorry for answering myself but the reason is that udev 130 is out and i give it a little test.
For an example i print over the net and therefore i blacklist all modules for the parallel device in my rc.conf with "lp !parport !parport_p". Should i now better create a file /etc/modprobe.d/attilas_blacklist with this lines:
# Comment: No need for the parallel device blacklist lp blacklist parport blacklist parport_p
This does not work because all this modules get loaded and it seems that blacklisting works only in the rc.conf.
See you, Attila
------------------------------
_______________________________________________ arch-general mailing list arch-general@archlinux.org http://archlinux.org/mailman/listinfo/arch-general
End of arch-general Digest, Vol 48, Issue 10 ********************************************
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Sat, 2008-10-11 at 15:36 +0200, Wiegand Sergej wrote:
Hey, I am new on the mailing-lists, but i try to behave!
Well since i've upgraded to the next kernel, i am having some issues with modules, and since i wanted to try out the mailinglists, this seems to be the perfect opportunity for that. Since i've upgraded to 2.6.27 (testing repository) my pcspkr module is being loaded again, and i cant remove it (rmmod pcspkr) is the module-name differrent now? Please reply! thank you
yes, the module is now called snd_pcsp. - Jonathan
participants (4)
-
Eric Belanger
-
Jonathan
-
Nigel Henry
-
Wiegand Sergej