Desktop lockup (13.1 + KDE)

English Install/Boot/Login
1

Hi all,

In early February this year I downloaded the openSUSE 13.1 iso for my 32-bit PC together with the requisite checksum to verify the download was correct, which it was. I then burned the iso to a DVD+RW using openSUSE 12.3 + K3B which completed successfully without any errors or warnings and used that to perform a fresh install of 13.1.

Since that time the system has suffered many soft lockups. Sometimes even the mouse pointer locks in place. As an example, on one past lockup the system switched to a black screen with some text on it, a part of which was:-

stuck for 22s! [Xorg:762]

Sometimes the number in the square brackets is 700.

Sometimes if the system is left for a few minutes it will revert to the login/password screen.

Does anyone know if the text that is displayed on the black screen after the lockup is saved into a log somewhere on the system ?
If so, where can I find that log ?

I think that much of the text on the black screen, that I can’t remember at this point, may be useful in fixing this problem.

Thanks in advance for any help that you can give with this.

Stuart

2

stuarte9 wrote:

>
> Hi all,
>
> In early February this year I downloaded the openSUSE 13.1 iso for my
> 32-bit PC together with the requisite checksum to verify the download
> was correct, which it was. I then burned the iso to a DVD+RW using
> openSUSE 12.3 + K3B which completed successfully without any errors or
> warnings and used that to perform a fresh install of 13.1.

Did you then run the updates?
There were initial problems with the 32 bit version.

> Does anyone know if the text that is displayed on the black screen after
> the lockup is saved into a log somewhere on the system ?
> If so, where can I find that log ?

All logs go to /var/log/. Listing by date (ls -ltr) you can detect which got
new entries, then have a look inside.

Also have a look at the .xsession-errors and .xsession-errors-:0 files on
your home.

–
Cheers / Saludos,

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

3

Good afternoon Carlos,

Thank you for such a fast reply. Yes I have applied all updates made available so far. Whenever I receive an update alert from the System Tray, I apply the updates right away. I even applied an update this morning so the system is as up-to-date as it can be.

I’m having a problem with examining the .xsessions-errors and the .xseesions-errors-:0 files you suggested I look at. As you can see from the partial “ls -al” listing of my home directory shown below,

-rw-r–r-- 1 suse users 1940 Feb 1 17:42 .xim.template
drwxr-xr-x 2 suse users 4096 Apr 22 18:29 .xine
-rwxr-xr-x 1 suse users 1112 Feb 1 17:42 .xinitrc.template
-rw------- 1 suse users 0 Jun 13 10:40 .xsession-errors
-rw------- 1 suse users 51525 Jun 13 11:11 .xsession-errors-:0
-rw-r–r-- 1 suse users 185586 Jun 6 11:51 .y2log
-rw-r–r-- 1 suse users 282 Jun 6 11:48 .y2usersettings
suse@linux-luwl:~> less .xsessions-errors
.xsessions-errors: No such file or directory
suse@linux-luwl:~> less .xsessions-errors-:0
.xsessions-errors-:0: No such file or directory
suse@linux-luwl:~> more .xsessions-errors
.xsessions-errors: No such file or directory
suse@linux-luwl:~> more .xsessions-errors-:0
.xsessions-errors-:0: No such file or directory

the files are present but wont show their contents using “less” or “more”. I should state here that I am logged in as ordinary user suse. I have also carried out the same process after I “su -” to root. I still could not see the contents of those two files.

With respect to /var/log, shown below is a partial “ls -ltr” listing.

-rw-r–r-- 1 root root 33412 Jun 13 10:41 Xorg.0.log.old
-rw-r----- 1 root root 10603865 Jun 13 10:43 pk_backend_zypp-1
-rw-r–r-- 1 root root 10320 Jun 13 12:24 wpa_supplicant.log
-rw-r–r-- 1 root root 10002 Jun 13 12:24 boot.log
-rw-r–r-- 1 root root 292292 Jun 13 12:24 lastlog
-rw-r–r-- 1 root root 281051 Jun 13 12:24 kdm.log
-rw-r–r-- 1 root root 24081 Jun 13 12:24 localmessages
-rw-r----- 1 root root 2128748 Jun 13 12:25 NetworkManager
-rw-r–r-- 1 root root 0 Jun 13 12:25 pm-powersave.log
-rw-r–r-- 1 root root 33412 Jun 13 12:25 Xorg.0.log
-rw-r----- 1 root root 1071622 Jun 13 12:30 warn
-rw-r----- 1 root root 3869650 Jun 13 12:31 messages
-rw-r----- 1 root root 1814112 Jun 13 12:31 pk_backend_zypp
-rw-r----- 1 root root 794253 Jun 13 12:33 firewall
-rw-rw-r-- 1 root utmp 48000 Jun 13 12:34 wtmp
suse@linux-luwl:/var/log>

This shows all the files that were last accessed by the system, this after the system suffered yet another soft lock up. Is their a particular tool to be used to view log files ?

I’ve had a brief look into some of the files (boot.log, kdm.log, Xorg.0.log) but none of them contains the text that is sometimes shown after a lock up has occured.

As this very much seems to be a graphics problem I should state that this old P4 PC is using an NVIDIA GeForce FX5200 in conjunction with the system-selected Nouveau driver.

Given that the numbers 700 and 762 have appeared in square brackets in the post lock up text, I had a look into /var/log/Xorg.0.log and found the following.

33.547] (--) RandR disabled
33.763] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
33.763] (II) AIGLX: enabled GLX_INTEL_swap_event
33.763] (II) AIGLX: enabled GLX_ARB_create_context
33.763] (II) AIGLX: enabled GLX_ARB_create_context_profile
33.763] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
33.763] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
33.763] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
33.771] (II) AIGLX: Loaded and initialized nouveau
33.771] (II) GLX: Initialized DRI2 GL provider for screen 0
33.777] (II) NOUVEAU(0): NVEnterVT is called.
33.793] (II) NOUVEAU(0): Setting screen physical size to 338 x 270
33.793] resize called 1280 1024
34.250] (II) config/udev: Adding input device Power Button (/dev/input/event2)

These are the only lines in the file with a 7xx in square brackets. I don’t see anything wrong here. However, earlier in the same file there is the following.

33.071] (==) Using config directory: "/etc/X11/xorg.conf.d"
33.071] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
33.073] (==) No Layout section.  Using the first Screen section.
33.073] (==) No screen section available. Using defaults.
33.073] (**) |-->Screen "Default Screen Section" (0)
33.073] (**) |   |-->Monitor "<default monitor>"
33.073] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
33.073] (==) Automatically adding devices
33.073] (==) Automatically enabling devices
33.073] (==) Automatically adding GPU devices
33.074] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.

The line sixth from the bottom of this group says no monitor was specified. Should I have specified a monitor during installation ? I thought that was detected automatically during the install.

As you can see from the foregoing, I am at a bit of a loss here. If you can give further help with this I would be very grateful.

Stuart

4

Take a closer look. The file name is “.xsession-errors”, not “.xsessions-errors”
So this should work: (.xsession-errors is empty anyway)

less .xsession-errors-:0

As this very much seems to be a graphics problem I should state that this old P4 PC is using an NVIDIA GeForce FX5200 in conjunction with the system-selected Nouveau driver.

Does this happen in “Recovery Mode” as well? (“Advanced Options” in the boot menu)

If not, it is most definitely a graphics driver issue.
In that I case I would strongly suggest to install the proprietary nvidia driver, you need the G01 variant, i.e. the third one labelled “For GeForce FX cards (5xxx)” here:
http://en.opensuse.org/SDB:NVIDIA_drivers

The line sixth from the bottom of this group says no monitor was specified. Should I have specified a monitor during installation ? I thought that was detected automatically during the install.

No. That’s ok.
And the monitor is not just detected automatically during the install, but whenever you connect one or boot.

5

Hi Forum Moderator,

Thanks for the reply and for pointing out my typo.

The code you supplied did work. Reviewing the output I found the following.

kwin(1168) KWin::EffectsHandlerImpl::loadEffect: EffectsHandler::loadEffect : Effect “kwin4_effect_blur”
is not supported
QDBusObjectPath: invalid path “”
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result
in instability
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
QGraphicsLinearLayout::insertItem: cannot insert null item
plasma-desktop(1173)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability
QGraphicsLinearLayout::insertItem: cannot insert null item

These are the only lines in the .xsession-errors-:0 file that make any mention about instability. They would seem to indicate that the
problem lies with KDE’s Plasma desktop. I’m not sure what 1173 refers to. I haven’t added any plugins to Plasma, as far as I know.
Maybe it happened during one of the many updates I have applied.

With respect to Advanced Options in the boot menu:-
How do I display the boot menu as well as its “Advanced Options” … option ? :wink:

With respect to installing the NVidia driver:-
I never(!!) had this instability problem with previous versions of openSUSE using the Nouveau driver. For example, 12.3 was rock solid!

In early February this year, two things happened. I changed my ISP which meant that I had to use “their” router and I downloaded and
installed 13.1. I’m not convinced that the problem does not arise from the former. There was never any instability using 12.3 in
conjunction with my previous ISP’s router, a different model from the current box.

Thanks very much for your help so far.

Stuart

6

Assuming you run grub2 not grub1 then advanced should be an option on first menu for each main menu item You can’’’’'t to my knowledge have both the menu and the advanved options active at the same time if that is what you ment

7

1173 is the process id of plasma-desktop.
But that’s just debug output, nothing critical.
It tells though that the “Blur” effect is not supported, which could also point to a graphics driver issue. Although I’m not sure that your card would support the Blur effect.
Maybe just try to turn that off though, it could well be the cause of your problems. “Configure Desktop”->“Desktop Effects”->“All Effects”.

With respect to Advanced Options in the boot menu:-
How do I display the boot menu as well as its “Advanced Options” … option ? :wink:

You should see an entry labelled “Advanced Options” in the boot menu, i.e. the menu right after you turn on/reboot your computer where you can select which operating system to boot. Selecting “Advanced Options” will give you some more choices like the “Recovery Mode” which uses (among other compatibility options) a generic graphics driver.

With respect to installing the NVidia driver:-
I never(!!) had this instability problem with previous versions of openSUSE using the Nouveau driver. For example, 12.3 was rock solid!

Well, the version included in 13.1 could have a bug/regression that affects your specific card. Things like this happened all the time.
OTOH, also KDE has changed and it (or specific desktop effects at least) might use the graphics driver in a slightly different way now than in 12.3.

In early February this year, two things happened. I changed my ISP which meant that I had to use “their” router and I downloaded and
installed 13.1. I’m not convinced that the problem does not arise from the former. There was never any instability using 12.3 in
conjunction with my previous ISP’s router, a different model from the current box.

The router should not render your system unstable.

As I said, I would suggest to try Recovery Mode to see if it happens there as well.
Then, if not, I would recommend to install the proprietary nvidia driver.

8

Hi all,

@gogalthorp:
Thanks for the reply. Yes, the system is using grub2. I found the “Advanced Options” on the boot menu. No, I didn’t mean having the main menu and advanced options active at the same time. I just haven’t used advanced options before and so didn’t really pay much attention to it before and so just wasn’t sure where advanced options were located. Thanks for the “heads up” though about not being able to have both the menu and advanced options available at the same time. I appreciate it.

@wolfi323:
Thanks for another reply.

With respect to your comments about the Blur effect:
I switched that off, switched off the PC completely for a few minutes, cold booted into Recovery mode, and played a few games of KMahjongg without any soft lock ups. (These lock ups always occurred during some sort of screen transition, e.g. rotating the cube desktop, a window/dialog box fading out) I then warm rebooted back to “normal” mode (i.e.not recovery mode), and played a few more games. So far(!!) there have been no more soft lock ups. It would seem that your comment about my graphics card not supporting Blur could very well be true. With all due respect I’ll use the PC for a few more days before I make a final decision on that.

With respect to finding "Advanced Options on the boot menu:
Thank you for pointing out its location. Please also see my reply to gogalthorp above.

With respect to my router:
I would agree that the router should not make a system unstable, given that the software that interacts with it is separate from the graphics sub-system. It just seemed rather curious that this instability coincided with using a different model of router with what had formerly been a rock solid distro. Jings, is my face red. :slight_smile:

One last thing. In a few days, assuming that the system now remains stable, I would like to amend the thread title to include “[Solved]” so that others don’t waste their time offering solutions to a hopefully solved problem. How do I go about amending the thread title in this way ?

Once again, thanks very much for all your help with this.

Stuart

9

Well, it’s not so much the graphics card not supporting it, but the graphics driver claiming to support it but having problems with it (at least the version shipped in openSUSE 13.1). If it’s not supported, it would be just turned off automatically.
If you install the proprietary nvidia driver, it should work even with Blur enabled.

You could also try to switch the “Composite Type” to “OpenGL 1.2” in Desktop Effects->Advanced though, as your card only supports up to 1.5 anyway.

If your system runs stable now, you can of course stay with the nouveau driver if you prefer that.
That’s your decision.

But only the nvidia driver would fully support your card and give the best possible performance (especially regarding 3D) I suppose.

One last thing. In a few days, assuming that the system now remains stable, I would like to amend the thread title to include “[Solved]” so that others don’t waste their time offering solutions to a hopefully solved problem. How do I go about amending the thread title in this way ?

If you post a reply, you can change the title as well.

10

On 2014-06-13 15:06, stuarte9 wrote:

>
> -rw-r–r-- 1 suse users 1940 Feb 1 17:42 .xim.template
> drwxr-xr-x 2 suse users 4096 Apr 22 18:29 .xine
> -rwxr-xr-x 1 suse users 1112 Feb 1 17:42 .xinitrc.template
> -rw------- 1 suse users 0 Jun 13 10:40 .xsession-errors
> -rw------- 1 suse users 51525 Jun 13 11:11 .xsession-errors-:0
> -rw-r–r-- 1 suse users 185586 Jun 6 11:51 .y2log
> -rw-r–r-- 1 suse users 282 Jun 6 11:48 .y2usersettings
> suse@linux-luwl:~> less .xsessions-errors
> .xsessions-errors: No such file or directory
> suse@linux-luwl:~> less .xsessions-errors-:0
> .xsessions-errors-:0: No such file or directory
> suse@linux-luwl:~> more .xsessions-errors
> .xsessions-errors: No such file or directory
> suse@linux-luwl:~> more .xsessions-errors-:0
> .xsessions-errors-:0: No such file or directory

You have to escape the colon:


cer@Telcontar:~> l .xsession-errors-\:0
-rw------- 1 cer users 1396524 Jun 15 21:13 .xsession-errors-:0
cer@Telcontar:~>

It is simple. You start typing “l .xsess”, then hit tab. The line auto
completes. A second tab and it shows you the choices:


cer@Telcontar:~> l .xsession-errors
..xsession-errors      .xsession-errors-:0   .xsession-errors.old
cer@Telcontar:~> l .xsession-errors

So I just type a single dash, hit tab again, and it fully completes.

–
Cheers / Saludos,

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

11

… for example, I have never found the nouveau driver to support tv-out/S-Video out on my card, but the nvidia driver works beautifully.

12

Good afternoon all,

@Fraser Bell:
I have been using the VGA port on the card and, for some years, the card has worked well with the Nouveau driver, including error free performance with the Cube Desktop. Thanks for the info though, much appreciated. :slight_smile:

@robin_listas:
I haven’t used tab completion much so I found your reply interesting. :slight_smile: Perhaps I should invest more time exploring that functionality. Thanks for your reply, again much appreciated.

@wolfi323:
Our last correspondence was on Sunday 15th June. I took your advice and turned off the Blur desktop effect. In Desktop Effects->Advanced I set “Composite Type” to “OpenGL 1.2” and the one below it (Qt Graphics System, if I remember correctly) to “Raster”. (I had to use my Fedora 20 HDD to generate this posting. Curiously, it has “Compositing type” set to OpenGL 2.0 and “Qt graphics sytem” to “Raster” and hardly ever locks up.)

The following day, there wasn’t a single desktop lock up and so it seemed that your suggestion had cured the problem. Sadly, from Tuesday onwards the desktop reverted to locking up.

On Wednesday I actioned your other suggestion and installed the NVidia driver. Immediately prior to doing that I followed the instructions listed in a previous “NVIDIA Accelerated Linux Driver Set README and Installation Guide”. (Years ago, before the Nouveau driver appeared, I had installed the NVidia driver several times with the driver not giving any problems. After Nouveau appeared I decided to give it a try and had been happy with it, untill this problem arose.) These instructions amounted to the following.

  1. Log in as root.
  2. cp /etc/inittab /etc/inittab.original, save original run level.
  3. Edit inittab, changing “id:5:initdefautl:” to “id:3:initdefautl:”
  4. Reboot the system into single user mode, no X server running.
  5. Run the installer, “sh NVIDIA-Linux-x86-1.0-7664-pkg#.run”
  6. cp /etc/inittab.original /etc/inittab, recover original run level.
  7. Reboot system to GUI.

On this occassion, having downloaded and saved the NVidia driver, I carried out steps 1-4 listed above. For some reason, the system kept booting to the desktop. So, as I was “locked out” of booting to the CLI, I decided to install the NVidia driver using the desktop, the link you provided, and the one-click install process using the first yellow button, above which was the label “For GeForce FX cards
(5xxx)”. This went smoothly and installed successfully.

On rebooting, the system now(!!) boots to runlevel 3, the CLI. I then carried out steps 6 & 7 listed above and rebooted. The system now will only(!!) boot to the CLI, even though /etc/inittab now contains “id:5:initdefautl:”. Further, on issuing startx, the system doesn’t
recognise this command and displays the following.

suse@linux-luwl.~>startx
hostname: Name or service not known
xauth: file /home/suse/.serverauth.968 does not exist

(EE)
fatal server error:
(EE) Cannot move old log file “/var/log/Xorg.0.log” to “/var/log/Xorg.0.log.old”
(EE)
(EE)
Please consult the The X.org Foundation support
at http://wiki.x.org
for help.
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

xinit failed. /usr/bin/Xorg is not setuid, maybe that’s the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
suse@linux-luwl.~>

I have payed a quick visit to wiki.x.org which appears to have some help available. However, before plumbing those depths(!!), I was
wondering if you might be able offer a more limited suggestion that nonetheless might work. Afterall, your suggestion about switching
off the Blur effect did work, albeit for only a short while.

Thanks again for all the help that you have given so far with this and for any help you may be able to give with this next problem.

Stuart

13

That’s completely outdated.
First of all, you don’t have to boot to runlevel 3 to install the nvidia driver via the repo.
And 13.1 uses systemd instead of sysvinit. Systemd does not use /etc/inittab and just ignores it.
Adding a ‘3’ to the boot options still works though.

And, as a side-note, that nvidia driver version 1.0 is ancient as well of course. You shouldn’t use that one. :wink:

On rebooting, the system now(!!) boots to runlevel 3, the CLI. I then carried out steps 6 & 7 listed above and rebooted. The system now will only(!!) boot to the CLI, even though /etc/inittab now contains “id:5:initdefautl:”. Further, on issuing startx, the system doesn’t
recognise this command and displays the following.

You are not booting to runlevel 3 now. But apparently the X server fails to start.
Please boot to recovery mode (“Advanced Options” in the boot menu) and post the file /var/log/Xorg.0.log.old to see why.

Probably the wrong packages got installed, so please post the output of this as well:

rpm -qa | egrep "(kernel|nvidia)"

And remove the /etc/inittab, it is useless.

Do you have an /etc/X11/xorg.conf maybe?
This would cause such a problem, as you probably specified the nouveau driver in there, but that cannot be loaded when the nvidia driver is installed.
So if you have that file, just remove it and reboot.

suse@linux-luwl.~>startx
hostname: Name or service not known
xauth: file /home/suse/.serverauth.968 does not exist

(EE)
fatal server error:
(EE) Cannot move old log file “/var/log/Xorg.0.log” to “/var/log/Xorg.0.log.old”
(EE)
(EE)
Please consult the The X.org Foundation support
at http://wiki.x.org
for help.
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

xinit failed. /usr/bin/Xorg is not setuid, maybe that’s the reason?
If so either use a display manager (strongly recommended) or adjust /etc/permissions.local
suse@linux-luwl.~>

“startx” only works as root. you don’t have the required permissions to run X as user.
Read the message (the last line) to see how you could use it as user.

But if X fails to start on a normal boot, “startx” won’t work either anyway.

14

On 2014-06-27 15:36, wolfi323 wrote:
>
> stuarte9;2651056 Wrote:

> So if you have that file, just remove it and reboot.

I think that there is some, very limited, support for the file. It can
be used to trick certain broken yast module into working.

> But if X fails to start on a normal boot, “startx” won’t work either
> anyway.

It can be used to diagnose the graphical driver, though, you usually see
the failure reason right in the text display. And it doesn’t “appear” to
lock the machine, you get back to the terminal.

–
Cheers / Saludos,

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

15

No. There is absolutely no support for that file by systemd.

You can use it to trick YaST’s legacy runlevel module into working by having that file (you can then change the default runlevel at least, which changes systemd’s default target as well), but you shouldn’t use that any more on 13.1 anyway.
It has been replaced by the “Services Manager” module, which of course absolutely ignores that file as well.

> But if X fails to start on a normal boot, “startx” won’t work either
> anyway.

It can be used to diagnose the graphical driver, though, you usually see
the failure reason right in the text display. And it doesn’t “appear” to
lock the machine, you get back to the terminal.

Well, you have the failure reason in the Xorg.0.log anyway.
And if X will fail to start on boot, the system should drop to a text mode login prompt as well.

But you know perfectly well yourself that “startx” won’t work out of the box as user, don’t you? :wink:

16

On 2014-06-27 17:06, wolfi323 wrote:

> No. There is absolutely no support for that file by systemd.
>
> You can trick to use YaST’s runlevel module into working by having that
> file (you can then change the default runlevel at least, which changes
> systemd’s default target as well), but you shouldn’t use that any more
> on 13.1 anyway.
> It has been replaced by the “Services Manager” module, which of course
> absolutely ignores that file as well.

Well, that clarifies it.

>>> But if X fails to start on a normal boot, “startx” won’t work either
>>> anyway.
>>
>> It can be used to diagnose the graphical driver, though, you usually see
>> the failure reason right in the text display. And it doesn’t “appear” to
>> lock the machine, you get back to the terminal.
>>
> Well, you have the failure reason in the Xorg.0.log anyway.

which you have to go look for :slight_smile:

With startx you do not need to reboot. You can do a change to X config,
test it, and go back. If you kill it (ctrl-alt-backspace-backspace)
because it fails, it does not try to restart graphics mode. You do not
need to logon. To try again you don’t have to do “init 3; init 5”, which
is slower because it also starts a few more things.

For testing, it has some advantages :wink:

> And if X will fail to start on boot, the system should drop to a text
> mode login prompt as well.

Yes, true.
Should.
But some people are baffled.

> But you know perfectly well yourself that “startx” won’t work out of the
> box as user, don’t you? :wink:

Oh, absolutely, and also how to make it work, which I do on some of
systems, and I also do know about its caveats, which preclude using it
for normal usage :wink:

–
Cheers / Saludos,

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

17

Good afternoon all,

@wolfi323:
The /etc/X11 directory does not contain a file called xorg.conf. I did have a look inside the files that are in this directory but did not find any mention of Nouveau in any of them.

The output of the rpm command you provided is as shown below.

suse@linux-luwl:~> rpm -qa | egrep “(kernel|nvidia)”
nvidia-gfxG01-kmp-default-173.14.39_k3.11.6_4-27.1.i586
texlive-l3kernel-doc-2013.81.svn_4469svn29409-10.5.3.noarch
kernel-default-devel-3.11.10-7.1.i586
kernel-docs-3.11.10-11.3.noarch
kernel-xen-devel-3.11.10-11.1.i686
kernel-xen-devel-3.11.10-7.1.i686
kernel-desktop-devel-3.11.10-11.1.i686
kernel-devel-3.11.10-7.1.noarch
kernel-source-3.11.10-7.1.noarch
texlive-l3kernel-2013.81.svn_4469svn29409-10.5.3.noarch
kernel-source-3.11.10-11.1.noarch
kernel-default-devel-3.11.10-11.1.i586
kernel-syms-3.11.10-7.1.i586
kernel-firmware-20130714git-2.17.1.noarch
x11-video-nvidiaG01-173.14.39-28.1.i586
kernel-pae-devel-3.11.10-11.1.i686
kernel-syms-3.11.10-11.1.i586
kernel-desktop-devel-3.11.10-7.1.i686
kernel-default-3.11.10-11.1.i586
patterns-openSUSE-devel_kernel-13.1-13.6.1.i586
kernel-devel-3.11.10-11.1.noarch
kernel-pae-devel-3.11.10-7.1.i686
kernel-default-3.11.10-7.1.i586
suse@linux-luwl:~>

Using the “Preview Post” button, the system tell me that the posting (at 21899 characters) is too long and that I need to shorten it to 15000 characters. Please see my next post for the contents of /var/log/Xorg.0.log.old.

I hope this helps you as I’m not sure what all of this means.

Stuart

18

Good afternoon again all,
@wolfi232:
The contents of the first part of the /var/log/Xorg.0.log.old are as shown below.

