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

[bigpup]

If you use the change kernel in Quickpet.

As long as you put the correct type of file, from the new kernel package, into the correct entry slots.
The names will get auto changed, to the correct names, used by the Bionicpup frugal install.
They will replace the original files with the new kernel ones.

Unpack the kernel .tar.gz package.
drag and drop the correct files into change kernel program window.

[vtpup]

I did that today Bigpup with the 5.5.13 kernel and Bionicpup64, and then got it on a bootable stick, and ran it on both the C720 and R11.

I noticed that kernel modules is tiny in comparison with the original Bionicpup64 version. I lost wifi and touchpad function on the R11. (needs pinctrl_cherryview, compiled in at kernel time for a functioning touchpad, as usual). That kernel modules piece looks to be pretty slim.

I think rockedges much larger 5.3.18 kernel modules package looks like a better possibliity. Might try that a little later (my eyes are bleary from trading OS'es around all day on about 5 thumbdrives)

[ozsouth]

@vtpup - I've just released a 5.4.27 kernel which has pinctrl_cherryview=y. Check out the ubuntu deriv version:
http://www.murga-linux.com/puppy/viewto ... 53#1055653. Also needs fdrv shown there.

[vtpup]

Great, thanks ozsouth! Will do shortly.

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

In other news, the rockedge 5.3.18 kernel placed into Bionicpup frugal would not boot on my main laptop -- error messages saying it couldn't read partitions. So I couldn't make a stick. Maybe it needed a different fdrv, as well? I only did the change kernels GUI script method with the two tarred files into the existing frugal directory and rebooted.

[vtpup]

@vtpup - I've just released a 5.4.27 kernel which has pinctrl_cherryview=y. Check out the ubuntu deriv version:
http://www.murga-linux.com/puppy/viewto ... 53#1055653. Also needs fdrv shown there.

No joy...... kernel panicked:

"Wrong EFI Loader signature........

(don't think I have EFI on this lappy)

There was no fdrv to start, I renamed yours per below:

Screenshots of directory and Grub stanza:

[vtpup]

Okay, took out the microcode bit in Grub and it booted up..... fingers crossed.....

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

Later:

Looks promising, ozsouth....made a USB stick, booted right up in the R11. Touchpad works, wifi works, even touch screen works, nice!

Audio doesn't work, but..... there are now what look like a hundred sliders and switches in retrovol. It looks like the card type is recognized.

I also remember that in GalliumOS dev notes online there is somewhere a specific ALSA config for these Braswell CYAN Chromebooks. I'm going to look for that....

[vtpup]

I think I need pulseaudio. Specifically I need it to respond to a configuration file: /etc/pulse/default.pa taken from GalliumOS.

Even more specifically I need it to respond to these lines in that file:

Code: Select all

set-default-sink   alsa_output.platform-cht-bsw-max98090.HiFi__hw_chtmax98090__sink
set-sink-port      alsa_output.platform-cht-bsw-max98090.HiFi__hw_chtmax98090__sink [Out] Speakers
set-default-source alsa_input.platform-cht-bsw-max98090.HiFi__hw_chtmax98090__source

Any suggestions?

[ozsouth]

You might try installing pavucontrol & its 2 deps from the ppm. No guarantees tho'.

[vtpup]

Thanks ozsouth. I tried it, but that still requires a running pulseaudio server to interact with and I don't have pulseaudio.

I've found notes on the forum about how pulseaudio server is a problem to run with puppy(s) -- not a lot of encouragement and no how-to's, so far.

I'm wondering if it's really necessary.... Maybe alsa just needs to assign properly to the cards.

[vtpup]

Latest on the Acer C720-2844:

Bionicpup64: Since the only problem here was the microphone, I found a very small USB microphone as a temp fix. The mic is the type used on Raspberry Pi's -- basically just a little button that plugs into the port.

Latest on the Acer R11 sound issue:

GalliumOS does provide sound on this Chromebook but Bionicpup64 does not, so far.

Ozsouth's 5.4.27 -64 kernel seems to be a better match for this computer than the stock BP64 kernel. It recognizes the sound card (chtmax98090).

I compared GalliumOS /proc/asound/ contents with those of the above modified BPup64 and they were nearly identical, other than BPup64 assigning audio cards as cards 0 and 1, while GaOS assigns them as 1 and 2. I don't know if that makes any difference, but I doubt it.

I also borrowed GaOS /usr/share/alsa/ucm contents and applied them to BP64.

But no sound yet. If I try to play a sound file (the Puppy bark) and enter dmesg, I get the following last line:

Code: Select all

intel_sst_acpi 808622A8:00: fw returned err -16
sst-mfld-platform sst-mfld-platform: ASoC: can't open interface ssp2-port: -16
 SSP2-Codec: ASoC: BE open failed -16
 Audio Port: ASoC: failed to start some BEs -16

[bigpup]

I feel your pain

sound card (chtmax98090)

That is what I am dealing with in my HP 14 Chromebook.
Correction, it is now my Hp 14 Puppy laptop!

You do seem to be trying some things I have not.

Got any ideas on getting a working Pulseaudio pet package that will install into Bionicpup64 8.0?
I have tried several found around the forum, but still get dependency stuff needed. I am finding out why people hate Pulseaudio for Puppy Linux.
That thing wants everything and the Out house sink.

[vtpup]

bigpup, I'm going to try to exhaust alsa attempts first. The biggest problem for me is, I really don't yet understand all that goes on to make audio happen in general. What is required re. initialization of hardware and when, what kernel modules are needed, and when, what needs to be blacklisted, what does ALSA need in terms of configurations, and how does it work.

I'm just hacking now, not understanding what the whole audio process looks like.

Things I've picked up in readings along the way, though:

1.) There is a problem with the way this chip was implemented. Some conflict of timing and interrupt assignment during initialization and some whacky Google code facilitating. I read references to this somewhere in the development specifically of GalliumOS. Trying to find that reference again.....

2.) And, a needed alsamixer setup to enable sound (I believe that is the GaOS /usr/share/ucm files that I mentioned last post).

3.) And possibly some bootcode re. acpii needed.

re. 1.) above: maybe the pci audio card assignments 1 and 2 for GaOS vs. 0 and 1 for BPup64 is a significant difference after all, if it relates to the timing of the initialization of those cards. And if card initialization timing is the key to the problem.

This morning I'm going to try to find that timing problem reference...

[vtpup]

Headphones now working........ still testing.......

[bigpup]

I wonder if something is needed in /usr/share/alsa/ucm

There is stuff here that is for it:
https://github.com/plbossart/UCM

[vtpup]

Edited (sound works):

Here is the present setup method on Bionicpup64 (with ozsouth's 5.4.27-64oz kernel) specifically for an Acer R11:

1.) Install firmware-intel-sound deb:
https://packages.debian.org/sid/firmware-intel-sound

2.) Need to create usr/share/alsa/ucm/chtmax98090 with two files: https://github.com/GalliumOS/galliumos- ... htmax98090

3.) Download https://github.com/GalliumOS/galliumos- ... .state.txt

4.) Open console in the download folder and execute:

Code: Select all

alsactl -f ./asound.state.txt restore 0

(My chtmax98090 is device 0 in the code above. If yours is different , change the number after "restore")

You may have to reboot after all of the above to get sound working. I used the Multiple Sound Card Wizard to select card 0 Device 0. (Card 0 Device 1 "Deep Buffer Audio" doesn't yet seem to work, but actually they are the same, anyway.)

[vtpup]

Sound now works on the Acer R11!

See above post, now edited, for the method.

[bigpup]

vtpup,

Great work and hunting!!!

That did it for me too.

HP 14 Puppy laptop now has sound!!!!!!

2.) Need to create usr/share/ucm/chtmax98090 with two files: https://github.com/GalliumOS/galliumos- ... htmax98090

Correction:
Should be /usr/share/alsa/ucm/chtmax98090

For this step, I got the stuff from here as a package.
https://github.com/plbossart/UCM
When unpacked, it had the chtmax9890 directory with needed files in it.
Copied the chtmax98090 directory to /usr/share/alsa/ucm

Now, I wonder how you would do this for other sound hardware, in other Chromebooks?

[bigpup]

Slight sound problem.

On reboot had to enter

Code: Select all

alsactl -f ./asound.state.txt restore 0

To get sound working.

I kind of have a Bionicpup64 8.0 frugal install with a lot of hacking in it.

I think I need to do this all with a clean fresh frugal install.
I will report back my results.

[vtpup]

Thanks bigpup.
I don't have to repeat the alsactl-assound fix on mine when rebooting. It stays.

Just tested the microphone, and it works, too.

I haven't tested yet, but there might be a problem (as mentioned at GalliumOS) of the headphone jack not registering when you plug/unplug. Maybe not. Seems minor by comparison with what was just gained on these Chromebooks.

I think other Chromebooks may actually be easier. Notice that the Intel Sound Firmware deb has many different chipsets included. The 5.xx kernel also has many fixes already in it for hardware. And many of the UCMs are already in place. So I think we're close to opening up Chromebooks as viable Puppy boxes now.

If there is an incompatibility, I now know a lot more about these problems, and can probably solve them easier. More than I wanted to know....

[bigpup]

Yes, this is more than we should need to know about Chromebooks

I posted a correction for your step 2.
Should be /usr/share/alsa/ucm/chtmax9890