[lug] mount NTFS without a kernel rebuild?

[carl.wagner at level3.com]

This system has a stock kernel, with source installed.
This is what I get:

/home/cwagner $ modprobe ntfs
modprobe: Can't locate module ntfs
/home/cwagner $ insmod ntfs
insmod: ntfs: no module by that name found
/home/cwagner $ 

So to build the module I did a kernel build without installing it (make
xconfig, 
make clean, make bzImage, make modules)

and then made the /lib/modules/2.4.9-31/kernel/fs/ntfs directory
I copied /usr/src/linux-2.4/fs/ntfs/ntfs.o to
/lib/modules/2.4.9-31/kernel/fs/ntfs

Then I added to /lib/modules/2.4.9-31/modules.dep the line
   /lib/modules/2.4.9-31/kernel/fs/ntfs/ntfs.o:

When I ran a # insmod ntfs
Using /lib/modules/2.4.9-31/kernel/fs/ntfs/ntfs.o
/lib/modules/2.4.9-31/kernel/fs/ntfs/ntfs.o: unresolved symbol
mark_buffer_dirty_Rsmp_6c1374e7

So I tried the new kernel
  make modules_install
  cp /usr/lib/linux-2.4/arch/i386/boot/bzImage /boot
  cp /usr/lib/linux-2.4/System.map /boot
  vi /etc/grub.conf and added
=====
     title Red Hat Linux (NEW)
	root (hd0,2)
	kernel /boot/bzImage ro root=/dev/hda3
	initrd /boot/initrd-2.4.9-31.img
======
and booted the new kernel.

It hung on 
  uhci.c: USB UHCI at I/O 0xdce0, IRQ 11
    
I am now rebuilding with the config from
/usr/src/linux-2.4/configs/kernel-2.4.7-i686.config
(this is taking forever, I need to strip out the unused modules)

Carl.


"Jarosko, Bill" wrote:
> 
> You mean insmod.
> 
> -----Original Message-----
> From: David Morris [mailto:lists at morris-clan.net]
> Sent: Tuesday, October 01, 2002 10:43 AM
> To: Boulder Linux User's Group
> Subject: Re: [lug] mount NTFS without a kernel rebuild?
> 
> On Tue, Oct 01, 2002 at 09:26:09AM -0600, carl.wagner at level3.com wrote:
> > Is there a way to get the kernel module for NTFS without having to
> > rebuild the whole kernel?  I want to grab some files from my nt partition.
> 
> If you are using a pre-built kernel, you can probably just
> probe the module:
> 
>     modprobe ntfs
> 
> Otherwise, you probably built the kernel yourself and, if
> you still have that directory around you built in, you can
> follow the instructions from another post to get just the
> module built...you might search the net (perhaps visit
> kernel.org) for details of incrementally building new
> modules, as it is easy once you know how to do it (never
> needed to).
> 
> BTW, I also suggest you use xconfig, not menuconfig.
> 
> --David
> 
> ----- End forwarded message -----
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug