Re: [Alsa-user] Problems with snd hda intel: works only part of the time
On Sat, 2006-10-07 at 10:24 -0500, Peter Hartman wrote: > I'm glad your issue was resolved, but if you check the start of this > thread, it was my original issue, which is still unresolved, that > started this all off! :) Any insights into the issue? > It must be a driver bug. You're not doing anything wrong. Please file a report in the ALSA bug tracker (search for existing ones first). 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.php&p=sourceforge&CID=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 glad your issue was resolved, but if you check the start of this thread, it was my original issue, which is still unresolved, that started this all off! :) Any insights into the issue? Thanks, Peter On 10/7/06, Dominique Michel <[EMAIL PROTECTED]> wrote: > Le Fri, 06 Oct 2006 16:55:29 -0400, > Lee Revell <[EMAIL PROTECTED]> a écrit : > > > On Fri, 2006-10-06 at 21:37 +0200, Dominique Michel wrote: > > > options snd-snd-usb-audio index=1 > > > > [...] > > > > > alias snd-card-1 snd-usb-audio > > > options snd-snd-usb-audio index=1 > > > > snd-snd-usb-audio is wrong, it should be snd-usb-audio. > > > > Did you create these files by hand? Or is it a Gentoo bug? > > > > Lee > > > > It is my bug and I am sorry about all this noise on the list. > > But I am not absolutely sure of what caused this misspelling, because it was > working it was a fee weeks ago, and it stop working after an upgrade. And I > don't remember at I edited some file before at it stop working. So maybe at it > was a problem with etc-update, but it look strange because I always refuse any > automatic modification of my files in /etc/modules.d. So it must be my fault > anyway. > > Thank you all of you that take the time to respond me. > > Best, > Dominique > > - > 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.php&p=sourceforge&CID=DEVDEV > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user > -- Hartman's Brain Consulting | Openflows Networks Ltd. | Campware.org gpg 1024D/ED6EF59B (7D1A 522F D08E 30F6 FA42 B269 B860 352B ED6E F59B) gpg --keyserver pgp.mit.edu --recv-keys ED6EF59B - 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.php&p=sourceforge&CID=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
Le Fri, 06 Oct 2006 16:55:29 -0400, Lee Revell <[EMAIL PROTECTED]> a écrit : > On Fri, 2006-10-06 at 21:37 +0200, Dominique Michel wrote: > > options snd-snd-usb-audio index=1 > > [...] > > > alias snd-card-1 snd-usb-audio > > options snd-snd-usb-audio index=1 > > snd-snd-usb-audio is wrong, it should be snd-usb-audio. > > Did you create these files by hand? Or is it a Gentoo bug? > > Lee > It is my bug and I am sorry about all this noise on the list. But I am not absolutely sure of what caused this misspelling, because it was working it was a fee weeks ago, and it stop working after an upgrade. And I don't remember at I edited some file before at it stop working. So maybe at it was a problem with etc-update, but it look strange because I always refuse any automatic modification of my files in /etc/modules.d. So it must be my fault anyway. Thank you all of you that take the time to respond me. Best, Dominique - 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.php&p=sourceforge&CID=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 Friday 06 October 2006 21:37, Dominique Michel wrote: > Le Fri, 06 Oct 2006 19:34:07 +0200, > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > Dominique Michel wrote: > > > The fact is at the alsa configuration in modprobe.conf will not work as > > > expected if udev load some sound module before modprobe or alsasound. > > > > Both udev and alsasound use modprobe to load modules. > > > > > I just checked my alsa configuration files to see if it was no > > > miss-spelling in it, ran a modules-update, removed snd-usb-audio from > > > my blacklist file, done a reboot, and the result was my webcam as sound > > > card 0 when it is sound card 1 in modules.conf. > > > > That file is named modprobe.conf with 2.6 kernels. > > > > Please show the contents of your modprobe.conf. > > > > > > Regards, > > Clemens > > Here it is: > > ### This file is automatically generated by modules-update > # > # Please do not edit this file directly. If you want to change or add > # anything please take a look at the files in /etc/modprobe.d and read > # the manpage for modules-update(8). > # > > alias binfmt-204 binfmt_aout options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330 > options snd-emu10k1 max_buffer_size=256 > options snd-snd-usb-audio index=1 I query the entry above. What is options snd-snd-usb-audio index=1? Surely this should be, options snd-usb-audio index=1. I would have thought as this is malformed it would be ignored, and depending how this file is read, snd-usb-audio would still end up being set as card 0. > options snd-virmidi index=2 > options snd-ens1370 index=3 > options snd cards_limit=4 > options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1 > > > ## > ## IMPORTANT: > ## You need to customise this section for your specific sound card(s) > ## and then run `update-modules' command. > ## Read alsa-driver's INSTALL file in /usr/share/doc for more info. > ## > ## ALSA portion > alias snd-card-0 snd-emu10k1 > options snd-emu10k1 index=0 > alias snd-card-1 snd-usb-audio > options snd-snd-usb-audio index=1 Same goes for the entry above. I see your using Gentoo, but have never seen an option entry for snd-usb-audio like that before. It may be worth editing this file to correct those 2 lines, running update-modules again, and try again. Nigel. - 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.php&p=sourceforge&CID=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 Fri, 2006-10-06 at 22:29 +0200, Sergei Steshenko wrote: > I think that we, end users, want the following: > > * we want to be able to disconnect/reconnect external cards; > * we want to be able to use (crappy) internal audio chips for things > like > Internet telephony; > * whenever we disconnect/reconnect external cards, we do NOT want to > adjust > ALSA configuration files - especially taking into account difficulty > creating > them. > > So, the mechanism should allow to assign to cards indices once and for > all - regardless whether the card is present or not. Please make sure to file bug reports against any application that relies on a fixed device order. Also, it's not necessary to manage the default card via module parameters. Look at gnome-sound-properties, which sets the default card by changing the definition in the user's ALSA config file. Module indexes are a short-term band aid, they should definitely not be considered a real solution. 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.php&p=sourceforge&CID=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 Fri, 2006-10-06 at 21:37 +0200, Dominique Michel wrote: > options snd-snd-usb-audio index=1 [...] > alias snd-card-1 snd-usb-audio > options snd-snd-usb-audio index=1 snd-snd-usb-audio is wrong, it should be snd-usb-audio. Did you create these files by hand? Or is it a Gentoo bug? 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.php&p=sourceforge&CID=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 Friday 06 October 2006 20:37, Dominique Michel wrote: >> Please show the contents of your modprobe.conf. > Here it is: > ... > ### This file is automatically generated by modules-update > # > # Please do not edit this file directly. If you want to change or add > # anything please take a look at the files in /etc/modprobe.d and read > # the manpage for modules-update(8). > ... > options snd-snd-usb-audio index=1 There's the problem - it says "snd-snd-usb-audio" instead of "snd-usb-audio". But you can't just edit /etc/modprobe.conf because it's autogenerated on your distro. So, run 'grep snd-snd-usb-audio /etc/modprobe.d/*' to find which file contains the typo, then edit it (or, if you're feeling daring, you could use sed to find and correct the typo automatically) and re-run modules-update (see its manpage). FYI, I use the index=x notation in my modprobe.conf with udev loading modules for onboard and offboard sound and it works fine - the Audigy is always card 0 and the VIA8237 is always card 1. Hope this helps, Stephen - 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.php&p=sourceforge&CID=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 Fri, 6 Oct 2006 21:37:37 +0200 Dominique Michel <[EMAIL PROTECTED]> wrote: ... > ### > > It seem correct to me, but I can be wrong. For me, the problem is only at udev > load the driver before alsasound. Udev have its own rules, and even if it use > modprobe, I don't think at it will use the options in this file. > It is more people that have similar problem with alsasound. It is a forum > thread about it, and some people run 2 time alsasound in their init script, > one > time in the boot level, they get a wrong sound card order, and one more time > in > the default runlevel. The second time, as alsasound is already started, init > will issue an "alsasound restart", the modules will be unloaded and loaded > again, but that time with the correct order. So, it confirm at udev and > hotplug just don't look at the options in modules.conf. > > It is also a bug report on bugzilla with similar problem between udev-hotplug > and /etc/modules.autoload.d/kernel-2.6. Udev load the modules specified in > that > file, but not the options of the specified drivers. > http://bugs.gentoo.org/show_bug.cgi?id=129047 > > Best, > Dominique > > - > 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.php&p=sourceforge&CID=DEVDEV > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user I think that we, end users, want the following: * we want to be able to disconnect/reconnect external cards; * we want to be able to use (crappy) internal audio chips for things like Internet telephony; * whenever we disconnect/reconnect external cards, we do NOT want to adjust ALSA configuration files - especially taking into account difficulty creating them. So, the mechanism should allow to assign to cards indices once and for all - regardless whether the card is present or not. Can the indices be non-contiguous ? Can we load external card driver even if the card is not present ? Do we need to load external card driver even if the card is not present ? Thanks, 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.php&p=sourceforge&CID=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
Le Fri, 06 Oct 2006 19:34:07 +0200, "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > Dominique Michel wrote: > > The fact is at the alsa configuration in modprobe.conf will not work as > > expected if udev load some sound module before modprobe or alsasound. > > Both udev and alsasound use modprobe to load modules. > > > I just checked my alsa configuration files to see if it was no > > miss-spelling in it, ran a modules-update, removed snd-usb-audio from my > > blacklist file, done a reboot, and the result was my webcam as sound card 0 > > when it is sound card 1 in modules.conf. > > That file is named modprobe.conf with 2.6 kernels. > > Please show the contents of your modprobe.conf. > > > Regards, > Clemens > Here it is: ### This file is automatically generated by modules-update # # Please do not edit this file directly. If you want to change or add # anything please take a look at the files in /etc/modprobe.d and read # the manpage for modules-update(8). # alias binfmt-204 binfmt_aout alias binfmt-263 binfmt_aout alias binfmt-264 binfmt_aout alias binfmt-267 binfmt_aout alias binfmt-387 binfmt_aout alias binfmt-332 iBCS alias binfmt--310 binfmt_java alias block-major-1-* rd alias block-major-2-* floppy alias block-major-3-* ide-probe-mod alias block-major-7-* loop alias block-major-8-* sd_mod alias block-major-9-* md alias block-major-11-* sr_mod alias block-major-13-* xd alias block-major-15-* cdu31a alias block-major-16-* gscd alias block-major-17-* optcd alias block-major-18-* sjcd alias block-major-20-* mcdx alias block-major-22-* ide-probe-mod alias block-major-23-* mcd alias block-major-24-* sonycd535 alias block-major-25-* sbpcd alias block-major-26-* sbpcd alias block-major-27-* sbpcd alias block-major-29-* aztcd alias block-major-32-* cm206 alias block-major-33-* ide-probe-mod alias block-major-34-* ide-probe-mod alias block-major-37-* ide-tape alias block-major-44-* ftl alias block-major-46-* pcd alias block-major-47-* pf alias block-major-56-* ide-probe-mod alias block-major-57-* ide-probe-mod alias block-major-58-* lvm-mod alias block-major-88-* ide-probe-mod alias block-major-89-* ide-probe-mod alias block-major-90-* ide-probe-mod alias block-major-91-* ide-probe-mod alias block-major-93-* nftl alias block-major-113-* viocd alias char-major-4-* serial alias char-major-5-* serial alias char-major-6-* lp alias char-major-9-* st alias char-major-10-0 busmouse alias char-major-10-2 msbusmouse alias char-major-10-3 atixlmouse alias char-major-10-116 snd alias char-major-10-130 wdt alias char-major-10-131 wdt alias char-major-10-135 rtc alias char-major-10-139 openprom alias char-major-10-144 nvram alias char-major-10-157 applicom alias char-major-10-175 agpgart alias char-major-10-181 toshiba alias char-major-10-183 hw_random alias char-major-10-184 microcode alias char-major-10-187 irnet alias char-major-10-189 ussp alias char-major-10-200 tun alias char-major-10-250 hci_vhci alias char-major-13-* input alias char-major-13-0 joydev alias char-major-13-32 mousedev alias char-major-14-* soundcore alias char-major-19-* cyclades alias char-major-20-* cyclades alias char-major-21-* sg alias char-major-22-* pcxx alias char-major-23-* pcxx alias char-major-27-* zftape alias char-major-34-* scc alias char-major-35-* tclmidi alias char-major-36-* netlink alias char-major-37-* ide-tape alias char-major-48-* riscom8 alias char-major-49-* riscom8 alias char-major-57-* esp alias char-major-58-* esp alias char-major-63-* kdebug alias char-major-90-* mtdchar alias char-major-96-* pt alias char-major-97-* pg alias char-major-99-* ppdev alias char-major-107-* 3dfx alias char-major-108-* ppp_generic alias char-major-109-* lvm-mod alias char-major-161-* ircomm-tty alias char-major-171-* raw1394 alias char-major-195-* nvidia alias char-major-200-* vxspec alias char-major-206-* osst alias char-major-216-* rfcomm alias dos msdos alias dummy0 dummy alias dummy1 dummy alias iso9660 isofs alias md-personality-1 linear alias md-personality-2 raid0 alias md-personality-3 raid1 alias md-personality-4 raid5 alias md-personality-7 multipath alias net-pf-1 unix alias net-pf-2 ipv4 alias net-pf-4 ipx alias net-pf-5 appletalk alias net-pf-15 af_key alias net-pf-17 af_packet alias net-pf-20 atm alias net-pf-23 irda alias net-pf-24 pppoe alias net-pf-25 wanrouter alias net-pf-26 llc alias net-pf-31 bluez alias netalias-2 ip_alias alias irlan0 irlan alias irda-dongle-0 tekram alias irda-dongle-1 esi alias irda-dongle-2 actisys alias irda-dongle-3 actisys alias irda-dongle-4 girbil alias irda-dongle-5 litelink alias irda-dongle-6 airport alias irda-dongle-7 old_belkin alias bt-proto-0 l2cap alias bt-proto-2 sco alias bt-proto-3 rfcomm alias bt-proto-4 bnep alias bt-proto-5 cmtp alias bt-proto-6 hidp alias bt-proto-7 avdtp alias plip0 plip alias plip1 plip alias tunl0 ipip alias cipcb0 cipcb alias cipcb1 cipcb alias cipcb2 cipcb alias cipcb3 cipcb alias ppp0 ppp_async alias ppp1 ppp_async alias slip0 slip alias slip1 s
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
Dominique Michel wrote: > The fact is at the alsa configuration in modprobe.conf will not work as > expected if udev load some sound module before modprobe or alsasound. Both udev and alsasound use modprobe to load modules. > I just checked my alsa configuration files to see if it was no miss-spelling > in > it, ran a modules-update, removed snd-usb-audio from my blacklist file, done a > reboot, and the result was my webcam as sound card 0 when it is sound card 1 > in > modules.conf. That file is named modprobe.conf with 2.6 kernels. Please show the contents of your modprobe.conf. 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.php&p=sourceforge&CID=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
Le Fri, 06 Oct 2006 15:48:28 +0200, "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > Dominique Michel wrote: > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > > Dominique Michel wrote: > > > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > > > > The correct way to specify sound card order is to set 'index' options > > > > > in modprobe.conf (or whatever file is used). This works regardless of > > > > > the order in which the drivers are loaded. > > > > > > > > I know that, but it just don't work if udev load any sound driver as > > > > snd_usb_audio before at alsasound is started. > > > > > > Of course it does work. Driver modules get their module options from > > > modprobe.conf regardless of when or how they are loaded. > > > > udev take its options from udev configuration files placed in /etc/udev/*. > > And not from modprobe.conf or whatever file is associated with modprobe. > > I'm speaking about module options. Those come from modprobe.conf, whether > the module is loaded manually, with kmod, or by udev. > > The udev configuration files do not specify any module options (except > when you manually add options to a modprobe call). > > > Regards, > Clemens > The fact is at the alsa configuration in modprobe.conf will not work as expected if udev load some sound module before modprobe or alsasound. And it is a fact. As you just said, The udev configuration files do not specify any module options. I just checked my alsa configuration files to see if it was no miss-spelling in it, ran a modules-update, removed snd-usb-audio from my blacklist file, done a reboot, and the result was my webcam as sound card 0 when it is sound card 1 in modules.conf. The situation is different if I do a "/etc/init.d/alsasound restart", because here, alsasound will first unload any sound module and reload them again. After this, I will get the same order as in modules.conf: 0: audigy, 1: usb, 2: virmidi This problem have at least tree aspects. 1) The alsa documentation use modules.conf and not udev, 2) the init process run udev and hotplug before to load the modules in modules.conf, 3) the average users just want at the sound work out of the box, and 3b) they are not confident with udev rules. A simple fix will be at "alsasound start" that most if not all the linux distribution are using to load the sound modules at boot time, first check for existing drivers and unload them if any before loading them. So, the sound cards order will be correct in any cases. Dominique - 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.php&p=sourceforge&CID=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
Dominique Michel wrote: > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > Dominique Michel wrote: > > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > > > The correct way to specify sound card order is to set 'index' options > > > > in modprobe.conf (or whatever file is used). This works regardless of > > > > the order in which the drivers are loaded. > > > > > > I know that, but it just don't work if udev load any sound driver as > > > snd_usb_audio before at alsasound is started. > > > > Of course it does work. Driver modules get their module options from > > modprobe.conf regardless of when or how they are loaded. > > udev take its options from udev configuration files placed in /etc/udev/*. And > not from modprobe.conf or whatever file is associated with modprobe. I'm speaking about module options. Those come from modprobe.conf, whether the module is loaded manually, with kmod, or by udev. The udev configuration files do not specify any module options (except when you manually add options to a modprobe call). 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.php&p=sourceforge&CID=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
Working: localhost peterjh # cat /proc/asound/card0/codec#0 Codec: SigmaTel ID 7634 Address: 0 Vendor Id: 0x83847634 Subsystem Id: 0x107b0461 Revision Id: 0x100101 Default PCM: rates 0x7e0, bits 0x0e, types 0x1 Default Amp-In caps: N/A Default Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Node 0x02 [Audio Output] wcaps 0xd0401: Stereo Power: 0x0 Node 0x03 [Audio Input] wcaps 0x1d0541: Stereo Power: 0x0 Connection: 1 0x14 Node 0x04 [Audio Input] wcaps 0x140311: Stereo Digital PCM: rates 0x160, bits 0x0e, types 0x5 Connection: 1 0x07 Node 0x05 [Audio Output] wcaps 0x40211: Stereo Digital PCM: rates 0x1e0, bits 0x0e, types 0x5 Node 0x06 [Audio Selector] wcaps 0x300901: Stereo Connection: 3 0x02* 0x07 0x14 Node 0x07 [Pin Complex] wcaps 0x430681: Stereo Digital Pincap 0x0810024: IN Pin Default 0x40c001f0: [N/A] SPDIF In at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Power: 0x0 Node 0x08 [Pin Complex] wcaps 0x400301: Stereo Digital Pincap 0x0810: OUT Pin Default 0x404001f0: [N/A] SPDIF Out at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Connection: 2 0x05* 0x14 Node 0x09 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=0 Amp-Out vals: [0x0f 0x0f] Connection: 1 0x0f Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x083f: IN OUT HP Pin Default 0x61813122: [N/A] Line In at Sep Rear Conn = 1/8, Color = Blue Pin-ctls: 0x00: Connection: 1 0x0e Node 0x0b [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN OUT Pin Default 0x02a11121: [Jack] Mic at Ext Front Conn = 1/8, Color = Black Pin-ctls: 0x20: IN Connection: 1 0x0e Node 0x0c [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN OUT Pin Default 0x50a70120: [N/A] Mic at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0x20: IN Connection: 1 0x0e Node 0x0d [Pin Complex] wcaps 0x400181: Stereo Pincap 0x083f: IN OUT HP Pin Default 0x90170110: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown Pin-ctls: 0xc0: OUT HP Connection: 1 0x0e Node 0x0e [Audio Selector] wcaps 0x300105: Stereo Amp-Out Amp-Out caps: N/A Amp-Out vals: [0x17 0x17] Connection: 1 0x06 Node 0x0f [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x04, stepsize=0x27, mute=0 Amp-Out vals: [0x04 0x04] Connection: 5 0x0b* 0x0c 0x0d 0x0a 0x11 Node 0x10 [Pin Complex] wcaps 0x400104: Mono Amp-Out Amp-Out caps: N/A Amp-Out vals: [0x00] Pincap 0x0810: OUT Pin Default 0x41f0: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Connection: 1 0x12 Node 0x11 [Pin Complex] wcaps 0x41: Stereo Pincap 0x0820: IN Pin Default 0x9033012e: [Fixed] CD at Int N/A Conn = ATAPI, Color = Unknown Pin-ctls: 0x20: IN Node 0x12 [Audio Mixer] wcaps 0x200100: Mono Connection: 1 0x06 Node 0x13 [Beep Generator Widget] wcaps 0x7c: Mono Amp-Out Amp-Out caps: ofs=0x03, nsteps=0x03, stepsize=0x17, mute=1 Amp-Out vals: [0x00] Node 0x14 [Audio Selector] wcaps 0x30090d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Connection: 1 0x09 -- NOT WORKING: localhost peterjh # cat /proc/asound/card0/codec#0 Codec: SigmaTel ID 7634 Address: 0 Vendor Id: 0x83847634 Subsystem Id: 0x107b0461 Revision Id: 0x100101 Default PCM: rates 0x7e0, bits 0x0e, types 0x1 Default Amp-In caps: N/A Default Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 Node 0x02 [Audio Output] wcaps 0xd0401: Stereo Power: 0x0 Node 0x03 [Audio Input] wcaps 0x1d0541: Stereo Power: 0x0 Connection: 1 0x14 Node 0x04 [Audio Input] wcaps 0x140311: Stereo Digital PCM: rates 0x160, bits 0x0e, types 0x5 Connection: 1 0x07 Node 0x05 [Audio Output] wcaps 0x40211: Stereo Digital PCM: rates 0x1e0, bits 0x0e, types 0x5 Node 0x06 [Audio Selector] wcaps 0x300901: Stereo Connection: 3 0x02 0x07* 0x14 Node 0x07 [Pin Complex] wcaps 0x430681: Stereo Digital Pincap 0x0810024: IN Pin Default 0x40c001f0: [N/A] SPDIF In at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Power: 0x0 Node 0x08 [Pin Complex] wcaps 0x400301: Stereo Digital Pincap 0x0810: OUT Pin Default 0x404001f0: [N/A] SPDIF Out at Ext N/A Conn = Unknown, Color = Unknown Pin-ctls: 0x00: Connection: 2 0x05* 0x14 Node 0x09 [Audio Selector] wcaps 0x30010d: Stereo Amp-Out Amp-Out caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=0 Amp-Out vals: [0x0f 0x0f] Connection: 1 0x0f Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x083f: IN OUT HP Pin Default 0x61813122: [N/A] Line In at Sep Rear Conn = 1/8, Color = Blue Pin-ctls: 0x00: Connection: 1 0x0e Node 0x0b [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN OUT Pin Default 0x02a11121: [Jack] Mic at Ext Front Conn = 1/8, Color = Black Pin-ctls: 0x20: IN Connection: 1 0x0e Node 0x0c [Pin Complex] wcaps 0x400181: Stereo Pincap 0x081737: IN
Re: [Alsa-user] Problems with snd hda intel: works only part of the time
Le Fri, 06 Oct 2006 13:35:43 +0200, "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > Dominique Michel wrote: > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > > The correct way to specify sound card order is to set 'index' options > > > in modprobe.conf (or whatever file is used). This works regardless of > > > the order in which the drivers are loaded. > > > > I know that, but it just don't work if udev load any sound driver as > > snd_usb_audio before at alsasound is started. > > Of course it does work. Driver modules get their module options from > modprobe.conf regardless of when or how they are loaded. > > > Regards, > Clemens > > - udev take its options from udev configuration files placed in /etc/udev/*. And not from modprobe.conf or whatever file is associated with modprobe. They just don't are the same programs and don't use the same configuration files. (man udev, man modprobe.conf) And again, if udev load at boot time some sound module, it will be the first sound card regardless of what is in modprobe.conf. When alsasound is started later in the boot procees and found a sound module allready loaded by udev, it will ignore it and do what it can to load the remaining drivers. If the allready loaded driver is not the first sound card in modprobe.conf, the final order of the sound card will be wrong according to modprobe.conf. Best, Dominique - 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.php&p=sourceforge&CID=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 Friday 06 October 2006 13:35, Clemens Ladisch wrote: > Dominique Michel wrote: > > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > > The correct way to specify sound card order is to set 'index' options > > > in modprobe.conf (or whatever file is used). This works regardless of > > > the order in which the drivers are loaded. > > > > I know that, but it just don't work if udev load any sound driver as > > snd_usb_audio before at alsasound is started. > > Of course it does work. Driver modules get their module options from > modprobe.conf regardless of when or how they are loaded. > > > Regards, > Clemens One problem I had, was to do with extra spaces at the end of option lines. It only happened once after updates from planetccrma. My sound card is index=0, and snd-usb-audio for my usb midi keyboard is index=1. After the updates snd-usb-audio was being loaded as card 0 again with consequently no sound from the actual soundcard which was being loaded as card 1. Fernando suggested that it might be to do with extra spaces after the options lines, and sure enough when I redid the 2 options lines being carefull to "enter" precisely at the end of each line, the problem was solved. It only happened once for me, but I did see it mentioned again on the planetccrma list. It may just have been a planetccrma problem, but I suppose it's good to bear in mind the importance of being carefull, and accurate when editing files. 2¢ worth. Nigel. > > - > 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.php&p=sourceforge&CID=DEVDEV > ___ > Alsa-user mailing list > Alsa-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user - 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.php&p=sourceforge&CID=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
Dominique Michel wrote: > "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > > The correct way to specify sound card order is to set 'index' options > > in modprobe.conf (or whatever file is used). This works regardless of > > the order in which the drivers are loaded. > > I know that, but it just don't work if udev load any sound driver as > snd_usb_audio before at alsasound is started. Of course it does work. Driver modules get their module options from modprobe.conf regardless of when or how they are loaded. 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.php&p=sourceforge&CID=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
Le Fri, 06 Oct 2006 11:26:50 +0200, "Clemens Ladisch" <[EMAIL PROTECTED]> a écrit : > Lee Revell wrote: > > On Thu, 2006-10-05 at 14:33 -0700, Bill Unruh wrote: > > > On Thu, 5 Oct 2006, Lee Revell wrote: > > > > 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... > > The correct way to specify sound card order is to set 'index' options > in modprobe.conf (or whatever file is used). This works regardless of > the order in which the drivers are loaded. > > > Regards, > Clemens > > I know that, but it just don't work if udev load any sound driver as snd_usb_audio before at alsasound is started. Dominique - 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.php&p=sourceforge&CID=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
Lee Revell wrote: > On Thu, 2006-10-05 at 14:33 -0700, Bill Unruh wrote: > > On Thu, 5 Oct 2006, Lee Revell wrote: > > > 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... The correct way to specify sound card order is to set 'index' options in modprobe.conf (or whatever file is used). This works regardless of the order in which the drivers are loaded. 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.php&p=sourceforge&CID=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
Le Thu, 05 Oct 2006 19:27:16 -0400, Lee Revell <[EMAIL PROTECTED]> a écrit : > 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 > > But my cables cannot switch without at I take a hand-light, go under the table and switch the cables by hand. I say that because many apps are not fixed, or can work with different ways. With the default option, or without option, most of the audio programs will use the first sound card they will find in the system and just don't care about the name of the device. If the first sound card is a webcam, they will use it. Even alsamixer will do that: -c Select the soundcard to use, if you have more than one. Cards are numbered from 0 (the default). We have to be practical. And it is so many options in a system at it is much more easier and faster to define the order of the sound cards in /etc/modules.d/alsa once for all and just use this order, even if it implies to have to blacklist the sound modules that will load before at alsasound load them. Dominique -- Dominique Michel - 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.php&p=sourceforge&CID=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 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.php&p=sourceforge&CID=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 ca
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.php&p=sourceforge&CID=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 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.php&p=sourceforge&CID=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+ >>>
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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=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 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.php&p=sourceforge&CID=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] Mes
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] > >>> Capabil
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.php&p=sourceforge&CID=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
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
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 [] > >
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.php&p=sourceforge&CID=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
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.php&p=sourceforge&CID=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]) > Su
