Biji, check my post of 22/10/2008:
I didn't do the fix as reported by Daniel, because I my case the bug is
surely in another part of the script. In my case it's in
mute_and_zero_levels_on_card() called during mute_and_zero_levels. I've
added debugging to test.
In the for loop all kind of devices
See my previous postings in this thread. I've exactly shown which
statements take that much time (any why). I did the same debugging.
Manni wrote:
I just tried to debug this some more and found out, that everything
/etc/init.d/alsa-utils does, it does really, really slow.
I added some
I don't know if this is the recent bug report about browsing windows network
pc's, but I can confirm this bug. In 8.10 browsing windows network shares
(samba) fails.
My windows shares are even no windows shares, but just smb shares from xubuntu
8.04.1 and smb shares from an embedded Linux
I don't know if this is the recent bug report about browsing windows network
pc's, but I can confirm this bug. In 8.10 browsing windows network shares
(samba) fails.
My windows shares are even no windows shares, but just smb shares from xubuntu
8.04.1 and smb shares from an embedded Linux
play to get my sound working on
aMSN. I just uninstalled sox, and the shutdown is fine again.
dAF2000 wrote:
It's solved here too after a fresh install of 8.10.
--
storing ALSA mixer element values during shutdown hangs nondeterministically if
non-loopback network interfaces are still up
https
It's solved here too after a fresh install of 8.10.
--
storing ALSA mixer element values during shutdown hangs nondeterministically if
non-loopback network interfaces are still up
https://bugs.launchpad.net/bugs/274995
You received this bug notification because you are a member of Ubuntu
Bugs,
Indeed, hda-intel
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
--
storing ALSA mixer element values during shutdown hangs nondeterministically if
non-loopback network interfaces are still up
https://bugs.launchpad.net/bugs/274995
You received this
07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast
Ethernet Controller (rev 12)
08:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
wireless driver: iwlagn
--
Suzan's ifconfig trick does indeed work! I also got some libpulse
updates from Daniel's repository so I tried with and without the
ifconfig in alsa-utils. Without gives the shutdown delay, with does work
fine.
Still unclear to me why the network interface influences alsa. If all is
up and running
Too bad, it didn't work (I've reverted the alsa-utils script to the
original one).
Daniel T Chen wrote:
I am providing a tentative ordering fix via my PPA
(https://edge.launchpad.net/~crimsun/+archive). Please test.
** Attachment removed: alsa-utils
The alsa-utils file by Daniel didn't work for me.
I didn't add extra debugging so I don't know now if the amixer $CARDOPT sget
$1 /dev/null 21 causes the delay now.
Some more info:
Running /etc/init.d/alsa-utils stop from the command line while Ubuntu is
running causes no delay. Also, I thought
.
Daniel T Chen wrote:
@dAF2000 We may be able to work around the hang by a more hackish method
that doesn't test for the existence of the problematic simple controls.
Please try the newer attached initscript.
** Attachment added: alsa-utils
http://launchpadlibrarian.net/18823843/alsa-utils
I didn't do the fix as reported by Daniel, because I my case the bug is
surely in another part of the script. In my case it's in
mute_and_zero_levels_on_card() called during mute_and_zero_levels. I've
added debugging to test.
In the for loop all kind of devices are muted and almost all entries
I can confirm this bug here on a Toshiba Satellite U400, Ubuntu 8.10,
latest updates up to Oct 13, 2008.
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
[EMAIL PROTECTED]:~$ lsmod | grep hda
snd_hda_intel 381488 3
snd_pcm83204
14 matches
Mail list logo
