Difference between revisions of "Fujitsu-Siemens Amilo Pro2000"

From ArchWiki
Jump to: navigation, search
(TOUCHPAD: Remove out of date info.)
(WIRELESS LAN: Remove out of date info.)
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{out of date}}
 
[[Category:Fujitsu]]
 
[[Category:Fujitsu]]
 
This info may be helpful in addition to the Arch Linux Installation guide. This may apply fairly well to many other Amilo computers, for example to M7400 which has very similar hardware.
 
This info may be helpful in addition to the Arch Linux Installation guide. This may apply fairly well to many other Amilo computers, for example to M7400 which has very similar hardware.
Line 8: Line 9:
 
IrDA Fast Infrared, AC'97 Modem, PS/2 Keyboard & Synaptics Mouse, 3 USB ports, Firewire, 2 card slots.
 
IrDA Fast Infrared, AC'97 Modem, PS/2 Keyboard & Synaptics Mouse, 3 USB ports, Firewire, 2 card slots.
 
Network adapters:Broadcom 440x 10/100 and Intel PRO/Wireless 2200GB.
 
Network adapters:Broadcom 440x 10/100 and Intel PRO/Wireless 2200GB.
 
==ETHERNET==
 
 
add driver b44 to loaded modules in /etc/rc.conf
 
and to modprobe.conf, add
 
 
    alias eth0 b44
 
 
==XORG CONFIGURATION==
 
 
Using arch's HW detection: hwd
 
 
    pacman -S xorg xorg-server xterm aterm xf86-input-mouse xf86-input-keyboard xf86-video-i810
 
    pacman -S hwd
 
 
With xorg 7. the modularization means that you have to get some packages extra apart from xorg in order to be able to load the i810 module.
 
 
This will write a new xorg.conf:
 
 
    hwd -xa
 
 
Or you could use the safer way to write a sample-file called xorg.conf.hwd:
 
    hwd -x
 
 
This is an example of the monitor and card parts of an xorg.conf file that works:
 
 
  Section "Device"
 
    Identifier  "Intel82852/855GM 0"
 
    Driver  "vesa"
 
    Driver      "i810"
 
    Option "MonitorLayout" "CRT,LFP"
 
    Screen 0
 
    BusID "PCI:0:2:0"
 
  EndSection
 
  Section "Monitor"
 
    Identifier "Generic 0"
 
    Option "DPMS"
 
    HorizSync 28-64
 
    VertRefresh 43-60
 
  EndSection
 
  Section "Screen"
 
    Identifier "Default Screen"
 
    Device "Intel82852/855GM 0"
 
    Monitor "Generic 0"
 
    DefaultDepth 24
 
    SubSection "Display"
 
      Depth 1
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
    SubSection "Display"
 
      Depth 4
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
    SubSection "Display"
 
      Depth 8
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
    SubSection "Display"
 
      Depth 15
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
    SubSection "Display"
 
      Depth 16
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
    SubSection "Display"
 
      Depth 24
 
      Modes "1280x768" "1024x768" "800x600" "640x480"
 
    EndSubSection
 
  EndSection
 
 
After checking the file you can test it with:
 
    Xorg -config /etc/X11/xorg.conf.hwd
 
Close the X-server with Ctrl-Alt-Backsapce
 
If it works all right you make it the default one with the command:
 
    mv /etc/X11/xorg.conf.hwd /etc/X11/xorg.conf
 
 
 
If you want to have kde to start at boot then you add this as last command in rc.local
 
    /etc/rc.d/kdm start
 
 
==SOUND==
 
Check here for more info about how to set up sound:
 
http://wiki.archlinux.org/index.php/ALSA_Setup
 
 
The needed modules to add to rc.conf list of modules are:
 
  snd-intel8x0 snd-pcm-oss
 
 
Then get the packages needed:
 
 
    pacman -S alsa-lib alsa-utils alsa-oss
 
 
Use alsamixer to set the default volume, use "m" to mute and unmute. Write the defaults with:
 
 
    alsactl store
 
 
Add "alsa" to loaded daemons in /etc/rc.conf. Finally,add user to audio group:
 
 
    gpasswd -a username audio
 
 
More reading:
 
 
http://wiki.archlinux.org/index.php/Allow_multiple_programs_to_play_sound_at_once
 
 
http://wiki.archlinux.org/index.php/Sound_permission_denied
 
 
http://wiki.archlinux.org/index.php/Open_Sound_System
 
 
http://wiki.archlinux.org/index.php/ALSA_Setup
 
  
 
==TOUCHPAD==
 
==TOUCHPAD==
 
See [[Touchpad Synaptics]]
 
See [[Touchpad Synaptics]]
 
==ACCESS TO DEVICES==
 
 
Add user to groups (given you have created a user):
 
 
    gpasswd -a username video
 
    gpasswd -a username optical
 
    gpasswd -a username storage
 
  
 
==WIRELESS LAN==
 
==WIRELESS LAN==
 
This will (apparently) need a kernel higher than 2.6.10. Note that upgrading Arch 0.7 with pacman -Su will break the system unless the DevFS -> Udev transition is made after the install, see guidelines here: http://bbs.archlinux.org/viewtopic.php?t=15585). If you install from 0.7.1, you can ignore this problem.
 
  
 
For wireless, the relevant driver is ipw2200.  
 
For wireless, the relevant driver is ipw2200.  
Line 189: Line 71:
 
   dhcpcd eth1
 
   dhcpcd eth1
 
This script both select the right key and channel for the router and uses dynamic ip-addresses in order not to need thinking about DNS-server addresses etc.
 
