0x30002 is RPI_FIRMWARE_GET_CLOCK_RATE
https://github.com/raspberrypi/linux/bl ... ware.h#L56
For a clock request to fail means you've killed the firmware somehow.
I'd check the output of `sudo vclog -m`, and `sudo vclog -a`. If -a returns nothing, then adding "start_debug=1" to config.txt and reproducing should give more information.
Please also give the output from "vcgencmd version" to confirm the firmware version you're running.
*edit*: Actually seeing as you've got 6.6.20+rpt-rpi-2712 as your kernel version, you're on a Pi5 (it always helps to say which hardware version you're using). start_debug=1 will do nothing, but that also gives a bigger question as to how you've killed the firmware when it is doing even less.
https://github.com/raspberrypi/linux/bl ... ware.h#L56
For a clock request to fail means you've killed the firmware somehow.
I'd check the output of `sudo vclog -m`, and `sudo vclog -a`. If -a returns nothing, then adding "start_debug=1" to config.txt and reproducing should give more information.
Please also give the output from "vcgencmd version" to confirm the firmware version you're running.
*edit*: Actually seeing as you've got 6.6.20+rpt-rpi-2712 as your kernel version, you're on a Pi5 (it always helps to say which hardware version you're using). start_debug=1 will do nothing, but that also gives a bigger question as to how you've killed the firmware when it is doing even less.
Statistics: Posted by 6by9 — Mon Apr 22, 2024 12:32 pm