[Solved] X11 won't start after fresh install

Hihi!
I've been using Debian for quite some time now but I want to switch to Arch. My notebook is fairly modern and this doesn't mix well with Debian and as such my dGPU is basically unusable. My preferred method of installing Debian is to start headless so I felt quite at home with Arch and got through the install just fine, but I'm having problems launching Openbox among other hardware related issues. I spent yesterday googling and attempting fixes but came up with nothing, so I had to reinstall Debian as I was counting on having a usable computer at the end of the day. I did write down the messages I was getting though, hopefully they are enough to diagnose the issue. My hardware:
AMD A10-5750M (8650G graphics)
AMD Radeon 8970M 2GB
The kernel was the one in the very latest install snapshot (3.12-9 or something)
The first thing I noticed after booting into the fresh install was a warning along these lines
[drm:r600_dma_ring_test] radeon: ring 3 test failed
I ignored it, and preceeded to install the following packages
xorg-server
xorg-utils
xorg-xinit
mesa
xf86-video-ati
openbox
openbox-themes
other things related to the UI I wanted
The ring 3 test warning still occured on reboot after installing X and the radeon drivers. Again I ignored it. My .xinitrc was simply exec openbox-session
I ran startx and it failed, and got a bunch of errors that began right after a reference to "radeon" and the kernel. My xorg log did not get far at all. In fact the last lines were
(II) config/udev: Adding drm device (/dev/dri/card0)
(II) config/udev: Adding drm device (/dev/dri/card1)
And that was literally the end of the log. This is clearly a GPU/driver issue, probably with the 8970M as card1 seems to be the last line? Any help is appreciated
edit: This is the same process I use to install Debian, and using this exact same kernel (plus the Debian patches) I can start X just fine. my dGPU is unusable with the FOSS drivers through as there is no glamor support in Debian. I get segfaults whenever I launch something with DRI_PRIME=1 after setting the 8970M as the offload provider
Last edited by remyze (2014-02-09 04:02:04)

Ok I installed fresh and had the same issues as last time. With KMS early start I still have the same problems launching X and I still have the ring 3 test error (it just appears earlier).
There is nothing pure text in /var/log, I don't know if theres a way to use systemd with wgetpaste, so I took a picture that is hopefully not to difficult to read. I tried to sharpen it up a bit in GIMP.
*see pastebin below*
I also noticed that I get that ring 3 error even when I boot up the Arch installer via USB. I wonder if I should try an older image with an older kernel?
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by remyze (2014-02-09 03:30:24)

Similar Messages

Vista won't start after fresh install of LabVIEW & 4G RAM

Since Vista is such a memory glutton I decided to upgrade my AMD64 box to 4 Gig RAM. Good idea, no? Turns out not. Now Vista won't start. It locks up at the (lack of) progress bar before the log-in screen. After much hollerin' and hair pullin' I reinstalled Vista and now it sees 3.25 Gig. I install updates; everything looks good; I install LabVIEW 8.0 and activate it. At restart WinDoze Vista won't start. Now I want to scream. My Linux (Ubuntu Gutsy) partition runs fine and indicates 3.9 Gig RAM.
What is LabVIEW installing that has caused this? Does anybody have a place to start looking?
Thank You for reading my rantings
LabVIEW 8.0.1; WinDoze XP
aut viam inveniam aut faciam

Well, NI doesn't claim LabVIEW 8.0 is Vista compatible.
If you did the full install, you probably also installed Device Drivers and such. If you used the ones released with 8.0, they are definitely not Vista compatible. Those device drivers will try to load during Vista bootup. If you did, you will need to do a clean uninstall following this procedure. Download the latest drivers from NI's website and see if that fixes your problem.
Message Edited by Matthew Kelton on 02-21-2008 12:50 AM

Portege R830 - Windows won't start after I install Comodo Firewall

Good afternoon,
I purchased today a Portege R830, and after the Windows configuration was over, the first program I installed was the popular free firewall Comodo. After I rebooted, Windows 7 wouldn't start anymore. It would get stuck on the user login screen and I know it's a problem with the firewall because if I make a system restore to the restore point created by the firewall installer, the windows will start again.
So I ask if there is any incompability between the firewall and some software on the Toshiba. Has anyone ever had this problem? I've been trying to solve this issue all day long with no results. I even re-installed Windows 7 using the Toshiba recovery and the issue persists. I really love Comodo, and I want this firewall on my laptop, but Windows just won't start!
Any help would be very apreciated.

Hi jillefsky,
Have you disabled the Windows firewall before you started with Comodo firewall installation? As far as I know Portege R830 is delivered with preinstalled McAfee security software and you should remove this program before you install any other security tools.
Generally speaking this issue has nothing to do with Toshiba and its recommendable to contact Comodo directly. Maybe they know about this issue so they can give you a proper answer.
But I dont understand why this program is so important for you. Windows has already an internal firewall so such programs are not necessary in my opinion. Just install a good antivirus program like AntiVir and activate automatic Windows updates. Thats all!

[SOLVED] Alsa won't start after upgrade

This is my last update:
[2010-07-18 08:59] Running 'pacman -Syu'
[2010-07-18 08:59] synchronizing package lists
[2010-07-18 08:59] starting full system upgrade
[2010-07-18 09:00] upgraded gtk-aurora-engine (1.5.1-1 -> 1.5.1-2)
[2010-07-18 09:00] #####################################
[2010-07-18 09:00] themes are moved in an extra package:
[2010-07-18 09:00] community/murrine-themes-collection
[2010-07-18 09:00] upgraded gtk-engine-murrine (0.90.3-1 -> 0.90.3-2)
[2010-07-18 09:00] upgraded imagemagick (6.6.2.0-22 -> 6.6.2.10-1)
[2010-07-18 09:00] Running OSS update script...
[2010-07-18 09:00]
[2010-07-18 09:00] -------------------------------------------------------------
[2010-07-18 09:00] Open Sound System was updated. Now you should restart the
[2010-07-18 09:00] daemon by running /etc/rc.d/oss restart.
[2010-07-18 09:00]
[2010-07-18 09:00] Please note that OSS stores some of its configuration files
[2010-07-18 09:00] at /usr/lib/oss. If you are upgrading from an older OSS
[2010-07-18 09:00] release and it doesn't work properly, try removing that
[2010-07-18 09:00] directory and reinstall this package.
[2010-07-18 09:00] -------------------------------------------------------------
[2010-07-18 09:00] upgraded oss (4.2_2002-2 -> 4.2_2003-1)
[2010-07-18 09:00] upgraded supertux (0.3.1-5 -> 0.3.3-1)
[2010-07-18 09:00] upgraded xine-lib (1.1.18.1-1 -> 1.1.18.1-2)
Pacman said to restart oss, so I did it. But I got loads of errors and a [FAIL], then I rebooted and got a [FAIL] for shutting down alsa.
Now alsa won't start at boot.
sudo /etc/rc.d/alsa start
Password:
:: Restoring ALSA Levels [BUSY] /usr/sbin/alsactl: load_state:1610: No soundcards found...
[FAIL]
And alsamixer won't run too:
alsamixer
cannot open mixer: No such file or directory
What can I do to fix this?
EDIT: I just removed the oss package and now it works fine
Last edited by spiridow (2010-07-18 08:17:16)

startx at the command line.
I just tried Xorg -reconfigure again, adding the AutoAddDevices = false option - still doesn't work, giving the error about config/hal. Without the option, it just goes back to the terminal with no errors.
Pacman log says the only thing upgraded today (after pacman) was the kernel, nvidia, and kernel-firmware. cdfs conflicted with the new kernel, so I removed it. Then I rebooted, and X stopped working. Downgrading those back again doesn't fix it. I don't get it.
>>EDIT:
Okay - what does cdfs have to do with Xorg???? This makes no sense. I downgraded the kernel pkgs and nvidia again, and this time installed cdfs, which I forgot to do last time. Now X starts. I don't really get it.
Maybe hal in xfce or some plugin needs to use cdfs for something?? I don't really know - but I'm just glad it's working. I guess I'll file a bug report for cdfs so it can be built to the new kernel and hold off upgrading until it's fixed with 2.6.31. sheesh! too weird.
Last edited by userlander (2009-10-10 23:27:36)

Apache won't start after ColdFusion Install

Any suggestions on what to look for, as to why Apache will
not start after installing ColdFusion MX Dev Edition on a Win 2003
Server? Is there something in a log file I could look at? Any help
is appreciated. Also, when I take the JRUN mod out of the Config
file, Apache starts back up..
Thanks,
Brian

If you're using Apache 2.2+ and CFMX 7+, then you need to
apply
a
hotfix for CF.
Once you update the wsconfig.jar file, re-run the Web Server
Configuration Tool. Remove the old Apache mapping and create a new
one.

IPhoto won't open after fresh instal of Lion!

I recently erased my hard drive and did a fresh install of Lion as I am giving my MacBook Pro to my brother as a Xmas present. I used a USB pen to reinstall Lion. I used my time MAchine backup to bring over iPhoto, iMovie and Garageband. Everything works apart from iPhoto. It says "iPhoto cannot be opened because of a problem. Thing is iLife came bundled on my Mac and i did not have to buy it from the App Store. Everything is up to date but it just won;t open. Can anyone help explain why this maybe and help me fix the problem?
Thanks
Matt

iPhoto cannot be opened because of a problem
Matty....
Try holding down the Command + Option keys then launch iPhoto.
Select: Repair the iPhoto Library Data base then click Rebuild.

[SOLVED] CCSM won't start after updating compiz

I just updated compiz, compil-plugins-main, ccsm etc. and ccsm (Compizconfig settings manager) just dont start.
[broi@broi-Archlinux ~]$ ccsm
Info: No sexy-python package found, don't worry it's optional.
Traceback (most recent call last):
File "/usr/bin/ccsm", line 99, in <module>
import compizconfig
ImportError: /usr/lib/python2.7/site-packages/compizconfig.so: undefined symbol: ccsImportFromFile
[broi@broi-Archlinux ~]$
I tried with "python2" or "python3" before I type a .py command (which worked in some issues) but in this one it dont help.
When I try with python 3 -> "python3 /usr/bin/ccsm" I get:
[broi@broi-Archlinux ~]$ python3 /usr/bin/ccsm
File "/usr/bin/ccsm", line 45
if dbus.version < (0, 80, 0):
^
TabError: inconsistent use of tabs and spaces in indentation
[broi@broi-Archlinux ~]$
Thanks.
Solution: Rebuilt the compizconfig-python
UPDATE: Just run update and you will get fixed compizconfig-python.
Last edited by broi (2012-03-23 16:26:25)

Same problem after pacman -Syu (using XFCE).
Not only compiz won't start, my mouse cursor is gone until I open some windows. The window decorations have disappeared (minimize, maximize, close). This is even after removing the fusion-icon from autostart in XFCE and rebooting (afaict, compiz is not running as a process when I list running processes with ps -ef). Also having difficulty switching focus between open windows.
[2012-03-21 14:27] upgraded bash (4.2.024-1 -> 4.2.024-2)
[2012-03-21 14:27] upgraded libcompizconfig (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compizconfig-python (0.8.4-2 -> 0.8.4-3)
[2012-03-21 14:27] upgraded ccsm (0.8.4-2 -> 0.8.4-3)
[2012-03-21 14:27] upgraded compiz-bcop (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compiz-fusion-plugins-main (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compiz-fusion-plugins-extra (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded compizconfig-backend-gconf (0.8.8-1 -> 0.8.8-2)
[2012-03-21 14:27] upgraded device-mapper (2.02.90-1 -> 2.02.95-1)
[2012-03-21 14:27] upgraded emerald-themes (0.6.0-3 -> 0.6.0-4)
[2012-03-21 14:27] upgraded ffmpeg (20120127-3 -> 20120317-1)
[2012-03-21 14:27] upgraded fusion-icon (20101021-1 -> 20120321-1)
[2012-03-21 14:27] upgraded libtasn1 (2.9-2 -> 2.12-1)
[2012-03-21 14:27] upgraded gnutls (3.0.15-1 -> 3.0.17-1)
[2012-03-21 14:27] upgraded grub2-common (1:1.99-6 -> 1:2.00beta2-2)
[2012-03-21 14:27] upgraded grub2-bios (1:1.99-6 -> 1:2.00beta2-2)
[2012-03-21 14:27] upgraded iproute2 (3.2.0-2 -> 3.2.0-3)
[2012-03-21 14:27] upgraded libdrm (2.4.31-1 -> 2.4.32-1)
[2012-03-21 14:27] upgraded lib32-libdrm (2.4.31-1 -> 2.4.32-1)
[2012-03-21 14:27] upgraded lib32-libice (1.0.7-2 -> 1.0.8-1)
[2012-03-21 14:27] upgraded lib32-libxdmcp (1.1.0-2 -> 1.1.1-1)
[2012-03-21 14:27] upgraded lib32-libxcb (1.8.1-1 -> 1.8.1-2)
[2012-03-21 14:27] upgraded lib32-libx11 (1.4.99.901-1 -> 1.4.99.901-2)
[2012-03-21 14:27] upgraded lib32-libxcomposite (0.4.3-2 -> 0.4.3-3)
[2012-03-21 14:27] upgraded lib32-libxext (1.3.0-1 -> 1.3.1-1)
[2012-03-21 14:27] upgraded lib32-libxinerama (1.1.1-2 -> 1.1.2-1)
[2012-03-21 14:27] upgraded lib32-libxrandr (1.3.2-1 -> 1.3.2-2)
[2012-03-21 14:27] upgraded lib32-libxtst (1.2.0-2 -> 1.2.1-1)
[2012-03-21 14:27] upgraded lib32-libxxf86vm (1.1.1-2 -> 1.1.2-1)
[2012-03-21 14:27] upgraded lib32-util-linux (2.20.1-1 -> 2.21-1)
[2012-03-21 14:27] upgraded libftdi (0.19-1 -> 0.20-1)
[2012-03-21 14:27] upgraded linux (3.2.11-1 -> 3.2.12-1)
[2012-03-21 14:27] upgraded live-media (2012.02.29-2 -> 2012.03.20-1)
[2012-03-21 14:27] upgraded lvm2 (2.02.90-1 -> 2.02.95-1)
[2012-03-21 14:27] upgraded mpg123 (1.13.4-2 -> 1.13.6-1)
[2012-03-21 14:27] upgraded neon (0.29.6-3 -> 0.29.6-4)
[2012-03-21 14:28] upgraded openssl (1.0.0.h-1 -> 1.0.1-1)
[2012-03-21 14:28] upgraded psmisc (22.15-1 -> 22.16-1)
[2012-03-21 14:28] upgraded systemd-arch-units (20120311-1 -> 20120317-1)
[2012-03-21 14:28] upgraded vlc (2.0.0-8 -> 2.0.1-1)
[2012-03-21 14:28] upgraded xf86-input-evdev (2.7.0-1 -> 2.7.0-2)
Last edited by David Batson (2012-03-21 21:10:35)

[SOLVED] X won't start after update

I'm running Arch inside a virtual machine, with Virtualbox.
I ran 'sudo pacman -Syu' and let it install everything. It updated a bunch of xorg-* packages, among a few other things, and then I rebooted. Now it seems like X has stopped working. Normally I use SLiM for starting X, but SLiM itself isn't starting up. I tried 'startx' manually but that didn't work either. I can get into a normal CLI-environment just fine though.
Here are pacman.log: http://ix.io/4MK and Xorg.0.log: http://ix.io/4MJ
I notice the errors in Xorg.0.log but I'm not sure what to make of them.
I'm not sure what else to add here, I hope I'm not missing something obvious.
Last edited by CrashLog (2013-03-18 20:34:33)

I had this problem when I similarly made this update. I'm running Arch on a Dell Inspiron 1100, after the update X wouldn't start. I attempted to roll back to previous versions (as stipulated here and seeing as I had them in my cache) to no avail (gave up in frustration). Finally, I was able to get into X in two different ways:
First, I removed xf86-video-intel and installed xf86-video-vesa, when I rebooted I added the i915.modeset=0 parameter to the boot options at runtime in GRUB. For whatever reason X wouldn't load if I allowed the modeset to happen (bigger console area). This enabled me to boot into a slower X which I was still dissatisfied with, but at the very least it allowed me to isolate the problem as the intel driver as everything else is fully up to date.
Second, I created /etc/X11/xorg.conf.d/20-intel.conf with the following contents:
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "NoAccel" "True"
EndSection
This also meant switching back to xf86-video-intel (instead of using xf86-video-vesa) for X. I tried both the "uxa" (supposed to be default) and "sna" options for "AccelMethod" and neither worked, only explicitly using the "NoAccel" "True" option allowed me to get X to function anew. In this manner I don't have to disable the modeset option during boot in GRUB and I'm still utilizing the latest intel driver.
The only inference (albeit perhaps misguided or ignorant) I can make is that something changed in UXA that broke how it worked before (I say this because this laptop is too old to support SNA).

Boot Camp: Mac Pro won't start after Windows install

After installing Boot Camp on a Mac Pro dual 2.66 (firmware updated), XP installer went through installation & copying files, then restarted. Went to a black screen with white Windows-style text that said something along the lines of "XP cannot start from this CD, press any key to restart." Totally unresponsive, held down power to restart. Will no longer power up. Have reset the SMC without any effect. Makes a brief sound when trying to start, but does not actually start up.
Is there any known power issue that I might be able to solve myself, or is the supply likely blown?
Mac Pro Mac OS X (10.4.8)

I put Vista on its own dedicated drive, 64GB Vista, the rest as FAT32 to make it easier to share files. I had to remove the OS X drives in order to allow Windows/Vista to install. Once installed, had a black screen and some blue crash screen, until I ran the BootCamp driver updates.
I would try unplugging your drive(s) first and see if you boot from Tiger Installer DVD - or better, boot Apple Hardware Test (hold down "d" on startup from Install Disk #1).

Problem with MTRR - X doesn't start after fresh install

Hi all!
I have a big problem with MTRR, i think...
My PC Specs: P4 3GHZ with HT "prescot", Asus P4S800D-X, ATI x1650 Pro, 1024MB Ram Dual Channel, etc...
I can't start the X system. When i try to try the new Xorg.conf, the X seems to start but the screen stays blank and sometimes can i go back to TTY and sometimes not...
I've tryed with the following drivers and no luck.
- Vesa: Blank Screen, sometimes keyboard works and sometimes not.
- RadeonHD: The same...
- Radeon (or ati): The same...
At the end of the Xorg.0.log, i see the MTRR problem. the memory from the VGA Card is not detected automatically. The "cat /proc/mtrr" differs from ubuntu 8.04, when the X server works correctly.
Ive been reading a lot in google and others forum and see a lots of tricks related to MTRR (but im not completly sure of that's the problem...) but every trick i try doesn't seems to work.
I tryed the following tricks:
- Adding the memory to /proc/mtrr manually = Added correctly but NO LUCK
- Activate/Deactivate HotPlugging = NO LUCK
- Adding to my boot line the "nopat" and "enable_mtrr_cleanup = MTRR keeps showing wrong memory (no video memory)
- After adding correctly the memory to MTRR try the xorg.conf but blank screen (i dunno if xorg rewrites the mtrr when run)
- Some others tricks i cant remember...
Also, with the radeonhd, i get this errors in xorg.0.log:
- rhdAtomgetDDCIndex: GPIO_DDC Index 14 exceeds maximum 5
- RHDCSStop: Command Submission backen is not active!
- error setting MTRR ( base... blablabla) Invalid argument (22)
That's not my first install, but i can't make it work. As i readed, it's a kernel problem related to 2.6.29, in 2.6.28 there's no problem but i dont have access to the old kernel.
Can someone help my or i need to wait for a new kernel release to use Arch?
Bye!
Last edited by Driskol (2009-04-17 11:36:26)

Driskol wrote:but i dont have access to the old kernel
I can't solve your problem, but I can help you work around it by downgrading if nobody else can figure it out.
You can find old packages here at the Arch Rollback Machine project repo someone thankfully keeps running,
http://arm.nrk.cc/
Just go to 'core' and get the package(s) you need and downgrade. There is also a thread on here somewhere about setting up pacman.conf to point to a specific date with ARM if you don't want to get individual stuff manually, but just doing it individually would probably be easier, as I don't expect the kernel has too many other things you need
Last edited by FrozenFox (2009-04-17 10:51:42)

[solved] GDM won't start after update

Hello.
Today I made a pacman -Syu and gdm was updated.
On the next boot i only get a console and not the usual gdm login.
I loged in and tried to start gdm manualy with /etc/rc.d/gdm restart
wich results in an error message : "gdm already running. Aborting!", but it isnt
The X Server works (tried startx).
Any ideas what happend to gdm and how to fix it?
/edit : additional info: using current repository

Does your gdm.conf file contains paths like this: /usr/X11R6/bin
I think pacman just overwrites the config files if you never changed anything to them. In my case I did some modifications, so pacman made a backup of my modified file.
In case your file don't contain any /usr/X11R6/... , you may try do diff your file between mine:
# GDM Configuration file. You can use gdmsetup program to graphically
# edit this, or you can optionally just edit this file by hand. Note that
# gdmsetup does not tweak every option here, just the ones most users
# would care about. Rest is for special setups and distro specific
# tweaks. If you edit this file, you should send the HUP or USR1 signal to
# the daemon so that it restarts: (Assuming you have not changed PidFile)
# kill -USR1 `cat /var/run/gdm.pid`
# (HUP will make gdm restart immediately while USR1 will make gdm not kill
# existing sessions and will only restart gdm after all users log out)
# You can also use the gdm-restart and gdm-safe-restart scripts which just
# do the above for you.
# For full reference documentation see the gnome help browser under
# GNOME|System category. You can also find the docs in HTML form on
# http://www.gnome.org/projects/gdm/
# NOTE: Some of these are commented out but still show their default values.
# If you wish to change them you must remove the '#' from the beginning of
# the line. The commented out lines are lines where the default might
# change in the future, so set them one way or another if you feel
# strongly about it.
# Have fun! - George
[daemon]
# Automatic login, if true the first local screen will automatically logged
# in as user as set with AutomaticLogin key.
AutomaticLoginEnable=false
AutomaticLogin=tom
# Timed login, useful for kiosks. Log in a certain user after a certain
# amount of time
TimedLoginEnable=false
TimedLogin=
TimedLoginDelay=30
# The gdm configuration program that is run from the login screen, you should
# probably leave this alone
#Configurator=/opt/gnome/sbin/gdmsetup --disable-sound --disable-crash-dialog
# The chooser program. Must output the chosen host on stdout, probably you
# should leave this alone
#Chooser=/opt/gnome/libexec/gdmchooser
# The greeter for local (non-xdmcp) logins. Change gdmlogin to gdmgreeter to
# get the new graphical greeter.
#Greeter=/opt/gnome/libexec/gdmlogin
Greeter=/opt/gnome/libexec/gdmgreeter
# The greeter for xdmcp logins, usually you want a less graphically intensive
# greeter here so it's better to leave this with gdmlogin
#RemoteGreeter=/opt/gnome/libexec/gdmlogin
RemoteGreeter=/opt/gnome/libexec/gdmgreeter
# Launch the greeter with an additional list of colon seperated gtk
# modules. This is useful for enabling additional feature support
# e.g. gnome accessibility framework. Only "trusted" modules should
# be allowed to minimise security holes
#AddGtkModules=false
# By default these are the accessibility modules
#GtkModulesList=gail:atk-bridge:/opt/gnome/lib/gtk-2.0/modules/libdwellmouselistener:/opt/gnome/lib/gtk-2.0/modules/libkeymouselistener
# Default path to set. The profile scripts will likely override this
DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/bin
# Default path for root. The profile scripts will likely override this
RootPath=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/gnome/sbin:/opt/gnome/bin
# If you are having trouble with using a single server for a long time and
# want gdm to kill/restart the server, turn this on
#AlwaysRestartServer=false
# User and group used for running gdm GUI applicaitons. By default this
# is set to user gdm and group gdm. This user/group should have very
# limited permissions and access to ony the gdm directories and files.
User=nobody
Group=gdm
# To try to kill all clients started at greeter time or in the Init script.
# doesn't always work, only if those clients have a window of their own
#KillInitClients=true
LogDir=/var/log/gdm
# You should probably never change this value unless you have a weird setup
PidFile=/var/run/gdm.pid
# Note that a post login script is run before a PreSession script.
# It is run after the login is successful and before any setup is
# run on behalf of the user
PostLoginScriptDir=/opt/gnome/etc/gdm/PostLogin/
PreSessionScriptDir=/opt/gnome/etc/gdm/PreSession/
PostSessionScriptDir=/opt/gnome/etc/gdm/PostSession/
DisplayInitDir=/opt/gnome/etc/gdm/Init
# Distributions: If you have some script that runs an X server in say
# VGA mode, allowing a login, could you please send it to me?
#FailsafeXServer=
# if X keeps crashing on us we run this script. The default one does a bunch
# of cool stuff to figure out what to tell the user and such and can
# run an X configuration program.
XKeepsCrashing=/opt/gnome/etc/gdm/XKeepsCrashing
# Reboot, Halt and suspend commands, you can add different commands
# separated by a semicolon and gdm will use the first one it can find
RebootCommand=/sbin/shutdown -r now "Rebooted from gdm menu."
HaltCommand=/sbin/shutdown -h now "Halted from gdm menu."
SuspendCommand=/usr/bin/apm --suspend
# Probably should not touch the below this is the standard setup
ServAuthDir=/opt/gnome/var/gdm
# This is our standard startup script. A bit different from a normal
# X session, but it shares a lot of stuff with that. See the provided
# default for more information.
BaseXsession=/opt/gnome/etc/gdm/Xsession
# This is a directory where .desktop files describing the sessions live
# It is really a PATH style variable since 2.4.4.2 to allow actual
# interoperability with KDM. Note that <sysconfdir>/dm/Sessions is there
# for backwards compatibility reasons with 2.4.4.x
SessionDesktopDir=/etc/X11/sessions/:/etc/dm/Sessions/:/usr/share/xsessions/:/opt/gnome/share/gdm/BuiltInSessions/:/opt/gnome/share/xsessions/
# This is the default .desktop session. One of the ones in SessionDesktopDir
#DefaultSession=gnome.desktop
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=
# Fallback if home directory not writable
UserAuthFBDir=/tmp
UserAuthFile=.Xauthority
# The X server to use if we can't figure out what else to run.
StandardXServer=/usr/X11R6/bin/X
# The maximum number of flexible X servers to run.
#FlexibleXServers=5
# And after how many minutes should we reap the flexible server if there is
# no activity and no one logged on. Set to 0 to turn off the reaping.
# Does not affect Xnest flexiservers.
#FlexiReapDelayMinutes=5
# the X nest command
Xnest=/usr/X11R6/bin/Xnest -audit 0 -name Xnest
# Automatic VT allocation. Right now only works on Linux. This way
# we force X to use specific vts. turn VTAllocation to false if this
# is causing problems.
FirstVT=7
VTAllocation=true
# Should double login be treated with a warning (and possibility to change
# vts on linux and freebsd systems for console logins)
#DoubleLoginWarning=true
# Should a second login always resume the current session and
# switch vts on linux and freebsd systems for console logins
#AlwaysLoginCurrentSession=true
# If true then the last login information is printed to the user before
# being prompted for password. While this gives away some info on what
# users are on a system, it on the other hand should give the user an
# idea of when they logged in and if it doesn't seem kosher to them,
# they can just abort the login and contact the sysadmin (avoids running
# malicious startup scripts)
#DisplayLastLogin=false
# Program used to play sounds. Should not require any 'daemon' or anything
# like that as it will be run when no one is logged in yet.
#SoundProgram=/usr/bin/play
# These are the languages that the console cannot handle because of font
# issues. Here we mean the text console, not X. This is only used
# when there are errors to report and we cannot start X.
# This is the default:
#ConsoleCannotHandle=am,ar,az,bn,el,fa,gu,hi,ja,ko,ml,mr,pa,ta,zh
# This determines whether gdm will honor requests DYNAMIC requests from
# the gdmdynamic command.
#DynamicXServers=false
# This determines whether gdm will send notifications to the console
#ConsoleNotify=true
[security]
# If any distributions ship with this one off, they should be shot
# this is only local, so it's only for say kiosk use, when you
# want to minimize possibility of breakin
AllowRoot=false
# If you want to be paranoid, turn this one off
AllowRemoteRoot=false
# This will allow remote timed login
AllowRemoteAutoLogin=false
# 0 is the most restrictive, 1 allows group write permissions, 2 allows all
# write permissions
RelaxPermissions=0
# Check if directories are owned by logon user. Set to false, if you have, for
# example, home directories owned by some other user.
CheckDirOwner=true
# Number of seconds to wait after a bad login
#RetryDelay=1
# Maximum size of a file we wish to read. This makes it hard for a user to DoS
# us by using a large file.
#UserMaxFile=65536
# If true this will basically append -nolisten tcp to every X command line,
# a good default to have (why is this a "negative" setting? because if
# it is false, you could still not allow it by setting command line of
# any particular server). It's probably better to ship with this on
# since most users will not need this and it's more of a security risk
# then anything else.
# Note: Anytime we find a -query or -indirect on the command line we do
# not add a "-nolisten tcp", as then the query just wouldn't work, so
# this setting only affects truly local sessions.
DisallowTCP=true
# By default never place cookies if we "detect" NFS. We detect NFS
# by detecting "root-squashing". It seems bad practice to place
# cookies on things that go over the network by default and thus we
# don't do it by default. Sometimes you can however use safe remote
# filesystems where this is OK and you may want to have the cookie in your
# home directory.
#NeverPlaceCookiesOnNFS=true
# XDMCP is the protocol that allows remote login. If you want to log into
# gdm remotely (I'd never turn this on on open network, use ssh for such
# remote usage that). You can then run X with -query <thishost> to log in,
# or -indirect <thishost> to run a chooser. Look for the 'Terminal' server
# type at the bottom of this config file.
[xdmcp]
# Distributions: Ship with this off. It is never a safe thing to leave
# out on the net. Setting up /etc/hosts.allow and /etc/hosts.deny to only
# allow local access is another alternative but not the safest.
# Firewalling port 177 is the safest if you wish to have xdmcp on.
# Read the manual for more notes on the security of XDMCP.
Enable=false
# Honour indirect queries, we run a chooser for these, and then redirect
# the user to the chosen host. Otherwise we just log the user in locally.
#HonorIndirect=true
# Maximum pending requests
#MaxPending=4
#MaxPendingIndirect=4
# Maximum open XDMCP sessions at any point in time
#MaxSessions=16
# Maximum wait times
#MaxWait=15
#MaxWaitIndirect=15
# How many times can a person log in from a single host. Usually better to
# keep low to fend off DoS attacks by running many logins from a single
# host. This is now set at 2 since if the server crashes then gdm doesn't
# know for some time and wouldn't allow another session.
#DisplaysPerHost=2
# The number of seconds after which a non-responsive session is logged off.
# Better keep this low.
#PingIntervalSeconds=15
# The port. 177 is the standard port so better keep it that way
#Port=177
# Willing script, none is shipped and by default we'll send
# hostname system id. But if you supply something here, the
# output of this script will be sent as status of this host so that
# the chooser can display it. You could for example send load,
# or mail details for some user, or some such.
Willing=/opt/gnome/etc/gdm/Xwilling
[gui]
# The specific gtkrc file we use. It should be the full path to the gtkrc
# that we need. Unless you need a specific gtkrc that doesn't correspond to
# a specific theme, then just use the GtkTheme key
#GtkRC=/opt/gnome/share/themes/Default/gtk-2.0/gtkrc
# The GTK+ theme to use for the gui
#GtkTheme=Default
# If to allow changing the GTK+ (widget) theme from the greeter. Currently
# this only affects the standard greeter as the graphical greeter does
# not yet have this ability
#AllowGtkThemeChange=true
# Comma separated list of themes to allow. These must be the names of the
# themes installed in the standard locations for gtk themes. You can
# also specify 'all' to allow all installed themes. These should be just
# the basenames of the themes such as 'Thinice' or 'LowContrast'.
#GtkThemesToAllow=all
# Maximum size of an icon, larger icons are scaled down
#MaxIconWidth=128
#MaxIconHeight=128
[greeter]
# Greeter has a nice title bar that the user can move
#TitleBar=true
# Configuration is available from the system menu of the greeter
#ConfigAvailable=true
# Face browser is enabled. This only works currently for the
# standard greeter as it is not yet enabled in the graphical greeter.
Browser=true
# The default picture in the browser
#DefaultFace=/opt/gnome/share/pixmaps/nobody.png
# User ID's less than the MinimalUID value will not be included in the
# face browser or in the gdmselection list for Automatic/Timed login.
# They will not be displayed regardless of the settings for
# Include and Exclude.
MinimalUID=1000
# Users listed in Include will be included in the face browser and in
# the gdmsetup selection list for Automatic/Timed login. Users
# should be separated by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from
# the gdmsetup selection list for Automatic/Timed login. Excluded
# users will still be able to log in, but will have to type their
# username. Users should be separated by commas.
Exclude=bin,daemon,mail,nobody
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
IncludeAll=true
# will be displayed except users excluded via the Exclude setting and
# user ID's less than MinimalUID. Scanning the password file can be
# slow on systems with large numbers of users and this feature should
# not be used in such environments. The setting of IncludeAll does
# nothing if Include is set to a non-empty value.
#IncludeAll=false
# If user or user.png exists in this dir it will be used as his picture
#GlobalFaceDir=/opt/gnome/share/pixmaps/faces/
# File which contains the locale we show to the user. Likely you want to use
# the one shipped with gdm and edit it. It is not a standard locale.alias file,
# although gdm will be able to read a standard locale.alias file as well.
#LocaleFile=/opt/gnome/etc/gdm/locale.alias
# Logo shown in the standard greeter
#Logo=/opt/gnome/share/pixmaps/gdm-foot-logo.png
# The standard greeter should shake if a user entered the wrong username or
# password. Kind of cool looking
#Quiver=true
# The Actions menu (formerly system menu) is shown in the greeter, this is the
# menu that contains reboot, shutdown, suspend, config and chooser. None of
# these is available if this is off. They can be turned off individually
# however
SystemMenu=true
# Should the chooser button be shown. If this is shown, GDM can drop into
# chooser mode which will run the xdmcp chooser locally and allow the user
# to connect to some remote host. Local XDMCP does not need to be enabled
# however
#ChooserButton=true
# Welcome is for all console logins and RemoteWelcome is for remote logins
# (through XDMCP).
# DefaultWelcome and DefaultRemoteWelcome set the string for Welcome
# to "Welcome" and for DefaultWelcome to "Welcome to %n", and properly
# translate the message to the appropriate language. Note that %n gets
# translated to the hostname of the machine. These default values can
# be overridden by setting DefaultWelcome and/or DefaultRemoteWelcome to
# false, and setting the Welcome and DefaultWelcome values as desired.
# Just make sure the strings are in utf-8 Note to distributors, if you
# wish to have a different Welcome string and wish to have this
# translated you can have entries such as "Welcome[cs]=Vitejte na %n".
DefaultWelcome=true
DefaultRemoteWelcome=true
#Welcome=Welcome
#RemoteWelcome=Welcome to %n
# Don't allow user to move the standard greeter window. Only makes sense
# if TitleBar is on
#LockPosition=false
# Set a position rather then just centering the window. If you enter
# negative values for the position it is taken as an offset from the
# right or bottom edge.
#SetPosition=false
#PositionX=0
#PositionY=0
# Xinerama screen we use to display the greeter on. Not for true
# multihead, currently only works for Xinerama.
#XineramaScreen=0
# Background settings for the standard greeter:
# Type can be 0=None, 1=Image, 2=Color
#BackgroundType=2
#BackgroundImage=
#BackgroundScaleToFit=true
#BackgroundColor=#76848F
# XDMCP session should only get a color, this is the sanest setting since
# you don't want to take up too much bandwidth
#BackgroundRemoteOnlyColor=true
# Program to run to draw the background in the standard greeter. Perhaps
# something like an xscreensaver hack or some such.
#BackgroundProgram=
# if this is true then the background program is run always, otherwise
# it is only run when the BackgroundType is 0 (None)
#RunBackgroundProgramAlways=false
# Show the Failsafe sessions. These are much MUCH nicer (focus for xterm for
# example) and more failsafe then those supplied by scripts so distros should
# use this rather then just running an xterm from a script.
#ShowGnomeFailsafeSession=true
#ShowXtermFailsafeSession=true
# Normally there is a session type called 'Last' that is shown which refers to
# the last session the user used. If off, we will be in 'switchdesk' mode where
# the session saving stuff is disabled in GDM
#ShowLastSession=true
# Always use 24 hour clock no matter what the locale.
#Use24Clock=false
# Use circles in the password field. Looks kind of cool actually,
# but only works with certain fonts.
#UseCirclesInEntry=false
# Do not show any visible feedback in the password field. This is standard
# for instance in console, xdm and ssh.
#UseInvisibleInEntry=false
# These two keys are for the new greeter. Circles is the standard
# shipped theme. If you want gdm to select a random theme from a list
# then provide a list that is delimited by /: to the GraphicalThemes key and
# set GraphicalThemeRand to true. Otherwise use GraphicalTheme and specify
# just one theme.
#GraphicalTheme=circles
GraphicalTheme=happygnome-list
#GraphicalThemes=circles/:happygnome
GraphicalThemes=circles
GraphicalThemeDir=/opt/gnome/share/gdm/themes/
GraphicalThemeRand=false
# If InfoMsgFile points to a file, the greeter will display the contents of the
# file in a modal dialog box before the user is allowed to log in.
#InfoMsgFile=
# If InfoMsgFile is present then InfoMsgFont can be used to specify the font
# to be used when displaying the contents of the file.
#InfoMsgFont=Sans 24
# If SoundOnLogin is true, then the greeter will beep when login is ready
# for user input. If SoundOnLogin is a file and the greeter finds the
# 'play' executable (see daemon/SoundProgram) it will play that file
# instead of just beeping
#SoundOnLogin=true
SoundOnLogin=false
#SoundOnLoginFile=
# If SoundOnLoginSuccess, then the greeter will play a sound (as above)
# when a user successfully logs in
#SoundOnLoginSuccess=false
#SoundOnLoginSuccessFile=
# If SoundOnLoginFailure, then the greeter will play a sound (as above)
# when a user fails to log in
#SoundOnLoginFailure=false
#SoundOnLoginFailureFile=
# The chooser is what's displayed when a user wants an indirect XDMCP
# session, or selects Run XDMCP chooser from the system menu
[chooser]
# Default image for hosts
#DefaultHostImg=/opt/gnome/share/pixmaps/nohost.png
# Directory with host images, they are named by the hosts: host or host.png
HostImageDir=/opt/gnome/share/hosts/
# Time we scan for hosts (well only the time we tell the user we are
# scanning actually, we continue to listen even after this has
# expired)
#ScanTime=4
# A comma separated lists of hosts to automatically add (if they answer to
# a query of course). You can use this to reach hosts that broadcast cannot
# reach.
Hosts=
# Broadcast a query to get all hosts on the current network that answer
Broadcast=true
# Set it to true if you want to send a multicast query to hosts.
Multicast=false
# It is an IPv6 multicast address.It is hardcoded here and will be replaced when
# officially registered xdmcp multicast address of TBD will be available
#Multicast_Addr=ff02::1
# Allow adding random hosts to the list by typing in their names
#AllowAdd=true
[debug]
# This will enable debugging into the syslog, usually not neccessary
# and it creates a LOT of spew of random stuff to the syslog. However it
# can be useful in determining when something is going very wrong.
Enable=false
[servers]
# These are the standard servers. You can add as many you want here
# and they will always be started. Each line must start with a unique
# number and that will be the display number of that server. Usually just
# the 0 server is used.
0=Standard
#1=Standard
# Note the VTAllocation and FirstVT keys on linux and freebsd.
# Don't add any vt<number> arguments if VTAllocation is on, and set FirstVT to
# be the first vt available that your gettys don't grab (gettys are usually
# dumb and grab even a vt that has already been taken). Using 7 will work
# pretty much for all linux distributions. VTAllocation is not currently
# implemented on anything but linux and freebsd. Feel free to send patches.
# X servers will just not get any extra arguments then.
# If you want to run an X terminal you could add an X server such as this
#0=Terminal -query serverhostname
# or for a chooser (optionally serverhostname could be localhost)
#0=Terminal -indirect serverhostname
# If you wish to run the XDMCP chooser on the local display use the following
# line
#0=Chooser
## Note:
# is your X server not listening to TCP requests? Perhaps you should look
# at the security/DisallowTCP setting!
# Definition of the standard X server.
[server-Standard]
name=Standard server
command=/usr/X11R6/bin/X -audit 0
flexible=true
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Terminal]
name=Terminal server
# Add -terminate to make things behave more nicely
command=/usr/X11R6/bin/X -audit 0 -terminate
# Make this not appear in the flexible servers (we need extra params
# anyway, and terminate would be bad for xdmcp choosing). You can
# make a terminal server flexible, but not with an indirect query.
# If you need flexible indirect query server, then you must get rid
# of the -terminate and the only way to kill the flexible server will
# then be by Ctrl-Alt-Backspace
flexible=false
# Not local, we do not handle the logins for this X server
handled=false
# To use this server type you should add -query host or -indirect host
# to the command line
[server-Chooser]
name=Chooser server
command=/usr/X11R6/bin/X -audit 0
# Make this not appear in the flexible servers for now, but if you
# wish to allow a chooser server then make this true. This is the
# only way to make a flexible chooser server that behaves nicely.
flexible=false
# Run the chooser instead of the greeter. When the user chooses a
# machine they will get this same server but run with
# "-terminate -query hostname"
chooser=true

[solved] Spamd won't start after perl upgrade

Starting spamd via the initscript doesn't work anymore. If I try to run spamd via console I get the following error:
/usr/bin/perl: symbol lookup error: /usr/lib/perl5/site_perl/auto/Crypt/OpenSSL/RSA/RSA.so: undefined symbol: Perl_Gthr_key_ptr
Any idea how I can fix this?
Last edited by ChojinDSL (2011-07-06 10:48:29)

Ok, I solved it. Somehow.
I tested spamd on a different server and there the perl uprade worked without a hitch.
I tried re-installing a bunch of perl deps, but that didn't help either. In the end, I simply deleted the RSA.so file which the original error message complained about.. Since the files in that folder did not seem to belong to any package.
And presto, spamd starts again.

Ohasd not starting after fresh install

Hi,
I have installed Oracle Database 11g Release 11.2.0.1.0 - 64bit Production With the Real Application Clusters and Automatic Storage Management options on SUSE Linux Enterprise Server 11 (x86_64) 11.0.
After installation all cluster and resources were up, I could log in to database. I have restarted orcl1 node, and after boot the ohasd service is not started. Same is with orcl0 node. When I start manually, the cluster comes up. See below:
grid@orcl1:~> crsctl check has
CRS-4639: Could not contact Oracle High Availability Services
orcl1:~ # ps aux | grep ohasd
root      5157 0.0 0.0 11224 1448 ?        Ss   03:02   0:00 /bin/sh /etc/init.d/init.ohasd run
root      5365 0.0 0.0   4316   756 pts/0    S+   03:02   0:00 grep ohasd
orcl1:~ # chkconfig ohasd
ohasd on
orcl1:~ # service ohasd start
Starting ohasd:
orcl1:~ #
orcl1:~ # CRS-4123: Oracle High Availability Services has been started.
orcl1:~ # ps aux | grep ohasd
root      5157 0.0 0.0 11224 1464 ?        Ss   03:02   0:00 /bin/sh /etc/init.d/init.ohasd run
root      5414 3.3 0.3 569056 47124 ?        Ssl 03:03   0:01 /u01/app/11.2.0/grid/bin/ohasd.bin reboot
root      5736 0.0 0.0   4316   752 pts/0    S+   03:03   0:00 grep ohasdThen within short time everything is started up...
Anyone has idea why ohasd service is not started automatically ?
Update:
I have changed /etc/init.d/ohasd file so that it 'logs' to /tmp time when invoked (see below the code). After reboot there is no record of startup /tmp/ohasd*
orcl1:~ # chkconfig --list ohasd
ohasd                     0:off 1:off 2:off 3:on   4:off 5:on   6:off
# This script is invoked by the rc system.
/bin/touch /tmp/ohasd.start."`date`"    # <<<--- added line to 'log' the start
ORA_CRS_HOME=/u01/app/11.2.0/gridThanks !
Edited by: kamilp on Feb 17, 2013 11:35 PM

Hi,
there are two scripts - both installed by installer, I have not changed anything...
orcl1:~ # l /etc/init.d/*ohasd*
-rwxr-xr-x 1 root root 3079 Feb 18 00:37 /etc/init.d/init.ohasd*
-rwxr-xr-x 1 root root 2632 Feb 18 11:27 /etc/init.d/ohasd*
orcl1:~ # l /etc/init.d/rc5.d/*ohasd*
lrwxrwxrwx 1 root root 17 Feb 18 00:37 /etc/init.d/rc5.d/S96ohasd -> /etc/init.d/ohasd*
orcl1:~ # head -10 /etc/init.d/ohasd
#!/bin/sh
# Copyright (c) 2001, 2009, Oracle and/or its affiliates. All rights reserved.
# ohasd.sbs - Control script for the Oracle HA Services daemon
# This script is invoked by the rc system.
ORA_CRS_HOME=/u01/app/11.2.0/grid
orcl1:~ # head -10 /etc/init.d/init.ohasd
#!/bin/sh
# Copyright (c) 2001, 2009, Oracle and/or its affiliates. All rights reserved.
# init.ohasd - Control script for the Oracle HA services daemon
# This script is invoked by the init system

[Solved]Terminals won't start after merging bash.bashrc

Hi all,
As the topic states, after merging the files using meld, none of my terminals will start. I've never modified bash.bashrc and seeing that the developers decided to change it, I'll like to get this working.
Current bash.bashrc
# /etc/bash.bashrc
# If not running interactively, don't do anything
[[ $- != *i* ]] && return
PS1='[\u@\h \W]\$ '
PS2='> '
PS3='> '
PS4='+ '
case ${TERM} in
xterm*|rxvt*|Eterm|aterm|kterm|gnome*)
PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND; }'printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
screen)
PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND; }'printf "\033_%s@%s:%s\033\\" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
esac
[ -r /etc/bash_completion ] && . /etc/bash_completion
[ -r /etc/bash.bashrc.local ] && . /etc/bash.bashrc.local
Thanks in advance!
EDIT: This is embarrassing... A crappy alias in my .bashrc was causing this. Sorry for wasting your time
Last edited by Jodell (2011-02-22 02:40:25)

startx at the command line.
I just tried Xorg -reconfigure again, adding the AutoAddDevices = false option - still doesn't work, giving the error about config/hal. Without the option, it just goes back to the terminal with no errors.
Pacman log says the only thing upgraded today (after pacman) was the kernel, nvidia, and kernel-firmware. cdfs conflicted with the new kernel, so I removed it. Then I rebooted, and X stopped working. Downgrading those back again doesn't fix it. I don't get it.
>>EDIT:
Okay - what does cdfs have to do with Xorg???? This makes no sense. I downgraded the kernel pkgs and nvidia again, and this time installed cdfs, which I forgot to do last time. Now X starts. I don't really get it.
Maybe hal in xfce or some plugin needs to use cdfs for something?? I don't really know - but I'm just glad it's working. I guess I'll file a bug report for cdfs so it can be built to the new kernel and hold off upgrading until it's fixed with 2.6.31. sheesh! too weird.
Last edited by userlander (2009-10-10 23:27:36)

[SOLVED] KDE won't start after Xorg update(nvidia driver)

After update, I disabled hotplug, with :
Section "ServerFlags"
Option "AutoAddDevices" "False"
EndSection
kdm starts normally, i can write login/password, i see kde boot splash, then desktop shows and after about 10 secs it is killed and goes back to login screen.
I think the problem is with hal, because (Xorg.0.log):
(II) config/hal: Adding input device Video Bus
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Video Bus
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(EE) config/hal: NewInputDeviceRequest failed
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceRequest failed
Also (.xsession-errors)
ERROR: The control display is undefined; please run `nvidia-settings
--help` for usage information.
Last edited by ojciec (2008-12-01 22:28:08)

Well, I rebuilded my xorg.conf with
Xorg -configure
and it started working, even with evdev driver, just had to add
Option "AllowEmptyInput" "False"
in section "ServerFlags". I'm not really sure what caused that error.

[Solved] X11 won't start after fresh install

Similar Messages

Maybe you are looking for