Hi,
New forum member here. Thanks in advance for putting this forum together. It looks like it can be quite helpful.
QUESTION: How do I set the monitor scan rates in xorg.conf for 8.27.0?
I'll keep it moderately breif. I'm a Gentoo user with a MythTV network that's been up for about 16 months. I run a 2-tuner server, 3 Linux desktop machines that run mythfrontend, and two dedicated Pundit-R machines attached to TV. The network was in need of updating so all the machines got new kernels which necessitated new ati-drivers where appropriate. I have Myth running correctly and displaying to most machines but I have one Pundit-R machine that's having some problems. I suspect it's a scan rate issue, or would at least like to eliminate that as a problem.
1) I have two Pundit-R machines. Here is how lspci shows the VGA:
myth14 ~ # lspci
<SNIP>
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP
<SNIP>
myth14 ~ #
2) Both of these machine have been updated and are running as much as possible exactly the same software. (Myth, ati-drivers, Gentoo stuff, fluxbox)
3) Both machines use the S-Video output to drive TVs. The one that fails also uses the conposit video output.
4) One machine works completely correctly driving the Sony in the bedroom.
5) One machine fails with a blue screen on the Mitsubishi in the living room.
6) The failing machine has mythfrontend and fluxbox running when I ssh into it. If I kill them I see the screen on the Mitsubishi come back to the console and the myth and fluxbox restart automatically by design. The TV then goes blue screen again like it's getting no signal, or a signal with the wrong scan rate or no signal output.
7) Even though I used the aticonfig program to update the xorg.conf file it seems that there are still things that aren't correct:
myth12 ~ # cat /var/log/Xorg.0.log | grep EE
Current Operating System: Linux myth12 2.6.16-gentoo-r13 #1 PREEMPT Thu Jul 20 18:57:49 PDT 2006 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
myth12 ~ # cat /var/log/Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/local/".
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): MonitorLayout is no longer supported.
(WW) fglrx(0): The hex number setting for DesktopSetup is deprecated,
(WW) fglrx(0): Specified desktop setup not supported: 8
(WW) fglrx(0): DRI is not supported on Radeon 9000/9100 IGP (RS300/RS350) hardware.
(WW) fglrx(0): Option "IgnoreEDID" is not used
(WW) fglrx(0): Option "NoTV" is not used
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
myth12 ~ #
If I can fix that stuff along the way that would be great also.
7) In my /etc/X11/xorg.conf file I no longer see a command for setting the scan rate of the monitor. I have a vague recollection of having this problem using the driver 16 months ago and having to set the scan rate down to something low.
I can post lots of other info here if needed. I'll stop for now and hope for some conversation on the problems.
Thanks in advance,
Mark
New forum member here. Thanks in advance for putting this forum together. It looks like it can be quite helpful.
QUESTION: How do I set the monitor scan rates in xorg.conf for 8.27.0?
I'll keep it moderately breif. I'm a Gentoo user with a MythTV network that's been up for about 16 months. I run a 2-tuner server, 3 Linux desktop machines that run mythfrontend, and two dedicated Pundit-R machines attached to TV. The network was in need of updating so all the machines got new kernels which necessitated new ati-drivers where appropriate. I have Myth running correctly and displaying to most machines but I have one Pundit-R machine that's having some problems. I suspect it's a scan rate issue, or would at least like to eliminate that as a problem.
1) I have two Pundit-R machines. Here is how lspci shows the VGA:
myth14 ~ # lspci
<SNIP>
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon 9100 IGP
<SNIP>
myth14 ~ #
2) Both of these machine have been updated and are running as much as possible exactly the same software. (Myth, ati-drivers, Gentoo stuff, fluxbox)
3) Both machines use the S-Video output to drive TVs. The one that fails also uses the conposit video output.
4) One machine works completely correctly driving the Sony in the bedroom.
5) One machine fails with a blue screen on the Mitsubishi in the living room.
6) The failing machine has mythfrontend and fluxbox running when I ssh into it. If I kill them I see the screen on the Mitsubishi come back to the console and the myth and fluxbox restart automatically by design. The TV then goes blue screen again like it's getting no signal, or a signal with the wrong scan rate or no signal output.
7) Even though I used the aticonfig program to update the xorg.conf file it seems that there are still things that aren't correct:
myth12 ~ # cat /var/log/Xorg.0.log | grep EE
Current Operating System: Linux myth12 2.6.16-gentoo-r13 #1 PREEMPT Thu Jul 20 18:57:49 PDT 2006 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
myth12 ~ # cat /var/log/Xorg.0.log | grep WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/local/".
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): MonitorLayout is no longer supported.
(WW) fglrx(0): The hex number setting for DesktopSetup is deprecated,
(WW) fglrx(0): Specified desktop setup not supported: 8
(WW) fglrx(0): DRI is not supported on Radeon 9000/9100 IGP (RS300/RS350) hardware.
(WW) fglrx(0): Option "IgnoreEDID" is not used
(WW) fglrx(0): Option "NoTV" is not used
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
myth12 ~ #
If I can fix that stuff along the way that would be great also.
7) In my /etc/X11/xorg.conf file I no longer see a command for setting the scan rate of the monitor. I have a vague recollection of having this problem using the driver 16 months ago and having to set the scan rate down to something low.
I can post lots of other info here if needed. I'll stop for now and hope for some conversation on the problems.
Thanks in advance,
Mark
Comment