SuSE 9.3 not booting after mobo/cpu upgrade
 

I upgraded my motherboard and CPU, and when I try to boot into SuSE I get this error message:

Waiting for device /dev/hdb1 to appear: .....not found -- exiting to /bin/sh
sh: can't access tty; job control turned off

I tried booting with the install disc, and this is what comes up on the screen when I attempt to start the x window system:
xauth: (stdin):1: bad "add" command line
xauth: (stdin):2: bad "add" command line
xauth: (stdin):3: bad "add" command line

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: SuSE Linux [Elf] SuSE
Current Operating System: Linux linux 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC 2005 i686
Before reporting problems check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 20 05:36:57 2005
(==) Using config file: "/etc/X11/xorg.conf"
(EE) No devices detected.

Fatal server error:
no screens found

Please consult the X.Org Foundation support
at http://wiki.X.Org
for help
Please also check the log file at "/var/log/Xorg.0.log" for server ":0.0"
after 0 requests (0 known proccesses) with 0 events remaining

I am guessing it is just having trouble because it thinks it has a different motherboard. Is there a way to have it re-detect the hardware?

u can't just simply upgrade u'r pc..the kernel might be not recognize what is happenning.if u upgrade from intel to amd..the is an error "kernel panic" it's mean the linux system does'nt know what type of hardware and etc...in your case maybe ur hardware can't support the os...or vice versa...: )

Is there a way to re-scan the hardware from the install disc?

if i'm correct
 

if i'm correct,once u boot from cd there's option for booting...(in this case i refer to suse)
1. automatic installing
2. manual installing
3. safe install

as u can see first option is auto which mean all the hardware scan is doing automatically with gui..the second option is where u cant search/scan ur hardware manually...or in other words command line..it's not fully command line actually..just a bit non gui...whereby useful to load all the optional driver and etc...not sure bout other's os..

Here's what happened. The chipset on the motherboard is different enough that the basic instruction set has been changed. This happens when break from the 800 series in intel to the 900. Or switching to a via chipset, or from via to intel. For AMDs, nforce 2 and 3 have different instruction sets, the vias all seem to be fairly compatible with each other, but you can't switch in and out, or to/from 64bit. Basically even the simplest of things cannot be run, because the basic instruction sets have changed from chipset to chipset. No OS, inclding all Windows versions, can handle that kind of swap. So doing a repair install, or in linux's case, recompiling the kernel, would fix it. But if it is too different, it takes a whole fresh install. You can re-scan the hardware though, it should be able to during a repair install, or from recovery console.

I was able to copy my important files to another partition and do a fresh install, but my modem and onboard audio don't work.