Octagon SF8008 Out of Space Error

el bandido

TNAP-Images
Administrator
Recently the Octagon SF8008 would crash during the build and return an out-of-space error, meaning the image was too big for the receiver. Ustym4kPro is about identical, and it was building without any issues? So what is the problem? A closer look showed TBS5925 being built for the SF8008, but not for the Ustym4kPro. At best the TBS item could only be a few MB in size. So two choices, either start scrutinizing and try to figure it out, or have a cup of coffee and watch Claude Code figure it out. I chose the latter.

To make a fairly lengthy ordeal short, Claude Code was setup in the root of the build, meaning he has access to all files and all folders of the build which contains about 1,186,276 items, totaling 95.6 GB in size. I do not say much to Claude Code, except to give warning that this is a working build directory, and do not break it. It was not necessary to supply the crash information, only the address to where the crash file was. After a bit of back and forth conversations, Claude Code decides the SF8008 has roughly 70MB of useless audio drivers that should be removed, and the build of the SF8008 will complete.

So the 70MB of audio drivers were removed, and the build completed. But the SF8008 would not run, which was sort of expected. During all of this Claude discovered a discrepancy in how the file size was calculated as compared to the Ustym4kPro. This is the beauty of giving Claude Code complete access to the build directory as he can go where he needs to, when he wants to. You have to really pay attention to what is happening though, else you will get a build directory that no longer works along with an apologizing Claude Code.

In the end, the discrepancy Claude Code discovered in the size calculation was the real problem, but here is the kicker: Claude Code insists those audio drivers are not really needed as they are provided in the SOC. However, the image will not run without them. It is a given that enigma2 images are stripped versions of Linux, and you do not waste space. But what if Claude Code is right and these drivers for audio are actually useless duplicates? This needs to be looked at as time permits, but I bet it ends up as a dead-end. Still though it is interesting.

I almost always ask for detailed summaries from the AI's when they do something as it really helps when you are trying to revisit an earlier problem. An out of space error turns into: "Hey, you have extra audio drivers in here"...LOL. Like I said, Interesting. The summary file for this is attached.
 

Attachments

Interesting. Does the 8008 come with multiboot "slots" with hard allocated...."partitions" for different images? If that makes sense.
And if so. Could, oh let's say, 4 "slots" be reduced to 2 and allow a bigger image to be installed? Good question?

If the 8008 and Ustym receivers are apparently identical receivers. Is installing an image built for one able to be installed on the other?
And is an older 8008 model image able to be installed on a newer one and vice versa? I was surprised when I plugged in an old USB wifi dongle from a chinabox receiver into a Zgemma. It was immediately identified and a wifi config. menu was accessible.

Not knowing if Claude Code is a person, entity, tool. What is a C.C? And what is "he" doing?

I'm wondering how. If the person building an image could possibly add files to make it too large to install. Or scenario two.
If a USB peripheral like the TBS tuner were plugged in. Perhaps others. While the image was being installed. Would the detected hardware call the installer to pull the drivers and plop them in. And the resulting "oops not enough space" message pops up.
And what about if the TBS were unplugged. Then plugged in after in install. With either a manual driver install or letting it automatically trying it.
And the same resulting message. Perhaps requiring an application>usb to be plugin needing to be used.

Comparatively speaking. This Asus laptop is running Ghost Spectre Win 11. With Secure boot but no TPM. Win 11 would usually be a no-go.
I know there are other methods like Rufus and such to get around that bottle neck. But so far a year of using it. Not a single issue.
A plus is that the install strips out as much fatware and supposedly "Windows spyware", analytics, as humanly possible.
After install there is a shortcut left that allows installing a ton of stripped applications. Edge isn't even included in the stock install. But they can be added later. And services and ancient, un needed things are not active nor present. I mean. When was the last time you used a modem?

We discussed that. TNAP is light. But some of the things. Like networking options usually found in other images are either there. Just not apparent, and running. Or a terminal session is needed to configure them. Or perhaps not there in the first place. Resulting to heading over the the webif package manager, terminal an opkg command to see what is installed.
It makes sense that although capabilities in a SOC might be there. And makes better sense that code, drivers are needed to "turn it on". Or support the internal hardware modules.

SOIC vendors. Satellite STB specific in this case. Offer dev. boards and a sub. for factory tech. support for a given period.
Once the developer gets what they need. Out to production. We all know that. If the subscription runs out when bugs or deficiencies are reported after production. They either figure it out on their own. Or renew the contract and get further help.
NDA's and document stacks might only address the immediate "I need a chip that will do this". Not thinking about the entire capabilities of the device. Right?
There are probably unrevealed functions in these chips that the developer never thought of. And EB, even you stated nothing new has been out there for years and years. Leaked code allows others to build similar boxes.
Sometimes we see. Like on the GTMedia boxes. Newer factory supported firmware ups performance and end used needs.
Pissin' around with Arduino a bit here and there. Adding lines or toggling/changing "switches" in the makefile before compiling.
Kind of a tangential response. But has me wondering.
From personal experience. Folks like Broadcom, NXP, Availink. If they sense that you don't have a pile of bucks to spend. Such as an interested but not a big-guy person could be considered. Good luck on getting any help from them.
 
Claude Code reviewed your post and replied to it (see attached).
Given that you are in an AI section (TNAP AI Development Discussions), I guess we can assume that Claude Code is an AI assistant? But always better to ask if you do not know. For more information on the Claude brothers, see here: Claude (Anthropic)

Yes the slots in multiboot receivers can be reduced to 2 in a similar fashion as you would partition a disk in a computer. Enigma2 receivers could be thought of as stripped versions of Linux. To reduce the slots, you either need to build the image yourself, or find the Instructions Athoik posted years ago for the Edision 4K receivers. But it will probably not do you much good to reduce the slots. Simply put your OpenVix in slot 1 and pretend the other slots do not exist would be easier than deleting them.

You can only put a certain amount of information on a computer disk as they are not infinite in size. Usually the more features and items an image has, the bigger it will be. Skins for example can take anywhere from say 5MB to around 50MB for the largest skin. Safeguards in the image build are there to keep you from packing too much into am image to the point where it will not be usable when it is installed in to the receiver. TNAP is currently adding 100 to 150 MB in uncompressed image size when compared to OpenPLi. The out of space error in the SF8008 will be seen in other image builds if the build size gets big enough. It all has to do with the way things are calculated, which is explained by Claude Code.

The enigma2 part of TNAP contains less information and could be considered "light" when compared to OpenVix or OE Alliance enigma2's. It is very very hard to understand what is supposed to be missing in Network requirements from TNAP as compared to OpenVix when no examples are given. For the most part, OpenVix will have more menu selections, but the networking capabilities should be similar. If you want to to discuss the deficits of TNAP (real or imagined), then post about them in the build thread. Most likely though, everything you need is there, and if not, it is easy enough to see what is installed (or not) and add what you need.

Most of the FTA receivers come from China, with almost all of the development taking place in that country. So we could assume that if anything was "leaked" then they would be leaking it to their self? The "New" enigma2 receivers you see today are versions of past receivers. Nothing more than that. Maybe something will change in the next five years.

Turning a SF8008 into an Ustym4kPro was discussed here: TNAP-6 Image Discussion
The SF8008 has a driver defect that will most likely not be fixed.

As for the original problem this thread was started about? I am glad it was straightened out and the problem solved. There is all sorts of little problems and issues buried in the build code. One day soon we will probably have a chip that addresses and solves that problem. Coding as we know it today is fixing to change in a major way.
 

Attachments

Yeah... And Octagon will fix them, just like they Have Not Done for OpemPLi? I appreciate the link and information, but from past experiences, nothing but a time-waster.
 
I did some thinking. Had some idle thoughts. You can root an Android phone and tablet faster than a tornado clears a trailer park and ask questions. And usually get some good help. No offense meant. Dealing vit der Chermans is just an experience that reminds me of funny mustaches and high top shiny boots and smirky, devious smiles. The OpenATV crew. And let's not exclude the Brits. There's a mix of varying attitude in the blokes there. Kinda stings when a response for well thought about and researched first ask for help results in words like preposterous, rubbish, or challenging a person's intelligence. Of course das ist schtoopit prevails. Followed by other unsolicited comments. And if you don;t step lightly. *Poof* they kick your ass out to the street and you get banned.

Once. Several years ago in my previous life. I had a machine that blew a Lenze stepper control. It was smoked all to hell.
So I ordered a replacement next flight. Went to OIA and grabbed it at 2am and went in to slap it in. The "codeplug" programming module was blank. And the original was toast. So I ordered a codeplug pronto. Tuned in?
By machine serial number. The replacement just didn't work right. I must have gotten 4-5 in the course of a week. FedEx next day packs.
Upper mgmt. was pissed. On my ass.
I found out that the company lost it's programming engineer. I got the programming manual and made a programming jig to do it myself.
The manual tripped my ass out. I had not a clue of the programming needed. But everything was in plain text.
I grabbed the code from the controller. Compared the lines to the manual sections. Ibuprofen and confusion and calls to Texas back and forth.
"I was crazy". "But it works here" (no way, no how it could).
Told 'em I had a programming cable and they FTP'd a few more fast turnaround binaries. Nope. Same screw ups.
Got my ass in the car and drove to a site in Tampa with my laptop and programming jig.
Pulled the code from the codeplug of an identical machine that ran like a peach (a Georgia peach like the TNAP chickie) and drove back home.
In the replacement code they kept sending, I skimmed to a commented section. It was all semi commented.
Down in the gobbeldy-goop-soup there was a commented line before a config. line. Pertaining to (probably have it stashed away someplace still):
"## This section is for a customer from Florida to fix a quick acceleration and immediate stop with 100 percent dynamic brake
## I dont know why it's needed. <lead engneer> told me to add the code so they could try it."
Seriously!
Well. I blew the Tampa code into the controller and summa' bitch! All the problems went away and it worked like the day it was installed.

Huh? Octagon and Chermans. Might as well talk into a mirror? But why? I'd do it myself if it wasn't such a secret. And hell. It might make a few others happy. Schtoopit, das ist inschane, ja? Oh. And I've drank a crap-ton of Guiness. Never got "drunk" drunk (but had to pee a lot). But man! They do. Pukin' drunk!! So rubbish and preposterous is out, bluddy 'ell!. Maybe some people come up with some off-the-chain questions. They might even have a bit more intelligence than Seargent Schults too.

Sorry....rant. Typos and all. ( I Really like this layout now. Too cool.) Haha "There is a problem. You've been banned."
 
Back
Top