Didn't mean to offend any of those die hard debianites... I meant 2.1r4 I'll crawl back into my little hole now. ;) I run a 2.4 on another laptop (sound support man) and it works just fine. I had the source laying around hence me building a 2.4; this being after I read about the patch for cache detection. I figured the patch had made it into the kernel tree by now but I didn't really investigate. assume==bad; I also wanted a 2.0 kernel (slink) just to see what it had to say. I at least got an error on that one. I wouldn't really put anything past Intel and if it were 1Ghz I'd bet on it being a funky cache. But this is 800Mhz so it should be stable enough. It seems to work just fine in BSD so it'll end up a FreeBSD machine which is fine but I'd still like to know why linux choked on it. Anyone ever hear of a BIOS causing a problem like this? I don't see how off hand but I guess it's possible. Thanks, Charlie --------------------------------------------------------------------- To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org For additional commands, e-mail: tclug-list-help at mn-linux.org