Yesterday I performed a clean install from Ubuntu Lucid Lynx Minimal on my Asrock Ion 330.
I followed this guide like I did last time (for an earlier version of Ubuntu Minimal) but I encountered some problems.

Here’s how I solved them.

In chapter “Updating the computer”, change in the sources.list hardy or intreprid or jaunty by “lucid”.
No problems in “Install sound”.

The real problems came in “Installing the graphical environment”.
When I wanted to install the latest driver for my ION graphics card I always got this error:

ERROR: Unable to load the kernel module ‘nvidia.ko’. This is most likely
because the kernel module was built using the wrong kernel source files.
Please make sure you have installed the kernel source files for your
kernel; on Red Hat Linux systems, for example, be sure you have the
‘kernel-source’ rpm installed. If you know the correct kernel source
files are installed, you may specify the kernel source path with the
‘–kernel-source-path’ commandline option.

It took me a while before I found this solution:
Make the file (or edit the file if it already exists)  /etc/default/linux-restricted-modules-common
and add this content:

DISABLED_MODULES=”nv nvidia_new”

Now you should be able to run the installer without problems.

Another small problem was, logging in automatically. In earlier releases of Ubuntu you had to change some commands in /etc/event.d/tty1 (according to the guide mentioned earlier), but in Ubuntu Lucid, the event.d folder doesn’t exist anymore, and you have to put it in /etc/init/ instead.

Good Luck!

First of all, these instructions below are based on two tutorials I found using Google, namely http://www.stefanoforenza.com/how-to-get-the-new-notifications-on-intrepid/ and http://blog.alexrybicki.com/2009/02/how-to-install-notify-osd-in-intrepid.html. Also, this is what I had to do to get it working, it is possible this won’t work for you.

So, let’s get started.
First of all, you’ll have to install a bunch of needed files:

$ sudo apt-get install bzr gnome-common automake gconf2 libgconf2-4 libgconf2-dev libdbus-glib-1-dev libwnck-dev mono-gmcs libnotify-dev

The package bzr (short for ‘bazaar’) is needed to get the source from launchpad.
Next step is actually getting the source:

$ bzr branch lp:notify-osd

Just to make sure you have it right, LP, first char is an ‘L’
Before we can start compiling, we’ll have to fix something (I had to do it, not sure you’ll need to):
To successfully complete the build, the command ‘gmcs’ is needed. As you might have noticed, we installed the packet above, but for me that wasn’t enough. Apparently installing that package creates a file in /usr/bin named ‘gmcs2′ instead of just ‘gmcs’.
I fixed this by making a softlink:

$ sudo ln -s /usr/bin/gmcs2 /usr/bin/gmcs

So, we can start compiling now, as always, first run the ‘autogen’ script followed by the ‘make’ command:

$ cd ~/notify-osd
$ ./autogen.sh
$ ./make

If you have errors, it’s probably a dependencies problem, on both of the mentioned sites above they advised to make install some more packes:

$ sudo apt-get install libc6 libcairo2 libdbus-1-3 libdbus-glib-1-2 libgconf2-4 libglib2.0-0 libgtk2.0-0 libpango1.0-0 libpixman-1-0 libx11-6

Installing above packets wasn’t necessary for my, but it might be for you.
So, when you don’t have any errors (anymore) it means your build was successful, and so you can start using the new notification pop-ups.
First of all, you’ll have to end the current notifier and then you’ll be able to start notify-osd like this:

$ killall notification-daemon
$ cd src
$ ./notify-osd

Now to the check out your new notifier, you can run the test script in the same directory (you’ll have to open a new tab because notify-osd is still running):

$ ./send-test-notification.sh

This show a whole bunch of nice pop-ups, demonstrating the possibilities of notify-osd.

Just like me, you might like this notifier very much, and you’d like to have this running the next time you start up you’re machine.
As we didn’t make any permanent changes to the system, and the default notifier will be started when you restarted your system, we’ll have to write a little script to fix this:

$ touch ~/notify-osd/startup.sh
$ nano ~/notify-osd/startup.sh

Using the editor (nano) add these lines to the file:

#!/bin/bash
killall notification-daemon
sleep 1
~/notify-osd/src/notify-osd

Now all you have to do is make the script runnable and add the script to you’re startup scripts in ~/.config/startup:

$ sudo chmod a+x ~/notify-osd/startup.sh
$ touch ~/.config/startup/notify-osd.desktop
$ nano ~/.config/startup/notify-osd.desktop

This what you should put in the file (replace [USER] with your username):

Type=Application
Name=notify-osd
Exec=/home/[USER]/.config/autostart/notify-osd.sh
Icon=system-run
Comment=
X-GNOME-Autostart-enabled=tru

This worked out for me, I hope it does for you too!