Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Lenovo NotebooksLenovo P, Y and Z series Notebooks
All Forum Topics
Options

37 Posts

02-21-2017

Romania

73 Signins

512 Page Views

  • Posts: 37
  • Registered: ‎02-21-2017
  • Location: Romania
  • Views: 512
  • Message 51 of 59

Re: Lenovo Y50-70 WiGig upgrade

2019-09-04, 15:08 PM

Wait, you have NETGEAR R9000? You know it supports 802.11ad, right?

 

I ended up installing Ubuntu as a standalone PC, yes.

Originally, I wanted to install it as a VM like you, but that didn't work so well.

I installed the ESXi on the PC, created the Ubuntu VM along with Windows VMs, and I've configured a passthrough for the PCI network adapter. The adapter showed in VM, but it couldn't initialise properly. Could be because of a limitation of the motherboard, I don't know.

Then I installed Lubuntu 18.04 on PC with Ubuntu server VM in QEMU/KVM, successfully configured PCI passthru, the adapter showed in VM, but like in ESXi it didn't initialize.

So I moved all my networking in Lubuntu, bare hardware/standalone PC, and kept QEMU/KVM for the rest of my VMs. I even have a Windows gaming VM with a GPU passthru :P.

 

I don't think 10041R will work with QCA9008. Intel uses proprietary protocol.

Reply
Options

11 Posts

10-30-2012

Taiwan,China

14 Signins

140 Page Views

  • Posts: 11
  • Registered: ‎10-30-2012
  • Location: Taiwan,China
  • Views: 140
  • Message 52 of 59

Re: Lenovo Y50-70 WiGig upgrade

2019-09-05, 1:40 AM

Thanks for your detail guidance Chris_DB, it saves me a lot of endless trying.

I didn't have R9000, that's why I want to configure QCA9008 into soft AP mode.

 

When you survey all these wigig cards, have you ran across another wigig cards by Lenovo namely 04x6012

There is a small wilocity wording beside the wigig connector

I couldn't find anymore related details on google.

Reply
Options

37 Posts

02-21-2017

Romania

73 Signins

512 Page Views

  • Posts: 37
  • Registered: ‎02-21-2017
  • Location: Romania
  • Views: 512
  • Message 53 of 59

Re: Lenovo Y50-70 WiGig upgrade

2019-09-05, 14:04 PM

I can't find anything either. I don't think is a 802.11ad card. The WiGig is probably used for docking only, meaning it will work only with Lenovo docking stations. Similary how Intel one does.

Reply
Options

76 Posts

02-14-2017

United States of America

223 Signins

2196 Page Views

  • Posts: 76
  • Registered: ‎02-14-2017
  • Location: United States of America
  • Views: 2196
  • Message 54 of 59

Re: Lenovo Y50-70 WiGig upgrade

2019-10-23, 21:13 PM

@prostitute524 04x6012 is definitile QCA-Wilocity 802.11ac+ad card. While it could be QCA9008, chances are it is something older, thus it is hard to determine whether ASUS X299 antenna will work or not. Please let us know the results if you decide to try it.

Reply
Options

11 Posts

10-30-2012

Taiwan,China

14 Signins

140 Page Views

  • Posts: 11
  • Registered: ‎10-30-2012
  • Location: Taiwan,China
  • Views: 140
  • Message 55 of 59

Re:Lenovo Y50-70 WiGig upgrade

2021-02-17, 1:46 AM

Hi Chris_DB, finally I successfully putting all the parts (QCA9008+ASUS X299 antenna) together and make them recognized under win10 environment.  I am moving to linux environment next using VM first trying to familiarize the hardware/network settings and all sorts of stuff.  Its a big pain for newbie like me. A little bit guidance please regarding how you make sure QCS9008 is initialize properly under linux(Lubuntu)? I googled related information and found ifconfig is the best fit command, let me know if you tried something different ^_^ 

Reply
Options

37 Posts

02-21-2017

Romania

73 Signins

512 Page Views

  • Posts: 37
  • Registered: ‎02-21-2017
  • Location: Romania
  • Views: 512
  • Message 56 of 59

Re:Lenovo Y50-70 WiGig upgrade

2021-02-20, 16:10 PM

I don't think you can use the adapter in a linux VM. It has to be barebone.
My PC that has this adapter runs Proxmox (basically ubuntu with KVM preconfigured for virtualization), and I tried to passthrough the PCI adapter to a OpenWRT VM in the past, but it doesn't go through. I have the adapter configured in Proxmox the way I mentioned in this post.

 

So, first you need barebone linux on the machine where the adapter is installed.

Then, after boot up, check in lspci output if the PCI device shows up:

root@pve:~# lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 0a)

...

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
01:00.0 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)
01:00.1 Ethernet controller: Emulex Corporation OneConnect 10Gb NIC (be3) (rev 01)
04:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
05:00.0 Network controller: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter (rev 02)
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
08:00.0 USB controller: ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller
root@pve:~#

 

Once you found your PCI device, you can check what driver is loaded for this PCI device:

root@pve:~# lspci -vs 05:00.0
05:00.0 Network controller: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter (rev 02)
        Subsystem: Wilocity Ltd. Wil6200 802.11ad Wireless Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 194
        Memory at df200000 (64-bit, non-prefetchable) [size=2M]
        Capabilities: [40] Power Management version 3
        Capabilities: [b0] MSI: Enable+ Count=4/4 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [148] Latency Tolerance Reporting
        Capabilities: [150] L1 PM Substates
        Kernel driver in use: wil6210
        Kernel modules: wil6210

root@pve:~#

 

Then, you can check in dmesg if the driver loaded successfully:

root@pve:~# dmesg | grep 'wil6210'
[    5.563032] wil6210 0000:05:00.0: wil6210 device found [1ae9:0310] (rev 2) bar size 0x200000
[    5.563113] wil6210 0000:05:00.0: enabling device (0000 -> 0002)
[    5.563234] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_pcie_probe: CSR at [mem 0xdf200000-0xdf3fffff 64bit] -> 0x000000005a387180
[    5.563237] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_set_capabilities: Board hardware is Sparrow B0, flash exist
[    5.563237] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_set_capabilities: platform_capa 0x0
[    5.575683] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_refresh_fw_capabilities: keep_radio_on_during_sleep (0)
[    5.575685] wil6210 0000:05:00.0: using dma mask 48
[    5.638910] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:4e:b0:10 RF = 0x0000 (status 0x0000) bband = 0x00000000
[    5.638911] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_get_bl_info: Boot Loader build 255.255.0.6836
[    5.638912] wil6210 0000:05:00.0 (unnamed net_device) (uninitialized): wil_set_oob_mode: oob_mode to 0
[    5.649499] wil6210 0000:05:00.0 wlp5s0: renamed from wlan0
[   11.522542] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_TX_CNT_TRSH = 500 usec
[   11.522543] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_TX_IDL_CNT_TRSH = 13 usec
[   11.522544] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_RX_CNT_TRSH = 500 usec
[   11.522545] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_RX_IDL_CNT_TRSH = 13 usec
[   11.522545] wil6210 0000:05:00.0 wlp5s0: wil_refresh_fw_capabilities: keep_radio_on_during_sleep (0)
[   11.523456] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect: disconnect bssid=(null), reason=2
[   11.523457] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=2
[   11.523463] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect: disconnect bssid=ff:ff:ff:ff:ff:ff, reason=2
[   11.523464] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect_complete: disconnect_complete: bssid=ff:ff:ff:ff:ff:ff, reason=2
[   11.524440] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
[   11.524441] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
[   11.587140] wil6210 0000:05:00.0 wlp5s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:4e:b0:10 RF = 0x0000 (status 0x0000) bband = 0x00000000
[   11.587141] wil6210 0000:05:00.0 wlp5s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
[   11.587141] wil6210 0000:05:00.0 wlp5s0: wil_set_oob_mode: oob_mode to 0
[   11.587144] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
[   11.587144] wil6210 0000:05:00.0 wlp5s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
[   11.646903] wil6210 0000:05:00.0 wlp5s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:4e:b0:10 RF = 0x0000 (status 0x0000) bband = 0x00000000
[   11.646904] wil6210 0000:05:00.0 wlp5s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
[   11.646905] wil6210 0000:05:00.0 wlp5s0: wil_set_oob_mode: oob_mode to 0
[   11.646907] wil6210 0000:05:00.0 wlp5s0: wil_reset: Use firmware + board
[   11.670231] wil6210 0000:05:00.0 wlp5s0: wmi_evt_ready: FW ver. 5.2.0.18(SW 18); MAC dc:ef:ca:4e:b0:10; 0 MID's
[   11.670258] wil6210 0000:05:00.0 wlp5s0: wil_wait_for_fw_ready: FW ready after 8 ms. HW version 0x00000001
[   11.670531] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_TX_CNT_TRSH = 500 usec
[   11.670532] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_TX_IDL_CNT_TRSH = 13 usec
[   11.670532] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_RX_CNT_TRSH = 500 usec
[   11.670533] wil6210 0000:05:00.0 wlp5s0: wil_configure_interrupt_moderation: set ITR_RX_IDL_CNT_TRSH = 13 usec
[   11.670533] wil6210 0000:05:00.0 wlp5s0: wil_refresh_fw_capabilities: keep_radio_on_during_sleep (0)

