86 replies to this topic

[kelsinni]

OK... I have just flashed the latest image openpli-8.1-release-vuzero-20211024_usb.zip

 

Gonna plug the wifi pen on it, do the 1st reboot, set the basic options and LAN, install enigma2-plugin-drivers-network-usb-mt7601u_1.0-r0_all.ipk and enigma2-plugin-drivers-network-usb-mt7601u_1.0-r1_all.ipk, reboot, and then I will post here the respective output.

[WanWizard]

Pointless, both packages contain the same.

[kelsinni]

You'll probably see the same as in your post #5, and you'll get the same reply as I have in post #12.

 

For some reason the driver returns data in its scan request that python's iw libs choke on.

 

Can you try this:

 

After you've installed the drivers, reboot the box. Don't do anything in Enigma, but telnet (or ssh) to the box, and issue the command

iwlist wlan0 scan

(if the interface is not called wlan0, issue the command "ifconfig" to find the name of the WLAN interface and use that instead)

 

and please post or attach the output here, so we can see if we can use that output to find the bug.

So... done as you told too:

 

- Installed the enigma2-plugin-drivers-network-usb-mt7601u_1.0-r1_all.ipk drivers;

- reboot the receiver

- when accessed the network menu, there was no wifi menu (so I assume the receiver hasnt recognized the pen even after the drivers instalation)

- even so I tried to run the commands you told and there is the respective output:

openpli 8.1-release vuzero

vuzero login: root
Last login: Thu Jan  1 01:12:56 CET 1970 on pts/0
root@vuzero:~# iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

root@vuzero:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1D:EC:17:62:BE
          inet addr:192.168.1.118  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:ecff:fe17:62be/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:835 errors:0 dropped:2 overruns:0 frame:0
          TX packets:509 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:127557 (124.5 KiB)  TX bytes:82823 (80.8 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:140 (140.0 B)  TX bytes:140 (140.0 B)

root@vuzero:~#

So I think its not being recognized by the receiver...

 

Any guess?

 

Thanks

[kelsinni]

Here goes some pics of the receiver and the respective wifi pen:

 

 

 

 

 

[WanWizard]

Odd manufacturer label, does anyone else with a Zero v2 and check theirs?

 

So it doesn't even load the drivers. Can you do the following: type

lsusb

with the wifi stick connected, and post the result here, so we can double check the driver for support of this specific USB ID.

 

And

lsmod

to check what drivers have been loaded.
 

[mimisiku]

Info looks legit… See my photos from my old VU+SoloSE v2 and VUcZero 4K.. MAC addresses are like VU+

 

Attached Files

•  23277954-E6F9-490E-817D-8CC9374A51C8.jpeg   157.24KB   0 downloads
•  454BEB7D-8547-4A46-A643-B4D1D7526794.jpeg   64.92KB   0 downloads

[kelsinni]

Here it is:

root@vuzero:~# lsusb
Bus 001 Device 002: ID 148f:7601
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
root@vuzero:~# lsmod
Module                  Size  Used by
nfsd                  100177  11
exportfs                4211  1 nfsd
ipv6                  329561  56
fpga_directc             477  0
brcmfb                  1590  2
dvb_bcm73625         6932495  1 brcmfb
procmk                  1668  1 dvb_bcm73625
root@vuzero:~#

[kelsinni]

Just to add that the only way I could an eventual recognition of the wifi pen by the receiver was as it is mentioned on the post #3:

 

Running the following commands by telnet:

 

opkg update
opkg install firmware-mt7601u
opkg install kernel-module-mt7601usta

full reboot

 

But then as I told, when I choosed the option 'scan wireless networks' I got a green screen with that crash

[WanWizard]

I'm now confused. You report that the entire wireless interface is missing, and now it turns out that is because you didn't installed the driver and firmware?

 

So now that the driver is installed and you see the interface, we're back at:

 

Can you try this:

 

After you've installed the drivers, reboot the box. Don't do anything in Enigma, but telnet (or ssh) to the box, and issue the command

iwlist wlan0 scan

(if the interface is not called wlan0, issue the command "ifconfig" to find the name of the WLAN interface and use that instead)

 

and please post or attach the output here, so we can see if we can use that output to find the bug.

[kelsinni]

 

I'm now confused. You report that the entire wireless interface is missing, and now it turns out that is because you didn't installed the driver and firmware?

 

So now that the driver is installed and you see the interface, we're back at:

 

Can you try this:

 

After you've installed the drivers, reboot the box. Don't do anything in Enigma, but telnet (or ssh) to the box, and issue the command

iwlist wlan0 scan

(if the interface is not called wlan0, issue the command "ifconfig" to find the name of the WLAN interface and use that instead)

 

and please post or attach the output here, so we can see if we can use that output to find the bug.

 

Sorry, maybe I hadn't explain me well...

 

It was supose just connect the wifi pen on USB, reboot the receiver and when access the 'network' menu it should appear the 2 options to select either wifi or LAN right? This doesnt happen even after I do the following:

 

Copy the file enigma2-plugin-drivers-network-usb-mt7601u_1.0-r1_all.ipk by telnet to the receiver to  /tmp directory... access through the receiver and enter the Plugins menu - Software manager - Install local extension... reboot...and nothing happened (outputs mentioned on #27)

 

The only way I acheived an apparently recognition of the wifi pen by the receiver was before this last image flash, when I was searching here in the forum and saw a similar topic (here: https://forums.openp...enpli-71/page-2) on which a user (@Aliraza63) mentioning that running the following command by telnet had work for him (but not with a VU+ zero...I tought it was a VU+ Solo and Uno 4K). That commands were:

 

>opkg update
>opkg install firmware-mt7601u
>opkg install kernel-module-mt7601usta

>opkg install enigma2-plugin-systemplugins-wirelesslan

full reboot

 

After that, I had the 2 options 'wifi' and 'LAN' on the 'network' menu but if I choosed 'wifi' and then 'scan wireless networks' I had a green screen and a crash...

 

This last time, I followed what you said about 'Don't do anything in Enigma' and I didn't do it.

Edited by kelsinni, 26 October 2021 - 23:51.

[WanWizard]

Don't do anything in Enigma means do not go into the network menu and scan!

 

We already know it crashes, and we already know where it crashes. So repeating that process is pointless.

 

What we don't know is WHY it crashes there, for which I need the output of "iwlist wlan0 scan".

[ricki]

Same error as i got  when i select the option 'scan wireless networks' I got a green screen with that crash

 

https://forums.openp...8-enigma-crash/

[ccs]

..... that crash is 

 

IOError: [Errno 13] Permission denied: '/etc/resolv.conf'

[WanWizard]

Indeed, different issues.

[kelsinni]

Don't do anything in Enigma means do not go into the network menu and scan!

 

We already know it crashes, and we already know where it crashes. So repeating that process is pointless.

 

What we don't know is WHY it crashes there, for which I need the output of "iwlist wlan0 scan".

 

The respective output is the same:

root@vuzero:~# iwlist wlan0 scan
wlan0     Interface doesn't support scanning.

I'm now gonna run the follwing commands:

>opkg update
>opkg install firmware-mt7601u
>opkg install kernel-module-mt7601usta

>opkg install enigma2-plugin-systemplugins-wirelesslan
 

Then reboot and run again "iwlist wlan0 scan" and see if the output is the same...

[WanWizard]

And you're sure the interface is called "wlan0" (check the ouput of "ifconfig") ?

 

Reinstalling something that is already installed is pointless, that will not change anything. And drivers aren't the source of this problem.

[kelsinni]

And you're sure the interface is called "wlan0" (check the ouput of "ifconfig") ?

 

Reinstalling something that is already installed is pointless, that will not change anything. And drivers aren't the source of this problem.

here it is:

[ccs]

iwlist can have invalid parametes, it still reports back.  eg iwlist wlan99 scan gives wlan99    Interface doesn't support scanning.

[WanWizard]

The wlan interface isn't there again.

 

I have no idea what you're doing now, as you said earlier you could select the WLAN interface in Enigma (which isn't possible if ifconfig doesn't show it).

[kelsinni]

The wlan interface isn't there again.

 

I have no idea what you're doing now, as you said earlier you could select the WLAN interface in Enigma (which isn't possible if ifconfig doesn't show it).

 

Well if you have no ideia... imagine me, a noob on these matters

 

But see it:

The output of 'ifconfig' command
 

openpli 8.1-release vuzero

vuzero login: root
Last login: Wed Oct 27 10:54:14 WEST 2021 on pts/0
root@vuzero:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1D:EC:17:62:BE
          inet addr:192.168.10.74  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:ecff:fe17:62be/64 Scope:Link
          inet6 addr: 2001:818:e8c1:7e00:21d:ecff:fe17:62be/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3240 errors:0 dropped:8 overruns:0 frame:0
          TX packets:2462 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:489309 (477.8 KiB)  TX bytes:1666729 (1.5 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:140 (140.0 B)  TX bytes:140 (140.0 B)

root@vuzero:~#

And the screeshot of the 'network' menu now with the 2 options (wifi and LAN) after I had run the commands mentioned above on my post #35

 

By this point if I choose the 'wifi' option and then 'scan wireless networks'... BANG! I got that green screen...