Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012
Manual frugal install of latest version...... all looking good so far.
# report-video
VIDEO REPORT: Lucid , version 528
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
6002 frames in 5.0 seconds
6069 frames in 5.0 seconds
6046 frames in 5.0 seconds
6063 frames in 5.0 seconds
6005 frames in 5.0 seconds
6063 frames in 5.0 seconds
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (245MB used)
Operating System : Puppy Linux 0.52
User Name : root (root)
Date/Time : Thu 21 Nov 2013 03:01:34 PM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
# report-video
VIDEO REPORT: Lucid , version 528
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
6002 frames in 5.0 seconds
6069 frames in 5.0 seconds
6046 frames in 5.0 seconds
6063 frames in 5.0 seconds
6005 frames in 5.0 seconds
6063 frames in 5.0 seconds
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (245MB used)
Operating System : Puppy Linux 0.52
User Name : root (root)
Date/Time : Thu 21 Nov 2013 03:01:34 PM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
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
The latest Slacko 5.6 sfs or Precise sfs file I cannot access.
Could this have anything to do with using a different compression method that Lupu does not recognize?
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
5.2.8.6 Three-headed Dog and Super Lucid Pups Updated
I have uploaded new versions of the "experimental kernel" versions of lucid pup 5.2.8.6, as 30131124. The only differences from the 20131120 versions are the addition of the 'usb-devices' script, needed to obtain USB device information in lupusuper and later kernels, and the update of the browser home page to link to Barry's new blog.
To change the blog link in the 20131120 lupus, enter the following command in a console window:
Radky tells me he is experimenting with lupus based on kernels from dpup and upup, with only 2 problems, so far. Based on that work, I would like to offer alternative kernels for lupusuper, once we resolve or reconcile those problems.
Regarding xz compression, radky told me that it was added only after the kernel used by 3HD and is supported in lupusuper, although probably not fully. Such SFS files can be mounted, but there may not be complete support for creating those files. Please report any limitations, so that I might address them.
The direct link to the downloads is:
http://www.mediafire.com/folder/dc28t2r ... es-5.2.8.6
Richard
To change the blog link in the 20131120 lupus, enter the following command in a console window:
Code: Select all
sed -i 's%/blog2/"%/news/"%' /usr/share/doc/home.htm
Regarding xz compression, radky told me that it was added only after the kernel used by 3HD and is supported in lupusuper, although probably not fully. Such SFS files can be mounted, but there may not be complete support for creating those files. Please report any limitations, so that I might address them.
The direct link to the downloads is:
http://www.mediafire.com/folder/dc28t2r ... es-5.2.8.6
Richard
Maybe this also has something to do with sfs file mounting.
http://bkhome.org/blog/?viewDetailed=02701
http://bkhome.org/blog/?viewDetailed=02701
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Hi, rerwin.
You wrote:
> The only differences from the 20131120 versions are the addition
of the 'usb-devices' script, needed to obtain USB device information in
lupusuper and later kernels (...)
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?
Thanks in advance.
musher0
You wrote:
> The only differences from the 20131120 versions are the addition
of the 'usb-devices' script, needed to obtain USB device information in
lupusuper and later kernels (...)
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?
Thanks in advance.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Lupusuper-5.2.8.6-k3.0.25-2131124
I tried mounting Slacko 5.6 sfs file and it opens with no problem.
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 one step forward and one step back.
I tried mounting Slacko 5.6 sfs file and it opens with no problem.
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 one step forward and one step back.
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
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?
The file is /usr/sbin/usb-devices and nothing more. Copy it from the new super or 3hd or even a precise pup (which is where I got it).
Last edited by rerwin on Mon 25 Nov 2013, 15:41, edited 1 time in total.
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
(pdiag can be run from a console or from the frisbee diagnostic dialog window.)
Richard
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
Last edited by rerwin on Mon 25 Nov 2013, 15:44, edited 1 time in total.
Fresh frugal install of latest THD (2.6.37.6).
Small bug first...... The drivers tab in Quickpet downloaded the incorrect Nvidia driver for this kernel.See Screenie.
Actually didn't notice until the download was almost complete.....obviously wouldn't work. Correct Nvidia driver now installed from my repo.
Small bug first...... The drivers tab in Quickpet downloaded the incorrect Nvidia driver for this kernel.See Screenie.
Actually didn't notice until the download was almost complete.....obviously wouldn't work. Correct Nvidia driver now installed from my repo.
- Attachments
-
- wrong driver.jpg
- (16.94 KiB) Downloaded 758 times
Otherwise, no problems so far.
# report-video
VIDEO REPORT: Three-Headed_Dog, version 001
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5916 frames in 5.0 seconds = 1183.155 FPS
6020 frames in 5.0 seconds = 1203.940 FPS
5989 frames in 5.0 seconds = 1197.753 FPS
5865 frames in 5.0 seconds = 1172.905 FPS
5940 frames in 5.0 seconds = 1187.909 FPS
5876 frames in 5.0 seconds = 1174.926 FPS
5755 frames in 5.0 seconds = 1150.891 FPS
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (185MB used)
Operating System : Puppy Linux 0.00
User Name : root (root)
Date/Time : Mon 25 Nov 2013 12:11:20 AM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
-Display-
Resolution : 1440x900 pixels
Vendor : The X.Org Foundation
Version : 1.7.6
-Monitors-
Monitor 0 : 1440x900 pixels
-OpenGL-
Vendor : NVIDIA Corporation
Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
Version : 1.5.8 NVIDIA 96.43.19
Direct Rendering : Yes
# report-video
VIDEO REPORT: Three-Headed_Dog, version 001
Chip description:
VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe glx dri
Drivers requested to be loaded: nvidia
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nvidia
Loaded modules: dbe dri dri2 extmod fb glx kbd mouse ramdac record
Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
5916 frames in 5.0 seconds = 1183.155 FPS
6020 frames in 5.0 seconds = 1203.940 FPS
5989 frames in 5.0 seconds = 1197.753 FPS
5865 frames in 5.0 seconds = 1172.905 FPS
5940 frames in 5.0 seconds = 1187.909 FPS
5876 frames in 5.0 seconds = 1174.926 FPS
5755 frames in 5.0 seconds = 1150.891 FPS
-Computer-
Processor : AMD Athlon(tm) XP 2400+
Memory : 1034MB (185MB used)
Operating System : Puppy Linux 0.00
User Name : root (root)
Date/Time : Mon 25 Nov 2013 12:11:20 AM CST
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8233 - VIA 8235
-Display-
Resolution : 1440x900 pixels
Vendor : The X.Org Foundation
Version : 1.7.6
-Monitors-
Monitor 0 : 1440x900 pixels
-OpenGL-
Vendor : NVIDIA Corporation
Renderer : GeForce4 MX 440 with AGP8X/AGP/SSE/3DNOW!
Version : 1.5.8 NVIDIA 96.43.19
Direct Rendering : Yes
Took the latest update for a spin and is very usable and noticeably faster than other recent puppies. Good job updating it!
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
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
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
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
EDIT: I suspect there is no package, that it is just part of puppy. 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
Hello, rerwin.
Frugally installed your latest sulu.
For a few seconds there, I thought this sulu had the pusave-creation bug.
For a few long moments, the shutdownconfig stood still, checked /mnt/fd0,
but realized that the pupsave was to be created on the eSATA drive. Phew!
The mid-October sulu version didn't hesitate at all in detecting the eSATA
drive as /dev/sda, and went straight to /mnt/sda2/sulu-5.2.8.6 to create
the pupsave file.
As a second test, I imported my big production pupsave for the October
sulu to my new November sulu folder and booted with it.
It did mess up my desktop icons, but that's an ordinary Puppy "feature"
in this situation.
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.
Aside from the details above, my big production pupsave runs as it did
under the October sulu.
So, all in all, this update is ok. Good job, rerwin! BFN.
musher0
Frugally installed your latest sulu.
For a few seconds there, I thought this sulu had the pusave-creation bug.
For a few long moments, the shutdownconfig stood still, checked /mnt/fd0,
but realized that the pupsave was to be created on the eSATA drive. Phew!
The mid-October sulu version didn't hesitate at all in detecting the eSATA
drive as /dev/sda, and went straight to /mnt/sda2/sulu-5.2.8.6 to create
the pupsave file.
As a second test, I imported my big production pupsave for the October
sulu to my new November sulu folder and booted with it.
It did mess up my desktop icons, but that's an ordinary Puppy "feature"
in this situation.
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.
Aside from the details above, my big production pupsave runs as it did
under the October sulu.
So, all in all, this update is ok. Good job, rerwin! BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
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
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
Just drop 'invaliddeplist', since I believe is precise-specific.
Luci also has 'findwoofinstalledpkgs.sh' in its /usr/local/petget which I left there though as far as I can see is not used by PPM anywhere.
You will also need 'mini-trash.xpm' and 'mini-exit.xpm' from /usr/local/lib/X11/mini-icons of another recent puppy.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
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
New fresh frugal install.
Network wizard does not list a wlan0
Module that is needed by this USB wireless adapter is:
ath9k-htc usb
This module shows as loaded.
From Lupu3hd working wireless connection:
Attached pdiag from lupusuper-5.2.8.6-k3.0.25-2131124Manufacturer=NETGEAR WNA
Product=WNA1100
Driver=ath9k_hif_usb
- Attachments
-
- pdiag-20131126.tar.gz
- (118.67 KiB) Downloaded 241 times
Last edited by bigpup on Tue 26 Nov 2013, 14:21, edited 1 time in total.
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
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
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
It's nothing at all.
The names of those files appeared rather fleetingly (in my perception at
least). I remember "desksetup" and my own "Triangles" pet. The names
showed up with version numbers, I think. Sorry I cannot be more precise.
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
This has been added to the beginning of the first message in this Lucid 5.2.8 thread. Congratulations to rerwin, along with his helpers, Bigpup, shinobar, radky, mavrothal, and many others who worked on the original development of Lucid and some who are new.
This is the last version of Lucid Puppy coordinated by playdayz. Forum member rerwin has prepared an updated version named 5.2.8.6, which contains numerous updates, including the Puppy programs such as Pmusic, Pburn, and PupControl, etc., along with advances in hardware detection and drivers, as well as many updates in the basic infrastructure of all Puppies that have been introduced since the last version of Lucid. There are download links plus links to complete descriptions of the changes at the new page for Lucid 5.2.8.6. -> http://www.murga-linux.com/puppy/viewtopic.php?t=90461
This is the last version of Lucid Puppy coordinated by playdayz. Forum member rerwin has prepared an updated version named 5.2.8.6, which contains numerous updates, including the Puppy programs such as Pmusic, Pburn, and PupControl, etc., along with advances in hardware detection and drivers, as well as many updates in the basic infrastructure of all Puppies that have been introduced since the last version of Lucid. There are download links plus links to complete descriptions of the changes at the new page for Lucid 5.2.8.6. -> http://www.murga-linux.com/puppy/viewtopic.php?t=90461
bigpup,
Thanks for the pdiag file. The module loaded in sulu is ath9k_htc. It also is in 3HD. But I see in the messages log:So, the required firmware is missing. In 3HD, when you search /var/log/messages for "ath9k_htc", what messages do you see? A pdiag from your 3HD test might be helpful.
Thanks for the pdiag file. The module loaded in sulu is ath9k_htc. It also is in 3HD. But I see in the messages log:
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