John,
I get the impression that there was a lot I was doing wrong in the
configuring of the kernel before compiling it. Most of the problems though
centered around configuring for sound and Network. I'm not too clear on
why yet.
With Kernel 2.4.0-test9 the biggest troubles were with getting iptables
and net filters to configure correctly. Never was able to get them working
right. With kernel 2.3.4 I can't get the sound configured at
all. Everything else works though including ipchains. I really wanna hear
what this Turtle Beach sound card sounds like.
--
Mark
/* I never worry about the to-jams.
* Once I've stuck my foot in my mouth
* it's already too late...just make sure
* you chew them thoroughly before swallowing!
*/
Registered Linux user #182496
* Pine 4.21 *
On Mon, 23 Oct 2000 4:03am ,John Rye spake passionately in a message:
> Mark Weaver wrote:
> >
> > Larry...John...Lonny and others,
> >
> > I've done it! I managed to get Linux-2.4-test9 to compile and work! It's
> > running at the moment and it took a few times round and round to get
> > TCP/IP and PPP to work, but by God it's working. Now I'm curious to see if
> > I can get this Turtle Beach sound card working on here which was the
> > original reason I started on this adventure in the first place.
> >
> > --
> > Mark
> >
> > /* I never worry about the to-jams.
> > * Once I've stuck my foot in my mouth
> > * it's already too late...just make sure
> > * you chew them thoroughly before swallowing!
> > */
> > Registered Linux user #182496
> > * Pine 4.21 *
> >
> > On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message:
> >
> > > [EMAIL PROTECTED] wrote:
> > > >
> > > > >Is there a compilable kernel anywhere on this planet that will not bail
> > > > >on your with a ridiculous error making it impossible to update or
> > > > >recompile your kernel in any manner? Below is the result of my latest
> > > > >attempt to configure and compile a linux kernel. This one is
> > > > >2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause.
> > > > >
> > > > >
> > > > >sincerely fed up and frustrated,
> > > > >
> > > > >Mark
> > > >
> > > > Ummm....ok first you are going to have to do some digging to find out what
> > > > you need for the header/include files you are missing OR if you have them
> > > > ... check to see where the current tree (for the compile) is looking for
> > > > them. Can you send the output from a find / -name errno.h none of what
> > > > you have posted is *post* compilation and it looks like it couldn't create
> > > > the .o files to link in in order to continue. Compiling isn't always as
> > > > easy as "./configure, make, make install" ;-) or make make bzImage make
> > > > dep make modules etc etc, trouble shoot this first by figuring out where
> > > > the missing includes are or if you have them "usr/include/bits/errno.h:25:
> > > > linux/errno.h: No such file or directory" (you may have to look in the
> > > > Makefile(s) to see what the root dir is in order to find out "where" it
> > > > thinks linux/errno.h is or what linux actually is pointing to ... its
> > > > usually a sym link to the CURRENT kernel source .... ls -l should be
> > > > pretty easy to work from there =o)
> > > >
> > > > -Lonny
> > > >
> > > > +++++++++++++
> > > >
> > > > In file included from /usr/include/errno.h:36,
> > > > from scripts/split-include.c:26:
> > > > /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory
> > > <snip>
> > >
> > > Did you download the matching kernal-headers?
> > >
> > > I had something similar when I attempted my first kernal compile
> > > on 2.2.16 from a tarball.
> > >
> > > Cheers
> > >
>
> Did you establish what the problem was? Something missing? Malformed?
>
>
