(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: CD, netboot
Image version: d-i daily image, bookworm installer RC3
Date: 19-05-2023 13:30 UTC+8

Machine: VirtualBox 7.0.x
Partitions: empty disk, on a new vm instance


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [E]
Detect network card:    [ ]
Configure network:      [ ]
Detect media:           [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:

Boot the installer in EFI on virtualbox 7.0.x, select every install options
and all results in a grey screen if in text mode and an error can't
open display:0 on graphical gtk mode. In BIOS mode, everything works fine
In stable (bullseye), the issue is not present, most probably a bookworm
issue, similar bug report has been filed by another user on virtualbox
bug tracking system.


Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the
installer system in /var/log/ and later on the installed system
under /var/log/installer.) Please compress large files using gzip.

Hi Ismail,

Ismail Arif <ismxilxrif@gmail.com> (2023-05-19):

Nice! Could you please test an image for me and tell me if it helps?
https://people.debian.org/~kibi/bug-drm-vs-uefi/mini-hackhackhack.iso

Backstory is https://bugs.debian.org/1036019 for similar issues with
different graphics adapter under QEMU, only in UEFI mode; I wanted to
include the VirtualBox DRM module at first but couldn't find anyone to
reproduce the issue first, so I dropped that part for RC 3. It's trivial
to add back to my workaround if you can confirm if helps.

(And when I say “nice” I mean I'm sorry you're experiencing troubles,
but your bug report has very interesting details, which we were lacking
from other older bug reports, which were pretty vague.)


Cheers,

Hello there,

Thanks for the response, I've downloaded and tried to run the installer by
using the iso provided, however the issue still persists, I have a
screenshot of the error that i believe is still the same error that I
received before.

Hello there,

Thanks for the response, I've downloaded and tried to run the installer by
using the iso provided, however the issue still persists, I have a
screenshot of the error that i believe is still the same error that I
received before.

Ismail Arif <ismxilxrif@gmail.com> (2023-05-19):

So I'm seeing different errors on that screen. The fbdev video driver
tends to trigger error messages but those shouldn't be an issue. The
core keyboard thing seems more serious.

I'll try and provide you with a full netinst image, so that you have
both Graphical Install and (text…) Install options. My patch should fix
graphics-related issues, in both text and graphical modes. At first
glance it looks like your X might have another issue preventing it from
starting.

Could you please share a screenshot of the grey screen when booting the
RC 3 in text mode?


Cheers,

Cyril Brulebois <kibi@debian.org> (2023-05-19):

https://people.debian.org/~kibi/bug-drm-vs-uefi/netinst-hackhackhack+vbox.iso

(Since its size isn't negligible, it's scheduled for deletion two weeks
from now.)


Cheers,

Here's the screenshot for both the graphical and text modes,

First file should be the graphical mode, and the second is the grey screen
in text mode

The grey screen is kind of like a background for a shell, but typing and
entering any words or commands of any kind seems to be useless (no command
output, the commands typed appears but that's just it)

The third screenshot is where I tried to type any words/commands. but the
installer does respond to ctrl+alt+del signal which rebooted the vm

Here's the screenshot for both the graphical and text modes,

First file should be the graphical mode, and the second is the grey screen
in text mode

The grey screen is kind of like a background for a shell, but typing and
entering any words or commands of any kind seems to be useless (no command
output, the commands typed appears but that's just it)

The third screenshot is where I tried to type any words/commands. but the
installer does respond to ctrl+alt+del signal which rebooted the vm

Seems the problem still persists on both modes, so it might be something
else.

In bullseye there's no such issues

Trying to run the vm in windows too seems to output the same issue.

Either it's a virtualbox issue or a bookworm issue is yet to be identified,
as booting the image on my baremetal efi seems fine, also in vmware
workstation, there is no issue.

Ismail Arif <ismxilxrif@gmail.com> (2023-05-19):

Yeah, from the screenshot you shared, it didn't look like the same
framebuffer issue I've been chasing lately (wrong width, height, bits
per pixel being reported, leading to corrupted graphics in both modes).

I'll keep *not* including vboxvideo.ko at this time, and we'll need
someone to understand what's going on, or at least what changed and
when…

If you feel like walking down memory lane, you could try earlier Alpha
or RC releases, and let us know which one(s) is(are) affected by this
issue. You'll find all netinst images under these directories:
https://cdimage.debian.org/cdimage/bookworm_di_alpha1/amd64/iso-cd/
https://cdimage.debian.org/cdimage/bookworm_di_alpha2/amd64/iso-cd/
https://cdimage.debian.org/cdimage/bookworm_di_rc1/amd64/iso-cd/
https://cdimage.debian.org/cdimage/bookworm_di_rc2/amd64/iso-cd/
https://cdimage.debian.org/cdimage/bookworm_di_rc3/amd64/iso-cd/

Thanks for the report and your follow-ups so far!


Cheers,

I've downloaded and tested the images. and it seems the issue has been
present since alpha 1

Hi,

Encountering the same issue, I can confirm it still persists in RC4.
However, digging a bit deeper with the error I found on dmesg: "x86/PAT:
bterm:260: map pfn expected mapping type uncached-minus for ..., got
write-combining", I found this workaround:
Disabling paravirtualization in virtualbox acceleration or switching it to
legacy results in a properly booting installer.

Kind regards,
Erwin

Hello Erwin,
Thanks a lot for work-around advise ;)

Sorry for late answer but I just read it and give a try to "Disabling paravirtualization in virtualbox acceleration"
(i.e. VBox GUI, in the 'Settings...' of the VM, go to 'System' panel than in the 'Acceleration' tab select 'None' as
'Paravirtualization Interface' ;))

This help me to install like this a Debian-12.5 DVD as a simple SSH server on VBox release is 7.0.18 ;)

For what is weird: once the installation is completed , I can switch back the 'Paravirtualization Interface' to 'Default' (
even with 'Secure boot' enabled ;) )

Thanks a lot again,
Rudy S.