Chromebooks (Run and install Puppy)

[wizard]

@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

[wizard]

@don570

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

soundcardwiz.jpg (24.52 KiB) Viewed 2867 times

alsawiz.jpg (32.48 KiB) Viewed 2867 times

wizard

[bigpup]

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.

[don570]

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

[wizard]

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 /

tp11e_cb.pet

(47.57 KiB) Downloaded 74 times

-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

[bigpup]

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.

[wizard]

@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

[williwaw]

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?

[wizard]

@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

[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

[rcrsn51]

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.

[Clarity]

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

[dancytron]

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.

Code: Select all

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.

Code: Select all

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

[dancytron]

Surprisingly, it boots to SD card too.

edit:

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

[trawglodyte]

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.

Screenshot(2).png (44.99 KiB) Viewed 748 times

[wizard]

@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

[dancytron]

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.

Code: Select all

*** 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.

[dancytron]

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.

PuppyScrcpy-800.jpg (87.03 KiB) Viewed 603 times

[dancytron]

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.

[BenBooth1344]

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

[dancytron]

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.

[bigpup]

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.

[wizard]

@dancytron

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

wizard

[dancytron]

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.

[bigpup]

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.

[dancytron]

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.

[rcrsn51]

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.

[dancytron]

I did it.

Everything is fine.

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