I’ve been interested in Linux for a long time without ever having dared to take the plunge. You have to admit that I’ve been “Apple” since my first computer, which was an IIC, in the late 70s (I’m not very young anymore… :wink:).
Since the disappearance of Steve Jobs, in my opinion, the MacOS evolution policy is beginning to annoy me seriously :rage:: each year a new OS often and more and more often obliges to renew its hardware which has become incompatible (hello planet !)
For example, I regularly work with a “2020” iMac and Ventura, but my Mac-Mini 7.1 is no longer supported.
I didn’t want to try to circumvent this with the available patchers because it doesn’t work optimally.
Issue ? Solution ! : seriously try Linux… :cold_sweat:
Yes, but which Linux?..too many distros to really have a real choice…too many favorable and contrary opinions to get a good idea…
So you have to get your hands dirty and try!
So I started installing some well-known distros on this Mac-Mini 7.1:

  • Ubuntu: too restrictive and a curious policy with Canonical. Unable to get some drivers to work properly.
  • Mint: not so bad, still some drivers not working.
  • Fedora: good if we manage to install it to the end…but I’m not a Linux specialist.
  • Manjaro: lots of random malfunctions.
  • Elementary: less MacOS style. Too limited.
  • Pop’OS, MX Linux, Debian, OpenSUSE, PCLinuxOS…every time something was missing…and the search was tedious to find an answer.
    Ultimately, this quest allowed me to familiarize myself (a little) with the different approaches to Linux through distros.
    I must specify that all the distros tested had their pros and cons, but all of them gave this Mac-Mini 7.1 a second youth.
    On “DistroWatch” I finally spotted EndeavourOS, well placed, but which seemed a little “young” to me with regard to distros like Ubuntu, Mint and others, already prowled (apparently).
    At the point where I was, why not try?
    Surprise ! Easy installation and perfect “out of the box” recognition of the Broadcom 4360 chipset and the Logitech Brio webcam. Installation “on demand” of software like LibreOffice and others. A good wiki. A forum where discussions do not turn to nuclear conflict :bomb:. And lots of easy-to-find solutions.
    My installation of EndeavourOS is not yet perfect but with time, its regular evolutions and the precious help of the forum specialists, it will become, I hope, “my Linux”. For a few weeks, everything has been working fine (with the Gnome interface which is by far my preference over the others).
    However, I remain a bit anxious :fearful: about data security when you install packages from different sources that in the end you don’t know (with MacOS you know…or think you know…that what you install is safe) …but I’m new to Linux and still have a lot to learn.
    In short (thank you for taking the time to read me to the end): long life to EndeavourOS, congratulations to the designers and thank you to the members of the forum.



Ps: a request: why is it necessary to scroll all these lines when starting the OS? :innocent:



linux /boot/vmlinuz-linux-xanmod-anbox root=UUID=27278b37-506e-4fd7-915c-77d394e42b14 rw loglevel=3 audit=0 quiet splash vt.global_cursor_default=0 ibt=off

/boot/grub/grub.cfg :: (edit with ‘sudo nano’ or sudo thunar (any file manager) and open with mousepad )
if you do not have the word ‘quiet’, just add it and the boot will be quiet.


Thank you !
…but could you be more explicite for a Linux beginner ?

I understand you have to open the file “/boot/grub/grub.cfg” and make the modification as “linux /boot/vmlinuz-linux-xanmod-anbox root=UUID=27278b37-506e-4fd7-915c-77d394e42b14 rw loglevel=3 audit=0 quiet splash vt.global_cursor_default=0 ibt=off”

Am I right ?



Not really. This file will get overwritten the next time you regenerate your grub.cfg.

If you are using Grub, make the proposed change to the file /etc/default/grub.
just add quiet to other already present parameters in the line that begins with:


Afterwards, you need to run:

sudo grub-mkconfig -o /boot/grub/grub.cfg

No, sorry for not being clear enough.
Just add the word quiet and leave others alone (don’t make any other changes)
By the way, many Os’s told me that /etc/default/grub/ was not a good choice, it’s after grub. Ex. ibt=off does not work in it.
So i never did anything in that directory in the past.

I don’t have a file “grub” in my /etc/default ?

/etc/default/grub ::
GRUB_CMDLINE_LINUX_DEFAULT=“loglevel=3 audit=0 quiet splash vt.global_cursor_default=0”

Then you are most probably using systemd-boot and not Grub.
You need to add the parameter to /etc/kernel/cmdline

How to modify kernel options

In systemd-boot, it is actually quite simple. You edit the appropriate entry file which can be found on your EFI partition in the loader/entries directory. Each entry is a boot option on the menu and each has a line called options. You can modify these entries directly, however, these changes may be overwritten when packages are installed or updated.

To make the changes, instead of modifying the entries, modify the file /etc/kernel/cmdline which is a one-line file containing a list of kernel options. Then run sudo reinstall-kernels which will populate the entries and regenerate the initrds.

If you would prefer to use the current kernel options from the running system, you can instead rm the file /etc/kernel/cmdline and then run sudo reinstall-kernels.

:eye: https://discovery.endeavouros.com/installation/systemd-boot/2022/12/



Here is the only line in /etc/kernel/cmdline :

nvme_load=YES nowatchdog rw root=UUID=9ee5bba6-4ea1-45a2-bf1c-6cd57835175b

Where can I put the modifications ?

Add the word quiet to this line.

nvme_load=YES nowatchdog rw root=UUID=9ee5bba6-4ea1-45a2-bf1c-6cd57835175b quiet

Then run: sudo reinstall-kernels


hmmm - I like that, one can see what’s going on… :wink: :male_detective:


Stupid question :slight_smile:
How edit the file : /etc/kernel/cmdline ?

there are no stupid questions ever

you may do it with a texteditor in filemanager
or an editor in the terminal, e.g. sudo nano /etc/kernel/cmdline

1 Like

For a terminal editor, you could use nano:

sudo nano /etc/kernel/cmdline

Use the arrow keys to navigate. When done editing, press the following keys one after another:
Ctrl-O, Enter, Ctrl-X.

You are done.

If you want to use a GUI editor, you could use xed for example:

xed admin:///etc/kernel/cmdline

Don’t bother about the warnings.

1 Like

moi aussi :rofl:
are you coming of France ?
(because you started your post with “bonjour” )

Yes, I am from France !

1 Like

Thank you !

It just work perfectly !

And now I’m able to use nano !



Il n’y a de pas de quoi!


yea no stupid questions known here at all… there is simple no such thing !

Can i do ask a… stupid question?

What Desktop Evironment you have installed? gone with the default offline install and using XFCE4?

1 Like

Yes, I installed Gnome as DE using the “online” installation from the live media.