Has anyone else gotten either kernel 2.6.16-rc1 or rc2 successfully working? I haven't been able to get either one going. I forgot what the problem was with the first one for sure, but just spend several hours trying to massage -rc2 into working, without success.
-rc2 compiles and boots, but without a working keyboard driver! What's strange is that the standard driver, atkbd, is and has been dependent on !x86-pc for some time (it is in .15, anyway, which works), but only with .16 is there now an x86-pc config option enabled to kill it (there wasn't in .15), which it does -- the option disappears from menuconfig entirely! However, hacking Kconfig to get the atkbd option back and enable it does nothing! The driver does get compiled and I can see all 54 atkbd entries in the .15 systemmap in .16's as well, so it's there, but the thing simply won't work! As I said, the x86-pc config option is new to .16. It's a sub-arch choice, the only other one being Intel emt64 specific. While I have an AMD Opteron, not an Intel, I thought I'd try it. It doesn't seem to have much effect. The atkbd driver still won't work! (The emt64 thing probably just causes a bit of extra code bloat on AMD, with code that isn't ever run, would be my guess. Regardless, it does remove the blocker on the atkbd config option and allow me to choose it, but doing so doesn't result in a working driver, unfortunately.) I thought it might be related to the fact that I was compiling it with the latest (0210) gcc-4.1 snapshot, so I reverted to 4.0.2, but that didn't solve the issue either, and I suspect it's something bigger, having to do with the disappeared driver option in the config, in any case. The worst of the problem is that of course every single time I test it, it's a double-reboot, once to the kernel that STILL won't work, then back to a working kernel to try something else, or now, to give up for awhile and post this question seeing whether others on amd64 and running the kernel.org -rcs, or trying to, have come across the problem or know anything about it. Fortunately, I /can/ shut down gracefully, because altho the keyboard's locked, I have one of the triple-click commands on gpm set to init 0, and the mouse works just fine and executes the triple-click to shutdown safely. One can't get very far, particularly at an unlogged-in VT, with only a mouse, however, and no keyboard to login or do anything besides the three triple-click commands available on the mouse! It comes up so I can look at it, and I can shut down, but that's about it, and that's just enough to get good and frustrated at the login proompt you can see but not touch! =8^( I'll do a google on it and check kernel bugs as well, but haven't yet. Just wondering if anyone else has run into it, and already knows a solution, or at least can confirm that it's not just me! -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
