If you are reading this post you must know by now that the GHWT is not supported by the libcwiid1 found in the repositories.
This leaves as an only option compiling it from source.
The source of version 0.6 can either be picked up from
the old location of the project http://abstrakraft.org/cwiid/,
or from
the new location on GitHub http://abstrakraft.github.com/cwiid/.

At the end of this post i will post a script for each one of the options since the sources seem to differ.
The version from Github is meant to work as soon as compiled with GHWT. For me, no matter what guitar script i use it did not.
I will anyway present it as an option for the truth’s sake.

Installing Cwiid 0.6 From the old project page
*I suggest you go through this procedure and read it at least one to know what’s happening. Otherwise, you can jump at the end and either download the script or the .deb package.

We need to install necessary dependencies from this.
sudo apt-get install automake autoconf flex bison libbluetooth3 libtool checkinstall -y

Pick up the source from the site:
wget http://abstrakraft.org/cwiid/downloads/cwiid-0.6.00.tgz

Extract and move to the working dir:
tar zxvf ./cwiid-0.6.00.tgz
cd ./cwiid-0.6.00

This is the old version that does not support GHWT but it can be patched to do so.
It can be found here http://abstrakraft.org/cwiid/ticket/79.
*This patch is meant to be applied to the source from svn. So the path of the files is hardcoded id it with ‘trunk/’ preceeding.
Quick dirty trick:

mkdir trunk/
mv ./* trunk/

Afterwards there is a second patch that will need to be applied.
During the make process this error came up:
gcc -g -Wall -W -DHAVE_CONFIG_H -I/home/dreamer/src/cwiid/common/include -fpic -c -o bluetooth.o bluetooth.c bluetooth.c: In function ‘cwiid_get_bdinfo_array’: bluetooth.c:125: warning: implicit declaration of function ‘hci_remote_name’

In fact the name of the function needs to be hci_read_remote_name.
This patch can be found here : http://abstrakraft.org/cwiid/ticket/74.

Basically this is what just happened after creating and moving to the trunk folder:
wget http://abstrakraft.org/cwiid/raw-attachment/ticket/79/guitar.diff -O ./guitar.diff
patch -p0 < ./guitar.diff
cd trunk/
wget http://abstrakraft.org/cwiid/raw-attachment/ticket/74/hci_read.patch -O ./hci_read.patch
patch -p0 < ./hci_read.patch

We are ready to continue with the compiling process.
Run the automated procedures to create the configure script
aclocal
autoconf

then we make and install
make
sudo make install

Making the uinput module known to the system
sudo depmod -a

Loading the module
sudo modprobe uinput

Editing the modules to make uinput present after a restart
sudo echo "uinput" >> /etc/modules

That’s it.

Script to automate this procedure :
http://www.mediafire.com/file/ytet0iydzqz/script_cwiid_0.6_patched_GHWT.tar.gz

64-bit Debian/ubuntu package :
http://www.mediafire.com/file/mqiaddzmmw4/cwiidghwt_0.1-1_amd64.deb

32-bit Debian/ubuntu package (from ubuntu forums since i am currently on a 64 it machine and could not package it) :
http://ubuntuforums.org/showpost.php?p=7741117&postcount=2

Installing the latest from GitHub

Installing the neccessary dependencies:
sudo apt-get install automake autoconf flex bison libbluetooth3 libtool checkinstall -y

Retrieving the latest Cwiid from github:
wget http://github.com/abstrakraft/cwiid/tarball/master

Extracting and Changing working dir
tar zxvf ./abstrakraft-cwiid-*
cd abstrakraft-cwiid-*

Run the automated procedures to create the configure script
aclocal
autoconf

then we make and install
make
sudo make install

Making the uinput module known to the system
sudo depmod -a

Loading the module
sudo modprobe uinput

Editing the modules to make uinput present after a restart
sudo echo "uinput" >> /etc/modules

Done.
Script to automate this procedure http://www.mediafire.com/file/ytet0iydzqz/script_cwiid_0.6_patched_GHWT.tar.gz

Testing the whole thing
sudo wminput
Put Wiimote in discoverable mode now (press 1+2)...

After you press 1+2 on the wiimote you should see righ under the above output:
Ready.

Now the configuration file that worked with my guitar is the following:
#buttons
Wiimote.A = BTN_LEFT
Wiimote.B = BTN_RIGHT
Wiimote.Up = KEY_UP
Wiimote.Down = KEY_DOWN
Wiimote.Left = KEY_LEFT
Wiimote.Right = KEY_RIGHT
Wiimote.Minus = KEY_BACK
Wiimote.Plus = KEY_FORWARD
Wiimote.Home = KEY_HOME
Wiimote.1 = KEY_PROG1
Wiimote.2 = KEY_PROG2
Plugin.led.Led4 = 1
# Profil wiiguitar
Classic.A = KEY_F1
Classic.B = KEY_F2
Classic.X = KEY_F3
Classic.Y = KEY_F4
Classic.ZL = KEY_F5
Classic.Down = KEY_ENTER
Classic.Up = KEY_ENTER
Classic.Minus = KEY_F6
#Classic.Dpad.X = ABS_X
#Classic.Dpad.Y = ABS_Y
#Classic.LStick.X = ABS_HAT0X
#Classic.LStick.Y = ABS_HAT0Y
#Classic.RStick.X = ABS_HAT1X
#Classic.RStick.Y = ABS_HAT1Y
#Classic.Plus = BTN_START
#Classic.Home = BTN_MODE
#Classic.L = BTN_TL
#Classic.R = BTN_TR
#Classic.ZR = BTN_TR2

Let’s say i’ve saved it as guitar_wii in ~/Desktop.
On the command line you would execute:

sudo wminput -c ~/Desktop/guitar_wii
Put Wiimote in discoverable mode now (press 1+2)...

After you press 1+2 on the wiimote you should see righ under the above output:
Ready.

This : https://help.ubuntu.com/community/AspireOne is a extremely detailed and useful page where i could find the solutions to both my problems.
For entirely different purposes , days after i had to reinstall ubuntu , so i though i need to automatize these procedures.

Th following two scripts are just a collage of instructions found in that page.
Since they spared me loads of repetitive effort in the following installations of other machines i thought i’d share:

Microphone Issue :
Downloads and installs the latest alsa driver : link

Wifi Issue :
Downloads and installs the latest madwifi driver : here

After that i’ve been meaning for a long time to write about the same procedure, but running Ubuntu now as an operating system.

First we need to install Python for Symbian (pys60). The .sisx file can be found on the project’s SourceForge page here.

Hardware used:
Dikom Bluetooth Usb Dongle : 00:02:72:XX:XX:XX
Nokia E61i : 00:17:E5:XX:XX:XX
Dell Dimension C521 running Ubuntu Intrepid Ibex (8.10)

The correct functioning of the BT dongle, BT service, and the pairing of the devices goes beyond the scope of this article.

From this point it is assumed that BT works correctly on your system, and that the devices are paired.

First we need to know if the BT dongle is up and running. Open a shell window and type:
hcitool dev

If everything is running properly, the output should be something similar to this:
sid@dev:~$ hcitool dev
Devices:
hci0 00:02:72:XX:XX:XX

The next two steps are quite a logical following :
1. Create a serial port on the pc
sdptool add --channel=3 SP

that should output:
Serial Port service registered

2. Start listening for connections on that port:
rfcomm listen rfcomm0 3

that should output:
Waiting for connection on channel 3

Now on the phone, enable bluetooth, start up the python shell the choose:
Options -> Bluetooth console and select from the devices list the BT device of the computer

Done this, on the phone screen’s python shell you should see something similar:
Connecting to ('00:02:72:XX:XX:XX', 3)... OK.
telling that the connection with our device succeeded.

Meanwhile on the command line, where we are listening for connections on the serial port 3, the output should be:

rfcomm listen rfcomm0 3
Waiting for connection on channel 3
Connection from 00:17:E5:XX:XX:XX to /dev/rfcomm0
Press CTRL-C for hangup

If you’ve gotten this far with these results, we’re all good and we have one more step left.

So far we have an active connection between these two devices.
Let’s tap into it with cu

The cu command is used to call up another system and act as a dial in
terminal. It can also do simple file transfers with no error checking.

Open another command line window and type:

cu -l /dev/rfcomm0

Th desired output is something like this:

cu -l /dev/rfcomm0
Connected.
Python 2.4#
>>>

And voilà. Done.

Now we can fiddle around and do some Python Mobile programming.

The very same procedure can be used with any application using a bluetooth serial port.

Synergy lets you easily share a single mouse and keyboard between multiple computers with different operating systems, each with its own display, without special hardware. It’s intended for users with multiple computers on their desk since each system uses its own monitor(s).

Says it all, and was exactly what i was looking for.

Synergy works with a client server architecture. The box that i mainly use, runs Ubuntu 8.04, and i will be using this one as a server. The other machine, that i want to share the input devices with , is my laptop, that i will be booting into Windows XP. This one will be the server.

Then we’ll try them also the other way around.
At the end, a couple of troubleshooting tricks.

Synergy can be picked up from it’s Sourceforge page here.

Ubuntu as Server

For Ubuntu, it can be found in the repositories.

sudo apt-get install synergy

This will install two binaries:
synergys – the server
synergyc – the client

The installation will also create a configuration file in the home folder, .synergy.conf
This is what my file looks like:

section: screens
dev:
bender:
end
section: links
dev:
left = bender
bender:
right = dev
end

In the screens section, we place the hostnames of the boxes involved. For me, dev being the server and bender the client.

Since this is a quick miniguide to get it running, further details of configuration are outside of the scope. For other parameters check the very rich documentation of the software itself.

To run the server , on the command line type:

synergys -f
if you want the server to run in foreground, or simply
synergys
if once configured, you want it to run in the background.

Windows Xp as Client

After downloading and installing the windows binary, run it and define the name of the Synergy server, under “Other Computer’s Hostname”.

Test it. If the server is running correctly, it should all already work.

Windows XP as Server

After the installation, run Synergy, and on the main screen, choose to share this computer’s keyboard and mouse. “Screen & Links : Configure”.

The interface from here is quite intuitive. On the Screens section click the + button to add another screen, and underneath it, the relationship with the other screen.

Start.

Ubuntu as Client

On the Ubuntu box, after installation, to use it as a client, there is no further configuration needed.
The only thing to done is launch the client:

synergyc -f server.ip
to keep it verbose, or

synergyc server.ip
to leave it in the background.

Notes and troubleshooting
One of the biggest issues i had to get this running was getting the windows box to recognize Ubuntu’s hostname. After some research this turned out to be quite the popular topic.

The solutions varied from adding
send host-name "thehostname";
at the end of /etc/dhcp3/dhclient.conf,
to installing winbind and adding wins to the nsswitch.conf file.

The fact is that an entirely different article could be written about this, but none of them worked for me.

The only hack-ish solution was installing samba and editing /etc/samba/smb.conf.
At the end of the Global Settings section, adding :
netbios name = dev

After resolving that, another issue was that while running Ubuntu as the server, the mouse was not properly responsive on the client. The same thing happened when Ubuntu was the client on the Ubuntu box itself.
Turns out this is a known bug with the newer Ubuntu versions. The solution is not the safest, but the only one working so far. Whatever you’re running on Ubuntu ( client or server ), run it as root. Works.
Very important at this point is the location of the configuration file.
If synergys is launched as root with no extra parameters, will be looking for the .conf file in /root/.
Either move the file there, or launch it with the path parameter.

sudo synergys --config synergy.conf

Done and done.

mytop is a console-based (non-gui) tool for monitoring the threads and overall performance of a MySQL 3.22.x, 3.23.x, and 4.x server. It runs on most Unix systems (including Mac OS X) which have Perl, DBI, and Term::ReadKey installed. And with Term::ANSIColor installed you even get color. If you install Time::HiRes, you’ll get good real-time queries/second stats. As of version 0.7, it even runs on Windows (somewhat).

The source can be found on the official page. For ubuntu, the package is in the repositories, and this is the case we’ll be talking about.

sudo apt-get install mytop

After the installation, in your home folder you will be able to find the configuration file.
To set a few predefined parameters we can edit this file.

gedit ~/.mytop

For example, my configuration file looks like this:

user=sid
pass=********
host=xxx.xxx.xxx.xxx
delay=5
port=3306
socket=
batchmode=0
header=1
color=1
idle=1

where of course ***** is replaced with your password.
These parameters defined in the file will be the default ones if you start mytop from the command line with no options. Alternatively, all of the above can be overriden.

-u username
-p password
-h host
-d database

and so on. for more details take a look at the mytop man page.

Another thing to be kept in mind is that, if you’re going to check a machine other than localhost you need to have the correct permissions in my Mysql user table to do that.

In combination with this, there’s another nifty piece of software called Terminator.

Terminator, multiple terminals in one window. The goal of this project is to produce a useful tool for arranging terminals. It is inspired by programs such as gnome-multi-term, quadkonsole, etc. in that the main focus is arranging terminals in grids (tabs is the most common default method, which Terminator also supports).

So basically what Terminator does , is split your normal gnome-terminal window in as many sections as you wish, the way you wish, dropping you into the command line into each one of them.

The output :

OpenProj by Serena Software is a desktop replacement of Microsoft Project. OpenProj has equivalent functionality, a familiar user interface and even opens existing MSProject files. OpenProj is inter operable with Project, with a Gantt Chart and PERT chart

sourceForge page

Seems to be pretty handy. On it’s SourceForge page though there’s only a .rpm noarch package.
The RPM packet manager is available for Debian-based systems indeed, non the less there are a few complications.

When attempting to install openproj with rpm:

sid@dev:~/Desktop$ rpm -i openproj-1.4-2.noarch.rpm
rpm: To install rpm packages on Debian systems, use alien. See README.Debian.
error: cannot open Packages index using db3 - No such file or directory (2)
error: cannot open Packages database in /var/lib/rpm


What’s alien?

Alien allows you to convert LSB, Red Hat, Stampede and Slackware Packages into Debian packages, which can be installed with dpkg.
It can also generate packages of any of the other formats.
This is a tool only suitable for binary packages.

Here goes the installation from the Ubuntu repositories:

sudo apt-get install alien

Afterwards it’s time to convert Openproj from a .rpm package to a .deb one.

sudo alien openproj-1.4-2.noarch.rpm openproj-1.4-2.noarch.deb

Once the package is created, double click on it, to install with the gDebi installer.

Been using it for a few days now, and i must say, i regret not having picked it up earlier.

Java
After installing Java, the trick is done by giving Konqueror the absolute path of the executable:

Konqueror -> Settings ->Configure Konqueror -> Java & Javascript

and set (in my case) to /usr/bin/java

Flash

Open a shell window and type:
sudo apt-get install konqueror-nsplugins flashplugin-nonfree

Konqueror -> Settings ->Configure Konqueror -> Plugins.->Scan for new plugins

Restart Konqueror.

The track is called Jockin’ Jay-Z and has already leaked (intentionally? doesn’t matter), so it can be found around.
The chorus is sampled from Dumb Girl, a Run DMC song on Raising Hell (track 10).
In the original track it actually says “Jockin JC”, but it’s been moded into jay-z eventually-

Here’s the video of the performance. This track is a beast.

lspci | grep -i vga

The output should be similar to this :

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE)

Now we need to install the fglrx driver:

sudo apt-get install xorg-driver-fglrx

Enable the Ati driver from the System -> Administration -> Hardware Drivers.

Reboot the system, open a terminal window and type:

fglrxinfo

The output should be the following:

display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon Xpress Series
OpenGL version string: 2.1.7412 Release

That’s it.

Windows Media Center Remote (usb, 2nd model)
Hewlett Packard Easynote R0933 Laptop

Software used:

Ubuntu 8.04 Website
LIRC Website
Elisa Media Center Website

Before we begin, it would be a good idea to check your remote model.
Use this documentation over here.

First, we’re going to need to install lirc to get our remote to interact with the computer over infrared.

sudo apt-get install lirc

During the setup you will be prompted with a few configuration choices.
The first choice is the remote- On the list make sure you pick “Windows Media Center Remotes ( new version Philips et al. )”.
On the second prompt pick “None”.

After the installation finishes, plug in the infrared device and start the Lirc service:

sudo /etc/init.d/lirc restart

To test weather everything works correctly , on the terminal type:

irw

then after pressing any button on the remote you should see the output , altogether with the name of the key you pressed.

Elisa Media Center can be installed from the repos:

sudo apt-get install elisa

Now let’s create a proper configuration of the remote, with all the necessary keys and feed it to Elisa.

sudo irrecord -d /dev/lirc0 elisa.lirc

Afterward move the file to the directory where the IR Remote conf files are located for lirc:

sudo cp elisa.lirc /usr/share/pyshared/elisa/plugins/lirc_plugin/data/lirc/
sudo cp elisa.lirc /home/YOUR_USERNAME/.elisa/

create a symbolic link too :

cd /usr/lib/python2.5/site-packages/elisa/plugins/lirc_plugin/data/lirc
sudo ln -s /usr/lib/python2.5/site-packages/elisa/plugins/lirc_plugin/data/lirc/elisa.lirc ./

Now we need to instruct the elisa.conf file to take the info from the elisa.lirc
gedit /home/YOUR_USERNAME/.elisa/elisa.conf

Find the lirc_rc parameter and set it to:

lirc_rc = 'elisa.lirc'

Here’s the content of my elisa.lirc file:
begin
remote = mceusb
prog = elisa
button = Play
config = toggle_play_pause_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Right
config = move_right_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = OK
config = activate_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Power
config = close_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Mute
config = toggle_mute_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = VolDown
config = decrement_volume_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Rewind
config = seek_backward_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Stop
config = stop_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Up
config = move_up_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = VolUp
config = increment_volume_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Down
config = move_down_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Pause
config = pause_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Enter
config = activate_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Forward
config = seek_forward_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Home
config = toggle_menu_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Red
config = toggle_fullscreen_key
repeat = 0
delay = 0
end
begin
remote = mceusb
prog = elisa
button = Left
config = move_left_key
repeat = 0
delay = 0
end


Restart Lirc, fire up Elisa and all is done.