I got it working with the netgear buy just turinging off
the plug n' play. I will try your other suggestions to
try to get the AMD nic working.
thx,
Dave
The problem you describe is becoming common in the 4.x versions of FBSD.
I have seen these solutions voiced previously in this list.
1. Check the PC's bios, look for a toggle to disable plug-n-play function.
2. Check that your PCI Nic card is not in the first or last PCI expansion
slot on the motherboard.
3. There is a problem with autonegotiation of the media settings between
your NIC and your switch. The default setting of auto means the Nic card
should sense the Lan for the switch or hub and set it's media type to match.
There have been reports of the Nic Card media type changing on the fly
between
10/100 and halfduplex and fullduplex causing the network to freeze up.
To stop this use the ifconfig command in the rc.conf file to force the
media type. Like this
ifconfig_xl0=inet 10.0.10.2 media 100baseTX mediaopt full-duplex
4 add option PCI_ENABLE_IO_MODES
to your kernel source and recompile. See LINT
5. add device puc
option PUC_FASTINTR
to your kernel source and recompile. See LINT
6. Follow bug fix using this url
http://www.freebsd.org/cgi/query-pr.cgi?pr=40636
Try one of the above one at a time until your problem goes away.
I have two different cards on my Netfinity 5000 server, a pci Netgear
FA311 (showing up as a NatSemi (sis0), and the onboard network card
which seems to have an AMD chipset (pcn0). If I have the onboard
ethernet card enabled at all and have an active cable connected to it
and restart the computer it comes up on ukphy0, turns the pci error
light on and I get no internet access which it later makes the computer
reboot automatically without any warning. If I disable that card and
put in a PCI Netgear card, have also tried other cards such as Intel or
IBM cards, once in a while it will boot normally but every once in a
while it will get hung up on the ukphy0 as well, giving me the same
problem as the onboard network and reboot itself. At first I thought it
was an IRQ problem but all of my devices now have individual IRQ's set
in the bios and I'm still having this problem. I'm afraid to reboot
this thing because I'm afraid it won't be coming back up. Below are
from my dmesg, the first is when I have my onboard ethernet enabled and
the second is when I have the netgear installed. Any help would be much
appreciated on what to do with this problem. By the wayI'm running
on FreeBSD 4.6.2 but also have this problem running 4.7, I it also
usually hangs on the driver initialization during installation of the os.
Dave
Oct 4 21:11:36 hermes /kernel: pcn0: AMD PCnet/PCI 10/100BaseTX port
0x2180-0
x219f mem 0xfebfdc00-0xfebfdc1f irq 10 at device 9.0 on pci0
Oct 4 21:11:36 hermes /kernel: pcn0: Ethernet address: 00:06:29:39:bf:a9
Oct 4 21:11:36 hermes /kernel: miibus0: MII bus on pcn0
Oct 4 21:11:36 hermes /kernel: ukphy0: Generic IEEE 802.3u media
interface on
miibus0
Oct 4 21:11:36 hermes /kernel: ukphy0: 10baseT, 10baseT-FDX,
100baseTX, 100bas
eTX-FDX, auto
pcib1: ServerWorks NB6536 2.0HE host to PCI bridge on motherboard
pci1: PCI bus on pcib1
sis0: NatSemi DP83815 10/100BaseTX port 0x4b00-0x4bff mem
0xc0fdf000-0xc0fd irq 5 at device 4.0 on pci1
sis0: Ethernet address: 00:a0:cc:76:d9:f1
miibus0: MII bus on sis0
ukphy0: Generic IEEE 802.3u media interface on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
