mikeb,
Well, lupu is ancient as far as some of its applications go. But I am attempting to upgrade the pieces the folks in this thread and elsewhere call to my attention. And I have made several small internal improvements that I plan eventually to provide to the woof-CE project. Barry's comment seems triggered by an expectation that lupu is part of the evolution of puppy that he has provided.

Lupu is frozen in time except for selected upgrades, often plucked from recent puppy developments. I maintain it for those of us happy to stick with it because is does not evolve, but serves our needs over the years.

(...)

Richard

Hello Richard, and all.

"Frozen in time"... might not be so bad... Considering that the older Ubuntu Precise
will be supported until April 2017 and that the newer Ubuntu Raring's support ends
this month (Jan. 2014)... whoever chooses one of your updated Lucid Puppies --
even now -- might be making a good choice, even if all the programs are not
absolutely up to date.

The remainder of the versions will be uploaded as I get the time to build them. My intent is that this will be the final 5.2.8.6 update for awhile, other than adding updates for libreoffice (Feb. & Apr.). But please report any new problems with 5.2.8.6.

Please try the lupusuper2 version; I propose that users migrate to it because it includes support for xz compression, which allows click-mounting of- and access to SFS files produced by recent puppies. Particularly, report anything that no longer works in that version, as a consequence of the kernel upgrade. If there is no downside, we could promote lupusuper2 as the primary lucid pup.

Thank you for all of your help in getting lupu to this point.
Richard

EDIT: Uploaded lupusuper4. (21040106)

EDIT 1/9/2014: Uploaded corrected version of lupusuper2, as 20140109. The original (20140106) contains the wrong files in /etc/modules, DOTconfig and firmware.dep. The latter prevents use of the "all-firmware" "tarballs", although the impact is less than normal for other puppies; In the lupusupers, almost all of the actual firmware resides in /lib/firmware, so is unaffected by firmware.dep and the tarballs (and directory equivalents).

Since I needed to bump the version date, I added the 3 packages shinobar posted in the "5.2.8.6" thread, for defaults-chooser, ffconvert and grub4dos. (Lupusuper4 has the same problem.) If lupusuper2 is to be the long-term primary offering, I want it to be perfect.

Posted: Tue 07 Jan 2014, 04:05 Post subject:
If it last for longer than xxx hours, seek medical help

Erroneous post._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Wireless setup with SNS OK.
This was a problem in other versions of Lucid.

Used the included Nvidia driver sfs to get working Nvidia graphics driver.
Loaded it with the SFS-Load-On-The Fly.
Used Quickpet->Drivers->click here to test your graphics card to identify which Nvidia driver SFS file to load.

The Nvidia driver SFS files are ok for someone that knows how to use them, but the Quickpet->drivers->Nvidia wants to get driver from the repository._________________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

I took bigpup's advice and omitted the additional development and nvidia SFS files, to keep the ISO file small. But I also uploaded the development packages, devx and kernel source for lupusuper2, to join the nvidia files as "Supplemental SFS Packages.
RichardLast edited by rerwin on Tue 14 Jan 2014, 22:10; edited 1 time in total

There being no compatible ati driver, it was using vesa. I got & installed (full hd install) the sulu from rerwin's posting , the iso dated 1/6/14, which also selected vesa for me on 1st boot. After downloading and burning the updated iso of 1/09/14, I installed it to a 16g sandisk cruiser flash drive. On rebooting to bring up the flash drive, I got a black screen total crash before X could start.

So, I powered off, and rebooted the hard drive and got a failed X start with a multi-colored trash screen. After another reboot, got vesa again in X and ran xorgwizard to select the first ati driver from the "choose" list in wizard, which was listed as simply ati in the wizard. That one will drive a maximum resolution of 1280x 1024 @60.

A problem for this card is that the suggested driver in the quickpet downloads from ibiblio, which takes over 30 minutes, then needs the configuration pet which comes with missing library linglut.so.3. finding and downloading the library is a chore, but worse, when exiting to prompt, as directed by the .pet dialog and running aticonfig --initial the return states no such command supported.

Not wanting to turn this into a beginner's help thread here, I'll post to the proper subforum in a new topic with ati fglrx in the title.

Using upup raring on the Dell right now to post this. Just some input from a noob user on the ati/radeon drivers in the sulu current version.

There being no compatible ati driver, it was using vesa. I got & installed (full hd install) the sulu from rerwin's posting , the iso dated 1/6/14, which also selected vesa for me on 1st boot. After downloading and burning the updated iso of 1/09/14, I installed it to a 16g sandisk cruiser flash drive. On rebooting to bring up the flash drive, I got a black screen total crash before X could start.

The first iso you tried was probably "lupu" while the second has to be lupusuper2, which uses a different kernel so requires its own version of the video driver.

The repo containing the ati video driver does not contain the version for the "sulu2" kernel, k3.2.48. The drivers listed by QuickPet are for the regular "lupus" and lupu3hd. I have yet to learn how to build the ATI driver. But it is time I get to it.

For now, please stick with the vesa driver. I have an nVidia card in my development PC that does not work with the default "nv" driver. Every time I boot without a pupsave file (pfix=ram or equivalent), I get a black screen that gradually lightens a little bit. Disturbing to see. I then press ctrl-alt-bksp and enter "xorgwizard" (w/o quotes) to select <vesa> and my monitor resolution. (Apparently, LCD monitors do not report their information for the wizard.) I would hope that technique would work for your ATI video card.

The problem with the driver repo is that I cannot maintain it and rely on playdayz (originator of lucid pup) to update it. Future drivers there will contain the kernel version they support. It is crucial to select only drivers for the kernel your version of lupu/sulu contains, which is included in the names of the lupusupers.
Richard

UPDATE: lupusuper4 has been corrected and uploaded. The checksum for lupusuper2 has been corrected.

There being no compatible ati driver, it was using vesa. I got & installed (full hd install) the sulu from rerwin's posting , the iso dated 1/6/14, which also selected vesa for me on 1st boot. After downloading and burning the updated iso of 1/09/14, I installed it to a 16g sandisk cruiser flash drive. On rebooting to bring up the flash drive, I got a black screen total crash before X could start.

The first iso you tried was probably "lupu" while the second has to be lupusuper2, which uses a different kernel so requires its own version of the video driver.

The repo containing the ati video driver does not contain the version for the "sulu2" kernel, k3.2.48. The drivers listed by QuickPet are for the regular "lupus" and lupu3hd. I have yet to learn how to build the ATI driver. But it is time I get to it.

For now, please stick with the vesa driver. I have an nVidia card in my development PC that does not work with the default "nv" driver. Every time I boot without a pupsave file (pfix=ram or equivalent), I get a black screen that gradually lightens a little bit. Disturbing to see. I then press ctrl-alt-bksp and enter "xorgwizard" (w/o quotes) to select <vesa> and my monitor resolution. (Apparently, LCD monitors do not report their information for the wizard.) I would hope that technique would work for your ATI video card.

The problem with the driver repo is that I cannot maintain it and rely on playdayz (originator of lucid pup) to update it. Future drivers there will contain the kernel version they support. It is crucial to select only drivers for the kernel your version of lupu/sulu contains, which is included in the names of the lupusupers.
Richard

UPDATE: lupusuper4 has been corrected and uploaded. The checksum for lupusuper2 has been corrected.

Yes, you're right. the first I was using was a lupu, using the vesa default. SMplayer didn't seem to like vesa and crashed, taking gnome Mplayer along (or maybe vice-versa), so I installed sulu2 dated 1/06/14. My genius plan was to install the driver and see if SMplayer worked better. I now see that vesa was used as a default for a reason. Gotta control my genius impulse.

Thanks for the explanation about the ati driver. I have another ati card, which I'll try to see if one of the included ati drivers supports it. If that fails, what I think I should do is a new, clean install of the latest super2 or the super4 and use vesa, as you suggest.. ATI is new to me. All the machines I used before now had Nvidia.

I hadn't been using a save file on the full installs because I didn't want the partition mounted since I was changing versions fairly often. The save file will save me some trouble until I get a driver or a card that solves the issue.

Richard, thanks for all your work, and my sympathies to playdayz in his troubles.

LTS it is ! Very good job. Permanently improved, you keep the best.
The best choice.
Musher0 says "whoever chooses one of your updated Lucid Puppies --
even now -- might be making a good choice, even if all the programs are not absolutely up to date. " Fully agreed. More than agreed, it's the right way of doing, as there is nobody to Cook the huge repositories from Precise to 'PET'isize them (ready-made meals).
The young hens go bald

I have been given a Dell L attitude D531 laptop. I tried to run the latest version of Lucid Puppy 5286 which I have with a number of versions of 528 on a flash drive (fat32) booting with grub4dos, I booted with pfix=ram with a view to producing a new savefile for the Dell. I set the personal settings, set up the wifi and then shutdown. I get an error before I get to the option to make a savefile. The only thing that I've tried that gets me anywhere from here is to hold down the power button to power off. I then tried the same with 528.005 with the same result. I then tried the original 528. This time I got a normal savefile option. I made a savefile, rebooted and installed an number of pets. I have also used the 'on the fly' to install an sfs. All of this works fine. I found the 002 update for 528 and installed this so I suppose I am running 528.002. Using 528 with the update does not cause any shutdown problems. The shutdown problem seems to have been caused by something done in upgrading from 002 to 005. I would like to use 5286. Has anybody got any ideas as to a solution to the shutdown problem? Also when I do the search for a video driver I am told to install Xorg_High which I have done. However, I am not sure if I have the best driver. I have attached the output from open glx.

I tried to run the latest version of Lucid Puppy 5286 which I have with a number of versions of 528 on a flash drive (fat32) booting with grub4dos,

keniv,
Although I have no personal experience with flash drive installations, I am concerned that you have multiple lupu 528s available at boot time. Keep in mind that if there are multiple lupu_528.sfs files visible (mounted or not) at boot time, you have no control over which one gets used. So, it is unclear which version of 528 you are running with.

To remove that mystery, look at /etc/rc.d/PUPSTATE to see the value of the path in the PUPSFS parameter.

To avoid the ambiguity, I temporarily rename all but one of the lupu_528.sfs files to something else.
Richard

I am concerned that you have multiple lupu 528s available at boot time. Keep in mind that if there are multiple lupu_528.sfs files visible (mounted or not) at boot time, you have no control over which one gets used. So, it is unclear which version of 528 you are running with.

To remove that mystery, look at /etc/rc.d/PUPSTATE to see the value of the path in the PUPSFS parameter.

I assumed that this would cause only the lupu_528.sfs file within the particular folder, say 528, to be booted. Is this not the case? If a different lupu_sfs file was booted with a pre-existing different savefile, say the savefile in the 528 folder booted with the lupu_528.sfs in the 52864 folder, would this not cause an update of the savefile. I've never seen this happen. Just to avoid the possibility of this would I be better to burn a cd of 5286 and boot from this. I could then attempt a shutdown and if it worked make a savefile onto the hdd.

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