Archivi categoria: Fujitsu-Siemens S2110


Today I upgraded my Gentoo kernel to 2.6.23 version, but I had this problem when emerging madwifi-ng:

 * Messages for package net-wireless/madwifi-ng-

 *   CONFIG_CONFIG_KMOD:         is not set when it should be.
 * Please check to make sure these options are set correctly.
 * Failure to do so may cause unexpected problems.
 * Once you have satisfied these options, please try merging
 * this package again.
 * ERROR: net-wireless/madwifi-ng- failed.
 * Call stack:
 *         , line 1717:  Called dyn_setup
 *         , line  768:  Called qa_call 'pkg_setup'
 *         , line   44:  Called pkg_setup
 *   madwifi-ng-, line   34:  Called linux-mod_pkg_setup
 *            linux-mod.eclass, line  465:  Called linux-info_pkg_setup
 *           linux-info.eclass, line  576:  Called check_extra_config
 *           linux-info.eclass, line  475:  Called die
 * The specific snippet of code:
 *              die "Incorrect kernel configuration options"
 *  The die message:
 *   Incorrect kernel configuration options
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/net-wireless/madwifi-ng-'.

Of course KMOD (automatic kernel module loading support) was set. Damn developers!bombabomba

So I had to:

  1. open /usr/src/linux/.config
  2. look for CONFIG_KMOD and check tiat it wass indeed set (CONFIG_KMOD=y), otherwise one should have to recompile the kernel.
  3. add a line below: CONFIG_CONFIG_KMOD=y (yes, it makes me laugh too)
  4. save & close /usr/src/linux/.config
  5. emerge madwifi-ng
  6. re-open /usr/src/linux/.config
  7. delete the previous added line CONFIG_CONFIG_KMOD=y, save and exit.

I guess the bug should be resolved by madwifi developers, but was caused by kernel developers happily removing a CONFIG_ here and there…

error while loading shared libraries: cannot open shared object file: No such file or directory

EDIT!!! The right way to fix this (and similar problems) is:

emerge gentoolkit
revdep-rebuild -X

It appears that the libexpat problem was caused by Gentoo developers releasing too many updates without cross-checking them.

I got this error in Gentoo, after doing an “emerge world”. I’m using an AMD64 Turion laptop.

/usr/bin/dbus-daemon: error while loading shared libraries: cannot open shared object file: No such file or directory

dbus didn’t start, so hald couldn’t start, and finally kpowersave wasn’t able to read the battery state.

You’ll agree with me that it is pretty annoying if you have a 3h25m battery life laptop.

Here’s how I solved the problem:

1) First of all, I found the path to it’s /usr/lib/

root@smokey# ls -l /usr/lib/libexpat* -rw-r--r-- 1 root root 250620 Oct 29 14:17 /usr/lib/libexpat.a -rw-r--r-- 1 root root    795 Oct 29 14:16 /usr/lib/ lrwxrwxrwx 1 root root     17 Oct 29 14:17 /usr/lib/ -> lrwxrwxrwx 1 root root     17 Oct 29 14:17 /usr/lib/ -> -rwxr-xr-x 1 root root 141456 Oct 29 14:17 /usr/lib/

2) As you can see, there’s no such thing as a in /usr/lib. But there is a referenced by itself. So I made a symbolic link named pointing to

root@smokey#  ln -s /usr/lib/ /usr/lib/

bell.png Be warned: this may not be the right thing to do. I should have checked the configuration file of the dbus daemon, and changed it to reference instead of But as you may guess i was pissed enough to dig deeply into crappy conf files. And what if there was another app requiring You can never guess when a developer/mantainer will fail you.

3) Finally, fire up those lazy dbus and hald daemons:

root@smokey# /etc/init.d/dbus start  * Starting D-BUS system messagebus ... root@smokey# hald start

Tch… That was easy, man. happy And my battery is the best, you’ll never beat me in powersaving.

Contrassegnato da tag , , , , , , ,

Gentoo on a Fujitsu-Siemens S2110 Laptop

After 3 days of struggling, extensive compiling and binge drinking I managed to get Gentoo to work on my Fujitsu-Siemens s2110 laptop:

And not only work, but work fast and do everything!

This laptop has always been problematic, so I hope this guide will help many desperate owners.

Continua a leggere

Contrassegnato da tag , , , , , , ,

Debian And Slow Touchpad

The Problem: some touchpads are REALLY slow under Debian, you have to tap like a piano player to get the little arrow from one window to another.

And yes, this is really annoying since everything works fine with an USB mouse.

Even worse, you didn’t notice the problem with an Ubuntu installation. But you don’t want any brown hot nasty things on your precious laptop.

The solution was here. Maybe you’ve got an ALPS touchpad, not a Synaptics one! Eureka! lampadina

Wanna know what to do? Read on! happy
Continua a leggere