Paul B. Mahol wrote:
On 5/20/09, Chris Whitehouse wrote:
has this died a death? Anything else I can do? Should I file a PR?
Perhaps donate some money, not to me directly :) , file a PR, send card
with complete machine so that problem can be completly and promptly
explored and etc...
yes sp
On 5/20/09, Chris Whitehouse wrote:
> Chris Whitehouse wrote:
>> Paul B. Mahol wrote:
>>> On 5/13/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
> On 5/12/09, Chris Whitehouse wrote:
>> Paul B. Mahol wrote:
>>> Just typing bt on db prompt for now should be enough.
>> panic
Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/13/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
panic: sleeping thread
cpuid = 0
KDB: enter: panic
[thread pid 1497 tid 1000
Paul B. Mahol wrote:
On 5/13/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
panic: sleeping thread
cpuid = 0
KDB: enter: panic
[thread pid 1497 tid 100073 ]
Stopped atkdb_en
On 5/13/09, Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>> On 5/12/09, Chris Whitehouse wrote:
>>> Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
>>> panic: sleeping thread
>>> cpuid = 0
>>> KDB: enter: panic
>>> [thread pid 1497 tid 100073 ]
>>> Stopped at
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
panic: sleeping thread
cpuid = 0
KDB: enter: panic
[thread pid 1497 tid 100073 ]
Stopped atkdb_enter+0x3a: movl$0,kdb_why
db> bt
Tracing pid 1497 tid 100
On 5/12/09, Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>>
>> Just typing bt on db prompt for now should be enough.
>
> panic: sleeping thread
> cpuid = 0
> KDB: enter: panic
> [thread pid 1497 tid 100073 ]
> Stopped atkdb_enter+0x3a: movl$0,kdb_why
> db> bt
> Tracing pid 1497 tid 10007
Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
panic: sleeping thread
cpuid = 0
KDB: enter: panic
[thread pid 1497 tid 100073 ]
Stopped atkdb_enter+0x3a: movl$0,kdb_why
db> bt
Tracing pid 1497 tid 100073 td 0xc356c900
kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d40
On 5/11/09, Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>> On 5/8/09, Chris Whitehouse wrote:
>>> Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse wrote:
> In the meantime I've tried the three possible drivers (XP, NT and an
> unlabelled one). I've also installed a recent 8-
Paul B. Mahol wrote:
On 5/8/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse wrote:
In the meantime I've tried the three possible drivers (XP, NT and an
unlabelled one). I've also installed a recent 8-current snapshot,
updated to latest source and built world, an
On 5/8/09, Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>> On 5/7/09, Chris Whitehouse wrote:
>>
>>> In the meantime I've tried the three possible drivers (XP, NT and an
>>> unlabelled one). I've also installed a recent 8-current snapshot,
>>> updated to latest source and built world, and tried
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse wrote:
In the meantime I've tried the three possible drivers (XP, NT and an
unlabelled one). I've also installed a recent 8-current snapshot,
updated to latest source and built world, and tried the XP driver. Still
get interrupt storms everywher
On 5/7/09, Chris Whitehouse wrote:
> Tim Judd wrote:
>> I think project evil (ndis) requires a specific driver version, such as
>> the
>> WinXP drivers versus the Vista or 2000 or anything else.
>>
>>
>>
>> What drivers did you use? Any other drivers available on the manufacturer
>> website?
>>
>
Tim Judd wrote:
I think project evil (ndis) requires a specific driver version, such as the
WinXP drivers versus the Vista or 2000 or anything else.
What drivers did you use? Any other drivers available on the manufacturer
website?
If you're not using XP, I recall reading that XP is the pre
Tim Judd wrote:
I think project evil (ndis) requires a specific driver version, such as the
WinXP drivers versus the Vista or 2000 or anything else.
What drivers did you use? Any other drivers available on the manufacturer
website?
If you're not using XP, I recall reading that XP is the pre
Paul B. Mahol wrote:
On 5/2/09, Paul B. Mahol wrote:
On 5/1/09, Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse wrote:
Hi all
I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
Marvell 8335 chip. I've created a module with ndisgen and I can se
On 5/2/09, Paul B. Mahol wrote:
> On 5/1/09, Chris Whitehouse wrote:
>> Paul B. Mahol wrote:
>>> On 4/29/09, Chris Whitehouse wrote:
Hi all
I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
Marvell 8335 chip. I've created a module with ndisgen and I can s
I think project evil (ndis) requires a specific driver version, such as the
WinXP drivers versus the Vista or 2000 or anything else.
What drivers did you use? Any other drivers available on the manufacturer
website?
If you're not using XP, I recall reading that XP is the preferred driver for
On 5/1/09, Chris Whitehouse wrote:
> Paul B. Mahol wrote:
>> On 4/29/09, Chris Whitehouse wrote:
>>> Hi all
>>>
>>> I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
>>> Marvell 8335 chip. I've created a module with ndisgen and I can see
>>> ndis0. When I up it with ifconfig
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse wrote:
Hi all
I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
Marvell 8335 chip. I've created a module with ndisgen and I can see
ndis0. When I up it with ifconfig I immediately get repeated messages:
Apr 28 23:23:19 pcb
On 4/29/09, Chris Whitehouse wrote:
> Hi all
>
> I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
> Marvell 8335 chip. I've created a module with ndisgen and I can see
> ndis0. When I up it with ifconfig I immediately get repeated messages:
>
> Apr 28 23:23:19 pcbsd kernel: i
21 matches
Mail list logo
