Opened 4 years ago

Closed 4 years ago

#243 closed System Defect (fixed)

Can't set display resolution beyond 1024x768 pixels

Reported by: Traumflug Owned by:
Priority: major Milestone:
Component: System Configuration Version: 8.0-BETA
Keywords: Cc: trac-bugs@…


As discussed on the support mailing list (no archive?), Xorg doesn't let me set my monitor resolution beyond some imaginary barrier, which happens to be at 1024 pixels wide, 768 pixels high.

Display setup ("7" at the OS loader menu) offers me those higher resolutions, but doesn't manage to tell Xorg to actually use them. Here's my xrandr output, after manually adding the optimum resolution:

$ xrandr
Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       76.0*
   800x600        73.0
   640x480        73.0
  1152x864 LG (0x105)  108.0MHz
        h: width  1152 start 1216 end 1344 total 1600 skew    0 clock   67.5KHz
        v: height  864 start  865 end  868 total  900           clock   75.0Hz

This 1152 pixel resolution shows up in KDE's display settings panel as well, but KDE fails to actually set it either.

Attached /var/log/Xorg.0.log as found right after desktop startup.

Attachments (2)

Xorg.0.log.gz (5.1 KB) - added by Traumflug 4 years ago.
adiuminstall.jpg (10.9 KB) - added by domtheo 7 months ago.
Rumah Dijual di Jakarta, Jasa seo Jakarta, Jasa seo Bergaransi

Download all attachments as: .zip

Change History (8)

Changed 4 years ago by Traumflug

comment:1 Changed 4 years ago by kris

When you go to Display Wizard (option 7), go to the advanced tab and enable the option to specify Vert / Horz refresh rates. When you enable those and select your higher resolution does it change properly?

I've have seen quite a few cases where Xorg gets too smart for itself, and ignores your desired resolution unless you forcibly specify the refresh rates in the xorg.conf file. Let me know if this helps correct the issue in this case.

comment:2 Changed 4 years ago by Traumflug

Just enabling the upper of the two check boxes there helps indeed. All of a sudden, KDE offers more resolutions as well.

Please try to _not_ close this issue, as at least the usability issue isn't resolved yet.

comment:3 Changed 4 years ago by kris

Well at least that we've identified a work-around to the problem. I've run into this from time-to-time as well and it seems like xorg isn't auto-detecting your refresh rates properly, which in turn prevents it from switching to higher resolutions. It seems like an issue with certain monitors here. I'm unsure what else we can fix aside from just reporting the bug to the xorg guys with your monitor specifics. What do you think?

comment:4 Changed 4 years ago by Traumflug

I'm pretty sure Xorg introduced this intentionally. This hardware run Ubuntu before and resolutions vanished from Xorg release to Xorg release.

Mac OS X has a checkbox "recommended resolutions" which is enabled by default. It's apparently functionally the same as the upper one in PC-BSD's advanced settings. So we could move this upper checkbox to the first tab, leaving the frequency range text fields for "advanced". Additionally, offer non-standard resolutions in the drop down menu in case this check box is unchecked, only. A menu for choosing the screen refresh frequency (60.0 Hz / 75.0 Hz / auto) is needed, like KDE already has.

The best thing would be to do this in KDE's and GNOME's panel and drop PC-BSD's, perhaps for the next release. Duplicating functionality is rarely a good idea, as it adds obsolete maintenance costs.

comment:5 Changed 4 years ago by kris

That's probably what we'll end up doing in a future release to keep things simplified. I'm going to leave this issue open for now, and revisit it post 8.0-release to start seeing what we'll need to fix to make this happen.

comment:6 Changed 4 years ago by kris

  • Resolution set to fixed
  • Status changed from new to closed

Actually, I'm going to mark this as closed. I've created a new TODO list on the wiki, and added this feature to work on for 8.1:

Thanks for bringing it to my attention!

Note: See TracTickets for help on using tickets.