#modprobe: can't load module fuse: unknown symbol in module, or unknown parameter

1 messages · Page 1 of 1 (latest)

lavish apex
#

Hello people. I am trying to mount the Windows partition to support dual boot, so I installed ntfs-3g and enabled fuse in my kernel at File systems -> FUSE (Filesystem in Userspace) support to build as a module. But when running mount it gives me an error and asks to modprobe fuse, so I do, and it returns: modprobe: can't load module fuse: unknown symbol in module, or unknown parameter and this errors on dmesg that I show in the picture. After that I tried embedding fuse in the kernel, but it still is unable to mount (see second picture), and running mount without -t says: mount: mounting /dev/sda5 on /win failed: Invalid argument

wary flint
#

So

#

Are you POSITIVE you are currently booting with the kernel that has fuse built in?

#

Second

#

If you are sure

#

Make sure eselect kernel

#

Points to your kernel

#

Then re merge fuse

wary flint
#

I’m like 99% sure the issue is that you are not booted into the kernel that you think you are

#

The version mismatch also means that the module for fuse is built for a different kernel than the one running

lavish apex
# wary flint Then re merge fuse

Oh. I think I'm not booting on that hahah i have to rename the kernel files. I forgot
I'll do that tomorrow. I just turned off the computer

wary wing
#

relying entirely on or using ntfs-3g to mount an ntfs filesystem is no longer necessary for several years

#

the kernel provides ntfs3 filesystem driver support

#

the userland tools provided by ntfs-3g can still be useful however the filesystem type for a kernel supported ntfs partition mount should be ntfs3

lavish apex
lavish apex
#

Oh it mounted

#

Wait

wary flint
#

The error

#

Tells you what to do

wary flint
wary wing
#

mount -t ntfs3 /dev/sda5 /win

#

just avoid ntfs-3g using as the filesystemn type

lavish apex
lavish apex
wary wing
#

ntfs-3g filesystem type mount is depreciated

wary flint
lavish apex
lavish apex
lavish apex
wary flint
wary flint
lavish apex
#

Maybe i need to enable ntfs filesystem on kernel?

lavish apex
lavish apex
wary flint
#

Did you use os-prober

wary wing
#

did you make a custom kernel? ntfs3 filesystem is supported by the distro kernels

lavish apex
wary wing
#

there you go

wary flint
wary wing
#

the fuse errors were an obvious clue for a veteran :)

lavish apex
wary flint
#

Well as long as it only needs to read windows, it should work

#

As is

lavish apex
#

🤷 what's the difference from the last two options?

wary wing
#

if your custom kernel disabled partition type supports you'll have similar complcations

wary flint
wary wing
#

one of them is the very old read only ntfs driver

lavish apex
wary wing
#

the read/write driver name is ntfs3

#

you wont need both

lavish apex
wary wing
#

also if by some chance you decided to not use any <M> module configratiuosn that kenrel build may malfunction

#

ot would be more likely to

wary wing
#

booting a fully non modular kernel is akin to tube feeding an infant everything at kernel init 😅

wary flint
#

Kernels are black arcane magic

#

I do not question them

wary flint
#

I fear them

lavish apex
lavish apex
wary wing
#

exfat support as a module also could be useful

#

there's another subsection with partition type support features you need some of

#

if your curious and wanted to study some of my older custom configs you can find several here

#

no modules means everything loads at kernel init and occupies a memory address whether or not that feature is used or useful

#

thats not really ideal

wary flint
#

I paid for the ram I’m going to use the whole ram

lavish apex
lavish apex
wary wing
#

not so much about not having enough ram

#

more of a memory address conflict concern

lavish apex
#

Now os prober is active and it is not identifying windows

wary wing
#

custom kernel grief :)

wary flint
wary wing
#

if you want some sombering perspective about your kernel config vs. the dist-kernel create a diff of both configs then read the resulting text file.

#

helped someone do that last year and they were missing 30k lines or something of similar significance

lavish apex
#

Thx. I'll take a look at that later

wary wing
#

keep in mind that everything included in a kernel config file may not be every available kernel selection that could be used or configured. kernel kconfig covets many secrets until related features are available config selections

#

depmod can be your best friend or your worst nightmare ;p

wary flint
#

At that point just use gentoo kernel bin?

wary wing
#

at least very valuable reference

lavish apex
wary flint
#

Why

lavish apex
wary flint
wary flint
#

Do you or do you not want a working system

lavish apex
lavish apex
#

I manually edited /etc/grub.d/40_custom I think