Page 1 of 37 12311 ... LastLast
Results 1 to 10 of 363

Thread: Testing latest -intel in Ubuntu

  1. #1
    Join Date
    May 2008
    Posts
    343

    Default Testing latest -intel in Ubuntu

    There is quite some discussion on intel performance in Ubuntu 8.10, for instance in this bug report: https://bugs.launchpad.net/bugs/252094

    I'll open this thread in the hope of bringing the discussion here since it doesn't really all belong in a bug report.

    Using Jaunty (Ubuntu 9.04 to-be), if you're into experimental stuff, you can install updated Xorg packages from the xorg-edgers repository https://launchpad.net/~xorg-edgers/+archive

    The packages can also be tried out on a live CD (see the link on the repository homepage) for those who do not want to mess up their systems. Unfortunately, no official alpha live CD of Jaunty is released yet, but it is expected before Christmas. The daily-live builds work (http://cdimage.ubuntu.com/daily-live/current/), but as of today they still have the old 2.6.27 kernel. Anyway I recommend everyone that can to already install Jaunty to a separate partition.

    The Jaunty 2.6.28 kernel (deb packages) can be found at https://edge.launchpad.net/ubuntu/+source/linux (click on the latest version and eventually you'll find the deb for your architecture). The Jaunty kernel also installs without problems in Intrepid. Some people have successfully installed the Jaunty kernel and the Jaunty xorg-edgers packages in their Intrepid system, but don't count on that to work at any time.

  2. #2
    Join Date
    May 2008
    Posts
    343

    Default

    The current version of the -intel driver in the xorg-edgers repository can be confusing. It is 2.4.97 since this was the version inside configure.ac on the git trunk at the time the package was built, and this ends up in the package version automatically (a feature of the auto-xorg-git script which builds these packages pretty much automatically).

    On the 2.5.1 branch, the version is 2.5.1 of course. But the trunk should be considered newer, so our 2.4.97 is actually ahead of 2.5.1. You have to convince your package manager (dpkg) about this when it complains about downgrading

    Anyway, just yesterday the configure.ac on git trunk was updated to state 2.6.99.1, so later packages will have this version...

  3. #3
    Join Date
    Dec 2008
    Posts
    4

    Default

    Hi im using intrepid (64bit)... and have upgraded to 2.6.28-2-generic and all xedgers jaunty package but no big improvement tested using glxgears
    my chipset is GM965/GL960
    is there any option to enable in xorg.conf? please help

  4. #4
    Join Date
    Dec 2008
    Posts
    1

    Default

    Quote Originally Posted by Biji View Post
    Hi im using intrepid (64bit)... and have upgraded to 2.6.28-2-generic and all xedgers jaunty package but no big improvement tested using glxgears
    my chipset is GM965/GL960
    is there any option to enable in xorg.conf? please help
    What is your FPS? Note that for me I only saw improvement after restarting X (before GEM could not be initialized).

    You can also try renaming xorg.conf to let X autodetect everything, it might give better results.

  5. #5
    Join Date
    May 2008
    Posts
    343

    Default

    Quote Originally Posted by Biji View Post
    Hi im using intrepid (64bit)... and have upgraded to 2.6.28-2-generic and all xedgers jaunty package but no big improvement tested using glxgears
    my chipset is GM965/GL960
    is there any option to enable in xorg.conf? please help
    You did upgrade to 2.4.97 of course? Without seeing your Xorg.0.log it is difficult to diagnose anything.

    BTW, I should mention that I don't have any Intel card myself, so this is untested from my side. But apparently it works for some others, so I suggest you closely follow their instructions.

  6. #6
    Join Date
    Dec 2008
    Posts
    4

    Default

    Quote Originally Posted by ruisselet View Post
    What is your FPS? Note that for me I only saw improvement after restarting X (before GEM could not be initialized).

    You can also try renaming xorg.conf to let X autodetect everything, it might give better results.
    fps ranging from 550-600.. i have rebooted my system after update..

    yup, i'm using bare xorg.conf and
    ii xserver-xorg-v 2:2.4.97.0+git X.Org X server -- Intel i8xx, i9xx display d


    Here is my xorg.log (incomplete):

    (II) Matched intel from file name intel.ids
    (==) Matched intel for the autoconfigured driver
    (II) LoadModule: "intel"
    (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
    (II) Module intel: vendor="X.Org Foundation"
    (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    (II) intel(0): Creating default Display subsection in Screen section
    (==) intel(0): Depth 24, (==) framebuffer bpp 32
    (==) intel(0): RGB weight 888
    (==) intel(0): Default visual is TrueColor
    (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
    (--) intel(0): Chipset: "965GM"
    (--) intel(0): Linear framebuffer at 0xD0000000
    (--) intel(0): IO registers at addr 0xF8000000
    (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
    (==) intel(0): Using EXA for acceleration
    (II) intel(0): 2 display pipes available.
    (II) intel(0): Output VGA using monitor section Configured Monitor
    (II) intel(0): Output LVDS has no monitor section
    (II) intel(0): I2C bus "LVDSDDC_C" initialized.
    (II) intel(0): Attempting to determine panel fixed mode.
    (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
    (II) intel(0): EDID vendor "SEC", prod id 13140
    (II) intel(0): found backlight control method /sys/class/backlight/acpi_video0
    (II) intel(0): Output TV has no monitor section
    (II) intel(0): EDID vendor "SEC", prod id 13140
    (II) intel(0): Output VGA disconnected
    (II) intel(0): Output LVDS connected
    (II) intel(0): Output TV disconnected
    (II) intel(0): Using exact sizes for initial modes
    (II) intel(0): Output LVDS using initial mode 1280x800
    (II) intel(0): detected 512 kB GTT.
    (II) intel(0): detected 7676 kB stolen memory.
    (==) intel(0): video overlay key set to 0x101fe
    (==) intel(0): Intel XvMC decoder disabled
    (==) intel(0): Will not try to enable page flipping
    (==) intel(0): Triple buffering disabled
    (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) intel(0): DPI set to (96, 96)
    (II) intel(0): Comparing regs from server start up to After PreInit
    (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd0000009
    (WW) intel(0): PP_STATUS before: on, ready, sequencing idle
    (WW) intel(0): PP_STATUS after: on, ready, sequencing on


    (II) intel(0): Kernel reported 488960 total, 1 used
    (II) intel(0): I830CheckAvailableMemory: 1955836 kB available
    (II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) intel(0): [drm] framebuffer mapped by ddx driver
    (II) intel(0): [drm] added 1 reserved context for kernel
    (II) intel(0): X context handle = 0x1
    (II) intel(0): [drm] installed DRM signal handler
    (**) intel(0): Framebuffer compression disabled
    (**) intel(0): Tiling enabled
    (==) intel(0): VideoRam: 262144 KB
    (II) intel(0): Attempting memory allocation with tiled buffers.
    (II) intel(0): Tiled allocation successful.
    (II) intel(0): [drm] Registers = 0xf8000000
    (II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
    (II) intel(0): [dri] visual configs initialized
    (II) intel(0): Page Flipping disabled
    (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    (==) intel(0): Backing store disabled
    (==) intel(0): Silken mouse enabled
    (II) intel(0): Initializing HW Cursor
    (II) intel(0): [DRI] installation complete
    (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0cd40000 (pgoffset 52544)
    (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0e000000 (pgoffset 57344)
    (II) intel(0): Fixed memory allocation layout:
    (II) intel(0): 0x00000000-0x00000fff: power context (4 kB)
    (II) intel(0): 0x0077f000: end of stolen memory
    (II) intel(0): 0x0077f000-0x0cd3ffff: DRI memory manager (202500 kB)
    (II) intel(0): 0x0cd40000-0x0dffffff: exa offscreen (19200 kB)
    (II) intel(0): 0x0e000000-0x0fffffff: classic textures (32768 kB)
    (II) intel(0): 0x10000000: end of aperture
    (II) intel(0): BO memory allocation layout:
    (II) intel(0): 0x0077f000: start of memory manager
    (II) intel(0): 0x0079f000-0x00ddefff: depth buffer (6400 kB) Y tiled
    (II) intel(0): 0x00f9f000-0x015defff: back buffer (6400 kB) X tiled
    (II) intel(0): 0x01800000-0x01e3ffff: front buffer (6400 kB) X tiled
    (II) intel(0): 0x0179f000-0x0179ffff: overlay registers (4 kB)
    (II) intel(0): 0x017a0000-0x017aefff: exa G965 state buffer (60 kB)
    (II) intel(0): 0x017b0000-0x017b7fff: logical 3D context (32 kB)
    (II) intel(0): 0x017b8000-0x017c1fff: HW cursors (40 kB)
    (II) intel(0): 0x0cd40000: end of memory manager
    (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
    (WW) intel(0): Existing errors found in hardware state.
    (II) intel(0): using SSC reference clock of 96 MHz
    (II) intel(0): Selecting standard 18 bit TMDS pixel format.
    (II) intel(0): Output configuration:
    (II) intel(0): Pipe A is off
    (II) intel(0): Display plane A is now disabled and connected to pipe A.
    (II) intel(0): Pipe B is on
    (II) intel(0): Display plane B is now enabled and connected to pipe B.
    (II) intel(0): Output VGA is connected to pipe none
    (II) intel(0): Output LVDS is connected to pipe B
    (II) intel(0): Output TV is connected to pipe none
    (II) intel(0): [drm] mapped front buffer at 0xd1800000, handle = 0xd1800000
    (II) intel(0): [drm] mapped back buffer at 0xd0f9f000, handle = 0xd0f9f000
    (II) intel(0): [drm] mapped depth buffer at 0xd079f000, handle = 0xd079f000
    (II) intel(0): [drm] mapped classic textures at 0xde000000, handle = 0xde000000
    (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (II) intel(0): DPMS enabled
    (II) intel(0): Set up textured video
    (II) intel(0): Set up overlay video
    (II) intel(0): direct rendering: Enabled
    (II) intel(0): Setting screen physical size to 303 x 190

  7. #7
    Join Date
    May 2008
    Posts
    343

    Default

    The current drm-modules-source does not build against the new 2.6.28-2-generic kernel in Jaunty, due to some incompatibilities in the nv50 kernel-mode-setting code. If you're only interested in i915 (intel) anyway, you can specify only the i915 modules to be compiled, and save compile time also:
    Code:
    sudo env DRM_MODULES="i915" module-assistant -t auto-install drm-modules
    Last edited by tormod; 12-06-2008 at 08:15 AM. Reason: typo

  8. #8
    Join Date
    Dec 2008
    Posts
    4

    Default

    wow.. this is kinda new for me.. i will figure out what you mean..
    1. download drm-modules-source
    2. install module-assistant
    3. and recompile drm module
    is that right?

  9. #9
    Join Date
    May 2008
    Posts
    343

    Default

    Biji, that posting was not meant for you in particular, I don't whether using stock drm modules or those from git works better for you.

    When installing drm-modules-source, it will drag in module-assistant as a dependency. Then you just use the command I gave, which will build and install the modules. If you later want to go back to the official modules, you can just uninstall the package drm-modules-2.6.2* which was built and installed by module-assistant.

  10. #10
    Join Date
    May 2008
    Posts
    343

    Default

    For more information on the status of GEM and DRI2, see Eric Anholt's blog http://anholt.livejournal.com/40208.html

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •