Gentoo Acer 803LCi support thread (manual section)

[feffi]

Acer Travelmate 803 LCi Support Thread (manual section)

This Manual Thread is out of date, it's only intented to give a hint, where to move on. For the actual maintained manual move on to the Gentoo Wiki

If you wish to participate in the discussion around this thread just go ahead and use this thread Gentoo Acer 803 LCi Discussion threador the Gentoo Wiki directly[/i]
We are proud to be listed on TuxMobil


Table of contents

1. Updates
   
2. About this Howto
   
3. Important things to know about the ACER Travelmate 803 LCi
   Specifications of the ACER Travelmate 803 LCi
   General Handling
   Battery Uptime
   Falling down & Scratches
   Output of 'lspci'
   
4. Compiler Flags
   Design of the Pentium-M
   CFLAGS
   USE-Variables
   
5. Important Must-Have-Software
   
6. GEP (Gentoo Emerge.log Parser)
   Compile times for different applications
   
7. ACPI
   General ACPI
   ACPI Event Handling
   Enhanced Speedstepping
   Software suspending w/wo XFree
   Hardware Sensors
   
8. Harddrive & 'hdparm' Optimization
   
9. Networking LAN
   Broadcom 4400
   
10. Networking Tools
    SSH-Agent and Keychain
    tcpdump
    mtr
    iptraf
    tethereal
    nessus
    Backup and distribution solutions
    
11. Networking WLAN
    ipw2100
    ndiswrapper
    Exchanging the Intel Mini-PCI with a Dell Truemobile 1150
    
12. Wireless Tools
    Kismet
    Wellenreiter
    Airsnort
    IPSEC & VPN
    
13. Internal modem
    
14. IRDA support
    Siemens mobile phones
    
15. PCMCIA
    
16. Special Laptop-Keys aka FN-Keys
    Windows Keys
    System Help
    ACPI Standy/Sleep
    Video Out
    External Display
    Touchpad Activator
    Mute Sound
    Display Bightness
    Volume FN-Keys
    Volume Keys and XFree OSD
    Other FN-Keys
    Hints
    
17. Acer Launchkeys & AcerHK
    Installing
    Testing & Mapping
    Scripts
    
18. Graphics
    ATI Radeon 9000 Mobility & XFree
    Alternate ATI Radeon 9000 Mobility Installation & MTRR fix
    Console Framebuffer
    TV-Out
    Beamer & external devices
    
19. Sound
    Sound recording
    
20. Universal Serial Bus (USB)
    General Hotplug
    General USB
    USB-Mouse
    USB-Mouse and XFree support
    USB Tools
    RootPlug
    USB-Memory-Stick
    User Authentification via pam_usb
    
21. Synaptics Touchpad
    
22. Firewire IEEE 1394
    
23. Styleguide
    Exchanging XFree Cursors
    Bootsplash
    Qingy
    LILO Graphical Menu
    
24. Link Graveyard
    
25. Missing Items & later additions
    

Updates

23.07.2004 Added Networking Tools - SSH-Agent and Keychain
10.07.2004 Review of the Networking section
10.07.2004 Added Networking LAN
10.07.2004 Added Networking LAN - Broadcom 4400
10.07.2004 Added Networking WLAN
10.07.2004 Added Networking WLAN - ipw2100
10.07.2004 Added Acer Launchkeys & AcerHK (THX to pjv)
10.07.2004 Added Internal Modem (THX to pjv)
01.07.2004 Rewrote TOC
12.03.2004 Added 'Volume Keys and XFree OSD' (really nice)
12.03.2004 Added 'Alternate ATI Radeon 9000 Mobility Installation & MTRR fix'
24.02.2004 Added 'Compile times for different applications'
24.02.2004 Added 'Email LED' to section 17. Styleguide
24.02.2004 Added 'User Authentication via pam_usb to section 13. Universal Serial Bus
13.02.2004 Added my important configs to the Link Graveyard
13.02.2004 Added EXTENSIVE Report on Hardware to section 3
05.02.2004 Added pictures to Networking - Exchanging the Intel Mini-PCI with a Dell Truemobile 1150
05.02.2004 Quingy and Bootsplash resolution change to 1400x1050
29.01.2004 LILO Graphical Menu
29.01.2004 Qingy

About this Howto
Reference:
Gentoo Installation Documents
Gentoo Forum

This Howto is intended to provide a usefull overview and installation & configuration guide for Gentoo-Linux on a ACER Travelmate 80x/2xx/. This Howto doesn't cover the ultimate truth, it's merely a compilation of work-reports, own testing, redoing of other howtos always with focus on an optimal stability and relyability on an ACER Travelmate 803 LCi. This howto doesn't cover the basic installation process of the Gentoo Linux distribution as this is exaustively covered by the Gentoo Installation Documents. The Howto is structured upon the inside-out-concept. All sections are optimized for work progress optimization (e.g hdparm before software-installation). So if you do this tutorial from beginning to end, the result should be a optimized stable and working Gentoo-Linux on your ACER-Travelmate 803 LCi. Also this howto is based on kernel 2.6. In special I would like to thank all those geeks in the Gentoo Forums for their help, suggestions, hints, tips, tricks and corrections for this tutorial as it would not be in this form without their help. Thank you !


Code:

for $user in (  smiler.se, ScubaStreb, treehugger, mrblade, kwaakie, svmaris, Baron FrostFire,  Fladnag, corey_s, tuxlover, miju, swell, fredrin, federico, |T5|, pjv, thepi ) do    echo 'thanx to ${user}' done

Important things to know about the ACER Travelmate 803 LCi
Reference:
Acer Worldwide
Toms Hardware Guide
Specifications of the ACER Travelmate 803 LCi

CPU: Intel Pentium-M 1600 MHz
Memory: 512 MB DDR-RAM
Graphics: ATI Radeon 9000 Mobility (64 MB) with VGA-Out / S-Video-Out
Harddrive: 40 GB
Optical-Drive: DVD/CD-RW-Combo (6x-24x/10x/24x) in MediaBay
Soundcard: Intel AC'97 Sound-on-Board
PCMCIA: Standard (i82365)
O2Micro Smartcardreader
Network: Broadcom Corporation BCM4401 10/100Base-T
Wireless-LAN: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter
Internal Modem: Intel AC97 Modem-on-Board
Ports: Parallel Port (Standard)
FastInfraRed (F-IR)
USB (4x USB2.0 / EHCI / OHCI / UHCI)
FireWire Texas Instruments TSB43AB21 (iLink/IEEE1394)

General Handling

Although the Travelmate 803LCi looks relatively slim (overall height 34 mm) due to its 15.1" display, it is by no means small (area 333 x 284 mm). With 1400 x 1050 pixels, the display offers SXGA+-resolution. Perhaps the most conspicuous feature of the Travelmate (TM) 803LCi is the curved keyboard. The corresponding switches for enabling and disabling the WLAN, Bluetooth and IRDA modules are located on the front of the device. The combo drive is integrated on the right-hand side in the media bay. Anyone who does not require an optical drive while out and about can save himself around 100 grams in weight by using the supplied Weight Saver module. By way of an option, Acer offers an additional battery for this slot.
The rear side incorporates the ports for the modem, Ethernet, I/O port replicator, printer and VGA, in addition to the S-Video output. Acer has not fitted a flap to protect the ports from dust. The hard disk drive, RAM and WLAN modules are easily accessible via flaps on the underside, which greatly facilitates upgrading. Anyone thinking about upgrading his 800 series with more than 512 MB RAM will be disappointed. The only "free" RAM slot is already occupied by a 256-MB module. As such, users are left with only the (expensive) upgrade option of adding an additional 512-MB module to 768 MB max.

From a purely statistical perspective, only one in ten people are left-handed writers. A mere two percent of all people are ambidextrous, and the majority of those left over are clearly right-handed. Despite this, Acer has integrated the USB and audio ports as well as the PC card slot on the left-hand side. Left-handed users will be delighted, although the odd one or two right-handed users might find this annoying. The PC card slot is positioned between the audio jacks and the USB ports. Beneath the slot, you will find a smartcard reader, which provides the device's security functions.

Battery Uptime

From my own experience I can give you two settings on this section: First section is Gentoo-Linux with minimal usage of disc and processor. Due to the use of 'speedfreq' and the complete powerdown of all unneccesary devices (e.g. LAN/WLAN) my longest uptime with this layout is about 6 hours of writing this tutorial.
Second section is Gentoo-Linux with full blown usage of both CPU and disc. With this layout you'll get a runtime of about 2 hours compiling XFree and GCC over and over again.

Falling down & Scratches

From my own hard experience I had to take the bitter pill of frustration when a friend of mine dropped my laptop from about 1 meter right on the floor. I think it hit on the lower right edge. As far as I know nothing bad happened to my hardware. Not even my display or harddrive. Another bad thing is letting a full blown desktop computer drop on your lid-open laptop. It hit my laptop right above the 'P1' key at the angle of the lid. I now have a little (1mm) scratch there, but despite that AGAIN nothing happened.

Output of 'lspci'

[feffi]

Special Laptop-Keys aka FN-Keys
Reference:
xOSD Homepage
Enlightened OSD
Requirements:
media-sound/setmixer
x11-libs/xosd

Windows Keys

Because I'm using fluxbox I have no real need for those keys. But for one reason I include those keys here: I found it rather annoying to use FN+Home or FN+End to jump in text lines, so I remapped those for Home and End. This is a very simple task when using Xmodmap. Just add a file called 'Xmodmap' to your home directory and add the following lines:


Code:

bash$ vi Xmodmap    keycode 117 = End    keycode 115 = Home


Done this you need to tell your XFree server to load this remapping when starting your favourite window manager. To accomplish this just add the following line to your '.xsession' file:


Code:

bash$ vi .xsession    exec /usr/bin/X11/xmodmap /etc/X11/Xmodmap &


This will invoke the usespace tool 'xmodmap' to redefine your keycodes. Of course you can also redifine other keys.

System Help

Key combination: FN+F1
This key comnation hasn't any effect yet.

ACPI Standy/Sleep

Key combination: FN+F4
This combination triggers the ACPI sleep action which needs to be defined in '/etc/acpi/events/default'.

Video Out

Key combination: FN+F5
This combination uses raw BIOS calls and works out of the box.

External Display

Key combination: FN+F6
Again raw BIOS calls. But beware, you may connect your external device (e.g. Beamer, Monitor, etc.) BEFORE you power on.
If you don't, your device may get lost from the BIOS and doen't work until reboot.

Touchpad Activator

Key combination: FN+F7
This key function activates/deactivates the touchpad directly without any os interference. But be carefull: Sometimes you could hit those without notice and afterwards wonder why your touchpad isn't working and maybe even call for support.
Be warned.

Mute Sound

Key combination: FN+F8
See Volume Keys

Display Bightness

Key combination: FN+LEFT/RIGHT
The display dimming or display brightness Keys are working with raw BIOS calls and so there are no special tricks to handle. They should work right out of the box.

Volume FN-Keys

To get the Volume keys to work we first need the correct keycodes for those keys. To aquire the keycodes they use just fire up a xterm in XFree and start 'xev'. Now press the keys and watch xev's reaction to it. The correct keycodes for my laptop
were:
Raise Volume (Fn + UP) : 176
Lower Volume (Fn + DOWN): 174
Going on now we'll need to map these keycodes to specific events in XFree. Again we are using the 'Xmodmap' file and add the following:


Code:

bash$ vi Xmodmap    keycode 174 = XF86AudioLowerVolume    keycode 176 = XF86AudioRaiseVolume


After that you'll need to map these events to specific commands.
As I use fluxbox I need to add some actions to my ~/.fluxbox/keys file:


Code:

bash$ vi ~/.fluxbox/keys    None XF86AudioRaiseVolume :ExecCommand setmixer vol +3    None XF86AudioLowerVolume :ExecCommand setmixer vol -3


Before this can work, as you've probably noticed, you need to emerge media-sound/setmixer. Now you're set to use your volume keys in XFree.
Hint: I don't use the keycode for mute (160) because it interferes with the button "e"!

Volume Keys and XFree OSD

So, as time goes by, I've discovered a cool feature (maybe some of you know already), the XFree-OSD library. You cat display any message or text with the tool osd_cat directly on your XFree screen. This will enable us to implement all the funtions (and some more) the windows tools enable e.g. switching the sound. Let's begin installing the x11-libs/xosd package as it will provide you with all necessary tools:


Code:

bash$ emerge x11-libs/xosd


After successfull installation simply add a new file called osd.sh to your ~/bin directory (or somewhere similar):


Code:

bash$ vi ~/bin/osd.sh #!/bin/sh if [ $1 == '+' ] then         setmixer vol +5 else         setmixer vol -5 fi exec echo `setmixer -V vol +0 | awk '/vol/{split ($3,a,",");print a[1];}'` "% Volume" | osd_cat --font="-adobe-helvetica-bold-*-*-*-34-*-*-*-*-*-*-*" --shadow=2 --pos=top --align=right --colour=green --delay=1


After this make the file executable:


