aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/video4linux/bttv/PROBLEMS
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-04-16 18:20:36 -0400
commit1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch)
tree0bba044c4ce775e45a88a51686b5d9f90697ea9d /Documentation/video4linux/bttv/PROBLEMS
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
Diffstat (limited to 'Documentation/video4linux/bttv/PROBLEMS')
-rw-r--r--Documentation/video4linux/bttv/PROBLEMS62
1 files changed, 62 insertions, 0 deletions
diff --git a/Documentation/video4linux/bttv/PROBLEMS b/Documentation/video4linux/bttv/PROBLEMS
new file mode 100644
index 000000000000..8e31e9e36bf7
--- /dev/null
+++ b/Documentation/video4linux/bttv/PROBLEMS
@@ -0,0 +1,62 @@
1- Start capturing by pressing "c" or by selecting it via a menu!
2
3- Start capturing by pressing "c" or by selecting it via a menu!!!
4
5- The memory of some S3 cards is not recognized right:
6
7 First of all, if you are not using XFree-3.2 or newer, upgrade AT LEAST to
8 XFree-3.2A! This solved the problem for most people.
9
10 Start up X11 like this: "XF86_S3 -probeonly" and write down where the
11 linear frame buffer is.
12 If it is different to the address found by bttv install bttv like this:
13 "insmod bttv vidmem=0xfb0"
14 if the linear frame buffer is at 0xfb000000 (i.e. omit the last 5 zeros!)
15
16 Some S3 cards even take up 64MB of memory but only report 32MB to the BIOS.
17 If this 64MB area overlaps the IO memory of the Bt848 you also have to
18 remap this. E.g.: insmod bttv vidmem=0xfb0 remap=0xfa0
19
20 If the video memory is found at the right place and there are no address
21 conflicts but still no picture (or the computer even crashes),
22 try disabling features of your PCI chipset in the BIOS setup.
23
24 Frank Kapahnke <frank@kapahnke.prima.ruhr.de> also reported that problems
25 with his S3 868 went away when he upgraded to XFree 3.2.
26
27
28- I still only get a black picture with my S3 card!
29
30 Even with XFree-3.2A some people have problems with their S3 cards
31 (mostly with Trio 64 but also with some others)
32 Get the free demo version of Accelerated X from www.xinside.com and try
33 bttv with it. bttv seems to work with most S3 cards with Accelerated X.
34
35 Since I do not know much (better make that almost nothing) about VGA card
36 programming I do not know the reason for this.
37 Looks like XFree does something different when setting up the video memory?
38 Maybe somebody can enlighten me?
39 Would be nice if somebody could get this to work with XFree since
40 Accelerated X costs more than some of the grabber cards ...
41
42 Better linear frame buffer support for S3 cards will probably be in
43 XFree 4.0.
44
45- Grabbing is not switched off when changing consoles with XFree.
46 That's because XFree and some AcceleratedX versions do not send unmap
47 events.
48
49- Some popup windows (e.g. of the window manager) are not refreshed.
50
51 Disable backing store by starting X with the option "-bs"
52
53- When using 32 bpp in XFree or 24+8bpp mode in AccelX 3.1 the system
54 can sometimes lock up if you use more than 1 bt848 card at the same time.
55 You will always get pixel errors when e.g. using more than 1 card in full
56 screen mode. Maybe we need something faster than the PCI bus ...
57
58
59- Some S3 cards and the Matrox Mystique will produce pixel errors with
60 full resolution in 32-bit mode.
61
62- Some video cards have problems with Accelerated X 4.1