Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1148945 > unrolled thread

Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Hector Oron Martinez <zumbi@debian.org> - 2023-06-07 12:20 +0200
    Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Cyril Brulebois <kibi@debian.org> - 2023-06-07 12:40 +0200
      Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Hector Oron <zumbi@debian.org> - 2023-06-07 12:40 +0200
        Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Cyril Brulebois <kibi@debian.org> - 2023-06-07 13:10 +0200
          Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Hector Oron <zumbi@debian.org> - 2023-06-07 13:40 +0200
            Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system Cyril Brulebois <kibi@debian.org> - 2023-06-07 13:40 +0200

#1148945 — Bug#1037186: debian-installer: bookworm d-i graphics are not shown on Raptor system

Source: debian-installer
Version: 20230526
Severity: important
X-Debbugs-Cc: tpearson@raptorcs.com, zumbi@debian.org

Hello,

    We found latest installer for bookworm is missing ast DRM kernel module, causing graphical failure on ppc64el Raptor machines. Could you please consider the following change or similar for the debian-installer bookworm release.

  https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34

Regards

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE=ca_ES:ca
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]

#1148948

[Multipart message — attachments visible in raw view] — view raw

Hi,

Hector Oron Martinez <zumbi@debian.org> (2023-06-07):
> We found latest installer for bookworm is missing ast DRM kernel
> module, causing graphical failure on ppc64el Raptor machines. Could
> you please consider the following change or similar for the
> debian-installer bookworm release.
> 
>   https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34

Thanks for the patch, but this is too late. We can consider that for
unstable, and later on via a point release.

I know for a fact we have fbdev in ppc64el builds, as we've suffered a
regression there (#1033058, for which someone still needs to find a real
fix on the kernel side, hint hint wink wink); isn't that generic driver
sufficient to get some basic output?

Also, I don't understand what's going on with the build/Makefile part:
 1. This is a temporary workaround for 3 architectures that run into
    issues under UEFI/SB, which isn't quite relevant for ppc64el. (The
    idea was to avoid having to re-upload linux and linux-signed-* for
    just a few additions to the fb-modules udeb.)
 2. If you look at the following commit, I suppose you'll get the very
    same impression as I have: this merge request is very likely to
    trigger a direct FTBFS on ppc64el.
      https://salsa.debian.org/installer-team/debian-installer/-/commit/32e4d58c263fc5454067a7217ee7103cfb12bc1b


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#1148949

Hello,

  To be honest, I only updated ppc64el netboot image with the following patch:

--- a/build/pkg-lists/netboot/ppc64el.cfg
+++ b/build/pkg-lists/netboot/ppc64el.cfg
@@ -1,5 +1,6 @@
 input-modules-${kernel:Version}
 nic-modules-${kernel:Version}
+fb-modules-${kernel:Version} ?
 usb-modules-${kernel:Version}
 virtio-modules-${kernel:Version} ?

I built the installer posted at:
https://people.debian.org/~zumbi/netboot_ppc64el/

and Timonthy was able to test that. I could expand the change to ppc64
(be) and cdrom targets and test that.

Note, the ppc64el installer images are unusable with that change, at
least on the Raptor systems, and since the change only affects power
package lists, I'd consider it as low impact/risk. I know we are close
to a release, and it is very bad timing, however if it can be merged,
it'd be great, otherwise we'll have to wait until the first point
release.

Thanks for your support.

On Wed, 7 Jun 2023 at 12:29, Cyril Brulebois <kibi@debian.org> wrote:
>
> Hi,
>
> Hector Oron Martinez <zumbi@debian.org> (2023-06-07):
> > We found latest installer for bookworm is missing ast DRM kernel
> > module, causing graphical failure on ppc64el Raptor machines. Could
> > you please consider the following change or similar for the
> > debian-installer bookworm release.
> >
> >   https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/34
>
> Thanks for the patch, but this is too late. We can consider that for
> unstable, and later on via a point release.
>
> I know for a fact we have fbdev in ppc64el builds, as we've suffered a
> regression there (#1033058, for which someone still needs to find a real
> fix on the kernel side, hint hint wink wink); isn't that generic driver
> sufficient to get some basic output?
>
> Also, I don't understand what's going on with the build/Makefile part:
>  1. This is a temporary workaround for 3 architectures that run into
>     issues under UEFI/SB, which isn't quite relevant for ppc64el. (The
>     idea was to avoid having to re-upload linux and linux-signed-* for
>     just a few additions to the fb-modules udeb.)
>  2. If you look at the following commit, I suppose you'll get the very
>     same impression as I have: this merge request is very likely to
>     trigger a direct FTBFS on ppc64el.
>       https://salsa.debian.org/installer-team/debian-installer/-/commit/32e4d58c263fc5454067a7217ee7103cfb12bc1b
>
>
> Cheers,
> --
> Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
> D-I release manager -- Release team member -- Freelance Consultant



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

[toc] | [prev] | [next] | [standalone]

#1148952

[Multipart message — attachments visible in raw view] — view raw

Hector Oron <zumbi@debian.org> (2023-06-07):
> and Timonthy was able to test that. I could expand the change to ppc64
> (be) and cdrom targets and test that.
> 
> Note, the ppc64el installer images are unusable with that change, at
> least on the Raptor systems

I don't think you answered my question about fbdev.

> and since the change only affects power package lists, I'd consider it
> as low impact/risk. I know we are close to a release, and it is very
> bad timing however if it can be merged, it'd be great, otherwise we'll
> have to wait until the first point release.

If you look at the work that's been going on during the last few
months on the -boot or -cd side, I think it's fair to say I have been
very accommodating, trying hard to satisfy as many reasonable requests
as possible, balancing those against possible risks. We've got some
extensive and appreciated leeway/flexibility, but at some point, I
have to draw a line.

That line was drawn a few hours ago.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [next] | [standalone]

#1148957

[Multipart message — attachments visible in raw view] — view raw

Hello

El mié, 7 jun 2023, 13:03, Cyril Brulebois <kibi@debian.org> escribió:

> Hector Oron <zumbi@debian.org> (2023-06-07):
> > and Timonthy was able to test that. I could expand the change to ppc64
> > (be) and cdrom targets and test that.
> >
> > Note, the ppc64el installer images are unusable with that change, at
> > least on the Raptor systems
>
> I don't think you answered my question about fbdev.
>

I defer to Timothy since I do not have a machine myself, but since Raptorcs
is Debian partner I had assumed we - Debian - would like to ship a working
product that works for them.

Thanks for your support

>

[toc] | [prev] | [next] | [standalone]

#1148958

[Multipart message — attachments visible in raw view] — view raw

Hi,

Hector Oron <zumbi@debian.org> (2023-06-07):
> El mié, 7 jun 2023, 13:03, Cyril Brulebois <kibi@debian.org> escribió:
> 
> > Hector Oron <zumbi@debian.org> (2023-06-07):
> > > and Timonthy was able to test that. I could expand the change to ppc64
> > > (be) and cdrom targets and test that.
> > >
> > > Note, the ppc64el installer images are unusable with that change, at
> > > least on the Raptor systems
> >
> > I don't think you answered my question about fbdev.
> >
> 
> I defer to Timothy since I do not have a machine myself, but since Raptorcs
> is Debian partner I had assumed we - Debian - would like to ship a working
> product that works for them.

I'm happy to help. That just needs to happen *before* final preparations
have happened!


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web