Apparent freeze during installation of system.

You have a problem with Salix? Post here and we'll do what we can to help.
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: Apparent freeze during installation of system.

Post by mimosa »

Try just appending

Code: Select all

root=/dev/sdXY rdinit= ro
where XY is the correct device letter and partition number for your Salix. That ought to do it, but because I have a more recent kernel, it doesn't boot successfully here, so it is hard to be sure.

Incidentally, I do think laprjns is probably right that you don't actually need to bother with the initrd or UUID. The fact that (if I have understood correctly) your Devuan and Salix are ordering the devices differently after boot shouldn't make any difference to booting itself, as long as you don't move the drives around again.

If you continue to have difficulty booting your Salix from the USB, it would probably be worth pursuing this option, because then all you would need to do is install the correctly configured bootloader (without UUID) from Devuan. You could forget about both the USB booting and the initrd.

Code: Select all

If I boot from Devuan, the target disk is /dev/sdd
So that is what your lilo.conf should point to in the Salix stanza. You can retain the UUID for Devuan. Remember to ensure the kernel is currently mounted on the path given in the image line.
User avatar
laprjns
Salix Warrior
Posts: 1105
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Apparent freeze during installation of system.

Post by laprjns »

mimosa wrote:laprjns, are you sure he needs to install the generic kernel? My understanding is an initrd will work with huge if created for it, just would not normally be needed.
I did think about that and no I'm not sure that it will not work with kernel-huge. The OP could give it a try.
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

mimosa wrote:Try just appending

Code: Select all

root=/dev/sdXY rdinit= ro
where XY is the correct device letter and partition number for your Salix. That ought to do it, but because I have a more recent kernel, it doesn't boot successfully here, so it is hard to be sure.
It seems that I have reached an impasse. I tried appending

Code: Select all

root=/dev/sdXY rdinit= ro
after pressing TAB and getting a boot loader prompt ">", but the installer still loads, with nothing else happening. I tried downloading and burning slackware64-14.2-install-dvd.iso to a USB pen drive. Upon booting the Slackware DVD, I get the "boot:" prompt that I have been expecting on Salix as well, but when I tried:

Code: Select all

hugesmp.s root=/dev/sdX1 rdinit= ro
I got an error stating that a kernel couldn't be found. I tried both /dev/sdc1 and /dev/sde1.

Code: Select all

root=/dev/sdX1 rdinit= ro
Gave me the same error.
----
Regarding initrd, if you go to https://docs.slackware.com/slackware:beginners_guide and go down to the last line of the green highlighted section, it states:
For now, you need to remember that a “huge” kernel will not support an intial RAM disk, but the “generic” kernel will...
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
laprjns
Salix Warrior
Posts: 1105
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Apparent freeze during installation of system.

Post by laprjns »

Can you please boot into Devuan and post here the complete output of lsblk -f. Should look something like this:

Code: Select all

rich[~]$ lsblk -f
NAME    FSTYPE  LABEL                     UUID                                 MOUNTPOINT
sda     iso9660 Salix64 fluxbox 14.1beta1 2014-05-21-17-52-14-42               
├─sda1  vfat    ESP                       9037-2232                            /boot/efi
├─sda2  iso9660 Salix64 fluxbox 14.1beta1 2014-05-21-17-52-14-42               
├─sda3  ntfs    MSRP                      B00005150004E3E6                     
├─sda4  ntfs    Salix64 fluxbox 14.1beta1 60DCE13FDCE10FD8                     
├─sda5  swap    Salix64 fluxbox 14.1beta1 79ea5ca2-34a3-43ad-9461-000f30f58531 
├─sda6  ext4    Salix64 fluxbox 14.1beta1 1aacd13e-aeac-420e-90f2-5b4c31f334c2 
├─sda7  iso9660 Salix64 fluxbox 14.1beta1 2014-05-21-17-52-14-42               
├─sda8  ext4    OS-1                      2e53f119-efa6-40dd-b2df-1fba1296c03c /common_home
├─sda9  xfs     Salix                     fc97ac59-a196-402f-9c94-ad35d96ccd6b /
├─sda10 jfs     Salix64 fluxbox 14.1beta1 964e444d-c3e8-426c-a6d7-4b2d27889379 
└─sda12 ext4    Salix64 fluxbox 14.1beta1 d6e9d3d5-575a-4601-b0f0-c21742fff6c5 
Only you should have more devices listed, i.e sda, sdb,sdc, sdd, sde, etc)
Also, how many internal drives do have installed, how many external usb drives?
“Don’t you see that the whole aim of Newspeak is to narrow the range of thought?"
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

laprjns wrote:Can you please boot into Devuan and post here the complete output of lsblk -f.

Code: Select all

$ lsblk -f
NAME   FSTYPE LABEL UUID MOUNTPOINT
sda                      
├─sda1                   /
├─sda2                   
├─sda5                   [SWAP]
└─sda6                   /home
sdb                      
sdc                      
├─sdc1                   
└─sdc2                   
sdd                      
├─sdd1                   
├─sdd2                   
├─sdd5                   
└─sdd6                   
sde                      
└─sde1                   
sr0 
Everything is listed above except, if I am booting from a USB pen drive, which would typically be "sdf".
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

Interesting. I was successful at booting into my Salix system by using the slackware64-14.2-install-dvd.iso. Unfortunately neither (USB) keyboard nor mouse worked. It seems that things have moved on since the Salix documentation. "hugesmp.s" is no longer used. Instead "huge.s" should be used, but as I was following the Salix documentation exactly, rather than reading what was in front of my face, it wouldn't work. So the full phrase that worked was:

Code: Select all

huge.s root=/dev/sdc1 rdinit= ro
It would be nice to know why my USB devices or frozen...
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: Apparent freeze during installation of system.

Post by mimosa »

Please also post the output of
blkid
It doesn't work when booted with that kernel because it is the wrong one. Slackware is not the same as Salix.
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

mimosa wrote:Please also post the output of
blkid
It doesn't work when booted with that kernel because it is the wrong one. Slackware is not the same as Salix.
Ahh.

Code: Select all

$ sudo blkid
/dev/sda1: UUID="2e1478a0-3356-4ce7-9efe-f72cb7e85a2b" TYPE="ext4" PARTUUID="3e6b61ff-01"
/dev/sda5: UUID="f9bac0bb-cbde-4929-89f4-01fc00589209" TYPE="swap" PARTUUID="3e6b61ff-05"
/dev/sda6: UUID="9c6579ed-5dd5-43b3-b137-5e0e14661044" TYPE="ext4" PARTUUID="3e6b61ff-06"
/dev/sdc1: UUID="E6BCC326BCC2F05B" TYPE="ntfs" PARTUUID="00034d54-01"
/dev/sdc2: UUID="C03AC9203AC913F6" TYPE="ntfs" PARTUUID="00034d54-02"
/dev/sdd1: UUID="8624b400-0a3d-4e9d-92a2-56779e96260e" TYPE="ext4" PARTUUID="5d0c65f5-01"
/dev/sdd5: UUID="c79fdc90-d0cd-4797-9e62-5fe0591197d8" TYPE="swap" PARTUUID="5d0c65f5-05"
/dev/sdd6: UUID="3ff401b5-7069-45be-98e6-4a6ebb972c75" TYPE="ext4" PARTUUID="5d0c65f5-06"
/dev/sde1: UUID="155D414D7F808265" TYPE="ntfs" PARTUUID="0007fb19-01"
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

mimosa wrote:These are the instructions I meant, following laprjns:
https://docs.salixos.org/wiki/Boot_into ... llation_CD
The boot loader prompt is the one you want for those. # would be the tty after you boot.
The fundamental roadblock to running the mkinitrd_command_generator script and getting Lilo booting my Salix system, is still the inability to boot as described in the above Salix doc. I have tried using the boot loader prompt (after TAB) ">" with

Code: Select all

hugesmp.s root=/dev/sdc1 rdinit= ro
as well as

Code: Select all

root=/dev/sdc1 rdinit= ro
using both USB pen drives and burning to CD/DVD. No matter what I do, I end up with the Installer, rather than booting into my system.

Using a Slackware .iso on a USB pen drive, and "huge.s" instead of "hugesmp.s", I was able to boot into the system, but as the kernels aren't the same, this option is off the table, however, it is a proof of concept.

The only option appears to be to chroot into the system, which is not trivial - even for the average Linux user. If I am not the only one that is unable to follow the procedure in the Salix docs URL above, I would consider this to be a bug. Can anyone else confirm that the described boot procedure does not work?
Military justice is to justice what military music is to music. - Groucho Marx
User avatar
globetrotterdk
Posts: 435
Joined: 26. Oct 2010, 13:57
Location: Denmark

Re: Apparent freeze during installation of system.

Post by globetrotterdk »

I found this script and adapted it to try to simplify a chroot into my Salix system, to run the mkinitrd_command_generator script and get Lilo working. The question is if this will do what I need?

Code: Select all

#! /bin/sh

TARGET=/media/username/8624b400-0a3d-4e9d-92a2-56779e96260e
mount -o bind /proc $TARGET/proc
mount -o bind /sys $TARGET/sys
mount -o bind /dev $TARGET/dev
mount -o bind /tmp $TARGET/tmp
mount --bind /etc/resolv.conf $TARGET/etc/resolv.conf

chroot $TARGET /bin/bash -l
I am definitely out of my comfort zone, but still trying to find a solution.
Military justice is to justice what military music is to music. - Groucho Marx
Post Reply