HD Install :: Boot with alsa on HD install???

blackfrog,
You have done well to troubleshoot your audio hardware resource settings.
It's worth noting that your eventual success was probably due to NOT including certain module parameters - dma16/mpu_io/esstype/isapnp.
The dma16 setting, especially, may have caused lack of output because your soundcard might not be full-duplex.

Another point - I don't believe your boot parameter "alsa" is achieving anything - because the driver module you have (successfully) configured has nothing to do with ALSA. It's loading the OSS sb driver. ALSA drivers all have the "snd-" prefix. Yours would be snd-es18xx.
It might be worth checking that your sound is playing at the correct speed (mine wasn't with OSS drivers) but otherwise your sound card is "happy" under OSS, so there's no need to install ALSA. But if you want to try ALSA, it's available for download as a mydsl package. No need to compile it or obtain via apt-get.

Actually, the "dsl alsa" boot command DOES do something.

It prevents the autoloading of the default OSS sound drivers.

Typing "dsl alsa" without actually using the alsadebs.dsl extension will produce almost the exact same effect as typing "dsl nosound" or "dsl noaudio".

If DSL is loading incorrect OSS drivers, then you should continue to use either "dsl nosound" , "dsl noaudio" , or "dsl alsa" and then load the correct driver after bootup either via manual typing or via /opt/bootlocal.sh script.

cbagger01, thanks for the info about "noaudio". I just read through the main bootup script and I see that it instructs hwsetup to ignore audio devices. Very useful.
I suppose the other possible way of fixing an incorrectly loaded driver would be to unload it first?

By trying to talk blackfrog out of using the "alsa" boot option, my less-than-positive attitude towards the Knoppix alsa-autoconfig script is showing. No need for anyone to rush to its defence, I know it suits many people.

bookmark

original here.