Bug#1036952: rootskel: text installs on aarch64 lack glyphs for many languages

[Samuel Thibault]

Samuel Thibault, le mar. 30 mai 2023 21:21:51 +0200, a ecrit:
> Samuel Thibault, le mar. 30 mai 2023 21:16:46 +0200, a ecrit:
> > I'm wondering what kind of console aarch64 is using: is that the Linux
> > virtual Terminal on an fbdev, or a ttyS console? Something else? The
> > kernel boot logs could be useful to determine that.
> 
> Ah, https://openqa.debian.net/tests/151286/logfile?filename=serial0.txt
> provides it.
> 
> May 30 06:37:27 init: starting pid 246, tty '/dev/ttyAMA0': 
> '/sbin/debian-installer'
> May 30 06:37:27 init: starting pid 247, tty '/dev/tty1': 
> '/sbin/debian-installer'
> 
> So it might be "something else" :) Is the shown output from ttyAMA0, or
> tty1?

Also, to be noted:

May 30 06:37:27 kernel: [0.531174] Run /init as init process
May 30 06:37:27 kernel: [0.531176]   with arguments:
May 30 06:37:27 kernel: [0.531177] /init
May 30 06:37:27 kernel: [0.531178] ---
May 30 06:37:27 kernel: [0.531179]   with environment:
May 30 06:37:27 kernel: [0.531180] HOME=/
May 30 06:37:27 kernel: [0.531181] TERM=linux
May 30 06:37:27 kernel: [0.531181] BOOT_IMAGE=/install.a64/vmlinuz

So init does get started with TERM=linux, not vt102. So it's something
in-between that seems to be setting that.

Samuel

Bug#1036952: rootskel: text installs on aarch64 lack glyphs for many languages

[Samuel Thibault]

Samuel Thibault, le mar. 30 mai 2023 21:16:46 +0200, a ecrit:
> I'm wondering what kind of console aarch64 is using: is that the Linux
> virtual Terminal on an fbdev, or a ttyS console? Something else? The
> kernel boot logs could be useful to determine that.

Ah, https://openqa.debian.net/tests/151286/logfile?filename=serial0.txt
provides it.

May 30 06:37:27 init: starting pid 246, tty '/dev/ttyAMA0': 
'/sbin/debian-installer'
May 30 06:37:27 init: starting pid 247, tty '/dev/tty1': 
'/sbin/debian-installer'

So it might be "something else" :) Is the shown output from ttyAMA0, or
tty1?

Samuel

Bug#1036952: rootskel: text installs on aarch64 lack glyphs for many languages

[Samuel Thibault]

Hello,

Cyril Brulebois, le mar. 30 mai 2023 21:08:45 +0200, a ecrit:
> Philip Hands  (2023-05-30):
> > Apparently, this MR fixes the problem:
> > 
> >   https://salsa.debian.org/installer-team/rootskel/-/merge_requests/8
> > 
> > Although this does prompt the question of why aarch64 has TERM set to
> > 'vt102' at this point, rather than 'linux'.
> 
> Glancing at the merge request earlier, my first (intertwined) questions
> were:
> 
>   1. Why is aarch64 special here?
>   2. Where does that difference come from?

I'm wondering what kind of console aarch64 is using: is that the Linux
virtual Terminal on an fbdev, or a ttyS console? Something else? The
kernel boot logs could be useful to determine that.

Samuel

>   3. Which other architectures might be impacted if we were to change
>  that?
> 
> > Also, I wonder whether there could be other circumstances when $TERM
> > is set to 'vt102' where this change could be problematic (I'm guessing
> > that the $TERM_TYPE checks deal with that, but I'm not sure).
> 
> Yeah, that's the same kind of questions one would get by combined my
> second and third questions…

Bug#1036952: rootskel: text installs on aarch64 lack glyphs for many languages

[Cyril Brulebois]

Hi,

Philip Hands  (2023-05-30):
> Apparently, this MR fixes the problem:
> 
>   https://salsa.debian.org/installer-team/rootskel/-/merge_requests/8
> 
> Although this does prompt the question of why aarch64 has TERM set to
> 'vt102' at this point, rather than 'linux'.

Glancing at the merge request earlier, my first (intertwined) questions
were:

  1. Why is aarch64 special here?
  2. Where does that difference come from?
  3. Which other architectures might be impacted if we were to change
 that?

> Also, I wonder whether there could be other circumstances when $TERM
> is set to 'vt102' where this change could be problematic (I'm guessing
> that the $TERM_TYPE checks deal with that, but I'm not sure).

Yeah, that's the same kind of questions one would get by combined my
second and third questions…



Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1036952: rootskel: text installs on aarch64 lack glyphs for many languages

[Philip Hands]

Package: rootskel
Version: 1.135
Severity: normal
Tags: patch

Hi,

One can see the symptoms by looking here:

  https://openqa.debian.net/tests/151286

the orange "Soft Failed" boxes highlight some of the failing screens, where the
failure can be seen in the screenshot immediately preceeding the "Soft Failed"

I'll attach an example to save people from having to follow that link.

Apparently, this MR fixes the problem:

  https://salsa.debian.org/installer-team/rootskel/-/merge_requests/8

Although this does prompt the question of why aarch64 has TERM set to 'vt102' at
this point, rather than 'linux'.

Also, I wonder whether there could be other circumstances when $TERM is set to
'vt102' where this change could be problematic (I'm guessing that the $TERM_TYPE
checks deal with that, but I'm not sure).

BTW This seems to have some overlap with #263137.

Cheers, Phil.

Re: os-prober not detecting distros mounting ESP as /boot

[Pascal Hambourg]

On 30/05/2023 at 03:53, Avid Seeker wrote:

1) Layout:
/dev/sda1: ESP

and in both distros /boot is the mount point of ESP.


I expected a much more detailed description.
- Full partition layout and use
- Full contents of the ESP

So technically no content on /boot if ESP not mounted.

As I wrote previously, os-prober does not care about /boot and 
linux-boot-prober can mount it so it does not matter that /boot is separate.



2) os-prober outputs empty string
3) linux-boot-prober outputs empty string


Please post the full commands.