Bug#982422: debootstrap: segmentation fault around ldconfig during debootstrapping bullseye/arm64 on a buster/amd64 host

[Josef Hahn]

Yes, indeed! Great! I've just tried with qemu-user-static from buster-
backports, and it seems to be fine.


On Thu, 2021-02-11 at 13:32 -0600, Dick Hollenbeck wrote:
> I upgraded to the latest qemu-user-static using a manual download of
> the *.deb from packages.ubuntu.com and installed
> using dpkg -i.
> 
> This fixed the problem.  So the bug must have been in qemu-user-
> static.
> 

Re: state of shim and shim-signed.

[Steve McIntyre]

Thanks KiBi, was about to respond via d-boot anyway. :-)

On Thu, Feb 11, 2021 at 11:59:44PM +0100, Cyril Brulebois wrote:
>
>peter green  (2021-02-11):
>> I have noticed that there seem to be issues with shim and shim-signed,
>> the former has a complaint from the gcc maintainers about being built
>> with an old version of gcc, the latter depends on an old version of shim.
>> 
>> Are their plans to fix this for bullseye? are their difficulties getting
>> new versions signed by MS?

I'm doing some shim work at the moment, in fact. I'm not anticipating
any problems with getting things signed, but there will be at least
some delay. That delay *does* act as somewhat of a brake on shim
maintenance, hence I've let things sit for some time.

Now that we're near the end of the bullseye cycle and toolchains have
settled, I'm comfortable to switch to gcc-10 etc.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Re: state of shim and shim-signed.

[Cyril Brulebois]

peter green  (2021-02-11):
> I have noticed that there seem to be issues with shim and shim-signed,
> the former has a complaint from the gcc maintainers about being built
> with an old version of gcc, the latter depends on an old version of shim.
> 
> Are their plans to fix this for bullseye? are their difficulties getting
> new versions signed by MS?

Redirecting to shim maintainers.


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


signature.asc
Description: PGP signature

state of shim and shim-signed.

[peter green]

I have noticed that there seem to be issues with shim and shim-signed,
the former has a complaint from the gcc maintainers about being built
with an old version of gcc, the latter depends on an old version of shim.

Are their plans to fix this for bullseye? are their difficulties getting
new versions signed by MS?

Re: Bug#982283: override: bsdmainutils:oldlibs/optional

[Chris Hofstaedtler]

* Samuel Thibault  [210211 00:56]:
> As I mentioned previously in the bug, bsdutils (required) recommends
> bsdextrautils, so for that part things don't change.
> 
> For calendar and cal/ncal, the question indeed holds. For bsdmainutils
> maintainers: I guess the goal of splitting them out of bsdmainutils was
> precisely to not install them by default?

There were two goals:

1) for bsdmainutils delegate most things to util-linux (for various
reasons). This was done by moving the utilities to bsdextrautils
(from util-linux).

2) util-linux has the goal of making users "not pay" for tools they
do not need. That was achieved by putting the tools into
bsdextrautils and not into, say, bsdutils. The idea was that the
tools would still be there "on a normal install" (however that is
defined, ...), but not on minimal installs.

Maybe bsdextrautils should be prio standard then?
(I don't know exactly how d-i decides what to install for
"standard system".)

Thanks,
Chris

Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet

[Vagrant Cascadian]

Control: reassign 982270 linux
Control: retitle 982270 linux: [armhf] several imx6 systems unable to detect 
ethernet
Control: found 982270 5.10.13-1

On 2021-02-07, Rick Thomas wrote:
> It booted fine but when it got to the "Detect network hardware" phase, 
> it failed and said:
>
>> No Ethernet card was detected. If you know the name of the driver 
>> needed by your Ethernet card, you can select it from the list. 
>> Driver needed by your Ethernet card:  

I can confirm this is an issue on hummingboard-i2ex, cubox-i4x4 and
wandboard quad, all of which are similar imx6 systems, and all of which
use the SoC's gigabit ethernet interface.

I've had better luck with linux 5.9.x and 4.19.x versions, although
possibly backported patches on the stable branches may also trigger
similar issues, just not consistantly. 5.10.x seems to consistantly
result in no working ethernet interface.

Marked as found in 5.10.13-1, but I believe this affects all 5.10.x
versions I have seen.

Possibly related to changes to the mdio interface infrastructure, but
this pretty much needs someone to able take the time to git bisect and
boot test the issue...


live well,
  vagrant


> ==
> Installer hardware-summary:
> ==
> uname -a: Linux cube 4.19.0-13-armmp #1 SMP Debian 4.19.160-2 (2020-11-28) 
> armv7l GNU/Linux
> usb-list: 
> usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
> usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 
> 01
> usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
> usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
> usb-list: 
> usb-list: Bus 02 Device 01: EHCI Host Controller [1d6b:0002]
> usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 
> 01
> usb-list:Manufacturer: Linux 4.19.0-13-armmp ehci_hcd
> usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
> lsmod: Module  Size  Used by
> lsmod: dm_mod122880  9
> lsmod: md_mod143360  0
> lsmod: jfs   184320  0
> lsmod: btrfs1241088  0
> lsmod: libcrc32c  16384  1 btrfs
> lsmod: xor16384  1 btrfs
> lsmod: zstd_decompress61440  1 btrfs
> lsmod: zstd_compress 159744  1 btrfs
> lsmod: xxhash 20480  2 zstd_compress,zstd_decompress
> lsmod: zlib_deflate   28672  1 btrfs
> lsmod: raid6_pq   98304  1 btrfs
> lsmod: vfat   24576  0
> lsmod: fat73728  1 vfat
> lsmod: ext4  618496  3
> lsmod: crc16  16384  1 ext4
> lsmod: mbcache16384  1 ext4
> lsmod: jbd2  102400  1 ext4
> lsmod: crc32c_generic 16384  6
> lsmod: fscrypto   28672  1 ext4
> lsmod: ecb16384  0
> lsmod: brcmfmac  253952  0
> lsmod: brcmutil   16384  1 brcmfmac
> lsmod: cfg80211  548864  1 brcmfmac
> lsmod: rfkill 28672  1 cfg80211
> lsmod: usb_storage53248  0
> lsmod: sd_mod 49152  3
> lsmod: ahci_imx   20480  2
> lsmod: libahci_platform   20480  1 ahci_imx
> lsmod: libahci32768  2 libahci_platform,ahci_imx
> lsmod: libata208896  3 libahci_platform,libahci,ahci_imx
> lsmod: scsi_mod  196608  3 sd_mod,usb_storage,libata
> lsmod: sdhci_esdhc_imx24576  0
> lsmod: sdhci_pltfm16384  1 sdhci_esdhc_imx
> lsmod: sdhci  53248  2 sdhci_pltfm,sdhci_esdhc_imx
> lsmod: ci_hdrc_imx16384  0
> lsmod: ci_hdrc45056  1 ci_hdrc_imx
> lsmod: ulpi   16384  1 ci_hdrc
> lsmod: ehci_hcd   77824  1 ci_hdrc
> lsmod: udc_core   36864  1 ci_hdrc
> lsmod: usbcore   221184  4 usb_storage,ehci_hcd,brcmfmac,ci_hdrc
> lsmod: usbmisc_imx16384  1 ci_hdrc_imx
> lsmod: imxdrm 28672  0
> lsmod: anatop_regulator   16384  1
> lsmod: phy_mxs_usb16384  2
> lsmod: dw_hdmi_imx16384  0
> lsmod: dw_hdmi36864  1 dw_hdmi_imx
> lsmod: imx_ipu_v3 94208  1 imxdrm
> lsmod: cec49152  1 dw_hdmi
> lsmod: drm_kms_helper147456  2 dw_hdmi,imxdrm
> lsmod: drm   356352  5 
> imx_ipu_v3,dw_hdmi,dw_hdmi_imx,imxdrm,drm_kms_helper
> lsmod: at803x 16384  1
> df: Filesystem   1K-blocks  Used Available Use% Mounted on
> df: none20627656206220   0% /run
> df: devtmpfs   1010736 0   1010736   0% /dev
> df: /dev/mapper/ncube--vg-root
> df:   19092136769744  17329524   4% /target
> df: /dev/sda1   482922 31992425996   7% /target/boot
> df: /dev/mapper/ncub

Processed: Re: Bug#982270: linux: [armhf] several imx6 systems unable to detect ethernet

[Debian Bug Tracking System]

Processing control commands:

> reassign 982270 linux
Bug #982270 [installation-reports] installation-reports: Installing Debian 
Bullseye on Cubox-i4 - installer finds no ethernet
Bug reassigned from package 'installation-reports' to 'linux'.
Ignoring request to alter found versions of bug #982270 to the same values 
previously set
Ignoring request to alter fixed versions of bug #982270 to the same values 
previously set
> retitle 982270 linux: [armhf] several imx6 systems unable to detect ethernet
Bug #982270 [linux] installation-reports: Installing Debian Bullseye on 
Cubox-i4 - installer finds no ethernet
Changed Bug title to 'linux: [armhf] several imx6 systems unable to detect 
ethernet' from 'installation-reports: Installing Debian Bullseye on Cubox-i4 - 
installer finds no ethernet'.
> found 982270 5.10.13-1
Bug #982270 [linux] linux: [armhf] several imx6 systems unable to detect 
ethernet
There is no source info for the package 'linux' at version '5.10.13-1' with 
architecture ''
Unable to make a source version for version '5.10.13-1'
Marked as found in versions 5.10.13-1.

-- 
982270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems