Re: [qubes-users] HCL - G505s (HD 8650G + R5 M230 dual graphics)

2018-01-14 Thread 'Emil Novik' via qubes-users
I did, no idea why HVM still doesn't work.

---
Emil Novik

 Original Message 
On Jan 14, 2018, 19:48, taii...@gmx.com wrote:

> On 01/14/2018 06:05 AM, 'Emil Novik' via qubes-users wrote:
>
>> Mostly works fine, but has some issues :
>> - Can't use any HVM(crashes the computer every time).
> Have you applied awokd's patch?

-- 
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/oAGVaaWfkw0wmj9fRuONKnWW_psJ28q9DVEV9VTDfiv63n5ZzbkDG-Dh2xot5AFRZPvxscZDA8xRnFTExl2sjqu-qQ9Z2_YKs0w6y6CQgMY%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - G505s (HD 8650G + R5 M230 dual graphics)

2018-01-14 Thread 'Emil Novik' via qubes-users
Qubes 3.2 with all templates updated, using fedora-26-minimal, debian-9 and 
whonix upgraded to Debian 9 too.
Coreboot 4.6 with seaBIOS and option ROM for the integrated HD 8650G 
graphics(1002:990b). Didn't add the option ROM for the discrete R5 M230 
graphics(1002:6665) as it didn't work at all, so no discrete graphic support 
sadly.

Mostly works fine, but has some issues :
- Can't use any HVM(crashes the computer every time).
- Net VMs based on Fedora can't use my AR9287, but it's not the original card 
from the laptop.
- USB 3.0 ports only working as 2.0.
- "xen-pciback.hide=(Discrete:Graphics.PCIAddress)" has to be added to the grub 
command on boot or the laptop will just crash on startup every time when Qubes 
tries to initialize the card.
- Need to fix the boot as explained by qmastery 
https://groups.google.com/forum/#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ

Thanks to the other G505s owners for their help, mainly to Awokd who gave a lot 
of his time to find out what to do with my uncooperative machine.

---
Emil Novik

-- 
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/56wLBz2l-Vy1IUEhQOcgjshspUHrOAp1_WHSZcfxQQaacNg6dl-TKD-iOwhcKbcI22liKgemdBcDZMAAq0cDwy4ks1kczz7l2z37S3Pa2tM%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-LENOVO-_INVALID_-20180114-115601.cpio.gz
Description: Binary data


Qubes-HCL-LENOVO-_INVALID_-20180114-115601.yml
Description: Binary data


Re: [qubes-users] Re: Lenovo G505s with Coreboot and Qubes R4-rc3 fails to boot

2018-01-05 Thread 'Emil Novik' via qubes-users
Does any G505s owner ever tried to put more than 16Go ram in it?
The limit is meant to be 16Go but some laptops can use more than officially 
supported, wondering if the G505s is one of these.

Would be nice to run 32Go ram on it for Qubes !

---
Emil Novik

 Original Message 
On Dec 30, 2017, 10:16, Ivan Ivanov wrote:

> Thank you very much! Luckily, when the people search, your posts and
> posts like this are among the top results:
> https://libreboot.org/faq.html#will-the-purism-laptops-be-supported
> "There are severe privacy, security and freedom issues with these
> laptops, due to the Intel chipsets that they use"
> Hopefully the majority of their buyers realize that they are getting a
> typical Intel laptop with coreboot preinstalled,
> which is not the "Ultimate Freedom Machine" and actually not much
> better than Sandy/Ivy Bridge thinkpads...
>
> Meanwhile, let me to spam this again ;)
> " Great idea is to stockpile the G505S and its spare replacement parts
> / IC components , so that - if your current one breaks - you had a
> more than one replacement.
> Lenovo tells that the average lifespan of G505S laptop is 4 years -
> and, while it could survive longer in the caring hands - it would
> really help if you have the replacement G505S / G505S motherboards /
> major components of G505S motherboard like the spare KB9012QF A3
> controllers and southbridge.
> Especially the KB9012's - they are very cheap, and at the same time -
> vulnerable to voltage spikes, so if you have unstable electricity at
> house and your power adapter wouldn't block a spike - KB9012 could
> easily die. AliExpress is your friend... :P "
>
> Mike is good at writing wiki pages like these:
> http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
> http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
> http://dangerousprototypes.com/docs/Compal_POST_diagnostic_card
> http://dangerousprototypes.com/docs/Compal_POST_diagnostic_card_-_Additional
> Maybe together we could create a new page for us all, describing the
> G505S components and their part numbers.
> I will ask him about it soon
>
> Unlike the libreboot-supported laptops, which are good but have a slow
> hardware ( Core 2 Duo / 4 GB RAM ),
> G505S ia a quad core beast with 16 GB RAM possible -> and at the
> same time not Intel ME / PSP !
> Could take many years before we see another laptop with such a great
> performance / freedom ratio,
> so it makes a total sense to turn it into Long Term Support laptop for
> you and your freedom caring friends.
>
> And, if you accidentally get too many G505S - their value should only
> rise in the future, could re-sell.
> Just hope we wouldn't inflate the prices for each other at those auctions ;-)
>
> Happy coming New Year :)
> Ivan
>
> 2017-12-30 3:20 GMT+03:00 taii...@gmx.com :
>> On 12/29/2017 06:39 PM, awokd wrote:
>>
>>> On Fri, December 29, 2017 11:32 pm, Ivan Ivanov wrote:

 2017-12-30 1:57 GMT+03:00 taii...@gmx.com :

 Yes, I am also very disappointed in purism, and its still unclear for
 me why they went the Intel road, when - at 2013 - they could have created
 a
 more freedom-respecting equivalent of G505S, instead of
>>>
>>> This was hashed over in the Coreboot mailing list recently, see
>>> https://mail-archive.com/coreboot@coreboot.org/msg50746.html. To be
>>> honest, I'm kind of tired of hearing about Purism now. ;) I think people
>>> have made their positions clear.
>>
>> :<
>> I only make so much noise because no one else is doing so - they have
>> strangely universal positive coverage in the mainstream tech media and the
>> real facts and downsides are never mentioned or investigated - not to
>> mention that the real libre products like TALOS 2 and Novena get little to
>> no press for some reason.
>>
>> I respect your opinion, but there are still so many laymen who think that
>> "LibreM" means "Libre" (the purism goons say it doesn't and that its not
>> their fault people are confused) so I feel as though I must continue.
>
> --
> 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/CAAaskFB0U6fSBs3i06-0_8byp5g%2BNRvVJJcqcv40jVPZ8OUFcQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout. @gmx.com>@gmx.com>

-- 
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 

[qubes-users] Re: [coreboot] G505s with Coreboot unable to run any version of Qubes

2017-12-30 Thread 'Emil Novik' via qubes-users
Thanks !

With the help of Awokd I managed to boot each version by using 
"xen-pciback.hide=(PCI address of the discrete GPU)" and the small grub fix for 
3.2.

I was planning on using 4rc3 but the VM setup on first boot always fails to 
create sys-net because of a libxenlight error. I can still start my session but 
no internet access, same error each time I try to start sys-net and no VM 
manager to be found.

So I decided to use 3.2 and it works like a charm, just needs some more ram and 
all will be perfect :)

---
Emil Novik

 Original Message 
On Dec 30, 2017, 21:44, Ivan Ivanov wrote:

> Hi Emil, thank you very much for your report.
> Regarding Qubes 3.2 : at the Qubes HCL list I wrote:
>
> "after Qubes R3.2 installation it cant boot - cant reach GRUB Boot Menu
> because MBR (or GRUB) is corrupted. Use grub2-install to fix it (read more)
> Everything else is OK "
>
> https://groups.google.com/forum/#!msg/qubes-users/TS1zfKZ7q8w/JQFkVF4xBgAJ
>
> If you fix your GRUB as described ^^^ you may be able to finally boot Qubes 
> 3.2
> Please test it and let me know the results
>
> Live 3.1 was buggy, full 3.1 would have worked. Haven't tested 4.0 -
> can't speak about it
>
> Best regards,
> Ivan
>
> 2017-12-28 1:19 GMT+03:00 Emil Novik via coreboot :
>> Hey, I'm having some heavy trouble getting my laptop to run Qubes and I
>> first thought I was having issues with the OS. But after digging into the
>> logs I managed to get(crashes too early during boot to get any persistent
>> logs, had to write most by hand) it feels more like an issue with my
>> Coreboot built.
>>
>> So there are the details :
>> - G505s with integrated HD 8650G + discrete R5 M230 graphics.
>> - Coreboot 4.6-2477-g6ab3edac3c-dirty with processor microcode patch
>> (change-ID: Ibbfee47ce1d5081640d6924e2b12f5213a7fcadb).
>> - Runs Debian Stretch fine.
>> - Fails to start Qubes 3.2 / 4.0 rc3 / Live 3.1.
>> - I added the vgabios.rom for the integrated card with menuconfig and the
>> one for the discrete card with cbfstool.
>> - Coreboot.rom, .config and full make output as attachment.
>>
>>
>> Some more error data I gathered from coreinfo's Bootlog :
>>
>> Failed to enable LTR for dev = PCI: 01:00.0
>> Failed to enable LTR for dev = PCI: 02:00.0
>> ...
>> I2C: 01:50 missing read_resources
>> I2C: 01:51 missing read_resources
>> PNP: 00ff.1 missing read_resources
>> ...
>> Warning: Can't write PCI_INTR 0xC00/0xC01 registers because
>> 'mainboard_picr_data' or 'mainboard_intr_data' tables are NULL
>> Warning: Can't write PCI IRQ assignments because 'mainboard_pirq_data'
>> structure does not exist
>> ...
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CommonReturns.c', line 187
>> ASSERTION ERROR: file
>> 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 776
>> ...
>> Manufacturer: ef
>> SF: Detected W25Q32 with sector size 0x1000, total 0x40
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> Manufacturer: ef
>> SF: Detected W25Q32 with sector size 0x1000, total 0x40
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>> ASSERTION ERROR: file 'src/drivers/spi/spi_flash.c', line 425
>>