Announcement

Collapse
No announcement yet.

xf86EnableIOPorts: failed to set IOPL for I/O

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    xf86EnableIOPorts: failed to set IOPL for I/O

    Hi,

    After xorg updates from 31th May I'm getting such message when I try to run startx as user:

    Code:
    Fatal server error:
    xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
    same config works fine when I run it as root.
    It used to work before recent updates as well.

    I tried fglrx from dapper distribution and newest one from ATI webpage.

    Anyone know any solution to this one?

    Kind Regards

    #2
    Re: xf86EnableIOPorts: failed to set IOPL for I/O

    same config works fine when I run it as root.
    That implies that you've got some kind of permission problem. Is your user a member of the video group? Check /etc/group.

    Comment


      #3
      Re: xf86EnableIOPorts: failed to set IOPL for I/O

      Just did check again. Yes it is member of video group.
      It was working fine untill update from one day when it stoped working.

      And not working up to this day.

      Comment


        #4
        Re: xf86EnableIOPorts: failed to set IOPL for I/O

        Have you updated again since then and, if so, did that fix the problem?

        Changing the io permission level is a trick that the xserver uses to give normal users the right to perform i/o functions. That's why it worked when you logged in as root. I would expect that this kind of low level bug should have been fixed within a few days at most by the xorg people.

        Also, are you using an unusual driver for any of your input or output devices?

        Comment


          #5
          Re: xf86EnableIOPorts: failed to set IOPL for I/O

          Yes I update regulary so have recent Dapper packages.
          Maybe I will add some more information here.

          I use fglrx ATI driver (from ATI webpage not from Dapper package)
          But I was using the same before this particular update and it was working all right.

          All works good if i log from kdm (as user it is)

          Comment

          Working...
          X