> i actually figured out what it was, and i feel somewhat ashamed by how i > didn't realize this in the first place. even though i compiled the > 2.4.19 kernel, i accidentally copied the 2.5.33 bzImage into my boot > directory, so everytime i thought i was loading 2.4.19 it was just > loading the 2.5. i fixed this and it works fine in 2.4.19. i'm really an > intelligent person, just not very perceptive.
Stick with the stable version of the kernel if you don't have a specific need for the unstable branch. This is even more important for people without the skills to track down problems in these unstable systems. I do have these skills, I have created kernel drivers, I provided fixes for other drivers, I can disassemble a kernel into a heap of bits and reassemble it - blindfolded - into a running system again (OK, now I'm exaggerating a bit :-), and I'm still running a 2.4.19 kernel. > > so this means that it doesn't work in 2.5. i don't know if this is up to > the kernel guys to fix or you guys to write compatible drivers (my own > knowledge of c++ is limited to pacman and artificially "intelligent" > othello) for it, but that's the scoop. in terms of my personal kernel > compilation i'm pretty sure i had all the necesarry modules et c. It's a kernel problem.
