Jump to content
XPEnology Community

pigr8

Member
  • Posts

    224
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by pigr8

  1. so i tried to passthough the iGPU in a w10 vm, the hypervisor is the same ofc.. quicksync works just fine on windows, it's correctly detected and used by handbrake [17:15:25] CPU: Intel(R) Core(TM) i3-10100T CPU @ 3.00GHz [17:15:25] - Intel microarchitecture Comet Lake [17:15:25] - logical processor count: 1 [17:15:25] Intel Quick Sync Video support: yes, gpu list: 0 [17:15:25] Intel Quick Sync Video integrated adapter with index 0 [17:15:25] - Intel Media SDK hardware: API 1.35 (minimum: 1.3) [17:15:25] - Decode support: h264 hevc (8bit: yes, 10bit: yes) [17:15:25] - H.264 encoder: yes [17:15:25] - preferred implementation: hardware (1) via D3D11 [17:15:25] - capabilities (hardware): breftype icq+la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice [17:15:25] - H.265 encoder: yes (8bit: yes, 10bit: yes) [17:15:25] - preferred implementation: hardware (1) via D3D11 [17:15:25] - capabilities (hardware): bpyramid icq vsinfo opt1 so it must be something wrong with the backport, maybe not working as it should, i'm gonna try to spinup an ubuntu vm and check with the newer kernel if quicksync works. bummer.
  2. @fbelavenuto the loader boot gives me "ip: can't find device eth0" error in the first row (before /dev/sda SATA DOM), i cannot upload a screenshot, doing from terminal "ip a" shows me the device as eno1677677924 and not eth0, testing in a VM on ESXi, vmxnet3 or e1000e no changes.. maybe you could implement in grub_cmd_line the net.ifnames and biosdevname to avoid that error and always have eth0-1-2 names?
  3. i tested the disabled ds1520+ also (geminilake dt), works fine
  4. i think i got the same issue in the past, could be the apollolake i915 that is big? or not? i think i overcame that problem removing that tgz from p3, but i'm not sure what i did actually.
  5. yes it's VMWare, mm i have to research on those drivers you mention, @IG-88 were those drivers yours?
  6. tested on a test vm with ARPL 0.3a8 DS920+ build, install seems to work, ramdisk patch misses the new build but it seems that should work when added the correct version. avoid RC version for production.
  7. btw same happens on build DS918+, not only DS920+ after doing "cat /sys/kernel/debug/dri/0/i915_frequency_info" dmesg reports this, dunno if it's relevant. [ 528.649500] Module [i915] is removed. [ 528.662672] Module [video] is removed. [ 528.671464] Module [backlight] is removed. [ 528.680441] Module [iosf_mbi] is removed. [ 528.690424] Module [drm_kms_helper] is removed. [ 528.700498] Module [drm] is removed. [ 528.710492] Module [i2c_algo_bit] is removed. [ 528.720401] Module [fb] is removed. [ 537.772134] i915 0000:0b:00.0: enabling device (0000 -> 0003) [ 537.779777] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining [ 537.785354] Failed to add WC MTRR for [00000000d0000000-00000000dfffffff]; performance may suffer. [ 537.792724] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 537.795749] [drm] Driver supports precise vblank timestamp query. [ 537.797809] i915 0000:0b:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment) [ 537.800813] [drm] Failed to find VBIOS tables (VBT) [ 537.802469] vgaarb: device changed decodes: PCI:0000:0b:00.0,olddecodes=io+mem,decodes=none:owns=none [ 537.806473] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [ 537.810299] [drm] Initialized i915 1.6.0 20171222 for 0000:0b:00.0 on minor 0 [ 537.831388] [drm] Cannot find any crtc or sizes [ 537.832578] i915 0000:0b:00.0: fb0: inteldrmfb frame buffer device [ 560.067392] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [ 560.073035] IP: [<ffffffffa0d7ab11>] drm_debugfs_open+0x11/0x20 [drm] [ 560.077512] PGD 0 [ 560.079047] Oops: 0000 [#1] SMP [ 560.081489] Modules linked in: i915(E) video(E) backlight(E) iosf_mbi(E) drm_kms_helper(E) drm(E) i2c_algo_bit(E) fb(E) fuse 8021q vhost_scsi(O) vhost(O) tcm_loop(O) iscsi_target_mod(O) target_core_user(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) udf isofs loop synoacl_vfs(PO) btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq aesni_intel glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm_panel_orientation_quirks fbdev uhci_hcd r8168(O) e1000e(O) sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus 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 ip_tunnel zram sha256_generic synorbd(O) synofsbd(O) igb(O) etxhci_hcd vmxnet3(OE) vmw_vmci(E) button usb_storage xhci_pci xhci_hcd ehci_pci ehci_hcd usbcore usb_common [last unloaded: fb] [ 560.122073] CPU: 3 PID: 19503 Comm: cat Tainted: P OE 4.4.180+ #42661 [ 560.123326] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 [ 560.125104] task: ffff88008477a640 ti: ffff880167164000 task.ti: ffff880167164000 [ 560.126366] RIP: 0010:[<ffffffffa0d7ab11>] [<ffffffffa0d7ab11>] drm_debugfs_open+0x11/0x20 [drm] [ 560.127784] RSP: 0018:ffff880167167c80 EFLAGS: 00010286 [ 560.128592] RAX: ffff88016fc28780 RBX: ffff88016fc28780 RCX: ffff88016f7564a0 [ 560.129709] RDX: 0000000000000000 RSI: ffff88016fc28780 RDI: ffff88016fc28780 [ 560.130825] RBP: ffff880167167c80 R08: 0000000000000000 R09: 0000000000000000 [ 560.131950] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88004a62e980 [ 560.133043] R13: ffffffffa0d7ab00 R14: 0000000000000000 R15: ffff88016fc28790 [ 560.134128] FS: 00007fd69b304500(0000) GS:ffff880172d80000(0000) knlGS:0000000000000000 [ 560.135383] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 560.136278] CR2: 0000000000000008 CR3: 0000000168940000 CR4: 00000000003606f0 [ 560.137380] Stack: [ 560.137695] ffff880167167cc0 ffffffff81188f91 ffff880081409cc0 ffff88004db71cc0 [ 560.139008] ffff88016fc28780 ffff880167167efc ffff880085d81a80 ffff880167167dc0 [ 560.140229] ffff880167167ce8 ffffffff8118a63b 0000000000008000 0000000000008000 [ 560.141467] Call Trace: [ 560.141856] [<ffffffff81188f91>] do_dentry_open+0x1d1/0x350 [ 560.142755] [<ffffffff8118a63b>] vfs_open+0x5b/0x90 [ 560.143520] [<ffffffff8119f578>] path_openat+0x328/0x1bd0 [ 560.144370] [<ffffffff8113841a>] ? __alloc_pages_nodemask+0x11a/0xb50 [ 560.145368] [<ffffffff811a2b3e>] do_filp_open+0x7e/0xc0 [ 560.146186] [<ffffffff8118855c>] do_sys_open+0x17c/0x210 [ 560.147082] [<ffffffff8118a8ef>] SyS_openat+0xf/0x20 [ 560.147864] [<ffffffff8157b7ca>] entry_SYSCALL_64_fastpath+0x1e/0x8e [ 560.148875] Code: 5d 5d c3 49 8d 7d 00 e8 de f8 ff ff 49 8b 85 e8 01 00 00 eb d2 0f 1f 44 00 00 55 48 8d 06 48 8b 97 80 02 00 00 48 89 e5 48 89 c7 <48> 8b 4a 08 48 8b 71 08 e8 d2 d3 43 e0 5d c3 55 48 8d 06 48 c7 [ 560.153352] RIP [<ffffffffa0d7ab11>] drm_debugfs_open+0x11/0x20 [drm] [ 560.154400] RSP <ffff880167167c80> [ 560.154958] CR2: 0000000000000008 [ 560.155491] ---[ end trace 346afd34bbcba1e1 ]--- [ 560.156289] ------------[ cut here ]------------
  8. @blackmanga after @FalseMetal got in touch with me i tested the i915 backported drivers and i have the same issues that he has, the igpu sais "killed".. i'm confident i got it working in the past but since i have a lot of test bench i cant really remember it this was working or not, damn. z490-i + i3-10100T, esxi, gpu in passthrough, in dsm it's recognized as "0000:0b:00.0 Class 0300: Device 8086:9bc8 (rev 03)", no /dev/dri on a stock dsm 7.1 install.. after copying the firmware root@TestStation:/usr/lib/firmware/i915# ls -al total 420 drwxr-xr-x 2 root root 4096 Aug 10 08:22 . drwxr-xr-x 3 root root 4096 Aug 9 20:02 .. -rwxr-xr-x 1 root root 8380 Oct 7 2021 bxt_dmc_ver1_07.bin -rwxr-xr-x 1 root root 8800 Oct 7 2021 glk_dmc_ver1_04.bin -rwxr-xr-x 1 root root 8840 Aug 10 08:21 kbl_dmc_ver1_04.bin -rwxr-xr-x 1 root root 147776 Aug 10 08:22 kbl_guc_ver9_39.bin -rwxr-xr-x 1 root root 218688 Aug 10 08:22 kbl_huc_ver02_00_1810.bin and doing the rm_modules and in_modules script /dev/dri appears root@TestStation:/volume1/storage/i915# sh rm_modules.sh root@TestStation:/volume1/storage/i915# sh in_modules.sh root@TestStation:/volume1/storage/i915# cd /dev/dri root@TestStation:/dev/dri# ls card0 renderD128 root@TestStation:/$ tail -f /var/log/messages 2022-08-10T08:18:53+02:00 TestStation synodbudupdate[18770]: update.cpp:299 Fix syno-abuser-blocklist completed and succeed 2022-08-10T08:19:00+02:00 TestStation logger[20372]: version_change hook event: syno-abuser-blocklist installed successfully. 2022-08-10T08:19:02+02:00 TestStation synoindex[20465]: synoindex.cpp:421 Synoindex reindex by synoindex binary, newpath: media 2022-08-10T08:19:03+02:00 TestStation mediaserver.sh[20468]: Re-index triggered, cmd [/usr/syno/bin/synoindex -R media -P MediaIndex] 2022-08-10T08:19:45+02:00 TestStation kernel: [44277.796941] synobios get empty ttyS current 2022-08-10T08:20:46+02:00 TestStation kernel: [44338.596761] synobios get empty ttyS current 2022-08-10T08:21:47+02:00 TestStation kernel: [44399.389364] synobios get empty ttyS current 2022-08-10T08:22:48+02:00 TestStation kernel: [44460.236546] synobios get empty ttyS current 2022-08-10T08:23:48+02:00 TestStation kernel: [44521.074549] synobios get empty ttyS current 2022-08-10T08:24:49+02:00 TestStation kernel: [44581.902709] synobios get empty ttyS current 2022-08-10T08:25:50+02:00 TestStation kernel: [44642.725378] synobios get empty ttyS current 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.664222] Module [i915] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.672351] Module [video] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.681101] Module [backlight] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.690095] Module [iosf_mbi] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.701156] Module [drm_kms_helper] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.710137] Module [drm] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.718138] Module [i2c_algo_bit] is removed. 2022-08-10T08:25:55+02:00 TestStation kernel: [44647.727103] Module [fb] is removed. 2022-08-10T08:26:05+02:00 TestStation kernel: [44657.346787] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining 2022-08-10T08:26:05+02:00 TestStation kernel: [44657.348107] Failed to add WC MTRR for [00000000d0000000-00000000dfffffff]; performance may suffer. 2022-08-10T08:26:05+02:00 TestStation kernel: [44657.369102] [drm:gen9_set_dc_state [i915]] *ERROR* DC state mismatch (0x0 -> 0x2) [44647.664222] Module [i915] is removed. [44647.672351] Module [video] is removed. [44647.681101] Module [backlight] is removed. [44647.690095] Module [iosf_mbi] is removed. [44647.701156] Module [drm_kms_helper] is removed. [44647.710137] Module [drm] is removed. [44647.718138] Module [i2c_algo_bit] is removed. [44647.727103] Module [fb] is removed. [44657.344563] i915 0000:0b:00.0: enabling device (0000 -> 0003) [44657.346787] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining [44657.348107] Failed to add WC MTRR for [00000000d0000000-00000000dfffffff]; performance may suffer. [44657.352767] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [44657.356851] [drm] Driver supports precise vblank timestamp query. [44657.360460] i915 0000:0b:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment) [44657.365930] [drm] Failed to find VBIOS tables (VBT) [44657.369102] [drm:gen9_set_dc_state [i915]] *ERROR* DC state mismatch (0x0 -> 0x2) [44657.373895] vgaarb: device changed decodes: PCI:0000:0b:00.0,olddecodes=io+mem,decodes=none:owns=none [44657.380718] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [44657.386000] [drm] Initialized i915 1.6.0 20171222 for 0000:0b:00.0 on minor 0 [44657.408383] [drm] Cannot find any crtc or sizes [44657.410220] i915 0000:0b:00.0: fb0: inteldrmfb frame buffer device root@TestStation:/dev/dri# cat /sys/kernel/debug/dri/0/i915_frequency_info Killed any idea on why this is happening?
  9. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1-42661 Update 3 - Loader version and model: Automated Redpill Loader 0.3a7 DS920+ - Using custom extra.lzma: NO - Installation type: VMWare ESXi 7.03f @ custom Z490-i build (i3-10100T) - Additional comments: Upgraded: via GUI, no fancy stuff to do. Everything works great, CometLake Sata and iGPU in passthrough for real smart data and transcoding.
  10. why do you prefer usb loader instead of satadom? so it’s working now?
  11. are the disk recognized? check the log about that, and do a fdisk -L to see what is not correct you should always put the hardware you are using, the enviroment (baremetal or vm) and the logs.
  12. i finally swapped my old production VM to the new one on a different host, and after testing a lot i can say that it's very impressive and stable. latest version of ARPL 0.3a6, DS920+ build (with my real SN/MACs applied and working), ESXi 7.0U3f, Asus z490i + i3 8c 10th gen cpu (Comet Lake), iGPU (UHD630) in passthough with the backported i915 kernel modules working (hvec hdr and tonemapping works), Intel Sata Controller is also in passthough so all the disks are natively handled with all the real smart data.. perks, the disks start from the first sata port so no more /dev/sda reservation problem i had with the LSI in passthrough. great work with ARPL, a really good loader.
  13. works for me with esxi 7.0U3f and DS920+ build
  14. great, hope someone else could try and see if it works for them also, i just made a lot of copy paste hacks without knowing what I'm doing ahaha
  15. @fbelavenuto do you have an how-to add a custom external addon download? i would like to create an optional addon to add the backported i915 drivers for 10th gen, i saw the structure of /mnt/p3/addons but it's not clear what arpl is expecting. my idea is to add a custom addon (or maybe you could add it into your official repo) based on the work of @blackmanga backported drivers from here.. his readme sais to put the missing *.bin from the linux kernel to /usr/lib/firmware/i915 and his drivers in /usr/lib/modules to overwrite the stock ones.. could be done as a geminilake only platform addon, what do you think?
  16. if you need testing i can provide support with esxi 7u3
  17. it would be cool to being able to add custom user modules on loader build, like if someone wants to add the extra Intel GPU ko in the tgz. well it can be done before building via cli easily tho.
  18. i think I tested vmxnet3 and was not working for me also but I cannot confirm i have to check
  19. finally works! v41 loaded and no more want idx spam! btw, doing module update from the update menu breaks intel e1000e.
  20. ds3622xs+, i don't know why it's doing that.. i even copied the tcrp file where it boots v41 in arpl and rebooted, the same file loads v22.. i have no idea why it is doing that. maybe it's loaded earlier? pocopico suggested that but I have no clue..
  21. tested 0.3a3, still does not load the 41.xx version of the .ko, everything works but this timout stuff slowers a lot boot time and i did not yet notice other problems. wierd
  22. link works, you have to be logged in on github to download it
  23. so you think is a loading priority problem? well i switched the stock DSM ko with your compiled ad after a reboot it still loads 22.xx with the want_idx error spam, out of ideas
  24. @fbelavenuto i tried to manually copy the new mpt3sas.ko in /usr/lib/modules and reboot but it still shows ver 22....... i dont know why it does not load version 41, it should... @pocopico do you know why in tcrp it loads correctly the mpt3sas.ko v41 you compiled and in arpl no? even if the file is the same? is it missing something else? i dont think so but..
×
×
  • Create New...