[Openchrome-users] K8M890 still not working

[Jon Nettleton]

On Mon, 2006-12-18 at 18:38 +0100, Thomas Hellstr?m wrote:
> Javier Smaldone wrote:
> > Hi guys.
> >
> > I'm using linux 2.6.19.1 and X.org 7.1.1 (Debian etch), the drm driver
> > from git tree and the vt3336 branch of openChrome.
> >
> > I've followed the instructions in
> > http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=K8M890 but I
> > can't get DRI to work on my K8M890.
> >
> > This is the lspci output for the device:
> >
> > 01:00.0 VGA compatible controller: VIA Technologies, Inc. Unknown
> > device 3230 (rev 11)
> >
> > On boot, the kernel says:
> >
> > agpgart: Detected VIA K8M890CE chipset
> > agpgart: AGP aperture is 128M @ 0xd0000000
> > [...]
> > [drm] Initialized drm 1.1.0 20060810
> > [drm] Initialized via 2.10.2 20060616 on minor 0:
> >
> >
> > But X.org reports:
> >
> > (II) VIA: driver for VIA chipsets: CLE266, KM400/KN400, K8M800,
> >         PM800/PM880/CN400, VM800, K8M890
> > (II) Primary Device is: PCI 01:00:0
> > (--) Chipset K8M890 found
> > [...]
> > (II) VIA(0): VIAGetRec
> > (**) VIA(0): Depth 16, (--) framebuffer bpp 16
> > (==) VIA(0): RGB weight 565
> > (==) VIA(0): Default visual is TrueColor
> > (II) VIA(0): Starting to parse config file options...
> > (==) VIA(0): ShadowFB is disabled.
> > (==) VIA(0): Acceleration is enabled.
> > (==) VIA(0): Using XAA acceleration architecture.
> > (==) VIA(0): Hardware two-color cursors.
> > [...]
> > (--) VIA(0): Chipset: "K8M890"
> > (II) VIA(0): VIAMapMMIO
> > (--) VIA(0): mapping MMIO @ 0xdd000000 with size 0x9000
> > (--) VIA(0): mapping BitBlt MMIO @ 0xdd200000 with size 0x20000
> > (II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
> > (==) VIA(0): Will not print VGA Registers.
> > (==) VIA(0): Will not scan I2C buses.
> > (==) VIA(0): Chipset Rev.: 0
> > (--) VIA(0): Detected MSI K9VGM-V.
> > [...]
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is 7, (OK)
> > (II) VIA(0): [drm] loaded kernel module for "via" driver
> > (II) VIA(0): [drm] DRM interface version 1.0
> > (II) VIA(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Invalid argument
> > (EE) VIA(0): [dri] DRIScreenInit failed.  Disabling DRI.
> >
> >
> > And then, the kernel says:
> >
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(c0106407){00} arg(ffe63ff0)
> > on /dev/dri/card0
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(c0086401){00} arg(ffe63ff4)
> > on /dev/dri/card0
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(c0246400){00} arg(082002d8)
> > on /dev/dri/card0
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(c0246400){00} arg(082002d8)
> > on /dev/dri/card0
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(c0106407){00} arg(ffe64300)
> > on /dev/dri/card0
> > ioctl32(Xorg:2876): Unknown cmd fd(7) cmd(40086410){00} arg(ffe6430c)
> > on /dev/dri/card0
> >
> > As a result, X is working fine (including mplayer with the xv driver,
> > switching to text mode, etc.), but DRI refuses to work.
> >
> > Can you help me?
> >
> >   
> Hmm,
> Could it be that you are using a 64-bit kernel with a 32-bit X server?
> 
> /Thomas
> 
*clip*

That is exactly the problem.  We have seen a lot of this.  Right now we
have confirmed working 32-bit and 64-bit only systems.  Anything with a
64-bit kernel and a 32-bit Xserver causes ioctl32 errors with drm.

Jon