[ltp] no sound under linux on 600e

tmfu linux-thinkpad@linux-thinkpad.org
Sun, 08 Dec 2002 15:29:23 -0500


Dan Sawyer wrote:
> All,
> 
> The system is a 600e with a 4610/11 reported. Sound works under Win 
> however it does not work on the 600e.
> 
> I would appreciate a copy of the /etc/modules.conf setup that works for 
> the 4610 reported in /etc/...
> 
> Thanks,
> Dan
> 

To /etc/modules.conf, add:
----
alias sound-slot-0 cs4232
options sound dmabuf=1
alias midi opl3
options opl3 io=0x388
options cs4232 io=0x530 irq=5 dma=1 dma2=0 mpuio=0x330 mpuirq=9
----
  Create /etc/isapnp.gone:
----
# COM1
# MGA: you can comment out COM1, not much diff
IO 0x3f8,8
IRQ 4
#
# COM2
IO 0x2f8,8
IRQ 3
#
# Parallel
IO 0x378,2
IRQ 7
#
# PS2 mouse
IRQ 12
#
# Sound
##IO 0x220,16
IO 0x530,4
IO 0x538,4
IO 0x388,4
IO 0x220,4
IRQ 5
IRQ 9
DMA 1
DMA 0
----
  Create the following file, as /etc/rc.d/init.d/cs4232
----
#!/bin/bash
# chkconfig: 345 84 16
# description: Starts/stops the CS4232 driver at boot time and shutdown
HOME=/etc
case "$1" in
start)
echo "Starting CS4232 driver"
rmmod cs4232
modprobe cs4232
;;
stop)
echo "Stopping CS4232 driver"
rmmod cs4232
;;
restart)
$0 stop
$0 start
;;
status)
echo "Status (NO-OP)"
;;
*)
echo "Usage: cs4232 {start|stop|status|restart}"
exit 1
esac

exit 0
----
  Create some links to this file, to run it when runlevel changes:
  cd /etc/rc.d/rc3.d/
  ln -s /etc/rc.d/init.d/cs4232 S83cs4232
  cd /etc/rc.d/rc5.d/
  ln -s /etc/rc.d/init.d/cs4232 S83cs4232
  Now do a reboot, and test:
  play /usr/share/sounds/info.wav
  play /usr/share/sounds/startup3.wav
  I still see error messages in /var/log/messages:
   kernel: ad1848: Interrupt test failed (IRQ5)
  but everything seems to be working. Now you can listen to streaming 
audio on the web, via Real Player.

If sound stops working, reload the module:
  /sbin/rmmod cs4232; /sbin/modprobe cs4232


Hope this helps. I too have a TP600E. I actually have everything 
working(MWave modem included ). If you need anymore help just ask.
Also under DOS/Windows make sure using PS2.EXE to check your settings.



-- 
Greg