X1E-78-100 (2026): Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
| Zeile 26: | Zeile 26: | ||
*** Failed to load image ]]]]: Volume Corrupt | *** Failed to load image ]]]]: Volume Corrupt | ||
*** start_image() returned Volume Corrupt | *** start_image() returned Volume Corrupt | ||
** In another case, it took quite long (maybe a minute) that | ** In another case (during installation, there were already logs complaining about missing write access to boot/efi/...), it took quite long (maybe a minute) that a minimal grub console came up: | ||
*** GNU GRUB version 2.14 | *** GNU GRUB version 2.14 | ||
*** Minimal bash-like line editing is supported for the first word, TAB lists possible command completion... | *** Minimal bash-like line editing is supported for the first word, TAB lists possible command completion... | ||
| Zeile 34: | Zeile 34: | ||
Solution | Solution | ||
* I did the exact same procedure as above 3 times with different results | * I did the exact same procedure as above 3 times with different results | ||
** After ther 3rd try, I had a booting grub, a booting linux and windows also is booting again. | ** After ther 3rd try (where i did not immediately reboot after installation but started a terminal first and typed ''reboot'' there), I had a booting grub, a booting linux and windows also is now booting again. | ||
Below I describe some of the scenarios in the | Below I describe some of the scenarios in the hope that these may be of help to the reader. | ||
=== HP Omnibook X14 === | === HP Omnibook X14 === | ||
| Zeile 63: | Zeile 63: | ||
This process did detect the parallel windows installation. | This process did detect the parallel windows installation. | ||
On my system, windows was booting again afterwards | On my system, windows was booting again afterwards. | ||
=== qcom-firmware-extractor === | === qcom-firmware-extractor === | ||
When trying to run the qcom-firmware-extractor, it will complain about incombatibilities... | When trying to run the qcom-firmware-extractor, it will complain about incombatibilities... | ||
Version vom 26. April 2026, 06:26 Uhr
Clean-install of Ubuntu 26.04
2026 the simple start
Preconditions
- I had a running installation of an older Ubuntu, se X1E-78-100
- Windows was still installed in parallel
- I did a backup of my data
Steps
- Download the aarchc64 image uf Ubuntu 26.04
- Create an installation USB stick (see X1E-78-100#Prepare_a_USB_memory_stick)
- Run the test/install environment
- Select manual install
- select the partitions
- /boot/efi is on my system nvme0p1
- / is on my system nvme0p6 (it is marked as format/overwrite)
- /home is on my system nvme0p7
- Install and reboot
Postconditions
- The grub bootloader does not start
- In one case, the screen stated white text on black ground:
- Unexpected return from initial read: Volume Corrupt, bufersize 1000
- Failed to load image ]]]]: Volume Corrupt
- start_image() returned Volume Corrupt
- In another case (during installation, there were already logs complaining about missing write access to boot/efi/...), it took quite long (maybe a minute) that a minimal grub console came up:
- GNU GRUB version 2.14
- Minimal bash-like line editing is supported for the first word, TAB lists possible command completion...
- grub> _
- you can type some commands here like reboot
- In one case, the screen stated white text on black ground:
Solution
- I did the exact same procedure as above 3 times with different results
- After ther 3rd try (where i did not immediately reboot after installation but started a terminal first and typed reboot there), I had a booting grub, a booting linux and windows also is now booting again.
Below I describe some of the scenarios in the hope that these may be of help to the reader.
HP Omnibook X14
Boot selector
There is a build-in boot selector:
- A longpress (30 sec) on the power button reboots your system
- During the first 10 seconds immediately after the reboot, constantly hit the F9 key
- You then can choose between the linux/grub bootloader, a microsoft bootloader or starting from the USB-A memory stick again.
grub
Windows does not boot
In case windows still starts booting but does not succeed and ends up in a black screen
- remove all devices from USB ports
- boot into linux
- run the grub install and configure scripts there
- sudo fdisk --list # search your disk
- sudo grup-install /dev/nvme0n1 # adapt your disk name here
- sudo update-grub
- sudo reboot # to test the boot process
- run the grub install and configure scripts there
This process did detect the parallel windows installation. On my system, windows was booting again afterwards.
qcom-firmware-extractor
When trying to run the qcom-firmware-extractor, it will complain about incombatibilities...