On Wed, Aug 19, 2009 at 12:42 PM, Jack Vogel wrote:
> We've repro'd this, it wasnt caught before because he only tested copper.
>
> I will get the change submitted.
>
> Jack
Did this change ever get committed to RELENG_8?
Sam Fourman Jr.
___
freebsd-n
We've repro'd this, it wasnt caught before because he only tested copper.
I will get the change submitted.
Jack
On Wed, Aug 19, 2009 at 9:07 AM, Jack Vogel wrote:
> That should not be necessary. I will have someone look into this today.
>
> Jack
>
>
>
> On Tue, Aug 18, 2009 at 11:58 PM, Sam F
That should not be necessary. I will have someone look into this today.
Jack
On Tue, Aug 18, 2009 at 11:58 PM, Sam Fourman Jr. wrote:
> On Wed, Aug 19, 2009 at 1:06 AM, Jack Vogel wrote:
> > Hmmm, that's odd, I had the validation group do a thorough test
> > of older adapters, and that one did
On Wed, Aug 19, 2009 at 1:06 AM, Jack Vogel wrote:
> Hmmm, that's odd, I had the validation group do a thorough test
> of older adapters, and that one did not seem to have a problem,
> let me see if we can repro the issue tomorrow, but, in principle I
> have no problem doing this.
>
> Jack
I can p
Hmmm, that's odd, I had the validation group do a thorough test
of older adapters, and that one did not seem to have a problem,
let me see if we can repro the issue tomorrow, but, in principle I
have no problem doing this.
Jack
On Tue, Aug 18, 2009 at 7:55 PM, Sam Fourman Jr. wrote:
> On Mon,
On Mon, Jul 13, 2009 at 12:25 PM, Mark Atkinson wrote:
> Jack Vogel wrote:
>> In case you hadn't seen it, the code that fixes this is now checked into
>> the tip, so the latest em driver should work for you.
>
> I upgraded the machine in question this morning and it appears to be
> working, thanks!
Jack Vogel wrote:
> In case you hadn't seen it, the code that fixes this is now checked into
> the tip, so the latest em driver should work for you.
I upgraded the machine in question this morning and it appears to be
working, thanks!
>>> em0: mem
>>> 0xdb00-0xdb01
>>> irq 28 at device
In case you hadn't seen it, the code that fixes this is now checked into
the tip, so the latest em driver should work for you.
Jack
On Sun, Jun 28, 2009 at 9:52 AM, Jack Vogel wrote:
> Sigh.. both windows and linux have frozen drivers for this old hardware,
> therefore they never see the regre
Sigh.. both windows and linux have frozen drivers for this old hardware,
therefore they never see the regressions they cause in the current code :(
I will make a patch for you to test on Monday Mark, it will do the same
thing
that I did in the e1000_82540.c, basically change the read_mac function
>From: Jack Vogel
>Oh, hmmm, so this card is completely broken with the new driver then?
Completely, unfortunately (they don't show up in ifconfig, only in
dmesg/pciconf).
>What was the last working version you used?
I was running a kernel from -current May 2
Oh, hmmm, so this card is completely broken with the new driver then?
What was the last working version you used?
Jack
On Fri, Jun 26, 2009 at 11:36 AM, Mark Atkinson wrote:
> Jack Vogel wrote:
>
> > I'm willing to bet that its in fact the same problem that VMWare is
> > having. Our method of
Jack Vogel wrote:
> I'm willing to bet that its in fact the same problem that VMWare is
> having. Our method of getting the mac address changed, and the emulations
> seem to be unprepared for it.
>
> This was done for a real customer requirement to allow support of
> alternate mac addressing in f
2009/5/2 Jack Vogel :
> I'm willing to bet that its in fact the same problem that VMWare is having.
> Our method of getting the mac address changed, and the emulations seem
> to be unprepared for it.
>
> This was done for a real customer requirement to allow support of alternate
> mac addressing in
I'm willing to bet that its in fact the same problem that VMWare is having.
Our method of getting the mac address changed, and the emulations seem
to be unprepared for it.
This was done for a real customer requirement to allow support of alternate
mac addressing in firmware. What happens now is a
Hi,
When I upgraded my 7-STABLE virtual machine under VirtualBox to
8-CURRENT, the em driver stopped working. VirtualBox supports three
different flavours of emulated em devices, all of which result in the
"Invalid MAC address" error and cannot be used any more.
The error was previously repo
15 matches
Mail list logo
