Q: I am getting GRUB Error 18 or 17 when trying to boot off the USB key!
A: Your BIOS may not be able to boot from a large partition on the USB drive. This happens even with newer BIOSes like on the Via EPIA M. You must create a 50MB boot partition with nothing but the bootloader, and another partition with the actual OS in the rest of the space.
Just to be safe, first wipe out the MBR on the USB drive:
add if=/dev/zero of=/dev/sda1 bs=512 count=1
BE VERY SURE YOUR USB DRIVE IS AT ”/dev/sda1”! You don't want to wipe out any important drive's MBR. Then go through the Ubuntu command line installation again. In the partitioner, make a 50MB partition for ”/boot” and make it bootable (with the “noatime” option). Then make another partition for ”/” that is not bootable, and the installer should take care of the rest.
Q: I get a Kernel Panic error message when trying to boot my AudioPint!
A: Try adding 'acpi=force' to your kernel boot options. There's an issue with the 2.6.17-08+ kernel where it should include a patch for 'quirk_via_abnormal_poweroff' and it doesn't.
Q: My AudioPint somehow got into an infinite loop of rebooting, fsck repairing the flash drive, then rebooting again!
A: You need to break this vicious cycle. It probably happened because you switched off or rebooted your 'pint while the filesystem was in write-able mode. Remember to always change this back before shutting down whenever you put it into write-able mode.%0a%0aHere's how to fix the problem: reboot your 'pint (this part is easy, right?), and when you see the first message about grub, press the esc key to enter the grub menu. Using the arrow keys, choose the main kernel, and press 'e' to edit the boot parameters. Arrow-key to the end of the line, and remove quiet and splash. Then, add the following to the end:
init=/bin/bash Hit Enter to exit line-editing mode, then b to boot from this kernel, and it should boot you into the bash shell, where you can type commands. Here's what you want to do now, to fix the problem:
mount -o remount,ro
These commands will (1) make sure the root partition is mounted read-only, then (2) run fsck on /, then (3) flush all pending file access to /, then reboot the machine. The problem should now go away. If reboot doesn't work, just pull the plug, and power your AudioPint back up.
Q: I am getting this error when I try to use sudo:
sudo: timestamp too far in the future Help!
A: This can happen sometimes right after a fresh install from the Linux image. To fix it, try this:
sudo sudo -k
You'll have to enter the audiopint password, but then it should clear things up, by resetting sudo's timestamp. If that doesn't work, try this command:
gksudo touch /var/run/sudo/* /var/run/sudo/*/*
You may have to press control-C to kill the command if it doesn't exit..