Andrew Pafitis
-
Posts
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Andrew Pafitis
-
-
whatever, i set up a script to kill and relaunch aida64 and use Hibernate Trigger to launch it on resume from sleep. aida relaunches before the beadapanel fully boots up but it connects straight away when it does. seems to work well.
-
Please help, it seems that this does occur after every time I wake from sleep. The only solution is restarting Aida64. For a $120 panel, I would really like this working as intended.
-
@Fiery just want to make sure this gets seen, should i open a ticket instead?
-
Could we at least have the option to rotate the splash screen somehow? I have my panel mounted vertically, so the splash screen comes up sideways. Minor annoyance, but I've put a lot of effort into my build.
-
On 3/12/2021 at 8:53 PM, beada said:
Yes we have a PC tool named as 'BeadaTools‘ to access on-board storage
@beada Hi, I just received this new 6.8" BeadaPanel the other day. It looks great and I am thrilled to be able to change the screensaver using BeadsTools for when Aida64 is not yet connected. The only thing that bugs me is the Linux penguin and BeadaPanel splash screens that are displayed before the screensaver. Is there any way at all to disable these splash screens from appearing when the panel starts up?
-
I just got in the new 6.8" super wide BeadaPanel the other day and it's great when it's connected, but sometimes (not always) when coming back from sleep it goes to the screensaver and Aida64 shows "Error: LCD init failed" in the LCD preferences.
Disabling and re-enabling BeadaPanel support does nothing, but if I terminate Aida64 and relaunch it reconnects just fine.
Attaching some dump files if it helps. Let me know if there's anything else I can provide to help chase down this bug.
-
17 hours ago, Fiery said:
Let me know how it works
Wow you guys are fast.
The fan sensors are labeled and responding as expected, no issues with RPMs jumping sensors. However I'm not seeing the AIO_PUMP represented anywhere, and the "Power Supply" fan is no longer there. AIO_PUMP RPMs were previously reported, albeit with issues as described above. Is the Power Supply fan not able to be read from the motherboard?
-
I have the new NZXT B550 motherboard that was released a few weeks ago. Some of the cooling fans listed have oddly specific names in Aida64 (System, Chassis, GPU) when the motherboard pins are labeled CPU_FAN, AIO_PUMP, SYS_FAN 1, SYS_FAN 2, SYS_FAN 3, SYS_FAN 4, and SYS_FAN 5. See here on page 15, items 2, 5, 16 and 29: https://nzxt-site-media.s3-us-west-2.amazonaws.com/uploads/download/attachment/1033/N7_B550-Digital_Manual-210315-EN.pdf
For full context on my machine, it's the NZXT B550 motherboard with 5800x Ryzen, NZXT X53 AIO on the CPU, RTX 2080 (stripped for AIO), second RTX X53 AIO on the GPU, NZXT E850 power supply (connected via USB for smart monitoring in NZXT CAM), and a USB connected NZXT RGB & Fan Controller (although I have no fans attached to that, just using for additional RGB channels).
I can map some of the motherboard headers to sensors in Aida64, but not all.
CPU_FAN="Chassis", connected to CPU AIO Radiator Fans
AIO_PUMP="CPU", connected to CPU AIO "AIO" cable
SYS_FAN 1 = "System", connected to GPU AIO Radiator Fans
SYS_FAN 2="Aux", connected to GPU onboard fan
SYS_FAN 3=???, I don't have a fan connected to read outputs on A64
SYS_FAN 4=???, connected to case exhaust near CPU, I can't find any sensor in A64 showing this fan's speeds
SYS_FAN 5="Aux2", connected to case exhaust near GPU
Also strange, the AIO_FAN/"CPU" sensor properly reads out the AIO pump speed from the motherboard, BUT only if the CPU_FAN is not running. If CPU_FAN fan is running and displaying "Chassis" RPMs, Aida64 then shows 0 RPM from "Chassis" and the pump's actual RPMs are displayed against the "Power Supply" sensor. This is the only time that "Power Supply" shows any RPMs, and doesn't actually ever show the PSU's fan speed.
The only other cooling fan sensor showing in A64 is "GPU". This is likely reporting off the GPU's internal fan port, but I have that fan cable disconnected and instead control an aftermarket onboard fan for the card and the AIO fans through the motherboard headers (SYS_FAN 1 and SYS_FAN 2).
So in my system, the Power Supply fan from the E850 and SYS_FAN 4 are definitely not showing RPMs on any sensors in A64. SYS_FAN 3 could also be missing but I don't have anything connected to it to confirm.
I would have expected to see the 3 additional fan ports from the NXT usb fan controller, although I now see in another thread that support for the fan controller was added last month in a beta update. Just installed the beta and still not seeing them, assuming then that fans need to be connected before they're detected in A64. Besides that, latest beta still having all the same issues above with the motherboard ports and PSU fan.
I'm also assuming that the only way to see the pump speed from the second AIO attached to the GPU would be to connect it to one of the fan ports, is that correct? Both AIOs are connected via USB and report pump speed to NZXT CAM as expected, just not sure if A64 is supposed to be able to read from the USB or needs to read discretely from the headers. Is it an issue that I have 2 of the same AIOs attached to the system?
Attaching the ISA sensor and USB dumps as I've seen requested in other threads. I can do more testing if necessary, but my rig is mounted on the wall in a Thermaltake P90, so it's really a pain to disconnect and take down to work on. (It's so beautiful tho)
BeadaPanel "Error: LCD init failed" after wake from sleep, sometimes
in Bug reports
Posted
i reinstalled windows and tried to reimplement the kill script to force a restart of aida64, but for some reason the kill script doesn't work this time.
anyways, @Fiery i found this other post mentioning "lcd init failed" where you asked for a usbdump file so i started poking around. i took a usbdump file when it failed, after restarting aida when it was successfully connected, and after restarting a second time to be sure. i compared values from the 3 files and think believe i understand the problem here.
Under the section [ DevClass / USB Devices ] I found that the usb beadapanel device instance ID was logged as 20, however restarting aida64 the usbdump shows an instance id of 19 and is properly connected and displaying stats on my panel. Restarting aida64 the second time, panel connected again, and usbdump also still showing device instance id of 19.
I have a whole bunch of usb devices connected through several usb hubs, so I'm not sure of the exact root cause for the IDs to change, but it seems possibly related to usb selective suspend and when the pc wakes from sleep where the usb devices are reconnecting, where it seems the pc reindexes the usb devices (panel now at 19) but aida64 is looking for the index that was saved prior to going to sleep (20), and thus failing.
Is there any way to force aida64 to reindex the usb devices after waking from sleep, at some interval, or anything else without having to force a restart of the entire application?
usbdump-init failed.txt usbdump-ok.txt usbdump-ok2.txt