At 01:19 06/09/2019, 'awokd' via qubes-users wrote:
>How about connecting the external (HDMI audio supporting) monitor? If
>it's the issue I linked, maybe making HDMI audio use an interrupt will
>work around it.
Sorry, did not mention it explicitly, but yes I did try this and no, there was
the sa
Hi Awokd,
>Thanks. Hope I'm not leading you on a wild goose chase.
Most tech things are once you get involved in the details ;-)
>That odd interrupt changed in Debian. I wonder if it is
>https://www.spinics.net/lists/kernel/msg2709360.html. Link is to a
>kernel issue that was occurring with i915
The below info was collected from a debian running on the B116-M. Have added
/poc/cpuinfo for completeness (see below).
Thanks for your looking into this!
At 19:55 01/09/2019, 'awokd' via qubes-users wrote:
>'awokd' via qubes-users:
>> 'awokd' via qubes-users:
>>
HYP: 0
The requested details are inline below.
I really appreciate you looking into this - Thanks. If there are any other
thoughts and ideas to try to isolate the problem am happy to try and revert.
At 20:21 31/08/2019, 'awokd' via qubes-users wrote:
>>> At 23:22 28/08/2019, 'awokd' via qubes-users wro
.
At 13:16 29/08/2019, Guest wrote:
>Awokd,
>
>One of the machines is a B117-M and the other is a B116-M. The previous boot
>debug is from the B116-M.
>
>1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and
>B117-M respectively - still getting the
At 14:04 29/08/2019, unman wrote:
>I have to point out that you can run Qubes fine with HDD and 12GB RAM -
>even 8GB is doable.
>quick ebay suggests you can get x230 with *that* config regularly for less than
>$200 - i7 with 16GB went for $175 recently.
>If you drop down to an i5 (still workable) y
Awokd,
One of the machines is a B117-M and the other is a B116-M. The previous boot
debug is from the B116-M.
1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and
B117-M respectively - still getting the KERNEL PANIC on both machines.
2) Tried disabling all non essential
