I'm getting this error ... imsg3-mx root # modprobe fuse FATAL: Error inserting fuse (/lib/modules/2.6.11-gentoo-r4/extra/fuse.ko): Unknown symbol in module, or unknown parameter (see dmesg) imsg3-mx root # dmesg fuse init (API version 5.1) fuse distribution version: 2.2.1 fuse exit fuse: Unknown symbol vfs_permission Can someone help me and tell me what's wrong :) ? It's fuse 1.3, the ebuild is in bugs.gentoo.org If I update to 2.x it works, but I don't want to, since there are some programs which only work with the 1.3 Reproducible: Always Steps to Reproduce: 1.modprobe fuse Actual Results: FATAL: Error inserting fuse (/lib/modules/2.6.11-gentoo-r4/extra/fuse.ko): Unknown symbol in module, or unknown parameter (see dmesg) Expected Results: Should have been loaded without error. imsg3-mx root # emerge --info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Apr 28 2005, 23:17:47)] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.gg3.net/ http://mirror.averse.net/pub/gentoo/" LANG="fr_FR.utf8" LC_ALL="fr_FR.utf8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.asia.gentoo.org/gentoo-portage" USE="x86 X aac aalib alsa apache2 apm avi bash-completion berkdb bitmap-fonts bzlib cdr cjk crypt cups curl dedicated directfb divx4linux dvd dvdread eds emboss encode escreen exif fbcon flac flash foomaticdb fortran fusesuid gdbm gif gnome gpm gstreamer gtk gtk2 howl imagemagick imlib innodb ipv6 jabber java javascript jit jpeg junit libg++ libwww mad matroska mbox memlimit mikmod mime mmx mng motif mozilla mp3 mpeg mysql nas ncurses nls nocd nowin nptl nvidia ogg oggvorbis opengl oss pam pdflib perl png python quicktime readline real samba sdl shared sharedmem sockets socks5 sox spell sse sse2 ssl startup-notification stroke svga szip tcltk tcpd tiff toolbar truetype truetype-fonts type1-fonts unicode usb videos vorbis wmf xchatdccserver xine xinerama xml xml2 xmms xpm xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, LINGUAS
sorry, what program only works with fuse version 1.3? You have to upgrade since there is nothing in portage depending on version 1.3.
I could restore the old version and probably fix this bug when you tell me what you need it for .. From my perspective it is not usefull to do that since no pkg needs it.
The package which needs it is "gmailfs", which isn't officially implemented into the Portage tree ... but it does have an ebuild in here .. http://bugs.gentoo.org/show_bug.cgi?id=87659 http://bugs.gentoo.org/show_bug.cgi?id=63785 And the fuse 1.3 is also filed in here .. http://bugs.gentoo.org/show_bug.cgi?id=59733
I'm reopening the bug .... I'm sorry if I can't do this. And I've sent some info about fuse 1.3 on the last comment. Please help me, if possible.
Created attachment 59015 [details] gmail.tar Here is a tarball of my attempts to make the gmail ebuilds use the debian patches for fuse-2* support. It works for me, but I did not figure out the cmdline ;)
Can you please tell me if this works for you, so that I can close this bug?
OK ... I'm testing it right now .. thanx a lot ^^
I'm getting this while emerging fuse ... WARNING: //lib/modules/2.6.11-gentoo-r4/extra/fuse.ko needs unknown symbol vfs_permission [ ok ] And this while emerging python-libgmail : !!! Digest verification Failed: !!! /usr/local/portage/net-libs/python-libgmail/python-libgmail-0.0.9_pre20050208.ebuild !!! Reason: Filesize does not match recorded size I fixed it with the ebuild digest ... Same thing occured with the python-fuse ... also fixed with ebuild digest !!! Digest verification Failed: !!! /usr/local/portage/sys-fs/python-fuse/python-fuse-2.2.ebuild !!! Reason: Filesize does not match recorded size And finally, when I try to mount something, I get this error : --------------------- imsg3-mx root # fusermount: unknown option -n Try `fusermount -h' for more information --------------------- I'm trying to figure out what's wrong too ... is it because of the /usr/bin/gmailfs.py calling a non-existant option ? PS : FYI, fuse-1.3 had this switch -n PPS : And I'm also getting a weird error when I do mount -t gmailfs ----- mount: unknown filesystem type 'gmailfs' ----- And lastly, when I try to modprobe fuse, it still gives me this error : ---- imsg3-mx root # modprobe fuse FATAL: Error inserting fuse (/lib/modules/2.6.11-gentoo-r4/extra/fuse.ko): Unknown symbol in module, or unknown parameter (see dmesg) ---- dmesg gives (again) : ---- (snip) fuse: Unknown symbol vfs_permission ---- Is this because of my Gentoo or because of the fuse module =[ ?
Can you please rm /lib/modules/2.6.11-gentoo-r4/extra/fuse.ko and remerge the latest fusse? (not your 1.3.something) Oh, and for digest-mismatches: I am tired of fixing those I use FEATURES=-strict
Assuming you are testing gmailfs, this can't be added into portage. See bug 62100.
Strange .. I'm sure I re-emerged fuse to 2.2.1 ... Fuse works, and I think maybe I'll manage myself to make gmailfs work .. I'll trouble you no more ... Thank you for all your work & kindness ... =] You helped me a lot =] I'm sorry if working with gmailfs is against the rules ... :(
ok, please report back if it works for you I think the bug is fixed as we know that fuse-1.* is not needed
