support1 As I wrote at the beginning of my post, the system already has the latest BIOS (V029 from 10/23/2024, you can click on the link to see the image you want)

Of course, I first used the latest AMD Auto-Detect and Install tool (release date 2024-12-05).
I also tested the drivers provided by Beelink, as described above.

Since that didn’t work, I tried ALL previous versions of the AMD chipset drivers back to version (3.08.17.735 Release Date 2021-08-23).
I also tried the drivers provided by Microsoft for the GPIO controller.

Through my tests it is clear beyond doubt that there is a problem with either the GPIO controller (ACPI\AMDI0030), its driver or a peripheral connected to the system through the GPIO controller.

      10 days later

      Serli
      Hello,

      1. Could you please send your question to our official after-sales email? This is the address: support-pc@bee-link.com
      2. Please send your SN and purchase record again, as well as the link to this forum, so that our customer service colleagues can better check your question.
        Have a nice day!

      Best regards!
      Wendy
      Customer Support

          • SSerli

            • Post #5
            • #5

            support6 I wrote the same text to support-pc@bee-link.com already 10 days ago. Unfortunately, nobody at support-pc@bee-link.com has been able to help me so far.
            Then I was told to adjust the BIOS fan control - I tested it extensively - without success.
            They asked for the BIOS version again, although it is at the top of my text. Then told me, when I sent them pictures of the BIOS and nameplate again, that I was using the current BIOS - I know that and that is not the question.

            I haven’t heard anything from Beelink Support for a week now.

                Serli
                Hello,

                Could you tell me your email address on here?
                I saw a similar email today, but I’m not sure if it was from you.

                Have a nice day!

                Best regards!
                Wendy
                Customer Support

                    • SSerli

                      • Post #7
                      • #7

                      support6 No, I will definitely not write my e-mail address in a public forum.

                      How do you make a private message in this forum?

                          • SSerli

                            • Post #9
                            • Edited
                            • #9

                            support4 As I wrote above, I have already done this extensively. So far without getting any help.

                            I have just sent another email with the entire message history and the link to this forum topic.

                            It would be good if a competent employee would read through the entire description and understand the issue in order to solve the problem with the GPIO controller ( ACPI\AMDI0030 ).

                              • support7

                              • Post #10
                              • Edited
                              • #10

                              Thanks for your reply.Our relevant personnel will get back to you.

                              10 days later

                              Has there been any progress on this issue? Any fixes or developments?

                                May i ask does your machine have a problem with high idle current consumption?
                                Please send us a picture of SN number and BIOS version.
                                So we would be able to know whether it is latest BIOS and send you files accordingly.
                                Here`s how to check your BIOS version:https://mega.nz/#F!yuISGa4I!s1bQQajKwnsEdzjqq4nopQ 

                                8 days later

                                • SSerli

                                  • Post #13
                                  • #13

                                  DannyBoy7783 No, nothing has happened yet. Beelink doesn’t seem to care.

                                  I have had further contact with email support. Of course they asked for the firmware and serial number again and then told me that the BIOS is up to date.
                                  Later I was offered to send the device in for a replacement. In the meantime, I have been in contact with other SER8 users who have confirmed the same error with their devices. An exchange for a new device would therefore not help.

                                  On 21/02/2025, Beelink released a new BIOS (without a changelog). I installed it on my device without any changes. The problem with the GPIO controller still occurs.

                                  Dear Beelink developers: Please solve the problem with the GPIO controller ( ACPI\AMDI0030 ).

                                    Hey, in your posts you mention testing different driver versions.
                                    While updating my BIOS today, I noticed that newer versions have also been released:

                                    amd_chipset_software_7.02.13.148.exe [2025-02-25]
                                    https://www.amd.com/en/support/downloads/drivers.html/chipsets/laptop-chipsets/amd-ryzen-and-athlon-mobile-chipset.html

                                    amd-software-adrenalin-edition-25.2.1-win10-win11-feb2025-rdna.exe [2025-02-11]
                                    https://www.amd.com/en/support/downloads/drivers.html/processors/ryzen/ryzen-8000-series/amd-ryzen-7-8845hs.html

                                    have you tested them yet?

                                    I’ll add that I currently have the latest BIOS and the above drivers (+Windows Update @ 100%). I haven’t measured the usage in IDLE, but I’ll have to check it myself - it’s just a matter of taking a box from home to work to measure it in the socket :)

                                      bakahk This will not solve our problem. You can save yourself the effort of testing the new driver package: A look at the release notes reveals that the GPIO driver has remained the same. “AMD GPIO2 Driver 2.2.0.134 2.2.0.134 No change”

                                        Thanks for the heads-up! It seems like the new driver package will not be successful since the GPIO driver is not being altered. Thanks for the clarification, and I’ll focus on finding other workarounds instead. Let me know if there’s anything else I can help with!