Re: azt1008 on HP Vectra

Re: azt1008 on HP Vectra

[Robert.Siemer]

On Mon, Mar 31, 2003 at 10:07:49AM -0500, W. L. Estes wrote:

> ... and I get error messages from ad1848.o
> that don't really seem very helpful.
> 
> Any ideas or suggestions?

Yeah, include the error messages.


Rob

azt1008 on HP Vectra

[W. L. Estes]

I have an old HP Vectra with a sound card in it that seems to identify
itself as an azt1008. Using a fresh redhat 8.0 install, sndconfig sees
the card as the azt1008 and tries to use the ad1848.o module. But no
go, no sound comes out the card and I get error messages from ad1848.o
that don't really seem very helpful.

Any ideas or suggestions?


Thanks,

--Will



-- 
Will Estes
Unix Systems Programmer
UNCG MIS, Systems Group

Re: azt1008 on HP Vectra

[W. L. Estes]

On Monday, 31 March 2003,17:05 +0200, Robert.Siemer@gmx.de wrote:

> Yeah, include the error messages.

/lib/modules/2.4.18-14/kernel/drivers/sound/ad1848.o: init_modlue: no such device

This is the error I get when trying the modprobe step in running
sndconfig with my azt1008  inside my HP Vectra.

Any suggestions?

--Will

Re: azt1008 on HP Vectra

[Robert.Siemer]

On Mon, Mar 31, 2003 at 01:53:38PM -0500, W. L. Estes wrote:
> On Monday, 31 March 2003,17:05 +0200, Robert.Siemer@gmx.de wrote:
> 
> > Yeah, include the error messages.
> 
> /lib/modules/2.4.18-14/kernel/drivers/sound/ad1848.o: init_modlue: no such device

- I don't believe that this is the correct error message.
- Further, look into the kernel ring buffer (dmesg) for more messages.
- Use insmod and follow the dependancies manually.


Robert

Re: azt1008 on HP Vectra

[W. L. Estes]

I was looking through the linux-sound mail archives and saw a patch
posted for the azt1008 against linux kernel 2.4.20-rc1-ac4. That patch
didn't apply against kernel sources that I had (which isn't
surprising). It would seem like this problem has already been solved
so I was hoping that I could get the patch posted against 2.4.20 or
similar. The post I'm referring to is:

http://marc.theaimsgroup.com/?l=linux-sound&m\x103835842003582&w=2

On Tuesday, 01 April 2003,14:34 +0200, Robert.Siemer@gmx.de wrote:

> On Mon, Mar 31, 2003 at 01:53:38PM -0500, W. L. Estes wrote:
> > On Monday, 31 March 2003,17:05 +0200, Robert.Siemer@gmx.de wrote:
> > 
> > > Yeah, include the error messages.
> > 
> > /lib/modules/2.4.18-14/kernel/drivers/sound/ad1848.o: init_modlue: no such device
> 
> - I don't believe that this is the correct error message.
> - Further, look into the kernel ring buffer (dmesg) for more messages.
> - Use insmod and follow the dependancies manually.
> 
> 
> Robert

-- 
Will Estes
Unix Systems Programmer
UNCG MIS, Systems Group

Re: azt1008 on HP Vectra

[Zwane Mwaikambo]

On Tue, 1 Apr 2003, W. L. Estes wrote:

> I was looking through the linux-sound mail archives and saw a patch
> posted for the azt1008 against linux kernel 2.4.20-rc1-ac4. That patch
> didn't apply against kernel sources that I had (which isn't
> surprising). It would seem like this problem has already been solved
> so I was hoping that I could get the patch posted against 2.4.20 or
> similar. The post I'm referring to is:
> 
> http://marc.theaimsgroup.com/?l=linux-sound&m\x103835842003582&w=2

For a quick test you can send me your drivers/sound/ad1848.c and i'll send 
you back a patched one.

	Zwane
-- 
function.linuxpower.ca

Re: azt1008 on HP Vectra

[W. L. Estes]

On Saturday, 24 May 2003,18:03 -0400, Zwane Mwaikambo wrote:

> On Tue, 1 Apr 2003, W. L. Estes wrote:
> 
> > I was looking through the linux-sound mail archives and saw a patch
> > posted for the azt1008 against linux kernel 2.4.20-rc1-ac4. That patch
> > didn't apply against kernel sources that I had (which isn't
> > surprising). It would seem like this problem has already been solved
> > so I was hoping that I could get the patch posted against 2.4.20 or
> > similar. The post I'm referring to is:
> > 
> > http://marc.theaimsgroup.com/?l=linux-sound&m\x103835842003582&w=2
> 
> For a quick test you can send me your drivers/sound/ad1848.c and i'll send 
> you back a patched one.

Thanks, but I realized that the problem was my web browser had gotten
overly generous on the formatting for me so the white space was off in
the patch and I didn't think to tell diff to ignore the differences in
whitespace.

Thanks, all, for your time.

--Will