public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] KDE4 desktop effects
Date: Thu, 21 Aug 2008 13:14:22 +0000	[thread overview]
Message-ID: <d257c3560808210614s2718dd5bib41b1a4f418d547e@mail.gmail.com> (raw)
In-Reply-To: <48AC3C32.7050906@ercbroadband.org>


[-- Attachment #1.1: Type: text/plain, Size: 11842 bytes --]

2008/8/20 Mark Haney <mhaney@ercbroadband.org>

> Beso wrote:
>
>
>>>
>> well, the radeon driver for me works with compiz-fusion and kde4 (either
>> emerald or kwin-decorator-4) and is fantastic. also drm, exa and 2d video
>> playback is fantastic.
>> the only drawback is the following:
>> you'll need to use live ebuilds from the x11-overlay. i've been with them
>> for about  6 months now and i can tell you that everything works very well
>> (no instability or similar issues).
>> before starting to use them i'd advice you to tell me what board you have
>> and, since probably is equal to one of my 2 laptop boards (x200m rs480 or
>> x12xx, rs690) i can pass you all the configs to have everything working. a
>> full live xorg build (a partial one would cause you some instability
>> issues)
>> that includes xorg-protos, xorg-libs, xorg-server, mesa, drivers would
>> take
>> about 3-4 hours, but you might be forced to reinstall all kde4 after that
>> (this happens often after a new rebuild of xorg-git) and so you'll still
>> need around the old 3.5 installation. in fact i have compiz enabled by
>> default on that one and i start it manually on kde4 since sometime it has
>> some issues on startup with setting the kwindecorator4.
>> if you'll tell me that you'll be willing to use this method i'll prepare a
>> walkthrough of everything you'll need to install, in which order, what
>> overlays you'll need to use (you'll want desktop-effects for
>> compiz-fusion)
>> and what options you'll want to enable and use on the board. to do
>> everything in a fine way you'll probably take about one day of work
>> (including xorg-modular rebuild and kde4 rebuild).
>> also i reccomend the setup of portage-tmpfs on /tmpfs so that the
>> compilation speed would drammatically increase.
>> let me know if you're interested. if you're not then you won't be able to
>> use any desktop effect (not on kde3.5 or on kde4) and since i find out
>> some
>> compiz effects very PRODUCTIVE for business environments (i didn't
>> understood this until i've used compiz for about a week) it would be a
>> shame
>> not to use it.
>>
>>
> I am all for it.  Please enlighten me. My laptop has a Radeon XPress 200M.
>  The box is a Compaq Presario R4000 and I"ve had it for about 3 years now.
>  It's been the most rock solid laptop I've ever owned and it runs like a
> scalded dog on compiles.  I'm interested in getting all the info I can on
> getting this to work.
>

first of all you'd add 3 overlays:

the first one will be your personal overlay (since you'll need some modified
ebuilds and you'd want to put them there instead of modifying them all the
time in their original overlay).
you'll add the following directory as root: mkdir -p
/var/portage/personal-overlay and then assign it to portage: chown
portage:portage /var/portage/ -R

now you'll install layman (if you already don't have it): emerge layman
then go and edit the file /etc/layman/layman.cfg by pointing the storage to
this directory:

#-----------------------------------------------------------
# Defines the directory where overlays should be installed

storage   : /var/portage/layman


then you'll do a layman -a desktop-effects to add the first overlay
and layman -a x11
if one of them would fail then you should fetch the list of repos with
layman -f and add it again. it should work at that time.
you also should sync these 2 overlays once a week with layman -s.

then you go and edit /etc/make.conf to add the new layman repos and the
personal overlay by adding the following lines:

source /var/portage/layman/make.conf
PORTDIR_OVERLAY="/var/portage/personal-overlay"

the next step is to configure the various options of layman repos by editing
/var/portage/layman/make.conf.

and assure that the directories in which you've fetched the overlays are
listed here.
you should have the 2 directories (/var/portage/layman/x11 and
/var/portage/layman/desktop-effects) listed here.

now you have to unmask the packages you want to install by adding the
keyword and then unmask them in portage.
for the desktop-effects overlay you don't have much trouble cause there's a
good documentation in the /var/portage/layman/desktop-effects/Documentation
directory. you already have keywords and unmasks set there as a set to
install compiz-fusion.

