How to boot Ubuntu 16.04 on the Shield TV with X1 GPU drivers
|
05-18-2018, 02:30 PM
(05-18-2018, 02:30 PM)Helios Wrote: https://drive.google.com/drive/folders/0...XBqa1ZlRVU The shield 2015 and 2017 have the same cpu and gpu, I think it should't has such difference on installing ubuntu. The shield 2017 starts installing ubuntu but reboots back to android in 10 seconds and your usb.img is the same effect as sda1.img. Do you have any suggestion? Or should I rebuy the shield 2015 to having an nvidia ubuntu?
The 2017 doesn't have an SD slot, which is required to boot the kernel. As AFAIK there is no way to load the USB3 drivers before loading the kernel. Bootloader mode only has access to the SD slot.
Rootfs can be kept on a USB, but the kernel needs to be on the SD so the ShieldTV can access it. Ubuntu on the shield TV is a fun toy, but it's not really worth rebuying the hardware just to play with it unless you're an aarch64 dev wanting to hack on the X1. Especially since that version of ubuntu is now pretty out of date, you'll need to update most software yourself anyways and I can't be bothered to update it. This post was largely for interested devs that wanted a not trash OS to develop on.
Thanks for your reply! Very appreciate.
The shield 2015 have 4 ports(two USB3.0, one microUSB, one microSD), and the SD slot is for rootfs, the microUSB or USB for ADB, one USB for keyboard or controller, then there left one usb port not used. If the bootloader mode only has access to SD slot, then why you mentioned the USB drive in your tutorial? I manage to solve the problem of lessing SD slot with shield 2017. I flash the usb.img to recovery using "sudo fastboot flash recovery sda1.img", then I pull out the usb cable for ADB (the second usb port to hdmi, the first usb port is for keyboard control) and plug on the usb3.0 driver which having the rootfs, and then restart the shield and select the "recovery kernel", then Bootloader mode has access to usb3.0 too. And then the shield start installing ubuntu. And it fails with reboot back to android. As I know, the kernel is contained by .img file(sda1.img or usb.img) and is already flashed in recovery partition now,. Am I right abou the kernel? Do we miss the operation about dtb file? Does it necessary? Have you ever tried MultiROM+TWRP method? Many people used this way to install ubuntu on android devices. Do you think it's a wise choice? Forgive me so much questions and wish your suggestion! 05-20-2018, 03:38 PM
The difference between shield 2015 non-pro and pro varient is only the 16g flash and 500g hard disk. Why are you said this tutorial can not work in pro varient, that's beyond my understanding.
05-20-2018, 03:44 PM
usb.img and sd.img are just the "boot" image. It has the kernel with a small thing changed to make it look for the rootfs either on USB or SD, depending on which one you booted.
I mean that back when this documentation was written, the Shield TV bootloader could only boot from either the internal storage, or MicroSD. Once the kernel loaded, it could load the USB drivers and look for the rootfs there if you extracted it there and booted with usb.img. The bootloader at the time of writing could not access USB without loading a kernel. If bootloader has access to USB now, that's fantastic, and could actually simplify a LOT of this guide. I didn't know that. Unfortunately, I don't know if I'll summon up the motivation to update my shield tv and play around with this again, but that's really good to know. 05-21-2018, 12:43 PM
You've misunderstood.
[color=#000000]After flashing the usb.img to recovery partition using "sudo fastboot flash recovery usb.img" and restart the shield in fastboot mode with the second option of "... recovery kernel", then the shield kernel is loaded with usb.img. After running the kernel, it could load the USB driver and find rootfs in it.[/color] [color=#000000]Am I right?[/color] 05-21-2018, 02:17 PM
That is correct.
Just note that if you want to load a real android recovery, you're stuck booting it over MicroUSB until you flash it again. Hrm, maybe I should have clarified that there is no "risk-free" way to use Linux on the 2017 STV. If you're fine with flashing images across the partition table and hopefully not screw that up, yeah you should be good to go.
While loading the recovery mode which has flashed the usb.img previously, I was not stucked booting it and I did't need to flash it again.
It just reboots in linux and reboots back in 10 seconds. Maybe the 2017 SATV has many differences with 2015. 05-21-2018, 02:33 PM
Possibly some watchdog timer rebooting the system because it thinks it hung?
Not sure. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 2 Guest(s)