2010-12-06, 03:31
Preface (Skip to solution for fix)
I've had an Aspire Revo 3610 running XBMC beautifully for months now, and recently purchased a new 3700 for a second TV. I was able to install XBMC on it by writing the ISO to a thumbdrive using UNetbootin. I also worked around the inability to load modules from a CD-ROM by copying the ISO file to the root of the thumbdrive filesystem, mounting it during installation with `mount -t iso9660 -o loop`, and then specifying /dev/loop0 as the CD-ROM device.
Aside from that peculiar hack (it seems like there should be a more elegant solution), the installation went well. Upon rebooting, however, I noticed that the GRUB bootsplash looked odd, as if it were being rendered in 16 colors. No biggie. But then the boot finished, and left me at a barren CLI login prompt. Not good.
Solution
After much digging (I'm very much an XBMC noob), I finally figured out that X was not starting simply because nothing told it to; the output of `cat /proc/cmdline` had no mention of an xbmc= argument. Nor did /boot/grub/grub.cfg. Taking a clue from an unrelated bug report, I extended the relevant line in /etc/default/grub to read
Then, I ran
and rebooted. XBMC now happily boots directly to the graphical interface!
My question is this: what failed during the installation to prevent the GRUB configuration being modified appropriately? Was it something specific to the USB thumbdrive method of installation? And should I file a bug?
Thanks!
I've had an Aspire Revo 3610 running XBMC beautifully for months now, and recently purchased a new 3700 for a second TV. I was able to install XBMC on it by writing the ISO to a thumbdrive using UNetbootin. I also worked around the inability to load modules from a CD-ROM by copying the ISO file to the root of the thumbdrive filesystem, mounting it during installation with `mount -t iso9660 -o loop`, and then specifying /dev/loop0 as the CD-ROM device.
Aside from that peculiar hack (it seems like there should be a more elegant solution), the installation went well. Upon rebooting, however, I noticed that the GRUB bootsplash looked odd, as if it were being rendered in 16 colors. No biggie. But then the boot finished, and left me at a barren CLI login prompt. Not good.
Solution
After much digging (I'm very much an XBMC noob), I finally figured out that X was not starting simply because nothing told it to; the output of `cat /proc/cmdline` had no mention of an xbmc= argument. Nor did /boot/grub/grub.cfg. Taking a clue from an unrelated bug report, I extended the relevant line in /etc/default/grub to read
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xbmc=autostart,nodiskmount,setvolume loglevel=0"
Then, I ran
Code:
sudo update-grub
and rebooted. XBMC now happily boots directly to the graphical interface!
My question is this: what failed during the installation to prevent the GRUB configuration being modified appropriately? Was it something specific to the USB thumbdrive method of installation? And should I file a bug?
Thanks!