crouton: Probably to do with xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

@fermionic note that the config file according to your output is in

(==) Using system config directory "/usr/share/X11/xorg.conf.d"

Happy holidays to everyone who posted on this thread! On my son’s new Acer Chromebook R13, I was able to successfully setup Steam and Minecraft using Crouton and KDE thanks to the adding this file (as mentioned before) to the chroot for ‘trusty’:

/usr/share/X11/xord-conf.d/20-crouton.conf

Section “Device” Identifier “Intel Graphics SNA+TearFree” Driver “intel” Option “AccelMethod” “uxa” EndSection

–

Only remaining issues to figure out are why the mouse is ridiculously laggy 😃

I tried copying the file /etc/crouton/xorg-intel-sna.conf (containing @rtpavlovsk21’s edits) over to /usr/share/X11/xorg.conf.d/20-crouton.conf (which didn’t exist before) and that allowed me to get into XFCE

@JimAmuro It is said on #2923 that update of crouton could fix the problem now. I tried, and it really works! Though days ago it still did not work… And now I can enter i3wm/xfce/lxde on trusty with the option “sna” without any problem.

The issue as I currently see this: Intel Celeron Chromebooks (tested Acer 720p/Samsung Chromebook 3/Acer Chromebook 14) work (probably without acceleration) with changes in comment #2926. See #2917 for a longer discussion. ARM Chromebooks (tested by @AntiochInteractiveMedia on CB Acer R13, see #2926 comment )

There are exceptions listed to this (as I read them in this thread). A partial list of exceptions that need to be investigated further: Acer CB R11 (1 instance) Toshiba CB 2 (1 instance) - This case has an ambiguity between i3/Celeron Asus C300 (1 instance) - Ambiguity between Atom/Celeron and probably uses #2926 comment as the fix.

Also a great suggestion for Celeron HW Acceleration from @pmarkkula. I have tested this on both Acer 720p and Samsung CB 3.

On Acer c720p. With the xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) issue.

The following have not worked: @AntiochInteractiveMedia 's fix: https://github.com/dnschneid/crouton/issues/2926#issuecomment-269165182

This did not work because the file “20-crouton.conf” isn’t referenced, so changing it does nothing. Then someone suggested “20-crouton-intel-sna-conf” which is actually just a symlink to “/etc/crouton/xorg-intel-sna.conf”.

And HALLELUJAH PRAISE JESUS IT WORKED.

In other words, change

/mnt/stateful_partition/crouton/chroots/test2/etc/crouton/xorg-intel-sna.conf

to

# Copyright (c) 2016 The crouton Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

# On Intel platforms with FBC enabled, in order to see anything we need to use
# the SNA driver with the TearFree option.
Section "Device"
   #Identifier "Intel Graphics SNA+TearFree"
   #Driver     "intel"
   # Option     "AccelMethod" "uxa"
   # Option     "TearFree"    "true"
   Identifier "Modesetting"
   Driver "modesetting"
   Option "AccelMethod" "sna"
   Option "TearFree" "true"
EndSection

Keep in mind, depending on your system, it might be /mnt/stateful_partition/crouton/chroots/test2/usr/share/X11/xorg.conf.d/20-crouton.conf That you have to modify, OR /mnt/stateful_partition/crouton/chroots/test2/usr/share/X11/xorg.conf.d/20-crouton-intel-sna.conf but that last file is actually just a symbolic link to /mnt/stateful_partition/crouton/chroots/test2/etc/crouton/xorg-intel-sna.conf

On my Acer Chromebook 14 (CB3-431), I also found the “uxa” driver to work better. The “modesetting” one worked fine, except that it was obviously unaccelerated, so games like Minetest didn’t work very well. Changing the xorg conf file to what @yannym has allowed me to boot into XFCE with hardware acceleration–in fact, so far I’ve seen no difference between “uxa” and what “sna” was before the ChromeOS update

@rtpavlovsk21 I’m using a Lenovo Thinkpad 13, the “modesetting” drivers worked fine for me, it fixed the black screen issue I was having when attempting to enter the xfce environment using xorg, but I kinda needed hardware acceleration, and the “uxa” “Accel Method” works great for me, it starts xfce and has no issues I can see so far. It may be because I have Skylake hardware.

I attempted to use uxa plus modesetting but I saw now change there between sna or uxa, it was only after I reverted to the intel driver that it started to work, so I think sna might be the issue, because that’s what I had configured when the black screen was occuring, “intel” + “sna.” “intel” + “uxa” seemed to fix it.

This discussion was carried over from #2917 because the xf86EnableIOPorts error is more likely the issue it fixes. The issue I had was that on startlxde crouton would boot to what looked like an unlit black screen. Making these changes along with the edits fixed my issues on my Acer 720p:

After reading “man intel” I discovered that both the intel driver and modesetting driver implement common hardware acceleration parameters:

Section "Device"                                                                                                                                     
#   Identifier "Intel Graphics SNA+TearFree"                                                                         
#   Option     "AccelMethod" "sna"                                                                                                                   
#   Option     "TearFree"    "true"                                                                                                        
   Identifier "Modesetting"                                                                                                                
   Driver     "modesetting"
   Option "AccelMethod" "sna"
   Option "TearFree" "true"                                                                                                                  
EndSection     

These edits significantly reduce the number of artifacts and screen switching problems that i have seen. I have not observed crashes from switching, but previously modesetting was a step down from the intel driver. With the changes I don’t notice a difference in performance or appearance to how crouton use to work.

I will be getting a Samsung Chromebook 3 in the next few days and will note any obvious differences (I would have liked to had another processor series to test on but this will also be a celeron).

https://www.chromebookchart.com/

I’ve seen what I believe is this same issue, it was posted on Crouton Central here:

did google break crouton with latest update?.

At first, I thought it was due to some problems with the ‘precise’ release but the OP tried both ‘trusty’ & ‘xenial’ to no avail. Then I thought it might have been a problem with the ‘xfce4’ target but the OP tried ‘lxde’ and still the same black screen.

The only suggestion that I offered that worked was switching to the ‘xiwi’ xmethod but that has no hardware acceleration so it’s not a perfect solution.

Hopefully the devs can figure this out soon’ish, whenever they get some spare cycles…

Hope this helps, -DennisL