[K12OSN] X & cirrus cards

Peter Van den Wildenbergh pvdw at criticalcontrol.com
Tue Sep 21 17:27:43 UTC 2004


She worky !!! Thanks Chris.
 
Will craft an e-mail to Jim and Rob !
 
Thanks
 
Peter

	-----Original Message----- 
	From: Chris Thomas [mailto:cwt137 at yahoo.com] 
	Sent: Tue 9/21/2004 11:18 AM 
	To: Support list for opensource software in schools. 
	Cc: 
	Subject: RE: [K12OSN] X & cirrus cards
	
	

	I am not near my server so these instructions wont be
	exact but you should be able to fill in the gaps or
	mistakes.
	
	First, go to the lts.conf file and put in the
	[default] section 'SCREEN_02   = shell' (without the
	quotes). and save it.
	
	Second, start one of the troubled cirrus PCs and when
	X fails, press Alt-Ctrl-F2 (or F1, I don't remember)
	to get to the prompt.
	
	At the prompt, type 'cat /proc/bus/pci/devices' This
	will give you a whole bunch of numbers. The numbers in
	the second column are pci ids. Copy the 8-digit number
	that starts with 1013. This is the cirrus card.
	
	Next, open up the vidlist file, its in the same
	directory as the lts.conf file. Go down to the cirrus
	section. Find the number you wrote down. Change the
	driver from whatever it says to 'cirrus'. Save it.
	
	Make sure your lts.conf file has 'XSERVER = auto' so
	the other 75% of the computers will work. Restart the
	troubled terminal and it should work.
	
	Last, and maybe the most important; if the troubled
	terminal works, it is now time to give back to the
	open source community! Please email the guy at the top
	of the vidlist file and CC Jim from LTSP and tell them
	about your discoveries. Ask them that your changes be
	included in the next release of LTSP. Be sure to tell
	them the version of LTSP your using, the pci id, name
	of video card if possible, and the driver you got it
	to work with. There are 100's of video cards in that
	file and not all of them have been tested with LTSP so
	your input is important!
	
	Chris
	
	--- Peter Van den Wildenbergh
	<pvdw at criticalcontrol.com> wrote:
	
	> Chris :
	> 
	> Your assumption is correct, but I gonna need a bit
	> more guidance in this.
	> Where do I find the 'vidlist' and how to get the pci
	> id?
	> 
	> pci id:
	> I got a shell on screen two of the clients so is it
	> just a matter of :
	> cat /proc/pci
	> I found
	> Bus 0, Device 8, Function 0:
	> VGA compatible controller : Cirrus Logic ...
	> 
	> or am I completely in the dark here?
	> 
	> Thanks for the fast reply! Appreciat it very much!
	> 
	> Peter
	> 
	> 
	>
	>       -----Original Message-----
	>       From: Chris Thomas [mailto:cwt137 at yahoo.com]
	>       Sent: Tue 9/21/2004 10:18 AM
	>       To: Support list for opensource software in
	> schools.
	>       Cc:
	>       Subject: Re: [K12OSN] X & cirrus cards
	>      
	>      
	>
	>       Here is what I did to solve a problem I had with
	> some
	>       S3 and cirrus cards. But first, I'm assuming the
	> 25%
	>       of the computers that are having trouble all have
	> the
	>       same video card.
	>      
	>       Get the pci id of one of the cirrus video cards and
	>       edit the entry in the vidlist file. Change it to
	> the
	>       cirrus driver instead of whatever it says. Then you
	>       can keep your 'XSERVER = auto' setting in the
	> lts.conf
	>       file.
	>      
	>       Chris
	>      
	>       Change the
	>       --- Peter Van den Wildenbergh
	>       <pvdw at criticalcontrol.com> wrote:
	>      
	>       > Hi :
	>       >
	>       > Got some serious CIRRUS whoos...
	>       > I know these cards are crap but I have to use
	> them
	>       > in +/- 25% of my clients :-(
	>       >
	>       > This in my lts.conf right now :
	>       >         XSERVER            = auto
	>       >         X_MODE_0           = 800x600
	>       >         X_COLOR_DEPTH      = 8
	>       >
	>       > This works with 75% of my clients :-) except the
	>       > cirrus ones...
	>       > When I set
	>       > XSERVER = cirrus
	>       > The remaining 25% of my lab can work, but 75%
	>       > hangs...
	>       > Fatal server error
	>       > no screens found.
	>       >
	>       > I also know that I can make an entry inside
	> lts.conf
	>       > per workstation.
	>       > But this also adds a serious task to
	> maintenance...
	>       > I will end up with 6 or 7 LTS and 300-400
	> diskless
	>       > clients who will randomly connect to one of the
	>       > servers.
	>       > so I want to keep things simple in lts.conf
	>       >
	>       > Is there a solution?
	>       >
	>       > Thanks
	>       >
	>       > Peter
	>       >
	>       >
	>       > _______________________________________________
	>       > K12OSN mailing list
	>       > K12OSN at redhat.com
	>       > https://www.redhat.com/mailman/listinfo/k12osn
	>       > For more info see <http://www.k12os.org>
	>       >
	>      
	>      
	>      
	>                     
	>       _______________________________
	>       Do you Yahoo!?
	>       Declare Yourself - Register online to vote today!
	>       http://vote.yahoo.com
	>      
	>      
	>       _______________________________________________
	>       K12OSN mailing list
	>       K12OSN at redhat.com
	>       https://www.redhat.com/mailman/listinfo/k12osn
	>       For more info see <http://www.k12os.org>
	>      
	>
	>
	
	> ATTACHMENT part 2 application/ms-tnef
	name=winmail.dat
	> _______________________________________________
	> K12OSN mailing list
	> K12OSN at redhat.com
	> https://www.redhat.com/mailman/listinfo/k12osn
	> For more info see <http://www.k12os.org>
	
	
	
	               
	__________________________________
	Do you Yahoo!?
	Yahoo! Mail is new and improved - Check it out!
	http://promotions.yahoo.com/new_mail
	
	
	_______________________________________________
	K12OSN mailing list
	K12OSN at redhat.com
	https://www.redhat.com/mailman/listinfo/k12osn
	For more info see <http://www.k12os.org>
	

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 12882 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/k12osn/attachments/20040921/8206950d/attachment.bin>


More information about the K12OSN mailing list