At 16:52 25/06/2004. Simon Barner had this to say:
>Richard P. Williamson wrote:
>
>[...]
>
>Here another thing you could try: I once had a problem with a 3Com NIC
>not being detected properly when the driver was compiled statically into
>the kernel.
>
>Removing it and using the module instead made
Richard P. Williamson wrote:
[...]
Here another thing you could try: I once had a problem with a 3Com NIC
not being detected properly when the driver was compiled statically into
the kernel.
Removing it and using the module instead made it work...
[...]
> 1) It says 'Ethernet manual'. Does th
Simon, All:
At 15:30 01/06/2004. Simon Barner had this to say:
>I just had a look at that older post of yours, and I saw that you are
>still running FreeBSD 4.8. Could you consider upgrading to 4.10-RELEASE or
>-STABLE?
>...
>IMO there's a really good chance that upgrading will make your onboard
>
On Tue, Jun 01, 2004 at 11:36:40PM -0600, flowers wrote:
> From: Wayne Pascoe
> > I've tried installing 5.2.1 on the machine and it still doesn't work.
> > Now though, it's even worse, as the em0 device doesn't work either.
> >
> > I get something along these lines:
> > em0: Link is up 10Mbps Half
From: Wayne Pascoe
> I've tried installing 5.2.1 on the machine and it still doesn't work.
> Now though, it's even worse, as the em0 device doesn't work either.
>
> I get something along these lines:
> em0: Link is up 10Mbps Half Duplex
> em0: watchdog timeout -- resetting
> em0: Link is up 10Mbps
> I've tried installing 5.2.1 on the machine and it still doesn't work.
> Now though, it's even worse, as the em0 device doesn't work either.
>
> I get something along these lines:
> em0: Link is up 10Mbps Half Duplex
> em0: watchdog timeout -- resetting
> em0: Link is up 10Mbps Half Duplex
> em
On Tue, Jun 01, 2004 at 01:52:21PM +0200, Olaf Hoyer wrote:
> Well, I could imagine some special version of a 100Pro/VM integrated
> one, or some special (latest version) 82550 or so.
>
> Could you post a "pciconf -lv" from a FreeBSD system?
> Would help to identify the parts...
I've tried instal
Hi,
I just had a look at that older post of yours, and I saw that you are
still running FreeBSD 4.8. Could you consider upgrading to 4.10-RELEASE or
-STABLE?
Have a look at the CVS logs for the fxp driver, and at the driver
source itself, and you will notice that quite a lot has changed:
http://
Addendum:
>I have a 3 onboard NIC motherboard; I've asked the supplier for
>the manufacturer's name of the motherboard. I've tried adding
>the 0x1051 line to my if_fxp.c file, but it did not have any effect.
motherboard is an adlink ebc-2000 ...
Hope someone can help,
Richard
Hi Simon,
At 12:54 01/06/2004. Simon Barner had this to say:
>Wayne Pascoe wrote:
>> Hi all,
>>
>> I just bought a server from DNUK . It claims to have the following
>> Ethernet card combination:
>>
>
>Probably only the device ID of the card is not listed in the fxp0 driver.
>
>Your case reminds
On Tue, Jun 01, 2004 at 01:52:21PM +0200, Olaf Hoyer wrote:
> Well, I could imagine some special version of a 100Pro/VM integrated
> one, or some special (latest version) 82550 or so.
>
> Could you post a "pciconf -lv" from a FreeBSD system?
> Would help to identify the parts...
I'm going to go f
Wayne Pascoe wrote:
> Hi all,
>
> I just bought a server from DNUK . It claims to have the following
> Ethernet card combination:
>
> Intel PRO/1000 / 1000 Mbit / integrated
> Intel PRO/100 / 100 Mbit / integrated
>
> I've installed FreeBSD 4.10-RELEASE onto the box, and all I see is em0,
> I do
On Tue, 1 Jun 2004, Wayne Pascoe wrote:
> Hi all,
>
> I just bought a server from DNUK . It claims to have the following
> Ethernet card combination:
>
> Intel PRO/1000 / 1000 Mbit / integrated
> Intel PRO/100 / 100 Mbit / integrated
>
> I've installed FreeBSD 4.10-RELEASE onto the box, and all I
13 matches
Mail list logo