Hello,
Cyril Brulebois, le jeu. 01 juin 2023 21:12:18 +0200, a ecrit:
> Do we have other ttys than just tty1 that people might want to switch
> to, and that might benefit from a similar adjustment?
This script is actually not used for the other consoles, so it has never
had any effect on them on
Emanuele Rocca, le jeu. 01 juin 2023 15:11:53 +0200, a ecrit:
> On 2023-05-31 05:46, Samuel Thibault wrote:
> > I'd rather see a patch like
> >
> > if [ "$TERM" = vt102 -a `tty` = /dev/tty1 ] ; then
> > # Busybox's init uses a global TERM across all consoles.
> > # If the serial
Hi everyone,
Thanks for tracking down why the strange vt102 thing happens, and why it
mostly happens/was mostly reported on arm64 hardware… The patch below
(or further variations should there be any) looks mergeable to me.
Emanuele Rocca (2023-06-01):
> On 2023-05-31 05:46, Samuel Thibault
On 01/06/2023 16:27, Emanuele Rocca wrote:
> Hi again,
>
> On 2023-05-31 05:46, Samuel Thibault wrote:
>> The problem is that both are frown-prone. I guess there is a reason why
>> on arm the default console is set to the serial port, e.g. for simpler
>> debugging or something like that.
>
>
Hi again,
On 2023-05-31 05:46, Samuel Thibault wrote:
> The problem is that both are frown-prone. I guess there is a reason why
> on arm the default console is set to the serial port, e.g. for simpler
> debugging or something like that.
Also worth mentioning: there is no bug on real hardware
Hi,
On 2023-05-31 05:46, Samuel Thibault wrote:
> I'd rather see a patch like
>
> if [ "$TERM" = vt102 -a `tty` = /dev/tty1 ] ; then
> # Busybox's init uses a global TERM across all consoles.
> # If the serial console is the default such as on arm64, that
> # will force
Emanuele Rocca, le mer. 31 mai 2023 17:29:31 +0200, a ecrit:
> > 1. Why is aarch64 special here?
> > 2. Where does that difference come from?
>
> According to Jessica Clarke this is due to busybox using vt102:
> https://society.oftrolls.com/@jrtc27@mastodon.social/110459684352427882
Is it
Hi,
On Tue, May 30, 2023 at 09:08:45PM +0200, Cyril Brulebois wrote:
> 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
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
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,
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
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
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
13 matches
Mail list logo
