Mailinglist Archive: opensuse (1784 mails)

[john_meyer@xxxxxxxxxxxxx (John Meyer)]

From: "John Meyer" <john_meyer@xxxxxxxxxxxxx>
Date: Sat, 9 Dec 2000 08:31:12 -0700
Message-ID: <NEBBJDMFDIGHFPHPAMEMOENDCEAA.john_meyer@xxxxxxxxxxxxx>
Subject: 3com 3c509b NIC - Here's the way I did it.



For my card, I simply went into /etc/conf.modules and typed this:

options eth0 irq=7

Seemed to work like a charm, but I'm not so sure that's the best way to do
it.

-----Original Message-----
From: Tor Sigurdsson [mailto:tosi@xxxxxxxxxxxxxxxxxxxx]
Sent: Saturday, December 09, 2000 6:43 AM
To: suse-linux-e@xxxxxxxx
Subject: Re: [SLE] 3com 3c509b NIC - Chap 2

<p>Hi,

What is it exactly that you are trying to accomplish ?

Do you have two 3c509 cards ?

Please, for those that reply to this thread: 3c509 is NOT a PCI card, and
thus
catting /proc/pci is totally useless :-)

Also, if you have two 3c509 card, the second card WILL be problematic !

( my firewall has two of them, and here is my solution that I use :)

In /sbin/init.d/network I added the following lines to the script making
sure
that the interface was loaded ( compare to your own script to see the
differences )

*******************************************+
case "$1" in
    start)
        /sbin/rmmod 3c509
        sleep 4
        /sbin/modprobe 3c509
        sleep 4
        ifconfig eth1
        sleep 2
        /sbin/rmmod 3c509
        sleep 4
        /sbin/modprobe 3c509
        sleep 2
        ifconfig eth1
        for I in $NETCONFIG; do
********************************************

See ? It's kinda dumb, but it actually works. It seems that with more than
one 3c509,
the cards don't register correctly ( or fast enough ) with the networking
subsystem.

This seems to correct the problem...

Also, I don't have any append=" line in lilo.conf, as that didn't help any
in my situation.

Hope this helps.

-tosi

On Tue, Nov 28, 2000 at 07:26:01PM +0800, Robert Sweet wrote:
> On Fri, Dec 08, 2000 at 10:32:25AM -0500, Michael Long wrote:
> > <snip ... a big sigh of relief is heard by many :) >
> >
> > I have tried RTFM, searching the suse website, emailing suse support and
am
> > still at a loss.  When the system boots the network does not come up.
After
> > running the following scripts the network starts up.
> >
> > /sbin/init.d/dhclient restart
> > /usr/sbin/rcnetwork restart
> > /sbin/init.d/firewall restart
> >
> > I added the following line in lilo with no affect.
> > append="eth0=0xfce0,eth0 eth1=0x300,eth1"
> > What does 0xfce0 represent?
> >
> > Sorry for the frequency of my questions on this subject, but as you can
tell I
> > am new to both Linux and configuring networks.
> >
> > Thanks,
> > Mike
> >
> > > Also check the FAQ at http://www.suse.com/support/faq
> > > If you have more than one nic, you will need to edit
> > > lilo.conf:
> > >
> > > append="eth0=0xfce0,eth0 eth1=0x300,eth1"
> > >
> > > Otherwise only one may show up. I use yast1 for nic setup.
> > > --
> > > rsweet@xxxxxxxxxxxx        | Baker's First Law of Federal
> > > 		      -o)  | Geometry:  A block grant is a
> > > Linux, the Choice      /\  | solid mass of money surrounded
> > > of a GNU generation   _\_v | on all sides by governors.
> Sorry, you need to put your own hardware info...
> 0xfce0 is from /proc/pci:
>
>   Ethernet controller: Realtek 8029 (rev 0).
>       Medium devsel.  IRQ 11.
>       I/O at 0xfce0 [0xfce1].
> If you do a less or cat /proc/pci it will give you the
> hardware address. You are telling the system "Hey I have 2
> ethernets, one at XXXXXXX and one at XXXXXX. Hope that
> clarifies things.
> --
> rsweet@xxxxxxxxxxxx        | Maternity pay? Now every Tom,
> 		      -o)  | Dick and Harry will get
> Linux, the Choice      /\  | pregnant.   -- Malcolm Smith
> of a GNU generation   _\_v |
>                            |
>

--
                                         ______
 /---------------------------------------\     \
| Þór Sigurðsson     | Tor Sigurdsson     |  t  |
| Netmaður           | Network Specialist |  o  |
|-----------------------------------------|  s  |
|               tosi@xxxxxxxxx            |  i  |
 \---------------------------------------/_____/

--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/support/faq