Puppy Linux Discussion Forum

@don570

Don't have any experience with fatdog. Did you get the pet converted? The pet has to install the Intel drivers, alsa configuration files and some shell scripts in order for it to work. Also in fossa64 9.5 it required a kernel swap.

wizard

@don570

Here are alsawizard & alsamixer windows in fossa64 9.5. hdmi did not work.

wizard

Did you do this?

Note about Linux kernel:
The kernel has to be configured for activating the sound device in the Chromebook.
This is a kernel compiled, that hopefully does this, for your sound device.
Linux kernel 5.4.27 (64bit)
Ubuntu Derivative Kernel here: https://archive.org/download/Puppy_Linu ... oz.tar.bz2
Slacko Derivative Kernel here: https://archive.org/download/Puppy_Linu ... oz.tar.bz2
fdrv here (rename to suit your system): https://archive.org/download/Puppy_Linu ... an2020.sfs

change_kernels (entered in a terminal) will run a program made for changing the kernel.

This special kernel was compiled and configured for ChromeBooks.
It does turn on a very large amount of possible settings for sound devices.
You do not need all of them, but it does take a little try it and see, changing of settings, in the ALSA mixer or Retrovol Mixer, to get the correct settings selected.

Note:
The config for this kernel was done, kind of guessing, what may be needed activated.
But it will have what is needed turned on.
Wish someone that has worked on a ChromeBook kernel, could maybe give us a more polished kernel.

I noticed that the SOF project requires kernel 5.2
viewtopic.php?p=42764#p42764
__________________________________________

EDIT 9/11/23: The newer Bookworm Pup64 that works OOTB is a better Puppy for the Thinkpad 11e (this post shows how to get Fossapup64 9.5 working)

This Chromebook was school surplus purchased on Ebay. It is well made with an above average keyboard and makes a good Puppy notebook.

This procedure sets up a dual boot chromeos/puppy and does not require opening
the computer or disabling the write protect. It may also work on other intel
chromebooks with the chtmax98090 sound chip

Hardware:
Thinkpad 11e (Baytrail/Glimmer) MPN: 20DB-S03L00 from 2014-2015
CPU= Intel N2930 quad core
RAM= 4gb
SSD= 16gb
sound= chtmax98090

Recommend using a USB external mouse to make copy/paste into terminal easier.

The setup will be in two parts, TP-11e setup and Puppy USB setup

1. TP-11e setup
-boot enabling developer mode on the Chromebook (refresh is 4th button from left on top row)
-- press and hold the esc refresh power buttons at once.
-- press: ctrl d
Wait for reboot
-Browse as Guest
--press: ctrl alt t (opens a terminal in Chrome)
---type: shell
---press: enter
-open a new Chrome tab
--navigate to mrchromebox.tech, Firmware Utility Script (https://mrchromebox.tech/#fwscript)
-install seabios
--copy this line from the web page (highlight then press ctrl c):
cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh

-paste into the terminal by pressing the touchpad with two fingers
-press: enter
-choose: 1) RW_LEGACY Firmware
-choose: Default to booting from USB = y
-press: enter
-press: p
-press: enter
The TP-11e setup complete

2. Puppy USB setup (using another Puppy computer)
-create fossa64 9.5 bootable usb using menu>setup>Stickpup
-download: huge-5.4.27-ubun64oz.tar.bz2 https://archive.org/download/Puppy_Linu ... oz.tar.bz2
-copy huge-5.4.27-ubun64oz.tar.bz2 to USB /
-download https://archive.org/download/Puppy_Linu ... an2020.sfs
-rename fdrv_jan2020.sfs to fdrv_fossapup64_9.5.sfs and copy into your USB Puppy directory
-download: tp11e_cb.pet and copy tp11e_cb.pet to USB /

-shutdown

Insert USB into TP-11e and boot
-on 1st screen, press: ctrl l (lower case L)
-reboot and create your savefile
-using Rox, navigate to /mnt/home and click tp11e_cb.pet to install
-switch kernel to: /mnt/home/huge-5.4.27-ubun64oz.tar.bz2
--menu>quickpet fossa>change kernel
-reboot
The Puppy USB setup is complete

NOTES:
The TP-11e sound did not work when using previous setup methods. Sound did work in Gallium Linux, so the solution was to copy these directories from Gallium to Puppy:
-/var/lib/alsa
-/usr/share/alsa
-/usr/share/alsa-base
The tp11e_cb.pet installs those files for you.

Internet setup, Frisbee was more reliable than SNS, YMMV

The volume control in the jwm tray does not work.
You will need to use alsamixer for both speaker and headphone volume control (Menu>Multimedia>Alsa Sound Mixer)
EDIT 7/8/23
See this post for how to add an alsamixer icon to the right side of the JWM tray:
viewtopic.php?t=9103

Other files installed:
-/root/my-applications/bin/alsamixer.sh
-/usr/share/applications/alsamixer.desktop
These two files give you the Menu>Multimedia>Alsa Sound Mixer entry. Up/down arrow keys to adjust volume, right/left to select device. You can put a symlink on your desktop or in the tray for convenience.

Plugging in the headphones does not automatically mute the speakers.
-/root/my-applications/bin/speaker_toggle.sh
-/usr/share/applications/speaker_toggle.desktop
These two files give you the Menu>Multimedia>Speaker toggle entry to mute/unmute the speaker

-/root/Startup/alsarestore.sh = restarts sound during boot

-/root/my-documents/keyboard.txt = notes about chromebook F keys

Not Working:
-on board sdcard slot was not bootable.

The USB used was a SanDisk Ultra Fit 32gb (very small stick out from case), but any USB 2gb or larger should work.

wizard

SD card not able to boot.

If the SD card reader is working OK.

When you did this you set it to USB booting.

-paste into the terminal by pressing the touchpad with two fingers
-press: enter
-choose: 1) RW_LEGACY Firmware
-choose: Default to booting from USB = y
-press: enter
-press: p
-press: enter
The TP-11e setup complete

From MrChromebox.tech

After setting the Boot Options / GBB flags, the boot timeout and default OS will be whatever you selected, and can be changed at any time by re-running this script function.

Are you trying to boot from the SD card with no USB drives plugged in?
If the SD card is seen as a USB device.
It needs to be the only USB drive plugged in when you boot.

For sure it will be able to boot from SD card if you change to using The (UEFI) Full ROM firmware from MrChromebox.
This firmware gives you many more options.
But like my Chromebook, you will need to open the laptop case and find the disable the firmware write-protect (usually a screw you remove from the motherboard).
A web search. Should be able to find specific information on how to remove the screw to disable the firmware write-protect on your specific computer.

After using Puppy Linux.
You will never want to use ChromeOS and there is no reason to want to use it.

@bigpup

Are you trying to boot from the SD card with no USB drives plugged in?
If the SD card is seen as a USB device.
It needs to be the only USB drive plugged in when you boot.

Only had sdcard plugged in (confirmed bootable on another computer). On my dual boot config it is not seen as a USB. It would boot to grub menu, then error with failed to find puppy_fossapup64_9.5.sfs. Not a big issue since USB works well.

Thanks
wizard

wizard wrote: ↑Tue May 10, 2022 2:36 pm

This Chromebook was school surplus purchased on Ebay. It is well made with an above average keyboard and makes a good Puppy notebook.

This procedure sets up a dual boot chromeos/puppy and does not require opening
the computer or disabling the write protect. It may also work on other intel
chromebooks with the chtmax98090 sound chip

Hardware:
Thinkpad 11e (Baytrail/Glimmer) MPN: 20DB-S03L00 from 2014-2015
CPU= Intel N2930 quad core
RAM= 4gb
SSD= 16gb
sound= chtmax98090

Recommend using a USB external mouse to make copy/paste into terminal easier.

The setup will be in two parts, TP-11e setup and Puppy USB setup

1. TP-11e setup
-boot enabling developer mode on the Chromebook (refresh is 4th button from left on top row)
-- press and hold the esc refresh power buttons at once.
-- press: ctrl d
Wait for reboot
-Browse as Guest
--press: ctrl alt t (opens a terminal in Chrome)
---type: shell
---press: enter
-open a new Chrome tab
--navigate to mrchromebox.tech, Firmware Utility Script (https://mrchromebox.tech/#fwscript)
-install seabios
--copy this line from the web page (highlight then press ctrl c):
cd; curl -LO mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh

-paste into the terminal by pressing the touchpad with two fingers
-press: enter
-choose: 1) RW_LEGACY Firmware
-choose: Default to booting from USB = y
-press: enter
-press: p
-press: enter
The TP-11e setup complete

