Hello, I try to install a new machine via PXE. We did this many times before, but now we've got new hardware and it doesn't work anymore. But I don't know why.... The new hardware has a MSI MPG B550 mainboard, network chipset needs a r8169 driver. The machine boots fine (as allways) but after loading the initrd it stops with a "can't mount root fs" and a kernel panic. The config for the pxelinux looks like: label 15.4 kernel 15.4/boot/x86_64/loader/linux append initrd=15.4/boot/x86_64/loader/initrd ramdisk_size=65536 splash=silent showopts BrokenModules=+gma500_gfx install=nfs://10.3.1.2/tftpboot/15.4 Also tried it with "insmod=r8169", but it doesn't help. Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log... Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Am 17.12.22 um 09:33 schrieb David C. Rankin:
On 12/16/22 00:30, Daniel Spannbauer wrote:
MSI MPG B550 mainboard
Which version, Plus, Carbon, etc...
The Plus shows a Realtek® 8111H 1 Gbps LAN controller - not sure the 8169 driver will work?
Hello, it's the plus version. When I install via DVD, r8169 is the driver which is loaded and which is working. Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Daniel Spannbauer wrote:
Hello,
I try to install a new machine via PXE. We did this many times before, but now we've got new hardware and it doesn't work anymore. But I don't know why....
The new hardware has a MSI MPG B550 mainboard, network chipset needs a r8169 driver. The machine boots fine (as allways) but after loading the initrd it stops with a "can't mount root fs" and a kernel panic.
The config for the pxelinux looks like:
label 15.4 kernel 15.4/boot/x86_64/loader/linux append initrd=15.4/boot/x86_64/loader/initrd ramdisk_size=65536 splash=silent showopts BrokenModules=+gma500_gfx install=nfs://10.3.1.2/tftpboot/15.4
Also tried it with "insmod=r8169", but it doesn't help.
Something's not right with that driver. The spec for that mainboard says it is RTL8111H - however, my laptop here also has rtl8111/8168/8411 and it does work with the r8169 driver.
Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log...
Put a serial console on ? -- Per Jessen, Zürich (-0.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Something's not right with that driver. The spec for that mainboard says it is RTL8111H - however, my laptop here also has rtl8111/8168/8411 and it does work with the r8169 driver.
Fwiw, pxe booting 15.4 on my laptop (r8169 automatically loaded), works fine. I am not using NFS though, I'm using http. -- Per Jessen, Zürich (-0.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Am 17.12.22 um 13:56 schrieb Per Jessen:
Put a serial console on ?
If this is the only method I have to find a serial adapter cable, the board as no DSUB9 Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log... Put a serial console on ?
Here is a logfile with the ouput. As you can see, ist loads the kernel, the initrd but then it dies. https://service.marco.de/owncloud/index.php/s/RBnyg6xLYxjC0Yo Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Daniel Spannbauer wrote:
Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log... Put a serial console on ?
Here is a logfile with the ouput.
As you can see, ist loads the kernel, the initrd but then it dies. https://service.marco.de/owncloud/index.php/s/RBnyg6xLYxjC0Yo
Thanks - yes, there is never any network device found. Yet it is clearly there, when you're booting over pxe. I do see the network device in the PCI listing though: [ 26.790074][ T1] pci 0000:2a:00.0: [10ec:8168] type 00 class 0x020000 [ 26.870032][ T1] pci 0000:2a:00.0: reg 0x10: [io 0xf000-0xf0ff] [ 26.946042][ T1] pci 0000:2a:00.0: reg 0x18: [mem 0xfcd04000-0xfcd04fff 64bit] [ 27.034028][ T1] pci 0000:2a:00.0: reg 0x20: [mem 0xfcd00000-0xfcd03fff 64bit] [ 27.126149][ T1] pci 0000:2a:00.0: supports D1 D2 [ 27.186007][ T1] pci 0000:2a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [10ec:8168] is your Realtek interface. Afaict, the r8169 module should be good. So the question is, why is no module being auto-loaded ? Would you mind trying a 2nd time, with "insmod=r1869" ? You ought to see something like this: [ 4.210906] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 4.238350] libphy: r8169: probed [ 4.238727] r8169 0000:02:00.0 eth0: RTL8168gu/8111gu, c8:5b:76:nn:nn:nn, XID 509, IRQ 48 [ 4.240970] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] -- Per Jessen, Zürich (9.6°C)
On Wed, Dec 21, 2022 at 4:52 PM Per Jessen <per@computer.org> wrote:
Daniel Spannbauer wrote:
Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log... Put a serial console on ?
Here is a logfile with the ouput.
As you can see, ist loads the kernel, the initrd but then it dies. https://service.marco.de/owncloud/index.php/s/RBnyg6xLYxjC0Yo
Thanks - yes, there is never any network device found. Yet it is clearly there, when you're booting over pxe.
I do see the network device in the PCI listing though:
[ 26.790074][ T1] pci 0000:2a:00.0: [10ec:8168] type 00 class 0x020000 [ 26.870032][ T1] pci 0000:2a:00.0: reg 0x10: [io 0xf000-0xf0ff] [ 26.946042][ T1] pci 0000:2a:00.0: reg 0x18: [mem 0xfcd04000-0xfcd04fff 64bit] [ 27.034028][ T1] pci 0000:2a:00.0: reg 0x20: [mem 0xfcd00000-0xfcd03fff 64bit] [ 27.126149][ T1] pci 0000:2a:00.0: supports D1 D2 [ 27.186007][ T1] pci 0000:2a:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[10ec:8168] is your Realtek interface. Afaict, the r8169 module should be good. So the question is, why is no module being auto-loaded ?
Is it included in initrd?
Would you mind trying a 2nd time, with "insmod=r1869" ?
You ought to see something like this: [ 4.210906] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control [ 4.238350] libphy: r8169: probed [ 4.238727] r8169 0000:02:00.0 eth0: RTL8168gu/8111gu, c8:5b:76:nn:nn:nn, XID 509, IRQ 48 [ 4.240970] r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
-- Per Jessen, Zürich (9.6°C)
Andrei Borzenkov wrote:
On Wed, Dec 21, 2022 at 4:52 PM Per Jessen <per@computer.org> wrote:
Daniel Spannbauer wrote:
Any Idea what's going on here? How can I get more infos? When the kernel panics, I can't go backwards to inspect the log... Put a serial console on ?
Here is a logfile with the ouput.
As you can see, ist loads the kernel, the initrd but then it dies. https://service.marco.de/owncloud/index.php/s/RBnyg6xLYxjC0Yo
Thanks - yes, there is never any network device found. Yet it is clearly there, when you're booting over pxe.
I do see the network device in the PCI listing though:
[ 26.790074][ T1] pci 0000:2a:00.0: [10ec:8168] type 00 class [ 0x020000 [ 26.870032][ T1] pci 0000:2a:00.0: reg 0x10: [io [ 0xf000-0xf0ff] [ 26.946042][ T1] pci 0000:2a:00.0: reg 0x18: [mem [ 0xfcd04000-0xfcd04fff 64bit] [ 27.034028][ T1] pci 0000:2a:00.0: reg 0x20: [mem [ 0xfcd00000-0xfcd03fff 64bit] [ 27.126149][ T1] pci 0000:2a:00.0: supports D1 D2 [ 27.186007][ T1] pci 0000:2a:00.0: PME# supported from D0 D1 D2 [ D3hot D3cold
[10ec:8168] is your Realtek interface. Afaict, the r8169 module should be good. So the question is, why is no module being auto-loaded ?
Is it included in initrd?
It worked on my system when I tried it. Unless Daniel is using a different initrd ? This is what I am booting from: http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa... http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa... -- Per Jessen, Zürich (9.4°C)
Am 21.12.22 um 15:13 schrieb Per Jessen:
It worked on my system when I tried it. Unless Daniel is using a different initrd ?
This is what I am booting from: http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa... http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa...
yes, I use the standard kernel and initrd from the installation media. I found the cause, the driver is not the main problem :( [ 16.826383] PCI: CLS 64 bytes, default 64 [ 16.874794] Trying to unpack rootfs image as initramfs... [ 17.450294] Initramfs unpacking failed: XZ-compressed data is corrupt [ 17.537972] Freeing initrd memory: 112052K The kernel can't unpack the initrd. Don't know why. The same pxe boot works on a differnet machine. The cause must be something with the now board/bios sore something.... Thanks for your time so far...atm I don't know how to fix this... Regards Daniel
-- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
On 2022-12-21 15:28, Daniel Spannbauer wrote:
Am 21.12.22 um 15:13 schrieb Per Jessen:
yes, I use the standard kernel and initrd from the installation media.
I found the cause, the driver is not the main problem :(
[ 16.826383] PCI: CLS 64 bytes, default 64 [ 16.874794] Trying to unpack rootfs image as initramfs... [ 17.450294] Initramfs unpacking failed: XZ-compressed data is corrupt [ 17.537972] Freeing initrd memory: 112052K
I have seen that problem reported somewhere else, I forget which. Maybe Usenet. I can't locate it. Google finds reports of "XZ-compressed data is corrupt", but not recent. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Daniel Spannbauer wrote:
Am 21.12.22 um 15:13 schrieb Per Jessen:
It worked on my system when I tried it. Unless Daniel is using a different initrd ?
This is what I am booting from: http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa... http://download.opensuse.org/distribution/leap/15.4/repo/oss/boot/x86_64/loa...
yes, I use the standard kernel and initrd from the installation media.
I found the cause, the driver is not the main problem :(
[16.826383] PCI: CLS 64 bytes, default 64 [16.874794] Trying to unpack rootfs image as initramfs... [17.450294] Initramfs unpacking failed: XZ-compressed data is corrupt [17.537972] Freeing initrd memory: 112052K
The kernel can't unpack the initrd. Don't know why. The same pxe boot works on a differnet machine. The cause must be something with the now board/bios sore something....
Thanks for your time so far...atm I don't know how to fix this...
For starters, I would check your initrd against the original, maybe something went wrong in the download? My initrd is about 144Mb, but above I see "Freeing initrd memory: 112052K". -- Per Jessen, Zürich (9.7°C)
For starters, I would check your initrd against the original, maybe something went wrong in the download? My initrd is about 144Mb, but above I see "Freeing initrd memory: 112052K".
with an other, older machine this setup works as expected. Must be something with this type of hardware I think. Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 https://www.marco.de Email ds@marco.de Geschäftsführer Martin Reuter, Torsten Lukas HRB 171775 Amtsgericht München
Daniel Spannbauer wrote:
For starters, I would check your initrd against the original, maybe something went wrong in the download? My initrd is about 144Mb, but above I see "Freeing initrd memory: 112052K".
with an other, older machine this setup works as expected. Must be something with this type of hardware I think.
I guess it can't be excluded, but that would be my very last guess. To me, being unable to decompress the initrd suggests an issue with the initrd, first and foremost. I agree though, when it works on other hardware ... maybe something happens during the tftp transfer? Maybe you could try unpacking the initrd on a running system, to see if that fails too. Heh, I have just PXE/booted my laptop and I see "Freeing initrd memory: 146924K". That seems to fit a lot better with the 144Mb size of the initrd. -- Per Jessen, Zürich (12.1°C)
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Daniel Spannbauer -
David C. Rankin -
Per Jessen