Can't boot on manjaro 21.2.1 i3 minimal whereas I can boot on manjaro 21.2.1 xfce minimal edition

,

Hello !

I’m trying manjaro and really enjoying so far. I started with the xfce edition and discover that there were some community editions like i3. I love i3 so I wanted to give it a try. after the installation of manjaro 21.2.1 i3 minimal the screen stays black. There is only a cursor on the top left of the screen.

I bet there is a problem with the grub configuration but I’m not an expert.
Any ideas ?

Hi @S1lentKn1ght, and welcome!

The best, in my opinion, would be to boot with installation media, o0pen a terminal and enter a chroot environment of your system. Once there, you can inspect, and provide the logs:

  • To view the error and warnings from the previous boot:
journalctl --boot=-1 --priority=3

To chroot:

  1. Ensure you’ve got a relatively new ISO or at least one with an LTS kernel.

  2. Write/copy/dd the ISO to a USB thumb drive.

  3. When done, boot with the above mentioned USB thumb drive into the live environment.

  4. Once booted, open a terminal and enter the following command to enter the chroot encironment:

manjaro-chroot -a
  1. If you have more than one Linux installation, select the correct one to use from the list provided.

When done, you should now be in the chroot environment.

But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart. From here, you can run the journalctl command from earlier.

Hope this helps!

1 Like

Hey @Mirdarthos thank you for your answer. here what I have:

[manjaro@manjaro-i3 ~]$ manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/sda5]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro-i3 /]# journalctl --boot=-1 --priority=3              
Jan 30 17:43:51 s1lentkn1ght kernel: x86/cpu: SGX disabled by BIOS.
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/261)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/33030)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/1157)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/2309)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/405)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/661)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/4213)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/9474)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/897)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/49154)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/33105)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/9730)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/38160)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/1941)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/38145)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/49154)
Jan 30 17:43:51 s1lentkn1ght kernel: i2c_hid_acpi i2c-HTIX5288:00: i2c_hid_get_input: incomplete report (27/3593)
Jan 30 17:43:52 s1lentkn1ght kernel: [drm:wait_panel_status [i915]] *ERROR* PPS state mismatch
Jan 30 17:43:53 s1lentkn1ght kernel: sd 2:0:0:0: [sdb] No Caching mode page found
Jan 30 17:43:53 s1lentkn1ght kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
Jan 30 17:43:54 s1lentkn1ght systemd[1]: Failed to start Light Display Manager.
Jan 30 17:43:57 s1lentkn1ght kernel: [drm:wait_panel_status [i915]] *ERROR* PPS state mismatch
Jan 30 17:43:57 s1lentkn1ght kernel: [drm:wait_panel_status [i915]] *ERROR* PPS state mismatch

OK, I can’t see what’s causing this, maybe someone else knows.

In the meantime, try re-synching the system. To do so, run:

pacman-mirrors -f5 --fasttrack && pamac upgrade --aur --enable-downgrade

https://wiki.manjaro.org/index.php/GRUB/Restore_the_GRUB_Bootloader#Chroot_environment

I’ve seen that error every time I’ve chroot ed, so have probably taught myself not even to see it anymore. Yeah, I know. It’s not good. It is, however, the way things are.

Thanks @ishaan2479 for your answer. Could you explain what is the problem please ? I don’t understand why your link solve the problem :pray:

run these commands and reboot (assumming you have a efi system). I wonder why this stuff is happenning on a fresh system :thinking: :

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck 
grub-mkconfig -o /boot/grub/grub.cfg 

hope this helps

Thanks for your answer @anon12891489 here is what I have:

[manjaro@manjaro-i3 ~]$ grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck 
bash: /usr/bin/grub-install: Input/output error
[manjaro@manjaro-i3 ~]$ 

Is this in the chroot environment?

The above error is normal if os-prober probes an USB stick.

No can do - your system is loaded in bios mode and you are trying to install the efi loader

bios loader must be installed on the dev /dev/sdb NOT the partition /dev/sdb1.

IF your device is GPT - for bios boot to work - you need a small unformatted partition (1M) of the type 0xEF02 then installl the grub loader to the device NOT the partition

You need to be certain which mode you are using as they are mutually exclusive - efi loader cannot co-exist with bios loader.

EFI only works with GPT but BIOS can (if not too old) work with MBR or GPT.

I have seen the input/output error on some firmware - I can be caused by too many entries

I actually think it’s being executed outside of the chroot environment, but I’m no expert, so I might be wrong.

Sorry I was not in a chroot environment. This is what I have now:

[manjaro@manjaro-i3 ~]$ manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/sda5]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro-i3 /]# grub-install --target=x86_64-efi --efi-directory=/bocheck
Installing for x86_64-efi platform.
Installation finished. No error reported.
[manjaro-i3 /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_6
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.im
Warning: os-prober will be executed to detect other bootable partiti
Its output will be used to detect bootable binaries on them and crea
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

but unfortunately it still not boot correctly.

@linux-aarhus I don’t really understand what I you have said sorry.

IF your device is GPT - for bios boot to work - you need a small unformatted partition (1M) of the type 0xEF02 then installl the grub loader to the device NOT the partition

How do I know if my disk is GPT ?

Here are my partitions information before the installation of the system

Execute this, from the chroot environment:

test -d /sys/firmware/efi && echo efi || echo bios

it returns efi

Please provide the output of:

mount

And

efibootmgr

from within the chroot environment.

Seeing as the installation seems to have gone fine, it looks like a boot priority thing.

[manjaro-i3 /]# mount
/dev/sda5 on / type ext4 (rw,relatime)
/dev/sda7 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=3957152k,nr_inodes=989288,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
tmp on /tmp type tmpfs (rw,nosuid,nodev,inode64)
overlay on /etc/resolv.conf type overlay (rw,relatime,lowerdir=/run/miso/sfs/livefs:/run/miso/sfs/mhwdfs:/run/miso/sfs/desktopfs:/run/miso/sfs/rootfs,upperdir=/run/miso/overlay_root/upper,workdir=/run/miso/overlay_root/work,index=off,xino=off)
[manjaro-i3 /]# efibootmgr
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 0000,0005,0004,0002,0003
Boot0000* manjaro
Boot0002* Windows Boot Manager
Boot0003* UEFI OS
Boot0004* UEFI:  USB DISK 3.0 PMAP
Boot0005* UEFI:  USB DISK 3.0 PMAP, Partition 2

And now I’m going to ask 1 last question before I give up completely:

Have you played around with boot priority in UEFI/BI9OS? I ask, because everything looks fine, to me at least, so all that I can think of further is that it tried booting from the wrong drive. I know it’s a long shot.

In fact yes in the bios/boot section, I put first the usb key to launch my linux because I’m not sure I can replace the boot loader of windows.
This story is weird as I can boot normally with the xfce version of manjaro

OK, maybe that’s what’s wrong. You’ll have to check and play, because…well…because you’re there and we’re not…at least you can undo any changes you make.