fluiday / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

MacFUSE doesn't work on 64-bit kernels #406

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Example errors:
- NTFS-3G could not mount
- /Library/Filesystems/fusefs.fs/Support/fusefs.kext failed to load -
(libkern/kext) link error; check the system/kernel logs for errors or
try kextutil(8).
- the MacFuse file system is not available

Cause:
It is because the official version of MacFUSE being distributed is not 
compatible with new Mac's as Apple have changed the default kernel from 32-bit 
to 64-bit and the version of MacFUSE is 32-bit not 64-bit (MacFUSE itself 
hasn't been updated by the primary maintainer which makes things hard).

Workaround: 
Try installing this version from Tuxera:
http://www.tuxera.com/mac/macfuse-core-10.5-2.1.9.dmg 

Original issue reported on code.google.com by pasamio on 28 Apr 2011 at 2:31

GoogleCodeExporter commented 8 years ago
Tried the  sources listed above when the version shipped with  LaCie's Wuala 
cloud drive failed to install. Suspect it was the 32/64 bit problem with the 
original program. Since I'm using Os 10.5.8, I tried the version above. I got 
another error message that the media was damaged and I should contact Tuxera... 
will do so after I try  a second DL ( and it fails?)

Original comment by norton.w...@gmail.com on 29 Apr 2011 at 2:09

GoogleCodeExporter commented 8 years ago
See issue 346

Original comment by somek...@gmail.com on 24 May 2011 at 2:08

GoogleCodeExporter commented 8 years ago
Cross-posting this comment from bradleya...@gmail.com in issue #346, which 
solved the problem for me:

"Comment 20 by bradleya...@gmail.com, Feb 28, 2010

This worked for me SL 64bit

As of MacFuse 2.0, the entire stack is available in 64-bit. Not sure about 
TrueCrypt,
but you don't seem to be getting that far anyhow, probably because the default
MacFuse build is broken. You can download a hopefully fixed 64-bit MacFuse at
http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg"

Original comment by angela.b...@acquia.com on 4 Jun 2011 at 11:21

GoogleCodeExporter commented 8 years ago
Thanks Angela, the version you linked to works for me and solves the same issue 
for me.

Original comment by frig...@gmail.com on 15 Jun 2011 at 8:39

GoogleCodeExporter commented 8 years ago
I was going to try that but didn't like the idea of going back a version, at 
first. I finally tried this and it worked like a charm: 
http://www.tuxera.com/mac/macfuse-core-10.5-2.1.9.dmg

Hope this helps someone else.

Original comment by jmevalen...@gmail.com on 16 Jul 2011 at 9:14

GoogleCodeExporter commented 8 years ago
This one worked for me too :-)

http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg"

Original comment by miba...@gmail.com on 18 Jul 2011 at 9:13

GoogleCodeExporter commented 8 years ago
thx - 2.1.9 works !

Original comment by a1lexwin...@googlemail.com on 18 Jul 2011 at 10:55

GoogleCodeExporter commented 8 years ago
Thank jmevalen .......
Like you said, it worked like a charm

Original comment by wspamb...@gmail.com on 19 Oct 2011 at 4:37

GoogleCodeExporter commented 8 years ago
Thank you all. 2.1.9 works for me on Mac OS X 10.8.2

Original comment by mail.ke...@gmail.com on 26 Dec 2012 at 12:07

GoogleCodeExporter commented 8 years ago
Thanks a million. As you say "like a charm" on Mac OS X 10.8.2

Original comment by gordonst...@gmail.com on 29 Dec 2012 at 1:22

GoogleCodeExporter commented 8 years ago
Hi guys, I am using OS X 10.8.5. This works like a charm. Now i can read/write 
the external drives. However after 15 sec this message pop up on the desktop 
screen. I think this is because the drives system become slower when trying to 
connect with the updated system of my mac . Do you think i just close, ignore 
the message and continue life as normal.

NTFS-3G could not mount /dev/disk1s1
at /Volumes/SEAGATE 1 because the following problem occurred:

Did not receive a signal within 15.000000 seconds. Exiting...

Original comment by rudypar...@gmail.com on 20 May 2014 at 12:15