Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: tumbleweed won't boot after update

  1. #1

    Default tumbleweed won't boot after update

    Hi there,

    I was fine at 20210220 when I decided its time to update with the command "tumbleweed switch --install 20210320".
    During (the very long) update everything went fine. Time to reboot.
    After the few initial text messages that are normal before the graphical mode kicks in, the screen went black.
    CTRL-ALT_DEL and CTRL+ALT+F1 not worked. Reboot this time changing the boot command bty adding "3 nomodeset" at end and removing "quit" and "splash=silent".
    I added nomodeset because my GPU is a ****ing NVidia GTX-970 using proprietary driver.
    But, this time looks like it is not the problem.
    Booting in pure text mode this time, drop me in the emergency mode showing BTRFS related messages. Please see a screenshot https://imgur.com/a/QQMQieQ
    Booting again in GRUB, selecting "bootloader from a RO snapshot" followed by "snapper rollback" restored the system as it was before.
    I've tried 20210319 and 20210317 all with the same behaviour.
    Currently I am on I was before the update: 5.10.16-1-default and KDE 5.20, tumbleweed 20210220. Everything is fine !!
    So I suspect that BTRFS is not an issue really. 'Cause it is, why it not manifest itself on the current setup ?
    I suspect it is the kernel 5.11 or btrfs itself that was updated in some previous update since 20210220.
    Is it possible to update everything else expect the kernel ?
    Doing that, if the problem is not present after such update, then it is a kernel 5.11 issue, am I right ?





  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    28,713

    Default Re: tumbleweed won't boot after update

    Why don't you do a
    Code:
    zypper dup
    like most (all?) others?
    Henk van Velden

  3. #3

    Default Re: tumbleweed won't boot after update

    Thank you for your curiosity,

    Some reasons:
    Because I can.
    Because I am not like the (all) others.
    Because tumbleweed-cli exist and linux is about choices.
    Because I want to control when I will update my system.
    Because tumbleweed-cli will run a zypper dist-upgrade anyway.
    Because I am happy to managed to avoid all the hassle in opensuse updates related to big changes in the past weeks.

    My turn to ask: Can you guarantee me that if I was not running tumblewed cli I would never had this problem?
    Are you saying the reason I am having this issue is because I choose to use tumbleweed-cli ?

    Sorry if my reply sounded rude, but it is not the first time (and not the last, I am sure about this) someone lost the focus on the main problem to question me about why I am running tumblewee-cli and how good and perfect is the QA and so I must stay with tumbleweed vanilla or move to leap.

  4. #4
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    2,907
    Blog Entries
    1

    Default Re: tumbleweed won't boot after update

    Quote Originally Posted by marozsas View Post
    Is it possible to update everything else expect the kernel ?
    Code:
    zypper al kernel-def*
    zypper dup
    I always have kernels locked. When I want a new kernel, I ask for one specifically, choosing override the lock, the actual result when "remove lock" is offered of a lock that includes any wildcard. It seems to me most NVidia driver users should be doing this, as much NVidia driver trouble as I see in forums and mailing lists.

    Did you try booting an older installed kernel before snapping back, or was 5.10.16 already gone?

    Old kernels are available from home:/tiwai.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 15.2, +TW, 15.1, 15.0 & 13.1 on Haswell
    Secondary: eComStation (OS/2) &15.1 on i965P w/ Radeon
    Tertiary: Mageia,Fedora,Debian,more on Kaby Lake,iQ45,iQ43,iG41,iG3X,i965G,AMD,NVidia&&&&&

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,285
    Blog Entries
    15

    Default Re: tumbleweed won't boot after update

    Hi
    Could be glibc related, normally when this comes through it is prudent to move to that snapshot....

    I keep a number of old kernel but not felt the need to lock, can just set booting to a specific kernel (did that some months back with a qemu issue).

    Always use the hard way with nvidia drivers, not let me down yet, easy enough to add any necessary patches to the run file. My qemu machines run nvidia, so can test an update there if needed prior to updating my main system...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6
    Join Date
    Sep 2012
    Posts
    6,489

    Default Re: tumbleweed won't boot after update

    Quote Originally Posted by marozsas View Post
    Please see a screenshot https://imgur.com/a/QQMQieQ
    So do what it tells you to do and provide rdsosreport.txt.

  7. #7

    Default Re: tumbleweed won't boot after update

    Quote Originally Posted by mrmazda View Post
    Code:
    zypper al kernel-def*
    zypper dup
    I always have kernels locked. When I want a new kernel, I ask for one specifically, choosing override the lock, the actual result when "remove lock" is offered of a lock that includes any wildcard. It seems to me most NVidia driver users should be doing this, as much NVidia driver trouble as I see in forums and mailing lists.

    Did you try booting an older installed kernel before snapping back, or was 5.10.16 already gone?

    Old kernels are available from home:/tiwai.
    Thank you, add-lock is new to me. I will try. I go back here after.
    Yes I tried to boot other kernel (5.10 is still there), but I got black screen because the nvidia driver for that version is not in place.
    Now, I see I must add-lock to nvidia packages too.

  8. #8

    Default Re: tumbleweed won't boot after update

    Quote Originally Posted by arvidjaar View Post
    So do what it tells you to do and provide rdsosreport.txt.
    I couldn't ! The file is big. In emergency mode I had no way to transfer or copy it to another location.

  9. #9

    Default Re: tumbleweed won't boot after update

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Could be glibc related, normally when this comes through it is prudent to move to that snapshot....

    I keep a number of old kernel but not felt the need to lock, can just set booting to a specific kernel (did that some months back with a qemu issue).

    Always use the hard way with nvidia drivers, not let me down yet, easy enough to add any necessary patches to the run file. My qemu machines run nvidia, so can test an update there if needed prior to updating my main system...
    When you boot another kernel I supposed the nvidia packages for that specific version must be present, am I right ?
    I suppose if I lock a specific kernel version, automatically the nvidia packages will not be update too, it's right ?

  10. #10

    Default Re: tumbleweed won't boot after update

    ok, things moved on.
    Thank you so far. Locking the kernel worked and I could confirm it is a kernel problem. And it is 2 different problems after all.
    The system is now fully updated.
    I've uninstalled the nvidia drivers and switched to noveau to fix the first problem with the proprietary nvidia driver.
    With the noveau driver updated I could even unlock the kernel and installed the 5.11.6-1-default
    So, no nvidia to make things worse than necessary.

    Booting on 5.11.6-1-default
    I got the same screen saying there is a BTRFS problem and I was droped in emmergency mode shell.
    Please, check the screenshot here: https://imgur.com/a/OUPC7kw

    On grub menu Advanced option I select 5.10.16-1-default and boot:
    I got the message:

    Code:
    [ 6.534238] nouveau 0000:01:00.0: bus: MMIO write of B88881f4 FAULT at 18eb14 [ IBUS ]
    
    Welcome to openSUSE Tumbleweed 28218328 Kernel 5.10.16-1-default (tty).
    
    enp3sB: 192.168.1.33 feBB: :6424:37f8:c78e:d276
    
    kimera login: miguel
    Password:
    Last login: Sun Mar 28 08:23:31 on ttyl 
    Have a lot of fun... 
    
    miguel $
    So, on 5.10 no BTRFS error ! No graphical mode either (X11)
    So I think it is safe to assume there is a problem in 5.11 related to BTRFS, right ?
    Where should I post/report this bug ?

    The second problem is related to nvidia card both noveau and proprietary driver, both 5.10 and 5.11 kernels.

    The strange is I get a graphical display in 2 stages: I got the graphical boot screen (the one with a spinning whell and infinite symbol Tumbleweed below) and the graphical logout/poweroff/reboot screen .

    Going back to 20200220 snapshot, everything works as expected,

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •