sn9c291 驱动加载成功,mpayer无法播放

先目前将一个sn9c291+ov9712的模块驱动在fedora上加载成功,可是在使用mplayer却无法播放,不知道为何?

前后对比发现dev目录下多了video0,video1 设备节点已经出来,video1 是H264的节点

[[email protected] mplayer]#
mplayer tv:// -tv driver=v4l2:width=1280:height=720:device=/dev/video1:outfmt=0x34363248 -fps 24

MPlayer SVN-r37243-4.4.4 (C) 2000-2014 MPlayer Team

Playing tv://.

TV file format detected.

Selected driver: v4l2

name: Video 4 Linux 2 input

author: Martin Olschewski <[email protected]>

comment: first try, more to come ;-)

v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.

Selected device: USB 2.0 Camera

Capabilities:  video capture  streaming

supported norms:

inputs: 0 = Camera 1;

Current input: 0

Current format: YUYV

==================================================================

WARNING: UNTESTED OR UNKNOWN OUTPUT IMAGE FORMAT REQUESTED (0x34363248)

This may cause buggy playback or program crash! Bug reports will

be ignored! You should try again with YV12 (which is the default

colorspace) and read the documentation!

==================================================================

v4l2: ioctl set format failed: Invalid argument

tv.c: norm_from_string(pal): Bogus norm parameter, setting default.

v4l2: ioctl enum norm failed: Invalid argument

Error: Cannot set norm!

Selected input hasn‘t got a tuner!

v4l2: ioctl set mute failed: Invalid argument

v4l2: ioctl streamon failed: No space left on device

[VO_XV] It seems there is no Xvideo support for your video card available.

[VO_XV] Run ‘xvinfo‘ to verify its Xv support and read

[VO_XV] DOCS/HTML/en/video.html#xv!

[VO_XV] See ‘mplayer -vo help‘ for other (non-xv) video out drivers.

[VO_XV] Try -vo x11.

OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.

==========================================================================

Opening video decoder: [raw] RAW Uncompressed Video

Could not find matching colorspace - retrying with -vf scale...

Opening video filter: [scale]

Movie-Aspect is undefined - no prescaling applied.

[swscaler @ 0xb97a3a00] bicubic scaler, from yuyv422 to bgra using MMXEXT

VO: [x11] 640x480 => 640x480 BGRA

Selected video codec: [rawyuy2] vfm: raw (RAW YUY2)

==========================================================================

Audio: no sound

Starting playback...

[swscaler @ 0xb97a3a00] Warning: data is not aligned! This can lead to a speedloss

V:   0.0  31/ 31 ??% ??% ??,?% 0 0

MPlayer interrupted by signal 11 in module: video_read_frame

- MPlayer crashed by bad usage of CPU/FPU/RAM.

Recompile MPlayer with --enable-debug and make a ‘gdb‘ backtrace and

disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.

- MPlayer crashed. This shouldn‘t happen.

It can be a bug in the MPlayer code _or_ in your drivers _or_ in your

gcc version. If you think it‘s MPlayer‘s fault, please read

DOCS/HTML/en/bugreports.html and follow the instructions there. We can‘t and

won‘t help unless you provide this information when reporting a possible bug.

[[email protected] mplayer]# mplayer tv:// -tv driver=v4l2:width=1280:height=720:device=/dev/video1:outfmt=0x34363248

MPlayer SVN-r37243-4.4.4 (C) 2000-2014 MPlayer Team

Playing tv://.

TV file format detected.

Selected driver: v4l2

name: Video 4 Linux 2 input

author: Martin Olschewski <[email protected]>

comment: first try, more to come ;-)

v4l2: your device driver does not support VIDIOC_G_STD ioctl, VIDIOC_G_PARM was used instead.

Selected device: USB 2.0 Camera

Capabilities:  video capture  streaming

supported norms:

inputs: 0 = Camera 1;

Current input: 0

Current format: unknown (0x34363248)

==================================================================

WARNING: UNTESTED OR UNKNOWN OUTPUT IMAGE FORMAT REQUESTED (0x34363248)

This may cause buggy playback or program crash! Bug reports will

be ignored! You should try again with YV12 (which is the default

colorspace) and read the documentation!

==================================================================

tv.c: norm_from_string(pal): Bogus norm parameter, setting default.

v4l2: ioctl enum norm failed: Invalid argument

Error: Cannot set norm!

Selected input hasn‘t got a tuner!

v4l2: ioctl set mute failed: Invalid argument

v4l2: ioctl streamon failed: No space left on device

[VO_XV] It seems there is no Xvideo support for your video card available.

[VO_XV] Run ‘xvinfo‘ to verify its Xv support and read

[VO_XV] DOCS/HTML/en/video.html#xv!

[VO_XV] See ‘mplayer -vo help‘ for other (non-xv) video out drivers.

[VO_XV] Try -vo x11.

OpenGL Warning: Failed to connect to host. Make sure 3D acceleration is enabled for this VM.

==========================================================================

Opening video decoder: [ffmpeg] FFmpeg‘s libavcodec codec family

libavcodec version 55.71.100 (internal)

Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)

==========================================================================

Audio: no sound

Starting playback...

[h264 @ 0xb76089a0]no frame!

Error while decoding frame!

[h264 @ 0xb76089a0]no frame!

Error while decoding frame!

[h264 @ 0xb76089a0]no frame!

Error while decoding frame!

[h264 @ 0xb76089a0]no frame!

Error while decoding frame!

[h264 @ 0xb76089a0]no frame!

Error while decoding frame!

[h264 @ 0xb76089a0]no frame!

sn9c291 驱动加载成功,mpayer无法播放,布布扣,bubuko.com

时间: 2024-10-09 01:34:16

sn9c291 驱动加载成功,mpayer无法播放的相关文章

多功能PCIE交换机之八:窗口扩展和驱动加载的常见问题

结合本人在PCIE NTB/DMA最近的实际工作,总结了地址转换窗口扩展和驱动加载过程中碰到的主要问题和解决办法. 0.系统启动后看不到NTB设备 需要检查BIOS,在PCIE设置里面NTB芯片是否使能.这是因为针对不同的应用场景和客户需要,BIOS里面通常添加了Enable/Disable NTB的选项. 1.如何扩展地址转换窗口 a.确定系统要求的地址转换窗口的范围和大小: b.确保系统要求的地址转换窗口的范围和大能够被BIOS支持 c.从可用的BAR2/3和BAR4/5中选择未使用的或者可

Fresco 使用笔记(一):加载gif图片并播放

前言: 项目中图文混合使用的太多太多了,但是绝大部分都是静态图片. 然而现在项目开发中有这么一个需求:显示一个出一个简短的动画(一般都不超过3秒)演示 比如说:一个功能提供很多步骤来教用户做广播体操,那么第一步就显示一个3秒钟的动作图,第二步显示一个几秒钟的动作图.(当然这个需求不是这个功能) 怎么解决呢:一确定这个需求我的第一实现思路便是让美工给我搞几个连续的图片,我使用帧动画来轮回播放 便实现了这个动画. 但是帧动画使用起来太复杂了,一套动作我要搞好久来实现.那么就想Android中支持不支

另类阻止驱动加载

标 题: [分享][原创]另类阻止驱动加载 作 者: czcqq 时 间: 2010-05-04,22:27:47 链 接: http://bbs.pediy.com/showthread.php?t=112338 关于驱动的加载大概有几种方法 1 在WINDOWS下动态加载 2 在WINDOWS启动的时候加载 3 感染系统文件 对于 在WINDOWS启动的时候加载 和 感染系统文件 我们暂时不讨论,玩么只讨论动态加载 一般的加载流程,是这样的:打开服务管理器->创建服务->启动服务->

【ESXI6.0】 ESXI6.0安装时无法安装网卡驱动的解决方法及将网卡驱动加载进ISO

若安装时提示如下图所示 之后安装无法完成,会提示没有检测到网络适配器,如下图. 这时候需要将网卡驱动加载进ISO中才能在安装时候识别网卡驱动. 网卡驱动从这里下载: https://vibsdepot.v-front.de/wiki/index.php/List_of_currently_available_ESXi_packages 找到对应的型号.点击进入下一页下载. 需要使用如下工具: ESXi-Customizer-v2.7.2 http://pan.baidu.com/s/1eQ2f8

老调重弹:JDBC系列 之 &lt;驱动加载原理全面解析&gt;

前言 最近在研究Mybatis框架,由于该框架基于JDBC,想要很好地理解和学习Mybatis,必须要对JDBC有较深入的了解.所以便把JDBC 这个东东翻出来,好好总结一番,作为自己的笔记,也是给读者一个参考---以下是本文的组织结构,读者可以点击上面的目录查看: 概述 一般情况下,在应用程序中进行数据库连接,调用JDBC接口,首先要将特定厂商的JDBC驱动实现加载到系统内存中,然后供系统使用.基本结构图如下: 驱动加载入内存的过程 这里所谓的驱动,其实就是实现了java.sql.Driver

java访问access数据库驱动加载不正确

前几天新装了系统,做了一个从access数据库中查询内容的程序,运行的时候总是提示数据库的驱动加载不正确,网上百度的结果都是说电脑没有配置odbc数据源,或者是Driver后面空格的问题,可是我检查了之后,这些都没有错: 后来发现是新导入的java工程,程序默认了eclipse的jre system library,我就把这个默认的修改成我电脑配置的jdk后,再次运行,程序就正常了

判断ifame 是否加载成功

有的时候,需要临时判断是否加载成功和成功以后的操作. 1 var ifame = document.getElementById("mapHostel"); 2 if (ifame.attachEvent) { 3 ifame.attachEvent("onreadystatechange", function () { 4 if (ifame.readyState === "complete" || ifame.readyState == &q

(DT系列四)驱动加载中, 如何取得device tree中的属性

本文以At91rm9200平台为例,从源码实现的角度来分析驱动加载时,Device tree的属性是如何取得的.一:系统级初始化DT_MACHINE_START 主要是定义"struct machine_desc"的类型,放在 section(".arch.info.init"),是初始化数据,Kernel 起来之后将被丢弃.#define DT_MACHINE_START(_name, _namestr) \static const struct machine_

老调重弹:JDBC系列之&lt;驱动加载原理全面解析) ----转

  最近在研究Mybatis框架,由于该框架基于JDBC,想要很好地理解和学习Mybatis,必须要对JDBC有较深入的了解.所以便把JDBC 这个东东翻出来,好好总结一番,作为自己的笔记,也是给读者一个参考--- 概述 一般情况下,在应用程序中进行数据库连接,调用JDBC接口,首先要将特定厂商的JDBC驱动实现加载到系统内存中,然后供系统使用.基本结构图如下: 驱动加载入内存的过程 这里所谓的驱动,其实就是实现了java.sql.Driver接口的类.如oracle的驱动类是 oracle.j