Hi Bastian, I snipped the rest of the message body to spare you the huge reply. I have confirmed that today's daily build of the installer seems to resolve the bug. Interestingly, the installer chose 2.6.25-2 for the default kernel. So I suspect the problem was in the installer somehow. I am not sure what change fixes it but it works without problems now. Thanks, Matthew