Index:
[thread]
[date]
[subject]
[author]
From: Brent Fulgham <bfulgham@xpsystems.com>
To : GGI-Develop <ggi-develop@eskimo.com>
Date: Mon, 19 Jul 1999 10:45:26 -0700
Request for Assistance: Anyone with RIVA128 kgicon success?
I have working FB-level support for my RIVA128 card (Diamond MM Viper 330).
I can start my system in a variety of color depths and resolutions. The
LIBGGI examples all work fine.
I attempted to compile and use a RIVA128-based kgicon module, but was
unsuccessful.
Can someone who has a working RIVA128 kgicon get in contact with me?
I observed the following:
1. Hardare detection in the kgicon build process identified my card
correctly.
2. I build using a generic-generic monitor, and when I insmod the module,
my screen
goes "blank" and I have to reboot. Removing the module does not reset the
screen.
I can start X when the screen is "blanked" and this works, but as soon as I
leave X
I return to the "blank" screen.
The screen is not really "blank", but rather seems to be a light grey. I
can also hear
a high-pitched noise from my monitor, consistent with a bad setting for
screen refresh or similar. If I do an alt-F2/3/4 I sometimes get slightly
different colors (i.e., usually
a green color or sometimes a blue background).
I do not see text, or even "ASCII Graphic" text. I see no on-screen
indication that I am typing, although the system responds correctly (starts
X, reboots the system, etc.)
3. If I capture STDOUT/STDERR to a file (and read it after rebooting) I see
that the
RIVA128 support module has been loaded, and it correctly identifies the
memory available to the card (4 Megs).
4. Copying the kgicon.o modules to another name (kgicon2.o) and installing
after the first, then removing does not work (contrary to some reports in
the mailing list archives).
5. Recompiling kgicon.o using my monitors' specific settings does not
change matters.
6. Booting into a vga mode (instead of a text mode as previous) does not
change the behavior of the card. Neither does starting/stopping X before
insmoding the card.
7. I notice that the header files used in the kgicon source do not reflect
the most recent versions provided by nVidia. I swapped these files out, but
did not observe any benefit.
Can someone knowledgable either:
1) Let me know what I am doing wrong.
-or-
2) Provide me with some data to help me isolate and debug the cause.
Thanks,
-Brent
Index:
[thread]
[date]
[subject]
[author]