chrultrabook / docs Goto Github PK

See https://www.chromium.org/chromium-os/developer-library/guides/device/ro-firmware-unlock/

Newer 2023+ devices use a form of read only firmware verification.

Following the current documentation, if the user does not flash with a suzyq they will end up with a not usable device

Has anyone tried using an eGPU with a Chromebook through Thunderbolt 4 on Linux? Are there any additional issues or special instructions in addition to what can be found in https://wiki.archlinux.org/title/External_GPU?

We got many h3 (###) without prior h2 (##)

They need to be changed to h2

Since there is a rework I'll just put the docs in this issue. You can copy the markdown and add me as a co-author to the commit plz:

When disabling WP by disconnecting the battery, do not flash firmware while the battery is disconnected. Your Chromebook could get bricked there is a power failure or you accidentally unplug your Chromebook while flashing firmware. Use these steps to minimize the chance of bricking:

1. Make sure your Chromebook is in developer mode
2. Shut down your Chromebook
3. Open up your Chromebook
4. Disconnect the battery from your Chromebook
5. Lightly cover the Chromebook with a lid but do not securely close the lid, because you will reconnect the battery later
6. Turn on your Chromebook with the battery disconnected
7. Open crosh (Ctrl + Alt + T)
8. Enter shell (type shell and press Enter in crosh)
9. Run

sudo flashrom --wp-disable
sudo flashrom --wp-range 0 0

If the command sudo flashrom --wp-range 0 0 fails, try doing

sudo flashrom --wp-range 0,0

instead
10. Check that WP is disabled with

sudo flashrom --wp-status

11. Shut down your chromebook
12. Reconnect the battery
13. You can now securely close and screw the lid
14. Turn on your chromebook
15. Flash full ROM using mrchromebox's firmware utility script

disregard

Redrix has more hardware difficulties than most Chromebooks, so I will make a guide for other redrix users (and myself):

Status

What works OOTB:

• Touchscreen
• Wifi / Bluetooth
• Keyboard
• Side volume keys
• Keyboard light
• Clicking the touchpad (and getting haptic feedback)

What works after installing fixes:

• Speakers
• Microphone
• Moving the cursor with touchpad

What doesn't work (as of now):

• Camera
• Fingerprint Reader

Fixing / Setting Up

Fix Touchpad

Create a file /etc/libinput/local-overrides.quirks with these contents:

[Google Chromebook Redrix]
MatchUdevType=touchpad
MatchName=ELAN2703:00 04F3:323B Touchpad
MatchDMIModalias=dmi:*pn*Redrix*
ModelChromebook=1
AttrPressureRange=-0:-2
AttrThumbPressureThreshold=45
AttrPalmPressureThreshold=2500

Touchpad will start working work on next boot

Fix Speakers and Microphone

Follow the normal chromebook-linux-audio script. It will make speakers and microphone work.

Fix Camera (WIP, doesn't work yet, results in a black rectangle camera)

This is a Fedora-specific solution. Other distros probably have solutions but this guide doesn't have them.

Add RPM Fusion Repositories

Follow this guide to add both free and nonfree repositories.

Install IPU6

Steps are from this guide

Run

sudo dnf update \
  --enablerepo=updates-testing \
  --enablerepo=rpmfusion-free-updates-testing \
  --enablerepo=rpmfusion-nonfree-updates-testing \
  'kernel*' '*v4l2loopback' -y

sudo dnf install \
  --enablerepo=updates-testing \
  --enablerepo=rpmfusion-free-updates-testing \
  --enablerepo=rpmfusion-nonfree-updates-testing \
  akmod-intel-ipu6 -y

Sauce: https://vkc.sh/linux-on-a-chromebook-but-interesting-er/

The build-uefi.sh uses ../roms folder now

I made an automated Full ROM and altfw UEFI builder: https://github.com/ChocolateLoverRaj/scripts. It is much easier for simple things like changing the logo and timeout.

heroImage

https://forum.chrultrabook.com/t/disabling-hwwp-on-steelix-and-similar-models/2309/15

Idk where to put this so I'm just writing it in this issue:

This guide is for Chromebooks which support RW_LEGACY and use the edk2 bootloader for RW_LEGACY. If you do not want to keep Chrome OS, don't follow this guide, you can just delete all the partitions. If you want to install a linux distro other than Fedora you can probably do it, but I only tested Fedora.

Tested with: redrix with Fedora.

• Make sure you're in developer mode with standard ChromeOS partitions.
• Boot into Chrome OS. Sign in as guest because if you login you'll have to login again later anyways.
• All of the data in your internal storage will be wiped, so make sure to backup everything you don't want to lose
• Go into Crosh -> Shell
• Run chrx: curl https://chrx.org/ | sudo tar xzfC - /usr/local && chrx. Decide how much space to give to Fedora
• Reboot into Chrome OS. The Chromebook will say that it's repairing itself. Keep booting from internal storage until it successfully boots. You can sign in and you will stay signed in.
• Go into Crosh -> Shell
• Run curl https://chrx.org/ | sudo tar xzfC - /usr/local && chrx -d ubuntu
• Command should run successfully
• At this point, Ctrl + L will not work
• Install RW_LEGACY using mrchromebox's firmware utility script
• Plug in a USB drive containing a Fedora live USB
• Reboot
• Select "Alternative bootloader" -> "edk2"
• Press Esc when you see the coreboot logo
• Boot from the USB drive
• Choose custom install in the Fedora installation
• For the / partition, choose the parition which contains Ubuntu. This will probably be in partition 7 (update these docs if you are sure that it is on this partition). Click on format and make it /. I used ext4, but btrfs might work too. For the /boot/efi partition, choose the existing EFI partition. This will probably be in partition 12 (update these docs if you are sure that it is on this partition).
• Click "Install"
• Fedora should install successfully
• If everything went right, you have successfully dual-booted your Chromebook with Chrome OS (which can be accessed by booting internal storage when you turn on your chromebook).
• Shut down or reboot to exit the live USB Fedora
• To boot Chrome OS, select boot from internal storage. To boot Fedora, select alternative bootloader -> "edk2".
• Next steps: Setup Fedora by applying fixes such as audio, keyboard shortcuts, and other hardware.

I think adding phrasing like "If you choose to flash the Full ROM, the script will now offer to make a firmware backup" to the start of Step 4 will help clarify to the reader that they don't have to run a separate script/process/thing that isn't there.

I certainly got confused myself and thought I had to do the firmware backup separately.

(I'm citing firmware.sh in the scripts repository for this: backup_firmware is called in flash_coreboot if the firmware is stock, but not in flash_rwlegacy)

While Markdown is very forgiving with bad formatting, we should bring the docs to a common markdown formatting standard.

Selection of issues:

• Both too many and no blank lines. There should be only one empty line between elements
• Heading order: # -> ## - > ### -> ####; No ****' as headers
• Trailing spaces
• Inconsistent horizontal line - count (common is x3)
• ...

The introduction of coreboot 4.21 brought support to all Ryzen Chromebooks. We need to update the pages to reflect that, and also mention that you need special drivers / can't boot off of eMMC.

We should also mention somewhere that Stoney is no longer as broken.

Good evening,

I've got a problem with getting an exact information about what patches should be applied on the Linux kernel 6.1+ for Stoneyridge Chromebook devices.

The documentation of Known issues in the Stoneyridge devices section says:

Needs kernel compiled with AMDGPU=Y instead of =M and firmware built-in to get working audio

eMMC is only detected on a cold boot unless you have a patched kernel

although not linking any source to the patches for the Linux kernel as mentioned.

What patches should I use?

Additionally while reading dmesg for anything related to the problem of eMMC I've got:

[    0.000000] efi: EFI v2.7 by EDK II
[    0.000000] efi: SMBIOS=0xbf41a000 SMBIOS 3.0=0xbf418000 ACPI=0xbf533000 ACPI 2.0=0xbf533014 MEMATTR=0xbbf16c18 
[    0.000000] efi: Remove mem97: MMIO range=[0xffbc0000-0xffbfffff] (0MB) from e820 map

Me and some other people like to have the same top row behavior as Chrome OS (by default it does things like change brightness and volume, and when u hold the Search key it does F1, F2, ...

I forked the keyboard tester to do this: https://github.com/ChocolateLoverRaj/VivaldiKeyboardTester/tree/brightness-only

Can I add instructions for people who also want to do this on windows:

• Download https://github.com/ChocolateLoverRaj/VivaldiKeyboardTester/raw/brightness-only/croskbsettings.bin
• Copy the file to C:\Windows\System32\drivers\croskbsettings.bin
• Execute C:\Program Files\crosec\croskbreload.exe

I'll probably wait for the huge rewrite of the docs to make this change.

The instructions to install GNU/Linux contain the warning below:

Unfortunately, I do not know what AVS is. The term is also mentioned in the FAQ, but from there it sounds like it’s a Windows driver?

Can I get AVS or SOF drivers for free?

• Only the Linux drivers are free.

title

https://docs.chrultrabook.com/docs/firmware/manually-flashing.html