toaderxxix

Sorry to bring up a political issue, I will make sure it's on an off topic board in the future.

gtk gnutella and Qtella are both file sharing aps. But consider using pan and hit the newsgroups. alt.binaries.sounds.mp3.*** (***= at least 50 different groups covering different genres and types groups). Don't know if you connect broadband, which is best, but your isp should have a news server (nntp) Find out what it is, fire up pan and set it up. You find unbelievable amounts of music on the newsgroups and most of the time in complete albums. just type mp3 in the "find" dialog. Good Luck Todd

Glad to hear you got it working! Now we'll send all new extigy users your way! :wink: It's a great feeling once you get something working. It's also great to hear success stories. Now you can chalk it down to experience. It's how we all learn. Linux is a never-ending learning process. But to me, that's half the lure. Good luck. Todd

Just wondering, not to be offensive and please don't take it that way. What's wrong with the internal sound card on your laptop? You're more than likely right in that it won't let you disable it in bios. Laptops are notorious for keeping control away from the user in the bios setup. When we had you do the lsmod | grep snd, that's telling us what modules (or drivers) are loaded for the card. "snd" refers to alsa sound drivers; any module with a "snd" in the name is an alsa driver. These are the modules you asked linux to load by adding those lines to "modules.conf" From what I can see here, those drivers, specifically snd-usb-audio are installed and running on the computer. I see no snd-ess19**, which tells me that you're not loading any drivers for onboard card, which is OK, since you don't want to use it. The only scenario i can think of here, and I could be wrong, (wouldn't be the first time and definitely won't be the last :wink: ) is that maybe your system is trying to use the extigy module (i.e. snd-usb-audio) to run your internal card. Which definitely won't work. This is why we're asking you if you can disable onboard sound from the bios, which apparently isn't an option. My suggestion: Go ahead and open your modules.conf file. Change the references to "snd-usb-audio" to "snd-es1968" and test your onboard sound (after either a reboot or using modprobe etc.) There is no specific driver for ess-1988 sound card but the 1968 one should work. Once you get it working, keep the extigy around, and when either one of us comes accross one, or someone else has one that has gotten it working and can show us how, we'll post it and you can work from there. I've found that if you get frustruated, sometimes it's best to put it down and be unstressed for awhile. Eventually the solution comes along. Like me with my usb midi hub for example. I've had it for a couple of years and hadn't been able to get it to work in linux until just recently. Anyway, I hope this helps somewhat. Again, don't be offended or think i'm being pretentious, I'm just trying to give some friendly advice. I promise the solution will reveal itself eventually. Todd

Here's mine. Made no difference either way but I included both versions. before tweak and after tweak. It's back on the first one now. Note that mine is very similar to zero0w. Will check in later. Have to go to court. I resolve to put the old right foot on a diet.----Toader before change probeall scsi_hostadapter ide-scsi alias eth0 3c59x probeall usb-interface usb-uhci alias /dev/nvidia* nvidia above snd-emu10k1 snd-pcm-oss alias sound-slot-0 snd-emu10k1 after change probeall scsi_hostadapter ide-scsi alias eth0 3c59x alias /dev/nvidia* nvidia above snd-emu10k1 snd-pcm-oss alias sound-slot-0 snd-emu10k1 probeall usb-interface usb-uhci

I tried changing the modules.conf file like a mentioned a few posts posts (and days) back. Sorry i didn't get back sooner. Anyway, it doesn't make a difference. That file is parsed so I'm not sure how I can change the order that hardware devices load. Any suggestions? What I do is unplug the midisport and plug it back in after a boot. either that or i have to unplug it and do a "service alsa restart" as root. then I plug it back in. The way the midisport works: Uses usb-midi driver (http://member.nifty.ne.jp/Breeze/softwares/unix/usbmidi-e.html) along with hotplug and fxload. /etc/hotplug/usb has a script called "ezusbmidi" that calls fxload to load the rom to my hub (which is different than the windows ROM) then alsa loads a driver for it (snd-usb-audio). Anyway, you if the extigy is "hot plugable" then you might consider trying this. boot the machine with the extigy unplugged. login, switch user to root, do an "lsmod | grep snd" note what you find. Then plug in the extigy device, give a second and do an "lsmod | grep snd" again and see if it changes. Since it's a usb device on a laptop, I imagine it won't be that big a deal to plug it in after you boot. Grasping at straws i know. Anyway, again sorry I didn't respond right away. I'm running a computer shop now, and I'm finally starting to get regular business. Worked on an old compaq presario 1200 today. Keyboard didn't work right, turns out it's cable wasnt seated properly. Don't know how it could come loose by itself and the lady says it's never been opened up. Oh well. I'm in a mostly rural area right now, so have to deal with the old windoze alot. SIGH. But when I start generating enough revenue to build some new machines, I'll be loading mandrake dl edition on them and sell them cheaper for incentive. I will encourage them to join the Mandrake Club. Wish me luck, I need it. ToadeR

