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>
>
> > > > 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.
It appears to have configured itself properly since I am now online with 
the new kernel that I compiled.

bare.i  kernel - 735763 bytes
BL2 kernel -    512425 bytes - has NLS support, 386/math emu
my kernel   -    458604 bytes (434K) - no NLS, no math emu, but I added
module support for scsi (sg sr sd idescsi) and sound (sb, trident, ess1730 
1731)

Under ethernet I said yes to tulip and 3com but there was nothing about my 
rtl8139.  It works anyway.  I could make a smaller single-purpose kernel 
but I wanted one I could share (with anyone using the aic7xxx.o module for 
Adaptec scsi card).  If you have a different scsi card and want a kernel 
let me know.  This boots faster than the bare.i kernel (it does not do 
RAID etc.)  ppp is in the kernel, not a module (but my rc.S seems to have 
loaded the module anyway).

> > 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?
>
> I suppose if you configure either PPP or SLIP it is automatically
> included.
It was.

> > With esssolo1.o I did not need to make devices (but maybe I had
> > made them already somehow on that computer?)
>
> Probably. Someone mentioned earlier that one of the sound packages
> comes with modules? In any case, if the device files don't exist
> on your partition you'll have to set that up.
Christof's BL3 and Bl2 sound packages for sb came with the devices.

> > > > 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 finally figured out the sound problem by looking in the bare.i config 
file for DMA, and then I tried to add by hand CONFIG_BLK_DEV_IDEDMA and 
CONFIG_IDEDMA_AUTO but make dep was not happy so I did a make clean, make 
config, make dev (having saved my old .config for reference).


It is not at all clear what is being recommended since sometimes when 
configuring you see N/y/m but the help file recommends Y. This time I 
erred on the safe side and included most things they recommended.


> > I tried to insmod sound using my kernel and still got
> > isa_dma_bridge_buggy
>
> That should never happen with a fresh kernel + modules. Perhaps you
> have a corrupted source archive? Although that doesn't seem likely.

No, I was missing a couple of things for DMA.
> > This also happened on a different computer with the same kernel.
>
> I think that's an unresolved symbol in the kernel, rather than a comment
> on the condition of your ISA bus. Try a different kernel version if you
> can, if reconfiguration doesn't help.
Reconfiguring was the trick - it was not the motherboard.

> > 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?
>
> Perhaps the kernel driver doesn't support the sampling rate/data size
> of the ripped wav files but does support the SB16 files? If that's the
> case, you'll either need a newer driver, or conversion to a more
> primitive format.

How do I tell what rate the SB16 files were sampled at?  I am new to this 
but somehow eventually managed to learn to copy audio CDs.  First I needed 
to get a later cdda2wav to deal with copy protection, then put back the 
earlier cdrecord when the newer one would not work on my system.  I don't 
really need to listen to the .wav files before burning them, but the 
simplest solution would be to move the CD-burner to a different computer. 
I was trying to keep all the scsi stuff in one computer but I will just 
switch to using this new kernel everywhere since it does not take up more 
space than the BL2 kernel.

> > 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?
>
> When you insmod? Or when you select =m from configuration and then make?
When you configure and make, having told it to use a module later.


> > Thanks for all the help.
>
> You're welcome.

Another major victory for me - I could not have done it without the 
support.  I will try this kernel with the scsi scanner and zip drive next. 
(Or maybe redo my scrambled DOS drive).

If anyone else wants to try out this smaller kernel with sound and scsi 
(for my adaptec card) support:
keesan.freeshell.org/zImage.ss5  (for sound scsi 586)
keesan.freeshell.org/config.ss5 (rename .config if you want to use it)

> 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