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,

wiiarctus

Well-Known Member
Member
Joined
Aug 29, 2016
Messages
125
Trophies
0
Age
23
XP
161
Country
Germany
Hey, I followed all steps and nearly everything worked, I'm only stuck on the boot with:
"Waiting for root device /dev/mmcblk0p2...
random: crng init done".
Does anyone know how to fix this?^^
 

lordelan

Well-Known Member
Member
Joined
Jan 4, 2015
Messages
5,784
Trophies
1
Age
44
XP
6,508
Country
Germany
Hey, I followed all steps and nearly everything worked, I'm only stuck on the boot with:
"Waiting for root device /dev/mmcblk0p2...
random: crng init done".
Does anyone know how to fix this?^^
Did you make ext4 the second partition (after a FAT32 partition)?
 

Pinda

Well-Known Member
Newcomer
Joined
Jan 16, 2015
Messages
48
Trophies
0
Age
33
Location
Amstelveen
Website
jasonmeulenhoff.nl
XP
96
Country
Netherlands
Hey, I followed all steps and nearly everything worked, I'm only stuck on the boot with:
"Waiting for root device /dev/mmcblk0p2...
random: crng init done".
Does anyone know how to fix this?^^

Need another SD card, had that fault too just bought a Sandisk works fine now (had a lexar before that)
 

ExploitTnT

Devy | YT: DevRin | dev_settings
Member
Joined
Jul 30, 2017
Messages
150
Trophies
0
XP
270
Country
Austria
Wow okay i got far this time.
asset.JPG
 
  • Like
Reactions: lordelan and Pinda

J-Lit

Member
Newcomer
Joined
May 1, 2018
Messages
9
Trophies
0
Age
30
XP
63
Country
United States
I feel like a broken record at this point, but same. Tried running the precompiled after my own didn't work, and there's no difference. Running the final command with sudo, everything in Terminal appears as if it's working, but on the console, nada. I'm usually not this bad at troubleshooting, but this has me stumped, since the Terminal is acting like everything's fine. I considered the fact that it might just be the VM, but there are people claiming their VM setup works just fine in this very thread. Want to install Linux on my PC proper and try there, but my Ryzen processor is too new, most distros/kernels/drivers are still unstable. Looks like I'll have to try the old shitty laptop just to see if I can get something to run. sigh

DId you ever get your switch to boot Linux? I'm having the same problem and I've been beating my head over it for the last few days. My switch loaded linux ONCE and then immediately the screen went black, I have no idea why it decided to load that time or what caused it to crash, but I haven't been able to replicate it.
 

CptPotato

Active Member
Newcomer
Joined
Jan 1, 2016
Messages
34
Trophies
0
Age
25
Location
Hell
XP
374
Country
Serbia, Republic of
DId you ever get your switch to boot Linux? I'm having the same problem and I've been beating my head over it for the last few days. My switch loaded linux ONCE and then immediately the screen went black, I have no idea why it decided to load that time or what caused it to crash, but I haven't been able to replicate it.

Yup. Read somewhere in this very thread that someone fixed the issue by using a better USB-C cable, so I just bought a new one and it seems to work okay now. Was using a generic LG one, now Ugreen.
Mind you, it still won't boot sometimes, but very rarely, only had it happen a couple of times since. Guess not all cables are created equal.
 

J-Lit

Member
Newcomer
Joined
May 1, 2018
Messages
9
Trophies
0
Age
30
XP
63
Country
United States
So I think I figured out why my switch wont boot Linux. I have a USB3.0 port and USB a3.0 to c cable, but for whatever reason, my computer detects it as a USB 2.0 when plugged in.

If anyone knows how to fix this I'd appreciate the help, otherwise I guess I'm at peace knowing my laptop is trash
 

Attachments

  • Screenshot from 2018-05-02 11-32-11.png
    Screenshot from 2018-05-02 11-32-11.png
    7.7 KB · Views: 264
  • IMG_1029.jpg
    IMG_1029.jpg
    623.1 KB · Views: 224

Tommy084