28.956]

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the “xorg” product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
28.956]
X.Org X Server 1.14.3.901 (1.14.4 RC 1)
Release Date: 2013-10-26
28.957] X Protocol Version 11, Revision 0
28.957] Build Operating System: openSUSE SUSE LINUX
28.957] Current Operating System: Linux linux-luwl 3.11.10-11-default #1 SMP Mon May 12 13:37:06 UTC 2014 (3d22b5f) i686
28.957] Kernel command line: BOOT_IMAGE=/vmlinuz-3.11.10-11-default root=UUID=e713fb57-7098-4e6b-9f3e-ef3bbd3047e9 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
28.957] Build Date: 17 April 2014 05:36:11AM
28.957]
28.957] Current version of pixman: 0.30.2
28.957] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
28.957] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
28.957] (==) Log file: “/var/log/Xorg.0.log”, Time: Fri Jun 27 17:49:20 2014
28.958] (==) Using config file: “/etc/X11/xorg.conf.install”
28.958] (==) Using config directory: “/etc/X11/xorg.conf.d”
28.958] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
28.976] (==) ServerLayout “Layout”
28.976] () |–>Screen “vboxvideo” (0)
28.976] () | |–>Monitor “<default monitor>”
28.976] () | |–>Device “vboxvideo”
28.976] (==) No monitor specified for screen “vboxvideo”.
Using a default monitor configuration.
28.976] () |–>Screen “vmware” (1)
28.976] () | |–>Monitor “<default monitor>”
28.976] () | |–>Device “vmware”
28.976] (==) No monitor specified for screen “vmware”.
Using a default monitor configuration.
28.976] () |–>Screen “modesetting” (2)
28.976] () | |–>Monitor “<default monitor>”
28.977] () | |–>Device “modesetting”
28.977] (==) No monitor specified for screen “modesetting”.
Using a default monitor configuration.
28.977] () |–>Screen “fbdev” (3)
28.977] () | |–>Monitor “<default monitor>”
28.977] () | |–>Device “fbdev”
28.977] (==) No monitor specified for screen “fbdev”.
Using a default monitor configuration.
28.977] () |–>Screen “vesa” (4)
28.977] () | |–>Monitor “<default monitor>”
28.977] () | |–>Device “vesa”
28.977] (==) No monitor specified for screen “vesa”.
Using a default monitor configuration.
28.977] (==) Automatically adding devices
28.977] (==) Automatically enabling devices
28.977] (==) Automatically adding GPU devices
29.166] (WW) The directory “/usr/share/fonts/misc/sgi” does not exist.
29.166] Entry deleted from font path.
29.198] (==) 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
29.198] (==) ModulePath set to “/usr/lib/xorg/modules/updates,/usr/lib/xorg/modules”
29.198] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
29.198] (II) Loader magic: 0x8260620
29.198] (II) Module ABI versions:
29.198] X.Org ANSI C Emulation: 0.4
29.198] X.Org Video Driver: 14.1
29.198] X.Org XInput driver : 19.1
29.198] X.Org Server Extension : 7.0
29.201] (–) PCI:*(0:0:8:0) 10de:0322:0000:0000 rev 161, Mem @ 0xdc000000/16777216, 0xc0000000/268435456, BIOS @ 0x???/131072
29.201] (–) PCI: (0:1:0:0) 1106:3118:1106:3118 rev 2, Mem @ 0xd8000000/67108864, 0xdd000000/16777216, BIOS @ 0x???/65536
29.201] Initializing built-in extension Generic Event Extension
29.201] Initializing built-in extension SHAPE
29.201] Initializing built-in extension MIT-SHM
29.201] Initializing built-in extension XInputExtension
29.201] Initializing built-in extension XTEST
29.201] Initializing built-in extension BIG-REQUESTS
29.201] Initializing built-in extension SYNC
29.201] Initializing built-in extension XKEYBOARD
29.201] Initializing built-in extension XC-MISC
29.201] Initializing built-in extension SECURITY
29.201] Initializing built-in extension XINERAMA
29.201] Initializing built-in extension XFIXES
29.201] Initializing built-in extension RENDER
29.201] Initializing built-in extension RANDR
29.201] Initializing built-in extension COMPOSITE
29.201] Initializing built-in extension DAMAGE
29.201] Initializing built-in extension MIT-SCREEN-SAVER
29.201] Initializing built-in extension DOUBLE-BUFFER
29.201] Initializing built-in extension RECORD
29.201] Initializing built-in extension DPMS
29.201] Initializing built-in extension X-Resource
29.201] Initializing built-in extension XVideo
29.201] Initializing built-in extension XVideo-MotionCompensation
29.201] Initializing built-in extension XFree86-VidModeExtension
29.201] Initializing built-in extension XFree86-DGA
29.201] Initializing built-in extension XFree86-DRI
29.202] Initializing built-in extension DRI2
29.202] (II) LoadModule: “glx”
29.233] (II) Loading /usr/lib/xorg/modules/updates/extensions/libglx.so
29.623] (II) Module glx: vendor=“NVIDIA Corporation”
29.623] compiled for 4.0.2, module version = 1.0.0
29.623] Module class: X.Org Server Extension
29.623] (II) NVIDIA GLX Module 173.14.39 Wed Nov 27 15:13:59 PST 2013
29.623] Loading extension GLX
29.623] (II) LoadModule: “vboxvideo”
29.671] (WW) Warning, couldn’t open module vboxvideo
29.671] (II) UnloadModule: “vboxvideo”
29.671] (II) Unloading vboxvideo
29.671] (EE) Failed to load module “vboxvideo” (module does not exist, 0)
29.671] (II) LoadModule: “vmware”
29.672] (WW) Warning, couldn’t open module vmware
29.672] (II) UnloadModule: “vmware”
29.672] (II) Unloading vmware
29.672] (EE) Failed to load module “vmware” (module does not exist, 0)
29.672] (II) LoadModule: “modesetting”
29.673] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
29.673] (II) Module modesetting: vendor=“X.Org Foundation”
29.673] compiled for 1.14.3.901, module version = 0.8.0
29.673] Module class: X.Org Video Driver
29.673] ABI class: X.Org Video Driver, version 14.1
29.673] (II) LoadModule: “fbdev”
29.674] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
29.674] (II) Module fbdev: vendor=“X.Org Foundation”
29.674] compiled for 1.14.3, module version = 0.4.3
29.674] Module class: X.Org Video Driver
29.674] ABI class: X.Org Video Driver, version 14.1
29.674] (II) LoadModule: “vesa”
29.675] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
29.675] (II) Module vesa: vendor=“X.Org Foundation”
29.675] compiled for 1.14.3, module version = 2.3.3
29.675] Module class: X.Org Video Driver
29.675] ABI class: X.Org Video Driver, version 14.1
29.675] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
29.675] (II) FBDEV: driver for framebuffer: fbdev
29.675] (II) VESA: driver for VESA chipsets: vesa
29.675] (++) using VT number 7

Please see my next post for the remainder of /var/log/Xorg.0.log.olg.

Stuart

19

Don’t bother, this is from recovery mode, i.e. the wrong one.

I will reply to your previous post in a minute.

20

Good afternoon yet again all,
@wolfi232:
The remaining contents of file /var/log/Xorg.0.log.old are shown below.

