usual user
-
Posts
423 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by usual user
-
-
22 hours ago, mc510 said:
Yep, just tried it on the OPi's usb connection, and it worked first time.
Now you know you have a proper working CUPS.
22 hours ago, mc510 said:I don't see anything on my router that would be blocking communication
As hubs, switches or bridges usually do not apply any firewall rules if the devices are in the same network segment, there is nothing you should blame your router for.
22 hours ago, mc510 said:I haven't (knowingly!) done anything on the OPi that would block network communication.
Having *no* print spool service on a device is quite common and rightfully a firewall does not open any ports for any specific print communication by default.
22 hours ago, mc510 said:CUPS *was* able to detect the printer during setup.
Service discovery has primary nothing to do with print protocols. It is e.g. done by zero-conf (avahi) using different ports. And as it is being used by several services it is quite common a firewall has the involved ports open by default.
To check if the firewall on the OPi is the culprit, temporary disable it entirely and try printing via network again.
-
As can be seen from the log (Executing backend \"/usr/lib/cups/backend/dnssd\"...) the cups backend is been started over and over again without succeeding in transfer any data to the printer.
Maybe e.g. some firewall rules or something else network related is not setup properly. To approve this, connect the printer via USB and check if printing is working then. -
8 hours ago, mc510 said:
I can't find any guides about how to troubleshoot CUPS
First step would be to enable "Save debugging information for troubleshooting" in the administration tab and inspect the log files.
-
Does the image provided ---there---, put on a separate microSD with "xz -dcv Fedora-Minimal-armhfp-31-1.9-trial.raw.xz > /dev/sdX", boot for you properly?
"/dev/sdX" has to be replaced by the device where the separate microSD resides while the transfer. -
Screenshot while transcode pipeline is running on the HummingBoard-i2-i-MX6-Dual-Lite.
See conky panel for performance values.
-
https://linuxtv.org/irc/irclogger_log/v4l?date=2019-11-01,Fri&sel=38#l34
Quotehverkuil: of particular interest to you will be that we decided on how to tackle the final issues that are blocking the stateful encoding spec to be merged.
It should be possible to get that done before the end of this year.\o/
-
On 10/29/2019 at 11:31 AM, martos said:
the transcode h264 HD to H264 low resolution could works ?
If I looked this up correctly from the i.MX 6Solo/6DualLite Applications Processor Reference Manual the VPU has this specs:
HW Decoder: H.264 Profile: BP/CBP/MP/HP Resolution: 1080 i/p, 30 fps Bitrate: 50 Mbps
HW Encoder: H.264 Profile: BP/CBP Resolution: 1080p, 30 fps Bitrate: 14 MbpsOn 10/29/2019 at 11:31 AM, martos said:(only one dual core and only 1gb )
As the VPU is a dedicated IP the number of CPU cores does not matter for the codec performance and 1gb should suffice to provide the required buffer allocations for the intermediate frames.
Just composed my first transcode pipeline, see transcode-pipeline.pdf for reference. I do not really know what I am doing (google was my friend) and there are so much knobs for configuration and fine tuning so YMMV.
-
On 10/25/2019 at 10:53 PM, martos said:
What is the device with imx6q SoC ?
As the mentioned features are properties of the SoC it does not realy matter at which device the i.MX6 resides. Chose what fits your needs.
On 10/25/2019 at 10:53 PM, martos said:what is your linux ?
As already stated to have all features out the box you need at least kernel 5.4.0-rc1. The rootfs distribution does not really matter as long as it provides software of the latest mainline releases.
I tinker with cubox-i and hummingboard and as I wanted all bells and whistles I chose the quad variant with 2GB ram for me.
This is working for me since round about fedora 26. OK, in the early days many of early adopter patches were required.
But nowadays only proper configuration is necessary. -
1 hour ago, Deepu S said:
capture USB output destined for a printer
You have to start here: https://www.kernel.org/doc/html/v5.3-rc3/usb/gadget_printer.html
-
On 10/20/2019 at 10:16 PM, gounthar said:
make a table with all the information regarding h.264 encoding and transcoding on various SoCs
On imx6q SoC there is:
v4l2-ctl --device=/dev/video0 --all
SpoilerDriver Info:
Driver name : coda
Card type : CODA960
Bus info : platform:coda
Driver version : 5.4.0
Capabilities : 0x84208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Detected Stateful EncoderPriority: 2
Format Video Capture:
Width/Height : 1920/1088
Pixel Format : 'H264' (H.264)
Field : None
Bytes per Line : 0
Size Image : 3133440
Colorspace : Rec. 709
Transfer Function : Default (maps to Rec. 709)
YCbCr/HSV Encoding: Default (maps to Rec. 709)
Quantization : Default (maps to Full Range)
Flags :
Format Video Output:
Width/Height : 1920/1088
Pixel Format : 'NV12' (Y/CbCr 4:2:0)
Field : None
Bytes per Line : 1920
Size Image : 3133440
Colorspace : Rec. 709
Transfer Function : Default (maps to Rec. 709)
YCbCr/HSV Encoding: Default (maps to Rec. 709)
Quantization : Default (maps to Limited Range)
Flags :
Selection Video Capture: compose, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_default, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_bounds, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_padded, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop_default, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop_bounds, Left 0, Top 0, Width 1920, Height 1088, Flags:
Streaming Parameters Video Output:
Capabilities : timeperframe
Frames per second: 30.000 (30/1)
Write buffers : 0
User Controlshorizontal_flip 0x00980914 (bool) : default=0 value=0
vertical_flip 0x00980915 (bool) : default=0 value=0
min_number_of_output_buffers 0x00980928 (int) : min=1 max=1 step=1 default=1 value=1 flags=read-only
Codec Controls
video_gop_size 0x009909cb (int) : min=0 max=99 step=1 default=16 value=16
video_bitrate 0x009909cf (int) : min=0 max=32767000 step=1000 default=0 value=0
number_of_intra_refresh_mbs 0x009909d6 (int) : min=0 max=8160 step=1 default=0 value=0
sequence_header_mode 0x009909d8 (menu) : min=0 max=1 default=1 value=1
1: Joined With 1st Frame
maximum_bytes_in_a_slice 0x009909db (int) : min=1 max=1073741823 step=1 default=500 value=500
number_of_mbs_in_a_slice 0x009909dc (int) : min=1 max=1073741823 step=1 default=1 value=1
slice_partitioning_method 0x009909dd (menu) : min=0 max=2 default=0 value=0
0: Single
1: Max Macroblocks
2: Max Bytes
vbv_buffer_size 0x009909de (int) : min=0 max=262144 step=1 default=0 value=0
initial_delay_for_vbv_control 0x009909e1 (int) : min=0 max=32767 step=1 default=0 value=0
h264_i_frame_qp_value 0x00990a5e (int) : min=0 max=51 step=1 default=25 value=25
h264_p_frame_qp_value 0x00990a5f (int) : min=0 max=51 step=1 default=25 value=25
h264_maximum_qp_value 0x00990a62 (int) : min=0 max=51 step=1 default=51 value=51
h264_level 0x00990a67 (menu) : min=0 max=11 default=11 value=11
5: 2
8: 3
9: 3.1
10: 3.2
11: 4
h264_loop_filter_alpha_offset 0x00990a68 (int) : min=-6 max=6 step=1 default=0 value=0
h264_loop_filter_beta_offset 0x00990a69 (int) : min=-6 max=6 step=1 default=0 value=0
h264_loop_filter_mode 0x00990a6a (menu) : min=0 max=2 default=0 value=0
0: Enabled
1: Disabled
2: Disabled at Slice Boundary
h264_profile 0x00990a6b (menu) : min=0 max=0 default=0 value=0
0: Baseline
h264_constrained_intra_pred 0x00990a7f (int) : min=0 max=1 step=1 default=0 value=0
h264_chroma_qp_index_offset 0x00990a80 (int) : min=-12 max=12 step=1 default=0 value=0
mpeg4_i_frame_qp_value 0x00990a90 (int) : min=1 max=31 step=1 default=2 value=2
mpeg4_p_frame_qp_value 0x00990a91 (int) : min=1 max=31 step=1 default=2 value=2
mpeg4_level 0x00990a95 (menu) : min=0 max=7 default=7 value=7
7: 5
mpeg4_profile 0x00990a96 (menu) : min=0 max=0 default=0 value=0
0: Simplev4l2-ctl --device=/dev/video1 --all
SpoilerDriver Info:
Driver name : coda
Card type : CODA960
Bus info : platform:coda
Driver version : 5.4.0
Capabilities : 0x84208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04208000
Video Memory-to-Memory
Streaming
Extended Pix FormatDetected Stateful Decoder
Priority: 2
Format Video Capture:
Width/Height : 1920/1088
Pixel Format : 'NV12' (Y/CbCr 4:2:0)
Field : None
Bytes per Line : 1920
Size Image : 3133440
Colorspace : Rec. 709
Transfer Function : Default (maps to Rec. 709)
YCbCr/HSV Encoding: Default (maps to Rec. 709)
Quantization : Default (maps to Limited Range)
Flags :
Format Video Output:
Width/Height : 1920/1088
Pixel Format : 'H264' (H.264)
Field : None
Bytes per Line : 0
Size Image : 3133440
Colorspace : Rec. 709
Transfer Function : Default (maps to Rec. 709)
YCbCr/HSV Encoding: Default (maps to Rec. 709)
Quantization : Default (maps to Full Range)
Flags :
Selection Video Capture: compose, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_default, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_bounds, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Capture: compose_padded, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop_default, Left 0, Top 0, Width 1920, Height 1088, Flags:
Selection Video Output: crop_bounds, Left 0, Top 0, Width 1920, Height 1088, Flags:
Streaming Parameters Video Output:
Capabilities : timeperframe
Frames per second: 30.000 (30/1)
Write buffers : 0User Controls
horizontal_flip 0x00980914 (bool) : default=0 value=0
vertical_flip 0x00980915 (bool) : default=0 value=0
min_number_of_capture_buffers 0x00980927 (int) : min=1 max=1 step=1 default=1 value=1 flags=read-onlyCodec Controls
mpeg2_level 0x00990a0e (menu) : min=0 max=3 default=3 value=3 flags=read-only
0: Low
1: Main
2: High 1440
3: High
mpeg2_profile 0x00990a0f (menu) : min=0 max=4 default=4 value=4 flags=read-only
0: Simple
1: Main
2: SNR Scalable
3: Spatially Scalable
4: High
h264_level 0x00990a67 (menu) : min=0 max=12 default=12 value=12 flags=read-only
0: 1
1: 1b
2: 1.1
3: 1.2
4: 1.3
5: 2
6: 2.1
7: 2.2
8: 3
9: 3.1
10: 3.2
11: 4
12: 4.1
h264_profile 0x00990a6b (menu) : min=0 max=4 default=4 value=4 flags=read-only
0: Baseline
2: Main
4: High
mpeg4_level 0x00990a95 (menu) : min=0 max=7 default=7 value=7 flags=read-only
0: 0
1: 0b
2: 1
3: 2
4: 3
5: 3b
6: 4
7: 5
mpeg4_profile 0x00990a96 (menu) : min=0 max=4 default=4 value=4 flags=read-only
0: Simple
1: Advanced Simple
2: Core
3: Simple Scalable
4: Advanced Coding Efficiencyv4l2-ctl --device=/dev/video10 --all
SpoilerDriver Info:
Driver name : imx-media-csc-s
Card type : imx-media-csc-scaler
Bus info : platform:imx-media-csc-scaler
Driver version : 5.4.0
Capabilities : 0x84208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04208000
Video Memory-to-Memory
Streaming
Extended Pix Format
Media Driver Info:
Driver name : imx-media
Model : imx-media
Serial :
Bus info :
Media version : 5.4.0
Hardware revision: 0x00000000 (0)
Driver version : 5.4.0
Priority: 2
Format Video Capture:
Width/Height : 720/576
Pixel Format : 'YU12' (Planar YUV 4:2:0)
Field : None
Bytes per Line : 720
Size Image : 622080
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Limited Range)
Flags :
Format Video Output:
Width/Height : 720/576
Pixel Format : 'YU12' (Planar YUV 4:2:0)
Field : None
Bytes per Line : 720
Size Image : 622080
Colorspace : sRGB
Transfer Function : Default (maps to sRGB)
YCbCr/HSV Encoding: Default (maps to ITU-R 601)
Quantization : Default (maps to Limited Range)
Flags :
Selection Video Capture: compose, Left 0, Top 0, Width 720, Height 576, Flags:
Selection Video Capture: compose_default, Left 0, Top 0, Width 720, Height 576, Flags:
Selection Video Capture: compose_bounds, Left 0, Top 0, Width 720, Height 576, Flags:
Selection Video Output: crop, Left 0, Top 0, Width 720, Height 576, Flags:
Selection Video Output: crop_default, Left 0, Top 0, Width 720, Height 576, Flags:
Selection Video Output: crop_bounds, Left 0, Top 0, Width 720, Height 576, Flags:User Controls
horizontal_flip 0x00980914 (bool) : default=0 value=0
vertical_flip 0x00980915 (bool) : default=0 value=0
rotate 0x00980922 (int) : min=0 max=270 step=90 default=0 value=0 flags=modify-layout/dev/video10 requires at least kernel 5.4.0-rc1 to work out of the box.
gst-inspect-1.0 exposes:Quotevideo4linux2: v4l2h264enc: V4L2 H.264 Encoder
video4linux2: v4l2mpeg4enc: V4L2 MPEG4 Encoder
video4linux2: v4l2mpeg4dec: V4L2 MPEG4 Decoder
video4linux2: v4l2mpeg2dec: V4L2 MPEG2 Decoder
video4linux2: v4l2h264dec: V4L2 H264 Decoder
video4linux2: v4l2convert: V4L2 Video ConverterSo hardware accelerated video pipelines can be composed in all flavors.
-
In fedora these changes can`t land since the kernel is universal and device specific buildins are not allowed to prevent vmlinuz bloat. An initramfs is only required if you have an encrypted rootfs or want to use UUID or LABEL for rootfs identification. For this to work you need user space tools. The initramfs is highly rootfs dependent hence it is almost ever created on the fly while kernel package installation in the running system. Doing it in an offline manner is quite difficult if not impossible. For a not encrypted rootfs with PARTUUID the kernel can always find the rootfs as long as it has buildin support to access the rootfs. No matter at what block device the rootfs resides the kernel will find it. IMHO a distribution building device dedicated kernels should try to avoid using an initramfs. Without an initramfs installing a kernel boils down to copy preassembled files in place and point the boot loader at them. It can be done easily in an offline manner to recover a system and is rootfs independent as long as the files are copied in the correct location. I have done it with the fedora kernel to bootstrap the minimal armbian image.
On 9/13/2019 at 9:50 PM, Igor said:... and we are very limited with testings changes on hardware. I am the only one dealing with this.
As a fly by, I thought I should report some observations. I don't care enough for armbian to get this included.
An armbian supporter has to take over here. -
On 10/1/2019 at 7:21 AM, Igor said:
As the error tells. You need to recreate it. Boot without is possible if you set root device to /dev/mmcblk01 and not UUID
Boot without initrd with the current config-5.3.1-cubox is not possible. In fedora config I need at least to flip CONFIG_MMC_BLOCK, CONFIG_MMC_SDHCI, CONFIG_MMC_SDHCI_PLTFM and CONFIG_MMC_SDHCI_ESDHC_IMX from module to buildin to be able to boot without initramfs from mmc.
-
On 10/2/2019 at 4:28 PM, dudepron said:
I tired to copy the files from a new SD install of 5.3.1
If you have copied in /boot/vmlinuz-5.3.1-cubox, /boot/initrd.img-5.3.1-cubox, /boot/dtb-5.3.1-cubox/ and /lib/modules/5.3.1-cubox/ from your new SD install of 5.3.1 your only missing part should be to copy in the attached /boot/extlinux/extlinux.conf.
-
On 10/4/2019 at 8:16 AM, Igor said:
Check images from download section. They are working fine for me, for example: https://dl.armbian.com/cubox-i/archive/Armbian_5.98_Cubox-i_Ubuntu_bionic_next_5.3.1_desktop.7z
Dropping the bare image on the micro SD starts with working HDMI support. Maybe it is the different content of the initrd as that is the only difference to the previous used image kernel wise. But it is loading the wrong DTB (for cubox-i, not for hummingboard) and there is no visible cursor in the VT. Dropping in the attached /boot/extlinux/extlinux.conf fixes this. The first boot stanza doesn't even matter as uboot recognizes the missing files and gracefully skips to the second stanza. This gives a nice snappy desktop.
-
On 10/4/2019 at 8:16 AM, Igor said:
They are working fine for me
Your log shows the device is equipped with 1G of RAM, hence no cma is reserved.
Etnaviv support should not be working, you probably need "cma=256M@1G" as a workaround. -
OK, figured what was going on.
First step was to reinstall the armbian uboot from /usr/lib/linux-u-boot-next-cubox-i_5.98_armhf again. It has full distro boot feature available. I was mislead by a comment (# next kernels have different u-boot without autodetection) in /boot/boot.cmd.
In the end uboot is setting up the boot parameters in a not suitable manner for my environment. And "Starting kernel ..." as the only feedback is not of much help to analyse the problem. I came up with the append line setup of the first boot stanza in /boot/extlinux/extlinux.conf to boot successful in my environment.
In serial.log you see an automatic recover from a failing boot.
Initially the fourth boot stanza is selected with boot parameters derived from /boot/boot.cmd. This is failing with "Starting kernel ...". After a while the watchdog kicks in and triggers a reset. Uboot restarts and autoboots the first boot stanza.
The attached extlinux.conf can be used for the Armbian_5.98_Cubox-i_Debian_buster_next_5.3.1_minimal.7z as is. For other images the PARTUUID has to be adopted. "blkid" will tell you the proper value of your rootfs partition. -
What I have done with my exercise is to approve that the 5.3.1 kernel is really broken and missing some proper build config.
See serial.log for reference.
As uboot, kernel and rootfs have no hard dependence they can be exchanged independently. I have replaced uboot with a fedora one, dropped in a fedora kernel and an 5.2.10 armbian one. With distro boot I can select witch kernel to use at boot time. The 5.3.0-rc1 fedora kernel approves that the rootfs is flawless working with HDMI support. My distribution of choice is fedora and I am used to build kernels that sometimes break, like just 5.4.0-rc1 recently. But as I keep always a working kernel in place, it is only a matter of reboot to recover. -
2 hours ago, v-man said:
I had some sort of crash trying to start from a text console.
As Weston introduces some unnecessary indirection, using kms/drm with proper zero copy video pipeline maybe provide better performance. This is working for me like outlined in my first post. Only heavy scaling could be a problem as the support for hardware scaling has just landed in 5.4. I don`t know if ffmpeg has support for it (so Kodi can profit), gstreamer1 can use it already.
You unfortunately did not gave enough information to help you any further. -
Wondering what this is all about. Out of curiosity I downloaded Armbian_5.98_Cubox-i_Debian_buster_next_5.3.1_minimal.7z and took a look. The bare image does indeed not boot on my Hummingboard. Ok, lets copy over the fedora /usr/lib/modules/5.3.0-0.rc1.git0.1.fc30.armv7hl directory. As I have long time not tinkered with boot.cmd, boot.scr lets switch over to distro boot and drop in an /boot/extlinux/extlinux.conf.
Wow, the armbian uboot recognized it, but with missing DTB autoselect this is not of much use. Replace the uboot with a mainline one like used by fedora.
Now the image is properly starting up with HDMI support working. Dropping in a stanza for the image provided kernel confirms the 5.3.1 kernel gets stuck early while booting. A kernel from the Armbian_5.94_Cubox-i_Debian_buster_next_5.2.10_minimal.7z is properly booting, but only usable via serial console. The HDMI support seems to be missing. I ended up with the attached extlinux.conf. As I had to collect the armbian kernel command line parameters manually, there is a possibility I messed something up. But none of them should prevent booting up the kernel. -
3 hours ago, Igor said:
Can you provide a kernel configuration of that build.
The current fedora kernel config is here: https://src.fedoraproject.org/rpms/kernel/blob/master/f/kernel-armv7hl.config
-
Quote10 hours ago, v-man said:
under Weston... only Kodi worked, and only with 720p material the CPU usage was not 100%
You wrote that Kodi does not perform for you under Weston. Out of curiosity, with the kodi-gbm package installed, how does Kodi perform launched by a text console user in a virtual terminal. The user should be a member of the video, audio and input group.
Problem configuring CUPS
in Beginners
Posted
OK, now that you described your network topology in more detail it is obvious what is going on.
Your router does not connect the WiFi and Ethernet segment in bridged mode but handles them as two separate segments where routing takes place and firewall rules get applied. Ports for service discovery (mdns) and LPR (printer) seem to be enabled already but for ipp-everywere or aiprint (ipp) are not.
With all properly setup and cups-browsed from the cups-filters package running there should be no user intervention be required to add the printer. cups-browsed will discover it, setup a suitable queue and in applications it will show up as printer to use.