On Sat, Nov 13, 2010 at 09:09:18AM +0200, Zeus V Panchenko wrote:
> Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote:
> >
> > Please be more specific for the issue. Your description is hard to
> > narrow down possible cause.
> >
> > > i was sure it is the problem of the onboard rt nics ..
On Mon, Nov 15, 2010 at 11:11:42PM +, Bruce Cran wrote:
> I've been trying to get suspend/resume working on my Dell laptop. I have two
> if_msk adapters: one's the built-in 100Mb port and the other's a Sonnet Gb
> ExpressCard NIC. I've noticed that if I boot with the Gb card installed both
The appliance is in a 1U form-factor with just a single riser-based slot
(PCIe 2.0).
Thanks for your help with this,
Charles
On 11/15/10 6:14 PM, Jack Vogel wrote:
The way you talked about this at first made me think this was
something new, but its actually
fairly old, its just a quad port 8
The way you talked about this at first made me think this was something new,
but its actually
fairly old, its just a quad port 82571, id is 0x10A5, support has been in
the drivers for ages :)
The issue is the hardware not the OS or driver, even if the motherboard is
PCIE 2.0, does it
not have slot
I've been trying to get suspend/resume working on my Dell laptop. I have two
if_msk adapters: one's the built-in 100Mb port and the other's a Sonnet Gb
ExpressCard NIC. I've noticed that if I boot with the Gb card installed both
ports work fine when the laptop has been resumed but if I don't ha
Well, I believe we have an answer:
http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm
The motherboard definitely is PCIe 2.0 . The page suggests these cards
for use with a PCIe2.0 system:
# Intel® PRO/1000 PT Quad Port LP Server Adapter (P/N EXPI9404PTL)
# Intel® Gigabit E
The eth0 line in log: we rename our NICs to be ethX (via "iconfig em0
name eth0"). That line is just one of the copper NICs coming up.
Info on the card -- model number (EXPi9404PFBLK), chipset (dual 82571 GB
chips). Here's the Intel page:
http://www.intel.com/Products/Server/Adapters/PRO10
Well, if the system doesnt show the hardware in a PCI scan there isn't much
my driver can do :)
The last line in your log says 'eth0', what's that about?
You could try booting 8.1 64 bit, you can also send me all the details about
the board, just to
make sure I can get the exact one and then I'll
Howdy,
Please review this patch which adds the -T flag to netstat so that you can get
TCP information, per socket,
including retransmits, out-of-order receives, and zero window advertisements.
Best,
George
head-tcpinfo.diff
Description: Binary data
Jack, I'm afraid that with the card _not_ installed we get identical
pciconf output. We're running 32 bit simply because that's where we got
rolling with our product, and have not yet made the call to invest in
the effort required to make the jump to 64. Do you think that our being
at 32 bit
Looks like the higher end HP Proliant servers are coming with 10GE
adapters.
When I was at MeetBSD I ran into an engineer that was working on this
driver and I failed to document his contact information.
If anyone has that contact, I'd really appreciate it.
Sean
__
UH, did you do that with the adapter in the system?? I do not see the ID I
expected
to see. Some reason you're running 32 bit??
Can you run the pciconf with the adapter in and out, compare and tell me
what its
ID is? All the unidentified devices I see are in the 0x3XXX range and those
are not
net
Great... thanks! Please see attached. BTW, the system is running
8.0-RELEASE-p2 i386 (PAE).
Charles
On 11/13/10 2:24 AM, Jack Vogel wrote:
pciconf -l please, I'll betcha these are the new quad ports that are
in my next igb driver
update, it would have gone in already but I've been fighti
This is a patched version of original function
code
/*
* If underlying interface can not do VLAN tag insertion itself
* then attach a packet tag that holds it.
*/
if ((m->m_flags & M_VLANTAG) &&
(ifp->if_capenable & IFCAP_VLAN_HWTAGGING) == 0)
Hi,
I am having trouble finding a full documentation on how to set an mesh
portal (MPP) bridged to wired lan.
I gathered things from here and there, and here what I have came up to.
SETUP: I have a PC, and two RSPRO boards with atheros wifi. PC and one
RSPRO connected to a router.
On the mesh no
Hi,
Following patch fix panic on i386 for drivers using such functions.
Those two functions take 64-bit variable(s) for their arguments.
On i386 that takes additional 32-bit variable per argument.
This is required so that windrv_wrap() can correctly wrap function that
miniport driver calls with s
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
17 matches
Mail list logo
