Continual freeze and lockup with 6.6

[ArloGuthrie]

The latest ViX with latest update constantly freezes. At times I can restart the receiver through putty with a reboot command.
Other times I cannot connect with it even through FTP. Requiring unplugging it.
I use a 1TB external HDD. Ethernet connection. Added dvbsnoop. And the latest oscam-emu from .ipk.

In a new USB flash drive install in a slot that had ver 6.4. I went through the preliminary setup screens. Then added a few satellites in Tuner setup. Went init 4. And dragged in the NIMS section from a backup.
Then init 3 and reboot. Verified my satellite settings and rotor position for the diseqc 1.2 mover. Using a 4X1 Zinwell 1.0 switch and a multiswitch off of that for my twin Norsat lnb's.
Everything works well. But when the TV shuts off on either a clear or not channel. Turning the TV back on shows that the picture is frozen and pixellated and no sound.

Many times if the TV is off for just a short while. A channel change back and forth will restore the channel. If there as a longer period before turning it back on. Either ViX is frozen entirely or no channels can be watched until a cold boot.

If I leave the TV on or turn it on very soon after it shuts down from it's own timer. All looks good.
I have reinstalled 6.6 from scratch and added just a few satellites. With only oscam-emu installed. Same situation. I did not notice this in previous versions.
I did not try an indefinite record to see what happens to the recording when the TV shuts off. Nor did I set a scheduled recording and let it start when the TV shuts off.

Files attached. Really hope the problem can be identified and addressed and tips offered to try a fix.....for ViX.

[twol]

The latest ViX with latest update constantly freezes. At times I can restart the receiver through putty with a reboot command.
Other times I cannot connect with it even through FTP. Requiring unplugging it.
I use a 1TB external HDD. Ethernet connection. Added dvbsnoop. And the latest oscam-emu from .ipk.

In a new USB flash drive install in a slot that had ver 6.4. I went through the preliminary setup screens. Then added a few satellites in Tuner setup. Went init 4. And dragged in the NIMS section from a backup.
Then init 3 and reboot. Verified my satellite settings and rotor position for the diseqc 1.2 mover. Using a 4X1 Zinwell 1.0 switch and a multiswitch off of that for my twin Norsat lnb's.
Everything works well. But when the TV shuts off on either a clear or not channel. Turning the TV back on shows that the picture is frozen and pixellated and no sound.

Many times if the TV is off for just a short while. A channel change back and forth will restore the channel. If there as a longer period before turning it back on. Either ViX is frozen entirely or no channels can be watched until a cold boot.

If I leave the TV on or turn it on very soon after it shuts down from it's own timer. All looks good.
I have reinstalled 6.6 from scratch and added just a few satellites. With only oscam-emu installed. Same situation. I did not notice this in previous versions.
I did not try an indefinite record to see what happens to the recording when the TV shuts off. Nor did I set a scheduled recording and let it start when the TV shuts off.

Files attached. Really hope the problem can be identified and addressed and tips offered to try a fix.....for ViX.

That looks like hardware to me ... it gets nowhere before it dies (none of the logs show that it manages to boot up successfully)
I have a osmio4K+ running at my mother-in-laws using this version, so don't think that this is the issue.
I would disable the seagate , stick a usb stick in as HDD and reflash from new with minimal installed to see if it manages to boot and can successfully play a service and then restart OK and run a servicel

[ArloGuthrie]

Thank you. I had thought of either moving all of the stored data from hdd to my PC and preparing it again through the UI.
I did try running fsck on it but my linux skills are quite rusty. And fsck did not show in busybox on the receiver.
Will try your suggestions. It is a farily new drive and seems to work fine with openatv and older ViX 6.4.
Are there any changes to logging that would show more info?
I have a hint that on a hard crash, the system cannot write a log.

[ArloGuthrie]

Really need suggestions to diagnose and fix this annoyance.
Same receiver. Same oscam version. Same, but zereoed and prepared, initialzed external drive. A WB black passport.

ViX 6.4 shows zero issues. Can switch HDMI ports forever with the receiver on. Can record pv, clear channels while watching a Fire TV Cube streamer.
Monitor oscam webif live log with no problems at all. As perfect of operation as you can imagine.
Used E-Channelizer to transfer all of the lamedb saved channels, bouquets. I could go on.

ViX 6.6 on the other hand. Live log in oscam webif occasionally shows "too many open files". Or locks and shows no progress after awhile.
Less while watching pv, clear channels will it simply stop, freeze channels. Either changing back and forth a channel. Or a complete restart is necessary.
Putting it in standy, restart GUI. No good.

I wanted to try a later version of oscam-emu. Got the binary for an arm processor specific for the osmio4k. Put it in usr/softcams along with the existing version.
Changed permissions to 755, same as the existing version. In softcam manager I tried setting it to start, then started it. It won't.
What's up with that?

Not a single difference in setting up 6.6 versus 6.4. Using the same backup of lamedb.
As mentioned. First trying adding just a few known FTA satellites and using diseqc 1.2 for my dish mover. Followed by a Zinwell 1.0 4X1 switch and then to a unpowered multiswitch for my 2 Norsat lnb's.
Switches are new. No issues with 6.4 at all.

Hopefully a clear description and detailed enough. I tried running the receiver w/o the hdd and adjusted setting accordingly.
After prepping the drive and initializing, ViX wrote the corresponding directories to it.

Does 6.6 use the same lamedb version as 6.4? Missing dependencies? How to check for that? I performed an opkg update sequence. Nothing showed as updates available.

[ArloGuthrie]

Sorry. Too late to edit or add to he previous post.
In 6.4 when changing bouquets. The last channel viewed is saved in the previous one and the one you go to has the previous one you view right there.
In 6.6 it's "spotty" to say the least. Some favorites have the previous channel stored. Mostly the selection will be at the very top of the list.
Did I miss a setting somewhere? Don't remember having to do that in 6.4. Nor where there is (if there is) a way to do it.

[twol]

Really need suggestions to diagnose and fix this annoyance.
Same receiver. Same oscam version. Same, but zereoed and prepared, initialzed external drive. A WB black passport.

ViX 6.4 shows zero issues. Can switch HDMI ports forever with the receiver on. Can record pv, clear channels while watching a Fire TV Cube streamer.
Monitor oscam webif live log with no problems at all. As perfect of operation as you can imagine.
Used E-Channelizer to transfer all of the lamedb saved channels, bouquets. I could go on.

ViX 6.6 on the other hand. Live log in oscam webif occasionally shows "too many open files". Or locks and shows no progress after awhile.
Less while watching pv, clear channels will it simply stop, freeze channels. Either changing back and forth a channel. Or a complete restart is necessary.
Putting it in standy, restart GUI. No good.

I wanted to try a later version of oscam-emu. Got the binary for an arm processor specific for the osmio4k. Put it in usr/softcams along with the existing version.
Changed permissions to 755, same as the existing version. In softcam manager I tried setting it to start, then started it. It won't.
What's up with that?

Not a single difference in setting up 6.6 versus 6.4. Using the same backup of lamedb.
As mentioned. First trying adding just a few known FTA satellites and using diseqc 1.2 for my dish mover. Followed by a Zinwell 1.0 4X1 switch and then to a unpowered multiswitch for my 2 Norsat lnb's.
Switches are new. No issues with 6.4 at all.

Hopefully a clear description and detailed enough. I tried running the receiver w/o the hdd and adjusted setting accordingly.
After prepping the drive and initializing, ViX wrote the corresponding directories to it.

Does 6.6 use the same lamedb version as 6.4? Missing dependencies? How to check for that? I performed an opkg update sequence. Nothing showed as updates available.

1. just to be clear is this only an issue with oscam channels?
2. we build straight from the Gits, so oscam-latest is latest at that build and so is emu-
3. you should only download oscam from feeds as not only are they built for that box, but they are compiled with config values that we know work.
4. do you use softcam manager (config files go in /etc/tuxbox/config) or softcamscript (config files go in /etc/tuxbox/config/oscam-oscamname e.g. /etc/tuxbox/config/oscam-emu
5. lamedb is same

[ArloGuthrie]

1. just to be clear is this only an issue with oscam channels?

No. FTA also. Switch HDMI inputs on the TV for awhile. Or let the TV turn off on it's own. Either way. Seems like an HDMI detection issue. Not so on 6.4.

2. we build straight from the Gits, so oscam-latest is latest at that build and so is emu-

Not so sure of that statement. I am now running oscam from the feeds in Vix. Clearly states on the status screen MOHAMED_OS 2.24.08-11817-802. His is the only build I ever use now for a long time.

3. you should only download oscam from feeds as not only are they built for that box, but they are compiled with config values that we know work.

[I]Thanks. Late last night that was my venue. Compared the configs against my own. Only difference is logging settings. All un needed readers are turned off. Mohammed's latest is V118.12 EMU 802[I]


4. do you use softcam manager (config files go in /etc/tuxbox/config) or softcamscript (config files go in /etc/tuxbox/config/oscam-oscamname e.g. /etc/tuxbox/config/oscam-emu

Why change the wheel. Always used to be in /etc/tuxbox/config. Then I tried installing from the feed in ViX. And go nuts trying to figure out where they are and what drugs compelled someone to put them there. Mostly because 99% of support tells you to look in the regular location. Yes, using softcam manager.

5. lamedb is same

Well then. Since my lamedb files work fine in 6.4. That's one thing settled. Right?

And that's what I know so far.