Sign in Sign up
brintos

brintos / linux-6.12-glibc-bash-coreutils public Read only

1
1
Fork 3
Launch

hardwarejs: refusing to boot in Chrome and Safari on iPadOS (crossOriginIsolated false) #1

Not planned debbie opened this issue · 1 comment
D debbie commented

Summary Machine fails to boot on iPadOS in both Chrome and Safari.

Console output

brintoS serial console (xterm.js). Output and input are live
brintos/linux-6.12-glibc-bash-coreutils • 8 (auto) vCPU : 2048 MiB RAM
Press Power on to begin booting.
hardwarejs: fetching kernel from repo FS brintos/linux-6.12-glibc-bash-coreutils at /boot/vmlinux.wasm
hardwarejs: bootKernel = 15.65 MiB from repo FS /boot/vmlinux.wasm (1878ms)
hardwarejs: rootfs served from cloud (brintos/linux-6.12-glibc-bash-coreutils) - the kernel mounts virtiofs as / and execs its init; no initramfs.
hardwarejs: refusing to boot - window.crossOriginIsolated is false. SharedArrayBuffer / shared WebAssembly Memory require COOP+COEP, which this site already sets but the browser hasn't applied yet. Hard-refresh and retry.

Environment

  • Platform: iPadOS
  • Browsers affected: Chrome, Safari

Notes Kernel fetch and mount succeed; boot is blocked at the crossOriginIsolated check even though COOP/COEP headers appear to be set by the site. Suggests the browser isn't applying the isolation headers on iPadOS (possibly a WebKit-engine restriction affecting both Safari and Chrome-on-iOS, since both use WebKit under the hood).

debbie assigned joel
D debbie commented

Moved to brintos/linux-in-the-browser#57 (with added debugging notes and joel carried over as assignee). The boot refusal happens in the hardwarejs host at the crossOriginIsolated check, before any machine code runs — it would affect every machine on iPadOS identically — so it's platform work for the general tracker, not a defect in this image. Closing here.

debbie closed this as not planned