Page 145 of 191 [2858 Posts]   Goto page: Previous 1, 2, 3, ..., 143, 144, 145, 146, 147, ..., 189, 190, 191 Next
Author Message
zekebaby
PostPosted: Fri 02 Dec 2011, 15:40    Post subject:

rerwin wrote:
Rc.shutdown already invokes snapmergepuppy for pup-modes 3, 7 & 13. At least, in "patch-2". Is that not sufficient?

Sounds like it's late enough. Nuking /dev or /dev/snd too early will cause unpredictable results. Note that the removal needs to happen before the save file is written.
playdayz
PostPosted: Fri 02 Dec 2011, 15:09    Post subject:

Quote:
If I can get a link to 002, do I then "have" 003?

Yes Atie. And here is the link. That was the original intention of the Instant Updates, to give people the update without having to download a new iso.

I have hidden the Update 002 because, as you can see from the discussion there is some problem with some usb installs and sound, but everything else about Update 002 is OK (and that problem might not even be caused by Update 002).. But if you install to a usb drive or save on a usb drive, then hold off, or join the testing Wink If this problem is ever solved I will go back to posting the Update(s).

ftp://distro.ibiblio.org/puppylinux/puppy-5.2.8/Instant_Update-Lucid528-002.pet
Atle
PostPosted: Fri 02 Dec 2011, 15:00    Post subject: Update 001 and 002

Is it like those that are on mobile broadband or dialup can avoid to download a iso file? I have the 001 installed, but not the 002.

I can not find the 002 update anywhere, as i did with 001.

If I can get a link to 002, do I then "have" 003?

Atle
playdayz
PostPosted: Fri 02 Dec 2011, 14:50    Post subject:

Quote:
would agree, that having active on board sound and an add on sound card, will cause problems. Usually disabling the on board sound, in bios, works.


Bigpup, having "three" sound cards has never caused me a problem with Lucid or any other Puppy. One sound card is built-in, the second is a PCI add-in, and the third is a component of all ATI video cards for the last 5 years or so. It is that ATI component that is the "duplicate" sound card that rerwin is seeing. As I say, my sound has always worked on both "real" cards and I am able to switch between the sound cards using Pmusic or Audacious. This has been the same in all versions of Lucid so i don't think the multiple sound cards is what is causing the problem with sound and usb.

But, as you say, the built-in sound can be disabled in the BIOS usually. I certainly wouldn't advise anyone to modify their motherboard--that is for experts like Sage. I just don't think either approach should be needed.

I will check the link--it does seem to me that the sound problem may be caused by either inability to access the pupsave or the sound driver at the appropriate time Thanks.

Quote:
In my copy of Lupu-528.003...
The file /usr/sbin/snapmergepuppy exists...
There is within that file, the following line:
#110224 BK: revert remove all /dev, for now. 110503 added dev/snd


Sylvander, Is that the snapmergefix I posted earlier today. The one that is default in lupu-528-003.iso says "#110224 BK: revert remove all /dev, for now" and does not include the 110503 addition.

To test, make a new install of lupu-528.003 and then install the snapmergefix pet, and then start rebooting to see if the sound disappears. for this test, please do not install anything else, other than the snapmergefix pet. . The dates suggest that this *could* be something that changed in Lucid 5.2.8.
bigpup
PostPosted: Fri 02 Dec 2011, 14:08    Post subject:

Dealing with sound and USB drive issues.
Not too long ago Barry had a discussion about USB drives and save files.
Not sure if this is now implemented in Lucid 528 or even an issue, but just something to look at.
The code changes needed are in the comments toward the end.
http://bkhome.org/blog/?viewDetailed=02514

I would agree, that having active on board sound and an add on sound card, will cause problems. Usually disabling the on board sound, in bios, works.
Keep in mind, just because the hardware is there, does not meen it works.
Sylvander
PostPosted: Fri 02 Dec 2011, 12:43    Post subject:

