Dpup Exprimo 5.X.15

[pemasu]

Sound started to work. I removed manually all udev-174.pet installed files and then installed udev_167p-167-patched_t2-i486.pet. I then did modprobe snd-hda-intel and voila, previously seqfaulted retrovol_tray launched. Sound works now. It was udev prob after all...!!!

[soundNICK]

pemasu - sorry to hear about your sound troubles... for me,
EVERYTHING is working in eXprimo5x9... one or two apps still to work
out, but it is s-ooooo solid... nothing breaks... none of my old pets
complain when installed. Everything an experienced user could ask
for, and I didnt even ask

If it wasnt so totally innovative and different I would recommend
it for the next puppy... but then, you already had finlander
named in your honor so congrats for that !

EDIT: after some further look at eXprimo I would say it is very
close to being user friendly... I say this with the following reservation...
because for me, it was the enlightenment default which caused the
most slow downs... why not ship it with JWM as default, and keep
e2 as alternative ? I really dont think e2 is useable as it is.


thanks again for building this distro !!

soundNICK

[pemasu]

I think that 5.X.9 comes with JWM as default. Because of some graphics driver incompatibilities I changed JWM as default, especially after new JWM version update.

[Béèm]

Indeed. 5.X.9 comes to the JWM desktop.
To have e17 wmswitcher can be used.

[Iguleder]

pemasu - I'm working on more build scripts and doing my first dpup build with the PETs I uploaded.

I'll do my best to destroy all bugs I find - this time I promise to update the repo

[soundNICK]

I think that 5.X.9 comes with JWM as default. Because of some graphics driver incompatibilities I changed JWM as default, especially after new JWM version update.

Pemasu and Beem... ah thanks for clearing this up for me... somehow I was
using 5x8... just checked file I had... dont know how I got it instead.

Well, good JWM is default in latest... downloading 5x9 now, thanks again

soundNICK

[soundNICK]

OK_ tried 5.x.9... finally got it to load... and now I have a question...
is the "SCSI" designation in this filename referring to equipment it works
best with ? (Exprimo-dpup-SCSI <-- like that).

I had Lots of problems with this version_ no more old pets are working...
freezes at boot screen where savefile i s selected to load... there I get
blinking cursor, but cant enter number... number doesnt register on
monitor, like number pad is disabled.

I did get 5.x.9 loaded, and made savefile... but, to fix boot problem had
to move all old xPrimo files to remote, then 5.x.9 savefile does boot, as it is
the only instance..

If it helps, I am using a desktop computer.... maybe 5.x.9 is special version for USB
or notebook or other ?

hope you can answer what the differences in versions is... different
kernel maybe ? So many changes for my use.

soundNICK

[pemasu]

Soundnick. 5X9 uses same kernel as 5X8. Only difference is that it uses newer woof and so initial booting initrd.gz probably has somewhat different init script. I know that Barry K has improved things...usually every woof has something altered.

SCSI means that during woof build scsi drivers are not dropped out. In fact I dropped out only old phone line modem firmwares and not needed stuff. Almost everything has been included. As always.

About difficulties. I have now installed 5X9 to quad core intel i5 laptop, dual core AMD Turion laptop, P4 desktop, I have used several savefiles for same install, I have several 5X versions in their own folders, I havent had any problems.

I use only grub4dos and grldr installed in first partition, I have used ext3 and ntfs as filesystem in that first partition, puplets are installed in ext4 or ext3 partition, in their own folders as frugal installation. Savefiles are inside those folders with according puppy.sfs, vmlinuz and initrd.gz. I havent had ever problem with booting with them. Usb booting with these newer kernels had problem. Barry K responded to our findings and fixed the init script, also compiling all the usb drivers as in, not as modules is solution also.

5X9 has been the release, with I have tested several different installations, I havent experienced any problems.

So...I really dont know what was the problem with your installation.
Anyway, we move forward all the time. I use the latest released woof, things will be improved, next release might be better....or worse.....lol.

[soundNICK]

Soundnick. 5X9 uses same kernel as 5X8. Only difference is that it uses newer woof and so initial booting initrd.gz probably has somewhat different init script. I know that Barry K has improved things...usually every woof has something altered.

SCSI means that during woof build scsi drivers are not dropped out. In fact I dropped out only old phone line modem firmwares and not needed stuff. Almost everything has been included. As always.

About difficulties. I have now installed 5X9 to quad core intel i5 laptop, dual core AMD Turion laptop, P4 desktop, I have used several savefiles for same install, I have several 5X versions in their own folders, I havent had any problems.

I use only grub4dos and grldr installed in first partition, I have used ext3 and ntfs as filesystem in that first partition, puplets are installed in ext4 or ext3 partition, in their own folders as frugal installation. Savefiles are inside those folders with according puppy.sfs, vmlinuz and initrd.gz. I havent had ever problem with booting with them. Usb booting with these newer kernels had problem. Barry K responded to our findings and fixed the init script, also compiling all the usb drivers as in, not as modules is solution also.

5X9 has been the release, with I have tested several different installations, I havent experienced any problems.

So...I really dont know what was the problem with your installation.
Anyway, we move forward all the time. I use the latest released woof, things will be improved, next release might be better....or worse.....lol.

Pemasu - ah great_ thanks for your excellent answer. I use these words...
kernel / so forth... not knowing what they are... but... top quality answer
from you tells me I must have asked something sensible(!). If it works for
you, cant ask any more... glad there is this solid distro [ 5.x.8 ] for me.

now I ask important question (hope you see next post)

regards

soundNICK

[soundNICK]

[quote=
...now I ask important question (hope you see /this/ post)

pemasu - just thought of this last night... you will like it maybe !

here is the idea... based on what I see with 5.x.8/9 desktops_ where
you can pick e2 /or/ JWM_ maybe you could add a function to
wmswitcher so its possible to add multiple instances of JWM... such as
JWM-1 / JWM-2 /... to pick from the list.
You could add as many as needed, and have completely different
desktops to work with.
I see this functionality now with my e2/JWM... that is, when I switch
from one to the other one, icons on first desktop no longer show up in
the other... so, this idea already works, except there is just one JWM
available.
To me, this would be great for any app... say, maybe you like Gimp...
and you want to keep 5 or 10 gimp only files on a working desktop... so...
you make JWM-2 with just a gimp icon, and, all these associated files,
and then could switch to that when you want to work on gimp.
Of course, it would work for any application.

it might be there is only one JWM config file or one e2 config file, and this
idea wouldnt actually work... you would know better.

soundNICK

[James C]

Since you are busy building some new kernels......I just put together a Slacko 5.30 with k-3.1.0.Out of the 8 or 9 different kernels I'm running in different Puppy installs this one has the lowest ram usage so far...even lower than Guy Dog.
Just to give you some more ideas.....

[stu90]

Since you are busy building some new kernels......I just put together a Slacko 5.30 with k-3.1.0.Out of the 8 or 9 different kernels I'm running in different Puppy installs this one has the lowest ram usage so far...even lower than Guy Dog.
Just to give you some more ideas.....

Nice James C!

[stu90]

[quote=
...now I ask important question (hope you see /this/ post)

pemasu - just thought of this last night... you will like it maybe !

here is the idea... based on what I see with 5.x.8/9 desktops_ where
you can pick e2 /or/ JWM_ maybe you could add a function to
wmswitcher so its possible to add multiple instances of JWM... such as
JWM-1 / JWM-2 /... to pick from the list.
You could add as many as needed, and have completely different
desktops to work with.
I see this functionality now with my e2/JWM... that is, when I switch
from one to the other one, icons on first desktop no longer show up in
the other... so, this idea already works, except there is just one JWM
available.
To me, this would be great for any app... say, maybe you like Gimp...
and you want to keep 5 or 10 gimp only files on a working desktop... so...
you make JWM-2 with just a gimp icon, and, all these associated files,
and then could switch to that when you want to work on gimp.
Of course, it would work for any application.

it might be there is only one JWM config file or one e2 config file, and this
idea wouldnt actually work... you would know better.

soundNICK

JWM is the windows managers - the desktop icons are controlled by Rox-filer the file manager, you can have multiple different desktop profiles as you describe as switch to them on the fly.

the Pinboard file for puppy is /root/Choices/ROX-Filer/PuppyPin this is the file that controls what icons are show on the desktop.

Im not aware of any GUI for pinboard switching? but you could copy the pinboard file then edit it do display the icons and launchers of your choosing - see more about using rox-filer piboard on this link:
http://rox.sourceforge.net/Manual/Manua ... #id2456497

[pemasu]

I am not using Pinboard tuning much. All the time changing your puplet version makes the tuning quite useless...
But there is in menu > Desktop > Desksetup Templates for Desktop icons.
It has some functionality how to tune your Pinboard.
In same menu location is also Backup my Desktop. I believe both takes backups of your existing Pinboard.
Both apps can be found as pets in this forum. I am sure that playing with them could lead even better functionality with them. 01mickos Deskset already has switching capabilities.

[pemasu]

James C. That sounds great. I played with 3.0.8 yesterday. Almost all is now functional. Intel driver still refuses to work for me. Acpi section also needs another inspection.
But 3.1.0 sounds great. I am taking easy space with 3.X kernel. More or less I test them. My next version update will probably be still 2.6.39.4. The woof still coughs with 3.X even though Barry has updated builddistro, it does not do the 3.X kernel job automatically. The puppy.sfs will be squashed with 3.3 version. I have needed to do manual tuning to get 4.2 version used.

[pemasu]

Breakthrough with 3.0.8 kernel compiled in Dpup. I downloaded wuxiandianzi 3.1.0 lupu 525 and it booted X with intel driver. So...the 3.X kernel is not the reason for my intel driver failure. Then I checked the i915.conf file and it has a long command:

Code: Select all

 install i915 /sbin/modprobe --ignore-install fbcon; [ -e /tmp/.i915_modeset_0 ] && /sbin/modprobe --ignore-install i915 modeset=0 $CMDLINE_OPTS || ( [ -e /tmp/.i915_nomodeset ] && /sbin/modprobe --ignore-install i915 $CMDLINE_OPTS || /sbin/modprobe --ignore-install i915 modeset=1 $CMDLINE_OPTS )

I copied that conf file to my woof build and bingo. I can boot to the X with intel driver loaded:

Code: Select all

Linux Kernel: 3.0.8
Operating System: Dpup Exprimo-5.X.10
Window Manager: jwm
X Server: Xorg
Driver used: intel

acpitool -s does not suspend anymore:

# acpitool -s
Function Do_Suspend : could not open file : /proc/acpi/sleep.
You must have write access to /proc/acpi/sleep to suspend your computer.

....there isnt sleep file what to call.....
....but echo mem > /sys/power/state does suspend and also waking up is ok.
I changed that to the sleep.sh script and voila....Fn + Zz button suspends to the ram and also wakes up ok.
......frisbee-tray works with new kernel. I am sure many are dissapointed to hear that. It did seqfault with my previous test but with my latest woof build it somehow works. I was already ready to leave Frisbee out. I have however tested sleep.sh script without calling Frisbee after resuming suspend by calling /usr/local/simple_network_setup/rc.network and that enables automatic wireless connection after resume. I wonder if there is anyone who would miss Frisbee if I leave it out ?
It seems I can update scripts to work without it.
Now I need to use this kernel longer to see if I can trace other bugs.
By the way wuxiandianzi kernel does not have ath5k.ko or ath9k.ko wireless modules included, so I had to use ethernet card to get his kernel build lupu525 to connect to the net. But that build already has shown me the way.

[peebee]

I wonder if there is anyone who would miss Frisbee if I leave it out ?

Me
Cheers
peebee

[Puppyt]

Me three

[stu90]

Pemasu - could always set frisbee manager to disabled as default ?

[pemasu]

Stu90. I suppose so...well...it is fine tuning anyway.
It looks like that arch linux is the only linux distro so far which has fixed acpitool. Acpitool seems to suffer this new kernel naming convention. 3.0.X seems to confuse it and it needs samekind patching to work correctly as in Puppies filemnt, bootmanager and sfs_load. 3.1 kernel should have fix for naming so that it should adress it self as 2.6.39.xx something. I didnt remember to test wuxiandianzi 3.1 kernel and acpitool.
Anyway archlinux acpitool-0.5.1-4 package works. I compiled acpitool from latest source but it wasnt 3.x kernel fixed !!!
It looks like acpitool is not actively supported anymore.

Damn it. Now with new acpitool Vattery seqfaults. Oh well.....