Good Morning from my Robotics Lab! This is Shadow_8472 with a side project of the week. Let\u2019s get started!<\/p>\n\n\n\n
Surprise! Bad Manjaro update. I seem to be getting them once a year. I rebooted some time last Wednesday, seemingly to a black screen. My first thought this time wasn\u2019t, \u201cOh, no! What am I going to do?\u201d so much as, \u201cUgg, I need to refresh my memory on chroot and manual updating with pacman, skills I\u2019ve only used once or twice before.\u201d<\/p>\n\n\n\n
No need to go through all the trouble if it\u2019s not actually necessary. Manjaro has a feature where you can boot from one of an installed list of kernels, and I was seeing that list. Every option failed though \u2013 the most I ever got was an emergency shell that didn\u2019t aknowledge the keyboard enough to toggle number or caps locks. This install wasn\u2019t going to fix itself.<\/p>\n\n\n\n
My first thought was to grab the Debian drive from ButtonMash, but I\u2019d rather not mess up the only known working drive for scanning pictures. Instead, I riffled through my thumb drive collection and located one with Debian 11 install media. I got on Derpy Chips, my other daily driver workstation, and installed balenaEtcher special to safely make a new Manjaro live USB\/install media.<\/p>\n\n\n\n
During this time, I was researching the problem. Other people were talking about it within the past month, but I didn\u2019t pick up the actual reason \u2013 just something about most Linux kernel 5.x versions being incompatible with a change. Do not cite me on this. I also learned a bit about the command:<\/p>\n\n\n\n
manjaro-chroot -a<\/pre>\n\n\n\nThis command came in handy. The actual repair consisted of me booting to the live media, mounting my main Manjaro drive (graphically, even), going over to it in terminal, changing root directory per the above command, and updating with<\/p>\n\n\n\n
pacman -Syyu<\/pre>\n\n\n\nIf it actually did anything, I didn\u2019t discern anything. I rebooted to confirm it was still broken to find things seemingly repaired. Was it ever broken? Did I actually fix it? I may never know. In either case, I installed a 4.x kernel listed under KDE\u2019s system settings program on the off chance my successful reboot was a fluke. A further reboot held true.<\/p>\n\n\n\n
Takeaway<\/h2>\n\n\n\n
This fix was only done within 24 hours and no interactive help because I\u2019ve already knew all of the needed skills already. Unfortunately, as I finish writing this post, more update shenanigans appear to be inbound. It appears a new package conflicts with one called wxgtk-common but doesn\u2019t satisfy wxgtk2\u2019s requirements for it.<\/p>\n\n\n\n
Final Question<\/h2>\n\n\n\n
Were you affected by these or a similar Manjaro update?<\/p>\n\n\n\n
I look forward hearing your answers on in the comments below or on my Discord server<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Good Morning from my Robotics Lab! This is Shadow_8472 with a side project of the week. Let\u2019s get started! Surprise! Bad Manjaro update. I seem to be getting them once a year. I rebooted some time last Wednesday, seemingly to a black screen. My first thought this time wasn\u2019t, \u201cOh, no! What am I going … <\/p>\n