Does anyone know if there is an option to disable AMD PSP?
The intrusion detection switch not meant to prevent you from booting up the laptop, merely to inform you that you’re operating on live circuits.
@mackncheesiest @ClaudiuIO @Rufo_Sanchez @Bumblebee @lengau @Matt_Hartley @Maxr1998
I didn’t see that this charging issue was already being discussed in this thread, I had the same issue and already opened my own thread (with a more detailed analysis) about this here:
According to current information, only chargers with less than 3A should be affected (so 60W and above chargers should work reliably).
As of now, it is unclear if it’s actually related to the BIOS/EC/PD controller firmware up-/downgrade, as the issues are intermittent (sometimes it just works, sometimes it works after a few retries), so reports of chargers working before and not working now may be influenced by other factors like state of charge and it just randomly working / not working.
Though no matter if it was broken or not before, this is something that will have to be fixed in future versions.
(Also, funny how the “Steam Deck charger” seems to be a very common PD PSU that Framework owners seem to have )
Well, the audience might overlap quite a bit. At the end of the day the Steam Deck is just another repair-friendly Computer in a slightly different form factor.
This, and also maybe higher chance of an overlap than some random model Anker or whatever else charger found on Amazon
Check the physical contacts maybe
@LA-MJ Just did by removing the ram and adding it gain and now it does detect the 16 gb . Weird…
So half of my RAM is missing. It only shows 8 of my 16 gig. Does anyone else has the same issue? [signal-2023-11-06-172328_002]
The memory pin layout for the AMD mainboard will result with one memory chip facing up and one memory chip facing down.
I did the AMD mainboard install (Friday-over weekend). I almost the same mistake with putting the memory on the left side of the mainboard.
Hi all, just received the AMD Ryzen 13, loving it so far. However… I’ve not been able to upgrade the BIOS to 3.03. Currently on 3.02.
When the machine reboots to do the upgrade, it gives me an error code “21” Additionally, whenever I reboot the machine the charge that came with the laptop no longer works. I have to unplug it from the wall and then plug it back in for it to register that power is being delivered to the device.
Is it possible this is causing the error (as the BIOS instructions say the device must remain plugged in - which it is, it just does not accept power when it’s been reboot).
Any help or advice gratefully received.
I just received my batch 4 AMD Framework. It shipped with 3.02 and I thought I would try updating the BIOS with the UEFI Shell option before installing an OS. However when I try it says “upgrade completed” and on reboot gives an error code “15” “Invalid Image”
Anyone else encountering this error? I have tried a couple different flash drives and fresh formatted them to FAT32 and secure boot is disabled, but no luck. In a bit I will try installing Arch and using the Linux/LVFS method. I don’t understand why the UEFI method is not working.
UPDATE: I tried another flash drive because why not and it worked! Not sure what the issues was, but error code 15 could be caused by the flash drive?
When the machine reboots to do the upgrade, it gives me an error code “21” Additionally, whenever I reboot the machine the charge that came with the laptop no longer works. I have to unplug it from the wall and then plug it back in for it to register that power is being delivered to the device.
iirc this was in connection with charger compatibility. for some using a different charger helped, for others letting the battery deplete a little (to 90% or so) and then plugging in and doing the bios upgrade worked
Is the 3.03 stable release, the same build as the beta release?
Or should I downgrade to 3.02 stable and then up to 3.03 stable.
The 3.03 stable release is the same as the beta release.
Just wanted to say, I was having frequent AMDGPU errors on Arch:
- GDM Wayland failing at boot and falling back to X11
- severe screen flickering when running games
- display lockup when opening Steam or
alacritty
or anything else that used GPU resources - slow / unreliable video encoding
Updating to 3.03
via LVFS fixed all those problems. Thanks for releasing this update!
iirc this was in connection with charger compatibility. for some using a different charger helped, for others letting the battery deplete a little (to 90% or so) and then plugging in and doing the bios upgrade worked
Thanks @Johannes_Hedtrich I’ll try a different charger and see how I get on!
Questions:
a. is it possible to configure the keyboard such that the function keys work as functions keys without pressing the Fn key?
b. is it possible to configure the BIOS such that the laptop powers on when opening the lid?
a. is it possible to configure the keyboard such that the function keys work as functions keys without pressing the Fn key?
I believe you can hit FN-esc (escape key) which has “fn lock” which flips the behavior so the function keys work on press and you have to hit function and then the key to get the secondary function such as volume control or brightness. That’s what I did on mine in Windows 11.
b. is it possible to configure the BIOS such that the laptop powers on when opening the lid?
I think I saw in another thread that the sensors are not powered when the system is powered off or in hibernate, so it’s not possible for the system to recognize a change in lid sensor state when the system is off. (Maybe the design changed with AMD?)
@2disbetter right now the lid open sensor is driven off a power rail that is shut down when the system is off and no AC present, so this would not be possible. But it is an interesting idea!
Posted in more detail about this here; 3 out of 4 ports no longer working after hard crash - #7 by Nate_C
…but after doing the 3.03 bios update from within Windows 11 today, the system booted up to nonfunctional USB ports in all ports which had something plugged in (left rear and front and right front) during the update (I realize the instructions stated to unplug devices but accidentally didn’t before clicking the button to start the update and didn’t want to unplug anything while the process was going on). They became functional again after shutting down the computer and removing all ports and then replacing them and starting up. Just in case someone else experiences the same (or wants to avoid my experience). Unfortunately, the new bios did not seem to fix an issue I’m having with my Dell TB16 Thunderbolt 3 dock not reliably being recognized for power delivery and external monitors in Windows 11.
I’m having with my Dell TB16 Thunderbolt 3 dock not reliably being recognized for power delivery and external monitors in Windows 11.
I’ve had weird issues as well. With a Dell Thunderbolt dock, as well as a few more generic USBC docks. This morning, I had an inexpensive USBC Anker dock working, including pass through power delivery, powering two dock connected HDMI monitors. I unplugged the laptop to go to a meeting and when I came back, no power delivery nor display support. I switched the dock to the rear right USBC port on the Framework (instead of the rear left) and it started working. But at home where I also have a dock, I’ve also had general inconsistent support.
I have a rather large 34" 3440x1440 monitor at home. Worked through the docking station under Fedora 39, but not at all in Win 11, with Displaylink and all drivers/BIOS updated.