Unable to graphically log in after a full upgrade and the battery running flat

I forgot to turn on the power cord to my laptop, and did a “zypper up”. When I returned some hours later, the battery was flat and now I am unable to boot to the normal login screen. The last message I get is

drm:radeon_acpi_init *ERROR* cannot find a backlight controller

before it gives me a prompt for a text-based login rather than graphical. I am able to login but cannot get the normal graphical interface. I can remotely login to the machine. I can also bring the machine up in MS Windows, so there has been no damage to the hardware.

I tried issuing the command

startx

but this did not help. It suggested I look at the file .local/share/xorg/Xorg.0.log, which I have attached.

Can anyone advise me what I need to do to recover? I am running 13.2 on a 64bit machine.

The Xorg.0.log file:

   537.987] 
X.Org X Server 1.16.1
Release Date: 2014-09-21
   537.987] X Protocol Version 11, Revision 0
   537.987] Build Operating System: openSUSE SUSE LINUX
   537.987] Current Operating System: Linux t2 3.16.7-21-desktop #1 SMP PREEMPT Tue Apr 14 07:11:37 UTC 2015 (93c1539) x86_64
   537.987] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.7-21-desktop root=UUID=fba3c745-c56c-4f2d-8d6a-bf86c3aa4738 ro resume=/dev/disk/by-uuid/73229ef7-df65-4f6a-848c-ef99a4bbf47d splash=silent quiet showopts
   537.987] Build Date: 12 June 2015  07:55:09PM
   537.987]  
   537.987] Current version of pixman: 0.32.6
   537.987]     Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
   537.987] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
   537.987] (==) Log file: "/home/gfreeman/.local/share/xorg/Xorg.0.log", Time: Thu Jul 30 17:25:20 2015
   537.996] (==) Using config directory: "/etc/X11/xorg.conf.d"
   537.996] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
   537.997] (==) No Layout section.  Using the first Screen section.
   537.997] (==) No screen section available. Using defaults.
   537.997] (**) |-->Screen "Default Screen Section" (0)
   537.997] (**) |   |-->Monitor "<default monitor>"
   537.997] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
   537.997] (==) Automatically adding devices
   537.997] (==) Automatically enabling devices
   537.997] (==) Automatically adding GPU devices
   538.125] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
   538.125]     Entry deleted from font path.
   538.125] (==) FontPath set to:
    /usr/share/fonts/misc:unscaled,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/ghostscript/,
    /usr/share/fonts/cyrillic:unscaled,
    /usr/share/fonts/truetype/,
    built-ins
   538.125] (==) ModulePath set to "/usr/lib64/xorg/modules"
   538.125] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
   538.125] (II) Loader magic: 0x80ec80
   538.125] (II) Module ABI versions:
   538.125]     X.Org ANSI C Emulation: 0.4
   538.125]     X.Org Video Driver: 18.0
   538.125]     X.Org XInput driver : 21.0
   538.125]     X.Org Server Extension : 8.0
   538.126] (II) xfree86: Adding drm device (/dev/dri/card0)
   538.126] (II) xfree86: Adding drm device (/dev/dri/card1)
   539.400] (--) PCI:*(0:0:1:0) 1002:9999:1179:fa44 rev 0, Mem @ 0xd0000000/268435456, 0xf0300000/262144, I/O @ 0x00004000/256
   539.400] (--) PCI: (0:1:0:0) 1002:6663:1179:fa44 rev 0, Mem @ 0xe0000000/268435456, 0xf0200000/262144, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
   539.400] (II) LoadModule: "glx"
   539.438] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
   539.576] (II) Module glx: vendor="X.Org Foundation"
   539.576]     compiled for 1.16.1, module version = 1.0.0
   539.576]     ABI class: X.Org Server Extension, version 8.0
   539.576] (==) AIGLX enabled
   539.576] (==) Matched fglrx as autoconfigured driver 0
   539.576] (==) Matched ati as autoconfigured driver 1
   539.576] (==) Matched fglrx as autoconfigured driver 2
   539.576] (==) Matched ati as autoconfigured driver 3
   539.577] (==) Matched fglrx as autoconfigured driver 4
   539.577] (==) Matched ati as autoconfigured driver 5
   539.577] (==) Matched modesetting as autoconfigured driver 6
   539.577] (==) Matched fbdev as autoconfigured driver 7
   539.577] (==) Matched vesa as autoconfigured driver 8
   539.577] (==) Assigned the driver to the xf86ConfigLayout
   539.577] (II) LoadModule: "fglrx"
   539.583] (WW) Warning, couldn't open module fglrx
   539.583] (II) UnloadModule: "fglrx"
   539.583] (II) Unloading fglrx
   539.583] (EE) Failed to load module "fglrx" (module does not exist, 0)
   539.583] (II) LoadModule: "ati"
   539.583] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
   539.604] (II) Module ati: vendor="X.Org Foundation"
   539.604]     compiled for 1.16.1, module version = 7.4.0
   539.604]     Module class: X.Org Video Driver
   539.604]     ABI class: X.Org Video Driver, version 18.0
   539.604] (II) LoadModule: "radeon"
   539.604] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
   539.631] (II) Module radeon: vendor="X.Org Foundation"
   539.631]     compiled for 1.16.1, module version = 7.4.0
   539.631]     Module class: X.Org Video Driver
   539.631]     ABI class: X.Org Video Driver, version 18.0
   539.631] (II) LoadModule: "modesetting"
   539.631] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
   539.639] (II) Module modesetting: vendor="X.Org Foundation"
   539.640]     compiled for 1.16.1, module version = 0.9.0
   539.640]     Module class: X.Org Video Driver
   539.640]     ABI class: X.Org Video Driver, version 18.0
   539.640] (II) LoadModule: "fbdev"
   539.640] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
   539.642] (II) Module fbdev: vendor="X.Org Foundation"
   539.642]     compiled for 1.16.1, module version = 0.4.4
   539.642]     Module class: X.Org Video Driver
   539.642]     ABI class: X.Org Video Driver, version 18.0
   539.642] (II) LoadModule: "vesa"
   539.642] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
   539.643] (II) Module vesa: vendor="X.Org Foundation"
   539.643]     compiled for 1.16.1, module version = 2.3.3
   539.643]     Module class: X.Org Video Driver
   539.643]     ABI class: X.Org Video Driver, version 18.0
   539.643] (II) RADEON: Driver for ATI Radeon chipsets:
    ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
