Summary: | ivtv-0.2.0-rc3 and xorg-6.8.0-r3 dual head not working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jesse Adelman <jesse> |
Component: | New packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
Status: | RESOLVED LATER | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://ivtv.sourceforge.net | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Example of dmesg output using single-head xorg.conf
The "good" xorg.conf (single-head) An example "bad" dmesg-01 An example "bad" dmesg-02 An example "bad" dmesg-03 The "bad" xorg.conf (dual-head) The "bad" xorg.conf (nv drivers; dual-head) An example "bad" dmesg-04 (with nv driver) An example "bad" dmesg-05 (with nv driver; after reboot) An example "bad" Xorg.0.log (nv drivers; after reboot) |
Description
Jesse Adelman
2004-12-09 17:02:59 UTC
Created attachment 45648 [details]
Example of dmesg output using single-head xorg.conf
Created attachment 45649 [details]
The "good" xorg.conf (single-head)
Created attachment 45650 [details]
An example "bad" dmesg-01
Created attachment 45651 [details]
An example "bad" dmesg-02
Created attachment 45652 [details]
An example "bad" dmesg-03
Created attachment 45653 [details]
The "bad" xorg.conf (dual-head)
Gah... should read "xorg-x11-6.8.0-r3", not "-r4". Sorry. Okay, I talked to the Gentoo x guy(s) on this. They suggested you try with the regular nv module instead of the nvidia module. I don't know much about non-xinerama dual head setups, so I'm kind of flying blind here. Thank you, Brian. I'll do it tomorrow, as my s.o. and I are watching TV ;). Created attachment 45707 [details]
The "bad" xorg.conf (nv drivers; dual-head)
Created attachment 45708 [details]
An example "bad" dmesg-04 (with nv driver)
Created attachment 45709 [details]
An example "bad" dmesg-05 (with nv driver; after reboot)
Created attachment 45710 [details]
An example "bad" Xorg.0.log (nv drivers; after reboot)
OK, tried the nv drivers, with similar results to the proprietary nvidia drivers. At least today I've captured an actual kernel oops in a dmesg output file (if that's any help). It really appears to be a problem with ivtv-fb, but that's just a guess. This bug screams too much, especially since it is an "edge case" problem - downgrading from "Critical" to "Normal". There are new versions of ivtv, both 0.2 (stable) and 0.3 (devel), which might fix this issue. http://www.ivtv.tv/ is Chris Kennedy's new site. I just sent him a big box of black tape for his skateboard, so maybe it's time for a version bump in Portage ;)? maybe we can revisit this for later when the ivtv drivers grow up a little bit Also there has been some work recently on yuv decoding, so there may be some ivtvdev X driver changes coming soon |