Announcement

**GreyGeek** · May 28, 2018, 10:33 AM

What video chip is being used, and what is its driver?

**edugs** · May 28, 2018, 12:24 PM

Originally posted by GreyGeek View Post

What video chip is being used, and what is its driver?

lspci
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)

How I can see the driver?

Thank you so much

**Qqmike** · May 28, 2018, 01:29 PM

How I can see the driver?

Until GreyGeek returns, you might try this command:

inxi -Fxz

**GreyGeek** · May 28, 2018, 01:52 PM

You're probably running the i915 nouveau driver.
lsmod | grep i915
would confirm that if it is installed as the driver.

Here is a solution I found, which is easy (if it works):

I was able to solve it by creating a file called /etc/X11/xorg.conf.d/20-intel.conf containing the following:

Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "NoAccel" "True"
Option "DRI" "False"
EndSection

followed by logging out and then back in, or rebooting.

There is a bug report about hanging.
It seems that hanging can occur when the video goes into a power saving mode. Setting "enable_rc6" to 0 prevents that.
If you are using the i915 driver then we can discuss setting some of its params. You can see what their current settings are by listing the parameters:

Code:

vdir /sys/module/i915/parameters/
total 0
-r-------- 1 root root 4096 May 28 14:31 alpha_support
-r-------- 1 root root 4096 May 28 14:31 disable_display
-r-------- 1 root root 4096 May 28 14:31 disable_power_well
-r-------- 1 root root 4096 May 28 14:31 edp_vswing
-r-------- 1 root root 4096 May 28 14:31 enable_cmd_parser
-r-------- 1 root root 4096 May 28 14:31 enable_dc
-rw------- 1 root root 4096 May 28 14:31 enable_dpcd_backlight
-rw------- 1 root root 4096 May 28 14:31 enable_dp_mst
-r-------- 1 root root 4096 May 28 14:31 enable_execlists
-rw------- 1 root root 4096 May 28 14:31 enable_fbc
-r-------- 1 root root 4096 May 28 14:31 enable_guc_loading
-r-------- 1 root root 4096 May 28 14:31 enable_guc_submission
-r-------- 1 root root 4096 May 28 14:31 enable_gvt
-rw-r--r-- 1 root root 4096 May 28 14:31 enable_hangcheck
-rw------- 1 root root 4096 May 28 14:31 enable_ips
-r-------- 1 root root 4096 May 28 14:31 enable_ppgtt
-rw------- 1 root root 4096 May 28 14:31 enable_psr
-r-------- 1 root root 4096 May 28 14:31 enable_rc6
-rw------- 1 root root 4096 May 28 14:31 error_capture
-rw------- 1 root root 4096 May 28 14:31 fastboot
-rw------- 1 root root 4096 May 28 14:31 force_reset_modeset_test
-r-------- 1 root root 4096 May 28 14:31 guc_firmware_path
-r-------- 1 root root 4096 May 28 14:31 guc_log_level
-r-------- 1 root root 4096 May 28 14:31 huc_firmware_path
-r-------- 1 root root 4096 May 28 14:31 inject_load_failure
-rw------- 1 root root 4096 May 28 14:31 invert_brightness
-rw------- 1 root root 4096 May 28 14:31 load_detect_test
-r-------- 1 root root 4096 May 28 14:31 lvds_channel_mode
-rw------- 1 root root 4096 May 28 14:31 lvds_use_ssc
-rw------- 1 root root 4096 May 28 14:31 mmio_debug
-r-------- 1 root root 4096 May 28 14:31 modeset
-r-------- 1 root root 4096 May 28 14:31 nuclear_pageflip
-rw------- 1 root root 4096 May 28 14:31 panel_ignore_lid
-rw------- 1 root root 4096 May 28 14:31 prefault_disable
-rw------- 1 root root 4096 May 28 14:31 reset
-r-------- 1 root root 4096 May 28 14:31 semaphores
-rw------- 1 root root 4096 May 28 14:31 use_mmio_flip
-r-------- 1 root root 4096 May 28 14:31 vbt_sdvo_panel_type
-rw------- 1 root root 4096 May 28 14:31 verbose_state_checks

Doing
echo /sys/module/i915/parameters/enable_rc6
will show what enable_rc6 is set at, and
echo -n 0 > /sys/module/i915/parameters/enable_rc6
*might* even change it until your next boot up.

If the above doesn't work we'll discuss making changes in how modprobe works for the i915 driver, if that is the driver being used.

**edugs** · May 28, 2018, 03:21 PM

Thanks guys, I think it has been fixed with a linux-firmware update...

I am not sure...

I have dual boot with Windows 10...

Thank you so much.

**claydoh** · May 28, 2018, 05:51 PM

This is a Bay Trail Atom processor/System-on-a-Chip, which is well-known to freeze, and I do not know if has been fixed or not yet, but it is possible with a new Intel microcode update - check your driver manager in System Settings to see if it in use.

If you get freezes again, you will have to modify your grub config as a work around:
https://askubuntu.com/questions/8036...ntel-bay-trail

**edugs** · May 29, 2018, 01:33 AM

Originally posted by claydoh View Post

This is a Bay Trail Atom processor/System-on-a-Chip, which is well-known to freeze, and I do not know if has been fixed or not yet, but it is possible with a new Intel microcode update - check your driver manager in System Settings to see if it in use.

If you get freezes again, you will have to modify your grub config as a work around:
https://askubuntu.com/questions/8036...ntel-bay-trail

Thank you so much.

I read that the problem is with dual boot with Windows 10...

Yesterday it don't freezed after and update. I will see today...

**claydoh** · May 29, 2018, 01:47 PM

Originally posted by edugs View Post

Thank you so much.

I read that the problem is with dual boot with Windows 10...

Yesterday it don't freezed after and update. I will see today...

It has nothing to do with dual booting, it is that Intel does not offer or help much with Linux support on this specific hardware, where everything in on one chip. The kernel developers and hackers have to find and fix issues like this on their own, and it has been slow going but with success. Hopefully your update does fix this permanently. I have had a number of similar devices, and have had to jump through enough hoops that I have given up. I do have one left, might give it a go if I get bored enough.

**edugs** · May 29, 2018, 02:06 PM

Hello guys, thank you for the interes, this is a great community.

After longtime, I had the problem again. The system freezed when I thought that it was fixed.

Reading your post i did the follow:

Edit the line of the next file:

Code:

vim /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"

I tried the next command, but in spite of to be root, i can't did it. It said permission denied.

Code:

echo -n 0 > /sys/module/i915/parameters/enable_rc6

And

Code:

apt remove thermald

I will tell you how i go.

Thank you so much.

**claydoh** · May 29, 2018, 02:21 PM

Use sudo, you don't have to be root for this, do it as normal user, and do exactly as the first answer on the page says:

Code:

sudo nano /etc/default/grub

, etc

You can ignore all other answers and comments on this page, just follow the steps in the first answer only.

You can use any editor you choose of course, but likely even being root (BAAAD BAD BAD) you probably still need to use sudo.

There is a simple workaround for this until it gets properly fixed upstream.
You just need to pass a kernel boot parameter and the random freezing stops completely. The parameter may increase battery consumption slightly, but it will give you a usable system.

You do this by editing the configuration file for GRUB:

Boot Ubuntu and open a terminal by pressing Ctrl+Alt+T then type

Code:

sudo nano /etc/default/grub

Find the line that starts GRUB_CMDLINE_LINUX_DEFAULT=

This needs to be changed to include intel_idle.max_cstate=1

So after your edit it reads something like

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1"
quiet and splash are default parameters for Ubuntu Desktop - no need to change them, or any other pre-existing parameters

Now save the file by pressing ctrl+o then enter and exit by pressing ctrl+x

Now run

Code:

sudo update-grub

Then reboot.

**edugs** · May 29, 2018, 02:28 PM

Thank you claydoh

I did everything that you say. ( I am testing)

I just can't do the follow command:

Code:

echo -n 0 > /sys/module/i915/parameters/enable_rc6

**GreyGeek** · May 29, 2018, 03:18 PM

Originally posted by edugs View Post

Thank you claydoh

I did everything that you say. ( I am testing)

I just can't do the follow command:

Code:

echo -n 0 > /sys/module/i915/parameters/enable_rc6

That’s because the /sys dir is owned by root and you need to use sudo in front of it to execute that command. My fault for assuming you knew that.

**claydoh** · May 29, 2018, 04:22 PM

Originally posted by edugs View Post

Thank you claydoh

I did everything that you say. ( I am testing)

I just can't do the follow command:

Code:

echo -n 0 > /sys/module/i915/parameters/enable_rc6

Why do you need to do this, and where did you find the advice?
~~The file "/sys/module/i915/parameters/enable_rc6" may not be present, so the error is to be expected, as you can't write to something not there.~~
See y next comment, below.

**claydoh** · May 29, 2018, 04:42 PM

Originally posted by GreyGeek View Post

That’s because the /sys dir is owned by root and you need to use sudo in front of it to execute that command. My fault for assuming you knew that.

No, it is because the files in /sys/ are red-only, and only for the root user, so no one can write to it, if it is present.

Code:

ls -la /sys/module/i915/parameters/ | grep rc6
-r-------- 1 root root 4096 May 29 18:33 enable_rc6

Likely this needs to be set in grub somewhere, but I think this tweak may not be necessary in newer kernels, such as in 18.04

Announcement

Random crashes, system freezes

Random crashes, system freezes

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment