bwfm bcm43569

2019-06-24 Thread 3
i know that wifi adapters never worked in obsd(excluding those
adapters for which drivers were written by vendors), but i found one
that shows signs of life in 11n(11ac 2t2r supported by chip). it can
be bought anywhere where there are samsung tv. moreover it even works
in hostap mode(unlike the buggy athn).
but without a ton of bugs not done:
bwfm0: could not read register: TIMEOUT
bwfm0: could not open rx pipe: IN_USE
bwfm0: could not init bus
bwfm0: firmware did not start up
..and sometimes kernel panic on boot, but works would still!
meet https://wikidevi.com/wiki/Samsung_WCH730B
bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11 
Wireless Adapter" rev 2.10/0.01 addr 2
photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg 
it is shown where to solder the wires for wifi. on the right through
two pins(ground is first) is bluetooth, but for obsd this does not
matter(thx theo).  
data sheet for chip: https://www.cypress.com/file/310246/download



Re: bwfm bcm43569

2019-06-24 Thread Brian Brombacher
Provide a dmesg before you rant.

Thanks,
Brian

> On Jun 24, 2019, at 5:06 PM, 3  wrote:
> 
> i know that wifi adapters never worked in obsd(excluding those
> adapters for which drivers were written by vendors), but i found one
> that shows signs of life in 11n(11ac 2t2r supported by chip). it can
> be bought anywhere where there are samsung tv. moreover it even works
> in hostap mode(unlike the buggy athn).
> but without a ton of bugs not done:
> bwfm0: could not read register: TIMEOUT
> bwfm0: could not open rx pipe: IN_USE
> bwfm0: could not init bus
> bwfm0: firmware did not start up
> ..and sometimes kernel panic on boot, but works would still!
> meet https://wikidevi.com/wiki/Samsung_WCH730B
> bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11 
> Wireless Adapter" rev 2.10/0.01 addr 2
> photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg 
> it is shown where to solder the wires for wifi. on the right through
> two pins(ground is first) is bluetooth, but for obsd this does not
> matter(thx theo).  
> data sheet for chip: https://www.cypress.com/file/310246/download
> 



Re: bwfm bcm43569

2019-06-25 Thread 3
> 2019-06-24 23:06 GMT+02:00, 3 :
>> i know that wifi adapters never worked in obsd(excluding those
> I doubt that they never worked. Check this out:
> https://man.openbsd.org/usb#Wireless_network_interfaces
> You can find specific devices under each driver. For example I use an
> Asus USB-N10 nano which works with the urtwn(4) driver

>> adapters for which drivers were written by vendors), but i found one
>> that shows signs of life in 11n(11ac 2t2r supported by chip). it can
>> be bought anywhere where there are samsung tv. moreover it even works
>> in hostap mode(unlike the buggy athn).
>> but without a ton of bugs not done:
>> bwfm0: could not read register: TIMEOUT
>> bwfm0: could not open rx pipe: IN_USE
>> bwfm0: could not init bus
>> bwfm0: firmware did not start up
>> ..and sometimes kernel panic on boot, but works would still!
>> meet https://wikidevi.com/wiki/Samsung_WCH730B
>> bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11
>> Wireless Adapter" rev 2.10/0.01 addr 2
>> photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg
>> it is shown where to solder the wires for wifi. on the right through
>> two pins(ground is first) is bluetooth, but for obsd this does not
>> matter(thx theo).
>> data sheet for chip: https://www.cypress.com/file/310246/download
>>
>>

first, urtwn doesn't support 11n. i have not checked but it is written there.
second, hostap mode is not supported.
third, the only one task that obsd can solve is to be a router.
nothing more but even this task obsd can not solve adequately. and for
this you need wifi support with hostap mode. if you have a device from
the china there is usually a mini-pcie only with usb interface. for
example 
https://aliexpress.com/item/Minisys-NUC-Celeron-J3160-4-4-Intel-i210AT-Nic-X86/32891699351.html
only two drivers fit- athn and bwfm, but i could not get athn to work witn 
TL-WN821N(r3,r5)



Re: bwfm bcm43569

2019-06-25 Thread 3
> Provide a dmesg before you rant.

> Thanks,
> Brian

>> On Jun 24, 2019, at 5:06 PM, 3  wrote:
>> 
>> i know that wifi adapters never worked in obsd(excluding those
>> adapters for which drivers were written by vendors), but i found one
>> that shows signs of life in 11n(11ac 2t2r supported by chip). it can
>> be bought anywhere where there are samsung tv. moreover it even works
>> in hostap mode(unlike the buggy athn).
>> but without a ton of bugs not done:
>> bwfm0: could not read register: TIMEOUT
>> bwfm0: could not open rx pipe: IN_USE
>> bwfm0: could not init bus
>> bwfm0: firmware did not start up
>> ..and sometimes kernel panic on boot, but works would still!
>> meet https://wikidevi.com/wiki/Samsung_WCH730B
>> bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11 
>> Wireless Adapter" rev 2.10/0.01 addr 2
>> photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg 
>> it is shown where to solder the wires for wifi. on the right through
>> two pins(ground is first) is bluetooth, but for obsd this does not
>> matter(thx theo).  
>> data sheet for chip: https://www.cypress.com/file/310246/download
>> 

for what? but as you wish. if you want to see driver's error messages
or kernel panic just say it because they do not always appear. but we
both know it is a waste of time and it will not lead to anything.

OpenBSD 6.5 (BABUT) #6: Sun May 19 18:12:47 MSK 2019
r...@gw.pesec.cf:/usr/src/sys/arch/amd64/compile/BABUT
real mem = 8481652736 (8088MB)
avail mem = 8214913024 (7834MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xabaac000 (49 entries)
bios0: vendor American Megatrends Inc. version "5.11" date 04/13/2018
acpi0 at bios0: rev 2
acpi0: sleep states S0 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT SSDT SSDT UEFI LPIT CSRT
acpi0: wakeup devices SIO1(S0) BRC1(S0) XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) 
PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz, 1600.32 MHz, 06-4c-04
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 80MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz, 1600.00 MHz, 06-4c-04
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz, 1600.01 MHz, 06-4c-04
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU J3160 @ 1.60GHz, 1600.03 MHz, 06-4c-04
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus 4 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 
mwait.1), PSS
acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 
mwait.1), PSS
acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 
mwait.1), PSS
acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58), C1(1000@1 
mwait.1), PSS
acpipwrres0 at acpi0: ID3C, resource for ISP3
acpipwrres1 at acpi0: CLK0, resource for CAMD
acpipwrres2 

Re: bwfm bcm43569

2019-06-25 Thread Patrick Wildt
On Tue, Jun 25, 2019 at 12:06:51AM +0300, 3 wrote:
> i know that wifi adapters never worked in obsd(excluding those
> adapters for which drivers were written by vendors), but i found one
> that shows signs of life in 11n(11ac 2t2r supported by chip). it can
> be bought anywhere where there are samsung tv. moreover it even works
> in hostap mode(unlike the buggy athn).
> but without a ton of bugs not done:
> bwfm0: could not read register: TIMEOUT
> bwfm0: could not open rx pipe: IN_USE
> bwfm0: could not init bus
> bwfm0: firmware did not start up
> .and sometimes kernel panic on boot, but works would still!
> meet https://wikidevi.com/wiki/Samsung_WCH730B
> bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11 
> Wireless Adapter" rev 2.10/0.01 addr 2
> photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg 
> it is shown where to solder the wires for wifi. on the right through
> two pins(ground is first) is bluetooth, but for obsd this does not
> matter(thx theo).  
> data sheet for chip: https://www.cypress.com/file/310246/download

Did you solder that yourself?  As long as nothing has changed, bwfm(4)
on USB worked fine with the one USB one that I had:  The official
raspberry Pi USB WiFi stick that they sold before they put the WiFi
chip onto the board itself.  I wouldn't blame that on the driver.
Did you try the stick with Linux?  If it works with Linux then maybe
it's my fault after all.

Patrick



Re: bwfm bcm43569

2019-06-25 Thread 3
> On Tue, Jun 25, 2019 at 12:06:51AM +0300, 3 wrote:
>> i know that wifi adapters never worked in obsd(excluding those
>> adapters for which drivers were written by vendors), but i found one
>> that shows signs of life in 11n(11ac 2t2r supported by chip). it can
>> be bought anywhere where there are samsung tv. moreover it even works
>> in hostap mode(unlike the buggy athn).
>> but without a ton of bugs not done:
>> bwfm0: could not read register: TIMEOUT
>> bwfm0: could not open rx pipe: IN_USE
>> bwfm0: could not init bus
>> bwfm0: firmware did not start up
>> .and sometimes kernel panic on boot, but works would still!
>> meet https://wikidevi.com/wiki/Samsung_WCH730B
>> bwfm0 at uhub0 port 1 configuration 1 interface 0 "Broadcom BCMUSB 802.11 
>> Wireless Adapter" rev 2.10/0.01 addr 2
>> photo without cover: http://pichost.org/images/2019/06/24/Untitled-138.jpg 
>> it is shown where to solder the wires for wifi. on the right through
>> two pins(ground is first) is bluetooth, but for obsd this does not
>> matter(thx theo).  
>> data sheet for chip: https://www.cypress.com/file/310246/download

> Did you solder that yourself?  As long as nothing has changed, bwfm(4)
> on USB worked fine with the one USB one that I had:  The official
> raspberry Pi USB WiFi stick that they sold before they put the WiFi
> chip onto the board itself.  I wouldn't blame that on the driver.
> Did you try the stick with Linux?  If it works with Linux then maybe
> it's my fault after all.

> Patrick

not me but i asked another man to find for me where the usb pins out.
i can not overpower myself and use monkey style os like a linux :\ so
i have not tested on linux. but if you care i will give you any
information you need



Re: bwfm bcm43569

2019-06-27 Thread Joseph Mayer
On Tuesday, 25 June 2019 15:26, 3  wrote:
> third, the only one task that obsd can solve is to be a router.
> nothing more but even this task obsd can not solve adequately.

Babut,

You are not correct, OpenBSD is a full Unix/BSD implementation and can
do most anything BSD/Unix can.

I guess in the whole domain of general purpose functionality,
concurrent disk/filesystem IO performance would be OpenBSD's humblest
point today (due to not using block device multiqueueing and I get the
impression that the disk/IO subsystem is mostly not parallellized, for
some usecases also the 3GB buffer cap limit matters).

Joseph



Re: bwfm bcm43569

2019-06-28 Thread 3
> Babut,
> You are not correct, OpenBSD is a full Unix/BSD implementation and can
> do most anything BSD/Unix can.

> I guess in the whole domain of general purpose functionality,
> concurrent disk/filesystem IO performance would be OpenBSD's humblest
> point today (due to not using block device multiqueueing and I get the
> impression that the disk/IO subsystem is mostly not parallellized, for
> some usecases also the 3GB buffer cap limit matters).

> Joseph

obsd do not have a reliable file system and nothing is being done in
this direction. the fact that disk operations are slow is not so
important for me(with the advent of ssd, this problem has ceased to be
relevant).
the hardware support is in a terrible state and relative situation is
getting worse(i am not even talking about the drivers but about all
the 802.11 subsystem which still does not know how to 11ac, although
during this time it is outdated. and i suspect theo will cut out the
802.11 subsystem soon because no 802.11- no problem. it is obsd
style).
obsd has never been strong on multitasking, but now they are trying to
make it worse(thank god that ht support still kept). 
these disadvantages narrow the area where you can use obsd. your very
approach to evaluate the completeness of compliance with some
concept(as unix) is flawed. people do not use concepts in everyday
life, they use some opportunities. and it is necessary to adjust the
concept to what is demanded by people and not to limit opportunities
because of the concept. and although theo is wrong, obsd is his
brainchild and he has the right to kill him :\

ps: any fictional concepts is bullshit. there are only practical needs
and common sense



Re: bwfm bcm43569

2019-06-28 Thread Brian Brombacher
You’re always welcome to submit a patch for functionality you want.  It might 
not be accepted but your own use case would be covered.

Statements on the intentions of others, as the way you continue to do, is a 
sign of a troll.  Submit a patch and you’ll be a helpful troll, if such a thing 
exists.

-Brian

On Jun 28, 2019, at 3:53 AM, 3  wrote:

>> Babut,
>> You are not correct, OpenBSD is a full Unix/BSD implementation and can
>> do most anything BSD/Unix can.
> 
>> I guess in the whole domain of general purpose functionality,
>> concurrent disk/filesystem IO performance would be OpenBSD's humblest
>> point today (due to not using block device multiqueueing and I get the
>> impression that the disk/IO subsystem is mostly not parallellized, for
>> some usecases also the 3GB buffer cap limit matters).
> 
>> Joseph
> 
> obsd do not have a reliable file system and nothing is being done in
> this direction. the fact that disk operations are slow is not so
> important for me(with the advent of ssd, this problem has ceased to be
> relevant).
> the hardware support is in a terrible state and relative situation is
> getting worse(i am not even talking about the drivers but about all
> the 802.11 subsystem which still does not know how to 11ac, although
> during this time it is outdated. and i suspect theo will cut out the
> 802.11 subsystem soon because no 802.11- no problem. it is obsd
> style).
> obsd has never been strong on multitasking, but now they are trying to
> make it worse(thank god that ht support still kept). 
> these disadvantages narrow the area where you can use obsd. your very
> approach to evaluate the completeness of compliance with some
> concept(as unix) is flawed. people do not use concepts in everyday
> life, they use some opportunities. and it is necessary to adjust the
> concept to what is demanded by people and not to limit opportunities
> because of the concept. and although theo is wrong, obsd is his
> brainchild and he has the right to kill him :\
> 
> ps: any fictional concepts is bullshit. there are only practical needs
> and common sense
> 



Re: bwfm bcm43569

2019-06-29 Thread Janne Johansson
Den fre 28 juni 2019 kl 06:45 skrev Joseph Mayer <
joseph.ma...@protonmail.com>:

> point today (due to not using block device multiqueueing and I get the
> impression that the disk/IO subsystem is mostly not parallellized, for
> some usecases also the 3GB buffer cap limit matters).
>

That last point is solved in current,
My box now says:

Memory: Real: 361M/15G act/tot Free: 899M Cache: 14G Swap: 0K/81M

and some go even further:
https://twitter.com/mlarkin2012/status/1136821764959350784

-- 
May the most significant bit of your life be positive.