how do i force alsa to reconfigure to new hardware after moving drive to new machine?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Back in Penny Lane, I failed to reproduce PCM w/ huge kernel. Apparently I mixed it w/ a now erased partition an Ubuntu based distro and pulseaudio, not ALSA. My apologies If I misled you in any way. Getting older *sigh*
You could remove the /var/lib/alsa/asound.state as suggested by Allend, and then remove the alsa-utils package (with removepkg), and then compile alsa from source on your system (there is a more recent source at alsa-project.org).
ok, so here's the screenshot you keep asking for.... no national security issues here.... unless you try to sell my screenshot to north korea.... as you can see, a PCM control is present, and if you look at what i posted in post #4, PCM is the capture source.... this is why i am getting a bit confused as to why this isn't working... everything says it's supposed to work.... but it's not... i also have PulseAudio running, and i'm wondering if either a) it's what's causing the software to not connect to the capture source, or b) it can be used to provide the audio for the software i'm using (fldigi, both the native linux version, or the windows version running under wine... same issue with both)
pulseaudio is at present unconfigured
Last edited by unclejed613; 12-03-2013 at 09:22 PM.
bash-4.1$ cat /proc/asound/pcm
00-00: ALC888 Analog : ALC888 Analog : playback 1 : capture 1
00-02: ALC888 Analog : ALC888 Analog : capture 1
i'm not trying to rip or record the audio, i am trying to allow programs to process it, for instance an audio stream of FSK (radioteletype audio) or morse code, and turning it back into readable form. keep in mind, this WORKED when i was running on a machine with an SIS chipset, but is now NOT working after transferring to a machine with an intel chipset.
also, please understand i didn't see the point in the screenshot, since the capture sliders on the display don't identify what input the capture is linked to. somehow the system sees the capture input as "pcm" but for some reason isn't actually using "pcm" as the capture input.... either there's a problem with a configuration file, or there's a problem with how the hardware actually works... this is what i'm trying to sort out. right now i'm leaning towards putting in a sound card that has the functionality i'm looking for... my concern here is that Realtek (the actual manufacturer of the audio hardware) seems to strive for Windoze-Only functionality, and when belatedly releasing linux drivers, supplies them as "crippleware".... they have a very long history of this. if you look back at devices called "winmodems", you will see what i mean.... winmodems were modems made with soundcard architecture, and drivers supplied only to micro$oft, and realtek was one of the largest suppliers.
actually i mentioned it in post 1, but didn't explain what the software does..... it's actually doing quite a lot of things with the audio data at the same time, such as providing an audio spectrum analyzer function, and acting as a modem. and the modem function is very similar to the way a DSP-based phone modem works. as a matter of fact, internal modems in PCs are tied to the sound card hardware. the difference is that the ham radio software uses many different communication protocols, some much simpler (morse code, FSK, etc) and some much more complex (MT63, MFSK16, SSTV, etc...). you can find a few listed (along with sound clips of what they sound like) here: http://wb8nut.com/digital/
these programs are intended to do all of this in real time, whether from a line input (if i had it actually hooked up to a radio) or from a live stream (there are tunable receivers on the web that stream audio, some even have transmit priveleges for licensed ham operators). before i switched to this machine (still using slackware), i was able to capture audio from the PCM device when i was on a web radio, tune the radio to the desired receive frequency, and decode from the live stream. since moving to the new machine, this does not work anymore, so something must be amiss with the asound configuration, or the internal (hardware) mapping of the devices.
so now i have a question for you... when you play those wav files, can you look at them on a spectrum analyzer program (which is another example of the type of software with it's usage of the PCM device)?
also, does slackware have a tool i don't currently know about that does a menu based config for asound? this would be similar to the "netconfig" tool... if it exists
if you are not using slackware, then why are you wasting my time??????
this IS, after all the slackware subforum, and there are quite a few differences in the way slackware is set up vs debian..... if i wanted help with debian i would have gone to the debian subforum....