...
   539.656] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
   539.656] (II) FBDEV: driver for framebuffer: fbdev
   539.656] (II) VESA: driver for VESA chipsets: vesa
   539.656] (EE) 
Fatal server error:
   539.657] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
   539.657] (EE) 
   539.657] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
   539.657] (EE) Please also check the log file at "/home/gfreeman/.local/share/xorg/Xorg.0.log" for additional information.
   539.657] (EE) 

two suggestions,

  1. repeat the original cmd from the cmd line

alternatively

  1. try cmd yast and see if the terminal yast works, then try an update

Note startx is depreciated use init 5 as root to start X from terminal

On 2015-07-30 13:26, gogalthorp wrote:
>
> Note startx is depreciated use init 5 as root to start X from terminal

Yes, it is deprecated, but it is perfect for testing graphic driver
issues. Somethings may not work, perhaps sound, automount, permissions
to use cd, etc. Nothing relevant for this issue.

It is perfect because it prints error messages to the display when it
fails, and does not lock the system in the process :slight_smile:


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

Thanks for the suggestions.

I tried running the text command “yast” and doing an update. The system is already completely up-to-date.

I tried “init 5” as root, and this has brought the machine up properly in graphical mode, which is an enormous relief.

There is only one problem: when I reboot, it still goes to single-user login after detecting

cannot find a backlight controller

It would be good if it booted cleanly rather than requiring the root “init 5”. Any suggestions?

As root try running mkinitrd. It may not have been run because of the lack of power

I have tried that, but it still comes up in single user mode following the message “cannot find a backlight controller”.

My suggestions:

YaST > Online Update
Filter – select All Patches
Scroll to the bottom of the list to see the most recent patches
Select in turn each of the installed (i) patches on the bottom page and press <space> to reinstall (+).
Accept

If that does not work try “zypper lr” to list your repositories. Then "zypper dup from" at least the openSUSE-13.2-Oss and *openSUSE-13.2-Update *repositories.

I just noticed from your other thread that you have a btrfs root file system with snapshots enabled. You could use “snapper” to roll back to before the failed update and try again.

as root has the cmd

grub2-mkconfig -o /boot/grub2/grub.cfg

been tried?

fwiw
on laptops the message ‘cannot find a backlight controller’ is often seen,
assumption: this is just a timing problem during boot, from the boot log it should
be evident this corrects itself later in the sequence

I am afraid, that those ideas have made no difference.

I am wondering whether the problem lies with the machine not closing down cleanly when the battery ran out, rather than the update not completing. There were only a few packages needing to be updated, which would not have taken very long. What is involved in “finding the backlight controller”? How is it that “init 5” run as superuser succeeds when the normal boot process fails?

On 2015-08-01 12:16, tgf wrote:

> I am afraid, that those ideas have made no difference.

Then force reinstall all the packages in that update. There is a log.
Perhaps what failed was a postinstall script.

And perhaps nothing failed, but simply there is a bug contained in the
updates that don’t handle well your hardware.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Do you have a btrfs snapshot from just before the power failure and/or the update?

# snapper --help

Is this the same machine that you had to modify GRUB to get initrd to boot?

I have tried to boot from a snapshot. I get the message in Grub:

If OK, run 'snapper rollback 222' and reboot.

When I type Enter, nothing happens. When I type Esc, I get the normal Grub menu, reordered with the snapshot at the top, but I could not boot from it.

I had more success with the Advanced item, where I could choose between 3.16.7-7 and 3.16.7-21. Selecting ‘21’ comes up in single-user mode, whereas it booted cleanly in ‘7’. I also noted that the message about not finding the backlight controller appeared in both cases, so that message has nothing to do with the the problem, as keellambert said.

Is this the same machine that you had to modify GRUB to get initrd to boot?

No, this is a different machine. The other one is working fine now on 3.16.7-21. I was setting that one up to use until I could get this one working again.

Then force reinstall all the packages in that update. There is a log.
Perhaps what failed was a postinstall script.

I have pretty much done this without success. Following the suggestion of eng-int to try “zypper lr” to list my repositories. Then "zypper dup from" at least the openSUSE-13.2-Oss and *openSUSE-13.2-Update *repositories. This removed over 500 packages, reverting to an earlier system, and when I did the “dup” from “13.2-Update”, they were reinstalled.

Yes. I have tried this, but it still comes up in single user mode, needing me to login as root and then to do an “init 5” to get started and log in as me.

On 2015-08-03 09:06, tgf wrote:
> Yes. I have tried this, but it still comes up in single user mode,
> needing me to login as root and then to do an “init 5” to get started
> and log in as me.

I think that the system tries to boot in graphics mode but fails.
Probably some race condition, thus trying later works. You should have a
look at the logs to find out what fail.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

I have had a look at the output from dmesg. I am afraid that most of it is foreign to me. I have copied the tail of the output below:

   20.033486] AVX version of gcm_enc/dec engaged.
   20.295508] acpi-cpufreq: overriding BIOS provided _PSD data
   20.469079] input: PC Speaker as /devices/platform/pcspkr/input/input15
   20.481516] ACPI Warning: SystemIO range 0x0000000000000b00-0x0000000000000b07 conflicts with OpRegion 0x0000000000000b00-0x0000000000000b0f (\_SB_.PCI0.SMBS.SMB0) (20140424/utaddress-258)
   20.481533] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
   20.533088] kvm: Nested Virtualization enabled
   20.533100] kvm: Nested Paging enabled
   20.573920] usbcore: registered new interface driver btusb
   20.680200] Linux video capture interface: v2.00
   20.837301] usb 6-5: USB disconnect, device number 2
   20.837942] usbcore: registered new interface driver ath3k
   20.901132] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - HD (04f2:b3b1)
   20.903226] input: TOSHIBA Web Camera - HD as /devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0/input/input16
   20.903568] usbcore: registered new interface driver uvcvideo
   20.903574] USB Video Class driver (1.1.1)
   20.916889] snd_hda_intel: unknown parameter 'vid' ignored
   20.916897] snd_hda_intel: unknown parameter 'pid' ignored
   20.916903] snd_hda_intel: unknown parameter 'vid' ignored
   20.916906] snd_hda_intel: unknown parameter 'pid' ignored
   20.917410] snd_hda_intel 0000:00:01.1: Force to non-snoop mode
   20.917476] snd_hda_intel 0000:00:01.1: irq 48 for MSI/MSI-X
   21.004383] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card1/input17
   21.005005] sound hdaudioC0D0: autoconfig: line_outs=1 (0xd/0x0/0x0/0x0/0x0) type:speaker
   21.005011] sound hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
   21.005017] sound hdaudioC0D0:    hp_outs=1 (0xb/0x0/0x0/0x0/0x0)
   21.005021] sound hdaudioC0D0:    mono: mono_out=0x0
   21.005024] sound hdaudioC0D0:    inputs:
   21.005029] sound hdaudioC0D0:      Internal Mic=0x11
   21.005034] sound hdaudioC0D0:      Mic=0xa
   21.026676] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/sound/card0/hdaudioC0D0/input18
   21.027200] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:14.2/sound/card0/input19
   21.027402] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:14.2/sound/card0/input20
   21.527167] usb 6-5: new full-speed USB device number 3 using ohci-pci
   22.537665] Adding 2104316k swap on /dev/sda6.  Priority:-1 extents:1 across:2104316k FS
   22.795998] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
   22.813596] FAT-fs (sda2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
   22.844757] XFS (sda8): Mounting V5 Filesystem
   22.971111] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
   23.179777] XFS (sda8): Ending clean mount
   23.237019] cfg80211: Calling CRDA to update world regulatory domain
   23.341316] cfg80211: World regulatory domain updated:
   23.341326] cfg80211:  DFS Master region: unset
   23.341329] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
   23.341336] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
   23.341342] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
   23.341347] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
   23.341351] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
   23.341357] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
   23.341362] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
   23.341366] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
   23.341371] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
   23.382695] ath: phy0: WB335 2-ANT card detected
   23.382704] ath: phy0: Set BT/WLAN RX diversity capability
   23.389212] ath: phy0: Enable LNA combining
   23.390308] ath: phy0: ASPM enabled: 0x42
   23.390314] ath: EEPROM regdomain: 0x65
   23.390317] ath: EEPROM indicates we should expect a direct regpair map
   23.390322] ath: Country alpha2 being used: 00
   23.390324] ath: Regpair used: 0x65
   23.392538] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
   23.393063] ieee80211 phy0: Atheros AR9565 Rev:0 mem=0xffffc90006800000, irq=16
   23.484329] alx 0000:03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [0c:54:a5:0a:28:9e]
   24.581548] audit: type=1305 audit(1438584971.279:2): audit_pid=723 old=0 auid=4294967295 ses=4294967295 res=1
   26.665228] usb 6-5: New USB device found, idVendor=0930, idProduct=0220
   26.665239] usb 6-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
   29.105147] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
   29.105155] Bluetooth: BNEP filters: protocol multicast
   29.105168] Bluetooth: BNEP socket layer initialized
   30.115536] ip6_tables: (C) 2000-2006 Netfilter Core Team
   30.215372] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
   30.284941] ip_tables: (C) 2000-2006 Netfilter Core Team
   31.609292] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
   31.613006] alx 0000:03:00.0: irq 49 for MSI/MSI-X
   31.613379] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
   31.620517] NET: Registered protocol family 17
   46.241422] [drm] probing gen 2 caps for device 1022:1412 = 700d01/6
   46.241431] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
   46.669398] [drm] PCIE GART of 1024M enabled (table at 0x0000000000040000).
   46.669525] radeon 0000:01:00.0: WB enabled
   46.669532] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff8802215bbc00
   46.669536] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff8802215bbc04
   46.669540] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff8802215bbc08
   46.669544] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff8802215bbc0c
   46.669548] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff8802215bbc10
   47.019638] [drm] ring test on 0 succeeded in 1 usecs
   47.019646] [drm] ring test on 1 succeeded in 1 usecs
   47.019654] [drm] ring test on 2 succeeded in 1 usecs
   47.019665] [drm] ring test on 3 succeeded in 4 usecs
   47.019674] [drm] ring test on 4 succeeded in 4 usecs
   47.019879] [drm] ib test on ring 0 succeeded in 0 usecs
   47.020014] [drm] ib test on ring 1 succeeded in 0 usecs
   47.020081] [drm] ib test on ring 2 succeeded in 0 usecs
   47.519652] [drm] ib test on ring 3 succeeded in 0 usecs
   47.519684] [drm] ib test on ring 4 succeeded in 0 usecs
   57.890661] wlp2s0: authenticate with e8:94:f6:5c:b6:4a
   57.905293] wlp2s0: send auth to e8:94:f6:5c:b6:4a (try 1/3)
   57.907553] wlp2s0: authenticated
   57.909153] wlp2s0: associate with e8:94:f6:5c:b6:4a (try 1/3)
   57.913293] wlp2s0: RX AssocResp from e8:94:f6:5c:b6:4a (capab=0x431 status=0 aid=3)
   57.913395] wlp2s0: associated
   57.913449] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
   58.809240] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlp2s0
   58.809250] ll header: 00000000: ff ff ff ff ff ff e8 94 f6 5c b6 4a 08 00        .........\.J..
   59.240392] fuse init (API version 7.23)
   61.878743] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev wlp2s0
   61.878758] ll header: 00000000: ff ff ff ff ff ff e8 94 f6 5c b6 4a 08 00        .........\.J..
 2230.622539] sr 1:0:0:0: [sr0]  
 2230.622550] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2230.622556] sr 1:0:0:0: [sr0]  
 2230.622560] Sense Key : Illegal Request [current] 
 2230.622567] Info fld=0x472
 2230.622571] sr 1:0:0:0: [sr0]  
 2230.622578] Add. Sense: Illegal mode for this track
 2230.622584] sr 1:0:0:0: [sr0] CDB: 
 2230.622587] Read(10): 28 00 00 00 04 72 00 00 02 00
 2230.622603] end_request: I/O error, dev sr0, sector 4552
 2230.622611] Buffer I/O error on device sr0, logical block 569
 2230.680777] sr 1:0:0:0: [sr0]  
 2230.680787] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2230.680793] sr 1:0:0:0: [sr0]  
 2230.680797] Sense Key : Illegal Request [current] 
 2230.680803] Info fld=0x472
 2230.680808] sr 1:0:0:0: [sr0]  
 2230.680815] Add. Sense: Illegal mode for this track
 2230.680821] sr 1:0:0:0: [sr0] CDB: 
 2230.680823] Read(10): 28 00 00 00 04 72 00 00 02 00
 2230.680839] end_request: I/O error, dev sr0, sector 4552
 2230.680847] Buffer I/O error on device sr0, logical block 569
 2231.160355] ISO 9660 Extensions: Microsoft Joliet Level 3
 2231.214103] ISOFS: changing to secondary root
 2375.573068] sr 1:0:0:0: [sr0]  
 2375.573078] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2375.573084] sr 1:0:0:0: [sr0]  
 2375.573088] Sense Key : Illegal Request [current] 
 2375.573095] Info fld=0x7cf
 2375.573100] sr 1:0:0:0: [sr0]  
 2375.573106] Add. Sense: Illegal mode for this track
 2375.573111] sr 1:0:0:0: [sr0] CDB: 
 2375.573114] Read(10): 28 00 00 00 07 ce 00 00 02 00
 2375.573131] end_request: I/O error, dev sr0, sector 7996
 2375.573138] Buffer I/O error on device sr0, logical block 1999
 2375.585724] sr 1:0:0:0: [sr0]  
 2375.585734] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2375.585740] sr 1:0:0:0: [sr0]  
 2375.585745] Sense Key : Illegal Request [current] 
 2375.585751] Info fld=0x7cf
 2375.585756] sr 1:0:0:0: [sr0]  
 2375.585763] Add. Sense: Illegal mode for this track
 2375.585769] sr 1:0:0:0: [sr0] CDB: 
 2375.585772] Read(10): 28 00 00 00 07 cf 00 00 01 00
 2375.585788] end_request: I/O error, dev sr0, sector 7996
 2375.585796] Buffer I/O error on device sr0, logical block 1999
 2380.546555] ISO 9660 Extensions: Microsoft Joliet Level 3
 2380.594025] ISOFS: changing to secondary root
 2491.967101] sr 1:0:0:0: [sr0]  
 2491.967111] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2491.967118] sr 1:0:0:0: [sr0]  
 2491.967122] Sense Key : Illegal Request [current] 
 2491.967129] Info fld=0x76d
 2491.967133] sr 1:0:0:0: [sr0]  
 2491.967141] Add. Sense: Illegal mode for this track
 2491.967146] sr 1:0:0:0: [sr0] CDB: 
 2491.967149] Read(10): 28 00 00 00 07 6c 00 00 02 00
 2491.967169] end_request: I/O error, dev sr0, sector 7600
 2491.967177] Buffer I/O error on device sr0, logical block 950
 2492.338811] sr 1:0:0:0: [sr0]  
 2492.338822] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2492.338828] sr 1:0:0:0: [sr0]  
 2492.338832] Sense Key : Illegal Request [current] 
 2492.338839] Info fld=0x76d
 2492.338844] sr 1:0:0:0: [sr0]  
 2492.338851] Add. Sense: Illegal mode for this track
 2492.338856] sr 1:0:0:0: [sr0] CDB: 
 2492.338859] Read(10): 28 00 00 00 07 6c 00 00 02 00
 2492.338880] end_request: I/O error, dev sr0, sector 7600
 2492.338888] Buffer I/O error on device sr0, logical block 950
 2492.866373] ISO 9660 Extensions: Microsoft Joliet Level 3
 2493.154895] ISOFS: changing to secondary root
 2602.425895] sr 1:0:0:0: [sr0]  
 2602.425906] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2602.425912] sr 1:0:0:0: [sr0]  
 2602.425916] Sense Key : Illegal Request [current] 
 2602.425923] Info fld=0x3eed
 2602.425928] sr 1:0:0:0: [sr0]  
 2602.425935] Add. Sense: Illegal mode for this track
 2602.425940] sr 1:0:0:0: [sr0] CDB: 
 2602.425943] Read(10): 28 00 00 00 3e ec 00 00 02 00
 2602.425960] end_request: I/O error, dev sr0, sector 64432
 2602.425971] Buffer I/O error on device sr0, logical block 8054
 2602.711667] sr 1:0:0:0: [sr0]  
 2602.711678] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
 2602.711684] sr 1:0:0:0: [sr0]  
 2602.711688] Sense Key : Illegal Request [current] 
 2602.711695] Info fld=0x3eed
 2602.711700] sr 1:0:0:0: [sr0]  
 2602.711707] Add. Sense: Illegal mode for this track
 2602.711712] sr 1:0:0:0: [sr0] CDB: 
 2602.711715] Read(10): 28 00 00 00 3e ec 00 00 02 00
 2602.711732] end_request: I/O error, dev sr0, sector 64432
 2602.711744] Buffer I/O error on device sr0, logical block 8054
 2603.148410] ISO 9660 Extensions: Microsoft Joliet Level 3
 2603.201359] ISOFS: changing to secondary root
 2861.990844] ISO 9660 Extensions: Microsoft Joliet Level 3
 2862.113484] ISO 9660 Extensions: RRIP_1991A
[17827.248577] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage
[17827.248585] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
[51023.546033] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery reached max voltage
[51023.546042] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed
[52528.994696] ISO 9660 Extensions: Microsoft Joliet Level 3
[52529.117552] ISO 9660 Extensions: RRIP_1991A

On 2015-08-04 01:36, tgf wrote:
> I have had a look at the output from dmesg. I am afraid that most of it
> is foreign to me. I have copied the tail of the output below:

Mmm.

No, the logs to look at are /var/log/Xorg.0.log and
/var/log/Xorg.0.log.old. If you are running a graphic session, the
problem would logged in the previous (.old) one.

Don’t paste here, but in susepaste.org (for a limited time), then post a
link here.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

http://susepaste.org/78971396is Xorg.0.log.old

and
http://susepaste.org/13637729
is Xorg.0.log