DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
when I booted my computer today I got this message from ntfs-3g
Code:
WARNING: Deficient Linux kernel detected. Some driver features are
not available (swap file on NTFS, boot from NTFS by LILO), and
unmount is not safe unless it's made sure the ntfs-3g process
naturally terminates after calling 'umount'. If you wish this
message to disappear then you should upgrade to at least kernel
version 2.6.20, or request help from your distribution to fix
the kernel problem. The below web page has more information:
http://www.ntfs-3g.org/support.html#fuse26
I don't know where that comes from, but certainly it wasn't there yesterday. Was there maybe an update on ntfs-3g, which requires a newer kernel (module) ? Did anyone else have this and knows how to solve without making a 2.6.20 kernel ?
I'm using a lot of the precompiled kernel modules out of the repositories and a new kernel would require me to rebuild them all manually as well, which I'm not so keen on ...
Upgrade to kernel 2.6.20 or ask the Debian devs to fix their kernel. If you fix the kernel yourself then they will break your fix every time when they upgrade the broken kernel without the fix. So you either get rid of them altogether or make them fix their problem. No other way.
What it is, is that you installed ntfs-3g from source and not from Debian repositories. Which is OK because the one from source is more up to date. You did not however, install Fuse from source or did not install it properly. The 1st line in the instructions at ntfs-3g site has a link to the proper fuse from source that should be installed before ntfs-3g from source. Although you did not mention which Debian distribution you are using, I installed ntfs-3g from repositories in Etch which work good so far. But the one from source is probably better mostly because of the "deficient" fuse support in kernels below version 2.6.20
During the steps to add fuse from source, if you actually read what it tells you, you would have noticed after the ./configure command it told you it would not include building the fuse module because it is present in the kernel. There is also a link to a site which gives you the low down and tells you how to make sure to build the module from source instead of using the "deficient" fuse with the kernel, by issuing this command at the ./configure step:
Code:
./configure --enable-kernel-module
From now on it would probably be in your best interest to read the information supplied while building from source. What do you think?.
Funny I never got that error, because I installed ntfs-3g from source in all my other distributions where I have seen it with some of them way back when. I originally installed ntfs-3g on Etch when it was "testing", which also installed fuse and fuse libs, all from repositories. I also installed the 2.6.20 kernel from sid last week and everything is cool. But I also installed (upgraded) fuse related packages from sid repositories also.
You can still boot from the previous kernel though, right?. Is the mapping screwed with the old kernel also?. So basically you're saying you've pretty much done everything I've done so far by installing ntfs-3g and fuse from repos. in Etch and have kept "testing" in sources.list.
Well, I haven't applied updates in Lenny for a couple days now, maybe I'll make an image of it and install the image in another partition and play around with that before applying the ntfs-3g update in the first installation. Might have to remove the Debian packages and install the source packages that don't need anymore baby sitting after kernel upgrades anyways.
I also installed the 2.6.20 kernel from sid last week
There is a 2.6.20 kernel in sid ?!?
I hate myself ... I have taken the one from kernel.org
The new kernel has remapped all drives, hdb is now sdc for example, so it didn't even find the / partition at first. The whole (s)ata support seems to have changed in 2.6.20.
I have 7 drives with 20+ partitions, 6 of which are encrypted, so this is quiet a mess now, but I have almost finished it. I'm still tempted to try the sid kernel now ...
Yes
Not sure which mirrors supplied the kernel packages as I also have kernel.org mirrors in my sources.list, but basically just doubled my sources for Debian mirrors and the kernel.org mirror and changed the "testing" to "unstable" and added another line for kernel-archive.buildserver.net for the headers for compiling modem drivers/modules.
I just finished applying updates to a copy of my original installation, the "libxslt1.1" package is the one that required ntfs-3g packages to upgraded also. But no error messages, so it must be that sid 2.6.20-1 kernel that made the difference. They mentioned at ntfs-3g site that kernels 2.6.20 and above have the proper fuse version included.
Here is my sources.list, my Debian mirror (yorku) is a local mirror for me, probably best to stick to your nearest one, I commented out the sid repos till I want something from there:
Code:
###############################
##### From Debian Mirrors #####
###############################
deb http://debian.yorku.ca/debian/ testing main contrib non-free
deb-src http://debian.yorku.ca/debian/ testing main contrib non-free
#deb http://debian.yorku.ca/debian/ unstable main contrib non-free
#deb-src http://debian.yorku.ca/debian/ unstable main contrib non-free
####################
##### Security #####
####################
deb http://debian.mirror.iweb.ca/debian-security/ testing/updates main contrib non-free
deb-src http://debian.mirror.iweb.ca/debian-security/ testing/updates main contrib non-free
##################
##### Kernel #####
##################
deb http://mirrors.kernel.org/debian/ testing main contrib non-free
deb-src http://mirrors.kernel.org/debian/ testing main contrib non-free
#deb http://mirrors.kernel.org/debian/ unstable main contrib non-free
#deb-src http://mirrors.kernel.org/debian/ unstable main contrib non-free
deb http://kernel-archive.buildserver.net/debian-kernel/ trunk main
######################
##### Multimedia #####
######################
#gpg --keyserver hkp://wwwkeys.eu.pgp.net --recv-keys 1F41B907
#gpg --armor --export 1F41B907 | apt-key add -
deb ftp://mirrors.powersource.cx/pub/debian-multimedia/ testing main
deb-src ftp://mirrors.powersource.cx/pub/debian-multimedia/ testing main
######################
##### Unofficial #####
######################
#gpg --keyserver subkeys.pgp.net --recv-keys 6823D007
#gpg --armor --export 6823D007 | apt-key add -
deb http://ftp.debian-unofficial.org/debian/ testing main contrib non-free restricted
deb-src http://ftp.debian-unofficial.org/debian/ testing main contrib non-free restricted
##### Kirya #####
#gpg --keyserver wwwkeys.eu.pgp.net --recv-keys FBABB737
#gpg --export -a FBABB737 | apt-key add -
#deb http://packages.kirya.net/debian/ unstable main contrib non-free
#deb-src http://packages.kirya.net/debian/ unstable main contrib non-free
I just finished applying updates to a copy of my original installation, the "libxslt1.1" package is the one that required ntfs-3g packages to upgraded also. But no error messages, so it must be that sid 2.6.20-1 kernel that made the difference.
yup, the warnings are gone for me as well with 2.6.20. I have built it from scratch and spent the whole night with it, mainly because of the drive remapping. I have also installed the sid kernel now, but it does the same remapping procedure. Also the precompiled modules (like ivtv) are not there yet.
I think I'll stick now with the selfbuilt kernel and build all the additional modules from source for it. When the 2.6.20 comes to testing, I'm gonna switch back to the repository kernel. For now I'll keep it as backup kernel because the 2.6.18 is totally incompatible for me.
I should probably have stayed with etch a bit longer, hopefully there are not more unpleasant surprises to come.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.