s1oz

[Enable Intel Turbo/AMD Performance Boost] Can this be done using the command line

Thank you very much, it has been used normally

Use version 2023.03.17 Unable to open any folder in disk1, such as appdata folder, has been loading （The Chinese language environment cannot be displayed, and the English display is normal） The backup in disk3 can be opened and displayed normally It seems that the owner and permissions are the same, but it just cannot be opened Please help me, thanks phplog: [19-Mar-2023 18:05:56 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 2) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(2, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(166): my_age('1614660085') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90 [20-Mar-2023 08:45:37 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 2) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(2, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(166): my_age('1614660085') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90 [20-Mar-2023 08:48:31 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 2) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(2, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(166): my_age('1614660085') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90 [20-Mar-2023 08:48:51 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 1) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(1, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(179): my_age('1623389423') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90 [20-Mar-2023 08:48:53 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 1) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(1, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(166): my_age('1629799215') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90 [20-Mar-2023 08:49:43 Asia/Shanghai] PHP Fatal error: Uncaught ValueError: Unknown format specifier "" in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php:90 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(90): sprintf('% \xE5\xB9\xB4\xE5\x89\x8D', 2) #1 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(99): age(2, 'year') #2 /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php(166): my_age('1614660085') #3 {main} thrown in /usr/local/emhttp/plugins/dynamix.file.manager/include/Browse.php on line 90

Thank you, it is normal after updating the nut plugin

I'm very sorry for my poor English. From 6.12.0-rc1c > 6.12.0-rc1.4 > 6.12.0-rc2 the dashboard is blank and doesn't show anything. http://tower/Dashboard doesn't show anything http://tower/DashStats can display content normally Dashboard has no reset button

In addition to manually viewing the proxy-host-1_error.log file, is there any other more convenient way to query the real ip of each successful login?

gt740升级6.10rc3后无法正确驱动 显示错误43 降级6.9.2后正常 貌似是内核高于5.14+就会这样

What does the value of APC in the built-in UPS Settings plugin represent? The device used is a BK650M2-CH. UPS STATUS BATTERY CHARGE On battery 100.0 Percent UPS Details KEY VALUE APC 001,036,0880 This will show that it is working on the battery, and the value of APC will also change UPS STATUS BATTERY CHARGE online 98.0 Percent UPS Details KEY VALUE APC 001,035,0832 This will work fine.

nut插件试过，一段时间后ups就会失联 rc7的自带ups一样显示电池上 只要不是接unraid上，win dsm显示都正常在线 但是有的朋友一样型号的ups正常 对比了下参数发现ups中有一些细微差别 在自带ups中详细信息中有以下区别 ## 不知APC是指？ #正常运行 APC 001,038,0973 #运行在电池上 APC 001,036,0880 #正常运行 MODEL Back-UPS BK650M2-CH #运行在电池上 MODEL BK650M2-CH #正常运行 STATFLAG 0x05060008 #运行在电池上 STATFLAG 0x05060010 #正常运行 FIREWARE 294803G-292803G #运行在电池上 FIREWARE 294802G-292802G #无显示，通过官方PowerChute Personal Edition获得固件版本号，问厂家是内部版本号区别 无法更新固件

请问是BK650M2-CH吗？我用默认的ups配置还是显示运行在电池上

request deletion

gt740 can work normally in 6.9.2, and run in 6.10 rc2~rc4 report error code43

Lost UPS after running for a while, NUT plugin shows running, but no UPS device shows After re-plugging and unplugging the USB, restart the NUT plugin and enable it normally Feb 1 11:03:10 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:11 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:13 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:15 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:15 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:17 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:19 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:20 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:21 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:23 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:25 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:25 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:27 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:29 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:30 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:31 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:33 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:35 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:35 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:37 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:39 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:40 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:41 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:43 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:45 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:45 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:47 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:49 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:50 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:51 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:53 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:55 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround Feb 1 11:03:55 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale Feb 1 11:03:57 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround

Thank you, this should be the problem of Engineering Sample One more question, BK650M2-CH shows: On battery in the UPS setting plug-in, is there any way to fix it? Using the Network UPS Tools (NUT) plug-in also does not work properly NUT Settings issues

i9-9900 ES(Engineering Sample) QQZ5