trying to load sound module
Although I've been using Debian for over ten years, I don't consider myself a guru, so I'm hoping that some real gurus will jump in here and help me out. ;)
I'm running wheezy with the 3.0.0.1 kernel on a P4 3.0GHz machine, and I'm wanting to install a sound card called an Echo Layla 24 (a card/interface used for multi-track recording). The module is snd-layla24 which is in the kernel, but I'm having a heck of a time getting this to work. The card is a few years old and most of the online documentation is old as well, including the installation docs at alsa-project.org. Here's what I have so far: Code:
Revolver:/home/rl5# lspci Quote:
Code:
Revolver:/home/rl5# modprobe s <tab> And when I try aplay: Code:
Revolver:/home/rl5# aplay -l I added the module to /etc/modules like so: Code:
/etc/modules SO can anyone tell me why this module is not loading, and what I can do to fix it? I would be greatly appreciative! :) |
hi
I am not an expert....being Debian the thing that crossed my mind is firmware. 2) can you post this section of your /boot/config-kernelversion pls as that might suggest .....you have no firmware loader support in your current kernel...or firmware is being prevented in being built....for a newer firmware you can install from alsa-project.org ------------- # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y # CONFIG_FIRMWARE_IN_KERNEL is not set CONFIG_EXTRA_FIRMWARE="" 3) I have read your alsa-project link....but you have not reported ALL steps you attempted for their doc It is clear aplay -l is not good 4) In the meantime....getting info out of log is good Can I suggest you first add your module with root powers to the blacklist at /etc/modprobe.d/alsa-base-blacklist.conf with entry like so blacklist snd-layla24 Note we use hyphen and not understem reboot and run lsmod...mod must not load now with root powers run modprobe snd-layla24 lsmod if it loads now post the section of /var/log/messages relevant to our loading pls good luck |
oh I have trouble with my browser so forgive lack of edit
before you try above stuff download this file http://www.alsa-project.org/alsa-info.sh as a local user run Code:
chmod +x utils_alsa-info.sh now run it as a local user...keep it local stored then post to http://ompldr.org/ (no expiry) or http://paste.debian.net/ and choose 72 hours or never (your choice) I am particularly interested in whats in your asoundrc or module.conf type file for the alsamixer issue as well as the other juicy stuff. b) then run the blacklist / modprobe stuff with log output. as that log is smallish...post here I forgot to mention before blacklisting run lsmod > /home/(yourname)/lsmod1 then blacklist etc lsmod > /home/(yourname)/lsmod2 are they the same?....xxdiff will tell you .... Code:
xxdiff lsmod1 lsmod2 |
Thanks for helping out! :D
Quote:
http://ompldr.org/vYXl2Ng/alsa-info.txt.oxEGP02Y39 Quote:
http://ompldr.org/vYXl2YQ/modules.conf Quote:
And as a bonus: Code:
# Device Drivers Quote:
http://ompldr.org/vYXl2dA/lsmod3 Quote:
Code:
Oct 25 00:16:23 Revolver kernel: [ 9.283264] Echoaudio Layla24 0000:02:09.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 Code:
Oct 25 00:36:52 Revolver kernel: [ 6.773740] Echoaudio Layla24 0000:02:09.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 |
ok there are few things we need to get out of the way lets go for the main one....your hardware listing.
the alsa.sh file confirms you do not have a config in any module conf file or asoundrc etc (I was not actually asking for you to do extra but I do appreciate your enthusiasm. I will look at why your blacklist failed later ok 2) I do not use firmware and do not have (below) folder ....I use a Debian sid so do not have /lib/alsa/modprobe-post-install AND there is bug for those distros still using it and using udev.....they conflict as per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518242 Quote:
Driver version: 1.0.24 Library version: 1.0.24.1 Utilities version: 1.0.24.2 ok first try turning off that post script Code:
sudo su INTENTION We need to stop that alsa post install script first Now reboot and check aplay -l udev should give you the correct hardware settings but if not we may have to create an asoundrc....you already know how to do this....your link to alsa-project page. good luck |
ok that last bit might be considered rude eh?
so a little secret ...I don't use any asoundrc or modprobe.conf just edit with root powers your /etc/modprobe.d/alsa-base.conf YMMV mine reads http://ompldr.org/vYXowZA/alsa-base.conf yours will read....if needed...if the disabling of your post install fails http://ompldr.org/vYXowZw/layla but you use root powers to edit those last lines. as a backup and assuming you have a live cd and know how to get back to the net....post your current alsa-base.conf file here before rebooting and keep a local copy somewhere like /home/yourname so what we are trying to do is eliminate extra scripts interfering with our normal alsa stuff if that works run the alsa.sh script to check its contents if if fails then use root powers to edit your alsa-base.conf to include more hardware stuff for Alsa to get its teeth into good luck |
I appreciate all of your help... I only wish I had some good news to report. :(
Code:
find / -name modprobe-post-install Quote:
Code:
Revolver:/home# aplay -l Quote:
It's still not finding the lalya module... I'm tempted to purge all alsa apps and start over! :scratch: |
ok well thats weird you can't find it going back to your link
http://ompldr.org/vYXl2YQ/modules.conf its mentioned eg.....post-install snd-layla24 /lib/alsa/modprobe-post-install snd-layla24 so go to file manager and peek into that lib folder pls run file against it to see if its executable or run Code:
/lib/alsa/modprobe-post-install run it..... after it loads click on the pulldown and choose "installed" then run search string "alsa" in the results click on each alsa and right tab for Files......this should reveal where that pesky post-install stuff is 3) you could remove your debian packages and install the alsa projects's to eliminate other sound devices pls list any connected devices that use sound at time of boot up pls eg mobile phones modems mp3 players usb sound mixers etc ---------- Post added 27-10-11 at 07:27 ---------- ok well thats weird you can't find it going back to your link http://ompldr.org/vYXl2YQ/modules.conf its mentioned eg.....post-install snd-layla24 /lib/alsa/modprobe-post-install snd-layla24 so go to file manager and peek into that lib folder pls run file against it to see if its executable or run Code:
/lib/alsa/modprobe-post-install run it..... after it loads click on the pulldown and choose "installed" then run search string "alsa" in the results click on each alsa and right tab for Files......this should reveal where that pesky post-install stuff is 3) you could remove your debian packages and install the alsa projects's to eliminate other sound devices pls list any connected devices that use sound at time of boot up pls eg mobile phones modems mp3 players usb sound mixers etc |
ahhh my browser
forget that code box its missing ls -al try Code:
ls -al /lib/alsa/modprobe-post-install |
oops I forgot to mention you need root powers to run that find command
|
Quote:
Not sure why post-install shows up in modules.conf - I just checked again and it is still listed there. Quote:
BTW, I have been keeping up with recent updates from Debian - could a recent update have removed it? Quote:
Quote:
|
yeah well I am not sure why the alsa.sh stuff link is reporting that post alsa stuff.
2) err also I lied to on my own config. I use /etc/modprobe.d/alsa-base.conf but the correct info should read # my configs options snd-hda-intel model=5stack your card will differ. 3) OK I run sid packages. if interested and forgive me if you don't want to try it....consider removing your current packages and installing "sid" packages. However, I run a pure sid so in pulling in sid to a stable system it might break? Therefore can I suggest you place copies of the files you are going to change on removable media and know how to boot into single or use a live cd pls Here is ONE howto do it. http://wiki.debian.org/AptPreferences /etc/apt/sources.list.d/debian.lst deb http://ftp.iinet.net.au/debian/debian sid main contrib non-free ---------- Post added 28-10-11 at 13:32 ---------- yeah well I am not sure why the alsa.sh stuff link is reporting that post alsa stuff. 2) err also I lied to on my own config. I use /etc/modprobe.d/alsa-base.conf but the correct info should read # my configs options snd-hda-intel model=5stack your card will differ. 3) OK I run sid packages. if interested and forgive me if you don't want to try it....consider removing your current packages and installing "sid" packages. However, I run a pure sid so in pulling in sid to a stable system it might break? Therefore can I suggest you place copies of the files you are going to change on removable media and know how to boot into single or use a live cd pls Here is ONE howto do it. http://wiki.debian.org/AptPreferences /etc/apt/sources.list.d/debian.lst deb http://ftp.iinet.net.au/debian/debian sid main contrib non-free |
eek I forgot to tell you that you should try to remove...don't remove libasound2 as it removes too much IMHO
Code:
su |
Quote:
|
no only a suggestion it is less compiling.
if you are happy to download unpack and configure using the correct parameters to enable your device feel free. I am lazier (winks) |
All times are GMT -5. The time now is 11:24 PM. |