tabrisnet Posted July 31 Posted July 31 [|] Error 1 occurred in main shell [ at /armbian/.tmp/work-5d76f14c-45ca-4630-ba99-8ded11db4ca4/uboot-write-Fhg7X/usr/lib/u-boot/platform_install.sh:6 and tracking down that platform_install.sh yields dd if="$SRC"/cache/sources/arm-trusted-firmware/mtksoc-20250212/build/mt7988/release/bl2.img of=$2 bs=512 seek=34 status=noxfer > /dev/null 2>&1; Note that cache/sources/arm-trusted-firmware does not appear to exist, and [although this may be my lack of knowing what to look for] I find no evidence it attempted to fetch this repo or build the firmware. Yes, this board is only recently submitted, so some problems may be expected. I did wait for the automated build, but no luck there. or maybe I'm screwing up the build somehow. Using docker, but it's on a Debian11 host, which I know isn't supported as a build platform. ./compile.sh build BOARD=bananapir4 BUILD_MINIMAL=yes RELEASE=bookworm DEBUG=yes KERNEL_CONFIGURE=no BRANCH=current Full build log here: https://paste.armbian.com/isidematup @chainsx looks to be the guy who submitted the pull-request. 0 Quote
tabrisnet Posted July 31 Author Posted July 31 for more fun... the bootloader doesn't appear to build. I tried both the mtksoc-20250212 and mtksoc-20250711 branches. root@c4b6c21f3c6a:/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212# make PLAT=mt7988 Building mt7988 CC plat/mediatek/mt7988/bl2/bl2_plat_init.c plat/mediatek/mt7988/bl2/bl2_plat_init.c:10:10: fatal error: bl2_plat_setup.h: No such file or directory 10 | #include <bl2_plat_setup.h> There *is* a bl2_plat_setup.h, but it's not in the mediatek/mt7988 dir but rather mediatek/apsoc_common/bl2. Fixing mediatek/platform.mk to reference that eventually produces a *new* build error root@c4b6c21f3c6a:/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212# make PLAT=mt7988 Building mt7988 make: *** No rule to make target 'fdts/.dts', needed by '/armbian/cache/sources/arm-trusted-firmware/mtksoc-20250212/build/mt7988/release/fdts/.pre.dts'. Stop. 0 Quote
tabrisnet Posted July 31 Author Posted July 31 two patches make the build problems go away... plus have to specify BOOT_DEVICE=sdmmc on the make cmdline tabris@brunnt:~/build/armbian-build/cache/sources/arm-trusted-firmware/mtksoc-20250212/plat/mediatek/mt7988$ git diff . diff --git a/plat/mediatek/mt7988/bl2/bl2.mk b/plat/mediatek/mt7988/bl2/bl2.mk index 0cfae30a2..19184da07 100644 --- a/plat/mediatek/mt7988/bl2/bl2.mk +++ b/plat/mediatek/mt7988/bl2/bl2.mk @@ -16,9 +16,6 @@ BL2_IMG_HDR_SOC := mt7986 I2C_SUPPORT ?= 0 EIP197_SUPPORT ?= 0 -FDT_SOURCES += fdts/$(DTS_NAME).dts -BL2_CPPFLAGS += -DDTB_PATH=\"$(BUILD_PLAT)/fdts/$(DTS_NAME).dtb\" - BL2_CPPFLAGS += -I$(APSOC_COMMON)/drivers/spi \ -I$(MTK_PLAT_SOC)/drivers/gpio \ -I$(MTK_PLAT_SOC)/drivers/spi @@ -139,3 +136,7 @@ $(error BOOT_DEVICE has invalid value. Please re-check.) endif endif # END OF BOOT_DEVICE + +FDT_SOURCES += fdts/$(DTS_NAME).dts +BL2_CPPFLAGS += -DDTB_PATH=\"$(BUILD_PLAT)/fdts/$(DTS_NAME).dtb\" + diff --git a/plat/mediatek/mt7988/platform.mk b/plat/mediatek/mt7988/platform.mk index 7db8a33c3..233840a38 100644 --- a/plat/mediatek/mt7988/platform.mk +++ b/plat/mediatek/mt7988/platform.mk @@ -24,6 +24,7 @@ RESET_TO_BL2 := 1 PLAT_INCLUDES := -Iinclude/plat/arm/common \ -Iinclude/plat/arm/common/aarch64 \ -I$(APSOC_COMMON) \ + -I$(APSOC_COMMON)/bl2 \ -I$(APSOC_COMMON)/drivers/uart \ -I$(APSOC_COMMON)/drivers/trng/v2 \ -I$(APSOC_COMMON)/drivers/wdt \ Note that I'm *NOT* claiming this will work. Just that the bootloader *builds* with make PLAT=mt7988 BOOT_DEVICE=sdmmc Further, this is me building from inside the docker-shell, it's not doing this for me... 0 Quote
tabrisnet Posted July 31 Author Posted July 31 Armbian build error now on the next line [🐳|💥] Error 1 occurred in main shell [ at /armbian/.tmp/work-9693551e-c3dd-4d65-ae26-dc7dd901481a/uboot-write-IoNha/usr/lib/u-boot/platform_install.sh:7 dd if="$SRC"/cache/u-boot_sdmmc.fip of=$2 bs=512 seek=13312 status=noxfer > /dev/null 2>&1; 0 Quote
tabrisnet Posted August 6 Author Posted August 6 so today's community build did produce an artifact. haven't attempted to boot it yet however. also a local build did succeed. https://github.com/armbian/build/pull/8464 for reference 0 Quote
tabrisnet Posted August 7 Author Posted August 7 "official" image boots! minor concern, but it's harmless as this isn't mt7986, maybe concern re mt7988/i2p5ge-phy-pmb.bin, but I don't find any evidence this network driver is in use. update-initramfs: Generating /boot/initrd.img-6.12.35-current-filogic W: Possible missing firmware /lib/firmware/mediatek/mt7988/i2p5ge-phy-pmb.bin for built-in driver mtk_2p5ge W: Possible missing firmware /lib/firmware/mediatek/mt7986_wo_1.bin for built-in driver mtk_eth W: Possible missing firmware /lib/firmware/mediatek/mt7986_wo_0.bin for built-in driver mtk_eth W: Possible missing firmware /lib/firmware/mediatek/mt7981_wo.bin for built-in driver mtk_eth update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.35-current-filogic greater concern, these firmware files don't appear to be packaged root@bananapir4:~# dpkg-query -S /lib/firmware/mediatek/mt7988/mt7988_wo_1.bin dpkg-query: no path found matching pattern /lib/firmware/mediatek/mt7988/mt7988_wo_1.bin root@bananapir4:~# ls -lh /lib/firmware/mediatek/mt7988/mt7988_wo_1.bin -rw-r--r-- 1 root root 106K Aug 6 12:42 /lib/firmware/mediatek/mt7988/mt7988_wo_1.bin config looks saner, so far, than the BSP debian12 image, happy for that. maybe concerning, missing firmware [ 192.593808] crypto-safexcel 15600000.crypto: Firmware load failed. [ 192.600004] crypto-safexcel 15600000.crypto: HW init failed (-4) [ 192.606451] crypto-safexcel 15600000.crypto: probe with driver crypto-safexcel failed with error -4 0 Quote
tabrisnet Posted August 7 Author Posted August 7 (edited) SFP interfaces don't seem to be working. ethtool says no linkbeat. they did work with the BPI BSP image tabris@ratatosk:~$ sudo dmesg |egrep '(phy|sfp)' [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd090] [ 0.000000] arch_timer: cp15 timer(s) running at 13.00MHz (phys). [ 1.601461] mtk-xsphy soc:xs-phy@11e10000: failed to get ref_clk(id-1) [ 3.706978] phy phy-soc:xs-phy@11e10000.3: type_sw - reg 0x194, index 0 [ 6.870917] sfp sfp1: Host maximum power 3.0W [ 6.884162] sfp sfp2: Host maximum power 3.0W [ 7.193471] sfp sfp1: module AQUANTIA AQS-107-B0C2-CX rev 05 sn 174300000001458 dc 171024 [ 7.214379] sfp sfp2: module FS SFP-10G-PC01 rev A sn C2503280489-1 dc 250312 [ 12.530165] mt7530-mmio 15020000.switch lan1: configuring for phy/internal link mode Edited August 7 by tabrisnet 0 Quote
laibsch Posted August 7 Posted August 7 Thank you for your continued work on this. Would you be interested to step up as official maintainer for the board, @tabrisnet? @chainsx, what do you think? 0 Quote
chainsx Posted August 7 Posted August 7 This bl2 issue has been fixed by this PR: https://github.com/armbian/build/pull/8464 mt7988/i2p5ge-phy-pmb.bin is a firmware for the 2.5G upgrade of BPI-R4 (replacing one of the SFP with 2.5G ETH). This version of the armbian kernel is based on the mainline (patches are entirely from OpenWRT), so there are some imperfections. If support for bsp is needed, it will be tested and added in future work. Additionally, this firmware is supported by community enthusiasts like me and is .csc support. It is not OFFICAL support, nor is .conf support. The work of this SBC requires everyone to work together. 0 Quote
laibsch Posted August 7 Posted August 7 5 minutes ago, chainsx said: The work of this SBC requires everyone to work together. Absolutely, and I believe that @tabrisnet could be a great addition to the team of supporters. In case he wants to do that. He certainly seems to have a good skill set and required curiosity. 1 Quote
tabrisnet Posted August 7 Author Posted August 7 2 hours ago, laibsch said: Thank you for your continued work on this. Would you be interested to step up as official maintainer for the board I don't think I can take on such a role, but as I do have two of these boards, I can run tests and debug things within my knowledge level [and can run tests as requested]. My specific reason to not want to take on a maintainer role here is I don't know enough of the armbian process nor the board itself. Maybe I can work my way up to it. re tests... e.g. I have a few 10GbE SFP+ I can test: I have an FS.com DAC, an Aquantia [now Marvell] AQS-107-B0C2-CX [both the DAC & the AQS as posted above], and some other SFP+ as well. I haven't built my own linux kernels in a decade plus but I do know how to work with menuconfig et al. to @chainsx I do understand that this needs collaboration. I'm willing to work on it. I just don't know how much I know. I can, e.g., pull i2c data for the SFPs... but I don't know how to read the raw hex data. Point me at docs or forum posts, ask me questions or to do stuff... I'm also on github with the same username. 0 Quote
tabrisnet Posted August 7 Author Posted August 7 the Aquantia SFP root@ratatosk:~# i2cdetect -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: UU -- -- -- -- -- -- -- root@ratatosk:~# i2cdump -y 4 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 03 04 22 00 00 00 00 00 00 00 00 00 64 00 00 00 ??".........d... 10: 00 00 1e 00 41 51 55 41 4e 54 49 41 20 20 20 20 ..?.AQUANTIA 20: 20 20 20 20 1c 00 17 b6 41 51 53 2d 31 30 37 2d ?.??AQS-107- 30: 42 30 43 32 2d 43 58 20 30 35 20 20 00 00 00 33 B0C2-CX 05 ...3 40: 28 00 00 00 31 37 34 33 30 30 30 30 30 30 30 31 (...174300000001 50: 34 35 38 20 31 37 31 30 32 34 20 20 00 70 00 18 458 171024 .p.? 60: 03 04 01 60 4e 81 02 00 00 20 20 20 20 20 20 20 ???`N??.. 70: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ c0: 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?............... d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ethtool output root@ratatosk:~# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no root@ratatosk:~# ethtool -m eth1 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x22 (RJ45) Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x1c Transceiver type : Extended: 10Gbase-T Short Reach Encoding : 0x00 (unspecified) BR, Nominal : 10000MBd Rate identifier : 0x00 (unspecified) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 0m Length (62.5um) : 0m Length (Copper) : 30m Length (OM3) : 0m Laser wavelength : 0nm Vendor name : AQUANTIA Vendor OUI : 00:17:b6 Vendor PN : AQS-107-B0C2-CX Vendor rev : 05 Option values : 0x28 0x00 Option : Retimer or CDR implemented Option : Power level 3 requirement BR margin, max : 0% BR margin, min : 0% Vendor SN : 174300000001458 Date code : 171024 ethtool says no linkbeat, but the network switch it's connected to says it's up [but no traffic detected] I don't have the DAC plugged in right now, as the workstation i'm using doesn't have any SFP ports available. 0 Quote
tabrisnet Posted August 7 Author Posted August 7 I moved the board back to my network core, and swapped the AQS SFP back to the WAN port. then inserted a Fiber SFP+ to the LAN port. by ip link set up dev eth2, I get the network switch to say there's link beat... but ethtool still says no tabris@ratatosk:~$ sudo ethtool eth1 Settings for eth1: Supported ports: [ FIBRE ] Supported link modes: 10000baseSR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10000baseSR/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: FIBRE PHYAD: 0 Transceiver: internal Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no tabris@ratatosk:~$ sudo ethtool -m eth1 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Transceiver type : 10G Ethernet: 10G Base-SR Encoding : 0x06 (64B/66B) BR, Nominal : 10300MBd Rate identifier : 0x00 (unspecified) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 80m Length (62.5um) : 30m Length (Copper) : 0m Length (OM3) : 300m Laser wavelength : 850nm Vendor name : SOURCEPHOTONICS Vendor OUI : 00:1f:22 Vendor PN : SFP-SR Vendor rev : 10 Option values : 0x00 0x1a Option : RX_LOS implemented Option : TX_FAULT implemented Option : TX_DISABLE implemented BR margin, max : 0% BR margin, min : 0% Vendor SN : 201712060269 Date code : 171206 Optical diagnostics support : Yes Laser bias current : 6.426 mA Laser output power : 0.4686 mW / -3.29 dBm Receiver signal average optical power : 0.7100 mW / -1.49 dBm Module temperature : 27.25 degrees C / 81.06 degrees F Module voltage : 3.3160 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : Off Laser bias current high warning : Off Laser bias current low warning : Off Laser output power high alarm : Off Laser output power low alarm : Off Laser output power high warning : Off Laser output power low warning : Off Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning : Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning : Off Laser rx power high alarm : Off Laser rx power low alarm : Off Laser rx power high warning : Off Laser rx power low warning : Off Laser bias current high alarm threshold : 15.000 mA Laser bias current low alarm threshold : 1.000 mA Laser bias current high warning threshold : 13.000 mA Laser bias current low warning threshold : 2.000 mA Laser output power high alarm threshold : 1.1220 mW / 0.50 dBm Laser output power low alarm threshold : 0.1862 mW / -7.30 dBm Laser output power high warning threshold : 1.0000 mW / 0.00 dBm Laser output power low warning threshold : 0.2344 mW / -6.30 dBm Module temperature high alarm threshold : 80.00 degrees C / 176.00 degrees F Module temperature low alarm threshold : -10.00 degrees C / 14.00 degrees F Module temperature high warning threshold : 75.00 degrees C / 167.00 degrees F Module temperature low warning threshold : -5.00 degrees C / 23.00 degrees F Module voltage high alarm threshold : 3.5999 V Module voltage low alarm threshold : 3.0000 V Module voltage high warning threshold : 3.5000 V Module voltage low warning threshold : 3.0999 V Laser rx power high alarm threshold : 1.1220 mW / 0.50 dBm Laser rx power low alarm threshold : 0.0645 mW / -11.90 dBm Laser rx power high warning threshold : 1.0000 mW / 0.00 dBm Laser rx power low warning threshold : 0.0812 mW / -10.90 dBm tabris@ratatosk:~$ sudo dmesg |egrep 'sfp[12]' [ 7.656413] sfp sfp1: Host maximum power 3.0W [ 7.664987] sfp sfp2: Host maximum power 3.0W [ 7.973441] sfp sfp1: module AQUANTIA AQS-107-B0C2-CX rev 05 sn 174300000001458 dc 171024 [ 7.994274] sfp sfp2: module SOURCEPHOTONICS SFP-SR rev 10 sn 201712060269 dc 171206 [ 723.697583] sfp sfp1: no PHY detected Hopefully this somewhat more normal SFP+ is useful. it's a Macroreer 10GBASE-SR, for HP Procurve. tabris@ratatosk:~$ sudo i2cdump -y 4 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 03 04 07 10 00 00 00 00 00 00 00 06 67 00 00 00 ????.......?g... 10: 08 03 00 1e 53 4f 55 52 43 45 50 48 4f 54 4f 4e ??.?SOURCEPHOTON 20: 49 43 53 20 00 00 1f 22 53 46 50 2d 53 52 20 20 ICS ..?"SFP-SR 30: 20 20 20 20 20 20 20 20 31 30 20 20 03 52 00 8e 10 ?R.? 40: 00 1a 00 00 32 30 31 37 31 32 30 36 30 32 36 39 .?..201712060269 50: 20 20 20 20 31 37 31 32 30 36 20 20 68 f0 03 ca 171206 h??? 60: 48 50 a0 00 80 50 20 20 4a 39 31 35 30 41 20 31 HP?.?P J9150A 1 70: 39 39 30 2d 34 30 36 35 20 20 00 32 00 00 00 00 990-4065 .2.... 80: 10 31 f1 e3 d6 b5 28 11 23 15 b1 f6 cf 33 34 cc ?1????(?#????34? 90: 1f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ??.............. a0: 00 00 48 50 20 50 72 6f 43 75 72 76 65 20 50 72 ..HP ProCurve Pr b0: 6f 70 72 69 65 74 61 72 79 20 74 72 61 64 65 20 oprietary trade c0: 73 65 63 72 65 74 20 2d 20 63 6f 70 79 69 6e 67 secret - copying d0: 20 69 73 20 70 72 6f 68 69 62 69 74 65 64 20 77 is prohibited w e0: 69 74 68 6f 75 74 20 70 65 72 6d 69 73 73 69 6f ithout permissio f0: 6e 2e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 n............... tabris@ratatosk:~$ sudo i2cdump -y 4 0x51 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 50 00 f6 00 4b 00 fb 00 8c 9f 75 30 88 b8 79 17 P.?.K.?.??u0??y? 10: 1d 4c 01 f4 19 64 03 e8 2b d4 07 46 27 10 09 28 ?L???d??+??F'??( 20: 2b d4 02 85 27 10 03 2c 00 00 00 00 00 00 00 00 +???'??,........ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00 ....??......?... 50: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 55 ?...?...?......U 60: 1b 46 81 71 0c 8d 12 6d 1b bc 00 00 00 00 00 00 ?F?q???m??...... 70: 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 ..........@..... 80: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? 90: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? a0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? b0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? c0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? d0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? e0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? f0: aa aa aa aa aa aa aa aa ff ff ff ff ff ff 49 2f ????????......I/ 0 Quote
laibsch Posted August 8 Posted August 8 9 hours ago, tabrisnet said: I don't think I can take on such a role, but as I do have two of these boards, I can run tests and debug things within my knowledge level [and can run tests as requested]. That's all it really means to be a maintainer in Armbian, though. People can look up in the board config that you have the machine and are - time permitting on a best-effort basis - willing to check for and verify devivce-specific issues. 9 hours ago, tabrisnet said: My specific reason to not want to take on a maintainer role here is I don't know enough of the armbian process nor the board itself. Maybe I can work my way up to it. Nobody in Armbian knows everything about the project and its boards or even a single board and nobody expects you to. What I have seen from you is more than enough to join @chainsx in his effort to improve support for the board. Again, at the very minimal your commitment can kind of go as low as being willing to try and reproduce/WFM device-specific issues, your time permitting. In this thread you've already done way, way more than that. I'd really like to welcome you to the official Armbian maintainer pool. If ever you have a question, don't hesitate to ask me personally or in our discord server. BTW, on the topic of missing firmware which started this thread, maybe it needs to be added to armbian-firmware, something I've also only discovered yesterday, thanks to @c0rnelius. 0 Quote
tabrisnet Posted Monday at 07:39 PM Author Posted Monday at 07:39 PM https://github.com/armbian/build/pull/8517 appears to fix my SFP problems. 1 Quote
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.
Note: Your post will require moderator approval before it will be visible.