: codec_valid: codec 0 is not valid [0x980000]

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Sat, 07 Jul 2001 21:34:57



Hi,

I just upgraded to linux-2.4.6 and the latest ALSA driver from the CVS tree
(07/05/01) and found my sound system is no longer working.  I checked the
/var/log/messages file and found the following message:

        PCI: Found IRQ 10 for device 00:04.5
        ALSA card-via686a.c:241: codec_valid: codec 0 is not valid [0x980000]

Has anyone encountered such a problem with ALSA on a MOBO that has a
VIA686a chip?

TIA.

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Sun, 08 Jul 2001 00:56:57


slightly off-topic, but why are you using the latest(bets) drivers?
alsa 0.5.1 works wery well...

sorry for being of no real help :)

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Sun, 08 Jul 2001 02:14:28



> slightly off-topic, but why are you using the latest(bets) drivers?
> alsa 0.5.1 works wery well...

> sorry for being of no real help :)

> the excession

Some of the audio/sound proggies require newer ALSA and the ALSA 0.5.1 does
not work.
 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Sun, 08 Jul 2001 04:17:42


ok, not i problem i've had so far, but give us more information and well
see what we can do about it.

for instance, what is your alsa configuration in etc/modules.conf?

what does lsmod say once the system is booted up?

what happends if you load the modules manually?

give enough info and well hopefully figure somthing out - tho if you're
using the beta, it could be a bug, but i'd wait to start bugging the
alsa guys. at least until you've excluded all other options.

if everything else fails, i'll turn on the onboard sound on my 686a mb,
and give the drivers a try. :) - i've got an sb live...

the excession - what's this proggie that wants the beta alsas?

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Sun, 08 Jul 2001 09:26:01



> ok, not i problem i've had so far, but give us more information and well
> see what we can do about it.

> for instance, what is your alsa configuration in etc/modules.conf?

alias   char-major-116          snd
alias   char-major-14           soundcore

alias   snd-card-0              snd-card-via686a

alias   sound-slot-0            snd-card-0

alias   sound-service-0-0       snd-mixer-oss
alias   sound-service-0-1       snd-seq-oss
alias   sound-service-0-8       snd-seq-oss
alias   sound-service-0-3       snd-pcm-oss
alias   sound-service-0-12      snd-pcm-oss

options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660
snd_device_gid=17 snd_device_uid=0
options snd-card-x snd_index=0 snd_id=card1 snd_mpu_port=0x300
snd_joystick=0x300 snd_pbk_frame_size=128 snd_cap_frame_size=128

Quote:> what does lsmod say once the system is booted up?

Module                  Size  Used by
snd-seq         46592   0 (autoclean)
snd-pcm-oss             47328   0 (autoclean) (unused)
snd-mixer-oss           11200   0 (autoclean) [snd-pcm-oss]
snd-card-via686a        7632    0 (unused)
snd-pcm         57184   0 [snd-pcm-oss snd-card-via686a]
snd-timer               11232   0 [snd-seq snd-pcm]
snd-ac97-codec  24640   0 [snd-card-via686a]
snd-mpu401-uart 3776    0 [snd-card-via686a]
snd-rawmidi             13664   0 [snd-mpu401-uart]
snd-seq-device          4512    0 [snd-seq snd-rawmidi]
snd                     33424   0 [snd-seq snd-pcm-oss snd-mixer-oss snd-card-via686a snd-pcm
snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device]

Quote:> what happends if you load the modules manually?

Manually loading via686a module gives the following error messages:

/lib/modules/2.4.6/kernel/drivers/sensors/via686a.o: init_module: No such
deviceHint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.6/kernel/drivers/sensors/via686a.o: insmod
/lib/modules/2.4.6/kernel/drivers/sensors/via686a.o failed
/lib/modules/2.4.6/kernel/drivers/sensors/via686a.o: insmod via686a failed

Quote:> give enough info and well hopefully figure somthing out - tho if you're
> using the beta, it could be a bug, but i'd wait to start bugging the
> alsa guys. at least until you've excluded all other options.

My Linux system is an AMD Athlon 500MHz with Asus K7M Mobo, thus a via686a
sound system.

Quote:> if everything else fails, i'll turn on the onboard sound on my 686a mb,
> and give the drivers a try. :) - i've got an sb live...

The only via686a sound my system has is on board.
Quote:> the excession - what's this proggie that wants the beta alsas?

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Sun, 08 Jul 2001 16:05:46



> options !!!!snd-card-x!!!! snd_index=0 snd_id=card1 snd_mpu_port=0x300
> snd_joystick=0x300 snd_pbk_frame_size=128 snd_cap_frame_size=128

it should not be snd-card-x, but snd-card-0.
cuz they are the options for the module of your soundcard. no wonder
modprobe sez u have a bad config...unless it's a typo from you?

Quote:> Module                  Size  Used by

<snip>

Quote:> snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device]

so far so good, modules there, but your main is unused. see above?

Quote:> Manually loading via686a module gives the following error messages:

> /lib/modules/2.4.6/kernel/drivers/sensors/via686a.o: init_module: No such
> deviceHint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters

there you go. i't either that "x" which should be "0", or bad irq/dma.
my via kt133 mb lets me set the stuff manually in the bios. check that
it's right?/modify the settings in modules.conf to match?

Quote:> My Linux system is an AMD Athlon 500MHz with Asus K7M Mobo, thus a via686a
> sound system.

mine an athlon 800 thunderbird, via kt133, via 686a southbridge - sound
turned off - and sblive. but - as i've said - i can always turn it on
and check if I get the same problem :)

so, change that thing in your modules.conf. also, try turning off the joystick stuff,

as i've yet to see it work aniway :(

keep us posted, i f it still doesen't work, ill try it here.

the excession - getting the files right now...

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Sun, 08 Jul 2001 16:09:03


belay that, it should be the exact name of the module you need - i
checked on mine and it says snd-card-emu10k1.

so yours should say snd-card-via686a

modify, run depmod -a
and loading the module again

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Sun, 08 Jul 2001 21:20:00


It was not a typo and I made changes to it as you had suggested below;
however, the problem still presists and the /var/log/messages says:

        PCI: Found IRQ 10 for device 00:04.5
        ALSA ac97_codec.c:1388: AC'97 0:0 does not respond - RESET

(I don't know if that error messages will help).



>> options !!!!snd-card-x!!!! snd_index=0 snd_id=card1 snd_mpu_port=0x300
>> snd_joystick=0x300 snd_pbk_frame_size=128 snd_cap_frame_size=128

> it should not be snd-card-x, but snd-card-0.
> cuz they are the options for the module of your soundcard. no wonder
> modprobe sez u have a bad config...unless it's a typo from you?

>> Module                  Size  Used by

> <snip>

>> snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device]

> so far so good, modules there, but your main is unused. see above?

>> Manually loading via686a module gives the following error messages:

>> /lib/modules/2.4.6/kernel/drivers/sensors/via686a.o: init_module: No such
>> deviceHint: insmod errors can be caused by incorrect module parameters,
>> including invalid IO or IRQ parameters

> there you go. i't either that "x" which should be "0", or bad irq/dma.
> my via kt133 mb lets me set the stuff manually in the bios. check that
> it's right?/modify the settings in modules.conf to match?

>> My Linux system is an AMD Athlon 500MHz with Asus K7M Mobo, thus a
>> via686a sound system.

> mine an athlon 800 thunderbird, via kt133, via 686a southbridge - sound
> turned off - and sblive. but - as i've said - i can always turn it on
> and check if I get the same problem :)

> so, change that thing in your modules.conf. also, try turning off the
> joystick stuff,

> as i've yet to see it work aniway :(

> keep us posted, i f it still doesen't work, ill try it here.

> the excession - getting the files right now...

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Mon, 09 Jul 2001 02:18:09


right.

this might be a hardware/alsa problem/bug.

i'll try seeing what happends if I turn mine on and configure it.

ill ask again, do you _really_ need the 0.9.x betas? i've got 6 gigs of
the latest software installed, and found none that complains with 0.5.1...

while I do this - i have to shutdown, change a jumper, fiddle in the
bios etc... - see if the driver that comes with the kernel loads.
the one in 2.4.6 has midi support too. i'm not suggesting that you use
it instead of the alsa's, cuz' alsa has better sound quality, but at
least we'll know if its specific to the alsa drivers or a
systemwide/hardware problem.

let me know what happends with the kernel modules..

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Mon, 09 Jul 2001 05:18:16



> right.

> this might be a hardware/alsa problem/bug.

I believe it is a software problem, i.e. alsa-driver.  If I installed
alsa-driver 0.5.11 (back drop), I could use regulard audio software without
a problem.  However, someone has asked me to compile his audio program that
requires the beta version of alsa-driver, i.e. cvs tree.  I even tried
alsa-driver-0.9beta1 - alsa-driver-0.9beta5 to noavail.

Quote:> i'll try seeing what happends if I turn mine on and configure it.

> ill ask again, do you _really_ need the 0.9.x betas? i've got 6 gigs of
> the latest software installed, and found none that complains with 0.5.1...

Definitely...:(  Also, it is better to find out what the problem is with
the beta driver now than having such problems when the beta version becomes
a released one.

Quote:> while I do this - i have to shutdown, change a jumper, fiddle in the
> bios etc... - see if the driver that comes with the kernel loads.
> the one in 2.4.6 has midi support too. i'm not suggesting that you use
> it instead of the alsa's, cuz' alsa has better sound quality, but at
> least we'll know if its specific to the alsa drivers or a
> systemwide/hardware problem.

Is you Mobo Asus K7M?  Mine, K7M, does not have any jumper setup that I
know to fiddle with.  When I installed the v0.5.11, the via686a occupied
interrupt 10.  Now, when I install the beta version of alsa-driver from the
cvs source, checked the /proc/int, and found interrupt 10 is not occupied
at all.  Here is the cat /proc/int:

           CPU0
  0:    2933058 XT-PIC  timer
  1:    27503           XT-PIC  keyboard
  2:    0               XT-PIC  cascade
  3:    954             XT-PIC  serial
  5:    18164           XT-PIC  eth0
  8:    1               XT-PIC  rtc
  9:    68              XT-PIC  usb-uhci, usb-uhci
 11:    1               XT-PIC  ohci1394
 12:    223724          XT-PIC  PS/2 Mouse
 14:    88341           XT-PIC  ide0
 15:    26              XT-PIC  ide1
NMI:    0
ERR:    0
MIS:    0

Quote:> let me know what happends with the kernel modules..

Did you mean patching the linux-2.4.6 kernel with the  
alsa-0.9.0beta4-k2.4.4-1342026.diff.bz2?  I have not touched the alsa
kernel patch since the alsa-0.9.0beta3-k2.4.3-1131131.diff.bz2.  I
remembered getting a lot of error with the patch and abandoned it since.
Quote:> the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Mon, 09 Jul 2001 07:58:20



> I believe it is a software problem, i.e. alsa-driver.  If I installed
> alsa-driver 0.5.11 (back drop), I could use regulard audio software without
> a problem.  However, someone has asked me to compile his audio program that
> requires the beta version of alsa-driver, i.e. cvs tree.  I even tried
> alsa-driver-0.9beta1 - alsa-driver-0.9beta5 to noavail.

right. i'm just back from dinner, ill try it out and if the problem
comes up on me too, we file a bug report.

Quote:> Definitely...:(  Also, it is better to find out what the problem is with
> the beta driver now than having such problems when the beta version becomes
> a released one.

agreed

Quote:

> Is you Mobo Asus K7M?

a gigabyte GA-7ZX, via kt133 chipset, via 686a southbridge.
on mine there is a jumper that allows you to physically disable the
audio. which i had done, because the first bios revision did not allow
me to disable it otherwise. it's now enabled.

Quote:> Did you mean patching the linux-2.4.6 kernel with the  
> alsa-0.9.0beta4-k2.4.4-1342026.diff.bz2?  I have not touched the alsa
> kernel patch since the alsa-0.9.0beta3-k2.4.3-1131131.diff.bz2.  I
> remembered getting a lot of error with the patch and abandoned it since.

no, i meant trying the sound drivers that come with the vanilla linux
kernel. but since you say that the old alsas worked, then it's
definetely an asls problem. give , say half an hour, ill make a test
kernel and install the beta drivers on it, and report back.
then we can send mails to the alsa developers, since this appears to be
a bug.

be back soon.

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Mon, 09 Jul 2001 09:24:56


what does lspci say?

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by the excessio » Mon, 09 Jul 2001 09:54:40


forget it.

the beta are way tooo beta.

nothing works.
period.

the excession

 
 
 

: codec_valid: codec 0 is not valid [0x980000]

Post by Young4er » Mon, 09 Jul 2001 22:12:26



> what does lspci say?

> the excession

lspci reports as follows:

00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System
Controller (rev 25)
00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP
Bridge (rev 01)
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 1b)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 0e)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 0e)
00:04.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20)
00:04.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686
[Apollo Super AC97/Audio] (rev 21)
00:0d.0 FireWire (IEEE 1394): Lucent Microelectronics: Unknown device 5811
(rev 04)
00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
10)
01:05.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01)

 
 
 

1. ASUS A7V8X-X , ALSA and VIA-82xx : codec 0 is not valid [0x87e5370]

Hi !

I have an ASUS A7V8X-X motherboard and I am trying to configure my
sound module. I tryed with Alsa v. 0.9.6, 0.9.7c, 1.0.6 and 1.0.7rc1
and I always have the following problem. Typing :
   $ modprobe snd-via82xx
Gives the following message repeated 4 times :
   "codec 0 is not valid [0x87e5370]"

I am using DEVFS (because I am using Crux distribution)

Looking into "via82xx.c", I guess it's related to the ac97 module.

Any suggestions ?

Thanks a lot in advance.

Dominic

2. Large hard disk error

3. Newbie Question: Valid File Descriptor Value, Valid Thread Id

4. ESS 1888

5. pcm0: ac97 codec invalid or not present

6. How do I get past the partitions screen?

7. AC'97 codec - cd music not work

8. variable expansion: weird question

9. MPlayer not working after new codecs installed

10. ETH0 not a valid device????????

11. CDROM not a valid block device

12. MS-DOS not a valid mount point

13. External USB hard drive not recognized as valid block device