Dell 3040 will not boot from installation. (solved)

[number77]

Hello
I am trying to install Fossapup or xenial64 on a Dell Wyse 3040 thin client. I has Intel Atom x5 Z-8350 and 8gb eMMC flash. I can boot it from usb and install to flash but not get it to boot.
I read it turns out that the 3040 requires the UEFI fallback location (\EFI\BOOT\BOOTX64.EFI) to be populated.
What does it mean and how could I get Fossapup or Xenial64 to boot on it, preferably Xenial as it boots faster.
Help appreciated
Thanks
number77

[Phoenix]

See Grub2Config post here: viewtopic.php?t=3360&hilit=grub2config

Select UEFI installation method. Make sure you point it to the FAT32 partition that is marked with esp flag. You can find this in GParted.

Then once the keys are placed there, replace the mentioned file with the key. (Should be grub or boot efi)

But, if you want to be able to boot multiple systems with little effort other than placing in the boot keys, see rEFInd here: https://rodsbooks.com/refind/getting.html

This also contains a basic tutorial on Secure Boot and how to set it up. Please note depending on your manufacturer they may make this extraordinarily difficult. Also toggling Secure Boot off, may end up wiping out the entire database, therefore forcing you to repeat these steps tediously. As well the option to 'Install Default Secure Boot Keys' may simply replace everything in the database with the default.

[number77]

See Grub2Config post here: viewtopic.php?t=3360&hilit=grub2config

Select UEFI installation method. Make sure you point it to the FAT32 partition that is marked with esp flag. You can find this in GParted.

Then once the keys are placed there, replace the mentioned file with the key. (Should be grub or boot efi)

But, if you want to be able to boot multiple systems with little effort other than placing in the boot keys, see rEFInd here: https://rodsbooks.com/refind/getting.html

This also contains a basic tutorial on Secure Boot and how to set it up. Please note depending on your manufacturer they may make this extraordinarily difficult. Also toggling Secure Boot off, may end up wiping out the entire database, therefore forcing you to repeat these steps tediously. As well the option to 'Install Default Secure Boot Keys' may simply replace everything in the database with the default.

Hello Pheonix
I have tried with your instructions but got no where, I think it may be too complex for me. Pity as I have installed Puppies on everything so far.

[mikewalsh]

@number77 / @Phoenix :-

There may be more to it than simply recycling through all the standard options. Take a look on the "ParkyTowers" website, here:-

https://www.parkytowers.me.uk/thin/wyse/3040/

Is this the model in question? There's instructions for getting Fossapup64 up-and-running via UEFI from a flash drive, on the 'Linux' tab. No mention of getting it running from the internal MMC flash, however.

It's a shame starhawk is no longer a part of this community. He was really into these things, and was an absolute fount of knowledge concerning all the quirks involved in running them....

Most of the problems with modifying this thing to make it more usable appear to stem from the complete lack of internal USB & PCI-e buses. It appears only an M.2 interface is available, wired up to only supply SDIO signalling (whatever that means).

Mike.

[bigpup]

I wonder if making a bootable USB by using Frugalpup Installer would work.

You can do an install to USB using the frugalpup Installer.
It can install a boot loader that works with legacy bios or UEFI or both.

Frugalpup installer topic is here:
viewtopic.php?t=337

Note:
Fossapup64 9.5 has Frugalpup installer v20.
May want to get the latest version 37 to do this.
Use the main Frugalpup installer program not the stickpup ones.

This is how to setup the USB and install Puppy to the USB.

You do have to manually setup the USB drive with partitions, before using Frugalpup installer.

Use Gparted program to delete all partitions on drive.
Make two partitions.
First one a small 300MB, formatted fat32, flagged boot.
2nd partition the rest of the drive, formatted ext 3 or 4.

Note:
If you use a GPT partition table. Only the UEFI boot loader can be installed.
A msdos partition table. Can install UEFI, legacy, or both type boot loaders.

Have the Puppy version iso available at a location it can be accessed.

run menu->Setup->FrugalPup flexible frugal installer.

This is a program that requires you to make choices, just go slowly and read the provided info.

On main widow select the Puppy button.
This will go thru the install process.
Install Puppy version to the 2nd partition.
It will provide a way to make a directory(folder) to put the frugal install in.
Do that. Best if you name it the name of the Puppy version or similar.
Carefully read that pages information. Pressing OK does not make the directory. Pressing enter key does.
Complete install.

Back at main window.
Select boot button.
This will install the boot loader.
Choose to install to the first partition.
You can choose UEFI or legacy or both.
Both will install both types of boot loaders, so both will provide for UEFI and legacy booting.

When complete you should have Puppy version as a frugal install on the 2nd partition.
The Grub2 boot loader on the first partition.

Note:
On a normally setup UEFI (secure boot enabled) it will require installing the Puppy security key.
When you boot.
The Puppy security key install will run and walk you through installing the security key.

[number77]

@number77 / @Phoenix :-

There may be more to it than simply recycling through all the standard options. Take a look on the "ParkyTowers" website, here:-

https://www.parkytowers.me.uk/thin/wyse/3040/

Is this the model in question? There's instructions for getting Fossapup64 up-and-running via UEFI from a flash drive, on the 'Linux' tab. No mention of getting it running from the internal MMC flash, however.

It's a shame starhawk is no longer a part of this community. He was really into these things, and was an absolute fount of knowledge concerning all the quirks involved in running them....

Most of the problems with modifying this thing to make it more usable appear to stem from the complete lack of internal USB & PCI-e buses. It appears only an M.2 interface is available, wired up to only supply SDIO signalling (whatever that means).

Mike.

Thanks Mike, I have seen Parky Towers and yes thats the model. I can get it to boot easily from USB but really want to install to HDD or rather eMMC.

[number77]

I wonder if making a bootable USB by using Frugalpup Installer would work.

You can do an install to USB using the frugalpup Installer.
It can install a boot loader that works with legacy bios or UEFI or both

Thanks bigpup it does boot from USB without much trouble but I need to install to internal drive. Any ideas

[bigpup]

Can you access the bios and see any settings for selecting the boot device or have a boot device selection list accessible at boot?

when you boot with the Puppy USB.
Does the emmc drive show up as a drive icon on the desktop?
If yes.
Can you do anything with it by using Gparted?
If yes.

Try using Frugalpup installer to install Puppy to the emmc.
Seup the emmc drive as I posted earlier about using Frugalpup installer.
Select to install the UEFI boot loader.

This worked for me to boot an install to a internal emmc drive on a chromebook and a HP stream laptop.

Note:
May need to use gpt partition table setup on the emmc drive.

[number77]

Can you access the bios and see any settings for selecting the boot device or have a boot device selection list accessible at boot?

when you boot with the Puppy USB.
Does the emmc drive show up as a drive icon on the desktop?
If yes.
Can you do anything with it by using Gparted?
If yes.

Try using Frugalpup installer to install Puppy to the emmc.
Seup the emmc drive as I posted earlier about using Frugalpup installer.
Select to install the UEFI boot loader.

This worked for me to boot an install to a internal emmc drive on a chromebook and a HP stream laptop.

Note:
May need to use gpt partition table setup on the emmc drive.

Yes bios boot

capture31692.png (472.37 KiB) Viewed 4286 times

gives option UEFI Hard drive partition 1
Gparted works as normal HDD.
I have installed Puppy files to either one fat32 partition, or one fat32 and next ext4 and boot to partition 1, fat32. Still no boot.
I get an error message as attachment:

[number77]

I should add at boot:
Loading vmlinux
Loading initrd.gz
wait for usb storage done
loading puppy files failed
Then the rest of the error

[bigpup]

These images are booting from Fossapup64 installed on the internal emmc drive?
If yes.
Do you have any USB drives plugged into the computer?
If yes.
Have no USB drives plugged in.
Now try booting the emmc drive install.

to Fossapup64 the emmc drive may be seen as a USB device.
Fossapup64 has a bug about not booting from USB if another USB drive is also found.

[number77]

These images are booting from Fossapup64 installed on the internal emmc drive?
If yes.
Do you have any USB drives plugged into the computer?
If yes.
Have no USB drives plugged in.
Now try booting the emmc drive install.

to Fossapup64 the emmc drive may be seen as a USB device.
Fossapup64 has a bug about not booting from USB if another USB drive is also found.

Yes booting from emmc drive.
No usb drive connected to computer.
Images from installation to emmc with no usb connected.

[number77]

The 3040 has 8.2GB emmc.
How should I partition it. It is at the moment two partitions, first fat32 boot flag esp or boot, I have tried both, no difference same error.
And same error if I install to partition 1 or 2.
Funny thing is if I try to run Grub2 it says boot flag not set, run Gparted.

[Phoenix]

It probably means where GRUB2 is installed, which should be the Linux partition, rather than the fat32 partition.

Also could you try removing any flags that is psomething= besides pfix= and flags with no p at the beginning, and attempt booting (without a USB of course)? It may be that the kernel doesn't have the support needed, but we need to rule out bad configuration for init. You can press e in GRUB2 to edit the boot stanza temporarily.

Example:

/vmlinuz pfix=ram

[number77]

It probably means where GRUB2 is installed, which should be the Linux partition, rather than the fat32 partition.

Also could you try removing any flags that is ``psomething=`` besides ``pfix=`` and flags with no ``p`` at the beginning, and attempt booting (without a USB of course)? It may be that the kernel doesn't have the support needed, but we need to rule out bad configuration for init. You can press e in GRUB2 to edit the boot stanza temporarily.

Example:

``/vmlinuz pfix=ram``

/vmlinuz pfix=ram
gives /bin/sh: /vmlinuz: not found

[bigpup]

Fossapup64 9.5 installed on an internal emmc drive.
I setup the drive with two partitions.
1st one fat32 300MB flagged boot, esp
2nd one the rest of drive space, ext4 format.

The boot loader stuff is on 1st partition. (the uefi boot loader was selected for install)
Frugal install of Fossapup64 on 2nd partition.

I did the install the way I earlier posted using the Frugalpup Installer program.

So, see if your grub.cfg entry looks similar like mine.

Note:
Your UUID will be different.

menuentry "Puppy fossapup64 9.5" {
insmod ext2
search --no-floppy --fs-uuid --set=root 58288cbf-84f1-4f7c-a7a7-28f4cb19f0fc
echo "Loading vmlinuz"
linux /fossapup6495/vmlinuz pmedia=atahd pdrv=58288cbf-84f1-4f7c-a7a7-28f4cb19f0fc psubdir=/fossapup6495 pfix=fsck,fsckp,trim TZ=EST5EDT,M3.2.0,M11.1.0
if [ -e /fossapup6495/local-initrd.gz ]; then
set local_rd=/fossapup6495/local-initrd.gz
else
set local_rd=
fi
if [ -e /fossapup6495/ucode.cpio ]; then
set ucode_rd=/fossapup6495/ucode.cpio
echo "Loading ucode.cpio and initrd.gz"
else
set ucode_rd=
echo "Loading initrd.gz"
fi
initrd $ucode_rd /fossapup6495/initrd.gz $local_rd
}

[Phoenix]

It probably means where GRUB2 is installed, which should be the Linux partition, rather than the fat32 partition.

Also could you try removing any flags that is ``psomething=`` besides ``pfix=`` and flags with no ``p`` at the beginning, and attempt booting (without a USB of course)? It may be that the kernel doesn't have the support needed, but we need to rule out bad configuration for init. You can press e in GRUB2 to edit the boot stanza temporarily.

Example:

``/vmlinuz pfix=ram``

/vmlinuz pfix=ram
gives /bin/sh: /vmlinuz: not found

No, edit when you are presented with the option to select entries for booting. It should say GRUB2. Then you press e.
Or as already showed by the above post, use that configuration for the grub.cfg. (There are multiple of them, so make sure it contains the boot entries and not simply point to another file instead.)

[number77]

Fossapup64 9.5 installed on an internal emmc drive.
I setup the drive with two partitions.
1st one fat32 300MB flagged boot, esp
2nd one the rest of drive space, ext4 format.

The boot loader stuff is on 1st partition. (the uefi boot loader was selected for install)
Frugal install of Fossapup64 on 2nd partition.

I did the install the way I earlier posted using the Frugalpup Installer program.

So, see if your grub.cfg entry looks similar like mine.

Note:
Your UUID will be different.

menuentry "Puppy fossapup64 9.5" {
insmod ext2
search --no-floppy --fs-uuid --set=root 58288cbf-84f1-4f7c-a7a7-28f4cb19f0fc
echo "Loading vmlinuz"
linux /fossapup6495/vmlinuz pmedia=atahd pdrv=58288cbf-84f1-4f7c-a7a7-28f4cb19f0fc psubdir=/fossapup6495 pfix=fsck,fsckp,trim TZ=EST5EDT,M3.2.0,M11.1.0
if [ -e /fossapup6495/local-initrd.gz ]; then
set local_rd=/fossapup6495/local-initrd.gz
else
set local_rd=
fi
if [ -e /fossapup6495/ucode.cpio ]; then
set ucode_rd=/fossapup6495/ucode.cpio
echo "Loading ucode.cpio and initrd.gz"
else
set ucode_rd=
echo "Loading initrd.gz"
fi
initrd $ucode_rd /fossapup6495/initrd.gz $local_rd
}

I have two grub.cfg s
One in root of emmc the other in EFI folder.
Root is
#
set default=0
set timeout=5

set menu_color_normal='yellow/blue'
set menu_color_highlight='black/cyan'

if [ $grub_platform = 'efi' ]; then
loadfont /boot/grub/fonts/DejaVuSansMono18.pf2
set gfxmode=auto
terminal_output gfxterm
fi

menuentry "Puppy fossapup64 9.5" {
insmod fat
search --no-floppy --fs-uuid --set 341B-CD77
echo "Loading vmlinuz"
linux /vmlinuz pmedia=atahd pdrv=341B-CD77 pfix=fsck,fsckp,trim TZ=GMT0
echo "Loading initrd.gz"
initrd /initrd.gz
}
if [ $grub_platform = 'efi' ]; then
menuentry 'System BIOS setup' {
fwsetup
}
fi
menuentry "Shutdown computer" {
halt
}
menuentry "Reboot computer" {
reboot

EFI folder is
# The real config file for grub is /grub.cfg
configfile /grub.cfg

[number77]

It probably means where GRUB2 is installed, which should be the Linux partition, rather than the fat32 partition.

Also could you try removing any flags that is ``psomething=`` besides ``pfix=`` and flags with no ``p`` at the beginning, and attempt booting (without a USB of course)? It may be that the kernel doesn't have the support needed, but we need to rule out bad configuration for init. You can press e in GRUB2 to edit the boot stanza temporarily.

Example:

``/vmlinuz pfix=ram``

/vmlinuz pfix=ram
gives /bin/sh: /vmlinuz: not found

No, edit when you are presented with the option to select entries for booting. It should say GRUB2. Then you press e.
Or as already showed by the above post, use that configuration for the grub.cfg. (There are multiple of them, so make sure it contains the boot entries and not simply point to another file instead.)

Pheonix, I don't understand.

[number77]

In the BIOS boot sequence, I have two options.
UEFI: USB Disk 2.0 PMAP. Partition 1
UEFI: hard drive. Partition1

Details of UEFI: Hard drive are as attached file.

[Feek]

Are the puppy files in a folder or in the root of the partition?

If they are in a folder, you could try to add the parameter psubdir=/name_of_the_folder to the "linux" (kernel) line (see bigpup´s grub.cfg entry).

Did you get the uuid with "lsblk" command in terminal?
Maybe it is not an issue, but your uuid seems to be much shorter than the bigpup´s one.

EDIT:
Sorry,
blkid is the right one to get uuid in terminal (not "lsblk").
bigpup has already guided you (below)

[number77]

Are the puppy files in a folder or in the root of the partition?

If they are in a folder, you could try to add the parameter psubdir=/name_of_the_folder to the "linux" (kernel) line (see bigpup´s grub.cfg entry).

Did you get the uuid with "lsblk" command in terminal?
Maybe it is not an issue, but your uuid seems to be much shorter than the bigpup´s one.

Hello Feek
The file are not in a folder.
Also I don't understand:
Did you get the uuid with "lsblk" command in terminal?
My terminal experience is quite limited.

[bigpup]

From your posted grub.cfg file entry.
uuid --set 341B-CD77

I think this being used as the uuid is the problem with the boot entry.
That does not look like a true uuid.
Not sure why Frugalpup installer boot loader install made it that way.
Well, that does seem to be the correct UUID for a vfat formatted partition, which should be the boot partition, and only want on it the boot loader stuff, not Fossapup64 files.
This is kind of a UEFI boot requirement.
1st partition, boot partition, with the boot loader on it.

Did you use the latest version of Frugalpup Installer? v37
viewtopic.php?t=337

Did you put all the Fossapup64 9.5 files in a folder on the 2nd partition or at least put them on the 2nd partition?
That is where they need to be.

Yes, the grub.cfg, at root of the first partition, is the one that actually is used.

Try using this command in a console to see what the UUID is:

Code: Select all

blkid

I ran command blkid on my computer booting from a emmc drive install. (has 3 partitions)

/dev/mmcblk0p1: UUID="F516-26DA" TYPE="vfat" PARTUUID="42dcc82a-01"
/dev/mmcblk0p2: UUID="ce735d08-0396-49d7-8c34-3dfa3d1e0feb" TYPE="swap" PARTUUID="42dcc82a-02"
/dev/mmcblk0p3: UUID="5bdb0184-dace-4f4a-8353-85ba5064edc3" TYPE="f2fs" PARTUUID="42dcc82a-03"

Fossapup64 is on the 3rd partition in folder fossapup64.
My grub.cfg entry has:
UUID="5bdb0184-dace-4f4a-8353-85ba5064edc3
Identifying the 3rd partition as location of the Fossapup64 files.

[bigpup]

You got it working on another computer you posted about in this old topic:
https://oldforum.puppylinux.com/viewtop ... 9#p1042169

[Phoenix]

Once you find the UUID of the partition holding the puppy files, change that hexademical string to that of the partition's UUID. At /grub.cfg of the puppy partition.
As well to clarify what I meant, although you probably no longer need to do this anymore once you edit the grub.cfg, this is what I meant: https://www.howtogeek.com/wp-content/up ... 00&pad=1,1

[number77]

As I can't boot the system I can't use blkid, any other way.
I have downloaded frugal installer v37, made two partitions, first fat32 boot, the second ext4 with all installed Puppy files.
I then installed boot on first fat32 boot partition.
Still get the same error message on boot.

[number77]

As I can't boot the system I can't use blkid, any other way.
I have downloaded frugal installer v37, made two partitions, first fat32 boot, the second ext4 with all installed Puppy files.
I then installed boot on first fat32 boot partition.
Still get the same error message on boot.

I tried blkid on the usb booted Fossapup64 and got the following:
root# blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: UUID="fd4a69c2-164f-4b51-bdab-4c1512144253" TYPE="ext4"
/dev/sda1: UUID="7202-3CD9" TYPE="vfat" PARTUUID="20545ea6-01"
/dev/mmcblk1p1: UUID="52C4-C9E7" TYPE="vfat" PARTUUID="657a4485-01"
/dev/mmcblk1p2: UUID="182871bb-c8a9-4c5d-bc24-1eb03dda6857" TYPE="ext4" PARTUUID="657a4485-02"

So it does give the uuid of the two partitions on the emmc

What next.

[bigpup]

I then installed boot on first fat32 boot partition.

Our spy satellites cannot see what you exactly did and that is important to know.

When you used Frugalpup Installer to install the boot loader on 1st partition.
What type did you select?
UEFI?

On this new install.

Post what the entry is in the grub,cfg file that you boot with.
Need to see what this new install entry looks like.

Now that you know what the 2nd partitions UUID is.
Is it the same one used in the grub.cfg entry?
If not.
Change the UUID in the entry to 182871bb-c8a9-4c5d-bc24-1eb03dda6857

[bigpup]

You probably have already done this, but how do I know that.

found this info about setting one of these computers up for Linux.

Press F2 during boot to get into the BIOS.
Unlock the settings using the default password “Fireport”.
Reset the BIOS values to the factory settings and save.
This automatically put my Xubuntu USB stick first in the boot order

You probably want to change this device boot order, in the bios, to first the internal emmc drive or just boot with no USB plugged in.

[FeodorF]

Hi All!

If it is still needed the manual can be downloaded from here:

https://dl.dell.com/topicspdf/wyse-3040 ... _en-us.pdf