ALSA library compatibility
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
jamesbond,
Of the many Puppy projects I have taken on, compiling a new ALSA version for the current Puppy (2.16) is not on my list, especially since 2.17 is not far from release.
Puppy 2.17 will have the latest ALSA, so it's probably worth waiting for this.
But if you're keen to have a recent ALSA in Puppy 2.15 or 2.16, I suggest you download the devx compiler addon, and compile ALSA yourself. I can talk you through the configuration process if you like.
Of the many Puppy projects I have taken on, compiling a new ALSA version for the current Puppy (2.16) is not on my list, especially since 2.17 is not far from release.
Puppy 2.17 will have the latest ALSA, so it's probably worth waiting for this.
But if you're keen to have a recent ALSA in Puppy 2.15 or 2.16, I suggest you download the devx compiler addon, and compile ALSA yourself. I can talk you through the configuration process if you like.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Another report of these matched ALSA libraries fixing sound problem -
http://www.murga-linux.com/puppy/viewto ... 099#123099
http://www.murga-linux.com/puppy/viewto ... 099#123099
Thanks tempestuous.
I managed to compile it
For those who need it, it is here: http://www.murga-linux.com/puppy/viewtopic.php?t=18239.
I managed to compile it
For those who need it, it is here: http://www.murga-linux.com/puppy/viewtopic.php?t=18239.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I have systems with the CS5535 and CS5536 audio chips. On the ALSA site I see fixes for these chips on 1.0.11 thru 1.0.16rc2.
On my systems when I run ALSA it say already running, finds correct CS5535 and then when it puts out test WOOF WOOF no sound. If I move volume or mixer PCM or volume I can get a click or pop but no other sounds. These systems have CE or XPE built in and sound works for those programs so I guess hardware ok.
So does puppy need a update on ALSA to get these chips to work and how would that be done? I see on this section of forum updates have been done.
I need help.
edit
I see on forum that PUP 2.17 should have ALSA 1.0.14 and thats what I use, with no sound for CS5535 chips, maybe they need newer 1.0.16rc2?
On my systems when I run ALSA it say already running, finds correct CS5535 and then when it puts out test WOOF WOOF no sound. If I move volume or mixer PCM or volume I can get a click or pop but no other sounds. These systems have CE or XPE built in and sound works for those programs so I guess hardware ok.
So does puppy need a update on ALSA to get these chips to work and how would that be done? I see on this section of forum updates have been done.
I need help.
edit
I see on forum that PUP 2.17 should have ALSA 1.0.14 and thats what I use, with no sound for CS5535 chips, maybe they need newer 1.0.16rc2?
Retired from GM, a Etech on engine electronics
Like to play with older computers and TVs
DENNIS
Like to play with older computers and TVs
DENNIS
That was quite a long time ago when I did this.
If I recall correctly, what I did was simply to download the latest alsa drivers from their website here, compile them (the usual ./configure followed by make), and install them (make install). Then I'd reboot.
It worked immediately for me. All you need is devx for the version of puppy you're using.
If I recall correctly, what I did was simply to download the latest alsa drivers from their website here, compile them (the usual ./configure followed by make), and install them (make install). Then I'd reboot.
It worked immediately for me. All you need is devx for the version of puppy you're using.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I am a hardware person not software, last software I worked with was 6502 on an ATARI.jamesbond wrote:That was quite a long time ago when I did this.
If I recall correctly, what I did was simply to download the latest alsa drivers from their website here, compile them (the usual ./configure followed by make), and install them (make install). Then I'd reboot.
It worked immediately for me. All you need is devx for the version of puppy you're using.
Thanks for help but I would need a software person to do this?
I use Puppy 2.17 because some of these systems have only 128meg ram and 2.17 for the most part works fine in little ram.
Retired from GM, a Etech on engine electronics
Like to play with older computers and TVs
DENNIS
Like to play with older computers and TVs
DENNIS
I just found out how to get into ADMIN on these systems so I can install, uninstall, save ect. I am going to go with what I can get to work, CE and XPe. The S90 and S90L with XPe now works great with great sound and speed in stand alone mode instead of having to work with a server.
Thanks to all for trying to help.
Thanks to all for trying to help.
Retired from GM, a Etech on engine electronics
Like to play with older computers and TVs
DENNIS
Like to play with older computers and TVs
DENNIS
-
- Posts: 286
- Joined: Sun 01 Jun 2008, 16:07
- Location: Durango, Colorado - USA
- Contact:
Thank you so much, tempestuous, for putting together those .pets for alsa. I have enjoyed using the smp kernel which jcoder offered us. It makes compiz much more smooth. However, I couldn't get sound working when I was using it.
This is the method that worked for me: I created a new puppy using puppy-unleashed and exempted the two alsa sound items. Then I simply used the alsa-lib and alsa-util dot pets which you provided.
Finally, from the command line, I had to run "alsawizard," and then "alsamixer." The leftmost column in alsamixer is important (I'm talking to you newbies) - that's the main volume, and you can adjust it with the up and down arrow keys. By default the volume is turned down to nothing when you first install alsa sound using these .pet packages. So you won't hear the usual bark when you are finished with alsawizard.
This is the method that worked for me: I created a new puppy using puppy-unleashed and exempted the two alsa sound items. Then I simply used the alsa-lib and alsa-util dot pets which you provided.
Finally, from the command line, I had to run "alsawizard," and then "alsamixer." The leftmost column in alsamixer is important (I'm talking to you newbies) - that's the main volume, and you can adjust it with the up and down arrow keys. By default the volume is turned down to nothing when you first install alsa sound using these .pet packages. So you won't hear the usual bark when you are finished with alsawizard.
alsa.pet for Slacko 5.7 or 6.3, and Tahr 6.0.6
Sound is not working in Slacko 5.7 or Tahr 6.0.3 (I did not yet try Slacko 6.3) on a 2008 netbook HP Mini 1000. Another discussion suggested updated sound libraries - alsa.pet.
Is there a suitable pet for these newer linuxes? Everything else works on this very nice netbook (which has a switch to turn off the touchpad, and a lovely keyboard). My partner insists on sound. Our USB headphones are painful.
The SSD would not let me shrink NTFS to install linux to EXT2 partition but linux seems to work fine from NTFS.
Is there a suitable pet for these newer linuxes? Everything else works on this very nice netbook (which has a switch to turn off the touchpad, and a lovely keyboard). My partner insists on sound. Our USB headphones are painful.
The SSD would not let me shrink NTFS to install linux to EXT2 partition but linux seems to work fine from NTFS.
HP Mini 1000 sound works with headphones not speakers
Web research revealed that in some version of Ubuntu sound works with headphones not speakers.
Same result with Slacko 5.7.
Speakers work in XP so it is a software bug.
Same result with Slacko 5.7.
Speakers work in XP so it is a software bug.
HP Mini making sound work with speakers
Someone using Ubuntu got the mini 1000 working with speaker sound by adding to /etc/modprobe.d/alsa-base.conf the line
options snd-hda-intel model=mobile
Now they get a choice, and speakers are muted when headphones are plugged in.
Assume it works with Slack and Tahr if I don't write again.
Much nicer keyboard and trackpad than my ACER netbook.
options snd-hda-intel model=mobile
Now they get a choice, and speakers are muted when headphones are plugged in.
Assume it works with Slack and Tahr if I don't write again.
Much nicer keyboard and trackpad than my ACER netbook.
In my Tahr I have headphones plugged into the same USB port each time, I initially used the multi-sound card option to set the headphones - which in my case was card 2, and I added to /etc/modprobe.d/alsa-base.conf
options snd-usb-audio index=2
after the last line. I have my savefolder content stored in adrv sfs and boot pfix=ram (no savefile) so its the exact same each time. Prior to 'casting in stone' the Tahr sound did seem to have some form of race condition, where the headphone might be card 1 sometimes, card 2 other times.
I love the zdrv, ydrv, adrv options. Firmware/modules in zdrv, nvidia graphics in ydrv, savefolder in adrv and booted pfix=ram,nocopy is working really well for me.
If I decide to made a change then usually I just create a savefolder at shutdown, and then extract the adrv content
unsquashfs -d ADRV adrv_tahr_6.0.5.sfs
and then copy into that the new savefolder content
cd ADRV
cp -rf ../tahrsave/* .
and reform the adrv again
cd ..
mksquashfs ADRV adrv_tahr_6.0.5.sfs -noappend
and then delete the savefolder
options snd-usb-audio index=2
after the last line. I have my savefolder content stored in adrv sfs and boot pfix=ram (no savefile) so its the exact same each time. Prior to 'casting in stone' the Tahr sound did seem to have some form of race condition, where the headphone might be card 1 sometimes, card 2 other times.
I love the zdrv, ydrv, adrv options. Firmware/modules in zdrv, nvidia graphics in ydrv, savefolder in adrv and booted pfix=ram,nocopy is working really well for me.
If I decide to made a change then usually I just create a savefolder at shutdown, and then extract the adrv content
unsquashfs -d ADRV adrv_tahr_6.0.5.sfs
and then copy into that the new savefolder content
cd ADRV
cp -rf ../tahrsave/* .
and reform the adrv again
cd ..
mksquashfs ADRV adrv_tahr_6.0.5.sfs -noappend
and then delete the savefolder
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
bookmarked
rufwoof your processes are of high interest for me. I am thinking all that could be done with pupsave adrive zdrive. Reviewing the process..
Bokomarked
Bokomarked