[Alsa-user] microphone not working for Intel Corporation 82801G
Dear List members,I have an HP pavillion dv2000 laptop and I can't get the microphone to work. Sound works pretty well from the first installation without any reconfiguration using snd-hda-intel. I've looked throught the net and in the archives of this list and I've gotten a lot of pointers and tried many models listed in /usr/src/linux-2.6.16.21-0.13/Documentation/sound/alsa/ALSA-Configuration.txtwithout success. Any pointers to help me configure the microphone would be appreciated. From what I've read the following informatio seems relevant. Thanks in advance, Gus Degreef I am using OpenSuse 10.1[EMAIL PROTECTED]:~ uname -r2.6.16.21-0.13-smpcutie:~ # rpm -qa alsa*alsa-firmware-1.0.13-0.pm.0alsa-1.0.13-0.pm.0alsa-tools-gui-1.0.13-0.pm.0alsa-tools-1.0.13-0.pm.0 alsa-devel-1.0.11-32alsamixergui-0.9.0rc1-558cutie:~ #lspci (sound only)00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)[EMAIL PROTECTED] :/etc/modprobe.d cat soundoptions snd-hda-intel enable=1 index=0 model=laptop-dig# u1Nb.uHk6lYgTyh8:82801G (ICH7 Family) High Definition Audio Controlleralias snd-card-0 snd-hda-intelI've also tried model= hp, basic, laptop-dig, laptop, w810, z71v, and hp without success. I get sound with all of these models, but no microphone listed in alsamixer. I've tried manually editing /etc/modprobe.d//sound or configuring the sundcard with yast. I've googled for Codec: Generic 14f1 ID 5047 eith no really relevant results. cutie:~ #cat /proc/asound/dev0/codec#0Codec: Generic 14f1 ID 5047Address: 0Vendor Id: 0x14f15047Subsystem Id: 0x103c30b2Revision Id: 0x10Default PCM: rates 0x040, bits 0x02, types 0x1 Default Amp-In caps: N/ADefault Amp-Out caps: N/ANode 0x10 [Audio Output] wcaps 0x41d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x1e 0x1e] PCM: rates 0x040, bits 0x02, types 0x1 Power: 0x0Node 0x11 [Audio Output] wcaps 0x611: Stereo Digital PCM: rates 0x040, bits 0x02, types 0x1 Power: 0x0Node 0x12 [Audio Input] wcaps 0x100d1b: Stereo Amp-In Amp-In caps: ofs=0x00, nsteps=0x0e, stepsize=0x05, mute=1 Amp-In vals: [0x0e 0x0e] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] [0x80 0x80] PCM: rates 0x040, bits 0x02, types 0x1 Power: 0x0 Connection: 6 0x19* 0x14 0x15 0x1a 0x16 0x10Node 0x13 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x1e 0x1e] Pincap 0x081001c: OUT HP Pin Default 0xc3111010: [Both] Speaker at Ext Left Conn = 1/8, Color = Black Pin-ctls: 0xc0: OUT HP Power: 0x0 Connection: 3 0x19* 0x10 0x16Node 0x14 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x1f 0x1f] Pincap 0x0833c: IN OUT HP Pin Default 0x03811011: [Jack] Line In at Ext Left Conn = 1/8, Color = Black Pin-ctls: 0x20: IN Power: 0x0 Connection: 2 0x19* 0x16Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x1f 0x1f] Pincap 0x0833c: IN OUT HP Pin Default 0x03a11012: [Jack] Mic at Ext Left Conn = 1/8, Color = Black Pin-ctls: 0x20: IN Power: 0x0 Connection: 3 0x1c 0x19* 0x16Node 0x16 [Pin Complex] wcaps 0x400401: Stereo Pincap 0x0860: IN Pin Default 0x99330100: [Fixed] CD at Int ATAPI Conn = ATAPI, Color = Unknown Pin-ctls: 0x20: IN Power: 0x0Node 0x17 [Pin Complex] wcaps 0x400481: Stereo Pincap 0x08324: IN Pin Default 0xb7a00100: [Fixed] Mic at Oth Mobile-In Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Power: 0x0Node 0x18 [Pin Complex] wcaps 0x400701: Stereo Digital Pincap 0x0810: OUT Pin Default 0x21440100: [Jack] SPDIF Out at Sep Rear Conn = RCA, Color = Unknown Pin-ctls: 0x00: Power: 0x0 Connection: 1 0x11Node 0x19 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In Amp-In caps: ofs=0x17, nsteps=0x1e, stepsize=0x05, mute=1 Amp-In vals: [0x07 0x07] [0x07 0x07] [0x80 0x80] [0x17 0x17] Power: 0x0 Connection: 4 0x10 0x1b 0x1a 0x16Node 0x1a [Audio Selector] wcaps 0x30050d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x03, stepsize=0x1f, mute=0 Amp-Out vals: [0x00 0x00] Power: 0x0 Connection: 3 0x15* 0x14 0x17Node 0x1b [Audio Selector] wcaps 0x300501: Stereo Power: 0x0 Connection: 2 0x14* 0x15Node 0x1c [Audio Output] wcaps 0x41d: Stereo Amp-Out Amp-Out caps: ofs=0x17, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x80 0x80] PCM: rates 0x040, bits 0x02, types 0x1 Power: 0x0Node 0x1d [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1e, stepsize=0x05, mute=1 Amp-Out vals: [0x1f 0x1f] Pincap 0x08314: OUT Pin Default 0x90100112: [Fixed] Speaker at Int N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x40: OUT Power: 0x0 Connection: 3 0x1c 0x19* 0x16Node 0x1e [Vendor Defined Widget] wcaps 0xf0: Mono - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your
[Alsa-user] Unable to record in stereo from spdif on M-Audio DIO 2496
Hello, Following up on my post about `set_params:901: Sample format non available` I did some tests which I posted here. The outcome was that I could record, even in 16-bit, but not in stereo. Stereo would yield silence. Does anybody here have the M-Audio DIO2496 working for recording from spdif? If so, please post. Below are the tests I did. Thanks, Udo Yes. Use plughw:1 rather than hw:1. Or just use default:1 for automatic rate, format, channel conversion and dmix. Thanks for the tips. I did some tests. The setup: CD - coax - DiO 2496 Envy24control: masterclock spdif in rate state locked input coax The tests: arecord -d5 -r44100 -Dplughw:1 /data/0/test0.wav Recording WAVE '(null)' : Unsigned 8 bit, Rate 44100 Hz, Mono gives low quality audio arecord -d5 -fcd -Dplughw:1 /data/0/test0.wav Recording WAVE '(null)' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo gives silence arecord -d5 -fcd -Ddefault:1 /data/0/test0.wav Recording WAVE '(null)' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo silence arecord -d5 -Ddefault:1 /data/0/test0.wav Recording WAVE '(null)' : Unsigned 8 bit, Rate 8000 Hz, Mono silence arecord -d5 -r44100 -f S16_LE -Dplughw:1 /data/0/test0.wav Recording WAVE '(null)' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono audio, mono but OK arecord -d5 -r44100 -f S16_LE -c 2 -Dplughw:1 /data/0/test0.wav Recording WAVE '(null)' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo silence arecord -d5 -r44100 -f S16_LE -Ddefault:1 /data/0/test0.wav Recording WAVE '(null)' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono silence - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] How to know hardware limitations ?
Hi,I'm wondering if there is some way or some tool to know exactlythe hardware limitation of a particular sound card for the capturefunction (eg rate and bits).To avoid the hardware limits I'm using the plughw device. It works fine but i'm willing to know if the sample rate that I use (48Khz forexample) is native from the soundcard or if it is software resampled from the plughw device.Consider also an unkown multi sound card environnement viewed from a bash script for example. How can the script choose thesound card that natively has the highest capture sample rate capability ?Thanks for your time,Olivier Delhomme. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Some questions about the Audigy 2 NX
Hi Simeon, On Tue, 03 Oct 2006 20:39:55 +0200 Simeon Penev wrote: maybe this tutorial by Daniel Heyder will help you: http://praxeum.gmxhome.de/audigy2nx.html Although it's written in german, you can still try copy/pasting the configs and see if that is what you need. Uhm, I'm living in Germany for more than ten years now - I think I can understand German ;-) Thank you for the link, I've read it carefully... The first point seems to be not needed on Debian, because the card works without any changes to modprobe.d. The second point is the asound.conf, which I already have like this through digging around the alsa-wiki. And the last one is the lirc part, which I didn't have time yet for. The guide is written very well, but does not help me much :( So I still need an answer for my first question :( Regards, Evgeni PS: is your name correctly written like this: Семён ? -- ^^^| Evgeni -SargentD- Golov ([EMAIL PROTECTED]) d(O_o)b | PGP-Key-ID: 0xAC15B50C -|- | WWW: http://www.die-welt.net ICQ: 54116744 / \| IRC: #sod @ irc.german-freakz.net - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
On Tue, 3 Oct 2006, Andrew Gaydenko wrote: I use ICE1724 ALSA driver for Terratec Aureon 7.1 Space card. Almost all is fine, big thanks to developers! Nevertheless, I have noticed both default (line out) and plug:spdif devices'es outputs are inverted. Is it possible to configure additional inversion and, as a result, to get normal output signal? I'm not sure it is the the driver bug - probably, it is manufacturer's bug :-) Is not your problem related to signess? Did you tried to use 'U32_LE' format? Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SUSE Labs - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
Jaroslav, I use (with JACK) 'hw:0,0' for analog output and 'hw:0,1' for SPDIF one. Andrew === On Thursday 05 October 2006 15:39, you wrote: === On Tue, 3 Oct 2006, Andrew Gaydenko wrote: I use ICE1724 ALSA driver for Terratec Aureon 7.1 Space card. Almost all is fine, big thanks to developers! Nevertheless, I have noticed both default (line out) and plug:spdif devices'es outputs are inverted. Is it possible to configure additional inversion and, as a result, to get normal output signal? I'm not sure it is the the driver bug - probably, it is manufacturer's bug :-) Is not your problem related to signess? Did you tried to use 'U32_LE' format? Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SUSE Labs - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
On Thu, 5 Oct 2006, Andrew Gaydenko wrote: Jaroslav, I use (with JACK) 'hw:0,0' for analog output and 'hw:0,1' for SPDIF one. Could you try a more lowlevel tool like aplay with a raw file? You may try the python script bellow (modify values as you want to measure level for different samples). Note that hw: devices are signed for ICE1724, so zero is in the middle of range, minimum value is 0x8000 and maximum 0x7f00. import struct import os FILE=file.raw SAMPLE=0x12345600 FORMAT=S32_LE fp = open(FILE, w+) x = struct.pack(I, SAMPLE) for i in range(0, 10): fp.write(x) fp.close() os.system(aplay -D hw:0,0 -f %s -c 2 -r 48000 %s % (FORMAT, FILE)) os.remove(FILE) Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Full duplex support for ES1878 chip
Hello, Is the es18xx ALSA driver provides full duplex support for ES1878 chip? Thank you! - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
Jaroslav, Have tried the script. With given sample a speaker cone moves from a listener rather toward one. As 0x12345600 hasn't 0x8000 bit set, I suggest a cone must move toward a listener. Well, to avoid any mysticism I simply measured DAC output with multimeter :-) The output is negative, of course. Andrew === On Thursday 05 October 2006 16:32, you wrote: === On Thu, 5 Oct 2006, Andrew Gaydenko wrote: Jaroslav, I use (with JACK) 'hw:0,0' for analog output and 'hw:0,1' for SPDIF one. Could you try a more lowlevel tool like aplay with a raw file? You may try the python script bellow (modify values as you want to measure level for different samples). Note that hw: devices are signed for ICE1724, so zero is in the middle of range, minimum value is 0x8000 and maximum 0x7f00. import struct import os FILE=file.raw SAMPLE=0x12345600 FORMAT=S32_LE fp = open(FILE, w+) x = struct.pack(I, SAMPLE) for i in range(0, 10): fp.write(x) fp.close() os.system(aplay -D hw:0,0 -f %s -c 2 -r 48000 %s % (FORMAT, FILE)) os.remove(FILE) Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
Sorry, have fogot to mention I have checked both hw:0,0 and hw:0,1 devices with the same result (using non-inverting external DAC at last case). Andrew -- Forwarded Message -- Jaroslav, Have tried the script. With given sample a speaker cone moves from a listener rather toward one. As 0x12345600 hasn't 0x8000 bit set, I suggest a cone must move toward a listener. Well, to avoid any mysticism I simply measured DAC output with multimeter :-) The output is negative, of course. Andrew - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
On Thu, 5 Oct 2006, Andrew Gaydenko wrote:
Jaroslav,
Have tried the script. With given sample a speaker cone moves from a
listener rather toward one. As 0x12345600 hasn't 0x8000 bit set, I
suggest a cone must move toward a listener. Well, to avoid any mysticism
I simply measured DAC output with multimeter :-) The output is negative,
of course.
Okay, what about route plugin:
pcm.routetest {
type route
slave.pcm hw:0,0;
ttable {
0 { 0 -1.0 }
1 { 1 -1.0 }
}
}
Replace -D hw:0,0 with -D routetest.
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] configuring ALSA driver to avoid invertion
Jaroslav,
Inversion works. BTW, I have tried 'inv' LADSPA plugin (as ALSA
device) - it works too.
(Is it sufficient to perform futher tests with hw:0,1 only?)
Andrew
=== On Thursday 05 October 2006 17:58, you wrote: ===
Okay, what about route plugin:
pcm.routetest {
type route
slave.pcm hw:0,0;
ttable {
0 { 0 -1.0 }
1 { 1 -1.0 }
}
}
Replace -D hw:0,0 with -D routetest.
Jaroslav
-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Full duplex support for ES1878 chip
Sergey Sedov wrote: Is the es18xx ALSA driver provides full duplex support for ES1878 chip? The ES1878 chip supports full duplex only with mono data. HTH Clemens - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Some questions about the Audigy 2 NX
Evgeni Golov wrote:
there is no master volume, alsamixer shows 4 Master bars, but they
change only one output each. on my Audigy 4 (nonpro - yes, it works) I
have Master which controlls all the outputs, and PCM {Center|Front|
LFE} for the individual outputs. it there any chance to get this
working with the 2 NX?
The controls in the mixer are those that are implemented in the
hardware. The Audigy 2 NX does not have a volume control that would
affect all channels.
Regards,
Clemens
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Some questions about the Audigy 2 NX
On Thu, 05 Oct 2006 16:44:05 +0200 Clemens Ladisch wrote: The controls in the mixer are those that are implemented in the hardware. The Audigy 2 NX does not have a volume control that would affect all channels. Damn, what the h*** is the 'Master' control on the box is for then? Is there a possibility to create a virtual control in Alsa, which would control all the hardware ones the same? Regards, Evgeni -- ^^^| Evgeni -SargentD- Golov ([EMAIL PROTECTED]) d(O_o)b | PGP-Key-ID: 0xAC15B50C -|- | WWW: http://www.die-welt.net ICQ: 54116744 / \| IRC: #sod @ irc.german-freakz.net - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Some questions about the Audigy 2 NX
Evgeni Golov wrote: On Thu, 05 Oct 2006 16:44:05 +0200 Clemens Ladisch wrote: The controls in the mixer are those that are implemented in the hardware. The Audigy 2 NX does not have a volume control that would affect all channels. Damn, what the h*** is the 'Master' control on the box is for then? That control sends Volume + and Volume - events to the computer. If you have LIRC, you can try to do something useful with these events. It should be possible to create two scripts that change the volume of all eight channels with amixer. Is there a possibility to create a virtual control in Alsa, which would control all the hardware ones the same? Not at the moment. It is planned to create a virtual mixer layer that would allow doing things like this. Regards, Clemens - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Problems with snd hda intel: works only part of the time
Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d400-d5ff Prefetchable memory behind bridge: d000-d1f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Unknown (5) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind bridge: d600-d7ff Prefetchable memory behind bridge: d200-d3f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Unknown (5) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 20 I/O ports at 1820 [size=32] 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 1840 [size=32] 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at 1860 [size=32] 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 17 I/O ports at 1880 [size=32] 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 20 Memory at d8444000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=05, sec-latency=32 I/O behind bridge: 4000-4fff Memory behind bridge: d800-d80f Prefetchable
[Alsa-user] Strange behaviour with snd_hda_intel at 1.0.13
Hi, I've googled and browsed all the documentation that I can found and I can't see anything that describes this problem, but if I have missed something then feel free to point me to the appropriate source. This is a bit long but I think more detail up front is probably helpful. I have a Sony Vaio with a Intel ICH6 sound that identifies itself as: :00:1b.0 Class 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 03) The Linux distribution that I installed (SuSE 9.2) didn't have the alsa driver (snd-hda-intel) for this so I compiled and installed 1.0.11 and the libs and tools and all was fine. About a month ago SuSE made a security update to the kernel which necessitated my rebuilding the alsa drivers so I downloaded 1.0.12 and everything basically was fine except that gnome-volume-control stopped working with: ALSA lib pcm_hw.c:1357:(_snd_pcm_hw_open) Invalid value for card for what is probably forever. I've assumed that this is either a misconfiguration of the application or some mis-use of the API and just haven't got round to getting the source of that version to see where the problem lies. But otherwise the sound was working (modulo the crackling that is documented for the driver.) Anyway, I decided yesterday to install the 1.0.13 drivers to see if that would solve the problem with the gnome-volume-control and also the crackling. I installed the 1.0.13 drivers/libs/utils and just for good measure the latest OSS api library. Running alsaconf seemed fine, detecting the appropriate driver and so forth, until it went to play the test sample where it seemed to hang without making any sound. Okay that's fine, these things happen, so I ^C the program. Checking the generated /etc/modprobe.d/sound it appears to be fine: alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel So check the levels in alsamixer and try to play the test sample in alsaplayer as a normal non-root user and it comes up with a whole bunch of errors relating to permissions on IPC objects and so forth (I can't paste these as I haven't replicated this since.) I assume that this is as a result of the alsaplayer hanging when run as root and my terminating it and subsequently some resource not being released. So I reboot. Rebooted I again check the levels in alsamixer (and strangely they have reverted to the all off default) and attempt to play the test sample again ... it makes a sound, however unfortunately it appears that it is playing the first buffer full of the sample over and over again for what appears to be forever (or at least until my patience expired, certainly longer than the original sample by a factor of 10.) The the same problem is experienced in aplay, play and it appears the sound output of some other programs such as gaim so its not just a problem with alsamixer. All the modules appear loaded fine : snd_pcm_oss45736 0 snd_mixer_oss 18048 2 snd_pcm_oss snd_hda_intel 19352 4 snd_hda_codec 161456 1 snd_hda_intel snd_pcm76168 4 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 23172 2 snd_pcm snd_page_alloc 10504 2 snd_hda_intel,snd_pcm snd57536 11 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer,snd_page_alloc soundcore 9056 2 snd I hadn't noticed it before but there now appears a [hda_codec] in the process list as a child of [events/0] (it may have been there all along while it was working but I didn't notice it.) The only slightly suspicious thing I can see in dmesg is: ALSA /home/jonathan/drivers/alsa/alsa-driver-1.0.13/alsa-kernel/pci/hda/hda_intel.c:540: hda_intel: azx_get_response timeout, switching to polling mode... which kind of hints that this might be another symptom of the problem (or otherwise indicative of the cause.) There are no other ALSA messages in any of the logs. It might be coincidental but firefox (which depends on libaoss) started to develop random freezing behaviour since I changed the driver (though I'm not quite sure why it needs the libray TBH.) So, before I revert to an earlier version, has anyone got any clues as to what might be going on here? I'm quite happy to do other tests etc to provide debugging information. I'd even be quite happy to install a CVS version as I'm sure it can't be worse than what I have now. However I am suspecting that there is some configuration part that I have missed. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net
Re: [Alsa-user] Strange behaviour with snd_hda_intel at 1.0.13
On Thu, 2006-10-05 at 12:03 +0100, Jonathan Stowe wrote: ... This is a bit long but I think more detail up front is probably helpful. ... To follow up to myself this sounds very similar to the https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2505 /J\ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d400-d5ff Prefetchable memory behind bridge: d000-d1f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Unknown (5) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind bridge: d600-d7ff Prefetchable memory behind bridge: d200-d3f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Unknown (5) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 20 I/O ports at 1820 [size=32] 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at 1840 [size=32] 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at 1860 [size=32] 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02) (prog-if 00 [UHCI]) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, medium devsel, latency 0, IRQ 17
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
Le Thu, 5 Oct 2006 20:42:17 +0200, Dominique Michel [EMAIL PROTECTED] a écrit : If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Sorry, it is in fact: you must not have alsa compiled with the kernel. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 2006-10-05 at 20:42 +0200, Dominique Michel wrote: It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Blacklisting snd-usb-audio would be a pretty heavy handed approach. Applications should not rely on any specific card ordering. Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
On Thu, 2006-10-05 at 22:42 +0200, Dominique Dumont wrote: Francesco Peeters [EMAIL PROTECTED] writes: Have you tried using a different slot for the SB Live? Yes. No change at all. (Sorry for the delay). This is going to be a problem with the SATA driver not ALSA. I've heard that some motherboards do evil stuff like implementing legacy drive access modes using SMM which would cause dropouts without xruns reported. Please report it on LKML. Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
Hi Dominique: 1) hotplug isn't running. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d400-d5ff Prefetchable memory behind bridge: d000-d1f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Capabilities: [100] Virtual Channel Capabilities: [180] Unknown (5)
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
Update: 1) If sound isn't working, and I run alsaconf, it then starts working. 2) My lsmod | grep snd on these occasions is: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm (In other words, it is exactly the same.) (3) If I run /etc/init.d/alsasound restart, sound will stop working. So, in summary: (1) Immediately after running alsaconf, sound works. I have only Master in my alsamixer. If I run /etc/init.d/alsasound restart, even though the same modules are listed as loaded, sound stops working and in alsamixer I have Master and SPDIF. If I then run alsaconf again, sound works and I only have Master, etc, repeat ad nauseum. On 10/5/06, Peter Hartman [EMAIL PROTECTED] wrote: Hi Dominique: 1) hotplug isn't running. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more
Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
Lee Revell [EMAIL PROTECTED] writes: This is going to be a problem with the SATA driver not ALSA. I've heard that some motherboards do evil stuff like implementing legacy drive access modes using SMM which would cause dropouts without xruns reported. Why do I hear distortion with PCM on SPDIF output and no distortion at all on analog front output ? (both with the SB Live card) Please report it on LKML. Will do. (although your mail and this mail are cc'ed to LKLM) Thanks - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 20:42 +0200, Dominique Michel wrote: It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Blacklisting snd-usb-audio would be a pretty heavy handed approach. Applications should not rely on any specific card ordering. And people should not speed on the highways. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
There is nothing else in lsmod except my ipw3945 wireless. The kernel, of course, has CONFIG_SOUND on but CONFIG_SND and CONFIG_SOUND_PRIME off. I put that in my blacklist regardless, but I don't think that is the issue. On 10/5/06, Bill Unruh [EMAIL PROTECTED] wrote: On Thu, 5 Oct 2006, Peter Hartman wrote: Hi Dominique: 1) hotplug isn't running. If you have udev, hotplug is always running. And udev is the standard these days. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). Sounds like two different sound cards are in contention. 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm That is not lsmod, but I assume it is all of the entries which start with snd. ARe there perhaps some old oss modules being loaded as well? (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7
Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
On Thu, 2006-10-05 at 22:52 +0100, Alan Cox wrote: Ar Iau, 2006-10-05 am 16:45 -0400, ysgrifennodd Lee Revell: I've heard that some motherboards do evil stuff like implementing legacy drive access modes using SMM which would cause dropouts without xruns reported. They don't. SATA causes audio dropouts on some systems because its fast enough to starve the audio device of regular enough access to the PCI bus. If that is a problem the audio device should be tuning PCI latencies OK. In fact the Windows driver and IIRC the OSS driver do tune PCI latencies. But that can't be the problem here if analog playback is unaffected. Sounds like electrical noise could be the issue... Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
On Thu, 2006-10-05 at 23:01 +0200, Dominique Dumont wrote: Lee Revell [EMAIL PROTECTED] writes: This is going to be a problem with the SATA driver not ALSA. I've heard that some motherboards do evil stuff like implementing legacy drive access modes using SMM which would cause dropouts without xruns reported. Why do I hear distortion with PCM on SPDIF output and no distortion at all on analog front output ? (both with the SB Live card) Please report it on LKML. Will do. (although your mail and this mail are cc'ed to LKLM) Did you ever try the latency tracer? (See LKML archives for instructions) Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Pb with simultaneous SATA and ALSA I/O
On Thu, 2006-10-05 at 23:01 +0200, Dominique Dumont wrote: Lee Revell [EMAIL PROTECTED] writes: This is going to be a problem with the SATA driver not ALSA. I've heard that some motherboards do evil stuff like implementing legacy drive access modes using SMM which would cause dropouts without xruns reported. Why do I hear distortion with PCM on SPDIF output and no distortion at all on analog front output ? (both with the SB Live card) No idea. Maybe SPDIF playback is more sensitive to timing glitches. But the problem must be in the SATA driver not the emu10k1 driver. Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 5 Oct 2006, Peter Hartman wrote: Hi Dominique: 1) hotplug isn't running. If you have udev, hotplug is always running. And udev is the standard these days. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). Sounds like two different sound cards are in contention. 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm That is not lsmod, but I assume it is all of the entries which start with snd. ARe there perhaps some old oss modules being loaded as well? (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d400-d5ff Prefetchable memory behind bridge: d000-d1f0 Capabilities: [40] Express Root Port (Slot+) IRQ 0 Capabilities: [80] Message
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 05 Oct 2006 18:45:14 -0400 Lee Revell [EMAIL PROTECTED] wrote: On Thu, 2006-10-05 at 14:33 -0700, Bill Unruh wrote: On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 20:42 +0200, Dominique Michel wrote: It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Blacklisting snd-usb-audio would be a pretty heavy handed approach. Applications should not rely on any specific card ordering. And people should not speed on the highways. But what if people actually have USB audio devices? There must be a better way... Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user Is there a way to really stop ALSA ? If yes, it is possible to write a script that would see what indices cards assigned, stop ALSA, rewrite /etc/modprobe.conf file with the required card order and restart ALSA. The required order will be according to user defined rules. --Sergei. -- Visit my http://appsfromscratch.berlios.de/ open source project. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 5 Oct 2006, Peter Hartman wrote: There is nothing else in lsmod except my ipw3945 wireless. The kernel, of course, has CONFIG_SOUND on but CONFIG_SND and CONFIG_SOUND_PRIME off. CONFIG_SND should be m, for modules. You WANT alsa support. I put that in my blacklist regardless, but I don't think that is the issue. On 10/5/06, Bill Unruh [EMAIL PROTECTED] wrote: On Thu, 5 Oct 2006, Peter Hartman wrote: Hi Dominique: 1) hotplug isn't running. If you have udev, hotplug is always running. And udev is the standard these days. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). Sounds like two different sound cards are in contention. 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm That is not lsmod, but I assume it is all of the entries which start with snd. ARe there perhaps some old oss modules being loaded as well? (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from alsa-sound.org. But then I get an ioctl error or other strange errors (it sometimes crashes, sometimes (e.g., mplayer) will say that the sndcard isn't fast enough, sometimes (madplay) an ioctl error). So I tried (b) emerging the 1.0.13 ebuilds of alsa stuff. Ditto error message. So, in summary, only the MODULE version of snd hda intel worked (kernel 2.6.17-gentoo-r8). But it only worked every few (random) reboots; when it worked, it worked fine. If you want more information, please let me know! lspci -v 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Gateway 2000 Unknown device 0366 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at d824 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Capabilities: [100] Virtual Channel Capabilities: [130] Unknown (5) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 14:33 -0700, Bill Unruh wrote: On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 20:42 +0200, Dominique Michel wrote: It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Blacklisting snd-usb-audio would be a pretty heavy handed approach. Applications should not rely on any specific card ordering. And people should not speed on the highways. But what if people actually have USB audio devices? There must be a better way... Yes, it is a problem with Linux that one cannot specify the order in which Linux specifies things like soundcards, disk drives, ethernet cards, It tends to depend on the random events during bootup. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Thu, 2006-10-05 at 16:19 -0700, Bill Unruh wrote: On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 14:33 -0700, Bill Unruh wrote: On Thu, 5 Oct 2006, Lee Revell wrote: On Thu, 2006-10-05 at 20:42 +0200, Dominique Michel wrote: It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Blacklisting snd-usb-audio would be a pretty heavy handed approach. Applications should not rely on any specific card ordering. And people should not speed on the highways. But what if people actually have USB audio devices? There must be a better way... Yes, it is a problem with Linux that one cannot specify the order in which Linux specifies things like soundcards, disk drives, ethernet cards, It tends to depend on the random events during bootup. This is not a problem with Linux. ALSA supports addressing devices by name. Applications that rely on a specific card order are broken. Fix the apps, problem solved. Lee - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
I'm using the alsa-driver-1.0.11 package as the alternative to the inbuilt kernel modules. According to this site: http://www.gentoo.org/doc/en/alsa-guide.xml I want CONFIG_SND off, since I am using the package. 1. CONFIG_SOUND is set. (Basic Sound support enabled) 2. CONFIG_SOUND_PRIME is not set. (In-built OSS support disabled) 3. CONFIG_SND is not set. (In-built ALSA support disabled) 4. /usr/src/linux points to the kernel you want ALSA working on. Either way, I get the same behavior if I go with alsa-driver-1.0.11 or if I turn on the inbuilt ALSA module. However, for debugging purposes, I have chosen to go with the alsa-driver package (1.0.11 in this case, see my previous emails on why 1.0.11 rather than 1.0.13) rather than the inbuilt kernel modules. Correct me if I'm wrong, but I assume I SHOULD NOT have CONFIG_SND set if I am using the alsa-driver package? Peter On 10/5/06, Bill Unruh [EMAIL PROTECTED] wrote: On Thu, 5 Oct 2006, Peter Hartman wrote: There is nothing else in lsmod except my ipw3945 wireless. The kernel, of course, has CONFIG_SOUND on but CONFIG_SND and CONFIG_SOUND_PRIME off. CONFIG_SND should be m, for modules. You WANT alsa support. I put that in my blacklist regardless, but I don't think that is the issue. On 10/5/06, Bill Unruh [EMAIL PROTECTED] wrote: On Thu, 5 Oct 2006, Peter Hartman wrote: Hi Dominique: 1) hotplug isn't running. If you have udev, hotplug is always running. And udev is the standard these days. 2) A little more clarification: when I run alsamixer (on the occasions when it works) it only shows the Master; but on the occasions when it stops working, a mysterious SPDIF setting is available (with the Master as well). Sounds like two different sound cards are in contention. 3) If I run /etc/init.d/alsasound restart on a bootup when it works--it will go from working to not working. But, randomly, it will start to work again only on a reboot. 4) I am now using vanilla gentoo 1.0.11 alsa-driver and alsa-utils for testing with you. With 1.0.13 (gentoo), I get a different error, but with 1.0.13 compiled by hand, it has the same effect. Besides, it WORKS atleast once in a while with 1.0.11, so I figured I'd stick with the vanilla gentoo, until I need to move beyond. 5) here is my lsmod: snd_pcm_oss31328 0 snd_mixer_oss 13888 1 snd_pcm_oss snd_seq_oss26624 0 snd_seq_device 5384 1 snd_seq_oss snd_seq_midi_event 5504 1 snd_seq_oss snd_seq41072 4 snd_seq_oss,snd_seq_midi_event snd_hda_intel 12884 0 snd_hda_codec 123008 1 snd_hda_intel snd_pcm62788 3 snd_pcm_oss,snd_hda_intel,snd_hda_codec snd_timer 16004 2 snd_seq,snd_pcm snd39332 9 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq_device,snd_seq,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer snd_page_alloc 6856 2 snd_hda_intel,snd_pcm That is not lsmod, but I assume it is all of the entries which start with snd. ARe there perhaps some old oss modules being loaded as well? (Unfortunately, this is lsmod on a broken sound bootup; I didn't get a chance to lsmod on a working sound setting -- even though the /etc/modules.d/alsa remain the same between the two.) On 10/5/06, Dominique Michel [EMAIL PROTECTED] wrote: If you want to use the alsa-driver packages with gentoo, you must not have alsa compiled with the driver. See http://www.gentoo.org/doc/en/alsa-guide.xml Le Thu, 5 Oct 2006 11:09:44 -0500, Peter Hartman [EMAIL PROTECTED] a écrit : Hi, I've had quite a headache with the snd hda intel driver. Below is my lspci. I am using GENTOO (latest) on a brand new Gateway MX6920 Laptop. With alsa-utils-1.0.11 and 2.6.17-gentoo-r8 with SND_HDA_INTEL compiled in AS A MODULE (It did not work compiled in directly to the kernel; nor did it work with alsa-driver-1.0.11--by did not work I mean everything ran fine, but no sound came out--) it worked every few reboots; in other words, it was very random. The curious thing about alsamixer--when it worked it only presented one control option (Master), whereas when it didn't work there were two or more controls. It can be the case if you have an USB sound card as a webcam. The snd_usb_audio will be loaded by hotplug before at alsasound load the alsa modules, and the regular sound card will be the second sound card. If it is the case, you have to add snd-usb-audio (without the double quotes) in /etc/udev/blacklist and alsasound will work as expected. If it not solve the problem, what is the output of lsmod|grep snd Dominique I also tried: (a) compiling alsa-utils-1.0.13 and alsa-driver-1.0.13 (and alsa-lib and alsa-header) directly from
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On 10/5/06, Peter Hartman [EMAIL PROTECTED] wrote: So, in summary: (1) Immediately after running alsaconf, sound works. I have only Master in my alsamixer. If I run /etc/init.d/alsasound restart, even though the same modules are listed as loaded, sound stops working and in alsamixer I have Master and SPDIF. If I then run alsaconf again, sound works and I only have Master, etc, repeat ad nauseum. Can you post the contents of /proc/asound/card0/codec#0 for both the working and non-working states? -Richard - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