2. Puppy USB setup (using another Puppy computer)
-create fossa64 9.5 bootable usb using menu>setup>Stickpup
-download: huge-5.4.27-ubun64oz.tar.bz2 https://archive.org/download/Puppy_Linu ... oz.tar.bz2
-copy huge-5.4.27-ubun64oz.tar.bz2 to USB /
-download https://archive.org/download/Puppy_Linu ... an2020.sfs
-rename fdrv_jan2020.sfs to fdrv_fossapup64_9.5.sfs and copy into your USB Puppy directory
-download: tp11e_cb.pet and copy tp11e_cb.pet to USB /
tp11e_cb.pet
-shutdown

Insert USB into TP-11e and boot
-on 1st screen, press: ctrl l (lower case L)
-reboot and create your savefile
-using Rox, navigate to /mnt/home and click tp11e_cb.pet to install
-switch kernel to: /mnt/home/huge-5.4.27-ubun64oz.tar.bz2
--menu>quickpet fossa>change kernel
-reboot
The Puppy USB setup is complete

NOTES:
The TP-11e sound did not work when using previous setup methods. Sound did work in Gallium Linux, so the solution was to copy these directories from Gallium to Puppy:
-/var/lib/alsa
-/usr/share/alsa
-/usr/share/alsa-base
The tp11e_cb.pet installs those files for you.

Internet setup, Frisbee was more reliable than SNS, YMMV

The volume control in the jwm tray does not work.
You will need to use alsamixer for both speaker and headphone volume control (Menu>Multimedia>Alsa Sound Mixer)

Other files installed:
-/root/my-applications/bin/alsamixer.sh
-/usr/share/applications/alsamixer.desktop
These two files give you the Menu>Multimedia>Alsa Sound Mixer entry. Up/down arrow keys to adjust volume, right/left to select device. You can put a symlink on your desktop or in the tray for conveinience.

Plugging in the headphones does not automatically mute the speakers.
-/root/my-applications/bin/speaker_toggle.sh
-/usr/share/applications/speaker_toggle.desktop
These two files give you the Menu>Multimedia>Speaker toggle entry to mute/unmute the speaker

-/root/Startup/alsarestore.sh = restarts sound during boot

-/root/my-documents/keyboard.txt = notes about chromebook F keys

Not Working:
-on board sdcard slot was not bootable.

The USB used was a SanDisk Ultra Fit 32gb (very small stick out from case), but any USB 2gb or larger should work.

wizard

Hi wiz

is this TP-11e with the mrchromebox script your most recent conversion?

@williwaw

Hi will, that looks like it, just the stuff above Notes: needs to be done, the Notes: are just background info. Think it's pretty complete, if you find an issue let me know.

wizard

The mrchromebox.tech site has long been the "goto" to install the Seabios modification needed to boot old Chromebooks from a USB flash. Once installed you can boot Linux, etc. There are two types of modification:

1. RW Legacy - this was the easiest, did not require disabling the write protect and allowed dual boot with the existing ChromeOS.
2. UEFI (full rom) - this requires disabling the write protect (usually opening the case and removing a screw). It completely disables the ChromeOS, it also allows reformatting the internal drive for other uses if desired.

Unfortunately, most manufactures made access to the write protect screw difficult (for obvious reasons).

The sad news is mrchromebox has made the decision to no longer offer RW Legacy installs for Chromebooks that have reached Googles end-of-life (EOL).

The net result is thousands of existing Chromebooks are now much harder to convert since you can only do a UEFI (full rom) modification.

Makes little sense to me to withdraw what was a easy and working modification.

wizard

I don't see this as a big problem. There are lots of YouTube videos showing how to open the case and locate the WP screw.

For newer models, it's easier - just open the case and unplug the battery. That temporarily removes write protection so you can install the new firmware.

This is a new video from the authors of the BIOS/UEFI replacement firmware which enables the ability to load PUPs/DOGs/MLs (forum distros) on Chromebooks. The video is key to suggest ('recommend') which Chromebooks to use and which to stay away from.

I thought this was a excellent presentation giving the understanding of their directions as they navigate the field of manufacturers.

Enjoy

I bought a Lenovo Chromebook 11e Gen 3. $32 on ebay. Not the cool one that folds all the way into a tablet. The other one.

With @wizard's help, I've gotten it set up to usb boot Bookworm Puppy 64 and MX so far with stock Debian bookworm kernels.

So, mrchromebox.tech the author of all the firmware to run linux on chromebooks decided not to support usb boot because [reasons] and took down the firmware. Luckily, someone saved it and put it up at https://chromebook.bitejia.tech:8443/chromebox-old/

So basically follow the instructions at https://mrchromebox.tech/#fwscript except run the script on the new website. I broke it into 2 pieces to I could look at the file it downloads 1st.

