Porteus-v4.0 booting bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 booting bug reports

Post#1 by Ed_P » 10 Aug 2018, 15:25

Code: Select all

guest@porteus:~$ ls /mnt/sda1
EFI/
guest@porteus:~$ ls /mnt/sda1/EFI/
Boot/  Microsoft/  dell/  grub2win/
guest@porteus:~$ lsblk /mnt/sda1
lsblk: /mnt/sda1: not a block device

guest@porteus:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
 :
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   500M  0 part /mnt/sda1
├─sda2   8:2    0   128M  0 part 
├─sda3   8:3    0   213G  0 part /mnt/sda3
├─sda4   8:4    0   512M  0 part /mnt/sda4
├─sda5   8:5    0  10.5G  0 part /mnt/sda5
├─sda6   8:6    0   250G  0 part /mnt/sda6
├─sda7   8:7    0   250G  0 part /mnt/sda7
└─sda8   8:8    0 167.6G  0 part /mnt/sda8
guest@porteus:~$ 
Grub2 shows it as:

Code: Select all

Boot drive: hd1,gpt1
GParted shows it as:

Code: Select all

Partition  Name                  File System  Mount Point  Label  Size        Used       Unused      Flags
/dev/sda1  EFI system partition  fat32        /mnt/sda1    ESP    500.00 MiB  41.73 MiB  458.27 MiB  boot, esp 
porteus.cfg

Code: Select all

LABEL hd
MENU LABEL Boot from the first hd
COM32 chain.c32
APPEND hd0 1
TEXT HELP
    Don't start Porteus at all, but
    rather run any operating system
    installed on the first partition
    of the hard drive
ENDTEXT
APPEND hd0 0 didn't work either. :wall:
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#2 by Ed_P » 11 Aug 2018, 03:09

APPEND hd0 1 (And hd0 2 and hd0 3 and hd1 1)

Code: Select all

Warning: No MBR magic, treating disk as raw
ERR: Unable to find the requested disk / partition combination.
boot:
APPEND hd0 0

Code: Select all

Warning: No MBR magic, treating disk as raw
Booting...
ERR: Chainboot failed!
boot:
Each case results in the Porteus menu reappearing.
:wall:

Who maintains porteus.cfg? :unknown:
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Porteus-v4.0 bug reports

Post#3 by brokenman » 12 Aug 2018, 12:44

This chain booting was created long before UEFI was introduced. Perhaps it should be removed from the menu. I will need to take a look at how syslinux can chain boot currently.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#4 by Ed_P » 12 Aug 2018, 14:11

Maybe grub2...

-or-

Syslinux vs 6.+

https://docs.slackware.com/howtos:slack ... d_hardware
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 6104
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v4 all desktops
Location: Brazil
Contact:

Porteus-v4.0 bug reports

Post#5 by brokenman » 12 Aug 2018, 22:05

We are using syslinux 6+ now and the link you gave is how we are using syslinux for UEFI. The problem is the chain booting files which probably only chain successfully to older BIOS systems. The menu item boot from 1st hard drive now needs to detect if the drive is UEFI which I think is beyond the chain booter supplied.
How do i become super user?
Wear your underpants on the outside and put on a cape.

raja
Shogun
Shogun
Posts: 215
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Porteus-v4.0 bug reports

Post#6 by raja » 13 Aug 2018, 08:57

I boot following from a single USB disk with syslinux boot information. But have boot and efi directories. Boot directory has grub.

Grub Menu:

Code: Select all

menuentry "Porteus" {
    set gfxpayload=keep  
    linux /boot/vmlinuz-4.18-rc3 ipv6.disable=1 
    initrd /boot/intel-ucode.img /boot/initrd.xz
}


menuentry "Nemisis-New" {
     set gfxpayload=keep
     linux /boot/vmlinuz-4.16.14 ipv6.disable=1 nomagic norootcopy
     initrd     /boot/intel-ucode.img /boot/initrd-n.xz 
}
    
    
menuentry "Ubuntu - Deepin" {
    set gfxpayload=keep
    linux   /live/vmlinuz boot=live  username=live    
    initrd  /live/intel-ucode.img /live/initrd.img
}

    
menuentry "Porteus-4.0" {
    set gfxpayload=keep  
    linux /boot/vmlinuz-4.16.8 ipv6.disable=1 nomagic norootcopy 
    initrd /boot/intel-ucode.cpio /boot/initrd-4.0.xz 
} 


    menuentry "Windows" {
    search --fs-uuid --no-floppy --set=root B6BA-0F02
    chainloader (${root})/EFI/Microsoft/Boot/bootmgfw.efi
}
       
