Waydroid/binder module not working about vanilla-system-operator HOT 17 OPEN

The proposed fix is included in the new update.

from vanilla-system-operator.

Sorry, I think there's been a misunderstanding. This issue has nothing to do with secure boot. It affects 11th gen and higher intel chips, regardless of whether secure boot is enabled or not. It is a problem with indirect branch tracking. It has nothing to do with secure boot. IBT can be disabled with a kernel command line argument, but that reduces security.

Thank you!

from vanilla-system-operator.

This might be a similar issue, I'm facing although I don't have logs Vanilla-OS/desktop-image#111

from vanilla-system-operator.

Make sure that you have secure boot disabled, the module cannot be loaded if it is enabled.

from vanilla-system-operator.

I pushed a fix that checks if secure boot is enabled and then raise the proper error. Let me know if the problem persist once the fix is distributed. Feel free to re-open.

from vanilla-system-operator.

Re-opening since I now have the same problem on another laptop (with secure boot disabled):

from vanilla-system-operator.

I don't think it has anything to do with secure boot, it's a feature of Intel IBT on 11th gen and later processors. You need to compile the waydroid module with different flags iirc. You can disable IBT via the kernel command line, but that weakens security and isn't a solution.

from vanilla-system-operator.

I've applied the fix proposed by @TaeHagen in desktop-image's vso-waydroid-fcf-protection branch.
@mirkobrombin could you try if that solves it for you?

from vanilla-system-operator.

You can disable IBT via the kernel command line, but that weakens security and isn't a solution.

@TaeHagen, I assume it works for you when disabling IBT, right?

from vanilla-system-operator.

Honestly haven't tried, based on the error I assumed that would fix it.

from vanilla-system-operator.

It would be helpful if you could verify, so that we can know for sure.

from vanilla-system-operator.

I updated to the latest beta version, still getting same error. Is the fix included in the latest build? How do I know I have the fix?

from vanilla-system-operator.

I updated to the latest beta version, still getting same error. Is the fix included in the latest build? How do I know I have the fix?

Hi, are you in a VM in your installation using the vm image? (Seems like a build for it hasn't been triggered, will do it now)

from vanilla-system-operator.

No, I'm using raw standard hardware (non-nvidia)

from vanilla-system-operator.

I updated to the latest beta version, still getting same error. Is the fix included in the latest build? How do I know I have the fix?

What's the result of abroot status?

from vanilla-system-operator.

ABRoot Partitions:
• Present: vos-b ✓
• Future: vos-a

Loaded Configuration: /etc/abroot/abroot.json

Device Specifications:
• CPU: 11th Gen Intel(R) Core(TM) i5-1155G7 @ 2.50GHz
• GPU: [Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 03)]
• Memory: 23827 MB

ABImage:
• Digest: sha256:7d3e5bd662a3d22dc27cc93c025d34c021c8d3f6b9f798b9cf068651e6c0cf51
• Timestamp: 2024-05-15 17:36:45
• Image: ghcr.io/vanilla-os/desktop:main

Kernel Arguments: %s quiet splash bgrt_disable $vt_handoff

Packages:
• Added: docker.io
• Removed:
• Unstaged: docker.io
There are 1 unstaged packages. Please run 'abroot pkg apply' to apply them.

Package agreement: true

from vanilla-system-operator.

Hi, I am pretty sure this issue is no longer present, I tested Waydroid implementation a few days ago with Secure boot disabled on Intel hardware and it works fine, can you try checking it again?

from vanilla-system-operator.