Belajar Agar Berkembang

Selasa, 19 November 2024

Installing the Much Hyped Hyprland on Linux

Hyprland is a dynamic tiling window compositor that is both highly customizable and eye candy.

It is also used the most these days in Linux ricing group. And why not? If you are into customizing the looks of your desktop, Hyprland is surely worth all the hype.

In fact, the official Hyprland video provides more detailed visuals:

Now, I am not trying to discourage you, but these things take a lot of effort if you try to configure on your own. Or, you can use the dot files from someone else and get the same look as theirs.

I believe it's a good learning experience but something that should be done on a secondary system. At present, it is not officially supported in VMs but it still worked for most in my testing.

🚧

Hyprland is in highly active development. So, there won't be any one stable version that you can use for years, similar to what Ubuntu and Debian does for GNOME.

Things to note before installing Hyprland

Before starting to install Hyprland, you need to understand a couple of points about stability and compatibility.

Hyprland is not a beginner-centric window compositor.
It is Wayland-only. So, not all Xorg-only application will work on Hyprland.
Nvidia GPUs have limited compatibility due to their proprietary nature.
It is not officially supported in virtual machines, but works. So, to get a complete result, you should do it in bare metal.
If you are installing on a virtual machine, like VirtualBox, enable 3D Acceleration. Moreover, allow a RAM of at least 4 GB.

🚧

I suggest either you try it in a spare machine first, or keep another stable window manager in the system, so that you don't lose your work while experimenting with Hyprland.

Install Hyprland with Arch Linux using archinstall script

Arch Linux, NixOS and openSUSE Tumbleweed are the most supported distribution when it comes to Hyprland.

In Arch Linux, if you are using the archinstall script, you have an option to select Hyprland as the desktop in Profile → Type → Desktop → Hyprland.

As you can see in the screenshot above, the installer has selected some necessary dependencies for Hyprland to work.

On the next step, it will ask you to have access to hardware. Here, I have gone with Polkit.

Similarly, the greeter will be automatically set to SDDM.

📋

If you are installing Hyprland as the only option, it is better to select SDDM. In case you are installing Hyprland on a GNOME setup, there is no need to install and configure SDDM, as GDM just works fine.

On the additional packages installation prompt, install hyprpaper and waybar. Or do that after install and login.

sudo pacman -Syu hydrpaper waybar

📋

Hydrpaper is the wallpaper manager and Waybar is the bar, that host necessary panel buttons.

That's it. You will have a working Hyprland set up.

🚧

Hydrpaper needs to be enabled and configured to get a proper wallpaper to your screen. This will be discussed in another article.

Install Hyprland in base install

If you have installed Arch Linux base installation following our guide, then you need to install the Hyprland separately. To do that, log in to the base install and run the command:

sudo pacman -Syu hyprland hyprpaper xdg-desktop-portal-hyprland waybar wofi kitty sddm

Then enable the SDDM service using:

sudo systemctl enable sddm.service

Now, restart the system and login to Hyprland session.

Install Hyprland in Ubuntu

Hyprland is also available in the default repo of Ubuntu since 24.10 Oracular Oriole. But it is highly not recommended to install Hyprland from this package.

Instead, I will discuss another method, through which you can set up a working Hyprland on Ubuntu.

🚧

Here, I am using Ubuntu 24.0.1 as the distro. The method mentioned below has separate repositories for other versions. Please check you Ubuntu version before continuing.

Things to keep in mind before proceeding

You should back up your system and important data before start installing.
Ensure an active, uninterrupted internet connection.
Version older than 24.04 won't work.
Do not install SDDM.

Once you are ready, let's install.

Install Hyprland in Ubuntu 24.04

First, you need to enable the source packages repo in Ubuntu. Search for Software and Updates and open it.

Go to the tab and enable the checkbox near sources.

Click on close, and then use the Reload button. Now, update your system and install all pending updates.

sudo apt update && sudo apt upgrade

We use the Automated Hyprland Installer for Ubuntu to install Hyprland on Ubuntu. This offers a fast method to get started with Hyprland.

Ubuntu-Hyprland

🚧

There are methods to build Hyprland from source, but there are many hiccups included, which will put you in a long troubleshooting loop.

Clone the Hyprland installer third-party repository.

git clone -b 24.04 --depth 1 https://github.com/JaKooLit/Ubuntu-Hyprland.git ~/Ubuntu-Hyprland-24.04

Now, move inside the directory and give the installer file (install.sh) execution permission.

cd ~/Ubuntu-Hyprland-24.04
chmod +x install.sh

Run the installer.

🚧

You should NOT run the installer as root.

./install.sh

This will start the installer.

🚧

Only Hyprland up to v0.39.1 is compatible with Ubuntu 24.04. This is because of the version of required dependency in the Ubuntu repo remains as is, and Hyprland is a heavily active project, that changes the dependency requirements quite often.

Read the note carefully and proceed by entering y.

Now, some questions will be asked on the topics:

NVIDIA GPU: Hyprland may not work properly with NVIDIA, as said in an earlier section.
Install GTK Themes for Dark Light function.
Configure Bluetooth
Install Thunar file manager.
Install SDDM: This should be NO (n). Since Ubuntu has GDM and it works well.
Install XDG-DESKTOP-PORTAL-HYPRLAND: This should be YES (y).
Install ZSH
Install nwg-look: This is for GTK Theming. It will take a long time to build. So you can skip (n) this.
Installing on Asus ROG Laptops.
Preconfigured Dot files: Yes (y), if you don't want to configure the looks from scratch.

When asked, enter the sudo password to start installation.

Sit back and wait, while the installer completes the set-up process.

When asked, “Would you like to try to remove other XDG-Desktop-Portal-Implementations?”, give no.

Similarly, at the last stage, you will be asked to add yourself (the current user) to the input group. This might be necessary for some waybar functionalities.

If you are running in a VM and/or selected dot file install option, you will be asked more configuration options like:

Select keyboard Layout
Set Monitor resolution
Set time format
Keep/disable rainbow border animation.

These are shown in the screenshot below.

It also provides an option to download more wallpapers, but the size is greater than 600 MB.

Once all queries are answered properly, it will set the configuration accordingly.

Reboot the system.

When the system is rebooted, select the Hyprland session and Log in using your password.

You will be logged into the Hyprland desktop session.

Installing Hyprland in other Distributions

Hyprland is available in the repos of many other Linux distributions like openSUSE, Fedora, etc. The basic installation can be performed on these devices using:

In Fedora,

sudo dnf install hyprland

There is also a COPR repository for Fedora users for more updates.

In openSUSE

sudo zypper in hyprland

You can read the official detailed installation manual for other distribution.

I'll be covering the waybar configuration and Hyprland customization tips in future articles. Stay tuned and subscribe to our FOSS Weekly newsletter so that you don't miss them.

from It's FOSS https://ift.tt/HEB9eG4
via IFTTT

Benchmarking Your Linux System: What, Why and How

If you are using Linux on your system, it is a rare phenomenon that your system is not performing well.

But, "how fast?" is a question that we often ask ourselves or wonder when thinking to compare our experiences.

The easy and effective solution to know that is to benchmark your Linux system.

So, how do you do that? Using some benchmarking tools. And, what are the benchmarking tools available on Linux?

Fret not, in this article, I shall guide you with the tools with which you can perform a Linux system benchmark for all kinds of use-cases.

✋

Benchmarking is not the complete story. But, only a part of it when comparing or evaluating the performance of a system.

To ensure your system runs the best, you need the correct drivers, up-to-date software, performance-focused desktop environment, a stable kernel, and a few other things.

How to evaluate the benchmark results?

With every benchmark tool, you end up getting a final score.

The score alone is not meaningful unless you have a comparison in mind.

You can either perform benchmarks on two different systems to measure the performance gap. Or, you can benchmark the same system at different time intervals to check if a configuration/system update impacted the performance in any way.

For example, you benchmark the system right after you set it up for the first time, and then after a few months.

Some tools also provide you with access to a leaderboard chart, where you can see scores of systems with various hardware configurations. You may also find them mention a "baseline" which is a reference score of a particular hardware.

For instance, Geekbench utilizes 2500 as baseline score, which is for an i7-12700 processor. You can know if your CPU performs better or worse accordingly.

In either case, you can check the Geekbench website that ranks all processors, and then compare it against your score.

It is recommended to use the same benchmark test/tool when comparing multiple systems.

4 tools that can help you benchmark your Linux computer

Some benchmarking tools are open source, while a few are not. Some are available as a standalone tool for a quick check, and some help you take an in-depth analysis of your system (which is not needed for everyone).

I list the best ones to help you get the job done.

📋

Most of the benchmarking tools are CLI-based.

1. UnixBench

Key Features:

• Traditional test
• Open Source
• Easy to Use

One of the most traditional open source benchmark suite is UnixBench.

It is derived from the original BYTE UNIX benchmark app built back in 1983, and has been maintained over the years with several revisions. It may not be the most modern solution out there, but it performs essential tests that have been long proven to be indicators of performance.

You get around ten different tests which include basic 2D/3D graphics, process creation, string handling, floating-point operations, file copy, and a couple of others.

It is alright if you do not understand the meaning of the tests it performs. All you need to know is that it performs a type of stress test of your entire system (not just a part of it). So, the results will depend on the operating system, libraries, hardware, and compiler.

Once installed, you just have to run it by typing the following command:

ubench

Here's how the results look:

As you can see in the screenshots, as the test progresses (and completes), you can head to the mention directory (usr/lib/unixbench/results) to get the details. You should find HTML and log files, access what you are comfortable with.

You can install it via AUR for Arch Linux. And, for Ubuntu-based distros, it is available as a Snap.

💭

UnixBench could be an older generation of benchmarking tests, but it has its benefits of technical testing and being an open source tool. No options to fiddle around, just type in one command after installation to start benchmarking, it is that easy!

UnixBench

2. Geekbench

Key Features:

• Modern benchmark suite
• Cross-Platform
• Proprietary
• Uploads results to Geekbench website directly

If you want a modern tool to benchmark your entire system and do not mind if it is not open source, Geekbench is one of the most popular option.

There is no binary available for Linux distros. However, you just have to download a tar.gz file and run the executable via the terminal (no need of sudo) using the following command inside the extracted folder:

./geekbench_x86_64

It worked like charm for me.

It will automatically start running single-core, and multicore tests like Ray Tracer, File Compression, HTML5 browser test, PDF Renderer, and several others. In my testing, it took around 2–5 minutes to complete.

All you have to do is click on the URL provided to check your results.

💭

Geekbench testing requires an active internet connection unless you have its Pro edition. So, it uploads the results to its website, and gives you a URL to check the result. It is a neat experience if you do not mind uploading your results.

Geekbench

3. Hardinfo2

Key Features:

• Graphical User Interface
• Open Source
• Easy to Use

Hardinfo2 is a multipurpose tool with which you can get essential information on your system's network, firmware, and hardware. And, of course, it lets you run benchmarks.

Unlike the above two tools, it does not perform a complete benchmark, but allows you to choose what to test (CPU/Memory/Storage/Graphics).

And, it is a complete GUI program. So, you do not need type any commands. Just head to the test you want to perform, and once it is done, it will show you the result along with a reference ranking compared to other hardware.

You can decide to generate a report for all the benchmarks you perform (HTML file) and access it separately.

I installed it via AUR on Arch Linux. You can find it in your default Linux repositories. In either case, you can build it from source using the instructions on its GitHub page.

💭

Hardinfo2 is a wondering GUI-focused benchmarking tool. The tests finish up fast, and it is easy to test all kinds of parts in your system. Not to forget, you can get essential system information with this tool, so you will want to keep it around after testing.

Hardinfo2

Suggested Read 📖

4. Phoronix Test Suite

Key Features:

• Cross-Platform
• Open Source
• Comprehensive tests for advanced users

One of the most advanced (and useful) benchmark applications is the Phoronix Test Suite. While it is available for all platforms, you can expect the full feature-set on Linux, for which it is tailored for.

It has a massive collection of tools that are installable, as per your requirements. For instance, you can install Geekbench from within the Phoronix Test Suite. Of course, that is a bit redundant in our use-case.

I had to install the suite first, then the test(s) I wanted to perform, and then run them.

The command for installing a test and running it looks like (ignore words with #):

phoronix-test-suite install pts/sysbench #installing 
phoronix-test-suite run pts/sysbench #running

Unfortunately, some tests like pts/browsers failed, while pybench (benchmark inspired by geekbench) and sysbench (open source benchmark) tests worked like charm. If you wish to test various aspects of your system using a set of tools (not just limited to one), Phoronix Test Suite is for you.

Moreover, it makes use of OpenBenchmarking.org to which you can upload your test results, and compare it with great details with other combination of hardware.

You can install the suite via AUR for Arch Linux with phoronix-test-suite as the package name or download the deb package from its GitHub releases for Ubuntu-based distros.

💭

Unlike hardinfo2, it is CLI-based. But, it gives you all kinds of interactive options when you start a test. Things like if you want to save a report, the name of your system, and more. If you follow its documentation correctly, you can perform a comprehensive analysis of your system.

Do you really need benchmarking?

It depends on what you are looking for but benchmarking could give you some ideas about how your computer is performing with the operating system.

For instance, when I switched from Ubuntu to Archcraft, and I noticed a few performance improvements. In my case, there were visual indicators for me to say that.

But, in many scenarios, you cannot easily gauge the difference unless you extensively use/keep track of file extraction times, boot times, CPU performance, and other resource efficiency/usage stats.

Similarly, maybe you are switching to another distro, and want to check the performance difference. Or, perhaps, you just built a new computer, and want to test the waters before you start using it.

Benchmarking Linux can be helpful in such cases.

💬 Do you perform a system benchmark? Let me know your thoughts in the comments below!

from It's FOSS https://ift.tt/3BaC4cI
via IFTTT

Minggu, 17 November 2024

What's the Deal with Raspberry Pi's New SD Card? A Hands-On Review

The Raspberry Pi Foundation recently introduced a new microSD card specifically designed for their beloved range of single-board computers.

As an essential component for Raspberry Pi enthusiasts, the microSD card plays a vital role in ensuring smooth operation, quick access to data, and stability for various projects.

This launch aims to enhance user experience, but how does it really stack up? In this review,

I’ll dive into its features, capabilities, and real-world performance compared to industry heavyweights like Samsung, WD, and HP.

Specifications

A2 microSD cards with support for DDR50 and SDR104 bus speeds and command queueing (CQ) extension
Speed Class: C10, U3, V30, A2
Random 4 KB read performance: 3,200 IOPS (Raspberry Pi 4, DDR50) 5,000 IOPS (Raspberry Pi 5, SDR104)
Random 4K write performance: 1,200 IOPS (Raspberry Pi 4, DDR50) 2,000 IOPS (Raspberry Pi 5, SDR104)
Shock-proof, X-ray–proof, and magnet-proof
32 GB32 GB, 64 GB, or 128 GB capacity
Available unprogrammed or pre-programmed with Raspberry Pi OS.
microSDHC / microSDXC formats
Compatible with microSDHC- and microSDXC-supporting host devices

Key features and capabilities

The new Raspberry Pi microSD card, developed in partnership with Longsys (the same company behind Amazon Basics SD cards), promises a significant boost in performance, especially when paired with Raspberry Pi’s Operating System.

This is largely due to the implementation of Command Queuing in the OS, which is said to streamline tasks and enhance read/write speeds.

Raspberry Pi offers these cards in several capacities (32 GB, 64 GB, and 128 GB), aiming to cater to a wide range of users, from casual tinkerers to professional developers.

What sets these cards apart, at least on paper, is the claimed optimization for the Raspberry Pi ecosystem.

But before we get into the performance side of things, let's decode some of the cryptic symbols and terms you might find on your typical SD card.

A2, UHS, and Speed Classes: What are they?

When shopping for SD cards, you’ve likely noticed terms like A2, UHS-1, and U3.

These aren’t just marketing fluff but provide valuable insights into a card’s performance capabilities.

A2 (Application Performance Class 2): SD cards with an A2 rating are optimized for running apps, meaning faster random read/write speeds—crucial for Pi users running lightweight applications or databases.
UHS (Ultra High Speed): UHS-1, UHS-2, and UHS-3 refer to the card’s bus speed. UHS-1 can theoretically hit 104 MB/s, while UHS-3 is significantly faster, but only certain devices can leverage this speed.
Speed Class: This is often denoted by a number inside a circle or a U-shaped symbol (e.g., Class 10 or U1). Class 10 or U1 cards guarantee a minimum write speed of 10 MB/s, essential for recording HD videos or handling large data files.

The new Raspberry Pi microSD card falls under the A2 and UHS-1 categories, meaning it should handle both general file operations and some light app hosting without much fuss.

But how does it perform in the real world?

Performance: Raspberry Pi SD card vs. the competition

🚧

The performance of SD cards can vary depending on the device, environment, and testing setup used. For the purpose of this article, all SD cards have been tested using the Raspberry Pi's inbuilt card reader to ensure consistent results across the board. However, real-world performance may differ slightly based on your setup or if using an external card reader.

I ran a series of tests to gauge how the official Raspberry Pi SD card compares to industry leaders like Samsung, Western Digital, Sandisk & HP.

Using the fio tool for benchmarking, I measured sequential read/write speeds, which are essential metrics for evaluating performance in Raspberry Pi setups.

Here’s how the 64 GB Raspberry Pi card stacked up:

💡

All the 16 GB cards are a decade old from my old camcorder, I just tested them for fun.

and here's the data for Random read/ write performance:

Command queuing advantage?

While most cards performed similarly in sequential operations, the Raspberry Pi microSD card’s advantage became apparent in random operations, thanks to Command Queuing.

This feature significantly boosted random read/write speeds, especially in the 32 GB and 64 GB variants, offering up to 3x the performance boost compared to alternatives like the Samsung EVO Plus and WD Purple.

Summary of the benchmark tests

Based on these benchmarks, the new Raspberry Pi microSD card is clearly optimized for its target hardware, excelling in random read/write speeds where it matters most for Raspberry Pi users running complex workloads or multiple apps.

But does that mean you should rush out to buy one?

Pros

Optimized for Raspberry Pi OS: The card works best with the OS it was designed for, offering clear performance advantages.
Command Queuing: This feature sets it apart from the competition in specific use cases like random operations.
Value in Certain Markets: In the EU, these cards are priced competitively, often undercutting brands like Samsung and Amazon Basics.

Cons

Availability and Pricing: In some regions, like the US, the card is priced at a premium. You may find better value in alternatives like Samsung or Western Digital for similar sequential performance.
Performance Plateau: The performance gains taper off at higher capacities, making the card less appealing for users needing 128 GB or larger storage.

Verdict: Should you buy?

This decision comes down to price and specific needs. If the card is priced reasonably in your region, and you’re after those random performance boosts, it’s worth considering.

Otherwise, plenty of alternatives can provide the same speed without the extra markup.

Conclusion

Raspberry Pi’s official microSD card delivers on its promise of enhanced performance, especially when paired with the Raspberry Pi OS and its unique Command Queuing feature.

It’s a solid choice for those looking to maximize their Pi’s potential, but depending on where you are and how you use your Pi, it might not always be the best bang for your buck.

Evaluate your needs, check the pricing in your region, and make an informed decision that works best for you.

from It's FOSS https://ift.tt/tWzlNgG
via IFTTT

Sabtu, 16 November 2024

This Simple Change Improved the Performance of My Homelab Running on Raspberry Pi

Running a homelab on a Raspberry Pi can be a rewarding yet challenging experience. My journey began with a Raspberry Pi 4 (4 GB) hosting several WordPress websites and a few Ghost blogs.

Recently, I became more ambitious, aiming to expand my setup with Nextcloud for private cloud storage and ONLYOFFICE to create a fully self-hosted ecosystem. This is where things got interesting and a bit messy.

Adding Nextcloud and ONLYOFFICE to the mix put a significant strain on my Pi 4, leading to slowdowns, occasional freezes, and a slew of input/output errors.

After some investigation, I found that the default 200 MB swap memory was entirely maxed out.

Curious, I thought, “Why limit it to just 200 MB? Let’s see what happens if I increase it.” So, I expanded the swap space to 2 GB, and my Pi started running noticeably smoother.

Here’s how I did it, and some tips if you're considering the same.

Prerequisites

To follow along, make sure you have:

A Raspberry Pi running Raspberry Pi OS.
Access to a terminal (either directly or via SSH).
Sufficient free space on your SD card for the additional swap.

Step 1: Turn off the current swap

Before resizing the swap file, you’ll need to turn off the active swap space. Run the following command in your terminal:

sudo dphys-swapfile swapoff

This disables the swap temporarily, allowing you to adjust its size.

Step 2: Edit the swap configuration file

Next, open the swap configuration file in a text editor. I prefer nano, but any editor will do:

sudo nano /etc/dphys-swapfile

Look for the line CONF_SWAPSIZE=200 (or a similar value). This line defines the current swap size in megabytes.

Step 3: Increase the swap size

Change the value to your desired size. For instance, setting it to 2048 will give you 2GB of swap space:

CONF_SWAPSIZE=2048

Remember that the size you specify must be available on your SD card. Save your changes by pressing CTRL + X, followed by Y, then Enter to confirm.

Step 4: Apply the new swap size

After updating the configuration, recreate the swap file to match the new size by running:

sudo dphys-swapfile setup

This command will delete the old swap file and create a new one with the size specified in the configuration file.

Step 5: Turn the wwap back on

Now, re-enable swap with:

sudo dphys-swapfile swapon

At this point, your new swap file is active, but for the best results, reboot your Pi to ensure all applications recognize the additional memory:

sudo reboot now

Why Increase Swap Space?

The Raspberry Pi’s swap file acts as an overflow for RAM, giving the system extra memory by writing some data to disk when physical RAM is fully utilized.

Although accessing swap memory is slower than RAM, it can help manage resource-intensive applications by preventing crashes or system freezes.

However, keep in mind that an unnecessarily larger swap file can wear down your SD card over time.

Final Thoughts

Increasing my Raspberry Pi's swap space from 200 MB to 2 GB made a noticeable difference. My Nextcloud and OnlyOffice setup has been running more smoothly, with fewer slowdowns and far less system freezing.

However, this solution is still not perfect, SD card wear and the slower nature of swap memory mean it's more of a temporary solution than a permanent fix.

For anyone trying to push the limits of a Pi like I have, increasing swap space can provide short-term relief, but it’s essential to consider upgrading to hardware with more RAM if you're regularly maxing out your resources.

In my case, I'm exploring x86 servers to handle my containers and self-hosted applications more robustly, and I’ll cover that journey in a future article.

This experience has further reinforced my love for tinkering and optimizing setups, but also reminded me of the limitations of working on minimal hardware.

Sometimes, a modest hardware upgrade can make all the difference in creating a smoother, more reliable self-hosted ecosystem.

from It's FOSS https://ift.tt/4TLpaRZ
via IFTTT

7 Problems You Might Face After Dual Booting Linux and Windows [And How to Fix Them]

Dual booting enables you to enjoy the best of both worlds by having both Windows and Linux on the same computer.

However, as our years of experience goes with dual booting, you are likely to face some of the common issues that I list here.

Let me share what they are along with suggestions on fixing them.

1. Wrong time displayed when you switch OS

One of the most persistent issues with dual booting is that whenever you make a switch to the second operating system (or come back to the first one), you will find your time messed up.

Sure, you can correct the time every time you boot up. But, that will be annoying.

The most effective way to fix this issue is to type in a command in Ubuntu (or other Linux distros which sets the hardware clock to use local time:

sudo timedatectl set-local-rtc 1

Another easy way to resolve this issue is to enable automatic date & time via the internet.

Every Linux distro will have a similar setting, and the same applies for Windows too. With this option enabled, the OS will check the time from the internet even if it is messed up to start with, and should be updated automatically as soon as it connects to the internet.

If it still does not work, you can refer to our tutorial on fixing the wrong time displayed to know more.

2. Windows being lower in the boot order

Considering, you installed Linux as the second option for dual booting, it is possible you are worried about the order of boot displayed in the grub screen.

By default, you might end up loading the Linux distribution instead of Windows and see Windows listed in the second option in the grub screen.

So, how do we change this? We use Grub Customizer.

You can customize grub to your liking, not just the order, but its design too (if you want to go beyond what I say here).

First, you need to install the Grub Customizer. You can find it in the software center or install it via the terminal with the following command (for Ubuntu-based distros):

sudo apt install grub-customizer

Once you get it installed, open the program. It should prompt you to enter your password again. And, then access the list configuration as shown below.

All you have to do is to move Windows over the first Ubuntu. You can use the arrow option from the top menu for this task.

Make sure to hit "Save" once you change the order for it to take effect.

If you need detailed steps, you can watch this video (a little old but still works):

Subscribe to It's FOSS YouTube Channel

Or refer to this tutorial:

You can learn more about using grub customizer (and how to change the background of the grub screen) in our tutorial here:

3. No bootable device found error

Whether you installed Ubuntu as a secondary OS or decided to eliminate Windows completely, it is possible to mess up the bootloader (or UEFI settings).

You may not see a grub screen or fail to boot into the OS you installed entirely 😱

Fret not, do not panic, not all is lost.

In such cases, you need to fiddle around with the boot settings, trying a couple of options like turning secure boot on to fix the situation.

Here is what you could do:

Step 1: Head to the boot options before the OS loads up by pressing F12/F2/F10/DEL key.

Step 2: Navigate your way to the security settings, making sure the Secure Boot is enabled.

Step 3: Next, you must look for “Select an UEFI file as trusted for executing” and click enter.

📋

With this option, we are adding UEFI settings file (it was generated during Ubuntu installation) among the trusted UEFI boots in your device. If you remember, UEFI boot’s main aim is to provide security and since Secure Boot was not disabled (perhaps) the device did not intend to boot from the newly installed OS. We fix the secure boot issue, and hopefully, that solves our issue here.

In that option, you have to select the HDD/SDD you installed Ubuntu on, and navigate through:

 HDD → <EFI> → <ubuntu> → <shimx64.efi>

Select shimx64.efi file as the UEFI file and save the boot configuration. Now, when you reboot the system, grub should appear.

If you have already tried this, you might want to re-install Ubuntu, and ensure that you select the correct bootloader device for the grub screen to show up.

You can find more details on these steps on our tutorial for fixing no bootable device found:

4. No grub Screen & no option to boot into Linux/Windows

Occasionally, there is no error to be found, but instead, the entire grub screen disappears.

In such cases, you are directly booted in to Windows/Linux by default, with no option to head in to the second operating system.

The immediate workaround to this is to head into the boot menu (using F8, F12, or DEL key) and manually choose to boot into the second operating system.

However, if you want to fix this permanently, you need to fix the boot order for the grub screen to show up.

To achieve that, you can try to change the boot priority from your boot settings. It is the easiest method for most.

You should see the option to access the boot menu. Access it.

Here, identify the Linux boot option (here, it says - ubuntu).

Select it and move it up the order using the F5 key. Thereafter, press F10 to save and exit.

💡

Helpful keyboard shortcuts are always displayed in the boot menu.

If you do not have this option in your boot settings. You can try adding a new boot entr or set Linux boot from Windows EFI configuration.

To explore those two options, you can follow our tutorial on fixing no grub screen:

If nothing mentioned works, you can try re-installing the Linux distro with the correct bootloader device selected or update grub. That tends to work in some cases.

5. Windows does not appear at all in Grub screen

This was noticed with the release of Ubuntu 22.04 and you can still experience it at times.

The OS Prober feature in Grun probes for installed operating systems on the computer and adds them to Grub menu so that you can choose to boot into them.

But this OS_prober was disabled in Grub version 2.06 and thus when you install Ubuntu or some other Linux, the existing Windows would not show up in the Grub menu.

The fix, or should I say workaround, is to change the grub configuration by adding this line:

GRUB_DISABLE_OS_PROBER=false

to the file /etc/default/grub. After making changes, save the file and update grub with:

sudo update-grub

6. The system keeps on booting into live version of Linux

This happens when you have the live Linux USB still plugged into the system.

Here's the scenario. You create a live Linux USB, you plug it in the system and then change the BIOS settings to boot from USB at the top of the boot order and boot from it. Once you installed Linux but you keep the live USB plugged in, it is likely going to boot into the live session again as USB is up the boot order.

That's the reason why Ubuntu and some other distributions explicitly display a message to remove the installation media (i.e. the live USB) and then reboot.

7. Your distro might not use Grub

You hear about the grub boot screen all the time. However, there are some distributions that do not use grub at all.

So, what then? I was clueless when I first installed Pop!_OS and realized that it does not use grub.

In such a case, you can manually install rEFInd boot manager to act as a replacement to grub.

You can follow the official instructions to install the rEFInd package on your Linux distro. For instance, if you are on Ubuntu, you can install it from its PPA:

sudo apt-add-repository ppa:rodsmith/refind
sudo apt update
sudo apt install refind

Once done, all you need to do is run its installation script:

refind-install

You can also take a look at the ArchWiki for more information on the same if you need to customize the experience.

The installation script should automatically set things up for you. The next time you reboot, you should see a screen like the one in the screenshot above.

💬 What is the problem that you were facing? Did we manage to help you out? Is there something we missed? Let us know in the comments below!

from It's FOSS https://ift.tt/eirC4w7
via IFTTT