Jump to content
XPEnology Community

xuchuan

Transition Member
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

xuchuan's Achievements

Newbie

Newbie (1/7)

2

Reputation

  1. I am happy to inform you that I have modified the PCI slot location in the XML configuration file of the unraid virtual machine (the core display location is modified to 0000:00:02.0). Due to insufficient core memory, I can only assign the core graphics card to 2 VMs. Because I have an MSI 1660S graphics card, the rest of the virtual machines use VGPU, which solves the problem perfectly. However, the nuclear display decoding of the DSM version can only work under 7.1-42951, and it still does not work under 7.1-42962. I pray that I can work stably in the later period, and I am no longer tossing them.
  2. Before this, I ran your code successfully. However, I've switched to unraid now, using GTV-G, Assigned the nuclear display to 918-7.1-42951, But now there is an error and I don't know how to fix it ./in_modules.sh: line 10: 21836 Killed insmod i915.ko
  3. 1: You must integrate the 8125b driver when compiling the boot file. 2: Modify the number of network cards and MAC addresses in advance when compiling. 3: After the DSM is successfully installed, you can drive it perfectly after inserting the network card. (Remember, do not insert the network card in advance, otherwise there is a high chance that the IP will not be found)
  4. I also used an Asus AQC 107 last month, I found that it doesn't run at full speed, After that, I replaced it with a 8125b network card with 4 network ports. Then the network port aggregates 10 Gigabit, very perfect. One thing you must pay attention to: add the 8125B driver to the compilation boot file, and modify the number of network cards in advance. After successfully installing the DSM, insert a new network card. Otherwise, it will not succeed.
  5. Hi! I have an Nvidia card, but I don't know how I need to use the file you provided? Can you provide a document telling me how to use them?
  6. Hi! Thank you very much for your answer. After I searched for the reasons in many aspects. Your module is not any problem It is the reason of Google Chrome. (It is estimated that it is a version problem) When I switch to Firefox. It works perfectly.
  7. Emby can work with nuclear display. In the picture, the nuclear display has been called for transcoding I don't know the specific reason for this. Because you can see that the decoding is successful in the emby dashboard, but it will be stuck. At the same time, I also encountered the same problem as others. If I use 920+ 7.1 , It will display the standby interface of the monitoring system
  8. I am running it directly in DSM 918+7.1. No docker container is used. I also considered it to be a compatibility issue. Because my CPU is 10700, Nuclear ID: 9BC5 My friend's CPU is 10900T, DSM 918+7.1, using your module, Works perfectly.
  9. CPU: 10700 I used the 9BC8 file and found a little problem. jellyfin can decode, but emby prompts me:No compatible streams are currently available. Please try again later or contact your system administrator for details.
×
×
  • Create New...