• Re: Freeze with newest kernel - probably Intel-Graphics related

    From Don Spam's Reckless Son@hyperspace.flyover@vogon.gov.invalid to alt.os.linux.suse on Tue Apr 4 17:55:45 2023
    From Newsgroup: alt.os.linux.suse

    Don Spam's Reckless Son wrote:
    kernel-default-5.14.21-150400.24.49.3.x86_64 came out a day or so ago
    [leap 15.4] and I have been installing it on various machines.-a The AMD machines with Radeon Graphics are perfectly happy with it but my
    10-year-old Acer Laptop [intel graphics] freezes 3.6 seconds into the
    boot process.

    The last message before it stops is
    fb0: switching to i915 from EFI VGA

    The obvious workaround is to boot the previous kernel and that works
    just fine.

    I see others have had the problem over the last year, but theirs appear
    to be with brand new Intel Graphics systems and that does not describe
    my laptop. https://superuser.com/questions/1761864/leap-15-4-boot-hangs-on-fbo-switching-to-i915-from-efi-vga
    is an example.

    One last comment on this subject.
    I have a system where /boot is only large enough for two kernels
    (actually, 3 would fit easily but the update process refuses to try) so
    I have to remove the older kernel once I can see that the newer one is
    working fine. Normally I go there and remove it using yast -> software
    software management -> versions.

    Since the previous installed kernel had been retracted, I decided to ssh
    into the machine and mark the retracted kernel with "-" to uninstall it.
    Of course it uninstalled both the old broken-with-intel-graphics kernel
    along with the new one. Luckily everything I needed was in memory and I
    could simply install the three current "kernel-default*" packages again.

    We live and learn.
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Wed Apr 5 00:25:01 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-04-04 17:55, Don Spam's Reckless Son wrote:

    One last comment on this subject.
    I have a system where /boot is only large enough for two kernels
    (actually, 3 would fit easily but the update process refuses to try) so
    I have to remove the older kernel once I can see that the newer one is working fine.-a Normally I go there and remove it using yast -> software
    software management -> versions.

    You could try to remove "plymouth" package, it is big and goes into
    initrd. However, boot will be in text mode.

    It might be enough bytes to make the 3 kernels fit.


    Since the previous installed kernel had been retracted, I decided to ssh into the machine and mark the retracted kernel with "-" to uninstall it.
    Of course it uninstalled both the old broken-with-intel-graphics kernel along with the new one.-a Luckily everything I needed was in memory and I could simply install the three current "kernel-default*" packages again.

    We live and learn.

    kernel is a multiversion package. If you tick the top one, it deletes
    them all. You have to do it in the "version" tab in yast.
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Don Spam's Reckless Son@hyperspace.flyover@vogon.gov.invalid to alt.os.linux.suse on Wed Apr 5 13:05:25 2023
    From Newsgroup: alt.os.linux.suse

    Carlos E.R. wrote:
    On 2023-04-04 17:55, Don Spam's Reckless Son wrote:

    One last comment on this subject.
    I have a system where /boot is only large enough for two kernels
    (actually, 3 would fit easily but the update process refuses to try)
    so I have to remove the older kernel once I can see that the newer one
    is working fine.-a Normally I go there and remove it using yast ->
    software -> software management -> versions.

    You could try to remove "plymouth" package, it is big and goes into
    initrd. However, boot will be in text mode.

    It might be enough bytes to make the 3 kernels fit.


    You made that suggestion several months ago and I tried it, it did not
    help. There is easily enough room in /boot for three kernels, it is the update process being anal. Two kernels take around 50% of /boot so four kernels would probably not work.


    Since the previous installed kernel had been retracted, I decided to
    ssh into the machine and mark the retracted kernel with "-" to
    uninstall it.
    Of course it uninstalled both the old broken-with-intel-graphics
    kernel along with the new one.-a Luckily everything I needed was in
    memory and I could simply install the three current "kernel-default*"
    packages again.

    We live and learn.

    kernel is a multiversion package. If you tick the top one, it deletes
    them all. You have to do it in the "version" tab in yast.


    Yes, I saw that. I had thought I was just removing the Retracted
    Installed Packages but when it listed the six packages it had removed it
    was obvious that I had no kernel left.
    Using the Version tab is what I normally do.
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.os.linux.suse on Wed Apr 5 13:43:32 2023
    From Newsgroup: alt.os.linux.suse

    On 2023-04-05 13:05, Don Spam's Reckless Son wrote:
    Carlos E.R. wrote:
    On 2023-04-04 17:55, Don Spam's Reckless Son wrote:

    One last comment on this subject.
    I have a system where /boot is only large enough for two kernels
    (actually, 3 would fit easily but the update process refuses to try)
    so I have to remove the older kernel once I can see that the newer
    one is working fine.-a Normally I go there and remove it using yast ->
    software -> software management -> versions.

    You could try to remove "plymouth" package, it is big and goes into
    initrd. However, boot will be in text mode.

    It might be enough bytes to make the 3 kernels fit.


    You made that suggestion several months ago and I tried it, it did not help.-a There is easily enough room in /boot for three kernels, it is the update process being anal.-a Two kernels take around 50% of /boot so four kernels would probably not work.

    Maybe temporary files while initrd archives are created.



    Since the previous installed kernel had been retracted, I decided to
    ssh into the machine and mark the retracted kernel with "-" to
    uninstall it.
    Of course it uninstalled both the old broken-with-intel-graphics
    kernel along with the new one.-a Luckily everything I needed was in
    memory and I could simply install the three current "kernel-default*"
    packages again.

    We live and learn.

    kernel is a multiversion package. If you tick the top one, it deletes
    them all. You have to do it in the "version" tab in yast.


    Yes, I saw that.-a I had thought I was just removing the Retracted
    Installed Packages but when it listed the six packages it had removed it
    was obvious that I had no kernel left.
    Using the Version tab is what I normally do.

    Lucky you noticed before rebooting ;-)
    --
    Cheers, Carlos.

    --- Synchronet 3.21d-Linux NewsLink 1.2