Ben Stern <[EMAIL PROTECTED]> wrote: > On Wed, Dec 20, 2006 at 07:48:29PM -0500, J. Milgram wrote: > > Yup, I can modprobe vfat with no path, and that works. And same here, > > it's worked fine on every other machine I've used, up to now. Who knows. > > When you physically attach the device containing the VFAT filesystem, what > do you get out of dmesg? Based on the fact that you say your System.map is > right, it sounds to me like modules.conf is not winning OR you do not have > automatic module loading turned on in your kernel.
well I'll be... how could I have missed that! That should fix it. That said, I think I'll leave vfat support built in, as I enjoy the microseconds-faster response time I get now when I mount the flash drive :) While on the topic: what exactly is System.map for anyway? The truth is that for years I never even bothered copying it to /boot after installing a new kernel. > (I have noticed under Slackware that when I did a make install, it used to > shove the System.map in /, and leave Pat's System.map in /boot. I wonder why ... make install should be part of the kernel's makefile and I think Slackware always provided just the stock kernel source. > I have > since written my own /sbin/installkernel shell script, so this no longer > happens - but are you sure the kernel you are booting is loading the > System.map that matches it?) > > Ben > -- > Ben Stern UNIX & Networks Monkey [EMAIL PROTECTED] > This post does not represent FTI, even if I claim it does. Neener neener. > UM Linux Users' Group Electromagnetic Networks Microbrew Software >
