RE: RE: pxes-devel digest, Vol 1 #607 - 4 msgs
"C. Falconer" <[email protected]>
| Newsgroups | gmane.linux.pxes.devel |
|---|---|
| Organization | Avonside Girls' High School |
| Message-ID | <[email protected]> |
Squashfs is basically a compressed filesystem. It means that machines with less ram can be used as thin clients. If you've got 32 Mb in a machine, with squashfs you could get away with 16 or 20 (assuming no other changes) I've not used squashfs - my clients work with 32 and download time is not really major. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Graham.Pugh - SCH520 Sent: Tuesday, 11 May 2004 11:11 p.m. To: '[email protected]' Subject: [pxes-devel] RE: pxes-devel digest, Vol 1 #607 - 4 msgs Could anyone explain to me what the Squashed image is - what it does, if it's applicable to Etherboot images, and what advantages it would have if it does work, e.g. uses up less RAM? It's appeared as an option in PXES but am not quite sure what it does! Thanks, Graham Pugh PhD Web Developer Kings of Wessex Community School, Cheddar email: gpugh-AT-educ.somerset.gov uk web: www.grahampugh.co.uk -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 11 May 2004 03:41 To: [email protected] Subject: pxes-devel digest, Vol 1 #607 - 4 msgs Send pxes-devel mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/pxes-devel or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of pxes-devel digest..." Today's Topics: 1. CDRom drive not detected (Sebastien Dagnicourt) 2. Re: PXES 8 not working (but 5 did) (Chris) 3. RE: PXES 8 not working (but 5 did) (C. Falconer) 4. Re: PXES 8 not working (but 5 did) (Diego Torres Milano) --__--__-- Message: 1 To: [email protected] From: Sebastien Dagnicourt <[email protected]> Date: Mon, 10 May 2004 16:00:01 +0200 Subject: [pxes-devel] CDRom drive not detected Reply-To: [email protected] Message en plusieurs parties au format MIME --=_alternative 004CE792C1256E90_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Hello, New problem here (I searched but didn't find in the pxes forum). When booting Pxes don't see my cdrom drive. I run it on Gn/Gs and Gl Dell=20 (pentium I, II and MMX). The computer boot wihtout hard disk. Do I have to put some kernel parameters (may be idebus=3Dxx) ? Cordialement, S=E9bastien Dagnicourt. --=_alternative 004CE792C1256E90_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <br><font size=3D2 face=3D"sans-serif">Hello,</font> <br> <br><font size=3D2 face=3D"sans-serif">New problem here (I searched b= ut didn't find in the pxes forum).</font> <br> <br><font size=3D2 face=3D"sans-serif">When booting Pxes don't see my cdrom drive. I run it on Gn/Gs and Gl Dell (pentium I, II and MMX). The computer boot wihtout hard disk.</font> <br> <br><font size=3D2 face=3D"sans-serif">Do I have to put some kernel p= arameters (may be idebus=3Dxx) ?</font> <br> <br> <br><font size=3D2 face=3D"sans-serif">Cordialement,<br> <br> S=E9bastien Dagnicourt.<br> </font> --=_alternative 004CE792C1256E90_=-- --__--__-- Message: 2 From: Chris <[email protected]> To: [email protected] Subject: Re: [pxes-devel] PXES 8 not working (but 5 did) Date: Mon, 10 May 2004 12:34:45 -0400 Organization: NAIC Reply-To: [email protected] Diego, Yes, my reference to lilo was actually supposed to be PXELINUX... the config files look so similar... Sorry about that, my mistake. I have tried this with setting the ramdisk equal to the size of the squashed image, and larger. No dice. I have performed an md5sum on the squashed image, and it transfers intact. No where do I tell tftp to change to ascii. The problem remains: the prebuilt image will boot, but anything (and I have tried 100 combinations now...) I build with pxesconfig will not boot. It hangs at the little pxes fish logo (frame buffer) or "Uncompressing Linux... Ok," (no frame buffer). The machines in question have 64 Megs of ram and are celeron 333's. I have pushed the ramdisk up to 32 megs (way more than it should need) and it still does the same thing. It really seems like the problem is with pxesconfig. Any ideas? Thanks again, Chris On Thursday 06 May 2004 04:56 pm, Diego Torres Milano wrote: > > Hey, Diego. Thanks again for your assistance. > > > > On Thursday 06 May 2004 03:58 pm, Diego Torres Milano wrote: > >> > Diego, > >> > > >> > Yes, the prebuilt image works, but whenever I build one of my own > >> > >> using pxesconfig, it never works -- not matter how simple I make > >> the image. > >> > >> Can you explain "never works" ? > > > > from my first post: > > > > ============================================= > > > > > > have tested my tftp, and it seems to work, I can pull the kernel > > image just fine. I have increased by ramdrive size to 32M in lilo > > (for all > > options): > > Do you mean PXELINUX instead of LILO. A simmilar syntax but very > different boot loaders. > > > =====================<snip>========================== > > . > > . > > . > > label 1 > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > initrd=pxes-0.8. squash root=/dev/ram > > > > label pxes > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=32768 ro initrd=pxes-0.8.initrd root=/dev/ram > > > > label 2 > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > initrd=pxes-0.8. initrd root=/dev/ram > > > > label initrd > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > initrd=pxes-0.8. initrd root=/dev/ram > > ======================</snip>=========================== > > > > What happens is this: I get my graphical lilo screen, and > > everything looks good. I get a boot: prompt and all my lilo > > choices. If I choose the default, I get the framebuffer pxes icon > > at the top of the screen with a cursor under it, then it just > > hangs. > > If you're using a squashed image, the ramdisk_size is equal to the > size of thiis image. > i.e: > # ls -l pxes*.squash > -rw-r--r-- 1 root root 5644288 Mar 25 01:06 > /tftpboot/pxes/pxes-0.8.squash > > this implies > > ... ramdisk_size=5700 > > should work. > How much RAM does your clients have ? > Are you moving the image to another TFTP server ? Is it getting > corrupted in the transfer (ascii) ? Try making an md5sum before and > after. > > > If I choose the novesa option, then I get this: "Uncompressing > > Linux... Ok, " Then it just hangs. > > > > I have rebuild my image a dozen times now, and have it stripped way > > down with X3 now and no fun options. Nothing helps > > > > Can someone help me please? > > > > Thank you! ========================================================= > > > >> > Again, I am using pxes .8. I am using Gentoo linux on a dual > >> > PIII > >> > >> IBM Netfinity 4500R. > >> > >> > The client in question is a dell optiplex g1 with an ATI 3d Rage > >> > Pro > >> > >> card, 64 megs of ram and a celeron 333 cpu. > >> > >> Should work. > >> > >> > Also, I noticed that the autoconfig script for X works less > >> > >> effectively than did .5.1. .5.1 was able to configure the card > >> nicely at 1024x768 with a refersh of about 75hz -- .8 only gets it > >> at 800x600 at 60hz. > >> > >> I think the problem is in the monitor autodetection and > >> configuration. In PXES 0.8 default frequencies were changed to > >> Standard SVGA 800x600. You can select the frequencies that better > >> meet your monitor requirements. To test, just add the frequencies > >> in the kernel command line (these are only examples): ... > >> xh="50-70" xv="50-120" > > > > Thanks, I will have to give that a try.... > > > >> > Any help is sincerely appreciated. > >> > > >> > Thanks! > >> > > >> > Chris > >> > > >> > On Wednesday 05 May 2004 11:20 pm, Diego Torres Milano wrote: > >> >> Replace your image with the Pre-Built (PB) image and test it > >> >> again. > >> >> > >> >> > Hello. I am trying to upgrade our workplace from 0.5.1-35 to > >> >> > .8. > >> >> > > >> >> > I had good luck with 5.1, but I was interested in some of the > >> >> > new > >> >> > >> >> features. > >> >> > >> >> > I have tested my tftp, and it seems to work, I can pull the > >> > >> kernel > >> > >> >> image just fine. I have increased by ramdrive size to 32M in > >> >> lilo > >> >> > >> >> (for all options): > >> >> > =====================<snip>========================== > >> >> > . > >> >> > . > >> >> > . > >> >> > label 1 > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > >> >> > console=null initrd=pxes-0.8. squash root=/dev/ram > >> >> > > >> >> > label pxes > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=32768 ro initrd=pxes-0.8.initrd > >> > >> root=/dev/ram > >> > >> >> > label 2 > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > >> >> > console=null initrd=pxes-0.8. initrd root=/dev/ram > >> >> > > >> >> > label initrd > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > >> >> > console=null initrd=pxes-0.8. initrd root=/dev/ram > >> >> > ======================</snip>=========================== > >> >> > > >> >> > What happens is this: I get my graphical lilo screen, and > >> >> > >> >> everything looks good. I get a boot: prompt and all my lilo > >> > >> choices. If I choose the default, I get the framebuffer pxes icon > >> at the top of the screen with a cursor under it, then it just > >> hangs. > >> > >> >> > If I choose the novesa option, then I get this: "Uncompressing > >> >> > Linux... Ok, " Then it just hangs. > >> >> > > >> >> > I have rebuild my image a dozen times now, and have it > >> >> > stripped > >> > >> way > >> > >> >> down with X3 now and no fun options. Nothing helps > >> >> > >> >> > Can someone help me please? > >> >> > > >> >> > Thank you! > >> >> > > >> >> > Chris > >> >> > > >> >> > > >> >> > ------------------------------------------------------- > >> >> > This SF.Net email is sponsored by Sleepycat Software Learn > >> >> > developer strategies Cisco, Motorola, Ericsson & Lucent use > >> > >> to > >> > >> >> deliver higher performing products faster, at low TCO. > >> >> > >> >> > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > >> >> > _______________________________________________ > >> >> > pxes-devel mailing list [email protected] > >> >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > >> > > >> > ------------------------------------------------------- > >> > This SF.Net email is sponsored by Sleepycat Software Learn > >> > developer strategies Cisco, Motorola, Ericsson & Lucent use to > >> > >> deliver higher performing products faster, at low TCO. > >> > >> > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > >> > _______________________________________________ > >> > pxes-devel mailing list > >> > [email protected] > >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > > > > Cheers! > > > > > > Chris > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by Sleepycat Software > > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > > deliver higher performing products faster, at low TCO. > > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > > _______________________________________________ > > pxes-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/pxes-devel --__--__-- Message: 3 Date: Tue, 11 May 2004 08:42:46 +1200 From: "C. Falconer" <[email protected]> Subject: RE: [pxes-devel] PXES 8 not working (but 5 did) To: [email protected] Organization: Avonside Girls' High School Reply-To: [email protected] Just a stab in the dark here.... Try duplicating your ver 0.5 config as close as possible... So don't use squashfs (you have heaps of ram already) I only started with pxes 0.7, so I don't know much about what came = before. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chris Sent: Tuesday, 11 May 2004 4:35 a.m. To: [email protected] Subject: Re: [pxes-devel] PXES 8 not working (but 5 did) Diego, Yes, my reference to lilo was actually supposed to be PXELINUX... the = config files look so similar... Sorry about that, my mistake. I have tried this with setting the ramdisk equal to the size of the = squashed image, and larger. No dice. I have performed an md5sum on the squashed image, and it transfers = intact. No where do I tell tftp to change to ascii. The problem remains: the prebuilt image will boot, but anything (and I = have tried 100 combinations now...) I build with pxesconfig will not boot. = It=20 hangs at the little pxes fish logo (frame buffer) or "Uncompressing = Linux... Ok," (no frame buffer). The machines in question have 64 Megs of ram and are celeron 333's. I = have=20 pushed the ramdisk up to 32 megs (way more than it should need) and it = still does the same thing. It really seems like the problem is with pxesconfig. Any ideas? Thanks again, Chris On Thursday 06 May 2004 04:56 pm, Diego Torres Milano wrote: > > Hey, Diego. Thanks again for your assistance. > > > > On Thursday 06 May 2004 03:58 pm, Diego Torres Milano wrote: > >> > Diego, > >> > > >> > Yes, the prebuilt image works, but whenever I build one of my own > >> > >> using pxesconfig, it never works -- not matter how simple I make=20 > >> the image. > >> > >> Can you explain "never works" ? > > > > from my first post: > > > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > > > have tested my tftp, and it seems to work, I can pull the kernel=20 > > image just fine. I have increased by ramdrive size to 32M in > > lilo=20 (for all > > options): > > Do you mean PXELINUX instead of LILO. A simmilar syntax but very=20 > different boot loaders. > > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<snip>=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > . > > . > > . > > label 1 > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771 = console=3Dnull=20 > > initrd=3Dpxes-0.8. squash root=3D/dev/ram > > > > label pxes > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=3D32768 ro initrd=3Dpxes-0.8.initrd = root=3D/dev/ram > > > > label 2 > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771 = console=3Dnull=20 > > initrd=3Dpxes-0.8. initrd root=3D/dev/ram > > > > label initrd > > kernel vmlinuz-2.4.20-10pxes.i586 > > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771 = console=3Dnull=20 > > initrd=3Dpxes-0.8. initrd root=3D/dev/ram > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</snip>= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > > > > What happens is this: I get my graphical lilo screen, and=20 > > everything looks good. I get a boot: prompt and all my lilo=20 > > choices. If I choose the default, I get the framebuffer pxes > > icon=20 at the top of the screen with a cursor under it, then it > > just=20 hangs. > > If you're using a squashed image, the ramdisk_size is equal to the=20 > size of thiis image. > i.e: > # ls -l pxes*.squash > -rw-r--r-- 1 root root 5644288 Mar 25 01:06 > /tftpboot/pxes/pxes-0.8.squash > > this implies > > ... ramdisk_size=3D5700 > > should work. > How much RAM does your clients have ? > Are you moving the image to another TFTP server ? Is it getting=20 > corrupted in the transfer (ascii) ? Try making an md5sum before and=20 > after. > > > If I choose the novesa option, then I get this: "Uncompressing=20 > > Linux... Ok, " Then it just hangs. > > > > I have rebuild my image a dozen times now, and have it stripped > > way=20 down with X3 now and no fun options. Nothing helps > > > > Can someone help me please? > > > > Thank you! = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D > > > >> > Again, I am using pxes .8. I am using Gentoo linux on a dual=20 > >> > PIII > >> > >> IBM Netfinity 4500R. > >> > >> > The client in question is a dell optiplex g1 with an ATI 3d > >> > Rage=20 Pro > >> > >> card, 64 megs of ram and a celeron 333 cpu. > >> > >> Should work. > >> > >> > Also, I noticed that the autoconfig script for X works less > >> > >> effectively than did .5.1. .5.1 was able to configure the card=20 > >> nicely at 1024x768 with a refersh of about 75hz -- .8 only gets it > >> = > >> at 800x600 at 60hz. > >> > >> I think the problem is in the monitor autodetection and=20 > >> configuration. In PXES 0.8 default frequencies were changed to=20 > >> Standard SVGA 800x600. You can select the frequencies that > >> better=20 meet your monitor requirements. To test, just add the > >> frequencies=20 in the kernel command line (these are only > >> examples): ...=20 xh=3D"50-70" xv=3D"50-120" > > > > Thanks, I will have to give that a try.... > > > >> > Any help is sincerely appreciated. > >> > > >> > Thanks! > >> > > >> > Chris > >> > > >> > On Wednesday 05 May 2004 11:20 pm, Diego Torres Milano wrote: > >> >> Replace your image with the Pre-Built (PB) image and test it=20 > >> >> again. > >> >> > >> >> > Hello. I am trying to upgrade our workplace from 0.5.1-35 > >> >> > to=20 .8. > >> >> > > >> >> > I had good luck with 5.1, but I was interested in some of > >> >> > the=20 new > >> >> > >> >> features. > >> >> > >> >> > I have tested my tftp, and it seems to work, I can pull the > >> > >> kernel > >> > >> >> image just fine. I have increased by ramdrive size to 32M > >> >> in=20 lilo > >> >> > >> >> (for all options): > >> >> > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<snip>=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> >> > . > >> >> > . > >> >> > . > >> >> > label 1 > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771=20 > >> >> > console=3Dnull initrd=3Dpxes-0.8. squash root=3D/dev/ram > >> >> > > >> >> > label pxes > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=3D32768 ro initrd=3Dpxes-0.8.initrd > >> > >> root=3D/dev/ram > >> > >> >> > label 2 > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771=20 > >> >> > console=3Dnull initrd=3Dpxes-0.8. initrd root=3D/dev/ram > >> >> > > >> >> > label initrd > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > >> >> > append ramdisk_size=3D32768 ro video=3Dvesa vga=3D771=20 > >> >> > console=3Dnull initrd=3Dpxes-0.8. initrd root=3D/dev/ram = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</snip>= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D > >> >> > > >> >> > What happens is this: I get my graphical lilo screen, and > >> >> > >> >> everything looks good. I get a boot: prompt and all my lilo > >> > >> choices. If I choose the default, I get the framebuffer pxes icon > >> = > >> at the top of the screen with a cursor under it, then it just=20 > >> hangs. > >> > >> >> > If I choose the novesa option, then I get this: "Uncompressing > >> >> > = > >> >> > Linux... Ok, " Then it just hangs. > >> >> > > >> >> > I have rebuild my image a dozen times now, and have it=20 > >> >> > stripped > >> > >> way > >> > >> >> down with X3 now and no fun options. Nothing helps > >> >> > >> >> > Can someone help me please? > >> >> > > >> >> > Thank you! > >> >> > > >> >> > Chris > >> >> > > >> >> > > >> >> > ------------------------------------------------------- > >> >> > This SF.Net email is sponsored by Sleepycat Software Learn=20 > >> >> > developer strategies Cisco, Motorola, Ericsson & Lucent use > >> > >> to > >> > >> >> deliver higher performing products faster, at low TCO. > >> >> > >> >> > http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3 > >> >> > _______________________________________________ > >> >> > pxes-devel mailing list [email protected] > >> >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > >> > > >> > ------------------------------------------------------- > >> > This SF.Net email is sponsored by Sleepycat Software Learn=20 > >> > developer strategies Cisco, Motorola, Ericsson & Lucent use to > >> > >> deliver higher performing products faster, at low TCO. > >> > >> > http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3 > >> > _______________________________________________ > >> > pxes-devel mailing list [email protected]=20 > >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > > > > Cheers! > > > > > > Chris > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by Sleepycat Software > > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > > = > > deliver higher performing products faster, at low TCO.=20 > > http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3 > > _______________________________________________ > > pxes-devel mailing list > > [email protected]=20 > > https://lists.sourceforge.net/lists/listinfo/pxes-devel ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to = deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=3Dosdnemail3 _______________________________________________ pxes-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pxes-devel --__--__-- Message: 4 Subject: Re: [pxes-devel] PXES 8 not working (but 5 did) From: Diego Torres Milano <[email protected]> To: [email protected] Organization: IN3 Date: Mon, 10 May 2004 23:41:10 -0300 Reply-To: [email protected] On Mon, 2004-05-10 at 13:34, Chris wrote: > Diego, > > Yes, my reference to lilo was actually supposed to be PXELINUX... the > config > files look so similar... Sorry about that, my mistake. OK > > I have tried this with setting the ramdisk equal to the size of the > squashed > image, and larger. No dice. > > I have performed an md5sum on the squashed image, and it transfers > intact. > > No where do I tell tftp to change to ascii. > > The problem remains: the prebuilt image will boot, but anything (and > I have > tried 100 combinations now...) I build with pxesconfig will not boot. It > hangs at the little pxes fish logo (frame buffer) or "Uncompressing Linux... > Ok," (no frame buffer). Try the initrd image instead. > > The machines in question have 64 Megs of ram and are celeron 333's. I > have > pushed the ramdisk up to 32 megs (way more than it should need) and it still > does the same thing. > > It really seems like the problem is with pxesconfig. Run it from the command line and see if it outputs any message. > > Any ideas? > > Thanks again, > > Chris > > > On Thursday 06 May 2004 04:56 pm, Diego Torres Milano wrote: > > > Hey, Diego. Thanks again for your assistance. > > > > > > On Thursday 06 May 2004 03:58 pm, Diego Torres Milano wrote: > > >> > Diego, > > >> > > > >> > Yes, the prebuilt image works, but whenever I build one of my > > >> > own > > >> > > >> using pxesconfig, it never works -- not matter how simple I make > > >> the image. > > >> > > >> Can you explain "never works" ? > > > > > > from my first post: > > > > > > ============================================= > > > > > > > > > have tested my tftp, and it seems to work, I can pull the kernel > > > image just fine. I have increased by ramdrive size to 32M in lilo > > > (for all > > > options): > > > > Do you mean PXELINUX instead of LILO. A simmilar syntax but very > > different boot loaders. > > > > > =====================<snip>========================== > > > . > > > . > > > . > > > label 1 > > > kernel vmlinuz-2.4.20-10pxes.i586 > > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > > initrd=pxes-0.8. squash root=/dev/ram > > > > > > label pxes > > > kernel vmlinuz-2.4.20-10pxes.i586 > > > append ramdisk_size=32768 ro initrd=pxes-0.8.initrd > > > root=/dev/ram > > > > > > label 2 > > > kernel vmlinuz-2.4.20-10pxes.i586 > > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > > initrd=pxes-0.8. initrd root=/dev/ram > > > > > > label initrd > > > kernel vmlinuz-2.4.20-10pxes.i586 > > > append ramdisk_size=32768 ro video=vesa vga=771 console=null > > > initrd=pxes-0.8. initrd root=/dev/ram > > > ======================</snip>=========================== > > > > > > What happens is this: I get my graphical lilo screen, and > > > everything looks good. I get a boot: prompt and all my lilo > > > choices. If I choose the default, I get the framebuffer pxes > > > icon at the top of the screen with a cursor under it, then it > > > just hangs. > > > > If you're using a squashed image, the ramdisk_size is equal to the > > size of thiis image. > > i.e: > > # ls -l pxes*.squash > > -rw-r--r-- 1 root root 5644288 Mar 25 01:06 > > /tftpboot/pxes/pxes-0.8.squash > > > > this implies > > > > ... ramdisk_size=5700 > > > > should work. > > How much RAM does your clients have ? > > Are you moving the image to another TFTP server ? Is it getting > > corrupted in the transfer (ascii) ? Try making an md5sum before and > > after. > > > > > If I choose the novesa option, then I get this: "Uncompressing > > > Linux... Ok, " Then it just hangs. > > > > > > I have rebuild my image a dozen times now, and have it stripped > > > way down with X3 now and no fun options. Nothing helps > > > > > > Can someone help me please? > > > > > > Thank you! > > > ========================================================= > > > > > >> > Again, I am using pxes .8. I am using Gentoo linux on a dual > > >> > PIII > > >> > > >> IBM Netfinity 4500R. > > >> > > >> > The client in question is a dell optiplex g1 with an ATI 3d > > >> > Rage Pro > > >> > > >> card, 64 megs of ram and a celeron 333 cpu. > > >> > > >> Should work. > > >> > > >> > Also, I noticed that the autoconfig script for X works less > > >> > > >> effectively than did .5.1. .5.1 was able to configure the card > > >> nicely at 1024x768 with a refersh of about 75hz -- .8 only gets > > >> it at 800x600 at 60hz. > > >> > > >> I think the problem is in the monitor autodetection and > > >> configuration. In PXES 0.8 default frequencies were changed to > > >> Standard SVGA 800x600. You can select the frequencies that better > > >> meet your monitor requirements. To test, just add the frequencies > > >> in the kernel command line (these are only examples): ... > > >> xh="50-70" xv="50-120" > > > > > > Thanks, I will have to give that a try.... > > > > > >> > Any help is sincerely appreciated. > > >> > > > >> > Thanks! > > >> > > > >> > Chris > > >> > > > >> > On Wednesday 05 May 2004 11:20 pm, Diego Torres Milano wrote: > > >> >> Replace your image with the Pre-Built (PB) image and test it > > >> >> again. > > >> >> > > >> >> > Hello. I am trying to upgrade our workplace from 0.5.1-35 > > >> >> > to .8. > > >> >> > > > >> >> > I had good luck with 5.1, but I was interested in some of > > >> >> > the new > > >> >> > > >> >> features. > > >> >> > > >> >> > I have tested my tftp, and it seems to work, I can pull the > > >> > > >> kernel > > >> > > >> >> image just fine. I have increased by ramdrive size to 32M in > > >> >> lilo > > >> >> > > >> >> (for all options): > > >> >> > =====================<snip>========================== > > >> >> > . > > >> >> > . > > >> >> > . > > >> >> > label 1 > > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > > >> >> > console=null initrd=pxes-0.8. squash root=/dev/ram > > >> >> > > > >> >> > label pxes > > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > > >> >> > append ramdisk_size=32768 ro initrd=pxes-0.8.initrd > > >> > > >> root=/dev/ram > > >> > > >> >> > label 2 > > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > > >> >> > console=null initrd=pxes-0.8. initrd root=/dev/ram > > >> >> > > > >> >> > label initrd > > >> >> > kernel vmlinuz-2.4.20-10pxes.i586 > > >> >> > append ramdisk_size=32768 ro video=vesa vga=771 > > >> >> > console=null initrd=pxes-0.8. initrd root=/dev/ram > > >> >> > ======================</snip>=========================== > > >> >> > > > >> >> > What happens is this: I get my graphical lilo screen, and > > >> >> > > >> >> everything looks good. I get a boot: prompt and all my lilo > > >> > > >> choices. If I choose the default, I get the framebuffer pxes > > >> icon at the top of the screen with a cursor under it, then it > > >> just hangs. > > >> > > >> >> > If I choose the novesa option, then I get this: > > >> >> > "Uncompressing Linux... Ok, " Then it just hangs. > > >> >> > > > >> >> > I have rebuild my image a dozen times now, and have it > > >> >> > stripped > > >> > > >> way > > >> > > >> >> down with X3 now and no fun options. Nothing helps > > >> >> > > >> >> > Can someone help me please? > > >> >> > > > >> >> > Thank you! > > >> >> > > > >> >> > Chris > > >> >> > > > >> >> > > > >> >> > ------------------------------------------------------- > > >> >> > This SF.Net email is sponsored by Sleepycat Software Learn > > >> >> > developer strategies Cisco, Motorola, Ericsson & Lucent use > > >> > > >> to > > >> > > >> >> deliver higher performing products faster, at low TCO. > > >> >> > > >> >> > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > > >> >> > _______________________________________________ > > >> >> > pxes-devel mailing list [email protected] > > >> >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > > >> > > > >> > ------------------------------------------------------- > > >> > This SF.Net email is sponsored by Sleepycat Software Learn > > >> > developer strategies Cisco, Motorola, Ericsson & Lucent use to > > >> > > >> deliver higher performing products faster, at low TCO. > > >> > > >> > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > > >> > _______________________________________________ > > >> > pxes-devel mailing list [email protected] > > >> > https://lists.sourceforge.net/lists/listinfo/pxes-devel > > > > > > Cheers! > > > > > > > > > Chris > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by Sleepycat Software Learn > > > developer strategies Cisco, Motorola, Ericsson & Lucent use to > > > deliver higher performing products faster, at low TCO. > > > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > > > _______________________________________________ > > > pxes-devel mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/pxes-devel > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > _______________________________________________ > pxes-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/pxes-devel --__--__-- _______________________________________________ pxes-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pxes-devel End of pxes-devel Digest This communication is intended solely for the person (s) or organisation to whom it is addressed. It may contain privileged and confidential information and if you are not the intended recipient (s), you must not copy, distribute or take any action in reliance on it. If you have received this e-mail in error please notify the sender and copy the message to [email protected] ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ pxes-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pxes-devel ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3