Re: Fujitsu P7010 drm problems.

Gianmarco Giovannelli <[email protected]>
Newsgroups gmane.os.freebsd.devel.mobile
Message-ID <[email protected]>
At 22.40 03/01/2006, you wrote:

 >> > > agp0: <Intel 82855GME (855GME GMCH) SVGA controller> port 0x2430-0x2437
 >> > > mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 11 at device 2.0 on
 >> > > pci0 detected 8060k stolen memory
 >> > > aperture size is 128M
 >> [...]
 >> drmOpenDevice: node name is /dev/dri/card0
 >> drmOpenDevice: open result is -1, (No such file or directory)
 >> drmOpenDevice: open result is -1, (No such file or directory)
 >> drmOpenDevice: Open failed
 >> drmOpenDevice: node name is /dev/dri/card0
 >> drmOpenDevice: open result is -1, (No such file or directory)
 >> drmOpenDevice: open result is -1, (No such file or directory)
 >> drmOpenDevice: Open failed
 >> [drm] failed to load kernel module "i915"
 >> (II) I810(0): [drm] drmOpen failed
 >> (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.
 >
 >That part I don't know.  You can try asking anholt@.  I thought he 
might have
 >merged all the fixes back to RELENG_6 already though.

I have a lifebook p7010 too and i915 is working if and only if:

- you use a 7-current or apply this hack: 
ftp://213.85.11.250/pub/drm3.patch and recompile the kernel :-)
- you use the plain xorg 6.8.2 not the snapshoot one
- you use the dri-devel port not the plain one :-)

if you use all of this things, everything is working and glxgears 
show a 700-800fps

There was a very long discussion in -stable with subject i915 about 
this thread: things seems to work for i855GM but not for i915 (yet).







Best Regards,
Gianmarco Giovannelli ,  "Unix expert since yesterday"
http://utenti.gufi.org/~gmarco/

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.