Dynamode WL-700N-RXS wireless USB adapter - Bus 001 Device 004:ID 148f:7601 Ralink Technology, Corp. - installation in Ubuntu 14.04.1 LTS

Asked by Richard Smith

Hi,

I have just bought a Dynamode WL-700N-RXS USB wifi adapter and have tried to install it on Xubuntu 14.04.

I couldn't figure out how to install the Linux driver so I tried installing the windows driver using Ndiswrapper.

I first checked the adapter was working on a Windows pc using the windows driver supplied on the CD.

I then copied the .inf and .sys files to the Xubuntu pc.

I then installed the driver with Ndiswrapper.

I loaded the driver module using
sudo depmod -a
sudo modprobe ndiswrapper

When I checked the driver with
ip addr
iwconfig

I found that the driver had not been loaded.

The documentaion says

'Your wireless card should appear with an interface name of wlan0. If it doesn't appear here, then the driver is not working properly'.

Obviously the driver is not working, could you help me find out where I have gone wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
Richard Smith
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
Manfred Hampl (m-hampl) said :
#1

please plug in the adapter and provide the output of the following terminal commands

uname -a
lsb_release -a
lsusb

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#2

Also what is the output of:

sudo lshw -C network

Is there no native driver for the wireless chip?

Revision history for this message
Richard Smith (richardasmith) said :
#3

Hi

Here are the outputs requested

everyone@black-desktop:~$sudo lshw -C network
[sudo] password foreveryone:
  *-network
       description:Ethernet interface
       product:AR8131 Gigabit Ethernet
       vendor:Qualcomm Atheros
       physical id:0
       bus info:pci@0000:01:00.0
       logical name:eth0
       version: c0
       serial:14:da:e9:6c:4a:cc
       size:1Gbit/s
       capacity:1Gbit/s
       width: 64bits
       clock: 33MHz
       capabilities:pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=atl1cdriverversion=1.0.1.1-NAPI duplex=full ip=192.168.0.5 latency=0link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources:irq:44 memory:febc0000-febfffff ioport:ec00(size=128)

everyone@black-desktop:~$uname -a
Linux black-desktop3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 i686i686 i686 GNU/Linux

everyone@black-desktop:~$lsb_release -a
No LSB modules areavailable.
DistributorID: Ubuntu
Description: Ubuntu14.04.1 LTS
Release: 14.04
Codename: trusty

everyone@black-desktop:~$lsusb
Bus 001 Device 003:ID 18e3:9106 Fitipower Integrated Technology Inc
Bus 001 Device 004:ID 148f:7601 Ralink Technology, Corp.
Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002:ID 1267:0210 Logic3 / SpectraVideo plc LG Optical Mouse 3D-310
Bus 002 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
everyone@black-desktop:~$

Regards.

-----Original Message-----
From: Manfred Hampl <email address hidden>
To: <email address hidden>
Sent: Sun, 12 Oct 2014 9:56
Subject: Re: [Question #255620]: Dynamode wireless USB adapter installation

Your question #255620 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/255620

    Status: Open => Needs information

Manfred Hampl requested more information:
please plug in the adapter and provide the output of the following
terminal commands

uname -a
lsb_release -a
lsusb

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/255620

You received this question notification because you asked the question.

Revision history for this message
Richard Smith (richardasmith) said :
#4

Hi

Here is the output requested

everyone@black-desktop:~$sudo lshw -C network
[sudo] password foreveryone:
  *-network
       description:Ethernet interface
       product:AR8131 Gigabit Ethernet
       vendor:Qualcomm Atheros
       physical id:0
       bus info:pci@0000:01:00.0
       logical name:eth0
       version: c0
       serial:14:da:e9:6c:4a:cc
       size:1Gbit/s
       capacity:1Gbit/s
       width: 64bits
       clock: 33MHz
       capabilities:pm msi pciexpress vpd bus_master cap_list ethernet physical tp 10bt10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
      configuration: autonegotiation=on broadcast=yes driver=atl1cdriverversion=1.0.1.1-NAPI duplex=full ip=192.168.0.5 latency=0link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources:irq:44 memory:febc0000-febfffff ioport:ec00(size=128)

everyone@black-desktop:~$uname -a
Linux black-desktop3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:30:01 UTC 2014 i686i686 i686 GNU/Linux

everyone@black-desktop:~$lsb_release -a
No LSB modules areavailable.
DistributorID: Ubuntu
Description: Ubuntu14.04.1 LTS
Release: 14.04
Codename: trusty

everyone@black-desktop:~$lsusb
Bus 001 Device 003:ID 18e3:9106 Fitipower Integrated Technology Inc
Bus 001 Device 004:ID 148f:7601 Ralink Technology, Corp.
Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002:ID 1267:0210 Logic3 / SpectraVideo plc LG Optical Mouse 3D-310
Bus 002 Device 001:ID 1d6b:0001 Linux Foundation 1.1 root hub
everyone@black-desktop:~$

Regards

-----Original Message-----
From: actionparsnip <email address hidden>
To: <email address hidden>
Sent: Sun, 12 Oct 2014 10:12
Subject: Re: [Question #255620]: Dynamode wireless USB adapter installation

Your question #255620 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/255620

actionparsnip requested more information:
Also what is the output of:

sudo lshw -C network

Is there no native driver for the wireless chip?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/255620

You received this question notification because you asked the question.

Revision history for this message
Richard Smith (richardasmith) said :
#5

Hi,

The device driver name is RT2870.

I'm not sure if there is a native driver.

Regards.

-----Original Message-----
From: actionparsnip <email address hidden>
To: <email address hidden>
Sent: Sun, 12 Oct 2014 10:12
Subject: Re: [Question #255620]: Dynamode wireless USB adapter installation

Your question #255620 on Ubuntu changed:
https://answers.launchpad.net/ubuntu/+question/255620

actionparsnip requested more information:
Also what is the output of:

sudo lshw -C network

Is there no native driver for the wireless chip?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+question/255620

You received this question notification because you asked the question.

Revision history for this message
michael (yellupcm-gmail) said :
#6

Richard
In reading about your problem, I found a site that may help.

http://www.raspberrypi.org/forums/viewtopic.php?t=49864

Quote from site.

When I brought my Dynamode dongle I THOUGHT i was going to receive the 5370, however at some point the manufacturer changed the chip-set so my dongle shows up as

Bus 001 Device 005: ID 148f:7601 Ralink Technology, Corp

unfortunately, this device doesn't appear to work natively.

Revision history for this message
Manfred Hampl (m-hampl) said :
#7

There was a similar question https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/251824 with a link to instructions in http://askubuntu.com/questions/457061/ralink-148f7601-wifi-adaptor-installation
(Please note that you should use "sudo command" where the instruction says "su -c 'command')

Revision history for this message
Manfred Hampl (m-hampl) said :
#8
Revision history for this message
Mark Rijckenberg (markrijckenberg) said :
#9
Revision history for this message
Richard Smith (richardasmith) said :
#10

Hi

I am afraid I am getting out of my depth here when I looked at the possible solutions you suggest.

I would still like to pursue the Ndiswrapper line as I feel I am close to getting the wifi working that way.

I know this may not be the most elegant solution but it would get the wifi working until a native driver appears.

So to recap where I am up to:

lsusb gives
Bus 001 Device 003: ID 148f:7601 Ralink Technology, Corp.

ndiswrapper -l gives
rt2870: driver installed
device (148f:7601) present

I then come to load the driver using
sudo depmod -a
which responds with nothing

and
sudo modprobe ndiswrapper
which responds with nothing

At this point I was expecting the wifi to fire up and I would then be home and dry.

Does anyone know why the driver didn't load?

Regards, Richard.

Revision history for this message
Manfred Hampl (m-hampl) said :
#11

Ubuntu as all Unix/Linux variants acts mainly with a "no news is good news" strategy. So if you execute a command and you do not get any output, that usually means that the command was successfully executed.

"sudo modprobe ndiswrapper" giving no output most probably indicates that the ndiswrapper module has been successfully loaded. You can check with the command "lsmod | grep ndis". This, however, does not provide

If you have changed something related to the windows driver for that WLAN card, you might try unloading and reloading the ndiswrapper module with the commands

sudo modprobe -r ndiswrapper
sudo modprobe ndiswrapper

does the terminal command
ndiswrapper -l
list your device?

I assume you have read https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper

If you cannot get the device running with ndiswrapper, I recommend using the instructions from question 251824 to compile a native driver.

Revision history for this message
Richard Smith (richardasmith) said :
#12

Hi

I removed and re-installed ndiswrapper as you suggested.

Ndiswrapper -l shows the driver is installed and the device is present.

When I re-booted I noticed some messages relating to nsdiswrapper briefly on the screen.

I looked in the syslog file and found references to nsdiswrapper as follows.

Oct 14 20:41:43 silver-desktop kernel: [ 20.159237] ndiswrapper: module verification failed: signature and/or required key missing - tainting kernel
Oct 14 20:41:43 silver-desktop kernel: [ 20.159276] Disabling lock debugging due to kernel taint
Oct 14 20:41:43 silver-desktop kernel: [ 20.269205] [drm] initialized overlay support
Oct 14 20:41:43 silver-desktop kernel: [ 20.284445] ndiswrapper version 1.59 loaded (smp=yes, preempt=no)
Oct 14 20:41:43 silver-desktop kernel: [ 20.353431] ip6_tables: (C) 2000-2006 Netfilter Core Team
Oct 14 20:41:43 silver-desktop kernel: [ 21.106590] fbcon: inteldrmfb (fb0) is primary device
Oct 14 20:41:43 silver-desktop kernel: [ 21.317394] Console: switching to colour frame buffer device 180x56
Oct 14 20:41:43 silver-desktop kernel: [ 21.324038] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Oct 14 20:41:43 silver-desktop kernel: [ 21.324040] i915 0000:00:02.0: registered panic notifier
Oct 14 20:41:43 silver-desktop kernel: [ 21.468898] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Oct 14 20:41:43 silver-desktop kernel: [ 22.004229] usb 1-6: reset high-speed USB device number 3 using ehci-pci
Oct 14 20:41:43 silver-desktop kernel: [ 22.294635] Bluetooth: Core ver 2.17
Oct 14 20:41:43 silver-desktop kernel: [ 22.301977] NET: Registered protocol family 31
Oct 14 20:41:43 silver-desktop kernel: [ 22.301987] Bluetooth: HCI device and connection manager initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.302008] Bluetooth: HCI socket layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.302013] Bluetooth: L2CAP socket layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.302038] Bluetooth: SCO socket layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.395447] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 14 20:41:43 silver-desktop kernel: [ 22.395455] Bluetooth: BNEP filters: protocol multicast
Oct 14 20:41:43 silver-desktop kernel: [ 22.395476] Bluetooth: BNEP socket layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.458065] Bluetooth: RFCOMM TTY layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.458176] Bluetooth: RFCOMM socket layer initialized
Oct 14 20:41:43 silver-desktop kernel: [ 22.458201] Bluetooth: RFCOMM ver 1.11
Oct 14 20:41:43 silver-desktop rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 14 20:41:43 silver-desktop kernel: [ 22.784487] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'ExEventObjectType'
Oct 14 20:41:43 silver-desktop kernel: [ 22.784652] ndiswrapper (import:232): unknown symbol: ntoskrnl.exe:'MmGetSystemRoutineAddress'
Oct 14 20:41:43 silver-desktop kernel: [ 22.785060] ndiswrapper (load_sys_files:200): couldn't prepare driver 'rt2870'
Oct 14 20:41:43 silver-desktop loadndisdriver: loadndisdriver: load_driver(364): couldn't load driver rt2870
Oct 14 20:41:43 silver-desktop kernel: [ 22.813065] ndiswrapper (load_wrap_driver:103): couldn't load driver rt2870; check system log for messages from 'loadndisdriver'
Oct 14 20:41:43 silver-desktop kernel: [ 22.820133] usbcore: registered new interface driver ndiswrapper

Does this shed any light on the problem?

Regards.

Revision history for this message
Manfred Hampl (m-hampl) said :
#13

It seems that something in the ndiswrapper setup for your device is not yet correct. There are several possible causes, among others wrong versions of the Windows driver (sometimes the Windows 2000 driver works and the Vista driver doesn't, or the wrong architecture 32/64 bit, etc.).

I always had success in getting a native driver running, so I do not have any experience with ndiswrapper myself.

I can only recommend that you try googling for possible solutions of your ndiswrapper problem, or that you try compiling the native driver as shown in the question document referred by Mark.

Revision history for this message
Richard Smith (richardasmith) said :
#14

Hi

You will be glad to know that I have abandoned my attempt to get the wifi working using ndiswrapper.

I eventually managed to find and decipher the instructions you refer to above.

A few points to mention that may help others:

It would have been a lot easier if you had just sent me the relevant instructions written in a clearer to follow form.

I read somewhere that the next time a new kernel arrives because of a software update, I will have to go through this procedure again because the new kernel may not contain the RT2780 driver, is that right?

Will future software update kernels eventually contain the RT2870 driver?

Thank you very much for your help Mark.

Regards, Richard.

Revision history for this message
Manfred Hampl (m-hampl) said :
#15

I haven't tried that myself, but I assume after each new kernel installation the execution of

cd DPO_MT7601U_LinuxSTA_3.0.0.4_20130913
make install

should be sufficient (no new download, patching or compiling required).

Revision history for this message
Manfred Hampl (m-hampl) said :
#16

Oops, must of course be

cd DPO_MT7601U_LinuxSTA_3.0.0.4_20130913
sudo make install

or you will hit access restrictions.

Revision history for this message
Richard Smith (richardasmith) said :
#17

Hi,

When I reboot, I have to go to the directory

/lib/modules/3.13.0-37-generic/kernel/drivers/net/wireless

Then run the command

 sudo /sbin/insmod mt7601Usta.ko

The wireless then works.

To make this permanent I go to the directory

DPO_MT7601U_LinuxSTA_3.0.0.4_20130913

Then I run the command

sudo make install

This generates the output

richard@silver-desktop:~/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913$ sudo make install
[sudo] password for richard:
make -C /home/richard/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux -f Makefile.6 install
mkdir: cannot create directory ‘/etc/Wireless’: File exists
make[1]: Entering directory `/home/richard/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux'
rm -rf /etc/Wireless/RT2870STA
mkdir /etc/Wireless/RT2870STA
cp /home/richard/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/RT2870STA.dat /etc/Wireless/RT2870STA/.
install -d /lib/modules/3.13.0-37-generic/kernel/drivers/net/wireless/
install -m 644 -c mt7601Usta.ko /lib/modules/3.13.0-37-generic/kernel/drivers/net/wireless/
/sbin/depmod -a 3.13.0-37-generic
make[1]: Leaving directory `/home/richard/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913/os/linux'
richard@silver-desktop:~/Desktop/DPO_MT7601U_LinuxSTA_3.0.0.4_20130913$

Now the next time I reboot, the wireless isn't working again.

Have I misunderstood what 'sudo make install' does?

Regards, Richard.

I'm struggling with the very last instruction sudo make install

I'm in the right directory, run sudo make install,

Revision history for this message
Manfred Hampl (m-hampl) said :
#18

"sudo make install" is supposed to copy the driver files into the right directory. Due to the fact that the directory name includes the version number of the kernel, this has to be done after each new kernel installation. There is the possibility to automate this with dkms.

For getting the module loaded automatically with each boot, you might try the following:

issue the commands

cat /etc/modules
echo mt7601Usta | sudo tee --append /etc/modules
cat /etc/modules

copy/paste the output into this question document.
and then reboot, and after booting try
lsmod | grep 7601
to check whether the module was correctly loaded.

Revision history for this message
Richard Smith (richardasmith) said :
#19

Hi Manfred,

I tried your suggestion and here is the output.

richard@silver-desktop:~$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

lp

richard@silver-desktop:~$ echo mt7601Usta | sudo tee --append /etc/modules
[sudo] password for richard:
mt7601Usta

richard@silver-desktop:~$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

lp
mt7601Usta

richard@silver-desktop:~$

Following a reboot, the module has been loaded and the wifi is working.

Thanks for your help.

Regards, Richard.

Revision history for this message
Richard Smith (richardasmith) said :
#20

I have just done a software upgrade and the kernel has changed to 3.13.0-40-generic.

As expected the wifi no longer works.

I copied the wifi driver file mt7601Usta.ko to the new kernel directory.

When I run insmod mt7601Usta.ko the file fails to load.

This has worked on previous updates.

Any idea what has gone wrong this time?

Regards, Richard.

Revision history for this message
Richard Smith (richardasmith) said :
#21

The terminal shows the following

richard@silver-desktop:/lib/modules/3.13.0-40-generic/kernel/drivers/net/wireless$ sudo /sbin/insmod mt7601Usta.ko
[sudo] password for richard:
insmod: ERROR: could not insert module mt7601Usta.ko: Invalid module format
richard@silver-desktop:/lib/modules/3.13.0-40-generic/kernel/drivers/net/wireless$

Why would the module format be invalid, I used the same file previously.

Regards, Richard

Revision history for this message
Richard Smith (richardasmith) said :
#22

I have managed to get the wifi working again.

 I re-compiled the driver.

Copied the driver file to the new kernel directory (rather than the previously complied driver file)

Run insmod.

Wifi started working and still works after reboot.

I don't understand why the old driver file didn't work.

Regards, Richard.