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@xxxxxxxxxxxxx wrote:
Send arch-general mailing list submissions to
arch-general@xxxxxxxxxxxxx
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@xxxxxxxxxxxxx
You can reach the person managing the list at
arch-general-owner@xxxxxxxxxxxxx
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@xxxxxxxxxxxxx
Message-ID: <8db3s5xmfn.ln2@xxxxxxxxxxxxx>
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@xxxxxxxxxxxxx
Message-ID: <a7f3s5xqoq.ln2@xxxxxxxxxxxxx>
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@xxxxxxxxxxxxx
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.
