OK, you can close this ticket.
The problem was that I had "auto" instead of "auto=true" in the boot command.
That has worked in previous releases...
Moving those to boot command did not help me.
But I'd be interested to know more about the "second console" where I can see
some errors. Currently I have no idea what that is.
My packer boot-command config (and pre-seed does not have any
locale/country/language set now):
Hi,
"Marko, Peter" wrote:
> Unfortunately none of the suggested options work for me.
> - using spaces
> - using language/locale C and supported-locales en_US.UTF-8
> - using bullseye
>
> Could you get it working to preseed any non-EN country together with EN
> language/locale?
> Adding tests
Unfortunately none of the suggested options work for me.
- using spaces
- using language/locale C and supported-locales en_US.UTF-8
- using bullseye
Could you get it working to preseed any non-EN country together with EN
language/locale?
Adding tests for preseeding with settings mentioned in the
On 8/2/2020 3:10 PM, Holger Wansing wrote:
Hi,
one wrote (7 Feb 2020 08:39:02):
d-i debian-installer/language string en
d-i debian-installer/countrystring CH
d-i debian-installer/locale string en_US.UTF-8
From my testing this should be basically the correct
Hi,
one wrote (7 Feb 2020 08:39:02):
> d-i debian-installer/language string en
> d-i debian-installer/countrystring CH
> d-i debian-installer/locale string en_US.UTF-8
>From my testing this should be basically the correct parameters, however
when looking at
6 matches
Mail list logo
