Brian Henning wrote:
> Speculation:
> I've seen instances where there are different packages for i686 (Intel) versus athlon (AMD). It could be possible (couldn't it?) that your kernel is expecting an athlon-specific instruction set that won't work on an Intel machine.
Brian's statement is probably a good guess. Depending on the distro, and the choices you made when you setup the machine or during any kernel changes / recompiles, you very well may have an athlon-compiled kernel, which would exhibit similar problems to the behavior you are describing. In addition to simply trying the box on an athlon machine, you might look and see if you have another kernel choice at boot up, such as the original kernel installed with the machine, which *might* not be athlon specific. If all your choices are athlon-specific, it'll be easiest to find another athlon machine to at least temporarily boot it up in, and change to a generic kernel. It's possible to mount the disk in another box and change the kernel, but I wouldn't recommend it for the faint of heart, and you're likely to have other athlon packages that will bite you in the end, anyway.
Aaron S. Joyner -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
