Tutorial  Updated

How to boot Linux on your Switch

THIS GUIDE IS DEPRECATED
THIS IS BETTER https://github.com/natinusala/painless-linux


I've successfully booted ArchLinux using ShofEL2. Here is a quick guide on how to do it - I'll assume you're computer literate and know how to use a terminal / Linux commands / git.
Everything is taken from the README of the ShofEL2 repo so if you want to go even faster, go read that instead.

Thanks to NightHammer1000 and Y2K-x for the help !

There is a simplified and faster version of this tutorial available here, with precompiled binaries so you don't have to build everything : https://github.com/SoulCipher/shofel2_linux

The result

Without a SD card ("waiting for root device mmcblk0p2") : https://photos.app.goo.gl/7y6ut5ObuHMUIMZg2
Stock Arch Linux : https://photos.app.goo.gl/yALqe3zMZRe2dSQf1
Arch Linux with LXDE : https://photos.app.goo.gl/xaEgRqeSi8jvAwpz5
RetroArch running : https://photos.app.goo.gl/vBLPo5wiBto1qiUH3
Arch Linux with GNOME : https://gbatemp.net/attachments/img_0005-jpg.121608/
Arch Linux with KDE : https://gbatemp.net/attachments/img_20180427_121605-jpg.121666/

What works / what doesn't
  • Desktop environment : Gnome, LXDE, KDE
  • Wi-Fi : works
    • You will need to reboot your Switch and run the exploit again to make the Wi-Fi work (it never works on the first boot)
    • Then enter the Network Manager Application and add your network from there
    • If it doesn't work, you will need to edit the configuration on the host computer (see the additional notes at the end of this post)
    • With LXDE : Can cause a kernel panic if used at the same time as Bluetooth
  • Bluetooth : works but Joy-Cons can't be paired
  • Touch screen : works, although LXDE is not very touch-friendly
  • Audio : doesn't work yet
  • GPU acceleration : works (via mesa), with OpenGL (and maybe Vulkan too ?)
  • Joy-Cons : not recognized
  • Volume buttons : working with Gnome but not doing anything since there is no audio device
  • Power button : doesn't do anything, no sleep mode, no graceful shutdown
  • USB : doesn't work
  • Dock : not tested yet, but I bet it doesn't do anything besides charging the battery
  • Power management / battery level : working with Gnome
