I have now tested the xorgwizard caused hanging. It happens to me frequently with my dual graphics integrated intel...and sometimes with ati radeon also when I switch to use it in BIOS.

Okay...it is not kernel dependent. I have tested with 3.8.7 and with 3.7.10. They all cause the same hanging after you use xorgwizard > probe, start X and exit to prompt again.
Luckily I have acpid listening powerbutton and for me it shuts down the computer. No need to hard shutdown.

Anyway exiting to prompt after using xorgwizard probe property is the clue.

It looks like that xorgwizard with X server: X.Org X Server 1.13.3 is not anymore compatible. There is for example command: Xorg -configure > /tmp/xorgprobe.txt 2>&1 which give error about screens when you execute it in the prompt.

I suppose that Xorgwizard creates somewhat defective xorg.conf file due to incompatibility. And yes....I can create really weird xorg.conf with xorgwizard.

It has several screens, monitors, devices listed, most of them useless.

I suppose that this kind of defective xorg.conf created by xorgwizard might cause problems.
And it happens with all my tested 2 other kernels. Compiling latest jwm-731 or disabling acpid....causes only that acpid not listening disables my powerbutton shutdown function and I had to hard shutdown. Jwm change to 574 or 731 didnt make any difference.

My conclusion....it is due to X.Org X Server 1.13.3 and xorgwizard incompatibility. But this is just preliminary evaluation of the problem...

I think that Barry Kauler should check this post....when his vacation is over....or anybody who understands more about Xorg - X server and xorgwizard.

By the way...3.7.10 kernel behaves nicely in my laptop. 3.8.X kernels does not like my acpi_call module anymore. If I switch off ati dual graphics discrete card ( I do that because it eat watts and warms the laptop even when it is not in use ), the suspend to ram does not wake up nicely. Sometimes it hangs. I cant cause that hanging with 3.7.10 kernel. It makes me thinking that I could use this version more....posting from 3.7.10 kernel Upup Raring now....Needs more test and usage and prolonged suspend to ram before I am sure...

in all the recent puppies, my eeepc boots right into Intel video driver. It's a bit different with upup raring, as you will see in the attached picture. On the left side is the first run applet that shows upup precise 3.8.3.1, and on the right side, the same applet showing upup raring. It does pick up intel video in the end, but it's not doing so in a "straight" manner. Not a big deal, just an illustration to your thoughts on xorg as probably being buggy.

Anikin. That is caused just because I forgot to remove Video Wizard. You cant use Video Wizard in my builds. Different kernel. And I cant load my compiled proprietary drivers to ibiblio...so....I have removed it. Now I forgot to do it manually. Should include it to the script.

first use :
Surf on the Web : wireless, eth0, youtube music and image : nothing to do, that's is perfect.
Planner now by default,
NEW : icon finder, good idea.
Added : xvidcap 1.1.7 for tutorials, pupsaveconfig to avoid useless saves.
A good classical distribution.
Desktop icons : please change a little bit, there are a lot !
Wallpaper : ringtail is a new one ? ok fine.
F2fs dual boot : good idea
Laptop : hibernate some people want it (not me)
Wakepup ; very useful because this program avoids working with CDs on old laptops. But when you have burnt it once, it's for all your life. Not necessary here ( in PPM it's enough) ?
Planner is shown twice (calculate and setup). Remove it from setup.
Xblindkeys : well !
Xvidcap missing.
Pls make fun in your Ubuntu's Puppies. . No ? in french we shall say 'un peu de fantaisie'

Me gusta, j'aime, i appreciate : aurora theme,

Ah ORCA ! want to try it with Puppy. 34MB hum...
And no missing dependancies, well ! thus, something new ...
It's for the fun. A new step to vocal management
I Tried Orca with Ubuntu 12.04 a week ago.

I have compiled mksquashfs and need your help with a couple of sfs/devx questions:

1) What compression do you use - gz or xz (specifically for devx)? If it's xz, what block size would be the best? And if I follow help, the command makes quite a lengthy line. How does exactly your mksquashfs command line look like?
2) I'm confused by default mksquashfs3 and mksquashfs4 and mksquashfs symlink - I have only one binary for that.
3) Do I understand correctly that gz is a thing of the past and has been deprecated? Do I need it at all in the tool?

Anikin. With these recent enough kernels there is choice to use xz compression which creates higher compression. With old computers the decompression takes longer time.
I think since 2.6.38 kernel there has been support for xz compression.

So....Barry Kauler uses with Wary gz compression, which decompresses faster in old comp.

I have used xz compression nowadays. It is fast enough with most comps which people try with my builds.

To resolve the issue I used the KDE SFS provided for the precise puppy, the first error about the mime types was removed (like it could now find the mime types) but the second error syill persisted. With or without the KDE SFS when I click OK on the error pop up windows Okular remain open on the desktop but when I want to open a pdf file it gives a massage that says sorry for the interuption but there seems to be a bug there you can report if you like or restart the app. If I restart the app again the same story and if not anyway Okular has been closed. Even once I produced a /%i folder and the second error wasn't removed.

Searching the web I saw people were adding the mime types manually to resolve the issue but the folder to which I should add the data is not available here or more probably I cannot find it, meanwhile that I don't know what to copy there if I could find it.

Can you help with this? I prefer not to use the KDE SFS as only need those two KDE apps not the desktop and its many little or large applications.

rasul. Install devx sfs and load it with sfs_load right click....for example.
Then execute in console: update-mime-database /usr/share/mime
And you get mime types binary data file updated.
I did launch okular in console....as I do launch every app...I do test. That gave me hint what was wrong.

Next thing. /usr/share/applications/kde4/okular.desktop
In the Exec row: just leave okular word there, like this:
Exec=okular

Launch okular 2 times in console. You will see that the error messages are gone. Also launching from the menu will work, when you run in console:fixmenus
and then restart jwm

Done.

Sidenote: I installed all the dependencies from the PPM, estimated installed size about 167 Mb. For universal document viewer. Auch.

Thanks don570. It has been fixed in my woof2 already. Barry Kauler has also fixed it in woof2 level also....so no problem with libtiff symlinks in next build. Waiting that Ubuntu Raring official is out. Should be soon. Then I create the next build with latest fixes. Xorg - xorgwizard problem still exists.

rasul. Install devx sfs and load it with sfs_load right click....for example.
Then execute in console: update-mime-database /usr/share/mime
And you get mime types binary data file updated.
I did launch okular in console....as I do launch every app...I do test. That gave me hint what was wrong.

Next thing. /usr/share/applications/kde4/okular.desktop
In the Exec row: just leave okular word there, like this:
Exec=okular

Launch okular 2 times in console. You will see that the error messages are gone. Also launching from the menu will work, when you run in console:fixmenus
and then restart jwm

Done.

Sidenote: I installed all the dependencies from the PPM, estimated installed size about 167 Mb. For universal document viewer. Auch.

Thanks a lot! That worked fine. Now I can edit not only my PDFs but also DJVUs! Seems there is no excuse left for me not to switch to raring completely

rasul. Thank of the feedback. About Virtualbox. I know nothing about it. But....it sounds like you will need kernel sources sfs also to be loaded...if the pet....or virtualbox environment inside it compiles kernel module driver for virtualbox on the fly....just guessing....I really know nothing about Virtualbox. Now more experienced Puppy users should step in and give help.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum