NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Raspberry Pi Zero W almost useless





El 9/2/24 a las 1:41, Nat Sloss escribió:
On Fri, 9 Feb 2024 06:05:46 Ramiro Aceves wrote:
El 8/2/24 a las 16:48, Nat Sloss escribió:
Hi,

There's a little more required to add support for the FTV variant judging
by changes made to openbsd's if_urtwn.c.

There's new firware that needs to be uploaded to the device.  And new
power on and rssi functions (It seems judging by the changes they've
made it some what is similar to the 8188EUS).

I'm going to see if I can get one of these adaptors on ebay.

I't will be awhile though before I try to get it working.

This is best done on the new wifi stack, so I doubt it will get
backported to -10.

In the meantime if you search for an 8192eu variant that will work with
-10 and -9.

Best regards,

Nat

Hello Nat,

Thanks for your great explanation, I understand. I then abandon the
tests with the 8188FTV and wait for your improvements. They will be
appreciated. I cannot fix anything, the driver world seems to be a hell!
:-)

I have just received today from Amazon a TL-WN725N USB WIFI adaptor and
it just work in the raspberry Pi Zero W:

[     1.710793] urtwn0 at uhub0 port 1
[     1.710793] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev
2.00/0.00, addr 2
[     1.770890] urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R, address
e4:fa:c4:52:ac:4c
[     1.770890] urtwn0: 1 rx pipe, 2 tx pipes



netbsd-raspa# ifconfig
urtwn0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ssid MiFibra-3422 nwkey 65536:"",0xc81111000336c6e2b40b047cd2f5ef44,"",""
	powersave off
	bssid 60:8d:26:32:34:24 chan 1
	address: e4:fa:c4:52:ac:4c
	media: IEEE802.11 autoselect (OFDM54 mode 11g)
	status: active
	inet6 fe80::e6fa:c4ff:fe52:ac4c%urtwn0/64 flags 0 scopeid 0x1
	inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0
lo0: flags=0x8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33176
	status: active
	inet6 ::1/128 flags 0x20<NODAD>
	inet6 fe80::1%lo0/64 flags 0 scopeid 0x2
	inet 127.0.0.1/8 flags 0
bwfm0: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	ssid "" nwkey 65536:"","","",""
	powersave off
	address: b8:27:eb:ed:85:47
	media: IEEE802.11 autoselect
	status: no network
netbsd-raspa#

I have also the same problem that I had with the chineese 8188FTV,  as
soon I connect it to the raspberry pi it reboots inmediately. In the
next reboot it works fine. It occurs the same in another Zero W that I
own  with Raspbian and a different power supply. So I doubt that the
culprit is the power supply. The Zero W seems to be a very flaky device
in terms of power supply.

A powered hub should fix that, when a device is plugged directly into the
raspberry pis usb (IIRC only 300mA is available) it can cause reboots.


Oh yes, that would be a right technical fix for the problem but it's a bit of an aberration in terms of cost and size to use a powered HUB with its own power supply to fix a little thing like the ZeroW, you know.... ;-)



I am going to test it during several days to see if it works better than
the flaky bwfm driver for the built in WIFI.

I do not know if I have to  disable the bwfm driver to avoid any
interaction or I can leave it as is.

You shouldn't have to disable bwfm(4) just dont bring up it's interface.

Thanks, I will let it as is now.
Many thanks for all, I'm learning a lot of things along the way.
Regards.
Ramiro.




Thanks so much.
Ramiro.

Best regards,

Nat


Home | Main Index | Thread Index | Old Index