No, it's actually fairly innocuous. I get it every time I boot, and nothing seems slow.
Note that the second part of the message you quoted is the action taken to deal with the problem. And, as far as I know, not using MMCONFIG just means that the PCI bus is configured by an alternative method.
Also, ntfs-3g works fine on my system. (AMD 2200, Gateway laptop, 2.6.19-1.2895 kernel)
There are two problems I just discovered with ntfs-3g on Fedora. The first is that Fedora is using the 2.6.2 fuse release, and some bug fixes in 2.6.3 make ntfs-3g more stable. (Look at http://www.ntfs-3g.org/, under the Fedora link, for details.) Compiling and installing 2.6.3 is quite painless if you follow the instructions in the documentation on the site.
The second problem, also detailed at the web site, is that SELinux does not recognize a file type name that contains a dash. Thus, if you have SELinux in any non-permissive mode, the ntfs-3g file system type will be rejected, any ntfs-3g will not work. If you do set SELinux to "permissive" mode, you will still get the audit messages that selinux denied access to the ntfs-3g file system, but you'll actually be able to use the driver.
Since SELinux is not in permissive mode by default, you need to go to the "Firewall" settings application and change it in order to get ntfs-3g to work on Fedora.
You say you've now got a kernel panic. Try removing, say, the linuxant
module to see if that fixes your problem. (If you need to use some "windows only" driver, look into ndiswrapper
. It's quite easy to use.)
Note: Adding the appropriate line to /etc/modeprobe.d/blacklist
is often the easiest way to temporarily keep a module from loading during the boot process.