i915 and xorg - how?

Message

VinzC · Post by **VinzC** » Sat May 14, 2005 8:24 pm

thomasa88 wrote:I've managed to get direct rendering by using gentoo-sources 2.6.11-r8 (disabling drm and fb ), i915-20050513 from dri snapshots and xorg 6.8.99.5. The problem is that when I restart/stop X my laptop just hangs

I posted a bug to gentoo's bugzilla were they told me to post it on freedesktop. (https://bugs.freedesktop.org/show_bug.cgi?id=3217)
Unfortunately I havent got any answer yet. Anyone else than me have experienced the same problem?

For those who skip till the end of this thread:
Using DRI snapshots may freeze your system when X is closed

Xorg 6.8.99.3 and above work properly with i915. One issue exists with Gentoo sources though: DRI works with vanilla sources and not with Gentoo sources.

Good news: I have used vesafb instead of vesa-tng and now I get my cool bootsplash, theme emergence. Simply add kernel argument vga=0x31A, next to video=vesafb:ywrap,mtrr,1280x1024-16@60. Gentoo sources used of course for I don't mind my 680FPS in glxgears instead of 800FPS with DRI enabled.

Code: Select all

# uname -r
2.6.11-gentoo-r8

Thanks for posting a bug report anyway.

seppelrockt · Post by **seppelrockt** » Sun May 15, 2005 9:29 pm

I use gentoo-sources-2.6.11-r7 + xorg-x11-6..8.99.3 without any dri-snapshots and it looks quite promissing - drm and i915 are loaded automaticaly within startx (I have i810 in xorg.conf). Unfortuntaly there is no /dev/dri/card0 on my system (/dev/dri is empty). That's why dri is not used by X - see my Xorg.0.log. Can I create the device notes manualy? Might that be a udev prob (I use udev with tarball)?

Code: Select all

(II) I810(0): initializing int10
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 7872 kB
(II) I810(0): VESA VBE OEM: Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)915GM/910ML/915MS Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(==) I810(0): Default visual is TrueColor
(II) I810(0): Allocated 128 kB for the ring buffer at 0x0
(II) I810(0): Allocating at least 256 scanlines for pixmap cache
(II) I810(0): Initial framebuffer allocation size: 8448 kByte
(II) I810(0): Allocated 4 kB for HW cursor at 0xffff000 (0x18567000)
(II) I810(0): Allocated 16 kB for HW (ARGB) cursor at 0xfffb000 (0x18598000)
(II) I810(0): Allocated 4 kB for Overlay registers at 0xfffa000 (0x1856e000).
(II) I810(0): Allocated 64 kB for the scratch buffer at 0xffea000
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card1
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card2
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card3
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenByBusid: drmOpenMinor returns -1023
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) I810(0): [drm] drmOpen failed
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) I810(0): Updated framebuffer allocation size from 8448 to 16384 kByte
(II) I810(0): Updated pixmap cache from 256 scanlines to 1248 scanlines
(II) I810(0): 0x840e4f8: Memory at offset 0x00020000, size 16384 kBytes
(II) I810(0): 0x8383350: Memory at offset 0x0ffff000, size 4 kBytes

(II) I810(0): 0x8383378: Memory at offset 0x0fffb000, size 16 kBytes
(II) I810(0): 0x86071bc: Memory at offset 0x00000000, size 128 kBytes
(II) I810(0): 0x840e538: Memory at offset 0x0ffea000, size 64 kBytes
drmOpenDevice: node name is /dev/dri/card4
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card5
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card6
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card7
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card8
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card9
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card10
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card11
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card12
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card13
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card14
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) I810(0): [drm] drmOpen failed
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) I810(0): Updated framebuffer allocation size from 8448 to 16384 kByte
(II) I810(0): Updated pixmap cache from 256 scanlines to 1248 scanlines
(II) I810(0): 0x840e4f8: Memory at offset 0x00020000, size 16384 kBytes
(II) I810(0): 0x8383350: Memory at offset 0x0ffff000, size 4 kBytes
(II) I810(0): 0x8383378: Memory at offset 0x0fffb000, size 16 kBytes
(II) I810(0): 0x86071bc: Memory at offset 0x00000000, size 128 kBytes
(II) I810(0): 0x840e538: Memory at offset 0x0ffea000, size 64 kBytes
(II) I810(0): 0x83833a0: Memory at offset 0x0fffa000, size 4 kBytes
(==) I810(0): Write-combining range (0xc0000000,0x10000000)
(II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) I810(0): xf86BindGARTMemory: bind key 4 at 0x007bf000 (pgoffset 1983)
(II) I810(0): xf86BindGARTMemory: bind key 0 at 0x0ffff000 (pgoffset 65535)
(II) I810(0): xf86BindGARTMemory: bind key 1 at 0x0fffb000 (pgoffset 65531)
(II) I810(0): xf86BindGARTMemory: bind key 3 at 0x0ffea000 (pgoffset 65514)
(II) I810(0): xf86BindGARTMemory: bind key 2 at 0x0fffa000 (pgoffset 65530)
(II) I810(0): Display plane A is disabled and connected to Pipe A.
(II) I810(0): Display plane B is enabled and connected to Pipe B.
(II) I810(0): Enabling plane B.
(II) I810(0): Display plane A is now disabled and connected to Pipe A.
(II) I810(0): Display plane B is now enabled and connected to Pipe B.
(II) I810(0): PIPEACONF is 0x00000000
(II) I810(0): PIPEBCONF is 0x80000000
(II) I810(0): Mode bandwidth is 61 Mpixel/s
(II) I810(0): maxBandwidth is 1152 Mbyte/s, pipe bandwidths are 268 Mbyte/s, 0 Mbyte/s
(II) I810(0): LFP compensation mode: 0x1
(II) I810(0): Using XFree86 Acceleration Architecture (XAA)
        Screen to screen bit blits
        Solid filled rectangles
        8x8 mono pattern filled rectangles
        Indirect CPU to Screen color expansion
        Solid Horizontal and Vertical Lines
        Offscreen Pixmaps
        Setting up tile and stipple cache:
                32 128x128 slots
                17 256x256 slots
                5 512x512 slots
(==) I810(0): Backing store disabled
(==) I810(0): Silken mouse enabled
(II) I810(0): Initializing HW Cursor
(II) I810(0): direct rendering: Failed

VinzC · Post by **VinzC** » Mon May 16, 2005 10:02 am

seppelrockt wrote:I use gentoo-sources-2.6.11-r7 + xorg-x11-6..8.99.3 without any dri-snapshots and it looks quite promissing - drm and i915 are loaded automaticaly within startx (I have i810 in xorg.conf). Unfortuntaly there is no /dev/dri/card0 on my system (/dev/dri is empty). That's why dri is not used by X - see my Xorg.0.log. Can I create the device notes manualy? Might that be a udev prob (I use udev with tarball)?
[...]

I don't think it's a problem with udev but a problem with kernel. I've got the exact same "feature". If I boot with a vanilla sources kernel, the DRI node is present. I think it might be related to differences in how direct rendering is built into the kernel (Gentoo sources).
EDIT: you could always try to create the nodes manually and see what happens.

thomasa88 · Post by **thomasa88** » Mon May 16, 2005 3:32 pm

didnt think of that

, I will try to find/use the non-snapshots when I get back to my laptop and tell

Where and what should I download?

EDIT:

Wrong thread :S, must get some sleep (I read a similar thread and was going to post there, not here, sry)

EDIT: now im reeally tired, didnt see this page and I answered to a post on the previous page.

Edit: Anyway, new question: I dont get Direct rendering with the xorg alone :'(

VinzC · Post by **VinzC** » Mon May 16, 2005 4:53 pm

thomasa88 wrote:Where and what should I download?

Where? from Gentoo portage of course

What? xorg 6.8.99.3 or above. It is masked in portage so mkdir -p /etc/portage && echo '>=x11-base/xorg-x11-6.8.99.3 ~x86' >> /etc/portage/package.keywords && emerge -av xorg-x11.

This will
- create your /etc/portage directory if it doesn't exist
- unmask the latest version of xorg 6.8.99
- ask you if you still want to install it.

thomasa88 · Post by **thomasa88** » Mon May 16, 2005 6:29 pm

Whats the diff between gentoo and vanilla sources?

I really want my glx/drm/dri or what the heck its name

(800 vs 2700 fps)

Is there anyway I can patch the gentoo-sources to make it work?

seppelrockt: did you succeed to create the node by yourself?

VinzC · Post by **VinzC** » Tue May 17, 2005 6:56 am

thomasa88 wrote:Whats the diff between gentoo and vanilla sources?

The difference is the following: Vanilla sources are the official kernel sources, no exotic features inside. Gentoo sources are optimized by Gentoo developers and include the latest patches. See Gentoo kernel guide for more information.

thomasa88 wrote:I really want my glx/drm/dri or what the heck its name (800 vs 2700 fps)

Is there anyway I can patch the gentoo-sources to make it work?

About patching Gentoo sources, I don't know. I would rather wait till gentoo sources come fixed with the features you want. BTW where did you get the 2700 FPS? On a Dell Inspiron 6000?

thomasa88 · Post by **thomasa88** » Tue May 17, 2005 8:18 am

VinzC wrote:BTW where did you get the 2700 FPS? On a Dell Inspiron 6000?

Yep, glxgears, almost no load (running browser + my Eterms + some editor)

VinzC · Post by **VinzC** » Tue May 17, 2005 9:16 am

thomasa88 wrote:
VinzC wrote:BTW where did you get the 2700 FPS? On a Dell Inspiron 6000?
Yep, glxgears, almost no load (running browser + my Eterms + some editor)

Would you mind telling us how you did get such a hich rate, please? I couldn't get more than 880FPS even with DRI enabled so far... Post your xorg.conf and your kernel config file somewhere we can get to easily. Otherwise post them here, without comments. Example:

Code: Select all

grep -ivE '^#|^ *$' /etc/X11/xorg.conf

I suppose you were using Gentoo sources? Optionnally post your /var/log/Xorg.0.log. I think you were probably running XOrg in non-VESA mode.

thomasa88 · Post by **thomasa88** » Tue May 17, 2005 10:54 am

I installed xorg 6.8.99.5, latest dri snapshot install (but I commented out so it didnt replace the xorg-drivers), gentoo-sources-kernel (without drm)

Cant post my files today

I will check the config when I get the possibility

VinzC · Post by **VinzC** » Tue May 17, 2005 11:24 am

thomasa88 wrote:I installed xorg 6.8.99.5, latest dri snapshot install (but I commented out so it didnt replace the xorg-drivers), gentoo-sources-kernel (without drm)

So these were the snapshots you were experiencing problems with Xorg, if I understood? Maybe taking previous versions of DRI snapshots would solve this all. Someone (hoschi I think) has succeeded in getting less recent snapshots to work. But I don't know if he got that much FPS...

We would need the exact version of your kernel and snapshost. Also did you use the Common parts of DRI snapshots? Especially the ones that do not produce the expected results

...

thomasa88 · Post by **thomasa88** » Wed May 18, 2005 6:44 am

Okey, lets see.. (right now im trying with just xorg's own drivers, hmm.. should I have any i915-driver in the kernel to make it work?)

Code: Select all

i915-20050513-linux.i386 (and some b4 this existed, upgraded about once a week to see if the problem went away)
   modified the script to not install drivers in xorg

Edit.
In the latest version I didnt have to comment the part which installed in xorg cuz the dri-driver worked ok

Code: Select all

gentoo-sources 2.6.11-r8

(and r6 b4 if im not wrong)

Code: Select all

xorg 6.8.99.5

(and 6.8.99.3 b4)

as for the kernel config

I have modified back and forth and I use make install so I get one config.old
but this is what I remember (if u want other things I prob havent changed them so I can check)

Code: Select all

no vesa (cuz of nice colored squares, I hadnt tried the orig vesafb)
no drm (got it from the dri package)
agpart in kernel (hmm just the option to have it, no specific in the submenu)
  edit. do I need this?

hope thats all

Edit.

Maybe ill try with an older snapshot today, or some other kernel sources

VinzC · Post by **VinzC** » Wed May 18, 2005 8:49 am

Thanks a lot, thomasa88. So I'll summarize. At the time you got 2700FPS you were using:
- Gentoo sources 2.6.11-r6 with
. no VESA VGA graphics support in the Device drivers > Graphics support section
. no DRM support in the Device drivers > Character devices section
- Xorg 6.8.99.3
- DRI snapshot i915-20050513-linux.i386 but the kernel driver only.

With this configuration the system doesn't freeze when X is closed, right? I suppose you didn't use framebuffer devices either?

Was XOrg running in 16 bpp (64k colors) or 32bpp (16M colors)? I've just read on DRI web that 3D acceleration is only supported with 16bpp:

Intel i810/i8153D

Acceleration for the i810 is only available in the 16 bit/pixel screen mode at this time. 32bpp acceleration is not supported by this hardware. Use xdpyinfo to verify that all your visuals are depth 16. Edit your XF86Config file if needed.

That might explain...

Just one more thing: could you post the results of grep -i vesa /var/log/Xorg.0.log when Xorg gives you the high FPS rate (2700)?

thomasa88 · Post by **thomasa88** » Thu May 19, 2005 5:30 am

Almost right

With the latest dri snapshot I tried (20050513) I didnt have to do anythin with the install-script.
The system did freeze when I tried to close X

. And yes, I didnt use any framebuffer because of the nice colored squares I got together with dri.

About the colors then, I think the option you are refering to is the DefaultDepth option in xorg.conf.
Ive tried with both 16 and 24 (but 24 is 16 with alpha?)

sry but I have to run to school now

(when I was always finished I accidently closed the browser tab and had to rewrite this :S) Ill see if I got anything left in the log

VinzC · Post by **VinzC** » Thu May 19, 2005 1:27 pm

thomasa88 wrote:And yes, I didnt use any framebuffer because of the nice colored squares I got together with dri.

As for the screen corruption, I think there is a fix from within xorg.conf directly:

Option "VBERestore" "boolean" Enable or disable the use of VBE save/restore for saving and restoring the initial text mode. This is disabled by default because it causes lockups on some platforms. However, there are some cases where it must enabled for the correct restoration of the initial video mode. If you are having a problem with that, try enabling this option. Default: Disabled.

This comes from i810 man pages. I haven't tried this though. Also note the screen corruption occurs only with Gentoo sources when using vesa-tng; if you use vesafb it doesn't happen. I thought it might be of interrest.

thomasa88 wrote:About the colors then, I think the option you are refering to is the DefaultDepth option in xorg.conf.
Ive tried with both 16 and 24 (but 24 is 16 with alpha?)

Exactly. But I don't know if 32bpp is equal to 24 plus the alpha layer. In PNG pictures, yes but in xorg...

On my side I've installed once more the latest snapshots (May, 17th 2005); here are my observations.

1. They brought absolutely no gain in performance. Evenmore the DRM kernel module is not used though loaded without error: DRI cannot be enabled in xorg for there is no /proc/dri/cardn node. I guess the kernel module from the snapshots is either invalid or not functional. The good thing is X doesn't freeze the system anymore when closed. But it's a poor benefit compared to my expectations...

2. I've also seen the frame rate given by glxgears is highly dependent on the color depth: I get about 800FPS in true color mode (24bpp) against 1300FPS in 16bpp (64k)... My laptop's resolution is 1680x1050 (don't know if it matters for glxgears when not full-screen) and my adapter is PCI-Express. (BTW is your video adapter also PCIE?).

EDIT: I meant color depth not resolution.
EDIT: damn I need to get some sleep! my resolution is 1680x1050 not 1980x1050...

3. Plain Vanilla sources (2.6.12-rc4) is the only situation I can get DRI to work.

thomasa88 · Post by **thomasa88** » Thu May 19, 2005 2:36 pm

Resolution could be the reason, Im running 1280x800

I dont know if I have pcie or not, the only thing I now is that "the graphics are integrated"
here's output from lscpi

Code: Select all

0000:00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
0000:00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
0000:00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

0000:00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)

it says "Express" on the upmost things but I dont know..

I will try with the latest snapshots to see what happens and also the xorg-option seems nice if I try with vesa-tng again

btw. sry that I couldnt give you a log, but I kinda experiment with my system

edit. I noticed today that xset dpms force on/off only works when I have dri enabled

Edit. I couldnt get the VBERestore to work and even worse is that I cant get my dri back anymore, I will try with vanilla sources to see what happens

Edit. With the vanilla sources and no dri-snapshot I only get about 900 fps in glxgears

dmbtech · Post by **dmbtech** » Fri May 20, 2005 10:01 pm

This is a REALLY long thread, and i can't tell what exactly is recent and works and what doesn't. I'm just wondering if there is a solution to getting the intel 915 working with DRI, so you can play games and use blender, without it being blisterfully slow. (using the latest gentoo-sources) Thanks.

VinzC · Post by **VinzC** » Fri May 20, 2005 10:15 pm

dmbtech wrote:This is a REALLY long thread, and i can't tell what exactly is recent and works and what doesn't. I'm just wondering if there is a solution to getting the intel 915 working with DRI, so you can play games and use blender, without it being blisterfully slow. (using the latest gentoo-sources) Thanks.

Forget gentoo sources. Use vanilla sources instead. Snapshots are useless at this time - at least for me. It also depends on you laptop's hardware, as far as I could see.

I'll personnally wait till gentoo developpers put them into portage. For now I'm using Vanilla sources (2.6.12-rc4) with some patches (inotfify, fbsplash and vesa-tng). I get 1300FPS in 16 bit color mode but I can bear with it

.

dmbtech · Post by **dmbtech** » Fri May 20, 2005 10:24 pm

Well, i just tried the latest dri package for intel may 17 i think is the day, and it compiled all right and everything. But it just won't load the kernel module, it says undefined symble. Anyway, X still runs, but it says direct rendering is off.

I can't try vanilla sources, becuase i'v become depenent on gentoo-sources for things like bootsplash. Also, i have i915 for a pc, not a laptop, i guess i915 is used for both laptop and PC, don't know.

thomasa88 · Post by **thomasa88** » Fri May 20, 2005 10:29 pm

have you tried removing drm from the kernel? That was the problem when I was running gentoo-sources

VinzC · Post by **VinzC** » Sat May 21, 2005 12:09 pm

dmbtech wrote:I can't try vanilla sources, because i'v become dependent on gentoo-sources for things like bootsplash. Also, i have i915 for a pc, not a laptop, i guess i915 is used for both laptop and PC, don't know.

Don't worry, you can have bootsplash with Vanilla sources too. you will only have to patch your kernel. There is a little difference between kernel 2.6.11 and 2.6.12 in how framebuffer is implemented in the kernel.

I have vanilla sources 2.6.12-rc4 and bootsplash. The latest vanilla sources require splashutils 0.9.2, which you will have to unmask. If you don't want to use masked splashutils, you'll have to use vanilla sources 2.6.11 or older. The beauty of masked splashutils is that the splash now fades in instead of appearing at once. Just like Redmond's Fisher Price toy

, as I usually say.

seppelrockt · Post by **seppelrockt** » Sat May 21, 2005 2:53 pm

Why the hell doesn't xv work? Mplayer complains that the xv is not available for my driver. Remeber, I use vanilla 2.6.12rc4 + xorg-x11-6.8.99.5 WITHOUT any DRI snapshots. DRI works and I have the i810 driver in xorg.conf. Xorg has the xv useflag set. Do I have to configure anything else to get xv or is this realy not available for i810?

VinzC · Post by **VinzC** » Sat May 21, 2005 3:21 pm

seppelrockt wrote:Why the hell doesn't xv work? Mplayer complains that the xv is not available for my driver. Remeber, I use vanilla 2.6.12rc4 + xorg-x11-6.8.99.5 WITHOUT any DRI snapshots. DRI works and I have the i810 driver in xorg.conf. Xorg has the xv useflag set. Do I have to configure anything else to get xv or is this realy not available for i810?

Have you set VIDEO_CARDS="i810" variable in your make.conf?

seppelrockt · Post by **seppelrockt** » Sat May 21, 2005 4:19 pm

VinzC wrote: Have you set VIDEO_CARDS="i810" variable in your make.conf?

No, I haven't ... When I set this and remerge xorg-x11, will the apropriate xv driver be build? I couldn't find any hint in the docs about it.

Edit: Remember, I use the DRI from the kernel, in case you thought I use some extern DRi and didn`t specify the graphics card. It would be nice to know whether somebody has xv working and whether special configuration in xorf.conf or maybe make.cong is needed? xv doesn't have to be emerged, right? I mean there is an xv ebuild in portage but this seems to be something different, doesn't it? Sorry for my silly questions, I only used nvidia driver before and never had problems with xv ... have to learn ...

Thanks for the help so far
seppelrockt

VinzC · Post by **VinzC** » Sat May 21, 2005 5:03 pm

seppelrockt wrote:
VinzC wrote: Have you set VIDEO_CARDS="i810" variable in your make.conf?
No, I haven't ... When I set this and remerge xorg-x11, will the apropriate xv driver be build? I couldn't find any hint in the docs about it.

Edit: Remember, I use the DRI from the kernel, in case you thought I use some extern DRi and didn`t specify the graphics card. It would be nice to know whether somebody has xv working and whether special configuration in xorf.conf or maybe make.cong is needed? xv doesn't have to be emerged, right? I mean there is an xv ebuild in portage but this seems to be something different, doesn't it? Sorry for my silly questions, I only used nvidia driver before and never had problems with xv ... have to learn ...

Thanks for the help so far
seppelrockt

I have set the variable to "i810 i915"; one never knows. But I also have USE flag xv set and I don't get the error message that you have. I assume xv works correctly. Note I re-emerged XOrg multiple times. Try to set that flag and recompile XOrg.