You waited 42minutes before feeling the need to bump the thread again? Almost all of the Pi employees are based in the UK, so your post was also at 10pm for all of them. Please be reasonable.anything!!??
What kernel version are you running? If you've used rpi-update then I would expect 6.6.18.
Testing on a 6.6.18 kernel that I've just built, having "video=Composite-1:PAL,tv_mode=PAL-N" in /boot/firmware/cmdline.txt means I get
Code:
pi@bookworm64:~ $ kmstestConnector 0/@44: Composite-1 Crtc 0/@47: 704x512i@50.02 15.429 704/72/72/139/? 512/37/5/71/? 50 (50.02) P|D Plane 0/@45: 0,0-704x512 Fb 50 704x512-XR24press enter to exitpi@bookworm64:~ $ kmsprint -pConnector 0 (44) Composite-1 (connected) EDID (1) = blob-id 0 (immutable) DPMS (2) = 0 (On) [On=0|Standby=1|Suspend=2|Off=3] TILE (4) = blob-id 0 (immutable) link-status (5) = 0 (Good) [Good=0|Bad=1] non-desktop (6) = 0 [0 - 1] (immutable) CRTC_ID (20) = object id 47 TV mode (31) = 5 (PAL-N) [NTSC=0|NTSC-443=1|NTSC-J=2|PAL=3|PAL-M=4|PAL-N=5]From the information I have, the relevant registers are being programmed for a 3.58205625 MHz colour subcarrier. I'm not sure if I have any hardware that can detect which of the PAL standards is being produced to be able to confirm it for definite.
You don't say if you're booting to console or GUI.
xrandr is only applicable if booted into X11 as the GUI. Bookworm defaults to Wayfire on a Pi5, and the Wayland APIs have no way of setting random DRM properties.
If at the console, then kmstest/kmsprint or modetest are your best bet.
Statistics: Posted by 6by9 — Wed Feb 28, 2024 2:57 pm