FORUMS
Remove All Ads from XDA

Build kernel from source and boot to Ubuntu using L4T (Linux for Tegra) rootfs

392 posts
Thanks Meter: 88
 
By yahoo2016, Senior Member on 19th December 2015, 08:47 PM
Post Reply Email Thread
2nd May 2018, 05:29 PM |#641  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by efecto369

Hi,
I cheked many times before all the points that you suggest, anyway i checked again (I really want to get this working).
I can miss something but i tried many many options.
I format all usb devices from lubuntu machine with:

sudo mkfs.ext4 /dev/sdb1

And Gtparted say only one partition.

Today, when i was launching all the boot images again with a litle hard disk attached, i found one detail that i didn't realised before:

-With boot image mmcblk0p29.img there are some messages before the boot process crash whith my USB2 external hard disk attached on usb port near Hdmi conector, is recognised during boot process like "sd 0:0:0:0:[sda]" , and after there is message that say: "Assuming drive cache: write through sda: sda1", but the strange thing is that with "sda1.img" there is no message regarding to hard disk detection, only the "EXT-4 (sda1): error loading Journal" message.

-Note:This model only has two usb ports, no sd , no mini usb.
ID of my device is: tegra210-darcy-p2894-0050-a04-00.dtb.

Sorry about my english.

"USB2 external hard disk attached on usb port" - So, you're using external hdd instead of usb flash drive?
Make sure there is no bad sector in that hdd. When I searched the error message "EXT-4 (sda1): error loading Journal", many threads I found suggest corrupted disk. Corruption could be either the image file or the hardware disk itself. So, I'd suggest re-doing from scratch, downloading fresh new files, with a different drive.

* and sorry I forgot 2017 version didn't have micro-usb. Maybe I was confused with Pro version.
 
 
18th May 2018, 11:44 AM |#642  
Junior Member
Thanks Meter: 0
 
More
I met the same problem about reboot back to android.
Quote:
Originally Posted by ithuestad

Thank you for all your help thus far. I've flashed the appropriate dtb file but when booting from the boot image for the sdcard the SATV starts to load ubuntu and then it looks like it encounters some errors and reboots back into android.

I was using the shield 2017 to install ubuntu and it seemd start installing but reboots back to android in 10 seconds. How didi you fixed that? I was using usb driver mode because there is no sd slot in 2017 version.
I did't flash the dtb file, though I knew the dtb name but I didn't know where to download the dtb file. Is dtb file very important? Or should I turn on the develop mode?
Can you help me?

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------

Quote:
Originally Posted by yahoo2016

Can you try the following?
https://forum.xda-developers.com/sho...&postcount=421

I am using 2017 16gb, and it will reboots back to android after start installing ubuntu in 10 seconds.
Your previous method is just for dowloading the rootfs to usb or sd card.
Hope for your reply, thanks!
25th July 2018, 06:44 PM |#643  
Senior Member
Thanks Meter: 11
 
More
Can i boot l4t on USB drive and stay to Android TV os on primary?
30th July 2018, 01:26 PM |#644  
Senior Member
Thanks Meter: 11
 
More
Me too on 2017 TV ubuntu dont work
7th August 2018, 12:46 AM |#645  
Senior Member
Thanks Meter: 90
 
More
Anyone had luck setting this up over latest Oreo update ? Every attempt through USB/microSD ends up with kernel panic so far.
7th August 2018, 01:42 AM |#646  
Senior Member
Thanks Meter: 29
 
More
AFAIK the only release that works is R24.x, which is based on Ubuntu 14.04. The newer ones were only made for the Jetson development boards and won't run on the Shield TV.
7th August 2018, 09:40 AM |#647  
Senior Member
Thanks Meter: 90
 
More
Quote:
Originally Posted by Mogster2K

AFAIK the only release that works is R24.x, which is based on Ubuntu 14.04. The newer ones were only made for the Jetson development boards and won't run on the Shield TV.

Yes, that's exactly the releases I've been trying on latest update, both 24.1 and 24.2.1 results in kernel panic, even the rootfs' image files on forum, flashing them through dd to no avail.

I was wondering if it's something related to kernel/bootloader version..
7th August 2018, 09:21 PM |#648  
Senior Member
Thanks Meter: 29
 
More
Quote:
Originally Posted by wejgomi

Yes, that's exactly the releases I've been trying on latest update, both 24.1 and 24.2.1 results in kernel panic, even the rootfs' image files on forum, flashing them through dd to no avail.

I was wondering if it's something related to kernel/bootloader version..

It seems to be working fine on my 2015 system with 7.0.2 bootloader. I used one of the kernels in this thread to boot from an sdcard with fastboot.
8th August 2018, 08:00 AM |#649  
Senior Member
Thanks Meter: 90
 
More
Quote:
Originally Posted by Mogster2K

It seems to be working fine on my 2015 system with 7.0.2 bootloader. I used one of the kernels in this thread to boot from an sdcard with fastboot.

That's weird. Any extra steps you take apart from flashing correct boot.img, preparing SD card according to that post and .dtb flash ? I've seen 1-2 posts with same issue and resolved, but there isn't any follow-up explaining how they did.

How it boots with output on screen suggests it's a media related issue, but already tried both microSD/USB, with correct boot.img as explained. It's a 2015 16gb.
8th August 2018, 08:20 AM |#650  
Senior Member
Thanks Meter: 29
 
More
Quote:
Originally Posted by wejgomi

That's weird. Any extra steps you take apart from flashing correct boot.img, preparing SD card according to that post and .dtb flash ? I've seen 1-2 posts with same issue and resolved, but there isn't any follow-up explaining how they did.

How it boots with output on screen suggests it's a media related issue, but already tried both microSD/USB, with correct boot.img as explained. It's a 2015 16gb.

I haven't actually flashed the boot image - I use "fastboot boot mmcblk1p1.img" instead. And I'm using the stock .dtb.

Oh, I also formatted the sdcard on my PC, probably with a live system. I have noticed that the Shield and PCs seem to format cards differently - PCs usually leave a 1 MB gap before the first partition to prevent any alignment issues, while the Shield seems to format without a gap. I think the gap is required for Linux, even tho' Android will refuse to mount it.

Edit: added more info and a screenshot
Attached Thumbnails
Click image for larger version

Name:	Screenshot at 2018-08-08 07-46-57.jpg
Views:	20
Size:	68.1 KB
ID:	4567120  
8th August 2018, 10:57 AM |#651  
Senior Member
Thanks Meter: 90
 
More
Quote:
Originally Posted by Mogster2K

I haven't actually flashed the boot image - I use "fastboot boot mmcblk1p1.img" instead. And I'm using the stock .dtb.

Oh, I also formatted the sdcard on my PC, probably with a live system. I have noticed that the Shield and PCs seem to format cards differently - PCs usually leave a 1 MB gap before the first partition to prevent any alignment issues, while the Shield seems to format without a gap. I think the gap is required for Linux, even tho' Android will refuse to mount it.

Edit: added more info and a screenshot

Yes, that's how I also do, preparing the rootfs stick directly from Ubuntu 18.04, with a single partition(ext4) created through GParted, then uploading everything found in ./rootfs.

I'm actually trying to set this up in recovery partition, so can cycle through OS'es with adb commands, I also tried to fastboot boot either.

Maybe I'm asking too much, but is it possible for you to dump image(dd then zip) from your working rootfs ?

Thanks for all your troubles.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes