SB16 i386 Squeeze Scavenger hunt
Ah, the brave new world of separate firmware. These questions are based on ignorance on my part and google searches that turn up nothing or stuff that doesn't work. Stuff that Doesn't Work A web site reports to have sb16 firmware in a Redhat Package Manager .rpm package that it says will work on debian and a bunch of other distributions. Maybe it does, but alien bombs when trying to convert the .rpm in to a .deb. Stuff I Don't yet Understand. Lots of things, but specifically, my old lenny backups do have the kernel modules for SB16 cards. Basically, what is the best way to end up with workable firmware in the /lib/firmware/sb tree? Do the correct files exist somewhere in the old backup or do I need to do a make on a certain directory to produce compiled modules that can be copied in to /lib/firmware? Thank you. Martin McCormick -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201205091444.q49eikxh043...@x.it.okstate.edu
Re: SB16 i386 Squeeze Scavenger hunt
On Wed, 09 May 2012 09:44:46 -0500 Martin McCormick mar...@x.it.okstate.edu wrote: Ah, the brave new world of separate firmware. Stuff I Don't yet Understand. Lots of things, but specifically, my old lenny backups do have the kernel modules for SB16 cards. Basically, what is the best way to end up with workable firmware in the /lib/firmware/sb tree? Thank you. Martin McCormick I used to use the firmware from a Knoppix CD/DVD, if I couldn't find it easily elsewhere. -- keith km3...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120509161550.437206367e22298ea2e4f...@gmail.com
Re: SB16 Creative pnp desconfigura no boot
Em Fri, 27 Jul 2007 13:59:15 -0300 (BRT) [EMAIL PROTECTED] escreveu: Novamente alsaconf e tudo volta ao normal... depois do alsaconf digite alsamixer e ajute o que quiser, por último: alsactl store -- Sávio M Ramos Arquiteto, Rio, RJ Só uso Linux desde 2000 www.debian.org
SB16 Creative pnp desconfigura no boot
Fala galera! Tenho uma placa de som SB16 Creative Vi BRA16x pnp (é ISA e o chip é CTL1745) no meu Debian, consigo configurar via alsaconf sem problemas, mas toda vez que reinicio o Pc recebo a seguinte mensagem: Sound server informational message: Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory) The sound server will continue, using the null output device. Novamente alsaconf e tudo volta ao normal... Existe algum comandao para listar ISA? Já dei acesso ao usuário que utilizo no /dev/dsp...memos assim continua. Ah...depois do alsaconf tbm tenho que setar o dispositivo no Centro de Controle do KDE. Alguem sabe onde posso configurar isso de uma vez por todas? Valeu e aguardo, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE, aRts, Alsa und SB16 Vibra
Bischen späte Antwort, aber ich hattejetzt ewigkeiten auf mein neues Laptop gewartet... Am 2006-10-10 20:27:18, schrieb Evgeni Golov: On Tue, 10 Oct 2006 00:48:22 +0200 Michelle Konzack wrote: ich bin gerade dabei für einen Nachbarn einen kleinen Rechner (P2/350) als Workststion herzurichten und habe dazu KDE installiert. Will man da wirklich KDE? Naja, deine Sache. Für nen Anaenger besser als einen WM be dessen Konfig man sich ohne Vorkenntnisse nen Schuß git. cat /proc/asound/cards zeigt die Karte an? alsamixer auch? Dann hör auf veraltetes OSS zu nutzen (dsp == OSS), und sag aRTs es soll ALSA nutzen (oder nutz es direkt ohne aRTs). Da ist kein einziges OSS modul geladen. Hotplug hat nur rund 86 Module geladen zu denen auch die ALSA gehoeren. mpg321 -o alsa datei.mp3 oder mpg321 -o alsa09 datei.mp3 sollte aber jetzt schon gehen. Das einzige was funktioniert is den Sound ueber nen Sounddaemon auf mein Laptop redirekten. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: KDE, aRts, Alsa und SB16 Vibra
On Mon, 06 Nov 2006 12:52:10 +0100 Michelle Konzack wrote: Will man da wirklich KDE? Naja, deine Sache. Für nen Anaenger besser als einen WM be dessen Konfig man sich ohne Vorkenntnisse nen Schuß git. Lass ich mal unkommentiert ;-) cat /proc/asound/cards zeigt die Karte an? alsamixer auch? Dann hör auf veraltetes OSS zu nutzen (dsp == OSS), und sag aRTs es soll ALSA nutzen (oder nutz es direkt ohne aRTs). Da ist kein einziges OSS modul geladen. Hotplug hat nur rund 86 Module geladen zu denen auch die ALSA gehoeren. Du hast meine anderen Fragen nicht beantwortet. Wenn die ALSA Module geladen sind, wird dann eine Karte in /proc/asound/cards angezeigt? Wenn ja, lässt diese sich per alsamixer steuern? Das einzige was funktioniert is den Sound ueber nen Sounddaemon auf mein Laptop redirekten. Das willst du aber nicht. Wenn /p/a/cards keine Karte anzeigt, lass mal alsaconf laufen, evtl findet er eine Karte. Gruß Evgeni, sounddämonen nicht mögend
KDE, aRts, Alsa und SB16 Vibra
Hallo, ich bin gerade dabei für einen Nachbarn einen kleinen Rechner (P2/350) als Workststion herzurichten und habe dazu KDE installiert. Mittlerweile funktioniert alles mit Ausnahme des Sounds... Die Karte ist eine SB16 Vibra und alsacfg hat sie auch gefunden nur unter KDE habe ich das Problem, das kein dsp gefunden wird. Kann mir hier jemand weiterhelfen? Anm.: Ich kann per arts und rplay einwandfrei den Sound auf meine eigene Workstation über das Nertzwerk umleiten. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: KDE, aRts, Alsa und SB16 Vibra
On Tue, 10 Oct 2006 00:48:22 +0200 Michelle Konzack wrote: ich bin gerade dabei für einen Nachbarn einen kleinen Rechner (P2/350) als Workststion herzurichten und habe dazu KDE installiert. Will man da wirklich KDE? Naja, deine Sache. Mittlerweile funktioniert alles mit Ausnahme des Sounds... Die Karte ist eine SB16 Vibra und alsacfg hat sie auch gefunden nur unter KDE habe ich das Problem, das kein dsp gefunden wird. cat /proc/asound/cards zeigt die Karte an? alsamixer auch? Dann hör auf veraltetes OSS zu nutzen (dsp == OSS), und sag aRTs es soll ALSA nutzen (oder nutz es direkt ohne aRTs). mpg321 -o alsa datei.mp3 oder mpg321 -o alsa09 datei.mp3 sollte aber jetzt schon gehen. -- ^^^| Evgeni -SargentD- Golov ([EMAIL PROTECTED]) d(O_o)b | PGP-Key-ID: 0xAC15B50C -|- | WWW: http://www.die-welt.net ICQ: 54116744 / \| IRC: #sod @ irc.german-freakz.net
(solved) ISA sb16 problem
I have complained my sb16 does not work on sarge several times on the list. Now it is solved on my own! The problem is with isa-pnp module, it fails to assist sb module in detecting my card. The solution is to disable isa-pnp: isa-pnp isapnp_disable=1 sound uart401 sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with ISA SB16 sound card
Salut Serena, do you have tried to load the modules one by one? put following lines in your +---[ '/etc/modules' ]-- | | insmod soundcore | insmod sound | insmod sb_lib | insmod sb | insmod uart401 +--- sb maybe with your parameters... Greetings Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem with ISA SB16 sound card
The problem is with kernel configuration, I believe, because kernel 2.4 (self compiled, not bf24)in woody work well with my sb16. The commands below can load correctly in kernel 2.0, 2.2 and 2.4 in woody: modprobe sound insmod uart401 insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 but sarge complains: isapnp: Scanning for PnP cards... isapnp: SB audio device quirk - increasing port range isapnp: Card 'Creative SB16 PnP' isapnp: 1 Plug Play card detected total Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 sb: No ISAPnP cards found, trying standard ones... sb: dsp reset failed. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
my sb16 works with my *foolish* method
I have complain sb16 not working several times on the list, now I manage to solve it on my own, it works!!! The method is a little foolish, I'd like to seek your advice. Below is my foolish method: 1, compile 2.4.27, but unable to use newly-compiled kernel, (this is another question) 2,under stock kernel(2.4.27-2-386), use sb module compiled in the first step: modprobe sound insmod uart401 cd /lib/modules/2.4.27/kernel/drivers/sound insmod -f ./sb_lib.o insmod -f ./sb.o io=0x220 irq=5 dma=1 dma16=5 How to standard+ize the procedure? how to improve it? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: my sb16 works with my *foolish* method
On Sun, Mar 12, 2006 at 10:42:15PM -0800, Serena Cantor wrote: I have complain sb16 not working several times on the list, now I manage to solve it on my own, it works!!! The method is a little foolish, I'd like to seek your advice. Below is my foolish method: 1, compile 2.4.27, but unable to use newly-compiled kernel, (this is another question) 2,under stock kernel(2.4.27-2-386), use sb module compiled in the first step: modprobe sound insmod uart401 cd /lib/modules/2.4.27/kernel/drivers/sound insmod -f ./sb_lib.o insmod -f ./sb.o io=0x220 irq=5 dma=1 dma16=5 How to standard+ize the procedure? how to improve it? Hi Serena, I would guess you could post your /etc/modules I think they are 'insmod'd in order. Also, I think you can setup kernel module options in /etc/modules.conf Cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
problem with ISA SB16 sound card
sarge's default kernel can't use my SB16! I have used my SB16 ever since kernel 2.0, 2.2, and 2.4 in woody. They all work. But with sarge's kernel 2.4, it can't work. When I modprobe sb, it says: isapnp: Scanning for PnP cards... isapnp: SB audio device quirk - increasing port range isapnp: Card 'Creative SB16 PnP' isapnp: 1 Plug Play card detected total Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 sb: No ISAPnP cards found, trying standard ones... sb: dsp reset failed. What's the problem??? Thanks!!! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
question about sb16 module
I have woody and ISA non-PnP SB16 card, but the bf24 kernel of woody can't use it. It seems to me that bf24 try to use ISA PnP module before loading sb16 module. This is ridiculous, SB16 has both PnP and non-PnP versions! How can I remove such dependcy? I read depmod manual, edit /lib/modules/*/modules.dep, it does not work! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about sb16 module
On Wednesday 01 March 2006 05:16, [EMAIL PROTECTED] wrote: I have woody and ISA non-PnP SB16 card, but the bf24 kernel of woody can't use it. It seems to me that bf24 try to use ISA PnP module before loading sb16 module. This is ridiculous, SB16 has both PnP and non-PnP versions! Remember that with the non-PNP soundblaster, you have to specify the io address, interrupt, etc. -- Paul Johnson Email and IM (XMPP Google Talk): [EMAIL PROTECTED] Jabber: Because it's time to move forward http://ursine.ca/Ursine:Jabber -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about sb16 module
On Wed, Mar 01, 2006 at 12:23:06PM -0800, Paul Johnson wrote: On Wednesday 01 March 2006 05:16, [EMAIL PROTECTED] wrote: I have woody and ISA non-PnP SB16 card, but the bf24 kernel of woody can't use it. It seems to me that bf24 try to use ISA PnP module before loading sb16 module. This is ridiculous, SB16 has both PnP and non-PnP versions! Remember that with the non-PNP soundblaster, you have to specify the io address, interrupt, etc. Hi Paul, would sndconf (did I rememebr that utils name?) help? If he is using bf24 kernel, would it be useful to upgrade the kernel as the bf24 was the original boot floppies kernel? cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: question about sb16 module
On Wednesday 01 March 2006 14:36, Kevin Mark wrote: On Wed, Mar 01, 2006 at 12:23:06PM -0800, Paul Johnson wrote: On Wednesday 01 March 2006 05:16, [EMAIL PROTECTED] wrote: I have woody and ISA non-PnP SB16 card, but the bf24 kernel of woody can't use it. It seems to me that bf24 try to use ISA PnP module before loading sb16 module. This is ridiculous, SB16 has both PnP and non-PnP versions! Remember that with the non-PNP soundblaster, you have to specify the io address, interrupt, etc. Hi Paul, would sndconf (did I rememebr that utils name?) help? Not familiar with that. What I'm talking about is actually passing options to the kernel at the time the sb16 module gets inserted. You need io= irq= and one other argument (IIRC, it's been 10 years since I dealt with non-PnP hardware) to get the job done with that card. Though PCI is so common and a quality card like the SB Live 128 are as cheap as free if you look in the right places, and unlike the SB16, the Live 128 can play more than one sound at once. That might be a better long-term solution. -- Paul Johnson Email and IM (XMPP Google Talk): [EMAIL PROTECTED] Jabber: Because it's time to move forward http://ursine.ca/Ursine:Jabber -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: can't use default kernel's sb16 module
On Mon, 13 Feb 2006 22:21:43 -0800 (PST) Serena Cantor [EMAIL PROTECTED] wrote: I have SB16 and installed sarge, but can't make it play. autodetect does not do the magic It seems to me that my card is not PNP, but sarge first use a ISA-PNP module, which fails. Don't those developers know SB16 have both PNP and non-PNP version? does it show up in #dmesg? maybe the card is detected but the modules don't load? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Shawn Lamson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
can't use default kernel's sb16 module
I have SB16 and installed sarge, but can't make it play. autodetect does not do the magic It seems to me that my card is not PNP, but sarge first use a ISA-PNP module, which fails. Don't those developers know SB16 have both PNP and non-PNP version? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SB16 will nicht mit ALSA
Hi, Und noch eine Anmerkung: (sollte ich vielleicht einen neuen thread aufmachen): Ich kann das APM modul nicht laden ... no such device, ich möchte dass er sich beim poweroff eben ausschaltet. (Ein Win98 auf dem Rechner tut das). Any hints? Kernel gebacken ohne apm-support? Gruss Holger -- == Created with Sylpheed-Claws 0.9.12 under Debian GNU LINUX testing. http://counter.li.org/ Registered LinuxUser #311290 Spamfiltering powered by www.spamassassin.org =
SB16 will nicht mit ALSA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, ich habe ein kleines Problem mit einer SB16 (CT2230) in einem älteren Rechner. Wenn ich das OSS Modul sb.ko lade (mit irq=5 io=0x220 dma=1 dma16=5), dann geht alles wunderbar. Nun hätte ich aber gerne ALSA verwendet, also neugestartet/rmmod und versucht snd-sb16.ko zu laden (mit irq=5 port=0x220 dma8=1 dma16=5), aber er sagt immer, er habe keine Karte gefunden. - Ich versteh' das nicht, was mache ich falsch? System: Debian sarge, kernel 2.6.7 (debian quellen,neukompiliert, SMP aktiviert, als Proz: 586MMX). Es handelt sich um ein GA-586DX mit 2 Pentium 200MMX ... ;-) Kann es mit dem SMP Zeug zu tun haben? Aber warum geht dann OSS? ~ Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBNKpEZY86bR8HqNwRAl3EAJ4r8hULhOYUR6/v7O9PdRbC5uGHDQCgv3uj RZ0KhzAIn7SXqTOKk9vkAhU= =VMRY -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: SB16 will nicht mit ALSA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joachim Förster schrieb: | Kann es mit dem SMP Zeug zu tun haben? Aber warum geht dann OSS? So nun antworte ich mir mal selber ;-), also mit SMP hat es nichts zu tun. Ich hab das ganze mal mit dem 2.6.7-386 aus sarge probiert. Und noch eine Anmerkung: (sollte ich vielleicht einen neuen thread aufmachen): Ich kann das APM modul nicht laden ... no such device, ich möchte dass er sich beim poweroff eben ausschaltet. (Ein Win98 auf dem Rechner tut das). Any hints? ~ Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBNOMVZY86bR8HqNwRAtlPAKCwosN5GA8SsbeDmwoVfoqzPzXk0QCdGH/V sNUq/bJgE+1PH2uMS3cD3z4= =oA2Q -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: sb16
Tu es sur que c'est une vraie Sound Blaster. Beaucoup de cartes de cette époque était compatible sound blaster, par exemple les Opti930, mais elles ne marchent pas avec le pilot Sb. Bon courrage, Gonéri J'ai réinstallé en woody vanilla v 2.2.20 , elle fonctionne. - audio device: Sound Blaster 16 (4.12) (DUPLEX) - Midi device : Sound Blaster 16 - Mixers : Sound Blaster Je vais voir du côté de la liste ALSA pour le noyau 2.6.4 merci à tous
Re: sb16
On Sunday 04 April 2004 22:35, Delbos wrote: Jean-Luc Coulon (f5ibh) wrote: Le 04.04.2004 21:38, Frédéric Bothamy a écrit : * Delbos [EMAIL PROTECTED] [2004-04-04 20:49] : Bonsoir Penser à valider CONFIG_ISAPNP -- - Jean-Luc Soit le fichier Documentation/sound/alsa/ALSA-Configuration.txt d'une version du noyau Linux récente (2.6.x) ou encore dans le mini-guide Alsa (http://www.traduc.org/docs/HOWTO/vf/Alsa-sound.html) (et http://www.alsa-project.org/~valentyn/ en anglais). Il n'y est pas indiqué de problème particulier pour la détection des cartes SB16 PNP, mais il est possible de spécifier port pour spécifier l'adresse (et il y a d'autres options possible). On peut passer ces options lors du chargement du module avec modprobe (pour tester) ou automatiquement en utilisant un fichier dans /etc/modutils/ (noyau 2.4) ou /etc/modprobe.d/ (noyau 2.6) et update-modules. Merci à tous. modprobe - me répond inconnu au bataillon ! je vais voir ce qu'il me manque. CONFIG_ISAPNP - dmesg pas de cartes ISA Je vais tester la carte sous DOS Tu es sur que c'est une vraie Sound Blaster. Beaucoup de cartes de cette époque était compatible sound blaster, par exemple les Opti930, mais elles ne marchent pas avec le pilot Sb. Bon courrage, Gonéri
sb16
Bonsoir, J'ai une vieille SB16 (PNP sous winxxx) mais qui à une adresse IO=220 Hors pour des problèmes de compatibilité (si j'ai bien compris), ALSA ne cherche pas dans ce registre d'adresses. Donc pas de son en 2.6.4-1 Une piste pour la déclarer ? Merci à tous PS malgré les TROLLS que je ne comprends généralement pas, je suis très impressioné par la réactivité et la disponibilité de certains spécialistes (moi y'en a débutant!!!)
Re: sb16
4 avril 2004, 21:06 :Delbos wrote: Bonsoir, Bonsoir J'ai une vieille SB16 (PNP sous winxxx) mais qui une adresse IO=220 Hors pour des problmes de compatibilit (si j'ai bien compris), ALSA ne cherche pas dans ce registre d'adresses. Donc pas de son en 2.6.4-1 Une piste pour la dclarer ? Regarde sur (attention, adresse un poil longue) : http://www.alsa-project.org/alsa-doc/doc-php/template.php?company=Creative+Labscard=Soundblaster+16chip=sb16module=sb16 A la fin de la page y'a peut tre 2/3 trucs qui pourront t'aider, notamment les : options snd-sb16 index=0 id=SB-16 port=0x220 ... Merci tous De rien PS malgr les TROLLS que je ne comprends gnralement pas, je suis trs impression par la ractivit et la disponibilit de certains spcialistes (moi y'en a dbutant!!!) Y'en a qui passent leur journe accrochs leur client mail, sisi :) -- Lucas
Re: sb16
* Delbos [EMAIL PROTECTED] [2004-04-04 20:49] : Bonsoir, J'ai une vieille SB16 (PNP sous winxxx) mais qui à une adresse IO=220 Hors pour des problèmes de compatibilité (si j'ai bien compris), ALSA ne cherche pas dans ce registre d'adresses. Donc pas de son en 2.6.4-1 Une piste pour la déclarer ? Soit le fichier Documentation/sound/alsa/ALSA-Configuration.txt d'une version du noyau Linux récente (2.6.x) ou encore dans le mini-guide Alsa (http://www.traduc.org/docs/HOWTO/vf/Alsa-sound.html) (et http://www.alsa-project.org/~valentyn/ en anglais). Il n'y est pas indiqué de problème particulier pour la détection des cartes SB16 PNP, mais il est possible de spécifier port pour spécifier l'adresse (et il y a d'autres options possible). On peut passer ces options lors du chargement du module avec modprobe (pour tester) ou automatiquement en utilisant un fichier dans /etc/modutils/ (noyau 2.4) ou /etc/modprobe.d/ (noyau 2.6) et update-modules. Fred -- Comment poser les questions de manière intelligente ? http://www.gnurou.org/documents/smart-questions-fr.html Code de conduite des listes Debian http://www.debian.org/MailingLists/#codeofconduct
Re : sb16
Le 04.04.2004 21:38, Frédéric Bothamy a écrit : * Delbos [EMAIL PROTECTED] [2004-04-04 20:49] : Bonsoir, J'ai une vieille SB16 (PNP sous winxxx) mais qui à une adresse IO=220 Hors pour des problèmes de compatibilité (si j'ai bien compris), ALSA ne cherche pas dans ce registre d'adresses. Donc pas de son en 2.6.4-1 Une piste pour la déclarer ? Penser à valider CONFIG_ISAPNP -- - Jean-Luc Soit le fichier Documentation/sound/alsa/ALSA-Configuration.txt d'une version du noyau Linux récente (2.6.x) ou encore dans le mini-guide Alsa (http://www.traduc.org/docs/HOWTO/vf/Alsa-sound.html) (et http://www.alsa-project.org/~valentyn/ en anglais). Il n'y est pas indiqué de problème particulier pour la détection des cartes SB16 PNP, mais il est possible de spécifier port pour spécifier l'adresse (et il y a d'autres options possible). On peut passer ces options lors du chargement du module avec modprobe (pour tester) ou automatiquement en utilisant un fichier dans /etc/modutils/ (noyau 2.4) ou /etc/modprobe.d/ (noyau 2.6) et update-modules. Fred pgpYT5yslyq07.pgp Description: PGP signature
Re: Re : sb16
Jean-Luc Coulon (f5ibh) wrote: Le 04.04.2004 21:38, Frédéric Bothamy a écrit : * Delbos [EMAIL PROTECTED] [2004-04-04 20:49] : Bonsoir Penser à valider CONFIG_ISAPNP -- - Jean-Luc Soit le fichier Documentation/sound/alsa/ALSA-Configuration.txt d'une version du noyau Linux récente (2.6.x) ou encore dans le mini-guide Alsa (http://www.traduc.org/docs/HOWTO/vf/Alsa-sound.html) (et http://www.alsa-project.org/~valentyn/ en anglais). Il n'y est pas indiqué de problème particulier pour la détection des cartes SB16 PNP, mais il est possible de spécifier port pour spécifier l'adresse (et il y a d'autres options possible). On peut passer ces options lors du chargement du module avec modprobe (pour tester) ou automatiquement en utilisant un fichier dans /etc/modutils/ (noyau 2.4) ou /etc/modprobe.d/ (noyau 2.6) et update-modules. Merci à tous. modprobe - me répond inconnu au bataillon ! je vais voir ce qu'il me manque. CONFIG_ISAPNP - dmesg pas de cartes ISA Je vais tester la carte sous DOS
Re: kernel 2.6.2 ALSA config sb16
On Mon, Mar 01, 2004 at 05:04:04PM -0600, Lance Hoffmeyer wrote: Hello, I have been trying to setup kernel-2.6.2 with ALSA support for a SB 16 PNP. I keep getting the error modprobe snd-sb16 Sound Blaster 16 soundcard not found or device busy That an ISA PNP card? Have you enabled ISA PNP support? It's an experimental option in 2.6, so you have to turn on experimental options before you can see it. -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F pgp0.pgp Description: PGP signature
kernel 2.6.2 ALSA config sb16
Hello, I have been trying to setup kernel-2.6.2 with ALSA support for a SB 16 PNP. I keep getting the error modprobe snd-sb16 Sound Blaster 16 soundcard not found or device busy In case, if you have AWE card, try snd-sbawe module FATAL: Error inserting snd_sb16 (/lib/modules/2.6.2/kernel/sound/isa/sb/snd-sb16.ko): No such device I have the kernel compiled with sb16(M) and ice1712(M). using libasound2. here is my /etc/alsa/modutils/1.0 file: ### DEBCONF MAGIC # This file was automatically generated by alsa-base's debconf stuff alias char-major-116 snd alias char-major-14 soundcore options snd major=116 cards_limit=4 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/dsp* snd-pcm-oss alias snd-card-0 snd-ice1712 alias snd-card-1 snd-sb16 # I added this based on WinXP dual-boot: IRQ=5, DMA=1,5 I/O=0220,0330,0388 options snd-sb16 port=0x220 mpu_port=0x330 irq=5 dma8=1 dma16=-1 alias snd-slot-0 snd-card-0 alias sound-slot-0 snd-slot-0 alias snd-slot-1 snd-card-1 alias sound-slot-1 snd-slot-1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.6.2 ALSA config sb16
On Monday 01 March 2004 23:04, Lance Hoffmeyer wrote: Hello, I have been trying to setup kernel-2.6.2 with ALSA support for a SB 16 PNP. I keep getting the error modprobe snd-sb16 Sound Blaster 16 soundcard not found or device busy In case, if you have AWE card, try snd-sbawe module FATAL: Error inserting snd_sb16 (/lib/modules/2.6.2/kernel/sound/isa/sb/snd-sb16.ko): No such device alias snd-card-0 snd-ice1712 alias snd-card-1 snd-sb16 Have you tried without snd-ice1712 and making the sb16 snd-card-0? # I added this based on WinXP dual-boot: IRQ=5, DMA=1,5 I/O=0220,0330,0388 options snd-sb16 port=0x220 mpu_port=0x330 irq=5 dma8=1 dma16=-1 What happens if you leave teh above line out? Also, as a thought, do you have discover installed? It attempts to scan for the sound cards and installs non alsa ones. (you can check with an lsmod, you can prevent it by editing /etc/dicover.conf) -- Alan Chandler [EMAIL PROTECTED] First they ignore you, then they laugh at you, then they fight you, then you win. --Gandhi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Em Seg, 2004-01-26 às 05:52, Douglas A. Augusto escreveu: Isso nao deve ser mesmo, pois minha placa de som e pra la de vagabunda! Hmmm... não sei não. Qual é sua placa? Esta e a saida do lspci -vv: 00:08.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev 12) Subsystem: Hewlett-Packard Company: Unknown device 0012 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (500ns min, 6000ns max) Interrupt: pin A routed to IRQ 5 Region 0: I/O ports at 1400 [size=256] Capabilities: available only to root 00:08.1 Communication controller: ESS Technology ESS Modem (rev 12) Subsystem: Hewlett-Packard Company: Unknown device 0012 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Interrupt: pin A routed to IRQ 5 Region 0: I/O ports at 1800 [size=256] Capabilities: available only to root Note que ela e conjunta com o modem, que nao funciona em gnu/linux. Alias esta historia do modem e a mais cabeluda que ja vi[1]: Um dia eu capturei uma mensagem de um tal de All Stone, funcionario da HP francesa, que estava ajudando a mandrake. Nesta mensagem constava um binario para este conjunto de som/modem da ESS compilado para o kernel 2.4.18 da mandrake, que tinha o sufixo -6mdk. ENtao tentei por o modem pra funcionar e nao rolou porque o modulo exigia o kernel da mandrake. ENtao eu gerei uma compilacao do kernel com o tal sufixo -6mdk e instalei, e o FDP do modulo funcionou MAs ai eu cai na besteira de pedir os fontes do modulo e todo mundo fingiu que ele nunca existiu, de forma que algumas pessoas ate acham que eu inventei essa historia. TEnho ainda os binarios aqui, se alguem quiser fazer engenharia reversa ... De minha parte, jurei NUNCA mais comprar nada que venha o hardware da ESS, e todo funcionario da HP ligado ao SL que encontro eu toco no assunto falando tipo qual e a da hp, ta do lado do SL ou nao??? Na verdade não é bem o que eu disse antes, depende do hardware sim. A questão sobre o 'non-blocking' refere-se ao modo de como o aplicativo agirá caso não possa tocar o som simultaneamente, pode tanto esperar numa fila (padrão) como retornar um erro de dispositivo ocupado. A sua placa deve ser capaz de processar mais de um canal por vez, assim como a minha (SB Live!). Já a do meu irmão (via82xx), só se houver uma camada de software para fazer a mixagem (dmix). Isso eu nao sei, pois nao saco disso. Se voce conseguir identificar algo... [1] http://lists.debian.org/debian-user-portuguese/2002/debian-user-portuguese-200208/msg00185.html []'s -- Outgoing mail is certified Windows Free. Checked by Debian GNU/Linux http://www.debian.org. free your computer and your soul will follow... signature.asc Description: Esta é uma parte de mensagem assinada digitalmente
Re: [longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Em Sex, 2004-01-23 às 11:11, Douglas A. Augusto escreveu: No dia 23/01/2004 às 09:54, Marcio de Araujo Benedito [EMAIL PROTECTED] escreveu: Bao, eu tenho aki o 2.6.0 com o alsa para rodar a minha ess-maestro-3, e os sons sao tocados simultaneamente sim! Hoje mesmo tomei um sisto quando estava a ouvir uma musica usando o xmms e comecou uma falacao no meio da musica. Era um site com umsa saudacao de voz na abertura... Hmmm... o que dá a saída: 'dpkg -l | grep alsa' ? Além disso está certo que não tem nenhum servidor de som rodando não, tipo 'esd', 'arts'? localhost:~# dpkg -l | grep alsa ii alsa-base 1.0.1-1ALSA sound driver common files ii alsa-headers 1.0.1-1ALSA sound driver header files ii alsa-oss 0.9.8-1Advanced Linux Sound Architecture (OSS compa ii alsa-utils 0.9.8-1Advanced Linux Sound Architecture (utils) ii alsaconf 0.9.8-3ALSA configuration generator ii alsamixergui 0.9.0rc2-1-4 graphical soundcard mixer for ALSA soundcard ii alsaplayer 0.99.75-6 PCM player designed for ALSA ii alsaplayer-als 0.99.75-6 PCM player designed for ALSA (ALSA output mo ii alsaplayer-com 0.99.75-6 PCM player designed for ALSA (common files) ii alsaplayer-esd 0.99.75-6 PCM player designed for ALSA (ESD output mod ii alsaplayer-gtk 0.99.75-6 PCM player designed for ALSA (GTK version) ii alsaplayer-jac 0.99.75-6 PCM player designed for ALSA (jack output mo ii alsaplayer-nas 0.99.75-6 PCM player designed for ALSA (NAS output mod ii alsaplayer-oss 0.99.75-6 PCM player designed for ALSA (OSS output mod ii gnome-alsamixe 0.9.6-1ALSA sound mixer for GNOME ii gstreamer-alsa 0.6.4-2ALSA plugin for GStreamer ii snd-gtk-alsa 6.10-4 Sound file editor (GTK+ user interface) localhost:~# ps ax | grep esd 7856 pts/0S 0:00 grep esd localhost:~# ps ax | grep arts 8476 pts/0R 0:00 grep arts localhost:~# Cheguei a cogitar que dependia do hardware (isto é, a placa deveria ser capaz de fazer o mixer por si só), mas a explicação no FAQ foi bem enfática, reafirmando que agora o uso de filas é padrão. Isso nao deve ser mesmo, pois minha placa de som e pra la de vagabunda! Outra possibilidade do seu som estar saindo simultaneamente é se os aplicativos já estiverem em acordo com o alsa1x. Mas a versão que testei era a última, a mais recente até ontem, por isso não acredito nessa hipótese. Como disse, nao fiz nada de especial. Antes de compor esta mensagem fiz questao de testar: rodei uma musica no XMMS e mandei na linha de comando o mplayer tocar um audio em wma contendo a narracao do jogo em que o Galo venceu a selecao brasileira em 1969 e pus o fone de ouvido: ouvi os dois arquivos ao mesmo tempo!!! []'s -- Outgoing mail is certified Windows Free. Checked by Debian GNU/Linux http://www.debian.org. free your computer and your soul will follow... signature.asc Description: Esta é uma parte de mensagem assinada digitalmente
Re: [longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 26/01/2004 às 10:00, Marcio de Araujo Benedito [EMAIL PROTECTED] escreveu: Cheguei a cogitar que dependia do hardware (isto é, a placa deveria ser capaz de fazer o mixer por si só), mas a explicação no FAQ foi bem enfática, reafirmando que agora o uso de filas é padrão. Isso nao deve ser mesmo, pois minha placa de som e pra la de vagabunda! Hmmm... não sei não. Qual é sua placa? Na verdade não é bem o que eu disse antes, depende do hardware sim. A questão sobre o 'non-blocking' refere-se ao modo de como o aplicativo agirá caso não possa tocar o som simultaneamente, pode tanto esperar numa fila (padrão) como retornar um erro de dispositivo ocupado. A sua placa deve ser capaz de processar mais de um canal por vez, assim como a minha (SB Live!). Já a do meu irmão (via82xx), só se houver uma camada de software para fazer a mixagem (dmix). -- Douglas Augusto [Netiqueta] § Evitar escrever em maiúsculas, use *palavra* para o negrito e _palavra_ para sublinhar.
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 24/01/2004 às 00:17, FaRaOhh [EMAIL PROTECTED] escreveu: Depois de algum tempo tentando e seguindo as dicas, compilei o alsa como módulo e agora uso ele ao invés do OSS, notei a melhora considerável na execusão dos meus aplicativos sonoros. :-) Aproveitei para fazer o teste de sons simultaneo e comigo não funcionou, tenho a mesma opinião do Douglas com respeito ao tocar sons simultaneos. Qual sua placa de som? O que acontece se executar simultaneamente dois wavs, usando 'aplay -N arquivo.wav' (ao mesmo tempo)?. -- Douglas Augusto [Netiqueta] § A assinatura deve ser separada do corpo de e-mail por -- (sigdashes), isto é, (nova-linha)(traço)(traço)(espaço)(nova-linha).
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Em Sáb, 2004-01-24 às 07:36, Douglas A. Augusto escreveu: No dia 24/01/2004 às 00:17, FaRaOhh [EMAIL PROTECTED] escreveu: Depois de algum tempo tentando e seguindo as dicas, compilei o alsa como módulo e agora uso ele ao invés do OSS, notei a melhora considerável na execusão dos meus aplicativos sonoros. :-) Aproveitei para fazer o teste de sons simultaneo e comigo não funcionou, tenho a mesma opinião do Douglas com respeito ao tocar sons simultaneos. Qual sua placa de som? O que acontece se executar simultaneamente dois wavs, usando 'aplay -N arquivo.wav' (ao mesmo tempo)?. ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy aplay: main:503: audio open error: Device or resource busy -- Marcello Henrique - FaRaOhh Debian User:629 - #livres (irc.freenode.org) Projeto Livres: Por um mundo mais humano. As leis físicas que nos chamam à razão são as mesmas que nos conduzem para Deus (Tia Neiva)
[longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 03/08/2003 às 14:58, Leandro A. F. Pereira [EMAIL PROTECTED] escreveu: Tenho uma AWE32, ISA PnP. Funciona legal o ALSA no Linux 2.6.0-test2, tanto PCM quanto sequencer. Só tem duas coisas que estão quase me fazendo voltar para o bom e velho OSS: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmeros Uh-Oh em seqüência. Leandro, sou obrigado a reabrir este thread porque na minha resposta eu dizia que a arquitetura ALSA permitia de forma automática a execução de sons simultâneos. De fato estava certo, mas acredito que a partir da versão 1.0, o ALSA passou a seguir um novo modelo, que está sendo considerado padrão (não só pelo ALSA, mas os drivers mais novos de placa de som, etc). Descobri isso quando instalei o quérnel 2.6.0 (alsa 1.x) na máquina do meu irmão, e fiquei surpreso (decepcionado?) com a impossibilidade de tocar sons simultaneamente. A minha máquina ainda continua com o alsa antigo (quérnel 2.4 e ALSA 0.9.8) e consegue trabalhar perfeitamente com sons executados ao mesmo tempo. Este fato me intrigou, até quando achei um FAQ em '/usr/share/doc/alsa' dizendo exatamente sobre isso: Q: When I play something and I try to play something other the second attempt will not fail but instead it hangs waiting for the completion of the first sound. A: This is definitely the standard behaviour as described in many official documents that now ALSA follows. There is no reasons to complain about that for the following reasons: - it's the right (standard) way - the application that want a different behaviour can open the device in O_NONBLOCK mode - all modern OSS drivers in mainstream kernel (cmpci, es1370, es1371, esssolo1, maestro, sonicvibes, vwsnd) works in the same ways and the others have to be intended buggy - we want you ask to broken applications author to fix them ;-) O que entendi é que ainda é possível ter esta característica em funcionamento, mas isto agora fica a cargo dos desenvolvedores, podendo optar em abrir o dispositivo de som de forma exclusiva ou não (NONBLOCKING, do tipo open(/dev/dsp, O_RDONLY|O_NONBLOCK)). Por exemplo, já existe um patch para o mplayer (saída ALSA) que permite o usuário especificar o modo de abertura do dispositivo - por exemplo, especificando na linha de comando: mplayer -ao alsa1x:noblock. Mas ainda estou bastante confuso sobre isto, alguns pontos são: 1 - a possibilidade de gerenciar sons simultâneos, além de contar com o desenvolver, precisa que o *hardware* seja capaz de executá-lo, ou o mixer (merge) pode ser feito via software (ALSA) e então entregue à placa de som? 2 - como é de fato esta relação de exclusividade?!? Isto é, duas ou mais aplicações podem disparar sons ao mesmo tempo se e somente se estas abriram o dispositivo com a máscara O_NONBLOCK? 3 - qual a justificativa para a adoção deste novo padrão? - É lento! Lento! Lento! Um DivX que tocava normalmente com OSS, fica lerdão com o ALSA. Se desligar o som, fica perfeito. Se uso somente OSS (sem emulação do ALSA), fica melhor ainda. Pois é, na máquina do meu irmão (Duron 1GHz, 380MB RAM, via68xx), o som ALSA + quérnel 2.6.0 pipocava com uma freqüência razoável. Bastava por exemplo um uso mais intenso no HD (tipo uma descompactação de pacotes) e o som literalmente parava. Nem mesmo um 'renice -19' na aplicação de som conseguia elimitar este incômodo. Não cheguei a fazer uma comparação mais precisa com o quérnel 2.4.X, mas das vezes que rodei o Kurumin nesta máquina não cheguei a notar este pipocamento. -- Douglas Augusto [Netiqueta] § Evitar e-mails HTML, mesmo oferecendo alternativa puramente textual.
Re: [longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Em Qui, 2004-01-22 às 23:43, Douglas A. Augusto escreveu: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmeros Uh-Oh em seqüência. Leandro, sou obrigado a reabrir este thread porque na minha resposta eu dizia que a arquitetura ALSA permitia de forma automática a execução de sons simultâneos. De fato estava certo, mas acredito que a partir da versão 1.0, o ALSA passou a seguir um novo modelo, que está sendo considerado padrão (não só pelo ALSA, mas os drivers mais novos de placa de som, etc). Descobri isso quando instalei o quérnel 2.6.0 (alsa 1.x) na máquina do meu irmão, e fiquei surpreso (decepcionado?) com a impossibilidade de tocar sons simultaneamente. A minha máquina ainda continua com o alsa antigo (quérnel 2.4 e ALSA 0.9.8) e consegue trabalhar perfeitamente com sons executados ao mesmo tempo. Bao, eu tenho aki o 2.6.0 com o alsa para rodar a minha ess-maestro-3, e os sons sao tocados simultaneamente sim! Hoje mesmo tomei um sisto quando estava a ouvir uma musica usando o xmms e comecou uma falacao no meio da musica. Era um site com umsa saudacao de voz na abertura... OBS: Nao fiz nada de especial na compilacao do kernel! -- Outgoing mail is certified Windows Free. Checked by Debian GNU/Linux http://www.debian.org. free your computer and your soul will follow... signature.asc Description: Esta é uma parte de mensagem assinada digitalmente
Re: [longo] Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 23/01/2004 às 09:54, Marcio de Araujo Benedito [EMAIL PROTECTED] escreveu: Bao, eu tenho aki o 2.6.0 com o alsa para rodar a minha ess-maestro-3, e os sons sao tocados simultaneamente sim! Hoje mesmo tomei um sisto quando estava a ouvir uma musica usando o xmms e comecou uma falacao no meio da musica. Era um site com umsa saudacao de voz na abertura... Hmmm... o que dá a saída: 'dpkg -l | grep alsa' ? Além disso está certo que não tem nenhum servidor de som rodando não, tipo 'esd', 'arts'? Cheguei a cogitar que dependia do hardware (isto é, a placa deveria ser capaz de fazer o mixer por si só), mas a explicação no FAQ foi bem enfática, reafirmando que agora o uso de filas é padrão. Outra possibilidade do seu som estar saindo simultaneamente é se os aplicativos já estiverem em acordo com o alsa1x. Mas a versão que testei era a última, a mais recente até ontem, por isso não acredito nessa hipótese. -- Douglas Augusto [Netiqueta] § Assuntos fora do perfil da lista deveriam ser evitados e, quando ocorrer, vir marcados com [off-topic] ou [OT].
Re: Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Em Sex, 2004-01-23 às 17:54, Marcio de Araujo Benedito escreveu: Em Qui, 2004-01-22 às 23:43, Douglas A. Augusto escreveu: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmeros Uh-Oh em seqüência. Leandro, sou obrigado a reabrir este thread porque na minha resposta eu dizia que a arquitetura ALSA permitia de forma automática a execução de sons simultâneos. De fato estava certo, mas acredito que a partir da versão 1.0, o ALSA passou a seguir um novo modelo, que está sendo considerado padrão (não só pelo ALSA, mas os drivers mais novos de placa de som, etc). Descobri isso quando instalei o quérnel 2.6.0 (alsa 1.x) na máquina do meu irmão, e fiquei surpreso (decepcionado?) com a impossibilidade de tocar sons simultaneamente. A minha máquina ainda continua com o alsa antigo (quérnel 2.4 e ALSA 0.9.8) e consegue trabalhar perfeitamente com sons executados ao mesmo tempo. Bao, eu tenho aki o 2.6.0 com o alsa para rodar a minha ess-maestro-3, e os sons sao tocados simultaneamente sim! Hoje mesmo tomei um sisto quando estava a ouvir uma musica usando o xmms e comecou uma falacao no meio da musica. Era um site com umsa saudacao de voz na abertura... OBS: Nao fiz nada de especial na compilacao do kernel! Depois de algum tempo tentando e seguindo as dicas, compilei o alsa como módulo e agora uso ele ao invés do OSS, notei a melhora considerável na execusão dos meus aplicativos sonoros. :-) Aproveitei para fazer o teste de sons simultaneo e comigo não funcionou, tenho a mesma opinião do Douglas com respeito ao tocar sons simultaneos. Uso alsa-base 1.0.1-1, com o módulo intel8x0 -- Marcello Henrique - FaRaOhh Debian User:629 - #livres (irc.freenode.org) Projeto Livres: Por um mundo mais humano. As leis físicas que nos chamam à razão são as mesmas que nos conduzem para Deus (Tia Neiva)
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 24/01/2004 às 00:17, FaRaOhh [EMAIL PROTECTED] escreveu: Depois de algum tempo tentando e seguindo as dicas, compilei o alsa como módulo e agora uso ele ao invés do OSS, notei a melhora considerável na execusão dos meus aplicativos sonoros. :-) Aproveitei para fazer o teste de sons simultaneo e comigo não funcionou, tenho a mesma opinião do Douglas com respeito ao tocar sons simultaneos. Uso alsa-base 1.0.1-1, com o módulo intel8x0 E mais uma coisa, aquela opção non-block do ALSA é furada. Descobri que o alsaplay (aplay) tem a opção '-N' que é para abrir o dispositivo de modo não exclusivo. Fiz o teste, o resultado é que em vez de colocar o som em uma fila, ele diz que o dispositivo está ocupado, mesmo com a opção '-N' nos dois sons simultâneos. Uma conclusão é certa: o ALSA não trabalha com a mixagem via software. Pode ser que o som simultâneo (através do non-blocking) funcione com uma placa de som capaz de tal. A placa testada é simples, uma onboard via82xx da placa-mãe K7 VTA-Pro. -- Douglas Augusto [Netiqueta] § Prover ao tópico um assunto claro, descritivo e não genérico.
Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Quoted by a bunch of holy chickens For `Junior [EMAIL PROTECTED]' On Sunday, 27 July 2003 (23:28): Problema resolvido. Eu compilei como módulo o suporte ao sb via OSS, como fazia no antigo 2.4.x. Acho que eu estava fazendo baianada no novo modutils e ele não achava os módulos. :) Agora e' so' esperar para usar o novo driver da alsa, talvez ele sim possua alguns bugs. Tenho uma AWE32, ISA PnP. Funciona legal o ALSA no Linux 2.6.0-test2, tanto PCM quanto sequencer. Só tem duas coisas que estão quase me fazendo voltar para o bom e velho OSS: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmeros Uh-Oh em seqüência. - É lento! Lento! Lento! Um DivX que tocava normalmente com OSS, fica lerdão com o ALSA. Se desligar o som, fica perfeito. Se uso somente OSS (sem emulação do ALSA), fica melhor ainda. A única coisa que está me segurando para voltar ao OSS é o driver para a AWE (OSS) do 2.6.0 não está compilando. E o 2.4.x é muito instável na minha máquina... :/ -- Leandro Pereira (oO) [EMAIL PROTECTED] /||\ www.mindcrisis.tk glommer cartão perfurado orientado a objetos, imagina ? UdontKnow cartao eh objeto, ora
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 03/08/2003 às 14:58, Leandro A. F. Pereira [EMAIL PROTECTED] escreveu: Tenho uma AWE32, ISA PnP. Funciona legal o ALSA no Linux 2.6.0-test2, tanto PCM quanto sequencer. Só tem duas coisas que estão quase me fazendo voltar para o bom e velho OSS: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmeros Uh-Oh em seqüência. - É lento! Lento! Lento! Um DivX que tocava normalmente com OSS, fica lerdão com o ALSA. Se desligar o som, fica perfeito. Se uso somente OSS (sem emulação do ALSA), fica melhor ainda. Tem alguma coisa errada aí, e certamente não é com a arquitetura ALSA. Eu a uso já faz um bom tempo e só obtive melhorias. Mas estou com o kernel 2.4.20. Alguma configuração para tocar sons sequencialmente? Comigo posso ouvir mp3, divx e licq tudo ao mesmo tempo, sem problema algum. -- Douglas Augusto
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
On Sun, Aug 03, 2003 at 06:46:11PM -0300, Douglas A. Augusto wrote: | Tem alguma coisa errada aí, e certamente não é com a arquitetura ALSA. Eu a uso | já faz um bom tempo e só obtive melhorias. Mas estou com o kernel 2.4.20. | Alguma configuração para tocar sons sequencialmente? Comigo posso ouvir mp3, | divx e licq tudo ao mesmo tempo, sem problema algum. Uso uma sb16 ISA, e no Windows 2000 eu podia ouvir MP3, ouvir o som do ICQ, enfim, ela ficava multitarefa :-) Há alguma de ativar isso no linux? Se nao me engano, esse recurso se chama full duplex, nao tenho certeza. Será que os famosos sound daemons fazem isso? Obrigado. -- Junior - [EMAIL PROTECTED] http://jxz.dontexist.org/ pgpfFLL0ogVfw.pgp Description: PGP signature
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
No dia 03/08/2003 às 19:39, Junior [EMAIL PROTECTED] escreveu: Uso uma sb16 ISA, e no Windows 2000 eu podia ouvir MP3, ouvir o som do ICQ, enfim, ela ficava multitarefa :-) Há alguma de ativar isso no linux? Se nao me engano, esse recurso se chama full duplex, nao tenho certeza. Full duplex é quando é possível gravar e reproduzir ao mesmo tempo. Mas não está relacionado com múltiplas reproduções simultâneas. E o full duplex é mais 'hardware', ou seja, a placa tem que suportar. Já o tocar simultâneo é mais uma questão de software, o driver de som tem que mesclar as origens e enviá-las ao hardware. A ativação deste recurso geralmente é transparente ao usuário. Por padrão o driver ALSA faz assim. Sua placa foi reconhecida corretamente? Será que os famosos sound daemons fazem isso? O que chama de 'sound daemon' exatamente? Já havia tentado o ALSA sobre o kernel 2.4.x? -- Douglas Augusto
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Eu sempre usei o modulo sb do OSS. Nunca testei o ALSA. Vou dar uma olhada nisso, obrigado. On Sun, Aug 03, 2003 at 08:35:36PM -0300, Douglas A. Augusto wrote: | Já havia tentado o ALSA sobre o kernel 2.4.x? -- Junior - [EMAIL PROTECTED] http://jxz.dontexist.org/ pgpxiCZKbm6TG.pgp Description: PGP signature
Re: Bugs do Alsa (era: [off-topic] sb16 em 2.6.0-test2)
Sei lá em Leandro. Eu tinha um CMI8736 onboard que funcionava de maneira horrivel com o OSS, começei a usar ALSA, e blz, tanto que hj tenho uma Live... Acho que isso é algum problema relacionado diretamente ao kernel, pq utilizo o ALSA aqui numa boa, e acho muitas vezes melhor que o OSS original... Quando a tocar no xmms e outros sons ficarem a espera, utilize um daemon de som como o ESD ou o ArtsD On Sun, 3 Aug 2003 14:58:07 -0300 Leandro A. F. Pereira [EMAIL PROTECTED] wrote: Quoted by a bunch of holy chickens For `Junior [EMAIL PROTECTED]' On Sunday, 27 July 2003 (23:28): Problema resolvido. Eu compilei como módulo o suporte ao sb via OSS, como fazia no antigo 2.4.x. Acho que eu estava fazendo baianada no novo modutils e ele não achava os módulos. :) Agora e' so' esperar para usar o novo driver da alsa, talvez ele sim possua alguns bugs. Tenho uma AWE32, ISA PnP. Funciona legal o ALSA no Linux 2.6.0-test2, tanto PCM quanto sequencer. Só tem duas coisas que estão quase me fazendo voltar para o bom e velho OSS: - Se o dispositivo de som está sendo utilizado, o ALSA deixa outros processos usá-lo normalmente -- parece que coloca tudo numa fila, e quando ele é liberado, tudo que estava nessa fila é tocado. Por exemplo, se estou com o xmms e o licq aberto, tocando uma MP3, e chega alguma mensagem no ICQ, eu não ouço o Uh-Oh. É só fechar o xmms ou parar a música e ouço o som. Às vezes ouço inúmerosUh-Oh em seqüência. - É lento! Lento! Lento! Um DivX que tocava normalmente com OSS, fica lerdão com o ALSA. Se desligar o som, fica perfeito. Se uso somente OSS (sem emulação do ALSA), fica melhor ainda. A única coisa que está me segurando para voltar ao OSS é o driver para a AWE (OSS) do 2.6.0 não está compilando. E o 2.4.x é muito instável na minha máquina... :/ -- Leandro Pereira (oO) [EMAIL PROTECTED] /||\ www.mindcrisis.tk glommer cartão perfurado orientado a objetos, imagina ? UdontKnow cartao eh objeto, ora -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- André Filipe de Assunção e Brito decko em #debian-br @ irc.debian.org ICQ#45427385 / JabberID: [EMAIL PROTECTED] Sitio == http://filipebrito.blogspot.com Camarada SocialistaEngenheiro de Final de Semana Artista de Rua Tradutor solidário CIPSGA - Software Livre no Brasil - http://www.cipsga.org.br Projeto Debian-BR - http://www.debian-br.org Projeto Debian-SP - http://sp.debian-br.org
Re: [off-topic] sb16 em 2.6.0-test2
Trecho do post-halloween-2.5 do Dave Jones: Modules. - The in-kernel module loader got reimplemented. - You need replacement module utilities from http://www.kernel.org/pub/linux/kernel/people/rusty/modules/ - Debian sid users can 'apt-get install module-init-tools' On Thu, Jul 31, 2003 at 07:36:08AM -0300, Felipe Novaes Caldas wrote: | Porque é necessário atualizar o modprobe e o insmod? -- Junior j x z _em_ u o l c o m b r pgpV65mIpTlsx.pgp Description: PGP signature
Re: [off-topic] sb16 em 2.6.0-test2
Porque é necessário atualizar o modprobe e o insmod? --- Junior [EMAIL PROTECTED] escreveu: On Mon, Jul Compilei tranquilamente, e como uso Woody, minha primeira compilação foi com o mínimo possível de opções (só o básico), e compilei tudo estaticamente, sem uso de módulos, pois deveria atualizar o modprobe, insmod, etc, e eu não queria fazer isso sabendo que não poderia conseguir nem carregar o kernel novo, e poderia precisar voltar ao 2.4. = Felipe Novaes Caldas Engenharia de Controle e Automação - UFMG UIN: 74940355 http://fhp.cjb.net ___ Conheça o novo Cadê? - Mais rápido, mais fácil e mais preciso. Toda a web, 42 milhões de páginas brasileiras e nova busca por imagens! http://www.cade.com.br
Re: [off-topic] sb16 em 2.6.0-test2
On Mon, Jul 28, 2003 at 10:43:55AM -0300, Eduardo Peters wrote: | Subject: Re: [off-topic] sb16 em 2.6.0-test2 | From: Eduardo Peters [EMAIL PROTECTED] | To: Junior [EMAIL PROTECTED] | X-Mailer: Ximian Evolution 1.4.3 | Date: 28 Jul 2003 10:43:55 -0300 | X-SpamProbe: GOOD 0.000 f1762bdbff75d5594f034a40382b55f4 | | Em Dom, 2003-07-27 às 22:38, Junior escreveu: | Ola. | | Acabei de instalar o linux 2.6.0-test2 no meu Debian woody. Aparentemente tudo | esta OK, mas a minha sound blaster 16 (sim, e dai? :) nao esta sendo detectada | corretamente. | | E aí amigo | | Aproveitando que vc conseguiu instalar o kernel 2.6, queria saber como | foi a sua experiência, conseguiu instalar, compilar e fazer realmente | tudo funcionar? | Estou com alguns problemas de hardware, que supostamente serão | resolvidos com a próxima versão do kernel, mas ainda não tive tempo de | trabalhar com isso. | Por isso te pergunto, se houve algum problema , ou se simplesmente | instalo compilo, instalo o inet e tudo fuincionou? Olá. Até agora não tive nenhum problema (exceto o da placa de som, que foi resolvido) com o novo kernel. O menuconfig está muito mais organizado, e mais rápido. A compilação está mais limpa, somente aparece uma linha para cada .o compilado, e um [M] se está sendo compilado como módulo. Compilei tranquilamente, e como uso Woody, minha primeira compilação foi com o mínimo possível de opções (só o básico), e compilei tudo estaticamente, sem uso de módulos, pois deveria atualizar o modprobe, insmod, etc, e eu não queria fazer isso sabendo que não poderia conseguir nem carregar o kernel novo, e poderia precisar voltar ao 2.4. Os recursos de PnP melhoraram bastante, e o kernel detectou minha placa de som e de rede perfeitamente. Eu compilei com a opção de Kernel Preemptivo, mas, embora tenha notado uma boa melhora no tempo de resposta do X, ainda há uns enroscos, como o XMMS dar umas pausadas (skips). Quanto vi que tudo estava OK, recompilei-a com todos os módulos que preciso, atualizei o init-modules, e estou usando há alguns dias (o test1) e o test2 desde que saiu. Desabilitei o modo Preemptivo, e estou rodando-o tranquilamente aqui. Neste período fiz um pequeno crash-test em um programa aqui para testar uns lockfiles, e minha máquina ficou horas com centenas de processos simultâneos, sem sinal de instabilidade. Em geral, está mais rápido. Tem bastante coisa nova, mas alguns módulos ainda precisam ser trabalhados, mas os drivers que eu preciso estão funcionando perfeitamente. Com os novos threads, scheduler, e ainda usando o modo Preemptivo, eu notei um *grande* aumento de performance em aplicativos como o Mozilla (responde mais rápido), squid, KDE (trocar de desktops virtuais fica mais rápido e não há aquela sensação de ver a tela ser pintada), e uso de outros aplicativos enquanto estou compilando, compactando, ou movendo arquivos pesados de um disco para o outro. Quem quiser brincar um pouco, vá em frente. Afinal, quanto mais gente testar, mais bugs vão aparecer, e o 2.6.0 vai vir mais rapidamente e mais estável :-) -- Junior j x z _at_ uol com br pgpRSXHIQXdVj.pgp Description: PGP signature
[off-topic] sb16 em 2.6.0-test2
Ola. Acabei de instalar o linux 2.6.0-test2 no meu Debian woody. Aparentemente tudo esta OK, mas a minha sound blaster 16 (sim, e dai? :) nao esta sendo detectada corretamente. Tentei com os drivers da ALSA, e tambem com os modulos OSS. O problema e que o pnpdump nao me mostra nada, pois talvez isso possa ser uma questao de trocar irq ou dma. No dmesg, surge este trecho: Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 2003 UTC). pnp: the driver 'sb16' has been registered pnp: the driver 'sb16' has been unregistered ALSA device list: No soundcards found. A placa e ISA. Alguem tem alguma sugestao? Ou pelo menos sabe como devo proceder para achar os devidos IRQ's, DMA's, etc da placa, e tentar passar os parametros para o kernel? Nos kernels 2.4.x era so carregar o modulo sb e estava tudo pronto. Tentei com modulos e agora tentei compilar direto no kernel, mas nada. Obrigado. -- Junior [EMAIL PROTECTED] http://jxz.dontexist.org/ pgp7BXRDYPHFJ.pgp Description: PGP signature
Re: [off-topic] sb16 em 2.6.0-test2
Problema resolvido. Eu compilei como módulo o suporte ao sb via OSS, como fazia no antigo 2.4.x. Acho que eu estava fazendo baianada no novo modutils e ele não achava os módulos. :) Agora e' so' esperar para usar o novo driver da alsa, talvez ele sim possua alguns bugs. Obrigado. On Sun, Jul 27, 2003 at 10:38:47PM -0300, Junior wrote: | Date: Sun, 27 Jul 2003 22:38:47 -0300 | From: Junior [EMAIL PROTECTED] | To: debian-user-portuguese@lists.debian.org | Subject: [off-topic] sb16 em 2.6.0-test2 | User-Agent: Mutt/1.3.28i | X-Bogosity: No, tests=bogofilter, spamicity=0.00, version=0.13.7.2 | | Ola. | | Acabei de instalar o linux 2.6.0-test2 no meu Debian woody. Aparentemente tudo | esta OK, mas a minha sound blaster 16 (sim, e dai? :) nao esta sendo detectada | corretamente. | | Tentei com os drivers da ALSA, e tambem com os modulos OSS. | | O problema e que o pnpdump nao me mostra nada, pois talvez isso possa | ser uma questao de trocar irq ou dma. | | No dmesg, surge este trecho: | | Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 2003 UTC). | pnp: the driver 'sb16' has been registered | pnp: the driver 'sb16' has been unregistered | ALSA device list: | No soundcards found. | | A placa e ISA. | | Alguem tem alguma sugestao? Ou pelo menos sabe como devo proceder para | achar os devidos IRQ's, DMA's, etc da placa, e tentar passar os | parametros para o kernel? | | Nos kernels 2.4.x era so carregar o modulo sb e estava tudo pronto. | | Tentei com modulos e agora tentei compilar direto no kernel, mas nada. | | Obrigado. -- Junior [EMAIL PROTECTED] http://jxz.dontexist.org/ pgpsltLn44u1J.pgp Description: PGP signature
Configuracion SB16 en Kernel 2.4.18
Hola Lista, mi problema es que no soy capaz de recompilar mi kernel con las opciones necesarias para que se carge mi tarjeta Sound Blaster 16 y consiga sonido en mi Debian 3.0 r0. Antaño en el kernel 2.2.17 el dma, irq y esas cosas se ponian directamente cuando activabas el modulo en la configuracion del kernel, pero en este nuevo no esta por ningun sitio pero tengo entendido que si lo soporta. ¿Alguien podria echarme una mano?, he buscado por todos sitios y nada y esto es mi ultimo recurso. Muchas gracias de antemano a todos
Re: Problema con sonido (sb16)
Mira a ver que tienes el modulo correcto cargado OSS sound modules 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) Hola a todos amigos Tengo una Sound Blaster 16, y aleatoriamente se cuelga el sistema cuando empieza que debo hacer?? Tengo un 586mx puertos pci and isa 24Mb RAM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9pV4AcopWN41751ERAhcSAJ0VRRpwYJxG8Atlifb/HQdKqxjtbgCePHaP WmSWAtFzzUsbUKdv8EU589s= =Tocz -END PGP SIGNATURE-
Problema con sonido (sb16)
Hola a todos amigos Tengo una Sound Blaster 16, y aleatoriamente se cuelga el sistema cuando empieza que debo hacer?? Tengo un 586mx puertos pci and isa 24Mb RAM
Re: Installaltion d'une SB16 isa
Thomas Harding wrote: On Wed, Aug 14, 2002 at 08:50:40AM +0200, Patrice Karatchentzeff wrote: 3) Il ne te reste plus qu'à déterminer ces valeurs. Le plus simple est de faire une recherche exhaustive à l'aide d'un petit script en Perl ou Bash qui tente d'allouer une paire (IO, IRQ) à ton module. il y a aussi pnpdump qui produit une sortie lisible par un humain des possibilités de la carte (paquet isapnptools ?), même si isapnp n'a plus grande utilité en 2.4. c.f.$ zless /usr/doc/HOWTO/en-txt/Sound-HOWTO.gz TH. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] moi j'ai ca chez moi insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 j'utilise également uart401 comme module -- Ramon Maceiras - PimenTech SARL http://www.pimentech.net 7 bis rue Lesseps Paris XX Tel : 01-43-56-05-00 - 06-10-02-95-25
Re: Installaltion d'une SB16 isa
Le Wed, 14 Aug 2002 02:47:49 +0200 [EMAIL PROTECTED] écrivait : Bonjour à tous :) j'ai une carte son SB16 sur bus isa, modèle CT2960, que je cherche désespérément à installer sur une woody. A chaque fois modprobe me répond Device or ressource busy. J'ai demandé de l'aide sur IRC, on m'a conseillé qq techniques toutes sans succès. Je suis preneur de toutes suggestions. Merci d'avance et bientôt Ah, ces petits jeunes qui n'ont pas connu la joie de l'utilisation des configurations manuelles ! Il n'y a pas 36 solutions : il faut le faire à la mimine... 1) tu repères toutes les IRQ et IO des périphériques « automatiques » (PCI, AGP) pour ne pas les emprunter par mégarde (cat /proc, lspci sont des amis...). 2) Tu vérifies que la carte ISA n'est pas trop ancienne, i.e. que l'on peut lui allouer dynamiquement adresses et IRQ ou bien logiciellement. Sinon, il y a des cavaliers dessus (cas le plus simple : tu peux alors les choisir...). 3) Il ne te reste plus qu'à déterminer ces valeurs. Le plus simple est de faire une recherche exhaustive à l'aide d'un petit script en Perl ou Bash qui tente d'allouer une paire (IO, IRQ) à ton module. Normalement, tu dois trouver ce couple facilement. 4) dernière étape : si le couple (IO, IRQ) est fixé dans des valeurs non traditionnelles et vient marcher sur une adresse utilisée relativement conventionnellement par un périphérique PCI, il te faudra forcer sa détection en tout premier à l'amorçage pour éviter une allocation d'adresse PCI dynamique qui recouvre celle de ta carte ISA. Parfois, le seul moyen est de recompiler le noyau avec la carte ISA en dur (adresse et IRQ). Ce n'est pas très difficile à faire : juste un peu pénible. PK -- Patrice KARATCHENTZEFF STMicroelectronics Tel: 04-76-92-63-81 850, rue Jean Monnet 38926 CROLLES Cedex, France Courriel: [EMAIL PROTECTED]
Re: Installaltion d'une SB16 isa
Le Wed 14/08/2002, Patrice Karatchentzeff disait 4) dernière étape : si le couple (IO, IRQ) est fixé dans des valeurs non traditionnelles et vient marcher sur une adresse utilisée relativement conventionnellement par un périphérique PCI, il te faudra forcer sa détection en tout premier à l'amorçage pour éviter une allocation d'adresse PCI dynamique qui recouvre celle de ta carte ISA. Parfois, le seul moyen est de recompiler le noyau avec la carte ISA en dur (adresse et IRQ). Ce n'est pas très difficile à faire : juste un peu pénible. Du temps où j'avais un mélange ISA/PCI certains BIOS permettaient d'interdire au PCI l'usage de certaines IRQ/IOs. -- Erwan
Re: Installaltion d'une SB16 isa
Il suffit d'installer le paquet isapnp puis de tapper pnpdump. Apres, il
faut editer le fichier /etc/isapnp.conf (ou quelque chose comme ca) et
enlever les commentaires au niveau des paramettres que l'on souhaite
garder. En fait, en general, c'est a peu pres toutes les lignes qui
n'ont pas l'air de vrai commentaires de texte. Il faut bien faire
attention a activer la ligne avec ACT. Exemple pour une carte reseau :
(CONFIGURE PNP0060/15626399 (LD 0
# Compatible device id PNP80d6
# Logical device decodes 10 bit IO address lines
# Minimum IO base address 0x0200
# Maximum IO base address 0x03e0
# IO base alignment 32 bytes
# Number of IO addresses required: 32
(IO 0 (SIZE 32) (BASE 0x0300))
# IRQ 3, 4, 5, 9, 10, 11, 12 or 15.
# High true, edge sensitive interrupt
(INT 0 (IRQ 10 (MODE +E)))
(NAME PNP0060/15626399[0]{NE2000 PLUG PLAY ETHERNET CARD})
(ACT Y)
))
# End tag... Checksum 0x00 (OK)
A partir de la, on peux voir que l'IRQ est 10 et l'io=0x300.
Une fois fait ca, il faut soit redemarrer soit lancer /etc/init.d/isapnp
restart
Puis chager le module sb avec :
modprobe sb io=0x300 irq=10 (dans mon exemple)
Voila, normalement ca devrait rouler. Si toute fois, tu es en noyaux
2.4, a priori il suffit de compiler le PNP dans le noyaux et d'utiliser
modprobe avec les parametres que tu veux genre : modprobe sb io=0x320
irq=5 (assez courrant)
[EMAIL PROTECTED] a écrit:
Bonjour à tous :)
j'ai une carte son SB16 sur bus isa, modèle CT2960, que je cherche
désespérément à installer sur une woody. A chaque fois modprobe me
répond Device or ressource busy.
J'ai demandé de l'aide sur IRC, on m'a conseillé qq techniques toutes sans
succès.
Je suis preneur de toutes suggestions.
Merci d'avance et bientôt
++)
_
Comme disait Emile:
Nous n'héritons pas la terre de nos ancêtres,
nous l'empruntons à nos enfants.
Seattle ( | chef indien | )
Re: Installaltion d'une SB16 isa
Le Wed 14/08/2002, EISELE Pascal disait Il suffit d'installer le paquet isapnp puis de tapper pnpdump. Apres, il faut editer le fichier /etc/isapnp.conf (ou quelque chose comme ca) et enlever les commentaires au niveau des paramettres que l'on souhaite garder. En fait, en general, c'est a peu pres toutes les lignes qui n'ont pas l'air de vrai commentaires de texte. Il faut bien faire attention a activer la ligne avec ACT. Exemple pour une carte reseau : Toutes les SB16 ne sont pas PnP... Encore un jeune qui n'a pas connu les cartes ISA de base... -- Erwan
Re: Installaltion d'une SB16 isa
J'ai dit ca en connaissance de cause... J'avais exactement la meme carte et j'ai egalement eu des carte non-PnP. Non mais ! :-) Erwan David a écrit: Le Wed 14/08/2002, EISELE Pascal disait Il suffit d'installer le paquet isapnp puis de tapper pnpdump. Apres, il faut editer le fichier /etc/isapnp.conf (ou quelque chose comme ca) et enlever les commentaires au niveau des paramettres que l'on souhaite garder. En fait, en general, c'est a peu pres toutes les lignes qui n'ont pas l'air de vrai commentaires de texte. Il faut bien faire attention a activer la ligne avec ACT. Exemple pour une carte reseau : Toutes les SB16 ne sont pas PnP... Encore un jeune qui n'a pas connu les cartes ISA de base...
Re: Installaltion d'une SB16 isa
On Wed, Aug 14, 2002 at 08:50:40AM +0200, Patrice Karatchentzeff wrote: 3) Il ne te reste plus qu'à déterminer ces valeurs. Le plus simple est de faire une recherche exhaustive à l'aide d'un petit script en Perl ou Bash qui tente d'allouer une paire (IO, IRQ) à ton module. il y a aussi pnpdump qui produit une sortie lisible par un humain des possibilités de la carte (paquet isapnptools ?), même si isapnp n'a plus grande utilité en 2.4. c.f.$ zless /usr/doc/HOWTO/en-txt/Sound-HOWTO.gz TH.
Installaltion d'une SB16 isa
Bonjour à tous :) j'ai une carte son SB16 sur bus isa, modèle CT2960, que je cherche désespérément à installer sur une woody. A chaque fois modprobe me répond Device or ressource busy. J'ai demandé de l'aide sur IRC, on m'a conseillé qq techniques toutes sans succès. Je suis preneur de toutes suggestions. Merci d'avance et bientôt ++) _ Comme disait Emile: Nous n'héritons pas la terre de nos ancêtres, nous l'empruntons à nos enfants. Seattle ( | chef indien | )
sb16 na isa - konflikt IRQ
Witam, Mam soundblastera 16 na ISA (IRQ=5). Przy pomocy modconfa dodalem modul sb, ale pojawil sie problem - modconf ustala przerwanie na 7. Kiedy dodalem w linii polecen IRQ=5 modul nie zaladowal sie. Przy starcie systemu pojawia sie konflikt przerwan (IRQ=7), ale nie wiem z jakim urzadzeniem (jak to sprawdzic?). Czy ktos mial podobny problem? -- Pozdrowienia, SK Gdzie sprzedaæ szybko i z zyskiem? My ju¿ wiemy - http://aukcje.pf.pl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sb16 na isa - konflikt IRQ
Pewnego pięknego dzionkaMon, 22 Jul 2002 19:57:46 +0200 SK [EMAIL PROTECTED] stwierdził(a): Witam, Mam soundblastera 16 na ISA (IRQ=5). Przy pomocy modconfa dodalem modul sb, ale pojawil sie problem - modconf ustala przerwanie na 7. Kiedy dodalem w linii polecen IRQ=5 modul nie zaladowal sie. Przy starcie systemu pojawia sie konflikt przerwan (IRQ=7), ale nie wiem z jakim urzadzeniem (jak to sprawdzic?). Czy ktos mial podobny problem? Miałem chyba to samo. Sb 16 Vibra (EISA wersja Plug Pray) strasznie żarła mi się z 3Com509B. Zajęte (a dokładniej używane ) przerwania możesz zobaczyć w pliku /proc/interrupts Ta twoja karta to jest PnP? Na jakim kernelu jedziesz ? Używałeś isapnptools ? -- Sławomir Jeliński _ Adres zwrotny: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sb16 allelllluiiaaaaa!!!
[EMAIL PROTECTED] writes: Comme je suis [en grande partie] un newbie de la config, je tiens à faire une remarque : lorsqu'on m'a conseillé de mettre une ligne append hdb=ide-scsi dans lilo.conf, ça ne marchait pas car je ne faisais pas de lilo -i (ou -v je me souviens plus) pour écrire sur le MBR Oui, mais il y a une option directement dans le lilo.conf, du genre boot=/dev/hda, je ne me souviens plus. Ce qui m'emmene vers une autre question : Est-ce utile de faire une partition /boot ? Ca l'était, mais maintenant, plus trop, grace au support LBA dans les BIOS modernes et dans lilo : Avant, on ne pouvait booter que sur une partition au début du disque dur (dans les 2 premiers Go), et du coup, la finte était de mettre une petite partition /boot au début du disque, et de faire ce qu'on voulait avec la suite. -- Matthieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel+sb16
Le 2002.03.24 14:48, [EMAIL PROTECTED] a écrit : 'Jour Même en recompilant le kernel avec le support de ma sb16 (pas en modules, directement intégrés), ça foire :( J'ai activé le Sound Support, l'OSS, et le 100% compatible sb16, avec les paramètres 220 pour l'io, 5 (puis 7) pour l'IRQ, 1 (puis 3) pour le DMA,... j'ai aussi activé le DMA persistant pour voir si c'était ça qui foirait... La sb16 est très bien supportée depuis longtemps. Je l'ai utilisé avec Slakware à l'époque où les modules n'existaient pas, une RH5.2 avec un noyau 2.0.*, une potato k2.2.17 et maintenant une sid avec un k2.2.20. Je te conseille de l'utiliser sous forme de modules. Si tu l'as déjà utilisée sous windows, verifie que les paramètres (220,5,1) sont bien les mêmes. Y'a que çà qui peut faire merder. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel+sb16
[EMAIL PROTECTED] writes: 'Jour Même en recompilant le kernel avec le support de ma sb16 (pas en modules, directement intégrés), ça foire :( J'ai mis 1 an 1/2 à la configurer, cette ç_è'(! de sb16 ! J'ai finalement réussi, avec un kernel 2.2.20. (celui par défaut de la woody) Sous 2.4, le module son ne veut pas se charger. La solution pour moi était modprobe sb irq=5 (Pour connaitre les paramètre, fais-le sous windows par exemple) J'ai activé le Sound Support, l'OSS, et le 100% compatible sb16, avec les paramètres 220 pour l'io, 5 (puis 7) pour l'IRQ, 1 (puis 3) pour le DMA,... j'ai aussi activé le DMA persistant pour voir si c'était ça qui foirait... Que donne dmesg ? -- Matthieu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sb16 :(
'Soir Ma sb16 ne marche tjrs pas, ça doit être une isa (pnp), et le module sb m'affiche des erreurs d'IRQ et/ou IO. J'ai les modules soundcore,v_midi et oss installés, et j'ai testé les différentes adresses : modprobe sb io=0x220 irq=5 (avec plusieurs valeurs d'io et plusieurs d'irq) le cat /proc/interrupts n'indique pas que les irq 5 et 7 sont pris. Dans le BIOS, pour chaque IRQ, j'ai le choix entre PCI/PnP ou ISA/EISA, et dans les 2 cas j'ai toujours le même résultat (=foirage) Reste-t-il d'autres solutions avant d'envisager la recompilation du kernel ? (qui m'a toujours foiré avec les Mandrakes, j'epère que ça marchera sur la Woody). Merci d'avance Adrien
Re: sb16
[EMAIL PROTECTED] wrote: 'Soir j'ai beau tester, j'arrive pas à configurer ma sb16 : modprobe sb io=0x220 irq=5 ou avec modconf, j'ai toujours le même résultat : des erreurs d'adresse io et irq, sans compter que le device est busy :-) je me demande comment... qqun connait-il la soluce ? Merci d'avance ___ Adrien Bonjour, Je n'ai pas lu le début, donc si je dis une c... merci d'être indulgent, mais que donne un cat /proc/interrupts ? et un lsmod | grep sound* ? A suivre... -- [EMAIL PROTECTED]:~$ make love make : don't know how to make love. Stop [EMAIL PROTECTED]:~$
sb16
'Soir j'ai beau tester, j'arrive pas à configurer ma sb16 : modprobe sb io=0x220 irq=5 ou avec modconf, j'ai toujours le même résultat : des erreurs d'adresse io et irq, sans compter que le device est busy :-) je me demande comment... qqun connait-il la soluce ? Merci d'avance ___ Adrien
Re: alsa and sb16
Hold on... you don't even have an ISA card? You might wanna know that the sb16 driver is for old soundblaster ISA cards ONLY. You're not even using an sb16! I see from you're output that you have an AudioPCI128 -- this is a different card altogether, with different drivers. No wonder the modules aren't working! :) You should be using the ens1371 driver. Check out http://www.alsa-project.org/soundcards.php3 for detailed info. -Matt
RE: alsa and sb16
Curtis Farnham [EMAIL PROTECTED] wrote: --snip-- 00:09.0 Multimedia audio controller: Ensoniq 5580 AudioPCI (rev 02) Subsystem: Ensoniq Creative Sound Blaster AudioPCI128 Flags: bus master, slow devsel, latency 32, IRQ 12 I/O ports at ec00 Capabilities: [cd] #00 [] --snip-- I currently have the latest alsa-driver beta package. I'm running Woody on an i586 K6 machine. PnP OS has been disabled in my BIOS. I am positive that my sound card is SoundBlaster 16 PCI PnP. (I bought it less than a week ago, and I still have the box and all the documentation, which hasn't been any help.) I don't necessarily want to use ALSA. I just want sound to come out of my speakers. I'd be grateful if anyone can help. -Curtis Curtis, You apparently have a SB16-PCI card that uses a completely DIFFERENT audio chipset than the older SB16 ISA cards use. I suspect your fundamental problem is trying to use the wrong driver module. According to the ALSA supported soundcard list at: http://www.alsa-project.org/~goemon/, the SB16-PCI card uses the ens1371 driver module, rather than the sb16 module. I suggest you give it a try. You should NOT have to use any of the isapnp tools for this card. The PCI bus does PnP stuff quite well without any help in the 2.2.X kernels. The same is true of the 2.4.X series kernelsyou don't need it, but having it on your system will NOT hurt anything. Don't worry about trying to set it up, unless you have something else that needs it. I cannot guarantee this will completely solve your problem(s) since I don't have that particular card here, but I am fairlly certain that using the correct driver module will be a significant step!! Cheers, -Don Spoon-
alsa and sb16
Thanks to all who have submitted suggestions on getting ALSA to work with my Sound Blaster 16 PCI PnP card. However, nothing has worked. I've tried ALSA again and again. I tried the kernel's built-in sound-card modules. I tried a different sound card. I tried putting the sound card in a different slot inside my box. I re-installed isapnptools (even though the documentation says I don't need it for a PCI card). But still, nothing. Over and over, 'modprobe sb16' blows up at me, and I keep getting told that the device is either busy or not present. I've wondered if something is broken - either the main board or the sound card itself. But I think not; 'lspci -v -b' seems to indicate everything's fine: 00:09.0 Multimedia audio controller: Ensoniq 5580 AudioPCI (rev 02) Subsystem: Ensoniq Creative Sound Blaster AudioPCI128 Flags: bus master, slow devsel, latency 32, IRQ 12 I/O ports at ec00 Capabilities: [cd] #00 [] Here are some entries in /var/log/messages from my latest boot-up sequence. Some of them may give clues, but I'm too much of a newbie to know for sure. snip Dec 18 18:30:10 debian kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb480, last bus=1 Dec 18 18:30:10 debian kernel: PCI: Using configuration type 1 Dec 18 18:30:10 debian kernel: PCI: Probing PCI hardware Dec 18 18:30:10 debian kernel: PCI: Using IRQ router VIA [1106/0586] at 00:07.0 Dec 18 18:30:10 debian kernel: Activating ISA DMA hang workarounds. Dec 18 18:30:10 debian kernel: isapnp: Scanning for PnP cards... Dec 18 18:30:10 debian kernel: isapnp: No Plug Play devicefound snip Dec 18 18:30:10 debian kernel: ALSA card-sb16.c:612: Sound Blaster 16 soundcard not found or device busy Dec 18 18:30:10 debian kernel: ALSA card-sb16.c:616: In case, if you have AWE card, try snd-card-sbawe module snip Here's the result of 'modprobe snd-card-sb16': /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16 failed Here's the set of code alsaconf sticks into my modules.conf: ### update-modules: start processing /etc/modutils/alsa-path # ALSA modules configuration # --- ALSACONF verion 0.4.3b --- alias char-major-116 snd alias snd-card-0 snd-card-sb16 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0 options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220 snd_mpu_port=0x300 snd_irq=12 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 # Debian ALSA modules path # Do not edit this unless you understand what you're doing. path=/lib/modules/`uname -r`/misc ### update-modules: end processing /etc/modutils/alsa-path I currently have the latest alsa-driver beta package. I'm running Woody on an i586 K6 machine. PnP OS has been disabled in my BIOS. I am positive that my sound card is SoundBlaster 16 PCI PnP. (I bought it less than a week ago, and I still have the box and all the documentation, which hasn't been any help.) I don't necessarily want to use ALSA. I just want sound to come out of my speakers. I'd be grateful if anyone can help. -Curtis
Re: ALSA strikes again (sb16 no go)
I checked my last kernel config file, and automatic kernel loading was enabled. The problem seems to be in getting my computer to realize that the sound card is indeed plugged in. I tried the latest beta-release alsa-drivers and had similar problems as with version 0.5.12a. Would the isapnp-tools package have anything to do with this? All of my cards are pci, so I would think not. Ideas, anyone? On Sun, 2001-12-16 at 20:25, [EMAIL PROTECTED] wrote: snip From: csj [EMAIL PROTECTED] To: Debian User debian-user@lists.debian.org Subject: Re: ALSA strikes again (sb16 no go) Date: 17 Dec 2001 07:03:48 +0800 On Monday 17 December 2001 05:22, Curtis Farnham wrote: Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. Maybe you should enable the automatic kernel module loader. That way you'll be reasonably sure you get all the needed modules loaded (and sometimes more). snip
Re: ALSA strikes again (sb16 no go)
In einer eMail vom 17.12.2001 14:55:53 (MEZ) Mitteleuropäische Zeit schreibt [EMAIL PROTECTED]: I checked my last kernel config file, and automatic kernel loading was enabled. The problem seems to be in getting my computer to realize that the sound card is indeed plugged in. I tried the latest beta-release alsa-drivers and had similar problems as with version 0.5.12a. Would the isapnp-tools package have anything to do with this? All of my cards are pci, so I would think not. Ideas, anyone? Xes, of course you have to install the Isa-PnP package and configrate the alsa-driver with "./configure --with-isapnp=yes" ... that worked for me ... but try the 0.9 tgz from the alsa-homepage Oliver
Re: ALSA strikes again (sb16 no go)
ALSA works just fine with SB16. Try ALSA 0.9 -- it's better. Make sure you have the right module compile options.. oss-emulation, isa-pnp, etc. Then use modconf to make sure that the correct ALSA modules are indeed loaded. To make them load at boot automagically, add them to /etc/modules. Also, remember that ALSA defaults to mute everything. Use a good mixer like aumix-gtk to unmute the channels before you play (/etc/aumixrc will need to be edited so that it works with alsa -- you'll see what I mean when you look at the file. Just comment out the no-alsa lines) cheers, Matt On Sun, 2001-12-16 at 17:22, Curtis Farnham wrote: Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. I was using an ALS4000 card and having no success, and I read somewhere that ALSA didn't fully support it anyway. So, I bought a Sound Blaster 16 PCI PnP card and tried again. My speakers are still sadly silent. Following are various data, outputs, and files that might be of interest to someone gracious enough to help me. I'm running: Debian Woody i586 Sound card: sb16 pci pnp *or* als4000 pci (pnp?) (I only have room enough for 1 of these inside my box.) My ALSA version: 0.5.12a (compiled from source) The command I last used to configure alsa-driver sources before compiling: debian:/usr/src/alsa/alsa-driver-0.5.12a# ./configure --with-sequencer=yes --with-isapnp=no --with-cards=sb16 And after compiling, here was the output from alsaconf: Loading driver: Starting ALSA sound driver (version 0.5.12a): (sb16) Setting the PCM volume to 100% and the Master output volume to 50% The ALSA sound driver was not detected in this system. Could not initialize the mixer, the card was probably not detected correctly. And here's the output from lsmod for sound-related modules (I *think* that's all that were loaded after '/etc/init.d/alsa start'): Module Size Used byTainted: P snip snd30848 0 (autoclean) soundcore 3460 0 (autoclean) [snd] snip Here's the output of 'modprobe snd-card-sb16': /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16 failed And here are the contents of /etc/alsa/modutils/0.5 (also occurs in /etc/modules.conf): # --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF verion 0.4.3b --- alias char-major-116 snd alias snd-card-0 snd-card-sb16 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0 options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220 snd_mpu_port=0x300 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 # --- END: Generated by ALSACONF, do not edit. --- Here's an additional part of /etc/modules.conf, which is seen after the above section # Debian ALSA modules path # Do not edit this unless you understand what you're doing. path=/lib/modules/`uname -r`/alsa Finally, here is a recent portion of /var/log/messages (similar is seen during boot-up): Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #1 not found at 0x220 or device busy Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #2 not found or device busy Thanks, in advance, for any help you can give. -Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA strikes again (sb16 no go)
ALSA works just fine with SB16. Try ALSA 0.9 -- it's better. Make sure you have the right module compile options.. oss-emulation, isa-pnp, etc. Then use modconf to make sure that the correct ALSA modules are indeed loaded. To make them load at boot automagically, add them to /etc/modules. Also, remember that ALSA defaults to mute everything. Use a good mixer like aumix-gtk to unmute the channels before you play (/etc/aumixrc will need to be edited so that it works with alsa -- you'll see what I mean when you look at the file. Just comment out the no-alsa lines) cheers, Matt On Sun, 2001-12-16 at 17:22, Curtis Farnham wrote: Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. I was using an ALS4000 card and having no success, and I read somewhere that ALSA didn't fully support it anyway. So, I bought a Sound Blaster 16 PCI PnP card and tried again. My speakers are still sadly silent. Following are various data, outputs, and files that might be of interest to someone gracious enough to help me. I'm running: Debian Woody i586 Sound card: sb16 pci pnp *or* als4000 pci (pnp?) (I only have room enough for 1 of these inside my box.) My ALSA version: 0.5.12a (compiled from source) The command I last used to configure alsa-driver sources before compiling: debian:/usr/src/alsa/alsa-driver-0.5.12a# ./configure --with-sequencer=yes --with-isapnp=no --with-cards=sb16 And after compiling, here was the output from alsaconf: Loading driver: Starting ALSA sound driver (version 0.5.12a): (sb16) Setting the PCM volume to 100% and the Master output volume to 50% The ALSA sound driver was not detected in this system. Could not initialize the mixer, the card was probably not detected correctly. And here's the output from lsmod for sound-related modules (I *think* that's all that were loaded after '/etc/init.d/alsa start'): Module Size Used byTainted: P snip snd30848 0 (autoclean) soundcore 3460 0 (autoclean) [snd] snip Here's the output of 'modprobe snd-card-sb16': /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16 failed And here are the contents of /etc/alsa/modutils/0.5 (also occurs in /etc/modules.conf): # --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF verion 0.4.3b --- alias char-major-116 snd alias snd-card-0 snd-card-sb16 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0 options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220 snd_mpu_port=0x300 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 # --- END: Generated by ALSACONF, do not edit. --- Here's an additional part of /etc/modules.conf, which is seen after the above section # Debian ALSA modules path # Do not edit this unless you understand what you're doing. path=/lib/modules/`uname -r`/alsa Finally, here is a recent portion of /var/log/messages (similar is seen during boot-up): Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #1 not found at 0x220 or device busy Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #2 not found or device busy Thanks, in advance, for any help you can give. -Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ALSA woes (sb16 no go)
Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. I was trying an ALS4000 sound card and having no success. Then, I read somewhere that ALSA doesn't fully support it. So, I bought a Sound Blaster 16 card and tried again. My speakers are still sadly silent. Following are various data, outputs, and files that might be of interest to someone gracious enough to help me. I'm running: Debian Woody i586 Sound card: sb16 pci pnp *or* als4000 pci (pnp?) (I only have room enough for 1 of these inside my box.) My ALSA version: 0.5.12a (compiled from source) The command I last used to configure alsa-driver sources before compiling: debian:/usr/src/alsa/alsa-driver-0.5.12a# ./configure --with-sequencer=yes --with-isapnp=no --with-cards=sb16 And after compiling, here was the output from alsaconf: Loading driver: Starting ALSA sound driver (version 0.5.12a): (sb16) Setting the PCM volume to 100% and the Master output volume to 50% The ALSA sound driver was not detected in this system. Could not initialize the mixer, the card was probably not detected correctly. And here's the output from lsmod for sound-related modules (I *think* that's all that were loaded after '/etc/init.d/alsa start'): Module Size Used byTainted: P snip snd30848 0 (autoclean) soundcore 3460 0 (autoclean) [snd] snip Here's the output of 'modprobe snd-card-sb16': /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16 failed And here are the contents of /etc/alsa/modutils/0.5 (also occurs in /etc/modules.conf): # --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF verion 0.4.3b --- alias char-major-116 snd alias snd-card-0 snd-card-sb16 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0 options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220 snd_mpu_port=0x300 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 # --- END: Generated by ALSACONF, do not edit. --- Here's an additional part of /etc/modules.conf, which is seen after the above section # Debian ALSA modules path # Do not edit this unless you understand what you're doing. path=/lib/modules/`uname -r`/alsa Finally, here is a recent portion of /var/log/messages (similar is seen during boot-up): Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #1 not found at 0x220 or device busy Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #2 not found or device busy Thanks, in advance, for any help you can give. -Curtis
ALSA strikes again (sb16 no go)
Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. I was using an ALS4000 card and having no success, and I read somewhere that ALSA didn't fully support it anyway. So, I bought a Sound Blaster 16 PCI PnP card and tried again. My speakers are still sadly silent. Following are various data, outputs, and files that might be of interest to someone gracious enough to help me. I'm running: Debian Woody i586 Sound card: sb16 pci pnp *or* als4000 pci (pnp?) (I only have room enough for 1 of these inside my box.) My ALSA version: 0.5.12a (compiled from source) The command I last used to configure alsa-driver sources before compiling: debian:/usr/src/alsa/alsa-driver-0.5.12a# ./configure --with-sequencer=yes --with-isapnp=no --with-cards=sb16 And after compiling, here was the output from alsaconf: Loading driver: Starting ALSA sound driver (version 0.5.12a): (sb16) Setting the PCM volume to 100% and the Master output volume to 50% The ALSA sound driver was not detected in this system. Could not initialize the mixer, the card was probably not detected correctly. And here's the output from lsmod for sound-related modules (I *think* that's all that were loaded after '/etc/init.d/alsa start'): Module Size Used byTainted: P snip snd30848 0 (autoclean) soundcore 3460 0 (autoclean) [snd] snip Here's the output of 'modprobe snd-card-sb16': /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16 failed And here are the contents of /etc/alsa/modutils/0.5 (also occurs in /etc/modules.conf): # --- BEGIN: Generated by ALSACONF, do not edit. --- # --- ALSACONF verion 0.4.3b --- alias char-major-116 snd alias snd-card-0 snd-card-sb16 alias char-major-14 soundcore alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0 options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220 snd_mpu_port=0x300 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0 # --- END: Generated by ALSACONF, do not edit. --- Here's an additional part of /etc/modules.conf, which is seen after the above section # Debian ALSA modules path # Do not edit this unless you understand what you're doing. path=/lib/modules/`uname -r`/alsa Finally, here is a recent portion of /var/log/messages (similar is seen during boot-up): Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #1 not found at 0x220 or device busy Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #2 not found or device busy Thanks, in advance, for any help you can give. -Curtis
Re: ALSA woes (sb16 no go)
Hi, I am using a Yamaha sound card on my Toshiba laptop. First thing that i would do ist to use the alsa-drivers 0.9beta version. After you installed the driver you have to load it with "modprobe snd-card-nameofyourcard" for me it was modprobe snd-card-ymfpci. Than call the alsamixer with alsamixer and unmute all channels you need. This should work.
Re: ALSA strikes again (sb16 no go)
On Monday 17 December 2001 05:22, Curtis Farnham wrote: Does *everybody* have problems getting ALSA to run? Has anyone got an ALS4000 card to work? What about SB16? I am getting frustrated and desparate to get sound to come out of my speakers. Maybe you should enable the automatic kernel module loader. That way you'll be reasonably sure you get all the needed modules loaded (and sometimes more). -- Sir Isaac Newton: If I have seen further, it is by standing on the shoulders of giants.
Help: SB16 'potato'
Okay, I know it's been asked a million times before, probably, but anyone know of a step-by-step guide to getting a Soundblaster 16 to work under 'potato'? Starting with what modules do I have to put in kernel when first installing the system, and with what options, and ending with You now have sound. [and, if anywhere in the process are the words recompile the kernel, you might as well just shoot me now. :] -- ...there are hardly any excesses of the most crazed psychopath that cannot easily be duplicated by a normal, kindly family man who just comes into work every day and has a job to do.[Terry Pratchett, Small Gods] http://www.chebucto.ns.ca/~aa343/index.html
Re: Help: SB16 'potato'
You don't need compile again if you choose sb16 compatible sound support as modules, just lsmod if you not sure. If exist then modprobe the module. If not up to you (compile again or not). On Wed, 17 Oct 2001, Joseph William Dixon wrote: Okay, I know it's been asked a million times before, probably, but anyone know of a step-by-step guide to getting a Soundblaster 16 to work under 'potato'? Starting with what modules do I have to put in kernel when first installing the system, and with what options, and ending with You now have sound. [and, if anywhere in the process are the words recompile the kernel, you might as well just shoot me now. :]
Re: Help: SB16 'potato'
Hello Joseph, Wednesday, October 17, 2001, 07:41:38 Acasica, you wrote: JWD Okay, I know it's been asked a million times before, probably, but anyone JWD know of a step-by-step guide to getting a Soundblaster 16 to work under JWD 'potato'? Starting with what modules do I have to put in kernel when first JWD installing the system, and with what options, and ending with You now have JWD sound. JWD [and, if anywhere in the process are the words recompile the kernel, you JWD might as well just shoot me now. :] it's not hard. i have a creative sound blaster 16 myself. just do modprobe sb and you're all set. i think you're supposed to edit /etc/modules.conf or /etc/conf.modules and add an alias for sb but i bet modutils can do that for you. good luck and don't forget saytime and mpg123 Dani, X unsupport. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: Help: SB16 'potato'
On Wed, 17 Oct 2001, Petre Daniel wrote: it's not hard. i have a creative sound blaster 16 myself. just do modprobe sb and you're all set. I'm surprised - that *did* work. I had managed to get it working before on a previous installation of potato I had by jumping through hoops with insmod, isapnp and suchlike. [bad memory on my part - I have no idea these days just what I finally did last time to get it to work :] i think you're supposed to edit /etc/modules.conf or /etc/conf.modules and add an alias for sb but i bet modutils can do that for you. I remember trying to do that before and ending up with a ton of /etc/modules.conf is newer than /lib/modules/2.2.19pre17/modules.dep errors [and vice-versa]. good luck and don't forget saytime and mpg123 First things I grabbed. :) -- ...there are hardly any excesses of the most crazed psychopath that cannot easily be duplicated by a normal, kindly family man who just comes into work every day and has a job to do.[Terry Pratchett, Small Gods] http://www.chebucto.ns.ca/~aa343/index.html
Re[2]: Help: SB16 'potato'
Hello Joseph, Wednesday, October 17, 2001, 22:16:54 Acasica, you wrote: JWD On Wed, 17 Oct 2001, Petre Daniel wrote: it's not hard. i have a creative sound blaster 16 myself. just do modprobe sb and you're all set. JWD I'm surprised - that *did* work. I had managed to get it working before JWD on a previous installation of potato I had by jumping through hoops with JWD insmod, isapnp and suchlike. [bad memory on my part - I have no idea these JWD days just what I finally did last time to get it to work :] i think you're supposed to edit /etc/modules.conf or /etc/conf.modules and add an alias for sb but i bet modutils can do that for you. JWD I remember trying to do that before and ending up with a ton of JWD /etc/modules.conf is newer than /lib/modules/2.2.19pre17/modules.dep JWD errors [and vice-versa]. good luck and don't forget saytime and mpg123 JWD First things I grabbed. :) you're right.i forgot about those things. It's an isa card,right? so first you have to check it out,sort of speak,hehe.like pnpdump /etc/isapnp.conf then you have to edit that file and set the irq and port and activate it.then run isapnp /etc/isapnp.conf and it should say that soundblaster something enabled.. then there is a command in modutils that i can't remember right now,that sets that not to go away after reboot.i might be wrong.. once the card is set up,then just issue modprobe sb or insmod sb.mine it loads sb,mpu-401,soundcore,soundSOMETHING.. so like 4 modules.. i can't remember if you either edit /etc/modules.conf now or work with modutils to keep enable the sb modules autoloading after reboot..hmm...gotta get some lecithine :p c yah,and gluck. Dani, Winmodems unsupport. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
re re soundblaster sb16
if i only could play sound if i am root: how can i find out? how do i play an mp3 in the rootconsole? with mp3blaster for example? and how do i find other mp3 audioand mpeg1 video player? markus Many SB16 cards can be configured to select PnP or a fixed IRQ. If yours has that capability, you should definitely use a fixed IRQ. In my case, I created /etc/modutils/sb with the following line: options io=0x220 irq=7 dma=1 dma16=5 mpu_io=330 I then ran 'update-modules' (which creates /etc/modules.conf) and 'insmod sb' and sound was working. I put this line in /etc/modules, so sound would be enabled after boot: sb #Soundblaster 16 Bob On Thu, Jul 19, 2001 at 09:22:17AM -0400, Adam Bell wrote: I have the same card. Probably your problem is that it's in plug and play mode, and since it's an ISA card that is suckland for Linux. You need a package called isapnp (apt-get install isapnp), which might already be there. Then you need to dump the output of pnpdump --config into /etc/isapnp.conf (as root). Then you should be set recognizing the card (IF isa plug and play is enabled in your kernel...which it should be. If not, check modconf / recompile kernel with isapnp support). Try isapnp /etc/isapnp.conf. It should recognize some crap and your sound card, and tell you your settings (dma, dma16, io, irq) Write down those 4 things, then go into modconf. The module you want is sb in with all the other cards (It'll automagically get sound-core and all that other crap). For parameters, pass it all those 4 things (io=0x220 dma=1 dma16=5 irq=5 for example). Now it should be recognizable, BUT probably only to root. Anyone whom you wish to make able to use the card needs to be added to the audio group. OR, you could use ALSA, but I don't know how. :) --adam b. BTW, you don't strictly have to have the kernel call isapnp; it's just a lot cleaner. You can also use preloads in your system init scripts, and you can find how to do this on the net. I didn't need to...I just added isapnp.conf to /etc and everything worked after I installed the sb module. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Markus Hansen Sent: Thursday, July 19, 2001 9:05 AM To: Debian Mailinglist Subject: Soundblaster 16 Hi I have got a Debian gnu/linux 2.2 potato on my PC. My problem is the soundcard while using KDE2. I have a Creative Soundblaster sb16 I am not able to get the card working. As I am a real linux-greenhorn I do not know how to do nearly anything, but you all know the start is the hardest... If you could send me a list of the things I have to do I would be very glad. Thank you very much. Yours Markus Hansen. German Version: Hi ich habe ein Debian gnu/linux 2.2 potato installiert. Mein problem ist momentan der sound. Ich habe eine Creative Soundblaster sb16. Ich habe KDE2 und weiss nicht wie ich die karte zum laufen kriege. Es waere sehr nett von Euch, wenn ihr mir eine art Anleitung oder so schreiben koenntet. Ich bin der (fast) totale Linux Anfaenger und somit bitzte ich Euch um Nachsicht. Vielen dank im voraus Euer Markus Hansen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Bob Nielsen, N7XY [EMAIL PROTECTED] Bainbridge Island, WA http://www.oz.net/~nielsen IOTA NA-065, USI WA-028S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ALSA and Creative Vibra16x (sb16)
On Sun, 15 Jul 2001 18:31:47 EDT, Richard wrote: Does anyone have a working ALSA and Creative SB16 Vibra16x ? snd-card-sb16 loads, and xmms works, but I can't get wsoundserver to make any noise ;-( If I switch to the OSS sb module, things seem to work fine. The difference betwixt the Vibra16x and normal SB16 is that this card has two 8bit DMA channels, instead of on 8bit and one 16bit I have a Creative Vibra16x soundcard, but I run OSS with this card. IIRC, the card is unsupported by the ALSA. I'm planning on casting this card on the dustheap as soon as I find the time to get a better card. -- Paul T Wright [EMAIL PROTECTED] And, strange to tell, among the Earthen Lot Some could articulate, while others not: And suddenly one more impatient cried -- Who is the Potter, pray, and who the Pot? -- The Rubaiyat of Omar Khayyam --
Re: placa sb16 pnp - nao pega
Olá ALL, Celso, instala o 'sndconfig' e rode-o no console que é bem provável que ele consiga detectar corretamente sua placa e se não ele é bem intuitivo para configuração dos parâmetros da mesma. Na minha máquina ele consegui detectar corretamente, e entrega todo funcionando beleza; Só que quando reinicio o computador ele perde a confuração. Espero que com você não ocorra esse problema. __ ___ _ __ / |/ /__ _(_)__ / / [EMAIL PROTECTED] / /|_/ / _ `/ __/ / -_) / [EMAIL PROTECTED] /_/ /_/\_,_/\__/_/\__/_/ ICQ 44570007. On Sat, 9 Jun 2001, Celso Andrade wrote: Olá lista, venho acompanhando há algum tempo a lista e aprendido bastante, sou novo no debian e acredito ter encontrado a distribuição ideal. mas, vou direto ao ponto, estou tentando configurar minha placa de som sound blaster16 isa pnp. No win, no conectiva e mandrake ela funciona legal. Mas no debian não consegui ainda. Usei o pnpdump e isapnp mas não acha. Havia um conflito com o modem, mas já resolvi jampeando. Como posso fazê-la funcionar então? ela está na irq 5 dma 1 e 5. Só falta isso para funcionar na minha máquina. Obrigado. -- Celso Andrade [EMAIL PROTECTED] UIN: 107390204
placa sb16 pnp - nao pega
Olá lista, venho acompanhando há algum tempo a lista e aprendido bastante, sou novo no debian e acredito ter encontrado a distribuição ideal. mas, vou direto ao ponto, estou tentando configurar minha placa de som sound blaster16 isa pnp. No win, no conectiva e mandrake ela funciona legal. Mas no debian não consegui ainda. Usei o pnpdump e isapnp mas não acha. Havia um conflito com o modem, mas já resolvi jampeando. Como posso fazê-la funcionar então? ela está na irq 5 dma 1 e 5. Só falta isso para funcionar na minha máquina. Obrigado. -- Celso Andrade [EMAIL PROTECTED] UIN: 107390204begin:vcard adr;dom:;;;recife/pe;;; n:.;Celso x-mozilla-html:FALSE version:2.1 email;internet:[EMAIL PROTECTED] fn:Celso . end:vcard
Re: placa sb16 pnp - nao pega
On Sat, 9 Jun 2001, Celso Andrade wrote: Olá lista, venho acompanhando há algum tempo a lista e aprendido bastante, sou novo no debian e acredito ter encontrado a distribuição ideal. É assim que se fala... mas, vou direto ao ponto, estou tentando configurar minha placa de som sound blaster16 isa pnp. No win, no conectiva e mandrake ela funciona legal. Mas no debian não consegui ainda. Usei o pnpdump e isapnp mas não acha. Havia um conflito com o modem, mas já resolvi jampeando. Como posso fazê-la funcionar então? ela está na irq 5 dma 1 e 5. Tenho uma placa dessa tb... uso a opção da bios dizendo que o OS não é plug-and-play para não ter que me preocupar com o isapnp, depois só é carregar os modulos com os io's irq's e dma's corretamente que fica tudo beleza, no meu caso utilizo os seguintes modulos e opções: sb io=0x220 irq=5 dma=1 dma16=5 opl3 io=0x388 Só falta isso para funcionar na minha máquina. Obrigado. -- Celso Andrade [EMAIL PROTECTED] UIN: 107390204 Espero ter ajudado --==: Rodrigo Morais Araujo :==-- --==: :==-- --==: [EMAIL PROTECTED] :==-- --==:[EMAIL PROTECTED]:==-- begin:vcard adr;dom:;;;recife/pe;;; n:.;Celso x-mozilla-html:FALSE version:2.1 email;internet:[EMAIL PROTECTED] fn:Celso . end:vcard
Q: SB16 ok-Need load other modules?
Hi, I have my SB16 working fine with the following modules compiled and loaded: sound uart401 sb io=0x220 irq=10 dma=1 dma16=5 Everything works. But I didn't find the other card options when compiling to, I believe, load the following modules: mpu_io=0x330 op13 io=0x388 So the question is, have I in fact missed some settings in my kernel (if so, which) compiling and are there further modules and uses of the card and are they those just above? Thanks. Jonathan
Re: Loading SB16 modules...
Stefan Srdic wrote: Michael Steiner wrote: You will find my config, below, just change io irq and dma's to your needs. . ... Thanks for the info, I edited /etc/modules and /etc/modutils/sb along with /etc/isapnp.conf and could not get my sound card initialized. Here's a clip from dmesg: Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 SB 4.16 detected OK (220) sb: Interrupt test on IRQ7 failed - Probable IRQ conflict .. Stef See pnpdump (man pnpdump) it will show you the existing configuration of all pnp cards. You can store the output to a file, modify it for your use and play the configuration back via isapnp. I recommand to read the manpages for isapnp and pnpdump. Compare it with my isapnp.conf and you will understand how to go on. In the kernel doc's is a describtion how to go on with the Vibra card too. Michael -- Michael Steiner, Minorgasse 35, A-1140 Vienna, Austria
Re: Loading SB16 modules...
Michael Steiner wrote:
You will find my config, below, just change io irq and dma's to your
needs.
If it is an ISA card like my one see the isapnp.conf file too.
Michael
--
Michael Steiner, Minorgasse 35, A-1140 Vienna, Austria
in /etc/modutils/sb
options sb io=0x220 irq=5 dma=1 dma16=5
in /etc/modules
soundcore
sound
uart401
sb
...
in /etc/isapnp.conf
##
# VIBRA16
##
(READPORT 0x0273)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
# SB 16 and OPL3 devices
(CONFIGURE CTL0070/-1 (LD 0
(INT 0 (IRQ 5 (MODE +E)))
(DMA 0 (CHANNEL 1))
(DMA 1 (CHANNEL 5))
(IO 0 (SIZE 16) (BASE 0x0220))
(IO 1 (SIZE 2) (BASE 0x0330))
(IO 2 (SIZE 4) (BASE 0x0388))
(NAME CTL0070/-1[0]{Audio })
(ACT Y)
))
# Joystick device - only if you need it :-/
(CONFIGURE CTL0070/-1 (LD 1
(IO 0 (SIZE 1) (BASE 0x0200))
(NAME CTL0070/-1[1]{Game})
(ACT Y)
))
(WAITFORKEY)
Thanks for the info, I edited /etc/modules and /etc/modutils/sb along with
/etc/isapnp.conf and could not get my sound card initialized.
Here's a clip from dmesg:
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
SB 4.16 detected OK (220)
sb: Interrupt test on IRQ7 failed - Probable IRQ conflict
At first I thought that my sound card was fighting over my winmodems IRQ, so I
removed the winmodem from my computer. I later received the same error message
at
boot time.
Here a clip from cat /proc/interrupts
CPU0
0: 39755 XT-PIC timer
1: 1527 XT-PIC keyboard
2: 0 XT-PIC cascade
7: 2 XT-PIC soundblaster
8: 1 XT-PIC rtc
9:914 XT-PIC eth1
10: 1570 XT-PIC eth0
12: 32798 XT-PIC PS/2 Mouse
13: 1 XT-PIC fpu
14: 108499 XT-PIC ide0
15: 14 XT-PIC ide1
NMI: 0
As you can see the soundblaster card has attached itself to IRQ 7 (its a PnP
card). This should be no problem since I have mostly PCI hardware (besides the
soundcard) and I'm running PnP BIOS. Is there any way I can auto-detect my sound
card's hardware settings so that I can use those options for the sb module?
Stef
Re: Loading SB16 modules...
Have you tried modprobe sb yet? Basically, the Vibra line is a weird model SB16--most of them used PnP, so you might want to look into using isapnp program on bootup to configure it. IIRC, there's issues with the DMA8 and full duplex mode, but that shouldn't prevent you from using it: it should only prevent you from using both the mic and speakers simultaneously... On Fri, 22 Dec 2000, Stefan Srdic wrote: I have a Creative Vibra 16x (Sound Blaster 16) that I'm trying to configure so that I can listen to music in Debian. Where do I find the proper kernel modules for my card and how do I load them in Debian? I know which IRQ, DMA 8 and DMA 16 plus I/O that the card uses but do not no which module[s] are needed to load this card. Any suggestions? Thanks Stef -- Pardon me, but you have obviously mistaken me for someone who gives a damn. email [EMAIL PROTECTED]
Re: Loading SB16 modules...
Stefan Srdic wrote:
I have a Creative Vibra 16x (Sound Blaster 16) that I'm trying to
configure so that I can listen to music in Debian. Where do I find the
proper kernel modules for my card and how do I load them in Debian?
I know which IRQ, DMA 8 and DMA 16 plus I/O that the card uses but do
not no which module[s] are needed to load this card.
Any suggestions?
Thanks
Stef
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
You will find my config, below, just change io irq and dma's to your
needs.
If it is an ISA card like my one see the isapnp.conf file too.
Michael
--
Michael Steiner, Minorgasse 35, A-1140 Vienna, Austria
in /etc/modutils/sb
options sb io=0x220 irq=5 dma=1 dma16=5
in /etc/modules
soundcore
sound
uart401
sb
...
in /etc/isapnp.conf
##
# VIBRA16
##
(READPORT 0x0273)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
# SB 16 and OPL3 devices
(CONFIGURE CTL0070/-1 (LD 0
(INT 0 (IRQ 5 (MODE +E)))
(DMA 0 (CHANNEL 1))
(DMA 1 (CHANNEL 5))
(IO 0 (SIZE 16) (BASE 0x0220))
(IO 1 (SIZE 2) (BASE 0x0330))
(IO 2 (SIZE 4) (BASE 0x0388))
(NAME CTL0070/-1[0]{Audio })
(ACT Y)
))
# Joystick device - only if you need it :-/
(CONFIGURE CTL0070/-1 (LD 1
(IO 0 (SIZE 1) (BASE 0x0200))
(NAME CTL0070/-1[1]{Game})
(ACT Y)
))
(WAITFORKEY)
Loading SB16 modules...
I have a Creative Vibra 16x (Sound Blaster 16) that I'm trying to configure so that I can listen to music in Debian. Where do I find the proper kernel modules for my card and how do I load them in Debian? I know which IRQ, DMA 8 and DMA 16 plus I/O that the card uses but do not no which module[s] are needed to load this card. Any suggestions? Thanks Stef
