On Tue, Jun 03, 2025 at 06:36:25PM +0200, Paul Gevers wrote: > I experience a very similar problem when I try to boot into a trixie kernel > after dist-upgrading the s390x ci.debian.net host.
NVMe is not DASD and is configured completely different. Everything you show is a symptom, not a cause. So no, it is not the same, even remotely. > (initramfs) Ý6nls /dev > ls /dev > btrfs-control ptmx tty21 tty41 tty61 > char pts tty22 tty42 tty62 > clp random tty23 tty43 tty63 > console sclp tty24 tty44 tty7 > fd stderr tty25 tty45 tty8 > full stdin tty26 tty46 tty9 > fuse stdout tty27 tty47 ttyS0 > hvc0 tty tty28 tty48 ttysclp0 > hvc1 tty0 tty29 tty49 urandom > hvc2 tty1 tty3 tty5 userfaultfd > hvc3 tty10 tty30 tty50 vcs > hvc4 tty11 tty31 tty51 vcs1 > hvc5 tty12 tty32 tty52 vcsa > hvc6 tty13 tty33 tty53 vcsa1 > hvc7 tty14 tty34 tty54 vcsu > hwrng tty15 tty35 tty55 vcsu1 > input tty16 tty36 tty56 vmcp > kmsg tty17 tty37 tty57 zero > mapper tty18 tty38 tty58 > mem tty19 tty39 tty59 > null tty2 tty4 tty6 > psaux tty20 tty40 tty60 > (initramfs) Ý6n No dasd device configured. This means the bug is in sysconfig-hardware, an old and weird package, or it's interaction with udev. Also given that it works with an old version of udev. Long shot in /usr/lib/udev/rules.d/85-sysconfig-hardware.rules and /usr/share/initramfs-tools/hooks/sysconfig-hardware: replace /sbin with /usr/sbin. Is manualy running "hwup 0.0.0150" doing something? What about "bash -x /sbin/hwup 0.0.01500"? Bastian -- Captain's Log, star date 21:34.5...
