How to install on hp11-y023TU laptop?(solved)

[boof]

can't enter system to boot from usb. is there a utility?

[boof]

got into settings, re-config boot menu, BUTT mm02 not detected, so no main.sfs file found. using mm*64.efi. vmlinuz and initrd load, but not anything else. boot from usb works. did set trim in boot options. all win10 deleted

EDIT:
partitions named <mm01>, <mm02>, <mm03> appears faulty initrd.gz as it fails to pass on partion name when calling .sfs file . but it does have the partition UUID. failed to preserve logs, or they were temp only and have gone. currently booting from usb.

[bigpup]

I am confused.

The first post is talking about booting from USB.

Now you are talking about booting from I think the internal drive with some type of install.
In that post you say you are booting from USB.

So what exactly do you need help with????

I am going to guess it is getting a Fossapup64 9.5 install on an internal SSD type drive to boot.
Yes?
No?

[boof]

yes, an internal flash memory ssd, 30GB cant get to load beyond initrd.gz. partition mm02 has valid uuid, but is no longer recognised, hence critical error and loading stops. mm02 has all puppy files, mm01 has grub2, mm03 has savefile and swapfile, mm02 = ext2; mm03=ext4do not know how to disable hp system oversight of bios.

[boof]

gparted lists the main hard drive under 2 names, one of which it cannot read, they are:
mmcblk0 card r/w ok
mmcblk0rpmb card r/w not working.

is this the problem?

[boof]

As the vmlinuz and initrd.gz are loaded and run ok, perhaps the handover to the sfs file should retain their address mode/code.using the sub code ~rpmb nor its UUID is valid? I'll try and edit initrd.gz at that point and see.

NB forum does not allow double spaces. any gap after an <=> is a double space, indicating a null answer.
error msg is:

3 PSUBDIR=P BP-FN= BP-DEF-FN=puppy_fossapup64_9.5.sfs
HAVE-PART=''
ONE=PART=""
6 ONE-PART= ONE-TRY= PDRV=

NB: in gparted, the partitions are listed as sub partitions uunder the main drive, tho' it's not shown on screen. i'll look in the /dev /disk/ file to see how it's organised.
drives are organised by id, by uuid, by partition uuid and by path. i don't know which to use, but the uuid it displays is obviously wrong, i'll restart it and record the displayed uuid and see which one it uses. then it can be changed to the other. should not be an hard fix.

is this <fuseblk> SOMETHING I NEED TO CHANGE?
KFILESYSTEMS="$(cat /proc/filesystems | grep -v "nodev" | grep -v "fuseblk" | sed -e "s#\t##g" | tr '\n' '|' | sed -e 's#|$##g')"

[bigpup]

If Puppy Linux is the only Operating system on the drive.

I would start over and use Gparted to make a new partition table msdos
Partition and format.
Run check on the partitions when complete to make sure all is good before closing Gparted.

This is how I have done installs and having working boot, on internal SSD drives, on several laptops.

Using the Frugalpup Installer program
https://forum.puppylinux.com/viewtopic.php?t=337

This is what I do.

Use Gparted program.
Setup the drive with 2 partitions.
First one, small 300MB, fat32 format, flagged boot ,esp. (location for boot loader files, boot partition)
Rest of drive, whatever other partition(s), but one ext3 or 4 format. (location to put frugal installs)
(this is UEFI standard requirement, and some computers, look for a fat32 partition, for boot loader files)

Run Frugalpup Installer main program.
On the main window are selection buttons.
Select the Puppy button, to do the install.
Go through install process, selecting to install to the ext formatted partition.
Note:
When selecting the partition to install to.
A window pops up, giving option to make a directory, to put the frugal install in.
I make this directory and usually name it, the name of the Puppy version.
Carefully read that windows info.
Press enter, makes the directory, not the OK button.
complete the install.

When it gets back to the main Frugalpup window.
Select the boot button.
Select the location of the frugal install, on the drive.
Select the small 300MB partition as location to install the boot loader. (may need to scroll the selection window)
Select the boot loader type.
UEFI
mbr ->legacy bios boot
both

You can install the UEFI for UEFI computers, mbr for legacy bios computers, or both, to boot anything.

The UEFI will also install the needed files, to support secure boot enabled in UEFI.

When you first boot the drive, on a UEFI computer, with secure boot enabled.
A process will start, to allow you to install the Puppy security key, to the computer.
It will add this Puppy key, to the other ones, loaded on the computer.

To put more frugal installs on the same drive.
Do the complete process again, for the new Puppy version.
When you run the boot loader install.
It will make entries, for all installs it finds, on the drive.

[boof]

i followed the instructions, but it drops out of boot routines at <cannot find main sfs file.> invalid partition name? secure boot on, not having any effect having used secure boot on usb. what kind of partition name is it looking for, a blkid, or something else? this pc has several names for the same thing and i can't rell which to use/can't edit init to make it work., . a usb boot works, but the main drive does not. heaven knows what hp have done in the bios to lock out non-win 10 use.

[rcrsn51]

heaven knows what hp have done in the bios to lock out non-win 10 use.

Don't blame HP. I owned one of these and routinely installed the Deblive Starter Kit on it.

I would question whether your Puppy can boot off the emmc drive in this unit or whether you are using the correct boot arguments.

[boof]

hp laptops and i have a history of frustration. pls how diu get it to boot? i agree boot arguements may be the problem. pls dan i use them to overide init's preferences. i'm willing to customiseinit to make it work. an init 'geek' would be very helpful. we can share screens if needed, with vmware to test-boot the hard drive whilst it runs on a usb? i do not know enuf to sort this, and prob never will. i can no longger do the thinking/learning. i'm tempted to try and graft grub into init to get drive and main file detection.

edit
can't edit grldr, locked out? was thinking of placing grldr into start of init, and editing mebu list to point to main file, and editing out all init no longer needed. not neat, but it might work. might go back to grldr from grub1?

wsit 2
copy of modified init-bootmenu intial part to mount and boot main sfs.
pls check to see it works.

#!/bin/ash

# Custom file part by R J hillips to boot HP 11023TU
# which would not load main sfs file. 23/01/2023.
# sourced by /init
#
# requires: wait_for_usb() get_part_info() check_status()
# decode_id()
# ensure_mounted()

#===================================================================
# init-bootmenu_funcs
#===================================================================

TOP_LEFT_CORNER='╔'
TOP_RIGHT_CORNER='╗'
BOTTOM_LEFT_CORNER='╚'
BOTTOM_RIGHT_CORNER='╝'
HORIZONTAL_LINE='═'
VERTICAL_LINE='║'
MENU_COLOR=`echo -en '\033[97;44m'` # blue bg color bright white fg
KEY_UP=`echo -en '\033[A'`
KEY_DOWN=`echo -en '\033[B'`
KEY_ESC=`echo -en '\033\033'`

decode_entry() {
Z_PDEV1=""
Z_PDRV=""
Z_PFIX=""
Z_PIMOD=""
Z_PMEDIA=""
Z_PSAVE=""
Z_PSAVEMARK=""
Z_PSUBDIR=""
Z_PUPSFS=""
Z_UNDERDOG=""
Z_ZDRV=""
Z_FDRV=""
Z_ADRV=""
Z_YDRV=""
Z_SEARCH_DIR=""
Z_SEARCH_DRIVE=""
Z_DISTRO_SPECS=""
#CHOSEN_ENTRY="LABEL raspup|PMEDIA usbflash|"
while read FIELD VALUE
do
[ -z "$FIELD" ] && continue #empty line
#echo "'$FIELD' = '$VALUE'"
case "$FIELD" in
LABEL) continue ;; #ignore LABEL
PDEV1) Z_PDEV1=${mm0p2} ;;
PDRV) Z_PDRV=${mm0p2} ;;
PFIX) Z_PFIX=${VALUE} ;;
PIMOD) Z_PIMOD=${VALUE} ;;
PMEDIA) Z_PMEDIA=${VALUE} ;;
PSAVE) Z_PSAVE=${VALUE} ;;
PSAVEMARK) Z_PSAVEMARK=${VALUE} ;;
PSUBDIR) Z_PSUBDIR=${P} ;;
PUPSFS) Z_PUPSFS=${puppy_fossapup64_9.5.sfs} ;;
UNDERDOG) Z_UNDERDOG=${VALUE} ;;
ZDRV) Z_ZDRV=${VALUE} ;;
FDRV) Z_FDRV=${VALUE} ;;
ADRV) Z_ADRV=${VALUE} ;;
YDRV) Z_YDRV=${VALUE} ;;
SEARCH_DIR) Z_SEARCH_DIR=${VALUE} ;;
SEARCH_DRIVE) Z_SEARCH_DRIVE=${VALUE} ;;
DISTRO_SPECS) Z_DISTRO_SPECS=${VALUE} ;;
*) echo "Ignoring unknown keyword: $ENTRY_PART" ;;
esac
done <<EOF
$(echo "$CHOSEN_ENTRY" | tr '|' '\n')
EOF
}

draw_screen() {
echo -en '\033[s' # save cursor position

echo -en '\033[2J' # clear screen
echo -en "\033[${MENU_ROW_START};${MENU_COLUMN_START}H" # goto menu start
CURRENT_ROW=${MENU_ROW_START}
CURRENT_COLUMN=${MENU_COLUMN_START}

echo -n "$MENU_COLOR"
echo -n "$TOP_LEFT_CORNER"
let MENU_COLUMN_END=MENU_COLUMN_START+MAX_LABEL_WIDTH+2
while [ "$CURRENT_COLUMN" -lt "$MENU_COLUMN_END" ]
do
echo -n "$HORIZONTAL_LINE"
let CURRENT_COLUMN++
done
echo "$TOP_RIGHT_CORNER"

echo -en "\033[${MENU_COLUMN_START}G" # move to MENU_COLUMN_START
CURRENT_COLUMN=${MENU_COLUMN_START}

CURRENT_ENTRY_NR=0
while read ONE_ENTRY #$ALL_ENTRIES
do
[ -z "$ONE_ENTRY" ] && continue

let CURRENT_ENTRY_NR++

if [ "${ONE_ENTRY#LABEL}" != "$ONE_ENTRY" ]; then
ECHO_STRING=${ONE_ENTRY%%|*}
ECHO_STRING=${ECHO_STRING:6}
else
ECHO_STRING=${ONE_ENTRY%%|*}
fi

echo -n "$VERTICAL_LINE"
if [ "$CURRENT_ENTRY_NR" = "$CHOSEN_ENTRY_NR" ]; then
CHOSEN_ENTRY=${ONE_ENTRY}
echo -ne '\033[7m' # reverse video
fi
echo -n " $ECHO_STRING"
let CURRENT_COLUMN=CURRENT_COLUMN+${#ECHO_STRING}+1
while [ "$CURRENT_COLUMN" -lt "$MENU_COLUMN_END" ]
do
echo -n " "
let CURRENT_COLUMN++
done
[ "$CURRENT_ENTRY_NR" = "$CHOSEN_ENTRY_NR" ] && echo -ne '\033[27m' # reset reverse video
echo "$VERTICAL_LINE"

echo -en "\033[${MENU_COLUMN_START}G" # move to MENU_COLUMN_START
CURRENT_COLUMN=${MENU_COLUMN_START}
done <<EOF
$(echo "${ALL_ENTRIES}")
EOF

echo -n "$BOTTOM_LEFT_CORNER"
let MENU_COLUMN_END=MENU_COLUMN_START+MAX_LABEL_WIDTH+2
while [ "$CURRENT_COLUMN" -lt "$MENU_COLUMN_END" ]
do
echo -n "$HORIZONTAL_LINE"
let CURRENT_COLUMN++
done
echo "$BOTTOM_RIGHT_CORNER"
echo -en '\033[0m' # reset color

if [ "$TIMEOUT" -ge 10 ]; then
echo -en "\033[${MENU_COLUMN_START}G" # move to MENU_COLUMN_START
echo -n "Booting in ${TIMEOUT%[[:digit:]]} seconds..."
fi

echo -en '\033[u' # restore cursor position
echo -en '\033[10D' # backup cursor position
}

exec_init() {
[ "$Z_PDEV1" ] && export pdev1=$Z_PDEV1
[ "$Z_PDRV" ] && export pdrv=$Z_PDRV
[ "$Z_PFIX" ] && export pfix=$Z_PFIX
[ "$Z_PIMOD" ] && export pimod=$Z_PIMOD
[ "$Z_PMEDIA" ] && export pmedia=$Z_PMEDIA
[ "$Z_PSAVE" ] && export psave=$Z_PSAVE
[ "$Z_PSAVEMARK" ] && export psavemark=$Z_PSAVEMARK
[ "$Z_PSUBDIR" ] && export psubdir=$Z_PSUBDIR
[ "$Z_PUPSFS" ] && export pupsfs=$Z_PUPSFS
[ "$Z_UNDERDOG" ] && export underdog=$Z_UNDERDOG
[ "$Z_ZDRV" ] && export zdrv=$Z_ZDRV
[ "$Z_FDRV" ] && export fdrv=$Z_FDRV
[ "$Z_ADRV" ] && export adrv=$Z_ADRV
[ "$Z_YDRV" ] && export ydrv=$Z_YDRV
clear
}

show_menu() {
let MENU_ROW_START=ROWS-ENTRY_COUNT
let MENU_ROW_START=MENU_ROW_START/2
#echo "MENU_ROW_START = $MENU_ROW_START"

let MENU_COLUMN_START=COLUMNS-MAX_LABEL_WIDTH
let MENU_COLUMN_START=MENU_COLUMN_START/2
#echo "MENU_COLUMN_START = $MENU_COLUMN_START"

[ -z "$CHOSEN_ENTRY_NR" ] && CHOSEN_ENTRY_NR=1
[ -z "$TIMEOUT" ] && TIMEOUT=0

while true
do
draw_screen

local TEMP_INPUT=""
local INPUT=""
while true
do
if [ "$TIMEOUT" -eq 0 ]; then
read -n1 INPUT
else
while true
do
read -n1 -t 1 INPUT
[ "$?" -eq 0 ] && TIMEOUT=0 && break
if [ "$TIMEOUT" -gt 10 ]; then
let TIMEOUT=TIMEOUT-10
draw_screen
else
TIMEOUT=0
break
fi
done
fi
[ "$INPUT" = "" ] && break

TEMP_INPUT=${TEMP_INPUT}${INPUT}
[ "${#TEMP_INPUT}" -gt 3 ] && TEMP_INPUT=${TEMP_INPUT:1}

# Because arrow key codes start with the ESC charactor, ESC must be pressed
# twice to exit menu. KEY_ESC = '\033\033', two ESC chars in a row.
[ "${TEMP_INPUT}" = "$KEY_ESC" ] && INPUT="" && CHOSEN_ENTRY="" && break
[ "${TEMP_INPUT:1}" = "$KEY_ESC" ] && INPUT="" && CHOSEN_ENTRY="" && break

[ "$TEMP_INPUT" = "$KEY_UP" -a "$CHOSEN_ENTRY_NR" -gt 1 ] && let CHOSEN_ENTRY_NR-- && draw_screen
[ "$TEMP_INPUT" = "$KEY_DOWN" -a "$CHOSEN_ENTRY_NR" -lt "$ENTRY_COUNT" ] && let CHOSEN_ENTRY_NR++ && draw_screen

done
[ "$INPUT" = "" ] && break
done
}

#===================================================================
# init-bootmenu
#===================================================================

search_bootmenu(){
for ONETRY in $HAVE_PARTS;do
ONE_PART="$(echo -n "$ONETRY" | cut -f 1 -d '|')"
ensure_mounted "$ONE_PART" "/mnt/pdrv"
if [ "$ONE_MP" ];then
if [ -f /mnt/pdrv/puppy_fossapup64_9.5.sfs ]; then
cp /mnt/pdrv/puppy_fossapup64_9.5.sfs /tmp/puppy_fossapup64_9.5.sfs
fi
umount $ONE_MP
[ -f /tmp/puppy_fossapup64_9.5.sfs] && break
fi
done
}
# swap the above file content with oem file content and see if it works.

[bigpup]

Post the contents of the grub.cfg so I can see what the entries are.

Make sure the USB drive is not plugged in when you try to boot Fossapup64.

There is a bug about booting, if Fossapup64 is trying to boot from internal install and there is also a USB plugged in, with a Fossapup64 install on it.

Have secure boot disabled in the UEFI setup, just to make sure that is not causing any issues.

I assume if secure boot is enabled, you installed the Puppy security key the first time you tried to boot?
.
.

[bigpup]

Because this had Windows OS on it.
Who really knows what it could have left on the drive.

I did not put this in my directions for setting up the drive.

But maybe this will help.
Start over setting up the drive.

Make a new partition table (msdos)
Slight chance this computers UEFI wants to see a GPT partition table.
But the only boot loader that will work is the UEFI one with GPT setup.
I would use the UEFI boot loader no matter what partition table you setup.

Do the 2 partitions as before.

Now use Frugalpup Installer to do the install.

[bigpup]

Is this computer an HP Stream laptop?

[boof]

the second partition is not being read, i could try making the boot partition 1GB [fat32], and install fossapup64 in it with the save file in the remaining partition. the first partition boots, so that might work. perhaps a booted system will read the other partition?

/etc/fstab is empty, i've created a new fstab with entries for 2nd and 3rd partitions. will get another iso and graft it in place of original.

[boof]

i want command line control over grub2, but the option isn't offered, how do I get it pls?

[bigpup]

Did you try to start over setting up the drive?

New partition table.
New partitions and formatted.

Setting up the partitions and installing using Frugalpup Installer the way I posted earlier?

Tell Frugalpup Installer to install the UEFI boot loader.

Do not have the Fossapup64 USB plugged in when you try to boot from the internal drive install.

[boof]

please, i've expanded </mnt/mmcblk0p2/sbin/initrd.gz
then expanded <initrd.gz.expanded/init>
and edited <init.expanded/init>
now i want to recompress them, packit and pcompress both demand a file extension which init does not have.
how to fix pls.
the edit was to mount mmcblk0p2 as 1st thing, to test if drive was not recognised and unmounted or never mounted at begining of init.

vis

mount -t ext2 /dev/mmcblk0p2 /mnt/flash

[boof]

file initrd.gz/init/init required 2 edits

at line 54: remove leading "/" from sbin~

line 73 remove leading "." from /DISTRO-SPECS

[bigpup]

Sorry but I cannot help you.

After you installed the way I suggested earlier.

I have given you several things to look for, things to do, and ask for information.

You have done none of these things or if you have, did not provide any feedback on results.

You seem to be doing what you want to do, not what I ask, to give me some info, on what does work or does not.

I have an HP11 laptop, that boots Fossapup64 from an internal SSD drive install, with no problem.

What I am telling you to do or asking about, is based on my results, with my computer.

[boof]

i copied the original init file and added an header to make i singlr step thru so i could trace it.
my clumsy attempt failed to step, but did produce atrace when run in terminal.
the files are found at the addesses below:

someone kind who knows their stuff might go thru it for me.
sorry, but it's the best i can do after a week solid.

https://ufile.io/tnkh0xxe
https://ufile.io/0vcuacyz

[rcrsn51]

I have an HP11 laptop, that boots Fossapup64 from an internal SSD drive install, with no problem.

Is this a sata drive or an emmc drive?

[bigpup]

emmc drive.

I did have to have secure boot enabled to get it to boot from the internal emmc drive.
Install the UEFI boot loader.
Install the Puppy security key the first time I booted, so it will boot with secure boot enabled.

All of this can be done by doing the install using Frugalpup Installer the way I said in my earlier post.
It did the frugal install.
It installed the UEFI boot loader.
It installed the Puppy security key and the program to install it on the computer.

Typing this from my HP 11, with a n4000 CPU, 32Gb emmc drive, and it booted to a running Fossapup64 9.5

It shows only one internal emmc drive with msdos partition table with two partitions.
mm0p1 formatted fat32, flagged boot, lba with the boot loader on it.
mm0p2 formatted ext4, with the frugal installs on it.

If you have a SD card plugged in.
That will show as a type of emmc drive mm1p1
You will see two emmc drives.

[rcrsn51]

@bigpup: Could you please post your GRUB menu entry for Fossa64?

[boof]

HP 11-y023TU with N3060 processor, RealtekDF-4032 mmc card 32GB ss, so no main sfs file.d, incomplete booting. not mounting mmcblkop2, so not running main sfs file.
made gtp partition type, made 4 partitions, 300MB fat32 boot esc ; 1,000MB swap; 750MB ext2 OS; ballance ext4 savefile

files of boot log and grub,cfg here. all unaddressed files are empty.

Name Expiry time Size Link

grub.cfg 4 Weeks 696 Bytes https://ufile.io/mgxc8ody
misc.log 4 Weeks 4.6 KB https://ufile.io/q9nsifkd
sys.log 4 Weeks 52.7 KB https://ufile.io/u4zaegpq
bootinit.log 4 Weeks 397 Bytes https://ufile.io/xrsl5t5k
dmesg.txt 4 Weeks 27.8 KB https://ufile.io/xj7nrl6f
flag-usb-ready https://ufile.io/t7g4ul5f
ALLDRVS0
ATADRVS0
HAVE_PARTS
probedisk.log
probepart.log

[boof]

all drives accessable on usb boot, so drivers present and working. ssd boot prob loads drivers too late to boot from mmcblk0p2. drivers cannot be copied into initrd.gz for easier booting access [or at least i can't do it.] i cant expand sfs file, edit it, re-shrink and save it. the once familiar tools are now gone, or changed so much i cant use them. endless relearning is now beyond my mental powers, so i hate needless changes. can =!= should. not broken? leave it alone. tinkering: The MOST destructive form of maintenance known to man and/or God.

[bigpup]

This is my setup of the emmc drive that is working for me on my HP 11 laptop.
.
.

Screenshot.png (49.47 KiB) Viewed 362 times

.
.
This is using the Grub2 boot loader that Frugalpup Installer program installs as the UEFI boot loader.
Installing the boot loader produces the grub.cfg and puts all entries in it.
It is the entry it makes.

Fossapup64 is a frugal install, that is installed in directory fossapup6495, located on the 2nd partition of the emmc drive.

This is the grub.cfg menu entry that boots Fossapup64

}
menuentry "Puppy fossapup64 9.5" {
insmod ext2
search --no-floppy --fs-uuid --set 9ff829af-6ca7-4d90-9a87-7792f770f043
echo "Loading vmlinuz"
linux /fossapup6495/vmlinuz pmedia=atahd pdrv=9ff829af-6ca7-4d90-9a87-7792f770f043 psubdir=/fossapup6495 pfix=fsck,fsckp,trim TZ=EST5EDT,M3.2.0,M11.1.0
echo "Loading initrd.gz"
initrd /fossapup6495/initrd.gz

The drive icons on the desktop show the partitions as mm0p1 and mm0p2.

Do not have any USB drive or SD card plugged into computer, when you try booting from the internal emmc.
Just to make sure this is not confusing the boot process, looking on the wrong drive.
Fossapup64 has a bug, that it sometimes looks on the wrong drive, if there is an external drive also there.

[boof]

what does ~TZ onwards mean pls, and why wasn't it originally included?

[bigpup]

Originally included by what?

That TZ is actually at the end of the linux line

It post as two lines instead of one single line.

I have no idea what the TZ= is

That is just what the entry is being made by installing the UEFI boot loader.

Got me wondering.
Best I have found is TZ= is some kind of time zone info.

Let's examine the TZ string for a city with daylight saving time

[America/New_York]
TZ=EST5EDT,M3.2.0/2,M11.1.0

[boof]

TZ is Time Zone, but M~ is an unknown..
no it's not working. i've separated out the mmc host driver [rtsx_pci_sdmmc.ko] to try to trick init into loading it first thing, but don't know where to put it, nor how. i worked out how to open edit and condense sfs files. independently of the OS.

the mmc drive cannot be read unless its driver is loaded prior. that, i think, is the problem. init doesbnot do that by default on this type of drive, for an unknownreason. i have changed the bootborder to internal drive first, thrn usb, so if it is correct, it will boot from the int drive. it's a much faster boot, so i will know when it's happened. iff i could boot from the usb and transfer to the internal drive, i could then edit the module loading order, and fix it. this would require an early loading of the driver to enable handover, which i will now try to do. having only just thought of it. i'll report back soon.

[boof]

no, didn't work. no switchover. accelerated 3 rtsx components, inc mc.