you take the x11.tar.gz in attachment and uncompress it in the x11 overlay.
you have some files there:
in the Documentation directory you have the keywords for the packages and
the unmask of the packages you want to install while in the sets directory
you have some sets for the various stuff you'll need to install (x11-protos
x11-libs x11-base). you copy the keyword and unmask files in the portage
conf dir and then you can go and prepare the ebuilds in your personal
overlay.
you take the x11-drivers.tar.gz and extract it in the personal overlay.

now, before compiling the new server you have to recompile your kernel. i
assume you use the 2.6.26 kernel (i haven't yet tested this in the r1
release).
you have to apply this patch
http://people.freedesktop.org/~keithp/gem_patches/0001-Export-shmem_file_setup-for-DRM-GEM.patch<http://people.freedesktop.org/%7Ekeithp/gem_patches/0001-Export-shmem_file_setup-for-DRM-GEM.patch>
on the kernel with patch -p1 < <location of saved patch file>/patch file
after you go to the /usr/src/linux directory.

use flags to use for xorg-server and mesa:

[ Colour Code : set unset ]
[ Legend : Left column  (U) - USE flags from make.conf              ]
[        : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for x11-base/xorg-server-9999 ]
 U I
 - - 3dfx                      : Enable support for Voodoo chipsets, also
called as 3DFX and TDFX
 - - debug                     : Enable extra debug codepaths, like asserts
and extra output. If you want to get meaningful backtraces see
http://www.gentoo.org/proj/en/qa/backtraces.xml

 - - dmx                       : Build the Distributed Multiheaded X
server

 + + dri                       : Enable direct rendering: used for
accelerated 3D and some 2D, like
DMA
 + + hal                       : Enable Hardware Abstraction Layer (HAL)
support

 - - input_devices_acecad      :
<unknown>

 - - input_devices_aiptek      :
<unknown>

 - - input_devices_calcomp     :
<unknown>

 - - input_devices_citron      :
<unknown>

 - - input_devices_digitaledge :
<unknown>

 - - input_devices_dmc         :
<unknown>

 - - input_devices_dynapro     :
<unknown>

 - - input_devices_elo2300     :
<unknown>

 - - input_devices_elographics :
<unknown>

 + + input_devices_evdev       :
<unknown>

 - - input_devices_fpit        :
<unknown>

 - - input_devices_hyperpen    :
<unknown>

 - - input_devices_jamstudio   :
<unknown>

 - - input_devices_joystick    :
<unknown>

 + + input_devices_keyboard    :
<unknown>

 - - input_devices_magellan    : <unknown>
 - - input_devices_microtouch  : <unknown>
 + + input_devices_mouse       : <unknown>
 - - input_devices_mutouch     : <unknown>
 - - input_devices_palmax      : <unknown>
 - - input_devices_penmount    : <unknown>
 - - input_devices_spaceorb    : <unknown>
 - - input_devices_summa       : <unknown>
 + + input_devices_synaptics   : <unknown>
 - - input_devices_tek4957     : <unknown>
 - - input_devices_ur98        : <unknown>
 - - input_devices_vmmouse     : <unknown>
 + - input_devices_void        : <unknown>
 - - input_devices_wacom       : <unknown>
 + + ipv6                      : Adds support for IP version 6
 - - kdrive                    : Build the kdrive X servers
 - - minimal                   : Install a very minimal build (disables, for
example, plugins, fonts, most drivers, non-critical features)
 - - nptl                      : Enable support for Native POSIX Threads
Library, the new threading module (requires linux-2.6 or better usually)
 - + sdl                       : Adds support for Simple Direct Layer (media
library)
 - - video_cards_fbdev         : <unknown>
 - - video_cards_i810          : <unknown>
 - - video_cards_mach64        : <unknown>
 - - video_cards_mga           : <unknown>
 - - video_cards_nv            : <unknown>
 - - video_cards_r128          : <unknown>
 + + video_cards_radeon        : <unknown>
 - - video_cards_rendition     : <unknown>
 - - video_cards_savage        : <unknown>
 - - video_cards_tdfx          : <unknown>
 + - video_cards_vesa          : <unknown>
 - - video_cards_vmware        : <unknown>
 - - video_cards_xgi           : <unknown>
 + + xorg                      : Build the Xorg X server (HIGHLY
RECOMMENDED)


[ Colour Code : set unset ]
[ Legend : Left column  (U) - USE flags from make.conf              ]

[        : Right column (I) - USE flags packages was installed with ]
[ Found these USE variables for media-libs/mesa-9999 ]
 U I
 - - debug               : Enable extra debug codepaths, like asserts and
extra output. If you want to get meaningful backtraces see
http://www.gentoo.org/proj/en/qa/backtraces.xml
 - - doc                 : Adds extra documentation (API, Javadoc, etc)
 - - kernel_FreeBSD      : <unknown>
 + + motif               : Adds support for the Motif toolkit
 - - nptl                : Enable support for Native POSIX Threads Library,
the new threading module (requires linux-2.6 or better usually)
 - - pic                 : Build Position Independent Code.  Do not utilize
this flag unless you know what you're doing
 - - video_cards_i810    : <unknown>
 - - video_cards_mach64  : <unknown>
 - - video_cards_mga     : <unknown>
 - - video_cards_none    : <unknown>
 - - video_cards_r128    : <unknown>
 + + video_cards_radeon  : <unknown>
 - - video_cards_s3virge : <unknown>
 - - video_cards_savage  : <unknown>
 - - video_cards_sis     : <unknown>
 - - video_cards_sunffb  : <unknown>
 - - video_cards_tdfx    : <unknown>
 - - video_cards_trident : <unknown>
 - - video_cards_via     : <unknown>
 + + xcb                 : Support the X C-language Binding, a replacement
for Xlib

after that you might start compiling the x11 live packages by starting with
the x11-protos, then going with x11-libs and then x11-base. you might need
to keyword or unmask some other packages around and just do that if
something needs them. you might also have some fails on some ebuilds. the
following ebuilds are known to fail:
libXaw might fail; cairo and glitz probably fail due to some autoconf issues
(i don't know why but in the past they used to work then started not working
anymore), libxcb will surely fail and you might need to remove the installed
one before installing the new one. this approach works fine with all the
packages that fail for the missing libxcb-xlib.la file in the new libxcb.
after you've finished installing the xorg-server then you need to install
the drivers (you're almost there). first install the following:
xf86-input-keyboard xf86-input-mouse xf86-input-evdev xf86-video-ati (if the
new xorg-server hasn't yet pushed them in). now the synaptics driver doesn't
build anymore and i'm still struggling with it. for the moment you'll need
to use the xf86-input-synaptics driver, instead (the one in the personal
overlay).

the last attachment is the xorg.conf for use with xf86-video-ati driver.

sorry for the delay but it took me some time to write down everything.

for the compile into ram stuff i'll post the next time or you could follow
the instruction from gentoo wiki. the basis is that you'll point the
/var/tmp/portage folder to /tmp. i personally do this in /etc/local where i
create a folder in /tmp, i assign it the tmpfs permissions (chmod 1777) then
i mount in bind this folder to /var/tmp/portage.
the problem is that when mounting /tmp in fstab you'll need some tweaks on
the tmp dimension and you'll need to look out into your ram space and swap
space to see how to set this.

-- 
dott. ing. beso

[-- Attachment #1.2: Type: text/html, Size: 30641 bytes --]

[-- Attachment #2: x11.tar.gz --]
[-- Type: application/x-gzip, Size: 1830 bytes --]

[-- Attachment #3: x11-drivers.tar.gz --]
[-- Type: application/x-gzip, Size: 618 bytes --]

[-- Attachment #4: xorg.conf --]
[-- Type: application/octet-stream, Size: 4141 bytes --]


Section "Files"
EndSection

Section "ServerFlags"
  Option	"AllowMouseOpenFail" "off"
  Option	"IgnoreABI" "on"
  Option	"AIGLX" "on"
EndSection

Section "Module"
  Load	       "drm"
  Load         "dbe"
  Load         "type1"
  Load         "freetype"
  Load         "extmod"
  Load         "glx"
  Load         "dri"
EndSection

Section "InputDevice"
  Driver       "evdev"
  Identifier   "Keyboard[0]"
  Option	"Name" "AT Translated Set 2 keyboard"
  Option       "Protocol" "Standard"
  Option       "XkbLayout" "it"
  Option       "XkbModel" "pc102"
  Option       "XkbRules" "xorg"
EndSection


Section "InputDevice"
	Identifier   "Mouse[1]"
        Driver      "evdev"
        Option      "evBits"        "+1-2"
        Option      "keyBits"       "~272-287"
        Option      "relBits"       "~0-2 ~6 ~8"
        Option      "Pass"          "3"
EndSection

Section "InputDevice"
  Driver       "synaptics"
  Identifier   "Mouse[3]"
  Option       "AccelFactor" "0.1"
  Option       "BottomEdge" "650"
  Option       "Buttons" "5"
  Option       "CircScrollDelta" "0.1"
  Option       "CircScrollTrigger" "2"
  Option       "CircularScrolling" "1"
  Option       "Device" "/dev/input/mice"
  Option       "EdgeMotionMaxSpeed" "15"
  Option       "EdgeMotionMinSpeed" "15"
  Option       "Emulate3Buttons" "on"
  Option       "EmulateMidButtonTime" "75"
  Option       "FingerHigh" "15"
  Option       "FingerLow" "14"
  Option       "HorizScrollDelta" "20"
  Option       "InputFashion" "Mouse"
  Option       "LeftEdge" "120"
  Option       "MaxSpeed" "3"
  Option       "MaxTapMove" "110"
  Option       "MaxTapTime" "180"
  Option       "MinSpeed" "0.2"
  Option       "Name" "ALPS;Touchpad"
  Option       "Protocol" "auto-dev"
  Option       "RightEdge" "830"
  Option       "SHMConfig" "on"
  Option       "TopEdge" "120"
  Option       "UpDownScrolling" "1"
  Option       "Vendor" "Sysp"
  Option       "VertScrollDelta" "20"
  Option       "ZAxisMapping" "4 5"
EndSection


Section "Monitor"
  Identifier   "Monitor[0]"
  Option       "DPMS" "true"
  UseModes     "Modes[0]"
EndSection

Section "Modes"
  Identifier   "Modes[0]"
EndSection

Section "Screen"
  DefaultDepth 24
  SubSection "Display"
    Depth      15
    Modes      "1280x800" "1280x768" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" "1440x900"
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "1280x800" "1280x768" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" "1440x900"
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "1280x800" "1280x768" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" "1440x900"
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "1280x800" "1280x768" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x480" "1440x900"
  EndSubSection
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
EndSection


Section "Device"
  BoardName	"Radeon XPRESS 200M 5975 (PCIE)"
  BusID		"1:5:0"
  Driver	"radeon"
  Identifier	"Device[0]"
  VendorName	"Fujitsu-Siemens Computers"
  Option	"AccelDFS" "true"
#  Option	"AccelMethod" "XAA"
  Option	"AccelMethod" "EXA"
#  Option        "BackingStore" "true"
#  Option	"ColorTiling"   "on"
  Option	"DynamicClocks" "on"
  Option	"DRI" "true"
  Option	"EnableDepthMoves" "yes"
#  Option	"EnablePageFlip" "true"
  Option	"mtrr" "on"
  Option	"no_accel" "no"
  Option	"RenderAccel" "true"
#  Option	"SubPixelOrder" "none"
#  Option	"XAANoOffscreenPixmaps" "True"
#  Option	"TVOutput" "PAL"
#  Option 	"ForceTVOut" "true"
#  Option 	"TVStandard" "pal"
EndSection


Section "ServerLayout"
  Identifier   "Layout[all]"
  InputDevice  "Keyboard[0]" "CoreKeyboard"
  InputDevice  "Mouse[1]" "CorePointer"
  InputDevice  "Mouse[3]" "SendCoreEvents"
  Option       "Clone" "off"
  Option       "Xinerama" "off"
  Option       "OffTime" "5"
  Screen       "Screen[0]"
EndSection

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

Section "Extensions"
  Option	"DAMAGE" "true"
  Option	"RENDER" "true"
  Option	"Composite" "Enable"
EndSection


  parent reply	other threads:[~2008-08-21 13:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 14:20 [gentoo-amd64] KDE4 desktop effects Mark Haney
2008-08-20 14:24 ` Fernando Boaglio
2008-08-20 14:30   ` Mark Haney
2008-08-20 14:39   ` Beso
2008-08-20 14:48     ` Mark Haney
2008-08-20 14:53       ` Beso
2008-08-20 15:08         ` Mark Haney
2008-08-20 15:24           ` Beso
2008-08-20 15:45             ` Mark Haney
2008-08-20 16:45               ` Beso
2008-08-22 11:16                 ` Mark Haney
2008-08-22 13:59                   ` Beso
2008-08-22 14:57                     ` Beso
2008-08-21 13:14               ` Beso [this message]
2008-08-20 16:12           ` Volker Armin Hemmann
2008-09-03 15:39 ` Marc Redmann
2008-09-03 15:53   ` Beso
2008-09-03 17:12     ` Mark Haney
2008-09-04  8:58       ` Beso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d257c3560808210614s2718dd5bib41b1a4f418d547e@mail.gmail.com \
    --to=givemesugarr@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox