Kali

this is one of the hw we like to support, but we dont have it no one is able to pull dmesg ?

è probabile, ma io non ci scommetto e fidati di quello che dico

sono un po di giorni che è stato risolto il problema del timebomb il fatto è che risalire a tutte le protezioni infilate da synology è abbastanza complesso e quindi non c'è una certezza

u can find it into the hda1.tgz inside the .pat

i was not aware about 5004 installs fine on nanoboot 5.0.3.2 and this is promising as i cant find nanoboot source, i compared nanoboot and a stock rd, and applied thing over 5004 rd but is a stripped down version, i didnt apply things which looked to be cosmetics

the current problem is this one: Jan 1 00:00:14 updater: updater.c:5011 Start of the updater... Jan 1 00:00:14 updater: updater.c:5120 This is X86 platform Jan 1 00:00:14 updater: updater.c:5123 ==== Start flash update ==== Jan 1 00:00:14 updater: boot/boot_lock.c(225): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:6) Jan 1 00:00:14 updater: updater.c:4945 Failed to mount boot partition Jan 1 00:00:14 updater: updater.c:5711 Failed to accomplish the update! (errno = 2) for some reason it's trying to mount /dev/synoboot2, and this thing should not happen Jan 1 00:00:22 updater: updater.c:4890 Start of the updater... Jan 1 00:00:22 updater: updater.c:2270 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf Jan 1 00:00:22 syslog: ninstaller.c:1991 set upgrade completed cmd=[/bin/echo "C:0:" > /tmp/update.progress] both log are taken from 4458 pat install (1st with 5004 kernel/rd 2nd with 4458)

CONFIG_EXT4_FS_SYNO_ACL does not exist on 4458 kernel too btw, this is the 4458 to 5004 bromolow config changes http://sprunge.us/iHbO