Fujitsu-Siemens S-4572

LCO's Notebook

Model: Fujitsu-Siemens S Series Lifebook S-4572

Distribution: RedHat 7.1 with Ximian Gnome.

Disk Partitioning

The machine had originally two partitions: a 2GB (c:) FAT and a 17GB (d:) FAT32 partition. Since I wanted a dual-boot machine, I decided to resize and reformat the Windows partition and install the RedHat distributions on logical partitions:
Disk /dev/hda: 255 heads, 63 sectors, 2432 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1      1345  10803681    c  Win95 FAT32 (LBA)
/dev/hda2          1346      2432   8731327+   f  Win95 Ext'd (LBA)
/dev/hda5          1346      1856   4104576   83  Linux
/dev/hda6          1857      1922    530113+  82  Linux swap
/dev/hda7          1923      2432   4096543+  83  Linux

Network Configuration

The Intel network interface was detected by the instalation procedure and all the necessary files were copied to disk. If everything went fine you should have this line in /etc/modules.conf:

alias eth0 eepro100

USB Configuration

To my surprise, this RedHat distribution found and configured the machines USB chipset (as opposed to 7.0 that did not worked on my previous machine: an S-4510). The configuration essentialy added a line to /etc/modules.conf:

alias usb-controller usb-uhci

X Configuration

The X configuration program was able to identify the correct chipset (ATI Rage Mobility) and display (1024x768).

USB Mouse

The only trick I had to perform was to add another mouse so that I can use either the touch pad or the USB mouse. This is a must in this machine since it only has a ps/2 connector in the docking port.

Having two mice in X requires some additional lines in /etc/X11/XF86Config-4 file. First you must add the second mouse to the ServerLayout section and specifying that it sends core events:

Section "ServerLayout"
        Identifier     "Anaconda Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "USB Mice" "SendCoreEvents"
        InputDevice    "Keyboard0" "CoreKeyboard"

A little further in the XF86Config-4 file it is necessary to add the description of the new input device:

Section "InputDevice"
        Identifier  "USB Mice"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Buttons" "5"

The protocol IMPS/2 is for the thumbwheel of my Targus USB-PS/2 scroller mini-mouse, you may have to adjust it for your own mouse protocol.

Audio Configuration

The audio hardware of this notebook is a "Intel 82440MX AC'97 SigmaTel Codec" (the same as for S-4510 and S-4546). The OSS-Lite driver for this chip that is distributed with RedHat 7.1 does not allow any other sample rate than 44100 Hz. This is ok if you only need to play a few sound files with the play command or if you want to listen to mp3 files through xmms or a similar program. I have not tested it extensively but a colleague reported some hangings with this audio driver.

If, like myself, you need to use other sound processing programs, the solution is to use the ALSA project's driver for intel8x0. So, I downloaded the latest 3 packages:


It is necessary to compile and install the packages in order: first the driver, the library and finally the utilities.

To unpack them I used "tar xfI " and built the RedHat RPM's for my architecture by running "cd /utils; buildrpm":

$ 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:



case "$1" in
                  # store driver settings
                  if [ -x $alsactl ]; then
                      $alsactl store
                  echo -n -e "${rc_warning}!!!alsactl not found!!!${rc_reset} "
		  /etc/rc.d/init.d/alsasound stop
		  ESDPID=`ps -auxww|grep ' esd'|head -1|cut -c12-16`
		  kill $ESDPID
		  /etc/rc.d/init.d/alsasound start

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
Fujitsu-Siemens S-4572

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:

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.


And now the bad news... The S-4572 has a Lucent/Agere AMR modem which means no Linux support. The AMR version, as opposed to the LB Global LTMODEM of the S-4542, does not have a DSP chip required by the LTModem drivers (see and