RE: NumLock and Background problem with PXES 1.0-15/16

(see inline comments)

On Wed, 2005-09-28 at 10:30, Sascha Juch wrote:
> Hi Diego, 
> I checked what you said... 
> 
> > -----Original Message-----
> > From: [email protected] 
> > [mailto:[email protected]] On Behalf Of 
> > Diego Torres Milano
> > Sent: Wednesday, September 28, 2005 12:10 AM
> > To: PXES devel
> > Subject: Re: [pxes-devel] NumLock and Background problem with 
> > PXES 1.0-15/16
> > 
> > On Tue, 2005-09-27 at 13:10, Sascha Juch wrote:
> > > Hi everybody,
> > > 
> > > after installing PXES 1.0-15/16 (base/pxesconfig) I have 
> > discovered a 
> > > few things which shouldn't happen (I think).
> > > 
> > > 1) When making the pxes-config package, a strange non deterministic 
> > > warning occures. If I just restart the make process things 
> > look fine.
> > > 
> > > 2) For the prebuild image the NumLock-Key keeps the state 
> > it has set 
> > > by the bios. So if it is turned on it stays turned on the 
> > whole time.
> > > 
> > > 3) If the X-Windows-System and the ICEWM is loaded it has the
> > > steelblue4 background loaded.
> > > 
> > > 
> > > To 1)
> > > I installed pxes packages from the source tgz-balls (In a 
> > second try I 
> > > tested it with the RPM-packages but the results from 2) and 
> > 3) are the 
> > > same).
> > > 
> > > Pxes-base installs fine without any complications. However 
> > > installation of pxes-config leaves me with the following:
> > > 
> > > -----------------SNIP--------------
> > > [root@devbabe pxes-1.0-install]# cd pxesconfig-1.0 [root@devbabe 
> > > pxesconfig-1.0]# perl Makefile.PL Checking for Gtk.. ok 
> > Checking for 
> > > Gnome.. ok Checking for Glade-Perl.. ok Checking if your kit is 
> > > complete...
> > > Use of uninitialized value in -d at 
> > /usr/lib/perl5/5.8.0/File/Find.pm 
> > > line 664.
> > > Warning: the following files are missing in your kit:
> > >         COPYING
> [lots of files commented out, sj]
> > >         pixmaps/xdm.png
> > >         pxes-tiny-48x48.xpm
> > >         pxesconfig
> > >         pxesconfig.desktop
> > >         pxesconfig.spec
> > > Please inform the author.
> > > Use of uninitialized value in -d at 
> > /usr/lib/perl5/5.8.0/File/Find.pm 
> > > line 664.
> > > Use of uninitialized value in -d at 
> > /usr/lib/perl5/5.8.0/File/Find.pm 
> > > line 664.
> > > Setting RELEASE = 6 at Makefile.PL line 134.
> > > Writing Makefile for Pxesconfig
> > > [root@devbabe pxesconfig-1.0]#
> > > [root@devbabe pxesconfig-1.0]# perl Makefile.PL Checking 
> > for Gtk.. ok 
> > > Checking for Gnome.. ok Checking for Glade-Perl.. ok Use of 
> > > uninitialized value in -d at /usr/lib/perl5/5.8.0/File/Find.pm line 
> > > 664.
> > > Use of uninitialized value in -d at 
> > /usr/lib/perl5/5.8.0/File/Find.pm 
> > > line 664.
> > > Setting RELEASE = 6 at Makefile.PL line 134.
> > > Writing Makefile for Pxesconfig
> > > [root@devbabe pxesconfig-1.0]#
> > > -----------------SNIP--------------
> > > 
> > > So if I start it the first time, I get a bunch of file missing 
> > > warnings while at the second start everything seems to be 
> > fine (except 
> > > the warnings from Find.pm). make, make test (which is 
> > sensless at the
> > > moment) and make install worked fine.
> > All of these are MakeMaker problems.
> > Why are you receiving this: Setting RELEASE = 6 at 
> > Makefile.PL line 134.
> > Is this from pxesconfig-1.0-16 ?
> 
> Yes it is:
> 			warn "Setting RELEASE = $1";
> is line 134 in the Makefile.PL
Yes, but my question is why your relese is set to 6 instead of 16 ?
This should be taken from pxesconfig (near line 60).
> 
> > > 
> > > To 2)
> > > I checked the prebuild images 1.0-15PB.squash on three 
> > different types 
> > > of hardware. All the times a local desktop popped up with the 
> > > NumLock-Key activated. However if I start pxesconfig and 
> > click through 
> > > the wizzard on my own (leaving only the local desktop 
> > active) as soon 
> > > as the PXE-loading phase is over, NumLock LED turns off.
> > PREBUILT configuration file is here:
> > http://pxes.sourceforge.net/wiki/index.php/PREBUILT_images#PXE
> > S_PREBUILT_configuration
> > 
> 
> I checked this. However, the above config file is not working with
> pxesconfig from PXES 1.0. Here's the output:
> 
> -----------SNIP--------------
> [root@devbabe pxes-1.0-install]# pxesconfig
> --configuration=/root/pxes-1.0-install/Pxes-PB.conf
> --initrd=/tftpboot/pxes/pxes-1.0.initrd
> --squashed=/tftpboot/pxes/pxes-1.0.squash --initialize --druid=no
> Initializing ram disk.
> Use of uninitialized value in -d at
> /usr/lib/perl5/site_perl/5.8.0/Pxesconfig/PxesconfigModel.pm line 2593.
> Use of uninitialized value in concatenation (.) or string at
> /usr/lib/perl5/site_perl/5.8.0/Pxesconfig/PxesconfigModel.pm line 2594.
> Fatal error:
> Cannot calculate modules size for directory: ''.
> [root@devbabe pxes-1.0-install]#
> [root@devbabe pxes-1.0-install]# pxesconfig
> --dumpconfiguration=test.config
> [root@devbabe pxes-1.0-install]# pxesconfig
> --configuration=/root/pxes-1.0-install/test.config
> --initrd=/tftpboot/pxes/pxes-1.0.initrd
> --squashed=/tftpboot/pxes/pxes-1.0.squash --initialize --druid=no
> Initializing ram disk.
> Initial ram disk has been initialized.
> Initial ram disk has been uncompressed.
> Initial ram disk has been mounted.
> Extra files have been copied.
> Configuration has been written.
> Inittab has been parsed.
> Squashed bootable image has been created
> (/tftpboot/pxes/pxes-1.0.squash).
> Initial ramdisk has been unmounted.
> Initial ramdisk has been compressed.
> Selected kernel has been copied.
> Configuration complete.
> Squashed ramdisk_size=6108 KB
> Initrd ramdisk_size=13313 KB
> [root@devbabe pxes-1.0-install]#
> -----------SNIP--------------
> 
This process seems OK
> only thing I found out ad hoc was that the splash image has a false name
> (pxes.lss instead of pxes2.lss). But changing this didn't help at all.
> Error is the same. 
> If I create a config file without specifying an image file, the build
> process works fine.
> 
> Unfortunately it is not possible to dump the configuration file out of a
> squashed image file (I tried, but the resulting one is the same as if I
> hadn't passed the --squashed parameter to pxesconfig). So I diffed the
> Pxes-PB.conf with the one I made by hand.
Check the values in /etc/pxes.conf after booting or mounting this squash
image.
> I didn't see any obvious differences - only in vars for ICEWM_ (which
> are not in the Pxes-PB.conf). So I deleted those lines and rebuilt the
> image. With no further success.
> 
> > > 
> > > I checked X_NUMLOCK in /var/run/pxes/env and it is set to '1'.
> > > 
> 
> same here: NumLock shortly blinks on and turns off immediately with a
> selfmade image. Again, I haven't changed anything from the default
> installation.
Try issuing 'xsetleds +num' manually.
> 
> 
> > > To 3)
> > > Same with the background: With the prebuild image a nice steelblue 
> > > background is set in the Window Manager but with the custom build 
> > > there is no background (only the default psychodelic X-Window 
> > > background). /var/run/pxes/env has X_ BACKGROUND_COLOR='steelblue4'
> > > set. I don't see anything suspecious under /var/log/icewm-session 
> > > (except complaining about verdana fonts the wm cannot load). But I 
> > > don't think this should lead to a missing background.
> > > 
> > > I don't think I missed any dependencies, as the tgz-balls would 
> > > complain otherwise. It is a freshly installed Red Hat 9 
> > system. I also 
> > > checked this on another Red Hat 9 system with the same effects.
> > > 
> > > Any ideas, comments, whatever? 
> > > 
> 
> For my "selfmade" image I edited the resulting dumped config and changed
> the ICEWM_BACKGROUND_IMAGE to /usr/share/backgrounds/pxes-bg-800x600.jpg
> as seen in the default config. But during runtime that was switched to
> pxes-bg-1280x1024.jpg although the display is only showing a 1024x768
> resolution...
> But I would prefere just to see the steelblue4 background.
> 
> Is it possible that you could publish the config file you did the
> pxes-1.0-15PB.squash image with? I would check with this. 
I will update the Wiki when I have some time, but configuration file is
almost the same as published, there's only minor changes and all related
with new variables.
> 
> Greetings,
> Sascha.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel
-- 
Diego Torres Milano <[email protected]>
PXES Universal Linux Thin Client
http://pxes.sf.net



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl