BARLA HP StoneyRidge with RW_LEGACY: no TianoCore, only beep

Support
1

I have an HP Chromebook with:

  • Architecture x86_64
  • Board name: BARLA
  • CPU model: AMD A4-9120C RADEON R4, 5 COMPUTE CORES 2C+3G

I have not disabled the write protect. My goal is to make the device more flexible: to make it able to boot Linux (OpenSUSE) from USB, while also preserving ChromeOS.

I have put it in Developer Mode, then ran the MrChromebox script and installed the RW_LEGACY firmware. I didn’t see any errors at the time.

Result:

From the developer mode warning screen, when I press Ctrl+L, I see two options:

  1. U-boot - U-boot bootloader
  2. TianoCore - TianoCore bootloader

U-boot is functional, but won’t boot my OpenSUSE. TianoCore, however, doesn’t run. If I press 2, I get varying results:

  • if I press 2 quickly, I hear one beep (low) and am returned to the developer mode warning screen;
  • if I wait a minute then press 2, I hear two beeps (low-high) and then it boots into ChromeOS.

ChromeOS also boots fine if I press Ctrl+D.

Is there anything else I can try to get TianoCore working? Thank you all very much for your time and help.

I notice somebody else had a similar problem with a Lenovo, which sadly doesn’t seem to have ever gotten resolved. :frowning:

2

It’s broken

3

Hello WeirdTreething,

Thank you for your reply. What is broken: my Chromebook, or the script, or TianoCore? Can it be fixed?

4

the stock firmware. only by google.

5

Oh I see! That is a shame. At least I can just take it out of Developer mode and use Chrome OS (or use your full UEFI ROM to remove Chrome OS completely).

Is the RW_LEGACY option broken on all Chromebooks, or only ones with that that board? I ask because I also have a Dell Chromebook (board = FLEEX). Would RW_LEGACY work on that one?

6

it’s broken on devices where it’s marked as broken on my site

yes

7

Thank you very much for your replies, here and on Reddit. I appreciate the clarity :slight_smile: