L4T Ubuntu - A fully featured linux on your switch

tabzer · Oct 10, 2020

IGHOR said:
They all did work on previous builds, not always, but time to time.

Not always? Like screen flashes, or...?

IGHOR said:
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.

Is this with 3.2.0 or before? I know Jumpgate has issues that are Jumpgate specific issues, which seems to be not playing well with USB devices. If you have other devices you are trying to use, it'd be good to know what they are.

IGHOR said:
As I remember, issues with touch screen and docking mode seen in every build and they remains to be in latest builds.

Every iteration they have released, and stated improved touchscreen, had testable and observable improvements.

IGHOR said:
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.

Try joining the Discord server and work with a dev. Maybe you can find out the solution to your particular issues and contribute to a better build along the way.

imx3110 · Oct 11, 2020

I'm using the Jumpgate and it works perfectly for me. (Earlier version didn't).
Might be the you need a fresh install? I downloaded the 3.2.0 version, flashed it and then applied the update (before booting). Works smooth as heck. Easily the best build yet.

IGHOR · Oct 11, 2020

tabzer said:
Not always? Like screen flashes, or...?
Is this with 3.2.0 or before? I know Jumpgate has issues that are Jumpgate specific issues, which seems to be not playing well with USB devices. If you have other devices you are trying to use, it'd be good to know what they are.
Every iteration they have released, and stated improved touchscreen, had testable and observable improvements.
Try joining the Discord server and work with a dev. Maybe you can find out the solution to your particular issues and contribute to a better build along the way.

Pre 3.2.0: no screen flashes, everything works fine, but in one moment it starts ignoring the dock and external monitor, until full reboot. I have reported this few times already.
3.2.0: just none of my dongle works right on the first boot, and every next one.
Tested JumpGate, Apple USB+HDMI->USB-C adapter, and Satechi one.
Yes, Touch screen is much improved then first builds. As I said already, the issue remains with usb mouse connected, so it is actually not related to touch screen. It looks like some Ubuntu bug with a mouse.
Maybe I really should to report those in Discord instead, and I'll do it, thanks.

Silent_Gunner · Oct 16, 2020

So, I figured I'd give this a shot, and tried to boot into 3.2.0 now that it just released 11 days ago, and am at a red screen saying that it failed to mount rootfs and that the device will reboot in 10 seconds which, btw, its been more than 10 seconds and I'm still seeing red on the Switch tablet itself. :/

EDIT: Nvm. The world's always changing around us...

Gavin_Darkglider · Oct 17, 2020

IGHOR said:
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.

You are the only person reporting any of these problems. So, assuming you didn't do something wrong, like boot the wrong coreboot, because you didn't delete the old ubuntu boot files, or there is something wrong with your setup.

Silent_Gunner · Oct 17, 2020

So, does the Flycast core in RetroArch just not work on this version of Ubuntu or something? Because any game I try to load, it "fails to load the content" even though everything is set up correctly, just how I have it set up on my PC, with everything being in the right folders.

shim80 · Oct 18, 2020

Is there a way to upgrade to 20.04.1 without breaking switch packages ?

Silent_Gunner · Oct 18, 2020

This topic's dead nowadays...

Astrose · Oct 22, 2020

It says that I'm missing an partition how to I fix this issue

--------------------- MERGED ---------------------------

It says that I'm missing an partition how do I fix this issue.

Imancol · Oct 22, 2020

groslaine · Oct 25, 2020

Is there a way to use the joycon as a mouse ? Like having the cursor moving with the joystick ?

evil_santa · Oct 25, 2020

look in this thread
https://gbatemp.net/threads/l4t-ubuntu-applcation-install-guides.537579/

Astrose · Oct 26, 2020

Is there a way to get steam working on L4T Ubuntu

Worldblender · Oct 26, 2020

Astrose said:
Is there a way to get steam working on L4T Ubuntu

It's unlikely to work; the Steam client is likely in x86 form only, so it won't run native without qemu-user, or a virtual machine. Even if it could run on ARM devices, almost no games found there have binaries that can natively run on ARM devices, unless with emulation (which will have some performance tank).

Astrose · Oct 26, 2020

I thought that might be the case. Thanks

shim80 · Oct 27, 2020

Astrose said:
Is there a way to get steam working on L4T Ubuntu

Try this : https://github.com/ptitSeb/box86
Box86 allow to install wine/steam and launch some x86 software or games. This solution doesn't emulate everything like qemu, some libraries are already compiled for arm, so it's more like partial emulation. It's way more fast than qemu, and some games are working in full speed (Celeste, Shovel Knight, Half-Life, Portal...)

Silent_Gunner · Oct 28, 2020

shim80 said:
Try this : https://github.com/ptitSeb/box86
Box86 allow to install wine/steam and launch some x86 software or games. This solution doesn't emulate everything like qemu, some libraries are already compiled for arm, so it's more like partial emulation. It's way more fast than qemu, and some games are working in full speed (Celeste, Shovel Knight, Half-Life, Portal...)

Can someone say how effective this is? What's the performance hit it'd inflict? And I take it that Wine would be above the Switch's alcohol tolerance level, if you know what I mean?

Granted, the code would have to be adapted to work on ARM64 devices, but my understanding is that one could fork what the Box86 dev(s) are doing and go off of what they're doing to make the Switch a cheaper GPD WIN...or would that be GPD LIN?

Yo_Homie · Oct 31, 2020

Every time I run apt update I get:

