Michael Mol wrote:
Play with your BIOS settings. Look for things like legacy USB support. Also, double-check that all the relevant USB drivers (UHCI, EHCI, XHCI, HID, etc) are either built-into the kernel, or are loaded as modules. Consider rebuilding your kernel. Just because one processor has a superset of the instructions of the other doesn't mean there may not be other compatibilities. Some time back, a thread on here discussed how to find out what -march=native becomes, in terms of -march and a bunch of other parameters. I've noticed parameters like cache line sizes and cache sizes, among a couple others. I imagine a bungling of, e.g., cache line sizes could break code that has heavy dependency on data locality and/or memory models; it might have broken your USB drivers, for example. But, really, I think BIOS settings and driver presence are the more likely culprit.
Here it is: gcc -Q --help=target -march=native I agree tho that checking those BIOS setting is a good start. If that fails, boot a CD or something, chroot in, do a emerge -e system. Maybe make some corrections to the kernel then try booting. Oh, I'd rebuild the input drivers to, mouse and keyboard. Check the USE flags too. I'm not sure what all options they have. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
