looking at the log from Kevin we see:
MAV> messages blox
MAV> 2025-02-07 08:25:34.080 GPS 1: probing for u-blox at 230400 baud
2025-02-07 08:25:34.080 u-blox 1 HW: 000A0000 SW: ROM SPG 5.10 (7b202e)
2025-02-07 08:25:34.080 GPS 2: probing for u-blox at 230400 baud
2025-02-07 08:25:34.080 u-blox 2 HW: 000A0000 SW: ROM SPG 5.10 (7b202e)
2025-02-07 08:28:47.690 GPS 1: u-blox solution rate configuration 0x80008
2025-02-07 08:29:18.690 GPS 1: u-blox solution rate configuration 0x80008
2025-02-07 08:29:49.690 GPS 1: u-blox solution rate configuration 0x80008
2025-02-07 08:30:20.690 GPS 1: u-blox solution rate configuration 0x80008
this shows we do have bi-directional serial access to the GPS
The GPS fw hash matches one we run on a copter owned by @MichelleRos which doesn’t have this issue