On 04/02/2012 03:52 PM, Mike Tancsa wrote:
On 4/1/2012 4:21 PM, Tim Daneliuk wrote:
I am seeing this intermittently:
Apr 1 14:48:36 host kernel: fxp0: link state changed to DOWN
Apr 1 14:52:27 host kernel: fxp0: link state changed to UP
There were some fixes to the fxp driver on ~ March
On 4/1/2012 4:21 PM, Tim Daneliuk wrote:
> I am seeing this intermittently:
>
> Apr 1 14:48:36 host kernel: fxp0: link state changed to DOWN
> Apr 1 14:52:27 host kernel: fxp0: link state changed to UP
There were some fixes to the fxp driver on ~ March 26th that fixed the
NIC bou
I am seeing this intermittently:
Apr 1 14:48:36 host kernel: fxp0: link state changed to DOWN
Apr 1 14:52:27 host kernel: fxp0: link state changed to UP
This is observed both on some 8.2-STABLE and 8.3-PRERELEASE versions
on the same server. I have replaced the ethernet cable as well as the
Hello
I use FreeBSD 6.2-RELEASE #1 as a gateway server.
I have been receving a error message in /var/log/messages twice a month
recently;
kernel: fxp0: discard oversize frame (ether type 800 flags 3 len 1515 > max
1514)
As that problem has become, the concerning ethernet card has slow down v
th fxp[n] NICs on it.
jerry
`
>
> after the update finished compiling kernel and mergemaster.
>
> I have my nic fxp0 always show the link status to 'no carrier'
>
> I trie to force media and media opt on ifconfig to value has mentioned
> on man fxp.
>
Hello,
I have done an update of my freebsd 4.10 to 4.11.
after the update finished compiling kernel and mergemaster.
I have my nic fxp0 always show the link status to 'no carrier'
I trie to force media and media opt on ifconfig to value has mentioned
on man fxp.
I have trie to rec
Hi,
I have a Dell Inspiron 2500 with a intel network adapter on.
It hangs in the boot up process, but if I disable acpi i can boot up
into the install menu
>set hint.acpi.0.disabled=1
But heres the problem. When i tries to asign a ip either via dhcp or
manualy, it hangs if the cable are
On Sun Oct 9 16:58 , 'Brian A. Seklecki' <[EMAIL PROTECTED]> sent:
>Process of elimination:
>
>Q: On the same hardware this problem doesn't occur with an older
>version, correct?
Installed 5.3 on 0.7, problem remains. 0.5 runs 5.4 incidentally.
Changed the router identification protocol direction
Be sure to CC: the list on these responses. Someone else may have
ideas.
Your results below are indeed of concern.
What you need to do is have two terminals open on either machine. One
for ping'ing, one for watching tcpdump(8) on. You want to look for ARP
"who-as" and "is at" packets on either
--
Should have read man tcpdump prior to running it!
As root:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
23:10:40.704329 802.1d config 8000.00:0f:b5:16:dd:b6.8001 root 8000.00:0f:b5:16:
What
>>
>>>
>>> What do the outputs of "ifconfig fpx0", "arp -an", "tcpdump -i fxp0 -n"
>>> and "netstat -s" look like?
>>>
>>> ~BAS
>>
>>
>> arp -an
>> ? (192.168.0.1) at 00:0f:b5:16
On Wed, 5 Oct 2005, Bdrawyah wrote:
What do the outputs of "ifconfig fpx0", "arp -an", "tcpdump -i fxp0 -n"
and "netstat -s" look like?
~BAS
arp -an
? (192.168.0.1) at 00:0f:b5:16:dd:b6 on fxp0 [ethernet]
You should see an ARP entry for .07 fro
What do the outputs of "ifconfig fpx0", "arp -an", "tcpdump -i fxp0 -n"
and "netstat -s" look like?
~BAS
On Wed, 5 Oct 2005, Bdrawyah wrote:
I have a small LAN at home consisting of 192.168.0.5 (a single PIII) which runs
5.4 stable and 192.
ibus 0 on motherboard
pci0: on pcib0
agp0: mem 0xf800-0xfbff at device 0.0
on pci0
pcib1: at device 1.0 on pci0
pci1: on pcib1
pcib2: at device 30.0 on pci0
pci2: on pcib2
fxp0: port 0x5400-0x543f mem
0xfdc0-0xfdc00fff,0xfdd0-0xfd
df irq 18 at device 2.0 on pci2
miibus0
this.
Looking over the man pages for ifconfig and rc.conf, here is what I did.
1. Figure out what media options are available for the card
$ ifconfig -m fxp0
fxp0: flags=8843 mtu 1500
options=8
capability list:
=8
inet 192.168.0.16 netmask 0xff00 broadcast
Gerard Samuel wrote:
[ ... ]
This box currently uses DHCP to get its IP address.
When it boots up, and I log in, and immediately try to
initiate any network activity from this box, it takes about
2-3 seconds for said network activity to start.
For example, if I were to ping, or startx, it takes
abo
Im currently using FreeBSD 5.3, using the fxp driver for
my network card.
$ dmesg | grep fxp0
fxp0: port 0xec00-0xec1f mem
0xdff0-0xdfff,0xdd9ff000-0xdd9f irq 10 at device 8.0 on pci0
This box currently uses DHCP to get its IP address.
When it boots up, and I log in, and immediately
On Tue, 8 Jun 2004 17:45:09 +0200
<[EMAIL PROTECTED]> spake thus:
> Hey
>
> I've found some documented problems with this on google but nothing that really
> helped me. I have an IBM Thinkpad R40 and finding chipset information for it all the
> docs say that it's an Ethernet Driver(ya i know)
Hey
I've found some documented problems with this on google but nothing that really helped
me. I have an IBM Thinkpad R40 and finding chipset information for it all the docs say
that it's an Ethernet Driver(ya i know) so the best i've got is that it's intergrated
into the motherboard. I even ha
O fount of knowledge,
I'm stuck.
I've got
gndv# ifconfig fxp0
fxp0: flags=8843 mtu 1500
inet 172.x.x.188 netmask 0x broadcast 172.255.255.255
inet6 fe80::230:64ff:fe01:86ff%fxp0 prefixlen 64 scopeid 0x1
ether 00:30:64:01:86:ff
media: Ether
Hi,
I was trying to install a ProLiant BL10e G2 (blade server) over the
network. With all machines it's working fine.
But the blade isnt going fine.
I choose to use NFS to fetch the files.
But in ctrl-alt-F2 i see: fxp0: device timeout
This message is repeated and so the nfs mounting doesnt
You're probably doing something to put the adapters into promiscuous
mode -- like running a packet sniffer. If not, it's pretty weird...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send a
sometimes shows up
fxp0 promiscuous mode enabled
fxp0 promiscuous mode disabled
fxp1 promiscuous mode enabled
fxp1 promiscuous mode disabled
in this way in between.
I have a win2000 box in the internal network running edonkey with a lot of
connection. The compaq server Nic is supposed to be very
Hi,
I'm having problems with my Intel Pro/100 onboard LAN (fxp(4) driver). It
used to work just fine, but after I installed two rl(4) based NICs it
stopped working, even after I removed the other NICs. I get this in dmesg:
# dmesg | grep fxp
fxp0: port 0x78c0-0x78ff mem
0xfebff000-0xfeb
> Nothing is mentioned in /var/log/messages. The switch claims the port is
> running at 100Mbits, full-duplex, as does the output of
> ifconfig. Suggestions?
>
> - Mike Hogsett
Does ifconfig show any errors? Does the switch show any errors?
That's where I'd start..
--Charlie
__
ing
> 300Kbit/sec out of its interface. I confirmed this with an FTP
> directly to the host a few minutes ago (after killing off the
> backups).
>
> Nothing is mentioned in /var/log/messages. The switch claims the port
> is running at 100Mbits, full-duplex, as does the output of
I am having a strange problem.
I have this new Cisco Catalyst 2940T-24. On it I have 6 FreBSD/x86 boxes.
The first 5 are running great. The 6th is only getting 300Kbits/sec out
of its interface, but ... not right away after a reboot. I rebooted the
host Saturday afternoon and I was again getti
did a dump and a restore. For example,
> the /usr partition got this:
>
> #mount /dev/ad2s2g /mnt/s2/usr
> #dump -0uaf - /dev/ad0s2g | (cd /mnt/s2/usr; restore -rf - )
>
> Now the system I just created has a problem which I hope you can help me with.
> The kernel fills u
Now the system I just created has a problem which I hope you can help me with.
The kernel fills up ttyv0 with messages like
these:
fxp0: SCB timeout: 0xff 0xff 0xff 0xfff
fxp0: device timeout
fxp0: SCB timeout: 0xff 0xff 0xff 0xfff
fxp0: SCB timeout: 0xff 0xff 0xff 0xfff
fxp0: SCB timeout: 0xff
remove support for 486 and 586.
I have an Intel Pro100 Cardbus II PCMCIA card in an
IBM Thinkpad 600e.
I receive the following error when attempting to
obtain an IP address via DHCP. The following message
repeats until I take the interface down.
==
fxp0: device timeout
I moved all the cards around to different PCI slots and removed the TV
Card.
This weekend I will test if I can put the TV Card back in without causing
problems
: http://vzalive.bangrocks.com :
: VZ300/Laser 210/Salora/Texet :
. http://www.bangrocks.com .
---
I've just upgraded my FreeBSD server from a Pentium 133 with 32Mb EDO RAM
to a Celeron 433 with 256 Mb SDRAM.
I've rebuilt the kernel and world.
Now, I am constantly getting errors on my console screen and in dmesg
along the lines of:
> > fxp0: SCB timeout: 0x80 0x0 0x50 0
32 matches
Mail list logo
