Red Hat

I'm currently running dual boot Linux & Windows. Linux is Fedora core 3. I've downloaded and installed the rmp that was needed so that I could mount a NTFS filesystem. But when I go to mount the filesystem I'm still getting error's stating it does not support the NTFS filesystem.

Also the system tells me the package is installed. But whne I got to check the status of it running it isn't there. I'll post errors I have in a bit when I boot into Linux

Ok here the output.

cat /etc/redhat-release
Fedora Core release 3 (Heidelberg)

uname -r
2.6.9-1.667

rpm -q --queryformat "%{ARCH}\n" kernel
i686

rpm -ihv kernel-module-ntfs-2.6.9-1.667-2.1.20-0.rr.3.3.i686.rpm
Preparing... ########################################### [100%]
package kernel-module-ntfs-2.6.9-1.667-2.1.20-0.rr.3.3 is already installed

/sbin/modprobe ntfs
FATAL: Error inserting ntfs (/lib/modules/2.6.9-1.667/kernel/fs/ntfs/ntfs.ko): Invalid module format

cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev binfmt_misc
nodev usbfs
nodev usbdevfs
nodev futexfs
nodev tmpfs
nodev pipefs
nodev eventpollfs
nodev devpts
ext2
nodev ramfs
nodev hugetlbfs
iso9660
nodev mqueue
nodev selinuxfs
ext3
nodev rpc_pipefs
nodev autofs

So I've got no idea what and where I have gone wrong. I followed the instruction to install it. Yet it still will not work. I'm thinking I may be best to recompile the kernel with NTFS support.

All i want to do is be able to mount my Windows partition (/dev/hda2)

Oh yeah and when I go to mount this is what happens.

mount /dev/hda2 /mnt/windows
mount: fs type ntfs not supported by kernel

It doesn't matter if I use the "-t ntfs" option it still gives me the same error

Perhaps try depmod, then load module.

There is a good set of instructions here:

http://fedoranews.org/contributors/s...fc3_note/#NTFS

There is a lot of good info there about FC3.

Hope this helps.

I don't know if you noticed, but you have an invalid module format extension from your rpm that you installed. I have never seen a lib file with ext ".ko"

I would google again for another package and check the sig.

KW

The ko extension is valid, it's a change in kernel 2.6.x.