Archivi categoria: Gentoo

NVidia on Linux: IRQ error «nobody cared»

Well, I’ve got a marvellous nVidia 9800 GTX. I run KDE4 with KWin effects enabled.

It has happened many times that after some random hours of usage overall KDE performance dropped to the floor: moving windows was nearly impossible, desktop effects stopped working, writing in the Konsole was slow…

But the system was not unresponsive: SSH (and everything not related to the X server) was working as usual.

Since I was too lazy to investigate it, I simply restarted the X server (or closed and reopened my KDE session) when it happened.

Some days ago I took a look at dmesg | tail and found this string:

kernel: irq 16: nobody cared (try booting with the "irqpoll" option)

followed by a (stack?) trace.

So it was an IRQ problem. Looking at /proc/interrupts revealed that the interrupt #16 was shared between my nvidia card, a pata_jmicron thingy and an usb port.

After googling a little I found that you can (actually you should) put the nvidia card on MSI system (see this wikipedia entry).

You simply tell the nVidia module (loaded at startup) to use MSI rather than old pci irqs, by writing a file in /etc/modprobe.d/:

# nano /etc/modprobe.d/MSIfixes.conf
options nvidia NVreg_EnableMSI=1

Then you should unload the module and reload it (well, it’s easier to do a reboot).

I haven’t had that annoying freeze issue ever since I put MSI in the game.

On a side note, hda_intel module supports MSI too:

options snd_hda_intel enable_msi=1

=-=-=-=-=
Powered by Blogilo

Contrassegnato da tag , , , ,

Vai, Facciamolo!

Come buttare via i soldi faticosamente guadagnati?

  • Processore: Intel Core2 Quad Q9450 (12MB cache, 2,66GHz, 1333MHz FSB), circa 320€ 250€
  • Scheda Madre: Asus Rampage-Formula 90 (PCIe 2.0, chipset X48, 1600MHz FSB), circa 250€ 210€
  • Scheda Video: nVidia GeForce 9800 GTX (512MB della XFX), circa 270€ 250€
  • Monitor: Iiyama E2201W (22″, 1680x1050px), circa 320€ 286€
  • HD: due Maxtor SATA da 250GB (che ho già)
  • Case: ehehehehehehe! A Silvio non piacerebbe!

 
Finora questa è la lista delle cose da comprare. Mancano alcune cose importanti:

  • Memoria RAM? Trovata! Corsair Dominator DDR2 1066MHz, 60€
  • Alimentatore?

 
Invece sul sistema operativo non ci dovrebbero essere dubbi :D solo che…

  • Gentoo?
  • Sabayon?
  • Arch?
  • Debian?
  • Kubuntu?
  • vogliamo provare anche Fedora?
  • Slackware?

 
Il DE non sarà un problema: KDE4!

I programmi…

  • openoffice.org
  • urban terror
  • enemy territory
  • gimp
  • blender
  • inkscape

 
E poi…

  • apache
  • php
  • mysql

 
Insomma, non è facile farsi un nuovo computer! No proprio! Avete dei consigli, voi?

Gentoo Per Pigri

Se siete come me non avete voglia di battere le dita sulla tastiera per fare un emerge –ask –update –world.

(Specialmente quando vi svegliate la mattina, guardate le Alpi fuori dalla finestra e il vostro stato di pace viene rotto dalla mutter che sbraita).

Bene, la killer app di oggi è Kuroolinkgo! E sapete cosa? È già presente negli ebuilds distribuiti da Gentoo! Quindi basta fare un emerge kuroo et voilà, gioco fatto.

Cosa fa? Esattamente le stesse cose di Synaptic e Adept. Su Gentoo+KDE, però.

Come le fa? Da dio! Upgradare il sistema non è mai stato così facile: sposta il mouse, click, mouse, click, mouse, click, caffè e sistema aggiornato.

Ah, last but not least: ha anche l’interfaccia a etc-update!

Oggi sono un pigro contento di esserlo happy

Contrassegnato da tag , , , ,

CONFIG_CONFIG_KMOD is not set

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

 *   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-0.9.3.3 failed.
 * Call stack:
 *                   ebuild.sh, line 1717:  Called dyn_setup
 *                   ebuild.sh, line  768:  Called qa_call 'pkg_setup'
 *                   ebuild.sh, line   44:  Called pkg_setup
 *   madwifi-ng-0.9.3.3.ebuild, 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-0.9.3.3/temp/build.log'.
 *

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: libexpat.so.0: 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: libexpat.so.0: 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 libexpat.so: it’s /usr/lib/libexpat.so

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/libexpat.la lrwxrwxrwx 1 root root     17 Oct 29 14:17 /usr/lib/libexpat.so -> libexpat.so.1.5.2 lrwxrwxrwx 1 root root     17 Oct 29 14:17 /usr/lib/libexpat.so.1 -> libexpat.so.1.5.2 -rwxr-xr-x 1 root root 141456 Oct 29 14:17 /usr/lib/libexpat.so.1.5.2

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

root@smokey#  ln -s /usr/lib/libexpat.so /usr/lib/libexpat.so.0

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 libexpat.so instead of libexpat.so.0. But as you may guess i was pissed enough to dig deeply into crappy conf files. And what if there was another app requiring libexpat.so.0? 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 , , , , , , ,