Jump to content

BoarAnt

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

1 Neutral

About BoarAnt

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just an update: I'm on RC7, and everything still is working well. Server logs still produce the same results even after multiple reboots, so everything's looking great. Thanks!
  2. I just booted up RC6, and I'm happy to report the card is working correctly now: Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Reserved 92MB host memory for HMA Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Successfully enabled ppod edram feature Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Successfully configured using Firmware Configuration File "Firmware Default", version 0x0, computed checksum 0x0 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: max_ordird_qp 21 max_ird_adapter 5376 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: ppod edram start 0x0 end 0x0 size 0x1 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Current filter mode/mask 0x632b:0x21 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: 130 MSI-X vectors allocated, nic 16 per uld 16 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4 eth2: eth2: Chelsio T6225-OCP-SO (0000:81:00.4) 1G/10GBASE-SFP28 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4 eth3: eth3: Chelsio T6225-OCP-SO (0000:81:00.4) 1G/10G/25GBASE-SFP28 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Chelsio T6225-OCP-SO rev 0 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: S/N: XXXXXXX, P/N: YYYYYYYY Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Firmware version: 1.24.3.0 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Bootstrap version: 255.255.255.255 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: TP Microcode version: 0.1.23.2 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: No Expansion ROM loaded Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Serial Configuration version: 0x2001000 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: VPD version: 0x83 Nov 16 02:04:13 kernel: cxgb4 0000:81:00.4: Configuration: RNIC MSI-X, Offload capable Nov 16 02:04:14 kernel: Chelsio T4/T5/T6 Network Driver - version 2.0.0-ko Nov 16 02:04:14 kernel: cxgb4 0000:81:00.4: Coming up as MASTER: Initializing adapter Nov 16 02:04:14 kernel: cxgb4 0000:81:00.4: Direct firmware load for cxgb4/t6-config.txt failed with error -2 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Reserved 92MB host memory for HMA Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Successfully enabled ppod edram feature Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Successfully configured using Firmware Configuration File "Firmware Default", version 0x0, computed checksum 0x0 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: max_ordird_qp 21 max_ird_adapter 5376 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: ppod edram start 0x0 end 0x0 size 0x1 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Current filter mode/mask 0x632b:0x21 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: 130 MSI-X vectors allocated, nic 16 per uld 16 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: 63.008 Gb/s available PCIe bandwidth (8 GT/s x8 link) Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4 eth2: eth2: Chelsio T6225-OCP-SO (0000:81:00.4) 1G/10GBASE-SFP28 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4 eth3: eth3: Chelsio T6225-OCP-SO (0000:81:00.4) 1G/10G/25GBASE-SFP28 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Chelsio T6225-OCP-SO rev 0 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: S/N: XXXXXXX, P/N: YYYYYYYY Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Firmware version: 1.24.3.0 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Bootstrap version: 255.255.255.255 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: TP Microcode version: 0.1.23.2 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: No Expansion ROM loaded Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Serial Configuration version: 0x2001000 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: VPD version: 0x83 Nov 16 02:04:18 kernel: cxgb4 0000:81:00.4: Configuration: RNIC MSI-X, Offload capable eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.1.3 netmask 255.255.255.0 broadcast 10.0.1.255 inet6 fe80::207:43ff:fe04:c1c0 prefixlen 64 scopeid 0x20<link> ether 00:07:43:04:c1:c4 txqueuelen 1000 (Ethernet) RX packets 2901 bytes 990553 (967.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 246 bytes 42687 (41.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 117 eth3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 00:07:43:04:c1:c6 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 117 In this case, I just put in a transceiver in one port just as a test, and it got an IP without issues. The syslog is still complaining about a missing config file (cxgb4/t6-config.txt), but that's most likely user specific and shouldn't be in the image anyways. I believe this can be marked Solved now. Thanks!
  3. Correct. At the grub menu, press the Tab button to enable editing, and add nomodeset as an additional argument at the end of the linux line and press return to boot. Once unraid is up, be sure to go into the flash drive and edit those lines in your grub.cfg permanently.
  4. I'm not sure if you've done this yet, but have you added 'nomodeset' to the grub boot options yet? Most EPYC server boards have an aspeed bmc chip (mine is the ast2500) which interfered on boot. My unraid setup didn't boot until I added that in my grub configs.
  5. As you suggested I tried memtest in Legacy mode and it did work. I'll mark this as solved. thanks.
  6. I'm using a Gigabyte MZ32-AR0, and I upgraded from the stable build (6.7.2).
  7. Memtest reboots my server the second I select it in grub, but I'm assuming it's because I'm running a new EPYC 7002 build. I am able to run windows memory diagnostic and passmark's memtest86 fine, so I've used those instead to test my memory.
  8. Sorry. Too eager to move on to the next issue. 😅
  9. Hi, I'm have a Chelsio T6225-OCP nic that is currently experiencing errors when I try to bring it up: Nov 14 02:37:13 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:37:46 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:38:02 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:39:58 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 Nov 14 02:40:10 kernel: cxgb4 0000:81:00.4: Can't allocate queues, err=6 The boot log mentions that the drivers are failing to load: cxgb4 0000:81:00.4: Direct firmware load for cxgb4/t6fw.bin failed with error -2 cxgb4 0000:81:00.4: unable to load firmware image cxgb4/t6fw.bin, error -2 And upon further digging, there are no T5 & T6 drivers present in /lib/firmware/cxgb4 (/lib/firmware/cxgb3 drivers are present though). Hopefully it can be added soon (RC6 maybe?) Thanks.
  10. I'm using an EPYC 7452 on RC5 without issues.
  11. Awesome. I just tried it with the original version and it imports fine. Thanks for the quick turnaround!
  12. Following Mantene's suggestion, I also got it to work tonight by removing the comment at the top and removing any empty lines between the [Interface] and [Peer] entries. Importing the original config untouched ---------------------------------------------------------------------------------- # TorGuard WireGuard Config [Interface] PrivateKey = yyyyyyyyyyyyyyyyyyyyyy ListenPort = 51820 DNS = 1.1.1.1 Address = 10.29.1.55/24 [Peer] PublicKey = xxxxxxxxxxxxxxxxxxxxx AllowedIPs = 0.0.0.0/0 Endpoint = 111.111.111.111:443 PersistentKeepalive = 25 ---------------------------------------------------------------------------------- would give me 4 sections total: whereas the more compact version ---------------------------------------------------------------------------------- [Interface] PrivateKey = yyyyyyyyyyyyyyyyyyyyyy ListenPort = 51820 DNS = 1.1.1.1 Address = 10.29.1.55/24 [Peer] PublicKey = xxxxxxxxxxxxxxxxxxxxx AllowedIPs = 0.0.0.0/0 Endpoint = 111.111.111.111:443 PersistentKeepalive = 25 ---------------------------------------------------------------------------------- would give me 2 sections: The 2nd version was connecting fine, so I think it's just the import config parser that's messing up the setup. Thanks.
  13. To answer your question, no, those fields are not populated during the config file import.