Hi Shawn,
Thanks for let me know about iwlwifi driver status.
I will post at freebsd-wireless mailing soon about it.
Cheers,
Nuno Teixeira
Shawn Webb escreveu no dia segunda, 1/08/2022
à(s) 18:10:
> On Mon, Aug 01, 2022 at 01:05:07AM +0100, Nuno Teixeira wrote:
> > Hello,
> >
> > I'm trying to
On Mon, Aug 01, 2022 at 01:05:07AM +0100, Nuno Teixeira wrote:
> Hello,
>
> I'm trying to setup a failover mode ethernet/wireless as shown in
> https://docs.freebsd.org/en/books/handbook/book/#networking-lagg-wired-and-wireless
> and I got a panic.
>
> /etc/rc.conf:
> ---
> ifconfig_re0="ether "
On Mon, Aug 1, 2022 at 1:30 PM Mario Lobo wrote:
>
>
> On Mon, Aug 1, 2022, 11:01 Nuno Teixeira wrote:
>
>> Hi,
>>
>> Something is wrong about getting ether and wlan mac adresses.
>> dmesg shows the same address:
>> ---
>> iwlwifi0: Detected Inte
On Mon, Aug 1, 2022, 11:01 Nuno Teixeira wrote:
> Hi,
>
> Something is wrong about getting ether and wlan mac adresses.
> dmesg shows the same address:
> ---
> iwlwifi0: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
> iwlwifi0: base HW address: 6c:6a:77:df:09:21
> (..
Hi,
Something is wrong about getting ether and wlan mac adresses.
dmesg shows the same address:
---
iwlwifi0: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351
iwlwifi0: base HW address: 6c:6a:77:df:09:21
(...)
re0: port
0x3000-0x30ff mem 0xb4204000-0xb4204fff,0xb420-0xb4203fff at device 0.0
On Sun, Jul 31, 2022, 21:05 Nuno Teixeira wrote:
> Hello,
>
> I'm trying to setup a failover mode ethernet/wireless as shown in
> https://docs.freebsd.org/en/books/handbook/book/#networking-lagg-wired-and-wireless
> and I got a panic.
>
> /etc/rc.conf:
> ---
> ifconfig_re0="ether "
> wlans_iwlwif
Hello,
I'm trying to setup a failover mode ethernet/wireless as shown in
https://docs.freebsd.org/en/books/handbook/book/#networking-lagg-wired-and-wireless
and I got a panic.
/etc/rc.conf:
---
ifconfig_re0="ether "
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA"
create_args_wlan0="country PT"
cloned
On Fri, 11 Sep 2020 14:20:22 +
"Bjoern A. Zeeb" wrote:
> On 11 Sep 2020, at 14:02, Tomoaki AOKI wrote:
>
> > On Thu, 10 Sep 2020 10:22:05 +
> > "Bjoern A. Zeeb" wrote:
> >
> >> On 9 Sep 2020, at 22:41, Tomoaki AOKI wrote:
> >>
> >>> This breaks at least iwm. (Other drivers not tested.)
On 11 Sep 2020, at 14:02, Tomoaki AOKI wrote:
On Thu, 10 Sep 2020 10:22:05 +
"Bjoern A. Zeeb" wrote:
On 9 Sep 2020, at 22:41, Tomoaki AOKI wrote:
This breaks at least iwm. (Other drivers not tested.)
Messages below are repeatedly shown and no carrier detected.
Manually reverting this c
appers between
> >> ieee80211_vap_attach() and ieee80211_media_change(), so remove the
> > extra
> >> function, where possible as well.
> >>
> >> PR: 248955
> >> Submitted by:Tong Zhang (ztong0001 gmail.com) (origi
if_otus.c
head/sys/dev/usb/wlan/if_run.c
head/sys/dev/wtap/if_wtap.c
Modified: head/sys/dev/ath/if_ath.c
==
--- head/sys/dev/ath/if_ath.c Mon Sep 7 14:40:33 2020(r365418)
+++ head/sys/dev/ath/if_ath.
Modified:
> head/sys/dev/ath/if_ath.c
> head/sys/dev/bwi/if_bwi.c
> head/sys/dev/iwm/if_iwm.c
> head/sys/dev/iwn/if_iwn.c
> head/sys/dev/mwl/if_mwl.c
> head/sys/dev/otus/if_otus.c
>
On 9/19/19 7:30 PM, Cy Schubert wrote:
> In message om>
> , Johannes Lundberg writes:
>> --0875960592f275a3
>> Content-Type: text/plain; charset="UTF-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> Tested today with bgscan added. Didn=E2=80=99t connect to home network unti=
>
ISABLED]
> > > > >> > 2 network3 any[DISABLED]
> > > > >> > 3 network4 any[DISABLED]
> > > > >> > 4 network5 any[DISABLED]
> > > > >> > Selected
s this by doing network_enable x in wpa_cli and it all
> > > >comes
> > > >> > back. I asked Adrian about this in the past, but it needs some
> > > >> > debugging
> > > >> > to pin down.
> > > >>
>
;
> > >> Is this iwm(4) as well in your case or another card?
> > >>
> > >> /bz
> > >> ___
> > >> freebsd-wirel...@freebsd.org
> > <mailto:freebsd-wirel...@f
I've no idea, bgscan is broken with atheros NICs because the driver still
doesn't do background scan without dropping frames :(
(one of many thing I'd love to fix, but life/time.)
please do experiment though! I think wpa_supplicant's roaming logic would
benefit from a lot more work.
-adrian
On 9/19/19 3:06 PM, Adrian Chadd wrote:
> So roaming in ifconfig/net80211 is what's set to manual.
>
> wpa_supplicant right now does RSSI threshold based roaming. All of the
> roaming and network preferences when wpa_supplicant is running is done
> in wpa_supplicant. That's where you have to look.
So roaming in ifconfig/net80211 is what's set to manual.
wpa_supplicant right now does RSSI threshold based roaming. All of the
roaming and network preferences when wpa_supplicant is running is done in
wpa_supplicant. That's where you have to look. Ideally wpa_supplicant would
be triggering bgscan
On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
wrote:
>Roaming is done in wpa_supplicant when it's running.That's where the
>smarts
>need to be. :(
>
>
>
>-adrian
>
>
>On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb
>
>wrote:
>
>> On 19 Sep 2019, at 12:28, Tom Jones wrote:
>>
>> Hi,
>>
>> freebs
Roaming is done in wpa_supplicant when it's running.That's where the smarts
need to be. :(
-adrian
On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb
wrote:
> On 19 Sep 2019, at 12:28, Tom Jones wrote:
>
> Hi,
>
> freebsd-wireless might be a better list for all this ..
>
>
> > On Tue, Sep 17, 2019
On 19 Sep 2019, at 12:28, Tom Jones wrote:
Hi,
freebsd-wireless might be a better list for all this ..
On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote:
In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>,
Johannes Lundber
g writes:
For a long time now
On Tue, Sep 17, 2019 at 04:36:28PM +, Poul-Henning Kamp wrote:
>
> In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes
> Lundber
> g writes:
>
> >For a long time now I have had this problem with iwm and wlan0. Whenever
> >I move between work and home it won't reco
In message <707bcd3f-fa6b-82eb-fa8f-09c4b800f...@freebsd.org>, Johannes Lundber
g writes:
>For a long time now I have had this problem with iwm and wlan0. Whenever
>I move between work and home it won't reconnect automatically and I have
>to do wlan0 scan manually for it to pick up the di
Hi
For a long time now I have had this problem with iwm and wlan0. Whenever
I move between work and home it won't reconnect automatically and I have
to do wlan0 scan manually for it to pick up the different network.
Anyone have a solution for this? For now I think I'll put a 'ifconfig
wlan0 scan'
gt;> "unable to get regulatory domain info: Device not configured"
> >>
> >> ifconfig starts working again after I reverted the user land backt May
> >> 25th one; kernel don't seem to be a fact here.
> >>
> >> I use "ifconfig wla
starts working again after I reverted the user land backt May
25th one; kernel don't seem to be a fact here.
I use "ifconfig wlan create wlandev ath0 ssid wepmode on wepkey
weptxkey 1 up".
Is something changed in ifconfig?
Do I need to use diff
June 3rd. I had last updated kernel and world on May 25th
> before.
>
> "unable to get regulatory domain info: Device not configured"
>
> ifconfig starts working again after I reverted the user land backt May 25th
> one; kernel don't seem to be a fact here.
backt May 25th
one; kernel don't seem to be a fact here.
I use "ifconfig wlan create wlandev ath0 ssid wepmode on wepkey
weptxkey 1 up".
Is something changed in ifconfig?
Do I need to use different arguments?
Thanks,
Hiro
___
fr
Adrian Chadd wrote:
> Right, you need to create the interface:
>
> ifconfig wlan0 create wlandev iwn0
>
> then run wpa_spuplicant
>
> (or do it all in /etc/rc.conf .. :)
That seems to work. There seems to be something configured wrong for
wpa_supplicant but WLAN does
On 3/1/16, Carsten Kunze wrote:
> Conrad Meyer wrote:
>
>> "[1] iwn0: mem 0xf7b0-0xf7b01fff
>> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
>> is fine.
>>
>> What makes you say it isn't recognized or doesn't work?
>
> ifconfig iwn0 says "interface iwn0 does not e
Conrad Meyer wrote:
> "[1] iwn0: mem 0xf7b0-0xf7b01fff
> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
> is fine.
>
> What makes you say it isn't recognized or doesn't work?
ifconfig iwn0 says "interface iwn0 does not exist". Also starting
wpa_supplicant doesn
shows up in ifconfig -a .
>>
>>
>> -a
>
> Ok, "sysctl -a|grep iwn" gives quite some output.
>
> Actually I tried to start wpa_supplicant, but WLAN didn't react. Then--just
> for testing--I wrote "ifconfig iwn0 up", where ifconfig reported th
Adrian Chadd wrote:
> sysctl net.wlan.devices
>
> iwn0 no longer shows up in ifconfig -a .
>
>
> -a
Ok, "sysctl -a|grep iwn" gives quite some output.
Actually I tried to start wpa_supplicant, but WLAN didn't react. Then--just
for testing--I wrote &
sysctl net.wlan.devices
iwn0 no longer shows up in ifconfig -a .
-a
On 1 March 2016 at 13:42, Conrad Meyer wrote:
> "[1] iwn0: mem 0xf7b0-0xf7b01fff
> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
> is fine.
>
> What makes you say it isn't recognized or doesn't wor
"[1] iwn0: mem 0xf7b0-0xf7b01fff
irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
is fine.
What makes you say it isn't recognized or doesn't work?
On Tue, Mar 1, 2016 at 1:01 PM, Carsten Kunze wrote:
> Conrad Meyer wrote:
>
>> kldload iwn6000fw, iwn6000g2afw, iwn6000g2b
Conrad Meyer wrote:
> kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw.
This or edit loader.conf doesn't help, all these things had already been in the
kernel. dmesg stays the same.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/
kldload iwn6000fw, iwn6000g2afw, iwn6000g2bfw.
On Tue, Mar 1, 2016 at 12:48 PM, Carsten Kunze wrote:
> Larry Rosenman wrote:
>
>> Did you load the iwn firmware?
>
> How do I do this?
>
> I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
> "module iwn already present!" in dmesg...
> ___
On 2016-03-01 14:48, Carsten Kunze wrote:
Larry Rosenman wrote:
Did you load the iwn firmware?
How do I do this?
I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
"module iwn already present!" in dmesg...
___
freebsd-current@freebsd.org
Larry Rosenman wrote:
> Did you load the iwn firmware?
How do I do this?
I put "if_iwn_load="YES"" into /boot/loader.conf, now I get
"module iwn already present!" in dmesg...
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailm
On 2016-03-01 12:23, Carsten Kunze wrote:
Joe Nosay wrote:
Is the card removable? If so, have you tried plugging in one that
would
have the driver already included with the base - so to speak - system?
Have
you tried the card in another computer/laptop?
It is an integrated card. Theoretic
Joe Nosay wrote:
> Is the card removable? If so, have you tried plugging in one that would
> have the driver already included with the base - so to speak - system? Have
> you tried the card in another computer/laptop?
It is an integrated card. Theoretical it is removeable, but this is by design
Is the card removable? If so, have you tried plugging in one that would
have the driver already included with the base - so to speak - system? Have
you tried the card in another computer/laptop?
On Tue, Mar 1, 2016 at 10:47 AM, Carsten Kunze
wrote:
> Hello,
>
> the WLAN hardware o
Hello,
the WLAN hardware of my Dell E6540 (intel 633ANHMW) is not recognized (or at
least does not work).
The only message found in dmesg is:
[1] iwn0: mem 0xf7b0-0xf7b01fff irq 18 at
device 0.0 on pci3
Full dmesg is:
Copyright (c) 2013-2016 The HardenedBSD Project.
[1] Copyright (c
AES-CCM 3:128-bit powersavemode CAM
powersavesleep 100 txpower 13 bmiss 10 scanvalid 60 protmode CTS
ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi wme
roaming MANUAL
groups: wlan
While the 10-STABLE setup was never a pillar of reliability, HEAD seems to
have
Idwer,
can you please subscribe to this bug?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202784
And getting involved with debugging is much appreciated.
--
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
https://lists.free
lengthy, output of 'sh -x /etc/rc.d/netif
> O> > I> restart' when required.
> O> > I>
> O> > I> Note that I'm not subscribed to freebsd-current.
> O> >
> O> > Yes, please provide 'sh -x /etc/rc.d/netif restart'.
> O>
ut of 'sh -x /etc/rc.d/netif
> O> > I> restart' when required.
> O> > I>
> O> > I> Note that I'm not subscribed to freebsd-current.
> O> >
> O> > Yes, please provide 'sh -x /etc/rc.d/netif restart'.
> O> >
> O&g
ut of 'sh -x /etc/rc.d/netif
> O> > I> restart' when required.
> O> > I>
> O> > I> Note that I'm not subscribed to freebsd-current.
> O> >
> O> > Yes, please provide 'sh -x /etc/rc.d/netif restart'.
> O> >
> O&g
2015-08-29 10:02 GMT+02:00 Gleb Smirnoff :
> On Sat, Aug 29, 2015 at 01:19:40AM +0200, Idwer Vollering wrote:
> I> Manually running 'service netif restart' works around this.
> I>
> I> /etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
> I> -p and mergemaster -iF
> I>
> I> I can
I>
O> > I> Note that I'm not subscribed to freebsd-current.
O> >
O> > Yes, please provide 'sh -x /etc/rc.d/netif restart'.
O> >
O> > And please also check the revisions of your files:
O> >
O> > # ident /etc/rc.d/netif /etc/netwo
c.d/netif restart'.
>
> And please also check the revisions of your files:
>
> # ident /etc/rc.d/netif /etc/network.subr
I have faced the same issue today. wlan interface is not brought up at boot,
sh -x /etc/rc.d/netif restart does the trick.
# ident /etc/rc.d/netif /e
On Sat, Aug 29, 2015 at 01:19:40AM +0200, Idwer Vollering wrote:
I> Manually running 'service netif restart' works around this.
I>
I> /etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
I> -p and mergemaster -iF
I>
I> I can provide the, rather lengthy, output of 'sh -x /etc/rc.
2015-08-29 1:19 GMT+02:00 Idwer Vollering :
> Manually running 'service netif restart' works around this.
>
> /etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
> -p and mergemaster -iF
>
> I can provide the, rather lengthy, output of 'sh -x /etc/rc.d/netif
> restart' when requi
Manually running 'service netif restart' works around this.
/etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
-p and mergemaster -iF
I can provide the, rather lengthy, output of 'sh -x /etc/rc.d/netif
restart' when required.
Note that I'm not subscribed to freebsd-current.
Hi Adrian,
Am Mittwoch, 26. November 2014, 09:27:32 schrieb Adrian Chadd:
> Oh! Please file a PR for this.
Done, https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=195433
> This is two problems:
>
> * the NIC isn't being setup fully correctly - I'll see if i have an
> Intel 6200 in my pile-o-ni
Hi!
Oh! Please file a PR for this. This is two problems:
* the NIC isn't being setup fully correctly - I'll see if i have an
Intel 6200 in my pile-o-nics;
* .. and the re-initialise path is slightly broken it seems and it's
panicing. :)
Thanks!
-adrian
On 26 November 2014 at 09:02, Felix Pal
Hi all,
I just bought a Centrino Advanced N-6200 mini-pcie card because it should be
supported by iwn(4) -- unfortunately it leads to a kernel panic the instant I
try to do
# ifconfig wlan0 up
The creation of wlan0 on top of iwn0 works. Here are the (I hope) most
relevant exerpts from core.tx
On 2013/12/20 15:31, Alexey Dokuchaev wrote:
On Fri, Dec 20, 2013 at 01:35:37PM +0800, Kevin Lo wrote:
I'd like to port it after finishing RT5373 driver support. :-)
Nice, looking forward to it. :)
As promised, I have committed support for the RTL8188EUS chipset.
The driver is a work in progr
On 2014/03/10 15:47, Alexey Dokuchaev wrote:
On Mon, Mar 10, 2014 at 03:41:16PM +0800, Kevin Lo wrote:
On 2014/02/10 20:21, Alexey Dokuchaev wrote:
To augment this a bit: I also came across one of these dongles (vendor
0x0bda product 0x8176) that gave me this "timeout waiting for checksum
repor
On Mon, Mar 10, 2014 at 03:41:16PM +0800, Kevin Lo wrote:
> On 2014/02/10 20:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report" message. Retrying didn't help, but
orrectly, while full plug-and-play thing
does it. Any ideas?
We have to reset the bit of the R92C_MCUFWDL associated with checksum
report
before writing firmware. Could you try this patch? Thanks.
Index: sys/dev/usb/wlan/if_urtwn.c
===
On Thu, Mar 06, 2014 at 09:12:36AM +0100, O. Hartmann wrote:
O> > Obviously not. I patched the kernel sources of a box in question and
O> > the kernel has now r262821. The panic is gone, but there is nonetwork
O> > although the interface is up, the firewall is up (IPWF) and even
O> > netstat -rn sh
In message <1611.1394047...@critter.freebsd.dk>, Poul-Henning Kamp writes:
>
>Just tried a current kernel -r 262780 on my laptop.
>
>When wlan0 comes up (if_iwn) it explodes with something about witness
>and rtentry.c, but it clears the screen before I can get a photo...
-r262832 works.
--
Poul-
On Thu, 6 Mar 2014 08:43:07 +0100
"O. Hartmann" wrote:
> On Thu, 6 Mar 2014 08:37:59 +0300
> "Sergey V. Dyatko" wrote:
>
> > В Thu, 6 Mar 2014 12:47:07 +0800
> > 乔楚 пишет:
> >
> > > I have the same panic.
> > > Panic at net use.
> > > ping , svn, etc...
> >
> > It is fixed on r262806
> >
>
On Thu, 6 Mar 2014 08:37:59 +0300
"Sergey V. Dyatko" wrote:
> В Thu, 6 Mar 2014 12:47:07 +0800
> 乔楚 пишет:
>
> > I have the same panic.
> > Panic at net use.
> > ping , svn, etc...
>
> It is fixed on r262806
>
Obviously not. I patched the kernel sources of a box in question and
the kernel h
В Thu, 6 Mar 2014 12:47:07 +0800
乔楚 пишет:
> I have the same panic.
> Panic at net use.
> ping , svn, etc...
It is fixed on r262806
>
> 2014-03-06 4:51 GMT+08:00 Sergey V. Dyatko :
> > В Wed, 5 Mar 2014 21:33:36 +0100
> > "O. Hartmann" пишет:
> >
> >> On Wed, 5 Mar 2014 23:23:24 +0300
> >> "S
I have the same panic.
Panic at net use.
ping , svn, etc...
2014-03-06 4:51 GMT+08:00 Sergey V. Dyatko :
> В Wed, 5 Mar 2014 21:33:36 +0100
> "O. Hartmann" пишет:
>
>> On Wed, 5 Mar 2014 23:23:24 +0300
>> "Sergey V. Dyatko" wrote:
>>
>> > В Wed, 5 Mar 2014 21:15:17 +0100
>> > "O. Hartmann" пише
В Wed, 5 Mar 2014 21:33:36 +0100
"O. Hartmann" пишет:
> On Wed, 5 Mar 2014 23:23:24 +0300
> "Sergey V. Dyatko" wrote:
>
> > В Wed, 5 Mar 2014 21:15:17 +0100
> > "O. Hartmann" пишет:
> >
> > > On Wed, 05 Mar 2014 19:24:20 +
> > > Poul-Henning Kamp wrote:
> > >
> > > >
> > > > Just tried
On Wed, 5 Mar 2014 23:23:24 +0300
"Sergey V. Dyatko" wrote:
> В Wed, 5 Mar 2014 21:15:17 +0100
> "O. Hartmann" пишет:
>
> > On Wed, 05 Mar 2014 19:24:20 +
> > Poul-Henning Kamp wrote:
> >
> > >
> > > Just tried a current kernel -r 262780 on my laptop.
> > >
> > > When wlan0 comes up (if
On 03/05/14 20:24, Poul-Henning Kamp wrote:
Just tried a current kernel -r 262780 on my laptop.
When wlan0 comes up (if_iwn) it explodes with something about witness
and rtentry.c, but it clears the screen before I can get a photo...
Looks trivial to reproduce.
svn r262799, witness disabled
В Wed, 5 Mar 2014 21:15:17 +0100
"O. Hartmann" пишет:
> On Wed, 05 Mar 2014 19:24:20 +
> Poul-Henning Kamp wrote:
>
> >
> > Just tried a current kernel -r 262780 on my laptop.
> >
> > When wlan0 comes up (if_iwn) it explodes with something about
> > witness and rtentry.c, but it clears th
On Wed, 05 Mar 2014 19:24:20 +
Poul-Henning Kamp wrote:
>
> Just tried a current kernel -r 262780 on my laptop.
>
> When wlan0 comes up (if_iwn) it explodes with something about witness
> and rtentry.c, but it clears the screen before I can get a photo...
>
> Looks trivial to reproduce.
>
Just tried a current kernel -r 262780 on my laptop.
When wlan0 comes up (if_iwn) it explodes with something about witness
and rtentry.c, but it clears the screen before I can get a photo...
Looks trivial to reproduce.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org
On Mon, Feb 10, 2014 at 01:25:06PM +0100, Hans Petter Selasky wrote:
> On 02/10/14 13:21, Alexey Dokuchaev wrote:
> >To augment this a bit: I also came across one of these dongles (vendor
> >0x0bda product 0x8176) that gave me this "timeout waiting for checksum
> >report" message. Retrying didn't
On 02/10/14 13:21, Alexey Dokuchaev wrote:
On Tue, Oct 15, 2013 at 11:13:56PM -0700, Rui Paulo wrote:
On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
I too am seeing
urtwn0: timeout waiting for checksum report
Sorry, this is a know problem that I haven't been able to figure out...
I
On Tue, Oct 15, 2013 at 11:13:56PM -0700, Rui Paulo wrote:
> On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
> > I too am seeing
> > urtwn0: timeout waiting for checksum report
>
> Sorry, this is a know problem that I haven't been able to figure out...
> It probably exists in the OpenBSD dri
On Fri, Dec 20, 2013 at 01:35:37PM +0800, Kevin Lo wrote:
> I'd like to port it after finishing RT5373 driver support. :-)
Nice, looking forward to it. :)
> Here's a site you could use for info about your wireless device:
> http://wikidevi.com/wiki/TP-LINK_TL-WN723N_v3
Thank you Kevin.
./danfe
On 2013/12/19 17:51, Alexey Dokuchaev wrote:
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
Your usb wlan dongles use RTL8188EU chip which is currently not
supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is
On Thu, Dec 19, 2013 at 12:33 PM, Thomas Mueller
wrote:
> Better would be if manufacturers' and online vendors' websites would say what
> chipset their Ethernet, Bluetooth adapter, USB wi-fi adapter, etc use.
>
I think manufacturers don't consider this relevant info, they sell
features, not the
> On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
> > Your usb wlan dongles use RTL8188EU chip which is currently not
> > supported by any of drivers.
> I see; I guess I should not have believed when I was told that most likely
> all it would take is id-patch
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
> Your usb wlan dongles use RTL8188EU chip which is currently not
> supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is id-patch urtwn(4). ;-)
Does anyone k
s was clearly bogus (00:00:30:34:43:30); yet I've
created wlan0 just to find out that there is no list scan results, and
wpa_supplicant(8) gives me this in an endless loop (GENERIC kernel, so
I presume all wlan-related stuff should be in place):
Successfully initialized wpa_supplicant
ioctl[
:34:43:30); yet I've
created wlan0 just to find out that there is no list scan results, and
wpa_supplicant(8) gives me this in an endless loop (GENERIC kernel, so
I presume all wlan-related stuff should be in place):
Successfully initialized wpa_supplicant
ioctl[SIOCS80211, op=103, val=0,
On 10/15/13 11:13 PM, Rui Paulo wrote:
On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
I too am seeing
urtwn0: timeout waiting for checksum report
Sorry, this is a know problem that I haven't been able to figure out... It
probably exists in the OpenBSD driver as well. Usually retryi
On 8 Oct 2013, at 10:41, Julian H. Stacey wrote:
> I too am seeing
> urtwn0: timeout waiting for checksum report
Sorry, this is a know problem that I haven't been able to figure out... It
probably exists in the OpenBSD driver as well. Usually retrying works.
--
Rui Paulo
_
Ref.
http://lists.freebsd.org/pipermail/freebsd-current/2013-October/045333.html
I jhs@ wrote
> > > Rui ported the uwrtn stuff, right?
> > It seems others, so I added them:
> Whoops, I missed "Rui" = "paulo" in commit logs. Added to cc. Sorry.
This has header with corrected addresses for
> > Rui ported the uwrtn stuff, right?
>
> It seems others, so I added them:
Whoops, I missed "Rui" = "paulo" in commit logs. Added to cc. Sorry.
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
Reply below not above, like a play script. Indent o
d them:
To: ke...@freebsd.org
cc: dam...@openbsd.org
to ask if they have newer versions code or firmware to test ?
http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_urtwn.c?view=log
] Import Kevin Lo's port of urtwn(4) from OpenBSD. urtwn(4) is a driver for the
] Realtek RTL8188C
iver for a really miniature WLAN USB stick,
& if_urtwn is only in current ?
man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ?
This driver was never merged to FreeBSD 9.
OK, Thanks for confirmation.
Can you use FreeBSD 10 instead?
Yes, easier than building from 9.X
Hi,
Note the noise floor differences.. wonder why that is.
Rui ported the uwrtn stuff, right? He may be able to help. The driver is
recent and its likely there are bugs to shake out.
-adrian
On Oct 8, 2013 2:49 PM, "Julian H. Stacey" wrote:
> > I too am seeing
> > urtwn0: timeout waiting
> I too am seeing
> urtwn0: timeout waiting for checksum report
&
urtwn0: at uhub3, port 3, addr 4 (disconnected)
(BTW there's no external hub, uhub3 must be inside laptop,
& there's no loose connection, laptop was not touched, all work was remote)
PS a typical sample comparison of
current@,
> >>>> It seems I need if_urtwn driver for a really miniature WLAN USB stick,
> >>>> & if_urtwn is only in current ?
> >>>> man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ?
> >>>
> >>> This dr
I just happened to be browsing man urtwn in NetBSD-current (6.99.23), and
Edimax EW-7811Un is listed as supported by this driver.
This strongly suggests it should work for FreeBSD-current (barring bugs).
Tom
___
freebsd-current@freebsd.org ma
On 10/6/13 8:21 AM, Julian H. Stacey wrote:
I wrote Thu, 03 Oct 2013 23:28:43 +0200
Rui Paulo wrote:
On 2 Oct 2013, at 16:57, Julian H. Stacey wrote:
Hi current@,
It seems I need if_urtwn driver for a really miniature WLAN USB stick,
& if_urtwn is only in current ?
man 4 if_urtwn refer
I wrote Thu, 03 Oct 2013 23:28:43 +0200
> Rui Paulo wrote:
> >
> > On 2 Oct 2013, at 16:57, Julian H. Stacey wrote:
> >
> > > Hi current@,
> > > It seems I need if_urtwn driver for a really miniature WLAN USB stick,
> > > & if_urtwn is on
Rui Paulo wrote:
>
> On 2 Oct 2013, at 16:57, Julian H. Stacey wrote:
>
> > Hi current@,
> > It seems I need if_urtwn driver for a really miniature WLAN USB stick,
> > & if_urtwn is only in current ?
> > man 4 if_urtwn refers to ports/net/urtwn-firmware
On 2 Oct 2013, at 16:57, Julian H. Stacey wrote:
> Hi current@,
> It seems I need if_urtwn driver for a really miniature WLAN USB stick,
> & if_urtwn is only in current ?
> man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ?
This driver was never merged t
Hi current@,
It seems I need if_urtwn driver for a really miniature WLAN USB stick,
& if_urtwn is only in current ?
man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ?
It took hours to search this far, is there a quicker way to find
drivers that I should have taken,
Hy,
Any news about the development of this driver, is someone working on it?
Thanks in advance,
Coszmin
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Netgear-WNA1000N-USB-wlan-device-tp4980136p5565210.html
Sent from the freebsd-current mailing list archive at
1 - 100 of 165 matches
Mail list logo
