[icebaer]

Hi there,

currently i'm having the problem, that after starting my computer when a beamer is connected and running, kodi gives me only default refresh rate of 60Hz.
After first boot, when beamer is still warming up, all possible refresh rates (24,50,60Hz) are selectable within kodi.

When logging out and starting a XFCE session, all refresh rates are selectable in both cases.

kodi.log 1st boot: http://paste.ubuntu.com/12774758/
kodi.log reboot: http://paste.ubuntu.com/12774759/

I'm using kernel 4.3-rc5 on a N3150 with jarvis alpha from the VAAPI thread.

[icebaer]

When comparing both log files, i noticed two - maybe relevant - differences.

In kodi.log when beamer/display is up and running

Code:

DEBUG: GetFirstConnectedInterface no connected interface found - requery list

This entry isn't existing, in other log.

In kodi.log when beamer is warming up.

Code:

DEBUG: NotifyXRREvent - notify display reset event
   INFO: Available videomodes (xrandr):
   INFO: Output 'HDMI3' has 45 modes

This happend, when the beamer is ready after warming up.

Looks like the NotifyXRREvent Handler does something different, then the startup process does.

[icebaer]

Found a workaround for this problem.
Turning my AV-receiver off and on again while running kodi, reactivates the missing refresh rates

This should force the same event to appear, as when the beamer starts up.

So the problem itself isn't solved, but it's priority - at least for me - has been lowered

[fritsch]

I would try to write a little xrandr script, e.g. xrandr --output "youroutput" --off ; xrandr --output "youroutput" --auto and see if this makes a difference.

[fritsch]

Does a full edid overwrite help? Like I have shown in the other thread - in combination with a xorg.conf?

[Ales]

It seems to me it is an xorg / intel driver related. My workaround is to add sleep time before my xrandr command in .xinitrc:

Code:

cat ~/.xinitrc
( /usr/bin/sleep 15 ; /usr/bin/xrandr --output HDMI2 --mode 1920x1080 --rate 50.00 --set "Broadcast RGB" "Full" ) &
exec startlxde

It causes short blink while commant is issued.
Another workaround would be to add the same delay before kodi start up command.

Does a full edid overwrite help? Like I have shown in the other thread - in combination with a xorg.conf?

I am actually using edid downladed from my TV to provide available modes even if the TV is turned off while my HTPC is booting. My kernel line parameters are:

Code:

root=UUID=fd89ab2f-036f-4b49-8ae9-aa6a89f89324 rootfstype=ext4 rw loglevel=3 rootflags=relatime,data=ordered,commit=15,discard drm_kms_helper.edid_firmware=HDMI-A-2:edid/lg47la660s video=HDMI-A-2:1920x1080D systemd.show_status=0 libata.force=2:1.5G quiet pci=nomsi

Edid file is included in my initrd of course.

This solution worked perfectly for more than year, however I am not sure when exactly it start behave like it is behaving now.

[fritsch]

you hacked up initrd, too?

Mind adding a simple xorg.conf?

dmesg | pastebinit please and Xorg.0.log also - let's see if there is something.

[Ales]

Mind adding a simple xorg.conf?

Ok fritsch I am very sorry for not listening Your wise advice. I missed UXA option in my xorg.conf.

my xorg.conf is prety easy and now it is looking like this:

Code:

cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
    Identifier      "Intel Graphics"
    Driver          "intel"
    VendorName      "Intel Corporation"
    BoardName       "Intel Corporation N10 Family Integrated Graphics Controller"
    BusID           "PCI:0:2:0"
    Option          "TripleBuffer"    "Off"
    Option          "TearFree"        "false"
    Option          "AccelMethod"     "UXA"
EndSection

you hacked up initrd, too?

I mean iniramfs. (cat /sys/class/drm/card0-HDMI-A-2/edid > /lib/firmware/edid/lg47la660s then added FILES="/lib/firmware/edid/lg47la660s" to mkinitcpio.conf and run mkinitcpio -p linux)

dmesg | pastebinit please and Xorg.0.log also - let's see if there is something.

It is solved for me by UXA option. Would it be helpful for others to provide this log anyway?

[fritsch]

UXA should not at all have anything to do with mode enumeration.

Please file a bug with bugs.freedesktop.org but give me:

dmesg | pastebinit
and
dpkg -l |grep intel

before please.

[Ales]

I am not sure if it will be useful for you, because I am still on Archlinux, but here it is:

dmesg: http://paste.ubuntu.com/12802701/

intel packages:

Code:

pacman -Qs intel
local/intel-ucode 20150121-1
    Microcode update files for Intel CPUs
local/libva-intel-driver 1.6.1-1
    VA-API implementation for Intel G45 and HD Graphics family
local/mesa 11.0.3-1
    an open-source implementation of the OpenGL specification
local/xf86-video-intel 1:2.99.917+478+gdf72bc5-2 (xorg-drivers xorg)
    X.org Intel i810/i830/i915/945G/G965+ video drivers

[fritsch]

So - the downgrade your intel video driver and check what was changed lately to see if that is the reason.

Edit: Best is: bisect http://cgit.freedesktop.org/xorg/driver/...intel/log/