[K12OSN] introduction and PXES question

Diego Torres Milano diego at in3.com.ar
Thu Feb 10 20:54:50 UTC 2005

I'm glad to hear that PXES is helping you.
Have you built your own PXES images ? If so, video modes and monitor
definitions are in the corresponding page in pxesconfig druid.
Anyway, you can add command line parameters at the boot prompt or kernel
command line.
Like this:

boot: pxes xvm="1024x768" xh=31.5-58 xv=50-100

guessing that you are booting with pxelinux, your entry is named pxes,
you want 1024x768 and your monitor support those ranges.
You can also use Remote Configuration to set those parameters.
Just ask me if this doesn't help you.
On Thu, 2005-02-10 at 17:34, Eric Neiwert wrote:
> Diego
> Thank you for your response here to my previous inquiry. Your software has helped me set up a lab of thin client computers to do their testing at low cost allowing me to bring technology integration in the classroom to more students. 
> I have an additional question.
> When I use PXES to boot to the K12ltsp server using XDM it boots with a small screen resolution for the monitors. (in the 800X600 range).
> This is creating some problems for students reading the text and also some technical problems with a kiosk browser I am using. 
> How can I configure PXES to set the monitor resolution higher?
> Eric Neiwert
> 7th grade humanities
> Technology Coordinator
> Gordon Russell Middle School
> http://russell.gresham.k12.or.us
> Gresham-Barlow School District
> Gresham, OR
> diego at in3.com.ar on Wednesday, November 17, 2004 at 9:23 PM -0800 wrote:
> >PXES is a very flexible solution, as you may have discover.
> >Even, using the PREBUILT images, it is fully configurable (well, almost
> >:-)
> >
> >Short answer:
> >1) Be sure that the PREBUILT image is finding your Remote Configuration
> >server (TFTP). PREBUILT images are reading the remote configuration from
> >the TFTP server specified as tftp-server-name DHCP option. In
> >dhcpd.conf:
> >option tftp-server-name "your.tftp.server";
> >
> >2) In this TFTP server add a configuration file (i.e:
> >/tftpboot/pxes/config/default.conf):
> >
> >message -e '\ndefault.conf'
> >XDM_METHOD=query
> >XDM_SERVER_NAME=your.server.ip
> >
> >3) boot your thin clients with the PREBUILT image and XDM login will
> >appear.
> >
> >
> >I've found this message, just as a coincidence, following a referrer
> >URL.
> >The best place to post PXES questions is SF's mailing list:
> >pxes-devel at lists.sf.net
> >
> >There'are some nice PXES movies (live thin clients) at:
> >http://pxes.sf.net/movie-trailers.html
> >
> >Regards.
> >
> >> Greetings
> >> Having been a Macintosh administrator for the last 9 years of my professional career I am taking the plunge into using  Linux lab to solve some problems I have faced with our statewide testing we have here in Oregon.
> >> This year every students will test at least twice in front of a computer as all statewide testing is done using a computer and a network connection. Over the past two years this has taken the lab away from classroom integration and turned it over
> >to
> >> testing. 
> >> I needed a network solution that was inexpensive and flexible so that I can continue to teach language arts, science, math, and social studies using our computers. So I am piloting a lab for the district using the k12ltsp server.
> >> I have been working on establishing a lab of thin client machines using a mish mash of older computers that were being surplused out by our high school. They have a variety of network cards and monitors so making a boot floppy for each one was
> >going
> >> to be problematic.
> >> I have the server set up and it is working well. 
> >> 
> >> I also have been able to use the PXES boot CD for the client machines (a simple solution in that the CD image has most ethernet cards defined already) 
> >> The only problem is that the default boot method on the PXES image doesn't find the server and I have to choose XDM to get it to find and boot from the server. (I can't just boot it up and let it run but have to intervene in the boot up of each
> >> machine)
> >> Has anyone used the PXES image to boot from a CD for clients of the k12ltsp server? Has anyone been successful in getting either the default method of logging in with the pxes image to work with the server or customized the image to only boot
> >using
> >> XDM or some other successful boot method? I have been struggling to figure out how to customize the image even though the author has provided documentation, a configuration folder, and the iso boot image on his web site. 
> >> I may just revert to putting a boot partition on the hard drive of red hat and have it log in but would like to get this option to work for me.
> >> 
> >> Here is the web site where I got PXES from...
> >> http://pxes.sourceforge.net/
> >> A "how to" to configure the iso boot image...
> >> http://pxes.sourceforge.net/howtos/Creating_a_Custom_RDP_ISO_Image.pdf
> >> The downloads for the iso image and the config files.
> >> http://sourceforge.net/project/showfiles.php?group_id=45684&package_id=38453&release_id=258546
> >> 
> >> Eric Neiwert
> >> 7th grade humanities
> >> Technology Coordinator
> >> Gordon Russell Middle School
> >> http://russell.gresham.k12.or.us
> >> Gresham-Barlow School District
> >> Gresham, OR
> >-- 
> >Diego Torres Milano <diego at in3.com.ar>
> >IN3
> >
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/k12osn/attachments/20050210/d807fc30/attachment.sig>

More information about the K12OSN mailing list