Re: a sound question

[José Alburquerque]

Mark Grieveson wrote:

If I recall correctly, the module  lines were something like:

alias snd-card-0 snd-fm801
options snd-fm801 index=0
alias snd-card-1 
options  index=1

 represents the second module for a second "soundcard" to be 
loaded in the kernel at the same time.


Do you think this would work for you?  HTH.

--
Sincerely
Jose Alburquerque 


Thanks Jose.  When I first tried this, it did not work properly.  But, 
after a recent upgrade, I'm please to say that both the soundcard, and 
the usb-device-audio (skype phone) now work.


Mark


Excellent.  Happy computing. :-)

--
Sincerely
Jose Alburquerque


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a sound question

[Mark Grieveson]

Mark Grieveson wrote:
Hi everyone.  I have a usb-audio-device (aka a skype phone), and a 
couple of speakers plugged into my regular soundcard.  I can get 
sound out of either device separately, but not both.   I feel that I 
should be able to use both the soundcard, and the usb-audio-device at 
the same time

Mark




I sort of remember seeing in the list a way by which more than one 
"soundcard" can be loaded in the kernel at the same time.  If your usb 
device is "like" a soundcard, maybe this is possible for you.


If I recall correctly, the module  lines were something like:

alias snd-card-0 snd-fm801
options snd-fm801 index=0
alias snd-card-1 
options  index=1

 represents the second module for a second "soundcard" to be 
loaded in the kernel at the same time.


Do you think this would work for you?  HTH.

--
Sincerely
Jose Alburquerque 


Thanks Jose.  When I first tried this, it did not work properly.  But, 
after a recent upgrade, I'm please to say that both the soundcard, and 
the usb-device-audio (skype phone) now work.


Mark


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a sound question

[José Alburquerque]

Mark Grieveson wrote:
Hi everyone.  I have a usb-audio-device (aka a skype phone), and a 
couple of speakers plugged into my regular soundcard.  I can get sound 
out of either device separately, but not both.   I feel that I should 
be able to use both the soundcard, and the usb-audio-device at the 
same time (chat with Skype, while listening to music, for instance).  
Does anyone know how I might be able to do this?  I use Etch, with the 
latest updated kernel (2.6.17), and the desktop environment is KDE 
(though changing to Gnome is fine, if required).


Mark


As I understand it, isn't a usb-audio-device like a soundcard to the 
kernel?  If that's the case, is it that you can't have both your 
soundcard and your usb-audio-device active in the kernel at the same 
time?  In other words, is it that you can't load the modules for your 
soundcard and the modules for your usb device at the same time in the 
kernel?


I sort of remember seeing in the list a way by which more than one 
"soundcard" can be loaded in the kernel at the same time.  If your usb 
device is "like" a soundcard, maybe this is possible for you.


If I recall correctly, the module  lines were something like:

alias snd-card-0 snd-fm801
options snd-fm801 index=0
alias snd-card-1 
options  index=1

 represents the second module for a second "soundcard" to be loaded 
in the kernel at the same time.


Do you think this would work for you?  HTH.

--
Sincerely
Jose Alburquerque


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: a sound question

[Andrew Sackville-West]

On Wed, Dec 06, 2006 at 11:20:01PM -0500, Mark Grieveson wrote:
> Hi everyone.  I have a usb-audio-device (aka a skype phone), and a 
> couple of speakers plugged into my regular soundcard.  I can get sound 
> out of either device separately, but not both.   I feel that I should be 
> able to use both the soundcard, and the usb-audio-device at the same 
> time (chat with Skype, while listening to music, for instance).  Does 
> anyone know how I might be able to do this?  I use Etch, with the latest 
> updated kernel (2.6.17), and the desktop environment is KDE (though 
> changing to Gnome is fine, if required).


I suspect, that unless your soundcard actually has two devices
incorporated into it, that you cannot get two different sounds out of
two different outputs. you'll probably need two soundcards to do this.

A


signature.asc
Description: Digital signature

a sound question

[Mark Grieveson]

Hi everyone.  I have a usb-audio-device (aka a skype phone), and a 
couple of speakers plugged into my regular soundcard.  I can get sound 
out of either device separately, but not both.   I feel that I should be 
able to use both the soundcard, and the usb-audio-device at the same 
time (chat with Skype, while listening to music, for instance).  Does 
anyone know how I might be able to do this?  I use Etch, with the latest 
updated kernel (2.6.17), and the desktop environment is KDE (though 
changing to Gnome is fine, if required).


Mark


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again... (Sound now working)

[Andrea Vettorello]

On Thu, 18 Nov 2004 11:46:51 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Just in case anyone can use the two bits of information I turned up...
> 
> Having tried everything I could find to try to make the OSS
> ("i810_audio") driver work, based on what little information I
> could find about it in the docs or online , I finally gave up
> and compiled and installed Alsa drivers for my 2.4.18-bf2.4 kernel.
> 
> Then, by using "alsamixer" and unmuting the usual suspects, I was able
> to
> get sound working.
> 
> None of the other mixers I had previously installed ("aumix", "kmix",
> and "xamixer2" (which crashed completely)) would enable sound to work.
> One point of interest was that the "alsamixer" GUI has a "slider" for
> "headphone", which none of the other mixers have, and which was what
> I discovered by trial and error to be what controlled the sound output
> jack on my MB.
> 
> I'm wondering if the "i810_audio" OSS driver was really at fault or if
> the
> "mixers" I was using with it were just incapable of controlling the
> output
> to the jack on my motherboard (and more significantly, how one could
> make such a determination).  But, I gather there's no way do diagnose
> such things, so I guess I'll just "Move On".
> 
> I am disappointed, saddened, troubled, disheartened, and discouraged
> (did
> I miss any?) that it was only possible to get this working by trial
> and error.  Auto mechanics discriminate between real mechanics who
> troubleshoot problems and fix them, and "parts replacers" who, just
> keep on replacing things (and charging the customer for it)
> until something works.  The latter are generally considered
> by their cow orkers to be subhumans at best.  If there's no way
> to actually troubleshoot these problems, and we have to resort to
> swapping
> modules in and out until something works, we're no better than the
> "parts replacers".
> 

IIRC, the 2.4.18-bf2.4 is one of the kernel used in the Woody boot
floppy, so for space restriction and compatibility measures, his scope
is only to have a bare system up and running, it doesn't have all the
modules a default kernel sports.

You can really troubleshoot the problems, the sources are out there,
you only need the HW documentation on how your hardware works, but
usually HW vendors don't cooperate, and here i'm not talking about
asking for HW drivers, but only HW specs or documentations.


Andrea


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again... (Sound now working)

[listcomm]

Just in case anyone can use the two bits of information I turned up...

Having tried everything I could find to try to make the OSS
("i810_audio") driver work, based on what little information I
could find about it in the docs or online , I finally gave up
and compiled and installed Alsa drivers for my 2.4.18-bf2.4 kernel.

Then, by using "alsamixer" and unmuting the usual suspects, I was able
to
get sound working.

None of the other mixers I had previously installed ("aumix", "kmix",
and "xamixer2" (which crashed completely)) would enable sound to work.
One point of interest was that the "alsamixer" GUI has a "slider" for
"headphone", which none of the other mixers have, and which was what
I discovered by trial and error to be what controlled the sound output
jack on my MB.

I'm wondering if the "i810_audio" OSS driver was really at fault or if
the
"mixers" I was using with it were just incapable of controlling the
output
to the jack on my motherboard (and more significantly, how one could
make such a determination).  But, I gather there's no way do diagnose
such things, so I guess I'll just "Move On".

I am disappointed, saddened, troubled, disheartened, and discouraged
(did
I miss any?) that it was only possible to get this working by trial
and error.  Auto mechanics discriminate between real mechanics who
troubleshoot problems and fix them, and "parts replacers" who, just
keep on replacing things (and charging the customer for it)
until something works.  The latter are generally considered
by their cow orkers to be subhumans at best.  If there's no way
to actually troubleshoot these problems, and we have to resort to
swapping
modules in and out until something works, we're no better than the
"parts replacers".


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again...

[listcomm]

>> i810_audio 21248   0 
>> ac97_codec  9568   0  [i810_audio]
>> soundcore   3236   2  [i810_audio]

>What kernel version is this? 

2.4.18-bf2.4   (sorry, should have included that originally)

>How recent is the alsaconf package?
>
>If you try unloading all OSS modules (including all three above)
>and then run alsaconf does it work then? Try commenting the above
>modules out from being loaded, then reboot to be totally clean,
>and *then* (without these modules having been loaded at all) run
>alsaconf.

I haven't tried switching to ALSA yet.

I really would like to (a) be sure that the i810_audio driver really
is inoperable with the setup I have, (b) have some reason to believe
that the ALSA drivers will work, before switching drivers.

It seems to me that there should be some way to *troubleshoot* this
problem, rather than just trying one thing after another until I either
find something that works or just give up - I mean, isn't that the
advantage to having open source?

Is the "i810_audio" driver known to be inoperative with my combination
of processor/chipset/etc., or is the ALSA setup known to work?

>This is what did it for me. I have a different card but you can
>see what I did at
>http://dione.no-ip.org/~alexis/computing/ahdg/ahdg/node58.html
>(Look this week 'cos the document will be upgraded this weekend
>and node numbering is bound to change.)

Thanks...  I saved a copy of it.  (I'm amassing quite a collection of
"sound setup" sections from Linux port Web pages).

These responses don't seem to be threading on the list, so I'm copying
people at their private email addresses; my apologies for the
redundancy.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again...

[Alexis Huxley]

> i810_audio 21248   0 
> ac97_codec  9568   0  [i810_audio]
> soundcore   3236   2  [i810_audio]

What kernel version is this? 

How recent is the alsaconf package?

If you try unloading all OSS modules (including all three above)
and then run alsaconf does it work then? Try commenting the above
modules out from being loaded, then reboot to be totally clean,
and *then* (without these modules having been loaded at all) run
alsaconf.

This is what did it for me. I have a different card but you can
see what I did at
http://dione.no-ip.org/~alexis/computing/ahdg/ahdg/node58.html

(Look this week 'cos the document will be upgraded this weekend
and node numbering is bound to change.)

Hope that helps ...

Alexis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again...

[listcomm]

>lsmod? Does your driver show up?

Yes...  following is snipped from "lsmod" output:

i810_audio 21248   0 
ac97_codec  9568   0  [i810_audio]
soundcore   3236   2  [i810_audio]

>In syslog, does it get activated? Like:
>debian kernel: ad1848/cs4248 codec driver Copyright (C) by Hannu Savolainen 
>1993-1996

*NO*, I do not see anything like that in "syslog"...  The only kernel
messages there
are:

Nov  8 18:10:03 dork kernel: CSLIP: code copyright 1989 Regents of the
University of California
Nov  8 18:10:03 dork kernel: PPP generic driver version 2.4.1
Nov  8 18:10:04 dork kernel: PPP BSD Compression module registered
Nov  8 18:10:04 dork kernel: PPP Deflate Compression module registered
Nov  8 18:10:05 dork kernel: ip_tables: (C) 2000-2002 Netfilter core
team
Nov  8 18:10:12 dork kernel: ip_conntrack (4095 buckets, 32760 max)

But there are several modules listed in "/etc/modules", all of them
except the "i810_audio" driver having been put there by the Debian
install,

usb-uhci
input
usbkbd
keybdev
lp
i810_audio

and none of the others show up as kernel messages either.

Is that an issue?  Should I be getting a kernel message for drivers not
built
into the kernel (loaded via "/etc/modules")?

> Also, if the answer to the above is affirmative, there is no sound as root?

There's no sound as root either (already ran into the file permission
problem...)

Thanks for your response --  any ideas?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Oh, NO! Not that same "No Sound" question again...

[Hugo Vanwoerkom]

[EMAIL PROTECTED] wrote:
Yeah, that same "No Sound" question again.  But I can't find
an answer that's gotten my sound working anywhere, so I'll give
this list a try.
I have an Intel 82820 (Camino 2) chipset and a stable Woody.
I've installed the "i810_audio" driver (via "/etc/modules").
"lspci" output looks OK.  both "/dev/audio" and "/dev/dsp" are
there.  I don't see any sound-related (at least to my ability
to determine) error messages in the log files.  Sound works OK
in Windoze.  I don't get any sound when I "cat" a ".wav" or
".au" file to either "/dev/audio" or "/dev/dsp".  I've tried both
"kmix" and "aumix", to make sure sound isn't muted,and neither
makes any difference.
lsmod? Does your driver show up?
In syslog, does it get activated? Like:
debian kernel: ad1848/cs4248 codec driver Copyright (C) by Hannu 
Savolainen 1993-1996

Also, if the answer to the above is affirmative, there is no sound as root?
H.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Oh, NO! Not that same "No Sound" question again...

[listcomm]

Yeah, that same "No Sound" question again.  But I can't find
an answer that's gotten my sound working anywhere, so I'll give
this list a try.

I have an Intel 82820 (Camino 2) chipset and a stable Woody.
I've installed the "i810_audio" driver (via "/etc/modules").
"lspci" output looks OK.  both "/dev/audio" and "/dev/dsp" are
there.  I don't see any sound-related (at least to my ability
to determine) error messages in the log files.  Sound works OK
in Windoze.  I don't get any sound when I "cat" a ".wav" or
".au" file to either "/dev/audio" or "/dev/dsp".  I've tried both
"kmix" and "aumix", to make sure sound isn't muted,and neither
makes any difference.

I have not "Tried" the ALSA drivers.  I don't like "Trying" things
to see if they work - I like DEBUGGING things.  (I'm a little testy
about that because of all the random flailing I've been reading about
on the net, by people trying anything and everything to get their
sound working.)

Questions:

(1) Does anyone know how to get this particularly configuration to
work?  I.e., if there is anyone who has had success with this exact
configuration, please tell me what I'm missing here.

More specifically,

(2) Is it possible that doing a "cat" of a sound file directly to
"/dev/audio" or "/dev/dsp" simply won't work, and that I need Yet
Another Driver ("/dev/mixer" or "/dev/sound", FI (neither of which
I have)) to make sound work with this setup?  Should the "mixer"
utilities even have any effect when I try to "cat" a file directly
to the driver?

(2) Is there a patch or updated "i810_audio" driver for this chipset
(and if so, where should I have searched for it, since I've already
searched and haven't found anything)?  (As a related issue, I'm not
sure how to determine the exact version of the driver I'm running
- I haven't seen it in "lsmod" or in the system log files, etc.,
but maybe I've missed it).

(3) Is there any *specific*, KNOWN reason to think that it is
*impossible* to get this combination working with the "i810_audio"
driver?

(4) Correspondingly, is it *known* to work with the ALSA drivers?

(5) Is there any solid reason to try compiling and installing the
"i810_audio" driver from source (I've been loading the "i810_audio.o"
out of the "/lib" tree; I'm assuming, however accurately, that it
corresponds to the source from which the kernel was built, since
I loaded it all off the Debian CD-ROMs)?

(6) I notice that OSS also *sells* drivers...  is there any reason
to expect that whatever I might buy from them, can be expected to
work (or that it will be any simpler to deal with than the ALSA
installation, which looks like a convoluted mess)?

I've been at this for weeks, off and on, and have fixed any number of
problems along the way, but I still don't have sound, and I'm running
out of ideas (and websites to troll for information).

I'm not trying to bring up God's own sound mixing and recording system;
I just want things like Netscape plugins or whatever that happens to
want to output sound, to be able to output sound.

I'm somewhat mystified by all the suggestions to try this and try that
and see if it works, that I find on the net - I thought the advantage of
having an open-source environment was that it was possible to *identify*
what was going on, and that speculatively flailing around in every
direction was the provenance of the Gatesware droids.  Am I missing
something
here?  Do I need to become a specialist in sound system architectures
and
rewrite a driver in order to get sound working?  (I'm well on the way to
becoming a network engineer just to get my LAN up, so why not, I
guess...)

Re: OSS - I'm curious about the relationship between the
apparently-OSS-based
driver I'm trying to use, and the "commercial" OSS drivers that are
available...
did somebody decide to try to make money off doing it right for a
change, or
something?

Thanks in advance.  I sincerely hope somebody has a very simple fix
and I end up feeling like a complete idiot for posting this; it
would be more than worth the humiliation, after all of the fruitless
effort I've expended.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

sound question: Jack

[Richard Kimber]

The document "Installing and configuring ALSA, JACK, & Ardour on Red Hat
7.3" (June 2003) has some information on how Debian differs from RH
embodied in it.  But it also includes the statement:

"JACK is available from http://jackit.sourceforge.net.  Let me make this
perfectly clear - DO NOT use a tarball or RPM that you may find anywhere
else (trust me on this one)"

Do the Jack Debian packages overcome whatever fears the author had about
non-jackit.sourceforge.net versions?

- Richard.
-- 
Richard Kimber
http://www.psr.keele.ac.uk/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RE: sound question

[Panuganty, Ramesh]

I documented my sound experiences with alsa here:

http://panuganty.tripod.com/debiantips/sound.htm

The AC97 Audio controller is pretty standard. It should be fairly easy
to setup.

-Ramesh

-Original Message-
From: Malte Thoma [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 21, 2002 12:53 PM
To: debian-user@lists.debian.org
Subject: sound question


Hallo,

can anybody tell me, how to set up the soundsystem of my laptop? I have
tryed severalthings, but without success :-(

I've got:
Kernel 2.4.18

lspci says:
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio 
Controller (rev 50)

I would like to use alsa, but haven't found a dokumentation.
I tryed alsaconf, but at the end it's not possible to detect the 
soundcard, could be a problem of diffferent versions?

Any help is welcome,

Malte Thoma


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]

Re: sound question

[Adam Majer]

On Thu, Mar 21, 2002 at 07:53:24PM +0100, Malte Thoma wrote:
> can anybody tell me, how to set up the soundsystem of my laptop?
> I have tryed severalthings, but without success :-(
> 
> lspci says:
> 00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio 
> Controller (rev 50)

Try the VIA sound driver. Many built-in sound "cards" have ability to
be accessed as legacy Sound Blasters. This will be an option in the BIOS.

- Adam

Re: sound question

[Nick Hastings]

Hi,

* Malte Thoma <[EMAIL PROTECTED]> [020322 10:57]:
> Hallo,
>
> can anybody tell me, how to set up the soundsystem of my laptop?
> I have tryed severalthings, but without success :-(
>
> I've got:
> Kernel 2.4.18
>
> lspci says:
> 00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
> Controller (rev 50)

Do you have the appropriate driver in your kernel? Is you 2.4.18 kernel a
stock Debian one, or did you compile it yourself? If it is a Debian kernel,
then I guess it will be compiled as a module.

As root:

# modconf

Select

/kernel/drivers/sound

Then scroll to see if the driver is there. If it is load it.

If it is not there, you will have to compile a new kernel. Enjoy ;-)
>
> I would like to use alsa, but haven't found a dokumentation.
> I tryed alsaconf, but at the end it's not possible to detect the
> soundcard, could be a problem of diffferent versions?

Sorry don't know about ALSA. But I guess that making sure you have the
driver for your card will be the first step.

Cheers,

Nick.

-- 
Debian 3.0
Linux onefish 2.4.18-lavienx #1 Tue Feb 26 17:37:42 EST 2002 i686 unknown

sound question

[Malte Thoma]

Hallo,

can anybody tell me, how to set up the soundsystem of my laptop?
I have tryed severalthings, but without success :-(

I've got:
Kernel 2.4.18

lspci says:
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio 
Controller (rev 50)


I would like to use alsa, but haven't found a dokumentation.
I tryed alsaconf, but at the end it's not possible to detect the 
soundcard, could be a problem of diffferent versions?


Any help is welcome,

Malte Thoma

Re: (YASQ) - Yet another sound question

[Jason Stechschulte]

On Sat, Feb 16, 2002 at 01:38:40PM -0600, Dimitri Maziuk wrote:
> If you want to give that a try, recompile your kernel with
> sound support (but no drivers). Install alsaconf and 
> alsa-[source|utils] packages, and follow the instructions for
> building the intel82x driver. Install the driver, edit /etc/alsa/0.9
> and delete all options the driver's complaining about when you 
> modprobe snd-card-0. Don't forget to re-run update-modules after 
> each edit. When you get the module to load, make /etc/alsa/0.9 
> chattr +i, so that alsaconf doesn't crap all over it later.

I'm not seeing the intel82x driver.  There is an intel8x0 driver and I'm
trying that.  Now XMMS will play songs without complaining, but I'm
still not getting any sound out of it.  It is playing but no sound is
coming from speakers.  I'm getting this on bootup:

No /usr/sbin/alsactl for ALSA 0.5 found
snd_intel8x0_chip_init: invalid AC'97 codec
Intel ICH soundcard not found or device busy

> Ask on debian-kde. I never bothered with KDE sounds, all I want is a 
> working CD player. Kcd (or whatever it's called) works for me.

Ok, thanks, I'll try there.
-- 
Jason Stechschulte
[EMAIL PROTECTED]
--
I wasn't recommending that we make the links for them, only provide them
with the tools to do so if they want to take the gamble (or the gambol).
 -- Larry Wall in <[EMAIL PROTECTED]>

Re: (YASQ) - Yet another sound question

[Dimitri Maziuk]

* Jason Stechschulte ([EMAIL PROTECTED]) spake thusly:
> I've been struggling to get sound to work on a Dell system I got
> recently.  I'm running Woody with a 2.4.17 kernel.  I think my problem
> has to do with the sound being integrated.  According to WinXP which is
> also on this box, the chip is an intel 82801BA/BAM AC'97.  When
> recompiling the kernel, I don't see anything that looks like it would
> work for this.

There is an intel820 driver, actually, but I never tried it.
I got it to work with (FVO "with" approaching "despite") debian 
alsa packages... 

If you want to give that a try, recompile your kernel with
sound support (but no drivers). Install alsaconf and 
alsa-[source|utils] packages, and follow the instructions for
building the intel82x driver. Install the driver, edit /etc/alsa/0.9
and delete all options the driver's complaining about when you 
modprobe snd-card-0. Don't forget to re-run update-modules after 
each edit. When you get the module to load, make /etc/alsa/0.9 
chattr +i, so that alsaconf doesn't crap all over it later.

> I'm running KDE on this computer.  I've only ever installed X on one box
> before and on that I used gnome and esd for the sound server.  Which
> sound server works best with KDE?  If I run sound server from KDE menu
> it has arts listed as the sound server.  Is this what I should be using?

Ask on debian-kde. I never bothered with KDE sounds, all I want is a 
working CD player. Kcd (or whatever it's called) works for me.

Dima
-- 
Q276304 - Error Message: Your Password Must Be at Least 18770 Characters
and Cannot Repeat Any of Your Previous 30689 Passwords   -- RISKS 21.37

(YASQ) - Yet another sound question

[Jason Stechschulte]

I've been struggling to get sound to work on a Dell system I got
recently.  I'm running Woody with a 2.4.17 kernel.  I think my problem
has to do with the sound being integrated.  According to WinXP which is
also on this box, the chip is an intel 82801BA/BAM AC'97.  When
recompiling the kernel, I don't see anything that looks like it would
work for this.  Does anyone know if I'm overlooking something?  

I ran apt-get install sndconfig and tried that.  It said it found device
8086:2445 and that is was unknown and not supported, but before giving
up, I thought I'd see if this is reliable information.

I'm running KDE on this computer.  I've only ever installed X on one box
before and on that I used gnome and esd for the sound server.  Which
sound server works best with KDE?  If I run sound server from KDE menu
it has arts listed as the sound server.  Is this what I should be using?

If anyone has any more info on this chip and can point me in the right
direction with the other stuff, I would greatly appreciate it.
-- 
Jason Stechschulte
[EMAIL PROTECTED]
--
Even if you aren't in doubt, consider the mental welfare of the person who
has to maintain the code after you, and who will probably put parens in
the wrong place.  -- Larry Wall in the perl man page

Re: yet another sound question

[Marcelo Chiapparini]

On Tue, Jan 23, 2001 at 07:05:49PM -0500, Vinod Kurup wrote:

 
> Well, it depends which module works for your sound card.
> A quick search of the sound-HOWTO suggests that the
> 'sb' driver should work. 
> 
> So
> $ depmod -a
> $ modprobe sb
> 
It worked very well! now I have sound in my potato box! Thanks a lot 
for your help!

Regards,

Marcelo

> 

Re: yet another sound question

[Vinod Kurup]

On Tue, Jan 23, 2001 at 09:36:10PM -0200, Marcelo Chiapparini wrote:
> Hi!
> 
> I run potato 2.2r with the 2.2.17 kernel. My motherboard has a built in
> Creative Labs VIBRA 16CL sound, which is working under Windows and OS/2.
> I would like to put it to work under Debian too.
> I did:
> 
> grep CONFIG_SOUND config-2.2.17
> 
> and obtained the output:
> 
> CONFIG_SOUNDMODEM=m
> CONFIG_SOUND=m
> CONFIG_SOUND_CMPCI=m
> CONFIG_SOUND_ES1370=m
> CONFIG_SOUND_ES1371=m
> CONFIG_SOUND_MAESTRO=m
> CONFIG_SOUND_ESSSOLO1=m
> CONFIG_SOUND_ICH=m
> CONFIG_SOUND_SONICVIBES=m
> CONFIG_SOUND_TRIDENT=m
> CONFIG_SOUND_MSNDCLAS=m
> CONFIG_SOUND_MSNDPIN=m
> CONFIG_SOUND_OSS=m
> CONFIG_SOUND_PAS=m
> CONFIG_SOUND_SB=m
> CONFIG_SOUND_GUS=m
> CONFIG_SOUND_MPU401=m
> CONFIG_SOUND_PSS=m
> CONFIG_SOUND_MSS=m
> CONFIG_SOUND_SSCAPE=m
> CONFIG_SOUND_TRIX=m
> CONFIG_SOUND_VIA82CXXX=m
> CONFIG_SOUND_MAD16=m
> CONFIG_SOUND_WAVEFRONT=m
> CONFIG_SOUND_CS4232=m
> CONFIG_SOUND_OPL3SA2=m
> CONFIG_SOUND_MAUI=m
> CONFIG_SOUND_SGALAXY=m
> CONFIG_SOUND_AD1816=m
> CONFIG_SOUND_OPL3SA1=m
> CONFIG_SOUND_SOFTOSS=m
> CONFIG_SOUND_YM3812=m
> CONFIG_SOUND_VMIDI=m
> CONFIG_SOUND_UART6850=m
> CONFIG_SOUND_NM256=m
> CONFIG_SOUND_YMPCI=m
> 
> is it OK?
> 
>  From the lsmod command I obtain:
> 
> Module  Size  Used by
> nls_cp437   3904   1  (autoclean)
> serial 19564   1  (autoclean)
> sg 15320   0  (unused)
> ppp20684   1
> slhc4436   0  [ppp]
> soundcore   2628   0  (unused)
> hpfs8552   1
> ide-floppy  8444   0
> unix   10212  88  (autoclean)
> 
> 
> I learned from this list that I have to use modprobe. May be
> 
> modprobe ES1371 ?
> 
> Thanks in advance for the help!
> 
> Marcelo
> 

Well, it depends which module works for your sound card.
A quick search of the sound-HOWTO suggests that the
'sb' driver should work. 

So
$ depmod -a
$ modprobe sb

HOWTO - 

If that doesn't work, then you may need to do a 
search to figure out what the correct driver is...

Good luck!

Vinod


-- 
_
Vinod Kurup, MD
email: [EMAIL PROTECTED]
phone: 617.277.2012
cell:  617.359.5990
http://www.medicalrecords.com

yet another sound question

[Marcelo Chiapparini]

Hi!

I run potato 2.2r with the 2.2.17 kernel. My motherboard has a built in
Creative Labs VIBRA 16CL sound, which is working under Windows and OS/2.
I would like to put it to work under Debian too.
I did:

grep CONFIG_SOUND config-2.2.17

and obtained the output:

CONFIG_SOUNDMODEM=m
CONFIG_SOUND=m
CONFIG_SOUND_CMPCI=m
CONFIG_SOUND_ES1370=m
CONFIG_SOUND_ES1371=m
CONFIG_SOUND_MAESTRO=m
CONFIG_SOUND_ESSSOLO1=m
CONFIG_SOUND_ICH=m
CONFIG_SOUND_SONICVIBES=m
CONFIG_SOUND_TRIDENT=m
CONFIG_SOUND_MSNDCLAS=m
CONFIG_SOUND_MSNDPIN=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_PAS=m
CONFIG_SOUND_SB=m
CONFIG_SOUND_GUS=m
CONFIG_SOUND_MPU401=m
CONFIG_SOUND_PSS=m
CONFIG_SOUND_MSS=m
CONFIG_SOUND_SSCAPE=m
CONFIG_SOUND_TRIX=m
CONFIG_SOUND_VIA82CXXX=m
CONFIG_SOUND_MAD16=m
CONFIG_SOUND_WAVEFRONT=m
CONFIG_SOUND_CS4232=m
CONFIG_SOUND_OPL3SA2=m
CONFIG_SOUND_MAUI=m
CONFIG_SOUND_SGALAXY=m
CONFIG_SOUND_AD1816=m
CONFIG_SOUND_OPL3SA1=m
CONFIG_SOUND_SOFTOSS=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_UART6850=m
CONFIG_SOUND_NM256=m
CONFIG_SOUND_YMPCI=m

is it OK?

 From the lsmod command I obtain:

Module  Size  Used by
nls_cp437   3904   1  (autoclean)
serial 19564   1  (autoclean)
sg 15320   0  (unused)
ppp20684   1
slhc4436   0  [ppp]
soundcore   2628   0  (unused)
hpfs8552   1
ide-floppy  8444   0
unix   10212  88  (autoclean)


I learned from this list that I have to use modprobe. May be

modprobe ES1371 ?

Thanks in advance for the help!

Marcelo

RE: sound question

[Brendon B]

What about modconf in kernel 2.4? It doesn't seem to work because of the
directories the modules are put in.

brendon

 -Original Message-
From:   Allan F. Caetano [mailto:[EMAIL PROTECTED]
Sent:   Tuesday, November 21, 2000 5:23 AM
To: Adam C Powell IV
Cc: Daniel Pittman; Andrew Dixon; debian-user@lists.debian.org;
debian-laptop@lists.debian.org
Subject:    Re: sound question

>>>>> "Adam" == Adam C Powell IV <[EMAIL PROTECTED]> writes:

Adam> Daniel Pittman wrote:
>> Andrew Dixon <[EMAIL PROTECTED]> writes:
>> >
>> > Hi All, I just recompiled my kernel so that my sound now works. The
>> > only problem is that I have to enter:
>> >
>> > modprobe nm256
>> >
>> > in order to get the module to load into the kernel. Any body know
how
>> > I can automate this or get it to run at startup.
>>
>> Add the name of any modules you want loaded at startup to the file
>> '/etc/modules'.

Adam> The "right way" to do this is to add it using modconf.  But AFAIK
this just adds
Adam> it to /etc/modules (along with any arguments the module might
need).

Actually, modconf(8) also modifies /etc/modules.conf, where the
arguments to the modules are defined. But, you're right, using modconf
is the "right way" to go about it.

cheers,

--
Allan F. Caetano
Universo On Line - EngProd - F: (11) 224 4418
ComVc: 479966   ICQ: 68214944

"Who is this peer that keeps resetting my connection?
 I have a broken pipe I wanna hit him with!"


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]

Re: sound question

[Andrew Dwight Dixon]

Adam C Powell IV wrote:

>
> > Andrew Dixon <[EMAIL PROTECTED]> writes:
> > >
> The "right way" to do this is to add it using modconf.  But AFAIK this just 
> adds
> it to /etc/modules (along with any arguments the module might need).
>

Thanks for the info it's great to know about tools like modconf.  I do think 
your
right that it adds them to /etc/modules because it showed that my nm256 was 
already
configured, but, the man page looks like this tool is more powerful than *just*
adding them to the /etc/modules file.

thanks again,
Andy




_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: sound question

[Andrew Dwight Dixon]

Daniel Pittman wrote:

>
> Add the name of any modules you want loaded at startup to the file
> '/etc/modules'.
>
>

That works beautifully.  Thank you very much.

later,
Andy

>


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: sound question

[Allan F. Caetano]

> "Adam" == Adam C Powell IV <[EMAIL PROTECTED]> writes:

Adam> Daniel Pittman wrote:
>> Andrew Dixon <[EMAIL PROTECTED]> writes:
>> >
>> > Hi All, I just recompiled my kernel so that my sound now works. The
>> > only problem is that I have to enter:
>> >
>> > modprobe nm256
>> >
>> > in order to get the module to load into the kernel. Any body know how
>> > I can automate this or get it to run at startup.
>> 
>> Add the name of any modules you want loaded at startup to the file
>> '/etc/modules'.

Adam> The "right way" to do this is to add it using modconf.  But AFAIK 
this just adds
Adam> it to /etc/modules (along with any arguments the module might need).

Actually, modconf(8) also modifies /etc/modules.conf, where the
arguments to the modules are defined. But, you're right, using modconf
is the "right way" to go about it.

cheers,

-- 
Allan F. Caetano
Universo On Line - EngProd - F: (11) 224 4418
ComVc: 479966   ICQ: 68214944

"Who is this peer that keeps resetting my connection?
 I have a broken pipe I wanna hit him with!"

Re: sound question

[Adam C Powell IV]

Daniel Pittman wrote:

> Andrew Dixon <[EMAIL PROTECTED]> writes:
> >
> > Hi All, I just recompiled my kernel so that my sound now works. The
> > only problem is that I have to enter:
> >
> > modprobe nm256
> >
> > in order to get the module to load into the kernel. Any body know how
> > I can automate this or get it to run at startup.
>
> Add the name of any modules you want loaded at startup to the file
> '/etc/modules'.

The "right way" to do this is to add it using modconf.  But AFAIK this just adds
it to /etc/modules (along with any arguments the module might need).

Zeen,

-Adam P.

  Welcome to the best software in the world today cafe!

Re: sound question

[Daniel Pittman]

Andrew Dixon <[EMAIL PROTECTED]> writes:
>
> Hi All, I just recompiled my kernel so that my sound now works. The
> only problem is that I have to enter:
>
> modprobe nm256
>
> in order to get the module to load into the kernel. Any body know how
> I can automate this or get it to run at startup.

Add the name of any modules you want loaded at startup to the file
'/etc/modules'.

Daniel

-- 
We used to hate people.
Now we just make fun of them. 
It's more effective that way.
-- KMFDF, _Dogma_

sound question

[Andrew Dixon]

Hi All,
I just recompiled my kernel so that my sound now
works.  The only problem is that I have to enter:

modprobe nm256

in order to get the module to load into the kernel. 
Any body know how I can automate this or get it to run
at startup.

Thanks,
Andy

__
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

RE: Sound Question

[Lehel Bernadt]

On 25-May-2000 Jay Kelly wrote:
> I am trying to setup a SoundBlaster16 sound card, I have recomplied the
> kernel for sound and pnp support. Now I see the howto is telling me to:
> 
> Use pnpdump to capture the possible settings for all your Plug and Play
> devices, saving the result to the file /etc/isapnp.conf.
> Choose settings for the sound card that do not conflict with any other
> devices in your system and uncomment the appropriate lines in
> /etc/isapnp.conf. Don't forget to uncomment the (ACT Y) command near the
> end.
> Make sure that isapnp is run when your system boots up, normally done by one
> of the startup scripts. Reboot your system or run isapnp manually.
> 
> 1) after using the 'pnpdump' how do I save it to the /etc/isapnp.conf.
> 
> 2) Where do I uncomment the (ACT Y) command? I didnt see it.
> 
> 3) How do I make sure the isapnp is run at bootup?
> 
> Thanks Guys
> Jay
>

If you have a pnp-compliant bios, and you're happy with the card's
configuration, you don't need isapnptools. isapnp is for initialising the card
& setting one of its configuration. But if your bios does that on startup, you
can just pass the io,irq and dma to the sb module, and sb will recognize the
card.

Re: Sound Question

[Marshal Wong]

>>>>> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:

> How do I figure out what to uncomment from the
> isapnp.conf. After doing pnpdump the file has several lines that
> are all commented out. Any help would be great

Try uncommenting the lines with parentesis ( ).  They usually come in
groups, IRQ, IO, DMA, etc.  You can sometimes change some of the
values in them too.  Read the comments before the line to see what can
be changed.  If you want, I'll forward you mine.

Marshal

> -Original Message- From: Marshal Wong
> [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2000 4:16 PM To:
> Jay Kelly Cc: debian-user@lists.debian.org Subject: Re: Sound
> Question


>>>>> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:

>> I am trying to setup a SoundBlaster16 sound card, I have
>> recomplied the kernel for sound and pnp support. Now I see the
>> howto is telling me to:

>> Use pnpdump to capture the possible settings for all your Plug
>> and Play devices, saving the result to the file
>> /etc/isapnp.conf.  Choose settings for the sound card that do
>> not conflict with any other devices in your system and
>> uncomment the appropriate lines in /etc/isapnp.conf. Don't
>> forget to uncomment the (ACT Y) command near the end.  Make
>> sure that isapnp is run when your system boots up, normally
>> done by one of the startup scripts. Reboot your system or run
>> isapnp manually.

>> 1) after using the 'pnpdump' how do I save it to the
>> /etc/isapnp.conf.

> pnpdump > /etc/isapnp.conf

>> 2) Where do I uncomment the (ACT Y) command? I didnt see it.

> Once get the information from pnpdump, it should be at the end
> of each device configuration set.

> A note, you may have problems with isapnp say that there are
> fatel irq, and io errors, even if you know that that address is
> not being used.  To fix this, add (ACT N) at the beginning of
> each device section.  Let me know if you have problems.

>> 3) How do I make sure the isapnp is run at bootup?

> If there is a working /etc/isapnp.conf, it will be used at
> bootup.  There is a script that runs it.  This is for sure for
> potato.  I can't remember if this is true for slink.

> Good Luck

>> Thanks Guys Jay


>> -- Unsubscribe?  mail -s unsubscribe
>> [EMAIL PROTECTED] < /dev/null



> -- Unsubscribe?  mail -s unsubscribe
> [EMAIL PROTECTED] < /dev/null

Sound Question

[Kenneth Scharf]

>1) after using the 'pnpdump' how do I save it to the
>/etc/isapnp.conf.
Easy way is to (as root) 

