Beyonwiz EDUP wifi dongle not working in V2

[dangermouse]

I have just purchased brand a new Beyonwiz V2 with a one terabyte disk and an EDUP wifi dongle as a package from from the Beyonwiz web site direct. I ran setup with the machine powered down I plugged the WiFi dongle into usb2 and the disk into usb3 and rebooted. The network setup does not recognize the wifi dongle. At no stage does the blue light on the dongle light up. If I restart the network wizard no menu option appears to select WLAN as described in the setup instructions.
Entering Setup>Network>Network adapter selection>xmit does not result in a screen enabling LAN/WLAN selection as per the setup guide. I have tried all this multiple times. Both usb ports work with the disk. The wifi works in my windows PC. When I plug the wifi dongle into my RaspberryPi the blue light on the dongle flashes and a ”df” command reads the details on the dongle. Running setup I check the firmware which tells me it is all up to date. The LAN connection works OK but I require wifi because my TV has no access to the LAN.
Also
I just tried the Beyonwiz provided wifi dongle in my friend's identical V2 and I get exactly the same result
Can anybody help?

[MrQuade]

Did you do a full restart, or did you just restart the GUI?

I'm not sure if it matters either way, but a full reboot worked make sure.

And have you tried it in the USB3 port instead of the USB2 port? The USB3 port can deliver more power. Mind you, you also don't want to starve the HDD of power either (the speed of USB2 is plenty for recording purposes). If you can power the HDD separately, then you should do so if plugging into the USB2 port.

I've not had any opportunity to test the wifi dongle with the V2, so not sure what is supposed too work or not.

[dangermouse]

Sure as hell the disk will use more power than the dongle but I have just tried (again), powered off, put the wifi into the usb3, pulled the disk out and the same problem occurs. I am presuming powering off will force a hard reboot. I have checked the firmware - 19.3 with date=20191106
I am at a loss

[Grumpy_Geoff]

... but I have just tried (again), powered off, put the wifi into the usb3, pulled the disk out and the same problem occurs. I am presuming powering off will force a hard reboot.

What does "powered off" mean?
Use the MENU Power options.
Rebooting - MENU>>Power>>Reboot, or shutting down to deep standby - MENU>>Power>>Shutdown.

Assuming it's an EDUP EP-AC1619, using the Realtek RTL8811AU chipset. The RTL8812AU driver provides support for it.
What, if anything is shown in file /var/log/messages for the wireless dongle?

[peteru]

Unrelated to your WiFi problem, but still important...

Format the supplied HDD using the V2. Do not leave it at factory default format.

If you do, you may experience issues later.

Doing this will not fix your WiFi issues, but it will prevent you from being very unhappy later.

[dangermouse]

By powering down I mean a shutdown of the V2, turning off the power at the power point. I then switched the power on and 'boot' appeared in the window on the front of the V2 as it came up
You are correct - The model number of the EDUP wifi is EP-AC1619
To peteru - I will format the drive.
I rebooted and looked in /var/log/messages and nothing to do with wifi

[dangermouse]

I forgot to mention - I have attached /var/log/messages in my previous reply

[MrQuade]

I forgot to mention - I have attached /var/log/messages in my previous reply

Attach the whole file if you can. It looks like you have just copied a terminal buffer there. The hardware initialization happens before the start of that log.
Alternatively, unplugging and plugging the USB in should trigger something in the log as well. (seeing the message on boot would be best).

[dangermouse]

I will do as you ask but it is not going to help you much. Every time I reboot the file reverts back to a collection of entries for the 1 Jan with the last entry being for 10:00:26 This is then followed by the entries with a time stamp of the time of the boot. If you look at the file I sent you the entries are for Oct 20 13:58:20 which is when I rebooted. I am obtaining this file by doing cat /var/log/messages and just deleting the 1 Jan messages off the top but I will get back with the whole file in a few minutes

[Grumpy_Geoff]

It will help. The date change is usual for a WIZ that isn't using NTP for it time synching.

[dangermouse]

OK
I did a reboot of the V2. When it came up I pulled the wifi dongle in and out. I then pulled the ethernet in and out. This log looks a bit better. I don't have ftp so I did a cat of the file and copied and pasted into notepad in my windows pc. I then attached it as log2.txt

[Grumpy_Geoff]

I don't have a V2 to compare, but that looks like a sick V2 to me. There's a lot of errors listed.

I think you should flash the firmware and start again.

[MrQuade]

I don't have ftp so I did a cat of the file and copied and pasted into notepad in my windows pc.

