can it be a live cd? i’d rather try your way because your instructions are clear, gohgimp are not
the iso image must be able to fit in the cd/dvd. i would highly recommend any 2GB+ old usb you might already have.
you can use what you used to install manjaro in the 1st place =)
to be more clear
i can still go into tty2 and do the update but it says “nothing to do”
i reboot and after the manjaro loading screen it goes to the blinking cursor screen. it never makes it to the user login screen.
You are using an Arch based distro and you don’t want to “learn about Linux troubleshooting”? Then maybe you should consider a non rolling Linux distro. I’m not being passive aggressive here, it is genuinely something you should consider.
Manjaro is a leading edge rolling Arch based distro, every now and then there will be a bump in the road. That is the trade off when you are using the most recent version of kernels, drivers, DEs, system components and apps. Every effort is made to catch issues before they hit Stable repos, but occasionally something will slip between the cracks.
Hopefully the Manjaro community can help get you back up and running soon.
might be a good idea to open a new thread then. more people from the community will have a chance to see it and get involved. you will be fine.
Petulance won’t get your issue solved any faster.
If you want stability, install Debian stable.
If you want convenience, check out Linux Mint.
If you want to learn about Linux, install Arch.
If you want Arch with a reasonable amount of convenience and stability, install Manjaro.
Manjaro is Arch-based. Cutting edge software and frequent updates come with inherent risk to the end user. Manjaro will never be as stable as other slower, and more conservative, distributions.
I am really not trying to chide you here. But if you use Manjaro, these problems are absolutely, positively, going to happen at some point. Don’t be surprised when they do.
20 posts were split to a new topic: Manjaro debates: How to avoid Stable updates breaking the system?
Manjaro debates: How to avoid Stable updates breaking the system?
i’ve spent all day installing arch. very hard. the current kernel is now 4.7.6
I have to apologize for my last post, I came from a long flight and was deadly tired (never update a system when being sleepy… lesson learned…).
Anyway, I managed to recover my installation by using a LiveCD with Manjaro, chroot into my system and repaired the broken update by reinstalling the packets that got upgraded based on the pacman.log. I guess the issue was that I rebooted too fast after the XSession got lost and interrupted the installation at an critical point. Now I’m up-to-date and everything is working as expected. Updated another system by switching to the tty and everything worked like a charm directly.
This may help…
I’ve just done the update following the recommendations: TTY2, sudo pacman -Syu, all perfect. Just only get the black screen at the end, but after pressing Ctrl + Alt the TTY returned. Then I’ve rebooted and logged in my session as usual.
Thank to the Manjaro Team!!
PD: Just FYI, my kernel is default 4.4, free Radeon drivers and only a few and necessary packages installed from AUR.
The same for me. Fortunately nothing worse. Gruss aus Zürich
No black screen, but intermittently the system will completely freeze forcing a hard reset. Lesson learned to not update immediately. Thanks for the effort though and good luck to you guys smoothing things out!
Hi! Update went fine:
- updated from TTY without any other logged session.
- haven’t updated the 3 systemd packages mentioned by @philm at top of the thread. I’ll wait for the next release of systemd.
Some suggestions for those stuck at a black screen after successfully booting grub:
Try to downgrade libsystemd, systemd and systemd-sysvcompat packages:
- login through TTY as root (or use sudo if you don’t)
ls /var/cache/pacman/pkg | grep systemd
- note the filename of the previous version of the 3 packages mentioned above. On my system they are libsystemd-231-1-i686.pkg.tar.xz, systemd-231-1-i686.pkg.tar.xz and systemd-sysvcompat-231-1-i686.pkg.tar.xz (this might differ in your system).
# pacman -U /var/cache/pacman/pkg/libsystemd-231-1-i686.pkg.tar.xz /var/cache/pacman/pkg/systemd-231-1-i686.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-231-1-i686.pkg.tar.xz
# reboot now
If this doesn’t work and you use proprietary drivers (especially nvidea ones, because they seem more problematic), try to do the same with those or switch to free drivers to see if the problem goes away.
If this still doesn’t work try an older kernel (linux41, for example).
If I’m completely wrong and peeing off the pot, sorry! Just trying to help.
I use krusader-git in KDE and i3 and it doesn’t seem to depend on qt4. I had to install some KDE packages on i3 for it work properly, including plasma-workspace and kuiserver5 (it works fine without it, but things like thumbnailing and networking need extra packages). However, I don’t start KDE as I login (only kuiserver5), so I don’t get the memory footprint. Krusader only uses kio slaves as it needs and then turns them off. It works much better that krusader 2.4.0.
screen went black during the update.
upgrade of lightfirefox-49.0-1 (from lightfirefox-48.0-1) was unstable. Had to move the entire browser window to see changes.
re-installed lightfirefox-48.0-1 which runs stable.
will monitor and report if see other issues.
Bad update here
Screen went black during while updating systemd. The system went off a few seconds later. Now it’s broken.
I’ve already tried $ sudo fsck /dev/sda -f and $ sudo fsck /dev/sda -y to try to solve the non-contiguos part (in a live midia). Now the command says that everything is “clean” but the system is still dead.
I don’t know whatelse to do.
- Try to boot with a different kernel and check /var/log/pacman.log which package didn’t update as it should, reinstall it with
sudo pacman -S --force
- Or boot with a Manjaro install medium, chroot with
mhwd-chroot, check pacman.log and reinstall the package with --force or re-run the update with pacman -Syyu --force.
I cannot boot after the recent update, what should i do after chroot?
Thanks for your help, the problem was in the kernel 4.7.x
It was missing a file according to the log file. I will remove it, update the system and than maybe reinstall it or stay in the kernel 4.4.
Hi, this error happend only with the kernel 4.8, I have connected a Verbatim universal card reader.
scsi host9: runtime PM trying to activate child device host9 but parent (1-4:1.0) is not active
I also had a freeze ( kernel 4.8), but I could not find the reason for this.
Successful update using the pacman tty method on KDE.
As a linux newb I got stuck after the update on how to get out of tty-- I used Ctrl + Alt + Del, which closed tty and rebooted, and that worked perfectly.