Re: alsa drivers
Nigel and hopefully a few others, At Thu, 7 Aug 2008 22:43:42 +0200 Nigel Henry wrote, Did you try adding the 3 lines that I suggested to /etc/modprobe.d/alsa-base? It would be nice to find out if the C-Media device is actually causing snd-hda-intel to load, thus causing the conflict when booting with the usb device plugged in. Yes, the three lines have the same effect as keeping the USB sound device unplugged until on-board sound is initialized. Problem solved. Thanks! [EMAIL PROTECTED]:~$ tail --lines=5 /etc/modprobe.d/alsa-base # These specify the card indices. options snd-intel8x0 index=0 options snd-usb-audio index=1 options snd-hda-intel index=2 At Thu, 7 Aug 2008 22:43:42 +0200 nh This is normal from a long time back, ... Odd that the developers and maintainers have ignored this problem for so long. The on-board device should not have to be card0 to work. Arbitrary and superfluous constraints on order of device initialization are contrary to the intention of USB and udev. Thanks for all the help. I hate to think of sorting this out without the ideas and guidance. Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
alsa drivers; was Re: kernels for Lenny.
Nigel and anyone interested in alsa and USB development, nh ... both snd-intel8x0, and snd-hda-intel are being loaded, and it seems like they are both trying to grab card0, which is resulting in neither getting card0, and snd-usb-audio is getting card0, because the other 2 are having a non resolvable argument as to who gets card0. There are two sound devices. Intel 82801BA/BAM AC'97 on the system board and C-media USB plugged in. From my previous investigation. dalton:~# cat /proc/asound/cards 0 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed If the C-Media is card 0, then the Intel device should be card 1. The Intel drivers should not involve a USB device ... unless it contains an Intel or Intel-like chip. nh Try adding the 3 lines below to the bottom of the alsa-base file. There is a simple test before editing alsa-base. Unplug the C-Media device before starting the system and plug it after the on-board Intel chip is initialized. This is from my first trial. dalton:~# cat /proc/asound/cards 0 [I82801BAICH2 ]: ICH - Intel 82801BA-ICH2 Intel 82801BA-ICH2 with AD1885 at irq 17 1 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed Which seems consistent with my hypothesis. Further hypothesizing: the Intel 82801 invokes snd_intel8x0 while the C-Media USB invokes snd_hda_intel. I'll try this unplug/replug procedure a few more times and report next week. USB and udev are appealing concepts but implementation is certainly non-trivial. Thanks for the help. Progress would be difficult without it. Regards, ... Peter E. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alsa drivers; was Re: kernels for Lenny.
On Thursday 07 August 2008 11:46, [EMAIL PROTECTED] wrote: Nigel and anyone interested in alsa and USB development, nh ... both snd-intel8x0, and snd-hda-intel are being loaded, and it seems like they are both trying to grab card0, which is resulting in neither getting card0, and snd-usb-audio is getting card0, because the other 2 are having a non resolvable argument as to who gets card0. There are two sound devices. Intel 82801BA/BAM AC'97 on the system board and C-media USB plugged in. From my previous investigation. dalton:~# cat /proc/asound/cards 0 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed This is normal from a long time back, and in my case, when I was using Fedora Core 1. I have a usb midi keyboard, and it was always being set as card0, as the the usb starts early in the boot sequence, and consequently the actual sound card was unable to use the card0 slot, resulting in no sounds. The fix was to add the following lines to, in the case of Fedora's, /etc/modprobe.conf options snd-emu10k1 index=0(that's the actual soundcard) options snd-usb-audio index=1 (that's for the usb midi keyboard) If the C-Media is card 0, then the Intel device should be card 1. The Intel drivers should not involve a USB device ... unless it contains an Intel or Intel-like chip. I havn't found that that works. Logically yes, but in reality no. Looking back at my situation in Fedora 1 above (that is with no options set), the usb starts first in the bootup sequence, and thinks that my usb midi keyboard is a soundcard, and sets it as card0. the actual soundcard using the snd-emu10k1 driver is looking for setting itself as card0, but the slot for card0 has already been taken by the usb midi keyboard, and consequently the actual soundcard doesn't exist in /proc/asound/cards Btw, if I switch off the usb midi keyboard before booting, then bootup, the emu10k1 is set as card0, and if I then switch the usb midi keyboard on, that is set as card1, which is much as you see below. nh Try adding the 3 lines below to the bottom of the alsa-base file. There is a simple test before editing alsa-base. Unplug the C-Media device before starting the system and plug it after the on-board Intel chip is initialized. This is from my first trial. dalton:~# cat /proc/asound/cards 0 [I82801BAICH2 ]: ICH - Intel 82801BA-ICH2 Intel 82801BA-ICH2 with AD1885 at irq 17 1 [default]: USB-Audio - C-Media USB Headphone Set C-Media USB Headphone Set at usb-:00:1f.2-2, full speed Ok, I see where your going here. Having plugged in the C-Media device after booting up, the big question is, does the sound work? It should do, as snd-intel8x0 is set as card0 Which seems consistent with my hypothesis. Further hypothesizing: the Intel 82801 invokes snd_intel8x0 while the C-Media USB invokes snd_hda_intel. I'll try this unplug/replug procedure a few more times and report next week. USB and udev are appealing concepts but implementation is certainly non-trivial. Thanks for the help. Progress would be difficult without it. Regards, ... Peter E. Did you try adding the 3 lines that I suggested to /etc/modprobe.d/alsa-base? It would be nice to find out if the C-Media device is actually causing snd-hda-intel to load, thus causing the conflict when booting with the usb device plugged in. Just trying to help. Nigel. -- http://members.shaw.ca/peasthope/ http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
alsa-drivers for 2.4.27-speakup
Dear all, I am new to debian. I have a kernel 2.4.27-speakup, and want to install alsa-drivers. But apt-cache search shows there is only drivers for alsa-modules-2.4.27-1. depmod will complain if I install it. Can anyone let me know where to get the alsa drivers for 2.4.27-speakup. Thanks, Xiaowei -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
alsa drivers choking kdeinit
Hello list, for over a month now I've been troubled by a KDE that would increasingly slow down as the uptime of my laptop went up. After a wile, kdeinit would come up and take lots of system cpu. As I kept my laptop running, the cpu spikes caused by kdeinit would become higher, longer sustained and at shorter intervals making my laptop unusable after a few hours (about 3). I always thought it had to do with some kernel stuff since restarting KDE (or X for that matter) would'nt fix it, only a reboot would. Today I finally find out that it was ALSA that was causing all the trouble. I stopped alsa, removed the modules from my kernel, and everything runs smooth. Did anyone else notice this? Did I just have bad luck? When not starting KDE (just xinit) the problem never occured, so it has to be some combination of KDE and ALSA. I'm using a custom kernel (2.4.21-rc2-ac2) with alsa (1.0.3) compiled as module. Any way I can fix this, should I move to 2.6? joost DISCLAIMER This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify A.S.T.R.I.D. nv/sa immediately and then delete this e-mail. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuring alsa drivers on Debian 3.0r2 (2.4.18-bf2.4)
Mark Par markp at ph.inter.net writes: Besides alsa-driver, you also need alsa-lib, alsa-tools and alsa-utils in order to make your on-board soundcard work. You can get them at http://www.alsa-project.org. Thanks for the suggestion. I grabbed some debian packages that appear to be equivalent: alsa-base, libasound2, alsa-utils, and alsaconf. It appears that the files on the CD from ASUS were mostly copies from the alsa site. After reading the documentation there, I was able to fill in the gaps. I had to set some permission on a few device files, insert the modules, and unmute some mixer settings. I now have sound! Thanks for the assistance. Gary Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuring alsa drivers on Debian 3.0r2 (2.4.18-bf2.4)
On Thu, 2004-05-27 at 11:37, Gary Parker wrote: [snip] When KDE starts I get and error message: *** Begin Error message *** Sound Server Informational Messsage Error while initializing sound driver: divice /dev/dsp can't be opened (Permisson Denied) The sound server will continue, using the null output device *** End Error message *** I changed he permissions on /dev/dsp and /dev/dsp0 and added myself to the audio group. Now the error is (no such device). I'm not sure where to go from here. Any suggestions would be helpful. Well the first question is, are you getting any sound at all? If you are then I guess the stock OSS modules are working OK. When I had this issue recently, also after installing afresh on a 2.4 kernel, the suggestion was to change /etc/discover.conf from #boot bridge cdrom disk ethernet ide scsi sound usb video boot all to boot bridge cdrom disk ethernet ide scsi usb video #boot all The idea being to stop the OSS sound module from loading which then prevents the alsa ones from loading afterwards. The sound device is then reported as busy or missing when you try to use alsa. Admittedly I haven't used this workaround. I've removed the module for my soundcard from /kernel/drivers/sound and instead inserted a symlink to the alsa module for it in /lib/modules/1-2-etc/alsa. Works OK here. Just guesses. :) Fish -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuring alsa drivers on Debian 3.0r2 (2.4.18-bf2.4)
On Thu, 27 May 2004 10:37:21 +, Gary Parker wrote: I just installed Debian 3.0r2 with kernel 2.4.18-br2.4 on a new computer with on board sound. The manufacturer of the board, ASUS, provided alsa drivers, alsa-driver-0.9.1adi.tgz, on a CD along with a README file: snip I'm not sure where to go from here. Any suggestions would be helpful. Hello Gary! Besides alsa-driver, you also need alsa-lib, alsa-tools and alsa-utils in order to make your on-board soundcard work. You can get them at http://www.alsa-project.org. If you don't have the kernel headers installed yet, better do a `apt-get install kernel-headers`. And be sure to RTFM. Good luck! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
configuring alsa drivers on Debian 3.0r2 (2.4.18-bf2.4)
I just installed Debian 3.0r2 with kernel 2.4.18-br2.4 on a new computer with on board sound. The manufacturer of the board, ASUS, provided alsa drivers, alsa-driver-0.9.1adi.tgz, on a CD along with a README file: *** Begin README *** Instructions for Installing the ALSA Driver 1. Copy the distribution zip file to the target machine. This zip file is password protected. The password is in the notification email. 2. Unzip the distribution zip. It will ask you for the password. unzip distribution-file-name 3. You should have the ALSA driver tar file and this document. Untar the ALSA files with the command: tar xvzf alsa-driver-0.9.1ADI.tgz 4. You should have a directory called alsa-driver-0.9.1adi. CD to that directory and follow the standard ALSA build instructions in the file INSTALL. cd alsa-driver-0.9.1adi 5. To read the INSTALL file type: more INSTALL 6. The three basic commands needed to build the AC97 ALSA driver are summarize here: (These commands should be executed from the root account.) ./configure --with-cards=intel8x0 --with-kernel=/usr/src/kernel-headers-2.4.18-bf2.4 make install ./snddevices 7. Edit /etc/modules.conf and add the following lines: # ALSA native device support alias char-major-116 snd options snd major=116 cards_limit=1 alias snd-card-0 snd-intel8x0 # OSS/Free setup alias char-major-14 soundcore alias sound-slot-0 snd-intel8x0 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 post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L /dev/null 21 || : pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S /dev/null 21 || : 9. Reboot your system. 10. Please read the ALSA INSTALL file for more information. *** End README *** The INSTALL file had quick install steps which appear to be from alsa. The only thing I got from reading that was to run # modprobe snd-intel8x0, which I did. When KDE starts I get and error message: *** Begin Error message *** Sound Server Informational Messsage Error while initializing sound driver: divice /dev/dsp can't be opened (Permisson Denied) The sound server will continue, using the null output device *** End Error message *** I changed he permissions on /dev/dsp and /dev/dsp0 and added myself to the audio group. Now the error is (no such device). I'm not sure where to go from here. Any suggestions would be helpful. Gary Parker Cayuse, Oregon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
Emma Jane Hogbin wrote: Try: chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi add yourself to the audio group under /etc/group -- mine looks like this: audio:x:29:emmajane,root instructions from: http://www.alsa-project.org/alsa-doc/doc-php/template.php3?company=ALicard= M1535%2CM1535D%2CM1535%2B%2CM1535D%2Bchip=M5451module=ali5451 This worked perfectly. Thanks. I did already have myself added to that group, I did not know that you have to log in and then log out in order to notify the OS that you are now part of a group. Michael Kahle wrote: Any ideas why make-kpkg kernel-image does not work correctly with my Ethernet card? (I realize this is a different post entirely, just thought I would bring it up.) Emma Jane Hogbin wrote: I use wireless, so it may be a slightly different problem; however, for some reason make-kpkg found an old version of the pcmcia source and used out-dated modules. It took me SEVERAL tries to get everything in the right order. I was also configuring for my graphics card (nvidia) for a total of: nvidia, pcmcia and alsa as seperate modules. Plus all the things that are in my kernel as modules (i.e. soundcore). Instead of just relying on --append-to-version I actually (re)moved the /lib/modules/kernel directory and then did modules_install again. (Let me know if you want that in a non-short hand version.) I am not sure what you mean by the --append-to-version comment, I am going to assume that this is something that make-kpkg does automatically? When I built my kernel I did have to rename the /lib/modules/kernel directory before I ran modules_install, but remember this is a kernel built the classic way and --_not_ the Debian way. So if make-kpkg should do this automatically, is it broke on something? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
On Mon, Jul 07, 2003 at 09:30:06AM -0500, Michael Kahle wrote: This worked perfectly. Thanks. I did already have myself added to that group, I did not know that you have to log in and then log out in order to notify the OS that you are now part of a group. Great!! I am not sure what you mean by the --append-to-version comment, I am going to assume that this is something that make-kpkg does automatically? When I built my kernel I did have to rename the /lib/modules/kernel directory before I ran modules_install, but remember this is a kernel built the classic way and --_not_ the Debian way. So if make-kpkg should do this automatically, is it broke on something? Ah, I didn't realize you weren't doing things The Debian Way. In this case it's extra important that you remember to *delete* or otherwise move the /lib/modules directory that's created when you compile your kernel. If you don't you *may* end up not having the new modules put into the directory. This happened to me several times when I was trying to get my wireless card working--without deleting the directory the old drivers weren't overwritten when I compiled a new kernel. Hope that helps, emma -- Emma Jane Hogbin [[ 416 417 2868 ][ www.xtrinsic.com ]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel Compile the Debian Way... was RE: ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
Michael Kahle wrote: I am not sure what you mean by the --append-to-version comment, I am going to assume that this is something that make-kpkg does automatically? When I built my kernel I did have to rename the /lib/modules/kernel directory before I ran modules_install, but remember this is a kernel built the classic way and --_not_ the Debian way. So if make-kpkg should do this automatically, is it broke on something? Emma Jane Hogbin wrote: Ah, I didn't realize you weren't doing things The Debian Way. In this case it's extra important that you remember to *delete* or otherwise move the /lib/modules directory that's created when you compile your kernel. If you don't you *may* end up not having the new modules put into the directory. This happened to me several times when I was trying to get my wireless card working--without deleting the directory the old drivers weren't overwritten when I compiled a new kernel. I did end up figuring out that I needed to rename the /lib/modules directory in order to get the kernel and modules to build correctly. I am currently writing you on the computer running this new kernel. (Well, using Outlook running on VMWare, running on the new kernel! ;-) However, I did not want to do things this way. I wanted to do it the Debian way. I ran into problems with things working using make-kpkg. I just looked at the man page on make-kpkg. I understand what you were saying now with the --append-to-version argument. It seems to me that this is used to differentiate between one or more kernels that the sysadmin has customized. Apparently this command inserts a value (rather appends) the value of the EXTRAVERSION variable in the Linux Makefile. Good to know. So my final question then is this, what should be the steps one goes through to compile the kernel the Debian Way? I used Dwarf's Guide to Debian GNU/Linux to guide me through this process. The guide outlines two methods for building a custom kernel. The typical way and the Debian Way. The procedure for the typical way is as follows: make mrproper make xconfig make dep make clean make bzImage make modules make modules_install The procedure for the Debian Way is: make xconfig make-kpkg kernel-image Should I be doing other steps when doing it the Debian way? For instance instead of first running make xconfig should I run make mrproper? After I run make-kpkg kernel-image should I run make modules and make modules_install? Or does make-kpkg kernel-image take care of all of this for me? Thanks for your time! Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Compile the Debian Way... was RE: ADI Soundmax 1881(intel chipset) w/ ALSA Drivers
On Mon, 7 Jul 2003 12:54:54 -0500 Michael Kahle [EMAIL PROTECTED] wrote: The procedure for the Debian Way is: make xconfig make-kpkg kernel-image Should I be doing other steps when doing it the Debian way? For instance instead of first running make xconfig should I run make mrproper? After I run make-kpkg kernel-image should I run make modules and make modules_install? Or does make-kpkg kernel-image take care of all of this for me? The short answer is look here: http://newbiedoc.sourceforge.net/system/kernel-pkg.html The idea of make-kpkg was to automate that long sequence of steps; after you configure the kernel and make the kernel image all you need to do is install the kernel image .deb. By default make-kpkg runs distclean (cleaner than mrproper) after building the kernel .deb (it moves the .config file out of the way first, and restores it afterward). Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
On Thu, Jun 26, 2003 at 10:57:22AM -0500, Michael Kahle wrote: Greetings fellow Debianites, Sorry, this may be a little long winded. For the past couple of days I have been trying off and on to get the ALSA drivers setup on my Woody box. Big SNIP Now when I launch XMMS as a user, trying to play a mp3 brings up the message: Please check that: 1. You have the correct output plug-in selected 2. No other programs is blocking the soundcard 3. Your soundcard is configured properly Now when I run XMMS as root, it works just fine, plays my music just fine. Is this a permissions issue with the sound card device(s)? If so, what is the best (read most secure) way to enable access for my user account? If it works as root, I'd say with some confidence that the drivers *work* and it's a permission problem or xmms config problem or such. Have you added your user account to the group audio yet? * Note that being added to a group only takes effect on the next login (ie, if you're already logged in as that user, you'll need to log out completely and then log back in). If that doesn't do it, take a look at what output plugin you're using (as per the error message)... Any ideas why make-kpkg kernel-image does not work correctly with my Ethernet card? (I realize this is a different post entirely, just thought I would bring it up.) Nope, I'm afraid I haven't got a clue on that issue. -- ,-. -ScruLoose- | Oh, America my friend / And so once again Please do not| You are fighting us all / And when we ask you why reply off-list. | You raise your sticks and cry and we fall |- Joni Mitchell `-' pgp0.pgp Description: PGP signature
Re: ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
On Thu, Jun 26, 2003 at 10:57:22AM -0500, Michael Kahle wrote: Now when I launch XMMS as a user, trying to play a mp3 brings up the message: Please check that: 1. You have the correct output plug-in selected 2. No other programs is blocking the soundcard 3. Your soundcard is configured properly Now when I run XMMS as root, it works just fine, plays my music just fine. Is this a permissions issue with the sound card device(s)? If so, what is the best (read most secure) way to enable access for my user account? Try: chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi add yourself to the audio group under /etc/group -- mine looks like this: audio:x:29:emmajane,root instructions from: http://www.alsa-project.org/alsa-doc/doc-php/template.php3?company=ALicard=M1535%2CM1535D%2CM1535%2B%2CM1535D%2Bchip=M5451module=ali5451 I was getting that error message. Ulimately I'm not convinced I'd actually installed the (correct) ALSA modules. But since you *can* play music as root your problem might be somewhat easier to solve. Any ideas why make-kpkg kernel-image does not work correctly with my Ethernet card? (I realize this is a different post entirely, just thought I would bring it up.) I use wireless, so it may be a slightly different problem; however, for some reason make-kpkg found an old version of the pcmcia source and used out-dated modules. It took me SEVERAL tries to get everything in the right order. I was also configuring for my graphics card (nvidia) for a total of: nvidia, pcmcia and alsa as seperate modules. Plus all the things that are in my kernel as modules (i.e. soundcore). Instead of just relying on --append-to-version I actually (re)moved the /lib/modules/kernel directory and then did modules_install again. (Let me know if you want that in a non-short hand version.) emma -- Emma Jane Hogbin [[ 416 417 2868 ][ www.xtrinsic.com ]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ADI Soundmax 1881 (intel chipset) w/ ALSA Drivers
Greetings fellow Debianites, Sorry, this may be a little long winded. For the past couple of days I have been trying off and on to get the ALSA drivers setup on my Woody box. The computer is a IBM Intellistation Z-Pro (6866-60U). Because I never had sound installed on this machine, I never had the SOUNDCORE module loaded as part of my kernel. When I started this venture I was using a custom kernel that I made to support my 5 disk SCSI RAID5 LVM disk setup. So I built a new kernel that had SOUNDCORE support in addition to my other needs. I have the 2.4.18 debian package source for woody. Ran: make mrproper make xconfig make-kpkg kernel-image When I built the kernel the Debian way, for some reason my network card (eepro100) could never get an IP address. So, I built the kernel the manual way. Ran: make mrproper make xconfig make dep make clean make bzImage make modules make modules_install This worked wonderfully and I didn't have to figure out what was going on with make-kpkg. So now I have a custom 2.4.18 kernel with SCSI+RAID5+LVM and now soundcore support as a module. When I installed the Debian packages for ALSA using dselect, I could not get it to configure properly with my sound card. I then went to alsa's site (http://www.alsa-project.org) and followed their directions to install the latest stable release 0.94 of the Driver, Library, Utilities, and Tools. I now can see that these modules are loaded... lsmod shows: snip Module Size Used byTainted: PF snd-seq-oss23104 0 (unused) snd-seq-midi-event 2984 0 [snd-seq-oss] snd-seq36236 2 [snd-seq-oss snd-seq-midi-event] snd-pcm-oss36516 0 snd-mixer-oss 11232 0 [snd-pcm-oss] snd-intel8x0 15168 0 snd-pcm54624 0 [snd-pcm-oss snd-intel8x0] snd-timer 13920 0 [snd-seq snd-pcm] snd-page-alloc 4496 0 [snd-intel8x0 snd-pcm] snd-ac97-codec 32816 0 [snd-intel8x0] snd-mpu401-uart 2848 0 [snd-intel8x0] snd-rawmidi12384 0 [snd-mpu401-uart] snd-seq-device 3764 0 [snd-seq-oss snd-seq snd-rawmidi] snd27136 0 [snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-pcm snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device] soundcore 3492 5 [snd] /snip I launch alsamixer and it shows my sound card information at the top. So, it seems that everything is installed correctly and working. I then installed XMMS using dselect from the stable tree. This prompted me to install all sorts of stuff. Libasound1, libesd-alsa0, xmms, esound, some documentiation. Now when I launch XMMS as a user, trying to play a mp3 brings up the message: Please check that: 1. You have the correct output plug-in selected 2. No other programs is blocking the soundcard 3. Your soundcard is configured properly Now when I run XMMS as root, it works just fine, plays my music just fine. Is this a permissions issue with the sound card device(s)? If so, what is the best (read most secure) way to enable access for my user account? Any ideas why make-kpkg kernel-image does not work correctly with my Ethernet card? (I realize this is a different post entirely, just thought I would bring it up.) Any help is always appreciated. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ALSA drivers et devices, midi et ensoniq 1370 : des spcialistes son sous linux ?
Salut, Je cherche composer sous linux et plus particulierement sous notre chre debian. J'ai fait un petit tour des logiciels disponible et ai tent d'installer ceux qui tait dispos sur la distrib. Brahms fait semblant de s'installer, l'executable n'est pas prsent. Rosegarden4 dpends de paquets qui ne sont pas dispos. Muse freeze sans explications avant mme d'exposer une GUI. Je tiens autant que faire se peut utiliser les paquets de la distrib plutot que de compiler in situ les logiciels. En attendant j'ai voulu installer les drivers ALSA qui semblent indispensables, j'ai reussi avec les source 2.4.20 du noyau, tous les modules sont chargs, modules de compatibilt OSS et module natif ens1370 pour ma carte son. Je peux sortir du son via PCM sans problme et peux regler le mixer avec tous les utilltaires que j'ai pu trouver pour ce faire. J'ai essay solfege, qui a besoin du device /dev/music. Pas de sortie son de cette manire. Les aides sur ALSA que j'ai pu lire sur le net sont obsolte avec la version 0.9. Ce que je cherche alors, c'est des liens sur toutes documentations assez rcentes autour du thme du son sous linux, des indications sur des moyens de tester l'installation sonore dans son ensemble de sorte que je puisse m'assurer que l'install est bien complte avant de chercher des problme dans les logiciels utilisateurs ou bien un gentil gourou qui aura l'extreme gentillesse de bien vouloir m'indiquer les concepts cls du processus (et m'parger des jours de dcryptage de code :) ) Un grand merci par avance pour votre aide ! Fred -- Nul ne peut atteindre l'aube sans passer par le chemin de la nuit Khalil Gibran
alsa drivers
hola a toda a lista, mi problema es eso, la instalacion de los alsa drivers q por mas ke lo intento no lo doy conseguido, esta es la situacion: - tarjeta de red via8233a (ac97 codec) integrada en placa - sistema debian woody actualizado a sid lo he intentado de multiples maneras y siguiendo varios manuales de los que andan por el google incluidos en especifico para mi placa que se encuentra en la pagina de ALSA pero sin conseguirlo lo ultimo que he intentado ha sido siguiendo este estupendo manual que explica como instalar los alsa en debian: http://slashdot.org/articles/02/11/01/1645231.shtml?tid=90 despues de haberlo seguido al pie de la letra ahora me da este error cuando intento arrancarlo Starting ALSA sound driver (version 0.9.0beta12): no sound cards defined ya no se por donde seguir... as incluyo aki la configuración de los ficheros de alsa por si sirve de algo ## /etc/alsa/alsa-base.conf # This is a configuration file for alsa-base. # Define true if you want the OSS compatibility layer # to be automatically loaded as well startosslayer=true # Define true if you want to unload alsa modules before # your system suspneds. This is currently useful if your # machine is hanged up after resume. force_stop_modules_before_suspend=false # Uncomment if you always want to stop alsa modules forcibly in # /etc/init.d/alsa stop or restart by killing all of running # applications which use sound devices. ALSA_KILL_MODE=force ## /etc/modutils/alsa ## # Example Configuration of ALSA 0.9 for Debian GNU/Linux alias char-major-116 snd alias char-major-14 soundcore options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=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 alias snd-card-0 snd-via8233.o #alias snd-card-1 snd-serial #alias snd-card-2 snd-share #alias snd-card-3 snd-virmidi alias sound-slot-0 snd-card-0 alias sound-slot-1 snd-card-1 alias sound-slot-2 snd-card-2 alias sound-slot-3 snd-card-3 # You must need to add your own card setteings below. # or use alsaconf to setup in menu form. # gracias de antemano por la ayuda un saludo
Re: alsa drivers
brauz wrote: hola a toda a lista, mi problema es eso, la instalacion de los alsa drivers q por mas ke lo intento no lo doy conseguido, esta es la situacion: - tarjeta de red via8233a (ac97 codec) integrada en placa - sistema debian woody actualizado a sid Prueba con este enlace : http://bulmalug.net/body.phtml?nIdNoticia=1518 -- Josep M. Mendoza
ALSA: woody alsa drivers?
I'm trying to configure a Cirrus Logic 4614-series driver, understand that it wants ALSA, but the alsa-drivers packages are AWHOL. $ lspci 00:06.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) Best I can figure, the alsa-modules components aren't in Woody at the moment. I'm not quite clear on best means to configure them under Debian either. Enlightment or references? Thanks. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? Home of the brave http://gestalt-system.sourceforge.net/ Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpi3fa5HVyD6.pgp Description: PGP signature
Re: ALSA: woody alsa drivers?
On Tue, Nov 06, 2001 at 11:15:51PM -0800, Karsten M. Self wrote: I'm trying to configure a Cirrus Logic 4614-series driver, understand that it wants ALSA, but the alsa-drivers packages are AWHOL. $ lspci 00:06.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) Best I can figure, the alsa-modules components aren't in Woody at the moment. I'm not quite clear on best means to configure them under Debian either. Enlightment or references? Take a look at alsa-source package. Last time I used alsa was a long while ago, but as far as I remeber it was easy to compile your own modules (and AFAIK you have to if you use custom kernel). See documentation for that package, it describes in detail how to use kernel-package to roll your own deb with modules. Hope that helps. Thanks. -- Karsten M. Self kmself@ix.netcom.com http://kmself.home.netcom.com/ What part of Gestalt don't you understand? Home of the brave http://gestalt-system.sourceforge.net/ Land of the free Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html -- GPG key-id: 1024D/DF04A255 Dmitriy AA16 8FAB 74E1 3511 83D0 9F4B F087 CEC9 DF04 A255 Free Dmitry Sklyarov! http://www.freesklyarov.org pgpr1HkvNBnSR.pgp Description: PGP signature
Re: ALSA: woody alsa drivers?
* Karsten M. Self (kmself@ix.netcom.com) spake thusly: I'm trying to configure a Cirrus Logic 4614-series driver, understand that it wants ALSA, but the alsa-drivers packages are AWHOL. $ lspci 00:06.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] (rev 01) Best I can figure, the alsa-modules components aren't in Woody at the moment. I'm not quite clear on best means to configure them under Debian either. Enlightment or references? You're supposed to compile them yourself. Unfortunately, alsa packages in woody are screwed, use the upstream sources. Also, I had problems with latest alsa and 2.4.12 -- probably nothing serious but I haven't time to investigate. Dima -- Surely there is a polite way to say FOAD.-- Shmuel Metz Go forth and multiply. -- Paul Martin
alsa-drivers oops my kernel when i reload them
i'm using the alsa 0-0.9beta4 drivers as built from source
distributed with debian unstable.
since debian has started distributing the beta drivers (including
beta3), i've oopsed my kernel every time i've recompiled the
modules, installed them, unloaded the old, loaded the new, then
tried to play an mp3 thru mpg123 - esd - oss emulation.
unfortunately, i can't get a log of the oops, since it takes the
whole machine with it. even magic sysrq seems to be mostly broken
at that point.
any suggestions. i'll try to answer any questions sent my way.
thanks.
--
}John Flinchbaugh{__
| [EMAIL PROTECTED] http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~
pgpaXGaztkRoc.pgp
Description: PGP signature
Installing Alsa Drivers
I'm trying to install the alsa drivers for my yamaha sound card. when I input ./configure I get this error message: ... checking for working const... yes checking for inline... inline checking whether time.h and sys/time.h may both be included... yes checking whether gcc needs -traditional... no checking for directory with kernel source... /usr/src/linux checking for kernel version... expr: syntax error expr: syntax error expr: syntax error failed (probably missing /usr/src/linux/include/linux/version.h) debian:/home/dlm/tmp/alsa-driver-0.5.8b# What does this mean and what do I do to fix it? Thanks -- dale
Re: Installing Alsa Drivers
On Sat, Jul 29, 2000 at 07:00:54AM -0700, Dale Morris wrote: I'm trying to install the alsa drivers for my yamaha sound card. when I input ./configure I get this error message: [...] failed (probably missing /usr/src/linux/include/linux/version.h) you don't have a ready-to-build source tree under /usr/src/linux. do an, 'make-kpkg kernel_image' or 'make menuconfig dep clean' or something.. i'm not sure, which target is needed. then for example this version.h gets created, too... moritz -- /* Moritz Schulte [EMAIL PROTECTED] * http://hp9001.fh-bielefeld.de/~moritz/ * PGP-Key available, encrypted Mail is welcome. */
Re: Installing Alsa Drivers
On 29-Jul-2000 Moritz Schulte wrote: On Sat, Jul 29, 2000 at 07:00:54AM -0700, Dale Morris wrote: I'm trying to install the alsa drivers for my yamaha sound card. when I input ./configure I get this error message: [...] failed (probably missing /usr/src/linux/include/linux/version.h) you don't have a ready-to-build source tree under /usr/src/linux. do an, 'make-kpkg kernel_image' or 'make menuconfig dep clean' or something.. i'm not sure, which target is needed. then for example this version.h gets created, too... You mean make-kpkg clean make-kpkg --revision=yourhostname.1.0 kernel_image ? -- Andrew
Re: ALSA drivers
Samuel Montosa decía: El Sun, Oct 24, 1999 at 08:32:50PM +0200, Angel Vicente Perez dijo: si tengo el kernel 2.2.12 y una tarjeta Crystal CS 4232, ¿deberia instalar todas estas cosas? que son todas esas cosas?,si te refieres a todos los modulos, obviamente no, solamente los de la tarjeta mirate tambien el script de configuracion que viene en otro paquete, que te lo hace todo casi automaticamente... Realmente es que no se que es ALSA son unos driver de sonido, y por cierto... son la caña... Pues confesaré (sin que sirva de precedente) que mi experiencia con ALSA ha sido un auténtico fracaso. Serán mejores, pero yo me apaño mejor con OSS. Y mira que le he metido caña... -- The most secure computer is the one that's turned off, unplugged, encased in concrete and sunk in the atlantic. It's useabilty does suck, though. --- Barbwired (The Translatrix) - U. Complutense de Madrid - Filología Inglesa Web personal http://www.bigfoot.com/~barbwired/ Proudly running Debian GNU/Linux 2.1 (Kernel 2.2.12) on a Dell Laptop
Re: ALSA drivers
El Sun, Oct 24, 1999 at 08:32:50PM +0200, Angel Vicente Perez dijo: Hola a todos He bajado los fuentes que he encontrado relativos a ALSA, para leer documentacion, pero tengo muchas dudas. La pregunta es: si tengo el kernel 2.2.12 y una tarjeta Crystal CS 4232, ¿deberia instalar todas estas cosas? que son todas esas cosas?,si te refieres a todos los modulos, obviamente no, solamente los de la tarjeta mirate tambien el script de configuracion que viene en otro paquete, que te lo hace todo casi automaticamente... Realmente es que no se que es ALSA ¿?¿?¿?¿? :-) son unos driver de sonido, y por cierto... son la caña... Saludos. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null --
(Fwd) ALSA drivers
Hola a todos He bajado los fuentes que he encontrado relativos a ALSA, para leer documentacion, pero tengo muchas dudas. La pregunta es: si tengo el kernel 2.2.12 y una tarjeta Crystal CS 4232, ¿deberia instalar todas estas cosas? Realmente es que no se que es ALSA La verdad es que las tarjetas soportadas por el kernel no necesitan de ayudas externas para funcionar. Para ver si la tuya lo está mira en la parte de sonido de la documentación del kernel (directorio Documentation y subdirectorio Sound). Ahí hay un archivo que te lista las tarjetas soportadas. Si está ahí olvídate de ALSA pues seguro que si configuras bien el kernel este la manejará sin problemas. Si no está ahí es cuando hay algo más de trabajo. ALSA significa Advanced Linux Sound Arquitecture (arquitectura de sonido avanzada para Linux). También tendrás que mirar si tiene soporte para tu tarjeta y si es así instalarlo. Sobre ALSA no puedo ayudarte más pues no lo he usado. Siento no poder ayudarte más, pero espero que estas pistas te sirvan para algo. Saludos. Diego -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
ALSA drivers
Hola a todos He bajado los fuentes que he encontrado relativos a ALSA, para leer documentacion, pero tengo muchas dudas. La pregunta es: si tengo el kernel 2.2.12 y una tarjeta Crystal CS 4232, ¿deberia instalar todas estas cosas? Realmente es que no se que es ALSA Saludos.
Trouble with ALSA drivers w/ Debian
Hi, I'm trying to install the alsa sound driver which came with my Debian 2.1 cdroms. Everything goes fine until dpkg starts the configuration part, then the program complains about not being able to make certain devices under /dev (the audio devices) because it's a read- only filesystem. My linux partition is mounted read-write, and my /dev directory has the necessary permissions (I think). Has anyone besides me ever run into this or know whats wrong? Thanks, Joseph Dunn
Re: alsa drivers and slab
Dear Matt, thank you very much for your long answer. I will try all this when I get the time to try the 2.2 Kernels ... Yours -- ____ Frank Barknecht __ __ trip\ \ / /wire __ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / / / / / // // /\ \\ ___\\ \ /_/ /_/ /_/ /_//_// / \ \\_\\_\ /_/\_\
Re: alsa drivers and slab
Matt Garman hat gesagt: // Matt Garman wrote: On Thu, Feb 04, 1999 at 10:27:59AM -0600, Matt Garman wrote: Has anyone been sucessful using the Advanced Linux Sound Architecture (ALSA) drivers in FULL DUPLEX mode with the program slab? I have a SB AWE 32, wich is currently working great with the stock OSS kernel drivers (and isapnp), but these drivers are only good for half-duplex. I'll answer my own question here, in case anyone is ever interested in this. Yes, I am very interested but did not know the answer to your problem. I did never manage to get Slab working with OSSFree and the old kernels 2.0.3x not even without any duplex (half, full). With my SoundBlaster AWE 32 p'n'p, I can use SLab in full-duplex mode, that is, use my computer to record as many tracks as my hardware will allow! It's AWEsome (pun intended). I have a AWE 64 Value Ed. set up with the aweutils. Could you please tell me (and all on the list) what you did to get Slab running. What version of Slab did you use? What kernel version? As I said, I would really like to hear more... Thanks in advance -- ____ Frank Barknecht __ __ trip\ \ / /wire __ / __// __ /__/ __// // __ \ \/ / __ \\ ___\ / / / / / / / // // /\ \\ ___\\ \ /_/ /_/ /_/ /_//_// / \ \\_\\_\ /_/\_\
Re: alsa drivers and slab
On Thu, Feb 11, 1999 at 01:03:40PM +0100, Frank Barknecht wrote: Yes, I am very interested but did not know the answer to your problem. I did never manage to get Slab working with OSSFree and the old kernels 2.0.3x not even without any duplex (half, full). It's all about the ALSA drivers :) I was afraid to use them at first, but I figured I couldn't go wrong. I have a AWE 64 Value Ed. set up with the aweutils. Could you please tell me (and all on the list) what you did to get Slab running. What version of Slab did you use? What kernel version? As I said, I would really like to hear more... I'm running kernel version 2.2.1; I configured sound as a module in the kernel config, set my /etc/conf.modules correctly, and had OSS/Free (= stock kernel drivers) working fine for everything EXCEPT SLab. (I actually froze my machine _completely_ trying to use SLab with the stock kernel drivers.) So then I turned to ALSA. I did NOT use the Debian package, but just the plain tar.gz file from the ALSA website: alsa-driver-0.2.0-pre10p2.tar.gz. Shortly after I got that working, they released a new version of the ALSA driver: alsa-driver-0.3.0-pre3.tar.gz; I also got this working. With the alsa-driver-0.3 version, P'n'P support is included as a MODULE -- it negates the need for isapnp. But, since I already had isapnp running and working at start up, I configured alsa to *not* use its own pnp module (and you must explicity state this when running configure, because it defaults to yes for using the pnp module. If you try to use ALSA's pnp module and the standalone isapnp program, the sound will not work at all (at least in my case).). To be more concise, I simply installed ALSA as instructed in the INSTALL file that comes with the alsa tarball. Another quick aside: when you run the snddevices script that comes with the ALSA distribution, it changes the owner of the various audio devices to user root and group root. Normal users will not be able to use the audio devices, unless you change permissions, or ownership. I simply changed the group to audio and added myself to the audio group. For the slab version, I just got the following tarball: slab-3.0-1b.tar.gz. The default scripts have slab setup in /usr/slab, but I just installed in my home directory. Naturally, I had to modify the startup scripts (there is a bash startup script and a csh startup script; you can use either). An important point is to make sure that Slab does the xrdb -merge $SLAB_HOME/.Xresources or Slab will not work correctly. The first time SLab is run, it will ask you to config your soundcard. If you have only one soundcard, and have it working properly with ALSA, then you need only configure Audio Device 1 (main output) and Mixer. In the first field, I simply put /dev/dsp and for the second field, I have /dev/mixer and I indicated Full Duplex by clicking on the Full Duplex button. (According to the SLab documentation, you may have multiple audio devices; I don't know how hard this would be, but my roommate it getting a new soundcard, and I might buy his old SB16 just to try using multiple devices.) As far as the actual recording, it's a bit tricky to describe. Once you have the sound devices configured correctly, the built-in Help documentation is actually fairly useful. Check out the topic called recording, in particular. If you play with this software enough, you can achieve impressive results. Using only my ultra cheap microphone that came with my soundcard (sitting it in front of my guitar amp), I can record very clear sound. If anyone needs any more details on setting up ALSA and SLab, feel free to ask. I'm still in awe that I got the stuff to work :) Matt -- Matt Garman, [EMAIL PROTECTED] They're always havin' a good time down on the bayou, Lord, them delta women think the world of me. -- Dickey Betts, Ramblin' Man
Re: alsa drivers and slab
On Thu, Feb 04, 1999 at 10:27:59AM -0600, Matt Garman wrote: Has anyone been sucessful using the Advanced Linux Sound Architecture (ALSA) drivers in FULL DUPLEX mode with the program slab? I have a SB AWE 32, wich is currently working great with the stock OSS kernel drivers (and isapnp), but these drivers are only good for half-duplex. I'll answer my own question here, in case anyone is ever interested in this. With my SoundBlaster AWE 32 p'n'p, I can use SLab in full-duplex mode, that is, use my computer to record as many tracks as my hardware will allow! It's AWEsome (pun intended).
alsa drivers and slab
Has anyone been sucessful using the Advanced Linux Sound Architecture (ALSA) drivers in FULL DUPLEX mode with the program slab? I have a SB AWE 32, wich is currently working great with the stock OSS kernel drivers (and isapnp), but these drivers are only good for half-duplex. The program slab appears to be a full-featured, software-type multitrack mixer/recorder. I want to cut some demos, and slab would be *perfect* for this, but there's no using in setting it up if I don't have full duplex drivers. Just curious if anyone has ever tried this. It's worth some experimenting, considering actual (hardware) multitrack recorders start around $300 (just for a four track!). Thanks! Matt -- Matt Garman, [EMAIL PROTECTED] They're always havin' a good time down on the bayou, Lord, them delta women think the world of me. -- Dickey Betts, Ramblin' Man
Problem while installing alsa drivers (next)
re :) Well situation isn't seems to be as dramatic as i think. Sb_init command seems to work properly, it will say that my card is detected corectly... The problem seems to be when card need to be located, I'm not sure to have corectly configure isapnp.conf '(IO x (Base))' command, i want my card to be located at 0x220 or 0x240 adress. If someone can help :) Bye -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
