Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
05-07-2006, 02:08 AM
|
#1
|
Member
Registered: Sep 2003
Location: USA
Distribution: Ubuntu 20.04
Posts: 111
Rep:
|
NTFS broken w/ 2.6 kernel
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.)
$ more /etc/fstab
/dev/hdb2 swap swap defaults 0 0
/dev/hdb1 / reiserfs defaults 1 1
/dev/hda1 /mnt/winxp ntfs ro,umask=002 1 0
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
Also I did a
$ dmesg | grep ntfs
and there was no output, I'm not sure if the kernel is supposed to print a message when it is loading the ntfs support.
Any idea's guys?
|
|
|
05-07-2006, 02:19 AM
|
#2
|
Senior Member
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802
Rep:
|
You have ntfs built into the kernel so you will not see any module loading. What happens if you type this:
cat /proc/filesystems
and
mount /mnt/winxp
|
|
|
05-07-2006, 02:35 AM
|
#3
|
Member
Registered: Sep 2003
Location: USA
Distribution: Ubuntu 20.04
Posts: 111
Original Poster
Rep:
|
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev binfmt_misc
nodev sockfs
nodev usbfs
nodev pipefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev eventpollfs
nodev devpts
reiserfs
nodev ramfs
msdos
vfat
iso9660
nodev nfs
nodev nfsd
nodev autofs
udf
nodev mqueue
nodev oprofilefs
nodev rpc_pipefs
Mount only works as root, but that's not the real problem
root@markscpu:~# mount /mnt/winxp
mount: unknown filesystem type 'ntfs'
|
|
|
05-07-2006, 02:39 AM
|
#4
|
Senior Member
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802
Rep:
|
It seems you do not have ntfs support? Are you sure you are running the new kernel you just built?
uname -r
|
|
|
05-07-2006, 02:47 AM
|
#5
|
Member
Registered: Sep 2003
Location: USA
Distribution: Ubuntu 20.04
Posts: 111
Original Poster
Rep:
|
bash-3.00$ uname -r
2.6.16MyCustom
Which is correct, I changed the name in the makefile, and double checked the config.
|
|
|
05-07-2006, 02:55 AM
|
#6
|
Senior Member
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802
Rep:
|
Since you have ntfs built into the kernel I would try building it as a module and see if that helps.
|
|
|
05-07-2006, 03:09 AM
|
#7
|
Member
Registered: Sep 2003
Location: USA
Distribution: Ubuntu 20.04
Posts: 111
Original Poster
Rep:
|
Will leave compiling but for now sleep...
|
|
|
05-07-2006, 03:15 AM
|
#8
|
Senior Member
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 15.0, Slackwarearm 14.2
Posts: 1,158
|
I have ntfs compiled as a module but it doesn't show up in /proc/filesystems. I can mount ntfs partitions however.
|
|
|
05-07-2006, 03:17 AM
|
#9
|
Senior Member
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802
Rep:
|
I usually will not show up in /proc/filesystems untill you mount the partition. After that it loads the module then it should show up.
|
|
|
05-07-2006, 04:18 AM
|
#10
|
Member
Registered: Apr 2005
Distribution: Slackware
Posts: 350
Rep:
|
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.
|
|
|
05-07-2006, 05:06 AM
|
#11
|
Senior Member
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 15.0, Slackwarearm 14.2
Posts: 1,158
|
Quote:
Originally Posted by mjl3434
bash-3.00$ uname -r
2.6.16MyCustom
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...
|
|
|
05-07-2006, 09:16 AM
|
#12
|
Member
Registered: Sep 2003
Location: USA
Distribution: Ubuntu 20.04
Posts: 111
Original Poster
Rep:
|
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...
|
|
|
05-07-2006, 09:39 AM
|
#13
|
Senior Member
Registered: Jul 2003
Location: Indiana
Distribution: Mandrake Slackware-current QNX4.25
Posts: 1,802
Rep:
|
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.
|
|
|
05-08-2006, 01:10 AM
|
#14
|
Senior Member
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914
Rep:
|
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...
|
|
|
All times are GMT -5. The time now is 11:38 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|