i installed the brl-12_1.0.3 (BR Debian 12 Image) with BNR - Live USB on a APC2200 which worked perfect so far.
I created the USB Install Drive (Project and Hypervisor) under AS4.11 with AR E4.92.
According to help i run the install.sh to install the driver from this usb.
Installing the - install_BRHypervisor.sh is not working from within the GPOS.
If I try to install the Hypervisor via BIOS it Installs successfully, but the Linux is not booting in Hypervisor mode.
So i assume the failed install of the driver could be the cause.
You mentioned that installation hypervisor from BIOS worked properly for you, but only linux started in the end. Just question, during power on there is boot table with two options (Linux and hypervisor), can you see this table? If so, can you using keyboard and arrows up or down select hypervisor and press enter?
Ok, let’s start from the beginning. For Linux 12, please install the newest BIOS 1.36. I can see that, for example, in 1.34, some compatibility changes were implemented. After installing the new BIOS, set everything in the BIOS as described for the hypervisor system. Then, install Linux 12, followed by the hypervisor driver, and finally, the hypervisor itself.
In the meantime, I have received a response from support and have learned the following:
For Debian 12, due to major adjustments to the driver, at least Automation Runtime 6.0.2 is required.
Anyhow thank you @kovarj for your dedication and community work!
I wanted to share that the solution in this post worked to resolve the another similar issue, adding the details here in case it is useful:
PPC2200 with Linux for B&R 12, customer was attempting to install Hypervisor and was seeing two issues:
When installing the B&R Hypervisor driver, he noticed the same message that @MartinM experienced: “mkdir: cannot create directory ‘/etc/br’: File exists”.
When attempting to install Hypervisor, after one restart, the install process got stuck at the message: “/OS/0/ booting runtime 0”.
When checking the “log.txt” file found in the “D:/” root folder on the CFast card, there was an error message stating something similar to “no valid configuration found”.
After reading this Community post, we realized the customer was using AR Q4.93 / AS 4.12. Since they had a simple project, they quickly converted to AS 6 / AR 6.0.2 and followed the same steps as before to install the drivers and Hypervisor. This time, they were successful and did not see either of the above error messages, and Hypervisor was installed and confirmed to be working.