Code:

bash$ chmod 770 osd.sh


Executing this script will set a new volume and diplay it via OSD directly on your XFree screen. To use it with your already defined volume hotkeys (see above) simply change your keys assignments:


Code:

bash$ vi ~/.fluxbox/keys    None XF86AudioRaiseVolume :ExecCommand ~/bin/osd.sh +    None XF86AudioLowerVolume :ExecCommand ~/bin/osd.sh


Now try it, it should produce a really nice OSD-Volume display. Just for the coders out there: You can paste anything (like tail -f ...) to the osd_cat command...really nice

Other FN-Keys

All other key combinations like numeric pad, numlock, scroll-lock, etc work right out of the box. They also make raw BIOS calls, thus the system is not required to be configured here.

Hint:

If you don't like messing around with Xmodmap's config files directly, you can also emerge x11-misc/xkeycaps which is a GUI frontent for xmodmap.

Acer Hotkeys & LEDs
Installing

To be able to use the four hotkeys (mail, web, P1 and P2) you need a special driver called acerhk. Beside the keys this driver will also give you control over the mail LED, the wireless LED and the bluetooth LED. First you'll have to download the driver from http://www.informatik.hu-berlin.de/~tauber/acerhk/ and untar it in a directory of your choice. I prefer to include the acerhk driver directly into the kernel. The current version is acerhk-0.5.13. Note that support for the 800-series is still experimental, allthough it seems to work for me and others:


Code:

bash$ cd /usr/src/linux/drivers/misc bash$ wget http://www.informatik.hu-berlin.de/~tauber/acerhk/archives/acerhk-0.5.13.tar.bz2 bash$ tar xvfj acerhk-0.5.13.tar.bz2 bash$ mv acerhk-0.5.13 acerhk


As we copied the source files directly into the desired kernel directory. Now we just have to include the driver directory in the config files. Just add the following lines to the config file /usr/src/linux/drivers/misc/Kconfig as shown below:


Code:

bash$ nano /usr/src/linux/drivers/misc/Kconfig    config ACERHK    tristate "Acerhk driver"    depends on EXPERIMENTAL    ---help---       This is an experimental acer keyboard driver for       acer laptops


Now include the acerhk directory in it's parents Makefile (/usr/src/linux/drivers/misc/Makefile) and add the following line:


Code:

bash$ nano /usr/src/linux/drivers/misc/Makefile obj-$(CONFIG_ACERHK)   +=      acerhk/


Next you'll have to activate the misc drivers first by sourcing them:


Code:

bash$ source "drivers/misc/Kconfig"


One last step and the installation process is finished. Go to your favourite kernel config (make menuconfig, oldconfig, gconfig) and enable the acerhk driver by activating


Code:

Device Drivers  --->    Misc devices  --->       <M> Acerhk driver


Now recompile your kernel and install it. After a reboot with your new kernel you should have a fresh working acerhk module you can load. It's as easy as that!

Testing & Mapping

Now it's time to read the README file included with the driver (again the last part)... or you can read below. First load the module or put it in /etc/modules.autoload.d/kernel-2.6
to load it at every bootup automatically


Code:

bash$ modprobe acerhk


Now you can interact with the driver at:


Code:

bash$ cd /proc/driver/acerhk/ bash$ ls -al dr-xr-xr-x  2 root root 0 Jul  5 20:11 . dr-xr-xr-x  4 root root 0 Jul  5 20:11 .. --w--w--w-  1 root root 0 Jul  5 20:11 blueled -r--r--r--  1 root root 0 Jul  5 20:11 info -r--r--r--  1 root root 0 Jul  5 20:11 key --w--w--w-  1 root root 0 Jul  5 20:11 led --w--w--w-  1 root root 0 Jul  5 20:11 wirelessled


If you can see these entries, all is set up and should work. Let's go on! First press some hotkeys and then type "dmesg" in a terminal. You'll see that the kernel has detected your keypresses (and releases). Here's what the README says about it:


Code:

If you have one of the newer models with the dritek hardware <we do ;-)>, use kernel 2.6 and get (after enabling it) kernel messages of the form:    atkbd.c: Unknown key pressed (translated set 2, code 0xf4 on    isa0060/serio0).    atkbd.c: Use 'setkeycodes e074 <keycode>' to make it known. then you should do exactly what your told. In this case you could do    setkeycodes e074 158 to map the button with scancode e074 (hex) to keycode 158 (decimal). ... The keycode you give as parameter to setkeycodes is one out of the header file /usr/src/linux/include/linux/input.h ...



In my case I just had to do


Code:

setkeycodes e074 149


twice, once for e074 and once for e073. The keycode didn't matter because it seemed to choose it's own. It got set to 158 despite me asking for 149. Also all four keys got defined!?? So to get your keys working after boot, just edit /etc/conf.d/keyscodes to map the scancodes to keycodes:


Code:

bash$ nano /etc/conf.d/keycodes    KEYCODES="e025 89 e026 90 e027 91 e074 92 e073 93"


and install the keycodes rc script to your runlevel by typeing


Code:

bash$ rc-update add keycodes default


If you're keycodes script is missing, just create it:


Code:

bash$ nano /etc/init.d/keycodes    #!/sbin/runscript    depend()    {      need localmount    }        start()    {      # Load scan code to key code mappings         if [ -n "$KEYCODES" -a -x /usr/bin/setkeycodes ]      then        ebegin "Loading scan code to key code mappings"          /usr/bin/setkeycodes $KEYCODES        eend $? "Error loading key code mappings"      fi    }


Thats it, you're almost done. After a reboot or start of the keycodes script you should be able to get some output from e.g. xev for your keys pressed. I mapped all keys to F17 to F20 with xmodmap so I can access them easily in XFree. Just edit your .Xmodmap file and add:


Code:

bash$ nano /etc/X11/Xmodmap    keycode 236 = F17    keycode 178 = F18    keycode 129 = F19    keycode 120 = F20 bash$ xmodmap /etc/X11/Xmodmap


After execution of xmodmap all your keys should be mapped ready for use. For the gnome 2.6 users amongst you: You can now define actions for these keys in the "Multimedia keys" dialog. My settings seemed a bit gibberish because my "Preferred applications" dialog wouldn't hangon to my choices at first (not even via GConf) and I also had to redefine the multimedia keys once by deleting them and redefining them... But anyhow, at least now they are staying where I put them.

Scripts

I would suggest we gather some nice ways of utilizing the keys and the LEDs here. I'll start with some scripts to automize mailprocessing with gnome 2.6 and Ximian Evolution:


Code:

bash$ nano /usr/bin/ledon:    #! /bin/sh    #    # led* - a script to change "You've got mail"-led light state    echo "Setting mail led light on"    echo 1 > /proc/driver/acerhk/led




Code:

bash$ nano /usr/bin/ledoff:    #! /bin/sh    #    # led* - a script to change "You've got mail"-led light state    echo "Setting mail led light off"    echo 0 > /proc/driver/acerhk/led




Code:

bash$ nano /usr/bin/mailchecked:    #! /bin/sh    #    # mailchecked - a script for the double click event on the postbus-monitor applet: switch led off and start evolution    echo "Setting mail led light off and launching mail client"    ledoff    evolution $1


Put a Postbus-Monitor-2.6 applet on your panel and copy these scripts to /usr/bin (with right chmod 755 ofcourse). Setup the applet and set "ledon" to be executed when a new mail arrives. Set "mailchecked" to be executed on a double click. Also put "mailchecked %s" as your mail application in the "Preferred applications" dialog and link the mail hotkey to opening your mail. Now, when "you've got mail!", your LED will blink until you press the mail hotkey, which will launch Evolution (eventually already writing a new mail to %s) and turn off the LED. The mailto:%s command from your browser will still work.

Graphics
Reference:
Gentoo DRI Howto
Gentoo Forum Thread
Gentoo Forum Thread
Gentoo Forum Thread
Gentoo Forum Thread
DRI Project Homepage
FreeBSD DRI FAQ
FreeBSD DRI Troubleshooting Guide
DRI Patches by Alan H. from the XFree Project
Requirements:
media-video/ati-driversATI Radeon 9000 Mobility & XFree

Here comes the hardest part. The "ATI Radeon 9000 Mobility". After several troubles with XFree 4.2.x and kernel 2.4.x the ati-drivers included in portage now work with kernel 2.6. The version of the drivers which should work is 3.2.8 and to install those drivers, which recompile a part of your kernel upon install, just do:


Code:

bash$ opengl-update xfree bash$ emerge media-video/ati-drivers bash$ opengl-update ati bash$ fglrxconfig


The tool 'fglrxconfig', which is provided with the ati-drivers package, tunes and adjusts all needed settings for you in your '/etc/X11/XF86Config'. Beware: the config tool generates a new 'XF86Config-4' which overrides your old one. For all those who part the fate of an kernel 2.4.x, use the references above and try yourself. From my experience sometimes
the drivers work, sometimes not, don't really know why.

Alternate ATI Radeon 9000 Mobility Installation & MTRR fix

Ok here is the short alternative guide on the ATI 9000 Mobility configuration using the build in kernel Module:


Code:

cd /usr/src/linux


the 'linux' directory should be pointing to the kernel version you are about to build. Ok, for the 2.6.x kernel versions you'll have to enable the AGPgart support modules:


Code:

Device Drivers  --->    Character devices  ---> <M> /dev/agpgart (AGP Support) <M>   Intel 440LX/BX/GX, I8xx and E7x05 chipset support


After that you also have to enable the ATI-DRI-Module:


Code:

Device Drivers  --->    Character devices  ---> [*] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) <M>   ATI Radeon


Now recompile the kernel and load your new kernel and make sure the agp modules are loaded...how you did this? Either do it manually:


Code:

bash$ modprobe agpgart bash$ modprobe intel-agp


or load them automagically when you load your system by adding them to your '/etc/modules.autoload.d/kernel-2.x' file:


Code:

bash$ echo "agpgart" >> /etc/modules.autoload.d/kernel-2.6 bash$ echo "intel-agp" >> /etc/modules.autoload.d/kernel-2.6


This will load the modules during boot up. Now go on for a nice clean X Configuration:
IMPORTANT: Make sure you are using the opengl version from 'ati', so change it back to 'xfree':


Code:

bash$ opengl-update xfree


First of all i tested this on the Xfree 4.3.0-r4 AND Xfree 4.3.0-r5 so i can't gurantee anything for previous versions of Xfree (allthough it should work without any problems). Now let's go ahead to configure the XFree config file:


Code:

bash$ vi /etc/X11/XF86Config-4 Section "Device"         Option  "AGPMode"       "4"         Option  "EnablePageFlip"        "True"         Option  "IgnoreEDID"    "off"         Identifier  "Card0"         Driver      "ati"         VendorName  "ATI Technologies Inc"         BoardName   "Radeon R250 Lf [Radeon Mobility 9000 M9]"         BusID       "PCI:1:0:0" EndSection Section "Monitor"         #DisplaySize      300   230     # mm         Identifier   "Monitor0"         VendorName   "AUO"         ModelName    "f03"         HorizSync       27-90         VertRefresh     40-60         #DisplaySize    320 240         Option  "DPMS"  "true" EndSection Section "DRI"         Mode 0666 EndSection


Ok start X...you should be able to reproduce this scores:


Code:

bash$ glxgears    9360 frames in 5.0 seconds = 1872.000 FPS    10040 frames in 5.0 seconds = 2008.000 FPS    10037 frames in 5.0 seconds = 2007.400 FPS    10053 frames in 5.0 seconds = 2010.600 FPS


As a last change to your altenate config, you need to include the MTRR-fix:


Code:

bash$ vi /etc/conf.d/mtrr-fix    #!/bin/bash    echo "disable=2" >| /proc/mtrr    echo "base=0xd8000000 size=0x4000000 type=write-combining" > /proc/mtrr


Now make sure this fix is loaded at boot time:


Code:

bash$ vi /etc/conf.d/local.start    # This is a good place to load any misc.    # programs on startup ( 1>&2 )    /etc/conf.d/mtrr-fix


You can't be 100% sure the ranges included in this fix are reflecting the same range your card uses, so have a look at the kernel messages in '/var/log/messages'. You should be able to see the following lines:


Code:

Feb 16 17:11:52 computername mtrr: MTRR 3 not used Feb 16 17:11:52 computername mtrr: 0xd8000000,0x4000000 overlaps existing 0xd8000000,0x1000000


So, to be sure, if you can see the lines above, you're correct. If you don't see those lines, change the following in your 'mtrr-fix' file:


Code:

"base=0xd8000000" --> To the first number shown in the mtrr /var/log/messages message "size=0x4000000" --> to the second number of the mtrr message.


Now your ATI Radeon 9000 should be fixed. If you experience any errors or have corrections on this topic, pls pm me immediatly. This fix is very alpha and has not approved yet.


Special thanks to pestilence for researching so deeply into this topic

Console framebuffer

To get an high resolution framebuffer console in normal text mode, you'll need to tune your kernel a little bit:


Code:

