apriliars3 Posted August 12, 2022 Share #251 Posted August 12, 2022 Works FS2500 with JUN mode. Warning with power supple, only one and original with two. Quote Link to comment Share on other sites More sharing options...
pro_info Posted August 15, 2022 Share #252 Posted August 15, 2022 Le 24/07/2022 à 17:17, maqros a dit : hi all. thanks for making installing dsm so easy. I did not find drivers for AQC111U 5Gb usb network adapters in the extensions. I am currently using the package from here https://github.com/bb-qq/aqc111. is it possible to add it? I'm also interrested! Quote Link to comment Share on other sites More sharing options...
phone guy Posted August 15, 2022 Share #253 Posted August 15, 2022 Is it possible to add jun mode to an already made loader? or just rebuild with same user/info and add jun to build? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 16, 2022 Share #254 Posted August 16, 2022 (edited) On 7/9/2022 at 5:57 PM, jumkey said: There is no /dev/synoboot partition, you need to confirm the value of pid vid or satadom @jumkey At the request of users using Real Synology RS3413xs+ Adding RS3413xs+ to redpill. This model is a bromolow platform like the DS3615xs. So, all kernels were built the same based on 3.10.108. By the way, I am reminded of what you mentioned to me in July and I am asking you again. All settings of this RS3413xs+ were made by copying the same as DS3615xs. redpill.ko was also compiled for RS3413xs+ models. However, /dev/synoboot does not appear. VID/PID is not used as we are testing in a VM environment. What could be the cause? https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/RS3413xs%2B/7.1.0-42661/config.json Spoiler RackStation> cat linuxrc.syno.impl | grep "exts" (/bin/sh /exts/exec.sh load_kmods && /bin/sh /exts/exec.sh on_boot_scripts && echo "Extensions processed") || Exit 99 "rp ext init exec failure" RackStation> cat /var/log/*rc* START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO VirtIO hypervisor detected Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: ) Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: ) Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: ) Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: ) Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: ) Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: ) Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: ) Loading kmod #7 "virtio_balloon.ko" for thethorgroup.virtio (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot Loading module e1000 -> Module e1000 loaded succesfully Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== /dev/sda1 2048 100351 98304 83 /dev/sda2 100352 253951 153600 83 /dev/sda3 253952 2097151 1843200 83 /dev/sdb1 8192 16785407 16777216 fd /dev/sdb2 16785408 20979711 4194304 fd /dev/sdb3 21241856 37588991 16347136 fd /dev/sdc1 8192 16785407 16777216 fd /dev/sdc2 16785408 20979711 4194304 fd /dev/sdc3 21241856 37588991 16347136 fd ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Tue Aug 16 12:09:18 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Edited August 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Amoureux Posted August 17, 2022 Share #255 Posted August 17, 2022 Updated today. 🙂 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 18, 2022 Share #256 Posted August 18, 2022 On 8/16/2022 at 10:17 PM, Peter Suh said: @jumkey At the request of users using Real Synology RS3413xs+ Adding RS3413xs+ to redpill. This model is a bromolow platform like the DS3615xs. So, all kernels were built the same based on 3.10.108. By the way, I am reminded of what you mentioned to me in July and I am asking you again. All settings of this RS3413xs+ were made by copying the same as DS3615xs. redpill.ko was also compiled for RS3413xs+ models. However, /dev/synoboot does not appear. VID/PID is not used as we are testing in a VM environment. What could be the cause? https://github.com/PeterSuh-Q3/redpill-load/blob/master/config/RS3413xs%2B/7.1.0-42661/config.json cat /var/log/*rc* (Reveal hidden contents) RackStation> cat linuxrc.syno.impl | grep "exts" (/bin/sh /exts/exec.sh load_kmods && /bin/sh /exts/exec.sh on_boot_scripts && echo "Extensions processed") || Exit 99 "rp ext init exec failure" RackStation> cat /var/log/*rc* START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO VirtIO hypervisor detected Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: ) Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: ) Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: ) Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: ) Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: ) Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: ) Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: ) Loading kmod #7 "virtio_balloon.ko" for thethorgroup.virtio (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot Loading module e1000 -> Module e1000 loaded succesfully Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Still waiting for boot device (waited 5 of 30 seconds) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== /dev/sda1 2048 100351 98304 83 /dev/sda2 100352 253951 153600 83 /dev/sda3 253952 2097151 1843200 83 /dev/sdb1 8192 16785407 16777216 fd /dev/sdb2 16785408 20979711 4194304 fd /dev/sdb3 21241856 37588991 16347136 fd /dev/sdc1 8192 16785407 16777216 fd /dev/sdc2 16785408 20979711 4194304 fd /dev/sdc3 21241856 37588991 16347136 fd ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=1 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Tue Aug 16 12:09:18 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 There was help from @fbelavenuto He recompiled redpill.ko corresponding to RS3413xs+ in lkm. As a result of replacing it with this redpill.ko, I was able to check all synoboot. However, the following error is confirmed in the junior log. This error seems to be causing the 55% file corruption message. This is the first message I've seen. Do I need to set the RAID configuration on the RackStation in advance? I haven't seen this error in other RS models. Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... RackStation> ll /dev/syno* crw-r--r-- 1 root root 201, 0 Aug 18 06:54 /dev/synobios brw------- 1 root root 135, 240 Aug 18 06:54 /dev/synoboot brw------- 1 root root 135, 241 Aug 18 06:54 /dev/synoboot1 brw------- 1 root root 135, 242 Aug 18 06:54 /dev/synoboot2 brw------- 1 root root 135, 243 Aug 18 06:54 /dev/synoboot3 RackStation> cd /var/log RackStation> ll drwxr-xr-x 2 root root 0 Aug 18 2022 . drwxr-xr-x 9 root root 0 Aug 18 2022 .. -rw-r--r-- 1 root root 94 Aug 18 2022 junior_reason -rw-r--r-- 1 root root 1493 Aug 18 2022 juniorexpansionpack.log -rw-r--r-- 1 root root 2075 Aug 18 2022 linuxrc.syno.log -rw-r--r-- 1 root root 67364 Jan 1 00:00 messages -rw-r--r-- 1 root root 181 Aug 18 2022 synoupdate.log RackStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO VirtIO hypervisor detected Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: ) Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: ) Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: ) Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: ) Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: ) Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: ) Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: ) Loading kmod #7 "virtio_balloon.ko" for thethorgroup.virtio (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot Loading module e1000 -> Module e1000 loaded succesfully Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 All disk ready or timeout execeed Assemble args: Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... Thu Aug 18 06:54:10 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 RackStation> ll drwxr-xr-x 2 root root 0 Aug 18 2022 . drwxr-xr-x 9 root root 0 Aug 18 2022 .. -rw-r--r-- 1 root root 94 Aug 18 2022 junior_reason -rw-r--r-- 1 root root 1493 Aug 18 2022 juniorexpansionpack.log -rw-r--r-- 1 root root 2075 Aug 18 2022 linuxrc.syno.log -rw-r--r-- 1 root root 71601 Jan 1 00:01 messages -rw-r--r-- 1 root root 181 Aug 18 2022 synoupdate.log RackStation> cat junior_reason Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... 1 Quote Link to comment Share on other sites More sharing options...
jumkey Posted August 18, 2022 Author Share #257 Posted August 18, 2022 24 minutes ago, Peter Suh said: There was help from @fbelavenuto He recompiled redpill.ko corresponding to RS3413xs+ in lkm. As a result of replacing it with this redpill.ko, I was able to check all synoboot. However, the following error is confirmed in the junior log. This error seems to be causing the 55% file corruption message. This is the first message I've seen. Do I need to set the RAID configuration on the RackStation in advance? I haven't seen this error in other RS models. Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... RackStation> ll /dev/syno* crw-r--r-- 1 root root 201, 0 Aug 18 06:54 /dev/synobios brw------- 1 root root 135, 240 Aug 18 06:54 /dev/synoboot brw------- 1 root root 135, 241 Aug 18 06:54 /dev/synoboot1 brw------- 1 root root 135, 242 Aug 18 06:54 /dev/synoboot2 brw------- 1 root root 135, 243 Aug 18 06:54 /dev/synoboot3 RackStation> cd /var/log RackStation> ll drwxr-xr-x 2 root root 0 Aug 18 2022 . drwxr-xr-x 9 root root 0 Aug 18 2022 .. -rw-r--r-- 1 root root 94 Aug 18 2022 junior_reason -rw-r--r-- 1 root root 1493 Aug 18 2022 juniorexpansionpack.log -rw-r--r-- 1 root root 2075 Aug 18 2022 linuxrc.syno.log -rw-r--r-- 1 root root 67364 Jan 1 00:00 messages -rw-r--r-- 1 root root 181 Aug 18 2022 synoupdate.log RackStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO VirtIO hypervisor detected Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: ) Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: ) Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: ) Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: ) Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: ) Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: ) Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: ) Loading kmod #7 "virtio_balloon.ko" for thethorgroup.virtio (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot Loading module e1000 -> Module e1000 loaded succesfully Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 All disk ready or timeout execeed Assemble args: Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... Thu Aug 18 06:54:10 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 RackStation> ll drwxr-xr-x 2 root root 0 Aug 18 2022 . drwxr-xr-x 9 root root 0 Aug 18 2022 .. -rw-r--r-- 1 root root 94 Aug 18 2022 junior_reason -rw-r--r-- 1 root root 1493 Aug 18 2022 juniorexpansionpack.log -rw-r--r-- 1 root root 2075 Aug 18 2022 linuxrc.syno.log -rw-r--r-- 1 root root 71601 Jan 1 00:01 messages -rw-r--r-- 1 root root 181 Aug 18 2022 synoupdate.log RackStation> cat junior_reason Exit on error [12] No raid status in path /sys/block/md0/md/array_state, go to junior mode... You can take a look at this issue https://github.com/RedPill-TTG/redpill-load/issues/6 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted August 18, 2022 Share #258 Posted August 18, 2022 48 minutes ago, jumkey said: You can take a look at this issue https://github.com/RedPill-TTG/redpill-load/issues/6 I read issue 6 carefully. Among the contents mentioned by TG, the contents of swap serial caught my eye. https://github.com/RedPill-TTG/redpill-load/issues/6#issuecomment-893032413 Is it necessary to enable swap_serial in bromolow like the screenshot below? As for RS3413xs+, wouldn't it be okay to turn it off as false like other models? What do you think? inserts a "-" after every character I type. Yeah, we saw that too. It's annoying but we don't have a solution for that problem yet. It is related to the serial swapping which is finicky (as well, nobody in the right mind predicted switching serial ports which are defined in such a way for 50 years ;)). It seems the install stops and errors out when it tries to mount /dev/synoboot2. If you look at the log there are 3 lines dealing with USB devices detection: Aug 3 08:33:10 kernel: [ 21.648972] <redpill/boot_device_shim.c:70> Found new device <vid=1d6b, pid=0002> - didn't match expected <vid=46f4, pid=0001> Aug 3 08:33:10 kernel: [ 21.674594] <redpill/boot_device_shim.c:70> Found new device <vid=1d6b, pid=0003> - didn't match expected <vid=46f4, pid=0001> Aug 3 08:33:10 kernel: [ 22.203400] <redpill/boot_device_shim.c:70> Found new device <vid=0e0f, pid=0003> - didn't match expected <vid=46f4, pid=0001> None of them are a USB storage device. Currently RP supports booting from USB devices only. The SATA DOM support is not done yet. We are not sure if ESXi allows for adding virtual USB drives? If not we will prioritize this in the pipeline. Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted September 8, 2022 Share #259 Posted September 8, 2022 (edited) I need to add for the Jumkey loader this Network adapter because it is not found with my jumkey Loader: Which driver and with wich command this driver must be added? HPE Ethernet 1Gb 2-port 332i Adapter is for the gen8 microserver original NIC thank you very much ./redpill_tool_chain.sh add https://raw.githubusercontent.com/jumkey/redpill-load/develop/redpill-misc/rpext-index.json ---maybe Here and which command ?? and which driver ? ./redpill_tool_chain.sh build ds3622xsp-7.0.1-42218 ./redpill_tool_chain.sh auto ds3622xsp-7.0.1-42218 Edited September 8, 2022 by nemesis122 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted September 8, 2022 Share #260 Posted September 8, 2022 (edited) 45 minutes ago, nemesis122 said: I need to add for the Jumkey loader this Network adapter because it is not found with my jumkey Loader: Which driver and with wich command this driver must be added? HPE Ethernet 1Gb 2-port 332i Adapter is for the gen8 microserver original NIC thank you very much ./redpill_tool_chain.sh add https://raw.githubusercontent.com/jumkey/redpill-load/develop/redpill-misc/rpext-index.json ---maybe Here and which command ?? and which driver ? ./redpill_tool_chain.sh build ds3622xsp-7.0.1-42218 ./redpill_tool_chain.sh auto ds3622xsp-7.0.1-42218 HPE Ethernet 1Gb 2-port 332i Adapter is for the gen8 microserver original NIC According to the HP Customer Support Center, Broadcom tg3 is used as the Linux driver for the NIC inquired. https://support.hpe.com/connect/s/product?language=en&ismnp=0&l5oid=1010843602&kmpmoid=1010843605&tab=driversAndSoftware&cep=on&driversAndSoftwareFilter=8000113&environmentType=2200022 Try adding the driver as follows. ./redpill_tool_chain.sh add https://raw.githubusercontent.com/pocopico/rp-ext/main/tg3/rpext-index.json Edited September 8, 2022 by Peter Suh 1 Quote Link to comment Share on other sites More sharing options...
nemesis122 Posted September 8, 2022 Share #261 Posted September 8, 2022 Hi Thank you 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.