This bug is closed. If you have any problems at all then please open a
new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/449762
Title:
No sound with intel-hda without "alsa force-reload"
To ma
Hi,
I experience this bug again with Ubuntu 18.10.
I need to do:
sudo alsa force-reload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/449762
Title:
No sound with intel-hda without "alsa force-reload
Hi,
I experience this bug again with Ubuntu 14.10.
I need to do:
sudo alsa force-reload
To make it work permanently, I need to edit /etc/pulse/default.pa :
load-module module-alsa-sink device=hw:0
load-module module-alsa-source device=hw:0
--
You received this bug notification because you are a
Yes, it will.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
i would just like to extend my sincere thanks to everone here. this bug
has been DRIVING ME UP THE WALL for months since i upgraded to karmic.
i never thought it would be the modem, but disabling it has fixed the
problem.
based on post #41 can i assume that in lucid it will work even with the
mod
Thanks, Daniel.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
No, it was a PulseAudio bug (already fixed in Lucid).
** Changed in: sl-modem (Ubuntu)
Status: Incomplete => Invalid
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Is there still anything left that needs to be done for sl-modem?
** Changed in: sl-modem (Ubuntu)
Importance: Undecided => Medium
** Changed in: sl-modem (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: sl-modem (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
N
** Branch linked: lp:ubuntu/pulseaudio
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
This bug was fixed in the package pulseaudio - 1:0.9.22~0.9.21+341
-g62bf-0ubuntu1
---
pulseaudio (1:0.9.22~0.9.21+341-g62bf-0ubuntu1) lucid; urgency=low
* New snapshot based on stable-queue git branch (testing requested
specifically by upstream)
- LP: #164745, #173212, #201
Just to confirm that disabling the proprietary modem crap I have my
sound back!
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On Tue, Oct 27, 2009 at 4:31 PM, Bernhard Gehl wrote:
> What's the drawback of using module-udev?
You lose hotplugging.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which
Next workaround: Set DONTSTART to "1" in /etc/default/slmodemd
What's the drawback of using module-udev?
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Hey Daniel, Thanks for the tip. It fix my problem with Intel ICH8 sound.
I just remove the Proprietary driver of my Dial-up Modem and everythink
went back to normal. It doesn't need to reboot !
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You recei
Right, so your symptom is the same as others with the modem driver on the
same hw:X device. You have a number of options:
1) deinstall sl-modem-daemon;
2) use module-udev instead of module-udev-detect in
/etc/pulse/default.pa(or ~/.pulse/
default.pa);
3) continue to use alsa force-reload.
On Oct
My output when the sound still works after a reboot is:
USERPID ACCESS COMMAND
/dev/snd/controlC0: brad 1984 F pulseaudio
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification becau
My output after an alsa force-reload is:
USERPID ACCESS COMMAND
/dev/snd/controlC0: brad 2700 F pulseaudio
/dev/snd/pcmC0D0p: brad 2700 F...m pulseaudio
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
Y
My output before an alsa force-reload is:
USERPID ACCESS COMMAND
/dev/snd/controlC0: Slmodemd 1393 F slmodemd
/dev/snd/pcmC0D6c: Slmodemd 1393 F slmodemd
/dev/snd/pcmC0D6p: Slmodemd 1393 F slmodemd
--
No sound with intel-hda without "alsa force
When this symptom occurs, what is the output from the following
command _before_ you issue an "alsa force-reload"? sudo fuser -v
/dev/dsp* /dev/snd/* /dev/audio* /dev/mixer* /dev/seq*
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this b
Bug is still there with pulseaudio 0.9.19-0ubuntu4, linux-backports-
modules-alsa-karmic-generic 2.6.31.14.27. (Not nagging, just trying to
help.)
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a mem
Assign the bug to pulseaudio again, since it is probably related to this
issue.
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: sl-modem (Ubuntu)
Status: Invalid => Confirmed
--
No sound with intel-hda without "alsa force-reload"
https://bu
Nevermind again. The issue came back after working through 8 reboots.
This problem is strange.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this pulseaudio (1:0.9.19-0ubuntu3) upload fixed it, as I see
this in its changelog:
* debian/patches/0056-ignore-sound-class-modem.patch:
+ Apply patch from Whoopie to fix initialization of devices with
modem subdevices (LP: #394500, #450222)
** Changed in: sl-modem (Ubuntu)
The issue just went away with one of the last updates. Nevermind.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Karunadheera
Yeah, I'll probably do that until a real fix comes along.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I also have same issue since upgrade of 9.10 beta from 9.04. My audio
device is:
$ lspci
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
High Definition Audio Controller (rev 04)
No sound device listed after boot:
$ sudo fuser -v /dev/dsp* /dev/snd/*
The solution I found is to add the following entry to /etc/rc.local
/sbin/alsa force-reload
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have the exact same issue. My chip is a 82801H. There is no sound
device listed when the issue happens. An alsa force-reload always works
to get sound back. Sometimes the sound will even keep working for a
reboot or two, but eventually it loses my sound device again and I have
to do another alsa
I meant to say it didn't happen with 9.04, 8.10, and 8.04 on my system.
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Wow, that seems to be the right direction (and I'm learning about
linux):
After a (clean) boot (resulting in a "dummy device" sound output) fuser
gives the following:
$ sudo fuser -v /dev/dsp /dev/snd/*
USERPID ACCESS COMMAND
/dev/snd/controlC0: Slmodemd 1213 F
Devices in /dev/snd are grabbed by slmodemd and cannot be used by
pulseaudio until after "alsa force-reload".
** Package changed: pulseaudio (Ubuntu) => sl-modem (Ubuntu)
--
No sound with intel-hda without "alsa force-reload"
https://bugs.launchpad.net/bugs/449762
You received this bug notificat
I found another workaround for this problem: start pulseaudio system-
wide instead of per-user. There is a good explenation of the steps
involved here: http://www.alanbriolat.co.uk/2009/03/mpd-pulseaudio-
ubuntu-intrepid-810/
--
No sound with intel-hda without "alsa force-reload"
https://bugs.lau
Can you post the output of:
sudo fuser -v /dev/dsp* /dev/snd/*
I had this problem, and noticed the lirc daemon had hooked itself to the
/dev/snd/ device, resulting in pulseaudio being unable to load my
soundcard. After doing:
sudo update-rc.d -f lirc remove
Than I got sound after rebooting. Now
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33553881/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33553882/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/33553883/ArecordDevices.t
34 matches
Mail list logo
