Puppy Linux Discussion Forum

Not what you wanted to hear, you said you tried it.

I just booted F96-CE_4 from a Frugal install on my Chromebook internal emmc drive.

Used Frugalpup Install to do the frugal install.
Installed the UEFI boot loader provided by Frugalpup Installer.

So that is one normal Puppy version that is working for me.

@bigpup

I've tried Fossapup64 9.5 and F96ce_4 installed with Frugalpup and also tried using grub2config to install the boot loader. So far none can find the Puppy main file on boot.

Just as another point of reference, it gives the same error with Fossapup64 9.5 when trying to boot from a sd card.

Thanks
wizard

I believe that FossaPup is a separate issue. A number of Puppies from that generation had trouble with emmc drives, including on non-Chromebooks.

But it's a mystery why BookwormPup cannot find the emmc drive on this particular Chromebook. The emmc problem should be solved in its initrd.

Have you tried the Starter Kit?

Do you have output of lsmod and dmesg from any distro that recognizes the MMC drive? (doesn't matter if booted from MMC or not)

This could be a missing driver that gets loaded too late in the boot process, it's easy to fix once we know which one it is.

@rcrsn51

Have not, but will try Starter KIt

@dimkr

booted BW64 from USB, here are outputs

Thanks
wizard

@wizard Does the eMMC device disappear after rmmod dw_dmac? I'm not sure if this is the missing driver.

@dimkr

After rmmod dw_dmac I can still mount the eMMC

Thanks
wizard

"Just as another point of reference, it gives the same error with Fossapup64 9.5 when trying to boot from a sd card."

Anyway I dont use pdev even in this case I dont use pdrv/pmedia/pfix in cfg.
This is my config of grub SD-card for F96 and Bookworm. It tested and no boot error.

menuentry 'F96-CE_4'{
search --no-floppy --set=root --fs-uuid cced0de5-0630-43dd-9657-9d0cefde9f8a
linux /F964/vmlinuz psubdir=/F964 psave=L:/F964
initrd /F964/initrd.gz
}
menuentry 'Bookworm Pup64 10.0'{
search --no-floppy --set=root --fs-uuid cced0de5-0630-43dd-9657-9d0cefde9f8a
linux /bworm/vmlinuz psubdir=/bworm psave=L:/bworm
initrd /bworm/initrd.gz
}

@rcrsn51

Downloaded DebLive_daedalus-6109-amd64.iso and used Multi-installer to install to the eMMC per your instructions.
Good news is it will boot from the eMMC.

Thanks
wizard

What we now need is someone else with a Baytrail Chromebook to report whether they can boot BookwormPup.

People need to identify their Chromebook model, CPU and/or Chrome ID name,

rcrsn51 wrote: ↑Mon Aug 07, 2023 9:50 pm

What we now need is someone else with a Baytrail Chromebook to report whether they can boot BookwormPup.

This is disappointing. I was hoping that there are other Puppy users with converted Baytrail Chromebooks who could help.

I have owned Baytrails in the past but they are long-gone. FWIW, they could always boot the Starter Kit.

@rcrsn51

Looks like no one else on the forum has one up and running. Otherwise, BW64-10 works great (booting from USB) on my Thinkpad 11e Chromebook OOTB.

One other thing you might find interesting:
-eMMC is internal drive
-added entry to Starter KIt Grub to boot BW64 from USB = worked fine
Since I wanted to experiment with MX-linux, I figured I could do the same thing.
-installed MX-linux to eMMC
-added entry to MX-linux Grub to boot BW64 from USB = nope can't find USB

Seems MX-linux Grub doesn't load/mount the USB during boot.

It's always something.
Not really worth spending more time on it.

Thanks
wizard

rcrsn51 wrote: ↑Mon Aug 07, 2023 9:50 pm

What we now need is someone else with a Baytrail Chromebook to report whether they can boot BookwormPup.

People need to identify their Chromebook model, CPU and/or Chrome ID name,

I have one with a Baytrail CPU, but it is using a different motherboard than wizzard's Chromebook.

BookwormPup64 will not boot from internal emmc drive install.

F96-CE_4 will boot from emmc drive install.

My Chromebook is using a very old version of the mrchrombox.tech firmware.

Have been trying to get the newest version of the firmware to see if that would make any difference.
However, having problems getting the firmware script to download and install the newest version.
Keep getting error the check sum not good, on the firmware file, it is trying to download, from their web site.

Could be trying to do this using Puppy Linux to run their script.
When I first did it a few years ago.
I had to run Ubuntu Linux and run the script in it.

Again I just put all the Puppy frugal installs on a micro SD card and boot from it.
Use the internal emmc drive for storage.

There are so many different Chromebooks and none of them work exactly the same way.

I am just thankful mrchromebox provides a firmware, that can turn it into a normal computer UEFI boot process.

It's always something.

Sure is

this is a painstaking effort to do grab a usb memory card reader ok:
it should theoretically work if you instance puppylinux to the emmc drive and tell you if your flash drive is working
not flash drive as in emmc but you can use that also its the well it says here its not like a tablets nand
its not like a sata ssd its a memory card iterface over i2c or something like that is strictly in the kernel configuration
and ive only gotten it to work once or twice with gentoo now im trying to do it with OpenSUSE:
they all may use the same driver coming from shenzen china as would call it:
so once i have the right driver ill throw it on here:
then again i think somewhere along the line i already have***
meaning as i posted it i wrote though i already have *** #BLOWNOPEN: street lurkers installing SUSE 5: