Jump to content
XPEnology Community

gadreel

Member
  • Posts

    317
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by gadreel

  1. Device Tree it's the way each model identifies the drives. It has nothing to do with BareMetal or a VM (my opinion).
  2. @Orphée Thanks, I created a task and then I received a message that I cannot have more than one or two tasks which is very limited. I have placed an order for a GTX 1650 GDDR5, to test DVA3221 which has a lot more tasks...
  3. @Orphée It worked, I installed on Proxmox 7.4 instead of 8, followed your guide to blacklist the i915 and I installed arc loader and DSM 7.1. I used 3e91 as the device id and it works. I feel that the reason it was not working before it was due to DSM 7.2...
  4. @Orphée I tried through Proxmox, I went though your steps and everything but no luck. Today I tried with DSM 7.1 and I got it to output the display. Does the DSM version matters? Same question goes for ARPL and ARC will it make any difference if I use ARPL instead of ARC loader?
  5. @Orphée But now in baremetal what I did? I removed all the addons and the i915 module and I see the HDMI output. This is the same as in Plex and Emby, the iGPU will work upto that extend only (Plex/Emby/HDMI Output)?
  6. Hi all, From what I read in this topic from the 4th Gen to the 10th Gen, iGPU should work with DVA1622. I have an i5 10600 with UHD 630 8086:9BC8 but it does not work when I passthrough the iGPU with Proxmox. EDIT1: I tried baremetal and I am getting video output through the HDMI but I still when trying to test face detection I am getting "unable to perform this operation..." @DVA1622:/$ dmesg -T | grep i915 [Tue Sep 5 21:23:31 2023] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [Tue Sep 5 21:23:31 2023] [drm] Initialized i915 1.6.0 20171222 for 0000:00:02.0 on minor 0 [Tue Sep 5 21:23:32 2023] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [Tue Sep 5 21:23:34 2023] Modules linked in: thermal(OE) kvm_intel kvm irqbypass acpi_cpufreq rtc_cmos(OE) xhci_pci leds_lp3943 aesni_intel glue_helper lrw gf128mul ablk_helper geminilake_synobios(PO) hid_generic usbhid hid usblp i915(E) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button i2c_algo_bit uhci_hcd etxhci_hcd ehci_pci ehci_hcd usb_storage xhci_hcd usbcore sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus zram md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod arc4 crc32c_intel cryptd ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel Any ideas?
  7. Hello, I have a 1Gbit port and 10Gbit port, is it possible configure the ARPL i18n loader to which port will be eth0 and which eth1? Because every time I reboot the VM it changes around and is breaking my HA cluster.
  8. A more advanced approach is to use Cloudflare zero trust and apply security measures...
  9. Hi start reading from here. You can read in this guide which platforms can be used based on your CPU. The below topic contains even more info.
  10. What might not being supported is Transcoding and stuff related to that. Installing DSM should not be a problem.
  11. As long the is an x86 architecture it should not be any problem.
  12. Their are ways to fix it but it's "complicate" and it's more of a trial and error. Most of the time we suggest to users to let it go. Technically there is NO issue when the drives look like this. If you have a major OCD you could install a model that supports Directory Tree instead which maps the drives different and you do not have this issue.
  13. I do not know, I thought because it's a major version and different kernels we have to rebuild the loader. I might be wrong...
  14. Hi all, please remind me what is the correct procedure on arpl-i18n to update from 7.1.1 to 7.2? Update from DSM and then rebuild the loader or update from DSM and the loader will do the rest on it's own? Edit: Updated DSM and then rebuild the loader. All good at the end.
  15. I totally agree, provoking and poking Synology will take down the forum.
  16. I do not think so. XPEnology will only work on Intel and AMD x86 architecture CPUs.
  17. What I meant to say is that if you want to take Snapshots you will need Btrfs. If you do not need those you can stick with Ext4.
  18. Hi, you have answered your own question . If you are not using any of those APPs that require Btrfs then there is no need for it if you are just storing data.
  19. If you want to use Cloudflare Tunnel and you do not want others to mess with the DSM login page create application policies to protect it.
  20. No. Raspberry Pi 4 has an ARM CPU which is not compatible. Only x86, x86-64 architecture CPUs are supported like Intel and AMD.
  21. Yes read this guide to see the limits for each platform. As you mentioned the DS918+ cannot have more than 8 cores... Install DS3622xs+ if you want to have more cores.
  22. If bootloader was not updated, yes. Sonoloygy does not always update it with minor patches that is why u still see U2
  23. Hello guys, I just replaced my old motherboard with a new ASRock Rack X570D4U-2L2T/BCM. This motherboard contains the 2 x 10Gbe [14e4:16d8] 24:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) This motherboard also contains 2 x 1Gbe Intel I210 Previously I had a PCI card with 2 x 10gbe X550 Intel and it was working fine. To the question. I have ARPL loader v0.4-alpha 6 which works fantastic on my (Virtual) DS918+ and I do not want to replace it with an updated version. What is the correct procedure to detect this new BCM 10Gbe? I tried to only rebuild the loader and it does not work. If I pass-through the I210 it works just fine when I rebuild the loader. Any suggestions?
  24. It's not dead, it was used for the old loaders for DSM 6.
  25. No, DSM is not that type of OS that you can install with an ISO. Installing the DSM on Baremetal or VM still you need to follow the same procedures to do. Redpill is the loader is the code that makes all this magic work so that we can install DSM on a non-synology hardware. TinyCore and ARPL to keep it simple they are software to make us (noob users) life easier without the need to understand how this magic works. Write a few commands or press a few buttons and you are done... I do non know if downloading the image of others will work. I suggest start reading the forum and you will find that it's easy. The booting message that you see on your screen is totally normal that is what is supposed to say. In order to continue to see the log after the booting if you are on a VM you need a Serial Interface (again you need to read). After seeing the "Booting" message you need to use Synology assistant. If everything works fine and your DSM picked up an IP you will see the DSM in the synology assistant and from there you can install the DSM (like a normal synology). The whole thing about picking different models it depends on your needs and the hardware you have. See the guide below.
×
×
  • Create New...