Hello from Germany.
I just switched from a DM900 Ultra HD (you may have met me on other forums) to a Vu+ DUO 4K SE.
After a quick check with the factory image that the device is not dead on arrival, I flashed it with openbh-5.0.011.release-vuduo4kse-1205265b_usb.zip
which is why I created an account here.
At first look this feels like a very polished image, thank you for maintaining this!
Do you prefer issues in this board or on github?
(I personally would prefer GH, but I can also use this web forum if preferred.)
Once I know where, I'll gladly file the one bug I found so far[1] as well as other issues I might come across
pcfe
[1]. For now the below is just FYI why my intro post asks about where to file bugs
On issue during my initial bringup of OpenBh 5.0 was that channel scanning was not functional.
While the on TV message reads Cable scan executable utility not found '/usr/bin/bcm3148 '!
The binary is present on disk…
In my case that was not a big issue, I had regular web bouquet backups of my DM900 and OpenBh 5.0's web bouquet editor accepted it.
Still, I guess this bug needs tracking and debugging. I'll be happy to pull debug logs
I just switched from a DM900 Ultra HD (you may have met me on other forums) to a Vu+ DUO 4K SE.
After a quick check with the factory image that the device is not dead on arrival, I flashed it with openbh-5.0.011.release-vuduo4kse-1205265b_usb.zip
which is why I created an account here.
At first look this feels like a very polished image, thank you for maintaining this!
Do you prefer issues in this board or on github?
(I personally would prefer GH, but I can also use this web forum if preferred.)
Once I know where, I'll gladly file the one bug I found so far[1] as well as other issues I might come across
pcfe
[1]. For now the below is just FYI why my intro post asks about where to file bugs
On issue during my initial bringup of OpenBh 5.0 was that channel scanning was not functional.
While the on TV message reads Cable scan executable utility not found '/usr/bin/bcm3148 '!
The binary is present on disk…
Bash:
root@vuduo4kse:~# cat /etc/os-release
ID=openbh
NAME="openbh"
VERSION="5.0"
VERSION_ID=5.0
PRETTY_NAME="openbh 5.0"
root@vuduo4kse:~# uname -r
4.1.45-1.17
root@vuduo4kse:~# ls -l /usr/bin/bcm3148
-rwxr-xr-x 1 root root 12426 Feb 13 22:40 /usr/bin/bcm3148
root@vuduo4kse:~# /usr/bin/bcm3148
max=6900000 min=6875000
gI2CIndex=2 gDeviceNum=0
FAILED 50500 7000000
FAILED 57500 7000000
[… etc, they are all FAILED but then again I am not sure if enigma2 calls the binary with any options…]In my case that was not a big issue, I had regular web bouquet backups of my DM900 and OpenBh 5.0's web bouquet editor accepted it.
Still, I guess this bug needs tracking and debugging. I'll be happy to pull debug logs
