by Hi,
I have two questions, independent of each other. Both problems
are workable, but annoying.
I am not new to Linux, I have been using it for a while
now, and have done some simple kernal driver things. I glance
at EVERY c.os.lin.help posting to make sure my questions
haven't been asked before. This is therefore an unflammable
question (:-)
Ftape:
I've got it working great. I've got the Colorado 250 Internal,
and I have all of the ftape stuff working for 99.15
Tar works great, I've backed my whole hard drive a couple of times.
Except, in order to get it working completely I had to move
to libraries out of the set of files to be backed up. If
these two libraries were in the set of files ftape would go
chugging away happily until it got to these files, and would
then just stop. No errors, no warnings, it would just stop.
It is not a space problem. These two libs were the curses libs,
libdcurses.a and libncurses.a (may have the exact names wrong).
I can use curses, so they don't seem to be corrupt. The only thing
strange that I saw from them is that they are owned by "sys" and
the group is "sys". These are the only two files I've found
like that. Ideas? It is simple to just move them whenever I have
to back up, but I'd like to know the story.
XFree: I had a #9 Level 11 ISA card (surprise to me, since I paid
for a VLB card. When I found out that the wrong card has been installed
the salesman said "Gee, I wonder how that happened?"). X worked
great with the ISA card and my CTX 17" monitor. Once I got the
ISA replaced with a VLB card, I get some strange X things. It seems
I have to startx twice in order for the 1100x900 to work. The
following is the "diff" for the two startx runs:
---First time I do startx------------------
(--) S3: Maximum allowed dot-clock: 110MHz
(**) S3: Mode "1024x800": mode clock = 72.000
(**) S3: Mode "1152x900": mode clock = 85.000
(**) S3: Mode "800x600": mode clock = 40.000
(**) S3: Mode "640x480": mode clock = 25.000
(**) S3: Virtual resolution set to 1152x900
---Second time I do startx------------------
(--) S3: Detected a BrookTree Bt485 RAMDAC
(--) S3: Maximum allowed dot-clock: 85MHz
(**) S3: Mode "1024x800": mode clock = 72.000
(**) S3: Mode "1152x900": mode clock = 85.000
(**) S3: Mode "800x600": mode clock = 40.000
(**) S3: Mode "640x480": mode clock = 25.000
(**) S3: Virtual resolution set to 1152x900
It seems that they only difference is that it does not detect
the RAMDAC the first time, and that the Mac dot clock is different.
The first time I run it the 1152x900 is either a blank screen or
a very snowy screen.
Any ideas?
Thanks
Mark Coyle
U of Minn CS Department