PDA

View Full Version : 13.04 - No Display Port [Intel/ThinkPad X201]



devstuff
April 30th, 2013, 04:58 PM
Hi all,

Since installing 13.04 I do not seem to be able to use my external monitors properly. The first monitor (connected by vga cable) seems to work but only up to 1600x1200 while it was up to 1920x1200 before. While my other monitor (Yamakasi 27" connected via the display port) does not even show signs of starting up (the power led normally flashes red for a min before coming on).




xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200
default connected 1600x1200+0+0 0mm x 0mm
1600x1200 0.0*
1280x1024 0.0
1280x800 0.0
1024x768 0.0
800x600 0.0
640x480 0.0

This is only showing the monitor connected on the analogue port :-


parse-edid: parse-edid version 2.0.0
get-edid: get-edid version 2.0.0

Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful

VBE version 300
VBE string at 0x11100 "Intel(R)Ironlake Mobile Graphics Chipset Accelerated VGA BIOS"

VBE/DDC service about to be called
Report DDC capabilities

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful

Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
Read EDID

Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful

parse-edid: EDID checksum passed.

# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
Identifier "BenQ G2400W"
VendorName "BNQ"
ModelName "BenQ G2400W"
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
HorizSync 31-94
VertRefresh 50-85
# Max dot clock (video bandwidth) 210 MHz
# Block type: 2:0 3:fc
# DPMS capabilities: Active off:yes Suspend:no Standby:no

Mode "1920x1200" # vfreq 59.950Hz, hfreq 74.038kHz
DotClock 154.000000
HTimings 1920 1968 2000 2080
VTimings 1200 1203 1209 1235
Flags "-HSync" "+VSync"
EndMode
# Block type: 2:0 3:ff
# Block type: 2:0 3:fd
# Block type: 2:0 3:fc
EndSection

If I try and set the modes by hand :-


xrandr: Failed to get size of gamma for output default
warning: output HDMI1 not found; ignoring
warning: output LVDS1 not found; ignoring
warning: output DP1 not found; ignoring
warning: output VGA1 not found; ignoring



Anyone else have this problem before? It was fine on 12.10... Any help would be appreciated!

jizzyjugs
May 1st, 2013, 02:25 AM
I'm having a similar problem. After updating to 13.04 from 12.04, my computer stopped detecting my external monitor on HDMI, but still works fine with VGA.



blaise@lxdpy:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev ff)

Jack Kelly
May 1st, 2013, 08:13 AM
I appear to be having a similar problem. My displayport monitor worked fine on 12.10 but it goes into power saving mode when using 13.04.



~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)


update
Hmm... I can now use my displayport monitor in conjunction with my laptop screen on 13.04. I unplugged my displayport monitor, then I went to System Settings -> Appearance and I enabled auto-hiding of the launcher and enabled workspaces. I then plugged my displayport monitor back in and it "just worked". Not sure what's going on!

devstuff
May 1st, 2013, 09:41 AM
Hmm that is good Jack. :)

Curious, do you have an xorg config set. As in if you run cat /etc/X11/xorg.conf what do you get? Also does your extra ports show up if you run "xrandr" ?

Cheers,

Jodi

devstuff
May 1st, 2013, 11:34 AM
Right I "fixed" it.

Basically, removing "nomodeset" from grub on the new kernel fixed the issue. All monitors fired up just fine.

jizzyjugs
May 3rd, 2013, 05:57 AM
The latest kernel update in the repos seems to have fixed the problem.

devstuff
May 3rd, 2013, 10:57 AM
Going to give that a try and see what happens.

dontogbe
May 22nd, 2013, 02:17 PM
Having the same problem on ThinkPad T410. What's the fix again?