I’m having a hard time narrowing down the cause myself. It just seems like multiple things can cause it or the EC/bios is extremely buggy. Did they use AI to write it?
Another note, right now I have my 180w connected in addition to my dock which provides 100w when used alone. This seems like the only way I can get it to act properly and not lock down to 500MHz when using the dock. Throttle status in amdgpu_top has nothing set which i would expect for normal opperation.
As soon as I disconnect the 180w PSU, the dock disconnects and reconnects (should not do this as it is disruptive), and I see Throttle status show “PROCHOT_CPU, PROCHOT_GPU” but it is NOT stuck to 500MHz. It does seem to be partially throttled though. It is nowhere near overheating so these throttles do not make sense to me.
If I then reconnect the 180w PSU, nothing changes, it remains with those throttles in place.
EDIT: Come to think of it, I’m pretty sure amdgpu_top has ALWAYS had something there in the throttling section on the previous bios version 3.05. I have never seen Throttle status showing blank like I do now (power off, reconnect 180w psu, power on will clear it on this 3.06 version). There has always been a Throttle setting set as far as I can remember. I thought it was just normal for this laptop to always be in some throttle status.
During the 3 tests, did you have nothing plugged in except the FW180W PSU. or was the dock plugged in at the same time?
The 3 tests needed to be done with nothing plugged in except the FW180W PSU. The reason is that the dock looks to the laptop as a PSU, so with the FW 180W PSU, it looks like it has 2 PSUs plugged in at the same time, and the laptop can only use one of them.
Also, amdgpu_top is not very useful here. It cannot detect the “EC setting GPIO prochot”. When set, nothing appears in amdgpu_top.
I’m surprised you haven’t gleaned this from the 3.06-beta announcement thread which started 6 days ago and has lots about this - in fact it seems to be the only complaint in that thread.
While I understand it’s frustrating to experience bugs and not always have an immediate fix, can the issue not be simply avoided by just shutting it down rather than sleep? At least until we can get a fix. I get it, should have a working product etc etc. I’m not disagreeing. But it seems like that would be a very easy work around without much effort. It only takes a matter of seconds to cold boot way rather do that and have a more efficient use of the psu than all the studders and such that were caused previously.
One more thought - you are using Arch w/Gnome right? Or was it KDE?
I am sure you have stated this, but life has been busy.
Before the MB reset fixed this for me, toggling from Performance (or balanced) to powersave and back also seemed to fix this for me without a reboot. After doing that, I could use any of the 3 without issues. YMMV.
I don’t remember what kernel you are on but w/Arch I am sure you are beyond the version that had power negation issues - so it is definitely strange that you are seeing this. My laptop has been in and out of sleep multiple times today w/o issue.
Do you have an expansion card available that you could try a fresh install of Ubuntu or Fedora as a dual boot and just see if its happening in another OS?
If it can peak, even just for 1 ms, to 450W, then one will have full game play, without any battery use. It is those peak draw from the CPU/GPU that cause the battery to discharge for short periods. It will probably need an updated EC code to handle the peaks, but it could work.
Good luck even getting to 240w with it. In my limited testing, even the 180w psu doesn’t go past about 163w and I have never seen it “peek” higher. I’m only talking about into the machine, not what it pulls from the AC outlet.
Not currently possible, Framework EC restricts the current to 90% of the input current, which means your FL16 can only draw up to 4.5A from a 100/140/180/240W power adapter without modification.
I assume this should mean that the official FW 240W PSU shouldn’t have the issues you all have been finding in the Delta and UGreen ones right? Or have you also resolved those ones? (It’s a long thread)
I’m honestly wondering as a person interested in a 240w charger if i’m better off preordering the new charger from framework or getting the ugreen? I could make use of the extra ports on the ugreen but I’m more concerned with not having the battery drain while gaming. For people new here after the announcement. What exactly is going on with the ugreen charger and problems or studdering?
It’s likely it would have had the same issues. I think the only difference is that when the framework one releases the stable firmware will have the fix added to it. I’m testing the beta firmware to fix it and it works great with my Delta 240W charger!
way rather do that and have a more efficient use of the psu than all the studders and such that were caused previously.
