UEFI problem

[brokenman]

I havn't tested running the script after booting from an ISO. You should run it from a regular Porteus install in always fresh mode as per my initial instructions.

The other option is to read through the script and create the USB manually. It definitely won't boot with just a single partition. I think would simply entail creating a second ext2 partition on the USB and sticking the 'porteus' folder from the Porteus iso there. Then updating the EFI/Boot/refind.conf file so that the from= line contains the correct UUID.

[Ed_P]

I havn't tested running the script after booting from an ISO.

Well, here's your chance.

You should run it from a regular Porteus install in always fresh mode as per my initial instructions.

I don't have a "regular install".

The other option is to read through the script and create the USB manually. It definitely won't boot with just a single partition.

But it is booting from a single partition, it just isn't booting to Porteus. And the partition is 7GB rather than 100MB.

Code: Select all

root@porteus:~# blkid
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="14E65B5EE65B3F64" TYPE="ntfs" 
/dev/loop0: LABEL="Porteus" TYPE="iso9660" 
/dev/loop1: TYPE="squashfs" 
/dev/loop2: TYPE="squashfs" 
/dev/loop3: TYPE="squashfs" 
/dev/loop4: TYPE="squashfs" 
/dev/loop5: TYPE="squashfs" 
/dev/sdb1: UUID="53B8-7FD3" TYPE="vfat" 
root@porteus:~# 

I think would simply entail creating a second ext2 partition on the USB and sticking the 'porteus' folder from the Porteus iso there. Then updating the EFI/Boot/refind.conf file so that the from= line contains the correct UUID.

You do remember I'm the guy that asked how to boot to root, right?

[bour59]

@brokenman
all's fine now
I have recreated another usb device
and executed the last version of your shell after boot on a cd
i'had to re-execute the shell after mounting the cdrom
disable the secure boot and ok
my uefi desktop is happy !
a lot of thanks

[brokenman]

Welcome bour59. Glad it is working.

But it is booting from a single partition, it just isn't booting to Porteus.

Quite obviously I meant it won't boot into Porteus with a single partition that DOESN'T contain the porteus files. BTW, it is not booting, it is only bootstrapping.

Well, here's your chance.

Ok EdP I will boot to an ISO and try to run my script. If it doesn't create the USB device correctly I will edit the script for you. I will add it to my TODO list.

You do remember I'm the guy that asked how to boot to root, right?

Yes. Sorry. Sometimes I don't don't take the time to explain fundamentals. Now that bour59 has shown that the script works I will write a HOWTO on installing to HD with step by step instructions. The same steps can be applied to a USB device. The script was indeed created for people that don't have the knowledge (or the time to attain it) and just want a quick script to sort it out for them.

[Ed_P]

But it is booting from a single partition, it just isn't booting to Porteus.

Quite obviously I meant it won't boot into Porteus with a single partition that DOESN'T contain the porteus files. BTW, it is not booting, it is only bootstrapping.

"bootstrapping"! Ok.

At this point I have manually copied the Porteus ISO folders to the USB drive. Thus I now have:

Code: Select all

F:\>dir
 Volume in drive F has no label.
 Volume Serial Number is 53B8-7FD3

 Directory of F:\

08/28/2013  11:29 AM    <DIR>          EFI
07/06/2013  04:11 PM    <DIR>          porteus
07/06/2013  01:36 PM    <DIR>          boot
               0 File(s)              0 bytes
               3 Dir(s)   7,578,173,440 bytes free

F:\>dir EFI
 
 Directory of F:\EFI

08/28/2013  10:32 PM    <DIR>          BOOT
08/28/2013  10:15 PM    <DIR>          porteus
08/25/2013  02:35 PM    <DIR>          tools
               0 File(s)              0 bytes
               3 Dir(s)   7,578,173,440 bytes free

F:\>dir porteus

 Directory of F:\porteus

07/06/2013  01:25 PM             1,015 make_iso.sh
07/06/2013  01:25 PM               437 porteus-v2.1-i486.sgn
08/10/2013  03:52 PM    <DIR>          base
07/06/2013  01:25 PM    <DIR>          modules
07/06/2013  01:25 PM    <DIR>          optional
07/06/2013  01:25 PM    <DIR>          rootcopy
               2 File(s)          1,452 bytes
               4 Dir(s)   7,578,173,440 bytes free

F:\>dir boot

 Directory of F:\boot

09/30/2013  09:59 AM    <DIR>          .
09/30/2013  09:59 AM    <DIR>          ..
08/10/2013  03:50 PM           193,762 Porteus-installer-for-Linux.com
07/06/2013  01:25 PM           119,021 Porteus-installer-for-Windows.exe
07/06/2013  11:15 PM    <DIR>          docs
07/07/2013  06:09 PM    <DIR>          syslinux
               2 File(s)        312,783 bytes
               4 Dir(s)   7,578,173,440 bytes free

So what do I need to change to boot this?

Well, here's your chance.

Ok EdP I will boot to an ISO and try to run my script. If it doesn't create the USB device correctly I will edit the script for you. I will add it to my TODO list.

You do remember I'm the guy that asked how to boot to root, right?

Yes. Sorry. Sometimes I don't don't take the time to explain fundamentals. Now that bour59 has shown that the script works I will write a HOWTO on installing to HD with step by step instructions. The same steps can be applied to a USB device. The script was indeed created for people that don't have the knowledge (or the time to attain it) and just want a quick script to sort it out for them.

Don't worry about not explaining, not everybody is as raw as I am. Anyways, what do I need to change to boot the Porteus folders/files that I've added to the flash drive?

[Ed_P]

2) Your almost there. This error means that it is not finding the porteus installation on the USB. You should open the file EFI/Boot/refind.conf and scroll to the bottom where you will see the Porteus entry and you can check the from= line to make sure it points to the USB device.

This is my refind.conf file. I do not see any reference to the Porteus .sgn file.

Code: Select all

timeout 20
hideui label,editor,hints
icons_dir myicons
banner myicons/porteus-bootloader.bmp
use_graphics_for linux
showtools reboot, shutdown, exit
scan_driver_dirs EFI/tools/drivers_x64
scanfor manual,external
scan_all_linux_kernels
menuentry "Porteus" {
    icon EFI/BOOT/myicons/porteus-saved.png
        volume ext2
    loader /EFI/porteus/vmlinuz
    initrd /EFI/porteus/initrd.xz
    options "from=UUID:53B8-7FD3 changes=/porteus volume=99%"
}
  
menuentry "Porteus RAM" {
    icon EFI/BOOT/myicons/porteus-ram.png
        volume ext2
    loader /EFI/porteus/vmlinuz
    initrd /EFI/porteus/initrd.xz
    options "from=UUID:53B8-7FD3 copy2ram volume=99%"
}
  
menuentry "Porteus FRESH" {
    icon EFI/BOOT/myicons/porteus-fresh.png
        volume ext2
    loader /EFI/porteus/vmlinuz
    initrd /EFI/porteus/initrd.xz
    options "from=UUID:53B8-7FD3 base_only nomagic norootcopy volume=99%"
}
  
