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,
  • Like
Reactions: Deleted member 518148, globalc, MissingNo._ and 49 others
Click to expand...
kombos

kombos

Well-Known Member
Member
Level 2
Joined
Apr 24, 2018
Messages
140
Trophies
0
Location
Universe
XP
167
Country
Ukraine
Mittytoto said:
Yes, agreed but I am not sure about the life circle of the PRs on f0f's, could take weeks to get this merged, maybe? While I just need to apply the dirty patch for the Samsung cards to work. At least 3 people on this thread are having troubles with Samsung's. Obviously I would need to have the latest wifi fix source first OR @kombos is happy to patch it on his binary.
Click to expand...

@Mittytoto I'm quite busy today I’m not able to follow whole thread. What do you mean by Samsung ? What do you have to patch ? What card are you referring to ? Kernel binaries are meant to be transferred to Switch over usb after exploit and they run on Switch.

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

Mittytoto said:
Thanks, that the prebuilt binary everyone is using. I guess I haven't made myself clear. I would like to know the source of the wifi fix too, if possible. Because I just want to get over the Samsung card fix too.
Anyway, no big deal, so far only 3 people having the Samsung's. So no hard feeling.
Cheers

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


Oh right? Thanks for confirming. I was trying the KDE rootfs and wifi didnt work. Too early to make assumptions - sorry my bad. Will try another rootfs. Cheers
Click to expand...

@Mittytoto If kernel you have compiled doesn’t have proper firmware packages for Broadcom chipset, no matter what roots package you will use it just simply not work, because it’s kernel which hold the drivers not fs in that case. At least according to my knowledge this is the case.
 
Mittytoto

Mittytoto

Member
Newcomer
Level 2
Joined
Apr 27, 2018
Messages
21
Trophies
0
Location
Auckland
XP
140
Country
New Zealand
kombos said:
@Mittytoto I'm quite busy today I’m not able to follow whole thread. What do you mean by Samsung ? What do you have to patch ? What card are you referring to ? Kernel binaries are meant to be transferred to Switch over usb after exploit and they run on Switch.
Click to expand...

@kombos, please refer to this.

Type_O_Dev said:
For anyone having issues booting SDCHI sd card https://twitter.com/perillamint/status/990283321065095168
Click to expand...

Basically, according to the author, Switch bus bug so it cannot read high speed cards so he had to reduce the speed cap on these.
I have a 128GB Samsung and a couple other users in this thread also encounter the same issue - Linux boot time takes ages and hang at random: crng.
So I tried the above patch and my card works again but no wifi so I thought the original f0f's doesnt include the wifi drivers.
Cheers.
 
Last edited by Mittytoto,
  • Like
Reactions: Type_O_Dev
Rainbowfied Pokemaster

Rainbowfied Pokemaster

