On Wednesday, January 18, 2017 at 6:34:29 AM UTC-5, Asterysk wrote:
> >First of all we need to make sure that you are prepared for flashing. 
> >coreboot image cannot be >flashed internally on Lenovo G505S through a 
> >purely software way (I tried with >internal:laptop=force_I_want_a_brick 
> >flashrom option, it always fails, cant do that!) . 
> 
> >To install a coreboot, you will have to: 
> >1) get some hardware tools like screwdrivers, CH341A USB flasher and SOIC-8 
> >test clip 
> >2) tear down your laptop to access the motherboard 
> >3) take SOIC-8 test clip and attach its wires to USB flasher that is 
> >supported by flashrom (such as CH341A), then attach SOIC-8 test clip to BIOS 
> >chip with 8 legs, then plug USB flasher device to another computer with 
> >Linux (while it is still connected to G505S motherboard through wires and 
> >SOIC-8 test clip) 
> >4) using flashrom, make a dump of your existing BIOS just in case, then 
> >flash a new coreboot image with verification 5) assemble your laptop in 
> >reverse order . That is exactly how computer repair shops are repairing 
> >laptops with failed BIOS updates, and are earning pretty good money on it 
> 
> >Here is a hardware flashing manual - 
> >http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate . 
> 
> Everything is described in a great detail here: complete list of tools and 
> where you could buy them (need to spend from $0 to $30, depends on what tools 
> you already have), how to connect these tools properly, a lot of helpful 
> photos - for example, photo of G505S motherboard, so you could easily see 
> where is that BIOS chip with 8 legs is located, dont need to spend time 
> reading the motherboard chip labels. While this instruction mentions Bus 
> Pirate USB flasher, the instructions for CH341A USB flasher are exactly the 
> same - only a flashrom command is different (could see this command at the 
> end of page) 
> 
> My current coreboot build is from December 2016 - it is not the latest, but 
> still pretty recent, so I am not going to rebuild it from scratch yet. Still, 
> there is one component inside BIOS image that could be easily updated: 
> KolibriOS, tiny wonderful open source operating system that fits on a floppy. 
> It could be launched from SeaBIOS Boot Menu, and works as a RamDisk (no 
> changes to your computer saved). After you tell that you are prepared for 
> hardware BIOS flashing, I will take KolibriOS latest daily build, add it to 
> ROM and send a complete coreboot BIOS ROM to you 
> 
> Please reply if you have any questions 
> 
> Best regards, 
> qmastery
> -----------------------------------------------
> 
> Is it possible to also reflash the USB firmware at the same time in case it 
> has been tampered by Bad USB ?

Does anybody know where I can find an up-to-date copy of the microcode for this 
laptop? The latest microcode images I've been able to find *anywhere* are
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd-ucode
which according to the logs date back to 2016 and therefore can't possibly 
contain spectre mitigations for an A10-5750M CPU.

Supposedly AMD has/will release mitigating microcode for family 15h but I don't 
think AMD has an equivalent to: 
https://downloadcenter.intel.com/download/27776/Linux-Processor-Microcode-Data-File
 

Does AMD even announce when they release microcode for a particular family/CPU? 
Ideally they'd have a list of CPU->microcode.tar.gz but one can only dream I 
guess...

The next step of course will be figuring out how to build coreboot to load the 
microcode image, but, one step at a time.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/4b6c8e67-8188-4212-9998-8e1d1e9e2e1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to