03-21-2023, 07:07 PM
(03-21-2023, 06:19 PM)psychofaktory Wrote:(03-21-2023, 05:06 PM)TheOldPresbyope Wrote: Hmmm. I don't have one either but I do still have a Pi ZeroW which uses the same Broadcom BCM2835 SoC and ARM1176JZF-S CPU (albeit 1GHz instead of 700MHz).
That's right.
However, the Raspberry Pi 1B uses the LAN9514 chip for its Ethernet connection, while the Pi Zero W uses the Cypress CYW43438 chip for its Wifi connection, which is also used on the Raspberry Pi 3B.
My guess is that there are incompatibilities between the LAN9514 and the multicast packets used with UPnP.
Something seems to have changed here between Raspian Buster and Bullseye.
Could be...but it seems a better audience would be the gurus who hang out on the Raspberry Pi Forum (I'd go there first) or the counterpart github repo (I'd go there only if I had a pretty clear idea of the source of the incompatibilities, but that's just me).
If you had a USB-Ethernet adapter (or USB-WiF adapter for that matter) lying around, you could bypass the Ethernet aspect of the LAN9514 as a test of your hypothesis. For example, I just grabbed an Insignia-branded "USB 2.0 to Ethernet Adapter" out of the pile, rummaged around in the pile some more to find an micro-USB to USB-B pigtail, plugged everything together, and killed the onboard WiFi transceiver. This device contains an ASIX AX88772B Ethernet controller. The Pi ZeroW is now connected to the LAN via Ethernet and is still discoverable as a UPnP renderer.
Too bad I don't have a Pi 1B/B+ in the same pile but I gave all mine to a local school to play with when the Pi 2B series came out.
Regards,
Kent
