I tried dpup482b5 on my old machine, which normally needs a retro kernel, because some modern kernels are patched to still work on old m/c.
Well, it worked beautifully- I really like the clean desktop option. BUT when I clicked on reboot, intending to create the pupsave etc, the computer crashed, with a multicoloured line about 20mm wide across the screen.
Oh dear! I do need the retro after all.

Still, it works fine on the Acer Aspire One.... (not tried camera and other netbook gadgets that I don't know about).

If you can cast your mind back to the dpup that does have a retro kernel (477b1), and which won't boot up a second time (it gets a kernel panic) was there a quick fix that I could put in?

@Guy- good on yer, mate! (Do they still say that in Australia? I worked there for a couple of months thirty years ago- when they bought me a tube of Touhy's (?) they said "If you're feeling homesick, stick it under yer armpit for a while".) A good mob to work with.

A couple of reports of what look like bugs that I wanted to put up for consideration:

1. My bug regarding no saves in /etc is continuing, on every save file I use. It seems unrelated to what is installed and what is not, to the sfs files that are loaded, etc. (perhaps I could be wrong on this, but have tested almost every conceivable configuration) and just seems to start happening after a certain number of boots. The save files are fsck'ed on every reboot and dosfsck reports no problems with the underlying vfat file system excepting differences between the boot sector and its backup. It does not seem to be a bad block related problem because it happens in all save files. I have finally given up on trying to trace this and have started using workarounds instead (setup scripts in /root/Startup to copy over all the fiels that are lost, etc.) but things are still not working properly.

2. My screen goes blank when using intel video driver problem has started reoccuring in beta5. When we discussed it at that post, gposil, it had seemed to be a fluxbox thing. But now the identical problem has occurred when running icewm, jwm and Enlightenment DR17. Will post an xerrs.log as soon as I remmber to save it properly . It happens fairly frequently.

3. The wifi drivers for the Eee PC 701SD - something weird is going on with mine. The standard one (ath5k) in dpup was running ok at first and then suddenly developed severe problems, not connecting at all most of the time (would connect perhaps once out of ten times) and then, once connected, the connection would be very erratic and slow. So I switched to this driver compiled by tempestuous for this kernel and there was a great improvement. But then later this driver as well started showing similar problems, though not as bad as the ath5k one, and now I'm reduced to wired internet (which works fine ). The adapter is identiifed as an Atheros AR5001.

Should note that I have not had the latter two problems ever in 4.1.2 or 4.3.1, though as mentioned earlier the first problem did start occurring in 4.3.1.

Possibly these problems could be fixed with more up-to-date intel and atheros drivers? Just a shot in the dark...

Incidentally have finally managed to compile Enlightenment DR17 in dpup, will post shortly.

Wow! Thanks shankar, it's not just me! I'm having exactly the same problem with wifi connection, in dpup and in the old iscraig acerpup, based on 4.1 I think.
I been trying over and over to get both working. The acerpup has been working for some time on my Acer Aspire One, but won't work now, and in dpup I have one savefile that does work, and another that won't. It's always the "association" stage that fails, whatever that means.
EDIT: dpup also on AA1.

Ok, finally managed to compile Enlightenment DR17 for dpup beta 5. You will also need Lua, so that dotpet is also attached. This is compiled from the December 2nd snapshots (svn code refused to compile). These will not work in normal Puppy. You can find both at:

NB:Turns out you will also need to have the devx sfs loaded, or otherwise install libiconv - get it from the repository here.

This will switch off ROX, which otherwise will prevent you from seeing the E17 desktop.

Then, to start E17, exit to prompt from X and do this:

Code:

xwin enlightenment_start

I have been using E17 since January 2007 and nowadays can hardly work without it. It's space-heavy, but incredibly beautiful and very fast even on old machines. Screenshot attached. All those bits - the clock, the systray, and the iconbar (except freememapplet) are set to auto-hide, and I bring them out when I need with a keystroke. You may also want to turn off wbar (set /var/wbon to false) as E17's built in ibar module is better integrated and prettier.

This version is more up to date than the debian package available at package.enlightenment.org (which dates from the first week of August), and has a few new bells and whistles. You can get themes from http://exchange.enlightenment.org.

PS: as I am not a fan of menus, I have not bothered to fix the application menus (which are a little wonky) and the non-functional shutdown menu. Sorry no time . To get to applications I use the "Run Everything" dialog from the main menu, which is new and pretty cool, try it (you can also bind it to a key combination, which is what I've done). To shutdown I just Ctrl-Alt-Backspace and type poweroff.

PS-squared: can someone add in this note to the dotpet? I don't know how to do that - i.e. create a readme that will show up on install - so that people will know they have to make these changes before running E17.Last edited by shankargopal on Sat 26 Dec 2009, 00:40; edited 3 times in total

2. My screen goes blank when using intel video driver problem has started reoccuring in beta5. When we discussed it at that post, gposil, it had seemed to be a fluxbox thing. But now the identical problem has occurred when running icewm, jwm and Enlightenment DR17. Will post an xerrs.log as soon as I remmber to save it properly . It happens fairly frequently.

Ok, it just happened again, and this time managed to save the xerrs.log. I was running in E17 at the time so there is a lot of Enlightenment stuff in xerrs.log, but the key error appears to be the one about the "Ring" etc. This error, on a cursory visual inspection, was present in xerrs.log when I had this problem when running icewm as well.

Have attached xerrs.log and xorg.conf, both renamed to ".gz" to allow me to attach them (just rename them, not compressed).

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