Jump to content

Armbian + EFI\grub + NVMe

balbes150

By balbes150
in Rockchip

 Share

Recommended Posts

Chandler Klüser

Chandler Klüser

Posted
Posted
On 3/21/2023 at 2:29 AM, balbes150 said:

new u-boot with support for launching from USB

 

I could only boot from USB with my SD card connected to ROCK5B, even though I was not able to `armbian-install` to NVMe.

 

But... I `dd` the 20230320-edge image and I could use it without problems using this bootloader, including booting directly from NVMe.

 

Its kernel is indeed 6.2.0:

 

Captura-de-tela-2023-03-23-21-56-20.png

 

I have connected my MT7921 wifi PCI-e adapter to test the drivers, look at this part of my `lspci -k` output:

  

0002:21:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter
	Subsystem: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter
	Kernel driver in use: mt7921e
	Kernel modules: mt7921e

 

BUT, look at dmesg:

  

$ dmesg | grep mt7921e
[   10.557507] mt7921e 0002:21:00.0: enabling device (0000 -> 0002)
[   10.557938] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_RAM_CODE_MT7961_1.bin failed with error -2
[   10.575264] mt7921e 0002:21:00.0: ASIC revision: 79610010
[   10.659920] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   10.748937] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   10.843534] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   10.933420] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.013970] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.103412] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.193484] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.280129] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.370280] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.459981] mt7921e 0002:21:00.0: Direct firmware load for mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin failed with error -2
[   11.548061] mt7921e 0002:21:00.0: hardware init failed

 

I know it deserves an exclusive topic for that, I mentioned that only for information. The developers job to make a better kernel for this board is doing great!

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
7 часов назад, Chandler Klüser сказал:

I could only boot from USB with my SD card connected to ROCK5B, even though I was not able to `armbian-install` to NVMe.

write in detail what steps you did and why the installation failed.

which power supply do you use ?

 

7 часов назад, Chandler Klüser сказал:

But... I `dd` the 20230320-edge image and I could use it without problems using this bootloader, including booting directly from NVMe.

There is no USB startup support in this bootloader and there are hidden bugs, if there is a problem with the system on NVMe, you will not be able to start the system from the SD card for repair (you will have to physically disconnect NVMe to start the system from the SD card).

 

7 часов назад, Chandler Klüser сказал:

BUT, look at dmesg:

The log specifically states that there is a problem with the firmware file (most likely it is simply not in the specified location). Try installing the full firmware package via armbian-config or apt\synaptic or copy it manually

1
Link to comment
Share on other sites
pipi

pipi

Posted
Posted

Hello. I have tried to boot from both sd and nvme with the latest version for rock5.

The first problem I had is that it doesn't recognize the screen resolution. I am writing from sd card with original armbian image. This version recognizes the size of the screen without problems, but the version of Balbes I get only part of the screen. I see everything magnified. Excuse my technological language, it lacks words to determine things correctly. But you know what I'm talking about.

Even so, with the huge screen, I managed to log in with the minimal image of armbian balbes. From there, I managed to update spi to the latest version with armbian-config and run armbian-install to install to nvme.

And here it gets more complicated, because from sd I can log in, but from nvme (it boots without sd), I don't get to the login screen. The last screen I get is one where it tells me that the UUID does not exist. And that's where it all ends.

0
Link to comment
Share on other sites
pipi

pipi

Posted
Posted (edited)

hello. Thanks for the interest. It's an old Sony monitor, which doesn't even have an hdmi input. So there is an HDMI/VGA adapter between the hdmi output of the board and the monitor. And the image is this: https://users.armbian.com/balbes150/rock5b/Armbian_23.02.0-trunk_Rock-5b_jammy_legacy_5.10.110_gnome_desktop.img.xz

Edited by aguapi
0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
16 часов назад, aguapi сказал:

HDMI/VGA adapter

the driver does not receive a response and sets an arbitrary resolution. add a fixed value of the output setting to the extlinux.conf command line (search the forum for how to do this).

1
Link to comment
Share on other sites
pipi

pipi

Posted
Posted (edited)

 

1 hour ago, balbes150 said:

Provide a complete description of all the steps you performed, what was in MTD\SPI before the installation started, which power supply is used.

 

the power pd from radxa, 30w. mtd/spi of the same image I'm trying to install from sd. I burn the same image to sd card with balena or rpi-imager, boot with that image on sd, with nvme inserted and format it with gparted to ext4. then i update the system and record spi from armbian install. theni burn the nvme disk with the same sd image, and shutdown. I remove the sd, I leave the nvme, and I get that screen that I show above

Edited by aguapi
0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
18 минут назад, aguapi сказал:

