Updated to Kernel 4.7.3-desktop-1omv and the screen shows several small desktops

Support
21

Is it ok if I send it as a pdf file?

22

I am uploading the output of the command journalctl -b -1 as a pdf file.

J. M. Islas

23

I’m lost where did you upload to like pastebin or other?

24

Nope, as an attachment by email, but I admit this is the first time we use this feature, I did not even look at it and configure it :slight_smile:

Well I whitelisted txt but not yet pdf :smile:

Giving my email in pv

25

One thing I was wrong about is the naming of the video device or card (is it a card of chipset?). The way jmislas wrote it is correct. Sorry about that. Intel Corporation Mobile 4 series is something I don’t know anything about, for one important thing is when was it introduced? How old is it?

Edit: Is this it? http://ark.intel.com/products/35134

Edit: Found this:
http://www.intel.com/assets/PDF/datasheet/320122.pdf

26

Nope, I don’t after all. Also my heavily medicated brain seems to be failing me at times lately


jmislas thanks for reporting the issue and thanks for providing the requested information. I’m sure we’ll get the journalctl logs soon.

Edit: jmislas could you tell us what computer name and model # and cpu? Maybe run:

 $ inxi -CGM
27

Output of journalctl as attachment. (117.5 KB)

Starting from line 1633:

Sep 27 21:52:54 localhost.localdomain sddm-greeter[5153]: Loading
file:///usr/share/sddm/themes/breeze/Main.qml...
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject::installEventFilter(): Cannot filter
events for objects in a different thread.
Sep 27 21:52:56 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:58 localhost.localdomain sddm-greeter[5153]: "" has no desktop group, cannot construct
a KPluginInfo object from it.
Sep 27 21:52:59 localhost.localdomain sddm-greeter[5153]: QObject: Cannot create children for a
parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffe006a1228), parent's thread is
QThread(0x588950), current thread is QThread(0x5e2d80)
Sep 27 21:52:59 localhost.localdomain sddm-greeter[5153]: QObject::installEventFilter(): Cannot filter
events for objects in a different thread.
Sep 27 21:53:01 localhost.localdomain sddm-greeter[5153]:
file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to assign [undefined] to
int
1 Like
28

This is the output of the command using the old kernel:

$ inxi -CGM
Machine: System: Sony product: VGN-NS150FJ v: C6U0CNQT
Mobo: Sony model: VAIO Bios: American Megatrends v: R0190Y3 date: 07/09/2008
CPU: Dual core Intel Core2 Duo T5900 (-MCP-) cache: 2048 KB
clock speeds: max: 2200 MHz 1: 800 MHz 2: 800 MHz
Graphics: Card: Intel Mobile 4 Series Integrated Graphics Controller
Display Server: OpenMandriva X.org 118.4 driver: intel Resolution: 1280x800@59.94hz
GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1 Mesa 12.0.3

J. M. Islas

1 Like
29

After some researchs it seems vctivating dri3 in Intel driver fhould solve the issue, or at least be a workaround, I’m looking for how to do this in OM.

Source:
https://bbs.archlinux.org/viewtopic.php?id=207705&p=3

1 Like
30

Thank you very much for the workaround information Raphael! As a final
request, could you give me a hint on how to enable DRI? Do I need to make
the conf file and save it to /etc/X11/xorg.conf.d/20-intel.conf? And should
I do this while being in text mode in 4.7.3 kernel?

Thanks again!

J. M Islas

1 Like
31

Don’t know if this or anything in this post will help but it’s worth a look:

https://forum.kde.org/viewtopic.php?f=289&t=127575&sid=1e60b7d3483d2433f15ec52cb9000a6c&p=364257#p364257

Note that thread is pretty old now and the problems discussed are supposed to have long since been fixed in the driver or xorg or wherever.

1 Like
32

Hi Raph,
The thread you mention appears to be contradictory. According to this link Intel graphics - ArchWiki that is referenced in the text DRI3 is enabled by default. I can assume that people who were trying to fix this had DRI2 enabled in their xorg.conf file and just needed to remove that entry to enable DRI3. OMLx3 does not use an xorg.conf file in a normal install it relies on auto-detection thus we default to DRI3 as the normal configuration. The solution may well be to revert to DRI2.

jmislas to try out the various options mentioned in the page link above. As you have said yourself you will need to create the file /etc/X11/xorg.conf.d/20-intel.conf with this as the minimum content.
Section “Device”
Identifier “Intel Graphics”
Driver “intel”
EndSection
Once you have this file you can add options to this for example to enable DRI2 the file should look like this.
Section “Device”
Identifier “Intel Graphics”
Driver “intel”
Option “DRI” “2”
EndSection

Try testing this an see if it works it doesn’t matter what mode you are in when you create it you will always need to restart X to activate it. The simplest method is to reboot alternatively you can restart the sddm service with (as root) “systemctl restart sddm”
If you read the contents of the link in the this post you will see that there are also some kernel command line options you might try. Unfortunately I don’t have this hardware so I am unable to replicate the fault. There is one note in the link which mentions a setting to keep the graphics card in high power mode if it were me I would try this first.

3 Likes
33

Thank you very much Colin, I will post if it works as soon as possible.

J. M. Islas

1 Like
34

Hello Colin, Raphael and Ben, I created the file with Colin’s lines.
Unfortunately it did not work. I tried several combinations of the
workaround recommended before but still no success.
Thank you again for taking the time to help me with this issue.

J. M. Islas

1 Like
35

Hello again everybody, I want to report that the issue is repeated in Fedora 23 with kernel 4.7.x, so apparently it is a kernel and intel driver issue. Hopefully someone could give me a hint on how to proceed in order to fix this.

J. M. Islas

1 Like
36

Is there a bug report on this? There probably should be one.

Does kernel 4.7.3 work with vesa driver? This is important to know.

At this point I’d remove any files created that did not resolve this issue.
Next I would log into older kernel and reinstall kernel 4.7.3:

# urpmi --replacepkgs kernel-release-desktop-4.7.3-1omv

Then boot into it an see if that helped. If not then I’d run XFdrake and try to reinstall correct Intel driver. If none of that works you need help from a developer and the way to get that is with a bug report.

37

There is also a new kernel version 4.8.1 in Main-Updates repo to try.

38

Thank you very much Ben, is there a particular repository that I need to
use to get the kernel update? I do not see kernel version 4.8.1 in my list
of updates.

Thanks in advance.

J. M. Islas

39

If you have the normal repositories enabled it will come in updates when ever your mirror is up to date. The new kernel is in Main-updates repo. Normal repos are:

Main
Main-updates
Contrib
Contrib-updates
Non-free
Non-free-updates
and where legal and if you are brave and need these:
Restricted
Restricted-updates

Some people add i586 repos if they need to install i586 packages.

1 Like
40

Thank you again Ben, I meant mirror and not repository, anyways I deleted
and added the default repos and got the kernel update. Finally the problem
has been fixed by this kernel version. Thanks to all openmandriva users who
helped solving this issue.

J. M. Islas

2 Likes