Jump to content
XPEnology Community

superma87

Transition Member
  • Posts

    12
  • Joined

  • Last visited

Everything posted by superma87

  1. TDP is not power consumption, so @dimakv2014considerations are useless. Plus, newer CPUs have a way better power management than old ones or low power ones(those does not have the need to cut power even more) Please refer to this video to see what really matters about power consumption https://www.youtube.com/watch?v=MucGkPUMjNo
  2. Just mod your bios dump it and unlock CSM menu then flash it back and reset to default values
  3. injecting this code with DSM 7 cause some strange logs output 2022-02-05T20:11:19+01:00 terranas scemd[10820]: fs_btrfs_metadata_usage_query.c:125 Failed to check the btrfs metadata usage of volume [/volume1]. 2022-02-05T20:11:25+01:00 terranas scemd[10820]: fs_btrfs_metadata_usage_query.c:86 Failed to read result of getting btrfs tree info, err No such file or directory
  4. FIY just change // Sanity check that this is the 8772 assert(ioread(0x20) == 0x87); assert(ioread(0x21) == 0x72); to // Sanity check that this is the 8613 assert(ioread(0x20) == 0x86); assert(ioread(0x21) == 0x13); to make it working
  5. that's just and error from the script, it's very basic it fails very easily if you know you system just put the sata mappings inside the file and you are good nvme disk recognition has nothing in common with that part of the script just connect it and if you happen to boot to a working system, follow my last post to get info on how to use nvme on dsm
  6. this thread has a lot of redundad information: someone there got cache working too on dsm 7 short answer is patch the libnvme library with you pci id and copy it back to your system another Chinese post with "detailed" instructions, just translate it https://wp.gxnas.com/10930.html (feel free to test it before messing your system and/or your data)
  7. removing the nvme drive fixes the satamap recognition, however i got it working even without removing the nvme drive, the config should always be the same that the working satamap generates
  8. I'm still learning how this stuff work but i think tat nvme disk are not detected since they are not attached to a sata controller of any type but to the pci express
  9. Hi, I got the setup working on a Zotac CI323 mini box with just 1 disk Now I'm trying to get it to work on a more powerful bare-metal system motherboard is a ASUS P11C-I, it has intel C242 chipset and has 1 mini-SAS connector to 4 SATA disks and 2 more SATA ports, one of them got disabled if i connect an NVMe disk on the 2242 onboard connector. 2x intel GB ports Nothing fancy, it should work no problem and I found a couple of success reports around the forum the satamap function however does not works as expected ./rploader.sh satamap now HBA: 00:17.0 Disks : 6 ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory HBA: 00:1d.2 Disks : 0 ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory SataPortMap=60 DiskIdxMap=0001 some one has hints on that? even configuring it manually would be ok for me! mode info on lsscsi command that satamap uses, that should be the 5(4 used) disks + 1 nvme setup that i have now: lsscsi -Hv |grep pci |grep -v usb device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0 device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1 device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2 device dir: /sys/devices/pci0000:00/0000:00:17.0/ata4/host3 device dir: /sys/devices/pci0000:00/0000:00:17.0/ata5/host4 device dir: /sys/devices/pci0000:00/0000:00:17.0/ata6/host5 device dir: /sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0
  10. No problem for me. Virtual Xpenology(proxmox) Jun loader 1.02b
  11. yeah, managed to do that. The sources came from https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/15152branch/ I downloaded 15152 branch because matches the uname -a output of the kernel I just downloaded linux source, extracted to a folder and followed your procedure Dont know why this produces a 3.10.77 modules. No other sources involved This is a summary of my procedure: my goal is to use virtio for network and for disk images(not real disk or HBA, just virtual qcow2/raw disk) 1) Using Jun's v1.02b loader on a proxmox virtual machine with UEFI 2) img file is loaded as a usb stick, network is e1000 and the test disk is a sata(virtual) disk 3) Downloaded sources 4) Installed dependencies 5) Copied .config in kernel root 6) in menuconfig I just added virtio stuff as M (virtio-scsi, virtio-net, virtio-blk areas) 7) compiled modules and extracted like 7 .ko files to a shared folder -a---- 22/09/2017 16:44 9392 virtio.ko -a---- 22/09/2017 16:44 13400 virtio_balloon.ko -a---- 22/09/2017 16:50 21016 virtio_blk.ko -a---- 22/09/2017 16:44 13536 virtio_mmio.ko -a---- 22/09/2017 17:31 33928 virtio_net.ko -a---- 22/09/2017 16:43 15536 virtio_pci.ko -a---- 22/09/2017 16:44 15160 virtio_ring.ko 8) my first approach was to integrate them in extra.lzma but I was facing some reboot loop issues and the testing was a little difficult due to repack procedure 9) so I just copied .ko from chroot environment to non chroot environment with root privileges 10) tried insmod to .ko file and i have the "wrong format" error. 11) usimg modinfo <module>.ko i get 3.10.77 kernel 12) using modinfo on, let's say, e1000.ko i get 3.10.102 kernel I cant use 3617 variant since there arent debian-chroot and/or python extra packages on this architecture Thanks
  12. Hi @IG-88 I followed the procedure to integrate virtio drivers into a VM installation on proxmox but I have the following problems: 1) linux-kernel-devel does not exist in debian repository. What do you refer to? Kernel headera? 3.10 are not in repos. 2) Currently, any kernel between the last builds I tried produces kernel modules for kernl 3.10.77 instead of kernel 3.10.102. I use Jun's v1.02b loader with this kernel: Linux dsm-3.10.102 # 15152 SMP Thu Jul 13 04:20:20 CST 2017 x86_64 GNU / Linux synology_broadwell_3617xs I've tried both variant 3617 and variant 3615 but there are no changes. On 3615 sources include/linux/synobios.h was missing. Is there anything that I'm missing or is there a misalignment between the information? Thank you
×
×
  • Create New...