-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> > For instance, since he has an integrated AC97 sound card, Mandrake won't > > let his SB Live! work properly that has worked in every other GNU/Linux > > distro he has tried (including 8.2). > > what exactly are you referring to here? Or could you give me a bug number? My friend did not report it because he just finally concluded it wasn't anything he was doing wrong yesterday, and when I mentioned that the release would be out in 10 days, he felt so disappointed in the quality of the almost finalized distribution's stability, he just decided not to report it at all. Here is the problem from a message he posted on another list: - ---------------------------------- Even though mdk 8.2 installed perfectly on this box, mdk 9.0 couldn't even get through the install scripts, so I couldn't install it. Mdk 9.1 gets through the scripts ok, and the install appeared to be ok, but there are serious faults. The first is that no matter which xserver config I choose KDE 3.1 locks up on me several times a day, requiring a reset button. Secondly, 9..2 insists on installing the mobo AC97 sound chip even though I have a mobo jumper set to disable it. I was able to get sound as root, but not as user. In reinstalling the SBLive sound card I lost root too. Now, no sound. I do get a message as user saying that the sound driver could not find the device or file name, which means the /dev file doesn't exist or has the wrong permissions. Putting me into audio didn't help, neither did chown or chmod on the /dev/sound files. Quite frankly, since there are only 10 days before final release of 9.1 I see no hope of Mandrake fixing these problems before then, so I plan to do a rescue of my MDK 8.2 side (which 9.1's lilo blew away without asking). - ---------------------------------- More details: - ---------------------------------- For the first time in 6 years I am unable to get my sound card running! At this point I believe it is a weakness in the detection and installation software of rc1. The exact same hardware was easily setup when I installed MDK 8.2. When the sound card was first detected during the initial install it would work when I logged on as root but not as user. "Ah, ha!", you say, "permission problems". That's what I thought. So, I added myself to the audio group. No joy. Then I went to /dev/asound and made everything root:audio. No joy. I don't want to make the the /dev/asound jerry:audio, that's no solution. During my examination of the sound situation I noticed that the kmixer was showning AC97 components. That is odd, because I have AC97 sound (which is on my mobo) turned off in the bios. It looks like the autodection is adding AC97 (including modules!) regardless of what sound card I choose from the configure button of the Hardware listing in MCC. - ---------------------------------- Leon Brooks, yes, the one that's here too, suggested the good idea of trying switching to OSS from ALSA (or vice versa), but alas it seems the fellow who wrote this had already tried that. I can have him contact you if you'd like certain details... he isn't on this list due to its high traffic. -Tim - -- - ---------------------------------------------------------------- Timothy R. Butler [EMAIL PROTECTED] Universal Networks http://www.uninet.info Christian Portal and Search Tool: http://www.faithtree.com Enterprise Open Source Journal: http://www.ofb.biz ================================================================ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Zqu8K37Cns9gJ0gRAk58AJ9P02RoIlo5w6uZhlWP8L9W1lzT0QCdFnNy pLQ2mCJPrxLkE7I94u7PWig= =i4y/ -----END PGP SIGNATURE-----
