On Wednesday, 17 January 2018 19:24:05 UTC, Krišjānis Gross wrote:
> Hi,
>
> Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my
> hardware.
>
> Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is
> started. no other VM is started unfortuna
On Thu, January 25, 2018 7:19 pm, Krišjānis Gross wrote:
>
> here it is (attached). Hope that helps!
>From the journal:
Jan 25 20:53:15 localhost.localdomain kernel: [drm] The driver support for
your hardware in this kernel version is alpha quality
Se
On Wed, January 24, 2018 7:09 pm, Krišjānis Gross wrote:
>
> I can not find a kern.log or dmesg. I did find the Xorg log files. (This
> is all on the Fedora that I recently installed on this same hardware).
> Xorg Log files attached.
Try "sudo journalctl -b > journal.log". Review and redact any s
On Wednesday, 17 January 2018 21:24:05 UTC+2, Krišjānis Gross wrote:
> Hi,
>
> Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my
> hardware.
>
> Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is
> started. no other VM is started unfortu
On 01/23/2018 06:11 PM, Krišjānis Gross wrote:
>
> Managed to install Fedora on this hardware and here is the boot.log that I
> can find in /var/log
>
> Does that help to understand the issue?
>
It does not seem a very useful log. Send something like kern.log or
dmesg. Also Xorg.X.log since yo
On Wednesday, 17 January 2018 21:24:05 UTC+2, Krišjānis Gross wrote:
> Hi,
>
> Was using Qubes 3.2 on 4th generation i5 processor when decided to upgrade my
> hardware.
>
> Purchased 8th gen i5 processor and MB. Now when I start my Qubes only dom0 is
> started. no other VM is started unfortu
@ Foppe de Haan
>Most likely due to lacking hardware support (in the kernel) for the CL
>>graphics chip (even though it's little more than a rebrand of KL's). Try
>>installing a more recent (ideally 4.14-based) kernel. Iow, it's sort of
>>related, because the issues you
Please suggest how to in
