Re: [PATCH] ndis: safe fpu on amd64

On 11/22/11, Kostik Belousov wrote: > On Mon, Nov 21, 2011 at 03:49:16PM +0000, Paul B. Mahol wrote: >> Hi, >> >> This patch should fix panic on amd64 when using ndis with drivers >> which make use of fpu registers. > Do not allocate fpu_kern_ctx on stack. Its si

[PATCH] ndis: safe fpu on amd64

Hi, This patch should fix panic on amd64 when using ndis with drivers which make use of fpu registers. diff --git a/sys/compat/ndis/kern_windrv.c b/sys/compat/ndis/kern_windrv.c index 5572988..1a93b54 100644 --- a/sys/compat/ndis/kern_windrv.c +++ b/sys/compat/ndis/kern_windrv.c @@ -55,6 +55,9 @@

Re: kern/142197: [ndis] [patch] ndis is missing media status reporting

On Wed, Jan 6, 2010 at 1:04 PM, wrote: > Synopsis: [ndis] [patch] ndis is missing media status reporting > > State-Changed-From-To: open->patched > State-Changed-By: gavin > State-Changed-When: Wed Jan 6 12:02:52 UTC 2010 > State-Changed-Why: > Committed to HEAD in r201620 > > > Responsible-Chang

Re: bwi vs. bwn

On Fri, Feb 18, 2011 at 11:26 PM, grarpamp wrote: >>> Doesn't FreeBSD have some sort of ndiswrapper function for this? >>> http://www.broadcom.com/support/802.11/linux_sta.php >> NDISulator, ndis(4). > > Hmm, maybe that only applies to the Windows driver bundles as > distributed by the vendors (De

Re: bwi vs. bwn

On Fri, Feb 18, 2011 at 9:54 PM, grarpamp wrote: > Doesn't FreeBSD have some sort of ndiswrapper function for this? NDISulator, ndis(4). ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send

ndis: fix panic on i386

Hi, Following patch fix panic on i386 for drivers using such functions. Those two functions take 64-bit variable(s) for their arguments. On i386 that takes additional 32-bit variable per argument. This is required so that windrv_wrap() can correctly wrap function that miniport driver calls with s

ndis: properly allocate memory

Hi, Attached patch resolves buggy allocation of memory in NDISulator. Correct behavior is to not ignore parameters specified by miniport driver. diff --git a/src/sys/compat/ndis/subr_ntoskrnl.c b/src/sys/compat/ndis/subr_ntoskrnl.c index 04184ae..f169de5 100644 --- a/src/sys/compat/ndis/subr_ntos

Re: ndis: patch for review

On 10/20/10, Bernhard Schmidt wrote: > 9, 2010 at 23:53, Paul B Mahol wrote: >> Hi, >> >> First: we should pin curthread on CPU before we check on which CPU is >> curthread. >> >> Second: instead of sti & cli use critical sections when saving %fs &

ndis: patch for review

Hi, First: we should pin curthread on CPU before we check on which CPU is curthread. Second: instead of sti & cli use critical sections when saving %fs register. Third: I do not know what happens if we get preempted while windows code were running, so leave critical section only _after_ executin

Re: if_ndis: fix for panic with VIMAGE

On 10/13/10, Paul B Mahol wrote: > On 10/12/10, Paul B Mahol wrote: >> On 10/11/10, Paul B Mahol wrote: >>> Hi, >>> >>> There is no single valid reason to call rt_ifmsg() in >>> ndis_linksts_done() >

Re: if_ndis: fix for panic with VIMAGE

On 10/12/10, Paul B Mahol wrote: > On 10/11/10, Paul B Mahol wrote: >> Hi, >> >> There is no single valid reason to call rt_ifmsg() in ndis_linksts_done() >> >> Patch attached. >> > Ping. Pong. ___

Re: if_ndis: fix for panic with VIMAGE

On 10/11/10, Paul B Mahol wrote: > Hi, > > There is no single valid reason to call rt_ifmsg() in ndis_linksts_done() > > Patch attached. > Ping. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listi

if_ndis: fix for panic with VIMAGE

Hi, There is no single valid reason to call rt_ifmsg() in ndis_linksts_done() Patch attached. diff --git a/sys/dev/if_ndis/if_ndis.c b/sys/dev/if_ndis/if_ndis.c index 2ec9d0e..a4672e0 100644 --- a/sys/dev/if_ndis/if_ndis.c +++ b/sys/dev/if_ndis/if_ndis.c @@ -1644,10 +1644,6 @@ ndis_linksts_done(a

Re: VIMAGE + NDIS

On 10/9/10, Nikos Vassiliadis wrote: > Paul B Mahol wrote: >> On 9/27/10, Julian Elischer wrote: >>> anyone here have NDIS experience? >>> >>> On 9/27/10 10:51 AM, Nikos Vassiliadis wrote: >>>> Julian Elischer wrote: >>>>

Re: Monitor mode not working for iwi(4) on 7.X

On 10/9/10, Alexey Dokuchaev wrote: > On Fri, Oct 08, 2010 at 06:07:31PM +0000, Paul B Mahol wrote: >> Just to clear this up, iwi(4) can not support injection (see >> iwi_raw_xmit()) >> unless you manage to hack firmware ... > > Can you perhaps comment on

Re: Monitor mode not working for iwi(4) on 7.X

On 10/7/10, Alexey Dokuchaev wrote: > On Wed, Oct 06, 2010 at 11:56:25AM -0500, Brandon Gooch wrote: >> 2010/10/6 Alexey Dokuchaev : >> > On Fri, Dec 14, 2007 at 11:19:25PM +0100, Jan Henrik Sylvester wrote: >> >> In contrast to 6.2-RELEASE, monitor mode does not work. Kismet does >> >> not receiv

Re: Monitor mode not working for iwi(4) on 7.X

On 10/8/10, Alexey Dokuchaev wrote: > On Fri, Oct 08, 2010 at 03:20:08PM +0000, Paul B Mahol wrote: >> On 10/8/10, Alexey Dokuchaev wrote: >> > On Thu, Oct 07, 2010 at 08:43:37PM +0200, Bernhard Schmidt wrote: >> >> Try the attached patch, this is basically the code

Re: Monitor mode not working for iwi(4) on 7.X

On 10/8/10, Alexey Dokuchaev wrote: > On Thu, Oct 07, 2010 at 08:43:37PM +0200, Bernhard Schmidt wrote: >> Try the attached patch, this is basically the code from stable/6 >> ported to head and stable/7. I did only some basic tests but monitor >> mode seems to work and it is still possible to use

Re: Monitor mode not working for iwi(4) on 7.X

On 10/8/10, Alexey Dokuchaev wrote: > On Fri, Oct 08, 2010 at 11:48:57AM +0000, Paul B Mahol wrote: >> On 10/8/10, Alexey Dokuchaev wrote: >> > On Thu, Oct 07, 2010 at 12:44:20PM +, Paul B Mahol wrote: >> >> Monitor and injection work commpletly different a

Re: Monitor mode not working for iwi(4) on 7.X

On 10/8/10, Alexey Dokuchaev wrote: > On Thu, Oct 07, 2010 at 12:44:20PM +0000, Paul B Mahol wrote: >> On 10/7/10, Adrian Chadd wrote: >> > finding where the regression happened - eg, which revision along the >> > 6.x/head branch at the time caused the issue, would li

Re: Monitor mode not working for iwi(4) on 7.X

On 10/7/10, Adrian Chadd wrote: > finding where the regression happened - eg, which revision along the > 6.x/head branch at the time caused the issue, would likely help > Bernard very much.. > Also, exact instructions how to reproduce problem would help. Monitor and injection work commpletly dif

Re: ndis: fix ugly code

On 10/6/10, Julian Elischer wrote: > On 10/5/10 5:27 PM, Paul B Mahol wrote: >> On 10/5/10, Julian Elischer wrote: >>>On 10/5/10 1:19 PM, Paul B Mahol wrote: >>>> Hi, >>>> >>>> If clang did not complain, I would probbaly never spot it

Re: ndis: fix ugly code

On 10/5/10, Julian Elischer wrote: > On 10/5/10 1:19 PM, Paul B Mahol wrote: >> Hi, >> >> If clang did not complain, I would probbaly never spot it. >> >> Patch attached. > > personally I think you could use kproc_kthread_add so that a single > NDIS

ndis: fix ugly code

Hi, If clang did not complain, I would probbaly never spot it. Patch attached. diff --git a/sys/compat/ndis/subr_ntoskrnl.c b/sys/compat/ndis/subr_ntoskrnl.c index ba1e49f..714fcd8 100644 --- a/sys/compat/ndis/subr_ntoskrnl.c +++ b/sys/compat/ndis/subr_ntoskrnl.c @@ -274,7 +274,6 @@ ntoskrnl_libi

Re: Re: VIMAGE + NDIS

On 9/27/10, Julian Elischer wrote: > anyone here have NDIS experience? > > On 9/27/10 10:51 AM, Nikos Vassiliadis wrote: >> Julian Elischer wrote: #10 0xc0978200 in rt_dispatch (m=0xc764ad00, sa=0x0) at /usr/src/sys/net/rtsock.c:1374 1374if (V_loif) (kgdb)

Re: Re: convert Windows NDIS drivers for use with FreeBSD

On 5/14/10, jiani1012 wrote: > Yes, I use ndisgen(8) instead. Input the netathw.inf and athw.sys file, > appears: > segmentation fault (core dumped) > CONVERSION FAILED inf file have missing end of line at end, open file in text editor and add empty line at and, and try again. ___

Re: convert Windows NDIS drivers for use with FreeBSD

On 5/7/10, jiani1012 wrote: > Hi all, > I am using xp3264-7.7.0.329-whql.zip file from Atheros. > #cd /sys/modules/ndis > #make install > #cd /sys/modules/if_ndis > #make install > #ndiscvt -i netathwx.inf -s athwx.sys -o ndis_driver_data.h > (syn

NDISulator bug on amd64

On 1/16/10, Paul B Mahol wrote: > On 1/11/10, Paul B Mahol wrote: >> On 1/11/10, Bob Johnson wrote: >>> On 1/9/10, Paul B Mahol wrote: >>>> On 12/16/09, Bob Johnson wrote: >>>>> I'm using an ExpressCard for wireless networking because there se

Re: kern/142197: [ndis] [patch] ndis is missing media status reporting

The following reply was made to PR kern/142197; it has been noted by GNATS. From: Paul B Mahol To: Roman Bogorodskiy Cc: bug-follo...@freebsd.org, rpa...@freebsd.org Subject: Re: kern/142197: [ndis] [patch] ndis is missing media status reporting Date: Wed, 6 Jan 2010 11:54:48 +0100

Re: ndis: missing media status reporting

On 12/31/09, Paul B Mahol wrote: > Hi, > > if_ndis.c doesnt update link speed when associated. > > Patch is available here: > misc/142197: ndis is missing media status reporting > http://www.freebsd.org/cgi/query-pr.cgi?pr=142197 Anyo

ndis: missing media status reporting

Hi, if_ndis.c doesnt update link speed when associated. Patch is available here: misc/142197: ndis is missing media status reporting http://www.freebsd.org/cgi/query-pr.cgi?pr=142197 -- Paul B Mahol ___ freebsd-net@freebsd.org mailing list http

Re: ap_scan values

de this change, bwi works. > uath still escapes me. > > I hope someone changes the man page to let people know they need to use 2 > when > using the NDIS driver. I dont use ap_scan at all and it works for me. Using ap_scan=2 is just workaround for buggy/broken scan results. --

Re: 8.0R, AMD64 and wpi is giving me major grief

rnel: info: [drm] AGP at 0xe000 256MB >> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] Initialized i915 1.6.0 >> 20080730 >> Dec 14 07:17:57 grimsqueaker kernel: drm0: [ITHREAD] >> Dec 14 07:18:24 grimsqueaker kernel: pid 1424 (xfce4-panel), uid 1001: >> exited o

Re: kern/141376: [ndis] [patch] broken scan by passing ies and ies_len pointer to net80211

> freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > -- Paul B Mahol ___ freebsd-net@freebsd.org mailing list http://

patch: ndisusb: show device description on attach

->driver_ivar; sc = (struct ndis_softc *)dummy; sc->ndis_dev = self; -- Paul B Mahol ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-n

Re: ndis: broken scan

On 12/7/09, Paul B Mahol wrote: > Patch attached to fix scan results. > Bug is obvious if you use -v flag: > ifconfig -v wlan0 list scan > > It is interesting, that it never got noticed. I got hit with this one > when working on WPA instead of WPA2(RSN). In that case wpa_suppli

ndis: broken scan

Patch attached to fix scan results. Bug is obvious if you use -v flag: ifconfig -v wlan0 list scan It is interesting, that it never got noticed. I got hit with this one when working on WPA instead of WPA2(RSN). In that case wpa_supplicant would never pick AP because it doesnt see WPA, it could see

Re: wlan adhoc mode crash

On 12/1/09, John Hay wrote: > Hi, > > I'm not sure if this is the best list. > > I'm trying to get our Avila (arm) boards with atheros wireless cards > upgraded from 7.2 to 8.0. We use adhoc mode and I get a panic in > ieee80211_getcapinfo() because the chan pointer is 0x which seems > to mean

Re: if_ndis patch

On 10/31/09, Coleman Kane wrote: > Paul, > > Did you get to send this to sam@, etc ? Negative, now let @net know about it too. > On Fri, 2009-10-30 at 16:52 +0100, Paul B Mahol wrote: >> Hi, >> >> There is no point to do scanning how it is currentl

Re: PCI card for wlan AP

On 10/7/09, Boris Kochergin wrote: > Rui Paulo wrote: >> On 7 Oct 2009, at 20:04, Boris Kochergin wrote: >>> >>> The heavily-used ones exhibit the problem described at: >>> >>> http://lists.freebsd.org/pipermail/freebsd-net/2009-September/022894.html >>> >>> >>> >>> ...but that's a driver, not a h

Re: WLAN performance Windows/XP ./. FreeBSD 8-CURRENT

On 9/28/09, Matthias Apitz wrote: > > Hello, > > I am wondering what could cause the following WLAN performance diff > between a XP and 8-CURRENT laptop, sitting side by side and connected to > the same AP: > > OS XP 8-CURRENT > NIC Intel 3945ABGAtheros 5424/24

Re: ndis lor: hal preemption lock

On 7/15/09, Paul B. Mahol wrote: > On 7/4/09, Paul B. Mahol wrote: >> On 6/18/09, Coleman Kane wrote: >>> I've committed this one as r194432. >> >> Ah, that one introduced regression. >> Switching ndisX up before creating vap will cause panic. &

Re: ndis lor: hal preemption lock

On 7/4/09, Paul B. Mahol wrote: > On 6/18/09, Coleman Kane wrote: >> I've committed this one as r194432. > > Ah, that one introduced regression. > Switching ndisX up before creating vap will cause panic. > Here is fix: > > --- /sys/dev/if_ndis/if_ndis.c 200

Re: system panic when i use ath without swap,some advice?

On 7/10/09, ** wrote: > Hi all > > My system is atom n270 1G RAM, freebsd 7.2 release .without swap. > When my ath is associated with an AP, and the traffic is high, the > system will panic and reboot. this happened many times. > Can you give me some advice please. > thanks > > Mic

Re: ndis and USB wirelless ethernet

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

Re: hostapd with 802.1X EAP-TLS/TTLS support

On 6/18/09, Vladimir Terziev wrote: > Hi, > > i try to setup wireless access point at home, based on FreeBSD > 7.2R-i386, ral(4) wireless card and hostpad(8). > > I want my wireless AP to support 802.1x EAP-TLS/TTLS authentication. I > issued a custom SSL certificate for the hostapd(8) and put the

Re: Unable to clone wlan device

On 6/9/09, Vladimir Terziev wrote: > The actual problem, i play with wlan cloning because of, is, i try to > set up a FreeBSD based wireless access point either based on ral(4) or > iwi(4) interface. > > The ral(4) (which is "Edimax EW-7128g") seems more suitable for that, > since it has HOSTAP ca

Re: Unable to clone wlan device

only on >= 8.0. > On Tue, 2009-06-09 at 11:34 +0300, Paul B. Mahol wrote: >> wlan cloning is only available on 8.0, and iwi supports only one >> virtual >> interface at any time. -- Paul ___ freebsd-net@freebsd.org mailing list http

Re: Unable to clone wlan device

wlan cloning is only available on 8.0, and iwi supports only one virtual interface at any time. -- Paul ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr

Re: Problem/freezes with if_bwi and firmware

On 5/11/09, Gustau Perez wrote: > > Hi, > > I'm using a Broadcom BCM4312 with i386 FreeBSD-8.0 updated May 08 > 2009. Ports up to date. Using net/bwi-firmware-kmod. Loading > first bwi_v3_ucode and then if_bwi. > > When starting the supplicant, it associates fine and it works for a > period

Re: kernel crashes with ndis & -CURRENT

On 5/26/09, Adam K Kirchhoff wrote: > > In an attempt to get the native drivers working on a particular > wireless network at work I updated to -CURRENT to see if I'd have any > more luck ( http://www.freebsd.org/cgi/query-pr.cgi?pr=131153&cat= ). > > Unfortunately, that didn't work out so I was d

Re: Signal sensitivity problem with if_rum

On 5/3/09, Gustau Perez wrote: > >> That information is misleading, I remmember reading somewhere that linux >> rt73 >> had similar problems like rum but it got fixed, and is not present in >> new kernels. >> I think that problem originated for linux from now obsolete drivers. >> >> On what linux

Re: kern/125181: [ndis] [patch] with wep enters kdb.enter.unknown, panics

On 7/13/08, ga...@freebsd.org wrote: > Old Synopsis: [ndis] with wep enters kdb.enter.unknown, panics > New Synopsis: [ndis] [patch] with wep enters kdb.enter.unknown, panics > > State-Changed-From-To: feedback->open > State-Changed-By: gavin > State-Changed-When: Sun Jul 13 17:06:03 UTC 2008 > St

Re: Signal sensitivity problem with if_rum

On 5/2/09, Gustau Perez wrote: > >>> Any idea if is there anything to change/tune ? >>> >> >> There is not just bbp17 to tune there are probably others much more >> important >> registers. >> >> But as I already mentioned that code is completly missing. >> >> >I was not talking about autotun

Re: Signal sensitivity problem with if_rum

On 5/1/09, Gustau Perez wrote: > >> There is several places where bbp17 is changed. >> >> > >Editing the code looking for calls to the function rum_bbp_write, > I've been able to find where bbp17 is changed at init. Changing > rum_def_bbp[3] (which is reg 17) to values quite 'big' like 0x10 or

Re: Signal sensitivity problem with if_rum

On 5/1/09, Gustau Perez wrote: > > Hi, > > I think this is right place to post, if it is not, please let me know. > >I'm experiencing problems with two different devices using if_rum. > One is a Hercules Guillemot and the other is a Linksys Cisco WUSB54GC > > The first one is about sensi

Re: NDIS - True OR False

On 3/25/09, Chris Ruiz wrote: > > True OR False > > 1) NDIS only works with XP drivers. > > 2) NDIS only works with 32-bit drivers and wont work on amd64. > > There is a lot of conflicting information on various lists, forums and > websites regarding NDIS. http://en.wikipedia.org/wiki/NDIS -- P

Re: kern/132889: [ndis] [panic] NDIS kernel crash on load BCM4321 AGN driver

On 3/21/09, lini...@freebsd.org wrote: > Old Synopsis: NDIS kernel crash on load BCM4321 AGN driver > New Synopsis: [ndis] [panic] NDIS kernel crash on load BCM4321 AGN driver > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: S

Re: kern/132342: commit references a PR

capability only if driver reports it is capable > > PR: kern/132342 >Submitted by: "Paul B. Mahol" > > Modified: >head/sys/dev/if_ndis/if_ndis.c > > Modified: head/sys/dev/if_ndis/if_ndis.c > =

Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on device'

On 3/5/09, Erwin Hoffmann wrote: > Hi > > thanks for following my bug-report: > > --On Donnerstag, 5. Maerz 2009 01:43 + lini...@freebsd.org wrote: > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=130820 > > From: "Paul B. Mahol" > To: lini..

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/19/09, Adam K Kirchhoff wrote: > On Thu, 19 Feb 2009 05:50:35 -0500 > Adam K Kirchhoff wrote: > >> On Wed, 18 Feb 2009 19:48:10 -0500 >> Adam K Kirchhoff wrote: >> >> > On Thu, 19 Feb 2009 01:10:08 +0100 >> > "Paul B. Mahol"

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/18/09, Adam K Kirchhoff wrote: > --- if_ndis.c 2009-01-31 00:22:11.0 -0500 > +++ if_ndis.c.orig2009-02-18 14:03:30.0 -0500 > @@ -2459,6 +2459,11 @@ > bzero((char *)&config, len); > config.nc_length = len; > config.nc_fhconfig.ncf_length = sizeof(ndis_8021

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/18/09, Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 16:33:56 +0100 > "Paul B. Mahol" wrote: > >> On 2/18/09, Adam K Kirchhoff wrote: >> > On Wed, 18 Feb 2009 12:06:21 +0100 >> > "Paul B. Mahol" wrote: >> > >> >> O

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/18/09, Adam K Kirchhoff wrote: > On Wed, 18 Feb 2009 12:06:21 +0100 > "Paul B. Mahol" wrote: > >> On 2/17/09, Adam K Kirchhoff wrote: >> > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: >> >> On 2/17/09, Adam K Kirchhoff wro

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/17/09, Adam K Kirchhoff wrote: > On Tuesday 17 February 2009 17:14:07 Paul B. Mahol wrote: >> On 2/17/09, Adam K Kirchhoff wrote: >> > On Tue, 17 Feb 2009 19:22:22 +0100 >> > >> > "Paul B. Mahol" wrote: >> >> http://www.freebsd.org/

Re: kern/131781: [ndis] ndis keeps dropping the link

On 2/17/09, Adam K Kirchhoff wrote: > On Tue, 17 Feb 2009 19:22:22 +0100 > "Paul B. Mahol" wrote: > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 >> >> This one should not happen, 108 rate should get recognized. >> I will try to reproduce it on C

Re: kern/131781: [ndis] ndis keeps dropping the link

http://www.freebsd.org/cgi/query-pr.cgi?pr=131781 This one should not happen, 108 rate should get recognized. I will try to reproduce it on CURRENT. To OP, could you try 7 STABLE after 31 Jan? I guess it should not change anything but you never know. -- Paul

Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on device'

On 2/5/09, Erwin Hoffmann wrote: > Hi Paul, > > > --On 5. Februar 2009 18:56:06 +0100 "Paul B. Mahol" > wrote: > >> On 2/5/09, Erwin Hoffmann wrote: >>> Hi, >>> >>> I just saw Paul Mahol's comment: >>> &

Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on device'

On 2/5/09, Erwin Hoffmann wrote: > Hi, > > I just saw Paul Mahol's comment: > >>Yet another invalid bug report. >>OP should use -Dndis and not -Dbsd >> >>-- >>Paul > > Well. If things would be sooo easy. > Trying to declare "-D ndis" in the wpa_supplicant call as additional > argument yields: > >

Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on device'

On 1/21/09, lini...@freebsd.org wrote: > Old Synopsis: wpa_supplicant returns 'no space on device' > New Synopsis: [ndis] wpa_supplicant(8) returns 'no space on device' > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Wed Jan

Re: VLAN interface management - unloading carrying driver hangs the machine

On 1/8/09, Jack Vogel wrote: > Fine with me, go do it and I'll take the driver code out :) > > Jack > > > On Thu, Jan 8, 2009 at 12:18 AM, Yony Yossef > wrote: > >> > Jack Vogel wrote: >> > > >> > > >> > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler > > > > wrote: >> > > >

Re: kern/91859: [ndis] if_ndis does not work with Asus WL-138

If I'm not mistaken this report is bogus. Correct way to make ndis miniport module is via ndisgen which is shell script for ndiscvt. Report is bogus because OP did not kldload module which have been created with ndiscvt: kldload ndis kldload if_ndis kldload ./created_module_sys.ko -- Paul _

Re: crash in dummynet

On 12/12/08, Vyacheslav Bocharov wrote: > I have frequent panics in dummynet module: > > Dec 12 08:27:58 chip syslogd: restart > Dec 12 08:27:58 chip syslogd: kernel boot file is /boot/kernel/kernel > Dec 12 08:27:58 chip kernel: > Dec 12 08:27:58 chip kernel: > Dec 12 08:27:58 chip kernel: Fatal

Re: driver support for Belkin F5D7050 v 5xxx ?

On 11/16/08, Kayven Riese <[EMAIL PROTECTED]> wrote: > I just purchased a wireless connection device that connects to my ASUS > M6800N laptop dual > booting Vista and > > KV_BSD# uname -a > FreeBSD KV_BSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC > 2008 [EMAIL PROTECTED]:/usr/

Re: Backporting iwn(4): WPA auth hangs... Help!

On 9/21/08, Gavin Atkinson <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm attempting to backport the iwn(4) driver for the Intel 4965 driver > from -HEAD to RELENG_7 and am getting stuck with it at one particular > point: WPA authentication times out. > > I've so far tried to both take the -HEAD dr

Re: kern/125181: [ndis] [patch] with wep enters kdb.enter.unknown, panics

The following reply was made to PR kern/125181; it has been noted by GNATS. From: "Paul B. Mahol" <[EMAIL PROTECTED]> To: "Andrew Thompson" <[EMAIL PROTECTED]> Cc: "Coleman Kane" <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: kern/125181:

Re: kern/125181: [ndis] [patch] with wep enters kdb.enter.unknown, panics

On 7/17/08, Andrew Thompson <[EMAIL PROTECTED]> wrote: > The following reply was made to PR kern/125181; it has been noted by GNATS. > > From: Andrew Thompson <[EMAIL PROTECTED]> > To: Coleman Kane <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Re: kern/125181: [ndis] [pa