On Sat, 10 Feb 2007 10:33:21 +0200
Andrei Popescu <[EMAIL PROTECTED]> wrote:
> On Thu, 1 Feb 2007 20:38:06 -0800
> Andrew Sackville-West <[EMAIL PROTECTED]> 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)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
