maxim wexler wrote:
--- Mariusz Pêkala <[EMAIL PROTECTED]> wrote:
On 2005-12-18 18:18:34 +0100 (Sun, Dec), Holly
Bostick wrote:
[EMAIL PROTECTED] ~ $ grep FAT
/usr/src/linux/.config #
CONFIG_X86_MCE_NONFATAL is not set # DOS/FAT/NT
Filesystems
CONFIG_FAT_FS=y CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
Since you have the vfat module compiled into the
kernel, it seems to me
that this can only mean that the module is not
loaded (as it might not
be if a FAT32 filesystem did not need to be
mounted at boot, because it
was not detected, and/or the partition is not set
to autoload at boot
via /etc/fstab, and/or the module is not set to
autoload at boot via
/etc/modules.autoload.d/kernel-2.*).
If you get an error when attempting to modprobe,
or after modprobing
mounting still returns an error, then we've at
least got more
information (in the case of an error), or
eliminated one possible cause
(if mounting still fails after successfully
modprobing the module).
As I can see the VFAT is compiled in the kernel, not
as a module.
Compare:
[EMAIL PROTECTED] ~ $ zcat /proc/config.gz | grep -i fat
CONFIG_X86_MCE_NONFATAL=y
# DOS/FAT/NT Filesystems
CONFIG_FAT_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=852
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-2"
I wonder what is in your /proc/filesystems and
/etc/filesystems ? Could
you post their contents here?
reflex pindar # cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev debugfs
nodev pipefs
nodev futexfs
nodev tmpfs
nodev inotifyfs
nodev eventpollfs
nodev devpts
reiserfs
ext2
nodev ramfs
iso9660
ntfs
nodev mqueue
nodev usbfs
hmm, no vfat
reflex pindar # cat /etc/filesystems
# /etc/filesystems
#
# This file defines the filesystems search order used
by a
# 'mount -t auto' command.
#
# Uncomment the following line if your modular kernel
has vfat
# support and you want mount to try vfat.
#vfat
aha!
Well, I removed the comment but nothing changed. I'll
try etc-update...nope
oh, wait, it says to use -t auto...nope. OK, that's
all I got.
And are you sure that /usr/src/linux/.config belongs
to the kernel you
actualy run?
no alternatives
It would not hurt to modprobe, anyway. ;-)
FATAL: Module vfat not found. naturally
--
No virus found in this outgoing message.
Checked by "grep -i virus $MESSAGE"
OK. I haven't followed this thread letter by letter but noticed
something that I ran into after I did my gcc upgrade a bit ago. I
upgraded my kernel but it did NOT make my modules. I went back and did
a make modules && make modules_install and they were there then. May be
worth a try since you are using modules for this. Me, I compile
everything but my temp sensors *in* the kernel.
Another command that may help shead some light:
[EMAIL PROTECTED] / # modprobe -l
/lib/modules/2.6.14-gentoo-r2/kernel/drivers/hwmon/w83627hf.ko
/lib/modules/2.6.14-gentoo-r2/kernel/drivers/hwmon/hwmon-vid.ko
/lib/modules/2.6.14-gentoo-r2/kernel/drivers/i2c/busses/i2c-isa.ko
/lib/modules/2.6.14-gentoo-r2/video/nvidia.ko
[EMAIL PROTECTED] / #
It lists what is available even if it is not loaded up yet.
Dale
:-)
--
To err is human, I'm most certainly human.
I have four rigs:
1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two
80GB hard drives.
2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB
drive.
4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB
SCSI drive.
All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.
--
gentoo-user@gentoo.org mailing list
