L4T Ubuntu - A fully featured linux on your switch

HappehLemons · Jun 11, 2020

TheCasualties said:
There should be a button in the top bar, on the right. Think it's a rectangle with some lines? If you can tap on it, it should drop down a menu where it'll have onscreen keyboard options.

Thanks! It looks like it's 4 squares. It's the option "Show onboard" very cryptic, thanks for helping me!

Presentz · Jun 12, 2020

TheCasualties said:
That's where this post comes in. Page 113. It has a download in the post.

Find that page on your L4T chromium browser and download the file. Then use sudo mv to move the map file, so the command you put in the terminal is

sudo mv '/home/USERNAME/Downloads/50-joystick.conf' '/usr/share/X11/xorg.conf.d'

*and replace USERNAME with the username on your L4T. Hopefully you can just copy/paste that on your switch and change username, or use SSH on pc to post it exactly.

"no such file or directory", I extracted the zip, checked the directory was right, same result :/

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

TheCasualties said:
That's where this post comes in. Page 113. It has a download in the post.

Find that page on your L4T chromium browser and download the file. Then use sudo mv to move the map file, so the command you put in the terminal is

sudo mv '/home/USERNAME/Downloads/50-joystick.conf' '/usr/share/X11/xorg.conf.d'

*and replace USERNAME with the username on your L4T. Hopefully you can just copy/paste that on your switch and change username, or use SSH on pc to post it exactly.

nevermind! tysm for the hella helpful replies! While we're here is there a way to have the joycons connect automatically or do I have to delete and reconnect them everytime and is there a way to ajust sensitivity? Thanks again!

TheCasualties · Jun 12, 2020

Presentz said:
"no such file or directory", I extracted the zip, checked the directory was right, same result :/

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

nevermind! tysm for the hella helpful replies! While we're here is there a way to have the joycons connect automatically or do I have to delete and reconnect them everytime and is there a way to ajust sensitivity? Thanks again!

I've not found a way to have them connect to blutooth automatically yet. Been doing what you've described. You may be able to adjust sensitivity in that mapping file, but I've not checked it out yet.

I noticed Hekate now has a "Dump joycon BT", it says for android and linux, but I have no idea how to use it yet. Haven't been able to find more info about it.

from the Hekate 5.2.0 update: "Add Joy-Con Bluetooth pairing info dump. Used in L4T Android/Linux."

Presentz · Jun 13, 2020

TheCasualties said:
I've not found a way to have them connect to blutooth automatically yet. Been doing what you've described. You may be able to adjust sensitivity in that mapping file, but I've not checked it out yet.

I noticed Hekate now has a "Dump joycon BT", it says for android and linux, but I have no idea how to use it yet. Haven't been able to find more info about it.

from the Hekate 5.2.0 update: "Add Joy-Con Bluetooth pairing info dump. Used in L4T Android/Linux."

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

Thanks, I'll look around for the joycon thing. Sorry for all the questions but do u know where stuff downloaded from the store gets put? I know its on finder but I dont know where on the sd. Sorry again.

FellFromTheSky · Jun 15, 2020

@bylaws
dunno why, but it seems that L4T Ubuntu always reboot to Hakate 5.1.1 instead of Hekate 5.3.0. My NAND version is 10.0.4. How to fix it?

Gavin_Darkglider · Jun 23, 2020

3.0.1 released check op for update file, and instructions. This should fix most all issues.

evil_santa · Jun 23, 2020

Great Gavin
But have you uploaded the right update file?
The name is 3.0.0?

Gavin_Darkglider · Jun 23, 2020

Check update section of op, the link is there.

TheCasualties · Jun 23, 2020

I ran into a bit of an issue while updating. Didn't have a 01-ubuntu.ini, only 00-ubuntu. Likely because I used 'lite' version? It's only the launch config tho, so it shouldn't matter, right?

Followed the update instructions but I'm just getting a black screen while trying to boot to ubuntu now. Let it sit for 5+ minutes incase it was just taking a while, but nothing happens. Have to hold power to turn off the system.

PS: Also updated Hekate/Nyx to latest version. It works with 3.0.0 so i don't think thats the issue.

Edit: managed to extract the old l4t folder and restore my working 3.0.0 setup at least. Then tried updating again but still getting black screen. I'll just revert to 3.0.0 until someone more knowledgeable can help out. The update instructions are simple to follow, so IDK what the issue is. Are there any log files for this that I could post?

Edit2: Has everyone else managed to upgrade without issue? I'm wondering if something I installed to Ubuntu is the problem, but I really have no idea why I can't get 3.0.1 to boot.

The Official GMan · Jun 25, 2020

As has already been mentioned multiple times earlier in the thread. There seems to be an issue with the bluetooth in version 3.0.0 that wasn't present in earlier versions. I only have experience in version 3.0 but I can say that joycon and pro controller range/ connection consistency is significantly decreased from the stock NS OS bluetooth range. Usually I can travel a few dozen feet away with a good bluetooth connection but under L4T Ubuntu I have to be within a couple of feet of the switch to keep the joycons and pro controller from disconnecting.

(Note: I haven't updated to 3.0.1, not sure if this update is supposed to fix the range/incompatibility issues)

Gavin_Darkglider · Jun 25, 2020

The Official GMan said:
As has already been mentioned multiple times earlier in the thread. There seems to be an issue with the bluetooth in version 3.0.0 that wasn't present in earlier versions. I only have experience in version 3.0 but I can say that joycon and pro controller range/ connection consistency is significantly decreased from the stock NS OS bluetooth range. Usually I can travel a few dozen feet away with a good bluetooth connection but under L4T Ubuntu I have to be within a couple of feet of the switch to keep the joycons and pro controller from disconnecting.

(Note: I haven't updated to 3.0.1, not sure if this update is supposed to fix the range/incompatibility issues)

Not sure about that issue, but there were a few updates to both the joycon drivers, one of which for the Bluetooth hid driver was for an issues with rumble queue, where it was spamming Bluetooth. So maybe it will work better now.

As for the update, some people are having issues with it not booting. So backup the deleted files if you are going to try this.

TheCasualties · Jun 25, 2020

If it helps, I have retroarch, Ishiiruka dolphin, and Psensor installed. Xorg for the joycon-mouse too.
I may try uninstalling these and testing the update

Gavin_Darkglider · Jun 25, 2020

No need to erase those, just keep old boot files for now, if kernel doesn't boot, you will want them to restore.

Jertrn2g · Jun 26, 2020

Updated from 3.0 to 3.0.1 and everything works ok, fixed the battery misread icon (never showed the correct % left because it was kind of trying of make a resume of the mix 3 battery reads), now you can play undocked and then dock the switch and it will synchronize both joycons right away.
The only "problem" i've noticed is that i can't find out a way to put the switch to "sleep"/turn of the screen by any means; but that's a minor issue for me.

Gavin_Darkglider · Jun 27, 2020

First hard as hell to read all that, use a different color for font. Second, sleep works fine hit power button, it will go to lp0.... If you are looking for just screen off, look into dpms.

HappehLemons · Jul 7, 2020

Has anyone had success with retroarch building with N64 cores? Retroarch seems to be really feature light and missing a lot of essential settings + cores seen in other builds of RA on switch using things like HOS, Lakka or Switchroot.

OkazakiTheOtaku · Jul 8, 2020

Having some issues getting this working well.
I followed the guide, got it all installed, and I can boot to the Ubuntu login screen.
When I get to the login screen, the system goes nuts and just rotates the screen back and forth between Landscape and Portrait orientation, making it impossible to login. Not sure if it's a gyroscope (does this even support the gyro) issue or a graphics issues.

One time I did manage to get logged in, and it was fine, but it didn't see any wifi signals. So I tried rebooting, but after Ubuntu shuts down it just cuts the power to the console; it doesn't reboot me back to Linux or Hekate or RCM or anything. Anyone know what's going on?

Worldblender · Jul 8, 2020

OkazakiTheOtaku said:
Having some issues getting this working well.
I followed the guide, got it all installed, and I can boot to the Ubuntu login screen.
When I get to the login screen, the system goes nuts and just rotates the screen back and forth between Landscape and Portrait orientation, making it impossible to login. Not sure if it's a gyroscope (does this even support the gyro) issue or a graphics issues.

One time I did manage to get logged in, and it was fine, but it didn't see any wifi signals. So I tried rebooting, but after Ubuntu shuts down it just cuts the power to the console; it doesn't reboot me back to Linux or Hekate or RCM or anything. Anyone know what's going on?

That shutdown does what it says: shutdown the system, then power off. You might try reboot/restart instead.

OkazakiTheOtaku · Jul 8, 2020

Worldblender said:
That shutdown does what it says: shutdown the system, then power off. You might try reboot/restart instead.

Thanks for the suggestion, but that's actually what I did.

OkazakiTheOtaku said:
So I tried rebooting

I'm not that dumb.

What I meant by that is after the verbose real-time reading of what's going on (after selecting reboot) it cuts power.

Worldblender · Jul 8, 2020

OkazakiTheOtaku said:
Thanks for the suggestion, but that's actually what I did.

I'm not that dumb.

What I meant by that is after the verbose real-time reading of what's going on (after selecting reboot) it cuts power.

Then, that part, I may not be able to help out much on. I don't use L4T Ubuntu on my Switch as much because of how inconvenient it can be to execute a payload in RCM mode at times. I often just use standard Ubuntu (as KDE Neon) on my desktop and laptop computers.

Well-Known Member

New Member

Just trying to be helpful

New Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Just trying to be helpful

Well-Known Member

Well-Known Member

Just trying to be helpful

Well-Known Member

New Member

Well-Known Member

Well-Known Member

no thanks, I don't want a custom title

Well-Known Member

no thanks, I don't want a custom title

Well-Known Member

Similar threads

Popular threads in this forum