• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

trouble mounting my fat32 partition after kernel upgrade

CTho9305

Elite Member
I'm running RedHat 7.0 for the past few hours (gave up on Slackware - driver trouble)... and I needed a bzImage for LOADLIN (I dont want to deal with LILO's limit... I just noticed the LBA32 option - does that remove the limit??) and I couldn't find one. I didn't have my current (2.2.16) version's complete source, so I went ahead and got 2.4.0 and it compiled fine (lots of warnings, but otherwise fine). All is well, except now I can't mount my fat32 partition like I could before due to a bad "major or minor number" or something like that. What does that mean / how do I fix it?

thx
 
Huh, slack and driver problems? you sure it wasn't your problem? as in this case.Anyway onto the question,first of all read the Changes under /usr/src/linux/Documentation you'll need to have all the required utils updated in order to use 2.4.0.Most notably modutils package because 2.4.0 introduced new modules scheme and may cause some problems.Next when you configured the kernel have you choosen fat support either build right in the kernel (Y) or module (M)?You seem not to have it.Simply rerun your kernel config and include it (found under filesystems).Compile the kernel and make sure to make modules;make modules_install.Hope this helps.
 
Make sure you specify the parition number when you mount. You get that error if you don't. ie. mount -t vfat /dev/hdax /mnt
 
Back
Top