In my copy of Lupu-528.003...
The file /usr/sbin/snapmergepuppy exists...
There is within that file, the following line:
Code:
#110224 BK: revert remove all /dev, for now. 110503 added dev/snd


Also a couple of lines that include as part [at the end] of the line:
Code:
#110222 shinobar: remove all /dev
rerwin
PostPosted: Fri 02 Dec 2011, 11:17    Post subject:

zekebaby wrote:
I had the same problem with disappearing sound awhile ago in Wary. IIRC (If I Recall Correctly), I added a line to the /usr/bin/snapmergepuppy script to delete the /dev folder. Barry implemented my fix in Wary, but removed just /dev/snd to be more conservative. Look for comment #110224 in snapmergepuppy in the latest Wary to see the fix. Since Lupu doesn't run on this old laptop, I can't verify whether the snapmergepuppy actually script exists in Lupu.
Rc.shutdown already invokes snapmergepuppy for pup-modes 3, 7 & 13. At least, in "patch-2". Is that not sufficient?
Richard
Sage
PostPosted: Fri 02 Dec 2011, 10:44    Post subject:

Quote:
I think I'd rather use onboard sound than sever the connections.
Don't need high performance sound anyway.
I'll begin with the easy methods

Good move. When I build PCs the first question is always 'What do you want it for?' Concording with many surveys, most answer '..just send a few emails and web-surfing.'
Goons down at PCWorld trying to sell them W8PAE4Gb monsters for five hundred notes when all they need is a D1200/256Mb and a copy of Puppy. More important to focus on a good ISP and the house wiring...

All too easy to lose sight of reality, esp. if folks watch too much TV.
zekebaby
PostPosted: Fri 02 Dec 2011, 10:25    Post subject:

Sylvander wrote:

3. "IIRC, I did the mod in snapmergepuppy in Wary (don't know if it exists in Lupu)"
(a) What does this mean?
(b) What is IIRC?
(c) What is snapmergepuppy?

Here's the more detailed explanation.

I had the same problem with disappearing sound awhile ago in Wary. IIRC (If I Recall Correctly), I added a line to the /usr/bin/snapmergepuppy script to delete the /dev folder. Barry implemented my fix in Wary, but removed just /dev/snd to be more conservative. Look for comment #110224 in snapmergepuppy in the latest Wary to see the fix. Since Lupu doesn't run on this old laptop, I can't verify whether the snapmergepuppy actually script exists in Lupu.
Brown Mouse
PostPosted: Fri 02 Dec 2011, 10:12    Post subject:

Sage wrote:
After that, all you need for the radical solution is a magnifying glass like the one grandpa uses to read letters from the Revenue and a scalpel, with or without a holder (ask a friendly nurse?), or 'hobby' knife or even a new Stanley blade. It isn't necessary to tangle with the board inter-layers


How things have progressed!To think back when I worked for many years in the art of multi-layer repair and engineering changes to pcb's,I used a high powered Carl Zeiss microscope and a micro ball mill amongst other tools Smile
Sylvander
PostPosted: Fri 02 Dec 2011, 09:57    Post subject:

(A) STEPS
31. Restored PupsaveHotBackup=5 using Wary-5.2.2, then reboot to Lupu-528.003->[with pmedia=ataflash in isolinux.cfg in the ISO]
32. Installed snapmergefix.pet

(B) All looks well, with loudspeaker icon displayed.
Let's see how long that lasts.
Will report back after some reboots.

@Sage
(C) I have a magnifying glass and a scalpel, but...
I think I'd rather use onboard sound than sever the connections.
Don't need high performance sound anyway.
I'll begin with the easy methods and [if that fails] work my way up to increasing difficulty, but only if/as/when necessary.
Sage
PostPosted: Fri 02 Dec 2011, 09:50    Post subject:

Horses & Courses, Kev!
Depends if you want OK or excellence.
And it really ain't rocket science or need special tools as you suggest.
Folks round here tend to be techno geeks. Mostly they are good at reading, good at searching and surfing, although comprehension is lacking amongst the usual suspects. The datasheet shows a square/rectangle with numbers around it and the keyway. The numbers correspond to a bunch of irrelevant functions apart from '+', 'in', and 'out'. After that, all you need for the radical solution is a magnifying glass like the one grandpa uses to read letters from the Revenue and a scalpel, with or without a holder (ask a friendly nurse?), or 'hobby' knife or even a new Stanley blade. It isn't necessary to tangle with the board inter-layers - the plastic blob is sitting there on the top. If you doubt your talents, then sever all its damn legs!
Those who regularly settle for less know what to expect - that's the message I was sending.
kevin bowers
PostPosted: Fri 02 Dec 2011, 09:09    Post subject:

Sage wrote:
Congratulations! I have been doing HW diagnosis by phone and email for a long time and was 99% sure of your situation.
SW is one thing, but you will always run into problems unless you fix the HW once and for all.
Chances are that the add-in sound card is superior, that's why it was, errr, added.
Look up the specs of on-board and card chips to confirm which is best.
If you just want muzak in the background of indeterminate quality, rip out the add-in card and make do with the on-board sound.
If you need quality for feeding hi-fi, video phone, serious sound projects, it's time to take scalpel in hand and disable that on-board chip in the ways I described above.
There is absolutely no way you can guarantee no problems with the SW until you fix the HW. It may work initially with pd's clever SW manipulation, but one upgrade will break it again every time. Do it now, do it right.


Sage, I agree up to a point. Certainly doing it right is, well, righteous. However, please consider: very few people, even "technicians", can do surgery on PC boards, particularly multi-layer MoBos. I've been using soldering irons since I was 5 and I wouldn't attempt it without special equipment. Hacking out chips is a pretty good way to convert a MoBo into a patch for the hole in the drywall. Disabling the on-board sound in the BIOS is certainly worth trying if possible, and it's reversible. Another point: sound chips on modern boards have improved immensely over the last few years. I am currently using on-board audio for vinyl conversions and hi-fi editing with a high level of success. So I recommend either removing the redundant sound card or disabling the on-board stuff in BIOS lest we throw out the baby with the bathwater!
shinobar
PostPosted: Fri 02 Dec 2011, 08:34    Post subject: snapmergepuppy

Sorry i have not yet reviewed rerwin's code but deleting /dev/snd is good i think.
I proposed to Barry to remove whole /dev in the savefile, but Barry sais we need to keep symlinks.
Yes, we need to keep only symlinks user made but all the rest under /dev can be, should be, removed from the savefile.

EDIT:
Ah, recent woof is removing /dev/snd, It's OK as for sound.
What i want to say is removing whole /dev except symlinks is better. Because i sometimes got trouble with usb printers.
Sage
PostPosted: Fri 02 Dec 2011, 08:22    Post subject:

Congratulations! I have been doing HW diagnosis by phone and email for a long time and was 99% sure of your situation.
SW is one thing, but you will always run into problems unless you fix the HW once and for all.
Chances are that the add-in sound card is superior, that's why it was, errr, added.
Look up the specs of on-board and card chips to confirm which is best.
If you just want muzak in the background of indeterminate quality, rip out the add-in card and make do with the on-board sound.
If you need quality for feeding hi-fi, video phone, serious sound projects, it's time to take scalpel in hand and disable that on-board chip in the ways I described above.
There is absolutely no way you can guarantee no problems with the SW until you fix the HW. It may work initially with pd's clever SW manipulation, but one upgrade will break it again every time. Do it now, do it right.
Display posts from previous:   Sort by:   
Page 145 of 191 [2858 Posts]   Goto page: Previous 1, 2, 3, ..., 143, 144, 145, 146, 147, ..., 189, 190, 191 Next

Powered by phpBB © 2001, 2005 phpBB Group