View previous topic :: View next topic |
Author |
Message |
Hailst0rm n00b
Joined: 19 May 2009 Posts: 10
|
Posted: Tue May 19, 2009 8:05 pm Post subject: [SOLVED] xdm - black screen - startx occasionally works |
|
|
Hi!
I have already spent a long time on trying to solve this issue, my problem is the following:
Code: | /etc/init.d/xdm start | gives a black screen which is flickering occasionally (some white/red horizontal stripes)
also shows a black screen. After 10 flickers, the XSession starts to load and I sometimes get to my desktop
startx only worked after increasing two configurations of kdm (don't exactly remember the file right now):
ServerAttempts from 1 to 3
ServerTimeout from 15 to 30
I am running amd64 with gentoo-sources 2.6.28-r5 and an ATI Radeon 1800 XT. I have the keyworded kde4 from portage.
I already tried other versions of xorg-server, ati-drivers and reinstalled everything.
The strange thing is that there are no errors in Xorg.0.log nor in kdm.log. Even stranger is the fact that the same setup worked fine a few weeks ago. As soon as I identified xdm not working properly, I checked emerge.log without success.
here is my xorg.conf:
http://pastebin.com/m43867f69
a log of a successful startx call:
http://pastebin.com/m3f875b0f
a log of an unsuccessful startx call:
http://pastebin.com/m7cb52373
Feel free to ask for emerge --info or whatever you think might be of importance
Thanks in advance!
Last edited by Hailst0rm on Thu May 28, 2009 12:09 pm; edited 1 time in total |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Wed May 20, 2009 11:49 am Post subject: |
|
|
hi,
Are the monitor settings correct?
vsync, hsync?
Is the vesa driver with 60 hz vsync working? Try this. If this does then something with vsync or your binary driver is wrong! |
|
Back to top |
|
|
Hailst0rm n00b
Joined: 19 May 2009 Posts: 10
|
Posted: Thu May 21, 2009 1:33 pm Post subject: |
|
|
Thanks for having a look at my problem!
I tried the following:
- added vesa to the VIDEO_CARDS section of my make.conf
- re-emerged xorg-server (which installed the vesa driver)
- looked up the correct hsync values of my monitor, set VertRefresh to 60 and replaced fglrx driver with vesa
startx and "/etc/init.d/xdm start" both give a black screen with red and blue artifacts at the top. Now I cannot switch back to the console anymore. I also tried disabling AutoAddDevices and AllowEmptyInput.
Still doesn't work
It seems like the vesa driver doesn't work either.
here is my new xorg.conf
http://pastebin.com/m6b9cf699
and the corresponding Xorg.0.log:
http://pastebin.com/d70fa7e4c |
|
Back to top |
|
|
koppa n00b
Joined: 23 May 2009 Posts: 2
|
Posted: Sat May 23, 2009 7:47 am Post subject: |
|
|
Hello
Maybe I have the same problem? I just updated xorg, and found out that I can't get kdm login screen at start-up. I too see no errors or problems with kdm.log or Xorg.0.log. However, startx works fine, and I also get kdm login by doing manually: "/etc/init.d/xdm restart", or "kdm -nodaemon". When I get to KDE everrything works fine? I have checked that I (still) have xdm at default run level. I cannot think of much else to try. Maybe this is some timing issue, or has something to do with the order things happen at start-up? |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Sat May 23, 2009 10:11 am Post subject: |
|
|
http://pastebin.com/d70fa7e4c
that doesnt work. repost it again pls
try to build a newer xorg conf with some tools. e.g. xorg-config
First step should be a much smaller and minimalistic xorg.config file.
you have too much options enabled, if any of them makes problems you are screwed up. |
|
Back to top |
|
|
Hailst0rm n00b
Joined: 19 May 2009 Posts: 10
|
Posted: Sun May 24, 2009 7:51 am Post subject: |
|
|
Hi,
Again, I tried several things:
- installed Xfce4 -> the problem persists so it is an X-related problem not a problem of kde
- I did as you, tw04l124, suggested and created a new xorg.conf with xorgconfig -> changed graphics card driver to fglrx and vesa and locked VertRefresh of my monitor to 60 -> same problem with both drivers (didn't try "/etc/init.d/xdm start", though)
This is what Xorg.0.log says on a successful startup:
http://pastebin.com/m5cdc0ff2
There seems to be a problem with the microsoft habu mouse (which i do NOT recommend to anyone, btw. ), so I tried another mouse. The error was gone, but the flickering is still there .
This is my new xorg.conf:
http://pastebin.com/m9c9cd0b
One more information: I looked up the kdmrc file and noticed that ServerAttempts and ServerTimeouts are set to the default values after reinstallation.
@koppa:
your problem seems similar to mine, BUT:
- /etc/init.d/xdm start does not work on my machine
- startx works, but the monitor keeps flickering while loading kde (see my first post), after loading everything is fine
which xorg version did you update from? And which version are you running now? |
|
Back to top |
|
|
wsauerteig n00b
Joined: 24 May 2009 Posts: 1
|
Posted: Sun May 24, 2009 12:22 pm Post subject: X starts occasionally with black screen |
|
|
hi,
I've got a very similar problem.
Neither XDM nor startx work reliable. In common X starts with a blank screen, BUT X works in the background including sound etc. and accepts keyboard inputs (i.e. ctrl-alt-del and then enter for ending session). The special situation for my problem is that I can mostly get the X (KDE) screen by switching to text console (ctrl-alt-f4) and back to graphics console (ctrl-alt-f7). In all cases, no matter if the X gui appears or not, there are NO error messages (EE) in xorg.0.log.
Chipset is Intel i845 "Brookdale", graphics is Intel 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03), VIDEO_CARDS in make.conf is set to "intel".
My xorg.conf:
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "TFT"
# 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 31.5 - 48.5
# 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 60
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
Section "Device"
Identifier "video"
Driver "intel"
# Option "AccelMethod" "UXA"
# Option "Tiling" "False"
# Option "ModeDebug" "on"
#VideoRam 8192
# 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 "video"
Monitor "TFT"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768"
ViewPort 0 0
EndSubsection
EndSection
Any idea?
Has someone the same problem? Maybe, some of the former problems issued in this thread can also be worked around by switching to text console and back?
Best regards
Wolfram |
|
Back to top |
|
|
Hailst0rm n00b
Joined: 19 May 2009 Posts: 10
|
Posted: Sun May 24, 2009 5:32 pm Post subject: |
|
|
Switching to the console while loading X/kde makes kde play the starting sound, nothing more. I only see a black screen and I can move my mouse. X also responds to keyboard events (such as ctrl+alt+backspace).
I disabled HAL today: no improvement |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Mon May 25, 2009 5:50 am Post subject: |
|
|
habu mouse = razer mouse. I have a copperhead mouse. I think razortool is also capable to change the software of the mouse.
I considered buying this mouse, so there are "linux" support inoffical.
Never give up.
Hi,
did you try to figure out, which drivers and xorg.configs livecd uses if you fire them up on your hardware. Maybe you get a hint so your xorg.config will work.
Also use google and search for your hardware. My Bios has a bug, so no x-Server will ever run without changing some lines of the bios.
Damn Microsoft shit.
here is my config for my notebook, have a look, maybe you find something useful.
use the internet and try to read as many howtos to get the baby started.
This config works on the latest xorg-server.
Code: | localhost roman # cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Fri Apr 17 00:40:10 PDT 2009
#https://bugs.launchpad.net/ubuntu/+source/libsdl1.2/+bug/189958
#bevor man ein spiel startet, dies hier eingeben: SDL_VIDEO_X11_DGAMOUSE=0
#http://wiki.archlinux.org/index.php/Xorg
#http://wiki.archlinux.org/index.php/Xorg_input_hotplugging
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
# InputDevice "Keyboard0" "CoreKeyboard"
# InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
FontPath "/usr/share/misc"
EndSection
Section "Module"
#diese 3 zeilen dann sollte maus wieder funktionieren angeblich
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "dbe"
# Load "extmod"
Load "glx"
# support for Data Display Channel. Allows to query the monitor capabilities via the video card
Load "ddc"
# serial bus over which you speak the ddc protocol to get info from the monitor
Load "i2c"
#wegen maus jumps usw in games
EndSection
Section "ServerFlags"
Option "Xinerama" "0"
Option "SHMConfig" "on"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection
Section "InputDevice"
# generated from data in "/etc/conf.d/gpm"
# Option "ZAxisMapping" "4 5"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol"
Option "Device" "/dev/input/mice"
# Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
# Option "DPMS" "true"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "AUO"
HorizSync 30.0 - 75.5
VertRefresh 62.0
EndSection
Section "Device"
# Driver "vesa"
#enable AddarGB... for compiz, the second one i think too
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 9800M GTS"
Option "Coolbits" "1"
EndSection
Section "Screen"
# SubSection "Display"
# Depth 24
# EndSubSection
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
Option "RenderAccel" "True"
SubSection "Display"
Depth 24
Modes "1920x1200" "640x480" "800x600" "1600x1200" "1200x800"
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
localhost roman #
|
|
|
Back to top |
|
|
Hailst0rm n00b
Joined: 19 May 2009 Posts: 10
|
Posted: Wed May 27, 2009 2:07 pm Post subject: |
|
|
I did not complain about the hardware or the functionality of my habu mouse. It's fine!
It is the quality of manufacturing that I complain about. The wire is way too stiff. For me, this resulted in a cable break within (!) the case in less than a half year. It was only transported once and was not used as extensively as my other mice. I searched the internet and found out that there are several people with the same problem. Some soldering fixed the problem
Back to topic:
Messing around with the xorg.conf the livecd created gave no results.
Then I read in another thread here on the forums that some versions of ati-drivers don't work with certain kernel versions. Since I already tried upgrading my drivers to a newer version I thought upgrading the kernel could fix the issue. A pity the current ati-drivers (8.582 and 8.593) don't work with kernel version 2.6.29-r5
Thus, my only option was to downgrade my graphics card drivers and it worked!
Summary:
x11-drivers/ati-drivers-8.582 and x11-drivers/ati-drivers-8.593 seem not to work (assuming you use fglrx) with gentoo-sources-2.6.28-r5. Use x11-drivers/ati-drivers-8.573-r1 instead.
There are still some questions left:
- Why did it work with the same xorg version, the same drivers and the same kernel before?
- Why does the ebuild of ati-drivers not stop emerging (like with kernel 2.6.29-r5), telling you they are not compatible with your system?
Concerning the first question: I might have overlooked something when checking the emerge.log. I might have.
If anybody can confirm that the issue is solved after downgrading the drivers, I am probably going to file a bug report. The ebuild should prevent you from installing.
Thanks for your help! |
|
Back to top |
|
|
koppa n00b
Joined: 23 May 2009 Posts: 2
|
Posted: Fri May 29, 2009 12:28 pm Post subject: |
|
|
Hello
Good to hear your problem seems solved. My situation was probably not from the same origin (I'm on nvidia), but I too have now a working environment. The sad part is I don't know why. One night I was tinkering with various things, including compiling xorg, nvidia etc. with differing USE flags, trying different xorg.confs, setting some kdm -configs etc. I could swear that I rebooted one more time before I went to bed, and X did not come up. However, next morning I was greeted by kdm login screen! So, quite unsatisfactory, since I do not know what solved it. First time with gentoo that this happened to me. |
|
Back to top |
|
|
k9dog Tux's lil' helper
Joined: 22 Jun 2009 Posts: 103 Location: Denmark
|
Posted: Sun Apr 30, 2017 2:20 am Post subject: |
|
|
Pretty old thread, but same problem is showing up here. At least it looks like the same problem. I started getting black screen after an update. I managed to disable the the xdm service and could boot to console enviroment. I experimented a bit and found out I could run startx, but not the xdm. Neither could I run in daemon mode from command line. If I ran slim from command line desktop didn't start but just returned, which make me think xdm/daemon crashes from retrying endlessly. I am not sure why startx starts X enviroment and slim/lightdm doesn't. It was a new kernel with a bit different options, maybe thats a place to look. |
|
Back to top |
|
|
gent2one n00b
Joined: 09 May 2017 Posts: 1 Location: Earth
|
Posted: Wed May 10, 2017 2:43 am Post subject: |
|
|
k9dog wrote: | Pretty old thread, but same problem is showing up here. At least it looks like the same problem. I started getting black screen after an update. I managed to disable the the xdm service and could boot to console enviroment. I experimented a bit and found out I could run startx, but not the xdm. Neither could I run in daemon mode from command line. If I ran slim from command line desktop didn't start but just returned, which make me think xdm/daemon crashes from retrying endlessly. I am not sure why startx starts X enviroment and slim/lightdm doesn't. It was a new kernel with a bit different options, maybe thats a place to look. |
Are you still having this problem?
After backup; maybe try:
rm -r ~/.cache/sessions
rm -r ~/.config/{window manager}
rm -r ~/.config/Thunar
[/quote] _________________ All systems tend to its lowest energy state (ZERO) |
|
Back to top |
|
|
|