Re: Kernel 2.2 and 2.4: boot differences?

From: Adrian Zimmer (AZimmer_at_ossm.edu)
Date: 07/29/03

  • Next message: Hugh Saunders: "Re: new-bie problem"
    Date: Tue, 29 Jul 2003 09:35:31 -0500
    To: <debian-user@lists.debian.org>, <bob@proulx.com>
    
    

    No, no; ifconfig says the interface is up and running with both
    kernel images. Obviously *a* tulip module is installed (one way
    or the other). Happens to be two different ones.

    I compiled tulip in to 2.4.18 whereas I don't know how the prepackaged
    2.2.20-idepci worked. I'd kinda like to try the driver that shipped with
    2.2.20 but I don't know how to answer configuration questions to get it
    insted of the driver I now have compiled into 2.4.18.

    I don't know the driver in 2.4.18 is malfunctioning; I know only
    four things that seem relevant:
       ifconfig is happy;
       netstat only reports success with 2.2.20-idepci not with my
              compiled 2.4.18;
      the base addresses used by the two tulip modules are different;
      the configuration files the two kernel images are booting under
             are the same.

     (Of course, the configuration files ask for different things because of
    what they find in the /proc directories but that is a fact I don't know
    how to exploit in tracking down my problem.)

    J Adrian Zimmer
       www.ossm.edu/~azimmer
       azimmer -- dot -- ossm.edu

    >>> Bob Proulx <bob@proulx.com> 07/28/03 10:47PM >>>
    Adrian Zimmer wrote:
    > with 2.2.20 I get
    >
    > eth0: Accton EN1217/EN2242 (ADMtek Comet) rev 17 at 0xc6022000, 00:D0:59:24:04:C0, IRQ 11.
    > eth0: MII transceiver #1 config 3000 status 786d advertising 01e1.
    >
    > whereas with 2.4.18 I get
    >
    > eth0: ADMtek Comet rev 17 at 0x1c00, 00:D0:59:24:04:C0, IRQ 11.

    Googling and then looking at the tulip_core.c driver shows that the
    tulip driver is used with this card.

    Did you compile the tulip driver into your kernel? Or did you compile
    it as a module? If as a module did you load the tulip driver in
    /etc/modules? If you are using the Debian tuned kernels then
    everything is compiled as a module and you will need to include tulip
    in /etc/modules.

    Bob

    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Hugh Saunders: "Re: new-bie problem"

    Relevant Pages

    • Re: Kernel 2.2 and 2.4: boot differences?
      ... *after* tulip gets set up --- right where I would have thought things would ... On Tue, 2003-07-29 at 09:35, Adrian Zimmer wrote: ... > insted of the driver I now have compiled into 2.4.18. ... > Did you compile the tulip driver into your kernel? ...
      (Debian-User)
    • Re: Cant get on internet (10.2)
      ... I'm accustomed to using Symantec Ghost for partition-image backups. ... my workstations and other servers. ... Turned out it was a problem with the "Tulip" driver for my ... The so-called Tulip NIC has had problems like that over the ages. ...
      (alt.os.linux.suse)
    • Re: [patch] net/tulip: LAN driver for ULI M5261/M5263
      ... > We want to extract our LAN card driver from tulip core driver and make a ... > new file uli526x.c at tulip folder, ... > because we have added some ethtool interface support and non-eprom support ... have not applied a "fix tulip for ULi" patch is that it changes PHY ...
      (Linux-Kernel)
    • Fixed! (Cant get on internet in 10.2)
      ... There is a thread there about problems between the Davicom on-board ethernet controller and the "Tulip" driver. ... h3h_timo said to edit a file /etc/modules. ... Instead I was able to drill down to the "Tulip" driver in YAST and change it to "dmfe". ...
      (alt.os.linux.suse)
    • Microsoft MN-130 PCI Ethernet Adapter working on RedHat 9
      ... The Microsoft MN-130 PCI Ethernet Adapter seems to use the chip ADMtek ... and thus the driver "tulip" is the appropriate driver. ...
      (RedHat)