[qubes-users] Re: Lenovo G505s A10-5750m / qubes 4.0rc5 / Unsupported Hardware Detected
By the way: Mike Banon frequently visits reddit.com/r/coreboot , so you may also ask him if you have some coreboot G505S questions -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/055ef80f-dbac-4c28-ac2e-e4ddef65c142%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Broadcom wireless driver issue.
Broadcom hardware/software is a proprietary piece of crap that doesn't work well at the opensource operating systems. It could be easier to just replace your Broadcom MiniPCIe card with something from Atheros ath9k family which has opensource drivers / opensource firmware and work perfectly almost everywhere. Just make sure that either your BIOS doesn't have a wifi whitelist or you know how to remove it / where to obtain a hacked BIOS with it removed (e.g. bios-mods site). E.g. check AR9462 miniPCIe card: 2.4GHz+5.0GHz 300 Mbps 802.11n Wifi, costs just 8 dollars at aliexpress with free shipping from china --> and problem solved -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e3d8eedd-7a2f-479e-aefa-7944be976036%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Lenovo G505s A10-5750m / qubes 4.0rc5 / Unsupported Hardware Detected
> I think to order this material for a future flash coreboot on G505s. can you > confirm that the material is OK? Sorry for late reply, these links are almost ok but it's better to get CH341A with a green PCB because there were a few bad black CH341A with 5V instead of 3.3V while we haven't heard of such cases for green CH341A -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1678ebc3-77ef--9076-e22ad5606898%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Materials for BIOS flash procedure
Sorry for such a late reply, hope you already know about "Flashing a BIOS chip" article at DangerousPrototypes forums which uses G505S as an example. And another "Flashing KB9012" article is optional and not urgent (since it's not replacing the proprietary KB9012 firmware, just removing the serial numbers from it) so maybe you could wait for this 30-pin cable. I would have happily shared one of my spare cables but I'm concerned about privacy (postal address etc) and the international shipping could cost for me more than simply ordering 10pcs to your address. But your message is pretty old so I hope you got it resolved. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/34de72fc-b48e-4581-b41e-40be49c75029%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How many gigabytes of memory is required for G505s?
> and yes it is the best - remember to install coreboot with microcode > updates btw (check binary only repo + generate microcode from tree) "Generate microcode from tree" option does not work for G505S. Luckily these confusing options have been hidden at the latest coreboot from the boards which do not support this method. And I am using a script at "G505S hacking" dangerous prototypes page to patch the coreboot sources with the latest microcode -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b2bddbaa-9827-4064-887f-61fed2e4548b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] g505s BIOS settings for installing 4.0.1
Proprietary UEFI on this G505S laptop is a real piece of sheet and I really encourage you to "upgrade" it to coreboot opensource BIOS as soon as possible! There is a great "Flashing a BIOS chip" detailed step-by-step article at DangerousPrototypes site which uses this G505S laptop as an example, and if you'd have any questions regarding the coreboot build/configuration - we will be happy to help you. Although I could just send you my own coreboot build, it is discouraged because to become a productive member of our small community you'd have to be able to build coreboot on your own. So please try following this way, and if you'd have any questions we will happily answer -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/acd2a912-d13c-49d5-91b1-2a2f753cfedf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Intel ME Backdoor, called Odin's Eye
воскресенье, 7 января 2018 г., 18:14:26 UTC пользователь haaber написал: > > https://i.redditmedia.com/5mA7LrMiwgmmhrwfYF8Jks0WEng66fxWoCcGw33dhCA.jpg?w=597&s=339d919645f1de31a42913c748d1d7fb > > > > > > Summary: > > > > Intel Whistleblower leaks details about his role in backdooring all IME > > chips on behalf of Intelligence Agencies. > The post is unspecific. Of course ME is a problem: the allegations could > be true or could be disinformation. "I know exactly" is an unplausible > formulation for a backdooring engineer - it is almost surely a wrong ot > statement if it was not himself who spied ... To conclude: unless some > details are given to enhance trustworthyness (a specific backdoor, > protocol, communication interface, whatsoever), I personally consider > this troll post. Sorry but you haven't seen the full story. This "Intel guy" is legit, he provided proofs like this one: https://i.warosu.org/data/g/img/0595/40/1490327898699.png Best regards, Ivan Ivanov -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9757603f-5905-4b2d-ba1c-22fba634b8bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Intel ME Backdoor, called Odin's Eye
воскресенье, 7 января 2018 г., 18:20:37 UTC пользователь tai...@gmx.com написал: > On 01/07/2018 02:46 AM, d@gmail.com wrote: > > > Summary: > > > > Intel Whistleblower leaks details about his role in backdooring all IME > > chips on behalf of Intelligence Agencies. Posted 3/22/2017. Codename: > > Odin's Eye > > > That isn't an "intel whistleblower" that is simply a random dude with > too much time on his hands making up a bullshit story, besides there is > no "backdooring" IME as it already is a backdoor. > > Intel doesn't need to add a specific backdoor for such a thing nor would > a TLA ever ask as: > They already have knowledge of various exploits that do the same thing > A specific func_backdoor has zero plausible deniability > Any foreign intel agency could easily obtain proof and tell the media. Sorry but you haven't seen the full story. This "Intel guy" is legit, he provided proofs like this one: https://i.warosu.org/data/g/img/0595/40/1490327898699.png Best regards, Ivan Ivanov -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ac501523-14ca-4938-a074-0fd5a51fc6bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Lenovo G505s with Coreboot and Qubes R4-rc3 fails to boot
Tuesday, 28 December 2017 , 4:30:51 UTC+6 awokd wrote: > On Wed, December 27, 2017 6:05 pm, Taiidan [at] gmx [dot] com wrote: > > What version of coreboot are you using, they are removing AGESA from the > > latest versions due to some dumb choices by the leadership. > > I'm not sure that's accurate. From the thread on the Coreboot mailing list > a few months ago, it sounded to me like they had been considering it, but > someone did the work necessary to keep them alive. > > And Blooorp, you might want to try that mailing list too if you are still > stuck! Would be more there who'd know about Coreboot specific issues. The complete "trying-to-kill-AGESA-boards" story: 1) At the end of 2015 some coreboot devs didn't like AGESA and its' "long" compilation times, and because of that + maybe some other personal/financial reasons : they wanted to quietly move AGESA boards from the main coreboot to some separate soon-to-be-abandoned-for-death branch, or even remove it completely! For example: https://mail.coreboot.org/pipermail/coreboot/2015-November/080578.html - "[coreboot] A case for branching AGESA" But, thanks to Vladimir Shipovalov raising the heated discussion threads like this - https://mail.coreboot.org/pipermail/coreboot/2015-November/080637.html - "[coreboot] Removal of AGESA - to be or NOT to be? A story of G505S" - and thanks to the kind developers who supported his side, we all dodged a 'rotting code' bullet ! 2) Second attempt has been made by the Google people, who want to set up the higher standards for coreboot sources - e.g. by removing all the boards which didn't support EARLY_CBMEM_INIT ---> which included AGESA boards like G505S: https://mail.coreboot.org/pipermail/coreboot/2017-May/084255.html - "[coreboot] Platform / Chip removals after upcoming releases" Huge thanks to Kyösti Mälkki and everyone who financially supported his work, he brought that EARLY_CBMEM_INIT feature to many boards and now the majority of AGESA boards - including G505S - are safe again. But we should never relax: Carefully watch the coreboot mailing lists - so that, when a threat of G505S removal appears again - we will be able to address this threat in a timely manner, not just by modifying the source code to fix the "not matching the standard" issues - but also starting the big discussions to show that a huge amount of people TRULY CARE about AGESA boards and wouldn't let a silent removal happen. And, if "introducing a standard" means dropping half of coreboot supported boards, maybe we could argue that this standard shouldn't be introduced? If you can't contribute by source, contribute by your support voice ;) The next potential danger is: * After the 4.8 release, and with every release after that, platforms that have not been updated in the board-status repository within the previous year will be removed You need to learn how to submit a board status, and also re-test coreboot building at least one-two months, so that - if some commit suddenly breaks coreboot - we'll be able to quickly find that commit and do something with that offending code before the other parts of repository started to really depend on it Best regards, Ivan Ivanov -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/18e65624-5fc7-43ae-8934-16625c55ac5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Lenovo G505S Coreboot
Tuesday 26 December 2017 г., 15:18:14 UTC+0 user Blooorp wrote: > Le mardi 26 décembre 2017 00:05:28 UTC+1, tai...@gmx.com a écrit : > > On 12/25/2017 12:16 PM, Blooorp wrote: > > > > > Le lundi 25 décembre 2017 16:27:11 UTC+1, awokd a écrit : > > >> On Mon, December 25, 2017 3:07 pm, Blooorp wrote: > > >>> "Devices/Add a VGA BIOS image (don't specify location or IDs, let it > > >>> auto-populate) " > > >>> > > >>> make: *** No rule to make target 'vgabios.bin', needed by > > >>> 'build/coreboot.pre'. Stop. > > >>> > > >>> > > >>> Looks like it didn't work, should I put the location and ID of the one I > > >>> extracted from the stock bios? > > >> I think I copied mine to the top level coreboot folder as "vgabios.bin" > > >> and let it find it there. > > >> > > >> Email me directly if it's still not working and I can help, we're off > > >> topic from qubes-users now... > > > Everything works now, my mistake was using the wrong vgabios.bin, the > > > stock bios contains the ones for each version of the laptop but I didn't > > > know that so I took the first that I found, with device ID 6663. > > > The one I then searched for and that worked, thanks to awokd, was with > > > device ID 990b, appropriate for the G505s with integrated graphics and > > > not discrete card. > > > > > Don't forget about that microcode update - it is mandatory both for for > > security and IOMMU. > > > > Use the patch that awoke made, a true service to the community - the > > lenovo g505s is now properly working and is the best laptop for qubes as > > it supports an open source init version of coreboot without ME/PSP > > unlike purisms laptops with the not really disabled ME and entirely > > blobbed silicon init via intel FSP. > > Didn't forget about it, he did some awesome work :) > > I took my time to choose the right laptop to get into Qubes, really feels > that I made the right choice ! > But now, I need to make Qubes work on it, I'm collecting the issues haha The perfect VGA BIOSes for Lenovo G505S could be obtained here - https://mail.coreboot.org/pipermail/coreboot/2017-July/084680.html Go to "g505s-atombios" repository and download one or two vgabios files (depending on if your G505S had just integrated GPU, or integrated+discrete), then compare their checksums - and, if the checksums are correct - feel free to add them to your completed coreboot BIOS build. At the ReadMe of this repository, you could see how to add (or remove) a vgabios file to coreboot BIOS after its building - one or two simple commands. Actually, for G505S with "integrated+discrete GPU" even a single vgabios for integrated GPU - would be enough to show the image on display. I just hope that, if you add both vgabios you could somehow make your discrete GPU working (it still doesnt work for me) -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3822342b-1205-4be1-8623-bb9cba8c71db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
