Created attachment 1644881 [details] ``journalctl --no-hostname -k -b-1 > dmesg-1.txt`` 1. Please describe the problem: Fedora 31 with a fc31 kernel does not start the wired network 2. What is the Version-Release number of the kernel: kernel-5.3.14-300.fc31.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Network starts with kernel-5.3.6-200.fc30.x86_64 and kernel-5.3.14-200.fc30.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Start with fc31-kernel 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Hasn't tested yet, has to run update of grub.cfg manually after install of new kernels (grub2-mkconfig -o /boot/grub2/grub.cfg). 6. Are you running any modules that not shipped with directly Fedora's kernel?: Not as far as I remember 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Sending logs from not working kernel (dmesg-1.txt).
Created attachment 1644883 [details] ``journalctl --no-hostname -k -b-0 > dmesg-0.txt``
An upgrade of kernel, to kernel-5.3.15-300.fc31.x86_64, didn't solve the problem. The upgrade removed two oldest fc30-kernels. Now running kernel-5.3.14-200.fc30.x86_64. Has also removed kernel-5.3.14-300.fc31.x86_64.
New upgrade of kernel. Removed kernel*-5.3.15-300.fc31.x86_64 Installed kernel*-5.3.16-300.fc31.x86_64 Updated grub.cfg Start with kernel-5.3.16-300.fc31.x86_64, the network was missing. Start with kernel-5.3.14-200.fc30.x86_64, the network is OK.
New upgrade of kernel. Removed kernel*-5.3.16-300.fc31.x86_64 Installed kernel*-5.4.10-200.fc31.x86_64 Updated grub.cfg Start with kernel-5.4.10-200.fc31.x86_64, the network was missing. Start with kernel-5.3.14-200.fc30.x86_64, the network is OK.
New upgrade of kernel. Removed kernel*-5.4.10-200.fc31.x86_64 Installed kernel*-5.5.5-200.fc31.x86_64 Updated grub.cfg Start with kernel-5.5.5-200.fc31.x86_64, the network was missing. Start with kernel-5.3.14-200.fc30.x86_64, the network is OK.
(In reply to henrik.johansson.kank from comment #5) ... > Start with kernel-5.5.5-200.fc31.x86_64, the network was missing. > Start with kernel-5.3.14-200.fc30.x86_64, the network is OK. ... Could you try: kernel-5.5.6-201.fc31, kernel-headers-5.5.6-200.fc31, & 1 more https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd64d683c If there is still no networking, please attach another log after rebooting with 5.3.14-200.fc30: $ journalctl -b -1 --no-hostname > dmesg-3.txt That omits the "-k" option, because there isn't anything obvious in the attached logs. That may leak information, so it would be a good idea to review it before attaching the log. > The upgrade removed two oldest fc30-kernels. You can stop that from happening by editing /etc/dnf/dnf.conf: #installonly_limit=3 installonly_limit=0 "man dnf.conf" will give the details.
The e1000 driver seems to be bringing up the link, so this may not be a kernel problem. Have you tried removing the networking configuration and creating a new one? $ egrep 'Kernel command line:|e1000' dmesg-1.txt Dec 13 16:16:51 kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-5.3.14-300.fc31.x86_64 root=/dev/mapper/vg_xsy12-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_xsy12/lv_swap KEYTABLE=sv-latin1 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_xsy12/lv_root Dec 13 16:16:52 kernel: e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI Dec 13 16:16:52 kernel: e1000: Copyright (c) 1999-2006 Intel Corporation. Dec 13 16:16:52 kernel: e1000 0000:10:03.0 eth0: (PCI:33MHz:32-bit) 00:11:85:ae:e2:ee Dec 13 16:16:52 kernel: e1000 0000:10:03.0 eth0: Intel(R) PRO/1000 Network Connection Dec 13 16:16:52 kernel: e1000 0000:10:03.0 enp16s3: renamed from eth0 Dec 13 16:17:13 kernel: e1000: enp16s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
(In reply to Steve from comment #7) > Have you tried removing the networking configuration and creating a new one? The device is getting renamed a second time in your F30 configuration, so try removing all networking configurations and creating a new one: $ egrep 'Kernel command line:|e1000.*renamed' dmesg-0.txt Dec 13 17:14:23 kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-5.3.14-200.fc30.x86_64 root=/dev/mapper/vg_xsy12-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_xsy12/lv_swap KEYTABLE=sv-latin1 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_xsy12/lv_root Dec 13 17:14:25 kernel: e1000 0000:10:03.0 enp16s3: renamed from eth0 Dec 13 16:15:32 kernel: e1000 0000:10:03.0 em1: renamed from enp16s3 $ egrep 'Kernel command line:|e1000.*renamed' dmesg-1.txt Dec 13 16:16:51 kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-5.3.14-300.fc31.x86_64 root=/dev/mapper/vg_xsy12-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_xsy12/lv_swap KEYTABLE=sv-latin1 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_xsy12/lv_root Dec 13 16:16:52 kernel: e1000 0000:10:03.0 enp16s3: renamed from eth0
Dec 13 16:16:51 kernel: DMI: Hewlett-Packard hp workstation xw8200/08B4h, BIOS 786B8 v2.10 05/31/2006 There appears to be a BIOS update for your system: HP Workstation xw8200 System BIOS Packaged for Linux 2.10 Rev. a 6.8 MB Sep 20, 2006 https://support.hp.com/us-en/drivers/selfservice/hp-xw8200-workstation/424560
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Excuse my late answer, I've fallen due to slippery ice, not fully back in the game again. I've tried kernel-5.5.7-200 and kernel-5.5.8-200, didn't solve the problem. Next I tried the BIOS-update comment #9, but the script from HP didn't write to my USB-memory. The script created a data-file /dev/SCSI. I also tried a diskette, but Fedora didn't recognise it. Next try was comments #7 and #8. I removed em1 with the 'NetWork Connections'-tool and rebooted the workstation. The restart created 'Wired connection 1' (device enp16s3) and the network are OK. Remaining problems: 1) The installation of kernels doesn't update grub.cfg. I update /boot/grub2/grub.cfg with: # grub2-mkconfig -o /boot/grub2/grub.cfg.20200311 # mv -i grub.cfg grub.cfg.20200305; mv -i grub.cfg.20200311 grub.cfg 2) Need advice on how to write BIOS-update to USB-memory. Question comment #6: Should I send logs even if the network are OK?
(In reply to henrik.johansson.kank from comment #11) > Excuse my late answer, I've fallen due to slippery ice, not fully back in > the game again. Thanks for your follow-up reply. I hope you are getting better. > I've tried kernel-5.5.7-200 and kernel-5.5.8-200, didn't solve the problem. > > Next I tried the BIOS-update comment #9, but the script from HP didn't write > to my USB-memory. The script created a data-file /dev/SCSI. I also tried a > diskette, but Fedora didn't recognise it. > > Next try was comments #7 and #8. I removed em1 with the 'NetWork > Connections'-tool and rebooted the workstation. The restart created 'Wired > connection 1' (device enp16s3) and the network are OK. Awesome! > Remaining problems: > 1) The installation of kernels doesn't update grub.cfg. > I update /boot/grub2/grub.cfg with: > # grub2-mkconfig -o /boot/grub2/grub.cfg.20200311 > # mv -i grub.cfg grub.cfg.20200305; mv -i grub.cfg.20200311 grub.cfg > > 2) Need advice on how to write BIOS-update to USB-memory. Those a tech-support questions, and I will attempt to help. Please close the bug first using the "Status" menu at the bottom of the page. Although it may not seem like it, I believe the resolution should NOTABUG: https://bugzilla.redhat.com/page.cgi?id=fields.html#resolution > Question comment #6: Should I send logs even if the network are OK? No need, unless you see the problem again.
(In reply to henrik.johansson.kank from comment #11) ... > Remaining problems: > 1) The installation of kernels doesn't update grub.cfg. > I update /boot/grub2/grub.cfg with: > # grub2-mkconfig -o /boot/grub2/grub.cfg.20200311 > # mv -i grub.cfg grub.cfg.20200305; mv -i grub.cfg.20200311 grub.cfg ... After you update the kernel, do you see an entry for it in the grub2 menu when you reboot? If you get this: $ grep BLS /etc/default/grub GRUB_ENABLE_BLSCFG="true" Then the kernel-specific grub2 menu entries are here: # ls /boot/loader/entries/ "BLS" means "Boot Loader Specification". A web search will find more info.
(In reply to henrik.johansson.kank from comment #11) ... > Next I tried the BIOS-update comment #9, but the script from HP didn't write > to my USB-memory. The script created a data-file /dev/SCSI. I also tried a > diskette, but Fedora didn't recognise it. ... That shell script is very old, so it might not work with a recent version of Fedora. I would suggest not attempting to update the BIOS, unless you have a supported version of Windows (Vista, XP, 2000 per HP xw8200 Workstation web page).
(In reply to henrik.johansson.kank from comment #11) ... > I also tried a diskette, but Fedora didn't recognise it. ... This will show you the block devices the kernel knows about: $ lsblk -mf Anyway, floppies are not supported by Linux any more: Linus Torvalds prepares to wave goodbye to Linux floppy drives July 29, 2019 https://www.zdnet.com/article/linus-torvalds-prepares-to-wave-goodbye-to-linux-floppy-drives/ Since you have a CD ROM drive (sr0), you could try booting an older "live" version of Fedora and seeing if it recognizes the floppy drive: https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/
(In reply to Steve from comment #15) ... > Since you have a CD ROM drive (sr0), you could try booting an older "live" > version of Fedora and seeing if it recognizes the floppy drive: > https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/ You don't really need to run the shell script, because all it does is use "dd" to write to the floppy drive: ... FLOPPY_PATH="/dev/fd0" ... echo "Copying image to floppy, please wait..." dd if=./fd0_img/Rompaq.img of=${FLOPPY_PATH} ...
(In reply to Steve from comment #15) ... > Since you have a CD ROM drive (sr0), you could try booting an older "live" > version of Fedora and seeing if it recognizes the floppy drive: > https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/ Try this first: Verify that you have the floppy module and load it: $ modinfo floppy # modprobe -v floppy If there are no errors, verify with: $ lsmod | grep floppy $ lsblk -mf However, Fedora is going to be blacklisting the floppy driver: Bug 1789155 - non-existent devices appeared after 5.4.7 kernel update https://bugzilla.redhat.com/show_bug.cgi?id=1789155 Bug 1789155, Comment 5, explains why you don't see a floppy device: Hans: "The die-floppy-die patch does not actually kill the floppy driver, it just removes the modaliases so that it is not auto-loaded by udev."
(In reply to Steve from comment #13) > (In reply to henrik.johansson.kank from comment #11) > ... > > Remaining problems: > > 1) The installation of kernels doesn't update grub.cfg. > > I update /boot/grub2/grub.cfg with: > > # grub2-mkconfig -o /boot/grub2/grub.cfg.20200311 > > # mv -i grub.cfg grub.cfg.20200305; mv -i grub.cfg.20200311 grub.cfg > ... > > After you update the kernel, do you see an entry for it in the grub2 menu > when you reboot? No > > If you get this: > > $ grep BLS /etc/default/grub > GRUB_ENABLE_BLSCFG="true" # grep BLS /etc/default/grub GRUB_ENABLE_BLSCFG=false > > Then the kernel-specific grub2 menu entries are here: > > # ls /boot/loader/entries/ > > "BLS" means "Boot Loader Specification". A web search will find more info. I'm not shure, but I think that the auto update of grub.cfg stopped after upgrade from Fedora 29 to 30. I noticed it at the upgrade from Fedora 30 to 31. Are the solution to update /etc/default/grub?
(In reply to Steve from comment #17) > (In reply to Steve from comment #15) > ... > > Since you have a CD ROM drive (sr0), you could try booting an older "live" > > version of Fedora and seeing if it recognizes the floppy drive: > > https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/ > > Try this first: > > Verify that you have the floppy module and load it: > > $ modinfo floppy > # modprobe -v floppy > > If there are no errors, verify with: > > $ lsmod | grep floppy > $ lsblk -mf > > However, Fedora is going to be blacklisting the floppy driver: > > Bug 1789155 - non-existent devices appeared after 5.4.7 kernel update > https://bugzilla.redhat.com/show_bug.cgi?id=1789155 > > Bug 1789155, Comment 5, explains why you don't see a floppy device: > > Hans: "The die-floppy-die patch does not actually kill the floppy driver, it > just removes the modaliases so that it is not auto-loaded by udev." Maybe I should the read Release Notes for the BOIS-update first. With help of Comment 14 ... 17, it seems doable.
(In reply to Steve from comment #17) > (In reply to Steve from comment #15) > ... > > Since you have a CD ROM drive (sr0), you could try booting an older "live" > > version of Fedora and seeing if it recognizes the floppy drive: > > https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/ > > Try this first: > > Verify that you have the floppy module and load it: > > $ modinfo floppy > # modprobe -v floppy > > If there are no errors, verify with: > > $ lsmod | grep floppy > $ lsblk -mf > > However, Fedora is going to be blacklisting the floppy driver: > > Bug 1789155 - non-existent devices appeared after 5.4.7 kernel update > https://bugzilla.redhat.com/show_bug.cgi?id=1789155 > > Bug 1789155, Comment 5, explains why you don't see a floppy device: > > Hans: "The die-floppy-die patch does not actually kill the floppy driver, it > just removes the modaliases so that it is not auto-loaded by udev." Maybe I should the read Release Notes for the BOIS-update first. With help of Comment 14 ... 17, it seems doable.(In reply to Steve from comment #12) > (In reply to henrik.johansson.kank from comment #11) > > Excuse my late answer, I've fallen due to slippery ice, not fully back in > > the game again. > > Thanks for your follow-up reply. I hope you are getting better. > > > I've tried kernel-5.5.7-200 and kernel-5.5.8-200, didn't solve the problem. > > > > Next I tried the BIOS-update comment #9, but the script from HP didn't write > > to my USB-memory. The script created a data-file /dev/SCSI. I also tried a > > diskette, but Fedora didn't recognise it. > > > > Next try was comments #7 and #8. I removed em1 with the 'NetWork > > Connections'-tool and rebooted the workstation. The restart created 'Wired > > connection 1' (device enp16s3) and the network are OK. > > Awesome! > > > Remaining problems: > > 1) The installation of kernels doesn't update grub.cfg. > > I update /boot/grub2/grub.cfg with: > > # grub2-mkconfig -o /boot/grub2/grub.cfg.20200311 > > # mv -i grub.cfg grub.cfg.20200305; mv -i grub.cfg.20200311 grub.cfg > > > > 2) Need advice on how to write BIOS-update to USB-memory. > > Those a tech-support questions, and I will attempt to help. > > Please close the bug first using the "Status" menu at the bottom of the > page. Although it may not seem like it, I believe the resolution should > NOTABUG: > https://bugzilla.redhat.com/page.cgi?id=fields.html#resolution > > > Question comment #6: Should I send logs even if the network are OK? > > No need, unless you see the problem again. Maybe the network-error was an outcome of the upgrade from Fedora 30 to 31. I had a similar problem with Win95, back in 1996, I have been reminded now. Thanks
(In reply to henrik.johansson.kank from comment #18) ... > > After you update the kernel, do you see an entry for it in the grub2 menu > > when you reboot? > No OK, that shouldn't happen, but: > > If you get this: > > > > $ grep BLS /etc/default/grub > > GRUB_ENABLE_BLSCFG="true" > # grep BLS /etc/default/grub > GRUB_ENABLE_BLSCFG=false ... > Are the solution to update /etc/default/grub? See if you can solve the problem by setting: GRUB_ENABLE_BLSCFG="true" And then running grub2-mkconfig.
(In reply to henrik.johansson.kank from comment #18) ... > > After you update the kernel, do you see an entry for it in the grub2 menu > > when you reboot? > No ... I reproduced that in a VM, and it is a known bug: Bug 1713902 - With Fedora 30 the kernel update does not update the grub configuration anymore
Excuse me for my late answer, but I lost my internet-connection when I was writing the answer (11 days without internet!!) What should I do if next upgrade of kernel doesn't update grub.cfg?
My original request has been solved. My additional problem are also solved see [Bug 1819610] After update of kernel, stiil booting prevous kernel