View previous topic :: View next topic |
Author |
Message |
The Public n00b
Joined: 14 Dec 2003 Posts: 25 Location: Troy, NY
|
Posted: Sat Jan 17, 2004 3:01 pm Post subject: vfat support |
|
|
I'm trying to use a Lexar JumpDrive. I enabled vfat in make menuconfig and recompiled. I edited my fstab file. I created a JumpDrive file in /mnt/ .
When I try to mount, however, I keep getting an error saying that vfat is not supported by the kernel. I checked the .config file, and I have VFAT set there.
Where might my error be?
Thanks. _________________ Form is emptiness, emptiness is form. |
|
Back to top |
|
|
Helena Veteran
Joined: 02 Apr 2003 Posts: 1114 Location: Den Dolder, The Netherlands
|
Posted: Sat Jan 17, 2004 3:06 pm Post subject: Re: vfat support |
|
|
The Public wrote: | I'm trying to use a Lexar JumpDrive. I enabled vfat in make menuconfig and recompiled. I edited my fstab file. I created a JumpDrive file in /mnt/ .
When I try to mount, however, I keep getting an error saying that vfat is not supported by the kernel. I checked the .config file, and I have VFAT set there.
Where might my error be?
Thanks. | Unless you're able to provide more exact info (e.g. the exact error messages) I suspect that something still went wrong with the kernel. Maybe you compiled it as a module? You can find out with the following commands Code: | cd /usr/src/linux
grep -i 'vfat' .config | If you're using a 2.6 kernel replace the first command with Code: | cd /usr/src/linux-beta |
|
|
Back to top |
|
|
The Public n00b
Joined: 14 Dec 2003 Posts: 25 Location: Troy, NY
|
Posted: Sat Jan 17, 2004 3:17 pm Post subject: |
|
|
The line that I added in fstab:
Code: |
/dev/sda1 /mnt/JumpDrive vfat noauto,user,rw,unhide 0 0 |
My various commands to try and get the drive to mount:
Code: |
mount /dev/sda1 /mnt/JumpDrive /*this was before I changed fstab*/
mount -t vfat /dev/sda1 /mnt/JumpDrive
/*before changing fstab and without drive plugged in*/
mount /mnt/JumpDrive /*after modifying fstab*/
|
And this is the error I got, and still get
Code: |
mount: fs type vfat not supported by kernel
|
when I did the grep command as suggested above, I received:
_________________ Form is emptiness, emptiness is form. |
|
Back to top |
|
|
Helena Veteran
Joined: 02 Apr 2003 Posts: 1114 Location: Den Dolder, The Netherlands
|
Posted: Sat Jan 17, 2004 5:21 pm Post subject: |
|
|
/dev/sda1 ? I forget, but where does that come from again? What kind of drive is it, anyway? I mean, USB or IEEE-1394 or... |
|
Back to top |
|
|
mike4148 l33t
Joined: 09 Sep 2003 Posts: 641
|
Posted: Sat Jan 17, 2004 7:22 pm Post subject: |
|
|
Are you sure that you're running the kernel whose .config you're looking at? Post the output of
Code: | cat /proc/filesystems |
|
|
Back to top |
|
|
frekiR n00b
Joined: 15 Dec 2003 Posts: 42 Location: Sweden
|
Posted: Sat Jan 17, 2004 7:52 pm Post subject: |
|
|
Helena wrote: | /dev/sda1 ? I forget, but where does that come from again? What kind of drive is it, anyway? I mean, USB or IEEE-1394 or... |
sda is scsi |
|
Back to top |
|
|
The Public n00b
Joined: 14 Dec 2003 Posts: 25 Location: Troy, NY
|
Posted: Sun Jan 18, 2004 4:05 pm Post subject: |
|
|
cat /proc/filesystems yields the following:
Code: |
nodev rootfs
nodev bdev
nodev proc
nodev sockfs
nodev futexfs
nodev tmpfs
nodev shm
nodev pipefs
nodev binfmt_misc
ext2
nodev ramfs
iso9660
nodev devfs
nodev nfs
nodev smbfs
nodev supermount
nodev autofs
reiserfs
nodev pcihpfs
|
I only have one kernel on my system (as far as I know), so how could my .config not be the right one? _________________ Form is emptiness, emptiness is form. |
|
Back to top |
|
|
mike4148 l33t
Joined: 09 Sep 2003 Posts: 641
|
Posted: Sun Jan 18, 2004 6:13 pm Post subject: |
|
|
How did you configure your kernel? This just doesn't make any sense....
What kernel sources are you using (including version)?
Just to be sure:
1. You did use some interface (genkernel --config, make menuconfig, make x/gconfig, make config) to configure the kernel instead of just manually editing the .config file?
2. You then built the kernel, installed it properly (i.e., mounted /boot and copied the bzImage over), and are currently running it after a reboot?
Given that neither msdos nor vfat shows up in your /proc/filesystems, this is definitely not a problem with the USB drive. |
|
Back to top |
|
|
The Public n00b
Joined: 14 Dec 2003 Posts: 25 Location: Troy, NY
|
Posted: Sun Jan 18, 2004 7:38 pm Post subject: |
|
|
I'm using gentoo sources 2.4.20 r6.
I did this:
Code: |
# cd /usr/src/linux
# cp .config ~/.config
# make mrproper
# mv ~/.config .config
# make menuconfig
# make dep
# make bzImage
# make modules
# make modules_install
# cp arch/i386/boot/bzImage /boot/kernel-2.4.20-gentoo-r6
# cp System.map /boot/System.map-2.4.20-gentoo-r6
|
I noticed that you mentioned to mount /boot before copying the bzImage over. Is this where I went wrong? _________________ Form is emptiness, emptiness is form. |
|
Back to top |
|
|
Helena Veteran
Joined: 02 Apr 2003 Posts: 1114 Location: Den Dolder, The Netherlands
|
Posted: Sun Jan 18, 2004 8:49 pm Post subject: |
|
|
The Public wrote: | I'm using gentoo sources 2.4.20 r6.
I did this:
Code: |
# cd /usr/src/linux
# cp .config ~/.config
# make mrproper
# mv ~/.config .config
# make menuconfig
# make dep
# make bzImage
# make modules
# make modules_install
# cp arch/i386/boot/bzImage /boot/kernel-2.4.20-gentoo-r6
# cp System.map /boot/System.map-2.4.20-gentoo-r6
|
I noticed that you mentioned to mount /boot before copying the bzImage over. Is this where I went wrong? | That could very well be. You may want to compare the date&time of the kernel config to the bzImage you're loading in /boot. If you reverse the order or forget to mount, the bzImage will be copied to an "alternative" /boot directory! It happened to me several times too, which is why I decided at some point to remove the "noauto" option from fstab... |
|
Back to top |
|
|
|