Life’s an ocean with too much commotion

While some of my collegues use DAAP to listen to music over the network, I didn’t get it configured on my Ubuntu.

Starting Rhythmbox with the debug parameter ‘-d’, gives the following output when loading the DAAP plugin:

[0x80dc408] [rb_plugin_find_file] rb-plugin.c:255: found ‘/usr/lib/rhythmbox/plugins/daap/daap-ui.xml’ when searching for file ‘daap-ui.xml’ for plugin ‘daap’

[0x80dc408] [create_share] rb-daap-sharing.c:67: initialize daap sharing

[0x80dc408] [rb_daap_share_server_start] rb-daap-share.c:1903: Started DAAP server on port 3689

(rhythmbox:4302): Rhythmbox-WARNING **: Unable to notify network of music sharing: The avahi MDNS service is not running

Starting up the avahi MDNS service fixed the problem:
$ sudo /etc/init.d/avahi-daemon start

Here a short description on how to manage dualhead display with the NV43 GeForce Go 6600 on Ubuntu systems.

The binary drivers (listed below) available in the ubuntu repositories will not work by default for multihead displays:

• nvidia-glx-envy
• nvidia-glx-legacy
• nvidia-glx-new

Instead, the source for the nvidia-new driver needs to be downloaded and compiled. This is how you do that:
$ sudo apt-get install module-assistant nvidia-new-kernel-source
$ sudo m-a prepare nvidia-new-kernel-source
$ sudo m-a build nvidia-new-kernel-source
$ sudo m-a install nvidia-new-kernel-source

Shut down your currently running Xorg daemon:
$ sudo /etc/init.d/gdm stop # or xdm, kdm if you're running another display manager

Force the newly compiled driver to be loaded when gdm starts, by inserting the following line in your /etc/init.d/gdm init script:
( modprobe i2c-dev ; modprobe i2c-core ; insmod /lib/modules/`uname -r`/nvidia/nvidia.ko )

Make sure you’re X configuration file is configured for multihead display. You will need support for Twinview with Xinerama support.
$ sudo apt-get install libxinerama-dev libxinerama1 x11proto-xinerama-dev

Here’s my X11 configuration file (I left out the keyboard and mouse settings):

Section “ServerLayout”
Identifier     “Layout0″
Screen      0  “Screen0″ 0 0
EndSection

Section “Files”
RgbPath         “/usr/X11R6/lib/X11/rgb”
EndSection

Section “Module”
Load           “dbe”
Load           “extmod”
Load           “type1″
Load           “freetype”
Load           “glx”
EndSection

Section “ServerFlags”
Option         “Xinerama” “0″
EndSection

Section “Monitor”
Identifier     “Monitor0″
VendorName     “Unknown”
ModelName      “TOSHIBA Internal Panel”
HorizSync       64.0 – 65.3
VertRefresh     60.0
Option         “DPMS”
EndSection

Section “Device”
Identifier     “Videocard0″
Driver         “nvidia”
VendorName     “NVIDIA Corporation”
BoardName      “GeForce Go 6600″
EndSection

Section “Screen”
Identifier     “Screen0″
Device         “Videocard0″
Monitor        “Monitor0″
DefaultDepth    24
Option         “TwinView” “1″
SubSection     “Display”
Depth       24
EndSubSection
EndSection

he Groupwise Client version 6.x that is available for linux is consuming too much memory. The Groupwise Client version 7.0.1 is also available but that user-friendly for installing on a distribution other than SuSE (Novell).

Follow this guide to install the groupwise client version 7.0.1 on a Ubuntu Hardy distribution. Note that this procedure may also be valid for other (debian-package supported) distributions, but it has only been tested on Ubuntu Hardy.

• Download the groupwise client 7.0.1
  wget -P /tmp http://nsn.uvsc.edu/GWClient/gw701clnxm.tgz

• Untar the contents. The tarball contains two RPM packages.
  tar -zxpf gw701clnxm.tgz -C /tmp

• Convert the Groupwise Client RPM package to a debian package with alien.
  sudo alien -d /tmp/image/2006.06.13/client/linux/novell-groupwise-gwclient-7.0.1-20060613.i386.rpm

• Install the newly created debian package
  sudo dpkg -i /tmp/image/2006.06.13/client/linux/novell-groupwise-gwclient-7.0.1-20060613.i386.deb

• This will install some files into /opt/novell/groupwise/client

• Now we have to update the java runtime environment for this Groupwise Client. On my system this only worked with the Java 6 JRE from Sun.
  rm -rf /opt/novell/groupwise/client/jre
sudo ln -s /usr/lib/jvm/java-6-sun/jre /opt/novell/groupwise/client/jre

• Place the desktop icon on your desktop
  cp /opt/novell/groupwise/client/gwclient.desktop ~/Desktop/

This howto will show you how to boot your upgraded Ubuntu properly on a Toshiba Tecra S3 laptop. Note that this workaround will not work when installing Ubuntu for the first time on your laptop. If so, you will have to change some BIOS settings so that the SATA controller will be recognized as a generic IDE controller. If not, follow this procedure:

When booting a Toshiba Tecra S3 for the first time, it will fail trying to find the SATA harddisk.

A kernel and initrd image has been provided to boot your linux distribution. The initrd image provides a pseudo filesystem (loaded in RAM) which will execute some bash scripts. These bash scripts will do a lot of checks and configuring and load various modules to detect as much hardware as possible needed for booting your linux distribution. The modules that are loaded are specified in the ‘conf’ directory (modules, initramfs.conf) and the ‘/etc/modprobe.d’ directory.

What goes wrong in this case, is that the ‘ata_piix.ko’ module gets loaded before the ‘ahci’ module. In fact, the ‘ata_piix.ko’ module may not be loaded at all. It is a low-level SCSI driver that only needs to be loaded for Intel PIIX/ICH ATA controllers. So what needs to be done is make sure that the ‘ata_piix.ko’ module is unloaded before the ‘ahci.ko’ module gets loaded. This can be done in the bash scripts that are executed in the initrd image.

Follow this procedure to do so:

1. Boot your Ubuntu distribution with the recovery mode kernel
2. Wait until the initrd scripts time out. This can take up to 5 minutes. After timeout you will be thrown in a shell, forked by the initram process.
3. In this shell, execute the following commands:

# modprobe -r ahci
# modprobe -r ata_piix
# modprobe ahci
# mkdir /mnt
# mount /dev/sda1 /mnt -t ext3
# chroot /mnt
# mkdir /tmp/unpacked
# cd /tmp
# cp /boot/initrd.img-2.6.22-14-386 initrd.img-2.6.22-14-386.gz
# gunzip initrd.img-2.6.22-14-386.gz
# cd /tmp/unpacked
# cpio -id </tmp/initrd.img-2.6.22-14-386
# vi /tmp/unpacked/scripts/functions

4. In this file you will find a function load_modules(). Insert a line on top of this function:

modprobe -r ata_piix 2>/dev/null 1>&2
modprobe -r ahci 2>/dev/null 1>&2

5. Save the file and execute the following commands:

# vi /tmp/unpacked/conf/modules

6. Add the following entry on top of the file

ahci

7. Save the file and execute the following commands:

# cd /tmp/unpacked
# find . | cpio -o -H newc | gzip -9 > /boot/initrd.img-2.6.22-14-386.new
# vi /boot/grub/menu.lst

8. In this file you have to rename the initrd image filename to the new one:

initrd /boot/initrd.img-2.6.22-14-386.new

9. Execute the following commands to exit chroot environment, and reboot

# exit
# reboot

Note: This works for Ubuntu Feisty too.