how to make bt878 + ccd b/w camera work together
by Dr. Michael J. Chudobiak
Can someone give me some guidance on viewing the output of CCD
surveillance/astronomy cameras?
I have a low-light PC164C-EX black and white "high resolution" CCD
camera that I would like to use with a bt878-based PV-143PA 4-port
capture card. More info here:
http://www.supercircuits.com/index.asp?PageAction=VIEWPROD&ProdID=4167
http://www.bluecherry.net/store/catalog/index.php?main_page=product_info&...
How can I use mplayer or something similar to view the composite video
output of this camera? Do I need special modprobe.conf entries? I've
tried commands like:
mplayer -tv driver=v4l:norm=ntsc:input=3:width=352:height=240 -double
-vo sdl tv://
but all I get is static. (input=3 is correct, and all other choices give
a screen of mostly blue).
Some diagnostics:
[root@server2 ~]# dmesg | grep bttv
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:00:04.0, irq: 201, latency: 32, mmio:
0xfeb01000
bttv0: detected: Provideo PV143A [card=105], PCI subsystem ID is aa00:1430
bttv0: using: ProVideo PV143 [card=105,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
bttv0: using tuner=-1
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
[root@server2 etc]# ll -a /dev/video0
crw-rw---- 1 root root 81, 0 Jul 22 16:28 /dev/video0
[root@server2 ~]# lspci | grep 878
00:04.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
00:04.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
[root@server2 ~]# mplayer -tv
driver=v4l:norm=ntsc:input=3:width=352:height=240 -double -vo sdl tv://
MPlayer 1.0pre7-4.0.0 (C) 2000-2005 MPlayer Team
......[snip].....
Selected device: BT878 video (ProVideo PV143)
Capabilites: capture tuner overlay clipping scales
Device type: 171
Supported sizes: 48x32 => 768x480
Inputs: 4
0: Composite0: audio camera (tuner:0, norm:ntsc)
1: Composite1: audio camera (tuner:0, norm:ntsc)
2: Composite2: audio camera (tuner:0, norm:ntsc)
3: Composite3: audio camera (tuner:0, norm:ntsc)
Using input 'Composite3'
Selected input hasn't got a tuner!
SDL: Using driver: x11
Xlib: extension "XFree86-VidModeExtension" missing on display ":1.0".
vo: X11 running at 1024x768 with depth 16 and 16 bpp (":1.0" => local
display)
==========================================================================
Opening video decoder: [raw] RAW Uncompressed Video
VDec: vo config request - 352 x 240 (preferred csp: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [sdl] 352x240 => 352x240 Planar YV12
Selected video codec: [rawyv12] vfm:raw (RAW YV12)
==========================================================================
Any suggestions would be appreciated!
- Mike
18 years, 7 months
Screen savers in FC3
by Zoran Spasojevic
Screen savers in FC3 do not start with KDE-3.2
Is there a way to fix this?
Thanks,
Zoran
18 years, 7 months
Re: Restarting the mouse after KVM switch
by David G. Miller (aka DaveAtFraud)
I've had a similar problem and I think the problem has more to do with the
mouse and/or the kvm. I typically see the problem when I either traverse
a system on the kvm that isn't in graphical mode or a port on the kvm that
doesn't have a system attached. Generally, I can get the mouse back under
Linux by switching to a different virtual console (CTRL-ALT-Fn where n is
not 1 or 7) and restarting gpm from the command line. Sometime I have to
unplug and then plug the mouse back into the kvm before restarting gpm.
This problem was absent when I was using a non-optical mouse. It only
showed up as I have replaced my mice with optical versions.
dave
--
When buying and selling are controlled by legislation, the first things bought and sold are the legislators.
-- P.J. O'Rourke
18 years, 7 months
Re: Fedora Core 3 Update: mkinitrd-4.1.18.1-1
by Damian Menscher
On Fri, 29 Jul 2005, Dave Jones wrote:
> This update should fix the issue a number of people saw
> after the recent kernel update where various modules would
> fail to load during boot, making systems unbootable.
>
> After updating this package, remove, and reinstall the
> recent kernel update, and the initrd will be recreated
> correctly.
For those of us who recognized the dangers of the new kernel and never
installed it, what is the recommended course of action? Will a simple
"up2date" that installs the new mkinitrd and the new kernel
simultaneously work? I'm guessing I should up2date the mkinitrd in one
pass, then up2date the kernel in a second pass? Some confirmation would
be nice.
> * Thu Jul 28 2005 Peter Jones <pjones(a)redhat.com> - 4.1.18.1-1
> - Make nash check pids returned from wait*() (#145660)
I would like to know exactly what bug was fixed here, and am assuming
that 145660 is a bugzilla number. But I'm "not authorized to access"
that bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145660
Since when are bug reports so secretive? I can understand making them
restricted in the case of embargoed security fixes, but that does not
apply here (or in the several other cases I've seen of unreadable
bugzilla entries.
Rather than forming a fedora-bugs triage team, how about just letting
people see what bugs already exist, so we can avoid future dupes?
Damian Menscher
--
-=#| Physics Grad Student & SysAdmin @ U Illinois Urbana-Champaign |#=-
-=#| 488 LLP, 1110 W. Green St, Urbana, IL 61801 Ofc:(217)333-0038 |#=-
-=#| 4602 Beckman, VMIL/MS, Imaging Technology Group:(217)244-3074 |#=-
-=#| <menscher(a)uiuc.edu> www.uiuc.edu/~menscher/ Fax:(217)333-9819 |#=-
-=#| The above opinions are not necessarily those of my employers. |#=-
18 years, 7 months
Web Development Tools and Environments.
by Robert Cahn
Somehow between FC2 and FC4 Quanta disappeared. What replaces it? I
want to build a web site and not really do java coding so Eclipse
doesn't seem the right tool.
/Bob Cahn
Gipsy Trail Club
Carmel, NY 10512
18 years, 7 months
vertical color bars appearing in menus
by Claude Jones
Running FC4 with KDE 3.4.2
This machine is an upgrade from FC3. In many menus, small, translucent
vertical colored bars appear over individual letters that are underlined in
menus, It first appeared everywhere after the upgrade, including in Kmenu and
most programs and even the login screen. Since then, they've disappeared
from most of the above, but they still linger in some programs and on the
login screen. Unfortunately, I have no idea what changed. For a screen grab,
you can look here:
http://www.levitjames.com/kdecolorbars.html
I logged into Gnome yesterday, and the problem persisted in a couple of
programs (Kyum is one for example). I've tried all the items in the desktop
configuration, changing styles, widgets, etc. I looked at the xorg conf file
for anything obvious. I've posted this over at KDE-Redhat but no one there is
getting it, save one individual who got rid of it by playing with his widget
settings.
Anyone else getting this?
--
Claude Jones
Bluemont, VA, USA
18 years, 8 months
Constructive critisism; room for improvement:
by Andy Pieters
HI all
I am a huge fan of Linux and Fedora in particular. I just bought another low
budget pc with windows xp on so I could test how my software (php/xml) looks
on internet explorer. Again it filled me with joy that I switched to Linux
almost a year ago, for that windows box BSODed on me within the first fifteen
minutes! (actually while trying to uninstall AOL) (BSOD=Blue Screen of Death
= Kernel Error)
Still, one thing that windows handles well are bad cd's. When a cd fails, the
whole os doesn't come crashing down. I was just ripping the cd Europe
1982-1992 on my Linux box and listening to my collection with amaroK.
Suddenly the system got in an endless loop. The 5 seconds of music in the
play buffer were repeated over and over again. I ejected the cd but that
didn't save the system. I tried also to ssh in but that wasn't possible
either. It didn't respond to pusing the poweroff button and the only
solution was forced power off.
With kind regards
Andy
--
Registered Linux User Number 379093
Now listening to Pink Floyd - Another Brick in The Wall
amaroK::the Coolest Media Player in the known Universe!
Cockroaches and socialites are the only things that can
stay up all night and eat anything.
Herb Caen
--
-- --BEGIN GEEK CODE BLOCK-----
Version: 3.1
GAT/O/>E$ d-(---)>+ s:(+)>: a--(-)>? C++++$(+++) UL++++>++++$ P-(+)>++
L+++>++++$ E---(-)@ W+++>+++$ !N@ o? !K? W--(---) !O !M- V-- PS++(+++)
PE--(-) Y+ PGP++(+++) t+(++) 5-- X++ R*(+)@ !tv b-() DI(+) D+(+++) G(+)
e>++++$@ h++(*) r-->++ y--()>++++
-- ---END GEEK CODE BLOCK------
--
Check out these few php utilities that I released
under the GPL2 and that are meant for use with a
php cli binary:
http://www.vlaamse-kern.com/sas/
--
18 years, 8 months
arTs crashes for root
by kwhiskers
This error has been from the day I first installed a clean install of FC4.
It has not bothered me, as I don't use the root profile, but I thought I
might as well report the error now.
In root only, not for other users, the following error message appears when
logging in:
"Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (Invalid argument)
The sound server will continue, using the null output device."
For other users, the sound server works fine.
I am using kde-redhat for FC4 on a clean installation of FC4.
18 years, 8 months