Chromebook (How to use and put Puppy on a Chromebook)

Message

enrique · #61 Post by **enrique** » Mon 13 Apr 2020, 06:37

vtpup

You started with Acer R11 Chromebook. I guess you put it aside.

Now you bought an Acer C720-2844 Chromebook. And from you explanation it worked with default BionicPup64. I mean installing with UEFI method explained.

I guess you got over all sound issues. Do you have all working?

Nice. Congratulation for your hard work.
enrique.

vtpup · #62 Post by **vtpup** » Mon 13 Apr 2020, 12:45

H enrique!

Yes, everything works on the C720, including sound. No, I haven't given up on the sound issue for the Acer R11. I think we need to try to solve these problems in general for Chromebooks to be able to use Puppy properly, and sound seems to be the main hang-up for other models. The R11 is also a very nice Chromebook - newer, faster, larger HD and more memory standard, it also features a touch screen, and the screen folds backwards completely and can be used as a tablet, or in tent position.

So far, there are two issues for the Acer R11 running BionicPup64. The first, a non-functioning keyboard, was solved by ozsouth by compiling a special kernel with pinctrl_cherryview module enabled and tpm disabled:

http://www.murga-linux.com/puppy/viewto ... 7a#1023784

But, I just noticed that the latest standard BionicPup64 kernel still does not create a working keyboard (pinctr_cherryview included?) I still have to substitute ozsouth's kernel in.

The second issue is lack of onboard audio. (as mentioned elsewhere, hardware workarounds exist -- USB soundcard and/or bluetooth speakers.)

Besides, I don't like to give up on a puzzle. Onboard audio SHOULD be able to work if it works in Chrome and GalliumOS -- it's just a matter of knowledge. I hope we can get that knowledge....

bigpup · #63 Post by **bigpup** » Mon 13 Apr 2020, 17:59

My HP 14 Chromebook is being big trouble to get setup with MrChromebox Full ROM install,

I finally got the write protect screw removed.
Had to drill it off.
They really torqued it down.

Well, I did find out why you do not buy cheap screw drivers!

Now, I have problems getting it to boot to something other than Chrome.
Funny thing is, it was not a problem for a few boots.
It still booted to Puppy and legacy boot setup was working.

I think my mistake was booting into Chrome to run the Mrchromebox firmware script.
Would not have been a problem, usually.
But Chrome started automatically, doing some kind of updates to Chrome.
Now chrome is giving error message that it is missing stuff.
Booting, using ctrl -L to get to a boot device selection screen, is broken.

So, now I got to get Chrome fixed and it's firmware working correctly.
What a big bunch of crap!

One step forward, 2 steps back!
Now I know why I do this stuff in a room with no windows.

vtpup · #64 Post by **vtpup** » Mon 13 Apr 2020, 20:10

Now if only they didn't try to lock a device OS down with a screw inside a cabinet, and then force you to open account with your personal phone number and email to even boot for the first time, and then force automatic software updates on you, things would be, uh....simpler!

Funny how closed an "open source" implementation can be.

vtpup · #65 Post by **vtpup** » Tue 14 Apr 2020, 03:13

I've reached an impasse trying to set up another distro, Tahrpup64 on the Acer C720-2844 Chromebook. It hangs most of the way through the boot. Still working on it.

vtpup · #66 Post by **vtpup** » Tue 14 Apr 2020, 21:27

bigpup, found this elsewhere on the forum:

Warning

Don’t fall into this trap. Whilst the Chromebook was under guarantee I did not want to void it by opening it up and permanently altering the coreboot/seabios programme so I therefore ran the machine without those permanent changes and pressed Ctrl + L whatever each time on booting. I was caught out when I eventually upgraded the memory and thought it a good idea to disconnect the battery during the procedure, but it then forgot my coreboot/seabios changes and I had to reinstall ChromeOS to so that I could permanently rewrite the Coreboot/seabios changes.

enrique · #67 Post by **enrique** » Wed 15 Apr 2020, 05:03

vtpup wrote:I've reached an impasse trying to set up another distro, Tahrpup64 on the Acer C720-2844 Chromebook. It hangs most of the way through the boot. Still working on it.

Some time when we used old Puppy we wrongly cross a dead line.
What may happen is that the drivers or even firmware required by your device where not available at the time that particular OLD Puppy was build.

So 1rst suggestion, add new working firmware to old Puppy.

If that does not work then you can always try and see if you can run old Puppy using new working kernel from BionicPup. Many time OS will forgive you and allow you to use different kernel. Now you may expect a few apps to fail, as the apps may have features particular to certain kernel. Example in Ubuntu systemd may be required or similar new or old kernel service implementation.

And the more professional way, to find a "backported" kernel. But it is not always available and building your own backport drivers is a little tricky.

Good luck
enrique

vtpup · #68 Post by **vtpup** » Wed 15 Apr 2020, 13:06

Yes, I'll try the BionicPup64 kernel in Tahrpup64 tomorrow on the Acer C720. My daughter is using it today, and I'm working on the Acer R11 issues now.

Speaking of that, enrique, I have also read that the 5.2 kernel (and later) have the audio patches for the Acer R11 Chromebook onboard. Unfortunately latest huge Puppy kernel is still 4 series, I think.

rockedge · #69 Post by **rockedge** » Wed 15 Apr 2020, 16:16

Hello vtpup!

Unfortunately latest huge Puppy kernel is still 4 series, I think.

not true at all. I built a few 5 series for Puppy....and if one looks around some others have constructed even newer ones.....

which one do you want to try? Possibly whip together for you or show you how to build your own!

Puppy Linux kernels -> https://rockedge.org/kernels/

enrique · #70 Post by **enrique** » Wed 15 Apr 2020, 16:25

Many have post, but at the moment bigpup & you are at the front of Puppy Chromebook development. I am sure bigpup have works with kernels. But I strongly suggest you to start learning to build your own kernels.

Becoming an expert in kernel may look unreachable. Yes to many factors.

But Puppy had make the process of building it simple. Look at what I say. You may not produce the correct one, but you and anyone can build the evil thing. It only requires some Linux HDD Space and 1-2 hours in time depending on the kernel amount of drivers we build. There are ways to accelerate the process to 20 minutes by using ccache when you are just rebuilding same kernel. Or in cases that you know what driver you are adding it requires only a few minutes.

I build this simple procedure for fabrice_035 to see the process himself. http://murga-linux.com/puppy/viewtopic. ... 50#1055450

I already told you, on Android we did this process over and over. Chromebooks are no different. You have to start with Chromebook own kernel. Need to identify all drive modules been used in working Chromebook and or any other Linux OS you may find it works. Then next step is to try to activate all those needed on a New Kernel Source. Copying Chromebook firmware and blobs. Then the hard part is finding configures hidden on the Chromebook that set-ups the different devices. That how we did it in Cianogenmod, etc.

I did my 1rst ever success hardware help in this forum. fabrice_035 got the backlight working on today. But that was and easy lucky sample. As even when fabrice_035 did not posted BarryK's EasyOS results. I did in fact found lost on info in the net. Making easy to identify witch config in the kernel where needed. Well we have to thanks ozsouth for the final working kernel build. As mine seems to had a missing set up. Good catch ozsouth.

Edit:
While I was posting rockedge post similar sugestions. See learn it you will not regrete. I guess you can try 1rst any of the sugested kernels, it will be faster. Good luck.

vtpup · #71 Post by **vtpup** » Wed 15 Apr 2020, 19:00

Well, gee, rockedge and enrique, I'd like to do both: get a prebuilt working huge 5.2 kernel for the Acer R11 to try out if you have one available, AND learn how to compile a kernel myself!

*****************************************************************

In other news have found a flaw in the otherwise fine functioning Acer C720 on Bionicpup64:

We tried to Zoom with it this morning, but the microphone doesn't work.

So yes, audio does work OTB........ but not fully.

bigpup · #72 Post by **bigpup** » Thu 16 Apr 2020, 01:27

My HP 14 Chromebook followup.

Happy, Happy, Happy!!!!!!

No longer a Cromebook, but a full featured Puppy Linux laptop.
Well, almost there. Still sound problems

1. After drilling out the stuck write protect screw.
2. Fixing my broken ChromeOS boot loader by doing a full ChromeOS recovery.
3. Running the mrchromebox.tech Firmware Utility Script, replacing the Chromebook firmware(bios) with mrchromebox Full ROM firmware.
4. For now, I had a mico SD card with several Puppies on it.
5. Using Frugalpup Installer to install a UEFI boot loader on the micro SD.
6. Boots to the mrchromebox full firmware.
Select from it's menu the SD card.
Get boot menu on SD card to select what Puppy to boot.
Typing from it now.

Later I will re-partition and format the internal SSD and also use it.
Just wanted to first see if the mrchromebox Full ROM firmware is working OK.

Note:
After all the problems this gave me.
I now have some good tips on fixing problems or avoiding problems.

I will put something together and post the info.

bigpup · #73 Post by **bigpup** » Thu 16 Apr 2020, 01:40

A kernel that will just work on any Chromebook and have everything working is probably not possible.

There are just to many different Chromebooks.
There hardware setups are just all over the place.

However, the config, that is done when the kernel is compiled, can get the kernel setup to activate hardware as it finds it.
One of my problems was the hardware support is in the kernel, but not set to activate the hardware.
Changed that config setting and hardware is now active.

I wish someone would come along that has worked on Chromebook kernels.
They would probably easily get us a kernel.

bigpup · #74 Post by **bigpup** » Thu 16 Apr 2020, 02:23

peebee is testing this kernel for his Puppy versions.
http://www.smokey01.com/peebee/download ... 64.tar.bz2

I am trying this in Bionicpup64 8.0

You also have to install an fdrv.sfs
What fdrv do I need to use with this kernel?
I am using the larger one.

Small: https://sourceforge.net/projects/lxpup/ ... s/download

Large: http://www.fishprogs.software/puppy/firmware-sfs/

Change there names to reflect the names used in Bionicpup64 8.0 frugal installs.

vtpup · #75 Post by **vtpup** » Thu 16 Apr 2020, 04:21

Really glad you got your Chromebook sorted bigpup!

**********************

hardware:

I got a second C720-2844 in mail today, but developer mode was locked out "by owner" (probably a school/enterprise). Google enforces that. I figured out a way to defeat that -- took a couple hours of research and experiment, but I cracked it, got to developer mode, then downloaded Mr Chromebox onto it. Phew!

*****************

software:

I tried to insert rockedge's 5.3 huge kernel into Bionicpup64, but didn't get a successful boot. I'm definitely stabbing in the dark here!

rockedge, if you're following tis, since the 5.3 kernel is labeled for Bionicpup, do you have an already-built 5.3 kerneled Bionicpup64 iso?

bigpup · #76 Post by **bigpup** » Thu 16 Apr 2020, 10:26

Did you do the kernel change using Quickpet->Info->Change kernel?
All entries, in the change kernel program, are the stuff from the new kernel.

The info statements, are a little confusing, in that change kernel program.
Only input stuff from the new kernel.

bigpup · #77 Post by **bigpup** » Thu 16 Apr 2020, 10:37

Mrchromebox says their Full ROM Firmware requires the use of a 64bit operating system only.

But, I am running a 32bit Puppy right now.
I am using the UEFI boot loader that Frugalpup Installer will install.
So, seems this boot loader will boot a 32bit or 64bit Puppy version.

vtpup · #78 Post by **vtpup** » Thu 16 Apr 2020, 14:37

bigpup wrote:Did you do the kernel change using Quickpet->Info->Change kernel?
All entries, in the change kernel program, are the stuff from the new kernel.

No, bigpup, I just tried unpacked kernel, repacked the xxx.initrd file to gz, changed names to vmlinuz and initrd.gz and substituted in on a working frugal Bionicpup64 (on my main laptop). Forgot to substitute a new zdrv, which was one obvious major problem.

bigpup wrote:But, I am running a 32bit Puppy right now.
I am using the UEFI boot loader that Frugalpup Installer will install.
So, seems this boot loader will boot a 32bit or 64bit Puppy version.

Interesting!

vtpup · #79 Post by **vtpup** » Thu 16 Apr 2020, 17:23

Sure enough, Bionicpup32 when put on a stick using full Frugalpup 20, and choosing BOTH UEFI and grub, does load right up on the Acer C720!

But if you choose UEFI only in Frugalpup, it doesn't work.

bigpup · #80 Post by **bigpup** » Thu 16 Apr 2020, 19:21

You know, you are right.
I do seem to have both boot loaders installed by Frugalpup. I thought I only installed the UEFI one.

I am testing with too many drives.
Forgetting what I have actually put on each one.

These Chromebooks are in their own computer world.

What works or does not work, is all over the place.
Frugalpup Installer seems to provide some needed boot loader options.

Nothing seems to be 100% for all Chromebooks.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Chromebook (How to use and put Puppy on a Chromebook)