$ cd alsa-driver-0.5.10b/utils; buildrpm ... $ rpm -U /usr/src/redhat/RPMS/i386/alsa-driver-0.5.10b-1.i386.rpm $ cd alsa-lib-0.5.10b/utils; buildrpm ... $ rpm -U /usr/src/redhat/RPMS/i386/alsa-lib-0.5.10b-1.i386.rpm $ cd alsa-utils-0.5.10b/utils; buildrpm ... $ rpm -U /usr/src/redhat/RPMS/i386/alsa-utils-0.5.10b-1.i386.rpm
The next step was to add the drivers to /etc/modules.conf:
# Alsa Sound - Intel8x0 alias char-major-116 snd alias char-major-14 soundcore alias snd-card-0 snd-card-intel8x0 alias sound-slot0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-12 snd-pcm-oss
The last step was to start the driver:
/etc/rc.d/init.d/alsasound start
You may also want to had alsa sound to init levels 3 and 5:
chkconfig --level 35 alsasound on
The driver starts with all the mixer channels muted. It is necessary to use a program like gmix to raise the gains.
To be able to use the suspend mode it is necessary to remove all alsa modules before suspending and to re-install them when resuming. This can easily be configured by creating an apmcontinue script in /etc/sysconfig/apm-scripts/apmcontinue:
#!/bin/bash
alsactl=/usr/sbin/alsactl
case "$1" in
suspend)
#
# store driver settings
#
if [ -x $alsactl ]; then
$alsactl store
else
echo -n -e "${rc_warning}!!!alsactl not found!!!${rc_reset} "
fi
/etc/rc.d/init.d/alsasound stop
#
ESDPID=`ps -auxww|grep ' esd'|head -1|cut -c12-16`
kill $ESDPID
;;
resume)
/etc/rc.d/init.d/alsasound start
;;
esac
A problem that I have not yet solve is when the suspend mode is activated while the audio drivers are in use. This prevents the removal of the drivers and
IR Configuration
The problem with the configuration of the IR interface was that the chipset is not yet supported under Linux. The command 'findchip -vd' does not seems to find any supported chip and the solution was to stick with the SIR mode. This limits the performance of the IR link to 115000 bps but I do not have any other alternative to synchronize my Palm Pilot. BTW the S-4510 had a serial connector on the notebook but the S-4572 only has USB connections: you need the docking port to attach a serial device...
To enable the SIR mode you need to change the BIOS settings and change the FIR (Fast IR) selection. After that you will notice that the kernel, while booting (dmesg | grep tty), detects another serial interface (ttyS03) - this is not a real wired interface like ttyS00, but the IR interface. You should look for the irq and port address since you need them to add a few lines to /etc/modules.conf:
# Irda drivers alias tty-ldisc-11 irtty alias char-major-161 ircomm-tty alias irda0 irport options irport io=0x2e8 irq=3
and start irda:
# /etc/rc.d/init.d/irda start # chkconfig --level 3,5 irda
If you want to pilot-xfer you should also create a symbolic link on /dev:
# ln -s /dev/ircomm0 /dev/pilot
CD-RW Drive
Since you need the docking port to connect the floppy drive, having a CD-RW is a good thing if you want to transfer data while on the road.
The configuration of the CD-RW envolves adding some lines to /etc/modules.conf:
# IDE CD-RW options ide-cd ignore=hdb alias scd0 sr_mod pre-install sg modprobe ide-scsi pre-install sr_mod modprobe ide-scsi pre-install ide-scsi modprobe ide-cd
VMware configuration
I am using vmware workstation 2.0 to be able to use Linux and Windows 2000 simultaneously. The installation of the Windows 2000 virtual machine give me some trouble because I wanted to use the real machine installation (dual boot). The first problem was VMware's lack of ACPI support, however this is well documented in the VMware site: it is necessary to have a dual w2k boot, with and without ACPI suport in the kernel.
The other problem was related to InteliStep that does not work in the VMware virtual machine and had to disabled. Since it has no way of finding in what machine (virtual or real) it is running, it has to be enabled by hand.
Another problem was VMware's lack of support for the ALPS GlidePoint touchpad. I had to change /etc/X11/XF86Config-4 and use a standard PS/2 protocol for the built-in mouse (touchpad).
The last problem was related with the IDE controller, that is different in the real and virtual machine. Because the instalation was performed on the real machine, the w2k boot stoped with a disk error when running in the virtual machine. The trick was to create an hardware profile just for the virtual machine and reboot the real machine with the virtual profile. I then changed the IDE controller driver AMD... . In the next boot of with the virtual profile inside the virtual machine w2k worked fine.
A problem that I have not yet solved is the lack of acceleration while running in full screen mode. It seems that the acceleration support is only available for the SVGA X driver and not for the ATI driver that I am using.