menuentry "Porteus TEXT" {
    icon EFI/BOOT/myicons/porteus-text.png
        volume ext2
    loader /EFI/porteus/vmlinuz
    initrd /EFI/porteus/initrd.xz
    options "from=UUID:53B8-7FD3 3 volume=99%"

All loader and initrd entries do point to files on the USB drive.

The .sgn file is on the USB drive at /Porteus/Porteus-v2.1-i486.sgn.

[bour59]

@edP
as I can understand you are on a usb formatted in vfat (UUID with only two parms)
if correct please read my try
I have created a one partition vfat on an usb key
then copy /EFI and /porteus on it
check by the command blkid that the UUID was the same than in refind.conf
change in the option text "ext2" by "vfat"
boot on my Uefi desktop with secure disabled
see the boot menu
then choose text mode
It was fine.
maybe this can help!
ps build made from cd x64

[Ed_P]

change in the option text "ext2" by "vfat"

Whoa bour59!! You may have hit upon something. I didn't know the significance of that refind.conf parm. I will make the change and try it latter tonight.

THANK YOU

[bour59]

@brokenman
when the /EFI is created, you can copy it on another usb bootable with bios
if you change the UUID in the refind.conf then your key can boot
in either bios mode as before but also in Uefi mode (secure boot disabled
-tested with an usb vfat+ext2 with porteus 2.1/64-
I don't thought it was possible !

[Ed_P]

Well changing ext2 to vfat didn't change the results.

Booting still can't find the ....sgn file. But I've noticed that I have TWO refind.conf files. One in the /EFI/BOOT folder and one in the /EFI/porteus folder!! While the UUID in the file in the /EFI/BOOT folder looks right the one in the /EFI/porteus does not. Should I tweak this one also?

Code: Select all

"Boot into Graphics mode"    "from=UUID:d2c78202-d77d-4fea-a793-e3758ed1b438 initrd=\\initrd.xz"
"Boot into RAM mode"    "from=UUID:d2c78202-d77d-4fea-a793-e3758ed1b438 copy2ram initrd=\\initrd.xz"
"Boot into FRESH mode"    "from=UUID:d2c78202-d77d-4fea-a793-e3758ed1b438 copy2ram base_only initrd=\\initrd.xz"
"Boot into Text mode"    "from=UUID:d2c78202-d77d-4fea-a793-e3758ed1b438 3 initrd=\\initrd.xz"

Of course since this isn't working what have I got to loose right?

[Ed_P]

No change. Booting still can't find the ....sgn file.

A related question, the refind.conf files have parms for 4 bootstrap menu items but the bootstap menu shows 5 items. Saved, RAM, Fresh, Text plus a unlabeled Penguin. What controls the Penguin's options?

[brokenman]

Thanks bour, Yes I use this method to boot from another machine as I prefer the bootloader.

@ EdP
In one of your posts you show your UUID:
/dev/sdb1: LABEL="PORTEUSUEFI" UUID="8952-182C" TYPE="vfat"

I will assume that the USB drive you created with one FAT partition is the same device. I will also assume that the file structure is as you wrote:

EFI (containing the EFI boot files and a folder called porteus with initrd.xz and vmlinuz)
porteus (containing a base folder with all porteus modules, and the porteus .sgn file)
boot (i guess this is the default boot folder from the porteus iso. This is NOT required as it isn't being used. Please delete it)

The second refind_linux.conf file in EFI/porteus/refind_linux.conf is an extra menu that is shown when you press F2 when the penguin is selected in the first boot menu. Please remove it for troubleshooting purposes. The syntax in this file is incorrect it should read initrd=\EFI\porteus\initrd.xz.

Don't worry about the .sgn file ... porteus looks for this automatically and when found, boots from the folder it was found in.
For now you just need to adjust your /EFI/Boot/refind.conf file to read :

menuentry "Porteus" {
icon EFI/BOOT/myicons/porteus-saved.png
loader /EFI/porteus/vmlinuz
initrd /EFI/porteus/initrd.xz
options "from=UUID:8952-182C changes=/porteus volume=99%"
}

I took this UUID from one of your first posts where it clearly shows the UUID fo the USB device sdb1. Let me know how it goes. My only concern in this setup is having 2 folders called 'porteus' on the one device. There is one on the root of the drive and another inside the EFI folder. With the 2 partition setup this is not an issue but since linuxrc will automatically search the porteus folders, I am hoping -- 80% sure -- that it will find the first porteus folder on the root of the device before it goes looking deeper in the folder structure.

[Ed_P]

@ EdP
In one of your posts you show your UUID:
/dev/sdb1: LABEL="PORTEUSUEFI" UUID="8952-182C" TYPE="vfat"

I will assume that the USB drive you created with one FAT partition is the same device. I will also assume that the file structure is as you wrote:

EFI (containing the EFI boot files and a folder called porteus with initrd.xz and vmlinuz)
porteus (containing a base folder with all porteus modules, and the porteus .sgn file)

!!! Yes, that was the UUID but in my Sept 28th posting the UUID had changed to:
/dev/sdb1: UUID="53B8-7FD3" TYPE="vfat"
and had lost it's label. Same flash drive in all cases. Why would the UUID change?

boot (i guess this is the default boot folder from the porteus iso. This is NOT required as it isn't being used. Please delete it)

Yes, and now deleted.

The second refind_linux.conf file in EFI/porteus/refind_linux.conf is an extra menu that is shown when you press F2 when the penguin is selected in the first boot menu. Please remove it for troubleshooting purposes. The syntax in this file is incorrect it should read initrd=\EFI\porteus\initrd.xz.

Ok

Don't worry about the .sgn file ... porteus looks for this automatically and when found, boots from the folder it was found in.
For now you just need to adjust your /EFI/Boot/refind.conf file to read :

menuentry "Porteus" {
icon EFI/BOOT/myicons/porteus-saved.png
loader /EFI/porteus/vmlinuz
initrd /EFI/porteus/initrd.xz
options "from=UUID:8952-182C changes=/porteus volume=99%"
}

I took this UUID from one of your first posts where it clearly shows the UUID fo the USB device sdb1. Let me know how it goes. My only concern in this setup is having 2 folders called 'porteus' on the one device. There is one on the root of the drive and another inside the EFI folder. With the 2 partition setup this is not an issue but since linuxrc will automatically search the porteus folders, I am hoping -- 80% sure -- that it will find the first porteus folder on the root of the device before it goes looking deeper in the folder structure.

Ok.

But what about the new UUID?

[Ed_P]

Ok, I changed the UUID for the Fresh option to 8952-182C and left the others set to 53B8-7FD3.

When I boot the flash drive and select Fresh I get:

searching for ....sgn file
device not ready, waiting 6 seconds
from cheatcode= is incorrect .....

When I boot the flash drive and select RAM I get:

searching for ....sgn file
from cheatcode= is incorrect ......


I get similar results as the Fresh option with the Penguin option.


The contents of the flash drive's /porteus folder, which was copied from the .iso file, are:

Code: Select all

F:\porteus>dir
 Volume in drive F has no label.
 Volume Serial Number is 53B8-7FD3        <- current UUID?

 Directory of F:\porteus

09/29/2013  01:03 AM    <DIR>          .
09/29/2013  01:03 AM    <DIR>          ..
07/06/2013  01:25 PM             1,015 make_iso.sh
07/06/2013  01:25 PM               437 porteus-v2.1-i486.sgn
08/10/2013  03:52 PM    <DIR>          base
07/06/2013  01:25 PM    <DIR>          modules
07/06/2013  01:25 PM    <DIR>          optional
07/06/2013  01:25 PM    <DIR>          rootcopy
               2 File(s)          1,452 bytes
               6 Dir(s)   7,582,126,080 bytes free

And there is indeed a .sgn file there.


I finally see the problem.

While there is indeed a .....sgn file in the /porteus folder it is NOT the one being searched for. The Starting init script is looking for: Porteus-v2.1-x86_64.sgn not the one that I have. The UEFI machine is indeed a 64-bit machine but the Porteus iso that I run is a 32-bit version which runs on all machines.

[Ed_P]

I tried to download the 64-bit version but the download links on http://www.porteus.org/downloads.html are broken.