OpenWrt Forum Archive

Topic: problem mounting fat filesystems

The content of this topic has been archived on 29 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

Using Kamikaze 8.09 RC1 on an Asus WL500G Premium, I can mount ext2 file systems over usb just fine. But for fat32 there seems to be a problem loading the module:

root@OpenWrt:~# insmod fat
insmod: unresolved symbol load_nls
root@OpenWrt:~# insmod vfat
insmod: unresolved symbol fat_scan

I have already installed all the kmod-nls-* packages, what could be the problem?

Thanks!
Mark

kmod-fs-* package?

Thanks for your reply and you're right. I forgot to mention I had also installed these packages:

kmod-fs-ext2 - 2.4.35.4-brcm-2.4-1 -
kmod-fs-msdos - 2.4.35.4-brcm-2.4-1 -
kmod-fs-vfat - 2.4.35.4-brcm-2.4-1 -

I can't see which other packages I could need for mounting fat32 file systems, but just in case I installed all the other kmod-fs-* packages.

However, the errors remain the same.

All help appreciated wink

Mark

I think you also need to install modules:
- nls_cp437 , and
- nls_iso8859_1
(Kernel modules kmod-nls-cp437 and kmod-nls-iso8859-1)

Check your dmesg and logread after unsuccessful mount, they should also state it. I got my vfat mount working with these.

--
kurkku

Johndoe: did you try installing all packages starting with "kmod-nls-" ? That's basically what I did to solve the "unresolved symbol bla-nls" errors. I think this should be safe, as long as you have the available memory to install all of them.

johndoe - did you ever solve this?  I am seeing the exact problem.  Even though I've selected to bulid kmod-nls-base as a module, it doesn't seem to appear in the packages directory - nor is it in on the snapshot download location for opkg.

Any thoughts anyone?

yarrumretep wrote:

Even though I've selected to bulid kmod-nls-base as a module, it doesn't seem to appear in the packages directory - nor is it in on the snapshot download location for opkg.

Same problem here.

I have a working fat on usb. I remember i've installed alot of pkg to get it work right. At some momment it was working but with short file names. And it should have been installed another pkgs. Obviously i don't remember what i've installed for it to work but if you know a method to get the installed pkgs i will do dat.
My sistem is x86, if that matter.

From my memory, there was some OHCIsomething and UHCIsomething for usb. That should be installed too.

(Last edited by Misuser on 25 May 2009, 09:02)

For stock k809 firmware, I install the following to make vfat usb drives accessible.

opkg install kmod-fs-vfat kmod-fs-ext2 kmod-fs-ext3 fdisk e2fsprogs swap-utils dosfstools
opkg install kmod-usb-uhci nano kmod-loop kmod-nls-cp437 kmod-nls-iso8859-1
opkg install kmod-usb2 kmod-usb-storage usbutils

Not all may be needed, but in particular, kmod-nls-cp437 and kmod-nls-iso8859-1 are required.  I don't understand why, if they are needed, they are not dependancies of kmod-usb-storage.

In the build system, select these in "make menuconfig".  usbutils give you lsusb.  If you have problems after intstalling the above, provide the output from lsusb and the tail of dmesg after you insert the usb device.

Thanks! I got it to work now, but it's really strange. I used the menuconfig option "Enable all packages by default". This selects all modules automatically, but this only happens on a fresh tree. Not when I already built it earlier. You can see whether or not the option did its job by checking if all filesystems are enabled as modules (for example).

Then I built everything, flashed the new image, and now the funny thing: I just did:

opkg install kmod-usb-storage
opkg install kmod-fs-vfat

and after that I was able to mount the USB drive! smile

I was expecting that I had to install the other (ohci/uhci/usb2, nls*) modules as well (using opkg). Apparently enabling those modules in menuconfig was enough. Hmmmm....

The discussion might have continued from here.