Upgraded kernel (2.4.14) won't mount vfat partitoins!
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Upgraded kernel (2.4.14) won't mount vfat partitoins!
Upgraded kernel (2.4.14) won't mount vfat partitoins!
Compiled and installed new kernel 2.4.14 for my SuSE 7.0.
With the new kernel, I can't mount FAT32 partitions. I get an error
"/dev/hdaX has a wrong major or minor number".
I am not sure what that means.
Facts:
1. During the configuration (xconfig), I took enough care to select vfat as one of the mountable partitions.
2. New kernel can mount ext2 partitions.
3. If I boot using the old kernel, it mounts just fine.
4. Major and minor numbers of this partition are correct (3,1).
As a prerequisite, I tried
#mount /dev/hdaX -t vfat /abc
#chmod 777 /dev/hdaX
but no success.
I see this message posted on many boards, but wasn't lucky enough to get an answer.
i know it's not a solution as such, but you'd perhaps be better off using the configuration from your existing kernel and build the new one. you should have /boot/config-2.4.3 or something similar, load that in xconfig and then change anything after that, more chance of things working nicely.
you did install the modules aswell as making the bzImage?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.