Mailinglist Archive: opensuse (3983 mails)
| < Previous | Next > |
Re: [SLE] SUSE linux desktop video signal out of range.
- From: Felix Miata <mrmazda@xxxxxx>
- Date: Tue, 02 Dec 2003 22:15:38 -0500
- Message-id: <3FCD555A.3983@xxxxxx>
Marshall Heartley wrote:
> You can tell SaX2 to start in low resolution mode so you can configure
> your monitor. Start SaX2 on the command line with the -l flag like so
> sax2 -l and this should get you started.
Doesn't work for me. Same thing happened as in most XFree versions over
many different distros for as long as I've been installing Linux.
Excerpts from SaX.log:
(WW) TSENG(0): Mode pool is empty
(EE) TSENG(0): No valid modes found
(EE) TSENG(0): Screen(s) found, but none have a usable configuration.
The problem, as in the past, is that XF86Config actually contains:
Section "Device"
BoardName "ET6000"
BusID "0:9:0"
Driver "tseng"
Identifier "Device[0]"
VendorName "Tseng"
EndSection
instead of what it needs to contain to work:
Section "Device"
BoardName "ET6000"
BusID "0:9:0"
Driver "tseng"
Identifier "Device[0]"
VendorName "Tseng"
VideoRam 4096
Option "noaccel"
EndSection
Because it never gets started that way, it never creates usable
modelines. I can edit the file to get some working modes, but never the
maximum resolution supported by the hardware in windoze.
--
"You will know the truth, and the truth will set you free."
John 8:32 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://members.ij.net/mrmazda/
> You can tell SaX2 to start in low resolution mode so you can configure
> your monitor. Start SaX2 on the command line with the -l flag like so
> sax2 -l and this should get you started.
Doesn't work for me. Same thing happened as in most XFree versions over
many different distros for as long as I've been installing Linux.
Excerpts from SaX.log:
(WW) TSENG(0): Mode pool is empty
(EE) TSENG(0): No valid modes found
(EE) TSENG(0): Screen(s) found, but none have a usable configuration.
The problem, as in the past, is that XF86Config actually contains:
Section "Device"
BoardName "ET6000"
BusID "0:9:0"
Driver "tseng"
Identifier "Device[0]"
VendorName "Tseng"
EndSection
instead of what it needs to contain to work:
Section "Device"
BoardName "ET6000"
BusID "0:9:0"
Driver "tseng"
Identifier "Device[0]"
VendorName "Tseng"
VideoRam 4096
Option "noaccel"
EndSection
Because it never gets started that way, it never creates usable
modelines. I can edit the file to get some working modes, but never the
maximum resolution supported by the hardware in windoze.
--
"You will know the truth, and the truth will set you free."
John 8:32 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://members.ij.net/mrmazda/
| < Previous | Next > |