On Sun, 25 Jan 2004, Mark Knecht wrote: > On Sun, 2004-01-25 at 07:23, Frank Barknecht wrote: > <SNIP> > > There are other ways to specify this in the modules configuration. The > > most common is this from the docs: > > > > 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 > > > > Then you don't need the /dev/mixer lines and you can use > > snd-service-X-X for the second or third card as well. > > > > ciao > > Frank, > Now I'm not sure whether I'm doing something wrong, or possibly > haven't communicated the whole picture clearly enough. I think you're > suggesting I do something that is contrary to what I want to do. (Quote > 'Then you don't need the /dev/mixer lines...') > > First, if you look at my modules.conf stuff below, you'll see I do > have the Alsa commands you show above. Those are necessary, as far as I > know, to get OSS emulation turned on at all. However, I think the > aliases that Knute asked about are to take old standard /dev entires > (mixer, dsp and MIDI) and point them to someplace known. I didn't think > they had anything to do with enabling OSS emulation. Is this not > correct?
No, those lines (/dev/mixer, /dev/dsp,...) are NOT needed in /etc/modules.conf, and may get in the way of the assignment of the devices. If OSS emulation is running properly those devices will get set up automatically. > > Now, possibly I can remove those three lines. Looking around I'm not > sure myself where they come from, so possibly they are a Gentoo > creation. I'll continue to look for the answer since I'm certainly no > Alsa guru and I don't make these things up myself. > > My system has 3 sound devices - A Via 8235, a RME HDSP 9652 and a > MidiSport 2x2. By **DESIGN** I only want OSS to work with the Via sound > chip. I do **NOT** want OSS emulation to know ANYTHING about the HDSP > 9652 as the HDSP 9652 driver has severe problems on my system talking to > my D/A when running OSS. This came very early in my response to 'What > bugs you most' under the header 'driver problems', but that doesn't > concern me since I no longer use the HDSP 9652 for OSS apps. (First > circular problem - it doesn't work, so I don't use it, so it never gets > fixed, but hey, I've reported it and no developer wants to work on it so > I've moved on.) That is why there are the various numbers on the sound slots etc. > > To accomplish what I wanted in my system configuration I have the > following Alsa stuff for modules.conf: > > <SNIP> > # ALSA portion > alias char-major-116 snd > # OSS/Free portion > alias char-major-14 soundcore > > ## ALSA portion > alias snd-card-0 snd-via82xx > options snd-via82xx dxs_support=4 > > alias snd-card-1 snd-hdsp > alias snd-card-2 snd-usb-audio > > > ## OSS/Free portion > alias sound-slot-0 snd-card-0 > ## > > # OSS/Free portion - card #0 (Via8233) > 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/mixer snd-mixer-oss > alias /dev/dsp snd-pcm-oss > alias /dev/midi snd-seq-oss > > # Set this to the correct number of cards. > options snd cards_limit=3 > add options -k snd-card-0 > add options -k snd-card-1 > add options -k snd-card-2 > <SNIP> > > The *intention* is: > > 1) Alsa works for all 3 devices > 2) OSS emulation works for only the Via 8235 > > As far as I can tell most everything works fine on the audio side. There > are problems I just live with: > > 1) If I start an Alsa app using sound card 0, and then start a second > app using sound card 1, at that instant sound card 0 loses audio until I > make an adjustment in hdspmixer. Not good, but not a horrible problem. > > 2) I still have the HDSP 9652/AI-3 OSS problem which no one is working > on. > > On the MIDI side we have the problem that Clemens was earlier interested > in looking at wherein I have to do a cable pull to get the MidiSport > working: > > 1)snd-usb-audio is loaded: > > Wizard root # lsmod > Module Size Used by Not tainted > w83781d 23924 0 (unused) > i2c-viapro 3500 0 (unused) > i2c-proc 6452 0 [w83781d] > i2c-core 15300 0 [w83781d i2c-viapro i2c-proc] > snd-pcm-oss 37860 0 (unused) > snd-mixer-oss 12752 0 [snd-pcm-oss] > snd-usb-audio 44928 0 (unused) > snd-seq-midi 3744 0 (autoclean) (unused) > snd-hdsp 42628 1 > snd-hwdep 4640 0 (autoclean) [snd-hdsp] > snd-via82xx 13824 0 > snd-pcm 64484 0 (autoclean) [snd-pcm-oss snd-usb-audio > snd-hdsp snd-via82xx] > snd-ac97-codec 47564 0 (autoclean) [snd-via82xx] > snd-page-alloc 6164 0 (autoclean) [snd-hdsp snd-via82xx > snd-pcm] > snd-mpu401-uart 3680 0 (autoclean) [snd-via82xx] > snd-rawmidi 14176 0 (autoclean) [snd-usb-audio > snd-seq-midi snd-hdsp snd-mpu401-uart] > snd-seq-oss 27008 0 (unused) > snd-seq-midi-event 3840 0 [snd-seq-midi snd-seq-oss] > ide-scsi 9936 0 > sr_mod 13368 0 (unused) > sg 27580 0 (unused) > snd-seq 39728 2 [snd-seq-midi snd-seq-oss > snd-seq-midi-event] > snd-timer 15428 0 [snd-pcm snd-seq] > snd-seq-device 4144 0 [snd-seq-midi snd-rawmidi snd-seq-oss > snd-seq] > snd 35236 1 [snd-pcm-oss snd-mixer-oss > snd-usb-audio snd-seq-midi snd-hdsp snd-hwdep snd-via82xx snd-pcm > snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-oss > snd-seq-midi-event snd-seq snd-timer snd-seq-device] > sbp2 17748 0 (unused) > scsi_mod 58644 3 [ide-scsi sr_mod sg sbp2] > raw1394 19608 0 (unused) > ohci1394 26128 0 (unused) > ieee1394 47940 0 [sbp2 raw1394 ohci1394] > hid 16036 1 > Wizard root # > > 2) The MidiSport is recognized: > > Wizard root # lsusb > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro > 500 > Bus 001 Device 003: ID 0763:1001 Midiman Midisport 2x2 > Wizard root # > > 3) usbview says the MidiSport is not recognized: > > Unknown Device > Speed: 12Mb/s (full) > USB Version: 1.00 > Device Class: ff(vend.) > Device Subclass: ff > Device Protocol: ff > Maximum Default Endpoint Size: 64 > Number of Configurations: 1 > Vendor Id: 0763 > Product Id: 1001 > Revision Number: 0.01 > > Config Number: 1 > Number of Interfaces: 1 > Attributes: 80 > MaxPower Needed: 100mA > > 4) The lights are not flashing like the MidiSport normally does. > > 5) I pull and insert the USB cable and the lights start flashing and the > MidiSport is recognized by Alsa: > > Wizard root # lsusb > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro > 500 > Bus 001 Device 005: ID 0763:1110 Midiman > Wizard root # > > Note the change to (0763:1110) The midiman sport probably needs its firmware loaded onto the card befor it will work. I do not know that card, but am busting my head on the Maudio Transit, which certainly does need firmware loaded (and which someone who knows USB could probably do in 5 min-- I have the Windows output usb-sniffer 1.8 ) Typicaly the product ID changes when the firmware is loaded. I do not know which of 1110 or 1001 are the loaded and which the unloaded in your case. > > 6) The device is not seen in usbview any more. > ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
