Display goes blank while booting Debian 12 standard

Steps for Debian (substitute step 4):

  • Run update-initramfs -ck 6.6.16-stoney
  • Run update-grub

Hello, @sadlerm!

Unfortunately, that didn’t work. Here’s what I got:

update-initramfs: Generating /boot/initrd.img-6.6.16-stoney
grep: /boot/config-6.6.16-stoney: No such file or directory
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
grep: /boot/config-6.6.16-stoney: No such file or directory
E: gzip compression (COMFIG_RD_GZIP) not supported by kernel
update-initramfs: failed for /boot/initrd.img-6.6.16-stoney with 1.

Does anyone know what this means?
Any help would be greatly appreciated!

What kernel are you currently using?

My current kernel (without Stoneyridge patches) is version 6.1.0.
The Stoneyridge-patched kernel I’m trying to install is version 6.6.16.

StoneyRidge is poorly supported, but framebuffer issue shouldn’t happen assuming you flashed full firmware.

Stock build had too little UMA allocated, my patch raised it from 16 to 256MB and fixed the issue.

Hello!

I didn’t flash the full firmware because it would involve taking the the computer apart, removing the battery, putting it back together, installing the full firmware, and then diong it all over again to plug the battery back in. It may also cost money because the computer has pads on the bottom covering the screws that would need to be removed and then replaced (unless I didn’t destroy them getting them off).

Of course, if that’s my only option, then I guess I can do it. But there’s RW_LEGACY available and it’s supported on my device, so I thought “why not?”.

Would installing the full ROM fix the problem with installing the Stoneyridge kernel?
Thanks for any help you can provide!

Yes, RW_LEGACY doesn’t work correctly at all on stoney. Like I mentioned - platform is poorly supported overall, but other than missing audio in “normal” kernel, everything should work.

I totally agree with you.

Do you think installing the full ROM would fix the problem I’m having with installing the Stoneyridge kernel?

Thank you for taking your time to help me out!

No worries!

It won’t fix the issue with kernel (as that’s purely Linux), but it will fix the issues with framebuffer, sleep, power management, USB and probably much more.

Looks like person building the kernel linked above did not enable GZIP or ZSTD. I don’t use Debian (or anything Debian-based) so I don’t know which compression they support.

I think the best idea would be to build your own kernel with Tree’s kconfig as that one definitely supported GZIP.

Thank you for your quick reply!

I think I’m going to install the full ROM. After that’s finished, I’ll re-assess the situation and see how many problems it solved.

Depending on how many other projects I have going on, I’ll try to get back to you with my results in the next two days.

I’m still kind of a Linux beginner, so I might try to find a step-by-step guide to build my own kernel. One question I have is what is kconfig? Also, when you said “Tree”, are you talking about @WeirdTreeThing?

Thank you for any answers you can provide! This conversation is very helpful.

I have a question: can I disable write protection through the firmware, or will I have to take the Chromebook apart?

Here are my Chromebook’s specs:

Model: HP 14-db0044wm
Board name: CAREENA
Architecture: x86_64
CPU: AMD A4-9120C RADEON R4
CPU gen: Stoneyridge

Yes, you need to disable firmware write protection. You either need to unplug the battery or use a SuzyQ to do that.

There’s a guy that sells SuzyQ debug boards on eBay (so that you can use a regular USB-C with it).

Ok! Just as I got this reply I was prying pads off the back of my Chromebook to access the battery.

First, I’ll try the battery method.
If that doesn’t work, I’ll buy myself one of those debug boards and do it that way.

Will installing the full ROM fix my Stoneyridge problems?

You will still need to use a custom kernel. As elly suggested, maybe using WeirdTreeThing’s kconfig will solve the issues you’ve been having.

The README in the GitHub repository has instructions on what to do. After that, as before, move the kernel modules folder to /lib/modules, move vmlinuz to /boot, generate a initramfs by running update-initramfs -ck <kernel version>, and update-grub.

1 Like

Thank you so much!
I will try this as soon as I get my Chromebook back together and the full ROM installed on it. If anything goes wrong, I’ll post my questions here.

By the way, the disassembly is going great (so far).

Thank you for sharing your knowledge with me.

1 Like

Hello!

After removing the battery in my Chromebook, I turned it on and pressed Ctrl+Alt+F2 at the “OS verification is OFF” screen" to get to VT-2, but nothing happened. Is this because I’ve already installed RW_LEGACY, wiped the Chromebook, and put Linux on it? Or maybe it’s because I somehow exited Developer Mode removing the battery?

Thanks for any help you can provide!

CAREENA opens from the palmrest BTW. You need to unscrew all screws on the bottom, flip it, and pry the keyboard assembly (palmrest) out of the chassis).

You’re supposed to jump to VT-2 once the OS boots up into graphical environment, it won’t work in depthcharge.

Thank you!

I’ll try that and get back to you either tonight or tomorrow.

Unfortunately, that didn’t work.

The computer currently as Debian on it, so do I have to reinstall ChromeOS on it before I can access VT-2? If so, how would I do that?

MrChromebox’s script can be run from any Linux distro if you no longer have ChromeOS installed.

Otherwise, instructions on using VT-2 “Developer Console” are ChromeOS-specific, yes.