Manjaro XFCE won't boot on iMac

I already have a topic for Manjaro KDE. I wanted to try Manjaro XFCE to see if it would work, and I think it has a slightly different issue. I edited the grub menu by adding splash, noapic, nolapic, nomodeset, and systemd.mask=tlp.service, plus I switched all [graphics driver].modeset=1 to [graphics driver].modeset=0

I think the last edit is necessary, because when I tried booting without it, the screen went black instead of showing information.

When the screen did show information, I saw an "Error No UMS support in radeon module" followed by a lot of text, followed by "Failed to start Lightdm". I pressed Ctrl-Alt-F6, logged in, and ran the following commands:

$ sudo pacman-mirrors -f3
$ sudo pacman -Syyuu
$ sudo pacman -S lightdm lightdm-gtk-greeter lightdm-gtk-greeter-settings
$ sudo systemctl enable lightdm
$ sudo lightdm
$ systemctl status lightdm.service

The second to last command also failed. The last command showed the following (roughly):

lightdm.service: Main process exited, code=exited, status=1/FAILED.
lightdm.service: Failed with result 'exit-code'.
lightdm.service: Service restart job, restart counter is at 5.
Stopped Light Display Manager.
lightdm.service: Start request repeated too quickly.
lightdm.service: Failed with result 'exit-code'.
lightdm.service: Failed to start Light Display Manager.

You absolutely don't need that.

To understand what whose do, please read


You posted them on the other topic too

But are nowhere to be found as referenced in the iMac arch wiki install page.
https://wiki.archlinux.org/index.php/IMac_Aluminum
There is no need to make things up and add all the custom kernel boot parameters that exist ... Focus on what i told you previously.
Something else you might consider is to try the approach mentioned in the rEFIt boot ...

1 Like

I had some of those options because I read this discussion: https://askubuntu.com/questions/52096/what-do-the-different-boot-options-mean-i-e-acpi-off-noapic-nolapic-etc

I wanted splash because I wanted to see what was going on. I'll leave all these out, because they don't seem to make a difference.

I've tried systemd.mask=tlp.service multiple times, and the screen stays black. I only see text when I change the graphics drivers modesets to 0. The text goes on for a bit, then the screen clears, then I see:

[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
         Starting Light Display Manager...
[  OK  ] Started Light Display Manager.
[  OK  ] Stopped Light Display Manager.
[FAILED] Failed to start Light Display Manager.
See 'systemctl status lightdm.service' for details.
[  OK  ] Started Initialize Pacman keyring.
[  OK  ] Reached target Multi-User System.
         Starting TLP system startup/shutdown...
[  OK  ] Reached target Graphical Interface.
[  OK  ] Started TLP system startup/shutdown.
_

I can't type anything at this point, but I can press Ctrl-Alt-F6 and use a command line.

When I ran:

$ sudo pacman-mirrors -f3
$ sudo pacman -Syyuu

I noticed an error and a waning a few lines up from the prompt:

(11/20) Updating Grub-Bootmenu
/usr/bin/grub-probe: error: failed to get canonical path of `overlay'.
error: command failed to execute correctly
(12/20) Reloading system bus configuration...
(13/20) Warn about old perl modules
(14/20) Compiling GSettings XML schema files...
(15/20) Updating icon theme caches...
(16/20) Restore Linux kernel modules

==> Warning:
         -> Kernel has been updated. Modules of the current kernel
         -> have been backed up so you can continue to use your
         -> computer. However, the new kernel will only work
         -> at next boot.


I don't know if the warning is important, but I think the error is because this is a live boot. I remember when I was installing Ubuntu from a flash drive I went on an unsuccessful chase through multiple forums because of failed to get canonical path of cow while trying to run sudo update-grub, and when I got it on the computer I never saw that problem again. Is there any way I can get Manjaro onto the computer from the command line? It might help.

Honestly, that will not help you in live media at all. I don't understand what you want to achieve with that. Any modifications on live media install will not survive after reboot and the updates will not work "on the fly" ...
If you used systemd.mask=tlp.service you should not have this:

Is quite important in grub to press e to edit the BOOT line of the menu from live media installer ... add that kernel boot parameter, not elsewhere in the menu ...

Yes, here are the best instructions:

I've been trying to install Manjaro from CLI. I have successfully partitioned the disks and made the filesystems. I have 5 partitions, one for EFI, one for swap, one for root, one for home, and one for Mac (for firmware updates). I can't mount anything.

[manjaro manjaro]# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0  16.3M  1 loop /run/miso/sfs/livefs
loop1    7:1    0 540.9M  1 loop /run/miso/sfs/mhwdfs
loop2    7:2    0   1.7G  1 loop /run/miso/sfs/desktopfs
loop3    7:3    0 580.2M  1 loop /run/miso/sfs/rootfs
sda      8:0    0 465.8G  0 disk
|—sda1   8:1    0   300M  0 part
|—sda2   8:2    0     2G  0 part
|—sda3   8:3    0    32G  0 part
|—sda4   8:4    0 381.5G  0 part
|—sda5   8:5    0    50G  0 part
sdc      8:32   1  29.3G  0 disk
|—sdc1   8:33   1   2.9G  0 part /run/miso/bootmnt
|—sdc2   8:34   1     4M  0 part
sr0      11:0   1  1024M  0 rom
[manjaro manjaro]# mount /dev/sda3 /mnt
mount: /mnt: unknown filesystem type 'ext4'.
[manjaro manjaro]# mount /dev/sda1 /mnt/boot/efi
mount: /mnt/boot/efi: unknown filesystem type 'vfat'.
[manjaro manjaro]# mount /dev/sda4 /mnt/home
mount: /mnt/home: unknown filesystem type 'ext4'.
[manjaro manjaro]#

I searched online, but I couldn't find any solutions that worked for me.

By the way, this time the SDDM (I'm using the KDE) started successfully, and the messages stop at [ OK ] Reached target Graphical Interface. After that is a blinking underscore, and I can use the tty's without any problems.

This should help


But, i have two questions regarding this:

Why do you need that and not go with the simplest one? From where did you created those partitions since initially that was probably a HDD with a EFI and a HFS+ partition for MacOS?

After the last error message, I pressed Ctrl-Alt-F2, then logged in and tried the CLI method. I had Ubuntu before, and Mac OS before that. So far, the computer doesn't have any OS. I haven't reinstalled Mac OS yet.

Can you boot with a live medium? usb stick or DVD?

Forum kindly sponsored by