Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

16 hours ago, p33ps said:

 

I'm afraid that DS3615xs and DS3617xs won't be able to use the "face recognition" feature, according to this Synology article:

 

https://kb.synology.com/en-uk/DSM/tutorial/Which_Synology_NAS_models_support_the_facial_recognition_feature_on_Synology_Photos

 

There is only DS918+ model listed. 

I'm not sure about that. Currently I'm working on DSM 6.2.4 from ds3615xs and face recognition is working very well.

Video transcoding is not working because I couldn't find valid SN and MAC for ds3615xs.

 

Link to comment
Share on other sites

14 hours ago, nemesis122 said:

Which  VID and PID i have to set when i load/install in VMM VirtualmaschineManager ?

 

If you're running QEmu-based virtualization (e.g. Proxmox or VirtualBox) set vid to 0x46f4 and pid to 0x0001

If you're running SATA-based boot you can skip vid and pid fields (just remove them)

Link to comment
Share on other sites

may be @ThorGroup could enhance first topic with some extra info ?

 

link to latest version of haydibe docker image ?

 

how to get ride of the blank info center

sudo su - root

sed -i 's/supportsystemperature="yes"/supportsystemperature="no"/g' /etc.defaults/synoinfo.conf
sed -i 's/supportsystempwarning="yes"/supportsystempwarning="no"/g' /etc.defaults/synoinfo.conf

 

acpi throttle

sudo su - root
vi /usr/local/etc/rc.d/S99Powersaving.sh and insert according to number of core
 
Script-content:

#!/bin/sh

echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

chmod +x /usr/local/etc/rc.d/S99Powersaving.sh
sh /usr/local/etc/rc.d/S99Powersaving.sh

 

  • Like 4
Link to comment
Share on other sites

16 часов назад, imdgg сказал:

 

1.open ssh service

2.connect to your dsm

3.mount boot partion. Just like this: mount /dev/vda1 /mnt  #my device is /dev/vda1

4.vim /mnt/boot/grub/grub.cfg , search "sn",change the serial number

 

my dsm 7.0.1 runs on qnap 453b-mini

 

I forget to shutdown VM, in boot.cfg everything ok, now all services work fine!

Link to comment
Share on other sites

53 minutes ago, abesus said:

I'm not sure about that. Currently I'm working on DSM 6.2.4 from ds3615xs and face recognition is working very well.

Video transcoding is not working because I couldn't find valid SN and MAC for ds3615xs.

 

 

Synology says that the "face detection" feature which is implemented in lower versions (<7.0) for Moments app is different that the new one, which needs higher hardware to run smoothly. I hope not to affect to xpenology newer versions, but my current experience with 7.0 is quite bad. It consumes too many resources and does not detect any face after hours.

Link to comment
Share on other sites

4 hours ago, snowfox said:

How can I solve this problem?

ub1.jpg

The error message says "curl: command not found". Install the curl packge of your distro :)

The same is true if "jq" or "realpath" are missing on your system.

 

Probably I should add a senity checks that indicates when required commands are missing. 

 

Update: I see it was answered above.

Edited by haydibe
Link to comment
Share on other sites

5 minutes ago, haydibe said:

The error message says "curl: command not found". Install the curl packge of your distro :)

The same is true if "jq" or "realpath" are missing on your system.

 

Probably I should add a senity checks that indicates when required commands are missing. 

 

Update: I see it was answered above.

 

thank you 

Link to comment
Share on other sites

3 hours ago, titoum said:

acpi throttle


sudo su - root
vi /usr/local/etc/rc.d/S99Powersaving.sh and insert according to number of core
 
Script-content:

#!/bin/sh

echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo powersave > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

chmod +x /usr/local/etc/rc.d/S99Powersaving.sh
sh /usr/local/etc/rc.d/S99Powersaving.sh

 

It doesn't work on my setup. Currently DS918+(cpu xeon, motherboard MSI Z97I GAMING ACK). I've got such error:

 

-ash: echo: write error: Invalid argument

 

