Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

On Sat, 19 Feb 2005, David Moberg wrote:

> ----- Original Message -----
> From: "sindi keesan" <keesan AT sdf.lonestar.org>
>
> I'm combining several replies here so bear with me please. All of
> these replies are on the same general subject (building a kernel
> with modules)
>
> > I still don't know what corresponds to soundcore.o or uart401.o,
> > even assuming lowlevel is soundlow.o.  Help?
>
> CONFIG_SOUND=soundcore
> CONFIG_SOUND_OSS=sound
> uart401 should come with the SB driver, if not then enable
> CONFIG_SOUND_MPU401. Note the warning in the documentation for
> CONFIG_SOUND_MPU401 regarding usage with the SB16.


I will try without MPU401 first, and with LOWLEVEL and VMIDI and the 
above.

> > Does slhc.o correspond to something I should configure?
>
> You need it for kernel-mode PPP and SLIP connections, as it's the
> basic building block for the two.

I assumed I need it but I don't recall being asked about anything to 
configure that looks like it, just for PPP and SLIP.  Does it come with 
one of them?

> <---earlier message--->
>
> > The sb.o module was I think supposed to make sound devices and did
> > not (I had to mknod various dsp and audio devices)
>
> You have to make devices unless you use devfs (a can of worms in itself
> IMO).

With esssolo1.o I did not need to make devices (but maybe I had made them 
already somehow on that computer?)

> > I took your advice and made everything possible as modules except ppp
> > (which I use all the time) and cd-rom support.
>
> Some things work much better if they're in the kernel at boot time, such
> as the serial driver (if you're using a serial console) and ISAPNP (devices
> are autodetected).
>
> > but I will have to redo after hand-editing .config
>
> Good luck. I always use the configuration tools, as hand-editing may cause
> problems with configuration dependencies.

I will try one more time using the tools since it still did not work when 
I compiled again (after doing make clean) with OSS VMIDI SOUNDLOW (is 
this needed?  soundlow.o insmodded before I configured for it).
I tried to insmod sound using my kernel and still got
isa_dma_bridge_buggy

I don't think I get that with the bare.i kernel.

This also happened on a different computer with the same kernel.

The computer where I compiled the kernel is one of two ASUS boards that 
will not play ripped wav files in linux (they do play in DOS, and in linux 
I can play files that came with SB16 package for DOS).  When I try, I get 
an error message about IRQ/DRQ conflicts.  Is it possible that the kernel 
was compiled to give me this message, because of the motherboard that it 
was compiled on, so that I would not try to use sound on it?

I suppose I can try compiling with the same .config directly on the other 
computer to test this theory.  Or compiling with the bare.i .config on the 
ASUS computer to see if I get the same problem (in which case I should 
pick another computer to compile an all-purpose kernel on, assuming I can 
find one that is not buggy in some way, which seems unlikely since two 
don't load loop BL3, three don't loadlin without MSDOS 7, and one keeps 
changing its cpu speed).  Is it best to compile on a faster computer?  I 
looked at top while compiling and it only uses about 5% of memory (I have 
256MB in that computer but have not been using more than about 16) but I 
think it used nearly all of cpu once in a while.  Gzip is most cpu 
intensive.


> > I did not compile to support mdacon.o but it works as a module anyway
> > in BL2 and BL3.  Why?
>
> Some modules are compatible between different kernels. Your mileage may
> vary drastically, as other modules may spit out pages of unresolved
> symbols on insertion, force a kernel panic, or worse.

BL2 and BL3 use the same modules, but I was wondering why I did not have 
to answer any questions about mdacon while configuring to compile.  What 
exactly happens to the kernel when you tell it, for instance, to let you 
use the sound.o module?

> <---earlier--->
>
> > Do I really need to 'make dep'?
>
> Only for your first configuration, or after a drastic change.

What counts as a drastic change?  Do I need to make clean every time I 
change .config by adding another module?  (Or if I subtract something?).

Thanks for all the help.

> David
>
> --
> _______________________________________________
> Find what you are looking for with the Lycos Yellow Pages
> http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
>
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org