> this was a bug i reported back a few versions as well -- and i don't think> i received any responses (nor from the maintainer).> > i've got a box on which 2.4.x works fine, but 2.6.0-test2 gets into a snit> when it's trying to initialize the i8042. i can get 2.6.0-test2 to boot> if i add "i8042_nomux".> > the mux initialization code seems kind of ... wonk -- it seems to write> values to the registers then read back and if the value is the same then> it assumes the mux is there. that seems way too likely to be broken in> situations when the mux isn't there... it'd be better to be looking for> some value which is different after writing.

No, it writes f0, 56, a4 and if it gets f0, 56, and not a4, then it assumesthere is a mux.