[Info-vax] Audio and video technology, was: Re: getting pixel dimensions of monitor
VAXman- at SendSpamHere.ORG
VAXman- at SendSpamHere.ORG
Wed Feb 6 11:53:36 EST 2013
In article <kers70$msk$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>On 2013-02-05, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> wrote:
>>
>> I've moved from 1280x1024 to 1920x1080 over the last year and in each
>> case, while my manual 1280x1024 settings (which I had for historical
>> reasons) were used on the new monitor, all I did was to comment out the
>> manual settings in xorg.conf and restart X.
>>
>> In each case, the new monitor was then probed automatically and the
>> desktop came up just fine at 1920x1080 without any further action
>> required. This took me just a few minutes and was on unbranded generic
>> hardware; I am not using anything specifically branded as supporting
>> Linux.
>>
>
>I should clarify this part to make clear that in the case of my home
>machines I am referring to the PC hardware other than the graphics
>adapter; the graphics adapters use the NVIDIA binary Linux drivers
>so I can use hardware acceleration to play games and do other things.
>
>However, my main work machine is using a ATI adapter which uses the
>Scientific Linux supplied drivers and I had the same trouble free
>experience with that as well.
And just when I was about to praise how well things were going, I unstalled
the latest updates and now 'totem' is hopelessly broken. Complaining about
a Gdk error. Gotta love those informative error messages too... error_code
1 request code 154 minor_code 19. Talk about cryptic. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
More information about the Info-vax
mailing list