Hi,
Following the upgrade to 11.2-RELEASE, I've been seeing periodic network
adapter restarts for ena0 on an m5.large EC2 instance. I haven't seen
this prior with 11.1:
Jul 13 22:50:04 mail kernel: [1993] ena0: device is going DOWN
Jul 13 22:50:04 mail kernel: [1993] ena0: device is going UP
On Mon, Feb 4, 2013 at 10:05 PM, CeDeROM cede...@tlen.pl wrote:
I also want to use my KT-LINK multipurpose low-level embedded access
multitool based on FT2232H with RS232 port and I was worried there is
no driver - right now I will add the PID and recompile sources to see
if it works - happy
On 2/5/2013 11:25 AM, CeDeROM wrote:
On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger k...@denninger.net wrote:
The FTDI adapter has the provision for an external power supply (+5V)
but it does not require it unless you're running off an unpowered bus,
which is not normally the case. 500ma
Just an idea - do you use certified usb 2.0 cable ? I had some
problems many times using non-standard cables..
Try using certified cable. Try using different keyboard/mouse, maybe
they drain too much power from a single USB port that connects all
those equipment... try to see how much power do
a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3: vendor 0x0409 at usbus1
uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3
on usbus1
uhub4: 7 ports with 7 removable, self powered
.
The KVM (which talks to the box over USB for keyboard and mouse)
interferes with the FTDI adapter!
I have absolutely NO idea why, but if it's not plugged in the FTDI
adapter comes up instantly. Of course then I can't KVM into the box,
which creates its own set of problems.
ARGH.
Ok, now
.
The KVM (which talks to the box over USB for keyboard and mouse)
interferes with the FTDI adapter!
I have absolutely NO idea why, but if it's not plugged in the FTDI
adapter comes up instantly. Of course then I can't KVM into the box,
which creates its own set of problems.
ARGH.
Ok, now
.
The KVM (which talks to the box over USB for keyboard and mouse)
interferes with the FTDI adapter!
I have absolutely NO idea why, but if it's not plugged in the FTDI
adapter comes up instantly. Of course then I can't KVM into the box,
which creates its own set of problems.
ARGH.
Ok, now
if I remember correctly. If there is a
hub inside the serial port adapter it would be good to know it it is
powered directly from the USB port or does it have its own power
supply...
There could be too much power drain from the USB port by external
devices attached to the hub/adapter. But this would
that port
should be disabled by the host if I remember correctly. If there is a
hub inside the serial port adapter it would be good to know it it is
powered directly from the USB port or does it have its own power
supply...
There could be too much power drain from the USB port by external
On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger k...@denninger.net wrote:
The FTDI adapter has the provision for an external power supply (+5V)
but it does not require it unless you're running off an unpowered bus,
which is not normally the case. 500ma is quite a bit of available energy.
Karl
... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
9.1-STABLE #16 r244942
and it returns
ugen4.4: vendor 0x0409 at usbus4
uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4
on usbus4
uhub_attach: port 1 power on failed, USB_ERR_STALLED
uhub_attach: port 2
On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote:
... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
9.1-STABLE #16 r244942
and it returns
ugen4.4: vendor 0x0409 at usbus4
uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4
on usbus4
On 2/4/2013 2:06 PM, Ian Lepore wrote:
On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote:
... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
9.1-STABLE #16 r244942
and it returns
ugen4.4: vendor 0x0409 at usbus4
uhub6: vendor 0x0409 product 0x0050, class 9/0, rev
On 2/4/2013 2:06 PM, Ian Lepore wrote:
On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote:
... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
9.1-STABLE #16 r244942
and it returns
ugen4.4: vendor 0x0409 at usbus4
uhub6: vendor 0x0409 product 0x0050, class 9/0, rev
On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore i...@freebsd.org wrote:
FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and
10; I use it all the time. Sometimes aftermarket vendors who use FTDI's
parts program different vendor/product info and IDs have to be added to
code to
. Or the usb serial device is damaged
somehow so that the vendor and product ID are reading as garbage and
being mistaken for a hub.
Have you tried the ftdi adapter on another port/hub/computer? Have you
tried plugging something else into the port you're trying to use for the
ftdi adapter, like
On Mon, 2013-02-04 at 22:05 +0100, CeDeROM wrote:
On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore i...@freebsd.org wrote:
FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and
10; I use it all the time. Sometimes aftermarket vendors who use FTDI's
parts program different
at all. Or the usb serial device is damaged
somehow so that the vendor and product ID are reading as garbage and
being mistaken for a hub.
Have you tried the ftdi adapter on another port/hub/computer? Have you
tried plugging something else into the port you're trying to use for the
ftdi adapter
On Mon, Feb 4, 2013 at 10:20 PM, Karl Denninger k...@denninger.net wrote:
The machine is fine. The adapter is fine too -- I powered up the old
machine and it works too, and recognizes the adapter immediately (on
FreeBSD-Stable 7.) No problems with either.
Hello Karl :-) Is VID/PID the same
or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all. Or the usb serial device is damaged
somehow so that the vendor and product ID are reading as garbage and
being mistaken for a hub.
Have you tried the ftdi adapter on another port
with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3: vendor 0x0409 at usbus1
uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3 on
usbus1
uhub4: 7 ports
(perhaps the root hub or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3
or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3: vendor 0x0409 at usbus1
(perhaps the root hub or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3
you have a problem with a hub (perhaps the root hub or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so, they generally do have a hub included
it to the FTDI probe list.
It seems to me you have a problem with a hub (perhaps the root hub or a
motherboard hub if you don't have an external one) and this has nothing
to do with the ftdi device at all.
I assume we're talking about a multi-port usb to serial adapter, correct?
If so
-port usb to serial adapter, correct?
If so, they generally do have a hub included in the device.
Example:
ugen1.3: vendor 0x0409 at usbus1
uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3
on usbus1
uhub4: 7 ports with 7 removable, self powered
Then the individual
On Mon, 2012-06-18 at 23:07 +0200, Hans Petter Selasky wrote:
On Monday 18 June 2012 23:03:34 H wrote:
On Monday 18 June 2012 12:54 Hans Petter Selasky wrote:
On Monday 18 June 2012 00:00:51 H wrote:
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes
On Monday 18 June 2012 18:07 Hans Petter Selasky wrote:
On Monday 18 June 2012 23:03:34 H wrote:
On Monday 18 June 2012 12:54 Hans Petter Selasky wrote:
On Monday 18 June 2012 00:00:51 H wrote:
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes the link
On Monday 18 June 2012 00:00:51 H wrote:
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes the link is
down for various reasons, and then the routes start changing for
manually created routes, and I want to prevent that.
well that is certainly
On Monday 18 June 2012 12:54 Hans Petter Selasky wrote:
On Monday 18 June 2012 00:00:51 H wrote:
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes the link is
down for various reasons, and then the routes start changing for
manually created routes, and I
On Monday 18 June 2012 23:03:34 H wrote:
On Monday 18 June 2012 12:54 Hans Petter Selasky wrote:
On Monday 18 June 2012 00:00:51 H wrote:
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes the link is
down for various reasons, and then the routes start
any news I might have missed... :)
Also do you have any idea why AMD based CPUs could be vulnerable to this
alternative networking scheme and cause a remote denial service in fbsd
stable but not in CURRENT?
Thanks,
Etienne
Hi,
I loose packets because I use a WLAN adapter. Sometimes
a WLAN adapter. Sometimes the link is down for
various reasons, and then the routes start changing for manually created
routes, and I want to prevent that.
well that is certainly not a reason for changing routes
I have the feeling you are not explaining good enough what really is
going
I loose packets because I use a WLAN adapter. Sometimes the link is down
for
various reasons, and then the routes start changing for manually created
routes, and I want to prevent that.
well that is certainly not a reason for changing routes
I have the feeling you
sth...@nethelp.no wrote:
I loose packets because I use a WLAN adapter. Sometimes the link is down
for
various reasons, and then the routes start changing for manually created
routes, and I want to prevent that.
well that is certainly not a reason for changing routes
I have the feeling
because I use a WLAN adapter. Sometimes the link is down for
various reasons, and then the routes start changing for manually created
routes, and I want to prevent that.
--HPS
Hi Hans,
As per the usual PR triage workflow, I recommend you fill a bug report
and add me to the CC list
Hi,
Maybe there is a simple answer, but how do I bind a route to a network
interface in 8-stable? Is that possible at all? I'm asking because the routes
I add in my network setup are lost because of ARP packet drops. I.E. they
exist for a while, but not forever like I want to.
--HPS
Perhaps you can ask the very same question in another way so its easier
to understand why you losing packets? All in all I always thought TCP/IP
was the basic unit in Internet based networking but feel free to correct
me if you have any news I might have missed... :)
Also do you have any idea
On 06/15/12 12:19, Hans Petter Selasky wrote:
Hi,
Maybe there is a simple answer, but how do I bind a route to a network
interface in 8-stable? Is that possible at all? I'm asking because the routes
I add in my network setup are lost because of ARP packet drops. I.E. they
exist for a while, but
Perhaps you can ask the very same question in another way so its easier
to understand why you losing packets? All in all I always thought TCP/IP
was the basic unit in Internet based networking but feel free to correct
me if you have any news I might have missed... :)
This is an old and well
On Fri, Jun 15, 2012 at 07:54:52PM +0200, sth...@nethelp.no typed:
Perhaps you can ask the very same question in another way so its easier
to understand why you losing packets? All in all I always thought TCP/IP
was the basic unit in Internet based networking but feel free to correct
me
Thanks Herbert. I bought another Intel CT to test and it work flawlessly,
so it was a bad PT adapter.
On Mon, Mar 5, 2012 at 8:04 AM, Herbert J. Skuhra hsku...@fastmail.fmwrote:
On Sun, 4 Mar 2012 14:39:01 +0800
Irjohn Junus i.ju...@gmail.com wrote:
Hello,
This was originally posted
with Intel PRO/1000 PT dual port server adapter.
The adapter is recognized as em0 and em1 but em0 just won't work (i.e no
light on the port when connected to the switch) and em1 works only in
100baseTX full-duplex mode (no carrier if I force it to 1000baseT). I tried
to change switch port, UTP cable
Hello,
This was originally posted here:
http://forums.freebsd.org/showthread.php?p=168854posted=1#post168854
I'm building a new PF firewall box based on FreeBSD 9 Release. Motherboard
is Foxconn H61S Mini-ITX with Intel PRO/1000 PT dual port server adapter.
The adapter is recognized as em0
hi lists
DWL-G132 failed to load on 9.0RC3
uath0: Atheros Communications Inc USB WLAN Device, rev 2.00/0.01, addr 2
on usbus3
uath0: timeout waiting for reply to cmd 0x4 (4)
uath0: could not read capability 3
uath0: could not get device capabilities
device_attach: uath0 attach returned 35
and
Hi everyone,
i have a 82599EB network card.
the ixgbe driver on 8* supports 82598 cards, although it identified my card
but i'm not sure it will work fine and won't make kernel panics, since its a
production server i want to put a good driver that will work without
problems.
I just found this
What OS release are you going to be using, 8.2 ? The driver in HEAD is the
latest code, the internal tarball goes thru release machinery so it is
lagging a
bit (2.3.8 vs 2.3.11), you should be OK in either case, but I'd recommend
the newer.
Jack
On Tue, Aug 23, 2011 at 12:39 AM, Sami Halabi
);
adapter-msix_mem = bus_alloc_resource_any(dev,
SYS_RES_MEMORY, rid, RF_ACTIVE);
...
bus_release_resource(dev, SYS_RES_MEMORY,
PCIR_BAR(EM_MSIX_BAR), adapter-msix_mem);
Though manpage for bus_release_resource specifies, that rid needs to
be exactly the same
:
hw.em.enable_msix=0
When set in loader.conf to 0, then the card magically starts to work
properly. The only thing in our code in em_setup_msix(), that raises
my doubts, is the following code path:
int rid = PCIR_BAR(EM_MSIX_BAR);
adapter-msix_mem
, then the card magically starts to work
properly. The only thing in our code in em_setup_msix(), that raises
my doubts, is the following code path:
int rid = PCIR_BAR(EM_MSIX_BAR);
adapter-msix_mem = bus_alloc_resource_any(dev,
SYS_RES_MEMORY, rid, RF_ACTIVE
Hi,
I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box
and I can't see any incoming traffic on this card. Even ARP resolution
doesn't work. Though I see the outgoing traffic on the other end.
Relevant info:
kadlubek# uname -a
FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2
installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box
and I can't see any incoming traffic on this card. Even ARP resolution
doesn't work. Though I see the outgoing traffic on the other end.
Relevant info:
kadlubek# uname -a
FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE
installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box
and I can't see any incoming traffic on this card. Even ARP resolution
doesn't work. Though I see the outgoing traffic on the other end.
Relevant info:
kadlubek# uname -a
FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20
Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box
and I can't see any incoming traffic on this card. Even ARP resolution
doesn't work. Though I see the outgoing traffic on the other end.
Relevant info:
kadlubek# uname -a
FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat
On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote:
Hi,
I really don't know (I haven't done that intentionally). There is
nothing special in /var/log/messages:
kadlubek# grep -i msix /var/log/messages
Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 vectors
On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin j...@freebsd.org wrote:
On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote:
Hi,
I really don't know (I haven't done that intentionally). There is
nothing special in /var/log/messages:
kadlubek# grep -i msix /var/log/messages
2011/4/28 Jack Vogel jfvo...@gmail.com:
On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin j...@freebsd.org wrote:
On Thursday, April 28, 2011 5:17:11 pm Wiktor Niesiobedzki wrote:
Though they mention that HT MSI windows is disabled. I'm not sure,
whether this matters.
Yes, that is probably
On 06/12/2009 02:26, Karl Denninger wrote:
BUT BUT BUT - there is no way to clear the devices nodes from FreeBSD!
If I attempt a camcontrol rescan all after pulling a set the machine
instantly panics with uncompleted I/Os to the disks I did not tamper
with - whether I tell the adapter I did
Hi Folks...
To those who might have more experience with these boards than I do - is
there a way to have them re-read the bus and export anything new (or
remove anything not new) from the driver configuration?
I can't figure out a way to do it as of yet - the 3Ware drivers
automatically export
On Sat, Dec 05, 2009 at 07:43:35PM -0600, Karl Denninger wrote:
To those who might have more experience with these boards than I do - is
there a way to have them re-read the bus and export anything new (or
remove anything not new) from the driver configuration?
If you're talking about getting
On Sat, Dec 05, 2009 at 07:43:35PM -0600, Karl Denninger wrote:
Hi Folks...
To those who might have more experience with these boards than I do - is
there a way to have them re-read the bus and export anything new (or
remove anything not new) from the driver configuration?
I can't figure
On Sat, Dec 05, 2009 at 07:43:35PM -0600, Karl Denninger wrote:
To those who might have more experience with these boards than I do - is
there a way to have them re-read the bus and export anything new (or
remove anything not new) from the driver configuration?
I can't figure out a way to
show up in FreeBSD and all
appears well.
Now let's say I need to DISMOUNT a set (or a passthrough JBOD disk)
while the machine is running. I dismount the disk in FreeBSD - now what?
If I pull the drive without telling the controller first, I get the
beep of death from the adapter bleating about
to i386 7.2-STABLE.
The mpt driver spends a minute or so eager to initialize the
controller, but fails with the following messages:
mpt0: LSILogic SAS/SATA Adapter port 0xec00-0xecff mem
0xdfbec000-0xdfbe,0xdfbf-0xdfbf irq 16 at device 0.0 on pci1
mpt0: [ITHREAD]
mpt0: MPI Version
I did some additional testing:
1) Installed 7.2-RC2 directly on the Perc 4e/Si H435 machine (RAID1)
from a cd, this went fine.
2) Turned off, and placed one drive in the machine with Perc 4e/Si H430,
boot went fine
Checked install of 7.1-RELEASE from cd on the 4e/Si H435 machine,
failed: no
Hello All,
I encountered the same problem as reported to this list earlier,
http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html,
but then with 7.1-RELEASE-p4.
Interestingly enough, FreeBSD booted fine on the machine installed
(updated from 7.0 to 7.1-RELEASE-p4).
This
The just-released 7.2-RC2 should fix this problem. Please let me
know ASAP if it works for you.
Scott
Jeroen Hofstee wrote:
Hello All,
I encountered the same problem as reported to this list earlier,
http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html,
but then with
I did the following to verify:
1) Installed 7.2-RC2 on the Perc 4e/Si H430 machine (RAID1), this went fine.
2) Turned off, and placed one drive in the machine with Perc 4e/Si H435,
boot went fine and no long delays after amr0
So the problem as I encountered with 7.1-RELEASE-p4 is not
On Wed, 2009-02-11 at 10:38 -0500, Brian A. Seklecki wrote:
There's already discussion about this in the archives. We're aware and
working on it.
Set:
/boo/loader.conf
kern.cam.scsi_delay=2
As a work-around for now.
Many thanks for your answer, it fixed the problem for now.
Now it
amr0: LSILogic PERC 4e/Si Firmware 521X, BIOS H430, 256MB RAM
amr0: delete logical drives supported by controller
Any time!
NOTE: You're using the 4e/Si, which we have as well. We're experiencing
random crashes on the 1850/8th gen, as a result of a (believed) DMA bug
introduced into 7.x
Brian A. Seklecki wrote:
NOTE: You're using the 4e/Si, which we have as well. We're experiencing
random crashes on the 1850/8th gen, as a result of a (believed) DMA bug
introduced into 7.x
Just to note, we are only seeing these issues in combination with megarc
(/usr/ports/sysutils/megarc)
on amr0
amrd0: 69880MB (143114240 sectors) RAID 1 (optimal)
Trying to mount root from ufs:/dev/amrd0s1a
- boot cd of 7.1 fails because the installed doesn't see any harddisk.
Message log abstract:
amr0: adapter is busy
amr0: adapter is busy
amr0: delete
:
amr0: adapter is busy
amr0: adapter is busy
amr0: delete logical drives supported by controller
I also tried to setup 7.0, and then upgrade to 7.1 with freebsd-update,
but then it fails exactly like with the 7.1 boot CD
(7.1-RELEASE-amd64-disc1.iso). Screenshot:
http
I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
recent 7.1-STABLE amd64 with GENERIC kernel. I expected the ixbg(4)
driver to attach, but it does not.
The labels on the card show:
INTEL(R) 10GbE XF SR 2 PORT SERVER ADAPTER
893135
EXPX9502FXSRGP5
Hi.
2009/2/12 Greg Rivers gcr+freebsd-sta...@tharned.org:
I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
recent 7.1-STABLE amd64 with GENERIC kernel. I expected the ixbg(4) driver
to attach, but it does not.
The labels on the card show:
INTEL(R) 10GbE XF SR
On Wed, Feb 11, 2009 at 3:21 PM, pluknet pluk...@gmail.com wrote:
Hi.
2009/2/12 Greg Rivers
gcr+freebsd-sta...@tharned.orggcr%2bfreebsd-sta...@tharned.org
:
I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
recent 7.1-STABLE amd64 with GENERIC kernel. I expected
see ixgbe(4)
On Wed, Feb 11, 2009 at 2:43 PM, Greg Rivers
gcr+freebsd-sta...@tharned.org wrote:
I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
recent 7.1-STABLE amd64 with GENERIC kernel. I expected the ixbg(4) driver
to attach, but it does not.
The labels
2009/2/12 Kip Macy km...@freebsd.org:
see ixgbe(4)
BTW I'm afraid ixgbe manpage still to be merged to 7.
On Wed, Feb 11, 2009 at 2:43 PM, Greg Rivers
gcr+freebsd-sta...@tharned.org wrote:
I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
recent 7.1-STABLE amd64
On Thu, 12 Feb 2009, pluknet wrote:
You probably want to load ixgbe(4), not ixgb(4) (latter is afaik an
older PCI-X version driver). The labels on the card are close to the
description of ixgbe. Note, it's not in GENERIC.
On Wed, 11 Feb 2009, Jack Vogel wrote:
Yes, its an Oplin, 82598,
Somehow that error was corrected but just AFTER the release. Its a simple
fix, look at
ixgbe.h in CVS to see it, you just get rid of the tcp_lro.h and change it
to netinet/tcp_lro.h
There will be a new code drop soon also.
Jack
On Wed, Feb 11, 2009 at 5:16 PM, Greg Rivers
On Wed, 11 Feb 2009, Jack Vogel wrote:
Somehow that error was corrected but just AFTER the release. Its a
simple fix, look at ixgbe.h in CVS to see it, you just get rid of the
tcp_lro.h and change it to netinet/tcp_lro.h
There will be a new code drop soon also.
That worked perfectly. Now
On Tue, Sep 16, 2008 at 09:24:26PM -0700, Jeremy Chadwick wrote:
Since you're still in the market: I've heard wonderful things about any
of the USB serial adapters that use the Prolific chip; see uplcom(4).
I can second that. I use a Sitecom CN-104 (also Prolific) with several
devices like Sun
the Prolific chip; see uplcom(4).
I can second that. I use a Sitecom CN-104 (also Prolific) with several
devices like Sun hardware and Soekris/Wrap systems boards and it al works
perfectly (FreeBSD/Linux and Windows).
Thanks. I decided to not take a chance and ordered a Prolific based Iogear
adapter
Hi,
I'm on the market for a USB serial adapter. The Keyspan USA-19HS gets a
lot of good reviews for its performance, but I've noticed previous Keyspan
models have a history of not supporting FreeBSD due to firmware issues.
The 19HS is listed in /usr/src/sys/dev/usb/usbdevs with nothing noted
On Tue, Sep 16, 2008 at 11:33:22PM +0200, Aragon Gouveia wrote:
I'm on the market for a USB serial adapter. The Keyspan USA-19HS gets a
lot of good reviews for its performance, but I've noticed previous Keyspan
models have a history of not supporting FreeBSD due to firmware issues.
The 19HS
this device to usbdevs
and umodem.c is sufficient?
Secondly, the bluetooth adapter shows up as a straightforward serial port ..
kernel: sio4: Bluetooth BT0100M at port 0x2f8-0x2ff irq 18 function 0
config 1 on pccard0
kernel: sio4: type 16550A
kernel: sio4: [FILTER]
How can I hook this up
Hello
Look. I have a problem with an Integris CathLab System.
It only uses 18GBytes HDD. And nowadays you can figure how difficult is to
get such as discs. Can you tell me a way to limit by Firmware the capacity
of a brand new Disc let says 73 GBytes to just 18GBytes.
By the way, and sure that’s
Hi,
I am seeing some problems with one of my Dell PowerEdge 2950's (running
RELENG_6_2) on board bce NICs. The interface seems to crash with the
following errors, to which the fix seems to be and ifconfig bce0 down;
ifconfig bce0 up:
Jun 7 12:20:29 gonzo kernel: bce0: discard frame w/o
Hi,
I have problems with both FreeBSD 6.2 and FreeBSD 5.5 when attach CF
adapter(IDE) with 1GB flash card(kingston). Card is not recognized on FreeBSD
here is part of dmesg.
-- from dmesg (freebsd 5.5) --
ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to
accept
Hello all,
A friend of mine is interested to use a usb network interface 'Zydas
1201'. Problem seems this usb adapter is not recongnized by FreeBSD
6.1 ?
Can somebody say me if this usb device is supported and how ?
Regards.
___
freebsd-stable
commands):
# ./MegaCli -AdpAllinfo -a0
# ./MegaCli -AdpGetProp SpinupDriveCount -a0
Segmentation fault (core dumped)
# ./MegaCli -LDGetNum -a0
Failed to get VD count on adapter -9993.
# ./MegaCli -CfgFreeSpaceinfo -a0
Failed to initialize RM
and so on ... I am guessing this is an issue
at the dates. Those nodes could
be wrong. We have an empty /compat/linux/dev directory.
| # ./MegaCli -AdpGetProp SpinupDriveCount -a0
|
| Segmentation fault (core dumped)
| # ./MegaCli -LDGetNum -a0
|
| Failed to get VD count on adapter -9993.
| # ./MegaCli -CfgFreeSpaceinfo -a0
|
| Failed
FreeBSD 6.2-PRERELEASE #3: Tue Oct 10 13:58:29 EDT 2006
LSi 8480e SAS Raid card
mount:
linprocfs on /compat/linux/proc (linprocfs, local)
linsysfs on /compat/linux/sys (linsysfs, local)
/dev/mfid0s1d on /usr/local/pgsql (ufs, local, noatime)
dmesg:
mfi0: 2025 - PCI 0x041000 0x04411 0x041000
Sven Willenberger writes:
| FreeBSD 6.2-PRERELEASE #3: Tue Oct 10 13:58:29 EDT 2006
| LSi 8480e SAS Raid card
|
| mount:
| linprocfs on /compat/linux/proc (linprocfs, local)
| linsysfs on /compat/linux/sys (linsysfs, local)
| /dev/mfid0s1d on /usr/local/pgsql (ufs, local, noatime)
|
| dmesg:
|
Hi,
How do i set up the adater in FreeBSD. I do have the internet connection but
the light does not come up. Do I have to do some installation. please tell
me.
(I do understand that this is trival for most but for me it is very
important starting step)
Thanks
--
What we see depends mainly on
On Jun 30, 2006, at 4:28 PM, Mihir Sanghavi wrote:
How do i set up the adater in FreeBSD. I do have the internet
connection but
the light does not come up. Do I have to do some installation.
please tell
me.
There isn't enough detail to address what's going wrong. :-)
I think you're
Dennis Berger wrote:
Hey list,
after a few hours of uptime I get an highlighted kernelmessage.
ciss0: ADAPTER HEARTBEAT FAILED yes this are capital chars.
I wonder if this can be a driver problem or if it definitly a hardware
failure.
Server is a fresh HP DL360g3
sorry i can't attach a dmesg
On Mon, May 29, 2006, Dennis Berger wrote:
ciss0: ADAPTER HEARTBEAT FAILED yes this are capital chars.
I wonder if this can be a driver problem or if it definitly a hardware
failure.
We have had similar messages on a DL380 G3 in the past. They were gone
as we replaced the system board incl
1 - 100 of 137 matches
Mail list logo
