Re: sensors-detect changed screen's vertical rate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2012/4/6 Jean Delvare <khali@xxxxxxxxxxxx>:
> Sorry for the late reply, I have a lot of work this week.

It is ok, take your time:)

> I presume you do not remember which ones defaulted to "no" and you had
> to say "yes" explicitly?

Yes, that is what I did.

> It's strange, I do see it in mine with the radeon driver:
> Maybe there is a verbosity level to set somewhere, my X server is
> started with -verbose, maybe you have to do the same. Or

I stopped X and gave "exec /usr/bin/X -nolisten tcp "$@" -verbose 20
2> /tmp/startx.log" command but still there is no dump of EDID.

> Good, so at least we have a reference. Now we need to find out which
> bytes in your own EDID have been altered.
> You also have to offset the 3 other vertical timings:
> $ xrandr --newmode "try" 68.94 1280 1296 1344 1408 800 801 804 816 -HSync -VSync

Now I get what you wanted me to do. I tried the command above but
resolution looks bad. Icons, fonts etc. looks blur and bigger.

> That's because you have loaded the eeprom driver. Either provide the
> contents of file /sys/bus/i2c/devices/i2c-2/2-0050/eeprom or unload the
> eeprom driver and provide the output of the i2cdump command above.

Sorry, my mistake. This is the output: http://pastebin.com/aSUSR7wX

Best regards,
Numan

_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux