On 5/20/09, Chris Whitehouse cwhi...@onetel.com wrote:
Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/13/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
Just typing bt on db prompt for now
Paul B. Mahol wrote:
On 5/20/09, Chris Whitehouse cwhi...@onetel.com 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
Chris Whitehouse wrote:
Paul B. Mahol wrote:
On 5/13/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
Just typing bt on db prompt for now should be enough.
panic: sleeping thread
cpuid = 0
KDB:
On 5/13/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse cwhi...@onetel.com 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 ]
Paul B. Mahol wrote:
On 5/13/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse cwhi...@onetel.com 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
On 5/12/09, Chris Whitehouse cwhi...@onetel.com 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
Paul B. Mahol wrote:
On 5/12/09, Chris Whitehouse cwhi...@onetel.com 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
On 5/11/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/8/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse cwhi...@onetel.com wrote:
In the meantime I've tried the three possible drivers (XP, NT and an
unlabelled one).
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
Paul B. Mahol wrote:
On 5/8/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse cwhi...@onetel.com 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
On 5/8/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse cwhi...@onetel.com 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
On 5/7/09, Chris Whitehouse cwhi...@onetel.com 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?
Paul B. Mahol wrote:
On 5/7/09, Chris Whitehouse cwhi...@onetel.com 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
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
Paul B. Mahol wrote:
On 5/2/09, Paul B. Mahol one...@gmail.com wrote:
On 5/1/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse cwhi...@onetel.com wrote:
Hi all
I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
Marvell 8335
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
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse cwhi...@onetel.com 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:
On 5/1/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse cwhi...@onetel.com 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
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/2/09, Paul B. Mahol one...@gmail.com wrote:
On 5/1/09, Chris Whitehouse cwhi...@onetel.com wrote:
Paul B. Mahol wrote:
On 4/29/09, Chris Whitehouse cwhi...@onetel.com wrote:
Hi all
I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a
Marvell 8335 chip. I've created a
On 4/29/09, Chris Whitehouse cwhi...@onetel.com 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
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: interrupt storm detected on irq11:;
22 matches
Mail list logo