sudo apt-get install kubuntu-desktop

then, after booting into Kubuntu and trying it for a few weeks, I installed KDE 4.0 (or Kubuntu's version of that) by using the Adept Manager (Kubuntu's version of Gnome's (ubuntu's) Synaptic Package Manager) and doing a search for kde4.

First, though, you have to add this line to your sources list:

deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu hardy main

(don't forget to reload your sources afterwards!)

I actually installed several packages which came up, but all you need is one, which you can install through the terminal with this command:

sudo apt-get install kde4-core

Aggiungiamo il repository:

Gutsy:

deb http://ppa.launchpad.net/compiz/ubuntu gutsy main
deb-src http://ppa.launchpad.net/compiz/ubuntu gutsy main

Hardy:

deb http://ppa.launchpad.net/compiz/ubuntu hardy main
deb-src http://ppa.launchpad.net/compiz/ubuntu hardy main

Adesso apriamo Synaptic, ricarichiamo e avremo disponibile la nuova versione.

Vai qui per vedere la guida completa su come personalizzare Ubuntu.

First, we need to install the libraries that allow Linux to read the sensors. Type the following command in a Terminal to install the libraries for the motherboard:

sudo apt-get install lm-sensors

To install the libraries for the hard-disk sensors, type the following command:

sudo apt-get install hddtemp

The installation program will ask you a few question. First, it wil ask you if it should run as a daemon.

Answer 'yes'.

It will then ask which interfaces it should listen to. I put 0.0.0.0 to listen to all.

The next screen is related to the port: leave the default value.

The libraries are now installed and we are going to detect the sensors. Type the following command in a Terminal:

sudo sensors-detect

Answer "YES" to all the question. Be careful not to just hit enter, but to type YES (because the default answer for the last question is No, and we want to answer Yes to that one as well).

The sensor modules are going to be automatically loaded by default the next time we start up the comptuer. So let's just do that.

We can now check if it works by trying to monitor the sensors. Type the following command:

sensors

It should display the temperatures for the hardware items for which sensors have been detected.

We are now going to add a graphical interface for the sensors. Type this command in a Terminal:

sudo apt-get install sensors-applet

Add the applet by doing a right click on the desktop panel, and select "Add to Panel"

Select the applet called "Hardware Sensors Monitor" in the System & Hardware section, and click on add.

You should now have the sensors displayed on the panel.
You can right click on any of the applets and select Preferences.
The first tab is for general settings, and the options are easy to understand.

For update intervall, choose a value between two and ten.

The second tab allows you to select the sensors you want to enable.

In pochi minuti avevo tutti i pacchetti pronti senza errori e li ho installati con un

[sourcecode language='css']sudo dpkg -i *.deb[/sourcecode]e riavviato compiz. Voilà... tutto aggiornato e nuovi plugin disponibili.
Dalle prove che ho fatto, sembra tutto ancora più veloce, anche sul mio vetusto notebook.

Dunque, dato che l'indaffarato Treviño non aggiorna ormai da tempo i suoi repository (sperando che ormai riprenda con Hardy), vi metto qua un archivio contenente tutti pacchetti necessari.
Non vi resta che estrarlo in una cartella, "entrarci" da terminale e digitare il comando che ho riportato sopra.

Chiaramente essendo una versione git di sviluppo, non sono da escludere bug e piccoli malfunzionamenti... ma se vi va di aggiornare e sperimentare... ;)

Here you are:  compiz-fusion_0.7.3~git20080323-ubuntu-debs.tar.bz2 Ricordo che tali pacchetti funzionano solo su Ubuntu 7.10 "Gutsy Gibbon" e architettura x86/i386

Edit:
Seguendo il mio esempio anche M0rF3uS ha creato dei pacchetti e li ha inseriti nel suo repository, sia in versione i386 che amd64.
Inseritelo nella vostra sources.list se volete avere dei pacchetti di Compiz Fusion aggiornati, d'ora in poi! ;)

Heute etwas völlig Nebensächliches für die meisten Blog-Leser hier. Ist eher für die Leute gedacht, die per Google oder anderen Suchmaschinen auf dieses Blog stoßen. Der Nicht-Suchmaschinen-Leser sei also gewarnt: Achtung! Extremer Technik-Beitrag! Wahrscheinlich völlig uninteressant!

Wie ich bereits im Blog geschrieben habe, habe ich mir vor ein paar Tagen ein Notebook geleistet, genauer gesagt ein HP 6720s (das zwar von Compaq produziert wird, aber trotzdem das HP-Logo trägt). Unter Windows Vista lief alles perfekt, aber es gab einige Probleme mit meiner geplanten DualBoot-Installation von Ubuntu.

Zunächst einmal weigerte sich die Gutsy-Live-CD, die Festplatte korrekt zu partitionieren und wollte immer nur eine neue Partition einrichten, meckerte aber anschließend, dass man keine swap-Partition eingerichtet habe. Nach einigem Herumprobieren ergab sich für mich folgende bequeme Lösung: Unter Windows Vista mit dem Microsoft-Partitionierungsprogramm (ist standardmäßig beigelegt; einfach in der Hilfe nach "Partition erstellen" suchen) die gewünschten Partitionen für das zukünftige Linux-System als NTFS-Partitionen erstellen (also schon mit der später angepeilten Größe). Dann die Live-CD starten und bei dem Installationsschritt "Partitionierung" Manuelle Partitionierung wählen. In dem folgenden Menü wählt man die unter Vista erstellten Partitionen aus (Achtung: Diese tragen nicht die Volume-Bezeichnungen, die man ihnen in Vista verpasst hat, man muss sie anhand ihrer Größe herausfiltern) und formatiert diese mit einem neuen Dateisystem. Jetzt klappt erst einmal die Installation!

Anschließend gab es für mich das Problem, meinen WLAN-Chip zum Laufen zu bewegen. Eigentlich hatte ich gedacht, dass die Verwaltung proprietärer Treiber unter Ubuntu Gutsy zuverlässig funktioniert, dem war allerdings nicht so. Ich konnte den WLAN-Chip zwar wunderbar einrichten, aber zum Laufen bewegen ließ dieser sich nicht. Trotz längerem Herumprobieren in diversen Netzwerkmanagement-Tools von Ubuntu war kein Netzwerk-Scan möglich.

Ein Hilferuf bei Ubuntuusers brachte Hilfe: Man wies mich auf eine Anleitung im Ubuntu-Wiki hin, mit der man den proprietären Treiber auf die Blacklist setzen und die WLAN-Verbindung mit ndiswrapper herstellen könne. Die Anleitung für Broadcom-Chips findet sich hier. Auf meinem HP 6720s liefen alle Schritte einwandfrei durch, nach einem Reboot wurden gleich mehrere Drahtlosnetzwerke gefunden. Bei Problemen mit Broadcom-Chips würde ich empfehlen, einmal genau die Anweisungen aus diesem Dokument zu befolgen, damit sind wirklich alle Fehlerquellen abgedeckt.

Nachtrag! Nach dem Update auf Ubuntu 8.04 "Hardy Heron" ging das W-LAN erst einmal nicht mehr. Ich fand relativ schnell heraus, wie sich der WLAN-Treiber unter Hardy wieder zum Laufen bewegen lässt. Zum manuellen Start des Treibers benötigt man eine Serie von Kommandos in der Shell (für Linux-Neulinge: auch Terminal genannt, das Linux-Pendant zur Windows-Eingabeaufforderung). Es kann passieren, dass bei den ersten beiden Befehlen Fehlermeldungen ausgegeben werden. Einfach ignorieren und weitermachen.

sudo rmmod b43
sudo rmmod b44
sudo rmmod ssb
sudo rmmod ndiswrapper
sudo modprobe ndiswrapper
sudo modprobe ssb

Damit bekommt man erst einmal den Treiber wieder in Bewegung, allerdings wird er nun nicht mehr bei jedem Systemstart geladen - doch auch das lässt sich automatisieren! Dazu nötig ist die Datei /etc/rc.local (nicht der Ordner, die Datei!). In dieser Datei stehen alle Befehle, die beim Systemstart ausgeführt werden sollen. Um bei jedem Bootvorgang den WLan-Treiber zu starten, müssen folgende Zeilen in die Datei eingefügt werden (wichtig: die Zeile mit dem Inhalt exit 0 muss immer am Ende der Datei stehen, sonst wird das Skript beendet, bevor die gewünschten Kommandos ausgeführt werden):

rmmod ssb
rmmod ndiswrapper
modprobe ndiswrapper
modprobe ssb

Jetzt sollte der Treiber bei jedem Systemstart automatisch gestartet werden - also alles so wie vorher!

So, jetzt ist aber endgültig Schluss mit Tech-Beiträgen.

Hoy me ha llegado de regalo un dispositivo bluetooth usb. Cualquiera de ustedes se podría imaginar que estoy hablando de un dispositivo dlink , lynksys o alguna otra marca de renombre mundial. Pero no, estoy hablando de un dispositivo bluethoot usb que ni siquiera tiene marca. También llamados acá en Chile como marca acme, chancho, chanta, etc. Pero como para un geek con tiempo pasar horas en el pc investigando pueden ser parte de sus vacaciones, es que me puse a investigar sobre el manejo del notebook con mi celular usando este particular dispositivo bluetooth.

El primer experimento que vamos a hacer sera conectar en forma óptima el dispositivo usb a nuestro ubuntu gutsy. Pese a lo que muchos podrían pensar no tuve ningún problema para que gutsy me reconociera el dispositivo. Pero para eso debemos instalar los siguientes programas:

$ sudo aptitude install bluez-utils gnome-bluetooth

Ahora por si la moscas ...

$ sudo /etc/init.d/bluetooth restart

¿que vamos a hacer ahora?.. Ahora vamos a instalar todos los programas necesarios para usar nuestro celular como control remoto para controlar nuestros reproductores multimedia como amarok, xmms y rhythmbox. Se debe instalar un cliente y servidor de remuco. Este programa permite controlar los reproductores ya mencionados a través de bluetooth con una aplicación java instalada en nuestro celular.

Comencemos...

1- Descargas el .deb del programa que quieras controlar. Yo uso los tres asi es que baje e instale los tres programas.

Amarok

Rhythmbox

XMMS

Doble click o aplicamos...

$ sudo dpkg -i nombredeprograma.deb

2- Bajamos el programa cliente (java) para instalarlo en nuestro celular. Descargalo aquí.

El archivo que acabamos de bajar posee en su interior tres carpetas, cada uno con un programa cliente distinto. Desde mi punto de vista, el simple y el canvas son bastante buenos. Este ultimo tiene una interfaz gráfica en forma de reproductor multimedia. Las canciones se cambian con el joystick con la flecha hacia arriba y hacia abajo, mientras que el volumen se maneja con las flechas de los lados. El simple posee una interfaz gráfica mas “simple, obvio” en modo texto que es perfectamente funcional y se maneja con los botones de selección. Posee un menú lateral con el que se puede cambiar el volumen entre otras cosas.

Cualquiera haya sido tu elección tendrás que enviar el archivo remuco.jar a tu celular y dependiendo del modelo que poseas proceder a instalarlo. Seria recomendable que lo hagas vía bluetooth para que pruebes que tal el soporte. La primera vez que te conectas con tu celular tendrás que ingresar el pin que debe ser el mismo en tu computador y en tu celular. Yo poseo un sonyericsson y posteo las imágenes de la instalación del programa. En todo caso no es nada diferente a la instalación de los típicos juegos java que la gran mayoría tiene en sus celulares.

3- Una vez que tengas todo instalado debes echar a correr el programa servidor. Dependiendo del programa que quieras controlarlo tendrás que ejecutar el siguiente comando:

para amarok : remuco-amarok

para xmms : remuco-xmms

para rhythmbox : remuco-rythmbox

4- Buscar en el menú aplicaciones de tu celular el programa remuco. Obviamente tienes que echar a correr el programa servidor en tu equipo y luego el programa de tu celular.

5- Yo se lo que están pensando ustedes.... es una lata escribir el comando para echar a correr el servidor, luego lanzar el reproductor y luego el programa en tu celular. Bien... Yo me cree un script de esta forma.

Para rythmbox lo abrí un archivo de texto, pegue lo siguiente y lo guarde con el nombre remury.sh

#!/bin/sh

#Start both programs.

rhythmbox &

sleep 2

remuco-rhythmbox &

#Wait until rhythmbox closes.

wait %1

kill -s INT `pidof remuco-rhythmbox`

Luego cree un lanzador a ese scrpit, le puse un icono bonito y eso seria todo. Ahora si tu quieres utilizar otro reproductor, te recomiendo que solo cambies rhythmbox por xmms o amarok en el script anterior.

Eso seria todo, espero les haya servido esta pequeña guía.

saludos

OS X is without a doubt the easiest OS for configuring Bluetooth devices. Adding phones, keyboards and headsets is (more or less) as easy as it could be. Windows is way behind. You can add your phone, but where OS X automatically sets up the phone as a modem connection, you will have to download some PC Suite crap or hack your way onto the phone. Ubuntu is somewhere between Windows and OS X, but (sad to say) closer to Windows.
So, to ease the pain, here's a how to use your Nokia to connect to the Internet in Ubuntu. I'm using Ubuntu Gutsy Beta 4 and a Nokia N82. Everything should be pretty much the same for older Ubuntu versions and other Nokias.

Everything in the guide is really (that is, when you're following it) without the quotes.

a

1. Install needed applications
a

1. Go to System - Administration - Software Sources
2. Select Third-Party Software and add "deb http://download.tuxfamily.org/blueman ubuntu bluetooth"
3. Close Software Sources. It will ask for permission to update. Yes, you'd like that...
4. Go to System - Administration - Synaptic ...
5. Find "blueman" and "gnome-ppp", mark them for installation and click Apply
6. When done, all open applications can be closed

a

2. Configure Blueman
a

1. Start Blueman from Applications - Accessories
2. Click Inquiry, select your phone and click Bond
3. Type the same pin on both your computer and your phone and the bonding should be successful
4. With the phone selected, click Other and select "Set trusted"
5. Now go to Edit and select Services
6. Enable Serial, check autostart and click the configuration button
7. From the Host dropdown, select your phone
8. From the Service dropdown, select "dun: Dial-Up Networking" and click Add Port
9. When done, Blueman can be closed

a

3. Configure the dial-up
a

1. Start GNOME PPP from Applications - Internet
2. Click Setup and write "/dev/rfcomm0" in the Device field
3. Under Options, I recommend you check "On connect Dock in notification area"
4. Click Close
5. If you have gotten your own unique username, password and phone number, write those in
6. Otherwise, write your phone number as username and password and *99***# as phone number""
7. "Remember password" must be checked (this is a bug)
8. Now, click Connect

How to connect in the future

1. Start GNOME PPP and click Connect

a

UPDATE 8th of May 08

How to use the data cable / usb cable instead of bluetooth

1. Connect the phone with the cable
2. In 3.2, where you type /dev/rfcomm0, click Detect instead.
3. Close and Connect

To use it:
Use ./configure and make, like you would normally do, but instead of doing make install, type checkinstall -D make install. This command will create a .deb package that can be installed (and uninstalled) with Synaptic package manager.

If, after installing VLC, you cannot play some videos (with an error message like the following one), try installing gstreamer.

Type the following command in a Terminal

sudo apt-get install gstreamer0.10-ffmpeg

If it's still not working, then type the following command in a Terminal

sudo apt-get install totem-gstreamer

And if it's still not working, then try installing mplayer

sudo apt-get install mplayer

The final "extreme" solution would be to install all gstreamer plugins

sudo apt-get install gstreamer0.10-\*

AllTray allows you to dock any application with no native tray icon into the system tray.

First, you need to install AllTray:
Open the Synaptic Package Manager

Click on the "Search" button, and type alltray in the search window.
Once AllTray is found, right click on it and select "Mark for installation".

After the installation of AllTray, close Synaptic Package Manager

Open Gnome Terminal from Applications / Acccessories / Terminal.
After it is open, select Edit / Profiles

Press the "New" button.

Give the new profile a name (TransparentTerminal) and click on "Create".

Uncheck "Show menubar by default in new terminals".

Go to the Effects tab, select "Transparent background" and set the transparency to None.

Go to the Scrolling tab, and select Disabled from the drop-down list.

Close the editing profile window, and in the Profiles dialog, select the profile that you have just created from the "Profile used when launching a new terminal" drop-down list, and close it.

Create a new launcher on the desktop: right click on the background and select "Create Launcher..."

Go to Zattoo web site (http://zattoo.com/), sign in and download the zattoo package for Debian / Ubuntu (.deb).

Right click on the downloaded package, and select "Open with GDebi Package Installer".
Click on "Install Package". Some additional packages may be downloaded.

Enjoy the TV on you PC from the Internet.

Add first the medibuntu repository (if not already done) to your list of repositories.
Start by adding the gpg key using the following command:
wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add -

Then add the medibuntu repository to your sources list:
sudo wget http://www.medibuntu.org/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/medibuntu.list

Then, update the sources list:
sudo apt-get update

Then, install Acrobat Reader and the plug-in for Firefox with the following command in a terminal:

sudo apt-get install acroread mozilla-acroread acroread-plugins

First, we need to add the Medibuntu repository: Medibuntu (http://www.medibuntu.org/) is a packaging project dedicated to distributing software that cannot be included in Ubuntu for various reasons, related to geographical variations in legislation regarding intellectual property, security and other issues.

To add the Medibuntu repository to your system's list of APT repositories, type the following command in a terminal:
sudo wget http://www.medibuntu.org/sources.list.d/gutsy.list -O /etc/apt/sources.list.d/medibuntu.list

Then, add the GPG Key, with the following command in a terminal:
wget -q http://packages.medibuntu.org/medibuntu-key.gpg -O- | sudo apt-key add - && sudo apt-get update

To play encrypted DVDs, the libdvdcss2 package is essential. libdvdcss is a simple library designed for accessing DVDs like a block device without having to bother about the DVD decryption. Type the following command in a terminal:
sudo apt-get install libdvdcss2

There are a few formats such as certain Windows formats, Real, and Apple Quicktime which do not have native codecs under Linux. The needed package is called w32codecs and can be installed with the following command:
sudo apt-get install w32codecs

That's it: you should now be able to play DVDs and videos. If you want to install an "almost universal" video player, VLC is a good choice. I will report its installation in another post.

Second solution: the linux-backports-modules-generic
The second solution is to install the backports generic modules. Open a terminal and type the following command:

sudo apt-get install linux-backports-modules-generic

Edit the file /etc/modprobe.d/alsa-base

sudo gedit /etc/modprobe.d/alsa-base

and add the following line at the end of the file:

options snd-hda-intel model=acer

Reboot, and everything should work (well, at least, external speakers and headphones are working, but I have still not tested the internal microphone or an external one).

I've found two solutions to resolve, at least partially, this issue.

First solution: install the latest drivers from Realtek
The first solution that I have tried is to install the last drivers from Realtek. Those drivers can be downloaded from here. Go to the Unix (Linux) section and download the file to your hard drive (home folder is a good location).

Make sure that you have the last version of the Linux kernel as well as the libncurses5-dev by doing the following command in a terminal:

sudo apt-get install build-essential linux-headers-generic libncurses5-dev

Unpack the file that you have downloaded from Realtek web site, with the following command:

tar -jxvf realtek-linux-audiopack-4.07b.tar.bz2

(the name of the file could be different, depending on which version is the current one).

Move to the folder that has been created:

cd realtek-linux-audiopack-4.07b

Type the following command to compile and install the driver:

sudo ./install

After the compilation, the installer will start and you will have to answer to a series of questions.

When the installer asked me to choose a sound card, I just pick the first choice (but I did not really know at that stage if it was the correct choice).

I let the installation configuring /etc/modprobe.d/sound and /etc/modprobe.conf if present

At the end of the installation, the sound card was not working yet.

But after rebooting, the sound was working (at least the front speakers and headphones), but each time the PC is rebooted, the sound volume is set back to mute. So, I looked for another solution, which I will describe in the next post.

What I did instead is download Flash for Linux from the Adobe web site and install it myself.

After downloading the file, unpack it on your computer by typing the following command in a Terminal:

tar xvfz install_flash_player_9_linux.tar.gz

Then move to the unpacked folder (install_flash_player_9_linux) with the following command:

install_flash_player_9_linux

Close any opened browser, and start the installation with the command:

./flashplayer-installer

Answer to the various questions asked by the installation program, and at the end of the procedure, Flash Player should be installed on your computer.

Installing Thunderbird is quite easy: it is available as a package in Synaptic Package Manager, so this is where one can find it and start the installation.

Since I had a backup of my Thunderbird profile from my previous computer, I am going to install this profile in Thunderbird on my new computer. The Thunderbird profile (which contains all settings for emails accounts, the extensions that where installed, all the e-mails, ...) is stored in a folder in:

/home/.mozilla-thunderbird/

and as for name a code (something like "fxt8zbe9.default"). This is this last folder that you must put on a USB key, or a burn on a CD.

Once Thunderbird has been installed, you can start it, and when it ask you if you want to import previous preferences, settings, ..., you just select "Don't import anything".

Thunderbird will then launch the Account Wizard.

Again, you do not create any account, and you click on Cancel an then on Exit to confirm.

You can then close Thunderbird and copy your backup profile to the Thunderbird folder (/home/.mozilla-thunderbird). You can then delete the existing profile (the one that was installed by Thunderbird).

The last step is to edit the file called "profiles.ini" and, at the last line, to replace the name of the default profile folder by the name of your backup profile folder. After saving, you can start Thunderbird, and all your e-mails, preferences, add-ons, will be installed in Thunderbird.

The sound card is not working: I do not have any sound out of the loudspeakers or out of any headphones connected to the laptop. I guess that I do not have any sound out of any microphone (either an external one connected to the PC, or from the internal one). I will try to resolve that after installing the basic tools I need.

My first intention was (and still is) to install any Linux distribution on it: Ubuntu as a first choice, and any other one if Ubuntu was not working well enough on this laptop. Since I did not check the compatibility of this Acer computer with Linux before buying it, I didn't really now what to expect.

In this first post, I will just describe the first installation of Ubuntu Gutsy (7.10) on this computer. In the next posts, I will go over the post-installation operations that were necessary to make the computer work (since I am not expecting that Ubuntu will just "work out of the box" on this new laptop, especially since it's using the new Santa Rosa technology.

Here are the characteristics of the TravelMate 6292:

• Intel^® Centrino^® Duo mobile processor technology
• Integrated Intel^® GMA X3100 3D graphics
• Sound card codec is Realtek ALC268
• Wifi is Intel 4965AGN
• 2 Gb RAM
• 160 Gb hard drive
• Acer Crystal Eye webcam
• 5-in-1 card reader
• Acer Bio-Protection fingerprint solution
• Bluetooth^®

Dengan pertimbangan diatas maka muncullah berbagai macam aplikasi yang free dan tentunya semua kalangan dapat menjangkau karena murah dan juga tidak membutuhkan spesifikasi komputer yang cukup besar, dengan kata lain dapat juga dijalankan pada komputer yang mempunyai spesifikasi standart bahkan hampir ketinggalan jaman yang hanya bisa digunakan oleh komputer wartel dan harganya + 400rb saja anda bisa menjalankan transakasi perdagangan dengan cara yang sitematis...... mudah khan....

KASIR POIN OF SALE (POS Linux ala rab.co.id)

Transaksi penjualan, ialah transaksi yang berhubungan dengan daftar barang antara barang yang dijual ataupun barang yang dibeli oleh pembeli barang, secara langsung semua transaksi yang ada terekam dalam database dan secara default pula barang yang berada pada stock akan terkurangi.

Stock barang, stock barang berisi daftar barang sudah kita beli kepada produsen dan juga otomatis ditambahkan kedalam database dengan barang tersisa.

Stock Opname, biasanya hanya digunakan untuk mencocokkan barang yang ada di toko dan juga stock barang yang ada di database komputer kasir, dengan kata lain antara stock barang yang ada di toko haruslah sama dengan jumlah barang yang tertera di komputer kasir. Biasanya stock opname dilakukan per minggu, bulan, bahkan tahun.

Berikut Cara Instalasinya Pada Ubuntu :

Karena kita menggunakan program kasir gratis yang berada di http://rab.co.id jadi kita pelukan adalah repository dari http://rab.co.id.

Tambahkan repo pada list di bawah ini

$ sudo gedit /etc/apt/sources.list

 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 01)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0b:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01)

Il Pinguino si trova molto a suo agio su questo laptop, dato che l'installazione (Ubuntu Gutsy) fila liscia come l'olio e ci sono solo un paio di "ritocchi" da fare.

Il primo, e più curioso, dei ritocchi consiste nell'eliminare il noioso problema dello schermo che si abbuia continuamente quando siamo alimentati a batteria; a nulla vale modificare le relative opzioni nel power manager, dopo qualche secondo lo schermo diventa scurissimo, e l'unica soluzione è ritirare su la luminosità con i tasti di funzione.
Non ho ancora capito esattamente cosa sia che lo fa abbuiare, ma credo che abbia a che vedere con il sensore d'ambiente, che in questa configurazione non c'è ma all'analisi dei valori di gconf di gnome-power-manager, risulta abilitato.
Per soluzionare il problema, l'unico modo è stato disabilitare completamente la gestione della lampada dello schermo, impostando a zero il valore della chiave apps -> gnome-power-manager -> backlight -> enable tramite gconf-editor. Così facendo si perde ovviamente una parte importante del risparmio energetico, ma si può sempre impostare a mano la luminosità di volta in volta.
Sono graditi suggerimenti, se qualcuno ne ha.

Il secondo ritocco consiste nel far funzionare il microfono (che è solo esterno in questo modello): è stato sufficiente aggiungere la riga seguente in fondo al file /etc/modprobe.d/alsa-base:

 options snd-hda-intel index=0 model=auto

Il test dell'input audio continuerà a dare errore nella costruzione della pipeline, ma l'input funzionerà lo stesso :)