Device Drivers  --->    Graphics support  --->       [*] Support for frame buffer devices       [*]   VESA VGA graphics support       Console display driver support  --->          [*]   Video mode selection support          <*> Framebuffer Console support


now recompile your kernel and add the entry 'vga=794' to your kernel section in '/etc/lilo.conf'


Code:

bash$ vi /etc/lilo.conf    image = /boot/kernel_2.6.0_final       root = /dev/hda2       label = 2.6.0-final       read-only       vga=794


The important line is the vga=***. The values can be replaced to suit your needs:


Code:

Colours   640x480 800x600 1024x768 1280x1024 1600x1200 --------+--------------------------------------------- 256     |   769     771      773      775       796 32,768  |   784     787      790      793       797 65,536  |   785     788      791      794       798 16.8M   |   786     789      792      795       799

Sound

This topic is fairly easy as ALSA works right out of the box with kernel 2.6. To get the correct drivers you'll need to enable


Code:

Device Drivers  --->    Sound  --->       <*> Sound card support       Advanced Linux Sound Architecture  --->          <*> Advanced Linux Sound Architecture          <*>   Sequencer support          [*]   OSS API emulation          <*>     OSS Mixer API          <*>     OSS PCM (digital audio) API          [*]     OSS Sequencer API          PCI devices  --->             <*> Intel i8x0/MX440, SiS 7012; Ali 5455; NForce Audio; AMD768/8111


in your kernel settings. This will give you the interfaces to your AC97 sound chip in '/dev/sound/' with access to all volume settings, a dsp, sequencers and a mixer. After that you should emerge 'alsamixer' or some other tool to adjust your volume settings (I prefer gkrellm).

Universal Serial Bus (USB)
References:
pam_usb Project
PAM X509 Authentication Module
Requirements:
sys-apps/hotplug
app-admin/usbview
sys-libs/pam_usbGeneral Hotplug

For the USB section ahead the package 'sys-apps/hotplug' is esseantial as it manages all module loading and unloading required for several devices you can use with USB. To install hotplug just do


Code:

bash$ emerge sys-apps/hotplug bash$ rc-update add hotplug default


Also hotplug needs to be added to runlevel 'default' as you can see. This will load the hotplugd daemon at boot time. Just a little hint from me: Don't add hotplug to runlevel 'boot' (pointed out in several howto's if read) as it needs several variables from runlevel default.

General USB

The USB-Hub-Controller of the Acer Travelmate 803 LCi is an EHCI USB 2.0 compatible device. So all you have to do is to change the settings in your kernel to support the device. Also, for using USB 1.1 compatible devices, you need to select the UHCI module:


Code:

Device Drivers  --->    USB support  --->       <M> Support for USB       [*]   USB device filesystem       [*]   Enforce USB bandwidth allocation (EXPERIMENTAL)       [*]   Dynamic USB minor allocation (EXPERIMENTAL)       <M>   EHCI HCD (USB 2.0) support       <M>   UHCI HCD (most Intel and VIA) support


Chosen this settings you'll have basic USB 1.1 and 2.0 support compiled into the kernel as modules. Ahead now comes the customization section where several devices are discussed, so keep on reading before you compile your kernel.

USB-Mouse

Most people nowadays use an USB-Mouse despite of the tbuilt in touchpad, because it's more comfortable. To install the support for the most common mouse devices, you'll just have to activate the following also residing in the USB section:


Code:

<M>   USB Human Interface Device (full HID) support [*] HID input layer support [*] /dev/hiddev raw HID device support    USB HID Boot Protocol drivers  --->       <M> USB HIDBP Keyboard (simple Boot) support       <M> USB HIDBP Mouse (simple Boot) support


This will get you, in combination with hotplug a comfortable way to work with your mouse through the interface '/dev/input/mice' The USB kernel modules will automatically be loaded by hotplug if you plug in your device so no modules need to be loaded at boot time.

USB-Mouse and XFree support

To get your freshly installed mouse to work with XFree you need to tweak your 'InputDevice' section in
'/etc/X11/XF86Config':


Code:

bash$ vi /etc/X11/XF86Config    Section "InputDevice"       Identifier  "USBMouse"       Driver      "mouse"       Option "Protocol"    "ImPS/2"       Option "Device"      "/dev/input/mice"       Option "ZAxisMapping" "4 5"    EndSection


The 'Option "ZAxisMapping" "4 5"' will also give you back your mouse-wheel and third button. After that you normally have to add the following lines to your 'ServerLayout' section as it needs to be registered as pointer device. The following lines will get the touchpad and the USB-Mouse working both at the same time:


Code:

Section "ServerLayout"    InputDevice "USBMouse" "CorePointer"    InputDevice "Mouse2" "SendCoreEvents"    InputDevice "Keyboard1" "CoreKeyboard" EndSection


After a restart of XFree you're all set to use you USB-Mouse with XFree.

USB Tools

Just for making this topic complete I want to mention the tool usbview which is available through portage via:


Code:

bash$ emerge app-admin/usbview.

RootPlug

RootPlug is a fine thing to work with, as you only have to edit a file in your kernel directory. The file you need is '/usr/src/linux/security/root_plug.c'. But first you have to determine the vendor- and product-id of your root-plug-device. To do this, just fire up 'usbview' an look for your device. Next you'll have to extract the following information from the usbview-diplay:
Vendor Id: 033a
Product Id: 025f
These are the values you need to edit your device section in the root-plug file mentioned above accordingly:


Code:

bash$ vi /usr/src/linux/security/root_plug.c    /* default is a generic type of usb to serial converter */    static int vendor_id = 0x033a;    static int product_id = 0x025f;


After you've managed this, you simply have to enable some kernel options as shown below:


Code:

Security options  --->    [*] Enable different security models    <M>   Root Plug Support


After recompiling your kernel a module named 'root_plug' which can be loaded via


Code:

bash$ modprobe root_plug


But be warned: If ever your device is broken, you'll only be able to recover your root-state by circumventing your module loading phase by using a boot cdrom or another kernel (e.g. kernel 2.4.) without RootPlug support.

USB-Memory-Stick

A USB-Memory-Stick is a fine thing to make a quick backup of your config and favourite data or to store important data on. If you emerged the 'sys-apps/hotplug' package you nearly have all you need. Some kernel settings have to be adjusted to get the USB-Memory-Sticks work. First we need the SCSI section as this will give us a device in '/dev/scsi/' later if you plug in a memory stick.


Code:

Device Drivers  --->    SCSI device support  --->       <M> SCSI device support       [*]   legacy /proc/scsi/ support       <M>   SCSI disk support       <M>   SCSI generic support


