Puppy Linux Discussion Forum

Install FatDog64 812 on Chromebook

Dual boot of Chrome OS (actually Cloudready OS)and FatDog64 812

I am writing this post on a Dell Chromebook 11 (model 3180)
Dell Chromebook 11 3180 - Celeron N3060 / 1.6 GHz - Chrome OS - 4 GB RAM - 32 GB eMMC - 11.6" 1366 x 768 (HD)
Chipset: Intel Braswell
Hardware ID : KEFKA
There is also a low end model with 2GB of RAM and 16GB emmc.

Instructions
I first upgraded Chrome OS to CloudReady OS
Download and follow their Linux instructions for making a USB boot stick (8GB or bigger)
https://www.neverware.com/freedownload

I carefully studied this youtube video to install CloudReady OS.
https://www.youtube.com/watch?v=kzYzXTCBl70

A write protect screw needed to be removed (same as video)by opening up case.
The screw was easy to spot because of 'WP' written next to it.
(Note that only a few models use a write protect screw)
Check on this list...
https://wiki.mrchromebox.tech/Supported_Devices

So I followed the video and converted Chrome OS to CloudReady OS.
Of course this wouldn't be necessary for a recent Chromebook.

As part of the install I was required to install mrchromebox's script 'firmware-util.sh
https://mrchromebox.tech/#fwscript

cd; curl -LO mrchromebox.tech/firmware-util.sh
sudo install -Dt /usr/local/bin -m 755 firmware-util.sh
sudo firmware-util.sh

One of the features of the script is the install of a crude boot manager so a choice of several Lnux Operating systems is possible if installed on the EMMC or on a USB stick.

I took advantage of this feature to burn Fatdog64 812 ISO to a small USB stick
and then boot to the fatdog desktop in less than a minute.
It works surprising fast and is compatible. One big negative is the audio chip is NOT recognized.

_______________________________________________________________________

Here's a quick description of boot...

1) Computer is shutdown i.e. a black screen
2) insert USB stick (with fatdog ISO burnt inside) in empty port of the Chromebook
3) Press power key
4) Watch for bunny and then quickly press ESC key
5) Using arrow keys , choose 'Boot Menu' from list

6) Choose your USB stick from list
7) You will see a Fatdog icon on screen. Use your arrow keys to select it and press <ENTER>
8) You will see a long list of possible actions. The top item of the list is the best.
Select 'Fatdog64'. Press <ENTER>

9) You will automatically load a Savefile (or folder) if it exists and go to the Fatdog64 desktop to begin work.
____________________________________________________

Bluetooth and wifi and SAMBA is easy to set up using the control panel

Very little RAM is used. In my case it was 126 MB which is tiny in a 4 GB machine.

# free -h
total used free shared buff/cache available
Mem: 3.8G 126M 3.0G 28M 680M 2.9G
Swap: 0B 0B 0B

_______________________________________________________

I set up my SAVEFILE (actually a folder) in /dev/mmcblk0p1
which is the first partition in the EMMC. The CloudReady OS also uses this partition.
It has lots of space (see terminal output)

# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 1.7G 8.0K 1.7G 1% /dev
tmpfs 1.9G 6.1M 1.9G 1% /aufs/pup_init
/dev/loop0 74M 74M 0 100% /aufs/kernel-modules
/dev/loop1 353M 353M 0 100% /aufs/pup_ro
/dev/mmcblk0p1 23G 3.3G 19G 16% /aufs/devsave
aufs 23G 3.3G 19G 16% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 1.9G 400K 1.9G 1% /tmp

I am pleased that you reported your success and given instructions about changing your Chromebook to the CloudReady version. Chromebooks are ideal for Linux and Puppy. They tend to come with soldered in SSDs with a capacity of between 16 GB to at best 64 GB and soldered in RAM of either 2 GB or if you are lucky 4 GB and so not much chance of upgrading. This means that a light weight Linux such as more recent Puppies and Fatdogs are ideal on them.
I happened to get very good deals back in 2014 buying Chromebooks: the Acer C720 and a HP14 with the same chips as the Acer (and both 2 GB of RAM). For these the SSD was not soldered in and although Linux run well on the 16 GB I have replaced that with 128 GB SSDs which makes them more useful. On the C720 I changed the BIOS using the early John Lewis set of instructions and so is still MBR and for the HP14 I used MrChromebox instructions to get UEFI and I have updated that as well. They have both had various Linux Distros on them generally dual booting and generally with multiple Puppy variants frugally installed. In the early days of conversion the track pads were not recognised but with more recent kernels that is not an issue although with more mainline Distros it feels better. Sound has never been a problem for me.
More recently, I have bought a Chromebook for my wife but because both the SSD and RAM are more likely to be soldered in I chose a HP unit with 32 GB SSD and 4 GB of RAM so that when it stops getting updates I have better opportunities to run Linux on it.

Sound has never been a problem for me

When I tried FatDog64 812 I get the warning that the audio device is not recognized

I tried Gallium Linux to see if the audio worked and it did!!

Fatdog seems to see the chip (see image)

The audio chip name is chtrt 5650 from alsa output.
Apparently made by realtek ---> Realtek ALC5650/5654
The Gallium OS system log stated it found the audio chip...

Nov 18 21:48:14 galliumos alsactl[1316]: Found hardware: "chtrt5650" "" "" "" ""

Here is more of the system log...

Nov 18 21:48:14 galliumos systemd-udevd[1057]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.

Nov 18 21:48:14 galliumos systemd-udevd[1060]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.

Nov 18 21:48:14 galliumos systemd[1]: Reached target Sound Card.

Nov 18 21:48:14 galliumos systemd[1]: Started GalliumOS system customization for Braswell models.
Nov 18 21:48:14 galliumos alsactl[1316]: /usr/sbin/alsactl: load_state Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
Nov 18 21:48:14 galliumos alsactl[1316]: Found hardware: "chtrt5650" "" "" "" ""
Nov 18 21:48:14 galliumos alsactl[1316]: Hardware is initialized using a generic method
Nov 18 21:48:14 galliumos alsactl[1316]: Found hardware: "HDA-Intel" "Intel Braswell HDMI" "HDA:80862883,80860101,00100000" "0x8086" "0x7270"
Nov 18 21:48:14 galliumos alsactl[1316]: Hardware is initialized using a generic method
Nov 18 21:48:14 galliumos systemd[1]: Started Save/Restore Sound Card State.

The fatdog boot log appears confused about the chip...

Nov 18 13:29:50 fatdog64-9e6 user.err kernel: rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
Nov 18 13:29:50 fatdog64-9e6 user.info kernel: rt5645 i2c-10EC5650:00: Detected Google Chrome platform
Nov 18 13:29:50 fatdog64-9e6 user.warn kernel: rt5645 i2c-10EC5650:00: i2c-10EC5650:00 supply avdd not found, using dummy regulator
Nov 18 13:29:50 fatdog64-9e6 user.warn kernel: rt5645 i2c-10EC5650:00: i2c-10EC5650:00 supply cpvdd not found, using dummy regulator
Nov 18 13:29:50 fatdog64-9e6 user.info kernel: input: chtrt5650 Headset as /devices/pci0000:00/808622A8:00/cht-bsw-rt5645/sound/card1/input10
Nov 18 13:29:50 fatdog64-9e6 user.info kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Nov 18 13:29:50 fatdog64-9e6 user.info kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Nov 18 13:29:50 fatdog64-9e6 user.info kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13

A lot of useful info about installing and using Puppy Linux on a Chromebook:
viewtopic.php?t=431

My sound chip on both the Acer 720 and the HP 14 is a Realtek ALC283. It is recognised by all the Linux Distros and the sound works fine. I have to select the PCH (HDA Intel PCH) Analog ALC283 card to get it to work with the laptop speaker. That works for Puppy and Fatdog64 (811).

I wonder if it is sending the sound to HDMI. You could try try connecting via HDMI to a TV to see if you get sound on that. Also, with VLC > Audio > Audio Device you will or should get a list of sound options for you to try with a video.

I wonder if it is sending the sound to HDMI.

I doubt this will work since the audio device is not recognized.

But funny you mentioned HDMI audio. When using cloudready OS I couldn't make audio flow to internal speakers, so I attached to HDMI TV and the audio output worked perfectly!!! Bluetooth audio also works on Cloudready OS.

Gallium OS works perfectly with everything.

Dual boot is possible with Gallium OS as well.

https://medium.com/@adrian.carroll7/how ... ed5b073e1b

Googling your problem I see there maybe a solution. I cannot test it and am not sure if it works; however you can give it a go.
I installed Fatdog 812 to dual boot with Linux Mint and see that the chrt5650 is missing from Fatdog's /usr/share/alsa/ucm/. I just copied the chrt5650 Mint version to Fatdog and would expect that to work if I had that sound chip (after a reboot). In your case Gallium will have the missing chrt5650

@don570

Take a look at the link Bigpup posted above, on page 3. I have a Acer CB3-431 with the same sound chip working. Download the acerCB3-431_audio.pet, in the revised setup post and install it. The pet installs the intel audio drivers and sets up the alsa configuration. Follow the instructions starting with this one: -menu>setup>Alsa Sound Wizard>Sound Card Wizard 2>choose device 0>OK

Let me know if I can help

wizard

I'm following instructions as closely as possible i.e. pet needs to be converted to fatdog
My conclusion is that the kernel isn't quite right.?????

I'm close to success (I believe ) since alsa speaker test will alternate between speakers however
no sound will come out.

At least there is no warning messages however no soud when playing files.

Could that be HDMI sound?

You need a special kernel that has been configured to turn on the needed features of a ChromeBook.
Not sure how it will work in Fatdog64.
See this post:
viewtopic.php?p=2155#p2155

I wondered if the module for that sound card was compiled in the Fatdog kernel. This is the RT5XXX modules compiled in Mint and the kernel config files are in the boot directory for ease of examination.

CONFIG_SND_SOC_RT5514=m
CONFIG_SND_SOC_RT5514_SPI=m
CONFIG_SND_SOC_RT5616=m
CONFIG_SND_SOC_RT5631=m
CONFIG_SND_SOC_RT5640=m
CONFIG_SND_SOC_RT5645=m
CONFIG_SND_SOC_RT5651=m
CONFIG_SND_SOC_RT5660=m
CONFIG_SND_SOC_RT5663=m
CONFIG_SND_SOC_RT5670=m
CONFIG_SND_SOC_RT5677=m
CONFIG_SND_SOC_RT5677_SPI=m
CONFIG_SND_SOC_RT5682=m
If we had a copy of the Fatdog kernel config files then they could be compared. There is a process for adding kernel modules https://distro.ibiblio.org/fatdog/web/faqs/kernel.html

Also, there is many guides on the situation that might work such as: https://docs.slackware.com/howtos:hardw ... -hda-intel

peterw wrote: Fri Nov 26, 2021 8:53 am

If we had a copy of the Fatdog kernel config files then they could be compared.

It's in /proc/config.gz.

For k5.4.152:

# zgrep 'CONFIG_SND_SOC_RT5' /proc/config.gz 
CONFIG_SND_SOC_RT5514=m
CONFIG_SND_SOC_RT5514_SPI=m
CONFIG_SND_SOC_RT5616=m
CONFIG_SND_SOC_RT5631=m
CONFIG_SND_SOC_RT5640=m
CONFIG_SND_SOC_RT5645=m
CONFIG_SND_SOC_RT5651=m
CONFIG_SND_SOC_RT5660=m
CONFIG_SND_SOC_RT5663=m
CONFIG_SND_SOC_RT5670=m
CONFIG_SND_SOC_RT5677=m
CONFIG_SND_SOC_RT5677_SPI=m
CONFIG_SND_SOC_RT5682=m
#

Greetings!

Thanks for the location of the config file. Never realised it was there.

I see that the RT5650 module/codec is not listed. I have seen https://cateee.net/lkddb/web-lkddb/SND_ ... _MACH.html but not sure how to progress this.

I had a further look at the suggestions in https://docs.slackware.com/howtos:hardw ... -hda-intel and see in /etc/modprobe.d/alsaXXX.conf differences and
For Fatdog
options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
options snd-cmipci mpu_port=0x330 fm_port=0x388
options snd-aloop index=-2

compared to that in Mint which has many more entries.