Its about time someone put an EASY, step-by-step on how to get the sound on a 600E working. It doesn't bother me one bit that these instructions are for my distro
The best news of all, of course, is that it debunks the wild myth that you have to recompile your kernel to make the sonofagun work. The stock kernel on most major distros will work fine.
I have to add some thoughts of my own... There actually is a slightly
easier way to do it, and bluenevus didn't include all of the module parameters that you may need (there is also a teeny-weeny typo in his instructions that can flub you up).
Use the GUI! I have absolute respect for the command line and manually editing config files when it is necessary
, but why drive myself crazy when there is a super-cool GUI tool to do the hard stuff for me?
In yast2>Hardware>sound the sound will be (predictably) incorrectly detected as a cs4610 instead of the cs4236.
If you click on the edit button, then (if prompted) select the advanced option, a window will pop up TELLING you that the sound card is often (read: always) detected improperly on a 600E and asking if it should try to use the 4236 driver. Tell it yes, then in the advanced options, you will have a GUI to set all of the required module parameters, which should be as follows:
Description Option Value
Control port # for CS4236+ driver cport 0x538
DMA1 # for... dma1 1
DMA2 # for... dma2 0
FM port # for... fm_port 0x388
IRQ # for... irq 5
ISA PnP detection for... isapnp 0
MPU-401 IRQ # for... mpu_irq 9
MPU-401 port # for... mpu_port -1
Port # for... port 0x530
SB port # for... sb_port 0x220
You will notice that I have a different FM port address than bluenevus. The one I used is the correct one. Apparently he made a type-o, because every resource on the web that addresses this issue lists the FM port address as 0x388, not 0x338.
Then you may have to do some tinkering with kmix (or your mixer of choice) to get everything singing like it should.
As alluded to by bluenevus, the OSS version of SUSE is missing a lot of the libraries that you need for MP3 playback and a lot of the other fun stuff, but simply adding the typical repository collection to your yast sources and installing the missing parts will get you up and running fairly painlessly (that is a discussion for another thread).
Most major distros will have some type of GUI tool that you can use to set this up that is similar to the one I describe in Suse. If yours doesn't, just add the info to your modules.conf/modprobe.conf/whatever your distro calls it! Just be sure that you are not modifying a file that will be overwritten by your automated update system, like Suse is prone to do. If you opt to do all of this manually in Suse, be sure to put the lines in modprobe.conf.local and NOT
In fact, I think I will combine/smooth out these two posts a little bit and look into writing an article for those who need it. An article like that is LONG overdue!!!