Re: more install problems

From: Andrew McGuinness (andrew_at_arobeia.co.uk)
Date: 08/01/03

  • Next message: Johann Spies: "exim router question" 
    Date: Fri, 01 Aug 2003 05:45:26 +0000
To: debian-user@lists.debian.org

    Richard Lyons wrote:
    > On Wednesday 30 July 2003 19:54, Andrew McGuinness wrote:
    > [...]
    >
    >>The cause of the errors was that linux/version.h was being included
    >>from a 2.2 kernel, but linux/netdevice.h was being include from a
    >>2.4 kernel.
    >
    >
    > Thanks Andrew.
    >
    > We _may_ be getting somewhere.
    >
    > I have two version.h files:
    > /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/version.h
    > /usr/src/kernel-headers-2.4.18-bf2.4/include/pcmcia/version.h
    >
    > diff says:
    > 1,3c1,4
    > < #define UTS_RELEASE "2.4.18-bf2.4"
    > < #define LINUX_VERSION_CODE 132114
    > < #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))
    > ---
    > > /* version.h 1.94 2000/10/03 17:55:48 (David Hinds) */
    > >
    > > #define CS_RELEASE "3.1.22"
    > > #define CS_RELEASE_CODE 0x3116
    >
    > Should I rename one of them for the compile? or symlink one location
    > to the other having renamed the unwanted one?
    >
    > I have only one netdevice.h:
    > /usr/src/kernel-headers-2.4.18-bf2.4/include/linux/netdevice.h
    >
    > Does that make sense?
    >
    include/pcmcia/version.h isn't a problem.

    The errors you quoted from you compile are in code that shouldn't be
    compiled unless LINUX_VERSION_CODE indicates a 2.2 kernel, at least in
    the rtl8139.c I picked up from scyld.com.

    So either, a different LINUX_VERSION_CODE is being picked up from
    somewhere else, or the rtl8139.c you have been provided is so old or
    hacked up that it only supports 2.2 kernels.

    Options for continuing:

    a) Try to go back completely to 2.2 and compile with that. I don't
    really recommend that, as being stuck with 2.2 kernel will hold you back
    on other things.

    b) Find out where the rtl8139.c on your floppy disk came from. If it is
    patched or modified by the manufacturer, try to find if they have a
    newer version.
    If the changelog doesn't suggest it has been modified by anyone but
    Donald Becker, go to http://www.scyld.com/network/rtl8139.html
    and follow the instructoins there. (That means downloading the four
    files rtl8139.c kern_compat.h pci_scan.h, pci_scan.c and doing roughly
    what you've been doing).

    If that sounds a bit much, I'll try compiling it all for you tonight or
    Saturday morning. I'm getting kind of hooked on this problem.

    It might help if you mail the rtl8139.c you have to me (I don't think
    it's of much value to the list generally) 

    -- 
Andrew



    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Johann Spies: "exim router question"

    Relevant Pages

    • Re: Distributions
      ... | general there are a lot of packages for people to use. ... kernel, have to run on a multitude of different systems, they tend to be ... and slower than if you compile those packages, ... can have that stability with virtually any distro. ...
      (Debian-User)
    • Re: Distributions
      ... Ubuntu is based on Debian, ... | general there are a lot of packages for people to use. ... kernel, have to run on a multitude of different systems, they tend to be larger ... and slower than if you compile those packages, ...
      (Debian-User)
    • Problems with custom kernel fbsd 6.2
      ... My kernel for freebsd 6.2 is not compiling but only with my custom config. ... I was able to compile it with the GENERIC kernel included, but my modified one will not compile. ... # Power management support ...
      (freebsd-questions)
    • Re: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata
      ... >optimisations independently of each other', is fairly simple, (in ... >concept), and elegant, (as it lets you compile the most finely tuned ... >Up to now, selecting a CPU to compile for basically means, "Use ... it's silly to include them all in a kernel for a 386. ...
      (Linux-Kernel)
    • Re: C++ pushback
      ... There are all sorts of macros that use member initialization of that form. ... This does not break the code at run time, this breaks the code at compile time, and should be less painful. ... The kernel relies really _really_ heavily on such structure initializers, and breaking them would effectively break the world as far as the kernel is concerned. ... If they were not, one could simply make a base class having members outlined, and which class does not enforce type safety and is for inheritance only. ...
      (Linux-Kernel)