Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
xorg-x11 6.9.0 with compose cache ebuild [OBSOLETE]
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3 ... 13, 14, 15  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
nxsty
Veteran
Veteran


Joined: 23 Jun 2004
Posts: 1556
Location: .se

PostPosted: Sun Oct 30, 2005 9:47 am    Post subject: xorg-x11 6.9.0 with compose cache ebuild [OBSOLETE] Reply with quote

xorg-x11 6.9.0 with compose cache ebuild [OBSOLETE]

Here is an ebuild for 6.9.0 with the compose cache patches from suse and some additional fixes. It based in the 6.9.9 ebuild in portage but also has:

*Some additional bugfixes from Mandriva and SUSE SRPMS and the freedesktop bugzilla.
*Gcc 4.1 support.
*The Suse compose cache patches for faster applications startup time and less memory usage. The included mkcomposecache program doesn't work so there is currently no way to create the global cache files but the local cache files does work so just create the dir .compose-cache in your home to enable it. Check this bug for more info:
https://bugs.freedesktop.org/show_bug.cgi?id=3104

To use it:

1. Download the overlay from http://snigel.no-ip.com/~nxsty/linux/xorg-x11-overlay.tar.bz2 or http://enderandrew.com/nxsty/xorg-x11-overlay.tar.bz2 or http://www.kriga.net/dl/glibc/xorg-x11-overlay.tar.bz2.
2. Untar it in /usr/local/portage/x11-base/
3. Edit make.conf and make sure you have PORTDIR_OVERLAY="/usr/local/portage"
4. Backup your old xorg-x11 with quickpkg
5. Unmask it by adding =x11-base/xorg-x11-6.9* -* to your /etc/portage/package.keywords and x11-base/xorg-x11 to /etc/portage/package.unmask.
7. emerge xorg-x11
8. Create the dir .compose-cache in your home.

If you want to go back to the stable just unmerge it, remove the entry from package.keywords and re-emerge the stable xorg-x11.

This is of course unsupported but if you have any problems post them here and I'll take a look at it. And rember to report any problems to the freedesktop bugzilla:
https://bugs.freedesktop.org/

Problems?

Evdev support has been merged upstream so if you where using evdev with 6.8.2 you need to change your configuration:
http://floam.sh.nu/index.xhtml?page=guides&section=mx1000

The mouse button configuration has changed so if your'e currently using xmodmap to set your mouse up you might not need to anymore:
https://bugs.freedesktop.org/show_bug.cgi?id=4915
https://bugs.freedesktop.org/show_bug.cgi?id=1900

If GTK configure fails with "configure: error: Xft Pango backend is required for x11 target" try re-emerging pango.

If you can't connect to snigel.no-ip.com try one of the mirrors instead:
http://enderandrew.com/nxsty
http://www.kriga.net/dl/glibc/

Changelog

2006-05-05
*Synced with portage, based on 6.9.0-r1.

2006-04-17
*Synced with portage.

2006-02-12
*Updated the experimental radeon patch again.

2006-02-09
*Updated the experimental radeon patch. Disabled by default but it should work much better than the last.

2005-12-22 (2)
*Added a workaround for building with fontconfig prereleases.

2005-12-22
*It's released!!

2005-12-21
*Disabled the radeon fixes by default, caused too much problems.

2005-12-19
*New snapshot, mostly documentation changes.
*Based on the -rc4 tarball.
*Fixed the compose cache patch, it where previously spreading .orig files all over the source tree.
*Added a gcc 4.1 fix.
*Added some radeon fixes. The corresponding DRM fixes are in kernel 2.6.15-rc6 or later.

2005-12-15
*New snapshot, this brings it up to -rc4 the final rc!
*Removed some upstream applied patches.
*Synced with portage.

2005-12-11
*New snapshot (from yesterday)
*Removed #5258 patch, applied upstream
*Fixed patch for bug #1752, last one was broken

2005-12-09 (2)
*Fixed SRC_URI

2005-12-09
*New snapshot.
*Based on 6.9RC3.
*Updated patch for bug #1752.
*Added patch for bug #5258.
*Added patch to fix the xft/xproto problem.
*Removed 0126_all_4.2.99.3-startx-v2.patch and replaced it with a updated patch from Mandriva.
*Excluded 9400_all_4.3.0-mkcfm-FHS-install.patch and fixed it with a define in the ebuild instead.

2005-12-04
*Removed r300 from develdridrivers as it's not inlcluded in the tree.

2005-12-01
*New snapshot

2005-11-22
*New snapshot.

2005-11-17
*New snapshot.
*Included a patch for the annoying bug #1752.
*Included the compose cache patches. (Ping me if you can get them to work!)

2005-11-11
*New snapshot
*Now based on 6.9-rc2

2005-11-05
*New snapshot


Last edited by nxsty on Mon Jul 24, 2006 9:34 am; edited 47 times in total
Back to top
View user's profile Send private message
mfkr79
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jul 2004
Posts: 143
Location: Italy

PostPosted: Sun Oct 30, 2005 3:17 pm    Post subject: Reply with quote

emerged right now
seems stable as usual
I can confirm that nvidia bin drivers works...
and synaptics driver works too
thank you
_________________
Gentoo ~amd64 on DELL XPS M1530
Back to top
View user's profile Send private message
Diablo82
n00b
n00b


Joined: 23 Jan 2004
Posts: 15

PostPosted: Sun Oct 30, 2005 4:42 pm    Post subject: Reply with quote

I'm posting from xorg 6.9rc1 right now. I've been looking for a nice ebuild for so long :D 'cause I was too lazy to do it myself, so thank you 8)
It's been up and running for 70 minutes with kcompmgr on right now and it looks quite stable...hope it won't crash right now :P
Back to top
View user's profile Send private message
Negated Void
l33t
l33t


Joined: 25 Dec 2002
Posts: 662

PostPosted: Sun Oct 30, 2005 5:14 pm    Post subject: Reply with quote

Any particularily awesome features in this version over what's in portage?
Back to top
View user's profile Send private message
infirit
l33t
l33t


Joined: 11 Jan 2003
Posts: 774
Location: Hoofddorp / The Netherlands

PostPosted: Sun Oct 30, 2005 5:36 pm    Post subject: Reply with quote

Negated Void wrote:
Any particularily awesome features in this version over what's in portage?

Lots of bugfixes for example :wink:

The version in portage is a (i think) a pre _pre version of xorg 6.9 and this one follows upstream with their rc releases.
Like nxsty said gentoo is moving to the modular version and therefore the monolithic version is not updated anymore.
_________________
EASY TO INSTALL = Difficult to install, but instruction manual has pictures.
Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
amorpheus
n00b
n00b


Joined: 20 Dec 2004
Posts: 54

PostPosted: Sun Oct 30, 2005 8:40 pm    Post subject: Reply with quote

hmm.. compiled fine, not sure what the difference is :P just yet

EDIT: Oh and ati drivers work :) 8.18.8 with 2.6.14 gentoo
_________________
#!/usr/bin/amorpheus
Back to top
View user's profile Send private message
pwe
Guru
Guru


Joined: 12 Mar 2005
Posts: 445
Location: Polska aka Poland

PostPosted: Sun Oct 30, 2005 8:52 pm    Post subject: Reply with quote

what is "modular xorg tree" ?? so in portage what version will be in furure? and when?
_________________
there is no empty MHz :)
Back to top
View user's profile Send private message
scoobydu
Veteran
Veteran


Joined: 16 Feb 2003
Posts: 1076
Location: 'Mind the Gap'

PostPosted: Sun Oct 30, 2005 9:44 pm    Post subject: Reply with quote

Well merged on the powerbook ok, so we'll see how it goes ... thx for the build.
_________________
Tyan Tiger K8W, 2xOpteron 240,Powerbook5,6 15" 1.5g, Macbook Black 2g, Mac Mini 1g, Ipod P60g.
| Linux - From a windows user perspective|
Back to top
View user's profile Send private message
sirdilznik
l33t
l33t


Joined: 28 Apr 2005
Posts: 731

PostPosted: Sun Oct 30, 2005 11:55 pm    Post subject: Reply with quote

Emerged fine with gcc-4.0.2-r1. Everything looks good so far. Good work :)
Back to top
View user's profile Send private message
amorpheus
n00b
n00b


Joined: 20 Dec 2004
Posts: 54

PostPosted: Mon Oct 31, 2005 1:20 am    Post subject: Reply with quote

Btw, you spelled Migrating wrong.
_________________
#!/usr/bin/amorpheus
Back to top
View user's profile Send private message
Ma3oxuct
Guru
Guru


Joined: 18 Apr 2003
Posts: 520

PostPosted: Mon Oct 31, 2005 3:01 am    Post subject: Reply with quote

Hmmmm...xorg-x11 stable right now is taking up 400+ megabytes of ram; 600+ a few seconds ago. I guess this is the time for me to grab this cvs version.

emerging it at the moment. When I return from taking a bath, it should be done :). I will report back here if everything goes well, or not.
Back to top
View user's profile Send private message
Cinder6
l33t
l33t


Joined: 05 Aug 2004
Posts: 767
Location: California

PostPosted: Mon Oct 31, 2005 3:22 am    Post subject: Reply with quote

I'll try it out.
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.

Ugly Overload
Back to top
View user's profile Send private message
Ma3oxuct
Guru
Guru


Joined: 18 Apr 2003
Posts: 520

PostPosted: Mon Oct 31, 2005 4:36 am    Post subject: Reply with quote

Wow, I just re-entered into the newest xorg-x11 :).

I do not know about you all, but it works a great deal more smoothly than 6.8.2. I can't wait to play around with the new features :); but for now I have to go to sleep.
Back to top
View user's profile Send private message
Cinder6
l33t
l33t


Joined: 05 Aug 2004
Posts: 767
Location: California

PostPosted: Mon Oct 31, 2005 4:40 am    Post subject: Reply with quote

Well, I emerged it, and it feels smoother for me, as well. :) Nice work as always, nxsty.
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.

Ugly Overload
Back to top
View user's profile Send private message
jarealist
Apprentice
Apprentice


Joined: 07 Oct 2002
Posts: 227

PostPosted: Mon Oct 31, 2005 5:22 am    Post subject: Reply with quote

Another big "thank you" from here. :D Works great with the latest ati-drivers on my laptop. Now to get it installed on the destop.
Back to top
View user's profile Send private message
satanskin
Guru
Guru


Joined: 25 Apr 2005
Posts: 353

PostPosted: Mon Oct 31, 2005 2:02 pm    Post subject: Reply with quote

Wow, I guess I'm the only one having problems huh? Anyway, I emerged it and it won't startx. It fails with an error complaining about evdev (possibly unrecognized or unsupported) and not being able to load my mouse. Anyone have an idea? btw, this is with 6.9_pre20051030.
Back to top
View user's profile Send private message
nxsty
Veteran
Veteran


Joined: 23 Jun 2004
Posts: 1556
Location: .se

PostPosted: Mon Oct 31, 2005 3:02 pm    Post subject: Reply with quote

satanskin wrote:
Wow, I guess I'm the only one having problems huh? Anyway, I emerged it and it won't startx. It fails with an error complaining about evdev (possibly unrecognized or unsupported) and not being able to load my mouse. Anyone have an idea? btw, this is with 6.9_pre20051030.


What's the exact error message? And can you include your xorg.conf? I assume you have evdev support in your kernel.
Back to top
View user's profile Send private message
satanskin
Guru
Guru


Joined: 25 Apr 2005
Posts: 353

PostPosted: Mon Oct 31, 2005 5:15 pm    Post subject: Reply with quote

Here's the relevant part of the Xorg.0.log.old:
Code:
(**) Option "Protocol" "evdev"
(EE) Mouse1: Unknown protocol "evdev"
(EE) PreInit failed for input device "Mouse1"
(II) UnloadModule: "mouse"
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc104"
(**) Keyboard1: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) Keyboard1: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(WW) No core pointer registered
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
No core pointer

Fatal server error:
failed to initialize core devices

Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional informati
on.


And here is my xorg.conf. It is the same working xorg.conf that I used with 6.8.2-r6. Like I said, it works with that version using evdev, so yes I have support in the kernel. Here's the config:
Code:
# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"     # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
   


# This loads the font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

#This loads the composite extension which is needed for real transparency and shadows.
    Section "Extensions"
      Option "Composite" "Enable"
    EndSection


# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath   "/usr/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/local/"
#    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/TrueType/"
#    FontPath   "/usr/share/fonts/freefont/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier   "Keyboard1"
    Driver   "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option   "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg

#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"


    Option "XkbModel"   "pc104"
    Option "XkbLayout"   "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

  Identifier  "Mouse1"
  Driver   "mouse"
  Option   "Protocol" "evdev"
  Option   "Dev Name" "Logitech USB Receiver" # cat /proc/bus/input/devices
  Option   "Dev Phys" "usb-0000:00:02.0-2/input0" # cat /proc/bus/input/devices
  Option   "Device" "/dev/input/event2" # (/dev/input/mice also appears to work)
  Option   "Buttons" "12"
  Option   "ZAxisMapping" "11 12"
  Option   "Resolution" "800"



 # Identifier   "Mouse1"
   # Driver   "mouse"
   # Option "Protocol"    "IMPS/2"
   # Option "Device"      "/dev/input/mouse0"
   # Option "ZAxisMapping" "4 5"
   #Option "Resolution" "800"
# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"   "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"   "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"   "9600"
#    Option "SampleRate"   "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "IBM 21in Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30-120

#    HorizSync   30-64         # multisync
#    HorizSync   31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync   15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-160

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier   "Standard VGA"
    VendorName   "Unknown"
    BoardName   "Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset   "generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam   256

#    Clocks   25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "My GeForce"
    Driver      "nvidia"
    #Driver      "nv"
    Option      "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    #VideoRam    262144
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "My GeForce"
    Monitor     "IBM 21in Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection


And for the kernel:
Code:
thor satanskin # zgrep -i evdev /proc/config.gz
CONFIG_INPUT_EVDEV=y
Back to top
View user's profile Send private message
nxsty
Veteran
Veteran


Joined: 23 Jun 2004
Posts: 1556
Location: .se

PostPosted: Mon Oct 31, 2005 5:41 pm    Post subject: Reply with quote

Quote:
Driver "mouse"
Option "Protocol" "evdev"


I think that's the problem. Remove the protocol line and change driver to "evdev".
Back to top
View user's profile Send private message
Rainmaker
Veteran
Veteran


Joined: 12 Feb 2004
Posts: 1650
Location: /home/NL/ehv/

PostPosted: Mon Oct 31, 2005 11:10 pm    Post subject: Reply with quote

I think I'm the first one that can not even get it to compile...

Code:
/usr/lib/gcc/i686-pc-linux-gnu/4.0.2/../../../../i686-pc-linux-gnu/bin/ld: warning: creating a DT_TEXTREL in object.
rm -f tdfx_dri.so tdfx_dri.so.map
mv -f tdfx_dri.so~ tdfx_dri.so
rm -f ../../../../../../exports/lib/modules/dri/tdfx_dri.so
+ cd ../../../../../../exports/lib/modules/dri
+ ln -s ../../../../lib/GL/mesa/drivers/dri/tdfx/tdfx_dri.so .
make[6]: Leaving directory `/var/tmp/portage/xorg-x11-6.9_pre20051030/work/xc/lib/GL/mesa/drivers/dri/tdfx'
making all in lib/GL/mesa/drivers/dri/ffb...
make[6]: Entering directory `/var/tmp/portage/xorg-x11-6.9_pre20051030/work/xc/lib/GL/mesa/drivers/dri/ffb'
rm -f ffb_bitmap.o
i686-pc-linux-gnu-gcc -c -march=athlon-xp -O3 -pipe -fomit-frame-pointer -fno-strict-aliasing  -ansi -Wno-return-type -w  -I../../../../../../exports/include/X11 -I../../../../../../include/extensions -I../../../../../../extras/Mesa/src/mesa               -I../../../../../../extras/Mesa/src/mesa/main           -I../../../../../../extras/Mesa/src/mesa/glapi          -I../../../../../../extras/Mesa/src/mesa/shader                 -I../../../../../../extras/Mesa/include        -I../../../../../../extras/Mesa/src/mesa/drivers/dri/common              -I../../../../../../extras/Mesa/src/mesa/drivers/dri/ffb -I../../../../../../lib/GL/dri-I../../../../../../exports/include/X11          -I../../../../../../lib/GL/glx -I../../../../../../lib/GL/include               -I../../../../../../programs/Xserver/GL/dri             -I../../../../../../programs/Xserver/hw/xfree86/os-support              -I../../../../../../extras/drm/shared-core              -I../../../../../../lib/GL/dri/drm              -I../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb  -I../../../../../.. -I../../../../../../exports/include   -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L                          -D_POSIX_SOURCE -D_XOPEN_SOURCE                                 -D_BSD_SOURCE -D_SVID_SOURCE                                 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE                             -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS  -D_REENTRANT -DXUSE_MTSAFE_API    -DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA  -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DIN_DRI_DRIVER -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM     -fPIC ffb_bitmap.c
In file included from ffb_xmesa.h:11,
                 from ffb_context.h:11,
                 from ffb_bitmap.c:28:
../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb/ffb_dac.h:322: fout: syntax error before ‘Bool’
../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb/ffb_dac.h:326: fout: syntax error before ‘canshare’
../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb/ffb_dac.h:335: fout: syntax error before ‘}’ token
../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb/ffb_dac.h:341: fout: syntax error before ‘ffb_wid_info_t’
../../../../../../programs/Xserver/hw/xfree86/drivers/sunffb/ffb_dac.h:362: fout: syntax error before ‘ffb_wid_pool_t’


I think it's caused by this struct in the above file (it's in xc/programs/Xserver...):

Code:
typedef struct {
        Bool            InUse;

        /* The following fields are undefined unless InUse is TRUE. */
        int             refcount;
        Bool            canshare;
        unsigned int    wlut_regval;
        int             buffer;         /* 0 = Buffer A, 1 = Buffer B   */
        int             depth;          /* 8 or 32 bpp                  */
        int             greyscale;      /* 1 = greyscale, 0 = color     */
        int             linear;         /* 1 = linear, 0 = non-linear   */
        int             direct;         /* 1 = 24bpp directcolor        */
        int             channel;        /* 0 = X, 1 = R, 2 = G, 3 = B   */
        int             palette;        /* Only PAC2 has multiple CLUTs */
} ffb_wid_info_t;


Should this be:

Code:
typedef ffb_wid_info_t struct {


Or shouldn't this matter?
_________________
If you can't dazzle them with brilliance, baffle them with bullshit.


Last edited by Rainmaker on Mon Oct 31, 2005 11:45 pm; edited 1 time in total
Back to top
View user's profile Send private message
satanskin
Guru
Guru


Joined: 25 Apr 2005
Posts: 353

PostPosted: Mon Oct 31, 2005 11:44 pm    Post subject: Reply with quote

Ok, so I changed those lines to Driver "evdev" like you said and this time it booted a little further. I get to the nvidia bootscreen (which most people dislike yet I had never seen before) and then it just hard locks on me. I can't switch terminals, kill x, nothing. I have to hit the reset button to get it to reboot and then it's all right back to the same. I'm in knoppix at the moment and here is what the latest xorg log shows:

Code:
(II) Initializing extension GLX
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Mouse1: Device: "/dev/input/event2"
(EE) Unable to open evdev device "/dev/input/event2".
(EE) PreInit failed for input device "Mouse1"
(II) UnloadModule: "evdev"

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x8e) [0x44cb4e]
1: /lib/libc.so.6 [0x2aaaab376c50]
2: /lib/libc.so.6 [0x2aaaab3b2707]
3: /lib/libc.so.6(malloc+0x7b) [0x2aaaab3b414b]
4: /usr/X11R6/bin/X(xf86optionListCreate+0xd6) [0x45d736]
5: /usr/X11R6/bin/X(xf86CollectInputOptions+0x2e) [0x45829e]
6: /usr/lib64/modules/input/kbd_drv.so [0x2aaaaca6f268]
7: /usr/X11R6/bin/X(InitInput+0x1a6) [0x430e66]
8: /usr/X11R6/bin/X(main+0x31e) [0x4a6c9e]
9: /lib/libc.so.6(__libc_start_main+0xdc) [0x2aaaab36366c]
10: /usr/X11R6/bin/X [0x43097a]

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
    at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Back to top
View user's profile Send private message
NiLuJe
Guru
Guru


Joined: 06 Nov 2004
Posts: 303
Location: Paris, France

PostPosted: Tue Nov 01, 2005 1:34 am    Post subject: Reply with quote

(EE) Unable to open evdev device "/dev/input/event2".

You could maybe make a udev rule for your mouse, it'll be easier than check dev/input.

And you dont need anymore the Dev * Options for evdev.
Back to top
View user's profile Send private message
satanskin
Guru
Guru


Joined: 25 Apr 2005
Posts: 353

PostPosted: Tue Nov 01, 2005 1:40 am    Post subject: Reply with quote

NiLuJe wrote:
(EE) Unable to open evdev device "/dev/input/event2".

You could maybe make a udev rule for your mouse, it'll be easier than check dev/input.

And you dont need anymore the Dev * Options for evdev.


You possibly have a guide for this? Or could you please explain how? I'd appreciate it!
Back to top
View user's profile Send private message
Tiger683
Veteran
Veteran


Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House

PostPosted: Tue Nov 01, 2005 1:58 am    Post subject: Reply with quote

Use /dev/input/mice, it represents ALL mouse devices on the system.
_________________
Retired gentoo user
Back to top
View user's profile Send private message
satanskin
Guru
Guru


Joined: 25 Apr 2005
Posts: 353

PostPosted: Tue Nov 01, 2005 2:39 am    Post subject: Reply with quote

Tiger683 wrote:
Use /dev/input/mice, it represents ALL mouse devices on the system.


That gives me this:

Code:
(II) Initializing extension GLX
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Mouse1: Device: "/dev/input/mice"
(EE) ioctl EVIOCGBIT failed: Inappropriate ioctl for device
(EE) PreInit failed for input device "Mouse1"
(II) UnloadModule: "evdev"

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x8e) [0x44cb4e]
1: /lib/libc.so.6 [0x2aaaab376c50]
2: /lib/libc.so.6 [0x2aaaab3b2707]
3: /lib/libc.so.6(malloc+0x7b) [0x2aaaab3b414b]
4: /usr/X11R6/bin/X(xf86optionListCreate+0xd6) [0x45d736]
5: /usr/X11R6/bin/X(xf86CollectInputOptions+0x2e) [0x45829e]
6: /usr/lib64/modules/input/kbd_drv.so [0x2aaaaca6f268]
7: /usr/X11R6/bin/X(InitInput+0x1a6) [0x430e66]
8: /usr/X11R6/bin/X(main+0x31e) [0x4a6c9e]
9: /lib/libc.so.6(__libc_start_main+0xdc) [0x2aaaab36366c]
10: /usr/X11R6/bin/X [0x43097a]

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
    at http://wiki.X.Org[/quote]
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page 1, 2, 3 ... 13, 14, 15  Next
Page 1 of 15

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum