Re: dvisvga (tmview) can't do resolution more than -d320x200!

1999-03-10 Thread Hamish Moffatt
On Tue, Mar 09, 1999 at 05:41:01PM +1030, Mark Phillips wrote:
 I've just installed dvisvga and discovered that it can't seem to
 handle resolutions higher than 320x200.  Now I have a SVGA card that
 should be capable of handling 1024x768 --- certainly, this is the
 resolution of X.  When I try I get the following error:
 
 fatal error: display: no such vga-mode on this machine
 
 How can this be?  How can I fix it?

Does it use svgalib, and if so is there some configuration files for
svgalib which you need to edit to tell it what video card you have?


Hamish
-- 
Hamish Moffatt VK3TYD  [EMAIL PROTECTED], [EMAIL PROTECTED]
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome.   http://hamish.home.ml.org


dvisvga (tmview) can't do resolution more than -d320x200!

1999-03-09 Thread Mark Phillips
I've just installed dvisvga and discovered that it can't seem to
handle resolutions higher than 320x200.  Now I have a SVGA card that
should be capable of handling 1024x768 --- certainly, this is the
resolution of X.  When I try I get the following error:

fatal error: display: no such vga-mode on this machine

How can this be?  How can I fix it?

Thanks,

Mark.



_/\___/~~\
/~~\_/~~\__/~~\__Mark_Phillips
/~~\_/[EMAIL PROTECTED]
/~~\HE___/~~\__/~~\APTAIN_
/~~\__/~~\
__
They told me I was gullible ... and I believed them! 




Problems configuring libvga.conf (was: dvisvga (tmview) can't do resolution more than -d320x200!)

1999-03-09 Thread Mark Phillips
  I've just installed dvisvga and discovered that it can't seem to
  handle resolutions higher than 320x200.  Now I have a SVGA card that
  should be capable of handling 1024x768 --- certainly, this is the
  resolution of X.  When I try I get the following error:
 
  fatal error: display: no such vga-mode on this machine
 
  How can this be?  How can I fix it?
 
 If this uses svgalib, then you should see man vga.conf, and edit that file
 (vga.conf) somewhere in /etc/vga or I don't remember where...

Thanks.  It is /etc/vga/libvga.config

I set about editing this file for my card and monitor.  After doing
this, sure enough, when I run dvisvga it now is able to attempt the
1024x768 resolution.  The only problem is that it is not terribly
successful.

It starts up and the screen goes white (appropriate for dvi viewing I
suppose), but there are some slightly sloping funny lines on the
screen, a bit of text down the bottom --- ie the screen looks like it
has partly got there but gone wrong.  And this only lasts for about
a second or two before it totally blacks out leaving nothing.

I tried it the first time while X was still running.  When I got back
into X I found things seriously stuffed up.  The next time I decided
to get out of X before running it --- should I be able to run svgalib
stuff at the same time as X?

Anyway, I'd appreciate any help on getting the libvga.conf settings
right.  I include my current settings below.

Thanks,

Mark.

P.S.  Perhaps the problem is that my ARC chipset is not properly supported
by svgalib?  Here's some info from my XF86Config:

Section Device
Identifier  Mark's video card
VendorName  legend
BoardName   PV32
Chipset ark1000pv
Ramdac  ark1491
Clocks  25.00  28.32  39.33  71.90  50.00  76.49  35.94  44.25
Clocks  127.49 118.03  78.69  31.15 108.58  63.72  73.65  93.53
#VideoRam1024
# Insert Clocks lines here if appropriate
EndSection


Anyway, here's my libvga.config as promised:



# Configuration file for svgalib. Default location is /etc/vga.
# Other config file locations:  ~/.svgalibrc
#   where SVGALIB_CONFIG_FILE points
# Lines starting with '#' are ignored.

# Have a deep look at README.config to see what can do here (especially
# for mach32).

# Mouse type:

# mouse Microsoft   # Microsoft
mouse MouseSystems  # Mouse Systems
# mouse MMSeries# Logitech MM Series
# mouse Logitech# Logitech protocol (old, newer mice use Microsoft 
protocol)
# mouse Busmouse# Bus mouse
# mouse PS2 # PS/2 mouse
# mouse MouseMan# Logitech MouseMan
# mouse Spaceball   # Spacetec Spaceball
# mouse IntelliMouse# Microsoft IntelliMouse or Logitech MouseMan+ on 
serial 
port
# mouse IMPS2   # Microsoft IntelliMouse or Logitech MouseMan+ on PS/2 
port
# mouse none# None

mouse unconfigured

# (DEBIAN NOTE: the mouse used to default to microsoft, but this was changed
#  to fix bug #13458. If your mouse used to work fine, you can simply change
#  it back to read microsoft again. If you are careful to change *only that
#  one word*, and not to add or remove extra whitespace, the package
#  installation will continue to update this file without requiring user
#  intervention because of a modified config file.
#  This applies to all mouse types, not just microsoft.)

# Mouse/keyboard customisation by 101 (Attila Lendvai). If you have any good
# ideas you can reach me at [EMAIL PROTECTED]

# mouse_accel_type  normal  # No acceleration while delta is less then
# threshold but delta is multiplied by
# mouse_accel_mult if more. Originally done by
# Mike Chapman [EMAIL PROTECTED]

mouse_accel_typepower   # The acceleration factor is a power function
# of delta until it reaches m_accel_mult. It
# starts from the coordinate 
# [1, 1 + m_accel_offset] and goes to
# [m_accel_thresh, m_accel_mult]. If delta
# is bigger then m_accel_thresh it is a plain
# constant (m_accel_mult). It is the f(delta)
# function with which the delta itself will be
# multiplied. m_accel_offset is 1 by default,
# so for delta = 1 the accelerated delta will
# remain 1 (You don't lose resolution). The
# starting point of the f(delta) function
# might be moved along the Y axis up/down with
# m_accel_offset thus defining the initial
# minimum acceleration (for delta = 1).
# Basically it's like