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,

saneatsu

Well-Known Member
Newcomer
Joined
Apr 28, 2018
Messages
54
Trophies
0
Age
32
XP
209
Country
United States
Isn't that why sync exists ?
I believe sync just tells it to flush the buffer to make sure you can eject it quickly.

And yes while bs does impact however on OS X disk access is usually cached/compressed. Using rdisk3 (for example) will bypass any caching and means you don’t need to sync either. Personally this moves a 32gb image from hour+ (at 3-4MB/s) to 30 min (20MB/s).
 
  • Like
Reactions: uyjulian

Rainbowfied Pokemaster

Well-Known Member
Newcomer
Joined
Jun 28, 2016
Messages
47
Trophies
0
XP
191
Country
United States
That fixed the "command not found" error but now I get this:

Code:
arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
arch/arm64/Makefile:48: Detected assembler with broken .inst; disassembly will be unreliable
  CHK     include/config/kernel.release
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
Makefile:1129: recipe for target 'prepare-compiler-check' failed
make: *** [prepare-compiler-check] Error 1

Can anyone help me with this
 

cmsj

Well-Known Member
Newcomer
Joined
Apr 25, 2018
Messages
61
Trophies
0
Age
46
XP
223
Country
United Kingdom
That's very nice ! I see that you're still using imx_usb_loader though, is it for the u-boot script ?

For now, yes. That will go away when I change u-boot's default command to boot from SD and fall back to USB injection. I'll keep shipping imx_usb_loader after that point, it just won't be used by default.
 

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
Last edited by natinusala,
  • Like
Reactions: lordelan

wiiarctus

Well-Known Member
Member
Joined
Aug 29, 2016
Messages
125
Trophies
0
Age
23
XP
161
Country
Germany
Last edited by wiiarctus,

ShadowXin225

Active Member
Newcomer
Joined
Apr 30, 2018
Messages
37
Trophies
0
Age
26
XP
155
Country
Australia
is there a possibility for sound anytime soon or no? built the code up but what driver incomparability is causing the audio output to stuff up even using a bluetooth speaker?

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

i got a bluetooth keyboard to work with it ps4 controller connects but may need input mapper ported other or ds4 hardware with the kde image is a slow lags with gba emulation using retro arch am i doing something incorrect ??

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

i have not attempted using dolphin to test if theres a difference due to the reason of gba emulation being so buggy at this stage

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

acutually someone place me on the right track for audio and ill try to get it working spent 6 and a half hours from starting learning new things so mos awell give this a shot ill attempt to compile but need a general push in the right direction vice versa when i can that is
 

CuriousTommy

Well-Known Member
Member
Joined
Jul 22, 2014
Messages
524
Trophies
0
Age
27
XP
647
Country
United States
not on better Switch hardware support, I drew a lot of blanks in my investigations there.

is there a possibility for sound anytime soon or no? built the code up but what driver incomparability is causing the audio output to stuff up even using a bluetooth speaker?

I was also curious about the driver issues. For audio, the Switch uses a Realtek ALC5639, but (from what I understand) the datasheet (which describes how to communicate with the hardware) is not publicly available. So I guess someone would have to reverse engineer the Switch's driver to make a Linux driver...
 

ShadowXin225

Active Member
Newcomer
Joined
Apr 30, 2018
Messages
37
Trophies
0
Age
26
XP
155
Country
Australia
it seems this audio device was made way back 2014 i found a post not sure if this would help us but
amixer cset name="Stereo ADC MIXL ADC2 Switch" 0
amixer cset name="Stereo ADC MIXR ADC2 Switch" 0
amixer cset name="Int Mic Switch" 0
amixer cset name="ADC Capture Switch" 1
amixer cset name="RECMIXL BST1 Switch" 0
amixer cset name="RECMIXR BST1 Switch" 0
amixer cset name="RECMIXL BST2 Switch" 1
amixer cset name="RECMIXR BST2 Switch" 1
amixer cset name="Stereo ADC L1 Mux" "ADC"
amixer cset name="Stereo ADC R1 Mux" "ADC"
amixer cset name="Stereo ADC MIXL ADC1 Switch" 1
amixer cset name="Stereo ADC MIXR ADC1 Switch" 1
amixer cset name="Stereo ADC MIXL ADC2 Switch" 0
amixer cset name="Stereo ADC MIXR ADC2 Switch" 0
amixer cset name="IN1 Mode Control" "Single ended"
amixer cset name="IN2 Mode Control" "Single ended"
amixer cset name="Mic Jack Switch" 1

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

i cant post hyperlinks being a new member but ill pull all the page in a box


has a Realtek ALC5639 HD Audio codec with the following connectors:

  • 3.5mm audio stereo output (eg: for speakers)
  • 3.5mm audio input (eg: for microphone)
  • HDMI digital audio (eg: for a TV).
Fixing the sound recording input
, you might need to open a terminal and run the following to correctly configure sound recording on Jetson TK1:

amixer cset name="Stereo ADC MIXL ADC2 Switch" 0
amixer cset name="Stereo ADC MIXR ADC2 Switch" 0
amixer cset name="Int Mic Switch" 0
amixer cset name="ADC Capture Switch" 1
amixer cset name="RECMIXL BST1 Switch" 0
amixer cset name="RECMIXR BST1 Switch" 0
amixer cset name="RECMIXL BST2 Switch" 1
amixer cset name="RECMIXR BST2 Switch" 1
amixer cset name="Stereo ADC L1 Mux" "ADC"
amixer cset name="Stereo ADC R1 Mux" "ADC"
amixer cset name="Stereo ADC MIXL ADC1 Switch" 1
amixer cset name="Stereo ADC MIXR ADC1 Switch" 1
amixer cset name="Stereo ADC MIXL ADC2 Switch" 0
amixer cset name="Stereo ADC MIXR ADC2 Switch" 0
amixer cset name="IN1 Mode Control" "Single ended"
amixer cset name="IN2 Mode Control" "Single ended"
amixer cset name="Mic Jack Switch" 1
 

CuriousTommy

Well-Known Member
Member
Joined
Jul 22, 2014
Messages
524
Trophies
0
Age
27
XP
647
Country
United States
Last edited by CuriousTommy,

ShadowXin225

Active Member
Newcomer
Joined
Apr 30, 2018
Messages
37
Trophies
0
Age
26
XP
155
Country
Australia
that is weird that it does not work since it is implanted into the kernal as the others said we might have to start from scratch
 

lordelan

Well-Known Member
Member
Joined
Jan 4, 2015
Messages
5,784
Trophies
1
Age
44
XP
6,509
Country
Germany
Just out of curiousity as this popped up and I was thinking about this as well since day one, is it possible in Switch Linux to connect and mount a USB device (drive or flash stick)?
And if yes, even in docked mode? Because people in the thread are saying the dock can't read from USB drives.
 

Raugo

Well-Known Member
Member
Joined
Nov 22, 2014
Messages
630
Trophies
0
XP
2,450
Country
Spain
Using grep, I was can see that the driver for 5639 lives in the rt5640.c/.h files, but where I look at fail0verflow's kernel source, it also at the same functions. so why doesn't it work...

The Jetson TX1 use 'the nvidia,tegra-audio-t210ref-mobile-rt565x' driver, this driver is in the tegra-alt folder. What command you use to check the sound card? With dmesg I don't see nothing.
 

EpicLPer

Your friendly Austrian IT Guy
Member
Joined
Mar 13, 2015
Messages
1,060
Trophies
0
Age
28
Location
Austria
Website
epiclper.com
XP
1,141
Country
Austria
A lot of people complain that they have the battery bug simply after not even using the Switch Linux for 5 minutes, I think it stores a wrong battery calibration somewhere on the Switch itself... Is it possible that a driver goes apeshit somehow and does that?
 

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
Is it normal that with the "boot_linux.bat" it takes so long for me (over a minute) to load the kernel image binary file? (It's really annoying to wait that long to boot Linux, even twice for Wi-Fi, is there a way to make that faster? :whip:)

if you're using my switch_linux repo, then it loads the kernel from the SD card. The only files uploaded are cbfs.bin and coreboot.rom which are small. I suggest you try another USB port or cable.

Just out of curiousity as this popped up and I was thinking about this as well since day one, is it possible in Switch Linux to connect and mount a USB device (drive or flash stick)?
And if yes, even in docked mode? Because people in the thread are saying the dock can't read from USB drives.

It would be possible once the kernel is fixed. We will be able to boot Linux from an USB stick too, albeit not very practical.
 

lordelan

Well-Known Member
Member
Joined
Jan 4, 2015
Messages
5,784
Trophies
1
Age
44
XP
6,509
Country
Germany
It would be possible once the kernel is fixed.

So the information that USB mass storage devices can't be plugged into the dock and be used by the Switch is wrong?
I'm not talking about using an USB drive directly in the USB C port of the Switch (handheld mode).

albeit not very practical.
I second that. :)
Except for the use case where I buy an extra docking station which goes to my desk with a monitor, a mouse and a keyboard and in case I'd only use Switch Linux in that environment. Then it might make sense to have Linux on an USB drive plugged into that dock to boot from.
 
  • Like
Reactions: CuriousTommy

CuriousTommy

Well-Known Member
Member
Joined
Jul 22, 2014
Messages
524
Trophies
0
Age
27
XP
647
Country
United States
The Jetson TX1 use 'the nvidia,tegra-audio-t210ref-mobile-rt565x' driver, this driver is in the tegra-alt folder. What command you use to check the sound card? With dmesg I don't see nothing.

I didn't actually run the kernel to check for the drivers, I just did a simple recursive grep search for 5639 when I cd into the 4.4 kernel directory.

Code:
$ grep -r 5639
sound/soc/codecs/rt5640.h:#define RT5640_ID_5639                (0x0 << 1)
sound/soc/codecs/rt5640.c: * rt5640.c  --  RT5640/RT5639 ALSA SoC audio codec driver
sound/soc/codecs/rt5640.c:static const struct snd_kcontrol_new rt5639_sto_dac_l_mix[] = {
sound/soc/codecs/rt5640.c:static const struct snd_kcontrol_new rt5639_sto_dac_r_mix[] = {
sound/soc/codecs/rt5640.c:static const struct snd_kcontrol_new rt5639_out_l_mix[] = {
sound/soc/codecs/rt5640.c:static const struct snd_kcontrol_new rt5639_out_r_mix[] = {
sound/soc/codecs/rt5640.c:static const struct snd_kcontrol_new rt5639_hpo_mix[] = {
sound/soc/codecs/rt5640.c:static const struct snd_soc_dapm_widget rt5639_specific_dapm_widgets[] = {
sound/soc/codecs/rt5640.c:        rt5639_sto_dac_l_mix, ARRAY_SIZE(rt5639_sto_dac_l_mix)),
sound/soc/codecs/rt5640.c:        rt5639_sto_dac_r_mix, ARRAY_SIZE(rt5639_sto_dac_r_mix)),
sound/soc/codecs/rt5640.c:        0, rt5639_out_l_mix, ARRAY_SIZE(rt5639_out_l_mix)),
sound/soc/codecs/rt5640.c:        0, rt5639_out_r_mix, ARRAY_SIZE(rt5639_out_r_mix)),
sound/soc/codecs/rt5640.c:        rt5639_hpo_mix, ARRAY_SIZE(rt5639_hpo_mix)),
sound/soc/codecs/rt5640.c:        rt5639_hpo_mix, ARRAY_SIZE(rt5639_hpo_mix)),
sound/soc/codecs/rt5640.c:static const struct snd_soc_dapm_route rt5639_specific_dapm_routes[] = {
sound/soc/codecs/rt5640.c:    case RT5640_ID_5639:
sound/soc/codecs/rt5640.c:            rt5639_specific_dapm_widgets,
sound/soc/codecs/rt5640.c:            ARRAY_SIZE(rt5639_specific_dapm_widgets));
sound/soc/codecs/rt5640.c:            rt5639_specific_dapm_routes,
sound/soc/codecs/rt5640.c:            ARRAY_SIZE(rt5639_specific_dapm_routes));
sound/soc/codecs/rt5640.c:            "The driver is for RT5639 RT5640 or RT5642 only\n");
sound/soc/codecs/rt5640.c:    { "rt5639", 0 },
sound/soc/codecs/rt5640.c:    { .compatible = "realtek,rt5639", },
sound/soc/codecs/rt5640.c:MODULE_DESCRIPTION("ASoC RT5640/RT5639 driver");
sound/soc/tegra-alt/Makefile:snd-soc-tegra-alt-t210ref-mobile-rt5639-objs := tegra_t210ref_mobile_alt.o
sound/soc/tegra-alt/Makefile:obj-$(CONFIG_SND_SOC_TEGRA_T210REF_MOBILE_ALT) += snd-soc-tegra-alt-t210ref-mobile-rt5639.o
sound/soc/tegra-alt/tegra_t210ref_mobile_alt.c:#define DRV_NAME "tegra-snd-t210ref-mobile-rt5639"
sound/soc/tegra-alt/tegra_t210ref_mobile_alt.c:    { .compatible = "nvidia,tegra-audio-t210ref-mobile-rt5639", },
Documentation/devicetree/bindings/sound/rt5640.txt:RT5640/RT5639 audio CODEC
Documentation/devicetree/bindings/sound/rt5640.txt:- compatible : One of "realtek,rt5640" or "realtek,rt5639".
Documentation/devicetree/bindings/sound/rt5640.txt:Pins on the device (for linking into audio routes) for RT5639/RT5640:
arch/x86/crypto/crc32c-pcl-intel-asm_64.S:    .long 0xa563905d, 0xdf99fc11
arch/arm/boot/dts/tegra124-jetson-tk1.dts:        rt5639: audio-codec@1c {
arch/arm/boot/dts/tegra124-jetson-tk1.dts:            compatible = "realtek,rt5639";
arch/arm/boot/dts/tegra124-jetson-tk1.dts:        nvidia,audio-codec = <&rt5639>;
drivers/isdn/mISDN/dsp_blowfish.c:    0x2464369b, 0xf009b91e, 0x5563911d, 0x59dfa6aa,
drivers/gpu/drm/amd/include/asic_reg/dce/dce_11_0_d.h:#define mmDIG7_AFMT_60958_1                                                     0x5639
drivers/gpu/drm/amd/include/asic_reg/dce/dce_11_2_d.h:#define mmDIG7_AFMT_60958_1                                                     0x5639
drivers/s390/char/sclp_async.c:     * e.g. 5639CC140 500 Red Hat RHEL5 Linux for zSeries (RHEL AS)
CREDITS:P: 1024/31455639 B7 99 BD B8 00 17 BD 46  C1 15 B8 AB 87 BC 25 FA
crypto/blowfish_common.c:    0x2464369b, 0xf009b91e, 0x5563911d, 0x59dfa6aa,
fs/nls/nls_cp936.c:    0x562D,0x5658,0x5639,0x5657,0x562C,0x564D,0x5662,0x5659,/* 0xD8-0xDF */
fs/nls/nls_cp950.c:    0x563B,0x5639,0x5632,0x563F,0x5634,0x5629,0x5653,0x564E,/* 0x48-0x4F */
firmware/radeon/R300_cp.bin.ihex::100380000000001800000074000000040000E56395
firmware/bnx2x/bnx2x-e2-6.2.9.0.fw.ihex::10B23000F7852838F8F11EB1FEDE9D045639ABF7CC
firmware/bnx2x/bnx2x-e2-6.2.9.0.fw.ihex::100A90001CB7D21EC8563915DF2B1FB995F170E966
firmware/bnx2x/bnx2x-e2-6.2.9.0.fw.ihex::10EDC000C9D34687BD9A563990F403B7D7399DEC1D
firmware/bnx2x/bnx2x-e2-6.2.9.0.fw.ihex::1072E000D86BF83C0AF61ABE3F0CF61A3EBB56396C
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::106F4000AF75639EA1B6B5C816F71BDEE92561CC07
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::10982000EC60F32610432CA7AEE74A5CC75563965D
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::100F5000E753F56393D7A2E0B20C40D7E95E268F42
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::109EB000014CFDB187B15C8DB5639A16FB217EF72D
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::10C7900058DE9459A542B9AECA287FD6665639E606
firmware/bnx2x/bnx2x-e1-6.2.9.0.fw.ihex::1028A000436563908E9887F6C963F86E690EBEEF34
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::102600005717FCD4E8C17661C7EF8D149F5639BDCA
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::1042500069B1EDD8EE8DB563991A7B169F7B62CF5D
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::1049300092042621FCB4FCC026775639ECD3ABF3A5
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::10DC5000AFD3545A77156393117ED5B767D9173868
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::10E1D0008D7D1DE3FD1CE1799365DF756390FF2B59
firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw.ihex::1016D000C95F11FEC8C9FBDBFCDF1F56393FBBA544
firmware/edgeport/boot.H16::01660080007EB0007AB33FF27EF800237E00017E100012075F6920000ABE240000780575900D800375901DD2B57E0000A5D8FD75A80075B100A9D587CA291209CC1209A0F5097AA1201201E6DA29A9D0C77E00057A01F175E110A9D7F4A9D7E4A5D8F175F10075E13F75A20375A30075C00075C100A9D1B1A9D0B1A9D5D3D2AFE47E0428008DEF1B0478FA04A934D30330E0EEBE240000780563903080E3B29580DFBEB00222C0D0A920DF0FA931DF030201B575080112083380FE7508FE12083375A8007EB33FF230E04B300146C2927E2480007E1109740819B20010740E19B200042E240100A5D9ED7E2480007E1109E4D5E0FD09B2000820E00A09B2000009B2001880EB2E240100A5D9E4439030D2AA8005D2AA439034D2AFA9D1870000000000A911DF03A9D2DF7508FF120833C0D1CA02FFCA06830032D0D032C28BC2AA32750808120833A9C0B1A9C5D3A9C6D3A9D2B132CAB8750802120833E5C0540368051201EE80F5DAB832AE
firmware/qlogic/1040.bin.ihex::103300007F291A696F7000007370010078005639C8
firmware/qlogic/1040.bin.ihex::1035C00007007900E02AE82AB42A302A5639BB39A4
firmware/qlogic/1040.bin.ihex::1036B000442B780056391B681D0078007B37206941
firmware/qlogic/1040.bin.ihex::1040D0004B4B7800563984A6002040005A301868AF
firmware/qlogic/1040.bin.ihex::104190007810874878104B4B7800563984A6002059
firmware/qlogic/1040.bin.ihex::1042D00056393F2A4A2A703178316E316E3156395B
firmware/qlogic/1040.bin.ihex::1042E000563978108C2420698CA1FFFD8CA1FFFE2B
firmware/qlogic/1040.bin.ihex::10430000226978005639E47984A1300040008A316E
firmware/qlogic/1040.bin.ihex::1043700056395639BD315639BB39BB39563956399C
firmware/qlogic/1040.bin.ihex::105460000300400023257800563984A7040040003B
 

wiiarctus

Well-Known Member
Member
Joined
Aug 29, 2016
Messages
125
Trophies
0
Age
23
XP
161
Country
Germany
if you're using my switch_linux repo, then it loads the kernel from the SD card. The only files uploaded are cbfs.bin and coreboot.rom which are small. I suggest you try another USB port or cable.



It would be possible once the kernel is fixed. We will be able to boot Linux from an USB stick too, albeit not very practical.
And can you tell me how to use your repo (if I don't do that somehow already :blush:), that it loads it from the SD card and not has to upload it everytime, so I can start Linux much faster? :rolleyes:
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: https://www.youtube.com/@legolambs