Re: Bug#1107192: s390-tools: after upgrade from bookworm to trixie no network

Paul Gevers <[email protected]>
Newsgroups gmane.linux.debian.ports.s390
Message-ID <[email protected]>
Hi,

On 06-06-2025 11:10, Pranav P wrote:
> So sorry for the late reply.


3.5 days and you call that late? Welcome to Debian, where we're not 
supposed to be surprised if we need to wait weeks or months.

> After an upgrade which triggered `update-initramfs`, I was also having the issue where the system fails to detect the rootfs and would boot into the initramfs busybox.
> After reinstalling bookworm, I updated the sources.list to use unstable and then did a dist-upgrade.
> I am still facing the same rootfs detection issue, but now, with Bastian's patch, I am able to see `85-sysconfig-hardware.rules` in /usr/lib/udev/rules.d and one of my DASD devices is also showing up in `/dev/disk/by-path` and when running `fdisk -l`.
> I had installed Debian on an FCP device rather than on a DASD.


Sorry for not reporting back to this bug. The network issue only 
happened with the old initramfs. Once I was able to use the trixie 
generated initramfs due to the fix found in bug #1107249, not only were 
the storage devices found, but also networking worked. So, something is 
still wrong for the *old* initramfs/kernel, but apparently this bug 
doesn't apply for the full trixie (+ sysconfig-hardware from unstable) 
stack.

> Was the no network reported in this bug report because of this issue or was the network outage seen after properly booting into Debian?


In my perception, they were two different issues, but I'm not sure.

> With Bastian's patch was it fixed or is the issue still persisting?

I'm *guessing* that the problem is still there when I would boot into 
the old kernel, as the kernel and its initramfs have not been updated. 
However, maybe with the udev now in the right place on disk, maybe it 
works and the issues were just two different symptoms of the same issue. 
I might try that later (no promises, I hate that x3... terminal by now).

Paul
OpenPGP_signature.asc (application/pgp-signature, 585 B)
-----BEGIN PGP SIGNATURE-----

wsC7BAABCABvBYJoQxdlCRCcXJnrBb11CkcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmeSlVzkuQ2PYAxRoFwaoHk+7J6ZCT19OV95Mb2OrOE1
ABYhBFi2bUhza+k7BS3mcpxcmesFvXUKAACcWwf+MBgNWJLtdAmv48pIsddJt606
4xJugDFTcOZ1zotLyOXp+dNb4lkPuR1rqPYCemDWpPJxVNmghTfRaer6/3vUxzSE
LJLOzIQ/BTRNmme5dvCai5OHJkeNlFDMdRRRx3EUVaNjuF1DExxUng2s3T2BLL7s
XFsut9mTTODMcXXUGBwpuO/qbRPrCqOX1975UMo+l4xomlCjOHaxifteHQ+Q14Lg
yTYvhs6DJlbDmx55Bdlf2kN8LgFAEr8YKMUU4vgau2Qc+O0SKluUnLQ/q4jFeo7U
aQoUWzElPkgzlBg3FPzetd5DXtAZA9XNYFcPqCQa4Q5EovOT4zWOHOKhErGvYA==
=Ewfx
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.