i915 and xorg - how?

[Klavs]

I enabled DRI and GLX in xorg.conf, and now xvinfo and glxgears run. glxgears gives me approx 470 FPS - can it be that the graphics driver is that slow?

[Sejam]

I enabled DRI and GLX in xorg.conf, and now xvinfo and glxgears run. glxgears gives me approx 470 FPS - can it be that the graphics driver is that slow?

If you run glxinfo, do you get the following warnings at the start?

libGL warning: 3D driver claims to not support visual 0x22
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x26
libGL warning: 3D driver claims to not support visual 0x27
Mesa 6.3 implementation error: bad target in _mesa_new_program
Please report at bugzilla.freedesktop.org

BTW, I also get around 575 - 581 fps.

[Klavs]

Nope - no such errors.

[Klavs]

When playing avi (divx) with mplayer (using -vo xv) the image is "greyish" with stripes.. I have no such problems with mpg's. Anyone have the same problem?

btw. I just saw there's going to be no 6.8.3 release of xorg (which would include the i915gm driver) - but hey are going to go for 6.9 and 7.0.. that probably means we have to wait
Anyone running CVS version with any luck?

[VinzC]

I just saw there's going to be no 6.8.3 release of xorg (which would include the i915gm driver) - but hey are going to go for 6.9 and 7.0.. that probably means we have to wait

Oh damn! :'(

EDIT: What about XFree?

[VinzC]

Hi Klavs.

I've installed the latest i915 snapshot (20050414) from their web site. Now I can get X to work but when X starts the console display is corrupted: I get rectangles of random colors anywhere. Do you have any hint on what's causing this?

2 Notes however.

1. it seems X is running in VESA mode despite my settings (I've run xorgconf). It's not that bad after all as I finally have a graphical environment. I'll tune that afterwards. However the console display cannot be "reseted" using the command. I have to reboot to get a proper display. I'm starting with framebuffer console with theme "emergence". Is it the cause of my problem?

2. I had to recompile my kernel to get i915 module to load otherwise the module shipped with the snapshot produced dynamic link errors (symbols missing or something; anyway it didn't load at all). Besides I think X would start anyway even if i915 module is not loaded. Probably because it relies on VESA mode, which doesn't depend on i915, am I right?

Thanks.

[Klavs]

VESA does not require i915 module. You need to set it to use i810. Have a look at the xorg.conf I have made available at vsen.dk.
Your problem with "text-mode" is probably your framebuffer yes.
When my screen blanks (because I've closed the machine) I can always get it back by switching to text mode (ie. ctrl+alt+f1) and then back to X. When you run framebuffer - you're not running text-mode.

[hoschi]

one question, for the intel media acc. 900 (sonoma-chipset 915gm in r52 ibm thinkpad)

i need a kernel with:
-intel agp-gart
-915 drm

and xorg 6.8.x ? what? is the "i810" driver in xorg 6.8.2 oder the new 6.8.3 ?
whats about 3d accleration?

[VinzC]

VESA does not require i915 module. You need to set it to use i810. Have a look at the xorg.conf I have made available at vsen.dk.

I suppose you mean "setup xorg to use xorg's i810 driver (interface)"? Or do you also need i810 support into the kernel? This is something I haven't quite clearly understood, I must admit

Another thing:
- what does the snapshot do? Compile a kernel module *and* an xorg driver? or just a kernel module?
- can the i915 chipset be used in non-VESA mode (w/o a snapshot or whatever)?

Your problem with "text-mode" is probably your framebuffer yes.
When my screen blanks (because I've closed the machine) I can always get it back by switching to text mode (ie. ctrl+alt+f1) and then back to X. When you run framebuffer - you're not running text-mode.

So do you suggest not to use framebuffer consoles at all?

[VinzC]

Well, I booted Gentoo in pure text mode and my problem still arises. I don't get random blocks anymore but the screen is blank (with backlight on). Switching to another text console doesn't fix anything. When I get out of X the screen is blank; full stop . Any idea?

Note: I made my kernel based on your config file and I'm running X with your xorg config file.

[hoschi]

the newest xorg in portage + newest gentoo-dev-sources - supports this now the i915gm ?
news about dma für cdrom?

[hoschi]

Kernel 2.6.12-rc3 with newest Xorg-Release in Portage 6.9.x anything

I runs with Kernel DRM and Kernel i915GM-Driver, but i get this Warning:

I810: No matching Device section for instance (BusID PCI:0:2:1) found


glxinfo says direct rendering is okay

[VinzC]

Kernel 2.6.12-rc3 with newest Xorg-Release in Portage 6.9.x anything

I runs with Kernel DRM and Kernel i915GM-Driver, but i get this Warning:

I810: No matching Device section for instance (BusID PCI:0:2:1) found


glxinfo says direct rendering is okay

Latest XOrg in portage is now 6.8.99. Do you mean emerging that version doesn't require patching the kernel and XOrg with the snapshot? And it works right out of the box?

[hoschi]

yeah, more than 1000fps in glxgears (24bit) and no warnings with glxinfo (915i drm support is in a hidden intel submenu in the drm section)
i am now merging gnome + quake3...time to bash the stupid wintel newbs

[hoschi]

problems with videos (totem - xine or gstreamer),
if i watch a video the color are ugly or i have big problems to start a movie, anyone with the same problem?

[VinzC]

yeah, more than 1000fps in glxgears (24bit) and no warnings with glxinfo (915i drm support is in a hidden intel submenu in the drm section)
i am now merging gnome + quake3...time to bash the stupid wintel newbs

I have installed xorg 6.8.99 (I have nothing more recent than gentoo-sources 2.6.11-r6) and I still get the same problems with video as when I patched X with the snapshot:
- X still runs in vesa mode
- console screens are still corrupted and I must reboot right after I close X

Did you succeed in running X in *non* vesa mode?

[hoschi]

First rule for every linux-user - if something goes wrong: take the vanilla-sources
(next time i will post, that i am using the vanilla-sources)

2.6.12-rc3 (you must choose the intel driver "with more chipsets in drm-section, and it possible to switch between 915 and 810)

[VinzC]

First rule for every linux-user - if something goes wrong: take the vanilla-sources

Ah, I see. So the problem I'm experiencing might be due to the kernel video driver?
BTW, isn't Gentoo-sources equal to Vanilla-sources+gentoo developers' patches? (I just wanted to know/confirm). I never used Vanilla-sources in fact. So I have a couple of questions.

If I install them, I presume I will have to patch the kernel manually? Could you provide details on what you did exactly? Did you emerge vanilla-sources and then go straight with that or did you install patches? Will I be able to make oldconfig with my old configuration file from Gentoo-sources?

Thanks.

[UB|K]

If I install them, I presume I will have to patch the kernel manually? Could you provide details on what you did exactly? Did you emerge vanilla-sources and then go straight with that or did you install patches? Will I be able to make oldconfig with my old configuration file from Gentoo-sources?

yes, you'll be able to keep your gentoo-source's config with "oldconfig".

For info, i use:
-2.6.11.7 vanilla kernel (with some patch: inotify + software supend2)
-i915 and drm modules come from dri-snapshot
-xorg-x11-6.8.99.3

and everything's ok

[hoschi]

Has anybody difficulties in looking videos (mpeg, avi) with totem (xine and gstreamer backend)?
It looks here quiet ugly, like 256 colors only.

[stormer]

I'm using Xorg 6.8.99 and dri snapshot from yesterday (don't use it, it crash your kernel some times) on kernel 2.6.11-gentoo-r6 and totem with gstreamer backend. It it not as good as xine backend, but seems for the first time acceptable. I still recommand not using Gstreamer, video quality is still not as good as xine.

I'm experiencing trouble with Old unreal-tournament. It's too fast, about too time faster. I think it mess with speedstep mecanism. Any idea ?

p.s. for dri, I killed the script after compilation, and copied kernel stuff by hand, because X stuff does not seem to work, as exemple it creates a i810_drv.o insted of i810_drv.so and it is not corectly linked.

[stormer]

Any one as been able to get DMA on sata_piix cdrom drive ? Still can't watch DVDs.

[VinzC]

Any one as been able to get DMA on sata_piix cdrom drive ? Still can't watch DVDs.

Look at http://forums.gentoo.org/viewtopic-t-30 ... ml#2329485

[VinzC]

p.s. for dri, I killed the script after compilation, and copied kernel stuff by hand, because X stuff does not seem to work, as exemple it creates a i810_drv.o insted of i810_drv.so and it is not corectly linked.

I had almost the same problem with i915 snapshot. Copying kernel modules did it wrong and returned error messages. So I commented out the portion of code that copied the module into Gentoo-sources.

But I was also using Gentoo-sources. Have you tried vanilla-sources, as Hoschi mentionned?

[hoschi]

Any one as been able to get DMA on sata_piix cdrom drive ? Still can't watch DVDs.

Look at http://forums.gentoo.org/viewtopic-t-30 ... ml#2329485

Thank You Very Much! Oh my gosh! Godmode!




Maybe i will try the newest DRI Snapshot, Vesa is so slow...


<edit>

libata version 1.10 loaded.
ata_piix version 1.03
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1810 irq 14
ata1: dev 0 cfg 49:0f00 82:746b 83:5be9 84:6003 85:f469 86:1849 87:6003 88:203f
ata1: dev 0 ATA, max UDMA/100, 78140160 sectors:
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
Vendor: ATA Model: HTS541040G9AT00 Rev: MB2I
Type: Direct-Access ANSI SCSI revision: 05
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1818 irq 15
ata2: dev 0 cfg 49:0f00 82:4218 83:0000 84:0000 85:0000 86:0000 87:0000 88:0407
ata2: dev 0 ATAPI, max UDMA/33
ata2: dev 0 configured for UDMA/33
scsi1 : ata_piix
Vendor: HL-DT-ST Model: RW/DVD GCC-4241N Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 05
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

It works, but where is my device (running clean udev system with no tarball)?