I am already in contact with support but I think I will try my luck at sending this out to the forum:
I pre-ordered a core ultra 5 125H framework laptop that arrived in late August, shortly before my trip to Korea on the 29th. I was hopeful that I would have a functional laptop before my flight, but this did not happen. My laptop did not post no matter what (I even tested a ram stick that was verified and nothing changed). I talked with support and I got a replacement motherboard approved. I had my friend receive and ship the replacement motherboard, (since framework doesn’t ship to Korea) and I paid ~$120 in shipping and customs fees. Now it’s October 30th, and I finally have my new mainboard. But my laptop still doesn’t post, and it doesn’t seem like anything is different than before
Postcode: 0x10011111 = 0xF9 which means no boot drive I think? (it’s reversed for some reason; all diag LEDs were green so not very helpful)
-This was with an empty drive, and a stick of memory (I have two sticks, a patriot 16gb 5600 stick and a samsung 16gb 5600 stick; no difference between the two)
-No display on laptop screen nor on external display
On my other drive with Win 10 already installed, I have no post codes
-no display on the laptop nor anything on external display
I tried resetting the bios by pressing the button on the mainboard 10 times for two seconds consecutively. Nothing. I tried reseating all connectors + ram. Nothing. Tried both ram sticks in each slot, (I only tested with one ram stick) nothing. I tried leaving the laptop sitting for several hours. Nothing, although it gets quite hot.
My only theory now is that my display (120hz display btw) is somehow bad and also needs to be replaced. I would sincerely hope this is not the case.
Update: if I remove all the internal display connectors and try to boot the laptop with an external monitor connected, it posts to the external monitor! If I try to reconnect the internal monitor, I get nothing. Before, I was just testing the external monitor with the internal display still connected. So I’m definitely getting somewhere here.
Sounds like two things could be suspect; the display itself AND/OR the display cable. Glad to hear you got it to post with everything except the display. This is a 2.8K display correct? (You mentioned 120Hz display in a previous message)
There have been a few reports of it not posting or even if the machine does post it perpetually displays a display boot code on the LEDs (presuming the table from the 11th gen is still the correct one even for the Ultra 1 models)
There is a root cause somewhere and hopefully a BIOS update will correct it in the future.
At least you can get the laptop setup and tested just without the internal display. That is a better outcome than having to send it in for repair and wait weeks for it to be diagnosed/fixed. Let us know how it turns out and welcome to the community!
Now that I am in windows, it shows the internal display connected, but not active for some reason (there is still no picture). Unfortunately, when the internal display is connected, I cannot navigate the BIOS, as the video card driver seems to default to the internal display when that is connected and not show anything on the external display.
I had the exactly same behaviour when I received my AMD 2.8k version. So I can pretty surely tell you that your display, or the display cables/connectors are broken.
What you can check (not sure if you did this also) but remove the display panel and there should be a connector also in the back side of the display. If that is also connected properly and not gotten loose, I think you will need a new display panel.
As said, i had the exactly same problem and only way to get picture to external screen was to disconnect the display cable from the motherboard. Support sent my a new display and the issue was fixed.
Just checked the back display connector and it was indeed not properly connected! It was sort of in diagonally if that makes sense. Ever so slightly off. I reseated it and viola! Everything works now. My only question is why framework never told me to unscrew the display and check the cable in that spot back there. I will let them know to add that to their troubleshooting suite.
Yeah they didn’t tell me either, or even ask about it. I learned about the display connector on the back side afterwards, and I wasn’t brave enough at that point to even think to remove the whole display.
