Re: Steps to Sound
On Wed, Apr 25, 2001 at 11:00:02PM -0600, John Galt wrote:
> On Thu, 26 Apr 2001, Atukunda Martin wrote:
>
> >Yes,
> >On Wed, Apr 25, 2001 at 10:22:09PM -0600, John Galt wrote:
> >> On Wed, 25 Apr 2001 aphro@portal.aphroland.org wrote:
> >> >> Martin wrote:
> >> >> Hi everyone,
> >> >>
> >> >> I'd like to set up sound on my debian system. It is one of those IBM
> >> >> 300GL machines that come with (I think) an onboard sound card.
> >> >> Funny though is that the KDE CD player kscd plays fine when I insert a
> >> >> music CD into the drive.
> >> >> I added sound in my /etc/modules file but this doesn't seem to work.
> >> >
> >> >first thing is to determine EXACTLY what kind of soundchip
> >> >is on your soundcard. rip open the system and take a look.
> >>
> >>
> >> Easier way to find out PCI cards: lspci....
> >
> >lspci gives:
> >
> >root@fot2:~# lspci
> >00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev c4)
> >00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
> >00:02.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Apollo PRO] (rev 12)
> >00:02.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
> >00:02.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 08)
> >00:02.3 Host bridge: VIA Technologies, Inc.: Unknown device 3050 (rev 20)
> ^^^^^^^^^^^^mobo stuff
>
>
> >00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RT8029(AS)
> >00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RT8139 (rev 1
> ^^^^^^NICs
>
> >00:12.0 Multimedia audio controller: ESS Technology: Unknown device 1988 (rev 10)
> >01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04)
> ^^^^^^^video
>
>
> >root@fot2:~#
> >
> >I guess it is the second last listed device '00:12.0 Multimedia ... '
>
> It probably is the ESS. This means it's probably a Solo, Maestro, or an
> Allegro, but a straight SB compatible isn't ruled out (ESS built the
> first SB chipsets and can make them ala AMD/Intel). This implies one
> of the following modules:
>
> esssolo1
> es1370
> es1371
> sb
>
> Now, what I would do is just get a recent prepackaged kernel and start
> "easter egging" the four or so modules. modprobe each one in turn until
> one installs without error: that's your module.
when I run modprobes I get the following:
root@fot2:~# modprobe esssolo1
/lib/modules/2.2.18pre21/misc/esssolo1.o: init_module: Device or resource busy
Hint: this error can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.18pre21/misc/esssolo1.o: insmod /lib/modules/2.2.18pre21/misc/esssolo1.o failed
/lib/modules/2.2.18pre21/misc/esssolo1.o: insmod esssolo1 failed
roo@fot2:~# modprobe ess1370
/lib/modules/2.2.18pre21/misc/es1370.o: init_module: Device or resource busy
Hint: this error can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.18pre21/misc/es1370.o: insmod /lib/modules/2.2.18pre21/misc/es1370.o failed
/lib/modules/2.2.18pre21/misc/es1370.o: insmod es1370 failed
roo@fot2:~# modprobe es13701
/lib/modules/2.2.18pre21/misc/es1371.o: init_module: Device or resource busy
Hint: this error can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.18pre21/misc/es1371.o: insmod /lib/modules/2.2.18pre21/misc/es1371.o failed
/lib/modules/2.2.18pre21/misc/es1371.o: insmod es1371 failed
fot2:~# modprobe sb
/lib/modules/2.2.18pre21/misc/sb.o: init_module: Device or resource busy
Hint: this error can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.2.18pre21/misc/sb.o: insmod /lib/modules/2.2.18pre21/misc/sb.o failed
/lib/modules/2.2.18pre21/misc/sb.o: insmod sb failed
fot2:~#
I even tried others like the maestro, awe32 etc.
> Then edit /etc/modules
> and put in the module that worked. This will then load the module every
> time you boot. Don't worry about sound and soundcore: they'll come along
> for the ride with your soundcard's module. HTH
>
> > >if its a PCI soundcard you may be able to cheat by downloading
> >> >the demo of the commercial OSS and install it, it may auto
> >> >detect the card and show you what it is, then you can use
> >> >OSS or you can ditch it and keep the info it gave you.
> >
> >Where do I get the demo of the commercial OSS that nate suggests I try?
>
> Somewhere not in Debian. If you need to go for other tools, go for the
> DFSG free ALSA...
please explain this DFSG free ALSA in slightly more detail.
Martin
Reply to: