** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
no sound after upgrating to KK 9.10
https://bugs.launchpad.net/bugs/467747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Many thanks for explanation.
Could downgrading the PulseAudio solve my issue then?
I use now this version:
$> pulseaudio --version
pulseaudio 0.9.19
but I'm not sure what version I used before, in Jaunty.
Regards,
Petru
On Mon, Nov 2, 2009 at 6:51 PM, Daniel T Chen
wrote:
> On Mon, N
On Mon, Nov 2, 2009 at 6:32 PM, petrum wrote:
> Not sure where the coupling is, between:
The kernel (linux) contains alsa-kernel, or the actual sound driver.
For all intents and purposes, the userspace alsa-lib is not relevant
in this specific bug. So, "ALSA" is comprised of both a kernelspace
po
On Sun, Nov 1, 2009 at 11:42 PM, Daniel T Chen
wrote:
> Well, yes, you certainly could change Karmic's udev rules to work with
> Jaunty's kernel, but that's very much the *wrong* thing to do. You
> want to use Karmic's kernel with Karmic's udev. Seriously.
>
> --
>
I don't understand where is the
On Mon, Nov 2, 2009 at 12:23 AM, Daniel T Chen
wrote:
> On Mon, Nov 2, 2009 at 12:05 AM, petrum wrote:
> > My point is I cannot use the Karmic kernel's since it makes my machine
> > unusable!
> > Is there any way to have sound with the old kernel?
>
> Err, yes, but it will be painful.
>
>
Do you
...and after reboot with the v2.6.32-rc5 kernel, I got the same 'sensors'
failure, and the wicd was again crashing...
Regards,
Petru
On Mon, Nov 2, 2009 at 12:51 AM, Petru Marginean
wrote:
> Daniel T Chen wrote:
>
> On Mon, Nov 2, 2009 at 12:05 AM, petrum
> wrote:
>
>
> My point is I cannot
On Mon, Nov 2, 2009 at 12:05 AM, petrum wrote:
> My point is I cannot use the Karmic kernel's since it makes my machine
> unusable!
> Is there any way to have sound with the old kernel?
Err, yes, but it will be painful.
Why don't you try the 2.6.32-rc5 mainline build? Make sure to install
the he
On Sun, Nov 1, 2009 at 11:42 PM, Daniel T Chen
wrote:
> Well, yes, you certainly could change Karmic's udev rules to work with
> Jaunty's kernel, but that's very much the *wrong* thing to do. You
> want to use Karmic's kernel with Karmic's udev. Seriously.
>
>
Daniel,
My point is I cannot use the
Well, yes, you certainly could change Karmic's udev rules to work with
Jaunty's kernel, but that's very much the *wrong* thing to do. You
want to use Karmic's kernel with Karmic's udev. Seriously.
--
no sound after upgrating to KK 9.10
https://bugs.launchpad.net/bugs/467747
You received this bug
I just did this:
Code:
$> cd /dev/snd
$> sudo ln -s ../controlC0
$> ls -ltr
total 0
drwxr-xr-x 2 root root 60 2009-10-31 23:51 by-path
lrwxrwxrwx 1 root root 12 2009-11-01 23:17 controlC0 -> ../controlC0
and then surprise:
Code:
$> aplay -l
List of PLAYBACK Hardware Devices
card
Ugh, no, that just means that we definitely can't use that workaround.
It means you *must* use Karmic's kernel with Karmic's udev, else
module*detect fail utterly. :(
--
no sound after upgrating to KK 9.10
https://bugs.launchpad.net/bugs/467747
You received this bug notification because you are a
Hmmm...
Executed this command:
$> pkill pulseaudio; sleep 2; pulseaudio -vvv 2>&1 | tee pulse1.log
and then:
$> grep controlC0 pulse1.log
D: module-udev-detect.c: /dev/snd/controlC0 is accessible: no
It looks like the controlC0 is not in the /dev/snd but in /dev:
$> find /dev -name con
Hi,
Tried again to use module-detect instead module-udev-detect.
Changed the /etc/pulse/default.pa and then executed:
$> pkill pulseaudio; sleep 2; pulseaudio -vvv 2>&1 | tee
pulse2.log
but again no sound.
I've attached the logfile, and some interesting lines are below.
Thanks for help,
Thanks for suggestion.
I commented out "load-module module-udev-detect" command (see below), and
then rebooted.
However I have seen no improvement:
$> aplay -l
aplay: device_list:223: no soundcards found...
After reboot I've also got a report about a compiz crash (see the attached
picture
Then use module-detect instead of module-udev-detect. See /etc/pulse/
default.pa.
On Oct 31, 2009 10:50 PM, "petrum" wrote:
...and I can confirm that the sound is working with the new 2.6.31 kernel.
Is there any way to make it work with my old kernel (2.6.28)?
(since otherwise I cannot use the c
...and I can confirm that the sound is working with the new 2.6.31 kernel.
Is there any way to make it work with my old kernel (2.6.28)?
(since otherwise I cannot use the computer - see some issues I have below)
Thanks,
Petru
On Sat, Oct 31, 2009 at 10:19 PM, Petru Marginean wrote:
> Hi,
>
> Th
Hi,
Thanks for the quick reply.
I actually did the grub change after upgrade (9.04 => 9.10), but the
computer was not usable/stable.
Using the new kernel the wicd was crashing and the 'sensors' (controlling my
fan) was not working.
(see pictures below)
I had to downgrade the kernel so I could at
Please update grub's configuration (grub.cfg/menu.lst) to use the new Karmic
kernel (2.6.31). Note that you're still using Jaunty's kernel (2.6.28).
On Oct 31, 2009 9:25 PM, "petrum" wrote:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34825034/BootDmesg.txt
** Attachmen
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34825034/BootDmesg.txt
** Attachment added: "Card0.Amixer.info.txt"
http://launchpadlibrarian.net/34825035/Card0.Amixer.info.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/34825036/Card0
19 matches
Mail list logo
