Skip to contentSkip to conversation

azt1008 on HP Vectra

DISCUSSION [email protected] 3 participants 7 messages Mar 31, 2003 – May 26, 2003 Sound

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · W. L. Estes

... 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

#1 lore raw

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

Signature · 3 lines
Will Estes
Unix Systems Programmer
UNCG MIS, Systems Group
#2 lore raw
In reply to [email protected]
Quoted 1 line · On Monday, 31 March 2003,17:05 +0200, [email protected] 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

#3 lore raw
In reply to [email protected]
Quoted 5 lines · W. L. Estes
Quoted 1 line · On Monday, 31 March 2003,17:05 +0200, [email protected] 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

#4 lore raw
In reply to [email protected]

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&m3835842003582&w=2

Quoted 13 lines · On Tuesday, 01 April 2003,14:34 +0200, [email protected] wrote:
Quoted 5 lines · W. L. Estes
Quoted 1 line · On Monday, 31 March 2003,17:05 +0200, [email protected] 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

Signature · 3 lines
Will Estes
Unix Systems Programmer
UNCG MIS, Systems Group
#5 lore raw
In reply to [email protected]
Quoted 8 lines · 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&m3835842003582&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

Signature · 1 line
function.linuxpower.ca
#6 lore raw
In reply to [email protected]
Quoted 9 lines · Zwane Mwaikambo
Quoted 7 lines · 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:

Quoted 4 lines
Quoted 1 line

http://marc.theaimsgroup.com/?l=linux-sound&m3835842003582&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