Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012
AFter some further testing with the lupu528, lupu528+update002M, lupu528-002M, WITH SAMBA, I think the problem may be the version of SAMBA available in the PPM. Maybe a newer PPM version of SAMBA in the next Puppy kernel for LUPU, might be in order.
Sorry for the original alert. It had seemed that the couple issues I saw (ROX and SAMBA issue) were related to the filesystem in Puppy528. It appears that might not be the case.
Sorry for the original alert. It had seemed that the couple issues I saw (ROX and SAMBA issue) were related to the filesystem in Puppy528. It appears that might not be the case.
Have now tried Three-headed Dog on both my USB3 laptop and on my Intel D865GLC desktop with ATI X1550 video adapter.James C wrote:playdayz wrote:otropogo wrote: ....
Three-headed Dog should work fine with the default nv driver. ...
The results were surprising and disappointing:
1. Although luci-001 handled the laptop's Nvidia adapter without problems, it was unable to detect the 3TB Goflex Desk drive on the USB3 expressport adapter. The issue is not with the size of the drive, as it mounts without issues on the USB2 port. It follows that luci doesn't have support for USB3.
Slacko_5.29.6 does detect and mount the same drive on the USB3 port.
2. on the Intel PC, there was a major problem with the video which I've never experienced before in any OS. At first bootup with pfix=ram, the screen was improperly sized, but the popup for the display responded to my input and set the screen resolution to 1600x1200. A Radeon driver was installed, and everything looked normal.
I then used the date/time setting box to adjust the time for daylight savings. When x-windows reset, instead of showing the configured screen, it presented the xorg wizard setup. I chose probe, and the wizard refused the 1600x1200 setting, and when the desktop displayed the screen was so dim, it was impossible to see the icons. I had to maximize the brightness setting of the monitor (in all other puppies I have it set to about 50%) in order to get a minimally visible desktop. I created a save file and rebooted, but the result was the same - too dim to be usable.
I then rebooted with my lupu-528 disk, and was able to lower the brightness setting of the monitor by 50% without reaching anywhere near the dimness of the luci screen.
Since the purpose of the exercise was to get a Puppy with the versatility and range of applications of lupu 5.28, plus full support for USB3, my quest goes on. Presumably I'll have to wait for lupu to get a newer kernel with USB3 support.
otropogo@gmail.com facebook.com/otropogo
otropogo, I have asked tempestuous and rerwin if they have any ideas. They are the experts on drivers. Since Slacko does work with usb3 it might be useful to ask for the features (versatility and range of applications) you want in Slacko. The fact is that Slacko is at the beginning of its development and Lucid is toward the end of its--though it will remain available with this forum for questions and discussion as well as the Instant Update 002. I am disappointed that 3HD did not work since it uses the same kernel and kernel mode drivers as Slacko. Like Lupu, 3HD will also remain available with an upcoming update and its support forum.Since the purpose of the exercise was to get a Puppy with the versatility and range of applications of lupu 5.28, plus full support for USB3, my quest goes on. Presumably I'll have to wait for lupu to get a newer kernel with USB3 support.
.
Lupu 528 standard remains the only current version that works on both my Intel D865GLC desktop and my Toshiba laptop with USB3. No version of Slacko except 5.3 will boot my Intel desktop. But strangely, it doesn't provide native USB3 support (whereas 5.29.6 did)playdayz wrote:...
otropogo, I have asked tempestuous and rerwin if they have any ideas. They are the experts on drivers. Since Slacko does work with usb3 it might be useful to ask for the features (versatility and range of applications) you want in Slacko. The fact is that Slacko is at the beginning of its development and Lucid is toward the end of its--though it will remain available with this forum for questions and discussion as well as the Instant Update 002. I am disappointed that 3HD did not work since it uses the same kernel and kernel mode drivers as Slacko. Like Lupu, 3HD will also remain available with an upcoming update and its support forum.
.
Lupu528_K3.0.7 provides native support for USB3, but won't boot my desktop PC. It's also fatally crippled by inability to "see any active interfaces", wired or wireless on the 64-bit laptop.
Lupu 528 standard boots both of my PCs, and provides USB3 and 3TB support via pet (so I can't boot a save file or sfs from the USB3port). It seems initially that the 3TB drive is unwritable, because a red popup displays when mounting it that says:
The same thing happens when first mounting the drive on the USB2 port.NTFS WARNING The ntfs-3g drive was unable to mount the NTFS partition and reported the following error message
fuse: if you are sure this is safe use the 'nonempty' mount option
So, the inbuilt kernel NTFS drive has been used to mount the partition read only OK
However, after reattaching the drive to the second USB3 port and remounting it, the red popup no longer appears, and the partition is mounted writable. After that, it can also be reattached to the first port and mounted writable there.
It seems that some corruption has crept into all of the newer kernel versions of Slacko and lupu.
otropogo@gmail.com facebook.com/otropogo
UPDATE: sfs_load
sfs_load may fail to unload the excessive(>6) SFS on Lucid Puppy 528.
REASON: the losetup command(busybox) on Lucid Puppy 528 cannot properly handle /dev/loop10 and larger.
Try sfs_load-1.3 in such case.
http://www.murga-linux.com/puppy/viewtopic.php?t=64354
You may need to reboot PC after the sfs_load updated (only if you have loaded SFS more than 6).
REASON: the losetup command(busybox) on Lucid Puppy 528 cannot properly handle /dev/loop10 and larger.
Try sfs_load-1.3 in such case.
http://www.murga-linux.com/puppy/viewtopic.php?t=64354
You may need to reboot PC after the sfs_load updated (only if you have loaded SFS more than 6).
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Latest ISO, Windows exe installer and flash updates for Lucid here
http://puppylinux.org/wikka/puppy526
yep we don't have a 528 page . . .
Have not used Lucid in a long while, so anyone registering and updating the wiki for Lucid most welcome
Did use pemasu's Lucid derivative - which worked great for me
Have a friend with a Samsung laptop
- Wifi drivers not available out of the box in Slacko
- gonna try Lucid (lupu-528.002.iso) for him - will put on a USB drive.
He wants to dual boot some minor OS called Whinedoze 7 and Ubuntu and use Puppy from DVD/Keydrive for banking . . .
Gosh Slacko is a mature project for me
- been using Slacko for months . . .
- but Larry is right we need compiled programs for Slacko
- end user feedback etc
Beginning its cycle is Puppy 6 and PARM
No idea what will emerge . . .
I have hijacked ye olde Saluki page for now . . .
http://puppylinux.org/wikka/Puppy6
http://puppylinux.org/wikka/PARM
Lucid seems to be shining brightly
http://puppylinux.org/wikka/puppy526
yep we don't have a 528 page . . .
Have not used Lucid in a long while, so anyone registering and updating the wiki for Lucid most welcome
Did use pemasu's Lucid derivative - which worked great for me
Have a friend with a Samsung laptop
- Wifi drivers not available out of the box in Slacko
- gonna try Lucid (lupu-528.002.iso) for him - will put on a USB drive.
He wants to dual boot some minor OS called Whinedoze 7 and Ubuntu and use Puppy from DVD/Keydrive for banking . . .
The fact is that Slacko is at the beginning of its development and Lucid is toward the end of its--though it will remain available with this forum for questions and discussion as well
Gosh Slacko is a mature project for me
- been using Slacko for months . . .
- but Larry is right we need compiled programs for Slacko
- end user feedback etc
Beginning its cycle is Puppy 6 and PARM
No idea what will emerge . . .
I have hijacked ye olde Saluki page for now . . .
http://puppylinux.org/wikka/Puppy6
http://puppylinux.org/wikka/PARM
Lucid seems to be shining brightly
Problem eliminated.
Using the following method...
1. Restored a recent "Pupsave Hot Backup" [made on the 10th Nov].
2. Odd thing: the booted live 528 CD [and SFS beside the lupusave] treated the lupusave [that had been previously updated from 526 to 528] as a 526 lupusave, and asked if I wanted to update it to 528.
See this post for detail.
3. The speaker icon is now back where it aught to be, and sound appears normal.
Using the following method...
1. Restored a recent "Pupsave Hot Backup" [made on the 10th Nov].
2. Odd thing: the booted live 528 CD [and SFS beside the lupusave] treated the lupusave [that had been previously updated from 526 to 528] as a 526 lupusave, and asked if I wanted to update it to 528.
See this post for detail.
3. The speaker icon is now back where it aught to be, and sound appears normal.
In a session where the icon disappears, could you immediately run pmodemdiag to obtain some evidence to work with? Please post the generated pmodemdiag...tar.gz file or PM it to me.Sylvander wrote:Speaker icon has disappeared from bottom right...
Alsamixer flashes on-screen then off.
Gnome Alsamixer is blank.
Be aware that, in my alsawizard debugging attempts I found that the act of unloading the sound drivers causes retrovol to crash, losing the speaker icon. What have you been doing relative to "sound" that might unload the drivers? Alsamixer? Does rerunning the alsawizard restore the volume-control speaker icon?
Richard
1. "In a session where the icon disappears, could you immediately run pmodemdiag to obtain some evidence to work with? Please post the generated pmodemdiag...tar.gz file or PM it to me."
Will do, just as soon as I notice the icon has gone, and can respond.
2. "What have you been doing relative to "sound" that might unload the drivers? Alsamixer?"
Normally I only run retrovol to check the settings are OK, then close it.
I never mess with Alsamixer unless the icon has already disappeared.
Can't think of anything that might be causing this.
3. "Does rerunning the alsawizard restore the volume-control speaker icon?"
It did at least one time, that's for sure.
Then when the icon disappeared again, and I tried Alsawizard again, it didn't work.
Will do, just as soon as I notice the icon has gone, and can respond.
2. "What have you been doing relative to "sound" that might unload the drivers? Alsamixer?"
Normally I only run retrovol to check the settings are OK, then close it.
I never mess with Alsamixer unless the icon has already disappeared.
Can't think of anything that might be causing this.
3. "Does rerunning the alsawizard restore the volume-control speaker icon?"
It did at least one time, that's for sure.
Then when the icon disappeared again, and I tried Alsawizard again, it didn't work.
1. OK...
Opened and closed retrovol...[OK]
Browsed some web pages...[OK]
Manually saved the session...[OK]
Rebooted, and chose to not save the session [already saved]...[OK]
Once back into the desktop, the speaker icon was GONE!
2. Here's the text in the terminal window from running the pmodemdiag command:
3. The above created a folder = /tmp/pmodemdiag-20111114
Couldn't find any pmodemdiag-20111114.tar.gz file.
So...
I moved the above folder to /02, and made a tar.gz archive of it, and will attempt to upload it here:
[Seems to have succeeded]
Opened and closed retrovol...[OK]
Browsed some web pages...[OK]
Manually saved the session...[OK]
Rebooted, and chose to not save the session [already saved]...[OK]
Once back into the desktop, the speaker icon was GONE!
2. Here's the text in the terminal window from running the pmodemdiag command:
Code: Select all
# pmodemdiag
cat: /etc/puppyversion: No such file or directory
/usr/sbin/pmodemdiag: line 20: [: -ge: unary operator expected
Running PupScan to get hardware IDs and drivers - please close its window manually.
Collecting various modem-related files into an archive tarball:
pmodemdiag-20111114.tar.gz.
ls: cannot access /dev/char/116:16: No such file or directory
ls: cannot access /dev/char/116:26: No such file or directory
ls: cannot access /dev/char/116:17: No such file or directory
ls: cannot access /dev/snd/pcmC0D2c: Input/output error
ls: cannot access /dev/snd/midiC1D0: Input/output error
ls: cannot access /dev/snd/pcmC1D2p: Input/output error
ls: cannot access /dev/snd/pcmC0D1p: Input/output error
ls: cannot access /dev/snd/hwC0D0: Input/output error
ls: cannot access /dev/snd/pcmC0D0c: Input/output error
ls: cannot access /dev/snd/seq: Input/output error
ls: cannot access /dev/snd/hwC1D0: Input/output error
ls: cannot access /dev/snd/pcmC1D1p: Input/output error
ls: cannot access /dev/snd/controlC0: Input/output error
Diagnostic file collection complete.
Tarball pmodemdiag-20111114.tar.gz can be attached to a posting or personal
message (PM) in the Puppy forum, for analysis of dialup modem issues.
The content can be found in /tmp/pmodemdiag-20111114/.
#
Couldn't find any pmodemdiag-20111114.tar.gz file.
So...
I moved the above folder to /02, and made a tar.gz archive of it, and will attempt to upload it here:
[Seems to have succeeded]
Last edited by Sylvander on Mon 14 Nov 2011, 17:34, edited 1 time in total.
Sylvander, It might be good to start from scratch.
Is there a problem with the speaker if you use lupu-528.iso from the first page of this thread--booting as a Live CD and not updating any lupusave files?
Can you then shutdown and create a lupusave file from that Live CD boot and then reboot without a problem?
After rebooting can you then install the Instant Update 002 from the first page of this thread--does that cause a problem?
Can you then reboot with that Instant Update 002 installed--does that cause the problem?
Is there a problem with the speaker if you use lupu-528.iso from the first page of this thread--booting as a Live CD and not updating any lupusave files?
Can you then shutdown and create a lupusave file from that Live CD boot and then reboot without a problem?
After rebooting can you then install the Instant Update 002 from the first page of this thread--does that cause a problem?
Can you then reboot with that Instant Update 002 installed--does that cause the problem?
1. "Sylvander, It might be good to start from scratch"
Yes, I had that in mind, but when the lupusave restore seemed to work I just ran with that.
Do you think starting afresh is the thing to do at this point?
2. "Is there a problem with the speaker if you use lupu-528.iso from the first page of this thread--booting as a Live CD and not updating any lupusave files?"
Don't know yet, haven't ever tried that so far.
The update seemed to go OK...
Until this problem appeared out of the blue.
3. "Can you then shutdown and create a lupusave file from that Live CD boot and then reboot without a problem?"
I'll try that ASAP.
4. "After rebooting can you then install the Instant Update 002 from the first page of this thread--does that cause a problem?"
Originally, I did make the mistake of installing the 002 update...
To a lupusave updated from Lupu-526 to Lupu-528.002...
And it seemed to have caused no problem [you reported that it wouldn't, so I felt OK about that].
5. "Can you then reboot with that Instant Update 002 installed--does that cause the problem?"
(a) You want me to deliberately install the 002 update, even though that's not a thing that aught to be done [it's redundant]...
So as to check whether it causes a problem?
(b) I aught to first wait a while, using the new/fresh lupusave made using Lupu-528.002...
To first see that it's working reliably.
And only once satisfied that it's working well and relibly...
Only then apply the 002 update, OK?
Yes, I had that in mind, but when the lupusave restore seemed to work I just ran with that.
Do you think starting afresh is the thing to do at this point?
2. "Is there a problem with the speaker if you use lupu-528.iso from the first page of this thread--booting as a Live CD and not updating any lupusave files?"
Don't know yet, haven't ever tried that so far.
The update seemed to go OK...
Until this problem appeared out of the blue.
3. "Can you then shutdown and create a lupusave file from that Live CD boot and then reboot without a problem?"
I'll try that ASAP.
4. "After rebooting can you then install the Instant Update 002 from the first page of this thread--does that cause a problem?"
Originally, I did make the mistake of installing the 002 update...
To a lupusave updated from Lupu-526 to Lupu-528.002...
And it seemed to have caused no problem [you reported that it wouldn't, so I felt OK about that].
5. "Can you then reboot with that Instant Update 002 installed--does that cause the problem?"
(a) You want me to deliberately install the 002 update, even though that's not a thing that aught to be done [it's redundant]...
So as to check whether it causes a problem?
(b) I aught to first wait a while, using the new/fresh lupusave made using Lupu-528.002...
To first see that it's working reliably.
And only once satisfied that it's working well and relibly...
Only then apply the 002 update, OK?
Not exactly. I recommend beginning with the lupu-528.iso from the first message of this thread--that is the original (not the updated lupu-528-002.iso). Then, as you say, use it a while and make a save file and see that everything is OK, then install the Instant Update 002 and use that for a while.b) I aught to first wait a while, using the new/fresh lupusave made using Lupu-528.002...
To first see that it's working reliably.
And only once satisfied that it's working well and relibly...
Only then apply the 002 update, OK?