trying to install mt7610u (linksys ae6000)

[greenbag]

(20th Feb, 2016 10:13 AM)Nachteule Wrote:  Btw, I've just added the module source and build prodecure to our kernel build system.

Module will be built and packed successfully into kernel .deb file. Tomorrow after some more tests I'll commit changes and build new kernel packages

ok... so I decided to rebuild, and it only took me about 8 hours to figure out why the hell mt7650u_sta.ko already existed.. lol. The XBian_2016.02.21_rpi2.img.gz includes the module already. But it doesn't work. Even after editing "/etc/network/interfaces" and "/etc/wpa_supplicant/wpa_supplicant.conf" with the required info, it still shows ra0's ESSID as blank:

Code:

xbian@xbian ~ $ sudo iwconfig
[sudo] password for xbian:
wlan0     IEEE 802.11bgn  ESSID:"XXXXXX"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: xx:xx:xx:xx:xx:xx  
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm  
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=61/70  Signal level=-49 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:63   Missed beacon:0

ra0       Ralink STA  ESSID:""  
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated  
          Bit Rate:1 Mb/s  
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=10/100  Signal level:0 dBm  Noise level:0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

dummy0    no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

I finally got it going again by rebuilding with the 2016.02.14 release, making sure not to upgrade or update anything along the way. I did notice that for some reason, I couldn't get ra0 to connect unless I had wlan0 connected as well.. just to select the connection point, then to enter the passkey. After that, I removed the wlan0 adaptor and rebooted. Ra0 took over from there. I couldn't even scan on ra0 without wlan0 being connected.. it would just open and close the notification box immediately, without grabbing a list of networks. With wlan0 connected, I could then select my network on ra0. Very strange. But with your release... if I try to scan on ra0 by itself, it opens and closes immediately, just like my build. But when I try to scan on ra0 with wlan0 connected as well.. it starts to scan, then kodi reboots.. not the pi itself, just kodi goes black, then resets to the main menu screen.

Either I've done something wrong, forgotten something, or something's buggy with your release. Sorry.


btw... thanks for doing that to begin with. The guys at OpenELEC just say "your on your own".

cheers.