[opensuse] Boot failure after kernel update
Hello, today, I did a "zypper update" (after a long time) This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default After that, I was no longer able to boot: - At the prompt to typing LUKS key, the USB (cherry) did not work. - using a PS2 keyboard, I could type the LUKS key, but the LUKS volume could not be accessed. Investigation showed, that mkinitrd failed to add a lot of modules to the initrd image. This is the message from mkinitrd: Some kernel modules could not be included This is not necessarily an error: dm_crypt dm_mod dm-cache dm-cache-mq dm-cache-cleaner sr_mod scsi_dh ata_piix hid_generic ehci-hcd ehci-pci ohci-hcd ohci-pci uhci-hcd xhci-hcd yenta_socket scsi_dh_rdac scsi_dh_emc scsi_dh_alua usbhid hid-apple hid-sunplus hid-cherry hid-logitech hid-logitech-dj hid-microsoft firewire-ohci pcmcia usb_storage hid-hyperv hv-vmbus sdhci_acpi virtio_blk virtio_scsi crypto_LUKS sg Update bootloader... For the older kernels, mkinitrd still works as expected. Thus, luckily, I can still boot some old kernels. When I search for the missing modules, I find that the modules for the newest kernel got a new extension (compression?): raven:/ # find /lib -name 'hid-cherry*' /lib/modules/5.5.1-4.g267811a-default/kernel/drivers/hid/hid-cherry.ko.xz /lib/modules/5.2.8-1.gbf37e83-default/kernel/drivers/hid/hid-cherry.ko /lib/modules/4.8.1-3.gf7183f5-default/kernel/drivers/hid/hid-cherry.ko raven:/ # Anybody out there who understands the situation and has an idea how to fix? -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did a "zypper update" (after a long time) | | This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default So, what distribution are you using? It can not be Leap. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjs2wgAKCRC1MxgcbY1H 1eFeAJ9RmZNIbf9vnFmK8t17JjYGl+UnoQCdG3IJ7eS/3hIAMPE4w35XbdTenVs= =aVjr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mi, Feb 05, 2020 at 10:42:28 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did a "zypper update" (after a long time) | | This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default
So, what distribution are you using? It can not be Leap.
Sorry, forgot this info. Why can't it be leap? It's leap 42.1. Here's the full info: # lsb_release -a LSB Version: core-5.0-amd64:core-5.0-noarch:desktop-5.0-amd64:desktop-5.0-noarch:imaging-5.0-amd64:imaging-5.0-noarch:languages-5.0-amd64:languages-5.0-noarch Distributor ID: SUSE LINUX Description: openSUSE Leap 42.1 (x86_64) Release: 42.1 Codename: n/a -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/02/2020 23.07, Josef Wolf wrote:
On Mi, Feb 05, 2020 at 10:42:28 +0100, Carlos E. R. wrote:
On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did a "zypper update" (after a long time) | | This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default
So, what distribution are you using? It can not be Leap.
Sorry, forgot this info. Why can't it be leap? It's leap 42.1. Here's the full info:
# lsb_release -a LSB Version:
core-5.0-amd64:core-5.0-noarch:desktop-5.0-amd64:desktop-5.0-noarch:imaging-5.0-amd64:imaging-5.0-noarch:languages-5.0-amd64:languages-5.0-noarch
Distributor ID: SUSE LINUX
Description: openSUSE Leap 42.1 (x86_64) Release: 42.1 Codename: n/a
Well, it can not be because leap is on kernel 4.12. Further, Leap 42.1 is out of maintenance and support since 2017-05-17, which means that you are doing the maintenance on your own. Guessing, you have added some experimental kernel repository. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/02/2020 23.13, James Knott wrote: | On 2020-02-05 04:42 PM, Carlos E. R. wrote: |> So, what distribution are you using? It can not be Leap. | | Let's not Leap to conclusions. ;-) | I took a leap of faith and crashed ;-p - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjs/GgAKCRC1MxgcbY1H 1UatAJ9PkmmcPyDI0jCy8yQz07pwuVZhowCeL4At5HbvafuaC5EaAQtb8f/9+9I= =qUZt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-02-05 4:42 p.m., Carlos E. R. wrote:
On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did a "zypper update" (after a long time) | | This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default
So, what distribution are you using? It can not be Leap.
What can't it e leap? I'm using, as I've said many times, kernel_Stable and am at merely # uname -r 5.5.1-3.gfcd8e64-default but # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.1" ID="opensuse-leap" -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/02/2020 23.26, Anton Aylward wrote: | On 2020-02-05 4:42 p.m., Carlos E. R. wrote: |> On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did |> a "zypper update" (after a long time) | | This upgraded my kernel |> to vmlinuz-5.5.1-4.g267811a-default |> |> So, what distribution are you using? It can not be Leap. | | What can't it e leap? I'm using, as I've said many times, | kernel_Stable and am at merely That's not pure Leap... you are using a crucial modification. You have to say "Leap 15.1 + kernel_Stable", specially when we are talking of a boot failure after kernel update. | | # uname -r 5.5.1-3.gfcd8e64-default | | but # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.1" | ID="opensuse-leap" | | | - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjtCLQAKCRC1MxgcbY1H 1biSAJ0ZrMe11CVBKMvvI4497Y77+U44JgCcDh7LtAg+uM1l5qOuvO0j/VDt7/Q= =cWu8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 6/2/20 9:31 am, Carlos E. R. wrote:
On 05/02/2020 23.26, Anton Aylward wrote: | On 2020-02-05 4:42 p.m., Carlos E. R. wrote: |> On 05/02/2020 21.35, Josef Wolf wrote: | Hello, | | today, I did |> a "zypper update" (after a long time) | | This upgraded my kernel |> to vmlinuz-5.5.1-4.g267811a-default |> |> So, what distribution are you using? It can not be Leap. | | What can't it e leap? I'm using, as I've said many times, | kernel_Stable and am at merely
That's not pure Leap... you are using a crucial modification. You have to say "Leap 15.1 + kernel_Stable", specially when we are talking of a boot failure after kernel update.
| | # uname -r 5.5.1-3.gfcd8e64-default | | but # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.1" | ID="opensuse-leap"
Now the conversation is going into never-never land. Josef is using a copy of Leap which has its EOL way back in 2017. One hardly expects to have one of the latest stable kernels to function with a 3 yr old copy of Leap which hasn't been supported for 3 years. BC -- All things are possible, except skiing through a revolving door. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Feb 06, 2020 at 05:08:43PM +1100, Basil Chupin wrote:
Now the conversation is going into never-never land. Josef is using a copy of Leap which has its EOL way back in 2017.
The system was installed at 15. October 2016 with the latest "stable" available at that time. I always use the latest "stable". Turns out that the remaining life time of this latest stable was about 7 months at that time.
One hardly expects to have one of the latest stable kernels to function with a 3 yr old copy of Leap which hasn't been supported for 3 years.
Granted. OTOH, please remember that this kernel was installed by "zypper update". It would have been nice if zypper issued some warning instead of saying that it "is up to date" and happily installing the newest kernel which - by definition - is totally incompatible with this outdated distro: raven:/ # zypper refresh Repository 'Haupt-Repository (NON-OSS)' is up to date. Repository 'Aktualisierungs-Repository (Nicht-Open-Source-Software)' is up to date. Repository 'Haupt-Repository (OSS)' is up to date. Repository 'Haupt-Repository (Quellen)' is up to date. Repository 'Hauptaktualisierungs-Repository' is up to date. Repository 'openSUSE-42.1-0' is up to date. Repository 'packman' is up to date. Repository 'openSUSE-Leap-42.1-Update' is up to date. All repositories have been refreshed. raven:/ # Anyway, I'm going to reinstall now. Thanks, -- Josef Wolf jw@raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Josef Wolf wrote:
On Thu, Feb 06, 2020 at 05:08:43PM +1100, Basil Chupin wrote:
Now the conversation is going into never-never land. Josef is using a copy of Leap which has its EOL way back in 2017.
The system was installed at 15. October 2016 with the latest "stable" available at that time. I always use the latest "stable". Turns out that the remaining life time of this latest stable was about 7 months at that time.
One hardly expects to have one of the latest stable kernels to function with a 3 yr old copy of Leap which hasn't been supported for 3 years.
Granted.
OTOH, please remember that this kernel was installed by "zypper update".
Most likely not from a regular repo, but from KOTD or some such. You got what you asked for. -- Per Jessen, Zürich (1.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2020-02-06 at 10:15 +0100, Josef Wolf wrote:
On Thu, Feb 06, 2020 at 05:08:43PM +1100, Basil Chupin wrote:
Now the conversation is going into never-never land. Josef is using a copy of Leap which has its EOL way back in 2017.
The system was installed at 15. October 2016 with the latest "stable" available at that time. I always use the latest "stable". Turns out that the remaining life time of this latest stable was about 7 months at that time.
Yes, that's normal. But then, you did not upgrade it when the time came to the next stable.
One hardly expects to have one of the latest stable kernels to function with a 3 yr old copy of Leap which hasn't been supported for 3 years.
Granted.
OTOH, please remember that this kernel was installed by "zypper update".
So?
It would have been nice if zypper issued some warning instead of saying that it "is up to date" and happily installing the newest kernel which - by definition - is totally incompatible with this outdated distro:
Zypper has no idea of that; it does what you tell it to do. Current zypper may tell you that your repositories did not see changes in several months, thus obsolete.
Anyway, I'm going to reinstall now.
Or, you can upgrade it instead. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjwT0xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVc1gAn3tK23aFygmf3rHAeOVP aiz58V3pAJ9qc2BF4tCNkhtwJ/NvGldyTFtdtQ== =ak6K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Mittwoch, 5. Februar 2020, 21:35:36 CET schrieb Josef Wolf:
Hello,
today, I did a "zypper update" (after a long time)
This upgraded my kernel to vmlinuz-5.5.1-4.g267811a-default
After that, I was no longer able to boot:
[snip]
raven:/ # find /lib -name 'hid-cherry*' /lib/modules/5.5.1-4.g267811a-default/kernel/drivers/hid/hid-cherry.ko.xz /lib/modules/5.2.8-1.gbf37e83-default/kernel/drivers/hid/hid-cherry.ko /lib/modules/4.8.1-3.gf7183f5-default/kernel/drivers/hid/hid-cherry.ko raven:/ #
Anybody out there who understands the situation and has an idea how to fix?
You can try to build mkinitrd for your system. Check out dracut from openSUSE:Factory and try to build locally (all with osc). Of course, you backup your system before installing it. Your best bet maybe it upgrading the system, e.g. mkdir /etc/zypp/repos.d/42.1 cp -vp /etc/zypp/repos.d/*.repo /etc/zypp/repos.d/42.1/ sed -i 's,42\.1,15.1,g' /etc/zypp/repos.d/*.repo Check repos with zypper lr, disable auxiliary ones, especially the non std kernel ones. zyp dup 2>&1 | tee /tmp/zyp-dup-42.1-15.1.log This is *not* the officially recommended way, but surely the *most* *effective*, given you know, how to fix the fallout. By playing with arbitrary kernel versions, you do imply that! ;-) Good luck, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Basil Chupin -
Carlos E. R. -
Hans-Peter Jansen -
James Knott -
Josef Wolf -
Per Jessen