Maybe: Your kernel is using modules for the 'old' mobo and cpu. While booting, auto-hardware-detect changes the settings for another mobo, but it's not installed so the modules are not found.
If that's more or less right, you can try to recompile your kernel ? Steven (just a wild guess... But I think it makes sense) On Mon, 2003-06-09 at 16:07, Praedor Tempus wrote: > I recently picked up an Athlon XP2700+ to replace my > Duron 1100. The switch went fine except my [EMAIL PROTECTED] mobo > apparently doesn't support anything greater than an > XP1500+. It is an MSI KT333 ultra and the manual says > it can do a 200MHz FSB, etc, which would support the > chip but...in any case, this is true, it seems, only > with windoze when using a special MSI-supplied > application for "overclocking". > I downloaded the latest bios upgrade for this mobo > thinking/hoping it would add support for XP2000 and > higher chips but. After upgrading the bios, Windoze > ME still fires up just fine but Linux is hosed. I can > boot up in failsafe mode and from there start up > graphics and networking just fine as root. If I try > to login from failsafe as a user, if fails to start > XFree. This isn't the main problem at this point, > however. The primary problem is if I try to startup > linux via a normal kernel and graphical startup, I get > a screen full of error messages having to do with > "unable to touch /var/lock/subsys/<whatever> no such > file or directory" and I also get an error message > about being unable to mount most of my partitions > because their /dev/hd* entries do not exist. > Ultimately, the bootup fails when the system gets to > the point of trying to start the system logger, at > which point it just sits for a long time and then the > screen goes blank and that's it. > Why would I be able to start up just fine, graphics > and all, all my partitions, all my /var/lock/... > files, etc, from failsafe all the way to graphics (but > only for root) but not be able to do the same from a > normal bootup? How do I go about fixing this? > Since I can get in as root via failsafe I am not yet > ready to try reinstalling and feel that the system > MUST be salvagable, but where to start? And why would > a bios upgrade do this in such an odd manner, > affecting only the graphical bootup but leaving the > failsafe bootup (to graphics) intact? > > praedor > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com > > > ______________________________________________________________________ > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
