Re: Can't get audio to work
-BEGIN PGP SIGNED MESSAGE-
On Tuesday 18 June 2002 08:25 pm, Glen Lee Edwards wrote:
> > > in effigy. They won't blame Red Hat. After all, it was my
> > > decision to upgrade to 7.3. Not Red Hat's.
> >
> > Glen, could I interest you in apt-rpm ?? It's a rather sweet
> > package for your RH boxes.
>
> No. Downloading the rpms isn't the problem. The constant upgrades are.
> I need a stable operating system that allows me to upgrade individual
> packages instead of requiring that I upgrade the whole box. Red Hat
> clearly doesn't meet that requirement. Red Hat's problem is that
> they've gone commercial. In order to remain financially viable they
> now *have* to regularly put out upgrades.
>
> I have all the new 7.3 rpms on the hard drive. Some installed. Some
> won't. So have have a part 7.2, part 7.3 box with a lot of broken
> programs.
That's why I chimed in. Using apt-rpm, you can use all the commands
you've
grown comfy with in Debian. (e.g. apt-get update && apt-get upgrade,
apt-cache search {keyword}, etc) And the upgrades/updates are sweet. There
now are a number of new apt-rpm sites popping up (including /.) Here's a url
to wander thru..
http://apt-rpm.tuxfamily.org/
And for those wondering, NO! I DON'T WEAR THE HAT!! :--) I just support
linux wherever/whenever I can. :--)
>
> > Ouch! But, you DO have help. :--) My only request is "Purdy
> > Please!, no html mail"
>
> If I'm sending out html mail it's not by intent.
:--) Yer not, it's just that I've run into a couple of folks that used
'another box' and hotmail (or the likes) to write me while actually werking
on thier linux box. :--) Yer fine!
>
> > lspci shows that yes, you DO have the sound chip on your motherboard
> > and 'accessable". That's all. :--) So, let's see. Can you look at
> > "dmesg | less" and see if you can see what it says about the
> > initialization? THIS is where you'll see if the chipset was actually
> > activated.
>
> I see no reference in dmesg to anything audio, nor to IRQ 11, which is
> where lspci -vv says audio is located.
Then, somehow/someway the audio chip is STILL not being seen. There is
another thread running now about having to use the alsa drivers on the AC'97,
is this the same chipset you're calling? (it's early in my day and i don't
recall right now)
>
> Glen
- --
__
OutCast Computer Consultants of Central Oregon
http://outcast-consultants.redmond.or.us
[EMAIL PROTECTED]
(541) 504-1388 /\IRC: 205.227.115.251:6667:#OutCasts /\ICQ: UIN 138930
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
Since you're having to rebuild your kernel, check out the reference docs at http://www.alsa-project.org. If memory serves, you'll need to build the alsa modules as part of your kernel build. -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On 2002.06.18 23:59 Glen Lee Edwards wrote: On Tuesday 18 June 2002 12:41 am, you wrote: > The 'K7' builds are only for us who run AMD Athlons. I thought I > made this point in my previous message, but obviously not. Not sure what you mean. Last I heard the Duron, Thunderbird, and XP are all part of the Athlon product line. I have a 950 MHZ Duron with a Socket A motherboard. Hey Glen, I've got the same setup, and have successfully built and run K7-optimized kernels in the past. If you continue encountering problems w/ 2.4.18, your AC '97 audio device *is* supported with 2.2 kernels starting with 2.2.19 (I believe you mentioned you had 2.2.20 installed?), though the quality is not as good as the 2.4 incarnation. Good Luck, Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Tue, Jun 18, 2002 at 10:36:37PM -0500, Glen Lee Edwards wrote: > On Tuesday 18 June 2002 12:25 am, you wrote: > > As far as what's next, what happens when you try and play an mp3 > > file? Whether via xmms or mpg123, you should get some meaningful > > output. > > "Failed to open sound device." > > libstdc++-libc6.1-2.so.3: cannot open shared object file: No such file > or directory > libstdc++-libc6.1-2.so.3: cannot open shared object file: No such file > or directory That's in the libstdc++2.10 package, in case that helps. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Tuesday 18 June 2002 12:41 am, you wrote: > The 'K7' builds are only for us who run AMD Athlons. I thought I > made this point in my previous message, but obviously not. Not sure what you mean. Last I heard the Duron, Thunderbird, and XP are all part of the Athlon product line. I have a 950 MHZ Duron with a Socket A motherboard. > So when you do an 'apt-cache search asla-modules' (BTW, learn to love > apt-cache, it will save your skin many times), you get: > > coffee (steve)$ apt-cache search alsa-modules > alsa-modules-2.4.16-386 - Advanced Linux Sound Architecture (drivers) > alsa-modules-2.4.16-586 - Advanced Linux Sound Architecture (drivers) > alsa-modules-2.4.16-586tsc - Advanced Linux Sound Architecture > (drivers) alsa-modules-2.4.16-686 - Advanced Linux Sound Architecture > (drivers) alsa-modules-2.4.16-686-smp - Advanced Linux Sound > Architecture (drivers) alsa-modules-2.4.16-k6 - Advanced Linux Sound > Architecture (drivers) alsa-modules-2.4.16-k7 - Advanced Linux Sound > Architecture (drivers) alsa-modules-2.4.18-386 - Advanced Linux Sound > Architecture (drivers) alsa-modules-2.4.18-586tsc - Advanced Linux > Sound Architecture (drivers) alsa-modules-2.4.18-686 - Advanced Linux > Sound Architecture (drivers) alsa-modules-2.4.18-686-smp - Advanced > Linux Sound Architecture (drivers) alsa-modules-2.4.18-k6 - Advanced > Linux Sound Architecture (drivers) alsa-modules-2.4.18-k7 - Advanced > Linux Sound Architecture (drivers) > > So if you're running a pII or higher, you'll want to use the > alsa-modules-2.4.18-686 (this, of course, assumes that you're kernel > image comes from the package 'kernel-image-686'. So perhaps the > first order of business is determining which kernel image you're > using. Did you roll you own? If so, you'll have to rebuild with the Yes. I downloaded the tar.gz from kernel.org. I couldn't get the k7 dpkg to boot - said it couldn't mount the root file system. No matter how I messed with initrd= it still wouldn't do it. Compiling the source myself I was able to get 2.4.18 to boot without the initrd= section in lilo.conf. > alsa modules as well. If you're (as I am) lazy and installed from a > package, it will be a little less painful. I found out the hard way that it's not wise to wholly trust someone else with my system. On programs I *have* to rely on I'm getting away from relying on a pre-compiled package, and building them myself. > If you didn't builid you're own kernel, what shows up when you do > 'ls /lib/modules'? Let us know. $ ls /lib/modules 2.2.20 2.4.18 2.4.18-k6-2 2.4.18.COMPILE 2.4.18.KEEP The first two I can boot from. The k6 kernel is one I compiled on this box for my k6 pc. It takes about 30 minutes to compile it here, several hours on the k6 box. The latter two are for my personal reference to give me a frame of reference when I screw up a build. > Hang in there, chief. We'll get this figured out. ;) Thanks. I *really* appreciate the help. No matter which route I take, it would appear that the next step is to recompile the kernel. Heh, guess it's time to try the kpkg route. Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Tuesday 18 June 2002 12:25 am, you wrote: > As far as what's next, what happens when you try and play an mp3 > file? Whether via xmms or mpg123, you should get some meaningful > output. "Failed to open sound device." libstdc++-libc6.1-2.so.3: cannot open shared object file: No such file or directory libstdc++-libc6.1-2.so.3: cannot open shared object file: No such file or directory "Couldn't open audio. Please check that: 1) You have the correct output plugin selected 2) No other programs is blocking the soundcard 3) Your soundcard is configured properly" > One thing I forgot. 1) Make sure that you're a member of the 'audio' > group (type 'groups' at the command line to check this). 2) Make sure > that /dev/ dsp*, /dev/mixer*, and /dev/midi* (if you want) are > group-writable and that their ownerships are all set as belonging to > the 'audio' group. That's all set up correctly. Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
> > in effigy. They won't blame Red Hat. After all, it was my > > decision to upgrade to 7.3. Not Red Hat's. > > Glen, could I interest you in apt-rpm ?? It's a rather sweet > package for your RH boxes. No. Downloading the rpms isn't the problem. The constant upgrades are. I need a stable operating system that allows me to upgrade individual packages instead of requiring that I upgrade the whole box. Red Hat clearly doesn't meet that requirement. Red Hat's problem is that they've gone commercial. In order to remain financially viable they now *have* to regularly put out upgrades. I have all the new 7.3 rpms on the hard drive. Some installed. Some won't. So have have a part 7.2, part 7.3 box with a lot of broken programs. > Ouch! But, you DO have help. :--) My only request is "Purdy > Please!, no html mail" If I'm sending out html mail it's not by intent. > lspci shows that yes, you DO have the sound chip on your motherboard > and 'accessable". That's all. :--) So, let's see. Can you look at > "dmesg | less" and see if you can see what it says about the > initialization? THIS is where you'll see if the chipset was actually > activated. I see no reference in dmesg to anything audio, nor to IRQ 11, which is where lspci -vv says audio is located. Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
Glen Lee Edwards wrote: > > > It's written in geek. > > "The mainboard has a built-in AC'97 4Ch Codec, provides an AMR >slot..." > People consider this geek? sincerely, -- Ivo Wever [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
The 'K7' builds are only for us who run AMD Athlons. I thought I made this point in my previous message, but obviously not. So when you do an 'apt-cache search asla-modules' (BTW, learn to love apt-cache, it will save your skin many times), you get: coffee (steve)$ apt-cache search alsa-modules alsa-modules-2.4.16-386 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-586 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-586tsc - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-686 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-686-smp - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-k6 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.16-k7 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-386 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-586tsc - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-686 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-686-smp - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-k6 - Advanced Linux Sound Architecture (drivers) alsa-modules-2.4.18-k7 - Advanced Linux Sound Architecture (drivers) So if you're running a pII or higher, you'll want to use the alsa-modules-2.4.18-686 (this, of course, assumes that you're kernel image comes from the package 'kernel-image-686'. So perhaps the first order of business is determining which kernel image you're using. Did you roll you own? If so, you'll have to rebuild with the alsa modules as well. If you're (as I am) lazy and installed from a package, it will be a little less painful. If you didn't builid you're own kernel, what shows up when you do 'ls /lib/modules'? Let us know. Hang in there, chief. We'll get this figured out. ;) -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
> $ lspci > 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02) > 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev > d0) > 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 > 00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 > 10/100 Ethernet (rev 82) > 00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) > 00:01.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) > 00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] > SiS PCI Audio Accelerator (rev 02) > 00:01.6 Modem: Silicon Integrated Systems [SiS]: Unknown device 7013 > (rev a0) > 00:02.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP > 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] > SiS630 GUI Accelerator+3D (rev 31) > > I compiled the SiS audio module into the kernel. Question: does the > above actually state that I have an SiS audio card on the system, or > does it just state that I have a slot for a sound card? (Please no > rude comments from anyone. If I knew the answer to that question I > wouldn't have asked it). The above output indicates that you actually have the SiS sound card on the bus/device setup shown. As far as what's next, what happens when you try and play an mp3 file? Whether via xmms or mpg123, you should get some meaningful output. One thing I forgot. 1) Make sure that you're a member of the 'audio' group (type 'groups' at the command line to check this). 2) Make sure that /dev/ dsp*, /dev/mixer*, and /dev/midi* (if you want) are group-writable and that their ownerships are all set as belonging to the 'audio' group. HTH -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
> > "The mainboard has a built-in AC'97 4Ch Codec, provides an AMR > >slot..." > > Ah... now THIS is meaningful. I had a bear of a time getting this > identical piece of dung working on my otherwise "cherry" computer. > This next bit assumes that you're running sid. I don't know how it > is on potato. You'll need to download the 'alsa-drivers' packages > that matches your kernel-package version (e.g., I had to install > 'alsa-drivers-2.4.18-k7'). You'll also want to install the > 'alsaconf' package (although at last check, it was somewhat broken on > sid, we'll cross that bridge when we come to it). You'll want to > select the "VIA 82xxx" chipset stuff as the driver. Hopefully, this > will make things work. If not, send another message. Stephen, This creates other problems. apt-get returns the following: $ apt-get install alsa-modules-2.4.18-k7 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: alsa-base kernel-image-2.4.18-k7 The following NEW packages will be installed: alsa-base alsa-modules-2.4.18-k7 kernel-image-2.4.18-k7 0 packages upgraded, 3 newly installed, 0 to remove and 4 not upgraded. Need to get 798kB/9655kB of archives. After unpacking 26.9MB will be used. Do you want to continue? [Y/n] I've in the past installed kernel-image-2.4.18-k7, but it wouldn't boot, so I removed it and compiled the kernel from tar.gz from kernel.org, not (as|from) a deb package. I have to figure a way to download/install alsa-modules-2.4.18-k7 without installing the corresponding kernel-image. Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
-BEGIN PGP SIGNED MESSAGE- On Monday 17 June 2002 09:19 pm, Glen Lee Edwards wrote: > > Kent, I won't defend what I wrote, but by way of explanation: I had one > quality server (Red Hat) that crashed during upgrade a few weeks back. > It has several years of customizations and programming work on it that > I can't afford to lose. Unfortunately I didn't have the budget to buy > another quality server. So when the upgrade failed, I lost a lot of > the customizations, plus I have a couple hundred people who rely > heavily on that server wanting to burn me in effigy. They won't blame > Red Hat. After all, it was my decision to upgrade to 7.3. Not Red > Hat's. Glen, could I interest you in apt-rpm ?? It's a rather sweet package for your RH boxes. > > Being brand new to Debian, and in a real desperate situation here, I've > been trying to get the web sites, mail, mailman list program, MyPHPNuke > boards, etc., up and running. I've posted several letters to the list > asking for help in various areas. I've received some great replies. > But I've received just as many replies from idiots who left the subject > line of my letter the same but who wrote only to complain that > something was wrong with the way I posted the letter - no Reply-to: > field, line wrap not set at 72, real stupid stuff that has nothing to > do with my post. Can you imagine what it's like to be sitting here on > pins and needles desperately hoping for an answer from those > experienced with Debian so I can get the 200 irate people off my back, > only to open the letter to find someone bellyaching that my line wrap > isn't set to 72? That does very little positive for the disposition! > > Kent, there are people on this list who really need to get a life. Ouch! But, you DO have help. :--) My only request is "Purdy Please!, no html mail" > > > So, your next best bet is probably to search the Debian Mail List > > archives, and then to post specific questions to this list. However, > > So I can become the prime target at another turkey shoot? > Not by most of us! We've been down this sad, dark, lonely road. :--( > > to get you started, I offer the following suggestions. > > [snip] > $ lspci > 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02) > 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev > d0) > 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 > 00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 > 10/100 Ethernet (rev 82) > 00:01.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) > 00:01.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) > 00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] > SiS PCI Audio Accelerator (rev 02) > 00:01.6 Modem: Silicon Integrated Systems [SiS]: Unknown device 7013 > (rev a0) > 00:02.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP > 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] > SiS630 GUI Accelerator+3D (rev 31) > > I compiled the SiS audio module into the kernel. Question: does the > above actually state that I have an SiS audio card on the system, or > does it just state that I have a slot for a sound card? (Please no > rude comments from anyone. If I knew the answer to that question I > wouldn't have asked it). lspci shows that yes, you DO have the sound chip on your motherboard and 'accessable". That's all. :--) So, let's see. Can you look at "dmesg | less" and see if you can see what it says about the initialization? THIS is where you'll see if the chipset was actually activated. p.s. You might wanna use lspci -vv | less to get more information (just for YOU to look at while troubleshooting. The -vv equals VERY VERBOSE and dumps a squatload of info on each device. But what we have here now is fine for now. :--) > > Now what? > > Glen - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 /\IRC: 205.227.115.251:6667:#OutCasts /\ICQ: UIN 138930 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Monday 17 June 2002 06:54 pm, you wrote: > On Jun 17, Glen Lee Edwards wrote: > > Alex, > > > > I would like to thank you for your arrogant, obnoxious reply to my > > letter. > > no problem > > > It's people like you that keep Windows users using Windows. > > The reason I asked for a step by step howto for setting up sound is > > because I don't have a clue where to begin or what to look for. If > > I > > > > [snip winge winge wine wine] > > > > Please don't ever respond to my posts, even if you have the answer. > > I have better things to do with my time than to sort through your > > rudeness. > > consider it done, could you include a 'non-alex-reply' in your sig so > I can pass it more easily in my mail client? > > /me ponders, could put a filter in muttonce I get the darn POP > account working properly. > > Could you bear with me until this happens ta > > Alex Alex, Add the following to the top of your ~/.procmailrc file. It will kill any letters from me before you see them. :0 H * 15^0 [EMAIL PROTECTED] /dev/null Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
> Glen: Don't get your panties in a wad. It's easy to get offended on > email lists if you have a thin skin. Alex's posting was generally > accurate, if a bit harsh (although it didn't apply in this case > because you asked for a howto, not for direct help) . Ya gotta learn > to spot those smilies and weigh them more heavily than the hot words > in the posting. > > I'd encourage you two to kiss and make up, but I'm afraid the damage > has been done. Kent, I won't defend what I wrote, but by way of explanation: I had one quality server (Red Hat) that crashed during upgrade a few weeks back. It has several years of customizations and programming work on it that I can't afford to lose. Unfortunately I didn't have the budget to buy another quality server. So when the upgrade failed, I lost a lot of the customizations, plus I have a couple hundred people who rely heavily on that server wanting to burn me in effigy. They won't blame Red Hat. After all, it was my decision to upgrade to 7.3. Not Red Hat's. A couple of weeks back I found a special at PC Adventures - a bare bones computer for $179.00 US. AMD Duron 950 MHZ with floppy and built in 10/100 nic. No hd, cdrom, operating system nor memory. I swore after the last Red Hat crash that I'd never again install Red Hat, so this box has only seen Debian on it. Being brand new to Debian, and in a real desperate situation here, I've been trying to get the web sites, mail, mailman list program, MyPHPNuke boards, etc., up and running. I've posted several letters to the list asking for help in various areas. I've received some great replies. But I've received just as many replies from idiots who left the subject line of my letter the same but who wrote only to complain that something was wrong with the way I posted the letter - no Reply-to: field, line wrap not set at 72, real stupid stuff that has nothing to do with my post. Can you imagine what it's like to be sitting here on pins and needles desperately hoping for an answer from those experienced with Debian so I can get the 200 irate people off my back, only to open the letter to find someone bellyaching that my line wrap isn't set to 72? That does very little positive for the disposition! Kent, there are people on this list who really need to get a life. > So, your next best bet is probably to search the Debian Mail List > archives, and then to post specific questions to this list. However, So I can become the prime target at another turkey shoot? > to get you started, I offer the following suggestions. > Find out what sound card you have. According to your post above, it's > an AC'97 variant. It has been my experience that that's kind of a > general label, like having an Intel Pentium; do you mean Pentium > 5-120, or Pentium III, or what? To get more info, the "lspci" utility > is quite helpful. If you run it, you should see something like: > > Mon Jun 17 21:22:33 > --- > EnJaeLove[westk]:/home/westk> sudo lspci > Password: > 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] > System Controller (rev 12) > 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] > AGP Bridge > 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super > South] (rev 40) > 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) > 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 16) > 00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 16) > 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] > (rev 40) 00:07.5 Multimedia audio controller: VIA Technologies, Inc. > VT82C686 AC97 Audio Controller (rev 50) > 00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev > 20) 01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 > PF/PRO AGP 4x TMDS > > Notice that my sound "card" is also an AC'97, but more specifically > it's on a motherboard with a VIA chipset, and the sound chip is the > VT82C686. So I'd search the Debian Mailing Lists for "vt82c686". > > You'll find that there are several sound "solutions" floating around. > The two most common are OSS (Open Sound System) and ALSA (something > something something Architecture). If you want to try the OSS route, > I'd download the newest kernel source I felt comfortable with > (2.4.18) and compile a kernel with the appropriate module/built-in > support for the vt82c686 chipset. If you wanted to go the ALSA route, > you'd need to download some ALSA packages. I believe the ALSA > solution may be more newbie-friendly, but I'm not that conversant > with it. > > For now, I'd recommend you to run "lspci" and then post the results > here and see if anyone has any further suggestions. $ lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02) 00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) 00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 00:01.1 Ethernet controller: Silicon Inte
Re: Can't get audio to work
Glen Lee Edwards wrote: On Sunday 16 June 2002 06:03 pm, you wrote: On Jun 16, Glen Lee Edwards wrote: Is there a step-by-step howto of how to set up audio on Debian. If not, suggestions? please as a word of ettiqutte, in future post 'useful' problem reports. All that then happens is a generic response is sent out, which normally involves the reply containing information that should of been in the original e-mail. 'Requests' like this are normally passed over and ignored by mailing list/newsgroup roamers..you are lucky this time mear luser :) Alex, I would like to thank you for your arrogant, obnoxious reply to my letter. It's people like you that keep Windows users using Windows. "The mainboard has a built-in AC'97 4Ch Codec, provides an AMR slot..." Please don't ever respond to my posts, even if you have the answer. I have better things to do with my time than to sort through your rudeness. Glen Alex: You were a bit harsh with words like "luser". Glen asked for a howto; he didn't ask for a solution from the list. In such a situation, there's no need to post "'useful' problem reports". Glen: Don't get your panties in a wad. It's easy to get offended on email lists if you have a thin skin. Alex's posting was generally accurate, if a bit harsh (although it didn't apply in this case because you asked for a howto, not for direct help) . Ya gotta learn to spot those smilies and weigh them more heavily than the hot words in the posting. I'd encourage you two to kiss and make up, but I'm afraid the damage has been done. So on to your question: I don't know of any good howto for setting up sound on Debian. Sometimes www.debianplanet.com has good stuff that is Debian-specific, but my quick look-see there turned up nada. So, your next best bet is probably to search the Debian Mail List archives, and then to post specific questions to this list. However, to get you started, I offer the following suggestions. Find out what sound card you have. According to your post above, it's an AC'97 variant. It has been my experience that that's kind of a general label, like having an Intel Pentium; do you mean Pentium 5-120, or Pentium III, or what? To get more info, the "lspci" utility is quite helpful. If you run it, you should see something like: Mon Jun 17 21:22:33 --- EnJaeLove[westk]:/home/westk> sudo lspci Password: 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] System Controller (rev 12) 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 [IGD4-1P] AGP Bridge 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) 00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) 00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 16) 00:07.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) 00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) 00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20) 01:05.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS Notice that my sound "card" is also an AC'97, but more specifically it's on a motherboard with a VIA chipset, and the sound chip is the VT82C686. So I'd search the Debian Mailing Lists for "vt82c686". You'll find that there are several sound "solutions" floating around. The two most common are OSS (Open Sound System) and ALSA (something something something Architecture). If you want to try the OSS route, I'd download the newest kernel source I felt comfortable with (2.4.18) and compile a kernel with the appropriate module/built-in support for the vt82c686 chipset. If you wanted to go the ALSA route, you'd need to download some ALSA packages. I believe the ALSA solution may be more newbie-friendly, but I'm not that conversant with it. For now, I'd recommend you to run "lspci" and then post the results here and see if anyone has any further suggestions. Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
> I would like to thank you for your arrogant, obnoxious reply to my > letter. It's people like you that keep Windows users using Windows. I think you might have misinterpreted Alex's comments. I think he was trying to give you a good-natured ribbing more than anything else. Usually when people pepper their email with smilies, they're not trying to be rude. :) > "The mainboard has a built-in AC'97 4Ch Codec, provides an AMR >slot..." Ah... now THIS is meaningful. I had a bear of a time getting this identical piece of dung working on my otherwise "cherry" computer. This next bit assumes that you're running sid. I don't know how it is on potato. You'll need to download the 'alsa-drivers' packages that matches your kernel-package version (e.g., I had to install 'alsa-drivers-2.4.18-k7'). You'll also want to install the 'alsaconf' package (although at last check, it was somewhat broken on sid, we'll cross that bridge when we come to it). You'll want to select the "VIA 82xxx" chipset stuff as the driver. Hopefully, this will make things work. If not, send another message. HTH -- Stephen W. Juranich [EMAIL PROTECTED] Electrical Engineering http://students.washington.edu/sjuranic University of Washingtonhttp://ssli.ee.washington.edu/ssli -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Jun 17, Glen Lee Edwards wrote: > > Alex, > > I would like to thank you for your arrogant, obnoxious reply to my > letter. > no problem > It's people like you that keep Windows users using Windows. > The reason I asked for a step by step howto for setting up sound is > because I don't have a clue where to begin or what to look for. If I > > [snip winge winge wine wine] > > Please don't ever respond to my posts, even if you have the answer. I > have better things to do with my time than to sort through your > rudeness. > consider it done, could you include a 'non-alex-reply' in your sig so I can pass it more easily in my mail client? /me ponders, could put a filter in muttonce I get the darn POP account working properly. Could you bear with me until this happens ta Alex -- / Fortune finishes the great quotations, \ | #12| || | Those who can, do. Those who can't,| \ write the instructions./ \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || pgp2X5ciYioXY.pgp Description: PGP signature
Re: Can't get audio to work
On Sunday 16 June 2002 06:03 pm, you wrote: > On Jun 16, Glen Lee Edwards wrote: > > I can't get audio to work. I have the following sound card that is > > built into the motherboard: > > > >Multimedia audio controller: Silicon Integrated Systems [SiS] > > SiS PCI Audio Accelerator (rev 02) > > > > I have the driver for it compiled into the kernel (2.4.18). > > > > I have added myself to the audio group. > > > > Is there a step-by-step howto of how to set up audio on Debian. If > > not, suggestions? > > maybe a description of what happens when you try to play a tune. I > would personnaly recommend compiling as a module so you can > load/unload as you please for experimentation. > > Do you see a sound card entry in /proc/interupts, /proc/ioports or > /proc/dma? > > what happens if you do: > > cat /dev/urandom > /dev/dsp > > do you get static or not, an error message, for heavens sake man give > us something? :) > > If you get no error message or strange 'hung' style noises you > probably just have your mixer settings right down low (or > muted)..install 'nmixer' or something similar and try again with > the mixer settings dealt with. > > Can you see the mixer settings. > > please as a word of ettiqutte, in future post 'useful' problem > reports. All that then happens is a generic response is sent out, > which normally involves the reply containing information that should > of been in the original e-mail. 'Requests' like this are normally > passed over and ignored by mailing list/newsgroup roamers..you > are lucky this time mear luser :) Alex, I would like to thank you for your arrogant, obnoxious reply to my letter. It's people like you that keep Windows users using Windows. The reason I asked for a step by step howto for setting up sound is because I don't have a clue where to begin or what to look for. If I could have provided you with all the answers to your questions before you asked them, I wouldn't have needed your help, now, would I? When I used Red Hat I didn't need to ask how to set sound up. It worked from the get go. That isn't the case with Debian. So now I need a complete tutorial from a-z on how sound works in Linux so I can trouble shoot. It might be Debian. It might be the computer. This is a new computer. I'm not even sure it came with a sound card. But I don't know how to find out. Don't tell me to read the documentation that came with it. It's written in geek. "The mainboard has a built-in AC'97 4Ch Codec, provides an AMR slot..." Please don't ever respond to my posts, even if you have the answer. I have better things to do with my time than to sort through your rudeness. Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't get audio to work
On Jun 16, Glen Lee Edwards wrote: > > I can't get audio to work. I have the following sound card that is > built into the motherboard: > >Multimedia audio controller: Silicon Integrated Systems [SiS] SiS > PCI Audio Accelerator (rev 02) > > I have the driver for it compiled into the kernel (2.4.18). > > I have added myself to the audio group. > > Is there a step-by-step howto of how to set up audio on Debian. If > not, suggestions? > maybe a description of what happens when you try to play a tune. I would personnaly recommend compiling as a module so you can load/unload as you please for experimentation. Do you see a sound card entry in /proc/interupts, /proc/ioports or /proc/dma? what happens if you do: cat /dev/urandom > /dev/dsp do you get static or not, an error message, for heavens sake man give us something? :) If you get no error message or strange 'hung' style noises you probably just have your mixer settings right down low (or muted)..install 'nmixer' or something similar and try again with the mixer settings dealt with. Can you see the mixer settings. please as a word of ettiqutte, in future post 'useful' problem reports. All that then happens is a generic response is sent out, which normally involves the reply containing information that should of been in the original e-mail. 'Requests' like this are normally passed over and ignored by mailing list/newsgroup roamers..you are lucky this time mear luser :) Alex -- __ / He who fears the unknown may one day \ | flee from his own backside. | | | \ -- Sinbad/ -- \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || pgpUnmu8xQf3l.pgp Description: PGP signature
Can't get audio to work
I can't get audio to work. I have the following sound card that is built into the motherboard: Multimedia audio controller: Silicon Integrated Systems [SiS] SiS PCI Audio Accelerator (rev 02) I have the driver for it compiled into the kernel (2.4.18). I have added myself to the audio group. Is there a step-by-step howto of how to set up audio on Debian. If not, suggestions? Glen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
