pocopico

Yes GUI setup does not work for some reason. Please after loader rtc-cmod.ko try running : $ sudo sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" $ sudo sh -c "echo `date '+%s' -d '+ 5 minutes'` > /sys/class/rtc/rtc0/wakealarm" Then shutdown and wait 5 minutes for startup.

Can you try loading the attached with insmod ./rtc-cmos.ko and send me another round of the output of the above mentioned commands ? EDIT : even with the rtc-cmos.ko you cannot schedule the power up. Maybe you can test with the below after loading the module. : https://www.linux.com/training-tutorials/wake-linux-rtc-alarm-clock/ This worked on my case on a physical DVA1622 that the scheduled power on is not working. rtc-cmos.ko

So i guess this is a system that scheduled startup/shutdown is working right ?

We have notice that buildroot kexec causes kernel panic on some systems e.g. Microserver N54L which is also AMD based. Maybe you are also falling into the same issue. If thats true, then USB boot option is the only available solution. TCRP Friend , JUN mode and ARPL will not work as they are causing KP.

Yes, on my physical system the shutdown/startup works out of the box. I assume its something related to BIOS ACPI settings and/or capabilities. There are offcourse PCI devices that will break this if they do not support ACPI shutdown. On my system that power scheduling works the following are true : sh-4.4# cat /sys/class/rtc/rtc0/uevent MAJOR=254 MINOR=0 DEVNAME=rtc0 PHYSDEVPATH=/devices/pnp0/00:02 PHYSDEVBUS=pnp PHYSDEVDRIVER=rtc_cmos sh-4.4# ls /sys/class/rtc/ rtc0 sh-4.4# cat /proc/driver/rtc rtc_time : 09:09:33 rtc_date : 2022-10-23 alrm_time : 07:00:00 alrm_date : 2022-10-24 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay sh-4.4# cat /proc/acpi/wakeup Device S-state Status Sysfs node C0B0 S5 *disabled pci:0000:00:1e.0 C108 S3 *enabled pci:0000:00:1d.0 C10F S3 *enabled pci:0000:00:1d.1 C110 S3 *enabled pci:0000:00:1d.2 C111 S3 *enabled pci:0000:00:1d.7 C119 S3 *enabled pci:0000:00:1a.0 C11A S3 *enabled pci:0000:00:1a.1 C11B S3 *enabled pci:0000:00:1a.7 C131 S5 *disabled pci:0000:00:1c.1 C2A1 S5 *disabled pci:0000:10:00.0 C132 S5 *disabled pci:0000:00:1c.2 C137 S5 *enabled pci:0000:18:00.0 C134 S5 *disabled pci:0000:00:1c.4 C2A2 S5 *disabled C23D S5 *disabled platform:PNP0C32:00 sh-4.4# hwclock --verbose hwclock from util-linux 2.33.2 System Time: 1666517587.916932 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2022/10/23 09:33:08 Hw clock time : 2022/10/23 09:33:08 = 1666517588 seconds since 1969 Time since last adjustment is 1666517588 seconds Calculated Hardware Clock drift is 0.000000 seconds 2022-10-23 12:33:07.718012+03:00 sh-4.4# dmesg |grep rtc [ 5.609650] rtc_cmos 00:01: RTC can wake from S4 [ 5.609921] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0 [ 5.609973] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, hpet irqs [ 5.687269] rtc_cmos 00:01: setting system clock to 2022-10-18 07:39:01 UTC (1666078741) @Peter Suh can you check for the following also ? cat /proc/acpi/wakeup cat /sys/class/rtc/rtc0/uevent cat /proc/driver/rtc ls /sys/class/rtc/ More Info : https://www.mythtv.org/wiki/ACPI_Wakeup#Using_.2Fsys.2Fclass.2Frtc.2Frtc0.2Fwakealarm

You can use the ./rploader.sh postupdate ds3615xs-7.1.0-46661

Hi, I have a physical ds3622xsp laptop based server that power scheduling on/off works fine. can you please check your BIOS ACPI settings and post them here ? also the output of dmesg |grep -i acpi

Well the IP is not a requirement for booting. It should go past that and boot. Do you mean you cannot get to the DSM ? What if you try to boot with the USB GRUB option ?

You should be running version v0.9.2.9 image. So please run the following ./rploader.sh update ./rploader.sh fullupgrade and retry

First of all you can stop at TCRP Friend and check if network module is loaded and if the IP has been applied. lsmod lspci -k ip a

Try without sudo please.

- Outcome of the update: SUCCESSFUL - DSM version prior update: TCRP v0.9.2.6 DS3622xs+ DSM 7.1.1-42962 Update 1 withfriend - Loader version and model: TCRP v0.9.2.9 DS3622xs+ DSM 7.1.1-42962 Update 2 - Using custom extra.lzma: no - Installation type: VM on ESXI 6.7U3 - Additional comments: Using TCRP Friend detects the update and performs required actions

yes that an issue with ICH7. Sometimes its not possible to use as SATA AHCI but only IDE.

Yes thats correct.

You can go back to the TCRP and can you please check your user_config.json before running the build command ?

Yes, It should be applicable.

Is it configured as AHCI in BIOS ? Can you check with lspci -k ?

он использовался для создания загрузчика jumkey buildroot. TCRP Friend заменил это

Yes, build command would be : ./rploader.sh build ds3622xsp-7.1.1-42962 withfriend

Hi all, TCRP rploader.sh has been updated and you can now use the model instead of the platform.It should work with old custom_config.json files but the boot images have been updated with the new scheme. New build command : ./rploader.sh build ds3615xs-7.1.1-42962 withfriend Instead of : ./rploader.sh build bromolow-7.1.1-42962 withfriend Reason for that is that begginers get confused with all the platform names and that platforms are also used on other models as well.

You dont need to go to TCRP for postupdate anymore after you include TCRP Friend. All commands besides build that you can add withfriend are OK.

Привет, я изменил суффиксы для облегчения создания загрузчика для начинающих. Теперь вы можете использовать модель и версию вместо платформы и версии. Кроме того, режим JUN устарел, и вы можете использовать опцию withfriend при сборке. например ./rploader.sh build ds920p-7.1.1-42962 withfriend

Sorry, I've updated my answer, please go back and read that again.

You should be ok with DS3622xs+, what is the issue ? Follow @haydibe instructions for the VM creation : And try latest TCRP version image. Also build withfriend option for easier DSM update management and other goodies. e.g. ./rploader.sh build ds3622xsp-7.1.1-42962 withfriend

Are your disks SATA AHCI ? And on which controller they are attached to ? Can you please share an lspci -nnq from within TCRP ?