Is anyone looking at this? I've tried the two hacks posted and neither
of them work for me on the HP Pavilion.
It's troubling if this hasn't been addressed after a year. Screen
brightness is a health and safety concern. It may seem like a small
issue, but being able to see the screen comfortably
This now appears to have been mostly resolved following a recent
update... although headphone detection/playback is only working on one
speaker (the one that I managed to get sound through before).
Still, it's great to have the speakers and microphone back in action, as
well as one headphone
Having put my faith in Ubuntu, and upgraded to the new version at the
end of April, I've now been left with pretty much no audio for the best
part of six weeks. It's meant I'm unable to use the internet telephony I
rely on to stay in touch with relatives and friends in my home country,
and has
This bug would benefit from some input from someone in the Ubuntu sound
team, as it appears (from discussion on the Alsa mantis tracker) that
Alsa is installed in non-standard locations in Ubuntu. Therefore ubuntu-
specific knowledge is required to investigate further!
--
No sound in Ubuntu 9.04
Please could someone with Ubuntu/Alsa specific knowledge take a look at
the Mantis thread? It appears Ubuntu uses non-standard configuration for
Alsa, so Ubuntu-specific knowledge will be required to resolve this
problem.
--
No sound in Ubuntu 9.04
https://bugs.launchpad.net/bugs/368427
You
** Also affects: alsa-utils
Importance: Undecided
Status: New
--
No sound in Ubuntu 9.04
https://bugs.launchpad.net/bugs/368427
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I get no sound at all (have tried creating another account). Suspect you
may have a different problem... check your existing users are groups of
the three pulse audio user groups under user administration.
--
No sound in Ubuntu 9.04
https://bugs.launchpad.net/bugs/368427
You received this bug
Alsa debugging info here: http://www.alsa-
project.org/db/?f=2fe42dc572fff9e05357dc5a48adfa250ee81d07
(turlinux - you may wish to capture some alsa debugging info as well,
instructions are here: https://wiki.ubuntu.com/DebuggingSoundProblems)
--
No sound in Ubuntu 9.04
I've now worked through the instructions here too:
http://ubuntuforums.org/showthread.php?t=205449
Have recompiled my Alsa drivers successfully but sudo modprobe snd-
still returns no results:
$ sudo modprobe snd-
FATAL: Module snd_ not found.
--
No sound in Ubuntu 9.04
No sound following upgrade to 9.0.4 here, too. PulseAudio Volume Control
shows system thinks it's playing sound.
$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express
Testing according to instructions in this forum thread suggest the
problem is with ALSA and not PulseAudio...
http://ubuntuforums.org/showthread.php?p=7171670#post7171670
--
No sound in Ubuntu 9.04
https://bugs.launchpad.net/bugs/368427
You received this bug notification because you are a
If you right-click the speaker icon on the top panel, and choose Open
volume control, check you're on the Playback tab. Do you have a slider
for PCM? Is it at max?
--
CRITICAL ERROR: Since update, Ubuntu 8.10 plays no sound (MacBook Pro)
https://bugs.launchpad.net/bugs/328030
You received this
I'm running Ubuntu 8.10 64-bit on an HP Omnibook DV3507 which has also
worked fine with audio in the past. Today I rebooted and now there's no
sound.. just an ominous crackle! Am not convinced this issue is confined
to Macbooks.
Bugs #328869, #326864 and #325547 also appear to relate to vanishing
Hi Jean-Christophe,
Do you think the libao.conf file was changed as part of the cdemu-daemon
update?
Sound on my laptop has worked fine with Ubuntu for several months now,
but today I rebooted and now it only crackles. My conf file also points
to alsa, but I'm loathe to change settings and mask
Have you tried using a conventional set of headphones plugging into the
headphone out socket that is connected to your sound card?
My sound has also just stopped working; rebooted this morning for the
first time in a few days, and now it just crackles when the system tries
to play something.
Details from my system
vwil...@hp-pavilion:~$ aplay -l
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: STAC92xx Digital [STAC92xx Digital]
Just found Bug #272321 where a problem with PCM output being muted
without user intervention and a crackling noise while muted has been
identified:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/272321
Un-muting PCM has solved this issue for me, but I don't memorize the
status of all
This bug is still appearing; today I spent several hours trying to debug
my sound drivers when a PulseAudio update had muted PCM (not all my
sliders are at max by default, and I don't memorize where they all are -
so not easy to find) and then produced just crackling instead of sound.
Then I run
Update: I've now fixed this problem on my laptop by re-setting the PCM
volume to max - see this existing bug for details:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/272321
If this fixes the problem for you perhaps this bug should be updated to
point to the PCM one (272321) so users
Have you seen this existing bug?
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/272321
If you're unable to set the PCM volume at all, see related bug
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/315971
If this fixes the problem for you perhaps this bug should be updated
Have you seen this existing bug?
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/272321
If you're unable to set the PCM volume at all, see related bug
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/315971
If this fixes the problem for you perhaps this bug should be updated
Here's the /tmp/hal.log file for my HP DV3507ea with NVidia GeForce
9300GS card.
I pressed the brightness down button three times, then another three
times. Then I pressed the brightness up button three times, then
another three times. Then I unplugged the power, then plugged it back
in, twice -
Here's the /tmp/lshal.txt file for my HP DV3507ea with NVidia GeForce
9300GS card.
I pressed the brightness down button three times, then another three
times. Then I pressed the brightness up button three times, then
another three times. Then I unplugged the power, then plugged it back
in, twice
Ok, the fix probably doesn't apply to me. In terms of behaviour, it does
appear to be exactly the same bug, though - I press the buttons and the
little brightness symbol appears, and looks like it is being increased
or decreased, but the screen brightness stays exactly the same. I unplug
the power
Here's the /var/log/kern.log file for my HP DV3507ea with NVidia
GeForce 9300GS card.
I pressed the brightness down button three times, then another three
times. Then I pressed the brightness up button three times, then
another three times. Then I unplugged the power, then plugged it back
in,
Hi Duyn,
Thanks for the info you've posted. I just tried upgrading the kernel as
suggested but it didn't like the NVidia drivers (and in basic graphics
mode it wouldn't let me change the brightness, which doesn't auger
well).
I've tried using the xrandr command but this is what happens:
Hi folks,
I appear to be having exactly the same problem on a brand new HP
DV3507EA (arrived from HP yesterday :D ). It produces errors with both
hibernate and suspend. This is the first time I've ever used linux so
I'm sorry I really don't know how to use those two tools dmesg and
lspci, but I
27 matches
Mail list logo