This script both select the right key and channel for the router and uses dynamic ip-addresses in order not to need thinking about DNS-server addresses etc.
 
==USB==
 
 
Works normally. Create directory /mnt/stick, and add the following to fstab:
 
 
    /dev/sda1  /mnt/stick  vfat    rw,user,noauto,umask=0000    0    0
 
 
then the stick can be mounter by user with: mount /mnt/stick.
 
 
Another way is to use the autofs module:
 
  pacman -S autofs
 
More info you can get from:
 
http://wiki.archlinux.org/index.php/AutoFS_HowTo
 
 
That way you can get all usb-sticks, cd's and other stuff automatically mounted on connection. This is a configuration that works:
 
 
/etc/autofs/auto.master
 
    /media /etc/autofs/auto.media --timeout 3
 
 
/etc/conf.d/autofs
 
  # e.g. localoptions='rsize=8192,wsize=8192'
 
  localoptions=''
 
 
 
  # e.g. --timeout=60
 
  daemonoptions='-g'
 
 
 
/etc/autofs/auto.media
 
  cdrom -fstype=iso9660,ro,nodev,nosuid :/dev/cdrom
 
  usbG -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sda1
 
  usbH -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sda2
 
  usbI -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sdb1
 
  usbJ -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sdb2
 
Make sure you create the directories needed:
 
  /media/cdrom
 
  /media/usbG
 
  /media/usbH
 
  /media/usbI
 
  /media/usbJ
 
 
 
/etc/autofs/auto.misc
 
  kernel        -ro   ftp.kernel.org:/pub/linux
 
  boot         -fstype=ext2   :/dev/hda1
 
  removable -fstype=ext2   :/dev/hdd
 
  cd -fstype=iso9660,ro   :/dev/hdc
 
  floppy -fstype=auto   :/dev/fd0
 
Here you can add other filesystems if needed.
 
 
Finally add this line to rc.local
 
/etc/rc.d/autofs start
 
  
 
==ACPI==
 
==ACPI==

Revision as of 04:51, 18 February 2013

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Fujitsu-Siemens Amilo Pro2000#)

This info may be helpful in addition to the Arch Linux Installation guide. This may apply fairly well to many other Amilo computers, for example to M7400 which has very similar hardware.

LAPTOP SPECS

IntelCeleron 1500Mhz, 256+512MB ram, 40Gb HD, CD-RW/DVD (QSI). Display adapter Intel 82852/82855. IrDA Fast Infrared, AC'97 Modem, PS/2 Keyboard & Synaptics Mouse, 3 USB ports, Firewire, 2 card slots. Network adapters:Broadcom 440x 10/100 and Intel PRO/Wireless 2200GB.

TOUCHPAD

See Touchpad Synaptics

WIRELESS LAN

For wireless, the relevant driver is ipw2200.

    pacman -S ipw2200

From kernel 2.6.17 it is included and the relevant module is

    pacman -S ipw2200-fw

which only loads the firmware.

Add ipw2200 to loaded modules in rc.conf.

Append rc.conf to include eth1 (this is a static IP configuration),

    eth0="eth0 192.168.2.252 netmask 255.255.255.0 broadcast 192.168.2.255"
    eth1="eth1 192.168.2.252 netmask 255.255.255.0 broadcast 192.168.2.255"
    INTERFACES=(lo eth0 eth1)

and to modprobe.conf, add line

    alias eth1 ipw2200

Amilo requires a "kill switch" module that turns the wireless card radio on. Get fsam7400 module (0.4.0) from http://linux.zwobbl.de/pub/ unpack and install with make, make install. Don't need to add it to the loaded modules in /etc/rc.conf.

Then, to automate the wireless connection on boot, add the following to /etc/rc.local (thanks to nahoj1976):

    echo 100 > /sys/class/firmware/timeout
    modprobe fsam7400 radio=1 autooff=0 autoload=0
    modprobe ipw2200 

After this just the iwconfig and route settings need to be ok for the wireless to work (after reboot of course, unless you modprobe the above commands yourself!). In my case

    iwconfig eth1 essid Mynetworkname mode Managed rate 11M
    route add default 192.168.2.1 eth1

These can be in /etc/rc.local. Now the laptop will be online and iwconfig (from root) should give something like this:

    eth1      IEEE 802.11g  ESSID:"Mynetworkname"
              Mode:Managed  Frequency:2.462 GHz  Access Point: 00:11:50:34:A9:53
              Bit Rate=11 Mb/s   Tx-Power=20 dBm
              Retry limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:off
              Link Quality=91/100  Signal level=-38 dBm  Noise level=-82 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:3


If you want to connect to a secure network, WEP-encrypted, one way to do this is to write a small script. After boot you decide what script to run depending on what network you should connect to.

A typical setup-script could look like this:

 # /etc/rc.d/work
 # script to connect to network at work
 iwconfig eth1 key 1234567890 channel 6
 ifconfig eth0 down
 dhcpcd eth1

This script both select the right key and channel for the router and uses dynamic ip-addresses in order not to need thinking about DNS-server addresses etc.

ACPI

Seems to work normally: Battery life is visible automatically (in KDE at least), and screen goes to power saving mode after a period of inactivity.

MONITOR OUT

Works

S-OUT

not tested

IRDA

not tested

HOTKEYS, SPECIAL BUTTONS

Alt+Function key commands work ok. For left-side buttons, in kernel is a module called wistron_btns, it also drive the RadioSwitch.

CARD SLOTS

not tested

External Links