To use them to make and install a driver, need the devx file and kernel source file.

Where can I find the kernel source file for the Lupusuper versions?

I assume the Lupu 528 devx file will work for any version of Lupu?_________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

jeff757,
Thanks for posting the links to the source SFS files. I found that for the smokey01 links, I need to also click on the "ISO" icon ("puppy distributions") to get to the page containing the actual links to the files.

As for devx, I am assuming the lupu devx should work for all lupusuper/sulu versions, but have not tried using it. I also assume it is best to compile in the target version, to avoid possible compiler complaints.

Although I am familiar with compiling drivers, I have not mastered compiling applications, with all of their possible dependencies. I am relying on those of you comfortable doing that, to provide the additions to lupu/sulu. (I will provide a link for you to upload to the lupu 5.2.8.6 download site.)

On another subject, I have placed in the third posting of the "5.2.8.6" thread a link to packages constituting gnome-player-1.0.7. I find that "1.0.7" avoids a "null pointer" error that kills gnome-mplayer 1.0.4. It does log some debug-type messages, but at least does the job. I would appreciate some feedback on "1.0.7", as I plan to add it to the lupus/sulus the next time I upload them.
http://www.murga-linux.com/puppy/viewtopic.php?p=739520#739520

BTW, I am adding Barry's "gnomemplayershell" logic to lupu, modified for lupu's internal structure and done in a different way. It defaults to video output driver "x11" for graphics driver "vesa" and "xv" for all others, overridden, of course, by whatever the user has already selected (in Edit > Preferences). This avoids the need to instruct users to use "x11" if "xv" does not work. The logic also suppresses the X screensaver during mplayer operation; but I am not sure how to test that. I expect it should prevent any screen saver from interrupting mplayer sessions.

Although "20131221" may be the final "5.2.8.6", please alert me ASAP to anything I should attend to, to fix right away if I can.
Richard

Here is a bug report about Chrome crashes on 5.2.8.6
http://www.murga-linux.com/puppy/viewtopic.php?t=91059_________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

Lucid 5.2.8.6 makes another happy Puppy user! http://www.murga-linux.com/puppy/viewtopic.php?p=747261#747261_________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

The links to files, posted earlier, by me and jeff757 seem to be good for lupusuper1 k3.0.25.

The Add-on (devx) for all versions of Lucid 528.005 file seemed to have all that was needed for make program._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

Yes, indeed. I'm happy with rerwin's masterful remaster. Since this afternoon, I've done full hard drive installs on two machines and they are both apparently happy. I'm really impressed with Lucid, especially since getting my hands on 5.2.8.6.

Quick manual frugal install of lupusuper4 -k-3.9.9.... looking good. Installed Chromium 25 (I already had the pet and I know the newer versions don't work on Lucid) and a few other insignificant pets .....all working fine.

I am moving the "finish line" a bit, to allow lupusuper2, which uses the precise pup 5.7.1 kernel, 3.2.48, to become a fully operational upgrade for lucid pup 5.2.8.6.

The showstoppers, so far, have been the non-functioning QuickPet and proprietary video graphics drivers. I have upgraded QuickPet to support all of the offered nVidia drivers and have built the drivers for lupusuper2 with shinobar's "miraculous" 'getnvidia' package, as both pet packages and SFS files.

Use whichever form suits you. Note that they are initially for only lupusuper2/sulu002.

The updated QuickPet Drivers 'test your graphics card' button should tell you which driver you need. You can then download only that driver.

Please report your results here, so I can be confident they will work in the "final" release. Thanks for any help.

BTW, shinobar's getnvidia will be added to lupu 5.2.8.6, making it simple for anyone to create nvidia driver packages. It is very easy to use.
Richard

EDIT: The same set of drivers for lupu itself, for kernel 2.6.33.2, has been uploaded to the download site. The sets are now in separate subdirectories for each version of lupu/sulu, to make them easier to find.

EDIT: The set of nvidia drivers for lupusuper4, for kernel 3.9.9, are now uploaded, joining the others.

Well... First... I just had to do it, Check Out The WiFi... since in the past with most other puppy programs it has been nothing short of a headache for my- Linksys USB rt2800usb system to get configured. In fact so far only Wheezy puppy has setup and worked without any problems. I was already automatically connected to 'eth0' on starting the new puppy so that wasn't an issue. OK here we go... Shut down and created a SAVE file like asked at the FIRST dialog box on initial fire-up. After start-up again, pulled the Ethernet cable out of the modem and went for WiFi setup using 'frisbee' setup. Frisbee searched and found my WiFi configuration right off the bat. I said 'connect' and the small dialog window appeared asking for my encryption key password. Typed that in and Bingo!!! WiFi was connected and singing like a bird to my system... 'Nice job on that rerwin!'

Next went for Google Earth as that has always been a little tricky finding the correct version that works the best. I opted for the one in the setup menu, installed it. Went to PPM installed the 'xorg high-graphics' package (Google Earth Will Not Run Without It In This Puppy) and shortly I was looking at a picture of the earth from space. Nice... but in order to use the search function in Google Earth, you have to go into-
/opt/google/earth/free and 'rename or delete' the file named- libcurl.so.4 (that should be removed in next build!)

Installed Firefox-24 from PPM... nice that it's on automatic-update, installed '26 update' after clicking on the 'about Firefox' heading in the browser toolbar... nice!

So far, performance has been very nice... the 3.9.9 Kernel is very responsive in this build and works nice on theis old P-4 box... it's as fast as one would want a distro to be I believe!'

It would be interesting to see how a 3.12.x Kernel would do in this puppy.... 'Eh... rerwin?'

Keep up the good work... an old puppy has been given new life to run with the best of the pack!

>>>---Indian------>

EDIT: Before I forget... one issue noted, the 'Weather' module keeps dropping from the desktop after an Internet session etc., Using 2.4 Pwidgets!_________________Cloud Computing For Every Puppy (a .pet)
http://murga-linux.com/puppy/viewtopic.php?t=69192

Nice... but in order to use the search function in Google Earth, you have to go into-
/opt/google/earth/free and 'rename or delete' the file named- libcurl.so.4 (that should be removed in next build!)

Can you tell me more about this? I need to know the reasoning behind the removal, in case it would impact something else.

Quote:

It would be interesting to see how a 3.12.x Kernel would do in this puppy.... 'Eh... rerwin?'

To try that, I need to know of a puppy distro that already uses that kernel. The kernel-switch process starts with an existing puppy to supply the kernel pieces.

Quote:

EDIT: Before I forget... one issue noted, the 'Weather' module keeps dropping from the desktop after an Internet session etc., Using 2.4 Pwidgets!

I am very nervous about pwidgets, because it takes over the puppy internals and is impossible to remove (if you change your mind about using it). If there is someone maintaining pwidgets, they should be given some logs to provide evidence. A pdiag file would be good, but the main logs to provide are: /tmp/xerrs.log, /var/log.messages and the output of the dmesg command. Maybe pwidgets has its own logs, but they would require a pwidgets expert.
Richard