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

Hi Diego,

I found out why and when the background is missing: If you select in
pxesconfig a resolution of 1280x1024 _and_ 1024x768 _and_ the driver
does not support that (switching down to 1024x768) in /etc/init.d/rcS
the variable ICEWM_DESKTOP_BACKGROUND is set wrong (to
pxes-bg-1280x1024.jpg).

A simple fix is to add a symbolic link for the 1280x1024 resolution:
[root@devbabe /]# cd /opt/pxes/stock/extra/icewm/usr/share/backgrounds/
[root@devbabe backgrounds]# ln -s pxes-bg.jpg pxes-bg-1280x1024.jpg

(do the same for the 1600x1200 resolution for future clients ;o))

The NumLock-Problem however still exists: If I set xsetleds by hand in a
console the LED switches on when I switch to the console running IceWM;
if turning on is done in the script the LED turns of for half a second
and then turns off again.
Last test I did was with an=20

export DISPLAY=3D0:0
xsetleds +num=20

as last lines in the rcS script - without success.

I'm not quite sure why this is happening. As I had to install a Debian
machine today I installed PXES 1.0 on the freshly installed machine with
the same effect: NumLock is shortly set and then turns off when X
starts.
So I think it is not a typical case of PEBKAC. ;)

Greetings,
Sascha.

> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of=20
> Diego Torres Milano
> Sent: Wednesday, September 28, 2005 4:07 PM
> To: PXES devel
> Subject: RE: [pxes-devel] NumLock and Background problem with=20
> PXES 1.0-15/16
>=20
> (see inline comments)
>=20
> On Wed, 2005-09-28 at 10:30, Sascha Juch wrote:
> > Hi Diego,
> > I checked what you said...=20
> >=20
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]] On Behalf=20
> Of Diego=20
> > > Torres Milano
> > > Sent: Wednesday, September 28, 2005 12:10 AM
> > > To: PXES devel
> > > Subject: Re: [pxes-devel] NumLock and Background problem=20
> with PXES=20
> > > 1.0-15/16
> > >=20
> > > On Tue, 2005-09-27 at 13:10, Sascha Juch wrote:
> > > > Hi everybody,
> > > >=20
> > > > after installing PXES 1.0-15/16 (base/pxesconfig) I have
> > > discovered a
> > > > few things which shouldn't happen (I think).
> > > >=20
> > > > 1) When making the pxes-config package, a strange non=20
> > > > deterministic warning occures. If I just restart the=20
> make process=20
> > > > things
> > > look fine.
> > > >=20
> > > > 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.
> > > >=20
> > > > 3) If the X-Windows-System and the ICEWM is loaded it has the
> > > > steelblue4 background loaded.
> > > >=20
> > > >=20
> > > > 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).
> > > >=20
> > > > Pxes-base installs fine without any complications. However=20
> > > > installation of pxes-config leaves me with the following:
> > > >=20
> > > > -----------------SNIP--------------
> > > > [root@devbabe pxes-1.0-install]# cd pxesconfig-1.0=20
> [root@devbabe=20
> > > > pxesconfig-1.0]# perl Makefile.PL Checking for Gtk.. ok
> > > Checking for
> > > > Gnome.. ok Checking for Glade-Perl.. ok Checking if your kit is=20
> > > > 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 =3D 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=20
> > > > uninitialized value in -d at /usr/lib/perl5/5.8.0/File/Find.pm=20
> > > > line 664.
> > > > Use of uninitialized value in -d at
> > > /usr/lib/perl5/5.8.0/File/Find.pm
> > > > line 664.
> > > > Setting RELEASE =3D 6 at Makefile.PL line 134.
> > > > Writing Makefile for Pxesconfig
> > > > [root@devbabe pxesconfig-1.0]#
> > > > -----------------SNIP--------------
> > > >=20
> > > > So if I start it the first time, I get a bunch of file missing=20
> > > > 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 =3D 6 at=20
> Makefile.PL line=20
> > > 134.
> > > Is this from pxesconfig-1.0-16 ?
> >=20
> > Yes it is:
> > 			warn "Setting RELEASE =3D $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).
> >=20
> > > >=20
> > > > 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=20
> > > > 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
> > >=20
> >=20
> > I checked this. However, the above config file is not working with=20
> > pxesconfig from PXES 1.0. Here's the output:
> >=20
> > -----------SNIP--------------
> > [root@devbabe pxes-1.0-install]# pxesconfig=20
> > --configuration=3D/root/pxes-1.0-install/Pxes-PB.conf
> > --initrd=3D/tftpboot/pxes/pxes-1.0.initrd
> > --squashed=3D/tftpboot/pxes/pxes-1.0.squash --initialize =
--druid=3Dno=20
> > Initializing ram disk.
> > Use of uninitialized value in -d at
> >=20
> /usr/lib/perl5/site_perl/5.8.0/Pxesconfig/PxesconfigModel.pm=20
> line 2593.
> > Use of uninitialized value in concatenation (.) or string at=20
> >=20
> /usr/lib/perl5/site_perl/5.8.0/Pxesconfig/PxesconfigModel.pm=20
> line 2594.
> > Fatal error:
> > Cannot calculate modules size for directory: ''.
> > [root@devbabe pxes-1.0-install]#
> > [root@devbabe pxes-1.0-install]# pxesconfig=20
> > --dumpconfiguration=3Dtest.config [root@devbabe pxes-1.0-install]#=20
> > pxesconfig --configuration=3D/root/pxes-1.0-install/test.config
> > --initrd=3D/tftpboot/pxes/pxes-1.0.initrd
> > --squashed=3D/tftpboot/pxes/pxes-1.0.squash --initialize =
--druid=3Dno=20
> > 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=20
> > (/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=3D6108 KB
> > Initrd ramdisk_size=3D13313 KB
> > [root@devbabe pxes-1.0-install]#
> > -----------SNIP--------------
> >=20
> This process seems OK
> > only thing I found out ad hoc was that the splash image has a false=20
> > name (pxes.lss instead of pxes2.lss). But changing this=20
> didn't help at all.
> > Error is the same.=20
> > If I create a config file without specifying an image file,=20
> the build=20
> > process works fine.
> >=20
> > Unfortunately it is not possible to dump the configuration=20
> file out of=20
> > a squashed image file (I tried, but the resulting one is=20
> the same as=20
> > if I hadn't passed the --squashed parameter to pxesconfig). So I=20
> > diffed the Pxes-PB.conf with the one I made by hand.
> Check the values in /etc/pxes.conf after booting or mounting=20
> this squash image.
> > I didn't see any obvious differences - only in vars for=20
> ICEWM_ (which=20
> > are not in the Pxes-PB.conf). So I deleted those lines and=20
> rebuilt the=20
> > image. With no further success.
> >=20
> > > >=20
> > > > I checked X_NUMLOCK in /var/run/pxes/env and it is set to '1'.
> > > >=20
> >=20
> > same here: NumLock shortly blinks on and turns off=20
> immediately with a=20
> > selfmade image. Again, I haven't changed anything from the default=20
> > installation.
> Try issuing 'xsetleds +num' manually.
> >=20
> >=20
> > > > To 3)
> > > > Same with the background: With the prebuild image a=20
> nice steelblue=20
> > > > background is set in the Window Manager but with the=20
> custom build=20
> > > > there is no background (only the default psychodelic X-Window=20
> > > > background). /var/run/pxes/env has X_=20
> BACKGROUND_COLOR=3D'steelblue4'
> > > > set. I don't see anything suspecious under=20
> /var/log/icewm-session=20
> > > > (except complaining about verdana fonts the wm cannot=20
> load). But I=20
> > > > don't think this should lead to a missing background.
> > > >=20
> > > > I don't think I missed any dependencies, as the tgz-balls would=20
> > > > 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.
> > > >=20
> > > > Any ideas, comments, whatever?=20
> > > >=20
> >=20
> > For my "selfmade" image I edited the resulting dumped config and=20
> > changed the ICEWM_BACKGROUND_IMAGE to=20
> > /usr/share/backgrounds/pxes-bg-800x600.jpg
> > as seen in the default config. But during runtime that was=20
> switched to=20
> > pxes-bg-1280x1024.jpg although the display is only showing=20
> a 1024x768=20
> > resolution...
> > But I would prefere just to see the steelblue4 background.
> >=20
> > Is it possible that you could publish the config file you did the=20
> > pxes-1.0-15PB.squash image with? I would check with this.
> I will update the Wiki when I have some time, but=20
> configuration file is almost the same as published, there's=20
> only minor changes and all related with new variables.
> >=20
> > Greetings,
> > Sascha.
> >=20
> >=20
> >=20
> >=20
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,=20
> > 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
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,=20
> discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel
>=20


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