MSI Prestige 16 AI+ (Lunar Lake): OV5675 not probed — TPS68470 “No board-data found for this model”
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux
- Domain
- embedded-iot
Research direction
Start by locating the TPS68470 board-data lookup and the existing DMI entries for similar laptop models; the issue names the DMI product string Prestige 16 AI+ MercedesAMG B2VMG. Use the attached dmesg and request the offered ACPI table dumps to check the device wiring and board data. Done when the TPS68470 initializes for this model and the OV5675 camera appears in cam -l.
Written by the indexing model from the issue text.
Description
Laptop: MSI Prestige 16 AI+ MercedesAMG (DMI product: "Prestige 16 AI+ MercedesAMG B2VMG")
CPU: Intel Core Ultra (Lunar Lake), IPU 8086:645d rev 04
OS: Ubuntu 26.04 LTS, kernel 7.0.0-38-generic, libcamera 0.7.0
Camera works on Windows (same machine, dual boot).
Enabled ACPI devices (status 15): OVTI5675:00, HIMX1092:00, INT3472:06
All other OVTI* / INT3472* entries have status 0.
Relevant dmesg:
int3472-tps68470 i2c-INT3472:06: TPS68470 REVID: 0x21
int3472-tps68470 i2c-INT3472:06: error -ENODEV: No board-data found for this model
intel-ipu7 0000:00:05.0: no subdev found in graph
IPU7 firmware loads and authenticates fine. The ov5675 module is loaded but the sensor
never probes, presumably because the TPS68470 regulators/GPIOs are not set up without
board data for this DMI. cam -l lists no cameras.
Full dmesg attached. Happy to provide ACPI table dumps (acpidump) or test patches.
- Dominant language
- C
- Stars
- 14
- Forks
- 39
- Avg merge
- 28d 29m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/ipu7-drivers
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
intel/ipu7-drivers#111 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
intel/ipu7-drivers#102 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
intel/ipu7-drivers#93 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
intel/ipu7-drivers#92 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
intel/ipu7-drivers#86 ·
All issues in intel/ipu7-drivers
Similar issues
-
dependency component: oneMKL module: dpclang
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
intel/torch-xpu-ops#5880 ·
Maintainers usually reply within 2 days
-
area/ci-build bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DarkFlippers/qUnleashed#423 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
CVE-2026-111497Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
fink/fink-distributions#1322 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
openvehicles/Open-Vehicle-Monitoring-System-3#1563 ·
Maintainers usually reply within 2 days