/And you should be good to go!/
Nope :( Same error... X still looking at 01:00:0 for the Hauppauge
instead of 07:05:0. Strangely, it does say the 350's chipset was found:
(II) IVTVDEV_TST: driver for framebuffer: PVR-350
(II) Primary Device is: PCI 01:00:0
(--) Chipset PVR-350 found
(EE) ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device (null)
(EE) Screen 0 deleted because of no matching config section.
(II) UnloadModule: "ivtvdev"
(EE) Device(s) detected, but none match those in the config file.
Ricardo Lugo wrote:
On Apr 28, 2007, at 6:54 AM, Paul van Gerven wrote:
*The xorg.conf that crashes X:*
<snip>
Section "Device"
Identifier "HauppaugePVR"
Driver "ivtvdev"
Option "ivtv" "/dev/fb1"
Option "VideoOverlay" "on"
Option "XVideo" "1"
BusID "PCI:7:5:0"
Right here! Your BusID isn't supposed to include the word "PCI"... it
should just read:
BusID "7:5:0"
And you should be good to go!
- Rick
EndSection
Section "Screen"
Identifier "Hauppauge"
Device "HauppaugePVR"
Monitor "PALTV"
DefaultDepth 24
DefaultFbbpp 32
Subsection "Display"
Depth 24
FbBpp 32
EndSubsection
EndSection
Ricardo Lugo wrote:
On Apr 27, 2007, at 6:58 AM, Paul van Gerven wrote:
/To find your BusID for certain, kill all instances of X and run
this command as root:/
/
/
/ X -scanpci
/When Im not in X, the output defaults to the TV for some reason.
In itself not a problem, except the output of "X -scanpci" does not
fit on the screen and I cannot read the BusIDs. Would "X -scanpci |
tee scanpci" work so I can read the output later?
I'm not sure if the output is std out or std err. You could always
ssh into the machine.
/IVTVFB_IOCTL_GET_STATE means you probably put the wrong # for
"/dev/fb#" under Option "ivtv". Make sure you modprobe ivtv-fb
before starting X, too.
/The # is from cat /proc/fb. 0 is the VESA buffer I load with grub,
1 is the TV out. Should be the right one. How do I modprobe ivtv-fb
before starting X? (Now it's just in my /etc/modules file).
Well, you got it right, and the module has loaded. Can you post your
entire Xorg.0.log and xorg.conf files? That should shed some light.
Also, some documentation insists to use "fbdev" instead of "ivtv".
How about that?
I believe it is Option "ivtv" but I just realized I'm using "fbdev".
Who knows! The important thing is Driver "ivtvdev".
Ricardo Lugo wrote:
On Apr 25, 2007, at 1:09 PM, Paul van Gerven wrote:
/so theoretically you should only need to turn off menu drawing
with OpenGL and then the ubutnutu howto should work
/
Unfortunately, it does not. When I edited xorg.conf and restarted
X, both monitor and TV go blank. Checking out Xorg.0.log revealed
that X apparently found the Hauppauge chipset at the pci-adress of
the Nvidia-graphics card and obviously ran into a fatal error
(something with IVTVFB_IOCTL_GET_STATE device (null)). I entered
the correct BusID's, so I am at a loss why X would confuse them.
The error gives a few hits on google, but none are very useful.
------------------------------------------------------------------------
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
