4.0-rc4 install on Lenovo G505S - no network

[dbr287]

I've installed rc4 on G505S with Coreboot (legacy bios). Installation went ok (found iommu and interrupt remapping just fine).

On 1st (gui) boot, I've tried all the combinations selecting 1) create ServiceVMs, AppVMs, 2) only ServiceVMs, 3) only configure templates,... but none works. It always hangs at Configuring 1st template (usually debian-9). If I reboot, and attempt the same thing, I see it prepends tmp- for tmp-debian-9, and hangs while configuring again (and keeps prepending tmp-tmp-debian-9 on consequent runs, and halts). I then re-installed, and proceeded with last option.

So I did Advanced option (only creates dom0, no other VMs). Here I attempted to run 'firstboot-qubes-text' manually, but that fails for each one of the 4 options with the same error:

Failed to disable unit: No such file or directory
Failed to sotp kdump.service: Unit kdump.service not loaded.
-> Configuring template debian-9...
usage: qvm-start [-h] [--verbose] [--quiet] [--all] [--exclude EXCLUDE]
[--skip-if-running]
[--drive DRIVE | --hddisk IMAGE | --cdrom IMAGE | --install-windows-tools]
[VMNAME [VMNAME ...]]
qvm-start: error: no such domain: 'debian-9'

This is what I see in /var/lib/qubes/vm-templates

[root@dom0 vm-templates]# du -sk * | sort -n
1951428 whonix-gw
2431376 whonix-ws
2760892 debian-9
3599232 fedora-26

So templates are installed, but they are somehow not visible to qubes (they also don't show up in Qube Manager (only dom0 does)).

Looking at some anaconda scripts (qubes-os.py), I noticed this call:

qvm-template-postprocess --really 'post-install' fedora-26 /var/lib/qubes/vm-templates/fedora-26

Tried running it, but it produces a lot of errors, final one:

qubesadmin.exc.QubesDaemonNoResponseError: Got empty response from qubesd. See journalctl in dom0 for details.

Can you please let me know what should I focus on, to complete configuring the templates, and other standard qubes (sys-net, sys-firewall, personal, work...)? At this point obviously the system doesn't have the network access.

[awokd]

On Wed, February 7, 2018 3:28 am, dbr287 wrote:
> I've installed rc4 on G505S with Coreboot (legacy bios). Installation
> went ok (found iommu and interrupt remapping just fine).
>
> On 1st (gui) boot, I've tried all the combinations selecting 1) create
> ServiceVMs, AppVMs, 2) only ServiceVMs, 3) only configure templates,...
> but none works. It always hangs at Configuring 1st template (usually
> debian-9).

You probably need to manually add this patch
https://review.coreboot.org/#/c/coreboot/+/22843/ to your coreboot image.
Also, disable XHCI (two options right next to each other in menuconfig.)

If it continues to hang on sys-net creation, try pulling the wireless card
before installing Qubes. It will still create a sys-net qube containing
the onboard ethernet, but then you can add the wireless card back and
troubleshoot on a full system.

[dbr287]

Thanks!

This worked fine. Applied 2 patches, and rebuild coreboot, flashed, and re-ran R4.0rc4 install, works like a charm. Thanks again for the prompt response.

[awokd]

On Thu, February 8, 2018 1:58 am, dbr287 wrote:

> This worked fine. Applied 2 patches, and rebuild coreboot, flashed, and
> re-ran R4.0rc4 install, works like a charm. Thanks again for the prompt
> response.

Great! They are pretty unique laptops.

PS Don't suppose you (or anyone else reading and interested) are any good
at C++? Would be nice to get that Coreboot patch re-activated and working
properly. I can usually hack my way around code but that AGESA code base
is beyond my skill-set.