Sam.Nazarko Wrote:Why are you upgrading: what specifically is broken?

Sam.Nazarko Wrote:[quote=generikb]

Sounds like there is no Makefile (ls | grep Makefile) to see. If there isn't a makefile, then your script hasn't run right. "/configure CFLAGS="-fgnu89-inline" --enable-static=yes
works fine here and generates the Makefile perfectly. You have the buildtool essentials right?: "sudo /usr/bin/apt-get install build-essential patch"

generikb Wrote:[quote=Sam.Nazarko]

i did the ls | grep Makefile and nothing happens, it just goes back to the prompt.

when I do the sudo /usr/bin/apt-get install build-essential patch, it says

"sudo: usr/bin/apt-get: command not found.

But I did it just after firing up the ATV and SSHing in...do i need to go to a different folder or something? Where in the steps you gave before do I install this buildtool essentials?

Thanks again, I feel like I'm close to getting this to work!

Sam.Nazarko Wrote:To be quite frank, no, it does not make sense. If it isn't broken do not fix it. If you go down the route of upgrading then you may as well upgrade to Maverick, update ALSA, and update NVIDIA. As far as I am concerned, the current Nvidia drivers provide no issues (unlike later versions), so I would not change this. You could get undesired results (which it sounds like you have).

P.S: Don't double post.

Jimmer Wrote:[quote=generikb]

You've missed the / off the front of usr. You would need:

sudo /usr/bin/apt-get install build-essential patch

you ran:

sudo usr/bin/apt-get install build-essential patch

which looks for usr in the folder you are currently in. But usr resides at the root level, hence the error..... and the reason for the / before usr

but if your path is set right, you should be able to run:

sudo apt-get install build-essential patch

and get the desired result anyway. Hope this helps,

Jim

Jimmer Wrote:Sam, this may be a stupid question, but: if I did a dist-upgrade in crystalbuntu, would it leave me with a kernel that won't boot.....

Just wondering if I could do a few cheeky dist-upgrade from 8.04 --> 8.10 --> 9.04 --> 9.10? I know it's possible on regular machines, but will yours (and pin's) mach kernel pass on to the dist-upgraded linux kernel? Or does the mach kernel need to be re-compiled for each dist-upgrade?

Jim

generikb Wrote:[quote=Jimmer]

Thanks Jim, that's exactly what happened

So I've done the entire process again exactly as laid out on page 145 of this thread. It appears that it runs correctly all the way up to this part:

Code:

xbmc@atv:~/hfs_support/parted$ sudo parted -s /dev/sda mkpart primary HFS 40s 69671s
Error: /dev/sda: unrecognised disk label
xbmc@atv:~/hfs_support/parted$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sda doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 4100 MB, 4100980736 bytes
255 heads, 63 sectors/track, 498 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         488     3915775+  ee  EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(487, 125, 22)
xbmc@atv:~/hfs_support/parted$ ls | grep Makefile
xbmc@atv:~/hfs_support/parted$

I'm at wits end here! (not really, I'm enjoying the challenge lol) does anyone have any suggestions?