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 < qmastery16@gmail.com> 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 0x400000
> 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 0x400000
> 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
> ASSERTION ERROR: file 'src/drivers/amd/agesa/state_machine.c', line 309
> ...
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> EEPROM not found
> ...
> I2C: 01:50 (unknown)
> I2C: 01:51 (unknown)
> ...
> APIC: 11 (unknown)
> APIC: 12 (unknown)
> APIC: 13 (unknown)
> PCI: 01:00.0 (unknown)
> PCI: 02:00.0 (unknown)
> PNP: 00ff.0 (unknown)
>
>
> "..." are parts I didn't write down as they didn't show any obvious
> errors(but I'm bad at seeing them) and it would take me a loooong time to
> write down the full log as I can't export it as far as I know, if you need
> any more information from it, I can write down any part missing.
>
> Output of "cbfstool coreboot.rom print" after I added the optionrom for the
> R5 M230 discrete graphic card :
> Name Offset Type Size Comp
> cbfs master header 0x0 cbfs header 32 none
> fallback/ramstage 0x80 stage 129247 none
> config 0x1f9c0 raw 263 none
> revision 0x1fb00 raw 582 none
> payload_revision 0x1fd80 raw 239 none
> apu/amdfw 0x1fec0 raw 131072 none
> fallback/romstage 0x3ff00 stage 320556 none
> cmos_layout.bin 0x8e3c0 cmos_layout 1164 none
> pci1002,990b.rom 0x8e8c0 optionrom 61952 none
> fallback/postcar 0x9db40 stage 13268 none
> fallback/dsdt.aml 0xa0f80 raw 9435 none
> img/coreinfo 0xa34c0 payload 102712 none
> img/nvramcui 0xbc640 payload 141628 none
> fallback/payload 0xdefc0 payload 67370 none
> payload_config 0xef740 raw 1611 none
> pci1002,6665.rom 0xefe00 optionrom 32768 none
> (empty) 0xf7e80 null 3112984 none
> s3nv 0x3efec0 raw 32768 none
> (empty) 0x3f7f00 null 31192 none
> bootblock 0x3ff900 bootblock 1424 none
>
> What happened when I tried to boot each version of Qubes :
>
> Live 3.1 :
> mce: Unable to init device /dev/mcelog (rc: -16)
> radeon 000:04:00:0: Invalid ROM contents
> radeon 000:04:00:0: Invalid ROM contents
> [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
> radeon 000:04:00:0: Fatal error during GPU init
> [TTM] Memory type 3 has not been initialized
> SQUASHFS error: squashfs_read_data failed to read block 0x5cb75d68
> SQUASHFS error: Unable to read data cache entry [0x5cb75d68]
> SQUASHFS error: Unable to read page, block 0x5cb75d68, size af0
> SQUASHFS error: Unable to read data cache entry [0x5cb75d68]
> SQUASHFS error: Unable to read page, block 0x5cb75d68, size af0
> EXT4-fs error (device dm-0): ext4_find_entry:1289: inode #41642: comm
> plymouthd: reading directory lblock 0
> (Hangs at the Qubes graphical loading screen, with loading bar full.)
>
> 3.2 (Install looked fine) :
> Hangs at "Booting from Hard Disk..." in SeaBIOS on every try
>
> 4.0 rc3 :
> [ FAILED ] Failed to start Load Kernel Modules.
> ...
> [ OK ] Reached target Basic System.
> (Hangs for about 10secs, followed by 5s of black screen)
> BUG: Unable to handle NULL pointer dereference at (null)
> (followed by a lot of output likely concerning the error and quickly back to
> boot)
> Sadly too much output and disappearing too fast for me to get anything out
> of it if all I can do is read and type to export it. Tried Ctrl+S/Ctrl+Q to
> "pause" it but nope, also checked that the laptop should not reboot in case
> of kernel panic but it still does...
>
> Thanks to anyone that could help me find what's wrong and how to fix it :)
>
> ---
> Emil Novik
>
>
>
>
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot

--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot