Change
BusID "0:0x08:0"
To
BusID "0:08:0"
It has
Bus id's are decimal and should only contain digits and colons in the id
part.
The x in the Busid causes the parser to error.
John
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of Nicholas Gibson
> Sent: 19 December 2004 15:23
> To: [EMAIL PROTECTED]
> Subject: Re: [ivtv-devel] [X-Drviver] V0.7 xdriver source
>
> Before I started using this new driver X would start
> up. Now I get the following error: What would I
> change to fix this, lspci reports 00:08.0 as the
> busid. I have also attached my xorg.cong.
>
> Loading /usr/X11R6/lib/modules/input/keyboard_drv.o
> (II) Module keyboard: vendor="X.Org Foundation"
> compiled for 6.8.1, module version = 1.0.0
> Module class: X.Org XInput Driver
> ABI class: X.Org XInput driver, version 0.4
> (II) IVTVDEV: driver for framebuffer: PVR-350
> (II) Primary Device is: PCI 01:00:0
> (WW) ivtvdev: No matching Device section for instance
> (BusID PCI:0:8:0) found
> (EE) No devices detected.
>
> Fatal server error:
> no screens found
>
> Please consult the The X.Org Foundation support
> at http://wiki.X.Org
> for help.
> Please also check the log file at
> "/var/log/Xorg.0.log" for additional informati
> on.
>
>
> --- John Harvey <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > Attached is my V0.7 xdriver source code.
> > There are no performance changes just some
> > configuration things
> >
> > 1) restore use of fbdev to indicate frame buffer
> > device to use
> > 2) The probe routine now uses an ivtvfb ioctl to try
> > and ensure the fb
> > device we open is actually ivtv
> > 3) The initialisation code is more like most other
> > pci card drivers rather
> > than the more generic framebuffer initialisation.
> > This stops it trying to
> > initialise itself in a bad way if BusID's go wrong.
> > And means we get better
> > more helpful error messages
> > 4) It now uses the installed ivtv.h for definitions
> > of the ivtv ioctl's
> > 5) Because of 4 I needed to remove -ansi from the
> > compile line since ivtv's
> > header does not compile in strict ansi mode
> >
> > I think that's it.
> > I will send a second mail with a pre-compiled
> > binary.
> >
> >
>
> > ATTACHMENT part 2 application/x-compressed
> name=XFree86-4.3-incr-DMA-07.tgz
>
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
ivtv-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
