Johannes
Thanks for your reply
Johannes Erdfelt wrote:
> On Wed, May 17, 2000, Jerry White <[EMAIL PROTECTED]> wrote:
> > Have 2.2.15 kernel with backpatch applied.
> > using ov511.o as driver
> > below is the message s that I get
> > please don't flame Me if the attachment is too long
> > a nice "too much" will do
>
> >
> > the below was when I started the
> > xawtv program
> >
> > May 17 09:45:07 jerry kernel: ov511: [ov511_init_isoc:1529] *** Initializing
>capture ***
> > May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size:
>993, mult=31, alt=1
> > May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> > May 17 09:45:07 jerry kernel: ov511: [ov511_stop_isoc:1604] *** Stopping capture
>***
> > May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size:
>0, mult=0, alt=7
> > May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> > May 17 09:45:07 jerry kernel: ov511: [ov511_isoc_irq:1502] hmmm... not streaming,
>but got interrupt
> > May 17 09:45:07 jerry kernel: ov511: [ov511_isoc_irq:1502] hmmm... not streaming,
>but got interrupt
> > May 17 09:45:07 jerry kernel: ov511: [ov511_init_isoc:1529] *** Initializing
>capture ***
> > May 17 09:45:07 jerry kernel: ov511: [ov511_set_packet_size:813] set packet size:
>993, mult=31, alt=1
> > May 17 09:45:07 jerry kernel: ov511: [ov511_reset:745] Reset: type=0x3F
> > May 17 09:45:08 jerry kernel: ov511: [ov511_mode_init_regs:930] width:64,
>height:48, mode:4, sub:0
> > May 17 09:45:08 jerry kernel: ov511.c: Unknown mode (64, 48): 4
WHAT DOES THE ABOVE TELL US???
>
> > May 17 09:45:09 jerry kernel: ov511: [ov511_mode_init_regs:930] width:320,
>height:240, mode:4, sub:0
> > May 17 09:45:09 jerry kernel: ov511: [ov511_mode_init_regs:930] width:320,
>height:240, mode:4, sub:0
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [3]
>len=201, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7]
>len=393, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [8]
>len=652, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2]
>len=714, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [4]
>len=76, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5]
>len=843, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7]
>len=137, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [8]
>len=716, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [0]
>len=268, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [1]
>len=779, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5]
>len=139, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7]
>len=649, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [0]
>len=204, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2]
>len=714, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [1]
>len=139, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [5]
>len=587, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [7]
>len=585, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2]
>len=522, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [3]
>len=521, status=-63
> > May 17 09:45:12 jerry kernel: ov511: [ov511_move_data:1348] data error: [2]
>len=202, status=-63
>
> This is where the problem is.
>
> -63 = -ENOSR = TD_CTRL_DBUFERR is set
>
> All of that means "Data Buffer Error". In this case, there was an
> overrun writing data to system memory. I've never actually seen this
> error generated before.
>
> This sounds like a hardware problem. Could you give us a description of
> your hardware?
>
EP-58MVP3C-m EPOX board about 1 year old
AMD K6-II with 3d Now running @ 350Meg NOT overclocked.
Big Foot Quntram 8.4 Gig drive
Mustek 600 III Plus Scanner
HP DeskJet 694C Printer
AGP video card with mach 64 driver
17" Mag monitor
1 Realteck ethernet card hooked up to a small network 2 machines
96 Meg pc100 memory
1 CD Rom old 16x read
ALSO when I first call xawtv the following is displayed in konsole
This is xawtv-3.14 running on Linus/i586 (2.2.15)
visual: Id=0x20 class =4 (true color), depth =24
x11: 1024x768 32bit pixel , 4096 byte/scanline , DGA
/dev/video: no overlay support
waitpid: No child processes
v4l-conf had some trouble, trying to continue anyway
/dev/video: no overlay support
waitpid: No child processes
v4l-conf had some trouble, trying to continue anyway
wmhooks: kde
ioctl VIDIOCAPTURE(0,-,0X0): Invalid argument
ioctl VIDIOCAPTURE(1,-,0X0): Invalid argument
ioctl VIDEOSYNC: Invalid argument
ioctl VIDEOSYNC: Invalid argument
ioctl VIDIOCAPTURE(0,-,0X0): Invalid argument
ioctl VIDIOCAPTURE(1,-,0X0): Invalid argument
ioctl VIDEOSYNC: Invalid argument
ioctl VIDEOSYNC: Invalid argument
Then the picture comes Up and the message buffer starts to fill up
reached 6 or 7 Megs in size in a very short time. b4 i closed xawtv.
Hope this helps.
I also tried using kernel-3.3.99-Pre-8 but crashed b4 booting
also used 2.2-14 with backport patch.
>
> Is this machine typically busy?
>
Usually running KDE with 8 windows number of apps in but NOT actually running
A NOTE HERE
When My hard drive is running there are a lot of
"flash" lines going across the pic which is selected as
320x 240
when I try 640x480 size picture is very washed out.
pic quality is "pretty" good at smaller size.
When I compiled ov511.o IN kernel it NEVER did get detected.
would only work as module inserted after done booting and installing
as root.
>
> JE
Thanks
Jerry W White
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