All of them boot smoothly, including Windows 10. Windows(ntfs) and Porteus(all in ext4) OS are in the Hard disk. Ubuntu live is in USB boot disk (FAT32)
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#7 by Ed_P » 14 Aug 2018, 02:54

raja, I'm confused. How does syslinux invoke the grub system? :%) Or are you saying the USB drive boots directly to grub, or is that grub2, rather than syslinux?
Ed

raja
Shogun
Shogun
Posts: 215
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Porteus-v4.0 bug reports

Post#8 by raja » 14 Aug 2018, 10:34

Ed_P,

You can experiment..rename Porteus written boot folder with a -p. Copy [BOOT],boot,efi folders from one of neko's isos.

The boot directory will have a grub directory with , x86_64.efi, efiboot.img and grub.cfg. folder/files.

Edit your grub menu, off you go.

I use the same USB disk to boot 6 different 32 bit OSs , after renaming boot folders. (efi boot with -g, and removing -p from porteus boot folder.

Here menu entry is in porteus.cfg. My old legacy BIOS Laptop boots all OSs.

USB was written by UUI app. from a 32 bit tails ISO. Tails use isolinux instead of syslinux. isolinux uses ISO9660(Cd image )

Hope to see a big smile from you!!!
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#9 by Ed_P » 14 Aug 2018, 16:44

raja wrote:
14 Aug 2018, 10:34
You can experiment..rename Porteus written boot folder with a -p.
"-p" :%) Don't understand. https://linux.die.net/man/1/mv
Copy [BOOT],boot,efi folders from one of neko's isos.

The boot directory will have a grub directory with , x86_64.efi, efiboot.img and grub.cfg. folder/files.

Edit your grub menu, off you go.
An interesting approach. My Windows 10 systems use Grub2Win so I copy the EFI and grub2 files from it to the USB drive.

In the past with this approach I would end up with two menus, one which is used with EFI systems and one for BIOS systems. This was when brokenman was using rEFInd for Porteus. Does your grub2 menu invoke the porteus.cfg menu?
I use the same USB disk to boot 6 different 32 bit OSs , after renaming boot folders. (efi boot with -g, and removing -p from porteus boot folder.
I boot multiple systems also but I boot them as ISOs.
Hope to see a big smile from you!!!
:D
Ed

raja
Shogun
Shogun
Posts: 215
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32 and v5.0-rc1-zstd-64
Location: Chennai,India

Porteus-v4.0 bug reports

Post#10 by raja » 16 Aug 2018, 10:21

Does your grub2 menu invoke the porteus.cfg menu?
No.

Forget my bla.bla on renaming. Superfluous.
Linux Kernel-4.4.120-32 bit; Linux kernel-5.2-64 bit.

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#11 by Ed_P » 16 Aug 2018, 14:13

I've got one menuentry to boot to the porteus.cfg file.

Code: Select all

menuentry " Porteus 4.0 USB - EFI" --class slackware   --class icon-porteus  {
     set bootmgr=/EFI/boot/bootx64.efi
     search -f  $bootmgr --set=root
     chainloader $bootmgr
     }

menuentry " Porteus 4.0 USB syslinux" --class slackware --class icon-porteus {
     set bootmgr=/boot/syslinux/isolinux.bin
     search -f  $bootmgr --set=root
     chainloader $bootmgr
     }
The EFI one works but not the syslinux one. I'm not sure if it's the wrong bootmgr file or the fact I'm testing this on an EFI notebook. :hmmm:


Booting directly to a Porteus type is straight forward.

Code: Select all

menuentry " Porteus 4.0 USB - AF'" --class slackware   --class icon-porteus  {
     
     set porteus_parms="volume=33 reboot=cold extramod=/Modules;/Modsavedat noload=save.dat;cinnamon"

     search -f /boot/syslinux/vmlinuz --set=root
     if [ $? = 0 ]; then
        linux  /boot/syslinux/vmlinuz $porteus_parms
        initrd /boot/syslinux/initrd.xz
     else
        echo USB drive not found.
        echo
        sleep -v -i 20
     fi
     }
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 bug reports

Post#12 by Ed_P » 16 Aug 2018, 23:15

An option to reboot would be a nice addition to the porteus.cfg menu. I tried this but it didn't work.

Code: Select all

LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
# https://www.rodsbooks.com/efi-bootloaders/syslinux.html
TEXT HELP
    Don't start Porteus at all, rather reboot
ENDTEXT
I added reboot.c32 from https://www.rodsbooks.com/efi-bootloaders/syslinux.html.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 5509
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

Porteus-v4.0 booting bug reports

Post#13 by Ed_P » 17 Aug 2018, 02:37

Above posts split from Porteus-v4.0 bug reports.
Ed

Post Reply