Yesterday, out of the blue my laptop running Mandrake 7.2,
kernel-2.2.17-21mdk decided it would no longer support vfat. It had been
working fine before and I have done nothing to my system but it would just
refuse to recognize vfat.
I decided to take the opportunity to download and build the 2.4.0 kernel
(with supermount patch - which works!). I did and all went well, no errors.
I installed it and booted it up. That was fine too but during the bootup, it
kept saying that vfat filesystem was not supported by kernel. I selected
support for both fat and vfat during xconfiguration, damnit! It DOES support
vfat. I tried again and double-checked that I selected fat and vfat support.
SAME THING HAPPENED.
After booting, if I run "depmod -a" I get a huge list of "unresolved symbol"
garbage, almost all of it having to do with filesystems, including fat and
vfat. What the fuh? How can the kernel have problems with its own frickin'
modules? They were included in the source and built with that source, not
any other kernel, yet it has problems with unresolved symbols?(There were NO
error messages during compile).
What is wrong here? I tried deleting my System.map link, which had been
linked to System.map-2.2.17-21mdk and linking it to System.map-2.4.0-1 and
rebooting but the same problems arise. What does one have to do to make the
2.4.0 kernel accept and understand its own modules?
--
Against stupidity, the gods themselves contend in vain.
-------------------------------------------------------
--
Against stupidity, the gods themselves contend in vain.
