SlackwareThis Forum is for the discussion of Slackware 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.
I'm having trouble accessing my NTFS partition after compiling the 2.6.12 kernel. I did some searching and it seems like most solutions were that support was not included in the kernel or the /etc/fstab file was screwed up. I don't think it's either of these so I don't know what the problem is.
the NTFS partition is at /dev/hda1
from my .config:
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
(note CONFIG_NTFS_RW is for read and write, and since I don't trust the writing that's not what I want.)
ive had problems like that when i built my kernel... and simple make && make modules_install again will usually fix it. i dont know why it does that.. and i would get pissed off and fight with it over and over.. but now i just try reinstalling the kernel again.. and it usually works.
Which is correct, I changed the name in the makefile, and double checked the config.
You don't have the support as a module, but just make sure that the modules got installed to the right directory under /lib. I don't know if renaming can create other problems or not. On the other hand, if you didn't have the modules accessible, you would get tons of other errors...
Well I would prefer to have it built into the kernel, but I built it as a module and now it works. No idea why it didnt work built in. I'm not going remake my kernel just to see if I can get it built it. Anyway that was strange...
I have seen the same thing but with reiserfs, except it didn't like being built as a module for one particular kernel. Then a couple kernels later it was OK again. So if you really want it built into your kernel then keep trying cause it might work later.
I'm having the same thing happen with samba, only reverse. If I build it as a module I get a kernel oops when I try to interact with my win box. Building it directly into the kernel and all is well. Some strange things afoot in new kernel land...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.