Now we go on to the real USB section to enable all those neat USB mass storage devices.


Code:

Device Drivers  --->    USB support  --->       <M> Support for USB       <M>   EHCI HCD (USB 2.0) support       <M>   OHCI HCD support       <M>   UHCI HCD (most Intel and VIA) support       <M>   USB Mass Storage support       [*]     USB Mass Storage verbose debug


The settings ahead are not neccessary as you already havfe the basic settings for your device, but who knows which hardware you'll have to combat with. If you wish you can in addition enable:


Code:

[*]     Datafab Compact Flash Reader support (EXPERIMENTAL) [*]     Freecom USB/ATAPI Bridge support [*]     ISD-200 USB/ATA Bridge support [*]     Microtech CompactFlash/SmartMedia support [*]     HP CD-Writer 82xx support (EXPERIMENTAL) [*]     SanDisk SDDR-09 (and other SmartMedia) support (EXPERIMENTAL) [*]     SanDisk SDDR-55 SmartMedia support (EXPERIMENTAL) [*]     Lexar Jumpshot Compact Flash Reader (EXPERIMENTAL)


Recompiled and installed your new kernel it will now be able to send some events if you plug in your memory stick. These events will be handled by 'hotplug' which will start the correct modules for your memory device. After plugging in your memory stick a new device will be in '/dev/scsi/hostX...' with the endpoints 'disc' and 'partX' where 'X' stands for a generic number. The 'disc' device can be easily mounted via the normal mount commant. Although the most usb memory sticks have a vfat filesystem, some are reported to go fine with ext2. Here is a sample of mounting an usb memory stick:


Code:

bash$ mount -t vfat /dev/scsi/host0/target0/lun0/disc /mnt/usb


Now you can access your usb memory stick through '/mnt/usb'. Be aware to 'sync' AND unmount your usb stick BEFORE you unplug it. If you don't, you may loose data and sure get a kernel oops.

User Authentification via pam_usb

In this section I want to explain some basic user authentification via an USB stick using the pam_usb modules. To begin we first have to emerge the sys-libs/pam_usb with


Code:

bash$ emerge sys-libs/pam_usb


After the finished installation of the module we will have a application called usbadm which is responsible for managing keys and serial numbers stored on you USB stick. So the next step would be generating a key for your authentication e.g. for root. First mount your USB stick to something like /mnt/usb


Code:

bash$ mount -t vfat /dev/sda /mnt/usb


Then use the admin application to generate a appropiate key for your login:


Code:

bash$ usbadm keygen /mnt/usb root 4096


This will create a directory /mnt/usb/.auth where all your keys are stored. Optionally you can also cipher your key on the USB stick with a password or add a serial number so the only device that is valid with this key is the current mounted. Just go ahead and play a little bit with the options of usbadm. Now comes the tricky part as usb_pam needs a little workaround since we are using kernel 2.6. We need to tell PAM how to authenticate you with pam_usb. So we'll edit /etc/pam.d/system-auth:


Code:

bash$ vi /etc/pam.d/system-auth auth       required     /lib/security/pam_env.so # pam_usb # auth       sufficient   /lib/security/pam_usb.so fs=vfat debug=1 check_device=-1 check_if_mounted=-1 force_device=/dev/sda # pam_usb # auth       sufficient   /lib/security/pam_unix.so likeauth nullok auth       required     /lib/security/pam_deny.so account    required     /lib/security/pam_unix.so password   required     /lib/security/pam_cracklib.so retry=3 password   sufficient   /lib/security/pam_unix.so nullok md5 shadow use_authtok password   required     /lib/security/pam_deny.so session    required     /lib/security/pam_limits.so session    required     /lib/security/pam_unix.so


For PAM to use pam_usb we simply add the line above. After saving you can already try it, just fire up a normal user shell:


Code:

bash$ su - [device.c:287] Forcing device /dev/sda [device.c:267] Creating temporary mount point... [device.c:273] Using /tmp/pam_usbp9Y5UT as mount point [device.c:167] Trying to mount /dev/sda on /tmp/pam_usbp9Y5UT using vfat [device.c:175] Device mounted, trying to open private key [device.c:150] Opening /tmp/pam_usbp9Y5UT/.auth/root.somemachine [device.c:183] Private key opened [auth.c:135] Private key imported [auth.c:143] Public key imported [dsa.c:78] Checking DSA key pair... [dsa.c:88] Signing pseudo random data [1 time(s)]... [dsa.c:95] Valid signature [dsa.c:88] Signing pseudo random data [2 time(s)]... [dsa.c:95] Valid signature [dsa.c:88] Signing pseudo random data [3 time(s)]... [dsa.c:95] Valid signature [pam.c:88] Access granted bash root$ _


As you can see pam_usb will automagically mount /dev/sda and look for a key to authenticate your account. I've done this for the account 'root' here but you can also do this for every account you like by just logging in that account, mount the USB stick and generate a new key. The keyfile on the USB stick will have an automatical generated name. You can also generate keys for other machines beside you laptop (of course you'll have to install pam_usb on them too). If you're finished with configuring the module and keys, just remove the entry 'debug=1' from the line in /etc/pam.d/system-auth to prevent pam_usb spitting out all those debug messages.

Synaptics Touchpad
Reference:
http://www.gama.de/projects/debian/acertm800lci/index.php
Requirements:
http://www.tuxmobil.org/software/synaptics/

To get the touchpad working in XFree 4.x you'll need a synaptics-linux-driver which provides all function of the touchpad under XFree. You can obtain this driver at the link above. Once downloaded, untar it and copy the file 'synaptics_drv.o' into your XFree module directory '/usr/X11R6/lib/modules/drivers'. Now you'll have to change a few lines in your 'InputDevice' section in '/etc/X11/XF86Config':


Code:

Section "InputDevice"       Identifier      "SynapticsTouchpad"       Driver          "synaptics"       Option          "Device"        "/dev/psaux"       Option          "ZAxisMapping"  "4 5"       Option          "Edges"         "1900 5400 1800 3900"       Option          "Finger"        "25 30"       Option          "MaxTapTime"    "20"       Option          "MaxTapMove"    "220"       Option          "VertScrollDelta"       "100"       Option          "MinSpeed"      "0.02"       Option          "MaxSpeed"      "0.18"       Option          "AccelFactor"   "0.0007"       Option          "SHMConfig"     "on"       Option          "UpDownScrolling"       "on"       Option          "Protocol"      "ImPS/2"       Option          "CorePointer"   "" EndSection


All you need to do now is to register this device in the 'ServerLayout' section also in this file:


Code:

Section "ServerLayout"    InputDevice "USBMouse" "CorePointer"    InputDevice "SynapticsTouchpad" "SendCoreEvents"    InputDevice "Keyboard1" "CoreKeyboard" EndSection


This will add a pointer device for the Synaptics Touchpad for use in XFree. To use your mouse in an console (framebuffer or not) you'll need to use the 'sys-libs/gpm' package. First you'll have to install this package:


Code:

bash$ emerge sys-libs/gpm


This will give you the config files for 'gpm'. Change the following lines accordingly to the following to get your USB-Mouse and Synaptics Touchpad working in your text-console:


Code:

bash$ vi /etc/conf.d/gpm    # Config file for /etc/init.d/gpm    #MOUSE=ps2    MOUSE=imps2    MOUSEDEV=/dev/psaux    #MOUSEDEV=/dev/input/mice


Done that, you may add gpm to one of your runlevels by


Code:

bash$ rc-update add gpm default


If you want to test it now (without rebooting) start the service manually by typing


Code:

bash$ /etc/init.d/gpm start


Now a little text coursor should appear when you move your mouse in an text-console. You can also use copy and paste like in XFree.

Firewire IEEE 1394

The Acer Travelmate 803 LCi also has a firewire IEEE 1394 device. the kernel modules support a wide variety of firewire devices like harddiscs, cameras or LAN-over-1394. To enable all these features and the different hardware specific modules, enable the following settings in your kernel config:


Code:

Device Drivers  --->    IEEE 1394 (FireWire) support (EXPERIMENTAL)  --->       <M> IEEE 1394 (FireWire) support (EXPERIMENTAL)       <M>   OHCI-1394 support       <M>   OHCI-1394 Video support       <M>   SBP-2 support (Harddisks etc.)       [*]     Enable Phys DMA support for SBP2 (Debug)       <M>   Ethernet over 1394       <M>   OHCI-DV I/O support       <M>   Raw IEEE1394 I/O support       <M>   IEC61883-1 Plug support       <M>     IEC61883-6 (Audio transmission) support


After recompiling your kernel, you'll get several modules you can use to attach and work your firewire hardware. In special you'll get:


Code:

bash$ modprobe ieee1394.o


This is the standard interface for firewire support in the kernel. This has to be loaded always if you want to work with firewire.


Code:

bash$ modprobe ohci1394.o


As the firewire chipset is a OHCI-1394 specification compliant, this modules also has to be loaded.


Code:

bash$ modprobe video1394.o


This module enables video device usage for OHCI-1394 cards. Enable this module only if you have an IEEE 1394 video device connected to an OHCI-1394 card.


Code:

bash$ modprobe sbp2.o


This module enables you to use SBP-2 devices connected to your IEEE 1394 bus. SBP-2 devices include firewire-harddrives and DVD/CDROM devices.


Code:

bash$ modprobe dv1394.o


This module allows you to transmit and receive DV (digital video) over the OHCI-1394 firewire port.


Code:

bash$ modprobe raw1394.o


The raw firewire module enables direct communication of user programs with the IEEE 1394 bus and thus with the attached peripherals.


Code:

bash$ modprobe cmp.o


This module enables the Connection Management Procedures (IEC61883-1) driver, which implements input and output plugs. This is generally a good idea, because newer hardware also supports this feature.


Code:

bash$ modprobe amdtp.o


This module enables the Audio & Music Data Transmission Protocol (IEC61883-6) module, which implements audio transmission over IEEE1394.
This should get all your firewire hardware to work on kernel basis. For special needs you naturally need some userspace tools to use these features.

Styleguide
Reference:
Qingy Homepage
Lilo Graphics Tutorial
AcerHK Homepage
Requirements:
bootsplash diff
media-gfx/bootsplash
sys-apps/qingyExchanging XFree Cursors

XFree 4.3 supports the feature of semi-transparent mouse pointers with shadows. To exchange your boring standard XFree cursor you need to emerge one of the following packages:



Code:

bash$ x11-themes/blueglass-xcursors bash$ x11-themes/golden-xcursors bash$ x11-themes/silver-xcursors


To enable ththe installed cursors you just need to edit or create the file ".Xdefaults" in your home directory:


Code:

bash$ vi ~/.Xdefaults    Xcursor.size: 32    Xcursor.theme: blueglass


Dones this just reload your XFree server and enjoy your new fancy cursors.

Bootsplash

To get bootsplash up and running with Gentoo and kernel 2.6 you'll need a little patience as this not an easy task. First of all you have to install bootsplash


Code:

bash$ emerge media-gfx/bootsplash


to get your rc-scripts and some files in '/sbin' patched. Now follows the tricky part: Download the bootsplash diff-file for kernel 2.6.x from the bootsplash homepage and place it in '/usr/src'. Next we patch the kernel with


Code:

bash$ patch -p1 < /path/to/bootsplash-3.0.7-2.6.xxxx-vanilla.diff


to get the correct options in menuconfig. If patching was successfull, enable the following settings in your newly patched kernel:


Code:

Processor type and features  --->    [*] MTRR (Memory Type Range Register) support Device Drivers  --->    Block devices  --->       <*> RAM disk support       (4096) Default RAM disk size       [*] Initial RAM disk (initrd) support       [*] Support for Large Block Devices    Graphics support  --->       Bootsplash configuration  --->          [*] Bootup splash screen


Also be sure to disable ALL BootLogo options in


Code:

Device Drivers  --->    Graphics support  --->       Logo configuration  --->          [ ] Bootup logo


as the interfere with the bootsplash configuration. Now recompile your kernel with all the new options set and copy it to your /boot (or whatever you use) directory. Next we will set up an appropiate splashscreen as an initrd:


Code:

bash$ splash -f -s /etc/bootsplash/gentoo/config/bootsplash-*.cfg /boot/initrd-*


The * marks the desired screen size you want to use. The defaults are 800x600, 1024x768, 1280x1024 or 1600x1200. I prefer the size of 1400x1050 as it is the maximum this LCD can display correctly. To use an initrd with 1400x1050 you might have to edit your background images to suit your resolution. In this case simply take your current background image an resize it with gimp to 1400x1050 and afterwards edit your config file in your '/etc/bootsplash/...' directory to fit the resolution. Next you'll have to edit your '/etc/lilo.conf' again to introduce the new compiled kernel to the initrd and bootsplash options:


Code:

bash$ vi /etc/lilo.conf    image = /boot/kernel_2.6_splash       vga=0x342 #1400x1050       root = /dev/hda2       initrd = /boot/initrd-1400x1050       append = "video=vesa:1400x1050,mtrr splash=silent"       label = 2.6_fb_splash       read-only


After altering your 'lilo.conf' accordingly, you're just two commands away from your bootsplash screen:


Code:

bash$ lilo bash$ rc-update add bootsplash default


Now you should be all set for your bootsplash screen at boot time. If you wish to exchange the default Gentoo theme (which looks really nice), just go ahead and download them from your favourite themes archive around the corner.

Quingy

Qingy is a replacement of getty. Written in C, it uses DirectFB to provide a fast, nice GUI without the overhead of the X Windows System. It allows the user to log in and start the session of his choice (text console, gnome, kde, wmaker, ...). I use Qingy because it's really fast an not bloated and slow like the other login-managers provided by XFree (if you ever used gdm or kdm, you'll know what I mean). Qingy despite that is no real login manager by itself it's a replacement of agetty. If you don't know what agetty is, just switch to a terminal, where you aren't logged in, thats agetty. Despite that Qingy can also fire up your Xfree as well as log you into a text based console. But enough of that, let's begin installing:


Code:

bash$ emerge sys-apps/qingy


Right after emerging Qingy, you'll have to edit your '/etc/inittab' to set Qingy as your login manager. Just go ahead to the terminals section of the file and change the following lines. Terminal 6 will be your old 'agetty'. This is for security, if something with Qingy goes completely wrong, you have a secure way to log in.


Code:

bash$ vi /etc/inittab # TERMINALS c1:12345:respawn:/sbin/qingy tty1 c2:12345:respawn:/sbin/qingy tty2 c3:12345:respawn:/sbin/qingy tty3 c4:12345:respawn:/sbin/qingy tty4 c5:12345:respawn:/sbin/qingy tty5 c6:12345:respawn:/sbin/agetty 38400 tty6 linux #c7:12345:respawn:/usr/bin/top tty8


BTW: Don't forget to take 'gdm/kdm' out of your runlevels. This can be done by


Code:

bash$ rc-update del xdm


You can also change the theme Qingy uses for your login screen. Just go ahead to the Qingy homepage and read the manual. But let's go on now: To get Qingy work with a resolution of 1400x1050, you'll have to add a new mode (if it isn't already present) to your '/etc/fb.modes' file to get the correct mode settings, just boot to your freshly installed bootsplash kernel. Now log in as root and type


Code:

bash$ fbset    mode "1400x1050-77"        # D: 147.037 MHz, H: 83.166 kHz, V: 77.436 Hz        geometry 1400 1050 1400 1050 16        timings 6801 168 32 16 4 168 4        rgba 5/11,6/5,5/0,0/0    endmode


without any parameters. fbset should display your current framebuffer mode (if you already booted to bootsplash, this should be something like 1400x1050-77 or something similar like above). These lines need to be added to '/etc/fb.modes' before you can use Qingy at this resolution. Last step is to edit '/etc/directfbrc.qingy' and set your freshly added mode from '/etc/fb.modes'. Now do a simply reboot and Qingy should work at 1400x1050.

Lilo Graphical Menu

This topic was a really hard one. Not because it's hard to do the configuration itself, but because of the fact that there is merely no documentation about this topic available. First, this will give you a graphical boot menu in LILO (not bootsplash) instead of the text driven menu default. To archive this, you'll have to do several steps. First step is to prepare a nice bmp picture to load. Second step takes you to the LILO configuration. First go ahead and get some nice picture and load it with gimp. Now resize you picture to 640x480 pixels and crop down the colors to 16. Next save it to '/boot' as an bmp picture. If gimp asks you for RLE compression, go ahead and select it. Second: Edit your '/etc/lilo.conf'. There is an important line, that has to be changed in order to get graphics, so be aware. As the file differs from system to system, I only point out the major changes here.


Code:

bash$ vi /etc/lilo.conf    #menu-title=" linuXbunker "      # THIS has to be deactivated    #menu-scheme=Wb               # THIS also    install = /boot/boot-bmp.b      # ATTENTION: this is NOT 'boot-menu.b'    #bitmap=imagefile (bitmap 640x480x16)    #bmp-colors=<foreground>,<background>,<shadow>,<highlighted-fg>,<highlighted-bg>,<highlighted-sh>    #bmp-table=<x>,<y>,<ncol>,<nrow>,<xsep>,<spill>    #bmp-timer=<x>,<y>,<fg>,<bg>,<sh>    # I use these settings for a bootmenu with 3 options with gentoo.bmp :    bitmap          =       /boot/gentoo.bmp    bmp-colors      =       15,0,0,0,15,15    bmp-table       =       105p,125p,1,5,,    bmp-timer       =       45p,300p,15,0,0


Thats it. Remember to change the IMPORTANT lines. Just mess around some with the 'bmp-*' settings, as a description is included. More information can be found in the 'man lilo.conf'. Now fire up lilo and reboot. If everything works fine, you're setup for some cool graphics boot menu.

Link Graveyard

General


Gentoo Installation Documents
Gentoo Forum
All important configs from my laptop


Specs and Handling


Acer Worldwide
Toms Hardware Guide


Compiler Flags


GCC Documetation
CFLAGS Thread Gentoo Forum
USE-Flags Gentoo-Howto
USE-Flags Description


Harddrive & 'hdparm' Optimization


O'Reilly hdparm Howto
hdparm Thread Gentoo Forum


Networking


Gentoo Forum Thread
NDisWrapper Homepage


PCMCIA


This tutorial


USB & Hotplug


pam_usb Project
PAM X509 Authentication Module


Graphics


Gentoo DRI Howto
Gentoo Forum Thread
Gentoo Forum Thread
Gentoo Forum Thread
Gentoo Forum Thread
DRI Project Homepage
FreeBSD DRI FAQ
FreeBSD DRI Troubleshooting Guide
DRI Patches by Alan H. from the XFree Project

Missing Items & later additions:

Later Additions


General Hints and Tricks
Optimization for speed, space, stability
Parallel-/USB-Printer & maybe CUPS
Crypted root partition
CD-Writer and DVD playback
fetchmail/procmail || exim solution
Funny things
udev (wget http://home.insightbb.com/~g.rude/Linux_patches/fb_sysfs_udev.patch)


Missing Items


Smartcardreader & keycard login/logout

_________________
have fun

feffi

/(bb|[^b]{2})/ that is the Question!

Gentoo-Wiki: Acer Travelmate 803 LCi manual

[feffi]

reserved for later addidtion due to limitations of this board...

[feffi]

reserved for later addidtion due to limitations of this board...

[feffi]

reserved for later addidtion due to limitations of this board...

[feffi]

reserved for later addidtion due to limitations of this board...