Good afternoon, I have problems installing on a mini PC with N100 and NVME, I follow the steps of the guide conscientiously, but when I restart the computer it goes directly to the bios, the system does not start and in the startup options part it does not detect the nvme.
which image did you try ?
have you disabled secure boot ?
which guide was followed ?
1 Like
Upgrade BIOS and reset it to defaults, then disable secure boot and do not change other parameters.
I have followed this guide:
https://openwrt.org/docs/guide-user/installation/openwrt_x86
I have done the steps until the installation, I have not resized the partitions because I wanted to see the system first.
Yes, i disabled secure boot.
I tried:
22.03.3
23.05.5
23.05.3
Jose
Ok, you managed to answer two out of three questions, what about the last one ?
3 Likes
No, I answered all 3.
which image did you try ?
I tried:
22.03.3
23.05.5
23.05.3
have you disabled secure boot ?
Yes, i disabled secure boot.
which guide was followed ?
I have followed this guide:
openwrt.org/docs/guide-user/installation/openwrt_x86
I have done the steps until the installation, I have not resized the partitions because I wanted to see the system first.
Jose
Which image in the form of file name?
Version <> image.
openwrt-22.03.3-x86-64-generic-ext4-combined.img
openwrt-23.05.3-x86-64-generic-ext4-combined.img
openwrt-23.05.5-x86-64-generic-ext4-combined.img
Try the UEFI image.
3 Likes
The EFI system did work, how could I get the normal one to work to have all the options? Will I have to install grub manually?
Jose
UEFI and non-UEFI are identical, content wise, you won't be able to tell them apart, from an Openwrt point of view.
1 Like
To boot the non-EFI you would need to enable "Legacy Boot" in the BIOS, if that is available in your BIOS. This is different than Secure Boot. But as @frollic said there is no reason to do that since once booted both builds run exactly the same.
Ok, I said that because I had read this:
Once you select a target, there are multiple disk image files with different characteristics:
- ext4-combined-efi.img.gz This disk image uses a single read-write ext4 partition without a read-only squashfs root filesystem. As a result, the root partition can be expanded to fill a large drive (e.g. SSD/SATA/mSATA/SATA DOM/NVMe/etc). Features like Failsafe Mode or Factory Reset will not be available as they need a read-only squashfs partition in order to function. It has both the boot and root partitions and Master Boot Record (MBR) area with updated GRUB2.
- ext4-combined.img.gz This disk image is the same as above but it is intended to be booted with PC BIOS instead of EFI.
Now when I boot with UEFI firmware it stays here:
scripts to load br_netfilter if you need this.
3.563374] 80214: 802.1Q VLAN Support u1.8
3.567957] NET: Registered PF_USOCK protocol family
3.573691] microcode: sig=0xb06e0, pf=0x1, revision=0xe
5794701
microcode: Microcode Update Driver: u2.2.
3.579476]
IPI shorthand broadcast: enabled
3.589607]
لالا لا لا
3
AUXZ version of gem_enc/dec engaged.
.5948491
AES CTR mode by optimization enabled
3.601332]
3.610474]
sched_clock: Marking stable (2228512656, 1372808793)->(4071170790, -469849341)
clk: Disabling unused clocks
3.615090]
Waiting for root device PARTUUID=a21fa13b-346-35b-69bb-92e6f5a9002. •
How did you write the image ?
This steps:
wget https://downloads.openwrt.org/releases/23.05.5/targets/x86/64/openwrt-23.05.5-x86-64-generic-ext4-combined-efi.img.gz
gunzip openwrt-23.05.5-x86-64-generic-ext4-combined-efi.img.gz
dd if=openwrt-23.05.5-x86-64-generic-ext4-combined-efi.img bs=1M of=/dev/nvme0n1
fdisk /dev/nvme0n1
-delete nvme0n1p2
-create new partition nvme0n1p2
e2fsck nvme0n1p2
resize2fs nvme0n1p2
Jose
1 Like
Your recreate and resize is why the boot fails.
Replace PARTUIID with root=/dev/nvme0n1p2 in Grub.
1 Like
How?
Jose
Edit grub.cfg in /boot/grub.
You can edit the menu entry, during the count down, when Openwrt boots, but the change will only be valid for the current boot.
With NVMe you must use UEFI anyways…
6 Likes