The Toughbook Intel GMA flicker on Linux thread

[SHEEPMAN!]

As a reminder and a bump set MK3 (CF-30) bios to internal lcd in bios and not a flicker in sight.

Interesting things.
CF-30 Mark 2 does not have the flickeritis.
I'm running a huge update as we speak...will report if any change.

J'd
KTPAX2M (mk-3 30)

[SHEEPMAN!]

JS LOG: Cinnamon started at Sat Nov 08 2014 13:49:51 GMT-0800 (PST)

(cinnamon:2104): St-CRITICAL **: st_widget_get_theme_node called on the widget [0x2e63ba0 StBoxLayout.menu-selected-app-box] which is not in the stage.
JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
JS LOG: network applet: Found connection for active

(gnome-terminal:2202): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib.

(mintUpdate.py:2239): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(mintUpdate.py:2239): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(mintUpdate.py:2239): libglade-WARNING **: unknown attribute `swapped' for <signal>.

(mintUpdate.py:2239): libglade-WARNING **: unknown attribute `swapped' for <signal>.
Window manager warning: Log level 8: meta_window_move_resize: assertion '!window->override_redirect' failed
Window manager warning: Log level 8: meta_window_move_resize: assertion '!window->override_redirect' failed
Window manager warning: Log level 8: meta_window_move_resize: assertion '!window->override_redirect' failed

(cinnamon-settings-daemon:1824): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS1: unable to get EDID for output

(cinnamon-settings-daemon:1824): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS1: unable to get EDID for output

(cinnamon-settings-daemon:1824): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS1: unable to get EDID for output

After using [menu][displays] to reset to 800x600 then refusing the change. Flicker went away for this session.

[kode-niner]

Do you have Display and Monitor sections in xorg.conf? I don't think our old laptops LCD panels properly report EDID, so the driver doesn't know the full capabilities of the display without it being manually detailed in xorg.

[SHEEPMAN!]

That would be a negative.

I never went that far until the glitch (flicker).

It's all learning curve.

Thanks,

J'd

[kode-niner]

That would be a negative.

I never went that far until the glitch (flicker).

It's all learning curve.

Thanks,

J'd

Copy that. It's not all that necessary, but detailing our ancient LCD's parameters in xorg allows us to set different refresh rates and resolutions in our respective monitor control panels or xrandr. Otherwise we're locked at basic VESA and 60Hz.

I haven't really played around with monitors plugged into our VGA ports and how they are recognized and controlled. At this point it's more of a curiosity. Ultimately I am searching for an actual technical explanation for our flickering problems instead of hacking half-assed solutions.

Nick.

[SHEEPMAN!]

That would be a negative.

I never went that far until the glitch (flicker).

It's all learning curve.

Thanks,

J'd

Copy that. It's not all that necessary, but detailing our ancient LCD's parameters in xorg allows us to set different refresh rates and resolutions in our respective monitor control panels or xrandr. Otherwise we're locked at basic VESA and 60Hz.

I haven't really played around with monitors plugged into our VGA ports and how they are recognized and controlled. At this point it's more of a curiosity. Ultimately I am searching for an actual technical explanation for our flickering problems instead of hacking half-assed solutions.

Nick.

Total agreement with the last line. I care more for the why then the actual fix. Meanwhile I can use a LTS version with the exterior monitor disabled in bios.

[UNCNDL1]

Just brainstorming here with the left and right coasts. I can not help but wonder if it is as simple as a custom video driver from robolinux: http://sourceforge.net/projects/robolinux/files/
They will build for free a custom wifi and or video driver if none of the generic ones that load will work for your system. I've talked to Sadlmkr about this and posted another link to their site, but no one has tried out the new debian operating system they have available. Currently they have one for Mint, one for OpenSuse, and a debian version for xfce and gnome. This could be the end of a MK3 CF-30 flicker...

[SHEEPMAN!]

10-4 Cleve...I hear you as I am using a CF-53...not a flicker in sight.

J'd ...just wanna know why...

[mklym]

FYI.

Clean install, then all updates available, of Mint 17.1 Mate on a CF-19MK4. There is no flicker. Screen looks as it should....great!

[mklym]

This thread should be a sticky since we found a solution.