activating external WlanDongle?

[Alexus]

Hi,

Itried now several hours with every command to activate the external Wlan Dongle with Moodeaudio 9.1.4, but only the internal works. He is recognizing on USB Port that there is a Dongle, but wlan1 is off. I need it because I have no good reception in my music room and the external should work better.


Any Idea?

Alex

[Tim Curtis]

Try turning off the integrated WiFi adapter first (System Config), then shutdown, plug in the USB WiFi adapter and power up.

Just be aware if there is no Linux driver in the kernel for the particular USB WiFi adapter you are trying it won't work and you will have to connect an Ethernet cable in order to be able to access moode and turn back on the integrated WiFi adapter.

[Alexus]

Try turning off the integrated WiFi adapter first (System Config), then shutdown, plug in the USB WiFi adapter and power up.

Just be aware if there is no Linux driver in the kernel for the particular USB WiFi adapter you are trying it won't work and you will have to connect an Ethernet cable in order to be able to access moode and turn back on the integrated WiFi adapter.

Thanks, I tried it, afterwards there was no wifi anymore. If I type iwconfig, I can see under wlan1: IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off

So I think, there must be a driver in the operating system otherwise under wlan1 there is nothing written, but Moodeaudio only wants the internal....

Using Raspberry 3B+

[Tim Curtis]

If there is only one WiFi adapter then it will appear as wlan0. If you are seeing it assigned to wlan1 there is some sort of breakage in the configuration.

[TheOldPresbyope]

Try turning off the integrated WiFi adapter first (System Config), then shutdown, plug in the USB WiFi adapter and power up.

Just be aware if there is no Linux driver in the kernel for the particular USB WiFi adapter you are trying it won't work and you will have to connect an Ethernet cable in order to be able to access moode and turn back on the integrated WiFi adapter.

Thanks, I tried it, afterwards there was no wifi anymore. If I type iwconfig, I can see under wlan1: IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off

So I think, there must be a driver in the operating system otherwise under wlan1 there is nothing written, but Moodeaudio only wants the internal....

Using Raspberry 3B+

Just to confirm to myself that this procedure still works, I repeated it with a Canakit Raspberry Pi WiFi adapter I bought some years ago. I tested with moOde 9.1.4 on a Pi 3B+.

In moOde's Network Config screen, I have the Wireless parameters entered to connect with the Access Point on my LAN. This is working great with the integrated WiFi subsystem on the Pi 3B+.

As Tim described, I turned off the integrated WiFi adapter in moOde's System Config screen, shutdown, plugged in the Canakit adapter, rebooted, and after an appropriate interval, my player is again connected to the Access Point. I checked the MAC address of the live interface to confirm moOde is now using the external adapter.

There are a number of drivers built into the release of Raspberry Pi OS Lite that moOde is built on. I have three different make/model WiFi adapters which Just Work ™ with moOde and one that doesn't. I suppose you have one that doesn't. What is it?

Regards,
Kent

[Alexus]

Try turning off the integrated WiFi adapter first (System Config), then shutdown, plug in the USB WiFi adapter and power up.

Just be aware if there is no Linux driver in the kernel for the particular USB WiFi adapter you are trying it won't work and you will have to connect an Ethernet cable in order to be able to access moode and turn back on the integrated WiFi adapter.

Thanks, I tried it, afterwards there was no wifi anymore. If I type iwconfig, I can see under wlan1: IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off

So I think, there must be a driver in the operating system otherwise under wlan1 there is nothing written, but Moodeaudio only wants the internal....

Using Raspberry 3B+

Just to confirm to myself that this procedure still works, I repeated it with a Canakit Raspberry Pi WiFi adapter I bought some years ago. I tested with moOde 9.1.4 on a Pi 3B+.

In moOde's Network Config screen, I have the Wireless parameters entered to connect with the Access Point on my LAN. This is working great with the integrated WiFi subsystem on the Pi 3B+.

As Tim described, I turned off the integrated WiFi adapter in moOde's System Config screen, shutdown, plugged in the Canakit adapter, rebooted, and after an appropriate interval, my player is again connected to the Access Point. I checked the MAC address of the live interface to confirm moOde is now using the external adapter.

There are a number of drivers built into the release of Raspberry Pi OS Lite that moOde is built on. I have three different make/model WiFi adapters which Just Work ™ with moOde and one that doesn't. I suppose you have one that doesn't. What is it?

Regards,
Kent

[Alexus]

Try turning off the integrated WiFi adapter first (System Config), then shutdown, plug in the USB WiFi adapter and power up.

Just be aware if there is no Linux driver in the kernel for the particular USB WiFi adapter you are trying it won't work and you will have to connect an Ethernet cable in order to be able to access moode and turn back on the integrated WiFi adapter.

Thanks, I tried it, afterwards there was no wifi anymore. If I type iwconfig, I can see under wlan1: IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Power Management:off

So I think, there must be a driver in the operating system otherwise under wlan1 there is nothing written, but Moodeaudio only wants the internal....

Using Raspberry 3B+

Just to confirm to myself that this procedure still works, I repeated it with a Canakit Raspberry Pi WiFi adapter I bought some years ago. I tested with moOde 9.1.4 on a Pi 3B+.

In moOde's Network Config screen, I have the Wireless parameters entered to connect with the Access Point on my LAN. This is working great with the integrated WiFi subsystem on the Pi 3B+.

As Tim described, I turned off the integrated WiFi adapter in moOde's System Config screen, shutdown, plugged in the Canakit adapter, rebooted, and after an appropriate interval, my player is again connected to the Access Point. I checked the MAC address of the live interface to confirm moOde is now using the external adapter.

There are a number of drivers built into the release of Raspberry Pi OS Lite that moOde is built on. I have three different make/model WiFi adapters which Just Work ™ with moOde and one that doesn't. I suppose you have one that doesn't. What is it?

Regards,
Kent

You are right, "This product no longer works with the provided driver/instructions due to a kernel change in Raspberry Pi OS. https://downloads.raspberrypi.org/raspio...020-05-28/, however you won't be able to update that image. We are working on finding a new driver."
it is a:  RTL8188CUS  chipset

Thanks for your reply´s


Tomorrow i get a new one,

greetings

Alex

[Tim Curtis]

Recently I purchased a PIX-LINK 1200M from Aliexpress and it worked ok. The model number is LV-UAC04.

[Alexus]

Recently I purchased a PIX-LINK 1200M from Aliexpress and it worked ok. The model number is LV-UAC04.

Thanks!!

[Falco]

Thanks guys, I'll try this as well. I have a metal case around the RPi however that does not help the WiFi reception. An external dongle should be better.

I have a gembird WiFi dongle with RTL8812BU chipset. It worked without doing anything on my laptop.

In the RPi i had some issues as somehow my usb dac was not recognized when this was connected. But that's solved now so I'll try again...