On Tue, Jul 07, 2009 at 12:51:16PM +0300, Nikos Vassiliadis wrote:
> Weongyo Jeong wrote:
> >I'm happy to see your device is successfully associated with AP.
> >However it seems it's a bad news that you sometimes meet crashes. Does
> >a random crash mean a OS hang (e.g. could not type any keys) or
Weongyo Jeong wrote:
I'm happy to see your device is successfully associated with AP.
However it seems it's a bad news that you sometimes meet crashes. Does
a random crash mean a OS hang (e.g. could not type any keys) or no more
work of network operations?
It hangs, I cannot use the keyboard a
On Fri, Jul 03, 2009 at 06:49:07PM +0300, Nikos Vassiliadis wrote:
> Hello Weongyo & net,
>
> I did some tests with an AP. The bad news is that I am
> getting random crashes. At least I cannot relate them
> to something... It just stops responding, I cannot break
> to the debugger. Would I try ano
Hello Weongyo & net,
I did some tests with an AP. The bad news is that I am
getting random crashes. At least I cannot relate them
to something... It just stops responding, I cannot break
to the debugger. Would I try another driver? there are
3 versions if I recall correctly on the vendor's site.
Weongyo Jeong wrote:
OK. A last steps you can try is as follows and could you show me the
result?
# kldload ndis if_ndis NDIS_module
# sysctl debug.ndis=1
# sysctl hw.ndisusb.halt=0
[then plug-in USB stick]
# ifconfig wlan0 create wlandev ndis0
#
On Sat, Jun 27, 2009 at 04:13:29PM +0300, Nikos Vassiliadis wrote:
> Weongyo Jeong wrote:
> >Could you show me the *full* result after enabling `sysctl debug.ndis=1'?
> >Maybe steps would be as follows:
> >
> > # kldload ndis if_ndis NDIS_module
> > # sysctl debug.ndis=1
> > [then plug-
Paul B. Mahol wrote:
On 6/27/09, Nikos Vassiliadis wrote:
Weongyo Jeong wrote:
Could you show me the *full* result after enabling `sysctl debug.ndis=1'?
Maybe steps would be as follows:
# kldload ndis if_ndis NDIS_module
# sysctl debug.ndis=1
[then plug-in USB stick]
On 6/27/09, Nikos Vassiliadis wrote:
> Weongyo Jeong wrote:
>> Could you show me the *full* result after enabling `sysctl debug.ndis=1'?
>> Maybe steps would be as follows:
>>
>> # kldload ndis if_ndis NDIS_module
>> # sysctl debug.ndis=1
>> [then plug-in USB stick]
>
> It goes like
Weongyo Jeong wrote:
Could you show me the *full* result after enabling `sysctl debug.ndis=1'?
Maybe steps would be as follows:
# kldload ndis if_ndis NDIS_module
# sysctl debug.ndis=1
[then plug-in USB stick]
It goes like this:
ugen1.2: at usbus1
ndis0: NDIS API vers
Hello Mr.Vassiliadis,
I see you were trying to use a Netgear WG111v3 WiFi dongle. I had also
tried to work with this dongle last year with FreeBSD 7.0 but to no avail,
ndis never managed to build a correct driver module for this dongle.
I don't know if the more recent versions of FreeBSD have add
On Thu, Jun 25, 2009 at 03:16:10PM +0300, Nikos Vassiliadis wrote:
> Weongyo Jeong wrote:
> >Could you please test with attached patch and show me the result?
>
> The repeating warning message went away and the ndis0 interface
> appeared. Now, when I try to 'up' the interface, ifconfig gets
> stuc
Weongyo Jeong wrote:
Could you please test with attached patch and show me the result?
The repeating warning message went away and the ndis0 interface
appeared. Now, when I try to 'up' the interface, ifconfig gets
stuck in KeWFS state. If I try a second ifconfig, it will show
the ndis0 in up st
On Thu, Jun 25, 2009 at 11:42:21AM +0300, Nikos Vassiliadis wrote:
> Hello,
>
> I am trying to use a wireless ethernet USB thingy,
> but the ndis interface never appears. Any hints?
>
>
> ndis0: NDIS API version: 5.1
> lock order reversal:
> 1st 0xc0edc900 HAL preemption lock (HAL lock) @
> /u
Hello,
I am trying to use a wireless ethernet USB thingy,
but the ndis interface never appears. Any hints?
ndis0: NDIS API version: 5.1
lock order reversal:
1st 0xc0edc900 HAL preemption lock (HAL lock) @
/usr/src/sys/compat/ndis/subr_hal.c:416
2nd 0xc23a61ec NDIS USB (network driver) @
/us
14 matches
Mail list logo
