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 i
On 2/5/2013 11:25 AM, CeDeROM wrote:
> On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger 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 c
On Mon, Feb 4, 2013 at 10:05 PM, CeDeROM 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 to catch this
On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger 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,
t 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 t
ber 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 be rather obvi
b 4 21:29:12 FS kernel: usb_needs_explore:
>>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>>> Feb 4 21:29:12 FS kernel: usb_needs_explore:
>>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>>> Feb 4 21:29:12
b 4 21:29:12 FS kernel: usb_needs_explore:
>>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>>> Feb 4 21:29:12 FS kernel: usb_needs_explore:
>>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>>> Feb 4 21:29:12
t;>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>> Feb 4 21:29:12 FS kernel: usb_needs_explore:
>>> Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78
>>> Feb 4 21:29:13 FS kernel: usb_needs_explore:
>>> Feb 4 21:29:13 FS kernel: usb_bus_powe
;>>>
>>>>>>>>> Those messages all seem to be related to a hub. Vendor ID 0x0409 is
>>>>>>>>> NEC.
>>>>>>>>>
>>>>>>>>> FTDI's vendor ID is 0x0403, and FTDI stuff works fine in Fre
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
>>>>>>>
>>>>>>>> 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
>>>
gt;>>>>>
>>>>>>> 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 vendo
termarket vendors who use FTDI's
>>>>>> parts program different vendor/product info and IDs have to be added to
>>>>>> code to recognize them, that's the only trouble one usually encounters.
>>>>>>
>>>>>> -- Ian
>>
ly trouble one usually encounters.
>>>>>
>>>>> -- Ian
>>>> Well, that sorta kinda worked.
>>>>
>>>> Except that it still is identifying it as a hub too, and the two collide
>>>> and crash the stack.
>>>&g
usually encounters.
>>>>>
>>>>> -- Ian
>>>> Well, that sorta kinda worked.
>>>>
>>>> Except that it still is identifying it as a hub too, and the two collide
>>>> and crash the stack.
>>>>
>>>> Bu
at it still is identifying it as a hub too, and the two collide
> >> and crash the stack.
> >>
> >> But I can't find anything that is looking at the PID (0x0050) or the
> >> definition (HUB_0050) anywhere in the code.
> >>
> >> I'll
>>
>> Except that it still is identifying it as a hub too, and the two collide
>> and crash the stack.
>>
>> But I can't find anything that is looking at the PID (0x0050) or the
>> definition (HUB_0050) anywhere in the code.
>>
>> I'l
it as a hub too, and the two collide
> >> and crash the stack.
> >>
> >> But I can't find anything that is looking at the PID (0x0050) or the
> >> definition (HUB_0050) anywhere in the code.
> >>
> >> I'll go pull the NEC defs and
On Mon, Feb 4, 2013 at 10:20 PM, Karl Denninger 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 after
Except that it still is identifying it as a hub too, and the two collide
>> and crash the stack.
>>
>> But I can't find anything that is looking at the PID (0x0050) or the
>> definition (HUB_0050) anywhere in the code.
>>
>> I'll go pull the NEC defs
On Mon, 2013-02-04 at 22:05 +0100, CeDeROM wrote:
> On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore 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 i
PID (0x0050) or the
> definition (HUB_0050) anywhere in the code.
>
> I'll go pull the NEC defs and set up something else instead of simply
> adding 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
On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore 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 recognize them,
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: at usbus4
>> uhub6:
>> on usbus4
>> uhub_attach: port 1 power on
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: at usbus4
>> uhub6:
>> on usbus4
>> uhub_attach: port 1 power on
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: at usbus4
> uhub6:
> on usbus4
> uhub_attach: port 1 power on failed, USB_ERR_STALLED
> uhub_attach: port 2 pow
... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD
9.1-STABLE #16 r244942
and it returns
ugen4.4: at usbus4
uhub6:
on usbus4
uhub_attach: port 1 power on failed, USB_ERR_STALLED
uhub_attach: port 2 power on failed, USB_ERR_STALLED
uhub_attach: port 3 power on failed, USB_ERR_ST
; >>> 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.
> > > > >>
>
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:
> > > > >&g
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
> >
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 rou
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 t
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. :-)
And
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 th
> > 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
&
URRENT?
>>
>> Thanks,
>>
>> Etienne
>
> Hi,
>
> 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 th
t; me if you have 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
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
> 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 w
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... :)
Also do you have any idea
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
__
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 wrote:
> On Sun, 4 Mar 2012 14:39:01 +0800
> Irjohn Junus wrote:
>
> > Hello,
> >
> > This was origi
n H61S Mini-ITX 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).
Hello,
This was originally posted here:
http://forums.freebsd.org/showthread.php?p=168854&posted=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 a
hi lists
DWL-G132 failed to load on 9.0RC3
uath0:
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 uathload
lp# uathload -v -d /dev/ugen3.2
Load firmware ar5523.bin (bu
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 wr
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 from
ut this. I've did some source code
> > reading and found following tunable:
> > 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
> >
rce code
> reading and found following tunable:
> 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(
: 0
>
Ok, I found other way round about this. I've did some source code
reading and found following tunable:
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, i
2011/4/28 Jack Vogel :
> On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin 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 what breaks this.
>>
On Thu, Apr 28, 2011 at 2:28 PM, John Baldwin 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
> > Apr
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 vect
ed. I'm not sure,
> whether this matters.
>
> Cheers,
>
> Wiktor
>
> 2011/4/28 Jack Vogel :
> > Notice this: em0: Using MSIX interrupts with 0 vectors
> >
> > ZERO vectors are not a good sign :) You need to look at your system, you
> > have MSIX
me message in /var/log/messages??
>
> Jack
>
>
> On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki wrote:
>>
>> 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
> 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
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-PRERELE
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 adapte
he 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 it. If I remove the
volume set or passthrough from the adapter first, that's fine - I can do
tha
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 wa
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'
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 get
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm not sure if I should have sent this to freebsd-questions@, but
here we go.
I have a couple of Dell PowerEdge R200 rack servers, both equipped
with the Dell SAS 6i/R RAID controller, running i386 7.2-RELEASE but
they'll soon be upgraded to
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 h
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 present
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
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
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)
> amr0: 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
Please let us know i
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
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
There will be a new code drop soon also.
That worked perfectly. Now I see:
pci23:
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
There will be a new code drop soon also.
Jack
On Wed, Feb 11, 2009 at 5:16 PM, Greg Rivers
> wrote:
> On Thu, 12 Feb 2009, pl
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, it
2009/2/12 Kip Macy :
> 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
> wrote:
>> I'm trying to light an Intel 10GbE adapter in an HP DL380 G5 using very
>> recent 7.1-STABLE amd64 with GENE
see ixgbe(4)
On Wed, Feb 11, 2009 at 2:43 PM, Greg Rivers
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 on the card sh
On Wed, Feb 11, 2009 at 3:21 PM, pluknet wrote:
> Hi.
>
> 2009/2/12 Greg Rivers
>
> >:
> > 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
>
Hi.
2009/2/12 Greg Rivers :
> 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 S
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
EXPX9502FX
OS H430, 256MB RAM
> amr0: delete logical drives supported by controller
> amrd0: 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 ha
)
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 logical drives supported by controller
I also tried to setup 7.0
not take a chance and ordered a Prolific based Iogear
adapter. :)
Thanks,
Aragon
(who wishes laptops still had com ports)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 Su
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 firm
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 not
usbdevs
and umodem.c is sufficient?
Secondly, the bluetooth adapter shows up as a straightforward serial port ..
kernel: sio4: 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 to the bluetooth netgraph stack
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 leadi
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.
___
free
her entries look 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
scsi_host/host*/proc_name
(null)
megaraid_sas
(null)
# sysctl compat.linux
compat.linux.oss_version: 198144
compat.linux.osrelease: 2.6.12
compat.linux.osname: Linux
Although the MegaCli utility no longer complains about not finding a
controller, it sadly does nothing else either (except dump core on
ce
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:
| mf
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 0x041
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 trying
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 wha
it looks like '6.1 with qouta' bug back again ...
server works normaly for 10-15 minutes, then everything in the kernel
working perfectly, user-land programs - hangs up ...
cat /var/run/dmesg.boot:
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991
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 replac
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&
1 - 100 of 128 matches
Mail list logo