29.676] (EE) open /dev/dri/card0: No such file or directory
29.676] (WW) Falling back to old probe method for modesetting
29.676] (EE) open /dev/dri/card0: No such file or directory
29.676] (II) Loading sub module "fbdevhw"
29.676] (II) LoadModule: "fbdevhw"
29.677] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
29.677] (II) Module fbdevhw: vendor="X.Org Foundation"
29.677]     compiled for 1.14.3.901, module version = 0.0.2
29.677]     ABI class: X.Org Video Driver, version 14.1
29.677] (**) FBDEV(1): claimed PCI slot 0@0:8:0
29.677] (II) FBDEV(1): using default device
29.677] (WW) Falling back to old probe method for vesa
29.677] (EE) Screen 0 deleted because of no matching config section.
29.677] (II) UnloadModule: "modesetting"
29.678] (II) FBDEV(0): Creating default Display subsection in Screen section
"fbdev" for depth/fbbpp 8/8
29.678] (==) FBDEV(0): Depth 8, (==) framebuffer bpp 8
29.678] (==) FBDEV(0): Default visual is PseudoColor
29.678] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
29.678] (II) FBDEV(0): hardware: VESA VGA (video memory: 1280kB)
29.678] (II) FBDEV(0): checking modes against framebuffer device...
29.678] (II) FBDEV(0): checking modes against monitor...
29.678] (--) FBDEV(0): Virtual size is 1280x1024 (pitch 1280)
29.678] (**) FBDEV(0):  Built-in mode "current": 131.1 MHz, 80.3 kHz, 76.6 Hz
29.678] (II) FBDEV(0): Modeline "current"x0.0  131.09  1280 1312 1472 1632  1024 1028 1032 1048 -hsync -vsync -csync (80.3 kHz b)
29.678] (==) FBDEV(0): DPI set to (96, 96)
29.678] (II) Loading sub module "fb"
29.678] (II) LoadModule: "fb"
29.679] (II) Loading /usr/lib/xorg/modules/libfb.so
29.679] (II) Module fb: vendor="X.Org Foundation"
29.680]     compiled for 1.14.3.901, module version = 1.0.0
29.680]     ABI class: X.Org ANSI C Emulation, version 0.4
29.680] (**) FBDEV(0): using shadow framebuffer
29.680] (II) Loading sub module "shadow"
29.680] (II) LoadModule: "shadow"
29.680] (II) Loading /usr/lib/xorg/modules/libshadow.so
29.693] (II) Module shadow: vendor="X.Org Foundation"
29.693]     compiled for 1.14.3.901, module version = 1.1.0
29.693]     ABI class: X.Org ANSI C Emulation, version 0.4
29.693] (II) UnloadModule: "vesa"
29.693] (II) Unloading vesa
29.694] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
29.694] (==) FBDEV(0): Backing store disabled
29.698] (==) FBDEV(0): DPMS enabled
29.698] (==) RandR enabled
29.960] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
30.435] (II) config/udev: Adding input device Power Button (/dev/input/event2)
30.435] (**) Power Button: Applying InputClass "evdev keyboard catchall"
30.435] (**) Power Button: Applying InputClass "evdev keyboard catchall"
30.435] (**) Power Button: Applying InputClass "LocalKeyboard"
30.435] (II) LoadModule: "evdev"
30.436] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
30.461] (II) Module evdev: vendor="X.Org Foundation"
30.461]     compiled for 1.14.3, module version = 2.8.2
30.461]     Module class: X.Org XInput Driver
30.461]     ABI class: X.Org XInput driver, version 19.1
30.461] (II) Using input driver 'evdev' for 'Power Button'
30.461] (**) Power Button: always reports core events
30.461] (**) evdev: Power Button: Device: "/dev/input/event2"
30.461] (--) evdev: Power Button: Vendor 0 Product 0x1
30.461] (--) evdev: Power Button: Found keys
30.461] (II) evdev: Power Button: Configuring as keyboard
30.461] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
30.461] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
30.461] (**) Option "xkb_rules" "evdev"
30.461] (**) Option "xkb_model" "pc104"
30.461] (**) Option "xkb_layout" "gb"
30.533] (II) config/udev: Adding input device Power Button (/dev/input/event0)
30.533] (**) Power Button: Applying InputClass "evdev keyboard catchall"
30.533] (**) Power Button: Applying InputClass "evdev keyboard catchall"
30.533] (**) Power Button: Applying InputClass "LocalKeyboard"
30.533] (II) Using input driver 'evdev' for 'Power Button'
30.533] (**) Power Button: always reports core events
30.533] (**) evdev: Power Button: Device: "/dev/input/event0"
30.533] (--) evdev: Power Button: Vendor 0 Product 0x1
30.533] (--) evdev: Power Button: Found keys
30.533] (II) evdev: Power Button: Configuring as keyboard
30.533] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
30.533] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
30.533] (**) Option "xkb_rules" "evdev"
30.533] (**) Option "xkb_model" "pc104"
30.533] (**) Option "xkb_layout" "gb"
30.535] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
30.535] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
30.535] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
30.535] (**) Sleep Button: Applying InputClass "LocalKeyboard"
30.535] (II) Using input driver 'evdev' for 'Sleep Button'
30.535] (**) Sleep Button: always reports core events
30.535] (**) evdev: Sleep Button: Device: "/dev/input/event1"
30.535] (--) evdev: Sleep Button: Vendor 0 Product 0x3
30.535] (--) evdev: Sleep Button: Found keys
30.535] (II) evdev: Sleep Button: Configuring as keyboard
30.535] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
30.535] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
30.535] (**) Option "xkb_rules" "evdev"
30.535] (**) Option "xkb_model" "pc104"
30.535] (**) Option "xkb_layout" "gb"
30.537] (II) config/udev: Adding input device MOON AND  (/dev/input/event3)
30.537] (**) MOON AND : Applying InputClass "evdev pointer catchall"
30.537] (**) MOON AND : Applying InputClass "evdev pointer catchall"
30.537] (II) Using input driver 'evdev' for 'MOON AND '
30.537] (**) MOON AND : always reports core events
30.537] (**) evdev: MOON AND : Device: "/dev/input/event3"
30.537] (--) evdev: MOON AND : Vendor 0x13ee Product 0x1
30.537] (--) evdev: MOON AND : Found 3 mouse buttons
30.537] (--) evdev: MOON AND : Found scroll wheel(s)
30.537] (--) evdev: MOON AND : Found relative axes
30.537] (--) evdev: MOON AND : Found x and y relative axes
30.537] (II) evdev: MOON AND : Configuring as mouse
30.537] (II) evdev: MOON AND : Adding scrollwheel support
30.537] (**) evdev: MOON AND : YAxisMapping: buttons 4 and 5
30.537] (**) evdev: MOON AND : EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
30.537] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:10.1/usb2/2-1/2-1:1.0/input/input3/event3"
30.537] (II) XINPUT: Adding extended input device "MOON AND " (type: MOUSE, id 9)
30.537] (II) evdev: MOON AND : initialized for relative axes.
30.538] (**) MOON AND : (accel) keeping acceleration scheme 1
30.538] (**) MOON AND : (accel) acceleration profile 0
30.538] (**) MOON AND : (accel) acceleration factor: 2.000
30.538] (**) MOON AND : (accel) acceleration threshold: 4
30.539] (II) config/udev: Adding input device MOON AND  (/dev/input/mouse0)
30.539] (II) No input driver specified, ignoring this device.
30.539] (II) This device may have been added with another device file.
30.539] (II) config/udev: Adding input device HID 04f3:0103 (/dev/input/event4)
30.539] (**) HID 04f3:0103: Applying InputClass "evdev keyboard catchall"
30.539] (**) HID 04f3:0103: Applying InputClass "evdev keyboard catchall"
30.539] (**) HID 04f3:0103: Applying InputClass "LocalKeyboard"
30.539] (II) Using input driver 'evdev' for 'HID 04f3:0103'
30.539] (**) HID 04f3:0103: always reports core events
30.539] (**) evdev: HID 04f3:0103: Device: "/dev/input/event4"
30.540] (--) evdev: HID 04f3:0103: Vendor 0x4f3 Product 0x103
30.540] (--) evdev: HID 04f3:0103: Found keys
30.540] (II) evdev: HID 04f3:0103: Configuring as keyboard
30.540] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:10.1/usb2/2-2/2-2:1.0/input/input4/event4"
30.540] (II) XINPUT: Adding extended input device "HID 04f3:0103" (type: KEYBOARD, id 10)
30.540] (**) Option "xkb_rules" "evdev"
30.540] (**) Option "xkb_model" "pc104"
30.540] (**) Option "xkb_layout" "gb"
30.541] (II) config/udev: Adding input device HID 04f3:0103 (/dev/input/event5)
30.541] (**) HID 04f3:0103: Applying InputClass "evdev keyboard catchall"
30.541] (**) HID 04f3:0103: Applying InputClass "evdev keyboard catchall"
30.542] (**) HID 04f3:0103: Applying InputClass "LocalKeyboard"
30.542] (II) Using input driver 'evdev' for 'HID 04f3:0103'
30.542] (**) HID 04f3:0103: always reports core events
30.542] (**) evdev: HID 04f3:0103: Device: "/dev/input/event5"
30.542] (--) evdev: HID 04f3:0103: Vendor 0x4f3 Product 0x103
30.542] (--) evdev: HID 04f3:0103: Found 1 mouse buttons
30.542] (--) evdev: HID 04f3:0103: Found scroll wheel(s)
30.542] (--) evdev: HID 04f3:0103: Found relative axes
30.542] (II) evdev: HID 04f3:0103: Forcing relative x/y axes to exist.
30.542] (--) evdev: HID 04f3:0103: Found absolute axes
30.542] (II) evdev: HID 04f3:0103: Forcing absolute x/y axes to exist.
30.542] (--) evdev: HID 04f3:0103: Found keys
30.542] (II) evdev: HID 04f3:0103: Configuring as mouse
30.542] (II) evdev: HID 04f3:0103: Configuring as keyboard
30.542] (II) evdev: HID 04f3:0103: Adding scrollwheel support
30.542] (**) evdev: HID 04f3:0103: YAxisMapping: buttons 4 and 5
30.542] (**) evdev: HID 04f3:0103: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
30.542] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:10.1/usb2/2-2/2-2:1.1/input/input5/event5"
30.542] (II) XINPUT: Adding extended input device "HID 04f3:0103" (type: KEYBOARD, id 11)
30.542] (**) Option "xkb_rules" "evdev"
30.542] (**) Option "xkb_model" "pc104"
30.542] (**) Option "xkb_layout" "gb"
30.543] (II) evdev: HID 04f3:0103: initialized for relative axes.
30.543] (WW) evdev: HID 04f3:0103: ignoring absolute axes.
30.543] (**) HID 04f3:0103: (accel) keeping acceleration scheme 1
30.543] (**) HID 04f3:0103: (accel) acceleration profile 0
30.543] (**) HID 04f3:0103: (accel) acceleration factor: 2.000
30.543] (**) HID 04f3:0103: (accel) acceleration threshold: 4
30.544] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
30.544] (II) No input driver specified, ignoring this device.
30.544] (II) This device may have been added with another device file.
30.556] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
59.271] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
59.271] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
59.502] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)

2282.833] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
2282.833] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
2283.183] (II) evdev: HID 04f3:0103: Close
2283.183] (II) UnloadModule: “evdev”
2283.183] (II) evdev: HID 04f3:0103: Close
2283.183] (II) UnloadModule: “evdev”
2283.183] (II) evdev: MOON AND : Close
2283.183] (II) UnloadModule: “evdev”
2283.183] (II) evdev: Sleep Button: Close
2283.183] (II) UnloadModule: “evdev”
2283.183] (II) evdev: Power Button: Close
2283.183] (II) UnloadModule: “evdev”
2283.183] (II) evdev: Power Button: Close
2283.184] (II) UnloadModule: “evdev”
2283.340] (EE) Server terminated successfully (0). Closing log file.

Please note that I have been careful not to leave out anything from this file except the blank line that occurs between the end of the file (partial) contents as shown in my previous posting and the start of the file (remaining) contents as shown in this posting.

Once again, I hope this helps.

Stuart