ASUS USB-AC68 wireless adapter / U4 ??

[allie181]

Hi

Q1 - Before I replace my T4 with a U4, can anyone tell me whether the ASUS USB-AC68 wireless adapter https://www.asus.com/au/Networking/USB-AC68/ will work with the U4? (I believe it uses the Realtek RTL8814AU chipset.)

Q2 - I’ve accidentally deleted the recent email from BW containing the offer of a discount on the U4 when returning another PVR. Does anyone have the URL for this offer?

Thanks in advance.

[Grumpy_Geoff]

Here's the offer - https://mailchi.mp/beyonwiz/trade-in-yo ... r-trade-in

[dRdoS7]

Hi,

Hi

Q1 - Before I replace my T4 with a U4, can anyone tell me whether the ASUS USB-AC68 wireless adapter https://www.asus.com/au/Networking/USB-AC68/ will work with the U4? (I believe it uses the Realtek RTL8814AU chipset.)

Thanks in advance.

There are drivers for that chip, but no guarantee it will work for your device. I have an Edimax 7711mac, which has drivers (MT7610U), but it doesn't work for mine.

dRdoS7

[allie181]

Hi,

Hi

Q1 - Before I replace my T4 with a U4, can anyone tell me whether the ASUS USB-AC68 wireless adapter https://www.asus.com/au/Networking/USB-AC68/ will work with the U4? (I believe it uses the Realtek RTL8814AU chipset.)

Thanks in advance.

There are drivers for that chip, but no guarantee it will work for your device. I have an Edimax 7711mac, which has drivers (MT7610U), but it doesn't work for mine.

dRdoS7

Ok, thanks dRdoS7.

[dRdoS7]

Hi,

Before I replace my T4 with a U4, can anyone tell me whether the ASUS USB-AC68 wireless adapter

If you already have the device you can test it in the T4. You'll probably need the latest FW.

dRdoS7

[MrQuade]

If you already have the device you can test it in the T4. You'll probably need the latest FW.

You probably want to have a read of allie181's other thread on this topic.

Besides, the U4 uses a different chipset to the T series and as such all the drivers are different and have their own idiosyncrasies. There isn't a 100% guarantee that devices will behave the same way.

[Grumpy_Geoff]

There's no alternate versions of the Asus USB-AC68 listed on the WikiDevi page, so it should have worked in allie181's T4 - https://wikidevi.com/wiki/ASUS_USB-AC68
(as we know it has in another users' T4).
It appears the driver hasn't changed for close to 2 years.

allie181 -
Does the packaging or adapter give any indication of a version?
If you plug the adapter into your laptop, can you identify the chipset? You may have to go into Device Manager / Network adapters (I'm just guessing).

[dRdoS7]

If you already have the device you can test it in the T4. You'll probably need the latest FW.

You probably want to have a read of allie181's other thread on this topic.

Probably not.

[allie181]

There's no alternate versions of the Asus USB-AC68 listed on the WikiDevi page, so it should have worked in allie181's T4 - https://wikidevi.com/wiki/ASUS_USB-AC68
(as we know it has in another users' T4).
It appears the driver hasn't changed for close to 2 years.

allie181 -
Does the packaging or adapter give any indication of a version?
If you plug the adapter into your laptop, can you identify the chipset? You may have to go into Device Manager / Network adapters (I'm just guessing).

The packaging says:
Model: USB-AC68
H/W Ver: A1
so I'm guessing there is only 1 version of this adapter.

When I plug the adapter into my laptop and go to Device Manager / Network adapters, under driver details it says ... (see attached images below)

I've gone ahead and purchased the U4 so I'll find out in a few days whether it works or not. I'm hoping that maybe it is because the adapter is USB 3.0 that it will work in the USB 3.0 port on the U4. Yes, I realise USB 3.0 is backwards compatible with 2.0, I'm still hoping this may have been the issue with the adapter not working on the T4.

[Grumpy_Geoff]

The packaging says:
Model: USB-AC68
H/W Ver: A1
so I'm guessing there is only 1 version of this adapter.

Yep, I thought so.

When I plug the adapter into my laptop and go to Device Manager / Network adapters, under driver details it says ... (see attached images below)

It looks like the ASUS is using the TP-Link drivers. Never mind though.

I've gone ahead and purchased the U4 so I'll find out in a few days whether it works or not. I'm hoping that maybe it is because the adapter is USB 3.0 that it will work in the USB 3.0 port on the U4. Yes, I realise USB 3.0 is backwards compatible with 2.0, I'm still hoping this may have been the issue with the adapter not working on the T4.

Except bigglesworth on the Whirlpool forum has stated it's been successfully used on a T4 -
https://forums.whirlpool.net.au/thread/ ... #r55311263
https://forums.whirlpool.net.au/thread/ ... #r58578358

[allie181]

I received the U4. Unfortunately the ASUS USB-AC68 wireless adapter is NOT recognised by the U4

[Grumpy_Geoff]

Did you run over a black cat or walk under a ladder?
You need to find a goat to sacrifice, if there isn't one handy then a Collingwood supporter is a usually good alternative that is still acceptable to the gods

I suggest contacting ASUS support to confirm the chipset used in your 'H/W Ver: A1' adapter.
https://www.asus.com/au/support/CallUs
https://www.asus.com/support/Product/Co ... lang=en-au

What firmware is the U4 running - 20190207?
Do all 3 USB ports work (e.g. does your original BW adapter still work, a flash drive)?

[allie181]

Did you run over a black cat or walk under a ladder?
You need to find a goat to sacrifice, if there isn't one handy then a Collingwood supporter is a usually good alternative that is still acceptable to the gods

I suggest contacting ASUS support to confirm the chipset used in your 'H/W Ver: A1' adapter.
https://www.asus.com/au/support/CallUs
https://www.asus.com/support/Product/Co ... lang=en-au

Will do tomorrow.

What firmware is the U4 running - 20190207?
Do all 3 USB ports work (e.g. does your original BW adapter still work, a flash drive)?

Firmware is 20190206. Is this the wrong one?

Yes, the USB ports all work. I'm using my old BW adapter on the U4 for the time being and it is working.

[Grumpy_Geoff]

...

What firmware is the U4 running - 20190207?
Do all 3 USB ports work (e.g. does your original BW adapter still work, a flash drive)?

Firmware is 20190206. Is this the wrong one?
...

There's a small online update available to take the firmware to 20190207, but the RTL8814AU driver was available from 20180417 I believe.

[allie181]

Thanks Geoff. I'll install the update. You never know, it may just work

[allie181]

Did you run over a black cat or walk under a ladder?
You need to find a goat to sacrifice, if there isn't one handy then a Collingwood supporter is a usually good alternative that is still acceptable to the gods

I suggest contacting ASUS support to confirm the chipset used in your 'H/W Ver: A1' adapter.
https://www.asus.com/au/support/CallUs
https://www.asus.com/support/Product/Co ... lang=en-au

Will do tomorrow.

Hi Geoff

ASUS finally got back to me and confirmed that my wireless adapter uses the RTK8814AU chipset.

Is there a specific order for me to turn on the wiz, when to insert the wireless adapter etc? I updated the firmware and restarted, then I turned it off, inserted the wireless adapter and turned the wiz back on. Have I done something wrong?

Thanks.

[Grumpy_Geoff]

ASUS finally got back to me and confirmed that my wireless adapter uses the RTK8814AU chipset.

The RTL8814AU driver is included in the 20190207 firmware (as it was in the 20180417 f/w).

I'm wondering if the Beyonwiz doesn't like swapping wireless adapter types. I'm really just grasping at straws, as I can't think what else could be wrong.

Can you try this first -

• Take a backup
• Perform a factory reset
• Plug the Asus wireless adapter in at the "reset prompt"
• Upon reboot, scan the broadcast services
• You should then be prompted for the network wizard

See how that goes.
If that fails to detect the new adapter, can you try this -

• load 20190207 firmware from USB
• plug the Asus wireless adapter in at the conclusion of the firmware load but before it reboots
• scan the broadcast services
• you should then be prompted for the network wizard

There can't possibly be any leftover crud from the old adapter after a f/w load from USB that may (guessing) have been left behind after a factory reset.

If both fail, then restore your settings.
If one of these succeeds and the adapter is recognised, then you'll probably have to redo your settings and we'll try and work out a way to get your timers back if you don't use IceTV.

We may need to get a hold of some log files to see if the USB adapter is being recognised, perhaps it's not and hence your issues.

[allie181]

Hi Geoff

I went through the 2 step process several times, using different USB ports on the U4. No luck, so I've restored my settings.

How do I go about getting the log files as you've suggested?

Thanks.

[Grumpy_Geoff]

Hmm, that's bad luck.

Leave it with me, I'll knock up a script you can copy to a USB thumb drive to do the job easily.
No guarantees the logs will tell us anything though.

[Grumpy_Geoff]

I've put the below lines into the attached file.

Code: Select all

dmesg > /home/root/logs/dmesg_cmd.txt
cp /var/log/dmesg /home/root/logs/dmesg_log.txt
cp /var/log/messages /home/root/logs/messages_log.txt
echo "done - logs copied to /home/root/logs"
cp /home/root/logs/dmesg_cmd.txt /home/root/logs/dmesg_log.txt /home/root/logs/messages_log.txt /media/usb
echo "done - files copied to USB"

LogCopy.sh.txt

(326 Bytes) Downloaded 72 times

Download the file and copy onto a USB thumb drive and remove the '.txt' extension (thus leaving the file name as 'LogCopy.sh').
Eject the thumb drive and take it to the U4 (but don't plug it in yet).

Plug the Asus USB WiFi adapter in the U4 and reboot it (ensure no other USB storage drives are plugged in to the U4, to make it easier to read the logs, remove the USB tuner and the Beyonwiz WiFi adapter too).
Once live TV has started to display on the U4, plug the thumb drive in to the U4. You can EXIT the popup offering "watch and view movies, and install extensions" if it's offered.
Open File Commander (MENU>>Sources / Files).
Open the USB thumb drive (likely the last entry shown). Locate/select the file 'LogCopy.sh' and press OK on it, and choose '3 Run script'.
You should see some display results, including the two "done" messages. Press OK or EXIT to return back to the FC display.
Press '0' to refresh the display - the three new files should show.
Exit back to live TV. Unmount the thumb drive - MENU>>Plugins>>SimpleUmount (or also as an entry in the same "plugins" column) , select the USB drive (should already be selected), OK. Then remove it.

Attach the three *.txt files in a forum post.

(we may have to modify the script later to add the lsusb command, unless you are able to use the command line on the u4, can you?)

Cheers
Geoff

[allie181]

Attach the three *.txt files in a forum post.

Attached below.

(we may have to modify the script later to add the lsusb command, unless you are able to use the command line on the u4, can you?)

Sorry, I'm not sure how to do that.

Thanks!!

[Grumpy_Geoff]

Attach the three *.txt files in a forum post.

Attached below.

Thanks. I'll have a good look tomorrow, but on a cursory scan it looks like the U4 never saw the USB WiFi adapter (it only saw the Sandisk Cruzer Switch).

[Grumpy_Geoff]

When I boot the U4 with an RTL8812AU chipset USB WiFi adapter connected I get the below in the logs -

Code: Select all

Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8812au

I expected to see a similar entry in your logs (except yours should be for an rtl8814au) but didn't.

Are you using the extension cable and desktop cradle that came with the Asus USB-AC68?
I know you've previously tested the adapter in your laptop, does it also work in the laptop when using the cable and cradle?
Have you tried the USB-AC68 in the U4 without using the cable (and cradle obviously).


Log snippets -
Mine -

Code: Select all

Jan  1 08:00:31 beyonwizu4 user.info kernel: DVB: registering new adapter (beyonwizu4)
Jan  1 08:00:31 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 0 (Si21682)...
Jan  1 08:00:31 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 1 (Si21682)...
Jan  1 08:00:31 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 2 (Si21682)...
Jan  1 08:00:31 beyonwizu4 user.notice kernel: random: crng init done
Jan  1 08:00:31 beyonwizu4 user.info kernel: input: dreambox remote control (native) as /devices/virtual/input/input0
Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8812au
Jan  1 08:00:31 beyonwizu4 user.info kernel: EXT4-fs (mmcblk0p4): re-mounted. Opts: nodelalloc,data=journal
Jan  1 08:00:31 beyonwizu4 user.info kernel: unimac-mdio-0:01: Broadcom BCM7439 (2) PHY revision: 0x10, patch: 1
Jan  1 08:00:31 beyonwizu4 user.info kernel: bcmgenet f0b00000.ethernet: configuring instance for internal PHY
Jan  1 08:00:31 beyonwizu4 user.info kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 08:00:31 beyonwizu4 daemon.info avahi-daemon[686]: Found user 'avahi' (UID 998) and group 'avahi' (GID 998).

Yours -

Code: Select all

Jan  1 10:00:19 beyonwizu4 user.info kernel: DVB: registering new adapter (beyonwizu4)
Jan  1 10:00:19 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 0 (Si21682)...
Jan  1 10:00:19 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 1 (Si21682)...
Jan  1 10:00:19 beyonwizu4 user.info kernel: platform beyonwizu4.0: DVB: registering adapter 0 frontend 2 (Si21682)...
Jan  1 10:00:19 beyonwizu4 user.info kernel: input: dreambox remote control (native) as /devices/virtual/input/input0
Jan  1 10:00:19 beyonwizu4 user.info kernel: EXT4-fs (mmcblk0p4): re-mounted. Opts: nodelalloc,data=journal
Jan  1 10:00:19 beyonwizu4 user.notice kernel: random: crng init done
Jan  1 10:00:19 beyonwizu4 daemon.info avahi-daemon[669]: Found user 'avahi' (UID 999) and group 'avahi' (GID 999).

My entries look a little different because the usual network connection is via ethernet and I had unplugged the ethernet cable for the test with the WiFi adapter.


Your log has four RTL driver entries -

Code: Select all

Jan  1 10:00:19 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8187
Jan  1 10:00:19 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8192cu
Jan  1 10:00:19 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8xxxu
Jan  1 10:00:19 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8150

whereas mine has the fifth additional for the attached adapter -

Code: Select all

Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8187
Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8192cu
Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8xxxu
Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8150
Jan  1 08:00:31 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8812au

[allie181]

Hi Geoff

I’ve tried the adapter on the U4 both with and without the cradle. Currently it is plugged directly into the USB3 at the back of the U4 (ie I’m not using the cradle).

My laptop recognised the adapter both with and without the cradle.

Thanks for your continued help.

[Grumpy_Geoff]

When I boot the U4 with an Edimax RTL8192CU adapter attached, I see the following entries -

Code: Select all

Jan  1 09:59:23 beyonwizu4 user.info kernel: usb 4-1: new high-speed USB device number 2 using ehci-brcm
Jan  1 09:59:23 beyonwizu4 user.info kernel: usb 4-1.4: new high-speed USB device number 3 using ehci-brcm
Jan  1 09:59:23 beyonwizu4 user.info kernel: rtl8192cu: Chip version 0x11
Jan  1 09:59:23 beyonwizu4 user.info kernel: rtl8192cu: Board Type 0
Jan  1 09:59:23 beyonwizu4 user.info kernel: rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
Jan  1 09:59:23 beyonwizu4 user.info kernel: rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin

Plugging in the thumb drive then gives -

Code: Select all

Apr 11 09:39:04 beyonwizu4 user.info kernel: usb 4-1.1: new high-speed USB device number 4 using ehci-brcm
Apr 11 09:39:04 beyonwizu4 user.info kernel: usb-storage 4-1.1:1.0: USB Mass Storage device detected
Apr 11 09:39:04 beyonwizu4 user.info kernel: scsi host2: usb-storage 4-1.1:1.0
Apr 11 09:39:05 beyonwizu4 user.notice kernel: scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer           1.03 PQ: 0 ANSI: 2

When booted with the TP-Link RTL8812AU adapter attached, I see -

Code: Select all

Jan  1 10:37:27 beyonwizu4 user.info kernel: usb 4-1: new high-speed USB device number 2 using ehci-brcm
Jan  1 10:37:27 beyonwizu4 user.info kernel: usb 4-1.4: new high-speed USB device number 3 using ehci-brcm
Jan  1 10:37:27 beyonwizu4 user.warn kernel: 8812au: loading out-of-tree module taints kernel.
Jan  1 10:37:27 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8812au

Plugging in the thumb drive gives same as previous attempt -

Code: Select all

Apr 11 10:13:59 beyonwizu4 user.info kernel: usb 4-1.1: new high-speed USB device number 4 using ehci-brcm
Apr 11 10:14:00 beyonwizu4 user.info kernel: usb-storage 4-1.1:1.0: USB Mass Storage device detected
Apr 11 10:14:00 beyonwizu4 user.info kernel: scsi host2: usb-storage 4-1.1:1.0
Apr 11 10:14:01 beyonwizu4 user.notice kernel: scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer           1.03 PQ: 0 ANSI: 2

There's nothing similar with your logs.

Code: Select all

Jan  1 10:00:19 beyonwizu4 user.info kernel: usb 4-1: new high-speed USB device number 2 using ehci-brcm
Jan  1 10:00:19 beyonwizu4 user.info kernel: usb 3-1: new high-speed USB device number 2 using ehci-brcm

Plugging in your thumb drive -

Code: Select all

Apr 10 23:04:36 beyonwizu4 user.info kernel: usb 4-1.3: new high-speed USB device number 3 using ehci-brcm
Apr 10 23:04:36 beyonwizu4 user.info kernel: usb-storage 4-1.3:1.0: USB Mass Storage device detected
Apr 10 23:04:36 beyonwizu4 user.info kernel: scsi host2: usb-storage 4-1.3:1.0
Apr 10 23:04:37 beyonwizu4 user.notice kernel: scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Switch    1.26 PQ: 0 ANSI: 6

It appears the thumb drive was plugged into the rear upper USB 2.0 port.

_______________________________________________________________________________________________

So my U4 sees -

Code: Select all

usb 4-1: new high-speed USB device number 2 using ehci-brcm
usb 4-1.4: new high-speed USB device number 3 using ehci-brcm (rtl8192cu or rtl8812au adapter, rear lower USB2.0 port)
usb 4-1.1: new high-speed USB device number 4 using ehci-brcm (thumb drive, front port)

(rear upper USB2.0 port is 'usb 4-1.3')

Your USB entries are -

Code: Select all

usb 4-1: new high-speed USB device number 2 using ehci-brcm
usb 3-1: new high-speed USB device number 2 using ehci-brcm

You have bus 4 and bus 3 identified, whereas mine only listed bus 4.
Did you have something plugged into the USB3.0 port (as I think that is assigned bus 3) as well as the USB2.0 port?

Next action:
Let's see if your USB adapter at least registers. Download the attached script and run as per previous version. It includes an lsusb command which will show if the adapter is detected (even if the driver isn't matched).

LogCopy#2.sh

(394 Bytes) Downloaded 54 times

I note that sometimes the driver sometimes fails to load for my Edimax EW-7722UTn (RTL8192CU chipset) adapter -

Code: Select all

Jan  1 16:05:47 beyonwizu4 user.warn kernel: usb 4-1.3: Direct firmware load for rtlwifi/rtl8192cufw_TMSC.bin failed with error -2
Jan  1 16:05:47 beyonwizu4 user.warn kernel: usb 4-1.3: Direct firmware load for rtlwifi/rtl8192cufw.bin failed with error -2
Jan  1 16:05:47 beyonwizu4 user.info kernel: rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
Jan  1 16:05:47 beyonwizu4 user.err kernel: rtlwifi: Selected firmware is not available

[allie181]

Hi Geoff

I've attached the 4 files created when I ran the new script. I followed the instructions as per the previous script, so the only thing plugged into a USB port is the wireless adapter which is plugged into the USB 3.0 port. After the U4 restarted and live tv was showing, I plugged my flash drive into the USB port at the front of the U4.

Not sure if this is relevant, but "simple unmount" doesn't show my flash drive (it didn't last time either) so I don't "unmount" my flash drive, I just unplug it.

[Grumpy_Geoff]

Thanks.

Here's your lsusb output -

Code: Select all

Bus 005 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 004: ID 0781:5572
Bus 001 Device 001: ID 1d6b:0002
Bus 006 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0002
Bus 004 Device 002: ID 1a40:0101
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 002: ID 0b05:1852

The last entry is for the ASUS USB adapter, as far as I know.

Here's my U4's lsusb output with just the USB tuner plugged in -

Code: Select all

root@beyonwizu4:~# lsusb
Bus 005 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0002
Bus 001 Device 001: ID 1d6b:0002
Bus 006 Device 001: ID 1d6b:0001
Bus 004 Device 003: ID 0bda:2838
Bus 004 Device 001: ID 1d6b:0002
Bus 004 Device 002: ID 1a40:0101
Bus 002 Device 001: ID 1d6b:0003
root@beyonwizu4:~#

The Vendor ID '1d6b' entries are from Linux (https://usb-ids.gowdy.us/read/UD/1d6b).
The 0bda:2838 entry is for the Realtek USB tuner I'm using (https://usb-ids.gowdy.us/read/UD/0bda/2838)
The 1a40:0101 entry is for the U4's internal USB hub apparently (https://usb-ids.gowdy.us/read/UD/1a40/0101)

When I insert my RTL8192CU chipset Edimax EW-7722UTn v2 USB adapter, I see an additional entry of -

Code: Select all

Bus 004 Device 004: ID 0bda:8178

The 0bda:8178 entry matches with -
Name: RTL8192CU 802.11n WLAN Adapter
https://usb-ids.gowdy.us/read/UD/0bda/8178

When I insert my TP-Link T4U, I get an additional entry -

Code: Select all

Bus 003 Device 002: ID 2357:010d

That matches to -
Name: Archer T4U v2 [Realtek RTL8812AU]
https://usb-ids.gowdy.us/read/UD/2357/010d


Here is the ASUS listing - https://usb-ids.gowdy.us/read/UD/0b05
The USB-AC68 is listed as being 0b05:1817 - https://usb-ids.gowdy.us/read/UD/0b05/1817
This doesn't match your entry of -
Bus 003 Device 002: ID 0b05:1852
The Vendor ID matches, but not the Product ID.
The WikiDevi page for the USB-AC68 also lists the USB ID being 0b05:1817 - https://wikidevi.com/wiki/ASUS_USB-AC68


So I'm not sure where to progress from here.
We are told the USB-AC68 works in the T4. We know the T4 uses a different architecture than the U4 does - perhaps the 8814AU driver was built from different source, I'm just purely guessing.
Unless peteru can work some magic in getting Vendor ID 0b05 / Product ID 1852 recognised as being a RTL8814AU chipped adapter, I think you're out of luck with this adapter.

[peteru]

There are no further planned updates for the 17.5 series firmware. All effort is now going towards 19.3 series. I'm not sure when 19.3 will be ready for an open beta, but there are no guarantees that the USB device support will end up being any different.

As I mentioned earlier, it looks like allie181 has really bad luck when shopping for USB adapters and keeps on getting variants of devices that are not supported.

[allie181]

...

So I'm not sure where to progress from here.
We are told the USB-AC68 works in the T4. We know the T4 uses a different architecture than the U4 does - perhaps the 8814AU driver was built from different source, I'm just purely guessing.
Unless peteru can work some magic in getting Vendor ID 0b05 / Product ID 1852 recognised as being a RTL8814AU chipped adapter, I think you're out of luck with this adapter.

Thanks for all of your efforts Geoff. I really appreciate it.

There are no further planned updates for the 17.5 series firmware. All effort is now going towards 19.3 series. I'm not sure when 19.3 will be ready for an open beta, but there are no guarantees that the USB device support will end up being any different.

As I mentioned earlier, it looks like allie181 has really bad luck when shopping for USB adapters and keeps on getting variants of devices that are not supported.

Story of my life of late. Now I'm stuck with a $100 adapter that I can't return and don't need / can't use. Oh well, such as life. I guess I'll just hold onto it in the hope that maybe the next software update will support this adapter.

[peteru]

I'm stuck with a $100 adapter that I can't return

Not sure how you went about buying the adapter, but if you made the seller aware that you were buying the adapter for a specific purpose and it does not work for said purpose, then technically you are entitled to a refund under the ACL.

You could try a last ditch effort of forcing a specific driver to associate with the USB device. Something like this (untested):

Code: Select all

modprobe 8814au
echo 0b05 1852 >/sys/bus/usb/drivers/rtl8814au/new_id

[allie181]

I'm stuck with a $100 adapter that I can't return

Not sure how you went about buying the adapter, but if you made the seller aware that you were buying the adapter for a specific purpose and it does not work for said purpose, then technically you are entitled to a refund under the ACL.

You could try a last ditch effort of forcing a specific driver to associate with the USB device. Something like this (untested):

Code: Select all

modprobe 8814au
echo 0b05 1852 >/sys/bus/usb/drivers/rtl8814au/new_id

How do I install this code? (Sorry, I'm a complete newbie when it comes to code)

[peteru]

I don't have the time, but perhaps Geoff will be kind enough to whack it into a script and give you instructions. You would boot without the USB adapter, run the script, then plug in the USB adapter and restart GUI (but not reboot). If you are lucky, the dongle will be recognised. If you are really, really lucky, it will actually work properly.

If this hack works for you, we can explore making a more permanent solution.

[Grumpy_Geoff]

... Not sure if this is relevant, but "simple unmount" doesn't show my flash drive (it didn't last time either) so I don't "unmount" my flash drive, I just unplug it.

For 'SimpleUmount' to detect the removable USB drive, sometimes in the past I've had to toggle the switch 'Show only removable devices' to off/no. That switch is located at the bottom of the SimpleUmount popup window (toggle with LEFT/RIGHT). Give that a try (but just don't choose your hard drive [device /dev/sda1 mounted on /media/hdd] to unmount!).

[Grumpy_Geoff]

Here's the script containing the commands from peteru.
You can put it onto the same flash drive as the other script you've been running.
As per peteru's instructions, run this new script, exit back to live TV, then attach the ASUS WiFi adapter and restart the GUI - MENU>>Power>>Restart GUI (or 5).
Then run the logging script (LogCopy#2.sh) to see if it indicates the driver was loaded.
Then finally give the network wizard a go.

I'm not sure if the write to file /sys/bus/usb/drivers/rtl8814au/new_id will work as I don't have that path to rtl8814au.
If it doesn't work, we can try again with rtl8812au as I think that driver may also work with the rtl8814au chipset.

[allie181]

Here's the script containing the commands from peteru.
You can put it onto the same flash drive as the other script you've been running.
As per peteru's instructions, run this new script, exit back to live TV, then attach the ASUS WiFi adapter and restart the GUI - MENU>>Power>>Restart GUI (or 5).
Then run the logging script (LogCopy#2.sh) to see if it indicates the driver was loaded.
Then finally give the network wizard a go.

I'm not sure if the write to file /sys/bus/usb/drivers/rtl8814au/new_id will work as I don't have that path to rtl8814au.
If it doesn't work, we can try again with rtl8812au as I think that driver may also work with the rtl8814au chipset.

Hi Geoff

No, that didn't work unfortunately. I've attached the log files.

Can we try the other driver you've suggested?

Thanks!

p.s. I used the toggle switch on simple unmount, but it made no difference, it doesn't detect my flash drive.

[Grumpy_Geoff]

p.s. I used the toggle switch on simple unmount, but it made no difference, it doesn't detect my flash drive.

The Cruzer won't be listed by name, just as a device mounted on /media/usb (in this case of being the first attached USB drive).

[Grumpy_Geoff]

No, that didn't work unfortunately. I've attached the log files.

Can we try the other driver you've suggested?

I see some errors listed in the messages log (the same is in the dmesg output):

Code: Select all

Apr 16 13:38:47 beyonwizu4 user.info kernel: usb 3-1: new high-speed USB device number 2 using ehci-brcm
Apr 16 13:39:05 beyonwizu4 user.warn kernel: brcm-waketimer f0417580.waketimer: Using sysfs attributes, consider using 'rtcwake'
Apr 16 13:39:12 beyonwizu4 daemon.err ntpdate[907]: Can't find host pool.ntp.org: Name or service not known (-2)
Apr 16 13:39:12 beyonwizu4 daemon.err ntpdate[907]: no servers can be used, exiting
Apr 16 13:39:25 beyonwizu4 user.info kernel: usb 3-1: USB disconnect, device number 2
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: module init start
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: rtl8814au v4.3.21_17997.20160531
Apr 16 13:39:49 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8814au
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: module init ret=0
Apr 16 13:40:04 beyonwizu4 user.info kernel: usb 3-1: new high-speed USB device number 3 using ehci-brcm
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.read_chip_version ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_default_value ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.intf_chip_configure ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.read_adapter_info ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_power_on ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_power_off ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_xmit_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.free_xmit_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_xmit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.mgnt_xmit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_xmitframe_enqueue ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_recv_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.free_recv_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.inirp_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.inirp_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.dm_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.dm_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_dm_watchdog ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_bwmode_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_channel_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_chnl_bw_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHwRegHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHwRegHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHalDefVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHalDefVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHalODMVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHalODMVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.UpdateRAMaskHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetBeaconRelatedRegistersHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.Add_RateATid ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.fill_h2c_cmd ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.fill_fake_txdesc ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_get_tx_buff_rsvd_page_num ###
Apr 16 13:40:04 beyonwizu4 user.info kernel: usb 3-1: reset high-speed USB device number 3 using ehci-brcm

I don't pretend to know what they mean


I've updated the "modprobe" script to also try with the 8812au identification, so now it'll have both to pick from, but given the above I'd not be hopeful.

modprobe#2.sh

(281 Bytes) Downloaded 47 times

[allie181]

No, that didn't work unfortunately. I've attached the log files.

Can we try the other driver you've suggested?

I see some errors listed in the messages log (the same is in the dmesg output):

Code: Select all

Apr 16 13:38:47 beyonwizu4 user.info kernel: usb 3-1: new high-speed USB device number 2 using ehci-brcm
Apr 16 13:39:05 beyonwizu4 user.warn kernel: brcm-waketimer f0417580.waketimer: Using sysfs attributes, consider using 'rtcwake'
Apr 16 13:39:12 beyonwizu4 daemon.err ntpdate[907]: Can't find host pool.ntp.org: Name or service not known (-2)
Apr 16 13:39:12 beyonwizu4 daemon.err ntpdate[907]: no servers can be used, exiting
Apr 16 13:39:25 beyonwizu4 user.info kernel: usb 3-1: USB disconnect, device number 2
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: module init start
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: rtl8814au v4.3.21_17997.20160531
Apr 16 13:39:49 beyonwizu4 user.info kernel: usbcore: registered new interface driver rtl8814au
Apr 16 13:39:49 beyonwizu4 user.warn kernel: RTL871X: module init ret=0
Apr 16 13:40:04 beyonwizu4 user.info kernel: usb 3-1: new high-speed USB device number 3 using ehci-brcm
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.read_chip_version ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_default_value ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.intf_chip_configure ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.read_adapter_info ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_power_on ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_power_off ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_xmit_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.free_xmit_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_xmit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.mgnt_xmit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_xmitframe_enqueue ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.init_recv_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.free_recv_priv ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.inirp_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.inirp_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.dm_init ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.dm_deinit ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_dm_watchdog ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_bwmode_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_channel_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.set_chnl_bw_handler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHwRegHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHwRegHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHalDefVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHalDefVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.GetHalODMVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetHalODMVarHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.UpdateRAMaskHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.SetBeaconRelatedRegistersHandler ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.Add_RateATid ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.fill_h2c_cmd ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.fill_fake_txdesc ###
Apr 16 13:40:04 beyonwizu4 user.warn kernel: RTL871X: ### rtw_hal_ops_check - Error : Please hook HalFunc.hal_get_tx_buff_rsvd_page_num ###
Apr 16 13:40:04 beyonwizu4 user.info kernel: usb 3-1: reset high-speed USB device number 3 using ehci-brcm

I don't pretend to know what they mean


I've updated the "modprobe" script to also try with the 8812au identification, so now it'll have both to pick from, but given the above I'd not be hopeful.
modprobe#2.sh

Thanks Geoff.

Unfortunately this script didn't work either, so we can officially give up. Thanks for all of your efforts. I really appreciate it.