http://archive.org/details/Puppy_Linux_Lupu_5.2.8.6
![Smile :)](./images/smilies/icon_smile.gif)
Lupu3HD5.2.8.6- 2131124rerwin wrote: Regarding those later kernels, I am frustrated that lupu cannot access recent versions of SFS files, as in Precise pup and slacko. I understand that the issue is a capability that appeared in the later kernels but is not backport-able to lupu. But is it available in the kernels used by 3HD and sulu? If so, can anyone versify whether those pups can access precise's main SFS file? Or is there more we need in those lupus to make it work?
Richard
Code: Select all
sed -i 's%/blog2/"%/news/"%' /usr/share/doc/home.htm
Only if that's all you want from the 20131124 version. But you would miss the additions since your (20131012) version. The "difference" I mean is between 20131120 and 20131124. The newer version includes the changes that went into 30131120, but no 3hd/super ISOs were made for that version.musher0 wrote:I'm writing this from your sulu_001 from last month. If you posted the
added script, would it be enough for me to copy/paste it in a certain
folder? Or do I need to D/L the whole ISO?
bigpup, thanks for testing with lupusuper. Could you obtain a pdiag file from lupusuper when you see that wireless is not working. Maybe there is a clue in there somewhere. You can just attach it to a PM to me (if you don't want to post it).bigpup wrote:Lupusuper-5.2.8.6-k3.0.25-2131124
This version of Lupu will not recognize my Netgear n150 USB wireless network adapter.
The needed module is loaded, but no wlan0 showing in network manager.
Works fine in Lupu3HD
That is good news. The extensive changes to it "scared me off" from including it. Where do I find the pet package for it, assuming there is one?mavrothal wrote:You may want to also add the latest version of PPM. It can search multiple repost simultaneously. does a better job with dependencies and can search with partial names with multiple search terms and even searches in the descriptions.
Certainly worth updating.
I tried it with 20131120 and works fine
Thanks for reporting this "false alarm." The script that makes that check only compares package names and versions between the user-installed-packages file and the woof-installed-packages file. It compares versions so as to avoid recommending uninstalling later packages.musher0 wrote:What I found uncool, though, is that it warned me that I would have to
remove a couple of pets that I have created for pinboard management,
etc., if I wanted to use the PPM. I tested the PPM, it loads normally, and
I don't need -- nor want! -- to delete the pets I created. Thanks in
advance for any explanation.
Indeed I used the files directly from (various places in) the woof-CE tree but copying /usr/local/petget from precise-5.7.1 will do.rerwin wrote: So, when you add PPM to lupu, exactly which directories and files are you including as the complete component? /usr/local/petget/ seems to be the main set of files. Anything beyond that?
Richard
New download of lupusuper-5.2.8.6-k3.0.25-2131124.rerwin wrote:bigpup, thanks for testing with lupusuper. Could you obtain a pdiag file from lupusuper when you see that wireless is not working. Maybe there is a clue in there somewhere. You can just attach it to a PM to me (if you don't want to post it).bigpup wrote:Lupusuper-5.2.8.6-k3.0.25-2131124
This version of Lupu will not recognize my Netgear n150 USB wireless network adapter.
The needed module is loaded, but no wlan0 showing in network manager.
Works fine in Lupu3HD
EDIT 11/25: Are you sure you are using lupusuper-5.2.8.6-k3.0.25-2131124? At this time I see "0" as the download count for that ISO file.
R
Attached pdiag from lupusuper-5.2.8.6-k3.0.25-2131124Manufacturer=NETGEAR WNA
Product=WNA1100
Driver=ath9k_hif_usb
Hi, rerwin.rerwin wrote:Thanks for reporting this "false alarm." The script that makes that check only compares package names and versions between the user-installed-packages file and the woof-installed-packages file. It compares versions so as to avoid recommending uninstalling later packages.musher0 wrote:What I found uncool, though, is that it warned me that I would have to
remove a couple of pets that I have created for pinboard management,
etc., if I wanted to use the PPM. I tested the PPM, it loads normally, and
I don't need -- nor want! -- to delete the pets I created. Thanks in
advance for any explanation.
But it assumes the package names are in the form of packagename-x.x.x.xversionnumber. We know that not all names get formatted that way, so mistakes will occur. That is why I include in parentheses the name of the now-built-in package that the user-installed package appears to be a same-or-older version of. I encourage users to compare the names to be sure they actually refer to the same base package, and to ignore the warning if they are different.
So that I might improve the comparison logic, could you tell us your package names that were incorrectly assumed to conflict with something included in sulu? And what implied that the conflict involved the PPM? I am open to softening the wording of the message or adding to it -- suggestions are welcome.
Thanks for your help.
Richard
Code: Select all
Nov 27 04:44:23 puppypc user.err kernel: [ 20.974540] usb 1-2: ath9k_htc: Firmware - htc_9271.fw not found
Nov 27 04:44:23 puppypc user.warn kernel: [ 20.974557] ath9k_htc: probe of 1-2:1.0 failed with error -22
Nov 27 04:44:23 puppypc user.info kernel: [ 20.974598] usbcore: registered new interface driver ath9k_htc