Hello,
Cant run installer. BIOS hungs on it communicat
Fujitsu Esprimo P756 bios is high level
I also tried it on a new machine Gigabyte H510M K V2 chipset Intel H470 and output is the same. Cant run installer from the last ISO. ISO or kernel must be corrupted
What ISO are you using? Plasma6 or Plasma5? x86_64 or znver1? Wayland or X11? How did you copy the iso to flash drive?
The problem looks more like a corrupted download or bad copy to flash drive. To check if the iso or kernel are corrupted we need to know the exact iso including Build ID. In this screen-shot you can see that the Build ID is a number in the line a top of grub2 menu page.
This is shows the installer in the ROME Plasma6 Wayland iso Build ID 3247
I have used this iso on hardware and in VirtualBox and do not see any evidence of iso or kernel corruption on this iso.
Edit: This is the journal log for that iso booted ‘Live’ in VirtualBox showing no evidence of iso or kernel corruption that I can tell.
journal-iso-3247.txt (54.0 KB)
I know others in OM Contributor group have tested all the x86_64 isos but am downloading the ROME Plasma5 iso to test for myself. Already have the Plasma6 X11 x86_64 and Plasma6 Wayland x86_64. The Plasma6 isos work for me.
Plasma 6 x11x86_64. Burned by omburn program included in OM ROME.
Tried two usb disk and on two different machines as mentioned
The first thing I should have asked is did you check the checksums?
You could try downloading again in Konsole like this:
aria2c -c -m 0 http://file-store.openmandriva.org/api/v1/file_stores/f8c266c4210f7a23ba98d32e48b629bd4ba5606c
Then burn the image to flash drive again with OM Image Writer.
Note: I am not saying there is not some problem. But a problem with firmware probably would need to be fixed by whomever made the firmware. As your error says: contact BIOS vendor for fixes. What made me think a corrupted download or burn to flash drive more likely is that this happened on 2 computers. It would be unlikely two different computers would have the same firmware.
Build 3241
No i did not check checksum
Did you download the iso from Sourceforge?
Edit: Another question are you running the iso in a Virtual Machine like VirtualBox in Windows?
On the dell machine is ok. Dell Optiplex 3020 SSF
Yes from sourceforge
No virtualbox. Now i will download from konsole and checksum. One moment
I found these with internet search of the error:
https://bbs.archlinux.org/viewtopic.php?id=253883
In the Ubuntu post they suggest to use boot parameters:
intremap=no_x2apic_optout nox2apic
It is also suggested to update BIOS is there is an update available.
its grub parametr - i have no enter to the grub
As I understand it everything that happens before grub2 menu is done by the computer firmware. If I am correct OpenMandriva can not fix that. A firmware upgrade might fix that. But I am not a developer and devs know a heck of a lot more than I do.
If that video is unavailable there are plenty of videos on Youtube.com explaining the Linux boot process.
I would suggest you talk directly to developers on OpenMandriva Chat.
your iso snapshot boot to emergency mode
I suggest you do this. Edit: In emergency mode you can press Ctrl>D as it says, which should take you to a root prompt (#), and type startplasma-x11 and see if that works. Also if you got to emergency mode there must have been a grub2 menu shown before that?
One or the other?
on the dell optiplex 3020 boot ok without problem - problem is on Fujitsu Esprimo P756 and gigabyte H510M K V2 chipset Intel H470. One computer ok two not
I believe it is this.
That appears to be a computer with no Linux support at all. Windows only. But I am learning as we go on this issue.
but i have rome installed on it. with kernel 6.4.11. 23.08 but normally. maybe is a way to update from 23.08 to 24.07 from terminal?
DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
Your title is telling us the the computer firmware is issue instructions that are incompatible with latest Linux kernel (which is 6.10.0). The very first thing to do is to find out if there is a firmware update for that computer and if there is install it and see if that improves the situation. This probably explains exactly why your ROME system is stuck on kernel-6.4.1. Because the computer firmware ceased to work with Linux kernels after that point.
Trying to solve problems on 2 different computers is to confusing. Probably best to do one at the time. Your choice which one.
