Jump to content

mrhanderson

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

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

mrhanderson's Achievements

Noob

Noob (1/14)

4

Reputation

1

Community Answers

  1. Wondering if 6.12.11 also fixes? Can't tell from the release notes, although it still seems to be on the older kernel, so perhaps not?
  2. Wondering if whatever fixed this issue was backported? Reports that the v7 betas have resolved it. If anyone with the 680 chip installs and can report, thanks.
  3. Anyone running a 13th gen Intel & W680 board combo that has been able to successfully install this update? Updates after 6.12.4 resulted in loss of iGPU access and reboot hangs. Hoping things are better with this update, but also hoping to hear from others before I try again myself. Still on 6.12.4 at this time. There is a thread here:
  4. Thank you for starting this thread. Hopefully it gets some attention so that the issue can be addressed (and hopefully it is something that actually can be addressed). Adding my +1 as a data point, I have a ASUS Pro WS W680M-ACE SE and a 13500 and am impacted by this issue. As such, I have remained on 16.2.4 at this time.
  5. I don't really want to lose KVM access either but I also definitely need iGPU, so I guess I'll continue to remain on 6.12.4 for the time being and hope that eventually the issue will be resolved.
  6. I believe so. I have not done it myself yet (I'm still on 6.12.4 which was the last unaffected version). Another user that had experienced the same issues as me when trying to move to 6.12.6 reported that it had fixed the issue for them though. The multimonitor setting seems to have no impact on the issues that arise. Namely loss of iGPU access and reboot hangs. The only provided solution that seems to have worked so far is to blacklist the IPMI GPU. See https://forums.unraid.net/topic/148775-unraid-os-version-6126-available/?do=findComment&comment=1346775
  7. Have you disabled Fast Boot? If you have a 13th/14th gen Intel with iGPU, have you blacklisted the ast? Without both of those I believe you are likely to experience boot/reboot issues.
  8. Anyone running a 13th gen Intel & W680 board combo that has been able to successfully install this update? The previous 6.12.6 update resulted in loss of iGPU access and reboot hangs. Hoping things are better with this update, but also hoping to hear from others before I try again myself.
  9. FYI nzbget-ng/nzbget will be merging into nzbgetcom/nzbget From this point forward, I strongly encourage folks to treat nzbgetcom/nzbget as the 'official' repo. https://www.reddit.com/r/nzbget/comments/18ywnrf/nzbgetngnzbget_will_be_merging_into/
  10. Per @jakea333 stock Unraid seems to encounter the same issues.
  11. Had a little downtime so thought I would revisit this. Made no difference. Still hangs on every reboot, have to force reset. No iGPU access. Had to rollback to 6.12.4, again. And everything was back to working immediately. However, noticed this time on reboot I had a bunch of extra random stuff appear onscreen, followed by the message "not automatically fixing this" Research suggested running chkdsk on the USB. I did that, but no errors found. Plugged back in to the same USB port and rebooted. However now it seems to be stuck at "Verifying bzfirmware checksum...", but it does let me login to the GUI. Further research suggested copying over the original bz* files. Did that, doesn't get stuck on verifying anymore, but the random stuff and "not automatically fixing this" remained. Now found this thread https://forums.unraid.net/bug-reports/prereleases/there-are-differences-between-boot-sector-and-its-backup-r1745/ and followed it. Seems to have fixed that issue. TL;DR back on 6.12.4 and going to leave it alone at this point. Once something newer than 6.12.6 comes out I will wait and see if others report success before I even try.
  12. I experienced similar, 6.12.4 to 6.12.6. Lost access to iGPU, server would not reboot or shutdown. Rollback to 6.12.4 and everything working as per normal.
  13. Thanks, I did find your thread, but I don't believe it's relevant to my case. I have iGPU only, and no VFIO bindings AFAIK. I found at least one other person with a 13th Gen Intel that also seems to have lost iGPU access after 6.12.6. They also have a dGPU as well though, so I pointed them to your thread in the hopes it will help them. Not sure what the issue is for me though.
  14. Your fix doesn't seem relevant in my case, as I have iGPU only, so no vfio-pci.cfg that I can tell. I didn't try disabling VT-d, and don't have the time or inclination to create a trial USB to test. I just rolled back to 6.12.4 and everything started working again. iGPU detected and usable in Plex docker, reboots work again, no system hangs.
  15. Seems like there might be an issue with iGPU and 13th gen CPUs in 6.12.6 See if the fix posted here works for you too https://forums.unraid.net/bug-reports/stable-releases/612x-call-traces-on-modprobe-i915-with-intel-13th-gen-gigabyte-z690-ud-ddr4-board-with-vt-d-enabled-r2756/?do=findComment&comment=26738
×
×
  • Create New...