!!!!!FIXED!!!No audio from Dell Latitude CPI using Puppy 4.2

Problems and successes with specific brands/models of computer audio hardware
Message
Author
User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

!!!!!FIXED!!!No audio from Dell Latitude CPI using Puppy 4.2

#1 Post by Eathray »

I've been reviving an old laptop, dell latitude cpi with 300 p2.

I boot puppy from live cd. Haven't found a way to get the sound working. Alsa config doesn't seem to be up to the challenge.

Hoping there might be a patch or something to get it to configure the sound.

Warning: I'm ignorant to Linux. Technical words may hurt me.
Last edited by Eathray on Wed 16 Sep 2009, 14:31, edited 2 times in total.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#2 Post by Aitch »

Hi Earthray

there was a recent post about this, maybe you can try some of the suggestions...?

http://www.murga-linux.com/puppy/viewtopic.php?p=330077

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

thanks

#3 Post by Eathray »

Wow. You guys are clearly a good deal brighter than me. I used to think I was pretty bright because of how proficient I've become with Windows.

I do not understand 9/10's of what was said there, but I'll keep looking at it. One of the replies had some pretty straightforward directions I think I can follow.

thanks again.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#4 Post by Aitch »

Hi I pm'd ttuuxxx about this, to see if his updated 214R might be better for you

He has added drivers, but also made a .pet for the new alsa [sound controller] which you could try also

214xx - 2 series latest updates - better for older pc's

http://www.murga-linux.com/puppy/viewtopic.php?t=42553

alsa

http://www.puppylinux.asia/tpp/ttuuxxx/ ... 0-i386.pet

http://www.puppylinux.asia/tpp/ttuuxxx/ ... 0-i386.pet

good luck

PS: bookmark this

http://www.wellminded.com/puppy/pupsearch.html

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

A small step, Bios

#5 Post by Eathray »

Okay, so I made a first step:

I upgraded my bios from A03 to A12...
A terrifying experience with warnings throughout the process. What if there's a power failure? OMG! I can't take the pressure!

Success. No power failure. I did not accidently kick the power cord out. The thing practically did itself. Thank God Dell doesn't trust the user!

Okay, in a bit, I will reboot puppy and see what happens.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#6 Post by Aitch »

I like a gambler :lol:

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

Bios success but link access problem

#7 Post by Eathray »

I tried the two links to puppylinuxasia, but I do not have access. Now what do I do?

Puppy booted fine in the new bios, by the way. I haven't noticed much of a difference... maybe just a little faster boot time for both my systems, puppy and win2k.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#8 Post by Aitch »

I tried the two links to puppylinuxasia, but I do not have access. Now what do I do?
login...user=puppy password=linux

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

Is there a tool for this?

#9 Post by Eathray »

Somebody please tell me there's a tool, widget or utility that can help me fix this sound thing. Audio I believe is legacy with soundblaster drivers. :cry:

Step-by-step instructions would help too...

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

oh, cool

#10 Post by Eathray »

Thanks. I'll try again. :?

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#11 Post by Aitch »

Best suggestion, if the version change/ alsa.pets don't help

pm tempestuous - it's his speciality

http://www.murga-linux.com/puppy/privms ... post&u=217

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

thanks

#12 Post by Eathray »

You're cool man, Although why you're helping me at 2am UK time is beyond me :D

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

downloaded files

#13 Post by Eathray »

So I downloaded the files using the default pup-get, which installed, and now it says to reboot. So here I go. I'm not sure what to expect on the other side. :?

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

not sure what to do next

#14 Post by Eathray »

I downloaded the files and rebooted. Not sure what to do now. don't really notice any difference. still no sound. should I run the utility again?

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

no progress

#15 Post by Eathray »

so I run alsaconfig again and like all the times before, it gets stuck trying to probe SB16 (SoundBlaster). Sits there and does nothing.

User avatar
Aitch
Posts: 6518
Joined: Wed 04 Apr 2007, 15:57
Location: Chatham, Kent, UK

#16 Post by Aitch »

I downloaded the files and rebooted. Not sure what to do now. don't really notice any difference. still no sound. should I run the utility again?
Sit Heel Speak wrote:
cegil wrote:...but I don't know what to do or which/what to run
Here's what works for me:

Download all three of the dot-pets provided above, then install them in the order shown below:

For each one, go

1. Right-click "Download" in the forum dialog box.

2. Open in New Tab.

3. A dialog box willl appear, titled "Opening alsa...pet"
--Left-click "Save it to disk," then "OK"

4. On the first one (choose ALSA-lib-1.0.12rc1.pet), do the following (not necessary on the two others):
--Click "Browse for other folders"
--Click "root" button, then "my-applications", then "Save" (if you are in 2.14 using the jwm windowmanager, you may have to drag the window up a bit to see the "Save" button).

5. On the second two (alsaconf-original.pet and ALSA-utils-1.0.12rc1.pet), just click Save, the dialog box will already point to /root/my-applications.

6. After you download all three, now open a Rox window, go to /root/my-applications, and left-click-and-install them in this order:

ALSA-lib-1.0.12rc1.pet
alsaconf-original.pet
ALSA-utils-1.0.12rc1.pet

7. Menu - Shutdown - Restart X Server.

8. Menu - Utility - rxvt and issue the command

fixmenus

9. Again do Menu - Shutdown - Restart X Server.

Now you can do Menu - Setup - ALSA sound wizard.

I've tried this on a P3 running 2.14 and a P4 running 2.15CE-Final (patched) and it works; the P3 had the can't-find-ESS1868-ISA-card issue, and this cures it. Please note that it does take a few seconds for the "Driver Selection" window to appear, if you don't have a PCI card and choose to "Probe ISA cards."

HTH,
SHS
thread

http://www.murga-linux.com/puppy/viewto ... 400#110400


SHS had a different sound card, and the .pets maybe earlier?, but what he did, including 'fixmenus', should work for you.....

....then try the new alsa


If you run

Code: Select all

lspci
in a console, it should list your devices to determine if the soundcard is getting recognised

soundcards can be notoriously tricky as many different chipsets were used on the same cards

we need to know exactly what is being seen, if any, as to why its trying to load SB driver - that's a legacy ISA device I think??

post the output of lspci here

did you try the 214x9 by ttuuxxx?

I had a reply from him, -I think he believes sound will be ok, but he's not familiar with your PC and doesn't have one for testing, so, you are his guineapig tester... :wink:

Aitch :)

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

thanks

#17 Post by Eathray »

I'm gonna try it after work. cool thanks.

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

followed directions, still no sound

#18 Post by Eathray »

Okay, I followed the directions given to cecil, but no good. the alsaconfig behaved a little differently this time and went directly to asking if I wanted to probe legacy (as apposed to making me select it from a list), so it seems to know what it is now anyway, but still no sound.

I suppose I should ask, how long does it take to probe? It sat there for twenty minutes doing nothing, and the curser doesn't blink as if it were busy. It just seems to get stuck there. Is there a setting in the bios I need to change? there was talk of that in an earlier reply, but I didn't understand it.

Help! :cry:

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

Ispci

#19 Post by Eathray »

All it said was:

bash: Ispci: command not found

I have no idea what that means.

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

the 214's

#20 Post by Eathray »

Yah, I tried those files. Those are the ones I had to ask you for the access codes. Didn't get anywhere, but the pet installer ran those instead of me like in the Cecil proceedure I just tried. Not getting anywhere.

Post Reply