L4T Ubuntu - A fully featured linux on your switch

Silent_Gunner · Sep 26, 2020

Is there still work being done on this? As in, updates that will require more re-flashes? Or is everything pretty much "done" and "stable?" Because I vowed to not try setting this up on my hacked Switch until all the kinks were ironed out due to all the setup required to get everything working how one would expect on something like a Switch as opposed to a PC which usually has a M/KB attached on a consistent basis.

Deleted User · Sep 26, 2020

Silent_Gunner said:
Is there still work being done on this? As in, updates that will require more re-flashes? Or is everything pretty much "done" and "stable?" Because I vowed to not try setting this up on my hacked Switch until all the kinks were ironed out due to all the setup required to get everything working how one would expect on something like a Switch as opposed to a PC which usually has a M/KB attached on a consistent basis.

Version 3.0.2 will be released soon. Updates will not require re-flashes. About if its stable or done, well, kinda. I mean, it has some errors, but from my personal experience, its a pretty stable system

Silent_Gunner · Sep 26, 2020

Lang_Kasempo said:
Version 3.0.2 will be released soon. Updates will not require re-flashes. About if its stable or done, well, kinda. I mean, it has some errors, but from my personal experience, its a pretty stable system

Really? I remember when version 2.0 I think was rolling around, and the idea of not having to re-flash the image was tossed around, but that it wasn't gonna work, or so @bylaws said at the time.

Well, I guess I'll have to wait until version 3.0.2 (just for the sake of convenience) and a week of free time or something along those lines to go ahead and maybe give this another go!

ZachyCatGames · Sep 26, 2020

Silent_Gunner said:
Is there still work being done on this? As in, updates that will require more re-flashes? Or is everything pretty much "done" and "stable?" Because I vowed to not try setting this up on my hacked Switch until all the kinks were ironed out due to all the setup required to get everything working how one would expect on something like a Switch as opposed to a PC which usually has a M/KB attached on a consistent basis.

Occasional re-flashing will be required always, Nvidia makes changes to their rootfs that can't easily be applied without a reflash.
3.2.0, which is still based on L4T r32.3.1 and is coming soon, will not require a reflash.
4.0.0, which will be based on L4T r32.4.3, will require a reflash.

orangpelupa · Oct 2, 2020

hiya, anyone know one-click solution to have L4T ubuntu partition, normal switch partition, and EmuNAND partition on 1 microSD?

I remember months ago someone made a tool to do just that. But i no longer able to find it.

Currently i'm using Switch Android + Sysnand.

thank you

evil_santa · Oct 2, 2020

You can use this script https://github.com/lulle2007200/SwitchSDSetup under Linux.
Or you can use these images https://psxtools.de/forum/index.php...otimages-einrichten-emummc-android-linux-und/
Use Google translator.
The images contain an emummc android and ubuntu. Just flash whit etcher and done.

orangpelupa · Oct 2, 2020

evil_santa said:
You can use this script https://github.com/lulle2007200/SwitchSDSetup under Linux.
Or you can use these images https://psxtools.de/forum/index.php...otimages-einrichten-emummc-android-linux-und/
Use Google translator.
The images contain an emummc android and ubuntu. Just flash whit etcher and done.

thank you! that ready to burn image sounds really handy!!! Thanks a bunch!

Jules_Red · Oct 3, 2020

so i don't know if anybody else is having this issue or something similar, but after updating all software via apt upgrade the system begins to lock up for upwards of 2 minutes at a time

IGHOR · Oct 7, 2020

deleted

Gavin_Darkglider · Oct 7, 2020

3.2.0 released, Check OP. Should fix just about everything issue.... Update package is available for those that don't want to wipe their preexisting install in update section, and this is the first official release to use the hekate installer, so it comes with hekate images not etcher images for fresh install....

IGHOR said:
3.2.0 released

switchroot-ubuntu-3.2.0-2020-10-05.7z
switchroot-ubuntu-3.2.0-dev_cuda-2020-10-05.7z

just because we push the download doesn't mean it is your job to give people links to files they have no idea about.... This is a whole new format, and if.you tried to flash with etcher, like instructions said, it wouldn't work. Wait on the devs to push the proper documentation before releasing.stuff to people so we don't have to then explain to people how to fix something you didn't provide instructions for. Don't make our job harder, or I will stop releasing stuff.

IGHOR · Oct 7, 2020

Gavin_Darkglider said:
3.2.0 released

Don't you worry, I'll not do it again.
I have tested hekate installer and it installed correctly. Good to have multiple boot partitions.
Also I can't make TV mode to work, all my USB-C->HDMI adapters ignored, even not charging. Is there some command to force switch TV mode on and off?

Gavin_Darkglider · Oct 7, 2020

It should handle it directly.... Try applying update, just in case.

crow132 · Oct 8, 2020

hey there, probably this is a dumb question but im not too used to ubuntu

when i do apt-get update && apt-get upgrade i get this 20 packages i can not update

nvidia-l4t-3d-core nvidia-l4t-apt-source nvidia-l4t-camera
nvidia-l4t-configs nvidia-l4t-core nvidia-l4t-cuda nvidia-l4t-firmware
nvidia-l4t-graphics-demos nvidia-l4t-gstreamer nvidia-l4t-init
nvidia-l4t-initrd nvidia-l4t-jetson-io nvidia-l4t-multimedia
nvidia-l4t-multimedia-utils nvidia-l4t-oem-config nvidia-l4t-tools
nvidia-l4t-wayland nvidia-l4t-weston nvidia-l4t-x11 nvidia-l4t-xusb-firmware

is this normal? is there anyway to update this packages?

Gavin_Darkglider · Oct 8, 2020

crow132 said:
hey there, probably this is a dumb question but im not too used to ubuntu

when i do apt-get update && apt-get upgrade i get this 20 packages i can not update

nvidia-l4t-3d-core nvidia-l4t-apt-source nvidia-l4t-camera
nvidia-l4t-configs nvidia-l4t-core nvidia-l4t-cuda nvidia-l4t-firmware
nvidia-l4t-graphics-demos nvidia-l4t-gstreamer nvidia-l4t-init
nvidia-l4t-initrd nvidia-l4t-jetson-io nvidia-l4t-multimedia
nvidia-l4t-multimedia-utils nvidia-l4t-oem-config nvidia-l4t-tools
nvidia-l4t-wayland nvidia-l4t-weston nvidia-l4t-x11 nvidia-l4t-xusb-firmware

is this normal? is there anyway to update this packages?

Which image did you use? Those are all packages you have to download through a special app from nvidia, then a couple you need to patch, and should only be included in cuda development package, which is only needed to develop for cuda on switch. Once app is compiled, they shouldn't be needed anymore.

ZachyCatGames · Oct 8, 2020

crow132 said:
hey there, probably this is a dumb question but im not too used to ubuntu

when i do apt-get update && apt-get upgrade i get this 20 packages i can not update

nvidia-l4t-3d-core nvidia-l4t-apt-source nvidia-l4t-camera
nvidia-l4t-configs nvidia-l4t-core nvidia-l4t-cuda nvidia-l4t-firmware
nvidia-l4t-graphics-demos nvidia-l4t-gstreamer nvidia-l4t-init
nvidia-l4t-initrd nvidia-l4t-jetson-io nvidia-l4t-multimedia
nvidia-l4t-multimedia-utils nvidia-l4t-oem-config nvidia-l4t-tools
nvidia-l4t-wayland nvidia-l4t-weston nvidia-l4t-x11 nvidia-l4t-xusb-firmware

is this normal? is there anyway to update this packages?

You don't want to update them, it'll fuck up a bunch of stuff.

IGHOR · Oct 8, 2020

ZachyCatGames said:
You don't want to update them, it'll fuck up a bunch of stuff.

That should be kept in apt held by default.

tabzer · Oct 9, 2020

Regarding the 3.2.0 Update-

Using DD to edit and re-encode the boot.scr, I see a whole new approach in the script:

setenv linux_dir ubuntu
setenv rootdev mmcblk0p2
setenv hekate_id SWR-UBU

if load mmc 0:1 0x83000000 switchroot/${linux_dir}/Image; then setenv mmc_index 0;
elif load mmc 1:1 0x83000000 switchroot/${linux_dir}/Image; then setenv mmc_index 1;
else reset; fi;

load mmc ${mmc_index}:1 0x92000000 switchroot/${linux_dir}/initramfs
load mmc ${mmc_index}:1 0x8d000000 switchroot/${linux_dir}/tegra210-icosa.dtb

fdt addr 0x8d000000 ${filesize}
setenv ovcfgaddr 0x8d100000
setenv fdtovaddr 0x8d200000
setenv evtmpaddr 0x8d300000

# patch dtb with overlays if they exist
if load mmc ${mmc_index}:1 ${fdtovaddr} switchroot/${linux_dir}/uenv.txt && env import -t ${fdtovaddr} ${filesize} && test -n ${overlays}; then
echo loaded overlays.txt: ${overlays}
for ov in ${overlays}; do
echo overlaying ${ov}...
fdt resize 8192

if load mmc ${mmc_index}:1 ${ovcfgaddr} switchroot/${linux_dir}/overlays/${ov}.dtbo && fdt apply ${ovcfgaddr}; then
echo Successfully loaded ${ov}.dtbo...

# Add additional bootargs for UART-B
if test ${ov} = tegra210-icosa-UART-B-overlay; then setenv bootargs_extra ${bootargs_extra} ${uartb}; echo Enabled UART-B logging; fi
fi

# Add additional bootargs for Serial USB
if test ${ov} = usb_logging; then setenv bootargs_extra ${usblogging} ${bootargs_extra}; echo Enabled usb serial logging; fi

# Disable rootdev search done by initramfs
if test ${ov} = auto_rootdev_disable; then setenv bootargs_extra ${bootargs_extra} "auto_rootdev_disable"; fi

# Override and launch nfs bootargs here
if test ${ov} = nfs; then
if load mmc ${mmc_index}:1 ${evtmpaddr} switchroot/${linux_dir}/overlays/nfs.txt && env import -t ${evtmpaddr} ${filesize}; then
run nfsargs_run
echo Using NFS root
fi
fi
done
fi

run kernelcmd_run

usb reset
booti 0x83000000 0x92000000 0x8d000000

On previous iterations, I was able to change all instances of "mmcblk0p2" to "mmcblk0p9" to work with my customized partition setup, for multi-boot purposes.

Now, I when I try the same thing, I run into a bootloop. I am only able to get as far as into the new splashscreen with Tux overlaying an open CPU, with the text "booting..." at the bottom. Then it restarts to my payload. Is there there something I can do to maintain my multi-boot setup?

tabzer · Oct 9, 2020

SOLUTION FOUND: Instead of messing with boot.scr from this point out, all that needs to be changed is the label of the Ubuntu partition on the SDcard. Label should be "SWR-UBU". Credit to Daj on switchroot discord for this.

Yo_Homie · Oct 9, 2020

I have updated from what I believe was 1.3.1 to 3.2.0 and Wi-Fi stopped working. Bluetooth still is though. Any ideas how to fix this?

IGHOR · Oct 10, 2020

I flashed 3.2.0 again just to confirm that I have not install any updates that have break something. The result:

None of my USB-C->HDMI adapter works, even Jumpgate is not working. They all did work on previous builds, not always, but time to time.
Clicks of a USB mouse including touch screen freezes sometimes, can't press any UI buttons, mouse is movable still, but can't do anything. I wasn't able to finish standard Ubuntu welcome dialog because of this. At the same time USB keyboard working as expected, I can change a focus and close/open windows. And some time later mouse starts working again.

As I remember, issues with touch screen and docking mode seen in every build and they remains to be in latest builds.
So change-log note of "Should fix just about everything issue" is far from truth.
Trying every next build just to find out that old bugs are fixed, but even when developer noted that they are fixed, they still there, it is really annoying.

Anyway thanks to the DEV, for hard work, I hope that some day we finally will be able to use Ubuntu without issues.

Crazy Cool Cyclops

Deleted User

Guest

Crazy Cool Cyclops

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

This place is a meme.

This place is a meme.

Member

Well-Known Member

Similar threads

Popular threads in this forum