If radeonfb is completely nonexistent in dmesg, it's not even seeing your card. If you're willing to get... 'experimental' with your kernel sources, then you can try the following (can't guarantee anything, though):
You need sysfsutils installed. (you're going to need both 'lspci', which is standard, and 'lsbus' which is in sysfsutils)
First of all, do an 'lspci -v' and find your video card. Note its pci number (the very first number before the device name. For example, my M9 gives "01:00.0").
Now, do an 'lsbus pci'. It'll give a list of devices, with pci devices like the ones from lspci. (except that they're prefixed with some extra zeroes) Find the entry that matches the pci bus from lspci. So, for example, to match mine, I would dig out the entry that looks like this:
0000:01:00.0: 1002:4c66
Those last 4 digits are your card's pci id. Now, you want to edit the kernel include "/usr/src/linux[-whatever-version]/include/linux/pci_ids.h". You'll see a whole bunch of defines, so scan down until you find the radeon section. First, check if your card is there, but I doubt it is. (Your sig says you have an M10 and I don't see it listed in my sources at the moment)
Technically, you should add a new define, but that requires adding it into a bunch of other source files, too. As a really messy and temporary hack, it's easier to just "hijack" one of the other defines and change its pci id. The card may be recognized with an incorrect name, but the device should still be found according to the pci id. So anyway, find the define that most closely matches your card (in your case, probably the M9), and change its id. Using my id as an example again, I'd find some card's define, and change it from 0x???? to 0x4c66. Just append "0x" to the beginning of the four digits you got from lsbus.
Recompile and try that kernel. It _might_ work, I really can't say - but that's how I hacked up the sources to recognize my M9, way back before it was supported natively in the kernel sources.
Huh, that's weird. My multimedia buttons don't send any X events at all. Maybe it's because I'm using an experimental version of x. But lineak still works fine, I'm just using the same codes that I got a long time ago.
Well, since the ati driver is a kernel module, unless you're using experimental module versioning support in the kernel, you're going to have to recompile it for each new kernel you use.
I will disable the highmem pagefile thing and see what happens. As for the multimedia keys, I've tried lineakd too and it locked up the input as well due to the Fn keys, etc. What keyboard are you using under lineakd?
