Hello,

Had a nicely tweaked Slack 10 install. But had a system repair this weekend that needed used parts, so i ripped out my board and chip and sold it (biostarM7viw and 1800+)

Ordered Soltek nforce 400 ultra based board and XP2500+. Slack begins to boot, goes throught boot process and at some point i loose screen, and it never makes it to the bash prompt. Same thing in mepis. Bluescreens in XP and 2000pro. I have redone XP setup as i make a living repairing pc's that are running windows, but i would love to have my slack install back w/out having to start from scratch.

Any ideas of how i might accomplish this?

Thanks and God Bless,
Boutros

It would help if you knew at which point it
blacks out/hangs. Also, how does it go if
you boot using "init 1" as parameter to lilo?


God bless,
Tink

It's been my experience that a major change like swapping the mobo is going to screw things up. A CPU is one thing, but a mobo, i think you're in for a fresh install. THe fact that even mepis won't boot is odd though. Have you tried the slack rescue disk (disk2) or even the install disk? How do you have things partitioned? Hopefully you can boot with a rescue disk, move all the file you want to keep to a different partition, reinstall, and then restore all the backup files.

I think you are correct. Saving the files i can is what i am in for. I can boot with a live cd save /home and just redo the rest. Certainly a fresh install is the best way to go but i remember in the 98se days. I could usually boot to safe mode pull all the hardware out of the device manager and hope for the best on reboot

I was hoping to try that here, but we'll see. Thanks for the input,
Boutros

Did you have a custom kernel configured for your previous motherboard chipsets/etc?
Booting with the generic stock kernel should work fine... You shouldn't have to re-install a-la windows at all.

The screen blanking out probably has something to do with the framebuffer. Try passing vga=normal to lilo at boot -- init 1 is also a good thing to try, as Tink suggested above.

When I did my processor and motherboard upgrade, everything went smoothly.. I went from a celeron 333 to an athlon 2400XP+... Different chipsets.. different ram.. different IDE controller.. everything. Booted the stock kernel fine, and from there I made a new kernel.

Try booting it with the install disk or rescue disk, chroot, and build a new kernel... Or put the stock 2.6 or 2.4 kernel on it.

Don't re-install unless you absolutely have to (And you shouldn't!)

--Shade

Well that was easy,

I just used slack disc #2 and at the boot prompt typed" bare.i root /dev/hda1" My slack install was then booted up and i was able to log-in. I shut down and tried to boot up again w/out the use of disc2. And i was able to boot into a working slack system. So all appears to be well.

Thanks,
Boutros