Enter ftp://root@beyonwizv2/ into your browser address bar .

[MrQuade]

I don't have a V2 to compare, but that looks like a sick V2 to me. There's a lot of errors listed.

I think you should flash the firmware and start again.

Those kernel warnings seem to be pretty normal when I compare it to my V2's messages file.

I did a reboot of the V2. When it came up I pulled the wifi dongle in and out. I then pulled the ethernet in and out.

I see the disconnection of the WiFi, then the Ethernet.

Code: Select all

Oct 20 15:07:44 beyonwizv2 user.info kernel: ^[[m<6>usb 3-1: USB disconnect, device number 2
Oct 20 15:07:54 beyonwizv2 user.info kernel: usb 3-1: new high-speed USB device number 3 using xhci-hcd
Oct 20 15:07:55 beyonwizv2 user.info kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Oct 20 15:07:55 beyonwizv2 user.info kernel: scsi host2: usb-storage 3-1:1.0
Oct 20 15:07:56 beyonwizv2 user.notice kernel: scsi 2:0:0:0: CD-ROM            Realtek  Driver Storage   1.00 PQ: 0 ANSI: 0 CCS
Oct 20 15:08:04 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Down
Oct 20 15:08:13 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 20 15:08:16 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Down
Oct 20 15:08:18 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 20 15:08:27 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Down
Oct 20 15:08:33 beyonwizv2 user.info kernel: hi_gmac_v200 f9840000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Oct 20 15:09:58 beyonwizv2 auth.info sshd[2244]: Accepted password for root from 192.168.1.34 port 50013 ssh2

It looks like the dongle is detected as USB storage though. When you plug that into your PC, does it add a new drive to your PC containing maybe drivers and a manual or something?

[Grumpy_Geoff]

Try this instead.
Shut down to deep standby. Connect both the ethernet cable, and wireless dongle. Boot the V2.
At a command prompt, enter lsusb and attach the command output here. That'll show if the wireless dongle is correctly detected. Retrieve the /var/log/messages file (use browser FTP as MrQuade suggested) and attach it here.

My earlier post about the sick V2 may be incorrect as I was seeing crap in the messages file that may have come from your errors in your terminal session splattering the log display.

[prl]

The date change is usual for a WIZ that isn't using NTP for it time synching.

The date change is normal on boxes that don't have a front panel clock displayed in shutdown (U/V models), whether it's using NTP or not. It will always start the boot at the epoch date/time, 00:00:00 1 Jan 1970 UTC. It will also try to set the system initially time using NTP, even if NTP is not set to be the box's time source, though that won't succeed if the box can't reach the au.pool.ntp.org NTP server.

That initial time fetch happens only after all the system startup has done and init runs enigma2.sh (at the point where the front panel says the the startup is at 50%).

If that NTP time fetch fails, time won't be set until later when the enigma2 program is running, has tuned to a channel, and fetched the time from that.

Here's the start of the system log on a box that is configured to use NTP (it shows the time as 10:00 because it starts at 00:00 UTC, and I'm in a timezone that's UTC+10):

Code: Select all

root@beyonwizv2:~# head -3 /var/log/messages 
Jan  1 10:00:24 beyonwizv2 syslog.info syslogd started: BusyBox v1.29.2
Jan  1 10:00:24 beyonwizv2 user.notice kernel: klogd started: BusyBox v1.29.2 (2019-05-06 14:54:22 UTC)
Jan  1 10:00:24 beyonwizv2 user.info kernel: log_buf_len individual max cpu contribution: 4096 bytes
root@beyonwizv2:~#

[Grumpy_Geoff]

The date change is usual for a WIZ that isn't using NTP for it time synching.

The date change is normal, whether it's using NTP or not.

I think it would be more correct if I said that for models without a front panel with a clock, i.e. U/V-series, the boot up date will be wrong until the time can be obtained from NTP.

[prl]

The date change is usual for a WIZ that isn't using NTP for it time synching.

The date change is normal, whether it's using NTP or not.

I think it would be more correct if I said that for models without a front panel with a clock, i.e. U/V-series, the boot up date will be wrong until the time can be obtained from NTP.

You're right, but it still has nothing to do with whether the box is configured to use NTP. I'll change the post.

Cheers,
Peter

[dangermouse]

Me again - I appreciate your help
I entered setup>power.shutdown
I left as requested
wifi in usb3
disk in usb2
ethernet cable in place
I rebooted by pressing the button on the front
I did lsusb and ftp the log - It lost it's line feeds when it got into windows
I think I noted in an earlier post when I put the wifi in my raspberrypi the lsusb command actually prints out "Realtech Semiconductor Corp" in one of the entries and the blue light flashes unlike in the V2
V2 example
root@beyonwizv2:~# lsusb
Bus 001 Device 002: ID 05e3:0608
Bus 003 Device 002: ID 0bda:1a2b
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0003
Bus 001 Device 003: ID 0480:0901

[Grumpy_Geoff]

Bus 003 Device 002: ID 0bda:1a2b

Yep, appears to be incorrectly identified -
https://usb-ids.gowdy.us/read/UD/0bda/1a2b

As an alternative, buy a gigabit switch and connect both your V2 and TV to the switch. Get you money back on the wireless dongle (including the cost of its postage back to Beyonwiz).

[MrQuade]

As an alternative, buy a gigabit switch and connect both your V2 and TV to the switch.

Rule 1. If Ethernet is available, use Ethernet!

[dangermouse]

I am sorry -You have lost me. I don't quite understand the problem? The PVR that the V2 is replacing and the TV both have built in wifi and no access to a lan. For the purpose of this testing I have used a spare TV. I must get the WLAN going. Did you say the id was incorrect? Have Beyonwiz sold me a lemon that was never going to work or is it just a matter of sorting out drivers?

Thanks

[MrQuade]

For the purpose of this testing I have used a spare TV. I must get the WLAN going. Did you say the id was incorrect?

No worries, that wasn't apparent from any of your previous messages. All good.

Have Beyonwiz sold me a lemon that was never going to work or is it just a matter of sorting out drivers?

It sounds like it.
Whatever stock of WiFi adaptors they were previously using may have dried up, and they have ordered similar units with the same chipset, but the new units may have some odd id attributes that are causing the V2 to misidentify them.

This is definitely a case for you to get in touch with Beyonwiz to help you out. They'll need to vet whatever WiFi adaptors they are sending out with their V2s now.

[Grumpy_Geoff]

I am sorry -You have lost me. I don't quite understand the problem? The PVR that the V2 is replacing and the TV both have built in wifi and no access to a lan. For the purpose of this testing I have used a spare TV. I must get the WLAN going.

My mind reading skills have failed me - my apologies.

If you don't have ethernet available at the intended location, then the next best thing is using a wireless extender, access point, or router, that can operate in wireless-to-ethernet bridge mode.
For wireless-N only capability, grab a TL-WA801N ($35 MSY) or TL-WA901N ($49).
For wireless-AC, grab a TL-WA1201 if you can get one (CPL Online states in stock, $79).
Set it up in "client" mode, connecting it to your wireless network and connect your Wiz via ethernet to the wireless-to-ethernet bridge.
"In Client mode, the access point connects your wired devices to a wireless network. This mode is suitable when you have a wired device with an Ethernet port and no wireless capability, for example, a smart TV, media player, or game console and you want to connect it to the internet wirelessly."

Did you say the id was incorrect? Have Beyonwiz sold me a lemon that was never going to work or is it just a matter of sorting out drivers?

I don't think there's a Linux driver for the RTL8188GU chipset, assuming the USB IDs are correct.

[peteru]

When I plug the wifi dongle into my RaspberryPi the blue light on the dongle flashes and a ”df” command reads the details on the dongle.

That sounds suss. df is used to examine the amount of free space on a disk, not to talk to network devices. It sounds like you were looking at a storage device, not a network device.

[dangermouse]

A brain failure - I meant "lsusb" command not "df".
I was also confused because lsusb command on the raspberrypi prints the manufacturer name as well as the id
whereas the V2 only prints the id.

[dangermouse]

The CD that came with the dongle has got linux drivers on it. Is it worth trying to install them? Also I have opened a call with Beyonwiz. I will see what happens

[Grumpy_Geoff]

The CD that came with the dongle has got linux drivers on it. Is it worth trying to install them?

I doubt you can. I think the dongle needs to identify itself as USB ID 0bda:a811 to get the RTL8811AU driver loaded.
https://usb-ids.gowdy.us/read/UD/0bda/a811
Unless peteru can do some special voodoo magic to re-assign USB ID 0bda:1a2b to 0bda:a811, then I think you're "Kangaroo Edward".

[peteru]

It's still a weird device. On the assumption that the following is a result of unplugging it and plugging it back 10 seconds later, it's coming up as a storage device (CD-ROM), rather than a network device.

Code: Select all

Oct 20 15:07:44 beyonwizv2 user.info kernel: ^[[m<6>usb 3-1: USB disconnect, device number 2
Oct 20 15:07:54 beyonwizv2 user.info kernel: usb 3-1: new high-speed USB device number 3 using xhci-hcd
Oct 20 15:07:55 beyonwizv2 user.info kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Oct 20 15:07:55 beyonwizv2 user.info kernel: scsi host2: usb-storage 3-1:1.0
Oct 20 15:07:56 beyonwizv2 user.notice kernel: scsi 2:0:0:0: CD-ROM            Realtek  Driver Storage   1.00 PQ: 0 ANSI: 0 CCS

[Grumpy_Geoff]

It's still a weird device. On the assumption that the following is a result of unplugging it and plugging it back 10 seconds later, it's coming up as a storage device (CD-ROM), rather than a network device.

Code: Select all

Oct 20 15:07:44 beyonwizv2 user.info kernel: ^[[m<6>usb 3-1: USB disconnect, device number 2
Oct 20 15:07:54 beyonwizv2 user.info kernel: usb 3-1: new high-speed USB device number 3 using xhci-hcd
Oct 20 15:07:55 beyonwizv2 user.info kernel: usb-storage 3-1:1.0: USB Mass Storage device detected
Oct 20 15:07:55 beyonwizv2 user.info kernel: scsi host2: usb-storage 3-1:1.0
Oct 20 15:07:56 beyonwizv2 user.notice kernel: scsi 2:0:0:0: CD-ROM            Realtek  Driver Storage   1.00 PQ: 0 ANSI: 0 CCS

Yes, and that's what lsusb reports -
Bus 003 Device 002: ID 0bda:1a2b
"RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode)"
https://usb-ids.gowdy.us/read/UD/0bda/1a2b

[peteru]

It's still a weird device. On the assumption that the following is a result of unplugging it and plugging it back 10 seconds later, it's coming up as a storage device (CD-ROM), rather than a network device.

It sounds like getting it to work will be fairly tricky. First step would be to install usbmodeswitch and usbmodeswitch-data and see if the device can be put into network adapter mode. If you get that far, then it's a question of having drivers for it.

This appears very much like the manufacturer that supplies Beyonwiz "upgraded" the model and in the process made it incompatible.

[peteru]

A bit more investigation suggests that maybe running eject on the CD-ROM device could be enough to switch the device from mass storage to network mode. I don't expect that to make networking automagically work, but if it works it would be one step in the right direction.

[dangermouse]

Thanks for your help. It sounds like weird things are happening and this is s is something for Beyonwiz to sort out. I guess what surprises me is that nobody else has reported the same problem. I have a friend with an identical V2 and if he plugs in my wifi dongle he gets exactly the same problem! Is there anyone out there in Beyonwiz land with an EDUP EP-AC1619 wifi dongle that actually works?

[MrQuade]

I guess what surprises me is that nobody else has reported the same problem. I have a friend with an identical V2 and if he plugs in my wifi dongle he gets exactly the same problem! Is there anyone out there in Beyonwiz land with an EDUP EP-AC1619 wifi dongle that actually works?

Someone has to be the first!
As we said, it is probably a new batch of WiFi dongles, and you were just one of the first recipients of the new batch it seems.

[Grumpy_Geoff]

Is there anyone out there in Beyonwiz land with an EDUP EP-AC1619 wifi dongle that actually works?

Yep, Kezza52 had one in use on his V2 and it was detected - here.
Paul_oz63 has had one at times on his U4. Plenty of others too.

What does Windows report for the chipset/driver?

[Paul_oz53]

Is there anyone out there in Beyonwiz land with an EDUP EP-AC1619 wifi dongle that actually works?

Yep, Kezza52 had one in use on his V2 and it was detected - here.
Paul_oz63 has had one at times on his U4. Plenty of others too.

What does Windows report for the chipset/driver?

My EDUP AC1619 is years old and works well with my U4, T4 and PCs. Normally connects at 433 Mb/s.

I swapped to wired ethernet a few years back.

Just plugged it into the U4, rebooted and it is showing as a WLAN 8812AU wireless network interface on 20201011 firmware.

[dangermouse]

Beyonwiz have just confirmed they have a bad batch of dongles. The bad dongles are identified by the words
"Free Driver" printed on the side. See attachment. When I get a good one I will update this forum
Thanks

[dangermouse]

All is now well. I replaced the dongle marked "free driver" with a new one that is not marked "free driver" and it all works though not without some trouble as the auto config wizard did not work and I had to configure the network manually.