Pausing live TV does not work reliably

[divil_a_bit]

The OS is Linux (a limited OE (Open Embedded) version), and of course Linux contains kernel and drivers.
Drivers are closed source, provided by the manufacturer, and compiled against the kernel.
The application in use = Enigma 2

An image = Linux + E2 + a skin + some plugins

Linux & E2 will vary over teams (as do skins and plugins), but the drivers (and hence the kernel) is the same for every team.

Brilliant explanation Rob - thanks very much.
I didn't realise E2 was an application! I thought it was more than that.

Do you by any chance know the latest version of the Gigablue Quad Plus drivers?
According to openvix, the "Driver date" on mine is 20141020

 

[divil_a_bit]

It's definitely a driver issue. I tried the latest openmips also from here:
http://image.openmips.com/4.2/index.php?open=gbquadplus
and I had the same problem with pausing live TV

 

[yeshu26]

Amen!

Ditto issues on my Miracleboxx Mini HD

 

[Larry-G]

Amen!

Ditto issues on my Miracleboxx Mini HD

The miracle box is a different receiver to the Gigablue so i can't see it having the same driver related issues but I could be wrong.


Sent from my iPad Air using Tapatalk

 

[divil_a_bit]

The OS is Linux (a limited OE (Open Embedded) version), and of course Linux contains kernel and drivers.
Drivers are closed source, provided by the manufacturer, and compiled against the kernel.
The application in use = Enigma 2

An image = Linux + E2 + a skin + some plugins

Linux & E2 will vary over teams (as do skins and plugins), but the drivers (and hence the kernel) is the same for every team.

Just a follow-up question: where do I find out about new kernel/driver release for the GB Quad Plus?
How soon after a kernel or a driver release for the GB Quad Plus receiver will it be picked up by openvix and be included as part of the image?

Thanks

 

[Larry-G]

Bootloaders are not automatically updated but have to be manually. When a new bootloader is made available and we're confident it does not break any thing in the image we will recommend you update and provide a link to it, drivers are added to the GIT and automatically updated with the image, unless we find a issue wit them and intentionally leave them out.


Sent from my iPad Air using Tapatalk

 

[divil_a_bit]

drivers are added to the GIT and automatically updated with the image, unless we find a issue wit them and intentionally leave them out.

Thanks for the information.
Am I correct in saying openvix developers get notified of a driver update from Gigablue and do some testing with that driver. If openvix developers find no issues, they release the drivers as part of the next openvix image?
Where does one find out about GB driver releases, when they're planned and the change logs for each release? I have a couple of issues with my GB Quad Plus and I'm wondering when/if they'll be fixed.

 

[Larry-G]

Thanks for the information.
Am I correct in saying openvix developers get notified of a driver update from Gigablue and do some testing with that driver. If openvix developers find no issues, they release the drivers as part of the next openvix image?
Where does one find out about GB driver releases, when they're planned and the change logs for each release? I have a couple of issues with my GB Quad Plus and I'm wondering when/if they'll be fixed.

That would be the ideal situation yes but it's not always the case. Sometimes we get a heads up, other times another member of the OE-A will get the drivers and submit them to the GIT them selves. Which ever way once new drivers are issued it's not a long wait until they appear in the image.


Sent from my iPad Air using Tapatalk

 

[divil_a_bit]

Great - thanks for the info pheonix

Where does one find out about GB driver releases, when they're planned and the change logs for each release? I have a couple of issues that GB are aware of with my GB Quad Plus and I'm wondering when/if they'll be fixed.

 

[Larry-G]

To be honest contrary to popular belief, we very rarely if ever get to know before hand from any manufacturer about upcoming driver releases, unless we have a specific bug report in with them, then maybe they will give us a advanced copy for testing. The rest of the time we find out the same way as every one else does, when they appear on the download page.

http://archiv.openmips.com/

As for changelogs again very rarely do we get to see those, in fact most manufacturers dont bother to release any form of changelog for their drivers etc.

 

[divil_a_bit]

All very interesting pheonix - thanks for the explanation. I'm keen to learn more ... so I have a few more questions.

If I ssh onto my GB Quad Plus ans run:

> modinfo dvb
filename:       /lib/modules/3.14.2/extra/dvb.ko
license:        GPL
description:    BCM7XXX DVB Driver (michael@gigablue)
version:        20141020154934-14.2
depends:
vermagic:       3.14.2 SMP mod_unload BMIPS 32BIT
parm:           config:string

So from the version the driver date is the 20-oct-2014
That corresponds with the driver date that openvix reports (menu->information->about->Drivers) ... I was always curious where that date came from!

You mentioned the driver for the GB Quad plus came from here:
http://archiv.openmips.com/
However, the date on that driver on that link is 31-jul-2014! So http://archiv.openmips.com/ is clearly not the location of the current driver. Is that right?

If I look here however:
http://gigablue-support.com/
and click "openMips 4.2 Firmware Download", I get to here:
http://image.openmips.com/4.2/index.php?open=gbquadplus
I can see there are more frequent released of openmips.
If I download the latest and unzip the dvb.ko, I can see it has a size of 16,492,687 bytes. The size of the dvb.ko on my own GB Quad Plus is: 11,060,791 byes.
Shouldn't those files be the same size if they were both the same version of the driver?

Thanks for taking the time to help out.

 

[Rob van der Does]

You can follow all changes in e.g. drivers on

https://github.com/oe-alliance/oe-alliance-core

 

[divil_a_bit]

Great - thanks
Any idea why the binary ko files are different here:
http://image.openmips.com/4.2/index.php?open=gbquadplus

??

 

[divil_a_bit]

Came across this thread:
http://www.gigablue-support.org/gig...dergabe-der-aufnahmen-nach-spulen/index2.html

The thread has a link to beta Gigablue Quad+ drivers that are due to be release at the end of Jan 2015.
Link to drivers:
http://archiv.openmips.com/beta/gigablue-drivers-3.14.2-gbquadseries-20141226.zip

I've downloaded and have used and all seems to be OK. Fast Fwd works perfectly! I haven't noticed any problems yet even though they are only beta drivers

 

[mruphillgard]

I have just tried the same beta driver on my box and it's fixed the Fast Fwd issue for me too.