[lug] Video conflict - KRUD

[Kevin Fenzi]

>>>>> "Jim" == Jim Morgan <bumper_morgan at usa.net> writes:

Jim> Jim here.  I'm a newbie.  Talked to Kevin last nigh, took his
Jim> advice to use KRUD ins= tead of LTP Caldera for support
Jim> reasons. 

:)

Jim> Installed very easily, Much better than the week long trial of no
Jim> sucess = I had with RH 5.2 on my old motherboard.

thats good. The install has really come a long way since 5.2

Jim> when I log on as user and type startx - it bombs - =

Jim> ERROR Message follows: Entry deleted from font path (**) Fontpath
Jim> set to "unix/:-1" (--) Trident chipset version: 0x33
Jim> (TVGA8900CLD) (--)SVGA Revision 0 (--)SVGA:Chipset tvga8900CL
Jim> (**)SVGA Videoram 1024k (--)SVGA Clocks 25.30 28.32 45.37 36.16
Jim> 57.87 65.76 50.63 40.38 (--)SVGA Clocks 88.43 98.90 119.43 109.21
Jim> 72.34 77.61 80.79 75.96 (--)SVGA Effective Pixel clocks 12.65
Jim> 14.16 22.68 18.08 28.93 32.88 =

Jim> 25.32 20.19 (--)SVGA Effective Pixel clocks 44.22 49.45 59.72
Jim> 54.60 36.17 38.80 40.40=

Jim> 37.98 (**) SVGA 16bpp not supported by this chipset *** A
Jim> configured device found, but display modes could not be resolved.
Jim> fatal server error: no screens found.

Jim> My video card is a Trident 8900 My monitor is an old (appx 1991)
Jim> 13" Goldstar Model3028 SVGA.

Jim> a) am I correct the card and monitor are ok but i misset
Jim> something?  If so what do I do?  

it looks like you told it to do 16bpp (16 bits per pixel, or in mac
terms "thousands of colors"), and there is not enough video memory to
do that. ;( 

You can run 

XConfigurator 

again and specify only 8bpp (8 bits per pixel or 256 colors)...that
should clear it up. 

Jim> b)I notice the difference in the
Jim> (--) and (**) , does one of those codes=

Jim> indicate where a problem/conflict is found?  any help
Jim> appriciated.  also - if i have to edit any scripts, I will need
Jim> clear instructions.  =

things with (--) were probed by the X server.
things with (**) are things you specified in your config file...

while you could edit the /etc/X11/XF86Config file and fix the above
problem, I would just say run XConfigurator again and have it do the
dirty work. ;) 

Jim> Thanks in advance, Jim

kevin
-- 
Kevin Fenzi
MTS, tummy.com, ltd.
http://www.tummy.com/  KRUD - Kevin's Red Hat Uber Distribution