It detects the Kahula audio It decides there is no module for it (sort of ok since its sb16 and needs hand setup) It says: Driver: Unknown However it also then says "Play test sound", If I hit that it informs me it couldnt load the unknown driver. I claim it worked and I get modules.conf saying alias sound-slot-0 unknown !!
Why would you say "Yes" if you didn't hear the sound?
Why did it put up a test audio button when it didnt know a driver to use. Thats the real problem. I hit it because I was going 'return, return, return, return...' as Im sure others will
Ok, gotcha. I have changed soundcardBackend.probeCards so that it filters out any cards whose driver kudzu reports as 'unknown'. This will fix both firstboot and redhat-config-soundcard. If the card with the 'unknown' driver is the only card in the system, the soundcard screen in firstboot will not appear at all. If there are other cards with valid drivers, they will appear in the soundcard screen in firstboot. If you run redhat-config-soundcard after installation and the card with the 'unknown' driver is the only soundcard in the system, the dialog will say "No soundcards were detected". If there are other cards with valid drivers, they will appear in the dialog. This should prevent anyone from being able to press the "Play test sound" button for a card that we already know doesn't have an available driver. This change should fix both this bug and bug #80884. I'm going to dupe bug #80884 against this report. firstboot-1.0.5-3 and redhat-config-soundcard-1.0.4-1 should contain the fix. QA, please verify.
*** Bug 80884 has been marked as a duplicate of this bug. ***
Also Alan, can you test these new packages if you get a chance? I don't actually have a soundcard that reports 'unknown' as it's driver. I'm pretty sure this fix should work but I can't actually test it myself.
Will look for them in rawhide tomorrow
There is a stack of 64 bugs that have been in Modified state for a long period of time. I am closing these as Rawhide now. If you find that the issue is not fixed, please reopen this report.