From: Ulrich v. Z. <ulr...@ar...> - 2007-02-28 14:31:12
|
Hi, I'm trying to get i915tex running on a gentoo machine here. Currently, /usr/lib/dri/i915tex_dri.so exists but isn't selected by X: (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so How does X determine whether to use i915 or i915tex? What are minimum software versions? I've got: mesa-6.5.2 libdrm-2.3.0 xorg-server-1.1.1 kernel 2.6.19 Thanks for any help, Uli -- Ulrich von Zadow | Software Development Unit Head ART+COM AG | Kleiststr. 23-26 | 10787 Berlin | Germany phone: +49.30.21001-464 | fax: +49.30.21001-555 HRB 68308 | Amtsgericht Charlottenburg Vorstand: Andreas Wiek, Sebastian Peichl Aufsichtsratsvorsitzender: Volker Tietgens USt-IdNr.: DE811998328 |
From: Sergio M. B. <se...@se...> - 2007-07-27 00:21:52
Attachments:
smime.p7s
|
Since last email about this subject (3 of July) , I had installed i915tex on my laptop , and I had working without problems . Michel suggest when install linux-agp-compat instead of delete Module.symvers=20 I append the Module(s).symvers file generated by linux-agp-compat to the kernel's file of the same name with cat >> before building the DRM. And works quite well. So this could be add mesa/linux-agp-compat/README 2nd - will linux-agp-compat enter in kernel main stream ?=20 Thanks,=20 --=20 S=C3=A9rgio M.B. |
From: Brian P. <bri...@tu...> - 2007-07-27 14:17:03
|
Sergio Monteiro Basto wrote: > Since last email about this subject (3 of July) , I had installed > i915tex on my laptop , and I had working without problems . > > Michel suggest when install linux-agp-compat instead of delete > Module.symvers > I append the Module(s).symvers file generated by linux-agp-compat > to the kernel's file of the same name with cat >> before building the > DRM. > And works quite well. > So this could be add mesa/linux-agp-compat/README Done. > 2nd - will linux-agp-compat enter in kernel main stream ? I'm not too familiar with this stuff but that sounds like a good idea. -Brian |
From: Sergio M. B. <se...@se...> - 2007-07-28 02:14:22
Attachments:
smime.p7s
|
On Fri, 2007-07-27 at 01:25 +0100, Dave Airlie wrote:=20 > > > > 2nd - will linux-agp-compat enter in kernel main stream ? >=20 > It's been in the kernel for a while.. >=20 > 2.6.21 has it but I've no idea when it went in.. hum ! If kernel 2.6.22 have it, I am missing something, I had test with one kernel 2.6.22 and I am seeing one configuration of kernel 2.6.23-git22 and I don't see any linux-agp-compat or it is supposed be on AGP_INTEL ? . I had try enable i915tex, with kernel 2.6.22 and with git drm/linux-core compiled against this kernel, but don't enable i915tex. I don't understand this, If we have mesa/linux-agp-compat on kernel, drm should work out of the box, no?. kernel have one drm that could enable i915tex. btw, I have an compiling error when I compile linux-agp-compat against kernel-2.6.22.1-33.fc7 "custom" or 2.6.23-rc1 =20 Thanks, --=20 S=C3=A9rgio M. B. |
From: Sergio M. B. <se...@se...> - 2007-07-28 19:30:56
Attachments:
smime.p7s
|
On Sat, 2007-07-28 at 04:54 +0100, Dave Airlie wrote: > > hum ! If kernel 2.6.22 have it, I am missing something, > > I had test with one kernel 2.6.22 and I am seeing one configuration of > > kernel 2.6.23-git22 and I don't see any linux-agp-compat or it is > > supposed be on AGP_INTEL ? . > > >=20 > It's in 2.6.21 and later, it is just a part of agp, nothing special about= =20 > compat or otherwise, I haven't used linux-agp-compat in a while. >=20 > a030ce4477baa06dd9c037ccd3c8d171aac9ed44 >=20 > is the kernel git commitid >=20 > > I had try enable i915tex, with kernel 2.6.22 and with git drm/linux-cor= e > > compiled against this kernel, but don't enable i915tex. ah ! with kernel 2.4.22 I have this message=20 (II) intel(0): direct rendering: Enabled (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (EE) intel(0): Could not initialize the DRM memory manager. (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0xe0320000 at 0xb7fd2000 (--) RandR disabled now I see 3 different bugs=20 1 - drm last git drm don't work 2 - last git xf86-video-intel have problem with video out xv=20 3 - the kernel 2.4.22 gives this problem. =20 I put xf86-video-intel with version 2.0.0-4 from fedora I done a git reset bc7d6c76fab2ff4d2f11b6bd84ca8b8f124729fd on git drm compile linux-agp-compat and drm on kernel 2.4.20=20 and enable i915tex ! . reboot and use kernel 2.6.22=20 compile the same drm code against kernel 2.4.22 and after reboot again=20 I got the above message . I have to go=20 I waste many time to unreset the reset, I don't handle git very well and lose many time with it :( Thanks,=20 --=20 S=C3=A9rgio M. B. |
From: Sergio M. B. <se...@se...> - 2007-07-31 08:24:16
Attachments:
smime.p7s
|
On Sat, 2007-07-28 at 04:54 +0100, Dave Airlie wrote: > It's in 2.6.21 and later, it is just a part of agp, nothing special > about=20 > compat or otherwise, I haven't used linux-agp-compat in a while. >=20 > a030ce4477baa06dd9c037ccd3c8d171aac9ed44 >=20 > is the kernel git commitid >=20 > > I had try enable i915tex, with kernel 2.6.22 and with git > drm/linux-core > > compiled against this kernel, but don't enable i915tex. ok, I forgot update libdrm, for git drm it is need libdrm bigger than 3.2.0, in this case latest git.=20 After update libdrm, things get to normal. And kernel 2.6.22 enable i915tex. which for me is a good new because I don't have to recompile kernel again and can use the stock kernel given by distros. Thanks, >=20 > Dave.=20 --=20 S=C3=A9rgio M. B. |
From: Sergio M. B. <se...@se...> - 2007-08-07 00:48:35
|
On Fri, 2007-07-27 at 08:16 -0600, Brian Paul wrote: > > Michel suggest when install linux-agp-compat instead of delete > > Module.symvers > > I append the Module(s).symvers file generated by linux-agp-compat > > to the kernel's file of the same name with cat >> before building > the > > DRM. > > And works quite well. > > So this could be add mesa/linux-agp-compat/README > Done. has Dave wrote: It's in 2.6.21 (kernel) and later, it is just a part of agp, nothing special about compat or otherwise, I haven't used linux-agp-compat in a while. a030ce4477baa06dd9c037ccd3c8d171aac9ed44 is the kernel git commitid So , this information should also enter in mesa/linux-agp-compat/README , that this is just for kernel < 2.6.21 And to install linux-agp-compat in kernel < 2.6.21 we should, overwrite .ko modules kernel like this: cp agpgart.ko intel-agp.ko /lib/modules/`uname -a`/kernel/drivers/char/agp/ instead install in other location. And we should swap, not append the symbols. I done a little script which do that, replace all agp_symblos generated by this new modules on old one. Just to be more precisely ... The script is a little raw, but the 2 temporary files, tmp1 and cm, could explain the script itself. I not sure that works in all platforms. Thanks, -- Sérgio M. B. |
From: Brian P. <bri...@tu...> - 2007-08-07 07:34:25
|
On 8/7/07, Sergio Monteiro Basto <se...@se...> wrote: > On Fri, 2007-07-27 at 08:16 -0600, Brian Paul wrote: > > > Michel suggest when install linux-agp-compat instead of delete > > > Module.symvers > > > I append the Module(s).symvers file generated by linux-agp-compat > > > to the kernel's file of the same name with cat >> before building > > the > > > DRM. > > > And works quite well. > > > So this could be add mesa/linux-agp-compat/README > > Done. > > has Dave wrote: > It's in 2.6.21 (kernel) and later, it is just a part of agp, nothing > special about compat or otherwise, I haven't used linux-agp-compat in a > while. > > a030ce4477baa06dd9c037ccd3c8d171aac9ed44 > > is the kernel git commitid > > So , this information should also enter in > mesa/linux-agp-compat/README , that this is just for kernel < 2.6.21 > > And to install linux-agp-compat in kernel < 2.6.21 > we should, overwrite .ko modules kernel like this: > cp agpgart.ko intel-agp.ko /lib/modules/`uname -a`/kernel/drivers/char/agp/ > instead install in other location. > And we should swap, not append the symbols. > I done a little script which do that, replace all agp_symblos generated > by this new modules on old one. > > Just to be more precisely ... > The script is a little raw, but the 2 temporary files, tmp1 and > cm, could explain the script itself. I not sure that works in all platforms. OK, I've checked in some updates to the README file. Please review. BTW, I think you meant to use `uname -r` above, not `uname -a`. -Brian |
From: Sergio M. B. <se...@se...> - 2007-08-07 22:18:45
Attachments:
smime.p7s
README.diff
|
On Tue, 2007-08-07 at 08:34 +0100, Brian Paul wrote: > > OK, I've checked in some updates to the README file. Please review. > BTW, I think you meant to use `uname -r` above, not `uname -a`. My suggestion ( add depmod -a ) Thanks, -- Sérgio M. B. |
From: Sergio M. B. <se...@se...> - 2007-03-01 19:30:28
Attachments:
smime.p7s
|
On Wed, 2007-02-28 at 15:31 +0100, Ulrich von Zadow wrote: > Hi, >=20 > I'm trying to get i915tex running on a gentoo machine here. Currently,=20 > /usr/lib/dri/i915tex_dri.so exists but isn't selected by X: >=20 > (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so >=20 > How does X determine whether to use i915 or i915tex? What are minimum=20 > software versions? I've got: >=20 > mesa-6.5.2 > libdrm-2.3.0 > xorg-server-1.1.1 > kernel 2.6.19 >=20 Last status that I have was 14-18 Fev, you need=20 git clone git://anongit.freedesktop.org/git/mesa/linux-agp-compat git clone git://anongit.freedesktop.org/git/mesa/drm=20 you _must_ have drm kernel compile has modules else recompile kernel with drm and other stuff has modules. cd linux-agp-compat=20 view README Compile using >make Install using (as root) >make install after this recompile drm but if kernel have /usr/src/kernels/2.6.19-1.2895.fc6-i686/Module.symvers like fedora does you must delete this Module.symvers file before recompile drm you have to do something like this: make ll *ko su KERNEL=3D`uname -r` mv /lib/modules/$KERNEL/kernel/drivers/char/drm drm.backup mkdir -p /lib/modules/$KERNEL/kernel/drivers/char/drm cp *.ko /lib/modules/$KERNEL/kernel/drivers/char/drm ll /lib/modules/$KERNEL/kernel/drivers/char/drm depmod -a $KERNEL Regards,=20 --=20 S=C3=A9rgio M. B. |
From: Sergio M. B. <se...@se...> - 2007-03-02 14:13:25
Attachments:
smime.p7s
|
On Thu, 2007-03-01 at 19:30 +0000, Sergio Monteiro Basto wrote: >=20 > you have to do something like this: > make > ll *ko > su=20 after install agp-compat you have to do something like this: rm drm/ -rf git clone git://anongit.freedesktop.org/git/mesa/drm cd drm/linux-core/ make --=20 S=C3=A9rgio M. B. |
From: Ulrich v. Z. <ulr...@ar...> - 2007-06-28 15:13:14
Attachments:
Xorg.0.log
|
Sergio Monteiro Basto schrieb: > On Thu, 2007-03-01 at 19:30 +0000, Sergio Monteiro Basto wrote: (Yup, took me several months to actually get around to this...) >> you have to do something like this: >> make >> ll *ko >> su > after install agp-compat you have to do something like this: > rm drm/ -rf > git clone git://anongit.freedesktop.org/git/mesa/drm > cd drm/linux-core/ > make Ok, I've got working mesa, libdrm and X running here, all with git versions. I'm loading the following modules: agpgart.ko, intel-agp.ko (from git://anongit.freedesktop.org/git/mesa/linux-agp-compat) drm.ko, i915.ko (from Xorg git) The dri drivers from git are used as well. I still get no i915tex driver. Some parts of the Xorg log that look relevant to my untrained eyes follow: (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [...] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 945GM found [...] (WW) intel(0): Bad V_BIOS checksum [...] (WW) intel(0): VideoRam configuration found, which is no longer recommended. (II) intel(0): Continuing with default 262144kB VideoRam instead of 131072 kB. [...] (EE) intel(0): Failed to init memory manager [...] (EE) intel(0): I830 Vblank Pipe Setup Failed 0 [...] ...and I've attached the complete Xorg.log as well. I'd be grateful for any ideas, and if I'm running into a bug, I'd be happy to help fix it. Regards, Uli -- Ulrich von Zadow | Software Development Unit Head ART+COM AG | Kleiststr. 23-26 | 10787 Berlin | Germany p: +49.30.21001-464 | f: +49.30.21001-555 | m: +49.172.7621408 w: http://www.artcom.de/ Trade Register 68308 | County Court Charlottenburg Board: Andreas Wiek, Sebastian Peichl Chairman: Volker Tietgens VAT-IdNr.: DE811998328 |
From: Sergio M. B. <se...@se...> - 2007-06-28 17:18:06
Attachments:
smime.p7s
|
On Thu, 2007-06-28 at 17:12 +0200, Ulrich von Zadow wrote: > Sergio Monteiro Basto schrieb: > > On Thu, 2007-03-01 at 19:30 +0000, Sergio Monteiro Basto wrote: >=20 > (Yup, took me several months to actually get around to this...) >=20 > >> you have to do something like this: > >> make > >> ll *ko > >> su=20 > > after install agp-compat you have to do something like this: > > rm drm/ -rf > > git clone git://anongit.freedesktop.org/git/mesa/drm > > cd drm/linux-core/ > > make >=20 > Ok, I've got working mesa, libdrm and X running here, all with git > versions. I'm loading the following modules: >=20 > agpgart.ko, intel-agp.ko (from > git://anongit.freedesktop.org/git/mesa/linux-agp-compat) > drm.ko, i915.ko (from Xorg git) >=20 > The dri drivers from git are used as well. >=20 > I still get no i915tex driver. Some parts of the Xorg log that look > relevant to my untrained eyes follow: >=20 > (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) > [...] > (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, > i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, > E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, > 965GM, 965GME/GLE, G33, Q35, Q33 > (II) Primary Device is: PCI 00:02:0 > (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) fou= nd > (--) Chipset 945GM found > [...] > (WW) intel(0): Bad V_BIOS checksum > [...] > (WW) intel(0): VideoRam configuration found, which is no longer recommend= ed. > (II) intel(0): Continuing with default 262144kB VideoRam instead of > 131072 kB. > [...] > (EE) intel(0): Failed to init memory manager > [...] > (EE) intel(0): I830 Vblank Pipe Setup Failed 0 > [...] >=20 > ...and I've attached the complete Xorg.log as well. you got on Xorg.log AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so should have=20 AIGLX: Loaded and initialized /usr/lib/dri/i915tex_dri.so >=20 > I'd be grateful for any ideas, and if I'm running into a bug, I'd be > happy to help fix it. --=20 S=C3=A9rgio M. B. |
From: Russell H. <eat...@gm...> - 2007-06-30 05:02:55
Attachments:
Xorg.0.log.old
|
I have a similar problem, but I don't get the failed to init memory manager error, and don't get the vblank error until x closes... (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 945GM found [...] (WW) intel(0): Bad V_BIOS checksum [...] (**) intel(0): Depth 24, (--) framebuffer bpp 32 (=3D=3D) intel(0): RGB weight 888 (=3D=3D) intel(0): Default visual is TrueColor (**) intel(0): Option "DRI" "true" (**) intel(0): Option "XVideo" "true" (**) intel(0): Option "Legacy3D" "false" (**) intel(0): Option "TripleBuffer" "true" (II) intel(0): Integrated Graphics Chipset: Intel(R) 945GM (--) intel(0): Chipset: "945GM" (--) intel(0): Linear framebuffer at 0xD0000000 (--) intel(0): IO registers at addr 0xEE100000 (II) intel(0): 2 display pipes available. (=3D=3D) intel(0): Using XAA for acceleration (**) intel(0): Will not try to allocate texture pool for old Mesa 3D driver= . (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. [..] (WW) AIGLX: 3D driver claims to not support visual 0x23 (WW) AIGLX: 3D driver claims to not support visual 0x24 (WW) AIGLX: 3D driver claims to not support visual 0x25 (WW) AIGLX: 3D driver claims to not support visual 0x26 (WW) AIGLX: 3D driver claims to not support visual 0x27 (WW) AIGLX: 3D driver claims to not support visual 0x28 (WW) AIGLX: 3D driver claims to not support visual 0x29 (WW) AIGLX: 3D driver claims to not support visual 0x2a (WW) AIGLX: 3D driver claims to not support visual 0x2b (WW) AIGLX: 3D driver claims to not support visual 0x2c (WW) AIGLX: 3D driver claims to not support visual 0x2d (WW) AIGLX: 3D driver claims to not support visual 0x2e (WW) AIGLX: 3D driver claims to not support visual 0x2f (WW) AIGLX: 3D driver claims to not support visual 0x30 (WW) AIGLX: 3D driver claims to not support visual 0x31 (WW) AIGLX: 3D driver claims to not support visual 0x32 (II) AIGLX: Loaded and initialized /usr/lib/dri/i915_dri.so Note the last line... i915_dri... not i915tex. I have Legacy3D set to false, so... wtf. I then get the following when X closes: (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 (II) intel(0): xf86UnbindGARTMemory: unbind key 2 (II) intel(0): xf86UnbindGARTMemory: unbind key 3 (II) intel(0): xf86UnbindGARTMemory: unbind key 4 (II) intel(0): xf86UnbindGARTMemory: unbind key 5 (II) intel(0): xf86UnbindGARTMemory: unbind key 6 (II) intel(0): xf86UnbindGARTMemory: unbind key 7 (II) intel(0): xf86UnbindGARTMemory: unbind key 8 (II) intel(0): xf86UnbindGARTMemory: unbind key 9 On a related note, starting any opengl will give me the error: libGL warning: 3D driver claims to not support visual 0x66 although it works. Can someone tell me what it is I also have the aiglx + direct rendering problems, but I think I know what causes those. Attached is my Xorg.0.log.old (the log for my last (closed) X session so you can see the closing errors as well as opening) On 6/29/07, Michel D=E4nzer <mi...@tu...> wrote: > On Thu, 2007-06-28 at 18:17 +0100, Sergio Monteiro Basto wrote: > > On Thu, 2007-06-28 at 17:12 +0200, Ulrich von Zadow wrote: > > > (EE) intel(0): Failed to init memory manager > > xf86-video-intel currently defaults to the legacy i915 driver, you need > to specify Option "Legacy3D" "off" to use i915tex. > > > -- > Earthling Michel D=E4nzer | http://tungstengraphics.co= m > Libre software enthusiast | Debian, X and DRI developer > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel > |
From: Russell H. <eat...@gm...> - 2007-07-02 20:55:38
|
> > (**) intel(0): Option "TripleBuffer" "true" > > BTW, this will currently only waste memory without "PageFlip" as well, > and the latter will currently cause XVideo issues with XAA (besides only > being useful with i915tex). That's good to know... I turned it off. > > Note the last line... i915_dri... not i915tex. I have Legacy3D set to > > false, so... wtf. > > (II) intel(0): Unable to use TTM-based memory manager with DRM version 1.6 > > You need the i915 kernel module built from the drm GIT tree. I tried building the module from the git tree, and got errors... russ@kiki ~/src/drm/src/linux-core $ make make -C /lib/modules/2.6.21-kamikaze6/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules make[1]: Entering directory `/usr/src/linux-2.6.21-kamikaze6' CC [M] /home/russ/src/drm/src/linux-core/i915_irq.o /home/russ/src/drm/src/linux-core/i915_irq.c: In function 'i915_driver_irq_postinstall': /home/russ/src/drm/src/linux-core/i915_irq.c:722: error: expected expression before '{' token make[2]: *** [/home/russ/src/drm/src/linux-core/i915_irq.o] Error 1 make[1]: *** [_module_/home/russ/src/drm/src/linux-core] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.21-kamikaze6' make: *** [modules] Error 2 > > I also have the aiglx + direct rendering problems, but I think I know > > what causes those. > > Probably that the 3D driver doesn't have any texture memory? The specific issue is with opengl apps, videos in particular. OpenGL apps will always be above other windows, even if I send it's window below another. I also have an issue with xv, which gives me "X11 error: BadAlloc (insufficient resources for operation)" I believe http://bugs.freedesktop.org/show_bug.cgi?id=8732 covers this problem however |
From: Russell H. <eat...@gm...> - 2007-07-03 18:48:02
|
> > > (II) intel(0): Unable to use TTM-based memory manager with DRM version 1.6 > > > > > > You need the i915 kernel module built from the drm GIT tree. > > I tried building the module from the git tree, and got errors... > > > > russ@kiki ~/src/drm/src/linux-core $ make > > make -C /lib/modules/2.6.21-kamikaze6/source SUBDIRS=`pwd` > > DRMSRCDIR=`pwd` modules > > make[1]: Entering directory `/usr/src/linux-2.6.21-kamikaze6' > > CC [M] /home/russ/src/drm/src/linux-core/i915_irq.o > > /home/russ/src/drm/src/linux-core/i915_irq.c: In function > > 'i915_driver_irq_postinstall': > > /home/russ/src/drm/src/linux-core/i915_irq.c:722: error: expected > > expression before '{' token > > make[2]: *** [/home/russ/src/drm/src/linux-core/i915_irq.o] Error 1 > > make[1]: *** [_module_/home/russ/src/drm/src/linux-core] Error 2 > > make[1]: Leaving directory `/usr/src/linux-2.6.21-kamikaze6' > > make: *** [modules] Error 2 > > I just pushed a change that might fix this. > Yep, that fixed it... thx |