the power pd from radxa, 30w.

In my images, support for PD power supplies has been removed, so nothing will work with this power supply.

Also, you are using the wrong system startup order. If you have already recorded other u-boots in MTD\SPI (from the official Rada website, from the official Armbian versions), you must first completely clear MTD\SPI (for example, with the dd command). Only after that, you immediately connect NVMe to the device, connect the SD card with my image, start the system from the SD card  performs the initial configuration of the system from the SD card, start gparted from the SD card and create a partition on NVMe, and you can immediately start installing the system on NVMe+MTD. The system will do all the necessary work by itself. It is important to confirm the installation of the bootloader on MTD. No manual manipulations are needed to write the image to NVMe, the armbian-config (armbian-install) script does everything, it correctly creates the system and configures its launch from NVMe.

0
Link to comment
Share on other sites
pipi

pipi

Posted
Posted (edited)
Hace 9 horas, balbes150 dijo:

En mis imágenes, se eliminó el soporte para fuentes de alimentación PD, por lo que nada funcionó con esta fuente de alimentación.

Además, está utilizando el orden de inicio del sistema incorrecto. Si ya ha grabado otros u-boots en MTD\SPI (del sitio web oficial de Rada, de las versiones oficiales de Armbian), primero debe borrar completamente MTD\SPI (por ejemplo, con el comando dd). Solo después de eso, conecte inmediatamente NVMe al dispositivo, conecte la tarjeta SD con mi imagen, inicie el sistema desde la tarjeta SD, realice la configuración inicial del sistema desde la tarjeta SD, inicie gparted desde la tarjeta SD y cree una partición en NVMe , e inmediatamente puede comenzar a instalar el sistema en NVMe+MTD. El sistema hará todo el trabajo necesario por sí mismo. Es importante confirmar la instalación del gestor de arranque en MTD.No se necesitan manipulaciones manuales para escribir la imagen en NVMe, el script armbian-config (armbian-install) hace todo,

bueno, gracias. ¿Qué fuente de alimentación debo usar entonces? one of the Raspberry pi 3 works? what happens is that it has another type of tab, and I don't think it goes in rock5. I would need an adapter. what a mess

Edited by aguapi
0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
12 часов назад, aguapi сказал:

bueno, gracias. ¿Qué fuente de alimentación debo usar entonces? one of the Raspberry pi 3 works? what happens is that it has another type of tab, and I don't think it goes in rock5. I would need an adapter. what a mess

Read this topic, there are answers to all your questions here.

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
1 час назад, linuxfriend сказал:

Reason for asking for U-Boot-Image (with UEFI) is I want to try installing Fedora on Rock5.

To do this, it is better to use ready-made versions of Armbian images with EDK2-EFI (there are links in this topic).

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
14 часов назад, linuxfriend сказал:

Or do you have a newer one?

the new version is not ready yet (in the process of testing). although they have the same bootloader, I recommend images with the 5.10 kernel, the edge version does not have an HDMI\LAN\USB output and needs a UART for initial startup and test

0
Link to comment
Share on other sites
moy804

moy804

Posted
Posted

http://ix.io/4sL9

 

$ dmesg | grep pvtm

[   10.636922] rockchip-pvtm fda40000.pvtm: pvtm@0 probed

[   10.636979] rockchip-pvtm fda50000.pvtm: pvtm@1 probed

[   10.637036] rockchip-pvtm fda60000.pvtm: pvtm@2 probed

[   10.637090] rockchip-pvtm fdaf0000.pvtm: pvtm@3 probed

[   10.637137] rockchip-pvtm fdb30000.pvtm: pvtm@4 probed

[   10.935727] cpu cpu0: pvtm=1479

[   10.935891] cpu cpu0: pvtm-volt-sel=3

[   10.944727] cpu cpu4: pvtm=1719

[   10.950375] cpu cpu4: pvtm-volt-sel=5

[   10.960574] cpu cpu6: pvtm=1728

[   10.964935] cpu cpu6: pvtm-volt-sel=5

[   11.044506] mali fb000000.gpu: pvtm=883

[   11.044580] mali fb000000.gpu: pvtm-volt-sel=3

[   11.135347] RKNPU fdab0000.npu: pvtm=879

[   11.140988] RKNPU fdab0000.npu: pvtm-volt-sel=3

0
Link to comment
Share on other sites
pipi

pipi

Posted
Posted (edited)

hello. I tried to boot from nvme with this loader (Raspberry one), but that didn't work either. I keep getting the same error message on the boot process, regarding the uuid. I would like to know if I should keep trying or according to your opinion this charger is not the right one either.

https://ibb.co/jRpbBdg

Edited by aguapi
0
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept