[Solved]Blank dark screen

Same here. And I can't upgrade:

pacman -Syu
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirror.catn.com : The requested URL returned error: 404
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
:: Replace pacman-mirrorlist with core/pacman-mirrors? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: bumblebee: installing mhwd (0.6.0rc1-4) breaks dependency 'mesa-libgl'
:: cairo: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: freeglut: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: glu: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: gnome-session: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: lib32-glu: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: lib32-libva: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: lib32-libva-vdpau-driver: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: lib32-primus: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-mesa-libgl'
:: libreoffice-fresh: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: libva: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: libva-vdpau-driver: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: libvdpau-va-gl: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: mesa-demos: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: mpv: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: qt4: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: qt5-base: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: sdl2: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: steam-manjaro: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: xorg-server: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: xorg-server-xwayland: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'
:: xorg-xdriinfo: installing mhwd (0.6.0rc1-4) breaks dependency 'libgl'

inxi -Gxx
Graphics:  Card-1: Intel HD Graphics 5500 bus-ID: 00:02.0 chip-ID: 8086:1616
           Card-2: Advanced Micro Devices [AMD/ATI] Opal XT [Radeon R7 M265]
           bus-ID: 08:00.0 chip-ID: 1002:6604
           Display Server: X.org 1.19.3 driver: N/A tty size: 107x24 Advanced Data: N/A for root

I'm currently chrooting from a live boot.

My machine is working again. Updating via tty solved the problem for me. But there was no way I could have done todays update the regular way, avoiding the issue. Synced / checked my mirror after reading an update was available. Only manjaro-system popped up and after updating it my system came to a standstill.

Anyway, thank your for your fast reply.

how do I chroot from a live usb? Do you have a link to a wiki?

https://wiki.manjaro.org/index.php/Restore_the_GRUB_Bootloader#Chroot_into_your_existing_Manjaro_Installation

1 Like

I need a bit of help... I booted a Manjaro live usb, but I can't mount/decrypt the LUKS volume:

[manjaro@manjaro ~]$ lsblk -f
NAME   FSTYPE      LABEL     UUID                                 MOUNTPOINT
loop0  squashfs                                                   /run/miso/sfs/livefs
loop1  squashfs                                                   /run/miso/sfs/mhwdfs
loop2  squashfs                                                   /run/miso/sfs/desktopfs
loop3  squashfs                                                   /run/miso/sfs/rootfs
sda                                                               
├─sda1 vfat        ESP       7659-7771                            
├─sda2 vfat        mnjBoot   48A9-EB6B                            
├─sda3 crypto_LUKS           aef0caeb-0eb8-40e4-a658-080287584249 
└─sda4 ntfs        WinRE_DRV 60F9001EF8FFEFE0                     
sdb    iso9660     MJRO170   2017-03-06-22-13-48-00               /run/miso/bootmnt
├─sdb1 iso9660     MJRO170   2017-03-06-22-13-48-00               
└─sdb2 vfat        MISO_EFI  AE2A-7700                            
[manjaro@manjaro ~]$ cryptsetup open /dev/sda3 cryptroot
Device /dev/sda3 doesn't exist or access denied.
[manjaro@manjaro ~]$ cryptsetup luksOpen /dev/sda3 cryptroot
Device /dev/sda3 doesn't exist or access denied.
[manjaro@manjaro ~]$ cryptsetup luksOpen /dev/sda3 crypto
Device /dev/sda3 doesn't exist or access denied.
[manjaro@manjaro ~]$ cryptsetup luksOpen /dev/sda3 crypto_LUKS
Device /dev/sda3 doesn't exist or access denied.

What about simultaneously pressing (logging to tty:

Crtl+Alt+F2

You can try also to use F3, F4, F5 instead of F2 but wait few seconds before you try another combination

Check out this link and I hope it helps you:

Did you try to log into tty? Press:

Crtl+Alt+F2

Yep, I'm one step further... volume is decrypted. It has lvm inside, should I somehow mount that first?

[manjaro@manjaro ~]$ lsblk -f
NAME             FSTYPE      LABEL     UUID                                   MOUNTPOINT
loop0            squashfs                                                     /run/miso/sfs/livefs
loop1            squashfs                                                     /run/miso/sfs/mhwdfs
loop2            squashfs                                                     /run/miso/sfs/desktopfs
loop3            squashfs                                                     /run/miso/sfs/rootfs
sda                                                                           
├─sda1           vfat        ESP       7659-7771                              
├─sda2           vfat        mnjBoot   48A9-EB6B                              
├─sda3           crypto_LUKS           aef0caeb-0eb8-40e4-a658-080287584249   
│ └─crypto       LVM2_member           <UUID>
│   ├─vg0-lvswap swap        mnjSwap   <UUID>   
│   └─vg0-lvroot ext4        mnjRoot   <UUID>   
└─sda4           ntfs        WinRE_DRV 60F9001EF8FFEFE0                       
sdb              iso9660     MJRO170   2017-03-06-22-13-48-00                 /run/miso/bootmnt
├─sdb1           iso9660     MJRO170   2017-03-06-22-13-48-00                 
└─sdb2           vfat        MISO_EFI  AE2A-7700

I managed to upgrade with:

pacman -R lib32-primus
pacman -Syu --force
pacman -S lib32-primus

Then I could start my system just fine.

Sorry can't help you here, beginner myself and never used encrypted disks

Did you try to log into tty? Press:

Crtl+Alt+F2

And try to update the system from there

sudo pacman -Syyu

Okay, I chrooted in succesfully, now pacman runs into some conflicting packages... what to do?

sh-4.4# pacman -Syyu
:: Synchronizing package databases...
 core                                                   138.0 KiB  3.64M/s 00:00 [##############################################] 100%
 extra                                                 1781.7 KiB  6.28M/s 00:00 [##############################################] 100%
 community                                                4.1 MiB  5.49M/s 00:01 [##############################################] 100%
 multilib                                               181.5 KiB  5.91M/s 00:00 [##############################################] 100%
:: Starting full system upgrade...
:: Replace pacman-mirrorlist with core/pacman-mirrors? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: lib32-glu: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: lib32-qt4: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'
:: lib32-simplescreenrecorder: installing mhwd (0.6.0rc1-4) breaks dependency 'lib32-libgl'

I suggest you ask in the forum that was last update posted, maybe someone can help there, I'm too green to help, sorry:

Actually, just to be on a safe side, I would first run these two commands:

sudo pacman -Sy manjaro-keyring
sudo pacman -S manjaro-system

This member seems to had the same problem? Look at his post how he fixed it:

2 Likes

i restored a backup and could update via terminal without any problems.

yet i wonder why the first attempt via gui rendered my system to a complete unresponsive state after installing the 2 manjaro packages?

now here is another little issue: pacman-mirros is now marked an orphaned package. when i try to uninstall it, it fails due to being locked. any ideas?

am i have to download manjaro iso for chroot or arch linux iso also can chroot it ?
and after get live usb what i should do ?

You didn't answer to my previous question, can you log into tty? Because if you can, you probably don't need to do chroot which is a little more advanced.

So first try to log to tty. If this fails, then you can go to next step - chroot which means you will use live USB/DVD to chroot (change root) into your system from outside.

Bellow I will post a link for steps to follow, but simple explanation what chroot is, when you boot your computer from live USB or DVD you are then inside live system, you are not inside your broken system. So, next step is, to access into your broken system from the live system. There are few steps involved though.

You asked if you need Manjaro live usb or Ubuntu will do? You can use any live USB/DVD but Manjaro live USB/DVD will save you few steps, will make chrooting a little simpler.

So what you will do next is this:

A - Easier way:
1 - log to tty
2 - update your system from there

if you can't log into tty, then you will need to do it harder way, but you need to learn it anyway:

B - Chrooting:
1 - chroot your system using steps in the link bellow
2 - update your system from there

Steps to follow:

Those steps above I followed once and they are working. There is some change happened since then, that I'm not sure exactly about. As far as I know if you follow those steps exactly, you should be fine. So just ignore what I will wrote bellow, to not confuse you, it is just some clarification question for others:

@eugen-b
@oberon
@...other experts...

Can any of experts explain exactly which step is now changed and preferred to use when chrooting? Something about instead of using "mhwd-chroot" to rather use "manjaro-chroot" which on it's own is simple enough, but then I have conflicting notes about -a flag. Which of these should be used?

manjaro-chroot /mnt
manjaro-chroot -a
manjaro-chroot -a /mnt

Can anyone with forum admin rights change the tutorial I linked above to reflect latest preferred way of chrooting?

4 Likes

hey hello the thing is that i can not enter tty and i have only arch linux live usb. I am living in dormitory and manjaro iso will be downloaded 14 hours later. So i need to chroot with arch linux live usb but commands which you shared is not found in arch linux chroot

Forum kindly sponsored by