I still ned to do this. I hope it is straightforward for a newbie like me, I would hate to screw up my laptop permanently.
1 Like
The same feeling here, 
I am frightened by the possibility of bricking my laptop… 
What a pity that it could not be delivered fully functional after such a long wait to get it.
I wonder if this is a so risky operation, and would love to have feedback of anybody who already did it !
Thanks 
Thank you, I will give you a feedback as soon as I have done so. In the meantime I will carefully study the procedure !
Same here I’m gonna read through it again carefully after work today and maybe run through the process afterward and hope all goes well. From the first readthrough it looks like a pretty straightforward automatic process and only takes a few minutes?
I will let you know how it went.
1 Like
Crap!
OK I did everything in the instructions and then it said to reboot for it to take affect and now the screen says
SeaBIOS (version rel-1.15.0-3-g8ee360c)
booting from hard disk…
Read error
and it’s been sitting there for a few minutes now!!!
FYI I am on the phone with support and apparently this new firmware does not play well with the NVMe drives.
I am having to create a live boot drive first, I cannot boot the laptop.
Sounds like he wants me to try a previous version of the firmware.
UPDATE: @MrChromebox turns out support has informed the lasted version doesn’t work with the NVMe drives, so you have to revert back to a previous version. I did this with support, so now the auto switching to a headset or other external speaker is not automatic. Still must be done in settings manually.
auto switching isn’t functional yet, you have to select manually
It doen’t sound very serious for such expensive laptop, that has been waited for a long time. And in my case, I cannot switch to headset even manually as there is no option in the setting /parameter menu…
It seems to me that I own a Ferrari but… I have only first gear…
It’s very disapointing and scaring so I dont even want to try to update the firmware until I will be sure that It works well, because I dont feel confident enough in case of problem.
As says the proverb : “wait and see”…
I’m confused, you have a Purism employee telling you that a firmware update will fix the issue. What more do you need to be confident?
1 Like
I confirm the firmware update worked for me.
After the firmware update, one thing to note: plugging the jack, does not automatically select the output device, you have to manually select it.
This firmware does not fix the microphone, USB microphone sensitivity is very low and adjusting sensitivity in pulse-audio, has not effect at all.
Sorry, but since I am not a computer scientist, just a user with some basic knowledge, update a firmware (when some say it can brick a computer), this is not an operation I will do without fear…
This is exactly the kind of details that will make me wait a little longer, until the firmware is more efficient (and me more confident 
), because each firmware update makes take a risk (…brick…) and to my point of view, the less often I will do it, the less risk I take…
yes, there’s a risk. It’s not zero but it’s pretty damn close.
I can’t promise a timeframe for the fix. The risk is near-zero. So it’s your choice to not have working headphones for some unknowable amount of time. You’re also potentially opening yourself to security risks by not running the latest CPU microcode updates, which are part of the firmware (and not a part of PureOS) - one of the main reasons we recommend users update any time there is a new firmware release
1 Like
Hi MrChromebox,
I finally get the courage up to try updating the coreboot and I have some troubles that seem related with “source.puri.sm/coreboot/utility”.
The command line “wget https://source.puri.sm…” (after creating and accessing “updates” dir) never acceded to “source.puri.sm…” and never got the script, even after waiting for 5 or 6 automatic new trials…
Same thing when trying to access “https://source.puri.sm/coreboot/utility” to get README file (message : Wait time is exceeded - The server at source.puri.sm takes too long to respond.)
I feel confused because my web connection is good and don’t know what to do or think about this update…
My only idea is that I suppose there is some issue with “source.puri.sm” server and any help is welcome ! Thanks
I can literally click that link (to the utility repo) and the site loads – does it not for you? It’s possible the server was temporarily inaccessible, but there have been no outages of which I’m aware
Now, it works… I have downloaded README file and coreboot_util.sh script. (Note that following the link, I’ve got a message “Project ‘coreboot/utility’ was moved to ‘firmware/utility’. Please update any links and bookmarks that may still have the old path.” and I hope it will not cause issues with the script…)
On the page “https://puri.sm/projects/coreboot/” screenshots don’t show “Librem 14” as device choice. Is it just a matter of updating screenshots, or which closest device should I choose ?
Or can you confirm that (I guess) the easiest is just to run the script and follow the menu starting with this choice 1) Update firmware using precompiled image
Sorry again if my questions are a bit naive and thanks for helping !
(Anyway, I’m not going to update tonight, we just had a cyclone and I’m still worried about the likely power outages and internet slowdown (maybe the reason for access problems?)
the screenshots were simply taken prior to the L14 release; when you run the script, your device will be correctly identified.
1 Like
- It’s done!
I was “a bit” nervous and I read the entire manual several times… and everything went well (Librem 14 immediately identified!)
I chose what I thought was the easiest option: the precompiled image.
If necessary, I can post screenshots of the different steps. Feel free to ask.
Thank you very much for your help and especially your patience !
2 Likes
@Bass20
How did it end finally for you ? On your last post ( Librem 14 ear bud headset output not working ) you still had boot troubles.
I hope all is fine for you now !
@kate.mason
Same for me! Thank you for your message that allowed me to be more confident to do what I thought was a delicate operation !
All good now, updated firmware one version earlier so had no issues with the HD after. I still need to update the latest version now as I think all the issues have been rectified.
1 Like