Hi,
I'm glad to say that just now I upgraded to the unstable kernel:
$ sudo apt-get install linux-image-amd64
and now I can boot normally:
$ uname -a
Linux debian 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64
GNU/Linux
I'm curious: I'd like to see the changelog and the code
to see w
Hi,
I suspect it may have to do with the 5th gen (Broadwell Desktop) only,
as they have a very special (and powerful) iGPU.
And maybe that's why the bug passed inadvertently so much time:
those CPUs didn't sell very well.
Yes, I have that package installed:
||/ NameVersion Archi
Hi,
I received no answer at all, so I guess you are very busy.
I know the bug was introduced somewhere between 5.6 and 5.7.
If you have an idea of what the source of the bug could be,
I'd like to help by testing on my computers,
or providing code.
I have two computers with similar CPUs (i5-5675
I tried booting in recovery mode,
and it also didn't work.
However, I could see the some info.
The 3 last lines of the boot log were:
{
[4.817936] hub 4-0:1.0: 2 ports detected
[4.819372] i915 :00:02.0: [drm] Found 128MB of eDRAM
[4.819882] fb0: switching to inteldrmfb from EFI VG
I tried installing the new kernel from unstable,
but I still can't boot with it.
Same problems.
5 matches
Mail list logo
