Re: WiFi Tool for BSD
> On 5 Apr 2018, at 20:21, Mateusz Piotrowski <0...@freebsd.org> wrote: > >> On 1 April 2018 at 05:24, Alex Andrews wrote: >>> What would be really useful is a simple wifi debugging tool that >>> could run through all of the steps necessary to get a wifi card >>> working (check the driver is loaded and working, check "syctl >>> net.lan.devices", then check /etc/rc.conf for the correct wlans_ and >>> ifconfig_ entries, etc etc). I imagine this would be a fairly >>> simple task for someone with the appropriate knowledge/skill set, >>> and I am sure others would find it useful too. Any chance this >>> might be considered? > > I wonder if bsdinstall(8) would be sufficient. It is the tool, which > configures your network connection during installation. I think it can > be used to configure WiFi of a running system as well. On a running system the equivalent is bsdconfig(8) - you can type `bsdconfig netdev' to get straight to the Network Interfaces menu. - Felix ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Any way to get the NDISulator working on 11.0-RELEASE?
I *was* using it for my BCM4331 prior to 11-BETA, when it mysteriously broke. If I can find some time this weekend I’ll have another go at getting it working. -- Felix Friedlander > On 6 Apr 2017, at 3:53 pm, Adrian Chadd wrote: > > hiya, > > I don't know of anyone actively using it, sorry. :( > > > -a > > >> On 2 April 2017 at 18:41, Kiernan Hager wrote: >> I am the not-so-proud owner of a BCM43224 wireless card, which is in my >> MacBook and, I am told, not easily replaced due to it having an odd shape. >> I am currently using 10.3. I tried to compile it myself from the github >> repository, but it gave me an error (I can't remember what it was). Does >> anyone know if there is a way to make NDISulator or the built-in version to >> work on 11.0? ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: sourcecode of broadcom drivers up to 2011 yr sup
> On 18 Nov. 2016, at 05:36, paradox via freebsd-wireless > wrote: > > seems all BCM WIFI PHY & MAC sourcecode of ABG/N/LP/NT/SSN > hope your can build it or take part for independ module > MAC > https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/sys > PHY > https://github.com/elenril/VMG1312-B/tree/master/bcmdrivers/broadcom/net/wl/impl10/wl/phy There’s a difference between finding the code, and having a licence to use it… If I’m not mistaken Adrian already has access to the proprietary Broadcom driver through his work, it’s more of a licensing issue. Still a nice find though, with this and the Cypress datasheets some things may become a bit easier. -- Felix Friedlander smime.p7s Description: S/MIME cryptographic signature
Re: Updating bwn to support newer chipsets
Hi Brett,
It turns out I actually have no idea how to write wireless drivers,
but progress is being made by adrian and others. I don't think there's
a working build to test - yet - but if you want to help code, then by
all means, just talk to someone more competent than me.
For the record, I'm also dual-booting several MacBooks, both BCM4331
(apparently not *that* far off) and the newer BCM4360 (which is miles
away, being an 11ac chip).
- Felix
On 1 September 2016 at 17:43, Brett Wiggins wrote:
> Hi everyone,
>
> I'm replying to a message from April 07 2015 which was calling for people to
> help get the bwn driver to support BCM4331 adapters. The message is provided
> below. I am happy to help with code or testing. I'm dual booting a Macbook
> Pro 10,1 with OS X and Freebsd 10.3-RELEASE, my wireless adapter is a
> BCM4331.
>
> If anyone know of progress on this or needs help please let me know.
>
> Brett.
>
>
> Updating bwn to support newer chipsets
>
> *Felix Friedlander* felixphew0 at gmail.com
> <mailto:freebsd-wireless%40freebsd.org?Subject=Re%3A%20Updating%20bwn%20to%20support%20newer%20chipsets&In-Reply-To=%3C20150407063452.GA918%40phewbox%3E>
> /Tue Apr 7 06:35:13 UTC 2015/
>
> * Previous message (by thread): hostapd with wpa
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/005710.html>
> * Next message (by thread): Updating bwn to support newer chipsets
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/005712.html>
> * *Messages sorted by:* [ date ]
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/date.html#5709>
>[ thread ]
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/thread.html#5709>
>[ subject ]
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/subject.html#5709>
>[ author ]
>
> <https://lists.freebsd.org/pipermail/freebsd-wireless/2015-April/author.html#5709>
>
>
>
>
> Hello all,
> I am trying to expand the bwn driver to support some newer-model Broadcom
> chips, like the BCM4331 in my machine. These chips require newer firmware,
> and so I have modified bwn-firmware-kmod to use a newer firmware. However, I
> do not have a device with one of the chips currently supported, so I cannot
> be sure that this change won't break things. Do any of you have a device
> that you are willing to try with the new firmware?
>
> The changes are quite simple:
>
> --- Makefile.orig 2014-01-27 08:52:12.0 +1100
> +++ Makefile2015-04-07 08:31:46.0 +1000
> @@ -2,7 +2,7 @@
> # $FreeBSD: head/net/bwn-firmware-kmod/Makefile 341294 2014-01-26 21:52:12Z
> bapt $
> PORTNAME= bwn-firmware
> -PORTVERSION= 0.1.0
> +PORTVERSION= 0.2.0
> CATEGORIES=net
> MASTER_SITES= http://downloads.openwrt.org/sources/ \
> http://mirror2.openwrt.org/sources/
> @@ -36,11 +36,11 @@
> WRKSRC=${WRKDIR}
> FWNAME=bwn_v4
> FWFILE=broadcom-wl-${FWVERSION}.tar.bz2
> -FWVERSION= 4.150.10.5
> +FWVERSION= 5.100.138
> KMODNAME= ${FWNAME}_ucode
> FWNAME_LP= bwn_v4_lp
> FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2
> -FWVERSION_LP= 4.178.10.4
> +FWVERSION_LP= 5.100.138
> KMODNAME_LP= ${FWNAME_LP}_ucode
> PLIST_SUB= KMODNAME="${KMODNAME}" \
> KMODNAME_LP="${KMODNAME_LP}"
> @@ -54,7 +54,7 @@
> tar xjf ${DISTDIR}/${FWFILE}
> mkdir -p ${WRKSRC}/bg
> b43-fwcutter -w ${WRKSRC}/bg \
> - ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o
> + ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o
> ${TOUCH} ${WRKSRC}/bg/v4/ucode.fw
> @${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile
> --- distinfo.orig 2014-01-23 02:30:13.0 +1100
> +++ distinfo2015-04-07 08:37:10.0 +1000
> @@ -2,3 +2,5 @@
> SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794
> SHA256 (broadcom-wl-4.178.10.4.tar.bz2) =
> 32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f
> SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780
> +SHA256 (broadcom-wl-5.100.138.tar.bz2) =
> f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f
>
> Any help would be much appreciated.
> --
> Felix Friedlander <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>>
> -- next part --
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 819 bytes
Re: Can't get BCM4313 ndis driver to work
> On 19 Jul. 2016, at 10:41, Yuri wrote: > >> On 07/17/2016 16:02, Yuri wrote: >> This post https://forums.freebsd.org/threads/33728/ says that BCM4313 should >> work. >> >> But ndis driver when loaded doesn't create the ndis0 interface. >> >> I think only bcmwl564_sys.ko should suffice, though I also tried with 3 .ko >> files too like this guy suggested. >> >> >> Why doesn't ndis0 appear? How to troubleshoot this? Is BCM4313 still not >> supported by the native drivers > > This was probably a wrong version of the Windows drivers. Some website called > WikiDrivers had the right version. > > Yuri > Does this mean that NDIS drivers are working again? I thought they were broken… -- Felix Friedlander smime.p7s Description: S/MIME cryptographic signature
Re: ath (AR9280) with nanoBSD (fwd)
> On 30 Jun 2016, at 21:02, Ian Smith wrote: > > Sorry Felix, didn't notice you hadn't cc'd the list .. hoping you don't > mind if I do, might save someone else from responding .. cheers, Ian Nope, that’s fine, I meant to but I forget all the time. Alpine, mutt and other CLI mail clients manage to do it automatically, so I wonder how the GUI clients have missed out… - Felix > > -- Forwarded message -- > Date: Thu, 30 Jun 2016 20:52:43 +1000 (EST) > From: Ian Smith > To: Felix Friedlander > Subject: Re: ath (AR9280) with nanoBSD > > On Thu, 30 Jun 2016 20:28:54 +1000, Felix Friedlander wrote: >>> On 30 Jun 2016, at 19:12, Ian Smith wrote: >>> >>> On Wed, 29 Jun 2016 11:51:40 -0700, Adrian Chadd wrote: >>> >>>> Hi, >>>> >>>> It's there, it just doesn't show up in ifconfig anymore. >>>> >>>> sysctl net.wlan.devices >>>> >>>> if you create the interface (ifconfig wlan0 create wlandev ath0) then >>>> it'll show up! >>> >>> Just curious .. why was it considered a good idea not to have ifconfig >>> show wireless interfaces? Won't this make for ongoing such confusion? >> >> As I understand it, it was to avoid duplication. You have to create a >> wlanN interface to use a wireless device, so you would end up with >> both athN and wlanN. Now ath (and every other wireless driver) donÿÿt >> directly appear in ifconfig, you only have one interface. > > Ah, that sounds fair enough. I expect there'll be something in 11.0 > release notes about that. > >> I believe there is a sysctl to list the hardware devices if you want. > > I guess that might be net.wlan.devices :) > > Ok, sorry for the side-track .. > > cheers, Ian smime.p7s Description: S/MIME cryptographic signature
Re: How to develop a wireless driver?
Are you sure the existing driver doesn’t work? Try adding these two lines to loader.conf: if_urtwn_load=“YES" legal.realtek.license_ack=1 and rebooting. If that doesn’t work, I would be looking at NDIS as your next best option - writing drivers is *hard*(as I have discovered in my own attempts to update the bwn(4) driver). > On 5 Sep 2015, at 7:16 AM, fmm...@openmailbox.org wrote: > > > > Hello, I have a wireless card that does not work in FreeBSD but in > Gnu/Linux with a proprietary firmware (my wireless card is Realtek > RTL8188CE), the firmware is rtl8192cfw.bin. > My question is: How can I develop a free wireless driver and build it > with a custom kernel in FreeBSD? > > Thanks for your help. > > ___ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
new bwn(4) firmware
Hi all, Sorry about my last firmware, it may have broken a few things. This one should be all good, but unfortunately I can't test it myself because I don't have a wireless card to test it on. The patch (against net/bwn-firmware-kmod) is available at http://paste2.org/X7XezZXg. -- Felix Friedlander pgpbhwwS91f9t.pgp Description: PGP signature
Re: bwn update
Unfortunately, the BCM4313 isn't supported. I'm in the same position with my
BCM4331. Tell you what - I'll try and do that one while I'm updating the
drivers.
On Fri, Jul 03, 2015 at 02:39:55AM +0100, Miguel C wrote:
> On Fri, Jul 3, 2015 at 2:33 AM, Adrian Chadd wrote:
> > Hm!
> >
> > Would someone please test those above dragonflybsd patches and see
> > what happens? I'm happy to commit patches if they're at least tested!
> >
>
> The only BCM I have is 4313, if that one is supported I would be glad to test
>
> > -a
> >
> >
> > On 2 July 2015 at 18:30, Miguel C wrote:
> >> If I may ask any change "'BCM4313" will ever be supported? (and also
> *chance*
>
> >> is it supported in drangonfly since it was mentioned)?
> >>
> >>
> >> On Thu, Jul 2, 2015 at 8:52 PM, Imre Vadasz wrote:
> >>> Hi,
> >>> Just FYI, since nobody at FreeBSD has picked this stuff up yet (and I
> >>> don't
> >>> have the time or energy to work on FreeBSD as well). In the DragonFly port
> >>> of bwn(4), we have fixed a few typos and added a few bugfixes (which end
> >>> up
> >>> improving bwn(4)'s performance and stability a lot on my BCM4312 chipset
> >>> ('BCM4311 802.11a/b/g' in pciconf -lv)):
> >>>
> >>> A fix for RF switch state polling:
> >>> http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/202e28d1f65e9f35df6032400df3242a3bafb483
> >>>
> >>> Remove a superfluous ieee80211_start_all call:
> >>> http://gitweb.dragonflybsd.org/dragonfly.git/commit/9ce8b3ee47294f82be9c626470deefb943eb2cb1
> >>>
> >>> A fix for a DMA issue on some chipsets, and a fix for a performance
> >>> problem on my BCM4312 (and maybe other chipsets):
> >>> http://gitweb.dragonflybsd.org/dragonfly.git/commit/b7a8b6abd2cfa6cd927aefa770aff3030ffce28c
> >>> ___
> >>> freebsd-wireless@freebsd.org mailing list
> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >>> To unsubscribe, send any mail to
> >>> "freebsd-wireless-unsubscr...@freebsd.org"
> >> ___
> >> freebsd-wireless@freebsd.org mailing list
> >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
pgp5CrlQFjrg5.pgp
Description: PGP signature
bwn update
Hi all,
So, I've been working a bit on the bwn(4) driver, updating it to support newer
cards, but I've hit a bit of a dead end. I've successfully made siba(4)
recognise the card, but much more mork needs to be done and it's a bit beyond
my skills (at least without help).
However, I _have_ ported the new(er) firmware, and it seems to work OK even on
older cards. This will need more testing, so if anyone has a card currently
supported by bwn(4) and would like to give it a go, the diff against
net/bwn-firmware-kmod is below:
Index: Makefile
===
--- Makefile(revision 391018)
+++ Makefile(working copy)
@@ -2,7 +2,7 @@
# $FreeBSD$
PORTNAME= bwn-firmware
-PORTVERSION= 0.1.0
+PORTVERSION= 0.2.0
CATEGORIES=net
MASTER_SITES= http://downloads.openwrt.org/sources/ \
http://mirror2.openwrt.org/sources/
@@ -24,24 +24,11 @@
lp0bsinitvals14 lp0bsinitvals15 \
n0bsinitvals11
-FIRMWARES_LP= \
- ucode ucode5 ucode11 ucode13 ucode14 ucode15\
- pcm5 a0g1initvals5 a0g0initvals5\
- b0g0initvals5 b0g0initvals13 a0g1bsinitvals5 a0g0bsinitvals5\
- b0g0bsinitvals5 \
- lp0initvals13 lp0initvals14 lp0initvals15 lp0bsinitvals13 \
- lp0bsinitvals14 lp0bsinitvals15 \
- n0bsinitvals11
-
WRKSRC=${WRKDIR}
FWNAME=bwn_v4
FWFILE=broadcom-wl-${FWVERSION}.tar.bz2
-FWVERSION= 4.150.10.5
+FWVERSION= 5.100.138
KMODNAME= ${FWNAME}_ucode
-FWNAME_LP= bwn_v4_lp
-FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2
-FWVERSION_LP= 4.178.10.4
-KMODNAME_LP= ${FWNAME_LP}_ucode
PLIST_SUB= KMODNAME="${KMODNAME}" \
KMODNAME_LP="${KMODNAME_LP}"
@@ -54,9 +41,8 @@
tar xjf ${DISTDIR}/${FWFILE}
mkdir -p ${WRKSRC}/bg
b43-fwcutter -w ${WRKSRC}/bg \
- ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o
+ ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o
${TOUCH} ${WRKSRC}/bg/v4/ucode.fw
-
@${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile
@${ECHO_CMD} "FIRMWS= ${FIRMWARES:C/.*/&.fw:${FWNAME}_&/}" >> \
${WRKSRC}/bg/v4/Makefile
@@ -63,20 +49,7 @@
@${ECHO_CMD} ".include " >> ${WRKSRC}/bg/v4/Makefile
@cd ${WRKSRC}/bg/v4; make all
- cd ${WRKSRC} && \
- tar xjf ${DISTDIR}/${FWFILE_LP}
- mkdir -p ${WRKSRC}/lp
- b43-fwcutter -w ${WRKSRC}/lp \
- ${WRKSRC}/broadcom-wl-${FWVERSION_LP}/linux/wl_apsta.o
- ${TOUCH} ${WRKSRC}/lp/v4/ucode.fw
- @${ECHO_CMD} "KMOD= ${KMODNAME_LP}" > ${WRKSRC}/lp/v4/Makefile
- @${ECHO_CMD} "FIRMWS= ${FIRMWARES_LP:C/.*/&.fw:${FWNAME_LP}_&/}" >> \
- ${WRKSRC}/lp/v4/Makefile
- @${ECHO_CMD} ".include " >> ${WRKSRC}/lp/v4/Makefile
- @cd ${WRKSRC}/lp/v4; make all
-
do-install:
@cd ${WRKSRC}/bg/v4; ${SETENV} ${MAKE_ENV}
KMODDIR="${STAGEDIR}${KMODDIR}" make install
- @cd ${WRKSRC}/lp/v4; ${SETENV} ${MAKE_ENV}
KMODDIR="${STAGEDIR}${KMODDIR}" make install
.include
Index: distinfo
===
--- distinfo(revision 391018)
+++ distinfo(working copy)
@@ -1,4 +1,2 @@
-SHA256 (broadcom-wl-4.150.10.5.tar.bz2) =
a9f4e276a4d8d3a1cd0f2eb87080ae89b77f0a7140f06d4e9e2135fc44fdd533
-SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794
-SHA256 (broadcom-wl-4.178.10.4.tar.bz2) =
32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f
-SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780
+SHA256 (broadcom-wl-5.100.138.tar.bz2) =
f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f
+SIZE (broadcom-wl-5.100.138.tar.bz2) = 13514651
Note that this one firmware replaces the two previous firmwares (standard and
low-power). I would be grateful if anyone else could try this firmware out, and
let me know if you have any issues.
In the meantime, Adrian is going to help find a developer from the Linux b43
driver to maybe help us out a bit. But don't expect a working driver anytime
soon :-)
--
Felix Friedlander
pgppsXZgArr_K.pgp
Description: PGP signature
Re: [x-post] BCM4313 Wireless LAN Controller in FreeBSD 10.1-RELEASE
Hello, I am not 100% sure, but I don’t think either the bwi(4) or bwn(4) drivers support the BCM4313. I am in the midst of updating the bwn driver but this is still a way off. In the meantime, NDIS is your best bet. By the way, the device name would be: bwi0 if you are using bwi, bwn0 if you are using bwn, ndis0 if you are using a driver generated with ndis. Hope this helps! > On 7 May 2015, at 5:14 pm, Avinash Sonawane wrote: > > Hello! > > I am pretty new to BSD world . I just installed FreeBSD > 10.1-RELEASE on my system. > > # uname -a > FreeBSD titanic.rootkea.me 10.1-RELEASE FreeBSD 10.1-RELEASE #0 > r274401: Tue Nov 11 21:02:49 UTC 2014 > r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > # pciconf -lv | grep -B3 -i wireless > subclass = HDA > none3@pci0:18:0:0:class=0x028000 card=0x00101028 chip=0x472714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN Controller' > > I have also installed the port net/bwn-firmware-kmod using make install clean. > > I have also made changes to /boot/loader.conf as suggested in the > Handbook. Here is my /boot/loader.conf > # cat /boot/loader.conf > if_bwn_load="YES" > wlan_wep_load="YES" > wlan_ccmp_load="YES" > wlan_tkip_load="YES" > > But now I am confused about the next step. > According to handbook it should be # ifconfig wlan0 create wlandev ath0 [1] > I have no idea what to write in place of ath0. So I tried bwn and > bwn0. But both the times system said > "ifconfig : SIOCIFCREATE2 : Device not configured" > > So how do I access wireless in my FreeBSD box? > > PS- On surfing the net I stumbled upon using ndisgen to install the > BCM4313 driver [2]. But I would really appreciate if there is any > other way to natively install the driver on FreeBSD instead of > converting the WINDOWS(R) driver. > Or is this the only way? > > Please help. > > Links: > [1] https://www.freebsd.org/doc/handbook/network-wireless.html#idp79356624 > [2] http://blog.cochard.me/2012/10/using-bcm4313-wireless-chip-under.html > > -- > Avinash Sonawane (RootKea) > PICT, Pune > http://rootkea.wordpress.com > ___________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: run vs urtwn
> Hmm... unusual. Try removing that last line entirely - it doesn’t seem to serve any useful purpose I can see. > It sounds good and it would allow me to spare some bucks (Croatian kunas) if > the performance would be satisfying. Performance is generally OK with NDIS drivers, the only issue is you often miss out on features like promiscuous and monitor mode. -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: run vs urtwn
Could you send me the whole file? It’s hard to tell from just that line. Also, in answer to your previous question, no, you do not have to repeat the process with each OS upgrade. It will only need doing once, except maybe if you rebuild world and kernel. > On 4 May 2015, at 5:49 pm, Gour wrote: > > > Felix Friedlander writes: > >> or reply to this email if you need help. > > I dl-ed winxp64 driver and tried running: > > ndisgen Drt2870.inf Drt2870.sys > > but got: "ndiscvt: line 841: :syntax error." > CONVERSION FAILED > > Line (last one) 841 of DrtDrt2870.inf is as follows: > > BaldEagle_SSID = "amz?;'seimdf^&j$#@ksjdo*(hq!" > > > Any hint what's wrong there? > > > Sincerely, > Gour > > -- > Those who are on this path are resolute in purpose, > and their aim is one. O beloved child of the Kurus, > the intelligence of those who are irresolute is many-branched. > -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: run vs urtwn
If you are wanting to purchase an adapter, any of those 3 would be fine. However, have you considered using your builtin NIC with ndis(4)? [See section 12.5.1.1 of the FreeBSD Handbook][1] for instructions, or reply to this email if you need help. [1]: https://www.freebsd.org/doc/en/books/handbook/config-network-setup.html#config-network-ndis > On 3 May 2015, at 10:42 pm, Gour wrote: > > After resolving some issue I'm preparing to fully migrate from (openSUSE) > Linux to Free/PC-BSD and looking for advice in regard to support for USB Wifi > adapters. > > My netbook has integrated RTL8188CE chipset which, afaict, is not supported > under FreeBSD. > > From before I have D-Link's DWA-125 USB adapter which works, but it's a > little bulky in comparison with newer mini/nano adapters and after some > research I've arrived to the following list of adapters which are easy to get > here: > > 1) Asus USB-N10 > > 2) Trendnet TEW-649UB > > 3) Edimax EW-7811UN > > According to the list at > https://www.freebsd.org/releases/10.1R/hardware.html#support > > 1) & 2) use 'rsu' driver while Edimax is supported by 'urtwn'. > > What would you recommend as the best option? > > > Sincerely, > Gour > > -- > One is understood to be in full knowledge whose every endeavor > is devoid of desire for sense gratification. > > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Any success stories for BCM 4331?
No, I have tried both ways and it is currently not supported - full stop (at least on 64bit installs, apparently it is possible to make 32-bit ones work with ndis(4) ). I am currently working on upgrading bwn(4) to support these newer cards however I am still a way off. I’ll let you know what I find! I have a mid-2012 13” BTW, it’s going great (apart from wifi obviously). > On 28 Apr 2015, at 2:49 am, John Nielsen wrote: > > I have a mid-2012 15” Retina MacbookPro10,1. I’ve been mostly successful > getting FreeBSD to run on it (I’ll do a blog post on that later), but haven’t > had any luck with the built-in wireless: > > none4@pci0:4:0:0: class=0x028000 card=0x00ef106b chip=0x433114e4 > rev=0x02 hdr=0x00 >vendor = 'Broadcom Corporation' >device = 'BCM4331 802.11a/b/g/n' >class = network > > Some googling led me to believe that although this chip isn’t supported by > bwn(4), it ought to work with ndis(4). However, I haven’t had any success. > Modules I load based on bcmwl664.sys (I’ve found and tried several different > versions) just complain that there is “no match for” a bunch of function > names and then I get “NDIS dummy called…”. > > Modules I load based on bcmwl564.sys seem to identify the card, but then I > get “driver attach returned 12” and no usable interface. > > Does anyone have any ideas or pointers to a specific Windows driver that > works with NDIS? > > Thanks, > > John Nielsen > > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Broadcom BCM4318
As you seem to be having problems applying my patch, I have applied the patch for you and compressed the result into the attached tarball. Unfortunately, I’m the only person who’s free to help with this atm and I’m less-than-knowledgable about the internal details of bwn(4) (which is unfortunate as I’m currently trying to update it!). Please try copying this firmware into the ports tree and rebuilding. > On 20 Apr 2015, at 1:38 pm, Mohammad BadieZadegan wrote: > > Hi, > Long time no new hint! > Is that impossible to fix this BCM4318 BUG? > Regards. > > On Sat, Apr 18, 2015 at 6:50 AM, Mohammad BadieZadegan > wrote: > >> Hi Nikola Pajkovsky, >> This is the Felix Friedlander patch file. >> I get some Hunks Error in step one(Makefile). >> >> On Wed, Apr 15, 2015 at 4:28 PM, Nikola Pajkovsky >> wrote: >> >>> Mohammad BadieZadegan writes: >>> >>>> I try your command but nothing changed! >>> >>> Send me your patch and I will try it. >>> >>> -- >>> Nikola >>> >> >> >> >> -- >> <http://ir.linkedin.com/in/xadegan> >> > > > > -- > <http://ir.linkedin.com/in/xadegan> > _______ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Broadcom BCM4318
Weird - that shouldn’t happen, I even tested it.. It will prompt you 3 times. Enter Makefile at the first prompt, distinfo at the second, and pkg-plist at the third. > On 14 Apr 2015, at 7:56 pm, Mohammad BadieZadegan wrote: > > My FreeBSD Prompt Messages is: > > > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -- > |diff -u 1/Makefile 2/Makefile > |--- 1/Makefile 2015-04-14 07:14:31.0 +1000 > |+++ 2/Makefile 2015-04-14 07:19:58.0 +1000 > -- > File to patch: > > On Tue, Apr 14, 2015 at 1:10 PM, Mohammad BadieZadegan > wrote: > OK, I correct your hint "patch -p0 patch" and wait for me! > > On Tue, Apr 14, 2015 at 12:15 PM, Felix Friedlander > wrote: > > I copied your patch into bwn-firmware-kmod folder and then: > > root@unix:/usr/ports/net/bwn-firmware-kmod # patch -p0 bwn5fw.patch > > > > but nothing occured! and my prompt > > [root@unix:/usr/ports/net/bwn-firmware-kmod #] does not appear! > You missed the < operator. The command should be "patch -p0 The patch program was just waiting forever for the patch to arrive on stdin, > which is where it expects it. Press Ctrl-C to stop it, and then run the > correct command above. Sorry if my email was less than clear. > -- > Felix Friedlander > > > > > > > -- > > > > > -- > -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Broadcom BCM4318
It just so happens I’m currently working on porting `bwn` to newer cards, and I
was thinking it might be worth trying out the new(er) firmware I’m using. Try
applying these patches to `bwn-firmware-kmod` and re-installing, and tell me
what happens.
--- Makefile.orig 2014-01-27 08:52:12.0 +1100
+++ Makefile2015-04-07 08:31:46.0 +1000
@@ -2,7 +2,7 @@
# $FreeBSD: head/net/bwn-firmware-kmod/Makefile 341294 2014-01-26 21:52:12Z
bapt $
PORTNAME= bwn-firmware
-PORTVERSION= 0.1.0
+PORTVERSION= 0.2.0
CATEGORIES= net
MASTER_SITES= http://downloads.openwrt.org/sources/
<http://downloads.openwrt.org/sources/> \
http://mirror2.openwrt.org/sources/
<http://mirror2.openwrt.org/sources/>
@@ -36,11 +36,11 @@
WRKSRC= ${WRKDIR}
FWNAME= bwn_v4
FWFILE= broadcom-wl-${FWVERSION}.tar.bz2
-FWVERSION= 4.150.10.5
+FWVERSION= 5.100.138
KMODNAME= ${FWNAME}_ucode
FWNAME_LP= bwn_v4_lp
FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2
-FWVERSION_LP= 4.178.10.4
+FWVERSION_LP= 5.100.138
KMODNAME_LP=${FWNAME_LP}_ucode
PLIST_SUB= KMODNAME="${KMODNAME}" \
KMODNAME_LP="${KMODNAME_LP}"
@@ -54,7 +54,7 @@
tar xjf ${DISTDIR}/${FWFILE}
mkdir -p ${WRKSRC}/bg
b43-fwcutter -w ${WRKSRC}/bg \
- ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o
+ ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o
${TOUCH} ${WRKSRC}/bg/v4/ucode.fw <http://ucode.fw/>
@${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile
--- distinfo.orig 2014-01-23 02:30:13.0 +1100
+++ distinfo2015-04-07 08:37:10.0 +1000
@@ -2,3 +2,5 @@
SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794
SHA256 (broadcom-wl-4.178.10.4.tar.bz2) =
32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f
SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780
+SHA256 (broadcom-wl-5.100.138.tar.bz2) =
f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f
Let me know what you find, this may not fix anything but it’s worth a shot.
> On 12 Apr 2015, at 6:18 pm, Mohammad BadieZadegan wrote:
>
> I installed that, I reported all of important messages at
> https://forums.freebsd.org/threads/unknown-hp-notebook-wireless-driver.51161/
>
> On Sun, Apr 12, 2015 at 11:31 AM, Felix Friedlander
> wrote:
>
>> You need to install the 'sysutils/bwn-firmware-kmod' port.
>> --
>> Felix
>> On 12 Apr 2015 5:59 pm, "Mohammad BadieZadegan"
>> wrote:
>>
>>> Hi,
>>> I have a problem to connecting Broadcom BCM4318 and I started this topic
>>> <
>>> https://forums.freebsd.org/threads/unknown-hp-notebook-wireless-driver.51161/
>>>>
>>> at FreeBSD forum about it.
>>> My device inform me about not finding of (bwn-open_v4_ucode5) firmware!
>>> How can I resolve this problem?
>>> Regards.
>>> ___
>>> freebsd-wireless@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>> To unsubscribe, send any mail to "
>>> freebsd-wireless-unsubscr...@freebsd.org"
>>>
>>
>
>
> --
> <http://ir.linkedin.com/in/xadegan>
> ___
> freebsd-wireless@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
--
Felix Friedlander
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Broadcom BCM4318
You need to install the 'sysutils/bwn-firmware-kmod' port. -- Felix On 12 Apr 2015 5:59 pm, "Mohammad BadieZadegan" wrote: > Hi, > I have a problem to connecting Broadcom BCM4318 and I started this topic > < > https://forums.freebsd.org/threads/unknown-hp-notebook-wireless-driver.51161/ > > > at FreeBSD forum about it. > My device inform me about not finding of (bwn-open_v4_ucode5) firmware! > How can I resolve this problem? > Regards. > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org > " > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Updating bwn to support newer chipsets
Hello all,
I am trying to expand the bwn driver to support some newer-model Broadcom
chips, like the BCM4331 in my machine. These chips require newer firmware, and
so I have modified bwn-firmware-kmod to use a newer firmware. However, I do not
have a device with one of the chips currently supported, so I cannot be sure
that this change won't break things. Do any of you have a device that you are
willing to try with the new firmware?
The changes are quite simple:
--- Makefile.orig 2014-01-27 08:52:12.0 +1100
+++ Makefile2015-04-07 08:31:46.0 +1000
@@ -2,7 +2,7 @@
# $FreeBSD: head/net/bwn-firmware-kmod/Makefile 341294 2014-01-26 21:52:12Z
bapt $
PORTNAME= bwn-firmware
-PORTVERSION= 0.1.0
+PORTVERSION= 0.2.0
CATEGORIES=net
MASTER_SITES= http://downloads.openwrt.org/sources/ \
http://mirror2.openwrt.org/sources/
@@ -36,11 +36,11 @@
WRKSRC=${WRKDIR}
FWNAME=bwn_v4
FWFILE=broadcom-wl-${FWVERSION}.tar.bz2
-FWVERSION= 4.150.10.5
+FWVERSION= 5.100.138
KMODNAME= ${FWNAME}_ucode
FWNAME_LP= bwn_v4_lp
FWFILE_LP= broadcom-wl-${FWVERSION_LP}.tar.bz2
-FWVERSION_LP= 4.178.10.4
+FWVERSION_LP= 5.100.138
KMODNAME_LP= ${FWNAME_LP}_ucode
PLIST_SUB= KMODNAME="${KMODNAME}" \
KMODNAME_LP="${KMODNAME_LP}"
@@ -54,7 +54,7 @@
tar xjf ${DISTDIR}/${FWFILE}
mkdir -p ${WRKSRC}/bg
b43-fwcutter -w ${WRKSRC}/bg \
- ${WRKSRC}/broadcom-wl-${FWVERSION}/driver/wl_apsta_mimo.o
+ ${WRKSRC}/broadcom-wl-${FWVERSION}/linux/wl_apsta.o
${TOUCH} ${WRKSRC}/bg/v4/ucode.fw
@${ECHO_CMD} "KMOD= ${KMODNAME}" > ${WRKSRC}/bg/v4/Makefile
--- distinfo.orig 2014-01-23 02:30:13.0 +1100
+++ distinfo2015-04-07 08:37:10.0 +1000
@@ -2,3 +2,5 @@
SIZE (broadcom-wl-4.150.10.5.tar.bz2) = 3888794
SHA256 (broadcom-wl-4.178.10.4.tar.bz2) =
32f6ad98facbb9045646fdc8b54bb03086d204153253f9c65d0234a5d90ae53f
SIZE (broadcom-wl-4.178.10.4.tar.bz2) = 5986780
+SHA256 (broadcom-wl-5.100.138.tar.bz2) =
f1e7067aac5b62b67b8b6e4c517990277804339ac16065eb13c731ff909ae46f
Any help would be much appreciated.
--
Felix Friedlander
pgpaiDglcTniL.pgp
Description: PGP signature
Re: How to make working new Broadcom chips like BCM4331?
> On 2 Apr 2015, at 9:12 am, Johannes Dieterich wrote: > > On Wed, Apr 1, 2015 at 11:42 PM, Felix Friedlander <mailto:felixph...@gmail.com>> wrote: >>> Hi, >>> >>> On Mon, 02 Feb 2015 08:12:17 +0300 >>> Alexander Perechnev wrote: >>> >>>> Hello everyone, >>>> >>>> I’ve installed FreeBSD 10.1 on my MacBook Pro 13 mid 2012. Everything >>>> works pretty good, except wireless. It works with [ndis], but it >>>> doesn’t work with existing [bwi-firmware-kmod] and >>>> [bwn-firmware-kmod] facilities. >>>> >>>> I’ve looked into [bwn] port Makefile >>>> (https://github.com/aperechnev/freebsd-ports/blob/master/net/bwn-firmware-kmod/Makefile) >>>> and found that all it does is just to download necessary firmware >>>> (4.150.10.5 and 4.178.10.4), extracts it via [b43-fwcutter-015] and >>>> compiles it into kernel module. >>>> >>>> So the first problem is that 4th gen firmware does not support my >>>> BCM4331. >>>> >>>> Also i’ve found the [siba-bwn], which recognizes the broadcom >>>> devices: >>>> https://github.com/freebsd/freebsd/blob/master/sys/dev/siba/siba_bwn.c. >>>> >>>> So summary it seems that it is not so hard to support my BCM4331. I >>>> have to: >>>> >>>> - port [b43-fwcutter-018] to FreeBSD, because earlier versions >>>> doesn’t work with newest firmware >>>> - update existing [bwn-firmware-kmod] to point it to newest firmware >>>> - add my BCM4331 device to [siba-bwn] >>>> >>>> I expect that after this steps my BCM4331 should be working. But I am >>>> new in FreeBSD and I’m just asking you for any help like related >>>> information, existing problems, links, etc. >>>> >>>> I am not sure if I am right in my theory, but for me it seems that it >>>> should work. So if you know another problems, which I don’t, please >>>> let me know before I go through this steps. >>>> >>>> Thank you for excellent operating system, now it’s my favorite one! >>>> >>>> Best regards, >>>> Alexander Perechnev. >>>> ___ >>>> freebsd-wireless at freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> To unsubscribe, send any mail to >>>> "freebsd-wireless-unsubscribe at freebsd.org" >>> >>> Hi, >>> >>> out of curiosity I reviewed the BCM status. >>> >>> IMO you don't have to port the b43-fwcutter to BSD. It would be nice, >>> but you can use any Linux to get the firmware (from /lib/firmware/). For >>> example. >>> https://help.ubuntu.com/community/MacBookPro8-2/Oneiric#Wireless >>> >>> As of the support, JFYI >>> BCM4331 Linux driver is provided by Broadcom >>> http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt >>> >>> ,there is no support in the Linux kernel atm >>> https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 >>> >>> and I'm not sure, where do the bwi/bwn drivers come from (to see how >>> probable is the support of BCM4331). >>> bwi -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver >>> bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver >>> >>> >>> Cheers, >>> >>> -vlado >> Just out of curiosity, is anyone working on this ATM? I’ve had the same >> problem, and it is (no offence to anyone intended) a bit ridiculous that the >> latest Broadcom chips we support are around 5 years old now. I don’t >> actually know enough to say this for sure, but judging by the first message >> it looks like this is a (relatively) simple fix - simply add newer firmware >> and sell siba to detect the new cards. Is this the case, or am I misreading >> the whole situation? > Well, looking at the commit history of both the siba source and the > port containing the firmware binaries, I'd say the driver is in > maintenance mode since March 2010. Which nicely lines up with the five > year old chips, unfortunately. No idea if it is indeed as simple as > adding a few PCI-IDs and the binaries but if you have such a device, > maybe you could try it? I’ll try, however my coding skills are truly woeful :-). I have access to devices with BCM4331 and BCM43224 (I’m a convert from the Mac worl
Re: How to make working new Broadcom chips like BCM4331?
> Hi, > > On Mon, 02 Feb 2015 08:12:17 +0300 > Alexander Perechnev wrote: > >> Hello everyone, >> >> I’ve installed FreeBSD 10.1 on my MacBook Pro 13 mid 2012. Everything >> works pretty good, except wireless. It works with [ndis], but it >> doesn’t work with existing [bwi-firmware-kmod] and >> [bwn-firmware-kmod] facilities. >> >> I’ve looked into [bwn] port Makefile >> (https://github.com/aperechnev/freebsd-ports/blob/master/net/bwn-firmware-kmod/Makefile) >> and found that all it does is just to download necessary firmware >> (4.150.10.5 and 4.178.10.4), extracts it via [b43-fwcutter-015] and >> compiles it into kernel module. >> >> So the first problem is that 4th gen firmware does not support my >> BCM4331. >> >> Also i’ve found the [siba-bwn], which recognizes the broadcom >> devices: >> https://github.com/freebsd/freebsd/blob/master/sys/dev/siba/siba_bwn.c. >> >> So summary it seems that it is not so hard to support my BCM4331. I >> have to: >> >> - port [b43-fwcutter-018] to FreeBSD, because earlier versions >> doesn’t work with newest firmware >> - update existing [bwn-firmware-kmod] to point it to newest firmware >> - add my BCM4331 device to [siba-bwn] >> >> I expect that after this steps my BCM4331 should be working. But I am >> new in FreeBSD and I’m just asking you for any help like related >> information, existing problems, links, etc. >> >> I am not sure if I am right in my theory, but for me it seems that it >> should work. So if you know another problems, which I don’t, please >> let me know before I go through this steps. >> >> Thank you for excellent operating system, now it’s my favorite one! >> >> Best regards, >> Alexander Perechnev. >> ___ >> freebsd-wireless at freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to >> "freebsd-wireless-unsubscribe at freebsd.org" > > Hi, > > out of curiosity I reviewed the BCM status. > > IMO you don't have to port the b43-fwcutter to BSD. It would be nice, > but you can use any Linux to get the firmware (from /lib/firmware/). For > example. > https://help.ubuntu.com/community/MacBookPro8-2/Oneiric#Wireless > > As of the support, JFYI > BCM4331 Linux driver is provided by Broadcom > http://www.broadcom.com/docs/linux_sta/README_6.30.223.248.txt > > ,there is no support in the Linux kernel atm > https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 > > and I'm not sure, where do the bwi/bwn drivers come from (to see how > probable is the support of BCM4331). > bwi -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver > bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver > > > Cheers, > > -vlado Just out of curiosity, is anyone working on this ATM? I’ve had the same problem, and it is (no offence to anyone intended) a bit ridiculous that the latest Broadcom chips we support are around 5 years old now. I don’t actually know enough to say this for sure, but judging by the first message it looks like this is a (relatively) simple fix - simply add newer firmware and sell siba to detect the new cards. Is this the case, or am I misreading the whole situation? Also, the Broadcom-provided linux STA driver you referenced above is not very widely used - b43 (the kernel driver) is much more common, and requires extracting the firmware just like the FreeBSD drivers. See https://wireless.wiki.kernel.org/en/users/Drivers/b43 -- Felix Friedlander ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
