Re: Network Card SMC2635W (ADM8211 Chipset) Setup

From: duncan brown (duncanbrown_at_linuxadvocate.net)
Date: 04/29/04

  • Next message: Robin Laing: "Re: Setting Up Video Server" 
    Date: Thu, 29 Apr 2004 14:52:04 -0400 (EDT)
To: <fedora-list@redhat.com>

    Ian Wallace said:

    > I've downloaded the driver source from ADMtek and compiled it using the
    > kernel sources for the kernel I'm running (2188.nptl). That works ok,
    > and when I pop in the card I can see in /var/log/messages that it
    > recognizes the card, and loads the 8211 driver.

    ha! HA HA HA! someone *else* shares my pain.

    i have a belkin nic that has the admtek chipset, the 103 drivers work for
    about 30 minutes and then the nic is unresponsive, retsarting the network
    helps for about 15 minutes. i'm testing 105, which seems to be alot
    better.

    if you have a wired nic and a wireless in the machine, you NEED to
    configure two ifcfg-eth* files, as fedora doesn't seem to do it with this
    chipset.

    now, what you need to check is this in your ifcfg-eth0 file (the one for
    your wireless nic)

    /etc/sysconfig/network-scripts/

    for your wireless nic put in the HWADDRESS="" line, inserting your
    hardware MAC/ETHERNET address in there

    make sure you have an ifcfg-eth1 for your wired nic, and add the
    HWADDRESS="" line for that also.

    also, if you're using the wireless as your default route out to the world,
    get rid of the GATEWAY="" line in your wire'd nic's ifcfg-eth1 file

    now, check your /etc/modules.conf and make sure that the appropriate
    module is listed there for your different nics (my wired nic is natsemi)

    alias eth0 8211
    alias eth1 natsemi

    now, i don't know if the gui tools work well taking care of this, the
    machine i did this on is only a p200 with 96mb of ram, and i didn't feel
    like waiting an hour for things to load.

    -d

    -+(duncan brown
    -+(duncanbrown@linuxadvocate.net
    -+(http://www.linuxadvocate.net

    () ascii ribbon campaign - against html e-mail
    /\ - against microsoft attachments

    Blessed is the man who, having nothing to say, abstains from giving wordy
    evidence of the fact.
                    -- George Eliot 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Robin Laing: "Re: Setting Up Video Server"

    Relevant Pages

    • Re: Udev coldplugging loads 8139too driver instead of 8139cp
      ... loads the driver for my NIC: ... There are 2 drivers for 8139-based NICs. ... of hardware, which both uses the same PCI identifiers. ... two) loads and actually checks which hardware we have here. ...
      (Linux-Kernel)
    • Re: Udev coldplugging loads 8139too driver instead of 8139cp
      ... loads the driver for my NIC: ... There are 2 drivers for 8139-based NICs. ... of hardware, which both uses the same PCI identifiers. ... two) loads and actually checks which hardware we have here. ...
      (Linux-Kernel)
    • Re: How to test a nic card?
      ... check yours against the photos on the download page for the proper driver ... it resolves the problem- some nics have trouble negotiating link speed with ... >>Windows 2000 IP Configuration ... >>Ethernet adapter Local Area Connection: ...
      (microsoft.public.win2000.networking)
    • Re: 2nd NIC ifconfig
      ... also assume eth0 and eth1 are different types of nics and thus need ... then ifconfig eth1 to bring the card up ... if you don't know the driver needed for the secound card. ... I know by using each NIC one at a time that all four NICs I've tried ...
      (comp.os.linux.networking)
    • Re: ethernet inteface: lost connection
      ... chipset nVidia, with a AMD64 CPU, and onboard NIC is nForce. ... While I'm having a problem with the onboard NIC, it's driver ... Why do you assume I have 2 "onboard" NICs? ... unknown hardware address type 776 ...
      (comp.os.linux.hardware)