Configuration of the old sound card in Linux

Article title: the configuration of the old sound card in Linux. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
There are a lot of articles on sound card configuration in Linux. if you are not very experienced, they will help you a lot. Linux supports far fewer sound cards than Win9x. even if the manufacturer provides Linux drivers, it is difficult for common users to install them. I spent almost a month researching and experimenting with driving an ALS007 sound card. when I heard it for the first time, you couldn't imagine how much I felt! How happy it would be if you had a piece of SB16?
　　
At first I installed Redhat Linux 6.0, which correctly detected the ALS007 sound card chip, but reported errors regardless of automatic or manual configuration. conf and isapnp. I tried to change the conf file, but it was not successful once! To this end, I learned to use a complex vi editor. Address, interrupt, and DMA are nothing more than just a few parameters. it is useless to try them one by one. I read one article after another in the English HOW TO article, which is useless. The message "Invalid parameter-mpu_irq" appears many times during the startup process reminds me: is there a BUG in its driver? ALS007 calls the sb. o module because it is declared to be compatible with SB16. I chose SB16 for a test and it is still incorrect. Does it prompt that my mpu_irq is invalid? I will delete it. what do you say! Delete mpu_irq = 9 in the last line of modules. conf. Restart, go to KDE, and open the MIDI player. unexpectedly, I heard the sound! I saw the desired deployment! Looking for a few WAV files to put, still not good, sticky, there seems to be a device conflict. It is useless to change it again and again. The same problem is still caused by the installation of the 1.0 red flag. I am unwilling to surrender. I continued to look for articles (all on my computer). one day I caught a surprise with a few words in a long article! Find the DOS driver package of ALS007. It adds c: \ alsound \ alinit c \: windows in the batch file autoexec. bat. Alinit is the sound card initialization program, which sets the DOS environment variable of the sound card. Run the SET command to view the environment variables. an additional line is displayed: BLASTER = A220 I5 D1 H5 P330 T6. People who have been rolling from the DOS era should not be familiar with them. I wonder that it is actually useful to my Linux system! In DOS, use the loadlin program to guide Linux, execute sndconfig -- noprobe, and select SB16. Unexpectedly, the harsh sound from two plastic speakers gave me an excited shout and finally succeeded! This is the result I spent nearly a month working on. it's so easy! Reboot and try again. normal! Shut down, boot, and enter Linux, and the ugly error message is coming again. Press Crtl + Alt + Del to restart and enter the DOS of win98. this is to obtain the DOS environment variable of ALS007, hot start, and Linux. OK! I'm sure the Linux driver of ALS007 depends on its DOS environment variable!
With this experience, it is really easy to configure RTA3000 (with the ALS120 chip) and Sun Flower 3D Storm card!
Key points:
1. obtain the configuration parameters under the sound card DOS;
2. set the DOS environment variable, which is automatically set by the sound card initialization program;
3. during hot boot into Linux, automatic detection is skipped when the sound card is set, that is, sndconfig -- noprobe is executed, SoundBlaster 16 is selected as the type, and the set parameter is the same as DOS.