No X srenn on 12.3

I updated from 12.2 in place but today I rebooted – resulting in no screen

I have a RadeonHD 4650 which should be supported by the radeon driver (I had radeonhd which seems to have gone) but while I can sometimes get a login screen I get no session after giving name/password. Same logging in as root. No error messages in the xdm log. I am booting with nomodeset as that was a good idea.

What can I do? machine is running, mounted disks etc. but rather hard to use this way; can ssh in from another machine though so I assume this is a driver issue?

Update

If I boot in safe mode it works

Maybe you have a file /etc/X11/xorg.conf that tries to load the radeonhd driver? If yes, please remove it.

And why do you think nomodeset is a good idea? It prevents the radeon driver from being used. Try to remove that as well.

If that doesn’t help, please do the following:

  • Do a normal boot
  • When it fails, reboot in failsafe mode
  • Then post the file /var/log/Xorg.0.log.old

No sign of such

And why do you think nomodeset is a good idea? It prevents the radeon driver from being used. Try to remove that as well.

Because with 12.0, 12.1 and 12.2 it did not boot without it. I have removed it now followinf an IRC conversation.

If that doesn’t help, please do the following:

  • Do a normal boot
  • When it fails, reboot in failsafe mode
  • Then post the file /var/log/Xorg.0.log.old

I had to reboot to clear an nfs problem so I now have that log file. Most interesting part is the repeated
37.008] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument

Full log is too long to post but there is nothing odd otherwise

36.308] 

X.Org X Server 1.13.2
Release Date: 2013-01-24
36.308] X Protocol Version 11, Revision 0
36.308] Build Operating System: openSUSE SUSE LINUX
36.308] Current Operating System: Linux xenakis.cs.bath.ac.uk 3.7.10-1.1-de
sktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) x86_64
36.308] Kernel command line: root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0
_WD-WCAV59154895-part1 apm=off noresume edd=off powersaved=off nohz=off highres=
off processor.max_cstate=1 x11failsafe vga=0x375
36.308] Build Date: 21 February 2013 10:01:18AM


37.000] (II) Module shadow: vendor=“X.Org Foundation”
37.000] compiled for 1.13.2, module version = 1.1.0
37.000] ABI class: X.Org ANSI C Emulation, version 0.4
37.000] (II) UnloadModule: “vmware”
37.000] (II) Unloading vmware
37.003] (II) UnloadModule: “cirrus”
37.003] (II) Unloading cirrus
37.003] (II) UnloadModule: “vesa”
37.003] (II) Unloading vesa
37.003] (==) Depth 24 pixmap format is 32 bpp
37.007] (==) FBDEV(0): Backing store disabled
37.008] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
37.008] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
… repeated many time
37.012] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
37.012] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
37.012] (==) FBDEV(0): DPMS enabled
37.012] (==) RandR enabled
37.019] (II) AIGLX: Screen 0 is not DRI2 capable
37.019] (II) AIGLX: Screen 0 is not DRI capable
37.232] (II) AIGLX: Loaded and initialized swrast
37.232] (II) GLX: Initialized DRISWRAST GL provider for screen 0
37.303] (II) config/udev: Adding input device Power Button (/dev/input/even
t2)
37.303] () Power Button: Applying InputClass “evdev keyboard catchall”
37.303] (
) Power Button: Applying InputClass “evdev keyboard catchall”
37.303] () Power Button: Applying InputClass “LocalKeyboard”
37.303] (II) LoadModule: “evdev”
37.303] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
37.304] (II) Module evdev: vendor=“X.Org Foundation”
37.304] compiled for 1.13.1, module version = 2.7.3
37.304] Module class: X.Org XInput Driver
37.304] ABI class: X.Org XInput driver, version 18.0
37.304] (II) Using input driver ‘evdev’ for ‘Power Button’
37.304] (
) Power Button: always reports core events
37.304] () evdev: Power Button: Device: “/dev/input/event2”
37.304] (–) evdev: Power Button: Vendor 0 Product 0x1
37.304] (–) evdev: Power Button: Found keys
37.304] (II) evdev: Power Button: Configuring as keyboard
37.304] (
) Option “config_info” “udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2”
37.304] (II) XINPUT: Adding extended input device “Power Button” (type: KEY
BOARD, id 6)
37.304] () Option “xkb_rules” “evdev”
37.304] (
) Option “xkb_model” “evdev”
37.304] () Option “xkb_layout” “gb”
37.325] (II) config/udev: Adding input device Power Button (/dev/input/even
t1)
37.325] (
) Power Button: Applying InputClass “evdev keyboard catchall”
37.325] () Power Button: Applying InputClass “evdev keyboard catchall”
37.325] (
) Power Button: Applying InputClass “LocalKeyboard”
37.325] (II) Using input driver ‘evdev’ for ‘Power Button’
37.325] () Power Button: always reports core events
37.325] (
) evdev: Power Button: Device: “/dev/input/event1”
37.325] (–) evdev: Power Button: Vendor 0 Product 0x1
37.325] (–) evdev: Power Button: Found keys
37.325] (II) evdev: Power Button: Configuring as keyboard
37.325] () Option “config_info” “udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:0
0/PNP0C0C:00/input/input1/event1”
37.325] (II) XINPUT: Adding extended input device “Power Button” (type: KEY
BOARD, id 7)
37.325] (
) Option “xkb_rules” “evdev”
37.325] () Option “xkb_model” “evdev”
37.325] (
) Option “xkb_layout” “gb”
37.325] (II) config/udev: Adding drm device (/dev/dri/card0)
37.326] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/
dev/input/event9)
37.326] (II) No input driver specified, ignoring this device.
37.326] (II) This device may have been added with another device file.
37.326] (II) config/udev: Adding input device Microsoft Microsoft 5-Button
Mouse with IntelliEye™ (/dev/input/event0)
37.326] () Microsoft Microsoft 5-Button Mouse with IntelliEye™: Applyi
ng InputClass “evdev pointer catchall”
37.326] (
) Microsoft Microsoft 5-Button Mouse with IntelliEye™: Applyi
ng InputClass “evdev pointer catchall”
37.326] (II) Using input driver ‘evdev’ for ‘Microsoft Microsoft 5-Button M
ouse with IntelliEye™’
37.326] () Microsoft Microsoft 5-Button Mouse with IntelliEye™: always
reports core events
37.326] (
) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Device: “/dev/input/event0”
37.326] (–) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Vendor 0x45e Product 0x39
37.326] (–) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Found 9 mouse buttons
37.326] (–) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Found scroll wheel(s)
37.326] (–) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Found relative axes
37.326] (–) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Found x and y relative axes
37.326] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Configuring as mouse
37.326] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
Adding scrollwheel support
37.326] () evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
YAxisMapping: buttons 4 and 5
37.326] (
) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
37.326] () Option “config_info” “udev:/sys/devices/pci0000:00/0000:00:1a.
0/usb1/1-1/1-1.5/1-1.5:1.0/input/input0/event0”
37.326] (II) XINPUT: Adding extended input device “Microsoft Microsoft 5-Bu
tton Mouse with IntelliEye™” (type: MOUSE, id 8)
37.326] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye™:
initialized for relative axes.
37.326] (
) Microsoft Microsoft 5-Button Mouse with IntelliEye™: (accel
) keeping acceleration scheme 1
37.326] () Microsoft Microsoft 5-Button Mouse with IntelliEye™: (accel
) acceleration profile 0
37.326] (
) Microsoft Microsoft 5-Button Mouse with IntelliEye™: (accel
) acceleration factor: 2.000
37.326] () Microsoft Microsoft 5-Button Mouse with IntelliEye™: (accel
) acceleration threshold: 4
37.326] (II) config/udev: Adding input device Microsoft Microsoft 5-Button
Mouse with IntelliEye™ (/dev/input/mouse0)
37.326] (II) No input driver specified, ignoring this device.
37.326] (II) This device may have been added with another device file.
37.327] (II) config/udev: Adding input device CHICONY HP Basic USB Keyboard (/dev/input/event10)
37.327] (
) CHICONY HP Basic USB Keyboard: Applying InputClass “evdev keyb
oard catchall”
37.327] () CHICONY HP Basic USB Keyboard: Applying InputClass “evdev keyb
oard catchall”
37.327] (
) CHICONY HP Basic USB Keyboard: Applying InputClass “LocalKeybo
ard”
37.327] (II) Using input driver ‘evdev’ for ‘CHICONY HP Basic USB Keyboard’
37.327] () CHICONY HP Basic USB Keyboard: always reports core events
37.327] (
) evdev: CHICONY HP Basic USB Keyboard: Device: “/dev/input/even
t10”
37.327] (–) evdev: CHICONY HP Basic USB Keyboard: Vendor 0x3f0 Product 0x2
4
37.327] (–) evdev: CHICONY HP Basic USB Keyboard: Found keys
37.327] (II) evdev: CHICONY HP Basic USB Keyboard: Configuring as keyboard
37.327] () Option “config_info” “udev:/sys/devices/pci0000:00/0000:00:1a.
0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0/input/input10/event10”
37.327] (II) XINPUT: Adding extended input device “CHICONY HP Basic USB Key
board” (type: KEYBOARD, id 9)
37.327] (
) Option “xkb_rules” “evdev”
37.327] () Option “xkb_model” “evdev”
37.327] (
) Option “xkb_layout” “gb”
37.327] (II) config/udev: Adding input device HDA Intel MID Line (/dev/inpu
t/event4)
37.327] (II) No input driver specified, ignoring this device.
37.327] (II) This device may have been added with another device file.
37.327] (II) config/udev: Adding input device HDA Intel MID Front Mic (/dev
/input/event5)
37.327] (II) No input driver specified, ignoring this device.
37.327] (II) This device may have been added with another device file.
37.328] (II) config/udev: Adding input device HDA Intel MID Rear Mic (/dev/
input/event6)
37.328] (II) No input driver specified, ignoring this device.
37.328] (II) This device may have been added with another device file.
37.328] (II) config/udev: Adding input device HDA Intel MID Front Headphone
(/dev/input/event7)
37.328] (II) No input driver specified, ignoring this device.
37.328] (II) This device may have been added with another device file.
37.328] (II) config/udev: Adding input device HDA Intel MID Line Out (/dev/input/event8)
37.328] (II) No input driver specified, ignoring this device.
37.328] (II) This device may have been added with another device file.
37.328] (II) config/udev: Adding input device PC Speaker (/dev/input/event3
)
37.328] (II) No input driver specified, ignoring this device.
37.328] (II) This device may have been added with another device file.
16158.000] (II) config/udev: removing device CHICONY HP Basic USB Keyboard
16158.006] (II) evdev: CHICONY HP Basic USB Keyboard: Close
16158.006] (II) UnloadModule: “evdev”

[542701.915] (II) UnloadModule: “evdev”
[542701.915] (II) evdev: Power Button: Close
[542701.915] (II) UnloadModule: “evdev”
[542701.915] (II) evdev: Power Button: Close
[542701.915] (II) UnloadModule: “evdev”
[542702.687] Server terminated successfully (0). Closing log file.

That is the log from failsafe mode. X does seem to start despite of that error, right?

Well, I would like to see the log from a normal boot. So please, again, follow these steps exactly in this order:

  • Do a normal boot
  • When it fails, reboot in failsafe mode
  • Then post the file /var/log/Xorg.0.log.old

And btw. you can upload the log to a site like http://susepaste.org and just post the link here.

That is what I did

  • Do a normal boot
  • When it fails, reboot in failsafe mode
  • Then post the file /var/log/Xorg.0.log.old

My experence of 12.3 is very negative as is other I know. I dread updating the other 4 machines

So X isn’t even trying to start?
Can you login at the text console?
If yes, please post the output of “systemctl status xdm”. (you could also take a picture with a camera and upload it to SUSE Paste)

My experence of 12.3 is very negative as is other I know. I dread updating the other 4 machines

Well, I had no problem with any of my systems…

What output do you get for the following commands?

grep radeon /etc/modprobe.d/*
grep radeon /etc/X11/xorg.conf.d/*
grep radeon /etc/modprobe.d/*

/etc/modprobe.d/50-blacklist.conf:blacklist radeonfb

grep radeon /etc/X11/xorg.conf.d/*

/etc/X11/xorg.conf.d/50-device.conf:# #Driver “radeon”
/etc/X11/xorg.conf.d/50-device.conf:# ## Required magic for radeon/radeonhd drivers; output name
/etc/X11/xorg.conf.d/50-screen.conf:# ## Doesn’t help for radeon/radeonhd drivers; use magic in

Sorry not to reply to previois response – not physically near the computer until Thursday

[quote="“jpff,post:4,topic:88828”]

Because with 12.0, 12.1 and 12.2 it did not boot without it. [/QUOTE] Yeah, I believe your assumption is right – driver issue.

Under 12.0-12.2 the radeon kernel module accepted either UMS or KMS, and you were using the (UMS based) radeonhd DDX driver as opposed to the (then UMS/KMS, but effectively KMS based) radeon DDX – obvious from your description you were doing so by evoking the use of “nomodeset” and presumably by using the radeonhd (in a xorg.conf or xorg.conf.d/* file) … and the reason for this choice was because “it did not boot without it”

Under 12.3, the radeon kernel module defaults to KMS (you have to go out of your way to evoke the old UMS), and the old (UMS only) radeonhd DDX is no longer available, whereas you are left with the (now KMS only based) radeon DDX driver. Booting with “nomodeset” under this circumstance will prevent the radeon kernel module from loading. When X starts, it will attempt to load the radeon DDX, which will fail outright or bork shortly afterwards in the absence of KMS.

save mode/recovery mode/rescue mode /failsafe mode … evokes a very basic environment – its x11failsafe boot option results in the use of the /etc/X11/xorg.conf.install file (which is created and reflective of the envirnoment utiilzed/setup during system installation) … xorg.conf.install typically lists several generic/basic DDX drivers, with the first working match being utilized … typically Fbdev

while I can sometimes get a login screen I get no session after giving name/password. Same logging in as root. No error messages in the xdm log. I am booting with nomodeset as that was a good idea.
Just to confirm, you mean you sometimes are able to see a graphical login screen (display manager greeter) ? And this is with nomodeset, or prior to trying to use that??

In any regard, it sounds to me like you are hitting up against a bug in the kernel module, as opposed to the xorg driver. Under normal boot conditions, and without nomodeset, what messages do you have in dmesg or /var/log/messages regarding the drm ? i.e. try “dmesg | grep -e drm -e DRM”

(that assumes that you can get to a console login … if not, then on your next boot (using recovery mode) you will have to view the messages file for such occurrences during the prior unsuccessful boot)

Justhad to reboot as machine unstable. Screen is all multicolored bit. No access to F1 terminal

however can ssh in


dmesg | grep -i drm
    9.209725] [drm] Initialized drm 1.1.0 20060810
    9.663785] [drm] radeon defaulting to kernel modesetting.
    9.663787] [drm] radeon kernel modesetting enabled.
    9.663824] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
    9.664024] [drm] initializing kernel modesetting (RV730 0x1002:0x9498 0x174B:0xE930).
    9.664039] [drm] register mmio base: 0xFE620000
    9.664040] [drm] register mmio size: 65536
    9.664115] [drm] Detected VRAM RAM=1024M, BAR=256M
    9.664116] [drm] RAM width 128bits DDR
    9.664167] [drm] radeon: 1024M of VRAM memory ready
    9.664168] [drm] radeon: 512M of GTT memory ready.
    9.664177] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    9.664178] [drm] Driver supports precise vblank timestamp query.
    9.664239] [drm] radeon: irq initialized.
    9.664241] [drm] GART: num cpu pages 131072, num gpu pages 131072
    9.664884] [drm] probing gen 2 caps for device 8086:d138 = 2/0
    9.664885] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
    9.664937] [drm] Loading RV730 Microcode
   10.087650] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
   10.134612] [drm] ring test on 0 succeeded in 1 usecs
   10.134897] [drm] ib test on ring 0 succeeded in 0 usecs
   10.135063] [drm] Radeon Display Connectors
   10.135065] [drm] Connector 0:
   10.135066] [drm]   HDMI-A-1
   10.135066] [drm]   HPD2
   10.135068] [drm]   DDC: 0x7f10 0x7f10 0x7f14 0x7f14 0x7f18 0x7f18 0x7f1c 0x7f1c
   10.135069] [drm]   Encoders:
   10.135070] [drm]     DFP2: INTERNAL_UNIPHY1
   10.135070] [drm] Connector 1:
   10.135071] [drm]   VGA-1
   10.135072] [drm]   DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c
   10.135073] [drm]   Encoders:
   10.135074] [drm]     CRT2: INTERNAL_KLDSCP_DAC2
   10.135075] [drm] Connector 2:
   10.135076] [drm]   DVI-I-1
   10.135076] [drm]   HPD1
   10.135078] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
   10.135078] [drm]   Encoders:
   10.135079] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
   10.135080] [drm]     DFP1: INTERNAL_UNIPHY
   10.135099] [drm] Internal thermal controller with fan control
   10.135125] [drm] radeon: power management initialized
   10.295286] [drm] fb mappable at 0xD0142000
   10.295289] [drm] vram apper at 0xD0000000
   10.295289] [drm] size 7680000
   10.295290] [drm] fb depth is 24
   10.295291] [drm]    pitch is 6400
   10.295410] fbcon: radeondrmfb (fb0) is primary device
   10.295549] fb0: radeondrmfb frame buffer device
   10.295549] drm: registered panic notifier
   10.295555] [drm] Initialized radeon 2.24.0 20080528 for 0000:01:00.0 on minor 0
   45.571232] [drm] probing gen 2 caps for device 8086:d138 = 2/0
   45.571233] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
   45.864301] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
   46.064089] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)
   46.064090] [drm:rv770_resume] *ERROR* r600 startup failed on resume

This is a gpu lockup.

What’s the boot line (i.e. cat /proc/cmdline) ? … wondering if this is a VM.


cat /proc/cmdline                                         
root=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV59154895-part1 resume=/dev/disk/by-id/ata-WDC_WD5000AADS-00M2B0_WD-WCAV59010634-part1 splash=silent quiet vga=0x375

No virtual machine; a Dell i7 machine


systemctl status xdm
xdm.service - LSB: X Display Manager
          Loaded: loaded (/etc/init.d/xdm)
          Active: active (running) since Thu, 2013-06-27 19:27:02 BST; 12h ago
         Process: 1259 ExecStart=/etc/init.d/xdm start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/xdm.service
                  ├ 1315 /usr/bin/xdm
                  ├ 1318 /usr/bin/X -nolisten tcp -br vt7 -auth /var/lib/xd...
                  └ 1328 -:0         

and from pa ax:

1315 ? Ss 0:00 /usr/bin/xdm
1318 tty7 Rs+ 721:45 /usr/bin/X -nolisten tcp -br vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-oK7Gsm

Well, what I would try is to add all boot options from failsafe mode to the normal boot entry (except x11failsafe and nomodeset, so: “apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1”).
Check if it works then.

And then remove them one by one to find out which of the options fixes your problem.

  • Try with the “vga=” boot parameter removed
  • What does the display manager log say? … you only mentioned XDM earlier, but I suspect that you are using KDE, so what does the actual KDM (which I’m assuming you are using) log say … as well, what does any associated greeter log say (I don’t recall off hand if KDM greeter has its own log, but other DM’s employ such (e.g. lightdm))

No, that all would be in /var/log/kdm.log …

No KDE or Gnome. I run with X+fvwm; minimal icons or desktop clutter so not sure what display manager log you might mean, but it has not started the display manager yet.

xdm.errors does not report any error, ending:

Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX

I doubt the vga= parameter is the problem as that is the same in failsafe which does boot

Have found in /var/log/messages


2013-06-27T19:27:15.037139+01:00 xenakis kernel:    45.376780] radeon 0000:01:0
0.0: GPU lockup CP stall for more than 10000msec
2013-06-27T19:27:15.037149+01:00 xenakis kernel:    45.376784] radeon 0000:01:0
0.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001
)
2013-06-27T19:27:15.053159+01:00 xenakis kernel:    45.392793] radeon 0000:01:0
0.0: Saved 89 dwords of commands on ring 0.
2013-06-27T19:27:15.053166+01:00 xenakis kernel:    45.392795] radeon 0000:01:0
0.0: GPU softreset 
2013-06-27T19:27:15.053167+01:00 xenakis kernel:    45.392796] radeon 0000:01:0
0.0:   R_008010_GRBM_STATUS=0xA0003028
2013-06-27T19:27:15.053168+01:00 xenakis kernel:    45.392798] radeon 0000:01:0
0.0:   R_008014_GRBM_STATUS2=0x00000002
2013-06-27T19:27:15.053168+01:00 xenakis kernel:    45.392799] radeon 0000:01:0
0.0:   R_000E50_SRBM_STATUS=0x200008C0
2013-06-27T19:27:15.053169+01:00 xenakis kernel:    45.392801] radeon 0000:01:0
0.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
2013-06-27T19:27:15.053169+01:00 xenakis kernel:    45.392802] radeon 0000:01:0
0.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
2013-06-27T19:27:15.053170+01:00 xenakis kernel:    45.392804] radeon 0000:01:0
0.0:   R_00867C_CP_BUSY_STAT     = 0x00000800
2013-06-27T19:27:15.053170+01:00 xenakis kernel:    45.392806] radeon 0000:01:0
0.0:   R_008680_CP_STAT          = 0x800000E3
2013-06-27T19:27:15.198179+01:00 xenakis kernel:    45.538221] radeon 0000:01:0
0.0: Wait for MC idle timedout !
2013-06-27T19:27:15.198186+01:00 xenakis kernel:    45.538223] radeon 0000:01:0
0.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
2013-06-27T19:27:15.213178+01:00 xenakis kernel:    45.553198] radeon 0000:01:0
0.0: R_008020_GRBM_SOFT_RESET=0x00000001
2013-06-27T19:27:15.229185+01:00 xenakis kernel:    45.569172] radeon 0000:01:0
0.0:   R_008010_GRBM_STATUS=0x00003028
2013-06-27T19:27:15.229192+01:00 xenakis kernel:    45.569174] radeon 0000:01:0
0.0:   R_008014_GRBM_STATUS2=0x00000002
2013-06-27T19:27:15.229193+01:00 xenakis kernel:    45.569175] radeon 0000:01:0
0.0:   R_000E50_SRBM_STATUS=0x200008C0
2013-06-27T19:27:15.229193+01:00 xenakis kernel:    45.569177] radeon 0000:01:0
0.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
2013-06-27T19:27:15.229194+01:00 xenakis kernel:    45.569178] radeon 0000:01:0
0.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
2013-06-27T19:27:15.229195+01:00 xenakis kernel:    45.569180] radeon 0000:01:0
0.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
2013-06-27T19:27:15.229195+01:00 xenakis kernel:    45.569181] radeon 0000:01:0
0.0:   R_008680_CP_STAT          = 0x00000000
2013-06-27T19:27:15.230177+01:00 xenakis kernel:    45.570181] radeon 0000:01:0
0.0: GPU reset succeeded, trying to resume
2013-06-27T19:27:15.231160+01:00 xenakis kernel:    45.571232] [drm] probing ge
n 2 caps for device 8086:d138 = 2/0
2013-06-27T19:27:15.231166+01:00 xenakis kernel:    45.571233] [drm] enabling P
CIE gen 2 link speeds, disable with radeon.pcie_gen2=0
2013-06-27T19:27:15.377182+01:00 xenakis kernel:    45.716925] radeon 0000:01:0
0.0: Wait for MC idle timedout !

but I do not understand any of that, but the time is as it booted with no usable screen/keyboard.
As far as I am aware I do not have a GPU.

Of course you have! But if not, it would explain why your X is not working.rotfl!
A RadeonHD 4650 should have an R700 I think…

GPU = Graphics Processing Unit, it’s that chip on your graphics card (or mainboard) that does all the graphics related work: Graphics processing unit - Wikipedia, the free encyclopedia

Well, did you try to add the boot options of failsafe mode as I suggested?
https://forums.opensuse.org/english/get-technical-help-here/install-boot-login/485207-no-x-srenn-12-3-a-2.html#post2568004

Cannot try that until I am physically close to the machine, but I will as soon as I can

Ahh, okay.

I didn’t recall seeing mention of that info (just recalled the mention of XDM), so I figured you were using a KDE desktop. Some of the display managers make use of the underlining XDM scripts (e.g. KDM, LightDM…). These DM’s have their own log file(s). As Wolfi pointed out just above, KDM uses just /var/log/kdm.log. Lightdm, on the other hand, makes use of several within /var/log/lightdm/ (lightdm.log and the, per display basis, x-n-greeter.log and x-n.log … where n= the ith X display number, for i=0,1,…)

but it has not started the display manager yet.
From what you are conveying it does read like there generally seems to be a gpu lockup that occurs before XDM’s greeter screen can even be shown/rendered on screen (this would require the X server to be running … DM –> X –> login greeter). However, I do note that you also made mention that

which would certainly indicate that your system is sometimes able to make it past the point of launching X.

I don’t know if the xorg.log from those instances might help shed more light or not. However:

xdm.errors does not report any error, ending:

Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
I just note that ending like that (i.e. with the last activity being related to the DRI framework) is consistent with the earlier reported message that seems to indicate that a lockup occurs/stems from something with the userspace r600g driver (i.e. the mesa/dri driver)

I doubt the vga= parameter is the problem as that is the same in failsafe which does boot
I don’t really expect it to be playing a part here either in this case, but would like to explore the possibility of the mode set having some cascading effect … in any regard, the underling dynamics (in terms of the graphics stack initilization and configuration) during the failsafe boot are different then that of normal boot’s routines, so just because it works under the one (failsafe boot) does not imply that it will not have impact under the other

Have found in /var/log/messages

2013-06-27T19:27:15.037139+01:00 xenakis kernel: 45.376780] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
2013-06-27T19:27:15.037149+01:00 xenakis kernel: 45.376784] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000003 last fence id 0x0000000000000001)
2013-06-27T19:27:15.053159+01:00 xenakis kernel: 45.392793] radeon 0000:01:00.0: Saved 89 dwords of commands on ring 0.
2013-06-27T19:27:15.053166+01:00 xenakis kernel: 45.392795] radeon 0000:01:00.0: GPU softreset
2013-06-27T19:27:15.053167+01:00 xenakis kernel: 45.392796] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003028
2013-06-27T19:27:15.053168+01:00 xenakis kernel: 45.392798] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000002
2013-06-27T19:27:15.053168+01:00 xenakis kernel: 45.392799] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200008C0
2013-06-27T19:27:15.053169+01:00 xenakis kernel: 45.392801] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
2013-06-27T19:27:15.053169+01:00 xenakis kernel: 45.392802] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
2013-06-27T19:27:15.053170+01:00 xenakis kernel: 45.392804] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000800
2013-06-27T19:27:15.053170+01:00 xenakis kernel: 45.392806] radeon 0000:01:00.0: R_008680_CP_STAT = 0x800000E3
2013-06-27T19:27:15.198179+01:00 xenakis kernel: 45.538221] radeon 0000:01:00.0: Wait for MC idle timedout !
2013-06-27T19:27:15.198186+01:00 xenakis kernel: 45.538223] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE
2013-06-27T19:27:15.213178+01:00 xenakis kernel: 45.553198] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
2013-06-27T19:27:15.229185+01:00 xenakis kernel: 45.569172] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0x00003028
2013-06-27T19:27:15.229192+01:00 xenakis kernel: 45.569174] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000002
2013-06-27T19:27:15.229193+01:00 xenakis kernel: 45.569175] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200008C0
2013-06-27T19:27:15.229193+01:00 xenakis kernel: 45.569177] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000
2013-06-27T19:27:15.229194+01:00 xenakis kernel: 45.569178] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000
2013-06-27T19:27:15.229195+01:00 xenakis kernel: 45.569180] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000
2013-06-27T19:27:15.229195+01:00 xenakis kernel: 45.569181] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000
2013-06-27T19:27:15.230177+01:00 xenakis kernel: 45.570181] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
2013-06-27T19:27:15.231160+01:00 xenakis kernel: 45.571232] [drm] probing gen 2 caps for device 8086:d138 = 2/0
2013-06-27T19:27:15.231166+01:00 xenakis kernel: 45.571233] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
2013-06-27T19:27:15.377182+01:00 xenakis kernel: 45.716925] radeon 0000:01:00.0: Wait for MC idle timedout !

but I do not understand any of that, but the time is as it booted with no usable screen/keyboard.
It looks like the gpu locks up but the drm kernel driver is able to it reset it and starts things going again but …