WiFi on OpenVix

[dazh1970]

I’m off to work now bro’ but I’ll have a look tmw and let you know.
How do I find the logs? I’m very much a 0 when it comes to Linux knowledge.
Cheers mate.

[twol]

Afraid that hasn’t worked. In fact, when I do anything now, I get a crash log.
I’ve attached a photo from the tv screen to show what’s happening.
I get this if I go into network, plugins to name just a couple…

Attachment 66779Attachment 66779

So I have seen that issue where a user is using an old skin…..have you installed a skin? What skin are you using?
If so we can probably get around that issue.
If you haven,t setup,logs they will be in /home directory
Just for future information:
you setup logs via menu/setup/system/logs/settings … set location to hdd (not flash), local time, enable logs.

[dazh1970]

So I have seen that issue where a user is using an old skin…..have you installed a skin? What skin are you using?
If so we can probably get around that issue.
If you haven,t setup,logs they will be in /home directory
Just for future information:
you setup logs via menu/setup/system/logs/settings … set location to hdd (not flash), local time, enable logs.

Hello twol - thanks very much for your reply.

When I gained access and connected via the internet, I first of all upgraded from v5 to v6 (latest patch) of VIX.
After that I downloaded the driver for my wifi dongle and then finally I did download one skin from the list to try.
It was one which the list which came from the internet connection and was VIXBMC HD-Night.

Since changing to this skin, every screen change or every save comes up with that error screen code that I attached earlier.
I can't do anything with the receiver without it crashing.

If you can help, I'd very much appreciate it mate.

Incidentally, I have tried to re-flash the version by USB but the receiver wont respond to the USB either despite I used the HP USB Disk Storage program to fully clean the USB before saving the version openvix-6.6.006.release-zgemmah7_multi to the usb device.

I won't be able to check in again after tmw for a few days but I'd appreciate if we can keep the thread going to try and resolve the issues.

[abu baniaz]

Issue following command by Putty or terminal in openwebif to stop enigma2

init 4

Using filezilla or any other FTP app on your PC, navigate to
/etc/enigma2 and edit the file called "settings"

Delete line with "config.skin.primary"

Save, transfer back and restart enigma2 with following command

init 3

[ArloGuthrie]

If I may. I have an H7. I like to know the IP addresses of devices on my LAN. So my preference is to assign static IP addresses for them.
Of course in webif. Selecting Settings>Packages and either installed or all. Make sure the actual RTL8192eu drivers are installed.
Look in the LAN interface settings and write your current LAN settings down. Unplug the LAN cable and configure your wifi.
Just to check (for me always) Use DHCP: No.
IP address. The same as the wired connection but select an address a few higher or lower than you wrote down. If wired was XXX.XXX.XXX.141. Give it a 145 or 140.
Everything else should be entered the same. Primary DNS should be your router IP (no change from LAN). You can leave secondary dns blank or use Google 8.8.4.4
Hopefully you're not trying to connect to a wifi guest network.
Double check Nameserver settings. The same as DNS settings.
Depending on your router for the wifi connection. Encryption should be WPA or WPA2. You should know that. You can check on other devices.
SSID, you said you entered correctly. The key. Correct also.
Run network test after you save the settings. In this scenario only DHCP should be red. Of course.
Make sure all settings are saved. Sometimes I've found that a handshake between the receiver and router are needed. A cold boot of the router, then cold boot of the receiver. Meaning the white power button in back after deep standby.
My H7 has a RTL8192 (no eu designation) USB wifi dongle. If you head into packages (dongle unplugged) and search for the RTL8192eu and remove all drivers for it. Then shut it down cold (no power). Insert the dongle and power it up.I should find it and install the correct drivers automatically. Going through the wifi setup may or may not have to be done again.
Just some personal findings. Hope it helps a little.

[birdman]

Look in the LAN interface settings and write your current LAN settings down. Unplug the LAN cable and configure your wifi.
Just to check (for me always) Use DHCP: No.
IP address. The same as the wired connection but select an address a few higher or lower than you wrote down. If wired was XXX.XXX.XXX.141. Give it a 145 or 140.

Sounds very dangerous to me. If the LAN address was DHCP assigned (as it probably would be) then a nearby address will likely be DHCP assignable too, so this is just setting up a future really-weird issue.
What you should do here is find out what range of addresses your router is using for DHCP then use one which is outside of that range. (And remember it, and don't use it anywhere else).

[Joe_90]

Sounds very dangerous to me. If the LAN address was DHCP assigned (as it probably would be) then a nearby address will likely be DHCP assignable too, so this is just setting up a future really-weird issue.
What you should do here is find out what range of addresses your router is using for DHCP then use one which is outside of that range. (And remember it, and don't use it anywhere else).

Good advice! Having duplicate IP addresses on your LAN is a major pain if and when it happens.