rok1 Posted April 10, 2023 Share #51 Posted April 10, 2023 13 hours ago, IG-88 said: nothing special, just a 9th gen cpu, B365 chipset and onboard sata (ahci) what hardware did you try? Shuttle MiniPC w/i3-7100T.. it works fine with DS920 and DVA3221 It does have an msata disk, not sure if the SA6400 has issues with non synology disks Quote Link to comment Share on other sites More sharing options...
IG-88 Posted May 3, 2023 Share #52 Posted May 3, 2023 (edited) On 4/10/2023 at 2:17 AM, rok1 said: Shuttle MiniPC w/i3-7100T.. it works fine with DS920 and DVA3221 It does have an msata disk, not sure if the SA6400 has issues with non synology disks there was a comment on jim ma's blog about disk issues "Due to compatibility or performance issues on some machines, /dev/console was created late, causing redpill.ko to fail to load, and eventually the hard disk could not be found. The donation version has been repaired" i did see a no disk message on a test notebook with 11th gen cpu that only had nvme and was extended to have a jmb585 ahci controller by a m.2 nvme to pcie adapter, my original test system with a m365 chipset and 9th gen cpu did work without problems in that regard Edited May 3, 2023 by IG-88 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 5, 2023 Author Share #53 Posted May 5, 2023 @pocopico Can you check the issue below? I would like to be able to use the SA6400 in TCRP as well. https://github.com/kiler129/recreate-zImage/issues/1 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 6, 2023 Author Share #54 Posted May 6, 2023 9 hours ago, Peter Suh said: @pocopico Can you check the issue below? I would like to be able to use the SA6400 in TCRP as well. https://github.com/kiler129/recreate-zImage/issues/1 I created a compilation environment after installing Ubuntu 22.04.02 desktop to the VM to be similar to the workflow environment. Prepared for compilation by following the steps below. [ sshd active ] sudo apt-get update sudo apt-get install ssh sudo service ssh start; sudo service ssh status sudo ufw allow ssh ; sudo ufw status [ Preparing Kernel Compilation ] 1. Install kernel compiler (including curl, git) sudo apt-get install build-essential libncurses-dev libssl-dev libelf-dev libgmp3-dev bison flex libmpc-dev libmpfr-dev texinfo curl git 2. Install Kernel Package Manager sudo apt-get install linux-generic [ From Action workflow make5.yml , need to run with root authority ] https://github.com/PeterSuh-Q3/redpill-load/blob/master/tools/make5.sh sudo -i curl -kLO https://github.com/PeterSuh-Q3/redpill-load/raw/master/tools/make5.sh chmod +x make5.sh ./make5.sh The direct cause of the issue you inquired about yesterday seems to come from the compiled results on my VM Ubuntu. If this error is resolved, it seems that zImage regeneration is possible even in kernel 5. /opt/build/toolchain/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-nm: vmlinux: no symbols CC arch/x86/boot/compressed/misc.o arch/x86/boot/compressed/misc.c: In function ‘handle_relocations’: arch/x86/boot/compressed/misc.c:182:39: error: ‘VO___bss_start’ undeclared (first use in this function); did you mean ‘mm_rss_stat’? unsigned long max_addr = min_addr + (VO___bss_start - VO__text); ^~~~~~~~~~~~~~ mm_rss_stat arch/x86/boot/compressed/misc.c:182:39: note: each undeclared identifier is reported only once for each function it appears in arch/x86/boot/compressed/misc.c:182:56: error: ‘VO__text’ undeclared (first use in this function); did you mean ‘xas_next’? unsigned long max_addr = min_addr + (VO___bss_start - VO__text); ^~~~~~~~ xas_next arch/x86/boot/compressed/misc.c: In function ‘extract_kernel’: arch/x86/boot/compressed/misc.c:347:42: error: ‘VO__end’ undeclared (first use in this function); did you mean ‘_end’? const unsigned long kernel_total_size = VO__end - VO__text; ^~~~~~~ _end arch/x86/boot/compressed/misc.c:347:52: error: ‘VO__text’ undeclared (first use in this function); did you mean ‘xas_next’? const unsigned long kernel_total_size = VO__end - VO__text; ^~~~~~~~ xas_next make[2]: *** [scripts/Makefile.build:280: arch/x86/boot/compressed/misc.o] Error 1 make[1]: *** [arch/x86/boot/Makefile:115: arch/x86/boot/compressed/vmlinux] Error 2 make: *** [arch/x86/Makefile:270: bzImage] Error 2 cp: cannot stat 'arch/x86/boot/bzImage': No such file or directory ... Make-ing early/80386 code... CALL scripts/checksyscalls.sh CALL scripts/atomic/check-atomics.sh DESCEND objtool make[2]: *** No rule to make target 'arch/x86/boot/compressed/cmdline.o'. Stop. make[1]: *** [scripts/Makefile.build:472: __build] Error 2 make: *** [Makefile:1822: arch/x86] Error 2 Failed to create early/80386 code! Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 6, 2023 Author Share #55 Posted May 6, 2023 Finally, I succeeded in creating bsp of SA6400 for TCRP. https://github.com/PeterSuh-Q3/redpill-load/tree/master/config/SA6400/7.1.1-42962 I've changed my mind a bit. To regenerate zImage, should I use the same version of the toolchain and Linux source as the kernel version of DSM? The bottom line was that it wasn't. It seems that the kernel version to be used for bsp generation does not have to be the same as the kernel version of DSM. https://github.com/PeterSuh-Q3/redpill-load/actions/runs/4902082033/workflow 7.1.1-42962 has been deployed to M SHELL for the SA6400 model. Loaderbuild and booting of the FRIEND kernel also work without problems. However, problems still remain. The /dev/synoboot device is not found normally. It doesn't discriminate between bare metal and VM. Although it was possible to force synoboot to be created, During the DSM installation process, I encounter a 55% file corruption message. I will focus on this matter from tomorrow. I'd love to have a solution for this part. 2 Quote Link to comment Share on other sites More sharing options...
merve04 Posted May 6, 2023 Share #56 Posted May 6, 2023 47 minutes ago, Peter Suh said: Finally, I succeeded in creating bsp of SA6400 for TCRP. https://github.com/PeterSuh-Q3/redpill-load/tree/master/config/SA6400/7.1.1-42962 I've changed my mind a bit. To regenerate zImage, should I use the same version of the toolchain and Linux source as the kernel version of DSM? The bottom line was that it wasn't. It seems that the kernel version to be used for bsp generation does not have to be the same as the kernel version of DSM. https://github.com/PeterSuh-Q3/redpill-load/actions/runs/4902082033/workflow 7.1.1-42962 has been deployed to M SHELL for the SA6400 model. Loaderbuild and booting of the FRIEND kernel also work without problems. However, problems still remain. The /dev/synoboot device is not found normally. It doesn't discriminate between bare metal and VM. Although it was possible to force synoboot to be created, During the DSM installation process, I encounter a 55% file corruption message. I will focus on this matter from tomorrow. I'd love to have a solution for this part. I'm already using your fork of TCRP and wondering if theres a quick way to update the loader or do I need to download latest and recreate usb? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 7, 2023 Author Share #57 Posted May 7, 2023 11 hours ago, merve04 said: I'm already using your fork of TCRP and wondering if theres a quick way to update the loader or do I need to download latest and recreate usb? The TCRP fork is worth using if you are interested in developing TCRP yourself. ^^ As soon as you enter TC Linux, the loader builder screen of M SHELL for TCRP, automatic update to the latest version is processed. The USB does not need to be re-recorded. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 11, 2023 Author Share #58 Posted May 11, 2023 (edited) SA6400 can finally be installed on M SHELL for TCRP. thank you jim3ma. I've been wandering for days because I didn't know that AuxXxilium's disks addon must be added. https://github.com/AuxXxilium/arc-addons/tree/main/disks So far, the loader only works for USB. It has not been developed for SATA. On bare metal it works just fine with a USB stick without any fiddling. Edited May 11, 2023 by Peter Suh 2 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 11, 2023 Author Share #59 Posted May 11, 2023 (edited) How to switch from proxmox to USB. vi /etc/pve/qemu-server/100.conf args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/images/tinycore-redpill.v0.9.4.3-2.m-shell.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader, id=usb-disk-bootloader,bootindex=999,removable=on' Edited May 11, 2023 by Peter Suh 2 Quote Link to comment Share on other sites More sharing options...
maqros Posted May 13, 2023 Share #60 Posted May 13, 2023 В 06.05.2023 в 18:27, Peter Suh сказал: During the DSM installation process, I encounter a 55% file corruption message. В 11.05.2023 в 18:17, Peter Suh сказал: SA6400 can finally be installed on M SHELL for TCRP. Hi guys. Trying to install SA6400 on proxmox with tinycore-redpill.v0.9.4.3-2.m-shell.img, but getting corruption message at 55%. Have I missed something? Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 13, 2023 Share #61 Posted May 13, 2023 Same for me. and 7.2 RC fails at 8% By the way while install running, serial log is flooded by : [ 155.395790] synobios: buzzer stop button pressed [ 155.396993] Cannot get i2c adapter! [ 155.397685] Cannot get i2c adapter! [ 156.675564] synobios: buzzer stop button pressed [ 156.676753] Cannot get i2c adapter! [ 156.677407] Cannot get i2c adapter! [ 157.955597] synobios: buzzer stop button pressed [ 157.956728] Cannot get i2c adapter! [ 157.957274] Cannot get i2c adapter! [ 159.235654] synobios: buzzer stop button pressed [ 159.236959] Cannot get i2c adapter! [ 159.237697] Cannot get i2c adapter! Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 13, 2023 Share #62 Posted May 13, 2023 SA6400 has a major issue. We cannot perform SATA shim. This means that the SA6400 loader will never work on VMware, unless we resolve the SATA shim issue. 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 13, 2023 Share #63 Posted May 13, 2023 While @jimmmmm 's loader worked and still running on my proxmox, trying to create a new VM with @Peter Suh's m-shell fails at 55% on 7.1.1 and 8% with 7.2 RC. I'm trying with directly downloading PAT from internet (and not putting it manually) I don't see anything usefull in serial logs. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 13, 2023 Author Share #64 Posted May 13, 2023 (edited) 4 hours ago, Orphée said: While @jimmmmm 's loader worked and still running on my proxmox, trying to create a new VM with @Peter Suh's m-shell fails at 55% on 7.1.1 and 8% with 7.2 RC. I'm trying with directly downloading PAT from internet (and not putting it manually) I don't see anything usefull in serial logs. Yesterday I worked on adjusting the disks addon from the bundle exts list to the sa6400's custom_config.json. https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/disks The repeated phenomenon of "synobios: buzzer stop button pressed" and "Cannot get i2c adapter" in the serial log has not been seen since this disks addon is running. Could you please check if disks addon is located in /exts in junior state? If it exists, please also show the activity log. Edited May 13, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 14, 2023 Share #65 Posted May 14, 2023 (edited) 10 hours ago, Peter Suh said: Could you please check if disks addon is located in /exts in junior state? Switching to "j" at boot for install, I still have the i2c adapter flood. how do I check if addon is there ? Install error at 55% in junior mode too. Edit : From serial console in junior mode : Quote SynologyNAS> [ 47.745731] synobios: buzzer stop button pressed [ 47.746686] Cannot get i2c adapter! [ 47.747258] Cannot get i2c adapter! [ 49.025346] synobios: buzzer stop button pressed [ 49.026425] Cannot get i2c adapter! [ 49.027013] Cannot get i2c adapter! [ 50.305522] synobios: buzzer stop button pressed [ 50.306683] Cannot get i2c adapter! [ 50.307326] Cannot get i2c adapter! ls -[ 51.585503] synobios: buzzer stop button pressed [ 51.586519] Cannot get i2c adapter! [ 51.586959] Cannot get i2c adapter! Rtl .: drwxr-sr-x 2 root root 0 May 14 09:37 acpid drwxr-sr-x 2 root root 0 May 14 09:37 all-modules drwxr-sr-x 2 root root 0 May 14 09:37 cpufreq-scaler drwxr-sr-x 2 root root 0 May 14 09:37 cpuinfo drwxr-sr-x 2 root root 0 May 14 09:37 disks drwxr-sr-x 2 root root 0 May 14 09:37 eudev drwxr-sr-x 2 root root 0 May 14 09:37 misc drwxr-sr-x 2 root root 0 May 14 09:37 smb3-multi drwxr-sr-x 2 root root 0 May 14 09:37 thethorgroup.boot-wait -rw-r--r-- 1 root root 1359 May 14 09:37 __README__.txt -rwxr-xr-x 1 root root 4103 May 14 09:37 exec.sh ./acpid: -rw-r--r-- 1 root root 25084 May 14 09:37 acpid.tgz -rw-r--r-- 1 root root 1073 May 14 09:37 install.sh ./all-modules: -rw-r--r-- 1 root root 4437977 May 14 09:37 epyc7002-5.10.55.tgz -rw-r--r-- 1 root root 3169106 May 14 09:37 firmware.tgz -rw-r--r-- 1 root root 1086 May 14 09:37 install.sh -rw-r--r-- 1 root root 142352 May 14 09:37 kmod ./cpufreq-scaler: -rw-r--r-- 1 root root 1120 May 14 09:37 install.sh -rw-r--r-- 1 root root 3261 May 14 09:37 scaler.sh ./cpuinfo: -rw-r--r-- 1 root root 35446 May 14 09:37 cpuinfo.sh -rw-r--r-- 1 root root 571 May 14 09:37 install.sh ./disks: -rw-r--r-- 1 root root 150200 May 14 09:37 dtc -rw-r--r-- 1 root root 9320 May 14 09:37 install.sh -rw-r--r-- 1 root root 51880 May 14 09:37 readlink -rw-r--r-- 1 root root 179384 May 14 09:37 sed ./eudev: -rw-r--r-- 1 root root 3477213 May 14 09:37 eudev.tgz -rw-r--r-- 1 root root 2376 May 14 09:37 install.sh ./misc: -rw-r--r-- 1 root root 2987 May 14 09:37 install-all.sh -rw-r--r-- 1 root root 143 May 14 09:37 install_rd.sh -rwxr-xr-x 1 root root 79208 May 14 09:37 lrz -rwxr-xr-x 1 root root 80648 May 14 09:37 lsz -rwxr-xr-x 1 root root 1131952 May 14 09:37 ttyd ./smb3-multi: -rw-r--r-- 1 root root 837 May 14 09:37 install.sh -rw-r--r-- 1 root root 530 May 14 09:37 smb3-multi.sh ./thethorgroup.boot-wait: -rw-r--r-- 1 root root 1309 May 14 09:37 boot-wait.sh SynologyNAS> [ 52.865609] synobios: buzzer stop button pressed [ 52.866681] Cannot get i2c adapter! [ 52.867224] Cannot get i2c adapter! proxmox VM conf : args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/dump/orphee/sa6400-tinycore-redpill.v0.9.4.3-2.m-shell.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on' bios: ovmf boot: cores: 4 efidisk0: local:103/vm-103-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K machine: q35 memory: 4096 meta: creation-qemu=7.2.0,ctime=1683988519 name: TCRP-SA6400 net0: e1000=XX:XX:XX:XX:XX:XX,bridge=vmbr2,firewall=1 numa: 0 ostype: l26 sata0: local:103/vm-103-disk-1.qcow2,size=32G scsihw: virtio-scsi-single serial0: socket smbios1: uuid=xxxxxxxxxxxxxxxxxxx sockets: 1 vmgenid: xxxxxxxxxxxxxxxxxxxxxxxxxx Edit 2 : as you can see, I must set E1000 as network card or no network detected with virtio. Edited May 14, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
jimmmmm Posted May 14, 2023 Share #66 Posted May 14, 2023 45 minutes ago, Orphée said: Switching to "j" at boot for install, I still have the i2c adapter flood. how do I check if addon is there ? Install error at 55% in junior mode too. Edit : From serial console in junior mode : proxmox VM conf : args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/dump/orphee/sa6400-tinycore-redpill.v0.9.4.3-2.m-shell.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on' bios: ovmf boot: cores: 4 efidisk0: local:103/vm-103-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K machine: q35 memory: 4096 meta: creation-qemu=7.2.0,ctime=1683988519 name: TCRP-SA6400 net0: e1000=XX:XX:XX:XX:XX:XX,bridge=vmbr2,firewall=1 numa: 0 ostype: l26 sata0: local:103/vm-103-disk-1.qcow2,size=32G scsihw: virtio-scsi-single serial0: socket smbios1: uuid=xxxxxxxxxxxxxxxxxxx sockets: 1 vmgenid: xxxxxxxxxxxxxxxxxxxxxxxxxx Edit 2 : as you can see, I must set E1000 as network card or no network detected with virtio. Please ensure redpill lkm is loaded. Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 14, 2023 Share #67 Posted May 14, 2023 (edited) 14 minutes ago, jimmmmm said: Please ensure redpill lkm is loaded. Quote SynologyNAS> dmesg |grep redpill [ 1.708908] redpill: loading out-of-tree module taints kernel. [ 1.709581] redpill: module verification failed: signature and/or required key missing - tainting kernel [ 1.710862] redpill: Unknown symbol __might_sleep (err -2) [ 1.711741] redpill: Unknown symbol __might_sleep (err -2) SynologyNAS> [ 641.708936] synobios: buzzer stop button pressed [ 641.709802] Cannot get i2c adapter! [ 641.710235] Cannot get i2c adapter! [ 642.988345] synobios: buzzer stop b Edited May 14, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
jimmmmm Posted May 14, 2023 Share #68 Posted May 14, 2023 3 hours ago, Orphée said: [ 1.710862] redpill: Unknown symbol __might_sleep (err -2) [ 1.711741] redpill: Unknown symbol __might_sleep (err -2) So you need rebuild the redpill lkm and any other modules. The kernel config between SA6400 7.1 and 7.2 are different. You can not share the modules. Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 14, 2023 Share #69 Posted May 14, 2023 (edited) 10 minutes ago, jimmmmm said: [ 1.710862] redpill: Unknown symbol __might_sleep (err -2) [ 1.711741] redpill: Unknown symbol __might_sleep (err -2) So you need rebuild the redpill lkm and any other modules. The kernel config between SA6400 7.1 and 7.2 are different. You can not share the modules. I'm using @Peter Suh's loader. So I don't compile anything myself. So I guess something is wrong somewere... or I miss a step. Edited May 14, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 14, 2023 Author Share #70 Posted May 14, 2023 (edited) A few days ago, I forked the lkm5 that jimmmmm told me and compiled the module. The results shared above have been successful using the lkm5 module in the release. https://github.com/PeterSuh-Q3/redpill-lkm5 However, as a result of repeating the test on proxmox now, it is impossible to install DSM on the 7.1.1-42962 SA6400 again. Repeated i2c and buzzer error messages also start appearing again. I don't know why this would be different either. Is it correct that the disks addon is helping? Edited May 14, 2023 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 14, 2023 Share #71 Posted May 14, 2023 (edited) With 7.2 RC I don't have the err -2 from dmesg command line : But it fails at 8% when downloading PAT file from GUI. SynologyNAS> dmesg |grep -i redpill [ 2.186418] redpill: loading out-of-tree module taints kernel. [ 2.187402] redpill: module verification failed: signature and/or required key missing - tainting kernel SynologyNAS> [ 91.254966] md/raid1:md0: active with 1 out of 1 mirrors [ 91.260737] md0: detected capacity change from 0 to 8589869056 [ 94.316333] md/raid1:md1: active with 1 out of 1 mirrors [ 94.319121] md1: detected capacity change from 0 to 2147418112 [ 95.322361] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 95.854503] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 95.868003] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Failed to install file. The file is probably corrupted. Edited May 14, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 14, 2023 Share #72 Posted May 14, 2023 (edited) OK, let me guess, you can't install 7.2 RC with selecting to download PAT file from internet ? Quote SynologyNAS> synoupgrade --check synoupgrade.c:1156 Percent = 100, Process = 2968, FilePath = /tmpData//@autoupdate/DSM_SA6400_42962.pat, FileLink = https://global.download.synology.com/download/DSM/release/7.2/64551/DSM_SA6400_42962.pat synoupgrade.c:370 LocalMajor = 7, ServerMajor = 7 synoupgrade.c:371 Localminor = 2, Serverminor = 2 synoupgrade.c:394 LocalInfo = 64551, ServerInfo = 64551 Title: DSM 7.2-64551 Download link: https://global.download.synology.com/download/DSM/release/7.2/64551/DSM_SA6400_42962.pat CheckSum: ef8ebe0f0f8734026c300515fd8a69ed Version: DSM 7.2-64551 It probably does not download the correct PAT file as the link tries to download 42962 release inside 64551 folder. And I can't upload mine manually as my server is remote and I can't upload it, it would last for hours... Edit : On my local server, manually updoading PAT file did work and passed the 8%, then 55%, then rebooted, OK So 7.2 RC install seems to work with manual giving PAT file. Edited May 14, 2023 by Orphée Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 15, 2023 Share #73 Posted May 15, 2023 13 hours ago, Orphée said: OK, let me guess, you can't install 7.2 RC with selecting to download PAT file from internet ? It probably does not download the correct PAT file as the link tries to download 42962 release inside 64551 folder. And I can't upload mine manually as my server is remote and I can't upload it, it would last for hours... Edit : On my local server, manually updoading PAT file did work and passed the 8%, then 55%, then rebooted, OK So 7.2 RC install seems to work with manual giving PAT file. So that means its an rss issue right ? Quote Link to comment Share on other sites More sharing options...
Orphée Posted May 15, 2023 Share #74 Posted May 15, 2023 1 hour ago, pocopico said: So that means its an rss issue right ? Well maybe, I don't really know how it works But looking in rss.json or rss.xml in @Peter Suh's redpill-load develop branch repo, I don't see SA6400 configuration. 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted May 15, 2023 Author Share #75 Posted May 15, 2023 29 minutes ago, Orphée said: Well maybe, I don't really know how it works But looking in rss.json or rss.xml in @Peter Suh's redpill-load develop branch repo, I don't see SA6400 configuration. Just corrected a typo in the revision. thank you. https://github.com/PeterSuh-Q3/redpill-load/commit/a62df779fe5940e243755a486095e079fa2bb1d5 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.