Jump to content


Photo

Edision MIO4k+ USB Tuner Issue in Develop Branch


  • Please log in to reply
101 replies to this topic

Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #81 rantanplan

  • PLi® Contributor
  • 1,861 posts

+87
Good

Posted 19 October 2020 - 10:53

 Then build it like that.
Hardcode tuner 0-11.
Why is it like this?
To do this, you would have to understand udev more precisely, mdev automatically generates it.
Certainly there is also a possibility to do this by the Udev itself, but that's how it worked.
Even if it doesn't look so nice, it doesn't matter.
It should work.
greetings

# There are a number of modifiers that are allowed to be used in some
# of the different fields. They provide the following subsitutions:
#
# %n the "kernel number" of the device.
#    For example, 'sda3' has a "kernel number" of '3'
# %e the smallest number for that name which does not matches an existing node
# %k the kernel name for the device
# %M the kernel major number for the device
# %m the kernel minor number for the device
# %b the bus id for the device
# %c the string returned by the PROGRAM
# %s{filename} the content of a sysfs attribute
# %% the '%' char itself

# The first rtc device is symlinked to /dev/rtc
KERNEL=="rtc0", SYMLINK+="rtc"

# Legacy paths for dbox devices
KERNEL=="oled0", SYMLINK+="dbox/oled0"
KERNEL=="fp0", SYMLINK+="dbox/fp0"
KERNEL=="lcd0", SYMLINK+="dbox/lcd0"
KERNEL=="vtuner0", SYMLINK+="misc/vtuner0"
KERNEL=="vtuner1", SYMLINK+="misc/vtuner1"
KERNEL=="vtuner2", SYMLINK+="misc/vtuner2"
KERNEL=="vtuner3", SYMLINK+="misc/vtuner3"
KERNEL=="vtuner4", SYMLINK+="misc/vtuner4"
KERNEL=="vtuner5", SYMLINK+="misc/vtuner5"
KERNEL=="vtuner6", SYMLINK+="misc/vtuner6"
KERNEL=="vtuner7", SYMLINK+="misc/vtuner7"
KERNEL=="vtuner8", SYMLINK+="misc/vtuner8"
KERNEL=="vtuner9", SYMLINK+="misc/vtuner9"
KERNEL=="vtuner10", SYMLINK+="misc/vtuner10"
KERNEL=="vtuner11", SYMLINK+="misc/vtuner11"
KERNEL=="pvr", SYMLINK+="misc/pvr"
KERNEL=="i2c-[0-9]*", SYMLINK+="i2c/%n"

# The first framebuffer is symlinked to /dev/fb
KERNEL=="fb0", SYMLINK+="fb/0"

# Make all input devices read-write to the input group
SUBSYSTEM=="input", GROUP="input", MODE="660"

You could start another attempt and change the application of the Vtuner in the current script from 0-9 to 0-11 and see what comes out of it.

https://github.com/O...extra.rules#L23


Edited by rantanplan, 19 October 2020 - 11:01.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #82 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 20 October 2020 - 04:30

Thanks.
I tried the changes above in post#81 with the same results. These changes were done using a fresh build.
 

The mdev.config file has this line:
dvb([0-9])\.(.*)([0-9]) 0:0     660     >dvb/adapter%1/%2%3
 

I do not see any useful lines in the udev.config file. I can only ask is the mdev.config file the only reason mdev works?



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #83 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 20 October 2020 - 14:47

For some reason the drivers create /dev/video0, while all other boxes use /dev/dvb/adapter0/video0.

 

Perhaps that mdev line is there as a workaround for this problem?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #84 Dimitrij

  • PLi® Core member
  • 10,370 posts

+354
Excellent

Posted 20 October 2020 - 14:59

el bandido

https://github.com/O...extra.rules#L23

change

KERNEL=="vtuner[0-11]*", SYMLINK+="misc/vtuner%n

It won't help?


GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #85 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 21 October 2020 - 11:49

No help when using this:
KERNEL=="vtuner[0-11]*", SYMLINK+="misc/vtuner%n
 

Thanks.



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #86 rantanplan

  • PLi® Contributor
  • 1,861 posts

+87
Good

Posted 21 October 2020 - 13:47

for me this is still try & error and it doesn't matter if it doesn't work ;-)

Just try to add the line

KERNEL=="dvb([0-9])\.(.*)([0-9])*", SYMLINK+="dvb/adapter%1/%2%3"

looks like this

# There are a number of modifiers that are allowed to be used in some
# of the different fields. They provide the following subsitutions:
#
# %n the "kernel number" of the device.
#    For example, 'sda3' has a "kernel number" of '3'
# %e the smallest number for that name which does not matches an existing node
# %k the kernel name for the device
# %M the kernel major number for the device
# %m the kernel minor number for the device
# %b the bus id for the device
# %c the string returned by the PROGRAM
# %s{filename} the content of a sysfs attribute
# %% the '%' char itself
#

# The first rtc device is symlinked to /dev/rtc
KERNEL=="rtc0", SYMLINK+="rtc"

# Legacy paths for dbox devices
KERNEL=="oled0", SYMLINK+="dbox/oled0"
KERNEL=="fp0", SYMLINK+="dbox/fp0"
KERNEL=="lcd0", SYMLINK+="dbox/lcd0"
KERNEL=="vtuner[0-9]*", SYMLINK+="misc/vtuner%n"
KERNEL=="pvr", SYMLINK+="misc/pvr"
KERNEL=="i2c-[0-9]*", SYMLINK+="i2c/%n"
KERNEL=="dvb([0-9])\.(.*)([0-9])*", SYMLINK+="dvb/adapter%1/%2%3"

# The first framebuffer is symlinked to /dev/fb
KERNEL=="fb0", SYMLINK+="fb/0"

# Make all input devices read-write to the input group
SUBSYSTEM=="input", GROUP="input", MODE="660"

Edited by rantanplan, 21 October 2020 - 13:48.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #87 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 21 October 2020 - 15:24

Thanks. I added your line, and it did not work.
KERNEL=="dvb([0-9])\.(.*)([0-9])*", SYMLINK+="dvb/adapter%1/%2%3"

 

I made a fresh build folder. and only moved the sources folder into it. No other changes were made to Any of the files. This build makes two video0 files as shown below.
root@osmio4kplus:~#  find /dev -name video0
/dev/video0
/dev/dvb/adapter0/video0
root@osmio4kplus:~#

 

My NinoPro does not have a video0 file in /dev.
 



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #88 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 21 October 2020 - 15:37

That is what I expected, the same is true for the OS Mio 4K (without the plus), but all other boxes I have don't have /dev/video0 either.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #89 rantanplan

  • PLi® Contributor
  • 1,861 posts

+87
Good

Posted 21 October 2020 - 16:45

Isn't that coming from the kernel, or am I getting it wrong?
Kernels up to version 5 have a different DVB handling and the kernel 5 actually does it internally.
Conversely, the problem here is the handling required for kernels <5.
If I understand that correctly in the kernel, then Vtuner symlink and i2c symlink would not be necessary there, or even wrong.

But I'm not sure ...



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #90 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 21 October 2020 - 17:02

Quite possible it's a v5 / v4l thing.

 

In which case isn't it not simply a matter of those USB drivers not being compatible with the new API?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #91 ims

  • PLi® Core member
  • 13,887 posts

+215
Excellent

Posted 21 October 2020 - 17:31

Btw - OsMio4k (no plus) has localextra.rules:

# There are a number of modifiers that are allowed to be used in some
# of the different fields. They provide the following subsitutions:
#
# %n the "kernel number" of the device.
#    For example, 'sda3' has a "kernel number" of '3'
# %e the smallest number for that name which does not matches an existing node
# %k the kernel name for the device
# %M the kernel major number for the device
# %m the kernel minor number for the device
# %b the bus id for the device
# %c the string returned by the PROGRAM
# %s{filename} the content of a sysfs attribute
# %% the '%' char itself
#

# The first rtc device is symlinked to /dev/rtc
KERNEL=="rtc0", SYMLINK+="rtc"

# Legacy paths for dbox devices
KERNEL=="oled0", SYMLINK+="dbox/oled0"
KERNEL=="fp0", SYMLINK+="dbox/fp0"
KERNEL=="lcd0", SYMLINK+="dbox/lcd0"
KERNEL=="vtuner[0-9]*", SYMLINK+="misc/vtuner%n"
KERNEL=="pvr", SYMLINK+="misc/pvr"
KERNEL=="i2c-[0-9]*", SYMLINK+="i2c/%n"

# The first framebuffer is symlinked to /dev/fb
KERNEL=="fb0", SYMLINK+="fb/0"

# Make all input devices read-write to the input group
SUBSYSTEM=="input", GROUP="input", MODE="660"

 


Kdo nic nedělá, nic nezkazí!

Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #92 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 21 October 2020 - 17:35

Those are standard for every box.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #93 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 21 October 2020 - 17:51

An older MIO4k backup image with kernel 4.19.4 also has video0 in /dev.

 

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


 



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #94 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 21 October 2020 - 21:22

I think problem is much simpler.

 

Running udev first load usb drivers faster than loading system drivers.

 

So the first usb is registered as /dev/dvb/adapter0/ and obviously there are no video0/audio0 devices on usb driver.

 

When the system driver is loading, the adapter0 is already occupied, so system drivers do not load any more.

dvbdev: DVB: registering new adapter (cx231xx #0)
cx231xx 2-1:1.1: DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3306A VSB/QAM Frontend)...
...
dvbdev: DVB: registering new adapter (Broadcom BCM7xxx)
...
[<c0840f90>] (dvb_register_adapter) from [<bf757a8c>] (brcmstb_dvb_init+0x40/0xbb4 [brcmstb_osmio4kplus])
[<bf757a8c>] (brcmstb_dvb_init [brcmstb_osmio4kplus]) from [<bf75e7d0>] (brcmstb_dev_init+0x514/0xa4c [brcmstb_osmio4kplus])
[<bf75e7d0>] (brcmstb_dev_init [brcmstb_osmio4kplus]) from [<bf15c250>] (osmio4k_init+0x250/0x1000 [brcmstb_osmio4kplus])
[<bf15c250>] (osmio4k_init [brcmstb_osmio4kplus]) from [<c0201650>] (do_one_initcall+0x58/0x1c4)
[<c0201650>] (do_one_initcall) from [<c029a168>] (do_init_module+0x5c/0x204)
[<c029a168>] (do_init_module) from [<c029c32c>] (load_module+0x1f20/0x22f4)
[<c029c32c>] (load_module) from [<c029c928>] (sys_finit_module+0xd0/0xe8)
[<c029c928>] (sys_finit_module) from [<c0200060>] (ret_fast_syscall+0x0/0x4c)
Exception stack(0xc9687fa8 to 0xc9687ff0)
7fa0:                   00000000 00000000 00000003 00028c44 00000000 00000000
7fc0: 00000000 00000000 0003c4a8 0000017b 0003a220 00000000 00000000 0003c848
7fe0: beda59f8 beda59e8 0001fcac b6e6d3a0
Code: ea000002 e5933000 e153000a 0a000007 (e5132004)
---[ end trace 8bd4c044fc9b8938 ]---
/etc/rcS.d/S05modutils.sh: line 37:   381 Segmentation fault      modprobe brcmstb-decoder > /dev/null 2>&1

So we need to make sure that system drivers are loaded before starting to load any usb drivers.


Edited by athoik, 21 October 2020 - 21:22.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #95 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 21 October 2020 - 22:11

You could add external modules to the end of

 

/etc/modprobe.d/blacklist

 

then add them to the beginning of

 

/etc/modules


Open Vision sources: https://github.com/OpenVisionE2


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #96 rantanplan

  • PLi® Contributor
  • 1,861 posts

+87
Good

Posted 21 October 2020 - 22:21

 

Running udev first load usb drivers faster than loading system drivers.

https://forums.openp...dpost&p=1264132

 

@athoik

Just how do you delay sent?



Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #97 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+542
Excellent

Posted 24 October 2020 - 10:04

Weird, on the STB's I know the modules that load the dvb drivers for their own platform are loaded explicitly, not using auto-mod-probe etc. If the edision fails to do that, it might be better if edision fixes that themselves.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #98 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 28 October 2020 - 21:59

The udev has a mechanism to load drivers.

 

GFA8G.png

 

https://unix.stackex...t-udev-requests

 

I think we are missing a "finetune" on udev regarding usb "dvb" drivers.


Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #99 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 28 October 2020 - 22:23

Can you please try to move modutils loading before udev? (udev is S04udev)

 

mv /etc/rcS.d/S05modutils.sh /etc/rcS.d/S03modutils.sh

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Edision MIO4k+ USB Tuner Issue in Develop Branch #100 el bandido

  • Senior Member
  • 392 posts

+15
Neutral

Posted 29 October 2020 - 01:17

Success with Udev!
As a test, I added all Hauppage atsc devices that are supported. Seems to work with perfection.
Where do I put this change in the image build .bb files?

 

 

Attached Files




5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users