Leaderboard

I have XPEnology experience since version 5.x on HP Microserver Gen7. I managed to compile 7.0.1-42214 somehow following a step-by-step-guide i found somewhere on the internet with maybe the third Linux distrubution or so. Linux is freaking crazy. It is working somehow, but compared to 6.2.3 it comes with limitations. These are my results on HP N54L: Hardware: HP Microserver Gen7, previously running fine with 6.2.3 DSM Version: DS3615xs 7.0.1-42214 Bootstick created using the toolchain with VID, PID, MAC, Ser. No. updated Booting fine, VGA output stops at 'Booting the kernel', which seems to be OK No connection using internal LAN -> added Intel PRO/1000 PT Machine now appeared in Synology Assistant as migratable I chose not to keep my settings for having a clean install of DSM DSM installed without any hick-ups Status: - Tab General in Info Center is blank - Volume and shares from 6.2.3 are still there - Volume manager asked for data scrubbing, which was successful. - WOL works using the usual shutdown script - Powersaving script fails with invalid parameter or so - New script (note there are 2 lines for the 2 cpu cores): #!/bin/sh echo "powersave" | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo "powersave" | sudo tee /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor - Note: scaling governor 'conservative' is not supported! Only performance and powersave This means 1500 MHZ (N40L) or 2200 MHz (N54L) constantly by default This is a kernel limitation as far as I understand, so no easy workaround! - but adjusting the frequency works! Instead of a scaling governor you might want to chose a fixed frequency between min. and max. frequency See supported frequencies under /sys/devices/system/cpu/cpu0/cpufreq/ Example for 800 MHz (same as governor 'powersave'): echo 800000 | sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq Do the same for cpu1 - HDD sleep does not work, even with modified scemd.conf :-(( - No idea if face recognition or docker are working as I only use it as a file or rsync server - packages.synocommunity.com could be added, this failed on my 6.2.3 install Again: I am not an expert. Opening the Linux terminal is like opening the gates to hell for me. My Linux is even much worse that my French. And I speak 4 words in French fluently without knowing their meaning. Conclusion: Start adding Intel PRO/1000 PT on bare metal before trying anything else. For now I would recommend to stay with 6.2.3 on HP Microserver, because: - Tab General in Info Center stays blank - No HDD hibernation - No dynamic CPU frequency

Lets Encrypt's root certificate expired on October 1, 2021, which causes the cert renewal or creation to fail with a message "No response from destination server. Please try again later." To Fix follow the following instruction which worked for me on my Xpenology box running DSM 6.2.2-24922 1. Download root cert from LetsEncrypt website: https://letsencrypt.org/certificates/ a. Download Active Root Cert “Pem” file, b. Open with text editor, and copy cert 2. Log into Synolog box via ssh 3. Back up CA cert file: cp /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt.ORIG 4. Edit CA cert file : sudo vi /etc/ssl/certs/ca-certificates.crt 5. “ESC” “G” to go to end of file 6. “o” to insert new line 7. Paste new cert into file. 8. “ESC”, “w”, “q”, “!” to save and close. This will update the root CA cert and should allow you to now install or renew Lets Encrypt certificates

9p worked well. Please check my post in another thread. Tapatalk を使用して私の ELS-NX9 から送信

You can ignore the message about zImage. Redpill just mentions that it doesn't know how to handle that and actually shouldn't care about that. Check messages on ttyS0 as well.

I do this command and it's solved for me this will reboot your dsm sudo -i && cp /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt.ORIG && curl -k "https://letsencrypt.org/certs/isrgrootx1.pem" >> /etc/ssl/certs/ca-certificates.crt && reboot from this post

I think this is where it would be ideal if some sort of tutorial could be drafted for the masses. I know that RP is still classed as Alpha and in theory for people with some experience, but I think that if there was a guide that could be followed then people who are willing to give it a go can do so. This would reduce the potential of image sharing. Of course any guide would be up to the end user to follow and if they didn't get it right then there could be no comeback. We should all be adult enough to run with the consequences in the event something went awry. Just my $0.02 worth.

hello, the api url change try this (it's working for me) https://your-ip:5001/webapi/auth.cgi?api=SYNO.API.Auth&version=3&method=login&account=admin&passwd=your_admin_password&format= cookie the other url (for activation) not change https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" regards

Just with one command and everything will be done for you... Remind: Your machine will restart after executing this command sudo -i && cp /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt.ORIG && curl -k "https://letsencrypt.org/certs/isrgrootx1.pem" >> /etc/ssl/certs/ca-certificates.crt && reboot

Hello, Il y as un post qui bouge pas mal ici =>

So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved.