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.
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.
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: https://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.
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.
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.
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.
- This report is listed at the TuxMobil: Linux Laptop and Notebook Installation Guides Survey: Fujitsu-Siemens - FSC.