Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
What is loading module pcspkr (inspite blacklist)?Hello Debian Users, I thought maybe somebody knows what loads the module pcspkr on a sid (up I even blacklisted the module in /etc/modprobe.d/00local (I blacklisted Am I missing something? Regards, -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
What is loading module pcspkr (inspite blacklist)?
On Friday 02 February 2007 03:16, Andrei Popescu wrote:
> Hello Debian Users,
>
> I thought maybe somebody knows what loads the module pcspkr on a sid (up
> to date) with stock kernel 2.6.18-3-686?
>
> I even blacklisted the module in /etc/modprobe.d/00local (I blacklisted
> ipv6 in the same file and it works correctly) and commented out the
> relevant entry in /etc/modprobe.d/pnp-hotplug
>
Hi Andrei,
No solution I'm afraid, just a "me too": this came up a little while back here
as:
etch : not loading some kernel modules howto ?
No solution was posted at the time; it happens on my etch box too. I found a
reference to pcspkr in /etc/udev/persistent-input.rules and commented it out;
but that pesky module just won't stay down!
Regards,
John
--
What is loading module pcspkr (inspite blacklist)?
On Fri, Feb 02, 2007 at 03:25:16PM +1100, John O'Hagan wrote:
> On Friday 02 February 2007 03:16, Andrei Popescu wrote:
> > Hello Debian Users,
> >
> > I thought maybe somebody knows what loads the module pcspkr on a sid (up
> > to date) with stock kernel 2.6.18-3-686?
> >
> > I even blacklisted the module in /etc/modprobe.d/00local (I blacklisted
> > ipv6 in the same file and it works correctly) and commented out the
> > relevant entry in /etc/modprobe.d/pnp-hotplug
> >
>
> Hi Andrei,
>
> No solution I'm afraid, just a "me too": this came up a little while back here
> as:
>
> etch : not loading some kernel modules howto ?
>
> No solution was posted at the time; it happens on my etch box too. I found a
> reference to pcspkr in /etc/udev/persistent-input.rules and commented it out;
> but that pesky module just won't stay down!
for the truly inelegant solution, what if you just rename/move aside
that thing? surely will cause an error, but will it make the whole
system barf? doubt it.
A
What is loading module pcspkr (inspite blacklist)?
On Thu, 1 Feb 2007 20:38:06 -0800
Andrew Sackville-West wrote:
> On Fri, Feb 02, 2007 at 03:25:16PM +1100, John O'Hagan wrote:
> > On Friday 02 February 2007 03:16, Andrei Popescu wrote:
> > > Hello Debian Users,
> > >
> > > I thought maybe somebody knows what loads the module pcspkr on a
> > > sid (up to date) with stock kernel 2.6.18-3-686?
> > >
> > > I even blacklisted the module in /etc/modprobe.d/00local (I
> > > blacklisted ipv6 in the same file and it works correctly) and
> > > commented out the relevant entry in /etc/modprobe.d/pnp-hotplug
> > >
> >
> > Hi Andrei,
> >
> > No solution I'm afraid, just a "me too": this came up a little
> > while back here as:
> >
> > etch : not loading some kernel modules howto ?
> >
> > No solution was posted at the time; it happens on my etch box too.
> > I found a reference to pcspkr in /etc/udev/persistent-input.rules
> > and commented it out; but that pesky module just won't stay down!
>
> for the truly inelegant solution, what if you just rename/move aside
> that thing? surely will cause an error, but will it make the whole
> system barf? doubt it.
In the end I just did that, thinking I could get more clues from an
error message. And guess what, no error messages! Now that's strange...
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
[Workaround] What is loading module pcspkr (inspite blacklist)?
On Sat, 10 Feb 2007 10:33:21 +0200
Andrei Popescu wrote:
> On Thu, 1 Feb 2007 20:38:06 -0800
> Andrew Sackville-West wrote:
>
> > On Fri, Feb 02, 2007 at 03:25:16PM +1100, John O'Hagan wrote:
> > > On Friday 02 February 2007 03:16, Andrei Popescu wrote:
> > > > Hello Debian Users,
> > > >
> > > > I thought maybe somebody knows what loads the module pcspkr on a
> > > > sid (up to date) with stock kernel 2.6.18-3-686?
> > > >
> > > > I even blacklisted the module in /etc/modprobe.d/00local (I
> > > > blacklisted ipv6 in the same file and it works correctly) and
> > > > commented out the relevant entry in /etc/modprobe.d/pnp-hotplug
> > > >
> > >
> > > Hi Andrei,
> > >
> > > No solution I'm afraid, just a "me too": this came up a little
> > > while back here as:
> > >
> > > etch : not loading some kernel modules howto ?
> > >
> > > No solution was posted at the time; it happens on my etch box too.
> > > I found a reference to pcspkr in /etc/udev/persistent-input.rules
> > > and commented it out; but that pesky module just won't stay down!
> >
> > for the truly inelegant solution, what if you just rename/move aside
> > that thing? surely will cause an error, but will it make the whole
> > system barf? doubt it.
>
> In the end I just did that, thinking I could get more clues from an
> error message. And guess what, no error messages! Now that's
> strange...
I filled a bug with module-init-tools. I got a prompt reply from the
maintainer (who also closed my bug) to see bug #407256 for more info.
Apparently it's an upstream kernel bug.
A proper Debian Way (tm) to solve this would be to add:
install pcspkr /bin/true
to a /etc/modprobe.d/00local file. This makes it consistent across
upgrades, as opposed to the renaming solution.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
What is loading module pcspkr (inspite blacklist)?
On Thu, Feb 01, 2007 at 06:16:35PM +0200, Andrei Popescu wrote:
> Hello Debian Users,
>
> I thought maybe somebody knows what loads the module pcspkr on a sid (up
> to date) with stock kernel 2.6.18-3-686?
>
> I even blacklisted the module in /etc/modprobe.d/00local (I blacklisted
> ipv6 in the same file and it works correctly) and commented out the
> relevant entry in /etc/modprobe.d/pnp-hotplug
>
> Am I missing something?
>
> Regards,
> Andrei
> P.S. Of course I can 'modprobe -r pcspkr', but this is not a very
> elegant solution.
> --
All I can add is that on one of my alsa recongnized sound cards, it had
a control for the pc speaker and I mute it. One solution.
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keysever: subkeys.pgp.net | my NPO: cfsg.org |
discover
I'm currently trying to solve the same problem. It looks like maybe the discover1 package is the culprit? I'm about to fiddle with /etc/discover.conf & /etc/discover.conf-2.6 and reboot.
solution to prevent modules from loading
So here's what I did on my Etch system running kernel 2.6.18:
used modconf to make sure the modules I didn't want weren't in the associated manual module load config files.
installed the discover package (which uses discover2 as opposed to discover1)
edited /etc/discover-modprobe.conf and added the applicable modules to the skip line.
AND
made files /etc/modprobe.d with blacklist lines for the same modules.
AFAICT all of that was necessary. Hopefully I didn't leave anything out. It works for me now.