38 seconds later a client connects to the AP and this is the log that was generated
[   49.905907] wil6210 0000:05:00.0 wlp5s0: wmi_evt_connect: Connect dc:ef:ca:92:ba:27 channel [2] cid 0 aid 0
[   49.906269] wil6210 0000:05:00.0 wlp5s0: wmi_evt_connect: successful connection to CID 0
root@pve:~#

 

If driver loaded successfully, you shoud see this device in ip link output:

root@pve:~# ip link show
5: wlp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DORMANT group default qlen 4000
    link/ether dc:ef:ca:4e:b0:10 brd ff:ff:ff:ff:ff:ff
root@pve:~#

 

Now install required packages:

root@pve:~# apt install wpasupplicant wireless-tools iw isc-dhcp-server

 

Create a file /etc/systemd/network/ad.cfg with this content:

ap_scan=2network={
frequency=60480
ssid="AD"
mode=2
key_mgmt=NONE
}

and start wpa_suplicant using this file
root@pve:~# wpa_supplicant -Dnl80211 -iwlp5s0 -c/etc/systemd/network/ad.cfg

 

Now you should see a wireless network called AD on your Windows machine.

 

If all works well, you can set it up so that it automatically runs wpa_suplicant on boot up by setting up a service.

Create a file at /etc/systemd/network/start-wifi.sh with this content:

#!/bin/bash
while [[ -z $(ip link | grep wlp5s0) ]]; do sleep 1; done
killall wpa_supplicant
sleep 1
wpa_supplicant -Dnl80211 -iwlp5s0 -c/etc/systemd/network/ad.cfg &
sleep 5
echo 1 > /proc/sys/net/ipv4/ip_forward
ip addr add 192.168.2.1/24 dev wlp5s0
iptables -t nat -A POSTROUTING -o -j MASQUERADE
systemctl restart isc-dhcp-server

Make it executable:

root@pve:~# chmod +x /etc/systemd/network/start-wifi.sh

 

Add the wireless interface in file /etc/default/isc-dhcp-server

INTERFACES="wlp5s0"  << change only this line, leave the rest alone

Replace /etc/dhcp/dhcpd.conf content to something like this:

default-lease-time 600;
max-lease-time 7200;

subnet 192.168.2.0 netmask 255.255.255.0 {
    range 192.168.2.100 192.168.2.200;
    option subnet-mask 255.255.255.0;
    option broadcast-address 192.168.2.255;
    option routers 192.168.2.1;
    option domain-name-servers 8.8.8.8;
}

And register the service

root@pve:~# systemctl enable wifi.service

 

Now after reboot, wpa_suplicant will start automatically, running the wireless AP and run DHCP on it for the clients.

 

Reply
Options

11 Posts

10-30-2012

Taiwan,China

14 Signins

140 Page Views

  • Posts: 11
  • Registered: ‎10-30-2012
  • Location: Taiwan,China
  • Views: 140
  • Message 57 of 59

Re:Lenovo Y50-70 WiGig upgrade

2021-02-20, 23:48 PM

Hi Chris_DB, thanks for the detail guidance, really appreciate. Meantime I had also done a little googling and found there are several ways to enable soft ap like wpa_supplicant recommend like yours and another one is hostapd. Have you compare their differences? I found softap created by hostapd can also be visited from window. Please let me know if you have further discovery. Thank you very much.

Reply
Options

11 Posts

10-30-2012

Taiwan,China

14 Signins

140 Page Views

  • Posts: 11
  • Registered: ‎10-30-2012
  • Location: Taiwan,China
  • Views: 140
  • Message 58 of 59

Re:Lenovo Y50-70 WiGig upgrade

2021-02-26, 0:49 AM

Hi Starlight5, finally I got this 04x6012 and figure out what it is. This card has its original name QCA9006NFC which combine AR9462(abgn+ac) and Wil6220(ad). It needs Wil6210 as the active antenna which is different from Wil6310 used by QCA9008. I couldn't get this card working because my soft AP for ad isn't on yet and the ad part of the card could not be recognized correctly under win10 either because of module damage or unusable driver. There is no exclamation mark showing unrecognizable ad devices inside device manager either. The ad active antenna Wil6310 might be using the same protocol to Wil6210 which makes 04X6012 could share X299 antenna but I couldn't confirm yet. 

Reply
Options

76 Posts

02-14-2017

United States of America

223 Signins

2196 Page Views

  • Posts: 76
  • Registered: ‎02-14-2017
  • Location: United States of America
  • Views: 2196
  • Message 59 of 59

Re:Lenovo Y50-70 WiGig upgrade

2021-02-26, 2:03 AM

Hi @**bleep**524, thanks for the info! 

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms