L4T Ubuntu - A fully featured linux on your switch

ThaDean · Aug 20, 2020

enzobelmont said:
yes, in a first step I dumped the file with this command: 'dd if=boot.scr of=boot.txt bs=72 skip=1', then edited the resulting boot text file to point to the linux partition, then repack again the boot.scr file with this other command: 'mkimage -A arm -T script -O linux -d boot.txt boot.scr'.

I used my laptop with linux for partitioning, and files management.

Black screen

tabzer · Aug 21, 2020

enzobelmont said:
1st.- HOS_DATA: horizon and switch stuff
2nd, 3rd, 4th, 5th and 6th.- Android partitions: Vendor, system, boot, recovery and dtb. all this stuff is necessary to run android.
7th.- Android user data: ,Where I store all my android stuff
and 8th.- UBUNTU, my ubuntu partition.
that's all.

Would Ubuntu benefit from a swap partition? lol.

ThaDean said:
Black screen

You are going to have to be patient with yourself and try to figure out what you did wrong. There isn't a lot poeple can do except ask you 20 questions to try to fish information from you. It's probably better for you to retrace your steps and ask yourself "why?" for each step than it is to have someone else to do it for you.

enzobelmont · Aug 21, 2020

ThaDean said:
Black screen

black screen and a f*cking hot switch is the result of a wrong partition selection on boot.scr, please refer to this thread https://gbatemp.net/threads/partition-based-emummc-and-l4t-ubuntu-on-the-same-sd-card.543956/ there are a lot info.

tabzer · Aug 21, 2020

Or he made the img file incorrectly, or he flashed it incorrectly. It's optimism that relays the suspicion to these three. But if he screwed up any of those, then it's possible that he doesn't even know what partitions he has (if he created any). We don't exactly have information volunteered from the guy; which makes trying to troubleshoot "Black screen

" frustrating.

ThaDean · Aug 21, 2020

I follow enzobelmont's indicatio step by step (I did this on linux). I'll retry soon

tabzer · Aug 21, 2020

Well, his setup includes having installed Android and all of its partitions, as well as handling his CFW--a modded setup, which is why he talked about modifying his boot.scr file. I'm not sure what your goal is, because your first message could be interpreted as wanting to get L4T Ubuntu onto an SD card, and the OP is all you need to get started--with no need to edit the scr file. You can also have complex setups as discussed here: https://gbatemp.net/threads/setup-g...id-with-emummc-bigger-fat32-partition.544981/

You can pretty much have it anyway you want. But first you have to decide exactly how you want it.

paintispaint · Aug 21, 2020

Gavin_Darkglider said:
Ok, Dev info update, new version around the corner.... This includes hekate images, Bluetooth fixes(audio works fully, and firmware updated for antenna fixes), pci sleep fixes(wifi sleeps properly now, other misc bugs have been fixed as well. Should be released this week so keep an eye for updates, have latest stuff in final testing.... Big thanks to ctcaer and azkali for all the work they put into the latest release. 3.0.2 should be coming soon.

Super excited for Hekate images thank you! previously tried to flash the img but it wouldn't fit on the sd card as it was over 4gb

ThaDean · Aug 21, 2020

I did it again. I use a empty sd only for ubuntu
This is the situation:

But didn't work :wacko:

quacka · Aug 22, 2020

I am also getting a black screen using 3.0.1 whilst 3.0.0 boots fine. freshly imaged card with nothing else but l4t

tabzer · Aug 22, 2020

ThaDean said:
I did it again. I use a empty sd only for ubuntu
This is the situation: View attachment 222390 View attachment 222391 View attachment 222392
But didn't work

Like I said before, for this situation you don't need to edit the boot.scr. You are breaking it.

It's supposed to read "setenv bootargs 'root=/dev/mmcblk0p2" which it already does by default. You are renaming it to how your computer addresses it and not how the switch addresses it.

quacka said:
I am also getting a black screen using 3.0.1 whilst 3.0.0 boots fine. freshly imaged card with nothing else but l4t

He's trying 3.0.2 You are doing something wrong as all versions have been bootable.

quacka · Aug 22, 2020

I am not sure what I did wrong as I thought the steps were straight forward as well.

Downloaded 3.0.0, extracted and flash this image with balenaEtcher
Downloaded the latest hekate_ctcaer_5.3.2_Nyx_0.9.3.zip and extracted to the root of fat32 partition
Boot into hekate, set the time and dump joycon pairing info
Launch Ubuntu from config and everything works fine setting this up, go into desktop and then shutdown
Took out SD card and deleted l4t-ubuntu folder and deleted the file bootloader\ini\01-ubuntu.ini
Extracted the content of update-3.0.1-for-switchroot-l4t-ubuntu-3.0.0-2020-03-02.zip into the root of the fat32 partition
Boot into hekate and dump joycon pairing info again just to be safe
Launch Ubuntu from config, waited for about 10 minutes and nothing boots

ThaDean · Aug 22, 2020

tabzer said:
Like I said before, for this situation you don't need to edit the boot.scr. You are breaking it.

It's supposed to read "setenv bootargs 'root=/dev/mmcblk0p2" which it already does by default. You are renaming it to how your computer addresses it and not how the switch addresses it.

Now work but black screen after the installation

tabzer · Aug 22, 2020

quacka said:
I am not sure what I did wrong as I thought the steps were straight forward as well.

Downloaded 3.0.0, extracted and flash this image with balenaEtcher

Downloaded the latest hekate_ctcaer_5.3.2_Nyx_0.9.3.zip and extracted to the root of fat32 partition

Boot into hekate, set the time and dump joycon pairing info

Launch Ubuntu from config and everything works fine setting this up, go into desktop and then shutdown

Took out SD card and deleted l4t-ubuntu folder and deleted the file bootloader\ini\01-ubuntu.ini

Extracted the content of update-3.0.1-for-switchroot-l4t-ubuntu-3.0.0-2020-03-02.zip into the root of the fat32 partition

Boot into hekate and dump joycon pairing info again just to be safe

Launch Ubuntu from config, waited for about 10 minutes and nothing boots

It sounds like you are doing it right. During your step 4, I would probably run apt update && apt upgrade, along with resizing the disk to be full size (this part is mentioned in the OP). I can only speculate it could be related to lack of disk space to install modules.tar (getting stuck?), or there are certain updates it needs to be done to handle it smoothly. I would test the 3.0.0 environment and then update it after you test it for stability via normal use.

quacka · Aug 23, 2020

3.0.1 still don't work even after partition resizing and update.

tabzer · Aug 23, 2020

quacka said:
3.0.1 still don't work even after partition resizing and update.

How many times did you reboot it to see if it was stable, before installing the update? What did you use to extract the update? How long did you let it sit at the black screen before concluding that it doesn't work? Are you using the FULL install of 3.0.0, or the LITE?

ThaDean · Aug 23, 2020

I try again. After initial setup (language, wifi, time zone) black screen

Kordru · Sep 4, 2020

this is beautiful

cucholix · Sep 6, 2020

Can you use use your main SD and partitioning? Also it’s possible to boot this through fastCFWswitch overlay?

evil_santa · Sep 6, 2020

cucholix said:
Can you use use your main SD and partitioning? Also it’s possible to boot this through fastCFWswitch overlay?

Yes it's possible

groslaine · Sep 10, 2020

Do we have an idea when will the next version (3.0.2) will be release ?

Member

This place is a meme.

Active Member

This place is a meme.

Member

This place is a meme.

Member

Member

Member

This place is a meme.

Member

Member

This place is a meme.

Member

This place is a meme.

Member

Well-Known Member

00000780 00000438

Well-Known Member

New Member

Similar threads

Popular threads in this forum