[EMAIL PROTECTED] wrote:
> On Wed, May 03, 2000 at 10:28:01PM +0100, Jonathan Heaney wrote:
> > [EMAIL PROTECTED] wrote:
> >
> > > I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
> ...
>
> > Compiling the OSS driver direct into the kernel should be OK; try and get
> > tha
At 08:45 AM 5/5/00 -0700, you wrote:
>Hello all,
>
>After nearly deciding to settle for the commercial sound drivers, yet
>another post from this list (thanks all!) urged me to retry the ALSA
>drivers. I went back and again compiled the latest source after fully
>cleaning out my system. What made
Hello all,
After nearly deciding to settle for the commercial sound drivers, yet
another post from this list (thanks all!) urged me to retry the ALSA
drivers. I went back and again compiled the latest source after fully
cleaning out my system. What made the difference this time was discovering
t
At 10:25 PM 5/3/00 -0700, Chris Baker <[EMAIL PROTECTED]>
wrote:
> <[EMAIL PROTECTED]> writes:
>
>> On Wed, May 03, 2000 at 05:25:14PM -0700, [EMAIL PROTECTED] wrote:
>> > Did you compile in the 'sound' module or leave it as a module? I've seen
...
>> Yes. The es1371 driver is compiled directly in
<[EMAIL PROTECTED]> writes:
> On Wed, May 03, 2000 at 05:25:14PM -0700, [EMAIL PROTECTED] wrote:
> > Did you compile in the 'sound' module or leave it as a module? I've seen
> > these symptoms once when the 'sound' module was not loaded.
>
> Yes. The es1371 driver is compiled directly into the
On Wed, May 03, 2000 at 10:28:01PM +0100, Jonathan Heaney wrote:
> [EMAIL PROTECTED] wrote:
>
> > I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
...
> Compiling the OSS driver direct into the kernel should be OK; try and get that
> working before attempting the switch to
On Wed, May 03, 2000 at 05:25:14PM -0700, [EMAIL PROTECTED] wrote:
> Did you compile in the 'sound' module or leave it as a module? I've seen
> these symptoms once when the 'sound' module was not loaded.
Yes. The es1371 driver is compiled directly into the kernel. I recompiled
the kernel (as an
Did you compile in the 'sound' module or leave it as a module? I've seen
these symptoms once when the 'sound' module was not loaded.
Gregg Berkholtz
On Wed, May 03, 2000 at 10:19:16AM -0700, [EMAIL PROTECTED] wrote:
> I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
> int
On Wed, May 03, 2000 [EMAIL PROTECTED] wrote:
> The ALSA install put every module they support into there. I modified
> /etc/modutils/alias to try both the ens1370 and ens1371 modules. The 1370
> failed to detect anything. The 1371 did, but still no sound.
have a look at the ALSA FAQ at www.al
[EMAIL PROTECTED] wrote:
> I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
> into the kernel the ES1371 sound driver. On bootup the card is detected at
> irq 10 and a memory address of 0x9000 (which does NOT happen with the
> ES1370 driver).
>
> I have added myself (as a
At 01:16 PM 5/3/00 -0600, you wrote:
>[EMAIL PROTECTED] wrote:
>>
>> I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
>> into the kernel the ES1371 sound driver. On bootup the card is detected at
...
>Did you add ens1370 to /etc/modules? I know I've made that mistake
>bef
[EMAIL PROTECTED] wrote:
>
> I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
> into the kernel the ES1371 sound driver. On bootup the card is detected at
> irq 10 and a memory address of 0x9000 (which does NOT happen with the
> ES1370 driver).
>
> I have added myself (as
I'm using the 2.2.14 kernel on an Asus k7V mb(Athlon), and have compiled
into the kernel the ES1371 sound driver. On bootup the card is detected at
irq 10 and a memory address of 0x9000 (which does NOT happen with the
ES1370 driver).
I have added myself (as a normal user) to the audio and cdrom g
13 matches
Mail list logo
