Re: Tool to configure sound
On Thu, Nov 01, 2007 at 00:23:34 +0100, Richard Lyons wrote: On Wed, Oct 31, 2007 at 06:38:02PM +0100, Florian Kulzer wrote: On Wed, Oct 31, 2007 at 11:48:16 +0100, Richard Lyons wrote: [...] OK, so the hardware works. Never mind -- I'll buy a phonograph, a soft cloth and scour the second-hand markets for vinyl... To keep yourself entertained until you get the phonograph, you could post the output of these commands: $ cat /proc/asound/card0/codec* | head Codec: Realtek ALC883 Address: 0 Vendor Id: 0x10ec0883 Subsystem Id: 0x1025160d Revision Id: 0x12 Default PCM: rates 0x560, bits 0x0e, types 0x1 Default Amp-In caps: N/A Default Amp-Out caps: N/A Node 0x02 [Audio Output] wcaps 0x11: Stereo PCM: rates 0x560, bits 0x0e, types 0x1 $ grep '.*' /sys/module/snd_hda_intel/parameters/* /sys/module/snd_hda_intel/parameters/enable:N /sys/module/snd_hda_intel/parameters/id:NULL /sys/module/snd_hda_intel/parameters/index:0 /sys/module/snd_hda_intel/parameters/model:NULL /sys/module/snd_hda_intel/parameters/position_fix:0 /sys/module/snd_hda_intel/parameters/probe_mask:-1 /sys/module/snd_hda_intel/parameters/single_cmd:N Maybe I'm dim or maybe it is just late, but I can't even guess what all that says. I'm impressed you even knew to suggest those. Do they help? I am just following Documentation/sound/alsa/ALSA-Configuration.txt. The Documentation directory is part of the kernel source; you can also get it separately by installing the linux-doc-... package for your version of the kernel. One source of problems with ALSA is that each driver (snd_hda_intel in your case) has to support different codec chips (here: ALC883) and that each codec chip can come in a number of different configurations (models). The ALSA developers are in an arms race with the laptop manufacturers, trying to make sure that the driver recognizes the codec chip model correctly for the ever-increasing number of laptop models. In your case no specific codec chip model was declared when the module was loaded, so the default configuration was chosen. This could mean that there might be an additional volume control for your chip which is currently inaccessible to you. You can try different codec chip models (e.g. 3stack) by running: modprobe -r snd_hda_intel modprobe snd_hda_intel model=3stack There might be a model which makes sound work right away, or which at least gives you an additional control which you can unmute and turn up. Maybe one of the other workarounds discussed in ALSA-Configuration.txt will get you going. If you find module parameters that work then you can append them to the hda-intel options line in /etc/modprobe.d/sound. Other things to consider are: - The problem might go away automatically if you upgrade to a newer version of ALSA and/or the kernel. (I don't recall if you mentioned which branch of Debian you are currently using.) - Maybe you can avoid the trial-and-error if you find someone who figured it out already for your laptop model. (TuxMobil, etc.) - The ALSA mailing list is the last resort if all else fails. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 12:51:51PM +0100, Florian Kulzer wrote: [...] I am just following Documentation/sound/alsa/ALSA-Configuration.txt. The Documentation directory is part of the kernel source; you can also get it separately by installing the linux-doc-... package for your version of the kernel. One source of problems with ALSA is that each driver (snd_hda_intel in your case) has to support different codec chips (here: ALC883) and that each codec chip can come in a number of different configurations (models). The ALSA developers are in an arms race with the laptop manufacturers, trying to make sure that the driver recognizes the codec chip model correctly for the ever-increasing number of laptop models. In your case no specific codec chip model was declared when the module was loaded, so the default configuration was chosen. This could mean that there might be an additional volume control for your chip which is currently inaccessible to you. You can try different codec chip models (e.g. 3stack) by running: modprobe -r snd_hda_intel modprobe snd_hda_intel model=3stack I tried that arbitrarily, but it didn't happen to be the one. I shall have to read the documentation to see what other options there are. There might be a model which makes sound work right away, or which at least gives you an additional control which you can unmute and turn up. Maybe one of the other workarounds discussed in ALSA-Configuration.txt will get you going. If you find module parameters that work then you can append them to the hda-intel options line in /etc/modprobe.d/sound. Other things to consider are: - The problem might go away automatically if you upgrade to a newer version of ALSA and/or the kernel. (I don't recall if you mentioned which branch of Debian you are currently using.)i Yes, I did upgrade to the latest in etch (which I am running currently) hoping for such a miracle. Maybe I should consider going back to sid, which I ran for a long time previously. I had the impression three months or so ago that that was a bad moment to get into sid, so I am still here in etch. - Maybe you can avoid the trial-and-error if you find someone who figured it out already for your laptop model. (TuxMobil, etc.) I'll go there when I have a moment - The ALSA mailing list is the last resort if all else fails. Florian, thanks for all these good suggestions, and for pointing me to the correct source for information. I hadn't planned on becoming an expert in alsa, but a suppose a little more knowledge will do no harm, and might make my computer speak... -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 13:33:26 +0100, Richard Lyons wrote: On Thu, Nov 01, 2007 at 12:51:51PM +0100, Florian Kulzer wrote: [...] - The problem might go away automatically if you upgrade to a newer version of ALSA and/or the kernel. (I don't recall if you mentioned which branch of Debian you are currently using.)i Yes, I did upgrade to the latest in etch (which I am running currently) hoping for such a miracle. Maybe I should consider going back to sid, which I ran for a long time previously. I had the impression three months or so ago that that was a bad moment to get into sid, so I am still here in etch. In that case, the first thing I would try is installing a 2.6.22 kernel from www.backports.org. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 01:33:26PM +0100, Richard Lyons wrote: On Thu, Nov 01, 2007 at 12:51:51PM +0100, Florian Kulzer wrote: [...] I am just following Documentation/sound/alsa/ALSA-Configuration.txt. The Documentation directory is part of the kernel source; you can also get it separately by installing the linux-doc-... package for your version of the kernel. One source of problems with ALSA is that each driver (snd_hda_intel in your case) has to support different codec chips (here: ALC883) and that each codec chip can come in a number of different configurations (models). The ALSA developers are in an arms race with the laptop manufacturers, trying to make sure that the driver recognizes the codec chip model correctly for the ever-increasing number of laptop models. In your case no specific codec chip model was declared when the module was loaded, so the default configuration was chosen. This could mean that there might be an additional volume control for your chip which is currently inaccessible to you. You can try different codec chip models (e.g. 3stack) by running: modprobe -r snd_hda_intel modprobe snd_hda_intel model=3stack I tried that arbitrarily, but it didn't happen to be the one. I shall have to read the documentation to see what other options there are. I'm not sure if its been mentioned in this thread yet or not, but at least some (well, okay, one -- mine!) distinguishes between onboard sound and an external amplifier. My rig has two jacks on the front, one for headphones and one for external amplifier. For some reason the default configuration is to have the external amp *on*. This mutes the rest of the sound (even if the channels don't show as muted in alsamixer. In the event you have this sort of configuration, unless you get an external amplifier control in alsamixer, then you've not got the right configuration and won't get sound. It took me a while to figure that out... mute the external amp, and the rest of sound magically works. Florian's idea of moving up to a backported kernel is a good one, IMO. A signature.asc Description: Digital signature
Re: Tool to configure sound
On Thursday 01 November 2007 16:28, Andrew Sackville-West wrote: On Thu, Nov 01, 2007 at 01:33:26PM +0100, Richard Lyons wrote: On Thu, Nov 01, 2007 at 12:51:51PM +0100, Florian Kulzer wrote: [...] I am just following Documentation/sound/alsa/ALSA-Configuration.txt. The Documentation directory is part of the kernel source; you can also get it separately by installing the linux-doc-... package for your version of the kernel. One source of problems with ALSA is that each driver (snd_hda_intel in your case) has to support different codec chips (here: ALC883) and that each codec chip can come in a number of different configurations (models). The ALSA developers are in an arms race with the laptop manufacturers, trying to make sure that the driver recognizes the codec chip model correctly for the ever-increasing number of laptop models. In your case no specific codec chip model was declared when the module was loaded, so the default configuration was chosen. This could mean that there might be an additional volume control for your chip which is currently inaccessible to you. You can try different codec chip models (e.g. 3stack) by running: modprobe -r snd_hda_intel modprobe snd_hda_intel model=3stack I tried that arbitrarily, but it didn't happen to be the one. I shall have to read the documentation to see what other options there are. I'm not sure if its been mentioned in this thread yet or not, but at least some (well, okay, one -- mine!) distinguishes between onboard sound and an external amplifier. My rig has two jacks on the front, one for headphones and one for external amplifier. For some reason the default configuration is to have the external amp *on*. This mutes the rest of the sound (even if the channels don't show as muted in alsamixer. In the event you have this sort of configuration, unless you get an external amplifier control in alsamixer, then you've not got the right configuration and won't get sound. It took me a while to figure that out... mute the external amp, and the rest of sound magically works. Florian's idea of moving up to a backported kernel is a good one, IMO. A I think I'd also consider upgrading the alsa driver. I've been on the alsa-user list for ages, and most recently on the alsa-devel list. the alsa folks are working hard on resolving problems, particularly with hda intel, and patches are constantly being applied to the nightly builds of the alsa driver, which is available from. ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ The now current 1.0.15 alsa driver is available from. http://alsa-project.org Richard is using Debian Etch, and on my Etch using the 2.6.18-5-686 kernel, the alsa driver version is showing as 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC). This works fine for my audigy2 soundblaster (emu10k1), but for your laptop Richard, if it's the latest, and greatest, you may just have to go with upgrading the alsa driver. I've experimented with upgrading the alsa driver on my Fedora installs, and apart from needing to install the kernel-devel package (the kernel headers were already installed) there were no problems. With Archlinux I only had the kernel headers installed, but a ./configure, make, su to root, and make install when cd'd to where the alsa driver was downloaded worked ok. I'm not sure which packages are required to upgrade the alsa driver on Debian, and any help/suggestions would be welcome, not only for me, but perhaps Richard also. 2¢ worth of suggestions. Nigel.
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 08:18:35PM +0100, Nigel Henry wrote: ... I'm not sure which packages are required to upgrade the alsa driver on Debian, and any help/suggestions would be welcome, not only for me, but perhaps Richard also. probably only linux-headers-kernel-version and build-essential. at least that's a good place to start. A signature.asc Description: Digital signature
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 08:28:08AM -0700, Andrew Sackville-West wrote: I'm not sure if its been mentioned in this thread yet or not, but at least some (well, okay, one -- mine!) distinguishes between onboard sound and an external amplifier. My rig has two jacks on the front, one for headphones and one for external amplifier. For some reason the default configuration is to have the external amp *on*. This mutes the rest of the sound (even if the channels don't show as muted in alsamixer. That could be the case, I suppose. I have three jack sockets, headphones, mike, and one of thse symbols that might be almost anything ((o) --a bit like that but with a horizontal line going through the 'o' and the right hand backet. In the event you have this sort of configuration, unless you get an external amplifier control in alsamixer, then you've not got the right configuration and won't get sound. It took me a while to figure that out... mute the external amp, and the rest of sound magically works. Florian's idea of moving up to a backported kernel is a good one, IMO. Hes, I am sure that is a good idea. Sadly I fear it will hae to wait for a few days as I am rushed with things that matter more. Thanks to both of you. I guess I shall start a new thread if the saga continues when I get back to it (or maybe there will only need to be a single SOLVED posting crosses fingers) -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Thu, Nov 01, 2007 at 08:18:35PM +0100, Nigel Henry wrote: I think I'd also consider upgrading the alsa driver. I've been on the alsa-user list for ages, and most recently on the alsa-devel list. the alsa folks are working hard on resolving problems, particularly with hda intel, and patches are constantly being applied to the nightly builds of the alsa driver, which is available from. ftp://ftp.suse.com/pub/projects/alsa/snapshot/driver/ The now current 1.0.15 alsa driver is available from. http://alsa-project.org Richard is using Debian Etch, and on my Etch using the 2.6.18-5-686 kernel, the alsa driver version is showing as 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC). This works fine for my audigy2 soundblaster (emu10k1), but for your laptop Richard, if it's the latest, and greatest, you may just have to go with upgrading the alsa driver. Well, latest and greatest it isn't. I bought it because it was cheap in a clearance sale and had 'doze on it, which I needed for 5 minutes to set up a GPRS modem. (Actually, it turned out I didn't need it after all...). By my standards, it is recent (my next most modern is the IBM 600E) Anyway, suggestion noted: I'll start with the kernel and move on to the alsa driver if necessary. Thanx, -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Thursday 01 November 2007 21:07, Andrew Sackville-West wrote: On Thu, Nov 01, 2007 at 08:18:35PM +0100, Nigel Henry wrote: ... I'm not sure which packages are required to upgrade the alsa driver on Debian, and any help/suggestions would be welcome, not only for me, but perhaps Richard also. probably only linux-headers-kernel-version and build-essential. at least that's a good place to start. A Thanks Andrew. That was easy. Install kernel headers for currently running kernel, which also pulled in as a dependency, the kernel-package package, and the rest is just as the other distros I've upgraded the alsa driver on. Many thanks. Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 02:10:24PM +0800, swhe wrote: can u get the sound when u use a headphone? No, that seems silent too. what's the result of cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xd000c000 irq 177 and, as I haven't given it before in this thread $ lspci | grep udio 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 00:28:46 +0100, Richard Lyons wrote: On Tue, Oct 30, 2007 at 11:32:18PM +0100, Florian Kulzer wrote: [...] That is indeed the normal output, so speaker-test seems to think everything is OK. What do you get from running amixer? Florian, hello. How nice to have your help once again. Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 230 [90%] Front Right: Playback 230 [90%] Simple mixer control 'Front',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 24 [77%] [on] Front Right: Playback 24 [77%] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 19 [61%] [on] Front Right: Playback 19 [61%] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 4 [13%] [off] Front Right: Playback 4 [13%] [off] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [off] Front Right: Capture 0 [0%] [off] Simple mixer control 'Capture',1 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [on] Front Right: Capture 0 [0%] [on] Simple mixer control 'Input Source',0 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' Simple mixer control 'Input Source',1 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' I assume this is listing the results of my last wild click-on- anything-to-see-if-it-helps session with alsamixergui. I don't see anything obvious, but the names and the functions of the ALSA controls are always a bit counterintuitive to me. (Also, for added fun, they are different for every card.) You could keep speaker-test running in one terminal while using alsamixer in another terminal to play with the controls until you hear sound. (Alsamixer is curses-based; the CURSOR keys move around and change volume, M toggles muting, SPACE switches values, and TAB changes between playback and capture channels.) Then it is trial-and-error time: I would start with looking at IEC958 and switching the Input Source ones. Sometimes weird interactions exist, for example it is possible that one channel has to be muted for another channel to have output. This might take a while; alsamixer at least gives you direct access to all ALSA channels. (It may well be that alsamixergui also does this; I simply have never used it.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 10:59:14AM +0100, Florian Kulzer wrote: I don't see anything obvious, but the names and the functions of the ALSA controls are always a bit counterintuitive to me. (Also, for added fun, they are different for every card.) In this case there are not too many of them, only 'PCM', 'Front', 'Line', 'Mic', 'IEC958', 'Capture', 'Capture', 'Input So', 'Input So.' You could keep speaker-test running in one terminal while using alsamixer in another terminal to play with the controls until you hear sound. That was fun. I think I tried every permutation. PCM has only volume; Front, Line, and Mic have volume and mute; IEC958 has only mute; the two Captures have volume and space toggles a display of LR CAPTUR beneath, whatever that may mean (stereo on and off?); the two Input So. have only the option to be Line or Mic. Anyway, it remains steadfastly silent in every conceivable state while speaker-test continues to say Time per period = 2,986811 0 - Front Left and so on. It is not hardware, I have booted Doze a couple of times, and that gives nasty little jingles. Never mind -- I'll buy a phonograph, a soft cloth and scour the second-hand markets for vinyl... Thanks anyway. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 11:48:16 +0100, Richard Lyons wrote: On Wed, Oct 31, 2007 at 10:59:14AM +0100, Florian Kulzer wrote: I don't see anything obvious, but the names and the functions of the ALSA controls are always a bit counterintuitive to me. (Also, for added fun, they are different for every card.) In this case there are not too many of them, only 'PCM', 'Front', 'Line', 'Mic', 'IEC958', 'Capture', 'Capture', 'Input So', 'Input So.' You could keep speaker-test running in one terminal while using alsamixer in another terminal to play with the controls until you hear sound. That was fun. I think I tried every permutation. PCM has only volume; Front, Line, and Mic have volume and mute; IEC958 has only mute; the two Captures have volume and space toggles a display of LR CAPTUR beneath, whatever that may mean (stereo on and off?); the two Input So. have only the option to be Line or Mic. Anyway, it remains steadfastly silent in every conceivable state while speaker-test continues to say Time per period = 2,986811 0 - Front Left and so on. OK, changing mixer settings does not help; there must be a more fundamental problem with the driver or the hardware. It is not hardware, I have booted Doze a couple of times, and that gives nasty little jingles. OK, so the hardware works. Never mind -- I'll buy a phonograph, a soft cloth and scour the second-hand markets for vinyl... To keep yourself entertained until you get the phonograph, you could post the output of these commands: cat /proc/asound/card0/codec* | head grep '.*' /sys/module/snd_hda_intel/parameters/* -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 06:38:02PM +0100, Florian Kulzer wrote: On Wed, Oct 31, 2007 at 11:48:16 +0100, Richard Lyons wrote: [...] OK, so the hardware works. Never mind -- I'll buy a phonograph, a soft cloth and scour the second-hand markets for vinyl... To keep yourself entertained until you get the phonograph, you could post the output of these commands: $ cat /proc/asound/card0/codec* | head Codec: Realtek ALC883 Address: 0 Vendor Id: 0x10ec0883 Subsystem Id: 0x1025160d Revision Id: 0x12 Default PCM: rates 0x560, bits 0x0e, types 0x1 Default Amp-In caps: N/A Default Amp-Out caps: N/A Node 0x02 [Audio Output] wcaps 0x11: Stereo PCM: rates 0x560, bits 0x0e, types 0x1 $ grep '.*' /sys/module/snd_hda_intel/parameters/* /sys/module/snd_hda_intel/parameters/enable:N /sys/module/snd_hda_intel/parameters/id:NULL /sys/module/snd_hda_intel/parameters/index:0 /sys/module/snd_hda_intel/parameters/model:NULL /sys/module/snd_hda_intel/parameters/position_fix:0 /sys/module/snd_hda_intel/parameters/probe_mask:-1 /sys/module/snd_hda_intel/parameters/single_cmd:N Maybe I'm dim or maybe it is just late, but I can't even guess what all that says. I'm impressed you even knew to suggest those. Do they help? -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Sun, Oct 28, 2007 at 10:55:02PM +0100, Bruno Costacurta wrote: [...] I followed instructions at the here previous indicated URL and run 'alsaconf' which indeed completed and corrected the configuration of my sound card. Now everything is fine. All tests are OK. Lucky man! I wish it would work for my Acer laptop! Still, I suppose after all these years I should know better than to expect sound on a laptop. I see I have 3 modules loaded that you don't have, maybe it's something to do with them. snd_hda_intel 17140 0 snd_hda_codec 126496 1 snd_hda_intel snd_pcm_oss35968 0 snd_mixer_oss 15872 1 snd_pcm_oss snd_pcm74532 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20836 1 snd_pcm snd48100 6 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 9216 1 snd snd_page_alloc 9512 2 snd_hda_intel,snd_pcm Still, it's all way over my head... :-( richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, 31 Oct 2007, Richard Lyons shared this with us all: --} On Sun, Oct 28, 2007 at 10:55:02PM +0100, Bruno Costacurta wrote: --} [...] --} I followed instructions at the here previous indicated URL and run 'alsaconf' --} which indeed completed and corrected the configuration of my sound --} card. --} Now everything is fine. All tests are OK. --} --} Lucky man! I wish it would work for my Acer laptop! Still, I suppose --} after all these years I should know better than to expect sound on a --} laptop. I see I have 3 modules loaded that you don't have, maybe it's --} something to do with them. --} --} snd_hda_intel 17140 0 --} snd_hda_codec 126496 1 snd_hda_intel --} snd_pcm_oss35968 0 --} snd_mixer_oss 15872 1 snd_pcm_oss --} snd_pcm74532 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss --} snd_timer 20836 1 snd_pcm --} snd48100 6 --} snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer --} soundcore 9216 1 snd --} snd_page_alloc 9512 2 snd_hda_intel,snd_pcm --} --} Still, it's all way over my head... --} --} :-( --} --} richard --} --} I have two Acer laptops and both have sound configured and working using alsaconf, have you tried it? Charlie -- Registered Linux User:- 329524 +++ What's here right now? Delusion is yesterday's dream-enlightenment, tomorrow's delusion. - TAIZAN MAEZUMI Debian - Just the best way to do magic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 07:52:59AM +1100, Charlie wrote: On Wed, 31 Oct 2007, Richard Lyons shared this with us all: [...] --} Lucky man! I wish it would work for my Acer laptop! Still, I suppose --} after all these years I should know better than to expect sound on a --} laptop. I see I have 3 modules loaded that you don't have, maybe it's --} something to do with them. --} --} snd_hda_intel 17140 0 --} snd_hda_codec 126496 1 snd_hda_intel --} snd_pcm_oss35968 0 --} snd_mixer_oss 15872 1 snd_pcm_oss --} snd_pcm74532 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss --} snd_timer 20836 1 snd_pcm --} snd48100 6 --} snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer --} soundcore 9216 1 snd --} snd_page_alloc 9512 2 snd_hda_intel,snd_pcm --} --} Still, it's all way over my head... I have two Acer laptops and both have sound configured and working using alsaconf, have you tried it? A hundred times. It says ALSA is ready to use, and wishes me a lot of fun. As long as it's happy... In fact the link given earlier in the thread to http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux says: Alsaconf is so buggy that it is best not to use it at the moment (according to [bug no 432678]). You now have to use udevtrigger instead of alsaconf. But that did nothing useful either as far as I could tell. Mine is an Acer Aspire 1640Z, FWIW. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, 31 Oct 2007, Richard Lyons shared this with us all: snip --} A hundred times. It says ALSA is ready to use, and wishes me a lot of --} fun. As long as it's happy... --} In fact the link given earlier in the thread to --} http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux --} says: --} Alsaconf is so buggy that it is best not to use it at the moment --} (according to [bug no 432678]). --} --} You now have to use udevtrigger instead of alsaconf. --} --} But that did nothing useful either as far as I could tell. --} --} Mine is an Acer Aspire 1640Z, FWIW. --} --} -- --} richard --} That might be a more modern Acer lappy than my two. One being an Acer 1350 and the other an Acer 3610. Only have solar power, so have to rely on laptops and watch DVD's on them as well. I didn't know about the bug. Maybe ignorance is bliss in this case. Also installed the alsamixergui package, thinking that it would work best with the sound card it discovered. It works well on both machines. I don't think anything other than that was done, and I use Debian testing on both, just in case that makes a difference? So maybe its something particular to your Acer lappy? Thanks for the heads up about udevtrigger. I might need that for a machine I install for someone else in the future. Be well, Charlie -- Registered Linux User:- 329524 +++ The sun is but a morning star. .Henry David Thoreau Debian - Just the best way to do magic.
Re: Tool to configure sound
On Tue, Oct 30, 2007 at 22:00:43 +0100, Richard Lyons wrote: On Wed, Oct 31, 2007 at 07:52:59AM +1100, Charlie wrote: On Wed, 31 Oct 2007, Richard Lyons shared this with us all: [...] --} Lucky man! I wish it would work for my Acer laptop! Still, I suppose --} after all these years I should know better than to expect sound on a --} laptop. I see I have 3 modules loaded that you don't have, maybe it's --} something to do with them. --} --} snd_hda_intel 17140 0 --} snd_hda_codec 126496 1 snd_hda_intel --} snd_pcm_oss35968 0 --} snd_mixer_oss 15872 1 snd_pcm_oss --} snd_pcm74532 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss --} snd_timer 20836 1 snd_pcm --} snd48100 6 --} snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer --} soundcore 9216 1 snd --} snd_page_alloc 9512 2 snd_hda_intel,snd_pcm --} --} Still, it's all way over my head... I have two Acer laptops and both have sound configured and working using alsaconf, have you tried it? A hundred times. It says ALSA is ready to use, and wishes me a lot of fun. As long as it's happy... In fact the link given earlier in the thread to http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux says: Alsaconf is so buggy that it is best not to use it at the moment (according to [bug no 432678]). You now have to use udevtrigger instead of alsaconf. But that did nothing useful either as far as I could tell. Mine is an Acer Aspire 1640Z, FWIW. What happens if you run speaker-test, do you get an error message or is it just not producing any sound? -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Tue, Oct 30, 2007 at 10:13:30PM +0100, Florian Kulzer wrote: On Tue, Oct 30, 2007 at 22:00:43 +0100, Richard Lyons wrote: [...] Mine is an Acer Aspire 1640Z, FWIW. What happens if you run speaker-test, do you get an error message or is it just not producing any sound? It says this sort of thing: speaker-test 1.0.13 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left Time per period = 2,657907 0 - Front Left Time per period = 2,986793 0 - Front Left Time per period = 2,986802 0 - Front Left Time per period = 2,986797 0 - Front Left ... until I ctl-c out of it. But silently. That doesn't look to me like errors. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Tue, Oct 30, 2007 at 23:09:47 +0100, Richard Lyons wrote: On Tue, Oct 30, 2007 at 10:13:30PM +0100, Florian Kulzer wrote: On Tue, Oct 30, 2007 at 22:00:43 +0100, Richard Lyons wrote: [...] Mine is an Acer Aspire 1640Z, FWIW. What happens if you run speaker-test, do you get an error message or is it just not producing any sound? It says this sort of thing: speaker-test 1.0.13 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left Time per period = 2,657907 0 - Front Left Time per period = 2,986793 0 - Front Left Time per period = 2,986802 0 - Front Left Time per period = 2,986797 0 - Front Left ... until I ctl-c out of it. But silently. That doesn't look to me like errors. That is indeed the normal output, so speaker-test seems to think everything is OK. What do you get from running amixer? -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Tue, Oct 30, 2007 at 11:32:18PM +0100, Florian Kulzer wrote: [...] That is indeed the normal output, so speaker-test seems to think everything is OK. What do you get from running amixer? Florian, hello. How nice to have your help once again. Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 230 [90%] Front Right: Playback 230 [90%] Simple mixer control 'Front',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 24 [77%] [on] Front Right: Playback 24 [77%] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 19 [61%] [on] Front Right: Playback 19 [61%] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 4 [13%] [off] Front Right: Playback 4 [13%] [off] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [off] Front Right: Capture 0 [0%] [off] Simple mixer control 'Capture',1 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [on] Front Right: Capture 0 [0%] [on] Simple mixer control 'Input Source',0 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' Simple mixer control 'Input Source',1 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' I assume this is listing the results of my last wild click-on- anything-to-see-if-it-helps session with alsamixergui. Needless to say, nothing did help. Perhaps the sound is just muted because Debian doesn't know about the blue function key things on the laptop. I have tried pressing the speaker-related ones, but also to no avail. Debian doesn't know about the screen brightness keys either -- gives 2 error messages for every keypress -- but they still work on the brightness. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
can u get the sound when u use a headphone? On 10/31/07, Richard Lyons [EMAIL PROTECTED] wrote: On Tue, Oct 30, 2007 at 11:32:18PM +0100, Florian Kulzer wrote: [...] That is indeed the normal output, so speaker-test seems to think everything is OK. What do you get from running amixer? Florian, hello. How nice to have your help once again. Simple mixer control 'PCM',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 255 Mono: Front Left: Playback 230 [90%] Front Right: Playback 230 [90%] Simple mixer control 'Front',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 24 [77%] [on] Front Right: Playback 24 [77%] [on] Simple mixer control 'Line',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 19 [61%] [on] Front Right: Playback 19 [61%] [on] Simple mixer control 'Mic',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 4 [13%] [off] Front Right: Playback 4 [13%] [off] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [off] Front Right: Capture 0 [0%] [off] Simple mixer control 'Capture',1 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 31 Front Left: Capture 0 [0%] [on] Front Right: Capture 0 [0%] [on] Simple mixer control 'Input Source',0 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' Simple mixer control 'Input Source',1 Capabilities: enum Items: 'Mic' 'Line' Item0: 'Mic' I assume this is listing the results of my last wild click-on- anything-to-see-if-it-helps session with alsamixergui. Needless to say, nothing did help. Perhaps the sound is just muted because Debian doesn't know about the blue function key things on the laptop. I have tried pressing the speaker-related ones, but also to no avail. Debian doesn't know about the screen brightness keys either -- gives 2 error messages for every keypress -- but they still work on the brightness. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Yours, swhe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Wed, Oct 31, 2007 at 09:13:55AM +0800, swhe wrote: On 10/31/07, Richard Lyons [EMAIL PROTECTED] wrote: On Tue, Oct 30, 2007 at 11:32:18PM +0100, Florian Kulzer wrote: [...] That is indeed the normal output, so speaker-test seems to think everything is OK. What do you get from running amixer? [...] Needless to say, nothing did help. Perhaps the sound is just muted because Debian doesn't know about the blue function key things on the laptop. I have tried pressing the speaker-related ones, but also to no avail. Debian doesn't know about the screen brightness keys either -- gives 2 error messages for every keypress -- but they still work on the brightness. can u get the sound when u use a headphone? No, that seems silent too. -- richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
can u get the sound when u use a headphone? No, that seems silent too. what's the result of cat /proc/asound/cards -- Yours, swhe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Tool to configure sound
Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. Drivers looks correctly installed as 'lsmod' shows following drivers : .. snd_hda_intel 17332 3 snd_hda_codec 137856 1 snd_hda_intel snd_pcm_oss38368 0 snd_mixer_oss 15200 1 snd_pcm_oss snd_pcm68676 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20996 2 snd_pcm .. Is there tool (ie. like system-config-sound) to setup and check sound setup ? Thanks for any help. Bye, Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
Hi, check your settings account in users and group Bye Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. Drivers looks correctly installed as 'lsmod' shows following drivers : .. snd_hda_intel 17332 3 snd_hda_codec 137856 1 snd_hda_intel snd_pcm_oss38368 0 snd_mixer_oss 15200 1 snd_pcm_oss snd_pcm68676 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20996 2 snd_pcm .. Is there tool (ie. like system-config-sound) to setup and check sound setup ? Thanks for any help. Bye, Bruno =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Scanned with Copfilter Version 0.84beta2 (ProxSMTP 1.6) by Markus Madlener @ http://www.copfilter.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Sun, Oct 28, 2007 at 05:21:52PM +0100, Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. there are several possible things: 1. you aren't in the audio group (adduser you audio, log out and back in). 2. your mixer is set to 0 volume. run alsamixer and review all the settings. 3. despite the apparently correct modules being inserted, sometimes it just doesn't work out of the box. If the above things don't work, you could try modprobe -r all the sound modules, then do a udevtrigger to reload them and see what happens. if none of the above help, post back up as there are several people who are very adept at solving sound issues here. A signature.asc Description: Digital signature
Re: Tool to configure sound
Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. Drivers looks correctly installed as 'lsmod' shows following drivers : .. snd_hda_intel 17332 3 snd_hda_codec 137856 1 snd_hda_intel snd_pcm_oss38368 0 snd_mixer_oss 15200 1 snd_pcm_oss snd_pcm68676 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20996 2 snd_pcm .. Is there tool (ie. like system-config-sound) to setup and check sound setup ? Thanks for any help. Check that levels are set in alsamixer or alsamixergui. Check that you are configuring the sound card you have attached the speakers to (some motherboards have built-in sound too). The name of the sound card appears at the top of the mixer. Check sound works by running speaker-test. $ speaker-test More details on the NewbieDOC wiki [1]. [1] http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux -- Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. Drivers looks correctly installed as 'lsmod' shows following drivers : .. snd_hda_intel 17332 3 snd_hda_codec 137856 1 snd_hda_intel snd_pcm_oss38368 0 snd_mixer_oss 15200 1 snd_pcm_oss snd_pcm68676 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20996 2 snd_pcm .. Is there tool (ie. like system-config-sound) to setup and check sound setup ? Thanks for any help. Bye, Bruno hi bruno, beside all the good advice you received: in my experience hda-intel gives problems when i use the built-in kernel-modules in the 2.6.18 kernels and their predecessors. their are several ways to circumvent this problem (see the archive of this list). i chose a rather radical way. i got the alsa-driver, alsa-libs and alsa-utils from the alsa website; compiled them in /usr/src/alsa and (the libs and utils) in my home-directory and installed them. i started installing the driver doing as root : #./configure --with-cards=hda-intel. since that time (rather long ago) my onboard nvidia sound chip hda-intel works perfect. regards, steef -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Sunday 28 October 2007 18:03, Andrew Sackville-West wrote: On Sun, Oct 28, 2007 at 05:21:52PM +0100, Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. there are several possible things: 1. you aren't in the audio group (adduser you audio, log out and back in). Already fine for user in group audio. 2. your mixer is set to 0 volume. run alsamixer and review all the settings. Same. Volume was set. 3. despite the apparently correct modules being inserted, sometimes it just doesn't work out of the box. If the above things don't work, you could try modprobe -r all the sound modules, then do a udevtrigger to reload them and see what happens. Followed these instructions. Fine to remove all module snd_xxx or soundcore with 'modprobe -r' but following 'udevtrigger --verbose' seems to give no useful info. if none of the above help, post back up as there are several people who are very adept at solving sound issues here. A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tool to configure sound
On Sunday 28 October 2007 18:56, Chris Lale wrote: Bruno Costacurta wrote: Hello, I installed Debian Etch but have no sound at all. Previous Fedora installation gave sounds so probably my Etch is missing some setup. Drivers looks correctly installed as 'lsmod' shows following drivers : .. snd_hda_intel 17332 3 snd_hda_codec 137856 1 snd_hda_intel snd_pcm_oss38368 0 snd_mixer_oss 15200 1 snd_pcm_oss snd_pcm68676 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 20996 2 snd_pcm .. Is there tool (ie. like system-config-sound) to setup and check sound setup ? Thanks for any help. Check that levels are set in alsamixer or alsamixergui. Check that you are configuring the sound card you have attached the speakers to (some motherboards have built-in sound too). The name of the sound card appears at the top of the mixer. Check sound works by running speaker-test. $ speaker-test More details on the NewbieDOC wiki [1]. [1] http://newbiedoc.berlios.de/wiki/Sound_in_Debian_GNU/Linux -- Chris. Hi, I followed instructions at the here previous indicated URL and run 'alsaconf' which indeed completed and corrected the configuration of my sound card. Now everything is fine. All tests are OK. Many thanks for help. Bye, Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