I cannot write to this file even using vi.

Am i doing something wrong?

 

 

Link to comment
Share on other sites

Are you sure that you executed `sudo su - root` to become root before the vi line?

 

Instead you could use `sudo -i` to become root.

 

Refactored to by dynamic:

#!/bin/sh
for cpu in /sys/devices/system/cpu/cpu[0-9]*; do
    echo powersave > ${cpu}/cpufreq/scaling_governor
done

 

Link to comment
Share on other sites

I have made progress in being able to get past the SATA disk error so thanks to those prior forum members who have helped so far.  I now get stuck at the 55 / 56% mark as others have when trying to install the pat file onto a new baremetal install (Dell Optiplex 9020 i5 4570 installing DS918+ 42214.pat)

 

I recall seeing something about this on prior pages but can anyone point me in the right direction to try not to read 45 pages of history?  A search on 55% / 56% didn't throw anything up for me.

 

Thanks

Link to comment
Share on other sites

7 minutes ago, scoobdriver said:

@WiteWulf Did you happen to try the same with the on onboard NIC ? 
when I get home in a few days I will try on mine if not. (Will try with a ‘standard’ build. And also with kg3.ko added. 

I haven't, but the comments on the previous page from MastaG suggested it was failing for them, and flyride confirmed that the drivers for the onboard NIC were included as an addition in Jun's bootloader and are not included at present in redpill. There was mention of adding a "tg3" driver to redpill, but I've not found any more information on that (it seems the forum search doesn't like such small search terms).

Edited by WiteWulf
Link to comment
Share on other sites

The kernel keeps reporting this information. What action should I take?

 

