You may be in the same boat as I am. I am trying to install the Linuxant driver for my Conexant card. I can only compile successfully with this script using -s, otherwise I get the same error I get with the .deb of the Linuxant driver. The driver also comes as a patch, but it only applies successfully to the stable version of ALSA.
The patch seems to claim that it is GPL; I wonder why it isn't in ALSA by default.
I don't think it's a driver issue on my end anymore. I can get some audio out of the analog ports on my card with the realtek driver as well as the standard alsa driver (unfortunately it is at a terribly low volume and distorted). I can't even compile the driver (not using this script) in Maverick. But, it compiles fine in Lucid. Both installs yield the same buggy analog results though.
Hi all,
Am having a problem with alsa on 2.6.32-25-generic kernel. started wit yavdr 0.3 and did a dist upgrade and got the new kernel.
So after a few hours of removing alsa-dkms and backports. I used the script provide here with the -s option to install the alsa driver.
the card is seen and the module is loaded but the aplay say no card available
alsa info locate here
http://www.alsa-project.org/db/?f=7a...296882b148e23c
anyone any ideas.
Chris
This upgrade failed for me.
See here:
Code:/usr/src/Alsa-1.0.23/alsa-driver-1.0.23/include/config1.h:175: warning: "CONFIG_SND_HDA_INPUT_BEEP_MODE" redefined ./include/generated/autoconf.h:2222: note: this is the location of the previous definition /usr/src/Alsa-1.0.23/alsa-driver-1.0.23/acore/pcm_native.c: In function ‘snd_pcm_hw_params’: /usr/src/Alsa-1.0.23/alsa-driver-1.0.23/acore/pcm_native.c:489: error: implicit declaration of function ‘pm_qos_remove_requirement’ /usr/src/Alsa-1.0.23/alsa-driver-1.0.23/acore/pcm_native.c:492: error: implicit declaration of function ‘pm_qos_add_requirement’ make[3]: *** [/usr/src/Alsa-1.0.23/alsa-driver-1.0.23/acore/pcm_native.o] Error 1 make[2]: *** [/usr/src/Alsa-1.0.23/alsa-driver-1.0.23/acore] Error 2 make[1]: *** [_module_/usr/src/Alsa-1.0.23/alsa-driver-1.0.23] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.35-22-generic' make: *** [compile] Error 2 *************************************************************************** * alsa-driver-1.0.23 make failed ***************************************************************************
The compilation step would not proceed and now the ALSA info script output is:
Code:ALSA Information Script v 0.4.59 -------------------------------- This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See 'alsa-info.sh --help' for command line options. cat: /proc/asound/version: No such file or directory grep: /proc/asound/cards: No such file or directory cat: /proc/asound/cards: No such file or directory cat: /proc/asound/modules: No such file or directory ls: cannot access /dev/snd/*: No such file or directory grep: /proc/asound/cards: No such file or directory /sbin/alsactl: save_state:1504: No soundcards found... cat: /tmp/alsa-info.iWezHwJd8O/alsactl.tmp: No such file or directory Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa-project.org/db/?f=9fbbe4189007e384ac6d9a5abdff51cac0e51797
Ubuntu 23.10
The script does not work on Maverick unless you use the -s option to grab a snapshot. Maverick already has the latest ALSA release anyway..
Any suggestions on how to recover from this?
Ubuntu 23.10
Hmm... I know this is somewhat tangential to this thread, but I wonder if I could apply the Linuxant patch to the source code of Ubuntu's default ALSA. I have the alsa-source package installed, but I'm not sure how to patch or compile it, as it doesn't seem to have the same directories as the source code downloaded by this script.
And so, in the end, my problem was fixed by other means.
I addedto /etc/modprobe.d/alsa-base.conf and installed updated ALSA modules as per this page.Code:options snd-hda-intel model=ideapad
The latter is probably what fixed my problem, but I'm not completely confident in my restarting of ALSA/pulseaudio while fiddling with the alsa-base.conf options (I did not reboot until the module upgrade).
Sorry for the noise, but hopefully this helps someone.
Bookmarks