Heres are the nic combinations I've tried in one machine:
3com 905 (at 100mbit) 3com 905b (at 10mbit)
3com 905b (at 100mbit) 3com 905 (at 10mbit)
3com 905 (at 100mbit) realtek 8039 (at 10mbit)
3com 905b (at 100mbit) realtek (at 10mbit)
3com 905b (at 100mbit) ne2000 (at 10mbit)
In each case
. But with only the 100mbit
network attached, it's detected fine.
Thanks again for any suggestions.
-Original Message-
From: RT tr49...@rcc.on.ca
To: curr...@freebsd.org curr...@freebsd.org
Date: Sunday, March 28, 1999 1:56 PM
Subject: 3com Nic Problems
Heres are the nic combinations I've
I like it too... No code anywhere than needed. After all, if /etc/rc
doesn't exist, everything's messed up anyway, so you mideswell make it more
dependent upon that script.
-Original Message-
From: Chas cpinck...@dynasty.net
To: p...@originative.co.uk p...@originative.co.uk
Cc:
I have a couple of 905B 3com cards. I'm interested in running diskless
(especially since a harddisk in the one machine just died).
After reading the handbook, I found the diskless information to be extreamly
outdated. Does netboot now support the 905 line of 3com cards? (Any test
drivers out
I've run into a small snag with the acd drivers.
Normal (store bought) CDs appear to function fine.
Recordables have some troubles. First off, 50% of the disks mount properly.
50% complain with the error Invalid Argument when doing a: 'mount -t
cd9660 /dev/acd0a /mnt/cdrom'
I can cat
Yesterday being daring I installed SoftUpdates. Works great locally, but
now I find that my NFS problems occur more often. I've also removed the
ne2000 cards from my system (as someone told me they may be causing network
traffic problems). The 3coms remain in the server.
On the client machine.
In the past 3 weeks I've upgraded from 3.0-release, to 3-stable to 4-current
(as of 4 days ago). I've tried nfs v2 and nfs v3. In all of those
circumstances I end up with programs locking due to write problems.
I'm no good a debugging, so if someone could hold my hand through this
one...
Basic
I update 3-Stable nearly weekly, and have been experiencing the same problem
for quite a while now. NFS imports, on the client side appear to be losing
data. When this occurs, I see .nfs78969 files on the server side. The
program on the client side always freezes (top reports it's STAT as 'D').
I'd have to agree with another message. Merging the defaults into rc sounds
to me like the best solution, then have rc.conf handle the changes. I
personally prefer to hand edit this file. This is coming from a user on
3.0-stable however... .conf normally means that it should be edited, not
-Original Message-
From: Matthew Dillon dil...@apollo.backplane.com
To: Richard Wackerbarth r...@nomad.dataplex.net
Cc: Jordan K. Hubbard j...@zippy.cdrom.com; Matthew Dillon
dil...@apollo.backplane.com; David Wolfskill d...@whistle.com;
curr...@freebsd.org curr...@freebsd.org
Date:
I highly doubt that I'll ever use FORTRAN directly or indirectly. If it's
not used by a vast majority, it should be optional...
-Original Message-
From: Mike Smith m...@smith.net.au
To: Mark Murray m...@grondar.za
Cc: obr...@nuxi.com obr...@nuxi.com; Steve Kargl
11 matches
Mail list logo
