Dell 3040 will not boot from installation. (solved)

[number77]

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.

First device is set to UEFI: Hard Drive. Partition 1

[number77]

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

I selected both for boot loader.
grub.cfg 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 ext2
search --no-floppy --fs-uuid --set=root 182871bb-c8a9-4c5d-bc24-1eb03dda6857
echo "Loading vmlinuz"
linux /vmlinuz pmedia=atahd pdrv=182871bb-c8a9-4c5d-bc24-1eb03dda6857 pfix=fsck,fsckp,trim TZ=GMT0
if [ -e /local-initrd.gz ]; then
set local_rd=/local-initrd.gz
else
set local_rd=
fi
if [ -e /ucode.cpio ]; then
set ucode_rd=/ucode.cpio
echo "Loading ucode.cpio and initrd.gz"
else
set ucode_rd=
echo "Loading initrd.gz"
fi
initrd $ucode_rd /initrd.gz $local_rd
}
if [ $grub_platform = 'efi' ]; then
menuentry "System BIOS setup" {
fwsetup
}
fi
menuentry "Shutdown computer" {
halt
}
menuentry "Reboot computer" {
reboot
}
UUID is the same but without: pfix=fsck,fsckp,trim TZ=GMT0

[number77]

Hi All!

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

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

Thanks FeodorF. Good manual.

[bigpup]

I have run out of ideas.

That grub.cfg entry should be working.

In the computers bios settings.
Is secure boot disabled?
If no.
Disable secure boot.

Internal emmc drive booting has been an issue getting it to work on all possible computers.
Fossapup64 9.5 has been a little problematic depending on the computer.

Only thing that may work is try a different Puppy Linux version.
Maybe lxPupsc or ScPup.
These seem to be built using a much newer version of Woof-CE than Fossapup64 9.5 used.
There has been some work on improving the boot process.

[number77]

I have run out of ideas.

That grub.cfg entry should be working.

In the computers bios settings.
Is secure boot disabled?
If no.
Disable secure boot.

Internal emmc drive booting has been an issue getting it to work on all possible computers.
Fossapup64 9.5 has been a little problematic depending on the computer.

Only thing that may work is try a different Puppy Linux version.
Maybe lxPupsc or ScPup.
These seem to be built using a much newer version of Woof-CE than Fossapup64 9.5 used.
There has been some work on improving the boot process.

I will try these bigpup. It is about time I finished with it, I am beginning to want to do damage to it.
Will get back if I have success. In the meantime thank you for your help and also to others who have been so patient.
All the best
number77

[Phoenix]

There are technically other routes to getting it into a desktop but all of this would be manual and extremely tedious. And maybe making mistakes. Also remove the pmedia and pdrv flag. It will make it look for something connected to a SATA port that is an 'HDD' and pdrv may also be intefering.

Additionally its entirely possible that you need to compile the kernel to work with the emmc drives.

[number77]

I have run out of ideas.

That grub.cfg entry should be working.

In the computers bios settings.
Is secure boot disabled?
If no.
Disable secure boot.

Internal emmc drive booting has been an issue getting it to work on all possible computers.
Fossapup64 9.5 has been a little problematic depending on the computer.

Only thing that may work is try a different Puppy Linux version.
Maybe lxPupsc or ScPup.
These seem to be built using a much newer version of Woof-CE than Fossapup64 9.5 used.
There has been some work on improving the boot process.

Dead right bigpup.
lxPupsc worked first time without trouble so thanks for that again.

[bigpup]

number777,

Do you want to try something?

See if changing the kernel in Fossapup64 9.5, to the one used in LxPupsc64, will make it now boot, from the internal emmc drive.

Here is download link to the kernel:
https://sourceforge.net/projects/lxpup/ ... 2/download

[number77]

number777,

Do you want to try something?

See if changing the kernel in Fossapup64 9.5, to the one used in LxPupsc64, will make it now boot, from the internal emmc drive.

Here is download link to the kernel:
https://sourceforge.net/projects/lxpup/ ... 2/download

Yes I will give it a try, it was easy to load ScPup64 again if it does not.
I have downloaded hugh-5.16.16 from sourceforge. You will have to tell me how.

[bigpup]

You will first need to do the install of Fossapup64 9.5 on the emmc drive using Frugalpup installer and installing the uefi boot loader.

Note:
If ScPup64 was installed with the Frugalpup installer.
You can keep it installed.
Run Frugalpup Installer to install Fossapup64 choosing to make a directory (folder) to install into. (all of Fossapup64 files in this directory)
Run Frugalpup Installer boot loader uefi type install and both ScPup64 and Fossapup64 will have entries in the boot loader menu.
So, both will be installed and you can choose which one to boot.

Because you cannot boot with this Fossapup64 install.
You will have to boot with some other operating system to do a manual kernel change operation.

If you can boot a Puppy version from USB. That would be good to do this procedure with or if you kept ScPup64 installed, boot it.

Take the huge kernel package and decompress it by using the program UExtract.
This should place all the files in a directory.
Should have these files.
.

Screenshot(2).jpg (17.95 KiB) Viewed 1447 times

.
Need to rename them to be able to replace the ones in the Fossapup64 install with them.

Rename vmlinuz-5.16.16-lxpup64 to vmlinuz.

Rename kernel-modules-5.16.16-lxpup64.sfs to zdrv_fossapup64_9.5.sfs.

Now delete the vmlinuz and zdrv_fossapup64_9.5.sfs files from the Fossapup64 install and replace them with these new ones you just made.

That is it.
You have manually replaced the kernel.

Now try booting with Fossapup64 install on the emmc drive.

Note:
For doing it in a Puppy version that can be booted. (Puppy version is running and operating normally)
You can use the change_kernels program.
viewtopic.php?p=1497#p1497

[number77]

number777,

Do you want to try something?

See if changing the kernel in Fossapup64 9.5, to the one used in LxPupsc64, will make it now boot, from the internal emmc drive.

Here is download link to the kernel:
https://sourceforge.net/projects/lxpup/ ... 2/download

It took some time but is Brilliant bigpup.
It is now booting Fossapup9.5 without problems, kernel 5.16.16.
So once again, Thank You.

[bigpup]

Thanks for that test of my idea.

Maybe this will help others having the same issue with Fossapup64 9.5.

[number77]

Thanks for that test of my idea.

Maybe this will help others having the same issue with Fossapup64 9.5.

I tried your modification with Xenialpup64 and it also worked perfectly so now have a choice of three Puppies.
Thanks again for your time.