Don't know if this will shed any light, but my midisport1x1 usb midi hub also uses the snd-usb-audio driver. I found that if i leave it plugged in on a reboot, since USB is scanned first, alsa will load the driver for the hub, then when boot does the alsctrl reset (for my soundcard) it flashes the message "alsa is already running" and doesn't load the driver for my soundcard. The solution (for now): either unplug the usb midi hub before i reboot or first thing, log in as root and do a "service alsa restart". I assume the extigy (not familiar with it) is a usb interface of some sort. Do you have a sound card on board the machine as well? Also, alsa loads a midi device for my midisport as soon as i plug it in (hot plugging is enabled) I have it connected through midi to my yamaha mu10 tone generator. Works like a champ. In fact it seems to transfer the xg sysex through to the mu10 better than the mpu401 (joystick port) interface on my sblive. ex. bending notes and sounds with effects like chorus or reverb. On another note, I wonder if i would solve my problem if i place the alsa lines BEFORE the usb lines in modules.conf (not sure if it matters but I'll try it) I think if alsa drivers were loaded first, THEN my system scanned for USB, it would hotplug the snd-usb-audio drivers as well. Things that make you say: "hmmmmm"

yeah it wasn't alsa, it was kmix. In the older versions of mandrake, after you switched from oss to alsa, kmix would not only be muted, but all the mixer sliders would be set to 0 as well. what threw me this time was kmix was muted (after switching), but after unmuting the sliders were all at the top. Plus, there's over 40 different sliders (specifically for live drive and audigy i suspect) so I was confused. (not the first time :wink: ) Anyway, this time I set XMMS playing mp3 and started throwing sliders and what do you know, it started working. I'm happy now, I have midi, PLUS I got my midisport1x1 usb midi hub working (also alsa drivers) so I can use it in tandem with my yamaha mu10 tone generator. Still I'm a bit embarrassed I missed that problem the first dozen times or so. Anyway, that edit to /etc/profiles works like a champ. I used it before and it's working now as well.

misspelled the font file 8mbgmgssfx.sf2 should be 8mbgmgsfx.sf2 I've been meaning to replace this keyboard... :wink:

As root, edit the file: /etc/profile and add the following before the last line: /bin/sfxload -V100 /*your_path*/8mbgmgssfx.sf2 make sure you add a carriage return (don't remember if it's crucial or not but it doesn't hurt. When you're done the last two lines of /etc/profile should look like this: /bin/sfxload -V100 /*your_path*/8mbgmgssfx.sf2 unset i Works great. Have fun.

Well all i can say is nevermind and kmix sucks. I found out that the snd-emu10k1 driver was working the whole time. the kmix applet would be muted after i installed alsa. However, what I didn't realize is that you had to move the sliders around. DUH! I should use aumix from now on, but kmix is more convenient. Main thing I don't like in the latest kmix is that it has 43 sliders on it. JEEZ! There's only 10 that I can even use with my card. Oh well, I'll live with it as long as i have my midi.

OK I have an original SB-Live value (non 5.1). I loved ALSA until MDK 9.1. Now the ALSA driver treats my card as an "audigy" card, and it doesn't work at all. Normal sound DOES work through oss (emu10k1) I have a Yamaha MU-10 tone generator, and the joystick midi port doesn't work under OSS. I also have a midisport 1x1 usb-midi port. I went through the whole deal with installing it and setting up for hotplug and it works. The problem is that the drivers linux loads for it are ALSA not OSS. DOH! So I know the usb-midi works now, but I'm still stuck with the alsa problem. I skimmed throuh the walkthrough, and I plan on trying the settings there, but I'm afraid it may not solve this problem. Please offer a suggestion to help me out and/or point me to the settings that will work for my card. Thanks in advance.