Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
USB hot-plug doesn't work in Intel-based MacBook Pro (16-inch, 2019) with T2 chip
Reported by VasylBaran · filed Sep 15, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details
MacBook Pro with T2 chip (16-inch, 2019): Intel i7-9750H, 16GB RAM. Omarchy 4.0.3-1, Linux 7.2.4-arch1-Watanare-T2-2-t2
What's wrong?
Hi there! I've installed Omarchy 4.0.3-1 onto my Intel-based MacBook Pro (16-inch, 2019).
It seems that it doesn't detect any USB Flash drives connected to the laptop unless it has already been plugged-in during boot.
Hot-plug did work fine in my T2 Arch Linux setup on this same machine.
When I plug/unplug USB device lsblk/lsusb doesn't show anything at all. No system events (dmesg -w), nothing.
lsusb -t shows:
Bus 001: xHCI
Bus 002: xHCI
Bus 003: xHCI
Bus 004: xHCI
Bus 005: xHCI
Bus 006: xHCI
Bus 007: BCE VHCICommand:
lspci -nn | grep -Ei 'usb|thunderbolt'
produced:
00:14.0 USB controller [0c03]: Intel Corporation 300/C240 Series Chipset Family USB 3.1 xHCI [8086:a36d] (rev 10)
06:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
07:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
07:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
07:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
07:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
08:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06)
09:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
7c:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
7d:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
7d:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
7d:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
7d:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
7e:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06)
7f:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)Kernel modules
Command:
lsmod | grep -Ei 't2|bce|thunderbolt|xhci'
produced:
t2bce_audio
snd_pcm
snd
thunderbolt
t2bce_vhci
t2bce_core
t2bce_dmaSpecifically:
t2bce_audio 77824 3
thunderbolt 614400 0
t2bce_vhci 90112 0
t2bce_core 53248 2 t2bce_audio,t2bce_vhci
t2bce_dma 32768 1 t2bce_coreThe T2 BCE modules are therefore loaded and functioning.
Important dmesg findings
The kernel successfully initializes the T2 BCE stack:
t2bce_dma: module initialized
t2bce_core: device initialized
t2bce_core: module initialized
t2bce_vhci: BCE VHCI Host Controller
t2bce_vhci: new USB bus registered, assigned bus number 7
t2bce_vhci: device initialized
t2bce_vhci: module initialized
Internal Apple devices subsequently enumerate successfully.
Thunderbolt initialization produces these two important messages:
thunderbolt 0000:08:00.0: device links to tunneled native ports are missing!
thunderbolt 0000:7e:00.0: device links to tunneled native ports are missing!There are no USB hotplug messages when the external USB drive is connected.
Thunderbolt service
bolt is installed and running:
bolt.service loaded active running Thunderbolt system service
t2-bce.service does not exist, which is expected; T2 BCE functionality is provided through kernel modules rather than a t2-bce systemd service.
t2fanrd.service is also running:
t2fanrd.service loaded active running
Thunderbolt domains
sudo boltctl domains
produced:
● domain0 c7010000-0062-640e-8360-3c8d8811b102
├─ bootacl: 0/0
└─ security: user
● domain1 bf010000-0082-8c0e-0346-a28d8490ba02
├─ bootacl: 0/0
└─ security: userboltctl list is empty.
So important conclusions so far:
- This is not currently a filesystem/mounting problem.
- The external USB device isn't even being enumerated by Linux.
- T2 BCE functionality is loaded and internal T2 USB devices work.
- USB xHCI controllers are present.
- Thunderbolt controllers are present.
- bolt.service is running.
- Thunderbolt reports: device links to tunneled native ports are missing!
View raw text
### System details MacBook Pro with T2 chip (16-inch, 2019): Intel i7-9750H, 16GB RAM. Omarchy 4.0.3-1, Linux 7.2.4-arch1-Watanare-T2-2-t2 ### What's wrong? Hi there! I've installed Omarchy 4.0.3-1 onto my Intel-based MacBook Pro (16-inch, 2019). It seems that it doesn't detect any USB Flash drives connected to the laptop unless it has already been plugged-in during boot. Hot-plug did work fine in my T2 Arch Linux setup on this same machine. When I plug/unplug USB device lsblk/lsusb doesn't show anything at all. No system events (dmesg -w), nothing. ``` lsusb -t shows: Bus 001: xHCI Bus 002: xHCI Bus 003: xHCI Bus 004: xHCI Bus 005: xHCI Bus 006: xHCI Bus 007: BCE VHCI ``` ``` Command: lspci -nn | grep -Ei 'usb|thunderbolt' produced: 00:14.0 USB controller [0c03]: Intel Corporation 300/C240 Series Chipset Family USB 3.1 xHCI [8086:a36d] (rev 10) 06:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 07:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 07:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 07:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 07:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 08:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06) 09:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06) 7c:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 7d:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 7d:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 7d:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 7d:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 7e:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06) 7f:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06) ``` **Kernel modules** ``` Command: lsmod | grep -Ei 't2|bce|thunderbolt|xhci' produced: t2bce_audio snd_pcm snd thunderbolt t2bce_vhci t2bce_core t2bce_dma ``` **Specifically:** ``` t2bce_audio 77824 3 thunderbolt 614400 0 t2bce_vhci 90112 0 t2bce_core 53248 2 t2bce_audio,t2bce_vhci t2bce_dma 32768 1 t2bce_core ``` The T2 BCE modules are therefore loaded and functioning. **Important dmesg findings** ``` The kernel successfully initializes the T2 BCE stack: t2bce_dma: module initialized t2bce_core: device initialized t2bce_core: module initialized t2bce_vhci: BCE VHCI Host Controller t2bce_vhci: new USB bus registered, assigned bus number 7 t2bce_vhci: device initialized t2bce_vhci: module initialized ``` Internal Apple devices subsequently enumerate successfully. Thunderbolt initialization produces these two important messages: ``` thunderbolt 0000:08:00.0: device links to tunneled native ports are missing! thunderbolt 0000:7e:00.0: device links to tunneled native ports are missing! ``` There are no USB hotplug messages when the external USB drive is connected. **Thunderbolt service** bolt is installed and running: bolt.service loaded active running Thunderbolt system service t2-bce.service does not exist, which is expected; T2 BCE functionality is provided through kernel modules rather than a t2-bce systemd service. t2fanrd.service is also running: t2fanrd.service loaded active running **Thunderbolt domains** ``` sudo boltctl domains produced: ● domain0 c7010000-0062-640e-8360-3c8d8811b102 ├─ bootacl: 0/0 └─ security: user ● domain1 bf010000-0082-8c0e-0346-a28d8490ba02 ├─ bootacl: 0/0 └─ security: user ``` boltctl list is empty. So important conclusions so far: - This is not currently a filesystem/mounting problem. - The external USB device isn't even being enumerated by Linux. - T2 BCE functionality is loaded and internal T2 USB devices work. - USB xHCI controllers are present. - Thunderbolt controllers are present. - bolt.service is running. - Thunderbolt reports: device links to tunneled native ports are missing!
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 13:42 UTC