Page 150 of 190 [2847 Posts]   Goto page: Previous 1, 2, 3, ..., 148, 149, 150, 151, 152, ..., 188, 189, 190 Next
Author Message
Jades
PostPosted: Tue 15 Nov 2011, 07:56    Post subject:

playdayz wrote:
The GetFlash script has been inoperative for two days because, I believe, Adobe must have moved the location of the flashplayer binary. 01micko has fixed it quickly.


I was wondering why it was repeatedly spamming me with splash screens until I killed the task. Will install it when I get home.
Sylvander
PostPosted: Tue 15 Nov 2011, 07:20    Post subject:

1. Oh dear! The problem has returned. Sad

2. What to do now? Confused
Sylvander
PostPosted: Tue 15 Nov 2011, 04:17    Post subject:

1. "Perhaps I aught to restore the backup lupusave->[produces a working system] and only THEN apply your patch?"
That's done, and so far all's looking good. Very Happy
Here's hoping it stays that way.
Will report back if it doesn't.
Sylvander
PostPosted: Mon 14 Nov 2011, 19:30    Post subject:

rerwin...
1. I installed your patch using the PET file [confirmed in PPM], but I see no change.
i.e.
(a) Still no speaker icon, even after running the Alsa sound wizard, and rebooting [the changes to the session were auto-saved at reboot].

(b) Still the Alsamixer window flashes on-screen then off.

(c) Still the Gnome Alsamixer window is blank.

2. Should I run pmodemdiag again?
Found the previous .tar.gz file in /root and deleted it.

3. Perhaps I aught to restore the backup lupusave->[produces a working system] and only THEN apply your patch?
playdayz
PostPosted: Mon 14 Nov 2011, 18:27    Post subject:

Flashplayer

Adobe has moved the flashplayer.so binary so the Get Flashplayer script no longer works (nor does the automatic install-flashplayer on first run of a browser).

This program by 01micko is not as automatic but it should be future proof, since if they moved the binary once they might move it again.

People might want to run this every week or two since Flashplayer is changing so often these days.

ftp://distro.ibiblio.org/puppylinux/pet_packages-lucid/flash_install-0.1.pet
rerwin
PostPosted: Mon 14 Nov 2011, 18:21    Post subject:

Sylvander,
Thanks for the diag file. It seems that you missed seeing the pmodemdiag file in your root directory. The /tmp/pmodemdiag... directory is so you can see what was collected. No need to compress that into a tarball. To help avoid that confusion, I have been more explicit in the messages returned by pmodemdiag, in the patch, above.

Anyway, the xerrs.log shows that retrovol crashed during bootup, so that the speaker icon should not have appeared. This suggests that retrovol ran before the driver was loaded or ready. The patch may cause it to start a little later in the process, so might avoid running prematurely. It uses the same technique as used in woof, and therefore wary, slacko and all the others.
Richard
rerwin
PostPosted: Mon 14 Nov 2011, 18:06    Post subject: Patch for installation onto Instant Update 002

Here are some additional fixes to make 5.2.8 even more perfect:
    Shutdown addition to prevent hanging related to networked drives
    Addition of support for USB3 devices
    Correction to ensure retention of selected sound driver during bootup
    Correction to ensure sound module loaded at bootup before being used
    Correction of retrovol/volume-icon restoration in alsawizard, as done in wary & slacko (woof), to restore the icon for the sound test
    Addition of ALSA version data for alsa-info script
    Addition of time tags to udev event (udevtrace) logging
    Updates to pmodemdiag script, to add capture of ALSA-device list and to clarify messages

Besides these fixes, the usb_modeswitch function has been upgraded to version 1.2.0 and data base 20111023, described here:
http://www.murga-linux.com/puppy/viewtopic.php?p=582834#582834

Please test the network-drive shutdown fix, USB3 and the usb_modeswitch upgrade, to verify they are qualified to be included in a future Instant Update. Sylvander, please try this to see if it helps with your speaker/volume icon problem. Thank you.
Richard
Sylvander
PostPosted: Mon 14 Nov 2011, 15:33    Post subject:

OK, understood. Smile
playdayz
PostPosted: Mon 14 Nov 2011, 15:20    Post subject:

Quote:
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.
Sylvander
PostPosted: Mon 14 Nov 2011, 13:48    Post subject:

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?
playdayz
PostPosted: Mon 14 Nov 2011, 13:31    Post subject:

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?
Sylvander
PostPosted: Mon 14 Nov 2011, 13:29    Post subject:

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! Sad

2. Here's the text in the terminal window from running the pmodemdiag command:
Code:
# 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/.
#


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]
Sylvander
PostPosted: Mon 14 Nov 2011, 13:03    Post subject:

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.
rerwin
PostPosted: Mon 14 Nov 2011, 11:52    Post subject:

Sylvander wrote:
Speaker icon has disappeared from bottom right...
Alsamixer flashes on-screen then off.
Gnome Alsamixer is blank.
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.

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
Sylvander
PostPosted: Mon 14 Nov 2011, 10:39    Post subject:

Problem has returned during the session! Sad

i.e. Speaker icon has disappeared from bottom right...
Alsamixer flashes on-screen then off.
Gnome Alsamixer is blank.
Display posts from previous:   Sort by:   
Page 150 of 190 [2847 Posts]   Goto page: Previous 1, 2, 3, ..., 148, 149, 150, 151, 152, ..., 188, 189, 190 Next

Powered by phpBB © 2001, 2005 phpBB Group