bxwen
mt7601 driver
October 12, 2016 01:17AM
bodhi:

First thank you for all the work. I have 4 pogoplugs running different versions of your debian systems.

I am trying to install mt7601 wireless adapter using
https://github.com/art567/mt7601usta

I get an error
make[1]: *** /lib/modules/4.6.0-kirkwood-tld-1/build: No such file or directory. Stop.

that directory doesn't exist.

information:

# uname -a
Linux serverSeries4 4.6.0-kirkwood-tld-1 #1 PREEMPT Wed May 18 03:54:14 PDT 2016 armv5tel GNU/Linux


# lsusb
Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


bxwen
bxwen
Re: mt7601 driver
October 12, 2016 01:25AM
never mind. I create a symbolic link to the headers, now it is compiling. I am not sure about if the card will work though.
bxwen
Re: mt7601 driver
October 12, 2016 01:49AM
didn't work.

# lsmod
Module Size Used by
mt7601Usta 533537 0
ipv6 321027 38
evdev 10805 0
marvell_cesa 25314 0
des_generic 16834 1 marvell_cesa
orion_wdt 6073 0
gpio_keys 7730 0
mmc_block 25318 2
sata_mv 25104 0
libata 164641 1 sata_mv
mvsdio 9070 0
mmc_core 103423 2 mmc_block,mvsdio
scsi_mod 176077 1 libata


no ra0 shows up in ifconfig.
Re: mt7601 driver
October 12, 2016 02:09AM
bxwen,

The MT7601 module is already in the kernel 4.6-tld-1, no need to compile it separately.

Try
modprobe mt7601u

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bxwen
Re: mt7601 driver
October 12, 2016 04:06PM
It is sort of work now.

It didn't work in the first place, is because the mt7601u.bin under /lib/firmware has 0 bytes. I downloaded another one from github.

Now it is sort of working. Because if I unplug the ethernet, I loss wireless connection also. I am not sure what is going on yet.
Re: mt7601 driver
October 12, 2016 04:53PM
bxwen Wrote:
-------------------------------------------------------
> It is sort of work now.
>
> It didn't work in the first place, is because the
> mt7601u.bin under /lib/firmware has 0 bytes. I
> downloaded another one from github.

Yes, usually you do need to take care of this for the RALINK. The good way to have this by default is to install the firmware-ralink package or some such package from the vendor.

>
> Now it is sort of working. Because if I unplug the
> ethernet, I loss wireless connection also. I am
> not sure what is going on yet.

This is probably the IP route setup is lacking (a common issue). If the routing rules is correct, then you can unplug ethernet without bringing down the wireless network.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bxwen
Re: mt7601 driver
October 12, 2016 10:56PM
bodhi,
thank you for the help.

Yes it is an IP route problem. Before I unplug ethernet,

# ip route list
default via 192.168.2.223 dev eth0
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.223
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.141

If I disconnect the ethernet cable, it becomes (I didn't this through serial port):
# ip route list
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.141

If I add the default route back it would work again
#ip route add default via 192.168.2.141

Unfortunately I don't know how to fix the problem.

Another problem I have is when I reboot, wlan0 doesn't come up automatically. I have to type ifup wlan0 to enable it.
~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

allow-hotplug eth0
#auto lo eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-ssid ffd
wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Re: mt7601 driver
October 13, 2016 12:44AM
It's been a long time. So I'm not sure if this will work, try:

ip route add -net 192.168.2.0  netmask 255.255.255.0 gw 192.168.2.1 dev wlan0
where 192.168.2.1 is your router.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: mt7601 driver
February 04, 2017 12:03PM
The default route disappeared because it was tied to the DHCP lease of eth0. When eth0 goes down, its default route is deleted from the routing table. If you simply leave eth0 unplugged then it won't be an issue.

You can bounce wlan0 to get the default route back:
ifdown wlan0; ifup wlan0

I'm not sure about wlan0 not coming up at boot -- that's not a problem on my oxnas systems. I'll be playing with a kirkwood system in the coming weeks and will post if I run into the same issue and find a solution.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: