Bug#220511: X -configure crash
Thanks for your reply :D
I got X to work using supervesafb and the fb driver in X..
regards,
//Martin
On Thu, Nov 13, 2003 at 01:51:48PM -0500, Branden Robinson wrote:
> retitle 220511 xserver-xfree86: PCI database doesn't recognize Trident 0x2100
> severity 220511 normal
> tag 220511 + upstream
> thanks
>
> On Thu, Nov 13, 2003 at 03:02:08AM +0100, Martin Kihlgren wrote:
> > Package: xserver-xfree86
> >
> > I ran X -configure and got a crash. The XFree86.log.0 is attached.
>
> It was less a crash than a deliberate abort. Yes, I know the message
> immediately afterwards calls it a crash. That's in a different function
> that doesn't know the difference.
>
> > XFree86 has found a valid card configuration.
> > Unfortunately the appropriate data has not been added to xf86PciInfo.h.
> > Please forward 'scanpci -v' output to XFree86 support team.
> >
> > I was asked to run scanpci -v. The output of that is also attached.
>
> The Linux kernel's PCI database doesn't know what your videocard is,
> either:
>
> > pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1023 device 0x2100
> > Trident Device unknown
> > CardVendor 0x1179 card 0x0002 (Toshiba, Card unknown)
> > STATUS 0x0230 COMMAND 0x0007
> > CLASS 0x03 0x00 0x00 REVISION 0x91
> > BIST 0x00 HEADER 0x00 LATENCY 0x08 CACHE 0x00
> > BASE0 0xf0000000 addr 0xf0000000 MEM
> > BASE1 0xefc00000 addr 0xefc00000 MEM
> > BASE2 0xe0000000 addr 0xe0000000 MEM
> > BASE3 0xdfff8000 addr 0xdfff8000 MEM
> > MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b
>
> --
> G. Branden Robinson | There's nothing an agnostic can't
> Debian GNU/Linux | do if he doesn't know whether he
> branden@debian.org | believes in it or not.
> http://people.debian.org/~branden/ | -- Graham Chapman
--
###################################################################
blithwapping:
Using anything BUT a hammer to hammer a nail into the
wall, such as shoes, lamp bases, doorstops, etc.
-- "Sniglets", Rich Hall & Friends
###################################################################
Reply to: