[PROBLEM] hdmi screen resolution

[nakinigit]

I have a raspi 3b+ connected via hdmi to my Samsung TV, 1028 x 768 resolution. moOde insists that it is 1920 x 1080. I have edited /boot/firmware/config.txt with numerous suggestion from the web, as well as cmdline.txt. Are we X or Wayland? I have searched raspi resolution problems to no avail as well.

OSMC has worked fine on this device with the correct resolution connected to the same TV.

So, last ditch effort, any suggestions?

Edit: I forgot to mention I have seen another post regarding resolution, but in my case it is not with a 'no name' TV. Audio through hdmi is a key feature.

[Tim Curtis]

What model Samsung TV?

[TheOldPresbyope]

@nakinigit

Are we X or Wayland? 

Hint: the local display is started in the /home/moode/.xinitrc script (or whatever default usename was chosen if not moode). That's where the screen size and orientation of the local display gets set.

I experimented with Wayland early in moOde's transition to Raspberry Pi OS Bookworm. I could make the local display work with it but it brings new issues. We'll probably have to make the transition someday but we don't need it for now.

Regards,
Kent

[nakinigit]

@nakinigit

Are we X or Wayland? 

Hint: the local display is started in the /home/moode/.xinitrc script (or whatever default usename was chosen if not moode). That's where the screen size and orientation of the local display gets set.

I experimented with Wayland early in moOde's transition to Raspberry Pi OS Bookworm. I could make the local display work with it but it brings new issues. We'll probably have to make the transition someday but we don't need it for now.

Regards,
Kent

Kent,

I'm aware of .xinitrc. It checks /boot/firmware/config.txt for the line 'dtoverlay=vc4-kms-v3d', which is there in my case. So then it seems as though resolution is set by:

Code:

SCREEN_RES=$(kmsprint | awk '$1 == "FB" {print $3}' | awk -F"x" '{print $1","$2}')

And that gives me:

Code:

moode@moode:~ $ kmsprint | awk '$1 == "FB" {print $3}' | awk -F"x" '{print $1","$2}'
1920,1080
64,64

Incidentally, that is the resolution of the computer monitor I used for initial setup. Could that be a lingering artifact?