• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: FUSE not found  (Read 12946 times)
elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« on: April 13, 2009, 03:03:32 PM »

I need fuse for ntfs-3g support, however it's not there:

Code:
root@debian:/lib/modules/2.6.22.18# modprobe fuse
FATAL: Module fuse not found.
Logged

bfmorgan
Guest
« Reply #1 on: April 13, 2009, 03:14:35 PM »

You might want to look at this thread. I still haven't solved some issues but, the fuse one is easy.

http://openplug.org/plugforum/index.php?topic=37.0
Logged

moshiach
Guest
« Reply #2 on: April 13, 2009, 04:17:31 PM »

You'll need to rebuild your kernel if you want FUSE.   
Logged

elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #3 on: April 13, 2009, 04:32:26 PM »

You might want to look at this thread. I still haven't solved some issues but, the fuse one is easy.

http://openplug.org/plugforum/index.php?topic=37.0


I have installed ntfs-3g and I have no errors at all during the install.

When I try to mount with ntfs-3g I get this error:

Code:
root@debian:~# mount -t ntfs-3g /dev/sda1 /mnt/sda1
FATAL: Module fuse not found.
fuse: device not found, try 'modprobe fuse' first
root@debian:~#

modprobe fuse returns:

Code:
root@debian:~# modprobe fuse
FATAL: Module fuse not found.
root@debian:~#

Logged

elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #4 on: April 13, 2009, 04:50:13 PM »

You'll need to rebuild your kernel if you want FUSE.   

Wow, so no built in ntfs support at all? Can't I just compile a kernel module without recompiling the entire kernel?
Logged

moshiach
Guest
« Reply #5 on: April 13, 2009, 07:07:47 PM »

I've never tried just building one module without having support for it in the kernel.  Try it and see.
Logged

elBradford
Newbie
*

Karma: 0
Posts: 44


View Profile
« Reply #6 on: April 13, 2009, 07:24:05 PM »

I've never tried just building one module without having support for it in the kernel.  Try it and see.

That's the problem! I can't compile it since I can't get the source from the repos. When I try to compile anything really, I can't because I don't have the kernel source or headers (I guess they're omitted to make it smaller).

Now I'm trying to compile my own kernel, however I am stuck at the "make tools" step in including the uBoot binary. Ahhh linux, every time I have another go at you you make me want to kill you.
Logged

moshiach
Guest
« Reply #7 on: April 13, 2009, 11:48:29 PM »

Linux - more fun than porn.  At least with linux there is always something new.

Here's how I managed to build things. Feel free to skip the first three steps if you are already booting from nand.

1)  If you aren't already booting into ubuntu (maybe you broke your plug when you opened the package like I did) get yourself booting to TFTP and NFS first using the uImage.sheeva.whateverdate kernel and the root package from the Linux Host tar.   Make sure you put your kernel image and the jffs2 of the root into that root directory so they are available for the next step.
2)  flash_eraseall /dev/mtd1
     flash_eraseall /dev/mtd2
     nandwrite -pm /dev/mtd1 uImage.sheeva.whatever
     nandwrite -pm /dev/mtd2 root.jffs2
3)  Now you can reboot and set your environment variables to boot from nand.  Do it.

4)  Since this is ubuntu, you need to apt-get a few things to build your environment properly.  I suggest:
apt-get install gcc make ncurses-dev ncurses-bin ncurses-base ncurses-term wget
although I might have missed a package or two there.  You'll know what you need when one of the next steps complains.
 
5)  Time to build u-boot. 
      mkdir ~/tmp
      cd ~/tmp
      wget http://ftp://ftp.denx.de/pub/u-boot/u-boot-2009.03.tar.bz2 
      # rumor has it that a newer version supports the plug, but this is the one I've had the most success with.
       tar xvjf u-boot-2009-03.tar.bz2
       cd u-boot-2009-03
       touch include/config.{h,mk}
       make tools   
       #this compilation will seem to fail, but it will produce mkimage for the next step
       cp tools/mkimage /usr/local/bin

6)  I used kernel sources taken from this snapshot  Just download the snapshot to /usr/src and untar it.  It will expand to orion.git with all the kernel sources below it.

7)  ln -sf /usr/src/orion.git /usr/src/linux

8 )  cd /usr/src/linux; make ARCH=arm mrproper; make ARCH=arm kirkwood_defconfig;make ARCH=arm menuconfig;make ARCH=arm uImage module module_install

9)  Wait 20 or so minutes after compilation gets going.  Once it completes you should have /usr/src/linux/arch/arm/boot/uImage which you can then use for:

10)  flash_eraseall /dev/mtd1
       nandwrite -pm /dev/mtd1 my-sparkling-uImage

Reboot, but stop the boot process.  You need to set/check 2 environment variables.  mainlineLinux should be yes and arcNumber should be 2097.  If they aren't set them.  Once they are set and saved, reset the plug and it should boot your new kernel. 

I'm not sure what the mainlineLinux variable is for exactly, but kernels I compile won't start without it.  The included uImage.sheeva.20090319 won't start with it.  Go figure. 

Hope that helps.
Logged

Pages: [1]
Print
Jump to: