https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
Piotr Kubaj changed:
What|Removed |Added
CC||pku...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
--- Comment #5 from Anthael ---
VMWare
ESXi : 7.0.3
Build: 20036589
Virtual Machine
Opnsense running FreeBsd 13
FreeBSD 13.1-RELEASE stable/22.7-n250212-a26d6065f1f SMP amd64
4 NIC 1G binded on driver VMXNEXT3
2 NIC 10G binded on driver V
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
--- Comment #4 from Anthael ---
(In reply to Anthael from comment #3)
the pci passthrought seems refusing to be activated.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
--- Comment #3 from Anthael ---
Created attachment 235760
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235760&action=edit
vmware hardware pci passthrought
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
Anthael changed:
What|Removed |Added
Hardware|Any |mips
Version|Unspecified
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
Krzysztof Galazka changed:
What|Removed |Added
CC||krzysztof.gala...@intel.com
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265431
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kubilay Kocak changed:
What|Removed |Added
Flags|maintainer-feedback?(emaste |maintainer-feedback+
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #43 from Thomas Hurst ---
The errata was published nearly a year ago:
https://www.freebsd.org/security/advisories/FreeBSD-EN-20:12.iflib.asc
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kubilay Kocak changed:
What|Removed |Added
Keywords|needs-patch, needs-qa |
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #41 from Aaron C. de Bruyn ---
This appears to be fixed on all my 12.2 boxes. I haven't had a lockup in
something like 8 months.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
Mark Johnston changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
Mark Johnston changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:
Author: markj
Date: Mon Oct 12 16:44:06 UTC 2020
New revision: 366649
URL: https://svnweb.freebsd.org/changeset/base/366649
Log:
MFC r366464:
re(4): Add a 81
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: markj
Date: Mon Oct 5 19:58:56 UTC 2020
New revision: 366464
URL: https://svnweb.freebsd.org/changeset/base/366464
Log:
re(4): Add a 8168-compatible d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
Mark Johnston changed:
What|Removed |Added
Assignee|n...@freebsd.org |ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250037
--- Comment #2 from Kevin Lo ---
(In reply to Kubilay Kocak from comment #1)
I added v2, but Hiroshi's card is v4.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
-stable11?
Summary|TP-Link TG-3468 V4 network |re(4): TP-Link TG-3468 V4
|card not work |network card not detected
CC||ke...@freebsd.org,
||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #39 from Ed Maste ---
Will include this with the next group of SA/ENs that affect 12.1
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #38 from Eric Joyner ---
Created attachment 214169
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214169&action=edit
Inprogress Errata Notice
I started working on an Errata Notice.
--
You are receiving this mail be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Eric Joyner changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #37 from Eri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Eric Joyner changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kyle Evans changed:
What|Removed |Added
CC||kev...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #35 from IPTRACE ---
Confirmed, bug backed from my side as well.
FreeBSD 12.1-RELEASE-p1
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
rob2g2 changed:
What|Removed |Added
CC||spam...@bitbert.com
--- Comment #34 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #33 from commit-h...@freebsd.org ---
A commit references this bug:
Author: erj
Date: Thu Jan 2 23:35:06 UTC 2020
New revision: 356310
URL: https://svnweb.freebsd.org/changeset/base/356310
Log:
iflib: Prevent watchdog from re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #32 from Vinícius Zavam ---
(In reply to Vinícius Zavam from comment #30)
% grep -v -E '^$|^#' /etc/rc.conf | sort | grep igb
ifconfig_igb0="up -tso -lro -rxcsum -txcsum"
ifconfig_igb1="up -tso -lro -rxcsum -txcsum"
vlans_igb0=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #31 from Edinilson ---
igb1@pci0:1:0:1:class=0x02 card=0xa04c8086 chip=0x10c98086 rev=0x01
hdr=0x00
vendor = 'Intel Corporation'
device = '82576 Gigabit Network Connection'
class = network
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Vinícius Zavam changed:
What|Removed |Added
CC||egyp...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Edinilson changed:
What|Removed |Added
CC||edinil...@atinet.com.br
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #27 from dar...@dons.net.au ---
+1 for D21712 - I ran into this on a new system and it's very unpleasant for
our almost totally unattended highly remote systems :(
--
You are receiving this mail because:
You are the assignee fo
make the network card working correctly.
It would be nice if these patches were included in the main release.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #25 from 76nem...@gmx.ch ---
Created attachment 209143
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209143&action=edit
Patch D21712 redone for the sources of the 12.1 release
Lines number have changed in the new sou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
robert.ayrapet...@gmail.com changed:
What|Removed |Added
CC||robert.ayrapet...@gmai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #23 from 76nem...@gmx.ch ---
This morning I have been able to connect to the machine after the network
switch
was switched off for the night. This has never worked until now. It seems then
that this problem is now solved.
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #22 from 76nem...@gmx.ch ---
After further tests, I think the problems I still had are no more
related to the fact that the network card is unplugged.
If I plug it again in the same port, the network is working
correctly. It
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #21 from 76nem...@gmx.ch ---
(In reply to 76nemo76 from comment #20)
Finally I have applied the patches D21712 and D21769 on FreeBSD
12.1-PRERELEASE.
This was probably not exactly the sources where the patches have been created
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #20 from 76nem...@gmx.ch ---
I am a little busy this week. I will apply the patches and test the system
probably next week.
Against what sources (FreeBSD 12_1?) should the patches be applied?
Thanks
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #19 from John Delano ---
(In reply to Harald Schmalzbauer from comment #18)
I did apply https://reviews.freebsd.org/D21712 to have a complete fix, but the
problem seemed solved before applying that fix.
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #18 from Harald Schmalzbauer ---
(In reply to John Delano from comment #16)
Since the issue/fix (https://reviews.freebsd.org/D21712 , queue-detection) of
this topic wasn't involved in your latest test, please see
https://bugs.f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Rodney W. Grimes changed:
What|Removed |Added
CC||rgri...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #16 from John Delano ---
Odd, I applied this (https://reviews.freebsd.org/D21769) manually, recompiled
the kernel and it seems to have fixed the state change and the buffer warnings.
I also have https://reviews.freebsd.org/D185
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #15 from Harald Schmalzbauer ---
(In reply to Krzysztof Galazka from comment #13)
Thanks four your D21769 fix. Unfortunately it doesn't solve the
link-state-change-issue. Please see
https://bugs.freebsd.org/bugzilla/show_bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kubilay Kocak changed:
What|Removed |Added
Severity|Affects Some People |Affects Many People
See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #13 from Krzysztof Galazka ---
The watchdog message is cased by an issue in the iflib framework. The queue
hang detection code does not check the state of the interface. We are working
on a fix in this review: https://reviews.fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Kubilay Kocak changed:
What|Removed |Added
CC||bugzilla.free...@omnilan.de
--- Co
||needs-patch, needs-qa
Summary|igb: TX(2) desc avail = |igb: TX(2) desc avail =
|1024, pidx = 0 messages |1024, pidx = 0 messages
|appear when the network |appear when the network
|card loses
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Piotr Pietruszewski changed:
What|Removed |Added
CC||piotr.pietruszewski@intel.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #10 from 76nem...@gmx.ch ---
(In reply to 76nemo76 from comment #9)
After further tests, I noticed that if many cards are available in the machine,
even if the card where the cable is disconnected is unavaible with the message
ab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #9 from 76nem...@gmx.ch ---
After compiling the Prerelease 12.1, the problem is a little bit different. As
somebody else has noticed, when the network card is disconnected the connection
seems to work for quite a long time
from the
machine or the network switch is unplugged the connection is no more lost.
However, when passing the command "ifconfig -a" the network card (where the
cable is disconnected) is still marked as active. To see the igb0 card no more
marked as "active", I have to pass the co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #7 from John Delano ---
I just applied the mentioned patch and the interface (IGB) does not immediately
fail, but if unplugged for a few minutes, the error messages begin and the
interface goes hard down with no method of recove
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Krzysztof Galazka changed:
What|Removed |Added
CC||krzysztof.gala...@intel.com
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Ozkan KIRIK changed:
What|Removed |Added
CC||ozkan.ki...@gmail.com
--- Comment #5
avail = 1024, pidx = 0
Jul 29 14:04:51 oche syslogd: last message repeated 18 times
and nothing, except a reboot, makes the bridge (and network card) functionnal
again.
This parameter is set in the "/boot/loader.conf"
--/boot/loader.con
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
Peter Jeremy changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
--- Comment #3 from John Delano ---
I have discovered that if I unplug the ethernet cable, ifconfig still shows the
cable is "status: active"!
FreeBSD 11 immediately goes to "status: no carrier" when I do the same.
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240
John Delano changed:
What|Removed |Added
CC||webmas...@rgcwireless.com
--- Commen
|igb: TX(2) desc avail = |igb: TX(2) desc avail =
|1024, pidx = 0 |1024, pidx = 0 messages
||appear when the network
||card loses ethernet link
--
You are receiving
Hi,
We've installed FreeBSD 12.0-Release on an HP DL380 Gen10.
Seems like the network card freezes from time to time.
Constant ping on machine stops working, ssh session is dropped and server is
inaccessible.
# pciconf -lv | grep -A4 bge
bge0@pci0:2:0:0:class=0x02
Dear Sir/Madam,
How are you doing?
Femrice is China's most professional, the most complete specifications of the
network card Manufacturer.
Femrice focus on PCIe Fiber Optical 1G/10G/40G Ethernet network card for 10
years.
We have own factory production.
Through theREACH,CE,FCC
On Fri, May 13, 2016 at 02:17:09AM -0700, Yuri wrote:
> On 05/11/2016 22:58, YongHyeon PYUN wrote:
> >hw.msk.msi_disable is a loader tunable so you can't check it with
> >sysctl(8). Add the tunable to boot/loader.conf to take it effect.
> >See loader.conf(5) for more information.
>
>
> Adding hw
On 05/11/2016 22:58, YongHyeon PYUN wrote:
hw.msk.msi_disable is a loader tunable so you can't check it with
sysctl(8). Add the tunable to boot/loader.conf to take it effect.
See loader.conf(5) for more information.
Adding hw.msk.msi_disable="1" reduced the mouse problem, but Marvell
Yukon c
On Wed, May 11, 2016 at 10:46:01PM -0700, Yuri wrote:
> On 05/08/2016 02:33, YongHyeon PYUN wrote:
> >msk(4) will try to use MSI unless not configured to do so the IRQ
> >wouldn't be shared with other devices. If msk(4) is using MSI you
> >should see a high irq number greater than or equal to 256
On 05/08/2016 02:33, YongHyeon PYUN wrote:
msk(4) will try to use MSI unless not configured to do so the IRQ
wouldn't be shared with other devices. If msk(4) is using MSI you
should see a high irq number greater than or equal to 256 in vmstat
output. Given that you're seeing issues with MSI, tr
On Sat, May 07, 2016 at 09:33:39AM -0700, Yuri wrote:
> On 05/07/2016 08:34, Eugene Grosbein wrote:
> >
> >Verify if your mouse (USB one?) is using IRQ 18 too.
> >"vmstat -ai" command would be helpful.
> Yes, I have a USB mouse, and my USB uses IRQ 18:
>
> irq18: ehci0 uhci5503154
07.05.2016 23:33, Yuri wrote:
Verify if your mouse (USB one?) is using IRQ 18 too.
"vmstat -ai" command would be helpful.
Yes, I have a USB mouse, and my USB uses IRQ 18:
irq18: ehci0 uhci5503154 9
stray irq180 0
That must be the
On 05/07/2016 08:34, Eugene Grosbein wrote:
Verify if your mouse (USB one?) is using IRQ 18 too.
"vmstat -ai" command would be helpful.
Yes, I have a USB mouse, and my USB uses IRQ 18:
irq18: ehci0 uhci5503154 9
stray irq180 0
Yuri
06.05.2016 23:29, Yuri пишет:
When Marvell Yukon card is active on the desktop system, mouse periodically
stops, sometimes for seconds. I think this also makes the system impaired in
some other ways.
The offending device:
mskc0: port 0xd800-0xd8ff mem
0xfbdfc000-0xfbdf irq 18 at device 0
When Marvell Yukon card is active on the desktop system, mouse
periodically stops, sometimes for seconds. I think this also makes the
system impaired in some other ways.
The offending device:
mskc0: port 0xd800-0xd8ff mem
0xfbdfc000-0xfbdf irq 18 at device 0.0 on pci6
msk0: on
mskc0
W
# ConnectX Infiniband support
device mlxen # ConnectX Ethernet support
device mthca # Infinihost cards
After these manipulations network card recognized by the system, it is now
possible to change the IP and MTU.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206016
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153816
Sean Bruno changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153816
--- Comment #2 from Sean Bruno ---
This should no longer be happening with FreeBSD 10.1 and 10.2r. If you can
retest, we'd appreciate it.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=153816
Sean Bruno changed:
What|Removed |Added
Keywords||IntelNetworking
CC|
Synopsis: [xl] Periodically, the network card xl0 stops working -- xl0:
watchdog timeout
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Thu Oct 18 05:08:25 UTC 2012
State-Changed-Why:
http://people.freebsd.org/~yongari/xl/xl.watchdog.diff
Would you g
Howdy,
Modern 10G NICs have the ability to have different types of cables plugged into
them.
There is a standard for the values contained in the cables which can be read
here:
http://www.10gtek.com/templates/wzten/pdf/SFF-8472-(Diagnostic%20Monitoring%20Interface).pdf
It's probably the case th
Old Synopsis: Periodically, the network card xl0 stops working -- xl0: watchdog
timeout
New Synopsis: [xl] Periodically, the network card xl0 stops working -- xl0:
watchdog timeout
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-W
Hi,
I recently bought a Zyxel NWD210N.
It works perfect since the developer fixed what I reported to be faulty.
It is a wireless USB device.
Erich
On Tuesday 28 February 2012 11:39:33 Mikhail T. wrote:
> Hello!
>
> The on-motherboard Ethernet "card" in one of my computers stopped
> working s
Hello!
The on-motherboard Ethernet "card" in one of my computers stopped
working suddenly... I'm too far away and don't want the local users to
open up the machine to insert anything. Thus, I'd like to use an
external USB nic.
The OS is FreeBSD-8.2-stable/i386. Any recommendations? It can be
Synopsis: [realtek/atheros]: None of my network card working
Responsible-Changed-From-To: freebsd-net->freebsd-wireless
Responsible-Changed-By: adrian
Responsible-Changed-When: Mon Apr 11 11:39:58 UTC 2011
Responsible-Changed-Why:
punt to wireless list
http://www.freebsd.org/cgi/query-pr.
On Sun, 6 Mar 2011, Dave Johnson wrote:
> Hi all
>
>
> An IPFW problem when going from release to stable on 8.2
>
> An help gladly accepted
>
> LOG ON
>
> Flushed all rules.
> 00010 allow ip from 127.0.0.1 to 127.0.0.1 via lo0
> 00030 divert 8668 ip from any to any via bge0
> ipfw
Hi all
An IPFW problem when going from release to stable on 8.2
An help gladly accepted
LOG ON
Flushed all rules.
00010 allow ip from 127.0.0.1 to 127.0.0.1 via lo0
00030 divert 8668 ip from any to any via bge0
ipfw: getsockopt(IP_FW_ADD): Invalid argument
5 allow ip from any to any
Firewa
Synopsis: [re] network card works only on 1000M
Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Thu Jan 20 21:43:48 UTC 2011
Responsible-Changed-Why:
Grab.
http://www.freebsd.org/cgi/query-pr.cgi?pr=152
Old Synopsis: ixgbe doesn't work properly with the Intel 10gigabit CX4 Dual
Port network card
New Synopsis: [ixgbe] ixgbe doesn't work properly with the Intel 10gigabit CX4
Dual Port network card
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimo
Old Synopsis: re network card works only on 1000M
New Synopsis: [re] network card works only on 1000M
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Sat Nov 20 21:40:21 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s)
h
Old Synopsis: None of my network card working
New Synopsis: [realtek/atheros]: None of my network card working
Responsible-Changed-From-To: freebsd-i386->freebsd-net
Responsible-Changed-By: remko
Responsible-Changed-When: Sun Sep 5 10:50:10 UTC 2010
Responsible-Changed-Why:
This is m
Hi al
Installed 7.1 earlier and did a kernel update(after a src update) to 7.2.
The network cards appear to have stopped working.
They are using the "bce" driver
Do they to have to patched?
Regards
--
___
freebsd-net@freebsd.org mailing list
http:
--- On Thu, 4/23/09, Peter Jeremy wrote:
> From: Peter Jeremy
> Subject: Re: Network Card
> To: "Barney Cordoba"
> Cc: "ovi freebsd" , freebsd-net@freebsd.org
> Date: Thursday, April 23, 2009, 2:28 AM
> On 2009-Apr-21 14:02:38 -0700, Barney Cordoba
On 2009-Apr-21 14:02:38 -0700, Barney Cordoba wrote:
>On all of the MBs that I have, the slot NIC appears before the onboard
>ports in the pciconf -l listing. Its certainly not for sure.
As a datapoint to add to the uncertainty, the SunFire V440 has 4
motherboard NICs - two come before the PCI sl
Kaushal Shriyan wrote:
...
so there is no such command line utility to get to know about that
information on Free BSD ?
There is no sure fire way to get that information anywhere, unless
you're working with a system which has implemented PCI geographical
addressing. Some of this is present
On Tue, 21 Apr 2009 16:37:29 +0530, Kaushal Shriyan wrote:
KS> I have two lan cards em0 and rl0 on my system. is there a way to know on
KS> freebsd which is onboard or pci card ?. The issue is my system is located at
KS> remote location.
KS>
install from ports dmidecode, it can show mainboard nam
--- On Tue, 4/21/09, Boris Kochergin wrote:
> From: Boris Kochergin
> Subject: Re: Network Card
> To: "ovi freebsd"
> Cc: freebsd-net@freebsd.org, "Kaushal Shriyan" ,
> "Ingo Flaschberger"
> Date: Tuesday, April 21, 2009, 9:36 AM
> ov
ovi freebsd wrote:
Kaushal Shriyan wrote:
On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote:
Dear Kaushal,
I have two lan cards em0 and rl0 on my system. is there a way to
know on
freebsd which is onboard or pci card ?. The issue is my system is
located
at
remote location.
Dear Kaushal,
I did pciconf -lv and ran dmidecode. I could not figure it out which one
was
onboard or pci ?
Do you want me to paste the output of that commands
yes, please send me the output.
Kind regards,
Ingo Flaschberger
___
freebsd-net@
Kaushal Shriyan wrote:
On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote:
Dear Kaushal,
I have two lan cards em0 and rl0 on my system. is there a way to know on
freebsd which is onboard or pci card ?. The issue is my system is located
at
remote location.
perhaps lspc
On Tue, Apr 21, 2009 at 5:30 PM, ovi freebsd wrote:
> Kaushal Shriyan wrote:
>
>> On Tue, Apr 21, 2009 at 5:07 PM, Ingo Flaschberger wrote:
>>
>>
>>
>>> Dear Kaushal,
>>>
>>> I have two lan cards em0 and rl0 on my system. is there a way to know on
>>>
>>>
freebsd which is onboard or pci car
1 - 100 of 127 matches
Mail list logo