What you'll need
  • A computer running Linux with a blue USB SuperSpeed port, or a Mac
    • A Linux VM can work in theory, but it depends on how the USB passthrough is implemented (apparently VMWare works, VirtualBox doesn't)
  • A USB A-to-C cable (with data support, obviously)
    • be careful as cheap cables were reported to work randomly / not work at all
  • Some time (you know, Linux is kinda large)

Prep work

First, you'll need to install the required toolchains. Open this link and download the tar.gz binaries for
  • aarch64-linux-gnu
  • arm-linux-gnueabi
Be careful to choose the right architecture for your PC (for me it was x86_64 so "gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabi.tar.xz").

Once you have them, extract them somewhere nice and add the "bin" (not "lib" as I previously stated) folder of both toolchains to your PATH ("$ export PATH=$PATH:/path/to/toolchain1/lib:/path/to/toolchain2/lib"). The building process won't work otherwise.

Then, install those dependencies (how to install them and their name might depend on your distribution) :
  • build-essential (sorry I didn't add it it was obvious to me)
  • libssl-dev
  • swig
  • bison
  • pkg-config
  • flex
  • zlib1g-dev
  • python3
  • python-dev
  • python3-pip
  • pyusb 1.0.0 : "$ sudo pip3 install pyusb==1.0.0"
  • libusb-1.0-0-dev

Compiling

Clone each required repository :

Code:
$ git clone https://github.com/fail0verflow/shofel2.git
$ git clone --recursive --depth=1 https://github.com/fail0verflow/switch-coreboot.git coreboot
$ git clone https://github.com/fail0verflow/switch-u-boot.git u-boot
$ git clone --depth=1 https://github.com/fail0verflow/switch-linux.git linux
$ git clone https://github.com/boundarydevices/imx_usb_loader.git

You can grab a coffee or two because Linux has more than 5 million files to download.

Then, build everything :

Code:
$ cd shofel2/exploit
$ make

Code:
$ cd u-boot
$ export CROSS_COMPILE=aarch64-linux-gnu-
$ make nintendo-switch_defconfig
$ make

Code:
$ cd coreboot
$ make nintendo_switch_defconfig
$ make iasl
$ make

If you have a tegra_mtc.bin file error, you'll have to extract it from a Pixel C stock image :
"$ ./build/util/cbfstool/cbfstool bootloader-dragon-google_smaug.7900.97.0.img extract -n fallback/tegra_mtc -f tegra_mtc.bin"

Or you can download it directly from here : https://0w0.st/tegra_mtc.bin (thanks to @CptPotato for uploading this)

You'll have to put it in the "coreboot/src/soc/nvidia/tegra210" directory.

Code:
$ cd imx_usb_loader
$ git reset --hard 0a322b01cacf03e3be727e3e4c3d46d69f2e343e
$ make

The big one :

Code:
$ cd linux
$ export ARCH=arm64
$ export CROSS_COMPILE=aarch64-linux-gnu-
$ make nintendo-switch_defconfig
$ make

If you encounter issues about a missing rule "/lib/firmware/nvidia/tegra210/vic04_ucode.bin" for the target "firmware" you'll have to :
  • install the firmware-misc-nonfree package
  • if you can't install it, or if it still doesn't work, download the package manually from debian sid and extract the file "/lib/firmware/nvidia/tegra210/vic04_ucode.bin" (from the root of your PC, not on the cloned repo) from the DEB (and chmod it if needed)
If you encounter issues about a missing rule "/lib/firmware/brcm/brcmfmac4356-pcie.txt", download this file and put it in "/lib/firmware/brcm/" (from the root of your PC, not on the cloned repo)

Building the rootfs

This is the annoying part. Download the archive / image corresponding to the distribution you want to use :
If it's a tarball you just downloaded

While it's downloading, you'll have to take a microSD card and, using the software of your choice (I used GParted) :
  • remove every existing partition to only have unallocated space on it (do I need to tell you that you're going to loose everything on the card ?)
  • create a tiny FAT32 partition (I chose 200mb but it doesn't matter) - that'll be mmcbkl0p1, you can label it "garbage"
  • create an ext4 partition on the remaining part of the card - that'll be mmcblk0p2, you can label it "rootfs"
  • it's important that the FAT32 partition comes first and the ext4 one comes after - on the Switch, Linux will look for mmcblk0p2, the second partition, if you have scrolling boot logs and then back to RCM it means you did it wrong
Once the rootfs tarball is downloaded, you can simple extract it to the mounting point of the ext4 partition you just created :

Code:
$ tar xvf ArchLinuxARM-aarch64-latest.tar.gz -C /mounting/point/of/ext4/partition && sync
$ cp ArchLinuxARM-aarch64-latest.tar.gz /mounting/point/of/ext4/partition/root && sync

("/mounting/point/of/ext4/partition/root" is the "root" directory on the partition)

Don't forget to properly eject the SD Card !

If "tar xvf" doesn't work for you you can install "bsdtar" and use "bsdtar -xpf" instead

Then you can put the SD card in the console.

If it's a img / bin file you just downloaded

You can simply write it on your SD card using :
  • If you're on Windows, Ether or Win32DiskImager
  • If you're on Linux / Mac OS : "sudo dd if=yourimage.img of=/dev/sdX && sync" where /dev/sdX is the device of your SD card (unmounted)
You will probably want to open a partition manager to resize the ext4 partition once it's flashed, so that it fits your SD card.

Then you can put the SD card in the console.

Booting linux

Run the exploit :

Code:
$ cd shofel2/exploit
$ sudo ./shofel2.py cbfs.bin ../../coreboot/build/coreboot.rom

Your terminal should now be waiting for the Switch to enter RCM mode.

To do so : (I don't have pictures but that's the same method as fusée gelée, just look at some video tutorials)
  • plug the Switch on your PC using the USB A-to-C cable - use a blue SuperSpeed port if you have one
  • shut it down
  • remove the right joy-con
  • using a method of your choice, short the 10th pin of the right joy-con (the last pin on the right, away from the screen, closer to the back) with the ground : that can be pin 1, 2 or 7, that can also be a screw on the joy-con rack or the console's fan - I personnaly stick a RPi jumper wire in the fan and touch the 10th pin on the other side, works everytime (like this)
  • keep the pins shorted and power the Switch while pressing the volume UP button
If it worked, the console will show a black screen and you'll see the exploit running on your terminal. If you see the Nintendo logo, it has failed. You can power off the console and try again.

Then, run those last commands :

Code:
$ cd shofel2/usb_loader
$ ../../u-boot/tools/mkimage -A arm64 -T script -C none -n "boot.scr" -d switch.scr switch.scr.img
$ sudo ../../imx_usb_loader/imx_usb -c .

Linux should then boot on your console - first the boot logs with the penguins, and then an ArchLinux login prompt. Voilà !
Again, if you have the boot logs and then a black screen, it means you did the SD card part wrong.

Additional notes

Hardware graphics acceleration


The most recents image already contain this fix.

To add mesa drivers install this package using pacman :
https://0w0.st/mesa-full-tegra-r101876.bf5e0276b6-1-aarch64.pkg.tar.xz

You will need a working internet connection to do so.

Then, use this script to choose your power profile : https://0w0.st/power.sh

Full speed RAM


According to the blog post ("Linux on Switch boot chain" section), you need to extract a file from a Pixel C factory image in order to have the RAM working at full speed. I didn't do it so I won't cover it here.

Fixing calibration issues of the touch screen (thanks to @Wizardy)

To fix calibration issues of the touch screen, edit the file /usr/share/X11/xorg.conf.d/10-evdev.confg (of the rootfs)

And change the InputClass section to :

Code:
Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
        Option "InvertX" "no"
        Option "InvertY" "yes"
        Option "SwapAxes" "yes"
        Option "Calibration" "0 1279 0 719"
EndSection

Wi-Fi

To setup Wi-Fi, mount the rootfs partition on your host PC and edit the configuration for your network in the file "/etc/NetworkManager/system-connections" (if it doesn't exist, take Gigaspot).

To have a working Wi-Fi you must reboot your Switch and run the exploit again each time you power it off

Moving the rootfs to another partition

If you want to move the rootfs to another partition on your SD card, edit the "shofel2/usb_loader/switch.scr" file and replace "/dev/mmcblk0p2" by the partition you want to use.
 
Last edited by natinusala,

Gren22

Well-Known Member
Newcomer
Joined
Apr 24, 2018
Messages
63
Trophies
0
Age
26
XP
210
Country
United States
Ugh anyone know the fix for getting WiFi to work with gigaa's rootfs? Have to recompile the kernel myself since I need to use the SD patch for my 64 GB card
 

Type_O_Dev

Developer
Developer
Joined
Dec 12, 2017
Messages
683
Trophies
0
XP
1,469
Country
United States

Hydr8gon

Dragon Trainer
Developer
Joined
Dec 15, 2014
Messages
316
Trophies
1
Website
hydr8gon.github.io
XP
2,580
Country
Canada
Yeah I've seen that, but it doesn't seem to be the same issue since I'm not getting any register dumps. There's no indication an SD is even inserted. I might try it some other time, but I'm already halfway to switching my cards around so hopefully the 32GB one works!

Edit: well, I stand corrected! I ended up trying the kernel patch anyways, and it seems to have worked. Now I just have to put my rootfs back on the card...
 
Last edited by Hydr8gon,

Krazer89

New Member
Newbie
Joined
Jul 28, 2017
Messages
4
Trophies
0
Website
krazer.ml
XP
122
Country
New Zealand
Ugh anyone know the fix for getting WiFi to work with gigaa's rootfs? Have to recompile the kernel myself since I need to use the SD patch for my 64 GB card
I downloaded brcmfmac4356-pcie.txt using WGET, but I accidentally pulled the HTML not the actual file.
Double check that /lib/firmware/brcm/brcmfmac4356-pcie.txt is correct if you are trying to build the kernel yourself.

This kernel includes a "fix" for the "Timeout waiting on hardware interrupt" error and has working WIFI.
Simply remove the .zip extension from the end of the file and place it in linux/arch/arm64/boot/ (NOT ON YOUR SDCARD)
Example: /home/USERNAME/switch-linux/linux/arch/arm64/boot/

(If you are using SoulCiphers precompiled binaries just drop it in /home/USERNAME/shofel2_linux/kernel/)

Remember, you have to reboot at least once to get WIFI working.
 

Attachments

  • Image.gz.zip
    8.2 MB · Views: 619
Last edited by Krazer89,

Kobigov

Well-Known Member
Member
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
That's not the issue I'm having though. This is.

EDIT: I decided I'll try the fix anyways, there's no /linux/ folder though?

yOnISwy.png
He meant the linux folder in your home folder. Oh, I remember having something like that when my rootfs was broken, did you use sync after taring the rootfs?

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

https://drive.google.com/open?id=1lX0s9SKOwu1jaPV5JJ2YTt9rj3bMZ7eB

^
Link to an image of the ext4 rootfs with chromium installed already, tried getting dolphin to compile but failed.
 

Lucar

Well-Known Member
Member
Joined
Sep 12, 2015
Messages
528
Trophies
0
XP
619
Country
Canada
He meant the linux folder in your home folder. Oh, I remember having something like that when my rootfs was broken, did you use sync after taring the rootfs?

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

https://drive.google.com/open?id=1lX0s9SKOwu1jaPV5JJ2YTt9rj3bMZ7eB

^
Link to an image of the ext4 rootfs with chromium installed already, tried getting dolphin to compile but failed.

I didn't use sync afterwards, no, however I made sure to properly eject which should have flushed everything anyways, so...?
 

Kobigov

Well-Known Member
Member
Joined
Jan 10, 2018
Messages
129
Trophies
0
Age
44
XP
300
Country
United States
I didn't use sync afterwards, no, however I made sure to properly eject which should have flushed everything anyways, so...?
Syncing fixed stuff for me, it's also added to the OP to do now.

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

I downloaded brcmfmac4356-pcie.txt using WGET, but I accidentally pulled the HTML not the actual file.
Double check that /lib/firmware/brcm/brcmfmac4356-pcie.txt is correct if you are trying to build the kernel yourself.

This kernel includes a fix for the "Timeout waiting on hardware interrupt" error and has working WIFI.
Simply remove the .zip extension from the end of the file and place it in "linux/arch/arm64/boot/".
(If you are using SoulCiphers premade repo just drop it in the kernel folder)

Remember, you have to reboot at least once to get WIFI working.
Nice! It works on my 32GB microSD now thanks!
 
  • Like
Reactions: Krazer89

bluke

Well-Known Member
Member
Joined
Feb 2, 2010
Messages
137
Trophies
1
XP
342
Country
"config file <conf//imx_usb.conf>
vid=0x0955 pid=0x701a file_name=switch.conf
no matching USB device found"

I got this error whe use with https://0w0.st/rootfs2.tar.bz2 and latest SoulCipher what i need to do ?

PS: Just get back to SoulCipher Image.gz and done.
 
Last edited by bluke,

Selim873

Nunnayobeesnes
Member
Joined
Jul 31, 2010
Messages
1,275
Trophies
0
Age
30
Location
Chillin' with Bob Ross
XP
1,112
Country
United States
I just want to throw this out there, if you're using LXDE, you can set up wifi by selecting to connect to a hidden network and inputting your SSID. When you choose a security measure, you have to click the box and use down on the arrow buttons on the on screen keyboard. It'll connect and save it so it'll automatically connect when you reboot after first boot. This only works for 2.4GHz connections though.
 
  • Like
Reactions: lordelan

Gren22

Well-Known Member
Newcomer
Joined
Apr 24, 2018
Messages
63
Trophies
0
Age
26
XP
210
Country
United States
I downloaded brcmfmac4356-pcie.txt using WGET, but I accidentally pulled the HTML not the actual file.
Double check that /lib/firmware/brcm/brcmfmac4356-pcie.txt is correct if you are trying to build the kernel yourself.

This kernel includes a fix for the "Timeout waiting on hardware interrupt" error and has working WIFI.
Simply remove the .zip extension from the end of the file and place it in linux/arch/arm64/boot/ (NOT ON YOUR SDCARD)
Example: /home/USERNAME/switch-linux/linux/arch/arm64/boot/

(If you are using SoulCiphers precompiled binaries just drop it in /home/USERNAME/shofel2_linux/kernel/)

Remember, you have to reboot at least once to get WIFI working.
Awesome! Thanks. Was a rough few days but glad the genius's working on this found and fixed the SD card issues :P
 
Last edited by Gren22,
  • Like
Reactions: Kobigov

Keksus

Active Member
Newcomer
Joined
Sep 24, 2013
Messages
35
Trophies
0
Age
35
XP
230
Country
Gambia, The
Hello..
I think my switch is broken now =(

i cant it power on ...
only with usb c cable in it works .... no why???
 

Keksus

Active Member
Newcomer
Joined
Sep 24, 2013
Messages
35
Trophies
0
Age
35
XP
230
Country
Gambia, The
Hold your power button down for like 20 seconds to make sure its turned off and out of RCM mode.


Dont work. Only with Power cable on the Switch.
battery is 50%...
But now it works lol...

i have no idea why.
I have restarted several times and then charged the battery...
Now it works normally again
 

masterclimby

Member
Newcomer
Joined
Nov 21, 2013
Messages
19
Trophies
0
XP
260
Country
United States
I've noticed that my glxspheres results are significantly slower than what f0f had in their video (this is with mesa drivers applied).
 

Attachments

  • screenshot.png
    screenshot.png
    276.1 KB · Views: 291
  • Like
Reactions: lordelan

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    NinStar @ NinStar: It will actually make it worse