Note you have to do the "this script must be run from a VT2 terminal (from login screen: CTRL+ALT+F2, login 'chronos');" instead of <control><alt><T> regular terminal like for some older models.

cd; curl -LOk https://chromebook.bitejia.tech:8443/chromebox-old/firmware-util.sh

Then after that ran without error and I checked the file was really there instead of an http error.

sudo bash firmware-util.sh

Then just follow the prompts and instructions on MrChromebox's website as if "legacy" usb boot was still supported.

After that, you need a legacy grub usb boot disk, not uefi. I used Bill's @rcrsn51 Debian Dog Starter Kit method to create a grub2 legacy boot disk for Puppy and MX, but I assume any "legacy" style boot disk should work.

https://forum.puppylinux.com/viewtopic.php?p=3615#p3615

The alternative to usb boot is to take the laptop apart to remove a "write protect" screw and then blow away the no longer updated Chrome OS (which runs my favorite Android map program) and install linux to the 16 gig internal drive.

--Dan

Surprisingly, it boots to SD card too.

edit:

Another source for the MrChromebox legacy scripts. https://github.com/OtterCodes101/rw_legacy-eol

wizard wrote: ↑Tue Sep 21, 2021 6:48 pm

no sound. Here are sound devices:

Screenshot.jpg
.

Did you wind up getting this solved? I have a similar thing with my NVIDIA sound options (which I don't ever use on this machine). This may not solve your problem, but it will make it easier to pinpoint. You can blacklist snd_hda_intel module and make all those options disappear. (This assumes your other card doesn't use snd_hda_intel module) Mine uses snd_usb_audio module.

@trawglodyte

I have two Chromebook models, a Acer CB3-431 and Lenovo Thinkpad 11e. When I first got them I was booting FossaPup64 9.5 and had the most problem with sound. I did resolve both and you can find details in my post in this topic. When radky released BookwormPup64 it worked on both of these Chromebook models without any tweaking.

wizard

The microphone doesn't work on my Lenovo 11e 3rd gen. Both Bookworm Puppy and MX linux.

Apparently this is a known issue.

It works in ChromeOS. I discovered it wasn't working when I was trying to make sure it was off by default, so I'm not too worried about it.

*** List of CAPTURE Hardware Devices ****
card 1: chtrt5650 [chtrt5650], device 0: 3 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Edit: I also can't seem to see the cpu temp.

I guess I should get as much milaege as I can out of this screenshot.

This is Bookworm puppy running on my Lenovo 11e gen 3 with scrcpy running.

MX runs fine too.

More chromebook testing.

It's remastering an MX install now. It almost immediately throttled down to 30% or so cpu, but shows no signs at all of being hot my old laptop would.

Debian dog Bookworm booted to the desktop and everything seems to work but the sound.

edit: another quirk, if you set MX to turn off the display but not suspend when you close the lid, it doesn't come back on and you have to reboot. Suspend works just fine though.

edit: You don't have to reboot. Just close it again, give it a couple of seconds, and then open it again.

Lenovo N22 REKS Chromebook working
BookwormPup64 iso (10.0.6)

Steps:
1) Follow steps here to completely install "Full ROM Firmware" https://mrchromebox.tech/#fwscript
2) Put BookwormPup64.iso on usb drive using Rufus (if on windows)
3) Boot from usb

No additional steps were needed

I have verified that these things work:
- keyboard
- trackpad
- audio
- wifi/internet
- usb keyboard/mouse
- usb flash drive

Just want to double check.

So if I do the "Powerwash" thing in ChromeOS to reset my ChromeOS back to the factory default, will that overwrite the Chromebox.tech legacy seabios firmware upgrade?

Lenovo Ultima gen 3 chromebook.

Your guess is as good as mine.

I would look on https://mrchromebox.tech/#fwscript

This seems to indicate the mrchromebox.tech firmware utility script would do it.

Maybe someone that has tried to do it will come along with better info.

Most people here changed to using Puppy Linux on their Chromebooks and do not want to go back.

@dancytron

Seems like "powerwash" only removes all the personal data and Google account info. Don't think it touches the bios.

wizard

bigpup wrote: ↑Sun May 05, 2024 4:33 am

Your guess is as good as mine.

I would look on https://mrchromebox.tech/#fwscript

This seems to indicate the mrchromebox.tech firmware utility script would do it.

Maybe someone that has tried to do it will come along with better info.

Most people here changed to using Puppy Linux on their Chromebooks and do not want to go back.

I'm usb booting MX, Bookworm Pup, and Debian Dog, so I still have Chrome OS on it.

If you used the mrchromebox.tech legacy seabios firmware.

You need to do what they say to do on their web site to remove it.

bigpup wrote: ↑Sun May 05, 2024 1:36 pm

If you used the mrchromebox.tech legacy seabios firmware.

You need to do what they say to do on their web site to remove it.

You misunderstand. I just want the Chrome OS that's still on there to be reset to the default. Mostly to get my main google id off of it. That way if someone steals it they don't get a computer with my google account on it. I'm still going to use MX and Puppy on usb or sd as my main OS.

Even if powerwashing reset the BIOS, it wouldn't be a big job to restore the SeaBIOS. And none of that would affect the stuff on your USB/SD drives.

I did it.

Everything is fine.

Along the way, there was an "update firmware" checkbox which I didn't check.

bigpup wrote: ↑Sun Aug 09, 2020 1:51 pm

How to remove Chrome OS and only use Puppy

Delete ChromeOS from internal drive and replace with a Puppy version.

There are so many different Chromebooks, that one method is probably not 100% works on all.
However, this general procedure will usually work.

These are the steps I took to modify an Acer C720-2844 Chromebook to become a Puppybook. Please note that this removes the Chrome operating system completely. Please also realize that this works specifically for this computer and model, and may not require the same steps, and or may not produce satisfactory results with any other Chromebook. My computer has 4GB of RAM memory and a 16GB SSD hard drive.

1.) I prepared a USB thumbdrive with a current (not updated) bootable Bionicpup64 installation. I added a current FrugalPup-20.shs puppy installer. This would be needed later when installing Puppy.

2.) I did a Startpage lookup for “C720 write protect screw” and found an online photo showing its location on the computer's motherboard. I removed all screws from the bottom of the computer's plastic case, and carefully worked the bottom loose by lightly prying out the edges..

3.) I removed the write protect screw, and re-attached the case with the screws.

4.) I booted the computer as a “guest” (I have never set up a Google acct on this box) then hit <CTRL> <ALT> <T> to open a terminal.

5.) To enter the shell I entered:

Code:
shell

6.) Before rewriting the ROM, I familiarized myself with the options explained at the mrchromebox.tech website. To download and run the Mr Chromebox configuration script I entered the following, (note -LO is capital letter O, not zero):
Code:
cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh

7.) I chose option 3, “Install/Update Full ROM Firmware”.

8.) I backed up the old firmware on separate USB drive when asked. When the script finished I exited.

9.) I booted the computer with the BionicPup64 USB drive (from step 1. above) attached, and hit <ESC> at the boot screen, then selected Boot Menu, and then selected the USB drive to initiate the boot. Puppy started up.

10.) I ran <Menu> <System> <Gparted> for device sda. I deleted every partition on the drive, one by one.

1. I clicked <Device> <Create Partition Table> and accepted the “msdos” default type (mbr).

2. I created a first new partition of 500Mb using a FAT32 type, named “BOOT”.

14.) When that was created, I right-clicked on the partition, then chose “flags” from the menu and then set the “boot” flag.

15.) I partitioned the rest of the drive as ext2 (because I wanted a non-journaling type to lengthen the life of the SSD drive. Likewise I didn't create a SWAP partition.

16.) I closed Gparted, and selected Install Puppy from the FrugalPup-20 installer menu. (Or depending on how you start the program you may have to run the Frugalpup installer by going to <Menu> <Setup> <Diskpup> ).

I entered the Puppy files source as “directory” and pointed to /mnt/home/bionicpup64 (the original files on the USB drive). (I believe you could also choose “This” from the menu to do the same thing.)

17.) I installed BionicPup64 to the second partition, in a new subdirectory I called “Bionicpup64”.
I also located the personal save folder as my new “Bionicpup64” subdirectory.

18.) After doing the Puppy install, I chose UEFI and to install the boot to UEFI on partition 1 (hda1).

19.) After all the questions were answered and the installation completed I re-booted, and the new puppy system started up correctly.

20.) After downloading several applications, I noticed that my trackpad started to lag and stick. I opened <menu> <setup> <Mouse/Keyboard Wizard> <Touchpad> and increased the sensitivity by moving the slider left (lower number) to 16, then saved it, The pointer now acts normally again.

WARNING:
This requires replacing the Chromebooks firmware(bios) with a full replacement firmware.
The one offered by mrchromebox.tech

Carefully follow all steps and procedures.

Note:
You will need to use a UEFI boot loader to boot any Puppy version.
Mrchromebox firmware only works with UEFI boot loaders.
Frugalpup Installer
viewtopic.php?f=105&t=337
This is the best Puppy installer to use.
It will install a UEFI boot loader.

Hi bigpup,

I got most of the way through these steps and was finally feeling some relief after the maze that was ArchLinux. Thank you for these very detailed steps!

I'm on a Banjo Chromebook, dead battery, kinda slow but otherwise running OK. So, Chrome OS has got to go. BionicPup64 runs great on this thing, but I wanted to make a full install so that I don't have to worry about carrying a USB with me.

I followed your steps very closely, and only diverted in the following areas:

• Step 1: I'm using BionicPup64 8.0 and FrugalPup-41.sfs flashed unto my USB with Rufus 4.5, which might differ from your original installation.
• Steps 2-8: Otherwise, got the full replacement firmware working fine, and tried some other distros before discovering BP64.
• Step 9: I was able to boot into BionicPup64 from USB. Really liking it so far. Noodled with the Quick Setup, Video Wizard, network setup, and other opening prompts for about an hour. Got Connect and PaleMoon to work.
• Step 10: Old Chrome OS partitions were already cleaned by ArchLinux, and then again by Absolute Linux, which I briefly tried before landing on BionicPup64
• Step 16: Here's where things got tricky. Was I right in clicking frugalpup_41.sfs > Install SFS > then its Installer Menus? I think I used "This" as the target for the full install. I think that was because when I tried pointing at the USB, it had some trouble finding what it needed. It was late last night, hard to recall. But in any case, both the "BOOT" (500M vfat with boot flag checked) and "nonjournal" (14.2G ext2) labeled partitions have good looking files inside them now. /boot, /EFI, crub.cfg, puppy.cer ... and BionicPup64/puppy_bionicpup64_8.0.sfs, vmlinuz, initrd.gz look like the important stuff.
• Step 17: I called my subdirectory for the saved data /BionicPup64 on the nonjournal partition. The boot logs that you'll see later agree that's what it's looking for.
• Step 18: I chose to install UEFI with x64-only on the "BOOT" partition.
• Step 19: I stored my session as a puppysave directory (with my timezone settings, network settings, etc, about an hour's work flubbing around) on the nonjournal partition as /bionicpup64save. Didn't see this coming so hopefully I didn't make a mistake.

So far so good, I thought. I was pretty confident that I was done at about midnight.

Then I rebooted, held ESC, and pulled the USB once I reached the boot menu. Then I tried booting from the disk. But I found that it doesn't seem to mount my new partitions on boot like I would have expected, so it cannot find the puppy sfs on disk. Coming from a .gov Red Hat background where most of the filesystem stuff should Never Be Touched, I must be doing something silly here.

After booting from the USB again (now without my puppysave, it's trapped in the nonjournal cage D:), I found that pMount has a right-click menu option for each partition where you can set it to "Mount partition at boot." Is that what I need? How can I set that in something like grub.cfg so that I can get past the below error when booting from the disk?

*** bionicpup64 8.0 - Linux 4.19.23 [x86_64] ***
Waiting for USB storage.....                                             done
Finding puppy main sfs file.                                             failed
Dumping last lines of /tmp/bootinit.log...
 - 1 - 2 - 3 - 4
2: ONE_PART= ONE_FN= ONE_MP=
Partition nonjournal not found.
6: ONE_PART=nonjournal ONE_TRY= PDRV=
Dumping last lines of kernel log...
usb 1-3: Manufacturer: Chicony Electronics Co.,Ltd.
usb 1-4: new full-speed USB device number 4 using xhci_hcd
usb 1-4: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
*** nonjournal /BionicPup64/puppy_bionicpup64_8.0.sfs not found.
*** Error is too critical, dropping out to console...

dancytron wrote: ↑Sun Feb 04, 2024 7:30 pm

I bought a Lenovo Chromebook 11e Gen 3. $32 on ebay. Not the cool one that folds all the way into a tablet. The other one.
Note you have to do the "this script must be run from a VT2 terminal (from login screen: CTRL+ALT+F2, login 'chronos');" instead of <control><alt><T> regular terminal like for some older models.

My HP Chromebook 11 G5 EE has no Fn keys,
I saw Lenovo Chromebook 11e also has no Fn keys.
How do you do CTRL+ALT+F2 ?