# tegra Published articles for tegra. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## postmarketOS in 2026-04: new boot splash DevFeed: [postmarketOS in 2026-04: new boot splash]() Original publisher: [Read original article]() Published: 2026-05-10T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [Linux](), [releases](), [Maintainers](), [Development](), [Documentation]() Tags: [2026](), [boot](), [development](), [linux](), [maintainers](), [news](), [postmarketos](), [releases](), [tegra]() ### AI overview A postmarketOS project update reports a new Plymouth-based boot splash with boot-log access and screen rotation support. It also covers a ModemManager upgrade, plans to upstream q6voice to mainline Linux, the v26.06 release timeline, reimbursement-policy changes, governance updates, and maintainer changes. ### Source excerpt Booting has been made more appealing by the new splash screen, which is shown above. It changes the splash by adding the three segments of the logo fading in and out, but comes with some underlying functional improvements as well. As we switched from pbsplash to Plymouth, it is now possible to press ESC (or power on phones) to get the boot log and we can finally rotate the splash screen on devices where it looks wrong otherwise. Implementing this was great teamwork by Clayton, Aster, Brady, Rob, Ferass, Hakşiye, Mirthe, bluebunny and Sicelo in !7482! In other news, ModemManager was upgraded to 1.25.95_git20260422 in edge by Achill: "Stable release will be soon (expected in a few weeks) and has been very stable for most users, while bringing new features like cell broadcast that we can start to test in Alpine edge." As always, we are very grateful for the hard work of ModemManager maintainers (Aleksander et al.), and specifically Guido from Phosh for implementing cell broadcast. Organizational We will be financing work to upstream q6voice(d) to mainline Linux, see the previous blog post for details. The timeline for the upcoming v26.06 release has been published (now at docs.postmarketos.org, the previous wiki page for creating releases has been split up, reworked and moved to dpo / issue templates as it made more sense: !8486). We have approved changes to our reimbursement policy which allow community members to request reimbursement of items they use for the development of the project (!46). In order to put it into action, we have approved an additional budget entry of 500EUR to cover some of those expenses (!23). If what you are doing fits the policy, please feel free to make use of it! Following up on the power delegation topic from the Hackathon, the responsibility over selecting finance team members was moved from only Core Contributors to the Assembly (Core Contributors and Trusted Contributors). device-microsoft-surface-rt and device-nvidia-tegra-armv7 (both us ## Call For Tegra U-Boot Testers DevFeed: [Call For Tegra U-Boot Testers]() Original publisher: [Read original article]() Published: 2024-01-13T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [tegra](), [Nvidia](), [boot]() Tags: [bootloader](), [devices](), [nvidia](), [postmarketos](), [tegra](), [testing]() ### AI overview postmarketOS is seeking testers for its generic U-Boot port on Nvidia Tegra 2, 3, and 4 devices. The port supports nine devices, and user testing can help replace proprietary vendor bootloaders with U-Boot. ### Source excerpt We currently have a generic port for Nvidia Tegra 2/3/4 devices using U-Boot as bootloader, supporting 9 different devices at the time of writing. This wouldn't have been possible without the work of Svyatoslav Ryhel (also known as Clamor), who has been working on Tegra devices for the last few years and is also a maintainer of Nvidia Tegra SoCs in U-Boot. The wiki page has a list of supported devices. Svyatoslav ported most of these devices without owning one, just relying on testing from people. This means anyone having such a device can reach him and eventually will be able to replace the old proprietary vendor bootloader with U-Boot. If you're interested, you can reach out Svyatoslav in #postmarketOS-on-tegra:matrix.org matrix room or e-mail him to get personal contacts at clamor95@gmail.com. ## Unbricking SHIELD TV (2015) with a Bootrom Exploit DevFeed: [Unbricking SHIELD TV (2015) with a Bootrom Exploit]() Original publisher: [Read original article]() Author: yifanlu Published: 2022-06-17T07:00:00Z Content type: article Language: en Sources: [Yifan Lu]() Topics: [Reverse Engineering](), [Raspberry Pi](), [configuration](), [boot](), [Nvidia](), [Linux]() Tags: [boot](), [bootrom](), [configuration](), [embedded](), [exploit](), [linux](), [nvidia](), [raspberry-pi](), [rcm](), [reverse-engineering](), [t210](), [tegra]() ### AI overview The article documents recovering a 2015 NVIDIA SHIELD TV after flashing an outdated device tree blob left it unable to boot. It examines serial-console diagnostics and the Tegra boot ROM's APX emergency recovery mode, including its use of NVIDIA's RCM protocol. ### Source excerpt Last year, a friend gave me his SHIELD TV when he moved. He worked at NVIDIA and got it for free and had used it only a handful of times before it traveled from his closet to my own. I had forgotten about it until I had a need for a Raspberry Pi and discovered that they were all still sold out. Wouldn't the SHIELD TV make a great RPI replacement? It has been out for almost a decade now and surely people have gotten Linux working on it. After following a guide from 2015, I quickly bricked the device trying to flash an outdated DTB file. It turns out that a bad DTB brick was quite common in the community and unfortunately the only proposed solution of "return it to Best Buy" was not an option for me. Even though I have never cared about this device, I was still ashamed at my negligence and felt guilty about creating more e-waste. Thus began my journey to recover the device.