Re: Firmware GR result - what happens next?

[Steve McIntyre]

Hi Pascal,

On Fri, Oct 14, 2022 at 09:57:37PM +0200, Pascal Hambourg wrote:
>On 14/10/2022 at 21:49, Holger Wansing wrote:
>> 
>> Pascal Hambourg  wrote (Fri, 14 Oct 2022 21:31:31 
>> +0200):
>> > > > > As far as I understand it, they can be packaged once their
>> > > > > redistributability is clarified?
>> > > 
>> > > The only way for the installer to make use of such firmware is, if the
>> > > user provides the firmware files on a removable device, like an USB 
>> > > stick.
>> > 
>> > This is my point. If Debian does not provide all firmware for drivers
>> > which are included into the installer, then support for extra firmware
>> > medium is still useful and should not be removed.
>> 
>> For this specific case (use of firmware files, which are not available in
>> Debian) there is no need for a special installer medium.
>
>I did not mention the need for any special installer medium, only the need
>for the installer to support extra firmware medium.
>
>> The usual installer also has the capability to make use of firmware
>> provided via USB.
>
>It was suggested in this thread to remove this feature.

ACK, that was our thought. Thanks for pointing out the issue here,
it's appreciated!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect."
  -- Bruce Schneier

debootstrap_1.0.128+nmu1 uploaded to DELAYED/1 (was: Re: debootstrap_1.0.128_source.changes ACCEPTED into unstable)

[Luca Boccassi]

Hi,

