ViX 6.6 Oscam-emu binary instal and get working.
-
- All E2 Devices & Images .ipk .deb
- Arm Support
- supwiddiss
- Thread is marked as Resolved.
There are 33 replies in this Thread which was already clicked 4,890 times. The last Post () by supwiddiss.
-
-
....words
-
Don't forget: unzip the file (binery) from .ipk file with any unzipping program.
that's how i do to extract the oscam file only from an .ipk file.
-
Beat you to it. Jens showed me that years ago. Meaanwhile....
Stop and enable startup.
In terminal start 11824 with ./shortened-name of11814
bus error.
Oh me oh my. What shall I do? -
Where did I provide files? Please post a link so I can edit it to remove confusion. If I did, it was a long time ago and the files are likely to be incompatible with the current version of ViX.
The simplest option for the OP is to install oscam compiled to run on vix 6.6
-
Where did I provide files? Please post a link so I can edit it to remove confusion. If I did, it was a long time ago and the files are likely to be incompatible with the current version of ViX.
The simplest option is to go the ViX forum, there are oscam ipks for ViX 6.6. Download and install them.
Here is the link for your post: post #777
It is nothing wrong with your files. He downloaded the wrong one: sh-4 instead of ARM !
-
Those are not by me. In any case, symlinks should have been sufficient.
Please find attached ipks for oscam-emu 2.24.09-11824 version built for ViX 6.6 environment
-
Thanks Mr. abu. The cortex version installed and is working. The webif works and 11824-802 is shown.
Having thoughts. You can say save them or bring them. -
You are missing the point. It is built to run with the libraries already on your receiver. There are no dependencies included. If any are needed, they will be installed from the plugin server.
All you had to do with the ipks I uploaded was transfer and install the arm version. (Maybe I should not have uploaded the mips one in this thread. I did so because of the rant nature of your posts suggesting there is an issue with the image). Even if you transferred both, opkg would not install the wrong architecture.
If you are going to use a softcam package that someone is uploading, start with a clean image ( i.e no restores), install the ipk as it is provided by the uploader. Start the oscam by command line and report back the error to the compiler . I would suggest you send a message in a succint manner. Less is more! I am sure that they will work out what needs to be done to get it to work.
If you are unzipping the ipk and maually transferring the binary, you could be avoiding any checks/links the installation process has been programmed to do to avoid issues. It is not easy to make the ipks for multiple images.
-
Display More
Having one heck of a time with Mohammed 11812 on a new install of openViX 6.6.
From another thread. Fresh install of ViX on my osmio4k. Installed the oscam version from .ipk.
Got errors. Remembered the lib dependencies that needed to be installed on other previous versions.
Installed it again and it 'took'. Comapred the config files against mine. Okay.
Put my backup configs in etc/tuxbox/config. Then my backup softcam.key file. Cold booted the receiver. It worked.
Massive issues when the TV input was switched to a different input with the receiver on.
The "too many open files" message in live log, suggested changing lb from 1 to 2. Not much, if any, better.
If the receiver is not switched to watch on the TV. It will stop decoding. Lot's of things too many to list.
I want to install a newer binary. So I got an arm platform newer version specifically listed for the osmio4k here.
Placed it in usr/softcams with the 11812 version. Changed permissions to 755. Softcam manager, disable startup for 11812, and the new version named simply oscam.Set it for enable startup. Then start.
Nothing. Restart the box. Nothing again.
Man. Am I rusty or what? Jeez!!Is it a ViX 6.6 'thing? Dependencies? I did not wish to install oscam from the ViX menu because the tend to put configs in funky places.
I multibooted to ViX 6.4 with 11812 and ran it all day. Not a burp, not a puke. Watch my streaming box with the mio running. Came back to it. Perfect.
ViX 6.6. Disaster. HELP!!!! lol
Did you read the upgrading to version 6.6 instructions ?
here it is:
-
Display More
You are missing the point. It is built to run with the libraries already on your receiver. There are no dependencies included. If any are needed, they will be installed from the plugin server.
All you had to do with the ipks I uploaded was transfer and install the arm version. (Maybe I should not have uploaded the mips one in this thread. I did so because of the rant nature of your posts suggesting there is an issue with the image). Even if you transferred both, opkg would not install the wrong architecture.
If you are going to use a softcam package that someone is uploading, start with a clean image ( i.e no restores), install the ipk as it is provided by the uploader. Start the oscam by command line and report back the error to the compiler . I would suggest you send a message in a succint manner. Less is more! I am sure that they will work out what needs to be done to get it to work.
If you are unzipping the ipk and maually transferring the binary, you could be avoiding any checks/links the installation process has been programmed to do to avoid issues. It is not easy to make the ipks for multiple images.
Thank you for that. I do rant at times. Expect that every time. It cuts the back and forth down. Details. Findings. And of course tips both to and from folks who either have issues or require helpful suggestions to a fix. Look at my osmio boot logo...."rant".....as you may call it.
-
When you install items from the plugin server, you are only offered items that are compatible with the the receiver.
Life is too short to waste on rant/rumbling threads. Good luck in your quest.
-
This one from the IPK ARM is working good all day.
-
Would I be permitted to ask what
(-) -- Skipped 2 duplicated log lines --
means. It appears in multiple lines of the live log.
If I may query. Does the message indicate a possible degrade in performance?
And with the proper terminology I pray. Is a method available to reduce or eliminate the anomaly?
That is if it might be something out of the norm and could be solved through the proper diagnostic to discover the cause.
Your resource for OSCam-EMU softcam
![]()
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
