Fixing Ubuntu shutdown problem

Some users, myself included, have had problems getting Ubuntu 5.10 (Breezy Badger) to restart correctly. When attempting to reboot my machine, it instead powered off – not ideal if I want to restart the machine from a remote location!

This thread details a number of possible solutions. One of which is to type the following line into a console:

sudo vi /boot/grub/menu.lst

and edit the following section (or similar), adding the italicised changes:

title Ubuntu, kernel 2.6.12-9-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda1 ro noacpi nolacpi quiet splash
initrd /boot/initrd.img-2.6.12-9-386

After a restart (or power off/on), the restart functionality should work as expected. You can also try adding reboot=h as well as, or in place of, noacpi nolacpi.

Unfortunately none of this worked for me, but turning the ACPI feature off on my motherboard (an MSI 6330) did – I assume I’m losing some power saving functionality by doing this but I’m not too concerned as it’s a desktop machine, not a laptop.

Recycle faulty RAM sticks in your Linux box

I’ve built a Linux box from my spare parts bin, but unfortunately two out of the three 128MB RAM sticks I have are faulty. Fortunately, an enterprising Linux hacker by the name of Rick van Rein has built a kernel patch which allows Linux users to mark faulty areas of RAM so that they are never accessed, similar to the way that bad sectors on hard drives can be marked unusable. You can read more at the BadRAM site.

Unfortunately, enabling BadRAM support requires recompiling the kernel, which is a daunting procedure for non-technical users. However, Ubuntu users might find this thread helpful.