[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#604197: marked as done (lenny->squeeze: pc speaker don't beep after upgrade)



Your message dated Fri, 10 Jun 2011 00:53:30 -0500
with message-id <20110610055329.GB27049@elie>
and subject line Re: PC speaker does not work after upgrade to squeeze
has caused the Debian Bug report #604197,
regarding lenny->squeeze: pc speaker don't beep after upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
604197: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604197
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: normal


I don't know the package this bug should be filed against,
so I'm sending it here.

After upgrading from lenny to squeeze the beeps on the
PC speaker don't sound anymore.

At the very beginning of the boot process the following error
is shown:

Waiting for /dev to be fully populated...[    4.151254] Error:
Driver 'pcspkr' is already registered, aborting...

After login I can see with lsmod that pcspkr is loaded, but
beeps (echo ctrl-V ctrl-G return)  don't sound.

If I run:

modprobe -r pcspkr
modprobe pcspkr

then the beeps work again as expected.

As a workaround, I have made the following:

1. I have added the line "blacklist pcspkr" to
/etc/modprobe.d/blacklist.conf

2. I have added the line "pcspkr" to /etc/modules

Now the pcspkr module is loaded later than before, and it
works for the very beginning:

[    7.023375] Console: switching to colour dummy device 80x25
[    7.023558] Console: switching to colour frame buffer device 240x75
[    7.400087] fb0: radeondrmfb frame buffer device
[    7.400090] registered panic notifier
[    7.400115] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
[    7.832740] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[    7.832783] HDA Intel 0000:00:1b.0: setting latency timer to 64
[    7.968049] hda_codec: ALC889: BIOS auto-probing.
see this_> [    7.969945] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input4
[    9.535854] Adding 2000084k swap on /dev/sda5.  Priority:-1 extents:1 across:2000084k 
[   10.049272] EXT3 FS on dm-0, internal journal
[   10.291630] Initializing USB Mass Storage driver...
[   10.291665] usbcore: registered new interface driver usb-storage
[   10.291968] USB Mass Storage support registered.
[   10.342942] lp0: using parport0 (interrupt-driven).
[   10.643094] f71882fg: Found f71889fg chip at 0xa00, revision 21
[   10.643349] f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode
[   10.643353] f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode
[   10.643356] f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode
see this _> [   10.684792] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   12.831363] kjournald starting.  Commit interval 5 seconds

It seems that it depends on the moment the pcspkr module is loaded.

Thanks,
Gonzalo.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



--- End Message ---
--- Begin Message ---
Version: 2.6.38-5

Petr Salinger wrote:

> It works correctly for me with kernel from testing (2.6.38-2-amd64).

Thanks, marking accordingly.


--- End Message ---

Reply to: