[AppleTV1] Can't seem to figure out how to install Crystalbuntu

TechLife Wrote:I know it is recommended to change the output to RGB from YPbPr or the colorspace will be wrong and you will have the pink screen issue. I was pretty sure I read at some point on Sam's forum that you also had to change the resolution there as well. As, "Crystalbuntu can only READ the vbios setting. Only the official OSX OS can change the vbios data."

Looks like you are correct about vbios. It will cause issues for anything outside of XBMC. While in XBMC it seems that another driver that over-rides vbios is used, which is why I never had an issue within XBMC.

http://stmlabs.com/forum/topic/pink-scre...#post-3018 :

Quote:When using the original ATV software, changing resolution and display format (YPrCr, RGB low, RGB high) will actually write this into the vbios. This causes the commandline of Linux (before starting XBMC, and after exiting XBMC) to use the format saved in Vbios, but when using the Nvidia Linux GFX driver (ie using XBMC), it will override the Vbios.

I'm not entirely sure, but it seems that from time to time the vbios (mostly pink screens) can creep into XBMC itself, although that might have just been a bug that has since been fixed.

I was not aware of this before, so thanks for the heads up. I'll add it to the XBMC wiki that people should still set things for their display in the native OS before installing Crystalbuntu. I really wish the Crystalbuntu info wasn't so scattered about.

No worries on the iOS thing ;)

Easier solution was posted in that same thread, and I overlooked it. Seems the reason it didn't work (the original instructions) is because the echo command has to be run at the root directory. So before typing that in, first type in:


and it should now work. I've also updated the wiki instructions to reflect this.

Ned Scott Wrote:Easier solution was posted in that same thread, and I overlooked it. Seems the reason it didn't work (the original instructions) is because the echo command has to be run at the root directory. So before typing that in, first type in:

Code:

cd /

and it should now work. I've also updated the wiki instructions to reflect this.

thanks so much! i'll try this when i get home from work later today.

i freaking love this community and how fast the responses are!

everything's working fantastically!

one more thing, ned scott you had mentioned that the wifi drivers have been included with this latest build of ubuntu, how do i configure the atv's wifi card? i went into ./configure and tried to toggle the WLAN but the UI just says something like "feature not available yet"

any suggestions on how to set up the built-in wifi now that the atv is purely crystalbuntu?

I'll search around and see if I can find the command line instructions to setting it up. It's a little funky with the command line, but Sam will have that configuration utility working sometime in the future.

I don't know if there is better information on this elsewhere, but FWIW these are the instructions that I use and it works like a champ. (After removing spaces and special characters from my SSID and PW).

http://stmlabs.com/forum/topic/enable-wireless-n/page/4

The post by AIR - though a read through the whole thread proved to be useful. I'm not sure what driver Sam now includes, but I have been using this one instead of the on AIR mentioned:

http://www.broadcom.com/docs/linux_sta/h...112.tar.gz

Again, I have had great success with this method. At least until the feature in the configuration utility is completed.

thank you both so much! i'll try out the AIR method later today when i get home from work, if all else fails i'll just wait for SAM's config.



one very last thing: how do i update xbmc? if found
is this correct? (sorry havent tried it yet as i've just been searching at work)

and in the long run does crystalbuntu just auto-update if it's set in ./configuration or is there commandlines for updating the OS itself?

Ned Scott Wrote:Looks like you are correct about vbios. It will cause issues for anything outside of XBMC. While in XBMC it seems that another driver that over-rides vbios is used, which is why I never had an issue within XBMC.

http://stmlabs.com/forum/topic/pink-scre...#post-3018 :


I'm not entirely sure, but it seems that from time to time the vbios (mostly pink screens) can creep into XBMC itself, although that might have just been a bug that has since been fixed.

I was not aware of this before, so thanks for the heads up. I'll add it to the XBMC wiki that people should still set things for their display in the native OS before installing Crystalbuntu. I really wish the Crystalbuntu info wasn't so scattered about.

No worries on the iOS thing

ALWAYS update to RGB High before permanently installing.

phi303 Wrote:thank you both so much! i'll try out the AIR method later today when i get home from work, if all else fails i'll just wait for SAM's config.



one very last thing: how do i update xbmc? if found

Code:

sudo apt-get remove xbmc-live  
sudo apt-get install xbmc-live

is this correct? (sorry havent tried it yet as i've just been searching at work)

and in the long run does crystalbuntu just auto-update if it's set in ./configuration or is there commandlines for updating the OS itself?

Never update via apt. There is no new builds via apt. Pull down from the downloads site.

Sam.Nazarko Wrote:ALWAYS update to RGB High before permanently installing.



Never update via apt. There is no new builds via apt. Pull down from the downloads site.

forgive me for my unfamiliarity but do you mean actually on the the website or does XBMC have a download tab somewhere for updates? sorry, i haven't spent much time with the xbmc UI. crystalbuntu is all command-lines right?

Sam's build automatically checks for updates when it reboots, unless automatic updating is explicitly turned off by the user. If you SSH in and issue a reboot command or power-cycle the ATV, during the boot process Crystalbuntu checks for any updated packages pushed down by Sam and installs them.