Apple Cinema Display display modes not detected

jbum · 03-25-2022, 01:24 PM

I have an Apple Cinema Display (30") attached to a Lenovo T430s through a Dual Link DVI to DisplayPort adapter. This setup has been working for my dual boot setup of Windows and Slackware for a long time. Up until recently, I was running Slackware 14.2 and had no issues.

Shortly into the boot initialization, the boot screen would change to a higher resolution (higher than the standard 1024x768 max for VGA framebuffer setting in lilo) and transition to the X login screen set to the correct 2560x1600 resolution.

Ever since I installed Slackware 15 (same machine), I cannot get this resolution detected and working automatically. Once I'm logged into my X desktop, I can run the following instructions to add in the 2560x1600 display mode and force that to correct the resolution. But this is temporary and doesn't feel like a solution.

Code:

xrandr --newmode "2560x1600"  268.00  2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync
xrandr --addmode DP-2 2560x1600
xrandr --output DP-2 --mode 2560x1600

Running xrandr before applying these steps shows only one resolution mode for the monitor.

Code:

DP-2 connected 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 401mm
   1280x800      59.91*

After applying the xrandr mode adjustments.

Code:

DP-2 connected 2560x1600+0+0 (normal left inverted right x axis y axis) 641mm x 401mm
   1280x800      59.91  
   2560x1600     59.86*

Just some more information related to display server/driver.

Code:

Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
  Device-2: Acer Integrated Camera type: USB driver: uvcvideo
  Device-3: HP HP Webcam HD 4310 type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
  Display: server: X.Org 1.20.14 driver: loaded: modesetting unloaded: vesa
    resolution: 2560x1600~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)
    v: 4.2 Mesa 21.3.5

I would really appreciate some help in troubleshooting why this isn't detected and automatically used as it was prior to Slack 15?

Thank you!

mrmazda · 03-25-2022, 07:34 PM

This smells like a server regression. Writing to intel-gfx@lists.freedesktop.org about this might be more effective than here.

Is the display end the DVI, or the DP?

Do you have any /etc/X11/xorg.con* files affecting graphics configuration?

Any change if you switch from modesetting DIX display driver to intel DDX display driver, and optionally, or after first trying without it, include video=DP-2:2560x1600e on the kernel command line at boot? Without the video option but with the intel DDX, does the output name change from DP-2 to something else, DisplayPort-0 maybe, so changing the video= propriety?

jbum · 03-26-2022, 02:14 AM

Thanks for your suggestions.

Quote:

Originally Posted by mrmazda

Is the display end the DVI, or the DP?

Do you have any /etc/X11/xorg.con* files affecting graphics configuration?

Any change if you switch from modesetting DIX display driver to intel DDX display driver, and optionally, or after first trying without it, include video=DP-2:2560x1600e on the kernel command line at boot? Without the video option but with the intel DDX, does the output name change from DP-2 to something else, DisplayPort-0 maybe, so changing the video= propriety?

The monitor/display cable is a DVI. I have an adapter that converts it to a DP which connects to my machine.

I had a couple xorg.conf.d/* files related to mouse/touchpad customizations but commenting those out had no effect.

Also, passing in the "video=DP-2:2560x1600e" kernel parameter using "append" in lilo.conf didn't change anything either.

For switching to the intel driver, I configured /etc/X11/xorg.conf.d/10-display.conf with the following simple "Device" section. Is this what you meant by going from modesetting DIX to intel DDX driver?

Code:

Section "Device"
    Identifier "Device0"
    Driver "intel"
EndSection

Using the intel driver also did not change anything for me. The following device information is seen.

Code:

Output of "inxi -G"
===================
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
  Device-2: Acer Integrated Camera type: USB driver: uvcvideo
  Device-3: HP HP Webcam HD 4310 type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo
  Display: x11 server: X.Org 1.20.14 driver: loaded: intel
    resolution: 1280x800~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2)
    v: 4.2 Mesa 21.3.5

Code:

Output of xrandr
================
DP2 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 640mm x 400mm
   1280x800      59.91* 
 . . .
DP3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Using the intel driver did change the output device from DP-2 to DP2 (no hyphen). It also seems to have introduced a "VIRTUAL1" output device (not sure what that is).

None of this worked but there was one interesting observation. The 2560x1600 resolution was listed using "hwinfo" but this is not seen in the normal resolution detection or selection.

Code:

19: None 00.0: 10002 LCD Monitor                                
  [Created at monitor.125]
  Unique ID: rdCR.GBsUpUTR2T8
  Parent ID: _Znp.YHichahshZB
  Hardware Class: monitor
  Model: "Apple Cinema HD"
  Vendor: APP "Apple"
  Device: eisa 0x9232 "Cinema HD"
  Serial ID: "CY6380HUUG1"
  Resolution: 1280x800@60Hz
  Resolution: 2560x1600@60Hz
  Size: 641x401 mm
  Year of Manufacture: 2006
  Week of Manufacture: 38
  Detailed Timings #0:
     Resolution: 2560x1600
     Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync
       Vertical: 1600 1603 1609 1646 (+3 +9 +46) +vsync
    Frequencies: 268.00 MHz, 98.53 kHz, 59.86 Hz
  Year of Manufacture: 2006
  Week of Manufacture: 38
  Detailed Timings #1:
     Resolution: 1280x800
     Horizontal: 1280 1328 1360 1440 (+48 +80 +160) -hsync
       Vertical:  800  803  809  823 (+3 +9 +23) +vsync
    Frequencies: 71.00 MHz, 49.31 kHz, 59.91 Hz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #15 (VGA compatible controller)

After running the xrandr command to get the 2560x1600 resolution working, I see this in the xrandr output. Did that mode already exist but wasn't visible/availability before?

Code:

DP2 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 640mm x 400mm
   2560x1600     59.86*+  59.86*   <<==================
   1280x800      59.91

Does any of this help narrow this down? I really appreciate the help.