Jump to content
XPEnology Community

dvuv

Rookie
  • Posts

    6
  • Joined

  • Last visited

dvuv's Achievements

Newbie

Newbie (1/7)

1

Reputation

  1. I'm running on i3-7100U (intel NUC), everything works without problems, but only on baremetal. Tried running through proxmox with gpu passthrough without luck on this cpu . On SS 9.1 i'm running 1 face and 1 people task (via task activation workaround) with average load of 25%. Interestingly, SS 9.0 was generating almost twice as much load.
  2. thanks, i took existing serial and replaced first 7 chars with new ones - everything working now.
  3. @Orphéehi, can you suggest how to generate UBR number? ARPL loader always creates SJR license, is there any other
  4. Hi, I'm running DSM 7.1.1 upd4 DVA1622 baremetal on latest arpl. Received SS 9.1 update and after installing it all licenses are gone, license manager shows default 0 with invalid expiration date. Tried both updating from SS 9.0 and reinstalling everything (incl. DSM itself on a new hardware) from scratch right into latest version, still same result. My other true Syno (but just DS, not DVA) installed 9.1 without issues, so I really hope this is not a new surprise validation that needs to be dealt with. Anyone sees the same and have any ideas how to resolve that?
  5. Thanks for your response. What i need to be looking at in the bios (of the host pc?) that affects proxmox setup? Bios is the latest and default (never changed)
  6. Hello, I'm little puzzled and looking for a hint from community. I have 2 Intel NUCs of different generations. Tried both automatic redpill and tinycore. 1) based on i3-7100u CPU. Installed 1622 baremetal, everything (AI tasks) works fine, no issues. Decided to install through proxmox to not waste entire NUC for a single task, specified host CPU, and PCI passthrough for GPU (HD 620). Result – AI processes constantly crash and tasks do not work. One small detail if it matters – when enabling Local Screen, or right before shut down, attached monitor goes garbage. All other time I see Syno 1622 logo. 2) I pulled HDD from this NUC and installed it as-is (proxmox setup) into 8-gen with i3-8109U CPU (HD 655 gpu). Booted without making any changes, and boom, everything works! So at this point i'm certain that I followed all steps for setting up passthrough in proxmox according to instructions and it works. I have no idea why 1622 works on baremetal, doesn't work in proxmox, but works in proxmox on a next-gen CPU. Logic says to me that it should work in the first case, but it doesn't. I'm out of clues on where to look or what else to try, any suggestions?
×
×
  • Create New...