Bruce Korb wrote:
> However, going through Yast and specifying that the motherboard sound
> was to be device 0 did no good.
If the other device is seen first, it will go to whatever index is
configured for it. Tell Yast that the other device is 1.
Many distributions configure the USB driver to a
On 11/09/11 14:47, Bill Unruh wrote:
> I suspect that alsa, for some random reason, decided to make the video camera
> the first or primary sound device suddenly (how it decides that is a mystery
> in linux).
That was my guess, too. However, going through Yast and specifying that
the motherboard
On Wed, 9 Nov 2011, Bruce Korb wrote:
> On 11/09/11 12:01, Bill Unruh wrote:
>>
>> ... I would also
>> advise you to unplug the usb camera as well,
>
> That did it. I've had the camera plugged in for months. However,
> the sound stopped a couple days ago and by removing it, the sound
> is bac
On 11/09/11 12:01, Bill Unruh wrote:
>
> ... I would also
> advise you to unplug the usb camera as well,
That did it. I've had the camera plugged in for months. However,
the sound stopped a couple days ago and by removing it, the sound
is back. Sound is necessary and sending video is merely fu
It looks to me that you webcam is being configured as sound card 0 confusing
the set up. If it were me I would remove the webcam, restart, reconfigue the
audio with YaST (set the audio device to sound card zero) and if that works
restart and confirm settings hold. Only then plug webcam back in.
pulseaudio is the new program which takes input from soundcards and delivers
it to the computer, and vice versa. Ie, it is an overall sound control
program. The best thing to do first is to disable pulseaudio and leave just
the bare soundcards. so that you can figure out what is going on. I would
On 11/09/11 11:09, Bruce Korb wrote:
Does this shed any light? alsamixer says
┌─ AlsaMixer v1.0.24.2
─┐
│ Card: PulseAudio F1: Help
│
│ Chip: PulseAudio
On 11/09/11 10:59, Bruce Korb wrote:
I think your guess may be correct as the snd-hda-intel module is now loaded.
Looking more carefully at the "lspci -vv", I notice:
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- \
> SERR- $ sr lspci -vv -s 00:07.0
> 00:07.0 Audio devic
On 11/09/11 10:27, Bill Unruh wrote:
> sound modules usually start with snd- You have none. Look in
> /etc/modules.conf, /etc/modules.d/* -- especially the ones that start with
> snd- -- for the sound modules and try reloading
> them (eg modprobe snd-hda-intel to load the intel driver-- I am not sa
On 11/09/11 09:41, Bruce Korb wrote:
The module list changed, too. There are some "snd" modules, but no sound.
$ diff -w tmp/old-list tmp/new-list
32c32
< nfs 363192 0
---
> nfs 363192 1
35c35
< nvidia 10286158 55
---
> nvidia 10
On 11/09/11 09:41, Bruce Korb wrote:
> $ sr lspci -vv -s 00:07.0
> 00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High
> Definition Audio (rev a1)
> Subsystem: ASUSTeK Computer Inc. M3N72-D
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- Par
sound modules usually start with snd- You have none. Look in
/etc/modules.conf, /etc/modules.d/* -- especially the ones that start with
snd- -- for the sound modules and try reloading
them (eg modprobe snd-hda-intel to load the intel driver-- I am not saying
that is the right one for you, it is jus
12 matches
Mail list logo