Well-Known Member
Member
Joined
Feb 24, 2013
Messages
126
Trophies
1
Age
25
XP
1,490
Country
Norway

Tommy084

Well-Known Member
Member
Joined
Feb 24, 2013
Messages
126
Trophies
1
Age
25
XP
1,490
Country
Norway
Have you placed "ehci_patch.py" script in same folder as the "linux-ehci-enable-large-ctl-xfers.patch"?
I dont use wm, pc with ubuntu 18.04
Comman i use is: sudo python ehci_patch.py -t

Code:
sudo python patch.py -t
0xffffffffb0b4b610L
make -C /lib/modules/4.15.0-20-generic/build M=/home/ubuntu/OPT/Switch/shofel2_linux modules
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-20-generic'
  CC [M]  /home/ubuntu/OPT/Switch/shofel2_linux/patch.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: modpost: missing MODULE_LICENSE() in /home/ubuntu/OPT/Switch/shofel2_linux/patch.o
see include/linux/module.h for more information
  CC      /home/ubuntu/OPT/Switch/shofel2_linux/patch.mod.o
  LD [M]  /home/ubuntu/OPT/Switch/shofel2_linux/patch.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-20-generic'
About to insert patch module, 'Operation not permitted' means it probably worked, check dmesg output.
insmod: ERROR: could not insert module patch.ko: Operation not permitted
 
Last edited by Tommy084,

J-Lit

Member
Newcomer
Joined
May 1, 2018
Messages
9
Trophies
0
Age
30
XP
63
Country
United States
Have you placed "ehci_patch.py" script in same folder as the "linux-ehci-enable-large-ctl-xfers.patch"?
I dont use wm, pc with ubuntu 18.04
Comman i use is: sudo python ehci_patch.py -t

Code:
sudo python patch.py -t
0xffffffffb0b4b610L
make -C /lib/modules/4.15.0-20-generic/build M=/home/ubuntu/OPT/Switch/shofel2_linux modules
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-20-generic'
  CC [M]  /home/ubuntu/OPT/Switch/shofel2_linux/patch.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: modpost: missing MODULE_LICENSE() in /home/ubuntu/OPT/Switch/shofel2_linux/patch.o
see include/linux/module.h for more information
  CC      /home/ubuntu/OPT/Switch/shofel2_linux/patch.mod.o
  LD [M]  /home/ubuntu/OPT/Switch/shofel2_linux/patch.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-20-generic'
About to insert patch module, 'Operation not permitted' means it probably worked, check dmesg output.
insmod: ERROR: could not insert module patch.ko: Operation not permitted

Yeah that's the output I get from running the script too. The script is in my shofel2_linux folder and it makes a bunch of other files. When I run sudo ./boot_linux.sh my switch never boots linux even though the terminal says success.

Actually my last line is:
insmod: ERROR: could not insert module patch.ko: Required key not available

I'm not sure if it matters though
 
Last edited by J-Lit,

MrWhosHacking

Well-Known Member
Member
Joined
May 3, 2018
Messages
293
Trophies
0
Age
34
XP
505
Country
United States
I using NXLoader on Nvidia shield usb works fine but it stays on the exploited logo then idk . What do I have to do I download the
shofel2_linux file


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

I need help please. I’m on windows 10 I went to shofel2 Linux and download the Linux file used the Etcher to sdcard zip file what am I doing wrong
 
Last edited by MrWhosHacking,

natinusala

Win32 error 31 is not an error
OP
Member
Joined
Dec 1, 2012
Messages
1,032
Trophies
0
Age
44
XP
2,914
Country
France
you try to write it to the 2nd partition:
Code:
sudo dd if=arch_lxde.bin of=/dev/sdb2

...you will end up with a partition with an unrecognized type, and it will fail to boot. I had to write it straight to sdb instead (actually, on my system it's mmcblk0, but you get the idea.)

Whoops, my bad - fixed the first post
 
  • Like
Reactions: RHOPKINS13

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    S @ salazarcosplay: How are you @AncientBoi :tpi: :tpi: :tpi: :tpi: :tpi: