[GiGaBlue QUAD] [NOT QUAD+] recording problem

[WOODWARD395]

I am using open ATV 4.1 but I had to re-flash the boot loader a couple of times then flash image with blue hd skin there are a couple of differences but you can pm me if you wish to try. you use the config files from vu+ uno on setup running vix. my box is giga quad.

 

[judge]

I am using open ATV 4.1 but I had to re-flash the boot loader a couple of times then flash image with blue hd skin there are a couple of differences but you can pm me if you wish to try.

Skin shouldn't matter. Box used, bootloader used & image used, a lot more helpful.

you use the config files from vu+ uno on setup running vix. my box is giga quad.

No idea why you would use config files from a VU box on a GB box?

 

[WOODWARD395]

Latest bootloader 20130507 open atv 4.1 image setup used only for a certain part of the setup if you know what i mean but quite a few files will work as majority enigma2 box's are very similar but don't advise it if you don't know what your doing but it works for me running smoothly ATV have stopped support on certain parts of their images so you have to find an alternative. I only found out via a third party.:thumbsup:

 

[rossi2000]

^^ what on earth is this guy going on about?

 

[WOODWARD395]

^^ what on earth is this guy going on about?

if you cant understand I wouldn't bother ,I know exactly what I have said maybe I haven't explained very well and its my fault what I can say all the overheating re-booting record glitching and freezing at re-boot has stopped and my box has had no problems whatsoever along with many other people.
I think it best to leave you to it.

 

[WOODWARD395]

Sorry but thats a load of crap, drivers are made and released by the manufacturer and independent of the image exactly the same as the bootloader.

you really need to read up on what a kernel module is

1.1. What Is A Kernel Module?

So, you want to write a kernel module. You know C, you've written a few normal programs to run as processes, and now you want to get to where the real action is, to where a single wild pointer can wipe out your file system and a core dump means a reboot.

What exactly is a kernel module? Modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. For example, one type of module is the device driver, which allows the kernel to access hardware connected to the system. Without modules, we would have to build monolithic kernels and add new functionality directly into the kernel image. Besides having larger kernels, this has the disadvantage of requiring us to rebuild and reboot the kernel every time we want new functionality.

 

[Larry-G]

you really need to read up on what a kernel module is

1.1. What Is A Kernel Module?

So, you want to write a kernel module. You know C, you've written a few normal programs to run as processes, and now you want to get to where the real action is, to where a single wild pointer can wipe out your file system and a core dump means a reboot.

What exactly is a kernel module? Modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. For example, one type of module is the device driver, which allows the kernel to access hardware connected to the system. Without modules, we would have to build monolithic kernels and add new functionality directly into the kernel image. Besides having larger kernels, this has the disadvantage of requiring us to rebuild and reboot the kernel every time we want new functionality.

Go sell your brand of horse manure to some one who cares, this issue is one of gigablue's making and its for them to fix.

END OF STORY.

 

[WOODWARD395]

Go sell your brand of horse manure to some one who cares, this issue is one of gigablue's making and its for them to fix.

END OF STORY.

what's up thought you new your subject and you don't
so you decided to take it personally.

 

[BubbleBalls]

Getting crazy

 

[judge]

what's up thought you new your subject and you don't
so you decided to take it personally.

You seem to be the only one taking it personally? Copying & pasting info on kernel modules doesn't make an expert.
As pheonix says, it's a GB f**kup. It's up to them to stop fobbing customers off & fix the issues.

 

[seame]

So you've come on to a forum to seek help from others with your issue, now that you've claimed your problem is solved, you're not willing to share in more detail how you've sorted it. Nice one pal

if you cant understand I wouldn't bother ,I know exactly what I have said maybe I haven't explained very well and its my fault what I can say all the overheating re-booting record glitching and freezing at re-boot has stopped and my box has had no problems whatsoever along with many other people.
I think it best to leave you to it.

 

[WOODWARD395]

So you've come on to a forum to seek help from others with your issue, now that you've claimed your problem is solved, you're not willing to share in more detail how you've sorted it. Nice one pal

yes I do come to many forums to get help and if I can help others I will but when some forum members start to ridicule you because your way of thinking and methods don't fall into their way of doing things and then say I am wrong and say I talk crap what do you expect.
I have presented the evidence that what I have said about images is correct and even tried to explain in a way the majority of people would understand.
It possibly could be me but I tried my best I just thought if I could solve the issues of at least two or three people I could do some good at least.
I have been very willing to listen to others and learn.
I have found a solution for my box and as said many times it runs flawlessly despite being shut away in a cupboard enclosed in a very small shelve with no fan.
every one is throwing their stones too busy passing the blame instead of working together to resolve the issue.
My solution may not work on all box's due to some of the software other users wish to run.
if I am attacked as I perceive it how do people expect me to react.

 

[Larry-G]

yes I do come to many forums to get help and if I can help others I will but when some forum members start to ridicule you because your way of thinking and methods don't fall into their way of doing things and then say I am wrong and say I talk crap what do you expect.
I have presented the evidence that what I have said about images is correct and even tried to explain in a way the majority of people would understand.
It possibly could be me but I tried my best I just thought if I could solve the issues of at least two or three people I could do some good at least.
I have been very willing to listen to others and learn.
I have found a solution for my box and as said many times it runs flawlessly despite being shut away in a cupboard enclosed in a very small shelve with no fan.
every one is throwing their stones too busy passing the blame instead of working together to resolve the issue.
My solution may not work on all box's due to some of the software other users wish to run.
if I am attacked as I perceive it how do people expect me to react.

No one is attacking you and if I came across as such I apologize, but the point still stands, these issues did not start until users updated their receivers with the newest bootloaders and drivers which are the sole responsibility of the manufacturer, we have no control over how they are created or how they will interact with the image. so once again I will say that this is a Gigablue issue and it is for Gigablue to fix instead of fobbing users off.

 

[WOODWARD395]

You seem to be the only one taking it personally? Copying & pasting info on kernel modules doesn't make an expert.
As pheonix says, it's a GB f**kup. It's up to them to stop fobbing customers off & fix the issues.

no I am no expert but I do take the time to read up on the subject before I make rude comments an do apologise when I think I may be wrong.
yes and I did post information on kernels as I thought others could benefit from knowing how they are actually incorporated into an image and have a better knowledge of the workings of their box.

Thought the whole point of these forums was to learn from one another and become well informed so we can help other newbies and welcome them into their new hobby and onto the forum.

 

[judge]

Thought the whole point of these forums was to learn from one another and become well informed so we can help other newbies and welcome them into their new hobby and onto the forum.

Of which you've done none.

 

[WOODWARD395]

Of which you've done none.

Thats the answer i expected from you.
all you can do is tell everyone GB have f---- up and its all their fault.
it takes months and sometimes years to develop the software for these box's why havent vix thought well after vix 30 the box's don't run so what has changed in the images to stop them working with the bootloader. VIX have more of a chance of resolving the problem as they know exactly when they changed their kernel and what developments they done after the lower images, instead of ridiculing GB as well as myself why not work with GB and assist to put things right.
As i said before you can sit there and call and blame people as many times as you want but it certainly has not resolved the situation,
Another point: one of your renound members stated nearly word for word what i said on images yet that has been accepted as true by all.

 

[Larry-G]

you seem to think that we created the kernel and you are wrong in that assumption, we work with what we are given by the manufacturer, they provide the kernel patch, they provide the bootloader and the drivers to work with that kernel. ALL images are affected by these changes so again go tell Gigablue to pull their finger out and fix these issues that they created in the first place.

 

[WOODWARD395]

Hold my hands up to that you have taught me something I never new but still a lot can be gleamed from the history of your images as does Vix not assemble them using module spanning?
some of the earlier images work with the boot loader which is a starting point
Is not a patched kernel an add on to the original?
and not all images are effected as you say.
I am not here for a fight, I got into this hobby because of the problems and issues you get watching TV is a bonus ok I do want to know the ins and outs of a ducks whatsit but is that not one of the reasons you do what you do.
I may be a thorn in your side at present But many problems are solved by going back to basics it is obvious GB have distribute kernel source that has been patched in various non-standard ways, which has caused all this trouble.
Please don't get back into an argument just asking legitimate questions not trying to catch anyone out.

 

[Sicilian]

Hold my hands up to that you have taught me something I never new but still a lot can be gleamed from the history of your images as does Vix not assemble them using module spanning.
some of the earlier images work with the boot loader which is a starting point
Is not a patched kernel an add on to the original.
and not all images are effected as you say.
I am not here for a fight.
I may be a thorn in your side at present But many problems are solved by going back to basics it is obvious GB have distribute kernel source that has been patched in various non-standard ways, which has caused all this trouble.
Please don't get back into an argument just asking legitimate questions not trying to catch anyone out.

See post 230 of this thread....

 

[WOODWARD395]

See post 230 of this thread....

ALREADY DONE
just trying to learn how images are assembled.
find it very interesting and hoped I could get some answers.