Hmm... I used the "alsasound start" command and it came back with:
.Starting sound driver: snd-cs46xx
So it appears to have started a non-running sound driver for my internal sound card chipset (of all things). Now when I fire up FlDigi and go to the configuration settings, the "File I/O only box" is still checked, but there is now a device listed in the OSS device box as "/dev/dsp"
I am assuming that If I now check the OSS box it uses the snd-cs46xx driver?! Since there had never been anything populated in this box before, it seems logical that this is the case.
However when I reboot the system and check FlDigi again the "/dev/dsp" is missing until I go run the alsasound start command again. Soooooo.... how do I get the alsa sound driver to start autoMAGICally when the system boots?
I can't have a bunch of whiny windoz teenage ham students trying to start a sound driver from root each time they start their session. Heck, it's bad enough that I have to figure out FlDigi for the first time. I had always been using simple HRDelux on my personal system and this is a little different (but much more satisfying
)
Gerald - thanks for giving the clueless a clue!
BKM