[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#175102: ati driver and two ati cards...



On Fri, Jan 03, 2003 at 10:35:05PM +0100, Jan-Benedict Glaw wrote:
> On Fri, 2003-01-03 01:20:03 -0500, Branden Robinson <branden@debian.org>
> > > 1. 'Load "i2c"' is missing after configuration through 'dpkg-reconfigure
> > > xserver-xfree86', but some symbol of libi2c.a is needed by the radeon
> > > driver.
> > 
> > That's not necessarily fatal, as I understand it.
> 
> If I don't add it to XF86Config-4, I'll get:
> 
> (WW) RADEON: No matching Device section for instance (BusID PCI:0:14:0) found
> Symbol xf86CreateI2CBusRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved!
> Symbol xf86I2CBusInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved!
> 
> Fatal server error:
> Caught signal 11.  Server aborting

Is that exactly what shows up in XFree86.0.log?

> > Thanks.  I also need the server's log file as described in
> > XF86Config(7).
> 
> I'm sorry I forgot it. Here it is:
[...]
> (--) PCI: (0:14:0) ATI Mach64 GR rev 39, Mem @ 0xe9000000/24, 0xe800a000/12, I/O @ 0x2800/8
> (--) PCI:*(1:5:0) ATI Radeon VE QY rev 0, Mem @ 0xf0000000/27, 0xea000000/16, I/O @ 0x3000/8
[...]
> (II) Loading sub module "int10"
> (II) LoadModule: "int10"
> (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> (II) RADEON(0): initializing int10
> 
> Fatal server error:
> Caught signal 11.  Server aborting
[...]

> Whatever you think you need, ask for it:-)

Can you try disabling the int10 module, and seeing what happens?

-- 
G. Branden Robinson                |    I just wanted to see what it looked
Debian GNU/Linux                   |    like in a spotlight.
branden@debian.org                 |    -- Jim Morrison
http://people.debian.org/~branden/ |

Attachment: pgpSuQJznO0Q0.pgp
Description: PGP signature


Reply to: