I run Gentoo as well, and I think I was getting those FBxxx errors as
well when I was using the version of ivtv in portage, however it never
prevented my system from working.
You might want to look elsewhere for the problem at hand. Are you sure
you're sending the signal out the correct port? Try a 'ivtvctl -N' and
'ivtvctl -L' for a sanity check.
Daniel
Matt Salerno wrote:
Gentoo 2005.1
Xorg 6.8.2-r1
ivtv: version 0.2.0 (rc3j)
I have read just about every howto I could find, but I cannot get X
out though the pvr-350. I have used the supplied X driver from the
source, I have compiled my own X driver, with video=vc:64-64 appended
to my kernel parameters and without, every time I get the same
results.
Using vt 7
bitsPerPixel=32, depth=24, defaultVisual=TrueColor
mask: ff0000,ff00,ff, offset: 16,8,0
(EE) IVTVDEV(0): FBIOBLANK: Invalid argument
(EE) IVTVDEV(0): FBIOPAN_DISPLAY: Invalid argument
(EE) IVTVDEV(0): FBIOBLANK: Invalid argument
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signal 11. Server aborting
I have run out of ideas, and I need some assistance.
Rather than flooding this list with my config files and logs, here are
the links.
modules
http://vagabond.homeip.net/modules.txt
Xorg.txt
http://vagabond.homeip.net/Xorg.txt
startx
http://vagabond.homeip.net/startx.txt
dmesg
http://vagabond.homeip.net/dmesg.txt
xorg.conf
http://vagabond.homeip.net/xorg.conf
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