Well-Known Member
Newcomer
Level 2
Joined
Jun 28, 2016
Messages
47
Trophies
0
XP
191
Country
United States
So I have libusb-1.0-0-dev installed but I get this error when trying to make imx_usb_loader
Code: 
make
cc -c imx_usb.c -o imx_usb.o -pipe -ggdb `pkg-config --cflags libusb-1.0` -Wall -Wstrict-prototypes -Wno-trigraphs -DSYSCONFDIR='"/usr/etc"'
/bin/sh: 1: pkg-config: not found
cc -c imx_sdp.c -o imx_sdp.o -pipe -ggdb -Wall -Wstrict-prototypes -Wno-trigraphs -DSYSCONFDIR='"/usr/etc"'
cc -o imx_usb imx_usb.o imx_sdp.o  `pkg-config --libs libusb-1.0`
/bin/sh: 1: pkg-config: not found
imx_usb.o: In function `print_devs':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:61: undefined reference to `libusb_get_device_descriptor'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:67: undefined reference to `libusb_get_config_descriptor'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_device_address'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_bus_number'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:87: undefined reference to `libusb_free_config_descriptor'
imx_usb.o: In function `find_imx_dev':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:193: undefined reference to `libusb_get_bus_number'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:194: undefined reference to `libusb_get_device_address'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:196: undefined reference to `libusb_get_device_descriptor'
imx_usb.o: In function `transfer_hid':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:262: undefined reference to `libusb_control_transfer'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:274: undefined reference to `libusb_interrupt_transfer'
imx_usb.o: In function `transfer_bulk':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:321: undefined reference to `libusb_bulk_transfer'
imx_usb.o: In function `do_work':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:419: undefined reference to `libusb_get_configuration'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:422: undefined reference to `libusb_kernel_driver_active'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:423: undefined reference to `libusb_detach_kernel_driver'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:425: undefined reference to `libusb_claim_interface'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:485: undefined reference to `libusb_release_interface'
imx_usb.o: In function `do_autodetect_dev':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:504: undefined reference to `libusb_init'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:508: undefined reference to `libusb_get_device_list'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:517: undefined reference to `libusb_free_device_list'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:560: undefined reference to `libusb_open_device_with_vid_pid'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:583: undefined reference to `libusb_close'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:594: undefined reference to `libusb_exit'
collect2: error: ld returned 1 exit status
Makefile:29: recipe for target 'imx_usb' failed
make: *** [imx_usb] Error 1
 
LarBob

LarBob

Well-Known Member
Member
Level 4
Joined
Dec 29, 2013
Messages
370
Trophies
0
Age
23
XP
563
Country
United States
Gigaa said:
I have heard good things about the oneplus cables, i also use it my self. But don't buy those unless you need fast charging on a oneplus device as they are kinda expensive.
Other that that i'm kinda blank really. I guess official phone chargers should be fine as they deal with data-transfer as well and not just charging.
Click to expand...
I got a cable like this: https://www.amazon.com/Native-Union-Cable-USB-USB-C/dp/B071SLK16V#customerReviews just a different color and am still having very inconsistent success rates with booting. Could it have to do with the USB 3.0 controller in my laptop?
 
D

Deleted User

Guest
here some news changing the usb 2.0 to 3.0 inside vmware was solving some issues but now i got some new ones.

Die Verbindung für das USB-Gerät „NVidia USB download gadget“ konnte nicht erfolgreich hergestellt werden.

Translation the Connection for the Device Nvidia USB Download Gadget could not be established any clues ?
 
NCDyson

NCDyson

Hello Boys...
Member
Level 3
Joined
Nov 9, 2009
Messages
278
Trophies
1
XP
319
Country
United States
AfkKun said:
I also have problems out of 5 reboots maybe 1, max. 2 times i actually can use wifi
Click to expand...

better than I'm getting. I've got it to work once in 3 days, and I've been trying to get it to work for the past hour. I'm using a belkin USB cable, so I don't think it's that.

will try again with a different cable when my switch cools down. got distracted and left it trying to reboot and it got really hot.
 
T

TerraPhantm

Well-Known Member
Member
Level 5
Joined
Jul 27, 2007
Messages
498
Trophies
0
XP
680
Country
United States
Natehaxx said:
here some news changing the usb 2.0 to 3.0 inside vmware was solving some issues but now i got some new ones.

Die Verbindung für das USB-Gerät „NVidia USB download gadget“ konnte nicht erfolgreich hergestellt werden.

Translation the Connection for the Device Nvidia USB Download Gadget could not be established any clues ?
Click to expand...
Seems to be a problem with however USB passthrough is handled on osx. I made a VM on my windows computer with the same settings, and it works fine there.
 
Dread_Pirate_PJ

Dread_Pirate_PJ

Well-Known Member
Newcomer
Level 2
Joined
Feb 24, 2018
Messages
64
Trophies
0
Age
53
XP
178
Country
United States
dankzegriefer said:
Why's there sound in the video if there's no sound in actuality? Unless I'm missing something.
Click to expand...

He's not playing Persona 5 on the Switch. He's playing it on his PC and streaming the video to the Switch using chromium and jsmpeg-vnc. The Joycons are paired to his PC. The sound is coming from his PC.

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

Natehaxx said:
here some news changing the usb 2.0 to 3.0 inside vmware was solving some issues but now i got some new ones.

Die Verbindung für das USB-Gerät „NVidia USB download gadget“ konnte nicht erfolgreich hergestellt werden.

Translation the Connection for the Device Nvidia USB Download Gadget could not be established any clues ?
Click to expand...

@Natehaxx I was able to get everything built on my Mac using this other how-to:

https://gbatemp.net/threads/docker-linux-toolchain-kit.502015/

The github repo is at https://github.com/Nold360/switch_linux_kit

It uses Docker for building, but after everything is built, you use Mac OS X to send the payloads. So your USB 2.0 Mac should work fine.
 
Last edited by Dread_Pirate_PJ,
S

SatsumeTheOne

New Member
Newbie
Level 1
Joined
Apr 30, 2018
Messages
2
Trophies
0
Age
40
XP
56
Country
Netherlands
Rainbowfied Pokemaster said:
So I have libusb-1.0-0-dev installed but I get this error when trying to make imx_usb_loader
Code: 
make
cc -c imx_usb.c -o imx_usb.o -pipe -ggdb `pkg-config --cflags libusb-1.0` -Wall -Wstrict-prototypes -Wno-trigraphs -DSYSCONFDIR='"/usr/etc"'
/bin/sh: 1: pkg-config: not found
cc -c imx_sdp.c -o imx_sdp.o -pipe -ggdb -Wall -Wstrict-prototypes -Wno-trigraphs -DSYSCONFDIR='"/usr/etc"'
cc -o imx_usb imx_usb.o imx_sdp.o  `pkg-config --libs libusb-1.0`
/bin/sh: 1: pkg-config: not found
imx_usb.o: In function `print_devs':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:61: undefined reference to `libusb_get_device_descriptor'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:67: undefined reference to `libusb_get_config_descriptor'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_device_address'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:71: undefined reference to `libusb_get_bus_number'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:87: undefined reference to `libusb_free_config_descriptor'
imx_usb.o: In function `find_imx_dev':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:193: undefined reference to `libusb_get_bus_number'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:194: undefined reference to `libusb_get_device_address'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:196: undefined reference to `libusb_get_device_descriptor'
imx_usb.o: In function `transfer_hid':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:262: undefined reference to `libusb_control_transfer'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:274: undefined reference to `libusb_interrupt_transfer'
imx_usb.o: In function `transfer_bulk':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:321: undefined reference to `libusb_bulk_transfer'
imx_usb.o: In function `do_work':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:419: undefined reference to `libusb_get_configuration'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:422: undefined reference to `libusb_kernel_driver_active'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:423: undefined reference to `libusb_detach_kernel_driver'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:425: undefined reference to `libusb_claim_interface'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:485: undefined reference to `libusb_release_interface'
imx_usb.o: In function `do_autodetect_dev':
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:504: undefined reference to `libusb_init'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:508: undefined reference to `libusb_get_device_list'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:517: undefined reference to `libusb_free_device_list'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:560: undefined reference to `libusb_open_device_with_vid_pid'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:583: undefined reference to `libusb_close'
/home/rainbowdev/Switch/imx_usb_loader/imx_usb.c:594: undefined reference to `libusb_exit'
collect2: error: ld returned 1 exit status
Makefile:29: recipe for target 'imx_usb' failed
make: *** [imx_usb] Error 1
Click to expand...

I made an account just to help you with this.
I ran into the same thing.

You have to install “pkg-config”.

It’s not on te requirements list, and missing in minimum Ubuntu installs.

—

Another package I was missing is zlib, eg. “
zlib1g-dev”
 
Last edited by SatsumeTheOne,
dovere

dovere

Well-Known Member
Newcomer
Level 3
Joined
Apr 26, 2018
Messages
55
Trophies
0
Age
29
XP
255
Country
Italy
Someone had any "luck" compiling steam (in-home streaming), parsec or moonlight?? jsmpegvnc is not enough to get high framerate and quality.

Everytime i try to compile or build i get the message that aarch64 is not supported, moonlight chrome extensions runs but chromium does not support NaCl
 
Last edited by dovere,
S

sigboe

Well-Known Member
Newcomer
Level 2
Joined
Feb 3, 2016
Messages
84
Trophies
0
Age
33
XP
202
Country
Norway
@Gigaa How did you launch KDE? How did you autologin? I am asking because I prefer to launch gnome via systemd, but I did not see a systemd entry for your autolaunching the GUI, and you didnt (or so it seams) use autologin setting in KDE.

Also anything else that runs as the user alarm that would be lost if I deleted that user?

Edit: I found the .xinitrc file in alarms userdir, currently looking for the way you autologged in, gonna edit the post if I find it.

Next time you upload a rootfs, maybe clean the pacman cache?
 
Last edited by sigboe,
Gigaa

Gigaa

Well-Known Member
Member
Level 1
Joined
Apr 25, 2018
Messages
108
Trophies
0
Age
26
Location
Norway
Website
giga.is
XP
130
Country
Norway
sigboe said:
@Gigaa How did you launch KDE? How did you autologin? I am asking because I prefer to launch gnome via systemd, but I did not see a systemd entry for your autolaunching the GUI, and you didnt (or so it seams) use autologin setting in KDE.

Also anything else that runs as the user alarm that would be lost if I deleted that user?
Click to expand...
If you want to launch gnome just swap out exec startkde in .xinitrc with exec gnome-session as i just use slim to autologin.
If you are gonna swap the user then you also have to change the user that gets autologed on in /etc/slim.conf .
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Emulation Homebrew  duckstation for Switch

Can you trade in a banned switch for an unbanned one?

Why is Atmosphere so dominant?

Crosscode Hacking thread

Hacking  Weird findings from that DQ trilogy switch port

Hacking Misc Tutorial  Eiyuden Chronicle Hundred Heroes save editing

Migswitch backups without certificate files

switch change sd card, but android start fail

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Goku likes to flip the bean to get others healthy