Results 1 to 4 of 4

Thread: "gma500 trying to get vblank count for disabled pipe" boot time error message

  1. #1

    Default "gma500 trying to get vblank count for disabled pipe" boot time error message

    Hi,

    I have an Asus Eee netbook PC with opensuse 13.1 on it.

    During boot time I always get this strange vblank message, which means nothing to me,
    except I assume it's something to do with the gma500 video driver.

    The PC still boots and the OS seems to work fine apart from that.

    I googled the error, and it came up with a kernel patch link:

    https://build.opensuse.org/package/v...1a41705a996269

    but I don't really want to start fiddling around with kernel patches if at all possible,
    as I have no experience of using them.

    Does anyone have any other solutions, or know what this error means?

    Thanks

  2. #2

    Default Re: "gma500 trying to get vblank count for disabled pipe" boot time error message

    Quote Originally Posted by Wild_Goose View Post
    During boot time I always get this strange vblank message, which means nothing to me,
    except I assume it's something to do with the gma500 video driver.

    The PC still boots and the OS seems to work fine apart from that.

    I googled the error, and it came up with a kernel patch link:

    https://build.opensuse.org/package/v...1a41705a996269

    but I don't really want to start fiddling around with kernel patches if at all possible,
    as I have no experience of using them.

    Does anyone have any other solutions, or know what this error means?
    Well, that patch (it's for kernel 2.6.31) just turns that _error_ message into a debug message.
    In Kernel 3.11 this _is_ only a debug message anyway.
    The corresponding code there:
    Code:
                    DRM_DEBUG_DRIVER("trying to get vblank count for disabled "
                                     "pipe %c\n", pipe_name(pipe));
    The message seems to point to a possible "bug" or flaw in the intel driver, you might try the latest version from the X11:XOrg repo. (you have to do a Full repository Vendor change update to that repo though, as the driver from that repo will not work with the Xorg from openSUSE 13.1.

    But why do you care about this message at all, if everything is working as expected? Just ignore it in this case, it's only a debug message anyway.
    Last edited by wolfi323; 16-Mar-2014 at 12:33.

  3. #3

    Default Re: "gma500 trying to get vblank count for disabled pipe" boot time error message

    Hi! I know this was 2014, but i have the same problem now! Same computer, same problem, just that im stuck at that message.
    Please help

  4. #4

    Default Re: "gma500 trying to get vblank count for disabled pipe" boot time error message

    Quote Originally Posted by IdkBro View Post
    Hi! I know this was 2014, but i have the same problem now! Same computer, same problem, just that im stuck at that message.
    Please help
    Your system gets stuck after displaying that message?
    As already explained, this message should just be a warning.

    Your best bet would probably be a bug report at http://bugzilla.opensuse.org/.

    But what does "stuck" mean?
    Can you login to text mode after pressing Ctrl+Alt+F1?
    Last edited by wolfi323; 13-Dec-2016 at 09:56.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •