I have a Dell laptop and I'm trying to run Fedora KDE Desktop 42 from an external SSD. I've freshly installed Fedora in the external SSD using another USB flash drive containing the live image. When I boot up Fedora from the external SSD, it tells me to enter passphrase for the disk. After I enter the correct passphrase/password, it takes me to a loading screen and stays there forever. If I press ESC on that screen, it displays a completely blank screen. When I press ESC again, it takes me back to the loading screen. For the installation options I made the following choices: * I selected Storage Configuration as Automatic. I also deleted everything in the drive by selecting Delete all/Reclaim space. Then I selected Encrypt my data option. * I enabled root account. I also created a user with admin privilege. I have tried to troubleshoot it and made the following adjustments as suggested by others in the Dell UEFI settings: * I have enabled all the thunderbolt related options (since I'm using thunderbolt 4 port to connect to the external SSD). Namely, *Enabled Thunderbolt Technology Support*, *Enable Thunderbolt Boot Support*, *Enable Thunderbolt (and PCle behind TBT) pre-boot modules*. * Selected Storage -> *AHCI* (default was *RAID On*, it didn't work when I tried with *RAID On* either) * Selected Pre-boot Behaviour -> *Thorough* (default was *Fastboot*) * Tried turning *Secure Boot* on and off, which made no difference (I understand that Fedora 42 is supposed to work with secure boot, but it was worth a try) #### Hardware specs - Dell Latitude 5530 - CPU: 12th Gen Intel(R) Core(TM) i5-1245U (1.60 GHz) - RAM: 16.0 GB (15.7 GB usable) - Internal Graphics Card: Intel(R) Iris(R) Xe Graphics - Internal 500 GB SSD (Contains Windows 11) - [This](https://www.amazon.co.uk/dp/B0B9C3ZVHR) Samsung 990 pro 1TB external SSD (to run Fedora) - [This](https://www.amazon.co.uk/dp/B0C8CTW8M6) ACASIS SSD enclosure, which uses thunderbolt 4 cable Any kind of help to resolve this would be appreciated. --- Edit: Just reinstalled Fedora without using the Encrypt Drive option, now I can see the following output/log when I press ESC on the loading screen. (Please note that it scrolls really fast at times so I couldn't take a proper sequential set of photos)

I have an issue creating VMs on CentOS using Boxes with the following error:

Virtualization extensions are unavailable on your system. Check your BIOS settings to enable them.

Also, when I try to use Virtual Machine Manager it says that

ins not available

, while I did install it and it's running with all needed libs. I wanted to access BIOS but there is a password on it (the laptop I have was a present and I don't know the password). I did try to flash the BIOS by upgrading it. I created a BIOS recovery USB drive, but it turns out that BIOS will not start the update wizard since there might be some issue with CMOS. The procedure for resetting CMOS on this HP is not working at all (it's ignored and the laptop just boots up regularly). Is there any way I can reset the BIOS password from the terminal? I lost a few hours Googling but I couldn't find any solution. It seems that my only chance is to do it from the terminal or some tool (if it exists). Edit: Laptop: HP Folio 9470m (I followed instructions for BIOS flash from HP support doc.) CPU on laptop is supporting virtualization: [root@DESKTOP-GHPREJB ivan]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 58 Model name: Intel(R) Core(TM) i5-3427U CPU @ 1.80GHz Stepping: 9 CPU MHz: 941.480 CPU max MHz: 2800.0000 CPU min MHz: 800.0000 BogoMIPS: 4589.71 Virtualization: VT-x Also: [root@DESKTOP-GHPREJB ivan]# egrep -q 'vmx|svm' /proc/cpuinfo && echo yes || echo no yes Edit 2: For future search results, this can help as this is the official reply I got from HP support on BIOS password reset request: >HP is committed to the security and privacy of its customers. HP has changed the policy regarding the BIOS Password Reset Service and will no longer provide this option to our customers. This change allows HP to protect customer’s data, BIOS configuration, and device settings, ensuring best in class security for HP products. Allowing access into the BIOS provides the potential opportunity for a rogue user to remove current security settings and change other device settings that could make the PC’s data vulnerable. For this reason, we are no longer able to reset the BIOS password for any reason. • The BIOS password feature on the HP PC was created for the users to provide an option to secure their PC at a hardware level, and it is the responsibility of the user to manage their password. If the BIOS password is forgotten, HP no longer provides a service to reset or remove the BIOS password. • If a unit has a BIOS password and is being sent in for repair, customer should remove the BIOS admin password and Power on password before the service is initiated. • If the unit has the password and the customer is unwilling/unable to provide the password, HP may not be able to complete the repair work. Then the option is that customer can replace the board at his/her own cost as this is not covered under warranty.

I know this is a common problem that has likely been addressed here before, but thus far none of the obvious solutions have worked. I'm trying to install Debian on my laptop (currently running Ubuntu) from a USB flash drive. I have reformated the drive to the FAT32 file system and made sure it has only one partition, I have used Unebootin to create the proper files on my flash drive, installed the ISO image on my root directory and the USB drive, programmed my BIOS chip to boot from the USB (put the HD last in boot order), and disabled secure boot and fast boot; but it just won't boot from from the USB drive. Instead it just boots directly to Ubuntu as if that was the only choice available. I've even tried pressing F2 during the boot sequence and have also tried using both USB ports on my computer, but to no avail. If I have to, I suppose I can live with Ubuntu, but I've been married to Debbie over a decade now and really don't feel like getting to know a whole new OS - even if she's related. Any hints or suggestions would be much appreciated. Thanks.

I was using a dual boot of openSUSE and Windows and I decided to delete OpenSUSE by deleting the partition. On rebooting, I found out that the secure boot for openSUSE was still there, leading to an error. to make things worse, the Windows boot loader was no longer there and I have to access it through the UEFI settings. How do I change this to automatically boot windows again?

I successfully installed arch, but my bios menu broke. Before the installation when I would press F2 or F12 on boot I would get the boot menu, now I just get a black screen. The default boot is windows. The only way I can open Linux is from windows > update & security > recovery > advanced startup then selecting "use a device". I select arch and it starts up with grub, which has linux and windows entries. I can enter Linux from there. How can I get bios back to change the boot order and have grub by default?

I had Windows 10 installed on my Acer SF3. I tried to give it a go with Linux and made a USB stick bootable with Garuda Linux installed onto it. It installed successfully and I rebooted but the GRUB menu didn't show up despite installing with no steps missing – it directly booted into Windows 10. I thought that the Garuda Linux was not properly installed and deleted the partition containing it, and tried booting into my USB stick again. To do that, I entered into the BIOS to change the boot priority of my USB stick to the highest. There, I saw: >1. Windows Boot Manager >2. Yes, 2 was empty. I thought that 2. was the USB stick and shifted to 1. Now, every time I boot my system it boots into *"Welcome to GRUB. grub rescue>"*, and I can't access the BIOS. If I reboot and press F2, it just shows a blank screen with nothing on it. And that is why I am not able to boot from my USB stick as well. I tried making the USB bootable again with Windows 10, (using another PC), but it still doesn't boot to it. Just stuck on GRUB. I watched YouTube and wrote down some commands as well. But nothing worked. Note: The BIOS was fully working before changing the boot priority. Any help would be appreciated. How can I fix this without taking my laptop apart (I am scared).

Welcome to GRUB!

error: no such partition.
Entering rescue mode...
grub rescue> set
cmdpath=(hd0,gpt1)/EFI/Garuda
prefix=(hd0,gpt6)/@/boot/grub
root=hd0,gpt6
grub rescue> set boot=(hd0,gpt6)
grub rescue> set prefix=(hd0,gpt6)/efi/boot/grub
grub rescue> insmod normal
error: no such partition.
grub rescue> set boot=(hd0,gpt6)
grub rescue> set prefix=(hd0,gpt6)/@/boot/grub
grub rescue> insmod normal
error: no such partition.
grub rescue> set prefix=(hd0,gpt6)/boot/grub
grub rescue> insmod normal
error: no such partition.
grub rescue>

I wonder how a 64-bit host BIOS can allocate a physical address for a 32-bit BAR in the PCIe devices? There is only 4GB of space for 32-bit address. And the host needs to write the base address during the enumerating time. If there are too many PCIe devices or the devices require too much space, then the 32-bit address can not provide enough space. Will the host allocate a 64-bit base address and tell the PCIe devices through some mapping mechanism, or will the host not allocate an address if there is not enough space in the low 4GB address space?

So, earlier I had Windows 7 on my laptop. I deleted all the Partitions and I think deleted the efi paritition too(which maybe shouldn't be deleted?). I boot into LM on my Live Disk and automatically installing using the option 'Erase Disk and Intall Linux Mint', I receive this error: 'Failed to Install Grub. Fatal Error.' I saw it on a LM Forum, and generated a boot report by these commands:

sudo add-apt-repository ppa:yannubuntu/boot-repair
apt update
apt install -y --install-recommends boot-info
boot-info

And I get this:

Boot Info Summary

=>No boot loader is installed in the MBR of /dev/sda.

sdb:

File system:

iso9660 Boot sector type: Unknown

Boot sector info:

Mounting failed: mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.

0 os detected

Architecture/Host Info

CPU architecture: 64-bit

Live-session OS is Linuxmint 64-bit (Linux Mint 20.2, uma, x86 64)

UEFI

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.

efibootmgr -V

Timeout: 10 seconds.

No BootOrder is set; firmware will attempt recovery This session has been detected as 'live' because /proc/cmdline contains (boot-casper)

This session has been detected as 'live' because df -Th / contains overlay

I don't understand this, except one that, I have created a GPT Partition Table from Gparted but this: >No boot loader is installed in the MBR of /dev/sda. so maybe this could be the issue. I read somewhere that this could be due to a missing efi partition, so I used 'Something else' during LM Installation and created a 500mb efi Partition and another partition formatted as EXT4 mounted at */*. And it works! I don't get the error this time during installation but when I restart to boot into the installed OS, I just see a blank screen, I don't even see the GRUB menu. I tried installation on Debian too, but I get the same error: 'Failed to Install Grub. Fatal Error.' and I didn't try manual partitioning as it doesn't have Gparted and I'm a bit new. This is an old laptop from 2011 and the bios doesn't have any option for 'Safe Boot' or 'Secure Boot and also it doesn't have 'Legacy USB boot for EFI systems' setting. The BIOS doesn't have any Legacy or UEFI settings Most answers on forums, AskUbunu, and SuperUser are about Dual Booting and are very complex.

I live in my car and it gets HOT in the summer. I've noticed when the temperature rises above normal room temperatures (like ~72f) my laptop proportionally starts to slow down to the point its unusable above 90f. I use Ubuntu and was wondering if anybody had any tips or suggestions to essentially 'overclocking' my laptop (a Dell precision 5520) to be more performant at high temperatures?

Scenario: - a Dell R740 server for example whose BIOS clock is first set, and it is set to UTC time but incorrectly and it is off 30 minutes. Then, a clean installation of Linux is performed (Redhat-8.10) and during installation the timezone is chosen, New York so EST. After installation, the time as presented in Linux via date is the correct local time but off 30 minutes, if we reference a peek at *time.gov* for correct time. There is no network connection to this server and no NTP/chrony is set up. - My observation is, if I manually adjust time to be correct (referencing time.gov from a different computer or my phone) by doing date mmddhhmm and then reboot, Linux reads the BIOS clock and then after booting the time in Linux is off 30 minutes again. - On my home computer which has an asrock motherboard and 2 different SSD's one for win10 the other for RHEL-8.10 Linux, and an internet connection, my BIOS clock is set to local time and I use win10 most of the time (and windows had NTP active). On the times I boot Linux, the time in Linux is the correct local time as presented by date however when I shutdown and then run windows the time in windows is then off by 4 or 5 hours; I am EST/EDT timezone. Also: > Windows expects the hardware clock to give “local time” by default. The reason is, according to Microsoft, so that users are not confused in BIOS menu; this is from a github page statement. Getting Windows to recognize BIOS (real-time-clock) as UTC apparently requires "tweaking" --- - What is the deal with how Linux deals with the BIOS clock? - **Am I expected** to use hwclock ? - What's the proper convention regarding what the BIOS clock is set to, UTC or local? - I seem to experience two different behaviors of Linux where it assumes on a Dell {enterprise style} server that the BIOS clock is UTC but on my cheap home asrock it is set to local time; And playing at home setting my asrock bios clock to UTC causes way more problems. - **What are files in Linux** dealing with this, to understand what Linux is going to do regarding time? Does it always reference the BIOS clock upon boot, and where is it specified in Linux for what timezone it should assume the BIOS clock to be in?

I've been running a RAID1 setup using two Samsung 970 EVO 500GB NVMEs on an Asus Z390 Maximus XI Formula motherboard for the last two years. This is my home server running Ubuntu 22.04 and I chose RAID1 for this specific reason in case one of the drives would fail. I wanted to upgrade the machine from 32GB to 128GB RAM for more ZFS Cache, but as the system didn't POST by itself I opted for a CMOS reset using the button on the motherboards I/O. After the reset I was anticipating having to change SATA Mode from AHCI to RAID (Intel Rapid Storage Technology) in the BIOS before being able to boot from my storage again as normal. Unfortunately this was not the case. I tried CSM (Compatibility Support Module) Settings recommended online, enable it and set Boot Device Control to UEFI and Legacy OPROM and UEFI priority for booting from storage devices. No change. I also tried manually rebuilding the RAID Volume without initializing/formatting the disks by creating a new RAID1 volume, but no change. So I moved on to data recovery by moving one of the disks to a separate PC I have with a minimal Ubuntu install.

and

fdisk -l

both show the disk being recognized, while the type reported by fdisk is cleary Linux RAID:

/dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 970 EVO 500GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 23ABA6D9-5923-4891-B67E-2208F422E40C

Device         Start       End   Sectors   Size Type
/dev/nvme0n1p1  4096 976506887 976502792 465.6G Linux RAID

## Steps taken in Ubuntu: ## 1. Copied the entire disk content to my local device:

dd if=/dev/nvme0n1 of=~/nvme_backup.img bs=4M status=progress

2. Installed and ran testdisk

testdisk /dev/nvme0n1

3. Chose

[EFI GPT]

partition table type, analyzed and found

Raid        4096 976506887 976502792 [ubuntu-server:0]

*The name of my raid volume!* So I accepted and WROTE. 4. After reboot, I attempted to mount the volume

: /mnt/recovery: unknown filesystem type 'linux_raid_member'

and realized I need to assemble the degraded RAID using

. 5. I followed this blogpost to examine the metadata, finding the following:

sudo mdadm --examine /dev/nvme0n1p1 
/dev/nvme0n1p1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : f4c5d883:1a67c158:7d34d079:c5e09397
           Name : ubuntu-server:0
  Creation Time : Mon Jul 10 16:26:43 2023
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 976502784 sectors (465.63 GiB 499.97 GB)
     Array Size : 488251392 KiB (465.63 GiB 499.97 GB)
    Data Offset : 264192 sectors
   Super Offset : 8 sectors
   Unused Space : before=264112 sectors, after=-264183 sectors DEVICE TOO SMALL
          State : clean TRUNCATED DEVICE
    Device UUID : de5af620:88784a78:693bf52a:bab766a4

Internal Bitmap : 8 sectors from superblock
    Update Time : Sun Apr 27 23:57:35 2025
  Bad Block Log : 512 entries available at offset 16 sectors
       Checksum : 88404970 - correct
         Events : 9909


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

6. Attempted to start the raid again using mdadm (my knowledge is very limited here so I tried both):

~$ sudo mdadm --assemble --run /dev/md0 /dev/nvme0n1p1 --force
mdadm: Device /dev/nvme0n1p1 is not large enough for data described in superblock
mdadm: no RAID superblock on /dev/nvme0n1p1
mdadm: /dev/nvme0n1p1 has no superblock - assembly aborted
~$ sudo mdadm --assemble --run /dev/md0 /dev/nvme0n1 --force
mdadm: Cannot assemble mbr metadata on /dev/nvme0n1
mdadm: /dev/nvme0n1 has no superblock - assembly aborted

My hopes was that this last step would allow me to mount the disk directly and find my now inaccessible data (OS files and configs, all important data is still on the ZFS pool luckily). I initially thought it would be as simple as moving a single disk to another system, enabling IRST and booting from the drive as the disks are "mirrored". Worth noting is that data is clearly still readable if I use:

photorec /dev/nvme0n1

But I would of course prefer if there were some way for me to get access to the proper file system again. Any help or guidance is greatly appreciated.

I've a minipc Qotom Q1900G2-P with AlmaLinux 9.5.\ Qotom with American Megatrends bios, build 06.01.2015.\ Bios reset to factory, default setup. Without video cable, HDMI or VGA, it doesn't start...from dmesg or syslog or message NOTHING!\ It seems that even get to the grub menu but obviously not having video connected I do not see until the boot comes. If I connect the video later, with the minipc on, no video signal.\ Same with Debian 12.10. **OK with Windows!! :(( With Windows it start also without video cable!** I've trie to insert in /etc/default/grub some options as:\ GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset console=tty1"\ or\ GRUB_CMDLINE_LINUX_DEFAULT="nomodeset text" But nothing! :(( some BIOS screen here https://imgur.com/a/TyDEDq5 Any ideas for solve? Thanks in advance

After i have formatted and de-allocated a space for my pop os installation, i used rufus to flash the pop os's iso images into my drive and installed pop os on my laptop(asus with nvidia gpu). i then booted the laptop into bios, changed the pop os in the boot order to the top, but the laptop would just try to boot pop os, then rebooted into the bios again. There is no error logs or anything of the sort. According to minitool wizard partition, the root partition's space has been used (i assumed is the initial fresh installation?) by ~10GB, while the boot partition's space has been used by ~100MB. I am certain the filesystem for both was correct(FAT32 for boot and EXT4 of root) but the boot partition(i will call esp from now on)'s status, according to minitool partition wizard, is marked as active. While the root partition's status, is marked as None. The aforementioned partition in the minitool partition wizard:

I am running Gigbyte Z97-HD3 mobo and Linux Mint 19.3. I also have another HD running windows 10. I usually use the grub boot menu to select my OS at start up. Today I decided to check what fast boot does. So I enabled it in "ultra" mode. I assumed I wouldn't be able to get into my BIOS at start up, but I thought I would still be able to use grub. The grub boot menu does show at every boot, but the keyboard is not working. Because of this, I can no longer select the windows 10 OS. Is there a way I can enable the keyboard in grub while still using fast boot. If not, how do I access the bios to turn it off?

I installed Arch Linux on a VMware virtual machine. To launch I use GRUB bootloader. I need to set the resolution for GRUB 16:9: 1366x768 or higher. Using vbeinfo (in GRUB) I can see the list of available resolutions. When setting the resolution from the list, everything works fine. But if I set, for example, 1366x768, then when loading GRAB the resolution will be 800x600. p.s. I change the resolution of GRUB by adding the parameter GRUB_GFXMODE=1366x768x32 to config file.

I have a Dell Latitude 7390 2-in-1 with a 256Gb NVMe installed with dual boot Win10 and Deb12. All working fine. Just running out of space so planned to clone to bigger drive. From Dell site and Crucial upgrade site concluded a 2Tb NVMe M.2 PCIe 4.0 should work. Bought a Kingston of that spec. I have attempted to clone the 256Gb to the 2Tb using, Clonezilla, dd, AOMEI Backupper and Macrium Reflect X Home (Free trial). Both via direct clone with the 2Tb in a USB-C housing or via backup to image file and restore. After replacing the 256Gb with the 2Tb in the Dell, ALL methods of cloning fail to boot. The Kingston is listed in BIOS but I just get a spinning white circle and unit eventually rebooting and repeating. If I boot the Dell from GParted live, clonezilla, or attempt to install a fresh Debian 12, ALL fail to find/list the 2Tb NVME drive, despite it showing in BIOS. If I swap back to the 256Gb the Dell boots fine and from Windows it will see the 2Tb from windows though it marks as offline as it has same disk signature ... all the partitions look as expected from the clone. If I connect to a separate unit running Debian 11 it shows as expected and I can mount the partitions and read write. So this maybe more a Dell question, but any thoughts or knowledge? Have I bought the wrong spec of NVME for that Dell or is there a BIOS setting I need to tweak? More info, the old drive is a "SK hynix SC311 SATA 256Gb" if that is an M2 SSD not NVMe would that prevent the cloning? Also in addition to software already previously listed above, have also now tried Boot-Repair that @oldfred suggested. It lists the 2Tb NVMe like BIOS does, but as per other software it then has no mention of it in the rest of the log Thank you to @oldfred, his comments were main part of answer. Per his comments, I had to put the old drive back in. Apply the AHCI change, then re clone it. I used Macrium and both created an image and also did a direct clone to the new 2Tb NVMe in a USB caddy. Then swapped the 2Tb for the old 256Gb drive, rebooted, which failed. I ran Macrium's boot repair option on the 2Tb but all the blue screen options failed to do anything apart from accessing UEFI settings failed. So option 2 was I booted Macrium's USB recovery media and used it to restore the image to the 2Tb, on rebooting the 2Tb said "Preparing Automatic Repair" and "Diagnosing PC" rebooted did again, but I could select Advanced and enter Safe Mode...which ran fine. Rebooted and finally all good.

I am trying to install GRUB on a USB purely so I can play around with a dummy boot menu on my laptop. ie this GRUB install should not refer to any working kernel/initrd files, or my current OS im using **(GRUB) 2.06** The problem is I keep getting a grub ext2 error despite using a ext4 filesystem. sudo dd if=/dev/zero of=/dev/sda bs=1024k sudo mkfs.ext4 /dev/sda mkdr /mnt/usb sudo mount /dev/sda /mnt/usb sudo grub-install --target=i386-pc --boot-directory=/mnt/usb /dev/sda Returns the error Installing for i386-pc platform. grub-install: warning: File system ext2 doesnt support embedding grub-install: warning: Embedding is not possible. Grub can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged. grub-install: error: will not proceed with blocklists. How can I resolve this? Ive attempted this over 5 times now and the error persists. Is it possible that my current /etc/default/grub config is interferring with the grub-install? I do not want my current linux OS to have anything to do with the grub-install, aside from the fact im using it to install...

I'm trying to install Proxmox on a new Mini PC (GMKteck NucBox M5 **Pro** Mini PC) but keep getting the following error : > EFI boot mode detected, mounting efivars filesystem mount: > /sys/firmware/efi/efivars: mount(2) system call failed: Operation not > supported. > > dmesg(1) may have more information after failed mount system call. > > Installation aborted - unable to continue (type exit or CTRL-D to reboot) I've also tried installing Ubuntu and Arch Linux and they both fail with a very similar error. The bios/uefi (AMI) has very limited options and seems to have no option for legacy boot so it's booting in UEFI mode by default. The Pro version of this NucBox M5 is very new and I have a feeling the Bios is missing some UEFI files. Choosing 'Launch EFI Shell' from bios results in a 'Not Found' error. Any help would be appreciated.

This is my ks file:

firewall --disabled
cdrom
lang ${$.system.locale$}
keyboard ${$.system.keymap$}
timezone ${$.system.timezone$}
network --bootproto=dhcp --hostname=${$.system.hostname$}
rootpw ${$.system.password$}
#if OS.VERSION  /etc/dracut.conf.d/virt-drivers.conf
KERNEL_VERSION=$(rpm -q kernel --qf '%{version}-%{release}.%{arch}\n')
mkinitrd -f \
            --with=xen-blkfront --preload=xen-blkfront \
            --with=virtio_blk --preload=virtio_blk \
            --with=virtio_pci --preload=virtio_pci \
            --with=virtio_console --preload=virtio_console \
        /boot/initramfs-$($KERNEL_VERSION).img $(KERNEL_VERSION)

sed -i '/PermitRootLogin/d'   /etc/ssh/sshd_config
sed -i '/PasswordAuthentication/d'   /etc/ssh/sshd_config
echo "PermitRootLogin yes"  >> /etc/ssh/sshd_config
echo "PasswordAuthentication yes" >> /etc/ssh/sshd_config
systemctl restart sshd.service

%end

And,why is vda2 marked as a BIOS partition during the Anaconda installation? Is very abnormal. Typically, BIOS is the first one.

I am trying to create a simple 200 M new qcow2 with just the grub2 BIOS mode installed in it. My objective is to get to the grub prompt or grub rescue prompt when i load the said qcow2 image in public cloud like OCI or AWS. The following are my steps 1. Compiling GRUB2 in BIOS mode from source code - mkdir grub2 - cd grub2 - wget https://ftp.gnu.org/gnu/grub/grub-2.06.tar.gz - tar -xvf grub-2.06.tar.gz - cd grub-2.06 - ./configure --target=x86_64 --with-platform=pc --disable-efiemu - make - grub-mkimage -v -O i386-pc -d ./grub-core -p\(hd0,msdos1\)/boot/grub -o core.img biosdisk part_msdos fat ntfs exfat part_gpt ext2 - cp core.img i386-pc After these steps i have boot.img, core.img and .mod files inside the i386-pc folder. 2. Create fresh qcow2 image and create partition table using gdisk - qemu-img create -f qcow2 cloud_grub2bios.img 200M - sudo qemu-nbd -c /dev/nbd4 cloud_grub2bios.img - sudo gdisk /dev/nbd4 - Then I set the disk to gpt using o command, and then create 2 partitions, first is 4MiB BIOS boot partition, and second is Linux filesystem for the remaining space in the image. The gdisk p command output after the said operations is presented below. I also run the

sudo mkfs.ext4 /dev/nbd4p2

after i create the partitions.

GPT fdisk (gdisk) version 1.0.8

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/nbd5: 409600 sectors, 200.0 MiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 4AF5DA38-30C9-4094-949A-60663B89B865
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 409566
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048           10239   4.0 MiB     EF02  BIOS boot partition
   2           10240          409566   195.0 MiB   8300  Linux filesystem

3. Install grub2 BIOS into the qcow2 image using grub-install present in the grub2.06 folder. - sudo mount /dev/nbd4p2 /mnt - sudo ./grub-install --target=i386-pc --boot-directory=/mnt/boot --directory=./grub-core/ /dev/nbd4 - Once the grub-install command is run, i get the following output -

Installing for i386-pc platform.
      ../grub/grub-2.06/grub-install: warning: cannot open directory `/usr/local/share/locale': No such file or directory.
      Installation finished. No error reported.

4. Once the qcow2 image is ready,I convert it into raw image using qemu-img command then run the raw image using the following command

qemu-system-x86_64 -m 4096 -cpu max -drive file=cloud_grub2bios.raw,if=virtio,format=raw -display none -nographic

Here i am able to see the grub2 prompt correctly. 5. But i upload this qcow2 image to OCI or AWS, configure the image to run using BIOS firmware and check the serial console, then i get nothing. It is completely blank. **Note** 1. I downloaded the Jammy Cloud Image from https://cloud-images.ubuntu.com/jammy/20240912/jammy-server-cloudimg-amd64.img and uploaded it back to OCI. Then in my uploaded image, i set the firmware to only BIOS by unticking the UEFI option. I had to manually upload and do instead of using the ubuntu image already published in OCI cause by default the ubuntu published in OCI supports both BIOS and UEFI and preferred is UEFI and when i launch an instance it always comes up with UEFI firmware. The jammy cloud image i uploaded in OCI which i am forcing to run with BIOS firmware, comes up successfully in OCI. 2. I tried using the boot.img, core.img and .mod files from the jammy cloud image which is running in OCI while creating my qcow2. Even with this, my image didnt get to grub or grub rescue prompt, and continued to give me blank screen. 3. I have tried extensive googling, and using AI tools like Chatgpt, Gemini etc but didnt find any working solution. The closest I found to generating a fresh cloud image is https://github.com/mvallim/cloud-image-ubuntu-from-scratch but this is using grub2 in UEFI mode and they arent building grub2 from scratch like i am doing.