An upgrade on one of my machines from xorg-server-1.4.2 to 1.5.0 prevented any graphical login manager from working. I could not find any error messages - KDM and GDM both simply failed to start. Downgrading back to 1.4.2 re-enabled the graphical login manager of my choice. Reproducible: Always Steps to Reproduce: 1. Use ~arch (mine is x86) 2. emerge --sync (make sure you have the latest) 3. emerge xorg-server (should give you 1.5.0) 4. Assuming you have a graphical login manager initiated by xdm or rc.conf, reboot or /etc/init.d/xdm restart. Actual Results: Graphical login fails. Expected Results: Start graphical login. Could not find any errors in the logs other than standard xorg stuff that the system spits out every time it starts up anyway. I will happily post more info if someone tells me what I should post. :-)
Have you tried to see if `startx` works ?
Attach /var/log/Xorg.0.log generated while running 1.5.0, and also your xorg.conf. Do you happen to use synaptics driver? There is a known crashing bug that came up on the latest testing version of synaptics (see bug 237074, looks like the upstream fix just came out)
I don't have 1.5.0 any more, having downgraded. I can say though that using startx didn't work when the terminal login came up instead of the graphical login I was expecting. I can attach my xorg log anyway, if that would help. Maybe version info is in there.
I'm also not using a synaptics driver (this happened on a desktop machine).
In order to work on this bug, maintainers need the log from a crash and your xorg.conf too (unless you run without one, where xorg detects your hardware each time) Switching to and from 1.5.0 should be quick if you build binary packages of both server versions, so hopefully you can get an opportunity soon to get a log from a crash...
Well, as other x11-base/xorg-server-1.5 bug reports have suggested, after the upgrade it's wise to rebuild all modules and drivers for X. so that may be a good approach to a solution of this problem as well - only upgrading xorg-server may not be enough for testing purposes either.
One thing that bit me was that the driver for integrated intel graphics cards changed the name from "i810" to "intel". It would lead to the output the starting Xserver normally gives with one added error line "No devices found".
It would really help if you posted the associated /var/log/Xorg.?.log
I'm going to switch over to 1.5.0 and post the log. Rebuilding all X modules: wouldn't that happen during an emerge -uDN world?
"One thing that bit me was that the driver for integrated intel graphics cards changed the name from "i810" to "intel"." You mean for 1.5.0? Would there be a workaround for that?
Nope, the driver changed its name. I could delete my xorg.conf and it would all run or rename the driver in the xorg.conf from "i810" to "intel" to get X running. If I left the driver name as "i810" X wouldn't start and give me the "Found no devices" error. Thinking about it, maybe there should be a note in the 1.5 xorg server ebuild about that?
There should definitely be a note, or just not change the name. I'm going to give that a try. Do I just change the name from "i810" to "intel" (no caps)?
Yes, just replace i810 with intel
Trying the upgrade again, I noticed that at the end of the emerge, you see: * Messages for package x11-base/xorg-server-1.5.0: * Forcing on xorg-x11 for new enough glxtokens.h... * Users of reduced blanking now need: * Option "ReducedBlanking" * In the relevant Monitor section(s). * Make sure your reduced blanking modelines are safe! * You must rebuild all drivers if upgrading from xorg-server 1.4.1 * or earlier, because the ABI changed. If you cannot start X because * of module version mismatch errors, this is your problem. * You can generate a list of all installed packages in the x11-drivers * category using this command: * emerge portage-utils; qlist -I -C x11-drivers/ I'm trying that now...
Ok, tried the suggestion from the end of the xorg-server emerge, and it didn't work. I do, however, have the log now, and while I'm no expert, it seems like it says it finds the intel driver, but the intel driver itself is not working. xorg.0.log: ----------------------------------- X.Org X Server 1.5.0 Release Date: X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-gentoo-r1 i686 Current Operating System: Linux localhost 2.6.26-gentoo-r1 #2 SMP Fri Aug 29 21:23:25 EST 2008 i686 Build Date: 10 September 2008 10:40:26AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 10 11:05:38 2008 (EE) Unable to locate/open config file (II) Loader magic: 0x81cdb80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (++) using VT number 7 (--) PCI:*(0@0:2:0) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xfea00000/0, 0xe0000000/0, I/O @ 0x0000eff8/0 (--) PCI: (0@0:2:1) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xfeb00000/0 (==) Matched intel for the autoconfigured driver New driver is "intel" (==) Using default built-in configuration (30 lines) (==) --- Start of built-in configuration --- Section "Device" Identifier "Builtin Default intel Device 0" Driver "intel" EndSection Section "Screen" Identifier "Builtin Default intel Screen 0" Device "Builtin Default intel Device 0" EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 0" Driver "vesa" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 0" Device "Builtin Default vesa Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default intel Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 0" EndSection (==) --- End of built-in configuration --- (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default intel Screen 0" (0) (**) | |-->Monitor "<default monitor>" (**) | |-->Device "Builtin Default intel Device 0" (==) No monitor specified for screen "Builtin Default intel Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default fbdev Screen 0" (1) (**) | |-->Monitor "<default monitor>" (**) | |-->Device "Builtin Default fbdev Device 0" (==) No monitor specified for screen "Builtin Default fbdev Screen 0". Using a default monitor configuration. (**) |-->Screen "Builtin Default vesa Screen 0" (2) (**) | |-->Monitor "<default monitor>" (**) | |-->Device "Builtin Default vesa Device 0" (==) No monitor specified for screen "Builtin Default vesa Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/Type1/" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/share/fonts/100dpi/"). (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/75dpi/ (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) System resource ranges: [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B] [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.5.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.5.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 1.1 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.5.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 1.1 (==) AIGLX enabled (==) Exporting typical set of GLX visuals (II) Loading extension GLX (II) LoadModule: "freetype" (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 1.5.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.6 (II) Loading font FreeType (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor="X.Org Foundation" compiled for 1.5.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 1.1 (II) Loading extension XFree86-DRI (II) LoadModule: "intel" (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so dlopen: /usr/lib/xorg/modules/drivers//intel_drv.so: undefined symbol: PictureScreenPrivateIndex (EE) Failed to load /usr/lib/xorg/modules/drivers//intel_drv.so (II) UnloadModule: "intel" (EE) Failed to load module "intel" (loader failed, 7) (II) LoadModule: "fbdev" (WW) Warning, couldn't open module fbdev (II) UnloadModule: "fbdev" (EE) Failed to load module "fbdev" (module does not exist, 0) (II) LoadModule: "vesa" (WW) Warning, couldn't open module vesa (II) UnloadModule: "vesa" (EE) Failed to load module "vesa" (module does not exist, 0) (EE) No drivers available. Fatal server error: no screens found ------------------------------------- Hope this helps. I've had this problem on two machines, now, with different configurations, so it seems like I can rule out my having done something wrong. ;-)
Looks like you did not rebuild the xorg drivers.
Ok... how do I do that, if it's not emerge portage-utils; qlist -I -C x11-drivers/?
qlist -I -C x11-drivers/ only gives you the list, you then emerge those packages. This is support which should be handled elsewhere, forums.gentoo.org or #gentoo on freenode. Not a bug..
Created attachment 165208 [details] Xorg server log
Thanks for the advice. I found the drivers, namely keyboard, mouse and video (i810), and rebuilt them. But something is STILL not working. Despite the fact that I rebuilt the keyboard and mouse modules by re-emerging them, keyboard and mouse did NOT work in terminal 7 when the graphical login came up (although this time, the display DID work). I had to switch to another terminal (which was odd because the keyboard worked - I could ctl-alt-f1, but not move the mouse or type alpha-numeric characters to login via the graphical login), downgrade again back to 1.4.2, and rebuild the modules again. I'm done. 1.5.0 clealy has issues and I'm sticking with 1.4.2 until the next release. If someone wants to take over this thread, that's cool. From the experience I've had so far, I'm still thinking bug, sorry. Plus someone needs to make it clearer what the user needs to do to get it working, or people just won't bother with it (which is where I am now). Attached is my last xorg log.
If I read this log correctly, your problem is simply that you failed to read it. xorg is trying to load evdev driver, but it seems that you don't have it installed, so everything works just like it should.
Dude, it has always done that and I've never had any "evdev" problems before. But I'm willing to explore it. What is evdev and how do I get it to work? I realise this is not a support forum, but from a simple search, I can see a lot of people are reporting all kinds of problems with xorg-server-1.5, so this is in the interest of ruling out bugs as well as reporting bugs. Other people are having keyboard issues with 1.5, such as here: http://bugs.gentoo.org/show_bug.cgi?id=237420 Thanks.
As of now, this is a standard hal/evdev problem. Search the forums. Dozens of threads about it. Here evdev stands for x11-drivers/xf86-input-evdev. Has to be at least 1.2.0, but better go for 2.0.4.
Thanks, I will give that a try. :-)
Hello, xorg-server-1.5.0 is also giving me a lot of trouble... usually it tries to start 3 times then gives up. From a root console, `X` works, so does `xinit`. `rc-config start xdm` with it set to gdm fails miserably though. It's always worked before this. There are no messages in the logs, I have recompiled the intel drivers, I have evdev installed and configured. I'll attach a log and my xorg.conf...
Created attachment 165525 [details] Xorg.0.log
Created attachment 165527 [details] xorg.conf
... and after noticing these: (WW) intel(0): ESR is 0x00000001, instruction error (WW) intel(0): Existing errors found in hardware state. I discovered that rebooting fixed the problem... cross-reference this comment on another bug: http://bugs.gentoo.org/show_bug.cgi?id=237091#c1 Maybe add something to the emerge info saying reboot if you have an intel chip.
I'm about to try this again. What's not very encouraging is shortly before the emerge is done, you see * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures.
Sorry about the double-post. It was not intended. Well, apparently there is a workaround. What I did to get it working was, and the exact order may not be important: * emerge --sync * emerge xorg-server * qlist -I -C x11-drivers/ * emerge those drivers * emerge xorg-x11 (may not be important to xorg-server, but it's part of what I did before it all worked) * emerge hal * emerge xf86-input-evdev Because there are so many critical dependecies to getting xorg-server-1.5.0 working, I think these should be included in the ebuild (note to developers). This would be especially useful for those who want to use Gentoo Linux but aren't so technical-minded. ;-) In other words, there does not appear to be a bug with 1.5.0 after all; however, more dependencies should be included in the ebuild, including specific minimum versions of other required packages.
Uh. Apparently there are also issues with mouse pads on laptops. The one in question: Dell Inspiron 1720. What drivers are needed to make sure mousepads work? Because with the recompiled standard mouse driver, taps on the mousepad do not work. I have to use the buttons. I know - oh, no, all is lost. But I want my hardware to work, and it was working fine with older versions. There are just so many issues with this version, in terms of lack of documentation and the fact the that the ebuild leaves the user wondering what the heck just happened.
see https://bugzilla.redhat.com/show_bug.cgi?id=439386 - that's probably what you're looking for.
Holy schuh-moly. Did I read correctly that someone up and decided to turn off a feature extremely basic to laptops just 'cause some folks no likey? Well, this is off the topic of this bug, anyway, but thanks for the tip. I *might* try to see if there are synaptics upgrades that need to be recompiled, but I'm just as likely to step back down to xorg-server-1.4 and not bother with 1.5 until 1.5.1.
I follow the discuss on here, unmask and re-emerge relevant packages: # emerge --sync # emerge xorg-server # qlist -I -C x11-drivers/ ... # emerge x11-drivers/xf86-input-evdev \ x11-drivers/xf86-input-keyboard \ x11-drivers/xf86-input-mouse \ x11-drivers/xf86-video-i810 fixed Intel_drv.so undefined symbol error. but also failed into memory error. /* Xorg.8.log */ ... (EE) intel(0): Non-contiguous GTT entries: (4096,0x16763fa000) vs (0,0x763fa000) (EE) intel(0): Non-contiguous GTT entries: (135168,0x16763fa000) vs (131072,0x763fa000) (WW) intel(0): xf86AllocateGARTMemory: allocation of 100 pages failed (Cannot allocate memory) ... /* END OF Xorg.8.log */
Changed the summary of this bug report to "is unfriendly toward existing drivers". It really is. Mousepad taps are off. This is bogus. Attached will be the output of trying to emerge the synaptics driver. Come on, guys. Don't mess with basic laptop functionality. Please. I'm downgrading to the previous 1.4 version, for good, or until 1.5.1 is released. Srsly. Enough is enough.
Created attachment 166047 [details] Output of failed emerge of synaptics driver. Complete xorg-server and xorg-x11 is installed. Current versions are just very unfriendly towards existing working drivers from server-1.4.
And yup - I just confirmed the synaptics driver emerges just fine on server-1.4.2. Sounds definitely buggy to me.
This bug is getting _out_of_hand_. Please _all_ of you, open separate bugs for _each_ issue you have. High jacking bugs like that will not help. The rule is simple : one issue => one bug report. For good measure, I'm closing this bug as it's become just a pile of mess. Thanks
Fixed my Keyboard and Mouse as well. Thet may not work if X is set to use evdev and hald is not included in the /etc/rc.conf daemons # emerge hal # rc-update add hald default More info on: http://en.gentoo-wiki.com/wiki/HAL http://wiki.archlinux.org/index.php/Xorg_input_hotplugging
I had the same problem, but I could fix it reemerging xf86-video-intel. Please, try with "emerge xf86-video-intel"