$ sudo apt update
[sudo] password for user:
Get:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Ign:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Get:2 file:/var/visionworks-repo InRelease
Ign:2 file:/var/visionworks-repo InRelease
Get:3 file:/var/visionworks-sfm-repo InRelease
Ign:3 file:/var/visionworks-sfm-repo InRelease
Get:4 file:/var/visionworks-tracking-repo InRelease
Ign:4 file:/var/visionworks-tracking-repo InRelease
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Err:11 http://turul.canonical.com bionic InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:14 http://turul.canonical.com bionic-updates InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:15 http://turul.canonical.com bionic-backports InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:16 http://turul.canonical.com bionic-security InRelease
502 Connection refused [IP: 91.189.91.11 80]
Get:18 https://repo.download.nvidia.com/jetson/common r32 InRelease [2,541 B]
Get:17 https://repo.switchroot.org unstable/ InRelease [1,631 B]
Get:19 https://repo.download.nvidia.com/jetson/t210 r32 InRelease [2,555 B]
Get:20 https://repo.switchroot.org unstable/ Packages [1,796 B]
Get:21 https://repo.download.nvidia.com/jetson/t210 r32/main arm64 Packages [8,084 B]
Fetched 16.6 kB in 4s (3,912 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://turul.canonical.com/dists/bionic/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-updates/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-backports/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-security/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

I cannot install any packages. I have tried reinstalling multiple times, running a VPN to CA and a lot of other random things, but cannot figure out what is going on. Any ideas?

sergio_prado · Oct 31, 2020

Yo_Homie said:
Every time I run apt update I get:

$ sudo apt update
[sudo] password for user:
Get:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Ign:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Get:2 file:/var/visionworks-repo InRelease
Ign:2 file:/var/visionworks-repo InRelease
Get:3 file:/var/visionworks-sfm-repo InRelease
Ign:3 file:/var/visionworks-sfm-repo InRelease
Get:4 file:/var/visionworks-tracking-repo InRelease
Ign:4 file:/var/visionworks-tracking-repo InRelease
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Err:11 http://turul.canonical.com bionic InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:14 http://turul.canonical.com bionic-updates InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:15 http://turul.canonical.com bionic-backports InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:16 http://turul.canonical.com bionic-security InRelease
502 Connection refused [IP: 91.189.91.11 80]
Get:18 https://repo.download.nvidia.com/jetson/common r32 InRelease [2,541 B]
Get:17 https://repo.switchroot.org unstable/ InRelease [1,631 B]
Get:19 https://repo.download.nvidia.com/jetson/t210 r32 InRelease [2,555 B]
Get:20 https://repo.switchroot.org unstable/ Packages [1,796 B]
Get:21 https://repo.download.nvidia.com/jetson/t210 r32/main arm64 Packages [8,084 B]
Fetched 16.6 kB in 4s (3,912 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://turul.canonical.com/dists/bionic/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-updates/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-backports/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-security/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

I cannot install any packages. I have tried reinstalling multiple times, running a VPN to CA and a lot of other random things, but cannot figure out what is going on. Any ideas?

I'm having the same problem. Yesterday I spend almost all the day googling on how to solve this problem, but with no avail. Seems like it is a server issue or something like that, because few days ago it was working fine.

Worldblender · Oct 31, 2020

Yo_Homie said:
Every time I run apt update I get:

$ sudo apt update
[sudo] password for user:
Get:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Ign:1 file:/var/cuda-repo-10-0-local-10.0.326 InRelease
Get:2 file:/var/visionworks-repo InRelease
Ign:2 file:/var/visionworks-repo InRelease
Get:3 file:/var/visionworks-sfm-repo InRelease
Ign:3 file:/var/visionworks-sfm-repo InRelease
Get:4 file:/var/visionworks-tracking-repo InRelease
Ign:4 file:/var/visionworks-tracking-repo InRelease
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:5 file:/var/cuda-repo-10-0-local-10.0.326 Release [574 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Get:6 file:/var/visionworks-repo Release [1,999 B]
Get:7 file:/var/visionworks-sfm-repo Release [2,003 B]
Get:8 file:/var/visionworks-tracking-repo Release [2,008 B]
Err:11 http://turul.canonical.com bionic InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:14 http://turul.canonical.com bionic-updates InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:15 http://turul.canonical.com bionic-backports InRelease
502 Connection refused [IP: 91.189.91.11 80]
Err:16 http://turul.canonical.com bionic-security InRelease
502 Connection refused [IP: 91.189.91.11 80]
Get:18 https://repo.download.nvidia.com/jetson/common r32 InRelease [2,541 B]
Get:17 https://repo.switchroot.org unstable/ InRelease [1,631 B]
Get:19 https://repo.download.nvidia.com/jetson/t210 r32 InRelease [2,555 B]
Get:20 https://repo.switchroot.org unstable/ Packages [1,796 B]
Get:21 https://repo.download.nvidia.com/jetson/t210 r32/main arm64 Packages [8,084 B]
Fetched 16.6 kB in 4s (3,912 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://turul.canonical.com/dists/bionic/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-updates/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-backports/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Failed to fetch http://turul.canonical.com/dists/bionic-security/InRelease 502 Connection refused [IP: 91.189.91.11 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

I cannot install any packages. I have tried reinstalling multiple times, running a VPN to CA and a lot of other random things, but cannot figure out what is going on. Any ideas?

sergio_prado said:
I'm having the same problem. Yesterday I spend almost all the day googling on how to solve this problem, but with no avail. Seems like it is a server issue or something like that, because few days ago it was working fine.

Try replacing "turul.canonical.com" with "ports.ubuntu.com"; it may lead to a different server.

This place is a meme.

New Member

Well-Known Member

Crazy Cool Cyclops

Well-Known Member

Crazy Cool Cyclops

Well-Known Member

Crazy Cool Cyclops

New Member

Otak Productions

New Member

Well-Known Member

New Member

Well-Known Member

New Member

Well-Known Member

Crazy Cool Cyclops

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum