101 replies to this topic

[rantanplan]

just as a note
A completely new building will be necessary to rule out errors.
Otherwise you will still have parts of the Mdev in the image afterwards.
The data generated by the mdev were not followed completely.
It is quite possible that you should test (0-11) instead of (0-9).
greetings

[el bandido]

The attached rs232 log comes from a new PLi Develop build that started with an empty folder.
The only exceptions or changes are:
(1) The sources folder was transferred.
(2) The 3 Hauppauge drivers were added to openpli-enigma2-image.bb as I have done in the past. The Hauppauge drivers are added so they can be installed in the image for my convenience. No other changes that I am aware of were made besides these two.

Attached Files

•  10-14-2020.zip   10.52KB   8 downloads

[WanWizard]

That is chinese to me. Really.

[el bandido]

Updated the kernel to 5.9. (This update did not help.)

 

What is interesting to me is every usb tuner I have tried will work IF they are inserted into the receiver immediately after the Edision splash screen completes.
A log file showing 6 usb tuners loading successfully is attached.
 

 

Attached Files

•  mioplus-tuner-h_19691231190543.jpg   109.11KB   1 downloads
•  MIOplus-Tuner-H.zip   10.26KB   2 downloads

[rantanplan]

Starting udev
udevd[132]: starting version 3.2.8
random: udevd: uninitialized urandom read (16 bytes read)
random: udevd: uninitialized urandom read (16 bytes read)
random: udevd: uninitialized urandom read (16 bytes read)
udevd[133]: starting eudev-3.2.8

possible that this still causes problems here?
But actually udev is there and the tuners seem to be properly involved, or am I wrong?
 

[el bandido]

The usb tuners load properly IF they are installed into the receiver After the Edision splash screen completes.  I guess the Edision splash lasts 15 seconds. So in order to get the tuners installed or on a reboot of the box, the usb tuners have to be physically removed, the box has to be restarted, and the Edision splash has to complete, then the usb tuners can be reinstalled into the receiver's usb ports.

[rantanplan]

Yes
exactly that could be a consequence of the error shown above.
One likes to hide these errors with 'print', but that is often not useful.
Here either the system seems to need a sleep (wait) command, or one would have to request re-initialization.
Maybe
@athoik has a clue how to go about this.

[Erik Slagter]

Enigma crashes because it can't open /dev/video0. That doesn't mean the complete STB crashed. There was no need to capture the console output. Also I see a lot of modules being loaded successfully and I am wondering why /dev/video0 doesn't appear. Maybe still one module is missing or not loaded automatically (like one of the many v4l2 modules). Another option might be that /dev/video0 is created, but by default at another place in the dev tree. A symlink in the udev config might help there. Do a "find -name video0 /dev" to check this.

[el bandido]

I have problems with the find -name command. The receiver rejects it when looking in /dev.

osmio4kplus login: root
root@osmio4kplus:~# find -name video0 /dev
find: unrecognized: /dev
BusyBox v1.31.0 (2020-10-12 22:16:19 UTC) multi-call binary.

I tried another way:

root@osmio4kplus:~# cd /
root@osmio4kplus:/# find -name video0
./sys/devices/platform/rdb/f0b00500.ehci_v2/usb2/2-1/2-1:1.1/video4linux/video0
./sys/class/video4linux/video0
./dev/video0
root@osmio4kplus:/#
 

You are 100% correct on how the receiver acts and how it functions.
* Remote Does Not Work
* No Tuners Are Present
* Web Interface Does Work
* Menus Can Be Accessed.

To me, It looks like part of the problem is video0 ends up in /dev when it should be in /dev/dvb/adapter0? I have no clue why or why this happens. Then like you say, other things are not being loaded like the remote.
 

Attached Files

•  About_19691231190545.jpg   75.73KB   2 downloads

[betacentauri]

By the way the directory is first parameter afaik:
find /dev -name video0

You found a /dev/video0 which looks ok for me.

[WanWizard]

Are you sure?

A standard develop build has

root@vuduo4k:~# find /dev -name "video0"
/dev/dvb/adapter0/video0

 

[betacentauri]

Ok, not sure. Forget that part from me

[el bandido]

Thanks Betacentauri.

root@osmio4kplus:/# find /dev -name video0
/dev/video0
root@osmio4kplus:/#

 

[WanWizard]

is that on an mdev or a udev image?

[essco]

Or it is an udev issue, comparable to VU+ Turbo tuners that didn't get reconised without some help.

Sorry, is it possible to VU Solo2 to recognize VU USB Turbo tuner in OpenPLi?

[Erik Slagter]

is that on an mdev or a udev image?

 

+1

 

Do this on the mdev and the udev image.

 

And yes I had the order of the parameters for find wrong, indeed.

[WanWizard]

Sorry, is it possible to VU Solo2 to recognize VU USB Turbo tuner in OpenPLi?

 

Yes, why not?
 

[essco]

I tried in August and did not worked, with usb turbo 1.0 driver.

 

It's Turbo SE, forgot to mention. 

Which driver should I install?

I also tried OBH and Pure2, without result. I use now VTi but I wish to go back to OpenPli

Edited by essco, 18 October 2020 - 18:11.

[el bandido]

is that on an mdev or a udev image?

That is on a udev image.

[el bandido]

Here is udev image:
osmio4kplus login: root
root@osmio4kplus:~#  find /dev -name video0
/dev/video0

Then a build with mdev:
osmio4kplus login: root
root@osmio4kplus:~# find /dev -name video0
/dev/video0
/dev/dvb/adapter0/video0

Telnet debug level 5 and rs232 logs of each  image is attached.

 

Attached Files

•  mdev-udev-debug files.zip   36.72KB   8 downloads