On Fri, 12 Jan 2001 06:11:53 -0500 (EST), Klaus Hameyer wrote:
> At the risk of telling you something that you already know,
> here is what I did to get Arachne166b for linux to run:
> 1. decompressed/untarred it
> 2. ran ./install
> 3. chose Arachne directory to be /opt/arachne166b
> (config, cookie, and other files ended up in dir /root/.arachne/)
> (a script to run it is in /usr/bin/arachne)
> 4. you NEED SVGAlib to run Arachne.
Hi Klaus;
Up to here I've done pretty much the same. I know, minor differences
CAN be fatal. <G>
I've assumed I *HAVE* SVGAlib. I have a /svgalib directory, but there
isn't much in it except mousey stuff - and I don't use a mouse.
There is ONE thing I found useful: VGATEST.
And I DO have the following mentioned libvga.config.
> 5. I obtained an rpm copy and installed via rpm (RedHatProgramMgr)
> 6. it needed to be configured; file = /etc/vga/libvga.config
> halfway through file are the screen settings:
> for 800x600 I used HorSync 35.1
> VertRefresh 90
> I then had to fiddle with other settings and found that
> Chipset VESA
> VesaText
> VesaSave 1
> worked for my TVGA 1MB video card. Yours may work
> without fiddling.
It WAS set for VESA but the uncommented settings were for a *RANGE* of
Horsync and VertRefresh. (31.5-37.9 and 50-90) I didn't change that.
Am I supposed to pick specific numbers ?
I commented out all references to mouse.
My results are: (see update below)
I can type "arachne" and get:
Illegal instruction /usr/bin/arachne-svgalib $*
I can cd to /usr/bin and type "arachne-svgalib" and get:
Illegal instruction arachne-svgalib
The dir has *arachne-svgalib in it (267224 bytes) and permissions are:
-rwxr-xr-- and owner is root and I'm logged in as root.
Updated results: New test.
I tried ./VGATEST with SINGLE numbers in Hsync and VRefresh and got an
error message telling me to use a RANGE followed by the same Illegal
instruction complaint. Something made me think the problem was in a
later part of VGAconfig (whatever) so I commented out everything after
the sync settings except VESA chipset and restored the range settings.
I got the same Illegal Instruction message. I then commented out VESA
chipset because it said it would auto-detect and bingo!
It decided to use standard VGA and proceeded to give me a test screen.
So it appears to have a problem with either VESA in general or Matrox
in particular. :(
I changed Arachne config to 640x480 (unfortunately Hicolor) to give it
a try and at least I don't get the "Illegal Instruction" anymore.
The Arachne screen is a total mess - nothing recognizeable at all - and
it doesn't reset or clear when I exit. I have to run blind. I guess my
card registers get screwed up. :(
PPP itself works fine and I can use lynx, links, fetchmail and ssh.
Thanks a lot everyone for all the help. I'll give the list a rest for
a while until I find a way to tell Linux I have a good VESA card. <G>
- Clarence Verge
- Still using Arachne V1.62 ....