Install of Ubuntu 26.04 LTS on Asus WS Pro WRX80E-SAGE SE Wifi system hangs at splash screen
▲ 3 r/Ubuntu

Install of Ubuntu 26.04 LTS on Asus WS Pro WRX80E-SAGE SE Wifi system hangs at splash screen

I have done some internet research on why the Ubuntu installer may be hanging for this motherboard but because it is an older motherboard everything I found was dated and I am hoping someone will have an idea as to what may be happening. I first set the following BIOS settings:

  • Fast Boot: Disabled
  • CSM: Disabled
  • Boot/Secure Boot state OS Type: set to Other OS
  • USB Configuration Legacy USB Support set to Enabled & XHCI Handoff Enabled (tried disabling both with no change)

I created the install USB by downloading Ubuntu 26.04 LTS Iso and using Rufus to store on USB 2.0 device. The USB was placed in one of the rear IO panel USB 3 slots and the system was booted through UEFI. I get to the GRUB Menu where I selected "Try Ubuntu or Install", I also tried "Ubuntu (Safe Graphics)", and the Ubuntu splash screen was displayed. The USB drive was accessed several times, then not accessed again and the system was hung and never started the install. Hitting the Escape key displayed the screen captured I attached. The system configuration is as follows:

  • Motherboard: Asus WS Pro WRX80E-Sage SE Wifi
  • BIOS: ver 1801 dated 10/16/2025 (latest version)
  • Processor: Ryzen Threadripper PRO 3955WX
  • DRAM: 128GB DDR4 2666 MHz ECC RDIMM (passed Memtest86 multiple times)
  • NVME: Corsair MP600 Pro MPX (4 TB)
  • GPU: EVGA RTX 3060 12GB in PCIe Slot 1

Windows 11 25H2 USB 3 flash did boot on this system. Any suggestion as to what I should try to get pass the splash screen would be very appreciated.

u/Plugh_Xyzzy — 1 day ago
▲ 0 r/unRAID

Crash Regularly Occurring During Build of Parity Drive

Hopefully, this is an appropriate place to post this but if not please let me know a better place. I have encountered a bunch of crashes when performing a Parity Sync upon installing a new parity drive in the system. The system was previously running without parity without incident. The system is configured with an ASUS B450M-M Motherboard (latest BIOS), Ryzen 7 5700G processor, 64GB of DDR4 RAM 3200 MT/s, an Intel ARC A5800 GPU, and 3 Seagate Exos SATA 14TB drives. At first the system would crash fairly quickly and required a hard reset to recover. Upon recovery an examination of the system log indicated the system crashed because of a Data Fabric Sync Flood with code 0x08000800. I found the following suggestions of things tried by another person on this forum and applied the same settings to my system.

CPU / Power Management:

  • Disabled Global C-States and set Power Idle Control to a non-low power mode
  • Disabled Performance Boost for stability
  • Disabled CPU Watchdog Timer

Memory / DRAM:

  • Left Gear Down Mode and Cmd2T at Auto
  • DRAM refresh modes and scrubber controls left on Auto
  • Spread Spectrum was disabled
  • XMP/DOCP profile disabled (running JEDEC default OF 2666 MT/s).

Interconnect / DF Options:

  • Memory Interleaving and related settings left on Auto
  • Disabled DF Sync Flood Propagation (to prevent cascading errors).
  • DF C-States disabled

PCIe / GPU / IOMMU:

  • PCIe ASPM Mode set to Disabled (to prevent link power management from destabilizing GPUs).
  • Removed the ARC A580 and only using iGPU

Misc

  • I have no VMs defined
  • Data hard drive temperature was stable at 40 deg C and 43 deg C. Parity was at 36 deg C

The system no longer indicates a Data Fabric Sync Flood but is still crashes after getting to about 75% of the 14TB parity sync after running for 11+ hours. Latest crash did require a hard reset. A notification indicated that the Parity Sync finished with 0 errors and was cancelled but it did not finish. I noticed that just before the crash occurred, the transfer rates from the two data drives to the parity drive drop to zero and then the crash occurred. I can't figure out how to attach the diagnostic log (perhaps someone can let me know how to do that). Any suggestions of what may be causing the issue or what things I can try next would be appreciated.

u/Plugh_Xyzzy — 1 month ago

Issue with use of Fan/ARGB Hubs on Light Base 900

I am having some difficulty using the two Fan/ARGB hubs installed in the Be Quiet Light Base 900 for a system I just built. I have a total of 9 fans installed in the case and an AIO all of which have their ARGB plugged into the upper and lower hubs that came with the case. The hubs are connected together and one of the hubs is then connected to the motherboard. All of the LEDs light but each fan and the case are not individually addressable. As many of you may know, SignalRGB does not natively have a definition for the Light Base 900 so I had to roll my own. When I first started SignalRGB, it did not identify any of the fans, the AIO or the case fans and I had to manually define them.

When I use SignalRGB to light LED #1 for example, it lights on all fans, the AIO and the case LEDs. It appears all ARGB strings are mapped to the same address. Is this expected behavior or are the LEDs supposed to be individually addressable when using the hubs. Is this a wiring problem, a SignalRGB problem, or a problem of my understanding how this is supposed to work because all of the examples shown in the SignalRGB videos seems to show for other cases the LEDs on each fan being independently controllable. Thanks for the help.

reddit.com
u/Plugh_Xyzzy — 3 months ago

Issue with use of Fan/ARGB Hubs on Light Base 900

All, I have already directed this question to Be Quiet but just in case anyone here has an idea I am also posting here. I am having some difficulty using the Fan/ARGB hubs installed in the Light Base 900. I have a total of 9 fans installed in the case and an AIO all of which have their ARGB plugged into the upper and lower hubs. One of the hubs is then connected to the motherboard. All of the LEDs light but each fan and the case are not individually addressable. As many of you may know, SignalRGB does not natively have a definition for the Light Base 900 so I had to roll my own. When I first started Signal RGB, it did not identify any of the fans, the AIO or the case fans and I had to manually define them.

When I use SignalRGB to light LED #1 for example, it lights on all fans, the AIO and the case LEDs. It appears all ARGB strings are mapped to the same address. Is this expected behavior or are the LEDs supposed to be individually addressable when using the hubs. Is this a wiring problem, a SignalRGB problem, or a problem of my understanding how this is supposed to work because all of the examples shown in the SignalRGB videos seems to show for other cases the LEDs on each fan being independently controllable. Thanks for the help.

reddit.com
u/Plugh_Xyzzy — 3 months ago