Installing Adopisoft 5.1.7-20260106 using script and with fixed for fastboot, and patch for RTNETLINK File not exist error.

Install ubuntu 24.04.4. There are many tutorials out there. Watch youtube tutorials or follow this guide: https://blog.adopisoft.com/uncateg...

Monday, March 23, 2026

Adopisoft 5.1.7-20260106 ubuntu 24.04.4

 1. Download image here
Supported UEFI compatible board only
https://drive.google.com/file/d/1VMcjkNBmOeafKTElHbJbzUvRiRfE3shl/view?usp=sharing

2. Flash using balena or rufus. For rufus select GPT. Works only on the machine where it was first booted after flash.

Flash directly into your SSD or harddisk drive HDD. Since you cannot flash directly into HDD/SSD of your machine using balena and rufus, flash first to your flashdrive and then clone your flashdrive to your HDD/SSD using Acronis, DiskGenius, or Partition Master.

https://rufus.ie/en/

Expand storage in ubuntu: 

After flashing Adopisoft 5.1.7-20260106_x64_Final.img directly onto SSD/HDD of your mini PC, SSH into your machine and expand your storage.

1. Identify the disk using terminal

use this command: lsblk

2. Screenshot the result. Open gemini.google.com and upload it and ask "how to expand my partition using terminal if this is the result of lsblk". Follow the instruction provided by gemini.

SSH username and password:
username: ubuntu
password: ubuntu

Here is the best workflow to refresh and ensure your cloned Ubuntu 24.04 Server is optimized for the new hardware:

1. Update Hardware Identification Database

Update the local list of PCI and USB IDs so the OS accurately identifies the new components (NICs, HBAs, Chipsets).

Bash
sudo update-pciids
sudo update-usbids

2. Force Firmware Refresh

Most "drivers" in Linux are actually firmware files. Reinstalling the common firmware package ensures that any specialized microcode for the new machine's CPU or network card is available.

Bash
sudo apt update
sudo apt install --reinstall linux-firmware

3. Handle Proprietary Drivers (NVIDIA/Broadcom)

If your new machine has hardware that requires non-open-source drivers (like an NVIDIA GPU or certain Wi-Fi chips), use the ubuntu-drivers tool:

  • Check for recommended drivers: ubuntu-drivers devices

  • Auto-install the best fit: sudo ubuntu-drivers install

4. Rebuild the Initramfs

The Initial RAM Filesystem contains the drivers needed to boot the system before the main hard drive is even mounted. Since the hardware has changed, you should rebuild this to include the modules for the new machine's storage controllers or motherboard.

Bash
sudo update-initramfs -u -k all

5. Network Interface Fix (Critical for Servers)

This is the most common "failure" after cloning. Ubuntu uses Netplan, and if the new machine has different MAC addresses or interface names (e.g., changing from eno1 to enp3s0), your network will be down.

  1. Check interface names: ip link

  2. Edit Netplan: sudo nano /etc/netplan/50-cloud-init.yaml or 01-netcfg.yaml (the filename may vary).

  3. Ensure the interface names in the config match what you saw in the ip link command.

  4. Apply changes: sudo netplan apply


6. Remove "Ghost" Drivers

If you previously installed specific drivers for the old machine (like the Realtek 2.5G driver you were troubleshooting recently), they might conflict with the new hardware.

  • Check for loaded modules that seem out of place: lsmod

  • If a specific driver is causing high CPU or instability, you may need to remove its specific .ko file or the DKMS package associated with it.

No comments:

Post a Comment