uaudio usb sound card verified working on NetBSD.

rvp

[   155.971969] uaudio0: autoconfiguration error: ignored audio interface with 2 endpoints
[   155.971969] uaudio0: autoconfiguration error: no usable endpoint found
[   155.971969] uaudio0: autoconfiguration error: audio descriptors make no sense, error=4

Hmm. This may already be working in -HEAD. Can you move the 10.0 kernel, modules and other bits out of the way and try a -HEAD kernel?

# Move 10.0-RELEASE bits out of the way.
#
mv /netbsd /netbsd.10
mv /etc/mtree/set.modules /etc/mtree/set.modules.10
mv /etc/mtree/set.gpufw /etc/mtree/set.gpufw.10
mv /libdata/firmware /libdata/firmware.10
mv /usr/libdata/firmware /usr/libdata/firmware.10

# Extract 10.99.10 (-HEAD) kernel and related bits.
#
tar -C/ -xf kern-GENERIC.tar.xz
tar -C/ -xf modules.tar.xz
tar -C/ -xf gpufw.tar.xz

If that works, but, you want to go back to 10.0, put everything back, then recompile a 10.0 kernel with this line uncommented.

anarchosax

rvp Thanks for the feedback, but I don’t have any idea what you are referring to. I am just a desktop user trying to get things working, and over time learn more about the system.

rvp

anarchosax I don’t have any idea what you are referring to.

Just follow the instructions in prev. post (now with comments!).

Kernel compilation steps I've already given.

anarchosax over time learn more about the system.

Now's your chance! Carpe Diem!

anarchosax

rvp I will take a look at the instructions again, when I have some more time. Despite appreciating your help, my important take away from this is that NetBSD users are being seriously let down. Users are relying on lists of hardware that is “confirmed” to work (as in the case of my other sound card) or purchase a card that is in the same class as what is recommended, yet neither works out of the box. The best case scenario is that users have to compile their own kernel, and when they express the slightest doubt, are told to give it the old college try? We deserve better.

I and many other users are willing to put an effort into learning about NetBSD, but that doesn’t mean that we should have to jump off at the deep end to learn to swim, nor is waiting three more years for the next version of NetBSD. Compiling lists of working hardware goes only so far, if the first thing needed after an install is to compile a kernel.

anarchosax

rvp It seems to me as a user, that the NetBSD fundamentals are sound, but hardware support for particularly WiFi and sound cards (internal as well as USB external) is slow.

Perhaps it is time for NetBSD users to wake up and realize that it is cheaper to try and finance bounties in these areas, rather than everyone ending up with hardware they can’t use… It would also draw new users to NetBSD.

rvp

anarchosax hardware that is “confirmed” to work (as in the case of my other sound card)

The specs. for the old (introduced 2013) Audigy Fx states the chipset used is a Realtek ALC898 but, yours is an ALC899. Marketing names can be tricky. In this case, the PCI ID is also the same, but the chipset is different.

BTW, Creative also says, in the Audigy Fx User Manual, that if you have an onboard or another card present, you should disable that first. Can you try that?

anarchosax [...] but that doesn’t mean that we should have to jump off at the deep end

More like paddling in the kiddie pool, in this instance.

anarchosax the first thing needed after an install is to compile a kernel.

Can't be helped: The complete set of people with commit access to NetBSD has precisely 284 names. These include all developers: kernel/lib/docs/www/pkgsrc/retired/dead/occasionally active people. The number who've actually worked on audio stuff is probably just 2 or 3. How much audio HW would they have access to?

kc9udx

One of the reasons I like NetBSD is because it's "slow to adapt". If I wanted latest, greatest, and so buggy I have to update every day and spend all my time figuring it out, I'd go with Arch. I don't use floppy disks on platforms where I'll use NetBSD. But I'm very happy that I could if I would.

I thought I posted recently about USB "sound cards" that I found to sorta work, but I can't find it at the moment.

anarchosax

kc9udx Slow to adapt is OK as a principle, but if it isn’t possible to find anything currently on the market that works (including eBay) or isn’t confirmed as working and actually works, then that is too slow. I am not looking for the latest and greatest either. In fact, I think that an operating system like NetBSD is far more environmentally correct, as it supports old hardware galore. Despite some of that old hardware being less energy efficient…

Coordination and bounties could avoid users purchasing dongles and what not that don’t work with NetBSD, and increase user and developer satisfaction.

kc9udx

There is hardware available that works. Finding it is the problem.

anarchosax

delete

anarchosax

Interesting problem in the context of the above. I needed to get the computer going for music practice and didn’t have time to try working with the kernel at the moment. I tried installing a number of Linux distros. All said that my built in audio card is disabled and I haven’t been successful in getting it to work again. I am not playing the blame game, but I am wondering if either NetBSD or the usb sound card did this, and what I can do to get it working again…

rvp

anarchosax All said that my built in audio card is disabled and I haven’t been successful in getting it to work again. I am not playing the blame game, but I am wondering if either NetBSD or the usb sound card did this, and what I can do to get it working again…

Don't think NetBSD has that kind of super-power. Try removing the Audigy.

anarchosax

rvp I don’t think so either, but I am almost certain now that the AudioQuest DragonFly Black USB sound card does. I don’t know how it does it, but that would get the sound card to work under both NetBSD and Linux, despite not being supported, and it works under Linux out of the box. Obviously, being class 1.0 compliant has something to to with it as well, but with Windows and Mac, a program is required to switch between sound cards. Maybe it only affects my system this way, I don’t know yet.

rvp

anarchosax I'm afraid you've lost me now: so the AudioQuest USB card was the culprit?

As for getting that to work, see my post #4. You can try the latest -HEAD kernel now, or compile the 10.0-RELEASE kernel with that 1-line change.

anarchosax Obviously, being class 1.0 compliant has something to to with it as well.

Sometimes generic USB class drivers won't do the trick. See PR #58250 which I filed recently. The generic ethernet driver cdce(4) would make the adapter work only in something like 1 out of 10 reboots.

anarchosax

rvp Yes. Actually, (the simplest explanation possibly being the correct explanation) something got overloaded, as switching sound cards wasn’t possible (as with Win and Mac systems)...

rvp

anarchosax something got overloaded, as switching sound cards wasn’t possible

In that case, just try the Audigy again on NetBSD after you pull out any HW or disable in BIOS anything not needed for an audiocfg test of the card. NetBSD's device power management is pretty pathetic.