2.15CE Final, no sound on Compac EVO N600C

Please post any bugs you have found
Post Reply
Message
Author
paperaussie
Posts: 8
Joined: Thu 12 Apr 2007, 09:26

2.15CE Final, no sound on Compac EVO N600C

#1 Post by paperaussie »

Version 2.14 detects the soundcard in a Compaq Evo N600c notebook as Maestro3 which works perfectly fine.

Version 2.15CE looks modern but does not detect a soundcard at all :(

User avatar
ezeze5000
Posts: 347
Joined: Tue 10 May 2005, 17:48
Location: Missouri U.S.A
Contact:

re-Puppy215CE-Final, no sound

#2 Post by ezeze5000 »

I have had the same problem on several computers whan loading
Puppy215CE-Final .
If your sound card is an old ISA card puppy215Ce-final won't load it.

There seems to be a slight bug in the detection script when looking
for ISA sound cards.

I haven't been able to narrow it down yet.

I am hoping somebody will spot the error and make a quick fix.

The GUI flashes by so fast you can't see the choices for the old card drivers. Then it says no drivers found.

Anyway thats my 2 cents worth.

I hope this helps.
If at first you don't succeed try try again!

GeoffB
Posts: 2
Joined: Sun 15 Apr 2007, 00:42
Location: Portsmouth, England

Soundcard Problems 2.15CE

#3 Post by GeoffB »

A quick and dirty fix for this problem. (Hard Drive Install)

Boot from a 2.14 disc.

Mount the partiton that 2.15CE is installed on.

Delete the following folders/files and replace them with the same folders/files from the 2.14 live install

/usr/bin/alsamixer
/usr/lib/ao/plugins-2/libalsa09.so
/usr/lib/alsa/lib
/usr/sbin/alsactl
/usr/sbin/alsawizard
/usr/share/alsa

Reboot into 2.15CE and alsaconf will work.

It's probably not necessary to replace all of these but not knowing which one is faulty it's easier to replace them all rather than trying them one at a time to find the culprit.

I hope this helps.

Geoff

User avatar
ezeze5000
Posts: 347
Joined: Tue 10 May 2005, 17:48
Location: Missouri U.S.A
Contact:

This might help with some sound problems

#4 Post by ezeze5000 »

I did exactly what GeoffB said and it was still a no go.......but!

I checked what puppy-214 had changed in the modprobe.conf , after I ran Alsa config and here is what changed: (This was added to the end of the file in my modprobe.conf)

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.8 ---
alias snd-card-0 snd-opl3sa2
alias sound-slot-0 snd-opl3sa2
options snd-opl3sa2 fm_port=-1 midi_port=-1 port=0x370 wss_port=0x530 isapnp=0 dma1=1 dma2=0 irq=5
# --- END: Generated by ALSACONF, do not edit. ---

I copied this and pasted it into my modprobe conf and now I have sound in
Puppy-215CE-Final

I hope this will help with some of the sound problems in Puppy-215CE-Final
If at first you don't succeed try try again!

User avatar
WhoDo
Posts: 4428
Joined: Wed 12 Jul 2006, 01:58
Location: Lake Macquarie NSW Australia

Re: This might help with some sound problems

#5 Post by WhoDo »

ezeze5000 wrote:# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.8 ---
alias snd-card-0 snd-opl3sa2
alias sound-slot-0 snd-opl3sa2
options snd-opl3sa2 fm_port=-1 midi_port=-1 port=0x370 wss_port=0x530 isapnp=0 dma1=1 dma2=0 irq=5
# --- END: Generated by ALSACONF, do not edit. ---

I copied this and pasted it into my modprobe conf and now I have sound in
Puppy-215CE-Final

I hope this will help with some of the sound problems in Puppy-215CE-Final
tempestuous has admitted that the alsa.conf script that he supplied for 2.15CE is preventing access to the legacy sound drivers in zdrv_215.sfs so he uploaded a modified script that fixes the sound detection problems for all supported legacy drivers - Projects>Puppy 2.15CE Patches and Updates for a link to the download.

Hope that helps
[i]Actions speak louder than words ... and they usually work when words don't![/i]
SIP:whodo@proxy01.sipphone.com; whodo@realsip.com

paperaussie
Posts: 8
Joined: Thu 12 Apr 2007, 09:26

Got sound with help of 2.14

#6 Post by paperaussie »

Got my soundcard working by booting 2.14 and then saving my settings to harddisk when shutting down.

2.15CE upgrades during next boot and sound works without any problems.

My guess is that something is wrong with the soundcard detection because 2.15CE would not detect any soundcards without having saved settings in 2.14. I usually don't save my settings because I use Puppy from USB stick on various computers.

Due to lack of time I haven't tried changing modprobe.conf yet as suggested by WhoDo but I guess it would work as well.

paperaussie
Posts: 8
Joined: Thu 12 Apr 2007, 09:26

Re: This might help with some sound problems

#7 Post by paperaussie »

WhoDo wrote: tempestuous has admitted that the alsa.conf script that he supplied for 2.15CE is preventing access to the legacy sound drivers in zdrv_215.sfs so he uploaded a modified script that fixes the sound detection problems for all supported legacy drivers - Projects>Puppy 2.15CE Patches and Updates for a link to the download.

Hope that helps
I downloaded and installed the patch but Alsa would still not find a soundcard. If I stop alsa in 2.14 and restart it, it loads snd-maestro3. If I copy the lines from modprobe.conf across into 2.15 alsa complains that snd_maestro3 cannot be found.

In 2.14 I find 2 snd-maestro3.ko files while in 2.15 I can't find them, maybe this is the problem.

paperaussie
Posts: 8
Joined: Thu 12 Apr 2007, 09:26

Re: Soundcard Problems 2.15CE

#8 Post by paperaussie »

Thanks for this tip. But I guess this only works if I have 2.15CE installed on a harddisk? It would probably not work for a Live CD or USB stick.

I had some time to play around with the other tips which didn't help. I got it working after saving my 2.14 settings to harddisk and then booting 2.15CE just would like to find out what exactly is causing the problem.
GeoffB wrote:A quick and dirty fix for this problem. (Hard Drive Install)

Boot from a 2.14 disc.

Mount the partiton that 2.15CE is installed on.

Delete the following folders/files and replace them with the same folders/files from the 2.14 live install

/usr/bin/alsamixer
/usr/lib/ao/plugins-2/libalsa09.so
/usr/lib/alsa/lib
/usr/sbin/alsactl
/usr/sbin/alsawizard
/usr/share/alsa

Reboot into 2.15CE and alsaconf will work.

It's probably not necessary to replace all of these but not knowing which one is faulty it's easier to replace them all rather than trying them one at a time to find the culprit.

I hope this helps.

Geoff

basslord1124
Posts: 73
Joined: Tue 12 Dec 2006, 03:11

#9 Post by basslord1124 »

Yup, I had the same issue as well with the new 2.15. I have just copied my settings from the 2.14 modprobe.conf file over to the 2.15's modprobe file and it works fine. Other than that, 2.15 has been fine for me.
[url=http://groups.myspace.com/puppylinux]The Official Myspace Puppy Linux Group[/url]

paperaussie
Posts: 8
Joined: Thu 12 Apr 2007, 09:26

Re: Soundcard Problems 2.15CE

#10 Post by paperaussie »

At last I tried this quick and dirty fix as well because I wanted to burn a new clean LiveCD but this fix does not work on the Evo N600C notebook. Neither does the modification of modprobe.conf work or the patch suggested by WhoDo.

Thanks for the suggestions though.
GeoffB wrote:A quick and dirty fix for this problem. (Hard Drive Install)

Boot from a 2.14 disc.

Mount the partiton that 2.15CE is installed on.

Delete the following folders/files and replace them with the same folders/files from the 2.14 live install

/usr/bin/alsamixer
/usr/lib/ao/plugins-2/libalsa09.so
/usr/lib/alsa/lib
/usr/sbin/alsactl
/usr/sbin/alsawizard
/usr/share/alsa

Reboot into 2.15CE and alsaconf will work.

It's probably not necessary to replace all of these but not knowing which one is faulty it's easier to replace them all rather than trying them one at a time to find the culprit.

I hope this helps.

Geoff

tytower

#11 Post by tytower »

See my post in audio re no sound

Seems if your card is not legacy then you have the same problem as me .

Find what your sound card is and what driver it needs
ie mine was a "SiS 7018" built in board , it needed "snd-trident " driver so my fix was in a console run "modprobe snd-trident"

Then I did the alsa setup thing and my board came up recognised.

Post Reply