public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Alge <mail@thorsten-alge.de>
To: Linux Newbie <linux-newbie@vger.kernel.org>, alge@ip-exchange.de
Subject: nic wount work with 10baseT-FD
Date: Thu, 17 Mar 2005 17:58:48 +0100	[thread overview]
Message-ID: <1111078728.4377.15.camel@localhost.localdomain> (raw)

Hi,

we have some problems with some of our servers. We have pcchips
motherboard with sis900 nics. the problem is, they are standardly set to
autonegociate and will work with 10mbps half-duplex but we do need
10mbps full-duplex.
we can set it to 10baseT-FD with "mii-tool" or "ethtool" but after
link-loss the will do autonegociate to 10baseT-HD again. we cant ever
change this by hand on a few hundred computers. Is there any way to
configure this on our debian machines by an option
in /etc/network/interfaces (/etc/sysconfig/network/ifcfg-eth0 on suse)
or the sis900 module option? I tried the opt. "media 10baseT-FD" but
that wount work.
on our suse linux boxes it is more difficult. some of these haves a 2.6
kernel and there mii-tool or ethtool wount work too!
has anywone experience with running a 
        debian linux / 2.4.28 kernel
        suse linux 9.0 / 2.4.. kernel
        suse linux 9.1 / 2.6.. kernel
and a static configuration for sis900 on 10mbps and full-duplex
(10baseT-FD)?
if anyone could help,  it would be very nice if you could give me a hint
how to solve this problem - maybe it ist very easy to configure?

Kind regards,

Thorsten 
                                  ,,,,,
                                 ( o ~ )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~.oooO~~(_)~~Oooo.~~~

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

                 reply	other threads:[~2005-03-17 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1111078728.4377.15.camel@localhost.localdomain \
    --to=mail@thorsten-alge.de \
    --cc=alge@ip-exchange.de \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox