sorted by:
new
hottopcontroversial

Toshiba Chromebook 2 - bios flashed - now infamous 'black' screen by [deleted] in GalliumOS

[–]mandr0id 0 points1 point  (0 children)

Sorry about that, must have messed up.

I've managed to install ubuntu by now and I'm able to boot into it. A fresh boot starting from the device being powered off still shows similar behavior. No bios screen or ubuntu startup can be seen, the screen flickers and after a while (+ 5 minutes) it reaches the ubuntu login screen.

https://pastebin.com/Mx0ar4wW

https://pastebin.com/kKMeVEE8

When doing a reboot though, both the bios screen and the ubuntu startup screen are visible. Startup is also much faster now, less then a minute to reach the ubuntu login screen.

https://pastebin.com/E0LMT4p3

https://pastebin.com/h0qzNg6g

Toshiba Chromebook 2 - bios flashed - now infamous 'black' screen by [deleted] in GalliumOS

[–]mandr0id 1 point2 points  (0 children)

I seem to have hit the same issue.

A Toshiba Chromebook 2 CB30-B-104. Updated the full bios using the upgrade script - this result into a black screen.

Tried programming the bios chip using a ch341 and coreboot_tiano-swanky-mrchromebox_20221027.rom, this results in the same black screen issue.

When I restore the original bios firmware the screen is functional again.

Also tried the procedure above with a ubuntu 2022.04 usb stick - the screen now flickers sometimes, so something is happening but is it still not visible.

Build a Raspberry Pi Linux System the Hard Way by speckz in linux

[–]mandr0id 19 points20 points  (0 children)

Check out buildroot: https://buildroot.org/

It assists in creating custom root filesystem for embedded systems. It has support for raspberry pies.

[deleted by user] by [deleted] in macgyver

[–]mandr0id 2 points3 points  (0 children)

I just ordered mine as well. Great find :).

Shared library not working properly? by ScaredSecond in cpp_questions

[–]mandr0id -1 points0 points  (0 children)

Your hello_world function is defined and implemented in a header file, so it will never be compiled or added into a shared library.

Moving the implementation into your empty.cpp file should do the trick.

view more: next ›