[nerpissad]

so I wanted to try my luck installing the latest crystalHD driver manually as per the 'todayguesswhat' guide. it seems everything is going smoothly, except for when I move the required files to /usr/lib with these commands:

Code:

mv crystalhd-for-osx-3.6.0/libcrystalhd.dylib /usr/lib/

the response I get:
override rwxr-xr-x root/wheel for /usr/lib/libcrystalhd.dylib? (y/n [n]) y
mv: rename crystalhd-for-osx-3.6.0/libcrystalhd.dylib to /usr/lib/libcrystalhd.dylib: Read-only file system

Code:

mv crystalhd-for-osx-3.6.0/bcm700*.bin /usr/lib/

override rwxr-xr-x root/wheel for /usr/lib/bcm70012fw.bin? (y/n [n]) y
mv: rename crystalhd-for-osx-3.6.0/bcm70012fw.bin to /usr/lib/bcm70012fw.bin: Read-only file system
mv: rename crystalhd-for-osx-3.6.0/bcm70015fw.bin to /usr/lib/bcm70015fw.bin: Read-only file system

Code:

chmod 644 /usr/lib/bcm700*.bin

chmod: /usr/lib/bcm70012fw.bin: Read-only file system

all other steps can be executed without any error. if I dmesg after all the steps, I can still see the crystalHD card:

BroadcomCrystalHD:tart
allocated 18 elem
Starting BCM70012 Device
clock is moving to 175 with n 35 with vco_mg 2
CStopping BCM70012 Device
BroadcomCrystalHD: Found HW and started driver SW.

the thing is, when I kextstat for crystalHD I still see the older version (0.9.26) instead of 3.5.0:

Code:

77    0 0x2fb06000 0xb000     0xa000     com.broadcom.crystalhd.driver (0.9.26) <5 4 3 2>

my conclusion is that this is because of the previous read only file system messages. is there anything I can do about it, or is this a typical 'wait until the driver can be downloaded from launcher' type of question

[davilla]

see http://forum.xbmc.org/showpost.php?p=589...stcount=16

[nerpissad]

see http://forum.xbmc.org/showpost.php?p=589...stcount=16

I was trying to be as complete as possible, but I should have mentioned that I'm running on atv(osx).
so, I tried using

Code:

mount -uw /

and that got rid of the read only file system messages, but kextstat still shows the old version after reboot?

Code:

BroadcomCrystalHD: Found HW and started driver SW.
bash-2.05b# kextstat | grep crystalhd
   77    0 0x2fc01000 0xb000     0xa000     com.broadcom.crystalhd.driver (0.9.26) <5 4 3 2>

[davilla]

sudo find / -name BroadcomCrystalHD.kext

[nerpissad]

/System/Library/Extensions/BroadcomCrystalHD.kext
/System/Library/Extensions/BroadcomCrystalHD.kext/BroadcomCrystalHD.kext

[davilla]

/System/Library/Extensions/BroadcomCrystalHD.kext
/System/Library/Extensions/BroadcomCrystalHD.kext/BroadcomCrystalHD.kext

you made a boo-boo

yes -> /System/Library/Extensions/BroadcomCrystalHD.kext

no -> /System/Library/Extensions/BroadcomCrystalHD.kext/BroadcomCrystalHD.kext

BroadcomCrystalHD.kext is a osx container, just like xbmc.app. So it's actually a directory structure. That's why it's copied using the "-r" flag which mean "recursive" to get everything.

[nerpissad]

you made a boo-boo

yes -> /System/Library/Extensions/BroadcomCrystalHD.kext

no -> /System/Library/Extensions/BroadcomCrystalHD.kext/BroadcomCrystalHD.kext

BroadcomCrystalHD.kext is a osx container, just like xbmc.app. So it's actually a directory structure. That's why it's copied using the "-r" flag which mean "recursive" to get everything.

I used the -R flags like this one:

Code:

chown -R root:wheel /System/Library/Extensions/BroadcomCrystalHD.kext

is that the culprit you are referring to?
should I simply remove the 'wrong' .kext from within the correct .kext or what would be the correct way to proceed? should I start over is there a way to correct the current state?

[davilla]

I used the -R flags like this one:

Code:

chown -R root:wheel /System/Library/Extensions/BroadcomCrystalHD.kext

is that the culprit you are referring to?
should I simply remove the 'wrong' .kext from within the correct .kext or what would be the correct way to proceed? should I start over is there a way to correct the current state?

sudo rm -rf /System/Library/Extensions/BroadcomCrystalHD.kext

now copy the new one in place.

[nerpissad]

sudo rm -rf /System/Library/Extensions/BroadcomCrystalHD.kext

now copy the new one in place.

Code:

bash-2.05b# kextstat | grep crystalhd
   77    0 0x2fc6b000 0x18000    0x17000    com.broadcom.crystalhd.driver (3.6.0) <5 4 3 2>
bash-2.05b#

thank you very much!