[80085.526427] <redpill/rtc_proxy.c:226> Mocking auto-power SET on RTC
[80085.532878] BUG: unable to handle kernel NULL pointer dereference at           (null)
[80085.540936] IP: [<ffffffff812fd1e6>] memcpy_erms+0x6/0x10
[80085.546473] PGD 363fb9067 PUD 3d1d07067 PMD 0
[80085.551076] Oops: 0000 [#713] SMP
[80085.554569] Modules linked in: fuse nfnetlink pci_stub vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_net(O) kvm_intel kvm irqbypass xt_ipvs ip_vs_rr ip_vs xt_mark br_netfilter bridge stp aufs macvlan veth xt_addrtype tun cmac ctr ccm ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat nf_nat_redirect xt_policy xfrm6_mode_transport xfrm4_mode_transport xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm6_mode_beet xfrm4_mode_beet deflate authencesn ipcomp6 ipcomp xfrm6_tunnel xfrm4_tunnel tunnel6 esp6 esp4 ah6 ah4 xfrm_ipcomp af_key xfrm_user xfrm_algo l2tp_ppp l2tp_core ppp_deflate bsd_comp ppp_mppe echainiv xt_TCPMSS iptable_mangle pppox ppp_async ppp_generic slhc 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)
[80085.628492]  target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) udf isofs loop nfsv3 nfs quota_v2 quota_tree synoacl_vfs(PO) iptable_nat nf_nat_ipv4 nf_nat raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xt_conntrack xt_mac xt_geoip(O) compat_xtables(O) nf_conntrack_ipv6 ip6table_filter ip6_tables xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables x_tables nfsd btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq lockd grace rpcsec_gss_krb5 auth_rpcgss sunrpc aesni_intel glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks
[80085.702288]  iosf_mbi fb fbdev video backlight button uhci_hcd ehci_pci ehci_hcd r8168(O) i2c_algo_bit openvswitch gre nf_defrag_ipv6 nf_conntrack igb(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 sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel zram ip_tunnel etxhci_hcd usb_storage xhci_pci xhci_hcd usbcore usb_common redpill(OE) [last unloaded: apollolake_synobios]
[80085.760520] CPU: 3 PID: 4856 Comm: scemd Tainted: P      D    OE   4.4.180+ #42214
[80085.768258] Hardware name: System manufacturer System Product Name/B150M-PLUS, BIOS 3806 05/18/2018
[80085.777496] task: ffff88004055d280 ti: ffff88012a65c000 task.ti: ffff88012a65c000
[80085.785166] RIP: 0010:[<ffffffff812fd1e6>]  [<ffffffff812fd1e6>] memcpy_erms+0x6/0x10
[80085.793225] RSP: 0018:ffff88012a65fbb0  EFLAGS: 00010246
[80085.798660] RAX: ffff88012a65fbf0 RBX: ffffffffffffffff RCX: 0000000000000134
[80085.805956] RDX: 0000000000000134 RSI: 0000000000000000 RDI: ffff88012a65fbf0
[80085.813252] RBP: ffff88012a65fbc0 R08: 000000000000000a R09: 00000000000085d6
[80085.820550] R10: 0000000000000005 R11: ffffffff819fe16d R12: ffff88012a65fbf0
[80085.827831] R13: ffff8800abd51a40 R14: ffff88042027c048 R15: ffff8800abd51a40
[80085.835135] FS:  00007f5fe7413700(0000) GS:ffff880433d80000(0000) knlGS:0000000000000000
[80085.843377] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[80085.849279] CR2: 0000000000000000 CR3: 0000000104946000 CR4: 00000000003606f0
[80085.856569] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[80085.863891] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[80085.871196] Stack:
[80085.873241]  ffffffffa000875c 00007f5fe7412320 ffff88012a65fe88 ffffffffa06a452c
[80085.880894]  ffff88012a65fc68 ffff88012a65fc60 ffff88012a65fcf0 0000000000000001
[80085.888512]  0000000100000001 00000000007f1700 0000000000000000 0000000000000000
[80085.896131] Call Trace:
[80085.898639]  [<ffffffffa000875c>] ? rtc_proxy_set_auto_power_on+0x70/0x76 [redpill]
[80085.906437]  [<ffffffffa06a452c>] synobios_ioctl+0x54c/0x1e50 [apollolake_synobios]
[80085.914252]  [<ffffffff81131bd9>] ? unlock_page+0x59/0x60
[80085.919748]  [<ffffffff8115e837>] ? do_wp_page+0x287/0x650
[80085.925356]  [<ffffffff8121ecf9>] ? ext4_getattr+0x19/0x90
[80085.930980]  [<ffffffff81194a20>] ? cp_new_stat+0x110/0x120
[80085.936674]  [<ffffffff811a70d2>] do_vfs_ioctl+0x4d2/0x960
[80085.942248]  [<ffffffff811a7601>] SyS_ioctl+0xa1/0xb0
[80085.947395]  [<ffffffff81579c4a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
[80085.953945] Code: 90 90 90 90 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 <f3> a4 c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38
[80085.974293] RIP  [<ffffffff812fd1e6>] memcpy_erms+0x6/0x10
[80085.979909]  RSP <ffff88012a65fbb0>
[80085.983480] CR2: 0000000000000000
[80085.986852] ---[ end trace 487f34b257519703 ]---

 

Link to comment
Share on other sites

35 minutes ago, haydibe said:

Are you sure that you executed `sudo su - root` to become root before the vi line?

 

Instead you could use `sudo -i` to become root.

 

Refactored to by dynamic:


#!/bin/sh
for cpu in /sys/devices/system/cpu/cpu[0-9]*; do
    echo powersave > ${cpu}/cpufreq/scaling_governor
done

 

Yes. I'm sure:

 

Quote

root@DS:~# echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
-ash: echo: write error: Invalid argument

 

Link to comment
Share on other sites

Just migrated to 7.0.1-RC1 on my baremetal HP Gen8 Microserver with NC360T NIC. The upgrade/migration went very smoothly apart from a similar issue I had going from 6.2.3 to 6.2.4 in that the connected NIC went back to DHCP and I had to set it up again with it's static details. Everything seems good so far. Now I wonder if that influxdb docker still crashes it 🤔🤣

Edited by WiteWulf
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...