101 replies to this topic

[el bandido]

I am having problems with the Hauppauge usb ATSC tuner being properly recognized when building an image using the  develop branch. During boot, the Hauppauge tuner  is registered as adapter 0, but then there is an error no video0 file (/dev/dvb/adapter0/video0: No such file or directory)
 

The Hauppauge usb ATSC tuner can be removed from the receiver, and then reinserted into the receiver during boot, immediately after the Edision splash screen exits, and there are no booting issues.  (cx231xx 1-1.2:1.1: DVB: registering adapter 1 frontend 0 (LG Electronics LGDT3306A VSB/QAM Frontend)...)
 

What can I do to fix this?  Surely there is a file that I can alter somewhere....

A RS232 log showing the Hauppauge tuner installed, and the Hauppuage tuner installed after the Edision splash screen exits is attached.

Thanks. EB
 

Attached Files

•  pli-develop-usb-tuner-issue.zip   12.1KB   4 downloads

Edited by el bandido, 21 September 2020 - 18:22.

[rantanplan]

Da fehlt sicher die Firmware, das kann dann nicht klappen.

 

ups...:-)

 

I think a firmware or part of the firmware will be missing.
So it doesn't work.

Edited by rantanplan, 21 September 2020 - 19:13.

[Erik Slagter]

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

[el bandido]

OpenPLi 7.3 (9-20-2020) works correctly.  Logfile attached showing this version loading Hauppauge 850,950, and 955 usb tuners without issues.

Attached Files

•  PLi-7.3-Hauppauge-ATSC-Tuners.zip   9.84KB   2 downloads

[Erik Slagter]

Yes, like I said. In develop we switched from mdev to udev. An although udev should be a seamless replacement, there appear to be some little quirks that need attention. Maybe this is one of them.

 

The first step ahead to fix this is:

 

- flash and boot release (7.3), then do ls -lR /dev

- flash and boot develop, then do ls -lR /dev

 

Put both in a zip file and post them here.

 

Make sure no formatting codes are in the files (like fancy colours etc).

 

It will almost certainly turn out that in develop one or more dev nodes are at a different location and need a symlink.

Edited by Erik Slagter, 23 September 2020 - 15:55.

[el bandido]

Thanks.
The attached file should be correct. Please let me know if it isn't.

Attached Files

•  ls -lR dev.zip   7.64KB   3 downloads

[rantanplan]

I still think the firmware is missing.
In comparison, the missing firmware is noticeable.
The kernel automatically installs the sis firmware in the image, but it seems to be missing the firmware-dvb-fe-xc5000-1.6.114.
Simply install and test it from the ipk via build feed.

 

firmware-dvb-fe-xc5000-1.6.114

[el bandido]

These files are in the 7.3-release image firmware folder:
total 1331
drwx------ 1 pli pli      0 Dec 31  1969 .
drwx------ 1 pli pli      0 Jul  4 20:15 ..
drwx------ 1 pli pli      0 Sep 23 08:21 ath10k
-rwx------ 1 pli pli   8124 Jul  5 00:59 bdwlan30.bin
-rwx------ 1 pli pli  62148 Jul  5 00:59 btfw32.tlv
-rwx------ 1 pli pli  13576 Jul  4 09:27 carl9170-1.fw
-rwx------ 1 pli pli  28656 Jul  5 00:59 dvb-demod-si2168-a20-01.fw
-rwx------ 1 pli pli  17576 Jul  5 00:59 dvb-demod-si2168-a30-01.fw
-rwx------ 1 pli pli   6919 Jul  4 20:14 dvb-demod-si2168-b40-01.fw
-rwx------ 1 pli pli  12401 Jul  4 20:15 dvb-fe-xc5000-1.6.114.fw
-rwx------ 1 pli pli  16497 Jul  4 10:38 dvb-fe-xc5000c-4.1.30.7.fw
-rwx------ 1 pli pli   5015 Jul  4 20:15 dvb-tuner-si2158-a20-01.fw
-rwx------ 1 pli pli  72684 Jul  4 09:27 htc_7010.fw
-rwx------ 1 pli pli  50980 Jul  4 09:27 htc_9271.fw
-rwx------ 1 pli pli  23921 Jul  5 00:59 otp30.bin
-rwx------ 1 pli pli 711662 Jul  5 00:59 qwlan30.bin
-rwx------ 1 pli pli   4196 Jul  5 00:59 regulatory.db
-rwx------ 1 pli pli   1182 Jul  5 00:59 regulatory.db.p7s
-rwx------ 1 pli pli   8192 Jul  4 09:27 rt2870.bin
-rwx------ 1 pli pli   2048 Jul  4 09:27 rt73.bin
drwx------ 1 pli pli      0 Sep 23 08:21 rtlwifi
-rwx------ 1 pli pli 296610 Jul  5 00:59 utf30.bin
-rwx------ 1 pli pli  16382 Jul  4 20:15 v4l-cx231xx-avcore-01.fw
drwx------ 1 pli pli      0 Sep 23 08:21 wlan
 

These files are in the Develop image firmware folder:
total 1330
drwx------ 1 pli pli      0 Sep 12 00:36 .
drwx------ 1 pli pli      0 Sep 12 00:36 ..
drwx------ 1 pli pli      0 Sep 12 00:36 ath10k
-rwx------ 1 pli pli   8124 Aug 26 02:37 bdwlan30.bin
-rwx------ 1 pli pli  62148 Aug 26 02:37 btfw32.tlv
-rwx------ 1 pli pli  13576 Aug 26 03:13 carl9170-1.fw
-rwx------ 1 pli pli  28656 Aug 26 02:35 dvb-demod-si2168-a20-01.fw
-rwx------ 1 pli pli  17576 Aug 26 02:36 dvb-demod-si2168-a30-01.fw
-rwx------ 1 pli pli   6919 Aug 26 02:33 dvb-demod-si2168-b40-01.fw
-rwx------ 1 pli pli  12401 Aug 27 20:48 dvb-fe-xc5000-1.6.114.fw
-rwx------ 1 pli pli  16497 Aug 27 20:48 dvb-fe-xc5000c-4.1.30.7.fw
-rwx------ 1 pli pli   5015 Aug 26 02:34 dvb-tuner-si2158-a20-01.fw
-rwx------ 1 pli pli  72684 Aug 26 03:12 htc_7010.fw
-rwx------ 1 pli pli  50980 Aug 26 03:11 htc_9271.fw
-rwx------ 1 pli pli  23921 Aug 26 02:37 otp30.bin
-rwx------ 1 pli pli 711662 Aug 26 02:37 qwlan30.bin
-rwx------ 1 pli pli   3764 Aug 26 02:31 regulatory.db
-rwx------ 1 pli pli   1182 Aug 26 02:31 regulatory.db.p7s
-rwx------ 1 pli pli   8192 Aug 26 03:11 rt2870.bin
-rwx------ 1 pli pli   2048 Aug 26 03:10 rt73.bin
drwx------ 1 pli pli      0 Sep 12 00:36 rtlwifi
-rwx------ 1 pli pli 296610 Aug 26 02:37 utf30.bin
-rwx------ 1 pli pli  16382 Aug 27 20:48 v4l-cx231xx-avcore-01.fw
drwx------ 1 pli pli      0 Sep 12 00:36 wlan
drwx------ 1 pli pli      0 Sep 12 00:36 zd1211
 

[rantanplan]

ok then it was worth a try ...
If you compare the two images this is missing from the tuner in the develop build.

You could test something else ...
OE-Alliance Image branch 4.4
is also udev and the firmware and kernel are similar there.
Maybe something else will stand out.
greetings

[rantanplan]

what I've only noticed now ...

the installation could be wrong

 

https://github.com/O....6.114.bb#L6-L7

https://github.com/o....6.114.bb#L8-L9

 

Edit:

But it should actually fit, no idea ..

Edited by rantanplan, 23 September 2020 - 18:55.

[WanWizard]

I see no difference. The base dir variable difference is related to the different way OE-A images are build.

[rantanplan]

yes, sorry didn't want to cause confusion.
It was noted above as an edit.
It was just an idea that something might go wrong.

[Erik Slagter]

The difference between the devs:

 

release has a directory "i2c" (but it's empty) where develop hasn't.

develop has an extra "video1" node

release has 9 vtuners while develop only has 4.

[rantanplan]

You mean this?
He could certainly test locally with adapted variables

 

https://github.com/O...a.rules#L19-L28

Edited by rantanplan, 23 September 2020 - 19:29.

[el bandido]

If it helps,
The attached file is from ATV image, OE-Alliance build using branch 4.4.

ATSC tuners seem to work correctly in this build.
 

 

 

Attached Files

•  atv- ls -lR dev.zip   2.47KB   2 downloads

[rantanplan]

 Have you tried to build it with the local adaptation in the localextra.rules mentioned above?

# 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"

 

[el bandido]

I installed the above file to: /openpli-oe-core/meta-openpli/recipes-core/udev/files

The receiver still crashes with this error:
/dev/dvb/adapter0/video0: No such file or directory

[rantanplan]

Did you rebuild 'clean'?
Nothing was changed in the assignment regarding dvb.
Maybe someone has a better idea?

[el bandido]

Attached is the output of ls -lR /dev after changing that file.

Attached Files

•  ls -lR dev_file change.zip   3.77KB   2 downloads

Edited by el bandido, 26 September 2020 - 15:43.

[el bandido]

Did you rebuild 'clean'?
Nothing was changed in the assignment regarding dvb.
Maybe someone has a better idea?

No clean rebuild. Let me try that....