Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed Fedora Core 1 today (2.4.22-1.2115.nptl is the version identifier that appears on my GRUB boot screen) and am having a problem mounting floppies. The machine is dual boot with Windows, and Windows has no trouble with the drive or this particular floppy.
My /etc/fstab contains the entry:
/dev/fd0 /mnt/floppy auto defaults 0 0
However when I try to mount the floppy with:
mount /dev/fd0
I get:
mount: you must specify the filesystem type
Trying the following:
mount -t FOO /dev/fd0 /mnt/floppy
with FOO equal to 'msdos' or 'fat' also fails, but with:
Can anybody tell me what I've bungled? The other RH versions I've run (including RH8 and RH9 on this very machine) were all able to grok the floppy drive right off the bat. Has something changed in Fedora, or do I have something mangled here in either my config or my understanding?
So it does in fact appear that the kernel support is somehow missing. I've never had this happen after an install before.
For grins I looked at /lib/modules/2.4.22-1.2115.nptl/kernel/fs and found directories and *.o files corresponding to all the filesystem types I can think of, including vfat.o in the vfat subdirectory. So it appears that modules of the correct version are around, just never getting picked up by modprobe when I try to mount.
Any idea what's botched here that's stopping those from loading? Or the lowest impact way of fixing it? I could reinstall, I'm just not terribly confident I'll get a different result, and would ultimately like to have some better understanding of how I got myself in this state, or, failing that, how to get out of it... :-)
Distribution: Fedora, Debian, OpenSuSE and Android
Posts: 1,820
Rep:
I had that happen not more than a month or so ago. I'm not sure why the installation felt it was not important to have fat32 support in the kernel. A recompile fixed it in my case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.