Hi *.*,
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
BTW: it is not an issue with the DHCP server. The 2W doesn't even send
DHCP requests.
TIA, Stefan
Hi *.*,
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
BTW: it is not an issue with the DHCP server. The 2W doesn't even send
DHCP requests.
On 06/11/2021 09:29, Stefan Kaintoch wrote:
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
BTW: it is not an issue with the DHCP server. The 2W doesn't even send
DHCP requests.
TIA, Stefan
Sounds unlikely, but MAC address different?
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
Stefan Kaintoch <stefan@ratri.rincewind.kaintoch.de> wrote:
Have you updated the firmware? I think there have been some pin-related changes for the 2W, which may affect the way the wifi is connected. If you're using an old SD card image that may be the problem.
sudo rpi-update
MAC addresses should be different. Two different WLAN chips. But as I
wrote: there are no DHCP requests from W2.
Bye, Stefan
Stefan Kaintoch wrote:
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Has anybody an idea what's the difference? Or how can I investigate why
one has a WLAN connection, and the other has not.
does raspbian bind the WLAN interface to the physical MAC address?
On 06-11-2021 10:29, Stefan Kaintoch wrote:
The Z2W has a slightly different wifi chip, so you need an absolutely up-to-date RaspiOS 32-bit. (Not sure if the driver is in the 64-bit
version yet; that's still in beta.) Both these commands are essential,
in this order:
sudo apt update
sudo apt -y full-upgrade
then shut down and pop the card into the Z2W.
Stefan Kaintoch wrote:
Andy Burns wrote:
does raspbian bind the WLAN interface to the physical MAC address?
I think so, but am not sure, as I'm not sure what your question exactly
means.
some distros (not really talking about PIs) when they first see e.g.
eth0 will check the MAC addr, and then store that association, if you
remove the disk/SD and boot a different computer, they'll see a
different MAC addr and may associate it with e.g. eth1, as a different NIC.
"ip addr" shows the interface wlan0 with a MAC. But the interface is
down.
sounds like MAC address isn't your issue then.
Andy Burns wrote:
does raspbian bind the WLAN interface to the physical MAC address?
I think so, but am not sure, as I'm not sure what your question exactly means.
"ip addr" shows the interface wlan0 with a MAC. But the interface is
down.
In syslog there's a message which says that wlan0 can't get a carrier.
I think that's the root cause. But why can't it get a carrier?
Theo <theom+news@chiark.greenend.org.uk> wrote:
Have you updated the firmware? I think there have been some pin-related
changes for the 2W, which may affect the way the wifi is connected. If
you're using an old SD card image that may be the problem.
sudo rpi-update
should handle that.
Surely the firmware needed for an officially released board is in the
general release software?
Have you updated the firmware? I think there have been some pin-related changes for the 2W, which may affect the way the wifi is connected. If you're using an old SD card image that may be the problem.
sudo rpi-update
should handle that.
On 06/11/2021 11:29, Stefan Kaintoch wrote:
MAC addresses should be different. Two different WLAN chips. But as I
wrote: there are no DHCP requests from W2.
Bye, Stefan
Yes, of course, that's why I thought it unlikely. If it were me, I would try a
completely fresh card with a minimal standard Raspberry Pi OS. I think the wireless /has/ changed, but I would be amazed if the Wi-Fi were non functional.
You might also try reconfiguring the Wi-Fi from the desktop (on a slightly bigger OS).
Be sure your OS and firmware are up-to-date, as others have suggested.
On 06/11/2021 15:23, A. Dumas wrote:
Theo <theom+news@chiark.greenend.org.uk> wrote:
Have you updated the firmware? I think there have been some pin-related >>> changes for the 2W, which may affect the way the wifi is connected. If >>> you're using an old SD card image that may be the problem.
sudo rpi-update
should handle that.
Surely the firmware needed for an officially released board is in the
general release software?
It may well be, but unless you do an image build, it may well not be incorporated into the current kernel.
At one point a kernel upgrade destroyed my wifi - the broadcomm driver
for that kernel release were not supplied with it.
My guess is you have to force a kernel rebuild. https://www.systutorials.com/docs/linux/man/8-update-initramfs/
is probably the tool to use.
David Taylor <david-taylor@blueyonder.co.uk.invalid> wrote:
On 06/11/2021 11:29, Stefan Kaintoch wrote:
MAC addresses should be different. Two different WLAN chips. But as I
wrote: there are no DHCP requests from W2.
Bye, Stefan
Yes, of course, that's why I thought it unlikely. If it were me, I would try a
completely fresh card with a minimal standard Raspberry Pi OS. I think the >> wireless /has/ changed, but I would be amazed if the Wi-Fi were non functional.
You might also try reconfiguring the Wi-Fi from the desktop (on a slightly
bigger OS).
Be sure your OS and firmware are up-to-date, as others have suggested.
The SD was freshly installed (RaspOS from 2021-05-xx), then "apt update;
apt dist-upgrade".
I tried a rpi-update on the Pi zero W. That brought 2 new files in
/boot: bcm2710-rpi-zero-2[-w].dtb.
Unfortunately that didn't make the trick. WLAN still not working.
Bye, Stefan
Stefan Kaintoch wrote:
Andy Burns wrote:
does raspbian bind the WLAN interface to the physical MAC address?
I think so, but am not sure, as I'm not sure what your question exactly means.
some distros (not really talking about PIs) when they first see e.g. eth0 will
check the MAC addr, and then store that association, if you remove the disk/SD
and boot a different computer, they'll see a different MAC addr and may associate it with e.g. eth1, as a different NIC.
On 06/11/2021 15:16, Stefan Kaintoch wrote:
David Taylor <david-taylor@blueyonder.co.uk.invalid> wrote:
On 06/11/2021 11:29, Stefan Kaintoch wrote:
MAC addresses should be different. Two different WLAN chips. But as I
wrote: there are no DHCP requests from W2.
Bye, Stefan
Yes, of course, that's why I thought it unlikely. If it were me, I would try a
completely fresh card with a minimal standard Raspberry Pi OS. I think the >>> wireless /has/ changed, but I would be amazed if the Wi-Fi were non functional.
You might also try reconfiguring the Wi-Fi from the desktop (on a slightly
bigger OS).
Be sure your OS and firmware are up-to-date, as others have suggested.
The SD was freshly installed (RaspOS from 2021-05-xx), then "apt update;
apt dist-upgrade".
I tried a rpi-update on the Pi zero W. That brought 2 new files in
/boot: bcm2710-rpi-zero-2[-w].dtb.
try an apt upgrade now...
You probly need to force a kernel rebuild and new initramfs and install it.
Loaded modules are cfg80211, brcmfmac and brcmutil. MAC addresses
between zero W and zero 2 W differ.
A. Dumas <alexandre@dumas.fr.invalid> wrote:
sudo apt update
sudo apt -y full-upgrade
then shut down and pop the card into the Z2W.
I did this before inserting the card the first time into the Z2W.
On Sat, 6 Nov 2021 18:21:53 +0100, Stefan Kaintoch wrote:
Loaded modules are cfg80211, brcmfmac and brcmutil. MAC addressesI may have missed seeing you mention it, but have you looked in the
between zero W and zero 2 W differ.
system logs to see what, if anything, they show about initialising wifi?
Martin Gregorie <martin@mydomain.invalid> wrote:
On Sat, 6 Nov 2021 18:21:53 +0100, Stefan Kaintoch wrote:
Loaded modules are cfg80211, brcmfmac and brcmutil. MAC addressesI may have missed seeing you mention it, but have you looked in the
between zero W and zero 2 W differ.
system logs to see what, if anything, they show about initialising
wifi?
Yes, I did. Something like "carrier not found".
The Natural Philosopher <tnp@invalid.invalid> wrote:MAC addresses are unique to every single adapter in the world - so
On 06/11/2021 15:16, Stefan Kaintoch wrote:
David Taylor <david-taylor@blueyonder.co.uk.invalid> wrote:
On 06/11/2021 11:29, Stefan Kaintoch wrote:
MAC addresses should be different. Two different WLAN chips. But as I >>>>> wrote: there are no DHCP requests from W2.
Bye, Stefan
Yes, of course, that's why I thought it unlikely. If it were me, I would try a
completely fresh card with a minimal standard Raspberry Pi OS. I think the
wireless /has/ changed, but I would be amazed if the Wi-Fi were non functional.
You might also try reconfiguring the Wi-Fi from the desktop (on a slightly
bigger OS).
Be sure your OS and firmware are up-to-date, as others have suggested.
The SD was freshly installed (RaspOS from 2021-05-xx), then "apt update; >>> apt dist-upgrade".
I tried a rpi-update on the Pi zero W. That brought 2 new files in
/boot: bcm2710-rpi-zero-2[-w].dtb.
try an apt upgrade now...
Already done several times; no changes.
You probly need to force a kernel rebuild and new initramfs and install it.
Why?
Loaded modules are cfg80211, brcmfmac and brcmutil.
MAC addresses between zero W and zero 2 W differ.
h
TIA, Stefan
Do nmap
and wireshark work for wifi connections?
If not, what are their wifi equivalents?
The Natural Philosopher <tnp@invalid.invalid> wrote:
I am merely suggesting that the old kernel may need a rebuild to
incorporate updated drivers.
Almost definitely, yes. But I'm quite sure that no normal user ever needs
to do a kernel rebuild to get wifi working on their Pi. That should be
fixed by regular apt updates.
"Should" doing a lot of work there, obvs.
On 06-11-2021 14:45, Stefan Kaintoch wrote:
A. Dumas <alexandre@dumas.fr.invalid> wrote:Then, like others said, I think the next step is to try a brand new SD
card image of the latest RaspiOS download. I would be very surprised if
that didn't work, or in other words: that would probably mean hardware
error. (Or a very peculiar wifi access point, maybe.)
https://forums.raspberrypi.com
I am merely suggesting that the old kernel may need a rebuild to
incorporate updated drivers.
On Sun, 7 Nov 2021 10:25:20 +0100, Stefan Kaintoch wrote:
Martin Gregorie <martin@mydomain.invalid> wrote:
On Sat, 6 Nov 2021 18:21:53 +0100, Stefan Kaintoch wrote:
Loaded modules are cfg80211, brcmfmac and brcmutil. MAC addressesI may have missed seeing you mention it, but have you looked in the
between zero W and zero 2 W differ.
system logs to see what, if anything, they show about initialising
wifi?
Yes, I did. Something like "carrier not found".
Exactly what the log entry(s) showed is always better than 'something
like', but OK.
So, can other PCs, etc. connect to your wifi endpoint?
Hi *.*,
There's a RPi zero w (1W) and a RPi zero 2w (2W).
Both can boot from the same (not a clone, physically the identical)
SD-card. But (there always is a but) the 1W has WLAN, the 2W doesn't
have.
Finally I found a solution for that issue.
pi@raspberrypi:~ $ sudo rfkill unblock wifi
Andy Burns <usenet@andyburns.uk> wrote:
Stefan Kaintoch wrote:
Finally I found a solution for that issue.
pi@raspberrypi:~ $ sudo rfkill unblock wifi
country code set?
No. Never did it on any of my machines.
Why is it necessary?
Stefan Kaintoch wrote:
Finally I found a solution for that issue.
pi@raspberrypi:~ $ sudo rfkill unblock wifi
country code set?
Andy Burns wrote:
country code set?
No. Never did it on any of my machines.
Why is it necessary?
No. Never did it on any of my machines.
Why is it necessary?
On 07/11/2021 17:01, Stefan Kaintoch wrote:
No. Never did it on any of my machines.
Why is it necessary?
It could be required to make sure you never radiate RF on channels that
are illegal in your country and/or at higher power than is allowed in
your country.
For instance in the US 2.4GHz WiFi channels 12, 13 & 14 are not allowed.
Stefan Kaintoch wrote:
Andy Burns wrote:
country code set?
No. Never did it on any of my machines.
Why is it necessary?
so it knows what powers/frequencies to allow various radios to use.
Was your rf "unkill" a one-shot deal, or needed after each boot?
On Sun, 7 Nov 2021 17:13:38 +0000
Brian Gregory <void-invalid-dead-dontuse@email.invalid> wrote:
On 07/11/2021 17:01, Stefan Kaintoch wrote:
No. Never did it on any of my machines.
Why is it necessary?
It could be required to make sure you never radiate RF on channels that
are illegal in your country and/or at higher power than is allowed in
your country.
For instance in the US 2.4GHz WiFi channels 12, 13 & 14 are not allowed.
Always struck me as being a bit daft having disallowed channels. I think the crims might look to see if there was something 'interesting' there.
USA reserved a bit of te band for something else.
https://docs.fcc.gov/public/attachments/FCC-16-181A1.pdf
which is a TLDR for me.
On Mon, 8 Nov 2021 11:36:09 +0000, The Natural Philosopher wrote:
USA reserved a bit of te band for something else.
https://docs.fcc.gov/public/attachments/FCC-16-181A1.pdf
which is a TLDR for me.
Wikipdia summarises it as 'Weather radar an Military'.
Presumably weather radar was there before the 2.4 GHz band WiFi was
allocated to WiFi since IIRC you need high RF frequencies to 'see' small raindrops. Presumably 'prior occupancy' also applies to the military.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 37:33:22 |
| Calls: | 7,932 |
| Calls today: | 2 |
| Files: | 12,998 |
| Messages: | 5,805,631 |