I've had the opposite happen, I've changed the MB in a computer that dual booted Debian Etch and Windows XP, and Etch kernel panicked on the way up, XP trundled along, the screen flashed a few times, and it managed to allow me to login.
After login, it continued to grind, then it said it was finished installing new hardware, and wanted me to reboot. When it was done rebooting, XP ran fine. I had to reinstall Etch.
Odd, considering you say this;
I've been using/administrating/developing Windows for about 20 years, and using/administrating Linux for about 10, and I have to say, other than exposing OS functionality through the filesystem, I have never found any real need for most of the stuff in your list with Windows.
That you didn't know you could just boot into a liveCD, chroot into the etch install, and reconfigure everything.
What part of Etch crashed? Just kernel panic, X die, what? I've switched hardware many times, and have never had such a problem. Generally if it crashes on a motherboard setup after a swap, then it just won't run on it at all (due to buggy hardware / driver or whatever) The fact that you were able to re-install on it says otherwise though. Could have just been a module option that was set that messed up on the new motherboard.
XP and pretty much all versions of Windows that have any sort of 'Plug and Play' have had the issue of either being completely unstable after a major hardware swap, or simply don't work.
One thing that could have messed up your Debian install was AHCI vs Legacy. AHCI has been kind of a harsh nail for all operating systems (for example, to get AHCI support in Windows at all you have to reinstall to use it, but for the most part it'll emulate the legacy mode, which Linux doesn't seem to like too much.)
Member since:
2006-01-10
After login, it continued to grind, then it said it was finished installing new hardware, and wanted me to reboot. When it was done rebooting, XP ran fine. I had to reinstall Etch.
Odd, considering you say this;
That you didn't know you could just boot into a liveCD, chroot into the etch install, and reconfigure everything.
What part of Etch crashed? Just kernel panic, X die, what? I've switched hardware many times, and have never had such a problem. Generally if it crashes on a motherboard setup after a swap, then it just won't run on it at all (due to buggy hardware / driver or whatever) The fact that you were able to re-install on it says otherwise though. Could have just been a module option that was set that messed up on the new motherboard.
XP and pretty much all versions of Windows that have any sort of 'Plug and Play' have had the issue of either being completely unstable after a major hardware swap, or simply don't work.
One thing that could have messed up your Debian install was AHCI vs Legacy. AHCI has been kind of a harsh nail for all operating systems (for example, to get AHCI support in Windows at all you have to reinstall to use it, but for the most part it'll emulate the legacy mode, which Linux doesn't seem to like too much.)