I have uploaded debootstrap_1.0.128+nmu1 to DELAYED/1, as 1.0.128 added
a new autopkgtest that fails in Debian because we still don't have
/usr/sbin in the default PATH (I guess it wasn't noticed in Ubuntu
because that's not an issue there).
The autopkgtest failure was holding back migration to testing.

MR: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/82

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Processing of debootstrap_1.0.128+nmu1_source.changes

[Debian FTP Masters]

debootstrap_1.0.128+nmu1_source.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.128+nmu1.dsc
  debootstrap_1.0.128+nmu1.tar.gz
  debootstrap_1.0.128+nmu1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

[Olaf Meeuwissen]

Package: debian-installer
Version: 20220917
Severity: normal
Tags: d-i

Dear Maintainer,

I recently tried this version with hardware that triggers loading of the
mt7921e kernel module.  Loading the module fails due to a firmware file
load error but the installer starts okay.  However, the installer later
crashes when probing for network hardware (when it tries to rmmod the
kernel module).

Since the hardware has 2 additional wired NICs that work fine (and I
wanted to do an air-gap install anyway!), I decided to blacklist the
module.

The first issue I ran into was that the documented[1] way to blacklist
kernel modules is no longer correct

 [1]: 
https://www.debian.org/releases/testing/amd64/ch05s03.en.html#module-blacklist

Instead of

  mt7921e.blacklist=yes

I had to use

  modprobe.blacklist=mt7921e

to prevent the kernel from loading the module (between the boot menu and
starting the installer proper).  With the latter appended to the `linux`
line of the boot menu entry, the installation appeared to have completed
without problems.

However, upon booting I saw a pile of ATA bus and I/O errors that made
me suspicious.  The disk is brand new and a smartmontools extended test
reports no errors.

I found a /etc/modprobe.d/blacklist.local.conf file with

  blacklist modprobe

Removing that file made the ATA bus and I/O errors go away.

For completeness' sake, the /etc/default/grub file included

  GRUB_CMDLINE_LINUX="modprobe.blacklist=mt7921e"

so the offending module is not loaded upon reboot after installation.

Seeing that the kernel boot argument is added correctly to the GRUB
configuration, there is no need to create a file in /etc/modprobe.d/.
In addition, the installation manual needs to be updated to use the
correct syntax.

Hope this helps,

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled
-- 
Olaf Meeuwissen

Re: debootstrap_1.0.128+nmu1 uploaded to DELAYED/1 (was: Re: debootstrap_1.0.128_source.changes ACCEPTED into unstable)

[Dimitri John Ledkov]

Ack, will look into it

On Mon, 17 Oct 2022, 10:50 Luca Boccassi,  wrote:

> Hi,
>
> I have uploaded debootstrap_1.0.128+nmu1 to DELAYED/1, as 1.0.128 added
> a new autopkgtest that fails in Debian because we still don't have
> /usr/sbin in the default PATH (I guess it wasn't noticed in Ubuntu
> because that's not an issue there).
> The autopkgtest failure was holding back migration to testing.
>
> MR:
> https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/82
>
> --
> Kind regards,
> Luca Boccassi
>

Bug#1021919: virtionet device not found in debian testing netinst ISO 20221017

[Laurent GUERBY]

Package: debian-installer
Severity: important

Hi,

Trying to install the testing netinst ISO in a VM (in proxmox):

https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-te
sting-amd64-netinst.iso

The issue is that the installer fails to find an ethernet card which is
there in lspci (virtio ethernet from proxmox).

Note : same VM under proxmox (just changing the ISO) finds the ethernet
card with officiel debian 11 netinst ISO.

Sincerely,

Laurent

Bug#1021919: virtionet device not found in debian testing netinst ISO 20221017

[Cyril Brulebois]

Hi Laurent,

Laurent GUERBY  (2022-10-17):
> Trying to install the testing netinst ISO in a VM (in proxmox):
> 
> https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-te
> sting-amd64-netinst.iso
> 
> The issue is that the installer fails to find an ethernet card which is
> there in lspci (virtio ethernet from proxmox).
> 
> Note : same VM under proxmox (just changing the ISO) finds the ethernet
> card with officiel debian 11 netinst ISO.

I'm seeing BFP issues, similar to those reported here:
  https://bugs.debian.org/1003210

except for the virtio_net module. Checking /var/lib/dpkg/status, it
looks like we have kernel-image from 5.19.11-1 and nic-modules from
5.19.11-1+b1, which would mean kernel and modules from a different
build, which was flagged in #1003210 as possibly problematic.

Looping in kernel maintainers to get some input, and debian-cd for
information given the way testing images are built…


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


signature.asc
Description: PGP signature

Bug#1021922: console-setup: FTBFS make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2

[Michael Biebl]

Source: console-setup
Version: 1.210
Severity: serious
Tags: ftbfs

console-setup FTBFS in unstable

gzip -9n >/acm/VISCII.acm >/<>/acm/VISCII.acm.gz
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-Fixed15.log  
/<>/Fonts/bdf/9x15-IL2.bdf+/<>/Fonts/bdf/9x15.bdf+/<>/Fonts/bdf/9x15c.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-Fixed15.psf 
/<>/Fonts/Arabic-Fixed15.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-Fixed16.log  
/<>/Fonts/bdf/georgian16.bdf+/<>/Fonts/bdf/unifont.bdf+/<>/Fonts/bdf/h16.bdf+/<>/Fonts/bdf/etl16-unicode.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-Fixed16.psf 
/<>/Fonts/Arabic-Fixed16.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-VGA14.log  
/<>/Fonts/bdf/legacy14i.bdf+/<>/Fonts/bdf/legacy14f.bdf+/<>/Fonts/bdf/legacy14l.bdf+/<>/Fonts/bdf/legacy14b.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-VGA14.psf 
/<>/Fonts/Arabic-VGA14.sfm
umask 022; /<>/Fonts/bdf2psf --log 
/<>/Fonts/Arabic-VGA16.log  
/<>/Fonts/bdf/u_vga16_fix.bdf+/<>/Fonts/bdf/u_vga16.bdf+/<>/Fonts/bdf/legacy16c.bdf+/<>/Fonts/bdf/legacy16f.bdf+/<>/Fonts/bdf/legacy16k.bdf
  /<>/Fonts/standard.equivalents \

/<>/Fonts/ascii.set+/<>/Fonts/linux.set+/<>/Fonts/fontsets/Arabic.512+:/<>/Fonts/useful.set
 512 /<>/Fonts/Arabic-VGA16.psf 
/<>/Fonts/Arabic-VGA16.sfm
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-Fixed15.psf] Error 
2
make: *** Waiting for unfinished jobs
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-Fixed16.psf] Error 
2
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA14.psf] Error 2
/<>/Fonts/bdf2psf: /<>/console-setup-1.210: No such file 
or directory
make: *** [Fonts/Makefile:338: /<>/Fonts/Arabic-VGA16.psf] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2



Full build log available at
https://buildd.debian.org/status/fetch.php?pkg=console-setup&arch=all&ver=1.210%2Bnmu1&stamp=1665832544&raw=0