Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Report Comments posted by eschultz

  1. On 10/5/2018 at 11:29 AM, Tward2 said:


    Looks like you manually booted in to 'Unraid OS GUI Mode' which doesn't have the 'pcie_acs_override=downstream' in the append line.  This explains why it's saying to reboot on the settings page because it expects 'pcie_acs_override=downstream' to be in the append line for the 'Unraid OS GUI Mode' too.  @bonienl is this a bug for the PCIe ACS Override setting not updating all the label sections in the syslinux.cfg file?

  2. 22 hours ago, Dazog said:

    Just to chime in.

    On my threadripper 1920x I am not seeing any issues on a asrock taichi running bios 3.30.


    Performance on my win10 vm is the same and no slow start up.

    It looks like Asrock BIOS 3.20 was AGESA but no mention of a AGESA upgrade in 3.30.  If it is still AGESA that would go against my suspicion of the older AGESA version causing the slowdown in the newer kernel found in Unraid 6.6.0.

  3. 7 hours ago, rinseaid said:

    I have a Gigabyte X399 Designaire running the F10 BIOS with a Threadripper 2950x. Windows 10 performance on 6.6.0 rc2 was very poor and I rolled back to 6.5.3. I haven't tried rc3 but I don't see anything in the changelog that makes me think this would be resolved.


    What I was seeing was extremely slow startups, including a significant delay until seeing the Tianocore logo, and then the spinning dots while Windows is booting would sort of stutter. Boot up took a total of around 5 minutes compared to 30ish seconds on 6.5.3. Performance while in the VM was similar - lots of stutters and delays. Couldn't see anything significant of interest in Task Manager.

    Was seeing this exact behavior with a early internal 6.6.0 build on my MSI X399 threadripper but it was before I upgraded the BIOS and the AGESA version installed was really old at the time.