Announcement

Collapse
No announcement yet.

Problem with graphics - maybe GPU related?

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

    Problem with graphics - maybe GPU related?

    What release of Kubuntu you are using. 11.04
    What version of KDE you are using. Platform Version 4.6.2 (4.6.2)
    What version of Grub you are using. GRand Unified Bootloader (Legacy version)
    What other Operating Systems are installed. Windows 7 (Dual Booted)

    Information about your PC:
    Type Desktop
    CPU Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz
    GPU Intel Corporation Core Processor Integrated Graphics Controller (rev 12)
    RAM 4Gb
    HDs All internal SATA drives
    Optical Drives 1 internal DVD/RW drive
    Audio:
    HDA Intel (ALC887 Digital)
    Audio:
    HDA Intel (ALC887 Analog)
    Audio:
    ALSA Timer Device
    Audio:
    ALSA Sequencer Device
    Audio:
    CS50/CS60-USB Headset
    Audio:
    CS50/CS60-USB Headset (USB Audio)
    Audio:
    HDA Intel(HDA Intel ALSA hardware specific Device)
    Audio:
    HDA Intel
    Audio:
    USB Speaker
    Audio:
    USB Speaker (USB Audio)
    Audio:
    HDA Intel (HDMI 0)
    Network:
    Loopback device Interface
    Network:
    RTL8111/8168B PCI Express Gigabit Ethernet controller

    Hi all, Linux noobie here. Getting to grips with Kubuntu now and using it as my main work machine but have one extremely frustrating issue which has been happening for quite some time. I recently upgraded to 11.04 but the issue remains. I think it's a GPU overload/crash but randomly (and I really mean randomly - happens when in use, and when idle .. when moving a cursor or when opening programmes or just doing boring stuff like typing) the screen gets 'corrupted' - by this I mean goes black, with green and other coloured vertical stripes, and then black. The monitor light is still on, and there is no 'disconnected' message.

    To resolve this I simply switch the monitor off and on again (that age old trick!) but it's getting a bit annoying as it's happening quite often.

    I've tried checking out the system logs and can't see anything obvious which would match up with the times when it has occurred. I've done a few other bits of troubleshooting like closing everything down and it still happens. It also happens when I'm in the middle of something (three times since I started writing this paragraph). I wondered if it might be driver related, but not sure where to start.

    I'm not sure what to do further than this to track down the nature of the problem, any suggestions would be great. Please remember I am fairly new to command line and linux so please don't assume I know how to do things (but I'm not completely thick!) .... fisher price step-by-step style would be handy.

    Thanks in advance!

    Ruth

    EDIT: This might be relating to the fact that I have the Gigabyte GA-H55M-S2H motherboard with an i3 processor - something about the graphics being done on the processor? Wonder if this might be a contributory factor.

    #2
    Re: Problem with graphics - maybe GPU related?

    Generally, if nothing is being logged that usually points to a hardware malfunction rather than a software one. You said this problem is an old one - so what's the history?

    I hate to be obvious here - but start with checking all the connections and when possible, swap out with another computer.

    Another good way to test would be to get a liveCD of a totally different distro and see if it happens while running that one.

    Assuming it is a software issue - look at the file named /var/log/Xorg.0.log and one named /home/<yourusername>/.xsession-errors

    Since you admit to being totally new with linux: a file with a period as the first letter indicates it is a hidden file. So to see the .xsession-errors file, open dolphin (file manager), it likely will default to your home directory - but if not navigate there, then select "Show hidden files" in the view menu.

    Most logs files are sequential text files so drop down to the end and read up.

    Oh, and Welcome to KFN and thanks for taking the time to make your first post informative.

    Please Read Me

    Comment


      #3
      Re: Problem with graphics - maybe GPU related?

      Thanks for the response, and yes it does sound hardware related. It doesn't happen with Windows and there can be quite lengthy periods where it doesn't do it at all in Kububtu, which is why it's a bit of a mystery to me as to what's wrong .. I can't even pin down what might be causing it to start happening.

      I had the same monitor running off a Windows 7 laptop for about 8 hours at a conference a few weeks ago and it didn't once switch off or do anything strange (having previously been doing the aforementioned stuff for some weeks previous).

      I checked out the log as part of the troubleshooting (found it suggested elsewhere) but couldn't see anything that tied in with the occurences, will post the results tomorrow when I get back into the office, didn't get as far as the errors file you suggest so will look at that also!

      Ruth

      Comment


        #4
        Re: Problem with graphics - maybe GPU related?

        Finally got around to checking out that log file, but not sure what I am looking for. Does this make any sense (it appears an awful lot in the .xsession-errors logs and seems to coincide with the symptoms I am getting (the file is being updated each time my monitor goes wonky):

        Code:
        [/usr/bin/nepomukservicestub] virtual void Soprano::Server::LocalServer::incomingConnection(quintptr)
        [/usr/bin/nepomukservicestub] void Soprano::Server::ServerCorePrivate::addConnection(Soprano::Server::ServerConnection*) New connection. New count: 9
        [/usr/bin/nepomukservicestub] Soprano::ODBC::Connection::Connection() Soprano::Server::ServerConnection(0x7ff400006f10)
        [/usr/bin/nepomukservicestub] virtual void Soprano::Server::ServerConnection::run() thread done.
        [/usr/bin/nepomukservicestub] virtual Soprano::ODBC::Connection::~Connection() Soprano::Server::ServerConnection(0x7ff400006f10)
        [/usr/bin/nepomukservicestub] void Soprano::Server::ServerCore::serverConnectionFinished() 
        virtual Soprano::Server::ServerConnection::~ServerConnection() Removing connection
        [/usr/bin/nepomukservicestub] void Soprano::Server::ServerCore::serverConnectionFinished() Connection removed. Current count: 8
        Ruth

        Comment


          #5
          Re: Problem with graphics - maybe GPU related?

          seems odd to me that nepomuk would be crashing X but it's possible.

          Go into System Settings and turn off, I think it's in Desktop (not at my linux box right now).

          Also, make sure you're fully updated. There are a couple strigi and soprano bugs floating around.

          Please Read Me

          Comment


            #6
            Re: Problem with graphics - maybe GPU related?

            Disabled & restarted but still got the problem.

            It seems to happen whenever anything graphical is being done - alt tabbing between windows for example, or a window opening. It is also, however, happening when the system is idle - so I'm typing this on my laptop at the moment and the screen just went off with nothing open (just the desktop).

            It's happening every few minutes now, making the system virtually un-useable from a commercial point of view as I'm constantly having to switch my monitor off and on again!

            Would it help to post the entire log (and is it sensible to do so?)

            Ruth

            Comment


              #7
              Re: Problem with graphics - maybe GPU related?

              You may need to change compositing type to xrender and/or turning off direct rendering.
              ASROCK Z87 Pro4 - i5 4670K - R9 270x ☞ Triple Boot: KDE NEON ★ Windows 10 ★ Windows 7

              Comment


                #8
                Re: Problem with graphics - maybe GPU related?

                So, given my above admission of being new to linux, would you care to translate that from Martian into plain english, with a 'how to'? Thanks for the suggestion but I am clueless as to how to proceed.

                Ruth

                Comment


                  #9
                  Re: Problem with graphics - maybe GPU related?

                  think I figured out some of it.

                  Turning off direct rendering - crashed kwin several times but eventually was able to set it, no change.

                  Changing from OpenGL to xrender crashed kwin several times, gave error messages about desktop effects, and wouldn't let me change it at all.

                  Disabling desktop effects - no change, still getting monitor switching off.

                  Ruth

                  Comment


                    #10
                    Re: Problem with graphics - maybe GPU related?

                    What does the output of dmesg give right after a crash?

                    Please Read Me

                    Comment


                      #11
                      Re: Problem with graphics - maybe GPU related?

                      Assuming I just type that into Konsole (again, not entirely sure what your instructions were so had to guess)

                      Code:
                      [ 6880.524537] end_request: I/O error, dev sr0, sector 64
                      [ 6880.526624] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 6880.526630] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 6880.526636] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 6880.526643] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 11 00 00 01 00
                      [ 6880.526654] end_request: I/O error, dev sr0, sector 68
                      [ 6880.581577] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 6880.581585] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 6880.581591] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 6880.581600] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00
                      [ 6880.581612] end_request: I/O error, dev sr0, sector 64
                      [ 6880.583619] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 6880.583625] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 6880.583631] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 6880.583638] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 01 00
                      [ 6880.583649] end_request: I/O error, dev sr0, sector 64
                      [ 6880.585559] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 6880.585565] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 6880.585571] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 6880.585578] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 11 00 00 01 00
                      [ 6880.585589] end_request: I/O error, dev sr0, sector 68
                      [ 7054.195443] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 7054.195451] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 7054.195459] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 7054.195468] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00
                      [ 7054.195480] end_request: I/O error, dev sr0, sector 64
                      [ 7054.195485] quiet_error: 46 callbacks suppressed
                      [ 7054.195489] Buffer I/O error on device sr0, logical block 16
                      [ 7054.195494] Buffer I/O error on device sr0, logical block 17
                      [ 7054.197521] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                      [ 7054.197526] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] 
                      [ 7054.197532] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track
                      [ 7054.197539] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 10 00 00 02 00
                      [ 7054.197550] end_request: I/O error, dev sr0, sector 64
                      [ 7054.197554] Buffer I/O error on device sr0, logical block 16
                      [ 7054.197558] Buffer I/O error on device sr0, logical block 17

                      Comment

                      Working...
                      X