FW13 After a Retimer update, after the BIOS Update yesterday, only boots into blank screen.
CITWil opened this issue · 2 comments
Device Information
System Model or SKU
Please select one of the following
- Framework Laptop 13 (11th Gen Intel® Core™)
- Framework Laptop 13 (12th Gen Intel® Core™)
- Framework Laptop 13 (13th Gen Intel® Core™)
- Framework Laptop 13 (AMD Ryzen™ 7040 Series)
- Framework Laptop 13 (Intel® Core™ Ultra Series 1)
- Framework Laptop 16 (AMD Ryzen™ 7040 Series)
BIOS VERSION
The Latest 3.05 I believe. I cannot boot to anything to confirm
Windows:
Open a command terminal as administrator:
wmic bios get SMBIOSBIOSVERSION
Linux:
Open a terminal and run the following command
sudo dmidecode --string bios-version
DIY Edition information
If you are experiencing an issue on a DIY system, Please also fill out the memory and storage devices you are using.
Memory: Framework 32 GB AD5S56
Storage:WD_Black SN770 1TB WDS100T3X0E
Port/Peripheral information
Issue occure when all ports are out so I do not think it is related
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
- Yes
- No
Describe the bug
A clear and concise description of what the bug is. - The laptop does not boot or show Bios screen. The power light comes on and stays on. The Charging light is on when plugged in and only blinks when the laptop goes from off to on. The Charging light only shows the battery status. I have attempted a mainboard reset based on the 11th gen instructions twice, but no change in behavior. Also the fans seem to be running constant though the process.
Steps To Reproduce
The Firmware update must have been queued on Friday night when I shut down my laptop, because when I booted on Sunday night it proceeded to update the firmware, when I turned it on. when completed I was able to work without issue. Then I shutdown the computer for the night. When I booted this morning it booted into what seemed to have been the retimer update, that reported that it updated successfully, but when It rebooted it started this behavior.
Expected behavior
boot into linux Federa 42 Aurora DX edition
Screenshots
If applicable, add screenshots to help explain your problem.
Operating System (please complete the following information):
- Universal Blue Aurora DX Stable
-Federa 42 - Linux Kernel Version: cannot double check but whatever was in the Aurora stable channel
Additional context
Add any other context about the problem here.
Sorry for not getting to this earlier. What's the current state of your system?
Hi John, I understand. I am all good over here. After troubleshooting with support, we swapped the mainboard. I do not know what happened to it after that, but I hope that someone gets chance to take a look at it.