"No state is present for card NVidia."
 

Well, for the first time in over 20 years I bought a video card brand other than ATi; a Nviada card. It runs quite well and all the software/drivers work as they should, BUT... :)

When booting up the following lines appear on the screen just before getting to the command prompt:

"No state is present for card NVidia
Unknown hardware: "HDA-Intel" "Nvidia GPU 0a HDMI/DP" "HDA:10de00a,10de0101,00100100" "0x19da" "0x6132"
Hardware is initialized using a guess method
No state is present for card NVidia"

I haven't seen much of anything on the 'Net that explains this.
Thanks.

Is that the exact way that the error message(s) looked on the screen? If not an exact copy+paste, would you please check /var/log/dmesg or /var/log/messages etc., and see if this and/or more information is in there, and copy + paste that here for us? Thanks.

Also, please describe the hardware - what model of video card is this, and in what sort/make/model/motherboard of machine is it in? Is it a laptop/desktop? Is it the only video device inside the machine? What about audio - how many audio devices present?

A few Googles seem to indicate that it's related to the audio side of an HDMI interface, but yes, not a whack of information on the net.

Here's one thread, don't know if you've looked at it (and it's about SuSE Linux):
http://forums.opensuse.org/english/g...ot-joking.html
I only read that page there, and there are more before+after than page. Looks interesting. Maybe something helpful in there? Also, the posters in the thread are looking at some command output, like `lspci` and similar commands (some appear to be SuSE special scripts?) to get more info about the hardware; perhaps posting similar output here will help someone help you.

Good luck!

EDIT: P.S> they mention checking for sound-related BIOS settings in that thread - that's a not-bad idea; see if there's something you can turn on, or off, that alters the messages.

I have only guesses here so keep that in mind. The "Unknown hardware" and "guess method" lines are almost certainly an indication that ALSA doesn't know how to handle the card, so it guesses certain options to pass to snd-hda-intel. If it works, then great -- the messages can be ignored. If not, you may have to pass model options to snd-hda-intel (or pass more advanced options...but usually model options are enough). I don't have an HDMI port to test this on...but I believe (and I could be wrong) that HDMI ports are listed as S/PDIF ports in alsamixer (and therefore should be unmuted). What is the output of the following:
The "No state" error should be easily fixed...delete (or move, to be safe) /etc/asound.state and reboot (or restart alsa?). They are misleading anyway, since digital audio is not really controlled the same way, but I suppose digital devices can be muted/unmuted.

GrapefruiTgirl, That is the exact message.

T3slider, It appears to have audio capability. Since it is a video card it never
occurred to me that it would also be a sound card. I haven't had much time today
to play with it, but I did check the windows drivers and the card apparently has
Surround Sound 7.1.
When I have more time I'll play with it and report back.

Boy, did I screw up this time!
I was trying to get the Nvidia sound to work, but no luck. It works in xp, btw,
and while kde can see it, alsaconf cannot.
Anyway, I went back and ran alsaconf, alsamixer and alsactl store, but now there
is no sound. I've done it three times and re-booted each time, but no sound.
Any ideas on how to fix this?
Many thanks!
:hattip:

if you look in slackware13.1 and current "CHANGES_AND_HINTS.TXT"

I again ask for the following output. As your regular user:
As root:
HDMI is the optimal method for outputting digital audio, since it can handle 5.1/7.1 uncompressed (unlike S/PDIF, which gets only two channels uncompressed and must use compression to get 5.1/7.1). If you can get it working, it would of course be better to use that than whatever else you were using (unless you have a 5.1/7.1 analog set of speakers already and are lacking speakers for a digital setup...). The output of the above commands should give a general picture of how your card is being recognized by ALSA.

Googling the product ID (0x6132) suggests you have an nVidia GeForce 210.
Here are a couple of links that discuss getting the HDMI audio to work. I think the key may be to create a file in /etc/modprobe.d that includes "options snd-hda-intel probe_mask=0xfff2". If you are running -current then there is support for the card in the kernel using the snd-hda-codec-nvhdmi.ko module.
https://bbs.archlinux.org/viewtopic.php?id=90350
http://wiki.xbmc.org/?title=HOW-TO_s...20%2C_or_GT240

I have sometime today, so here is aplay -l:
and

and as root:

and

I have to run out, but will do some reading on the subject and be back later.
Many Thanks.

It looks like it is all being recognized properly, so it may just be a configuration issue...but if it doesn't work at all, allend's advice may be valid. Does the following command get sound? (If not, give the output)
If that fails, try changing the 8 (7.1) to 6 (5.1) or even 5 (5.0)...I don't know what your speaker setup is, but if you just have 2 speakers then you would obviously only get sound from 2 channels. If you *do* get sound, then you just have to configure your hdmi device as the default sound device. If you *don't* get sound from that, and the following doesn't work either (give output if it fails...this can fail for other reasons as well), then it's not working at all and you may have to try passing options to the module itself as allend suggested.
^^ Be careful with that -- it might be *loud* depending on the volume you have set on your receiver, and it may even damage the speakers if played at full volume (not to mention your ears).

Many thanks for the information. I've used it a few times now to get back to the original sound settings.
:)
:hattip:

If possible, I would be interested in seeing the results of the following 2 commands:

The usage of the outputted data, would be to look into the kernel snd-hda-intel driver and related patch files which contain the quirks, bios workarounds, and widget values for different sound devices, and see if your exact make & model is listed in there (or what very similar models), and if so, what exact option(s) you should/could be giving the driver upon modprobe, so that it identifies the card correctly. If your device is not listed there, it'd very probably contribute to the current situation.

I went through this procedure with my current Realtek 888 device (when this was a new mobo), because it used to boot up with "Unknown HDA audio device..." but it would still make sound. I found that while my exact model was not yet in the kernel, it was similar to some other models and I was able to add the model, vendor & product ID to my kernel, create a patch, and have it added to the patch_realtek.c file. A few kernel releases later, it was included. If your device happens to be in the same boat, you could conceivably do the same -- but I'm getting ahead of things here. Let's look at the data first please, if/when you have a moment. :)

Thank you. Right on the button.
After reading the above and the information at the link provided by GrapeFruitgirl, thank you :) , I was able to get it running for a short while, but with no controls other than volume and then the volume was very low, so I went back to the onboard Intel device. Also, alsaconf does see the card,
but it is seen in alsamixer.
Provided there are additional controls, yet to be found, I would like to get it working as the default device, so I'm still working on it as time permits.
Thanks.
:hattip:

Here you go:

and

Many thanks for your time and effort.
:)

I tried the speaker test with various numbers and the result was always the same:

and,

Many Thanks!
:)