[Solved] Upgrade 13.37 to 14.0 got stuck on reboot

[mimosa]

I don't think the connecting / disconnecting strategy will work, because it changes the UUIDs of the partitions. So when another disk is connected, the first one won't boot any more.

[jpg153]

Yes,

something like that happened already ... years ago.
At that time I found a tweak with hints from Shador. I think I replaced UUIDs by....

Let's see!

[mimosa]

As luck would have it I find myself in a somewhat similar situation, with no Live handy. I was able to use the install disk (on USB actually) as a rescue system quite easily by chrooting into one of the existing Salix installations and running lilo from there. First mount the target partition somewhere and do the following:

Code: Select all

mount --bind dev salix/dev
mount --bind proc salix/proc # not sure whether this is necessary for this task

then

Code: Select all

chroot salix
vim etc/lilo.conf # edit judiciously, bearing in mind all you need for now is to boot this one Salix installation
lilo -v

.... reboot.

I just did this and it worked (in fact I got the disks the wrong way round and just swapped over the cables rather than repeating the procedure); then I ran lilosetup within Salix. You may prefer grub.

[jpg153]

Well,

I managed with

Code: Select all

huge.s root=/dev/sdb1 rdinit= ro

to get onto my old system.
First I received various errors from Xorg, as I used the proprietary Nvidia driver before but its not working.
So I finally removed xorg.conf completely (all which were present).
So now I come to the graphical login, but then again no mouse, no keyboard.
Do I need to specify mouse and keyboard in a new xorg.conf?

My hope is to get in my old system and fix it from there...

[gapan]

Why huge.s? Why not the smp kernel? The problem you're having with no mouse/keyboard is probably because you don't have the non-smp kernel modules installed, you only have the smp kernel modules installed.

[jpg153]

Well,

that was what I found on my 13.37 system before I followed the upgrade instruction...and what is stated on the prompt when booting
from the installtion CD.

Should I do something different then?

Or would it be safe to make a fresh install from CD instead?

Although I would loose some apps and settings...

[gapan]

Assuming you have an ssh server running, you can connect from another pc in your network and install the kernel-modules package.

Or, you could boot the hugesmp.s kernel, assuming that and the respective modules are installed.

Or, chroot from another system on the same pc (live CD/installation CD will do) and do either one.

[jpg153]

Well,

thanks for all the proposals.

But I am a bit fed up and just making a backup of my /home files.
Then I will completey redesign my partitions and start from a fresh install and likely will give it atry with a multilib environment or so.
The chroot into Salix32 was probably a technical piece of cake, but I had to use it for just Softmaker-Office with some downsides as well (poor integration - not opening files by doubleclick).
So maybe a multilib is the easier way...

Thanks anyway.

[aurlaent]

You can get files opening by doubleclick using the switch32 script and custom .desktop files.

[jpg153]

I could never get that to work...the switch script was ok but then....

What is behind the .desktop files?