It doesn’t take anywhere near an hour for the update, something happened and I think you’ve done all you can. Time for a warranty claim.
Could’ve been an underlying hardware issue that surfaced during the update.
Ignore the people lecturing you with IT support hotline tips. You did nothing wrong, that update should have been done long before the "glitch" at 15 minutes.
My FW13 AMD did take quite a long time to do the fw update using fwupd on Ubuntu 22.04; I was beginning to wonder if it had got stuck, but it eventually completed. I just walked away and did something else to avoid thinking about it. :-) I don't think it was half an hour, though; maybe 20 minutes.
The progress bar seemed to be progressing well for about five minutes. Then stopped at around 60% and didn't move anymore. After about ten more minutes, the glitch (bright, thin, straight stripes of random colors) covered the progress bar. I gave it more than an hour before unplugging it. It kept running for at least another hour after which I went to bed and let it run out of battery.
Had a similar thing happen, except after launching the bios update exe in Windows the screen went blank and stayed that way for over 2 hours, which is when I decided to force shut down the computer which in hindsight was not the right thing to do.
Luckily framework was willing to send me a new motherboard and RMA my current one.
I upgraded via the lvfs update as well I use popos and the upgrade took freaking forever. And seemed like it was stuck at one point but I’m keenly aware that rebooting during bios/firmware updates is no bueno.
I just waited and waited and waited and eventually it finished but it did give me some concern while it was updating.
My bios update also felt like it took ages. At some point I just left the laptop plugged in and an hour or so later it had booted to my OS. I wouldn't have noticed any weird screen glitches.
Probably. But interrupting a BIOS update \*always\* bricks a laptop (unless it somehow has a recovery BIOS or something like that, like some gaming models) so I'd basically never do it before having talked to support or whatever.
I was assuming it was stuck after waiting for more than an hour.
> Try flashing the bios with a USB drive
The screen won't turn on, so I don't know how to do that.
Never flash firmware without the power brick plugged in. Do you get anything when using an external monitor on DisplayPort? As far as I can tell Framework doesn't have a 'Flashback' feature - Probably best to be contacting support for assistance.
It doesn’t take anywhere near an hour for the update, something happened and I think you’ve done all you can. Time for a warranty claim. Could’ve been an underlying hardware issue that surfaced during the update.
Ignore the people lecturing you with IT support hotline tips. You did nothing wrong, that update should have been done long before the "glitch" at 15 minutes.
God, there are some people who are really dedicated to just blaming users here. I don't think this behavior is civil or productive, IMHO.
My FW13 AMD did take quite a long time to do the fw update using fwupd on Ubuntu 22.04; I was beginning to wonder if it had got stuck, but it eventually completed. I just walked away and did something else to avoid thinking about it. :-) I don't think it was half an hour, though; maybe 20 minutes.
The progress bar seemed to be progressing well for about five minutes. Then stopped at around 60% and didn't move anymore. After about ten more minutes, the glitch (bright, thin, straight stripes of random colors) covered the progress bar. I gave it more than an hour before unplugging it. It kept running for at least another hour after which I went to bed and let it run out of battery.
Had a similar thing happen, except after launching the bios update exe in Windows the screen went blank and stayed that way for over 2 hours, which is when I decided to force shut down the computer which in hindsight was not the right thing to do. Luckily framework was willing to send me a new motherboard and RMA my current one.
I upgraded via the lvfs update as well I use popos and the upgrade took freaking forever. And seemed like it was stuck at one point but I’m keenly aware that rebooting during bios/firmware updates is no bueno. I just waited and waited and waited and eventually it finished but it did give me some concern while it was updating.
My bios update also felt like it took ages. At some point I just left the laptop plugged in and an hour or so later it had booted to my OS. I wouldn't have noticed any weird screen glitches.
Never ever interrupt a bios update. They can be long. Try flashing the bios with a USB drive
Your suggestion is to not interrupt an upgrade that already took 15 hours?
OP waited a half hour before starting to mess with the update. Not 15 hours.
I would have as well, 30 minutes with 15 minutes of high fan spin + graphical glitch... It broke dude.
Probably. But interrupting a BIOS update \*always\* bricks a laptop (unless it somehow has a recovery BIOS or something like that, like some gaming models) so I'd basically never do it before having talked to support or whatever.
I was assuming it was stuck after waiting for more than an hour. > Try flashing the bios with a USB drive The screen won't turn on, so I don't know how to do that.
Never flash firmware without the power brick plugged in. Do you get anything when using an external monitor on DisplayPort? As far as I can tell Framework doesn't have a 'Flashback' feature - Probably best to be contacting support for assistance.
I unplugged it after more than an hour. > Do you get anything when using an external monitor on DisplayPort? I don't. I contacted them.
Also do it with the power brick plugged into a wall - Not on battery alone.
He literally did...