vi pnpdump

edit changes

w /etc/isapnp.conf
q


>
>2) Where do I uncomment the (ACT Y) command? I didnt
>see it.

There is one of these lines per section.  It's there,
if needed in vi use the '/' command to search for it!

>
>3) How do I make sure the isapnp is run at bootup?
>
If you installed the isapnp from the .deb, it's
already set to run.  The script is loaded in
/etc/init.d


=
Amateur Radio, when all else fails!

http://www.qsl.net/wa2mze

Debian Gnu Linux, Live Free or .



__
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

Re: Sound Question

[Stan Kaufman]

Jay Kelly wrote:
> 
> How do I figure out what to uncomment from the isapnp.conf. After doing
> pnpdump the file has several lines that are all commented out. Any help
> would be great

Read http://www.roestock.demon.co.uk/isapnptools/ and specifically
http://www.roestock.demon.co.uk/isapnptools/pnpdump.8.html and
http://www.roestock.demon.co.uk/isapnptools/isapnp.conf.5.html.


> 
> -Original Message-
> From: Marshal Wong [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 25, 2000 4:16 PM
> To: Jay Kelly
> Cc: debian-user@lists.debian.org
> Subject: Re: Sound Question
> 
> >>>>> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:
> 
> > I am trying to setup a SoundBlaster16 sound card, I have
> > recomplied the kernel for sound and pnp support. Now I see the
> > howto is telling me to:
> 
> > Use pnpdump to capture the possible settings for all your Plug
> > and Play devices, saving the result to the file
> > /etc/isapnp.conf.  Choose settings for the sound card that do
> > not conflict with any other devices in your system and uncomment
> > the appropriate lines in /etc/isapnp.conf. Don't forget to
> > uncomment the (ACT Y) command near the end.  Make sure that
> > isapnp is run when your system boots up, normally done by one of
> > the startup scripts. Reboot your system or run isapnp manually.
> 
> > 1) after using the 'pnpdump' how do I save it to the
> > /etc/isapnp.conf.
> 
> pnpdump > /etc/isapnp.conf
> 
> > 2) Where do I uncomment the (ACT Y) command? I didnt see it.
> 
> Once get the information from pnpdump, it should be at the end of each
> device configuration set.
> 
> A note, you may have problems with isapnp say that there are fatel
> irq, and io errors, even if you know that that address is not being
> used.  To fix this, add (ACT N) at the beginning of each device
> section.  Let me know if you have problems.
> 
> > 3) How do I make sure the isapnp is run at bootup?
> 
> If there is a working /etc/isapnp.conf, it will be used at bootup.
> There is a script that runs it.  This is for sure for potato.  I can't
> remember if this is true for slink.
> 
> Good Luck
> 
> > Thanks Guys Jay
> 
> > -- Unsubscribe?  mail -s unsubscribe
> > [EMAIL PROTECTED] < /dev/null
> 
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] <
> /dev/null
> 
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

RE: Sound Question

[Jay Kelly]

How do I figure out what to uncomment from the isapnp.conf. After doing
pnpdump the file has several lines that are all commented out. Any help
would be great

-Original Message-
From: Marshal Wong [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 25, 2000 4:16 PM
To: Jay Kelly
Cc: debian-user@lists.debian.org
Subject: Re: Sound Question


>>>>> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:

> I am trying to setup a SoundBlaster16 sound card, I have
> recomplied the kernel for sound and pnp support. Now I see the
> howto is telling me to:

> Use pnpdump to capture the possible settings for all your Plug
> and Play devices, saving the result to the file
> /etc/isapnp.conf.  Choose settings for the sound card that do
> not conflict with any other devices in your system and uncomment
> the appropriate lines in /etc/isapnp.conf. Don't forget to
> uncomment the (ACT Y) command near the end.  Make sure that
> isapnp is run when your system boots up, normally done by one of
> the startup scripts. Reboot your system or run isapnp manually.

> 1) after using the 'pnpdump' how do I save it to the
> /etc/isapnp.conf.

pnpdump > /etc/isapnp.conf

> 2) Where do I uncomment the (ACT Y) command? I didnt see it.

Once get the information from pnpdump, it should be at the end of each
device configuration set.

A note, you may have problems with isapnp say that there are fatel
irq, and io errors, even if you know that that address is not being
used.  To fix this, add (ACT N) at the beginning of each device
section.  Let me know if you have problems.

> 3) How do I make sure the isapnp is run at bootup?

If there is a working /etc/isapnp.conf, it will be used at bootup.
There is a script that runs it.  This is for sure for potato.  I can't
remember if this is true for slink.

Good Luck

> Thanks Guys Jay


> -- Unsubscribe?  mail -s unsubscribe
> [EMAIL PROTECTED] < /dev/null



--
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] <
/dev/null

Re: Sound Question

[Marshal Wong]

> "Jay" == Jay Kelly <[EMAIL PROTECTED]> writes:

> I am trying to setup a SoundBlaster16 sound card, I have
> recomplied the kernel for sound and pnp support. Now I see the
> howto is telling me to:

> Use pnpdump to capture the possible settings for all your Plug
> and Play devices, saving the result to the file
> /etc/isapnp.conf.  Choose settings for the sound card that do
> not conflict with any other devices in your system and uncomment
> the appropriate lines in /etc/isapnp.conf. Don't forget to
> uncomment the (ACT Y) command near the end.  Make sure that
> isapnp is run when your system boots up, normally done by one of
> the startup scripts. Reboot your system or run isapnp manually.

> 1) after using the 'pnpdump' how do I save it to the
> /etc/isapnp.conf.

pnpdump > /etc/isapnp.conf

> 2) Where do I uncomment the (ACT Y) command? I didnt see it.

Once get the information from pnpdump, it should be at the end of each
device configuration set.

A note, you may have problems with isapnp say that there are fatel
irq, and io errors, even if you know that that address is not being
used.  To fix this, add (ACT N) at the beginning of each device
section.  Let me know if you have problems.

> 3) How do I make sure the isapnp is run at bootup?

If there is a working /etc/isapnp.conf, it will be used at bootup.
There is a script that runs it.  This is for sure for potato.  I can't
remember if this is true for slink.

Good Luck

> Thanks Guys Jay


> -- Unsubscribe?  mail -s unsubscribe
> [EMAIL PROTECTED] < /dev/null

Sound Question

[Jay Kelly]

I am trying to setup a SoundBlaster16 sound card, I have recomplied the
kernel for sound and pnp support. Now I see the howto is telling me to:

Use pnpdump to capture the possible settings for all your Plug and Play
devices, saving the result to the file /etc/isapnp.conf.
Choose settings for the sound card that do not conflict with any other
devices in your system and uncomment the appropriate lines in
/etc/isapnp.conf. Don't forget to uncomment the (ACT Y) command near the
end.
Make sure that isapnp is run when your system boots up, normally done by one
of the startup scripts. Reboot your system or run isapnp manually.

1) after using the 'pnpdump' how do I save it to the /etc/isapnp.conf.

2) Where do I uncomment the (ACT Y) command? I didnt see it.

3) How do I make sure the isapnp is run at bootup?

Thanks Guys
Jay

Re: insmod sound question

[Michael Dahlberg]

David J. Kanter [EMAIL PROTECTED] wrote:
> Yesterday I recompiled my kernel with sound support, as a module, and then
> compiled the Aureal Vortex 2 driver. All worked well until I rebooted. 
> 
> After rebooting I had to log on a root, then type insmod au8830.o because
> all sound software said no sound device was detected. After that everything
> worked just fine.
> 
> This isn't a big deal, but how can I get this process automated? I've never
> had to insmod anything before. The module autoloader (kmod) was compiled
> into the kernel, and in my /etc/modules.conf I've got:
> 
> ### update-modules: end processing /etc/modutils/arch/i386
> 
> alias sound au8830
> alias midi au8830

Try adding 
alias char-major-14 au8830
alias sound-service-0-3 au8830
alias sound-slot-0 au8830
to the modules.conf file.  It worked for me but I'm using an es1371.

Mike

insmod sound question

[David J. Kanter]

Yesterday I recompiled my kernel with sound support, as a module, and then
compiled the Aureal Vortex 2 driver. All worked well until I rebooted. 

After rebooting I had to log on a root, then type insmod au8830.o because
all sound software said no sound device was detected. After that everything
worked just fine.

This isn't a big deal, but how can I get this process automated? I've never
had to insmod anything before. The module autoloader (kmod) was compiled
into the kernel, and in my /etc/modules.conf I've got:

### update-modules: end processing /etc/modutils/arch/i386

alias sound au8830
alias midi au8830

-- 
David J. Kanter
[EMAIL PROTECTED]

Sound question.

[Wintermute]

I have successfully compiled the sound driver with support for my cheap
Ensoniq Soundscape clone (made by Reveal).  This installs fine, and I
have verifyed that I am getting sound output by cat'ing a few .au files
to /dev/audio, and I even picked up the mpg123 player to try out the
Windows95suck.mp3 *grin*..  however, there is one problem and I'm not
sure where to look for the solution.

When playing .au files, the sound will play for about 8-10 seconds
suddenly beccome choppy and then I'll get this error message:

cat: write error: I/O error

Also, when using mpg123, it plays each 2 seconds of sound like 6 times
before moving on to the next 2 seconds.  

This is REALLY annoying, as the output sounds correct.  I imagine this
to be some sort of buffering problem.. but I don't know where to look.

The sound buffer is set to 65535 (the maximum) so I don't see a problem
there.. and yet...

Anyone run across this problem before?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .