Re: [Gumstix-users] 'Caspa camera boards' - Kernel panic

[Gonçalo B. <gon...@gm...>]

export DISPLAY=:0.0
mplayer tv:// -tv driver=v4l2:device=/dev/video0 -x 480 -y 272 -vo x11

seems to have solved the problem for now. thanks!

2011/7/5 Gonçalo Bernardo <gon...@gm...>

> ok. my error: here
> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards i missed the
> bit 'replace the kernel and modules of an existing image'.
>
> so, this partially worked:
> - http://www.gumstix.org/create-a-bootable-microsd-card.html Create a
> bootable MicroSD card
> - load it with this
> http://cumulus.gumstix.org/images/angstrom/factory/2011-03-25-1619/pre-built image
> - replace some files as explained in
> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards
> - configure the LCD touchscreen
>
> now, when i run:
> mplayer tv:// -tv driver=v4l2:device=/dev/video0
>
> a led in the camera does flash. however the terminal gives:
>
> //---------------------------------------
> MPlayer UNKNOWN-4.3.3 (C) 2000-2010 MPlayer Team
>
> Playing tv://.
> TV file format detected.
> Selected driver: v4l2
>  name: Video 4 Linux 2 input
>  author: Martin Olschewski <ols...@zp...>
>  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: omap3/mt9v032//
>  Capabilities:  video capture  streaming
>  supported norms:
>  inputs: 0 = camera;
>  Current input: 0
>  Current format: YUYV
> 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 query control failed: Invalid argument
> v4l2: ioctl query control failed: Invalid argument
> ==========================================================================
> Opening video decoder: [raw] RAW Uncompressed Video
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> VDecoder init failed :(
> Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
> Selected video codec: [ffrawyuy2] vfm: ffmpeg (RAW YUY2)
> ==========================================================================
> Audio: no sound
> Starting playback...
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
> Movie-Aspect is undefined - no prescaling applied.
> VO: [xv] 752x480 => 752x480 Packed YUY2
> Source image dimensions are too high: 752x480 (maximum is 480x272)
> FATAL: Cannot initialize video driver.
>
> FATAL: Could not initialize video filters (-vf) or video output (-vo).
>
> v4l2: ioctl set mute failed: Invalid argument
> v4l2: 10 frames successfully processed, 18 frames dropped.
>
> Exiting... (End of file)
> ---------------------------------------//
>
> any idea on how to fix this?
>
>
>
> On Tue, Jul 5, 2011 at 2:09 PM, Phillip Jones <pjo...@gm...> wrote:
>
>> close. modify mmcargs instead of mmcboot. (at least, that's what worked
>> for me).
>> -Phillip
>>
>>
>> 2011/7/5 Gonçalo Bernardo <gon...@gm...>:
>> > Modified the mmcboot envvar using the command editenv to:
>> >
>> > mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr};
>> > init=/init
>> >
>> > however the problem persists. any more ideas?
>> >
>> > On Tue, Jul 5, 2011 at 2:10 AM, Phillip Jones <pjo...@gm...>
>> wrote:
>> >>
>> >> Hi,
>> >> I went through this a couple days ago. I don't have my gumstix handy
>> >> right now, so my memory will be inexact, but hopefully can help you
>> >> out.
>> >>
>> >> At one point during boot up, you can pause the boot process by hitting
>> >> a key, do that.
>> >>
>> >> issue command "printenv"
>> >>
>> >> This will show several variables, including a variable for boot
>> >> options -- one for NAND boot and one for mmc card boot. (sorry, can't
>> >> remember the exact name offhand). You need to add "init=/init" to the
>> >> appropriate variable. something like, "setenv bootopt=$bootopt
>> >> init=/init"
>> >>
>> >> "printenv" again to verify that the line was changed correctly.
>> >>
>> >> Then issue the command to boot and you're good to go.
>> >>
>> >> -Phillip
>> >>
>> >>
>> >> 2011/7/4 Gonçalo Bernardo <gon...@gm...>:
>> >> > Dear all,
>> >> >
>> >> > (apologies for possible duplication. couldn't find anything about
>> this
>> >> > on
>> >> > the archives tough)
>> >> >
>> >> > I am trying to go down this tutorial
>> >> > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards .
>> >> > I got a booting kernel but then this output is shown:
>> >> >
>> >> > //--------------------------------------
>> >> > Waiting for root device /dev/mmcblk0p2...
>> >> > mmc0: host does not support reading read-only switch. assuming
>> >> > write-enable.
>> >> > mmc0: new high speed SDHC card at address 0001
>> >> > mmcblk0: mmc0:0001 00000 7.60 GiB
>> >> >  mmcblk0: p1 p2
>> >> > kjournald starting.  Commit interval 5 seconds
>> >> > EXT3-fs (mmcblk0p2): using internal journal
>> >> > EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
>> >> > VFS: Mounted root (ext3 filesystem) on device 179:2.
>> >> > devtmpfs: error mounting -2
>> >> > Freeing init memory: 940K
>> >> > Kernel panic - not syncing: No init found.  Try passing init= option
>> to
>> >> > kernel. See Linux Documentation/init.txt for guidance.
>> >> > --------------------------------------//
>> >> >
>> >> > I've seen here
>> >> > http://www.gumstix.org/create-a-bootable-microsd-card.html
>> >> > that an MLO and an u-boot.bin files are needed. As those are not
>> >> > provided
>> >> > I'm not putting them in the SDcard.
>> >> >
>> >> > Does any of you have a suggestion for this?
>> >> >
>> >> > Thanks in advance,
>> >> > gonber
>> >> >
>> >> >
>> >> >
>> ------------------------------------------------------------------------------
>> >> > All of the data generated in your IT infrastructure is seriously
>> >> > valuable.
>> >> > Why? It contains a definitive record of application performance,
>> >> > security
>> >> > threats, fraudulent activity, and more. Splunk takes this data and
>> makes
>> >> > sense of it. IT sense. And common sense.
>> >> > http://p.sf.net/sfu/splunk-d2d-c2
>> >> > _______________________________________________
>> >> > gumstix-users mailing list
>> >> > gum...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> All of the data generated in your IT infrastructure is seriously
>> valuable.
>> >> Why? It contains a definitive record of application performance,
>> security
>> >> threats, fraudulent activity, and more. Splunk takes this data and
>> makes
>> >> sense of it. IT sense. And common sense.
>> >> http://p.sf.net/sfu/splunk-d2d-c2
>> >> _______________________________________________
>> >> gumstix-users mailing list
>> >> gum...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>> >
>> > --
>> > .::Gonber::.
>> >
>> >
>> ------------------------------------------------------------------------------
>> > All of the data generated in your IT infrastructure is seriously
>> valuable.
>> > Why? It contains a definitive record of application performance,
>> security
>> > threats, fraudulent activity, and more. Splunk takes this data and makes
>> > sense of it. IT sense. And common sense.
>> > http://p.sf.net/sfu/splunk-d2d-c2
>> > _______________________________________________
>> > gumstix-users mailing list
>> > gum...@li...
>> > https://lists.sourceforge.net/lists/listinfo/gumstix-users
>> >
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> gumstix-users mailing list
>> gum...@li...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>
>
>
> --
> .::Gonber::.
>



-- 
.::Gonber::.