If you have an isa pnp Soundblaster I think the only way to get sound at all is through a modularized driver and isapnp. I never had any luck compiling sound into the kernel directly, but it has always worked perfectly when compiled as a module and initialized by isapnp at boot. Now that I am back to using 5.2, it will be interesting to find out why 5.3 partially broke sound on my box. I imagine by 6.0 this will be a non-issue as I believe that 2.0.36 will use a 2.1.x style sound driver, which, if I'm not mistaken, is different than how sound is handled in 2.0.x kernels. Fred A. Miller wrote:

I have the AWE-64 (ISA), and was unable to get sound compiled as a module or in the kernel, so paid my $20 for the OSS drivers. I notified

-- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hubert Mantel wrote:

Hi,

On Mon, Sep 07, Michael Lankton wrote:

...

non-issue as I believe that 2.0.36 will use a 2.1.x style sound driver,

No, the modularized driver will not be in 2.0.36

Ok, then when will audio be handled correctly? Fred -- - Windows 98 supports real multitasking - it can boot and crash simultaneously - Fred A. Miller, Systems Administrator Cornell Univ. Press Services fmiller@lightlink.com fm@cupserv.org - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Until it hits ftp.kernel.org, 2.2.0 is as real as Santa Claus as far as I'm concerned. There are still too many problems with 2.1.x to be talking about 2.2.x yet. _If_ 6.0 makes it's expected holiday release, say, hypothetically, that the 2.0.x kernel is at 2.0.37 and that 2.2.0 has just been released. 2.0.37 would be a wiser choice to include with the distribution because 2.0.x is proven to be a mature, reliable kernel. I expect early 2.2.x kernels to have their share of hiccups even though they are part of a 'stable' development branch. S.u.S.E. of course would include both, so the choice would ultimately be left to the individual, as it should be. Kaare Rasmussen wrote:

...

No, the modularized driver will not be in 2.0.36

Whaat kernel version are you planning? It will look funny if you use 2.0.3x if 2.2 alrady is out.

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

-- .###. /#######\## -==============================================- ;##### ;# Mike's WindowMaker ;##### ;# <A HREF="http://tasteslikechicken.ml.org/windowmaker.html"><A HREF="http://tasteslikechicken.ml.org/windowmaker.html</A">http://tasteslikechicken.ml.org/windowmaker.html</A</A>> \# /## -==============================================- ###'---'#### - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

On 08-Sep-98 Kaare Rasmussen wrote:

...

Until it hits ftp.kernel.org, 2.2.0 is as real as Santa Claus as far as I'm concerned. There are still too many problems with 2.1.x to be

Problem is that 6.0 will be sold until jan/feb 1999. If 2.2 is out in september, that will make œ a year on an old kernel line. Not a good selling point.

But perhaps as you point out, there could be two kernels.

That's ASSUMING that 2.2.x is that close to release ========================================================================= * <A HREF="http://benham.net/index.html"><A HREF="http://benham.net/index.html</A">http://benham.net/index.html</A</A>> * * -------------------- * -----BEGIN GEEK CODE BLOCK----- ---------------* * Darren Benham * Version: 3.1 * * <gecko@benham.net> * GCS d+(-) s:+ a29 C++$ UL++>++++ P+++$ L++>++++* * * E? W+++$ N+(-) o? K- w+++$(--) O M-- V- PS-- * * Debian Developer * PE++ Y++ PGP++ t+ 5 X R+ !tv b++++ DI+++ D++ * * <gecko@debian.org> * G++>G+++ e h+ r* y+ * * -------------------- * ------END GEEK CODE BLOCK------ ---------------* ========================================================================= - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Michael Lankton wrote:

If you have an isa pnp Soundblaster I think the only way to get sound at all is through a modularized driver and isapnp. I never had any luck compiling sound into the kernel directly, but it has always worked perfectly when compiled as a module and initialized by isapnp at boot. Now that I am back to using 5.2, it will be interesting to find out why 5.3 partially broke sound on my box. I imagine by 6.0 this will be a non-issue as I believe that 2.0.36 will use a 2.1.x style sound driver, which, if I'm not mistaken, is different than how sound is handled in 2.0.x kernels.

I hope so, cause this is a pain in the butt! Fred -- - Windows 98 supports real multitasking - it can boot and crash simultaneously - Fred A. Miller, Systems Administrator Cornell Univ. Press Services fmiller@lightlink.com fm@cupserv.org - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

David Bellows wrote:

hello all,

I have an AWE 64 installed on SuSE 5.3. Running Maelstrom with the ``free" OSS that comes with SuSE Linux produces wonderful sound. I wish I could tell you why it's working for me but I'm not that knowledgeable yet.

I wish you could as well! Fred -- - Windows 98 supports real multitasking - it can boot and crash simultaneously - Fred A. Miller, Systems Administrator Cornell Univ. Press Services fmiller@lightlink.com fm@cupserv.org - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e