3:53 a.m.
Hi
I'm trying to get a Dell M1330 with Intel GM965 ,using HDMI interface,
connected to a Samsung TV (LA32B650). The connection works but I cannot get
any better resolution than 1024x768 and I have HDMI Audio option in
pulseaudio profiles, I have no sound. Has anyone got similar setup to work
at native 1920x1080 resolution with audio? Also, if it is a problem with not
detecting TV's modes, is there a way to manually set the resolution for a
HDMI-connected device?
This is on a up-to-date rawhide.
Regards,
Masood
9:40 a.m.
On Wed, 2009-05-13 at 18:53 +1000, Masood wrote:
Hi
I'm trying to get a Dell M1330 with Intel GM965 ,using HDMI interface,
connected to a Samsung TV (LA32B650). The connection works but I
cannot get any better resolution than 1024x768 and I have HDMI Audio
option in pulseaudio profiles, I have no sound. Has anyone got similar
setup to work at native 1920x1080 resolution with audio? Also, if it
is a problem with not detecting TV's modes, is there a way to manually
set the resolution for a HDMI-connected device?
What does your X log look like? In particular, does it show the EDID
block for the HDMI monitor, and does it say why it's throwing away the
1920x1080 mode.
- ajax
11:12 a.m.
Here is the output from xrandr and Xorg.0.log:
$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis)
287mm x 180mm
1280x800 60.0*+
DVI1 connected (normal left inverted right x axis y axis)
1024x768 60.0
800x600 60.3
640x480 59.9
$ cat /var/log/Xorg.o.log
...
(II) intel(0): EDID for output DVI1
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "640x480" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "800x600" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1024x768" (vrefresh out of range)
(II) intel(0): Not using default mode "1152x864" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x960" (hsync out of range)
(II) intel(0): Not using default mode "1280x960" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (hsync out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1280x1024" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (hsync out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1600x1200" (vrefresh out of range)
(II) intel(0): Not using default mode "1792x1344" (hsync out of range)
(II) intel(0): Not using default mode "1792x1344" (vrefresh out of range)
(II) intel(0): Not using default mode "1856x1392" (hsync out of range)
(II) intel(0): Not using default mode "1856x1392" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (hsync out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "832x624" (vrefresh out of range)
(II) intel(0): Not using default mode "1400x1050" (hsync out of range)
(II) intel(0): Not using default mode "1400x1050" (vrefresh out of range)
(II) intel(0): Not using default mode "1920x1440" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (hsync out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Not using default mode "2048x1536" (vrefresh out of range)
(II) intel(0): Printing probed modes for output DVI1
(II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768
771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601
605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492
525 -hsync -vsync (31.5 kHz)
Regards,
Masood
On Thu, May 14, 2009 at 12:40 AM, Adam Jackson <ajax(a)redhat.com> wrote:
On Wed, 2009-05-13 at 18:53 +1000, Masood wrote:
> Hi
>
> I'm trying to get a Dell M1330 with Intel GM965 ,using HDMI interface,
> connected to a Samsung TV (LA32B650). The connection works but I
> cannot get any better resolution than 1024x768 and I have HDMI Audio
> option in pulseaudio profiles, I have no sound. Has anyone got similar
> setup to work at native 1920x1080 resolution with audio? Also, if it
> is a problem with not detecting TV's modes, is there a way to manually
> set the resolution for a HDMI-connected device?
What does your X log look like? In particular, does it show the EDID
block for the HDMI monitor, and does it say why it's throwing away the
1920x1080 mode.
- ajax
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
12:27 p.m.
On Wed, 2009-05-13 at 12:43 -0400, Kyle McMartin wrote:
On Thu, May 14, 2009 at 02:12:16AM +1000, Masood wrote:
> Here is the output from xrandr and Xorg.0.log:
>
Can you just attach the entire Xorg.0.log? You've snipped off the EDID
data from it...
Actually, I suspect he didn't. The xrandr output makes it look like
he's just not getting EDID at all.
There was a fix for EDID fetch from HDMI in 2.6.29.1-104, but it
certainly ought to be included in current kernels. There might have
been a followup fix since though, I'll check.
- ajax
11:28 p.m.
On Thu, May 14, 2009 at 2:43 AM, Kyle McMartin <kyle(a)mcmartin.ca> wrote:
Can you just attach the entire Xorg.0.log? You've snipped off the EDID
data from it...
Please see the attachment for a complete log though I couldn't find much
about DVI1 interface other than the what I'd posted earlier.
Regards,
Masood
7:46 a.m.
I have just found out that if I have HDMI cable plugged in and restart the
laptop, a correct EDID gets picked up during boot process and I will have
the native 1920x1080 available. So it seems the problem only exists if I
plug in a HDMI cable when X has already started. See the Xorg.0.log below:
(II) intel(0): EDID for output HDMI1
(II) intel(0): Manufacturer: SAM Model: 509 Serial#: 1
(II) intel(0): Year: 2008 Week: 48
(II) intel(0): EDID Version: 1.3
(II) intel(0): Digital Display Input
(II) intel(0): Indeterminate output size
(II) intel(0): Gamma: 2.20
(II) intel(0): No DPMS capabilities specified
(II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) intel(0): First detailed timing is preferred mode
(II) intel(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
(II) intel(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
(II) intel(0): Supported VESA Video Modes:
(II) intel(0): 720x400@70Hz
(II) intel(0): 640x480@60Hz
(II) intel(0): 640x480@67Hz
(II) intel(0): 640x480@72Hz
(II) intel(0): 640x480@75Hz
(II) intel(0): 800x600@60Hz
(II) intel(0): 800x600@72Hz
(II) intel(0): 800x600@75Hz
(II) intel(0): 832x624@75Hz
(II) intel(0): 1024x768@60Hz
(II) intel(0): 1024x768@70Hz
(II) intel(0): 1024x768@75Hz
(II) intel(0): 1280x1024@75Hz
(II) intel(0): 1152x870@75Hz
(II) intel(0): Manufacturer's mask: 0
(II) intel(0): Supported Future Video Modes:
(II) intel(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) intel(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
(II) intel(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) intel(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) intel(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
(II) intel(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
(II) intel(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 148.5 MHz Image Size: 160 x 90 mm
(II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end
2200 h_border: 0
(II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking:
1125 v_border: 0
(II) intel(0): Supported additional Video Mode:
(II) intel(0): clock: 85.5 MHz Image Size: 160 x 90 mm
(II) intel(0): h_active: 1360 h_sync: 1424 h_sync_end 1536 h_blank_end
1792 h_border: 0
(II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 795
v_border: 0
(II) intel(0): Ranges: V min: 24 V max: 75 Hz, H min: 26 H max: 81 kHz,
PixClock max 230 MHz
(II) intel(0): Monitor name: SAMSUNG
(II) intel(0): Number of EDID sections to follow: 1
(II) intel(0): EDID (in hex):
(II) intel(0): 00ffffffffffff004c2d090501000000
(II) intel(0): 30120103801009780aee91a3544c9926
(II) intel(0): 0f5054bdef80714f8100814081809500
(II) intel(0): 950fb3000101023a801871382d40582c
(II) intel(0): 4500a05a0000001e662150b051001b30
(II) intel(0): 40703600a05a0000001e000000fd0018
(II) intel(0): 4b1a5117000a202020202020000000fc
(II) intel(0): 0053414d53554e470a2020202020016f
(II) intel(0): Printing probed modes for output HDMI1
(II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080
1084 1089 1125 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024
1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768
771 777 795 +hsync +vsync (47.7 kHz)
(II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864
865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768
769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768
771 777 806 -hsync -vsync (56.5 kHz)
(II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768
771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625
628 667 -hsync -vsync (49.7 kHz)
(II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637
643 666 +hsync +vsync (48.1 kHz)
(II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601
604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601
605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491
520 -hsync -vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484
500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486
525 -hsync -vsync (35.0 kHz)
(II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492
525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414
449 -hsync +vsync (31.5 kHz)
8:27 a.m.
On Thu, 14 May 2009 22:46:59 +1000
Masood wrote:
So it seems the problem only exists if I
plug in a HDMI cable when X has already started.
Definitely. You'll see the same thing with KVM
switches. X has just gotta have the monitor
connection when it starts now, there is no
apparent way to convince it to just use the
mode you want.
11:26 a.m.
On Thu, 2009-05-14 at 09:27 -0400, Tom Horsley wrote:
On Thu, 14 May 2009 22:46:59 +1000
Masood wrote:
> So it seems the problem only exists if I
> plug in a HDMI cable when X has already started.
Definitely. You'll see the same thing with KVM
switches. X has just gotta have the monitor
connection when it starts now, there is no
apparent way to convince it to just use the
mode you want.
This isn't true with Kernel Mode Setting anymore. With KMS you do get
enough memory reserved to handle the largest resolution your card can
do, regardless of what was plugged in at the time X launched.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
8:01 a.m.
On Fri, May 29, 2009 at 2:26 AM, Jesse Keating <jkeating(a)redhat.com> wrote:
This isn't true with Kernel Mode Setting anymore. With KMS you
do get
enough memory reserved to handle the largest resolution your card can
do, regardless of what was plugged in at the time X launched.
As I mentioned, I don't think the problem is with X not having enough memory
for largest resolution, but not reading resolution information when you
hot-plug a HDMI connection (or maybe other interface types). If I manually
add the modelines using xrandr, it just works.
Regards,
Masood
8:48 a.m.
On Fri, May 29, 2009 at 9:01 AM, Masood <masoodbeh(a)gmail.com> wrote:
As I mentioned, I don't think the problem is with X not having
enough memory
for largest resolution, but not reading resolution information when you
hot-plug a HDMI connection (or maybe other interface types). If I manually
add the modelines using xrandr, it just works.
I actually had to disable KMS for my chipset (Intel G33). Worked fine
for some outputs, but totally broke hdmi (in a no picture at all kind
of way) [1].
Like most televisions, mine gives crappy edid info, so I ended up
having to use an xorg.conf for force things a bit. Now if only I could
get 1080i to work [2].
I just got sound over hdmi working last night. I just had to pass the
right model to the sound driver. [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=496772
[2] http://bugs.freedesktop.org/show_bug.cgi?id=11220
[3] https://bugzilla.redhat.com/show_bug.cgi?id=502890
10:39 p.m.
On Fri, May 29, 2009 at 11:48 PM, Mike McLean <mikem.rtp(a)gmail.com> wrote:
I just got sound over hdmi working last night. I just had to pass
the
right model to the sound driver. [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=496772
[2] http://bugs.freedesktop.org/show_bug.cgi?id=11220
[3] https://bugzilla.redhat.com/show_bug.cgi?id=502890
Where did you add "options and_hda_intel model=3stack-6ch" to?
Regards,
Masood
11:24 p.m.
On Sat, 2009-05-30 at 13:39 +1000, Masood wrote:
On Fri, May 29, 2009 at 11:48 PM, Mike McLean
<mikem.rtp(a)gmail.com>
wrote:
I just got sound over hdmi working last night. I just had to
pass the
right model to the sound driver. [3]
[1] https://bugzilla.redhat.com/show_bug.cgi?id=496772
[2] http://bugs.freedesktop.org/show_bug.cgi?id=11220
[3] https://bugzilla.redhat.com/show_bug.cgi?id=502890
Where did you add "options and_hda_intel model=3stack-6ch" to?
Just create a file named something.conf in /etc/modprobe.d . 'something'
can be anything you like. hdmi.conf , for e.g.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
11:27 a.m.
On Fri, 2009-05-29 at 23:01 +1000, Masood wrote:
On Fri, May 29, 2009 at 2:26 AM, Jesse Keating
<jkeating(a)redhat.com>
wrote:
This isn't true with Kernel Mode Setting anymore. With KMS
you do get
enough memory reserved to handle the largest resolution your
card can
do, regardless of what was plugged in at the time X launched.
As I mentioned, I don't think the problem is with X not having enough
memory for largest resolution, but not reading resolution information
when you hot-plug a HDMI connection (or maybe other interface types).
If I manually add the modelines using xrandr, it just works.
Yes, it could be a bad monitor. I have one monitor I use HDMI with,
however it uses a HDMI to DVI converter at the monitor side, and it's
plugged into the HDMI port on my M1330. No matter whats plugged into my
laptop at X launch time, I can plug in this monitor and successfully get
native resolution on it. I have a 26" LCD TV that I use direct HDMI
with and it too gets proper resolution when I plug it in, regardless of
when X launched. My M1330 uses the intel driver, and if yours does too,
then the likely culprit is the display.
--
Jesse Keating RHCE (http://jkeating.livejournal.com)
Fedora Project (http://fedoraproject.org/wiki/JesseKeating)
GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
identi.ca (http://identi.ca/jkeating)
10:18 a.m.
On Wed, May 13, 2009 at 4:53 AM, Masood <masoodbeh(a)gmail.com> wrote:
I'm trying to get a Dell M1330 with Intel GM965 ,using HDMI
interface,
connected to a Samsung TV (LA32B650). The connection works but I cannot get
any better resolution than 1024x768 and I have HDMI Audio option in
pulseaudio profiles, I have no sound. Has anyone got similar setup to work
at native 1920x1080 resolution with audio? Also, if it is a problem with not
detecting TV's modes, is there a way to manually set the resolution for a
HDMI-connected device?
Did you ever get you HDMI audio working? I'm having a similar audio
problem with my setup (intel G33 chipset).
7:52 a.m.
On Fri, May 29, 2009 at 1:18 AM, Mike McLean <mikem.rtp(a)gmail.com> wrote:
Did you ever get you HDMI audio working? I'm having a similar
audio
problem with my setup (intel G33 chipset).
Nope. I'm still working on it and will let you know if I find a solution for
it.
Regards,
Masood
5442
days inactive
5459
days old
15 comments
8 participants
participants (8)
-
Adam Jackson -
Adam Williamson -
Jesse Keating -
Jesse Keating -
Kyle McMartin -
Masood -
Mike McLean -
Tom Horsley