I've got a Raspberry Pi 500+, and am frustrated trying to debug a blank screen from boot. I can ssh in, but not get the attached display to work.
The display seems to be recognized correctly:The window manager seems to have started:I can get X windows to open remotely using ssh -Y, so the server is doing its thing correctly. I think it might be an ~/.Xauthority problem. Any thoughts about how I might track this down?
The display seems to be recognized correctly:
Code:
hunter@raspberrypi:~ $ kmsprintConnector 0 (33) HDMI-A-1 (connected) Encoder 0 (32) TMDS Crtc 2 (92) 1024x768@60.00 65.000 1024/24/136/160/- 768/3/6/29/- 60 (60.00) D Plane 2 (81) fb-id: 679 (crtcs: 2) 0,0 1024x768 -> 0,0 1024x768 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12 P010 P012 P016 S010 S012 S016) FB 679 1024x768 XR24 Plane 54 (655) fb-id: 684 (crtcs: 2) 0,0 64x64 -> 874,575 64x64 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12 P010 P012 P016 S010 S012 S016) FB 684 64x64 AR24Connector 1 (42) HDMI-A-2 (disconnected) Encoder 1 (41) TMDSCode:
hunter@raspberrypi:~ $ ps -A | grep labwc 840 ? 00:00:00 labwcCode:
hunter@raspberrypi:~ $ DISPLAY=:0 xeyesInvalid MIT-MAGIC-COOKIE-1 keyError: Can't open display: :0$ sudo xauth generate :0 .Authorization required, but no authorization protocol specifiedxauth: (argv):1: unable to open display ":0".Statistics: Posted by Larry H — Sat Dec 13, 2025 5:25 am — Replies 4 — Views 60