sleep 1 && /usr/sbin/hciconfig hci0 reset
  sleep 1 && /usr/sbin/hciconfig hci0 reset

Look in /var/lib/bluetooth/*/names for the bluetooth addresses of your keyboard and mouse, let's say they're KK:KK:KK:KK:KK:KK and MM:MM:MM:MM:MM:MM respectively. To configure them initially, use these commands.

To enable gdm auto-login, just add your username to the [daemon] section of /etc/gdm/gdm.conf-custom configuration file. This is obviously insecure, as no password screen will be presented by gdm, but then anyone can achieve a similar result by inserting an Ubuntu live CD into the slot and rebooting the system.

dbus-send --system --type=method_call --print-reply --dest=":1.10" /org/bluez/input/keyboard0 org.bluez.input.Device.Connect
<verbatim>
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=your_username
<nop>

dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez org.bluez.Manager.ActivateService string:input
dbus-send --system --type=method_call --print-reply --dest=":1.11" /org/bluez/input org.bluez.input.Manager.CreateDevice string:KK:KK:KK:KK:KK:KK
dbus-send --system --type=method_call --print-reply --dest=":1.11" /org/bluez/input/keyboard0 org.bluez.input.Device.Connect
dbus-send --system --type=method_call --print-reply --dest=":1.11" /org/bluez/input org.bluez.input.Manager.CreateDevice string:MM:MM:MM:MM:MM:MM
dbus-send --system --type=method_call --print-reply --dest=":1.11" /org/bluez/input/pointing1 org.bluez.input.Device.Connect

In case you're curious as to why that page doesn't display in Firefox 3.0b3, it's because the server it's hosted on is sending the wrong MIME Media Type, i.e. it's sending Content-Type: text/html; charset=UTF-8 in the HTTP header instead of Content-Type: application/xhtml+xml. More details are explained here and in mozilla bugs 305873, 419155, 399232 and 327796 -- thanks to Daniel Holbert for the list of bug numbers.

Adobe/Macromedia Flash

gst-launch-0.10 v4l2src ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=352,height=288 ! ffmpegcolorspace ! ximagesink

(On Gutsy, you might need to use lsusb -d 05ac:8501, to search specifically for the ID 05ac:8501, as the description listed by lsusb only includes the manufacturer, Apple Computer, Inc., and not the device name Built-in iSight [Micron]).

The Bus and Device numbers may change depending on what order the iSight device appears on the USB bus, e.g.:

The dmesg output shows:

[  924.507213] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8501)
[  924.513439] uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -32 (exp. 26).
[ 1014.917312] usbcore: deregistering interface driver uvcvideo
[ 1019.455855] Linux video capture interface: v2.00
[ 1019.460522] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8501)
[ 1019.463115] uvcvideo: Failed to query (135) UVC control 1 (unit 0) : -32 (exp. 26).
[ 1019.465041] usbcore: registered new interface driver uvcvideo
[ 1019.465045] USB Video Class driver (SVN r189)

Wireless keyboard (bluetooth)

The internal ATA hard drive can also be accessed using "Firewire Target Disk Mode" by holding down T when booting the iMac24, see here. Target Disk Mode only connects to the master ATA drive on the Ultra ATA bus. Essentially, your iMac24 becomes an external Firewire disk drive, and you can hotplug it into any machine which can access Firewire hard drives.

Internal Hard Drive

The internal ATA hard drive can be accessed using "Firewire Target Disk Mode" by holding down T when booting the iMac24, see here. Target Disk Mode only connects to the master ATA drive on the Ultra ATA bus. Essentially, your iMac24 becomes an external Firewire disk drive, and you can hotplug it into any machine which can access Firewire hard drives.

Update for Ubuntu 8.04 Hardy Heron

Apparently the steps to get the iSight working for the iMac24 go something like this (I only tested these steps while running the iMac24 from the Ubuntu 8.04 Hardy Heron alpha3 Live CD, as 8.04 is not yet released):

  wget http://ppa.launchpad.net/bersace/ubuntu/pool/main/i/isight-firmware-tools/isight-firmware-tools_1.0.2-0ubuntu0~ppa1_amd64.deb
  dpkg -i isight-firmware-tools_1.0.2-0ubuntu0~ppa1_amd64.deb

  Ensure you have access to the AppleUSBVideoSupport driver file. 
  If not disable firmware extraction, you can retry it later. 
  Extract firmware from Apple driver ? 
       <Yes>                          <No>

In case you don't want to waste time installing such an operating system, you can find the firmware file inside this package, at the location against-revision-*/firmware/AppleUSBVideoSupport.

Use the firmware tools to extract the firmware from the AppleUSBVideoSupport file, alter it by applying three patches and place the result in the file /lib/firmware/isight.fw, as follows.

  wget http://files.i-nz.net/projects/linux-kernel/isight/uvcvideo-isight.tar.gz
  tar zxvf uvcvideo-isight.tar.gz
  cd against-revision-*/firmware
  sudo ift-extract --apple-driver AppleUSBVideoSupport

** Message: Found Mac OS X.4 intel driver
** Message: Firmware extracted successfully in /lib/firmware/isight.fw
** Message: Apply patch 0 : Fix video control interface descriptor
** Message: Apply patch 1 : Fix video streaming interface descriptor
** Message: Apply patch 2 : Fix video streaming device qualifier
** Message: Firmware patched successfully

  svn checkout svn://svn.berlios.de/linux-uvc/linux-uvc/trunk
  cd trunk
  make
  sudo rm /lib/modules/2.6.24-8-generic/ubuntu/media/usbvideo/uvcvideo.ko
  sudo make install

Now we need to load the firmware, before loading the uvcvideo module. Run the command lsusb and search for the Bus and Device IDs. These may change depending on what order the iSight device appears on the USB bus, e.g.:

Bus 005 Device 008: ID 05ac:8501 Apple Computer, Inc. Built-in iSight [Micron]

  sudo mount -t usbfs /dev/bus/usb /proc/bus/usb/
  /usr/lib/udev/ift-load -f /lib/firmware/isight.fw -b 005 -d 008

  ift-load: Firmware loaded succesfully to 005:004

We should now be able to unload and load the uvcvideo using:

  modprobe -r uvcvideo
  modprobe uvcvideo

  gst-launch-0.10 v4l2src ! video/x-raw-yuv,format=\(fourcc\)UYVY,width=640,height=480 ! ffmpegcolorspace ! ximagesink

Exploring the Mac OS X DVD Contents

  /usr/bin/readcd -v dev=0,0,0 f=./Mac_OS_X_Install_Disc_1_image
  eject /dev/scd0
  /usr/bin/readcd -v dev=0,0,0 f=./Mac_OS_X_Install_Disc_2_image
  eject /dev/scd0

The resulting Mac OS X Install Disc 1 image was of size 5662343168 bytes and had an md5sum of 37e7a1e9432730ed04746654c44ef944.

The resulting Mac OS X Install Disc 2 image was of size 8253407232 bytes and had an md5sum of 88be5bd6e2f230c8809e4667ee83ca3c.

To explore their contents under Linux, the images can be mounted as follows, using the hfsplus filesystem driver.

  sudo losetup /dev/loop0 ./Mac_OS_X_Install_Disc_1_image
  sudo mkdir /MacOSX1
  sudo mount -t hfsplus /dev/loop0 /MacOSX1
  sudo find /MacOSX1 -print > /tmp/Mac_OS_X_Install_Disc_1_image.list
  sudo umount /MacOSX1
  sudo losetup -d /dev/loop0
  rmdir /MacOSX1

The commands to mount the second image are similar.

  sudo losetup /dev/loop1 ./Mac_OS_X_Install_Disc_2_image
  sudo mkdir /MacOSX2
  sudo mount -t hfsplus /dev/loop1 /MacOSX2
  sudo find /MacOSX2 -print > /tmp/Mac_OS_X_Install_Disc_2_image.list
  sudo umount /MacOSX2
  sudo losetup -d /dev/loop1
  rmdir /MacOSX2

I wasn't able to locate the firmware file AppleUSBVideoSupport, mentioned earlier in the iSight section. Where does the Apple installer retrieve it from?

• isight-firmware-tools_1.0.2-0ubuntu0ppa1_amd64.deb: mirror of isight-firmware-tools for amd64

• isight-firmware-tools_1.0.2-0ubuntu0ppa1_i386.deb: mirror of isight-firmware-tools for i386

• Mac_OS_X_Install_Disc_1_image.list.bz2: List of files in Mac_OS_X_Install_Disc_1_image

• Mac_OS_X_Install_Disc_2_image.list.bz2: List of files in Mac_OS_X_Install_Disc_2_image

Framebuffer in Gutsy

Basically, just add the following two lines to the /etc/initramfs-tools/modules (the set of modules included in the initial ramdisk) configuration file.

fbcon
vesafb

Then run this command to rebuild the initial ramdisk:

sudo update-initramfs -u

Also, edit /etc/modprobe.d/blacklist-framebuffer and comment out the line blacklisting vesafb so that it will actually be loaded into the kernel during boot:

#blacklist vesafb

Edit /boot/grub/menu.lst and add the following line.

# defoptions=vga=0x346

Run the following command to update the kernel boot line in the grub configuration file:

sudo update-grub

After reboot, you should now see the full boot messages, and have a nice high resolution console font to work with on your virtual terminals (Ctrl Alt F1 through Ctrl Alt F6, Ctrl Alt F7 is where xorg is running). The console is particularly good for reading manual pages.

For more details on framebuffer support with uvesafb (which is a lot faster than vesafb) in the upcoming Ubuntu 8.04 (Hardy Heron), see here.

But if you're here, you already know there's no substitute for Free Software, so this page is about using Ubuntu (a GNU/Linux distribution of Free Software) on the iMac.

  export WINDOW_MANAGER=metacity

Remember to install the settings manager:

xterm in Gutsy

*saveLines:     100000
*scrollBar:     true

There's also a bug in kopete which prevents outbound conversations from being established, although inbound conversations work fine.

• cpuinfo: /proc/cpuinfo for iMac24