Announcement

Collapse
No announcement yet.

Intel GMA915 and severe Screen Flicker

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

    #61
    Re: Intel GMA915 and severe Screen Flicker

    updated, upgraded, rebooted, still flickers.

    It takes about 10 to 15 keystrokes after rebooting until the skinny 3cm black bands start forming in a random position vertically.

    xorg.log

    (WW) Failed to open protocol names file /etc/X11/xserver/protocol.txt
    X.Org X Server 1.5.1
    Release Date: 23 September 2008
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
    Current Operating System: Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686
    Build Date: 10 October 2008 11:01:44AM
    xorg-server 2:1.5.1-1ubuntu3 (buildd@rothera.buildd)
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 11 16:12:27 2008


    Question. I have been on i386 path forever with this celeron 2.4 ghz. This was an upgrade (fresh install with gutsy). So why would my Curr Oper Sys be listed as 2.6.27-7-generic #1 SMP I don't believe I should be smp

    BTW, I was wrong I am intel sis650 not 810 I liked the gui hardware detection programs in 3.5 better - could find them easier. I am reverting back to using cpuid, lshw, etc.

    (entire screen went black again twice there maybe 500ms)

    more log

    (II) Loading /usr/lib/xorg/modules/drivers//sis_drv.so
    (II) Module sis: vendor="X.Org Foundation"
    compiled for 1.5.0, module version = 0.10.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 4.1
    (II) SIS: driver for SiS chipsets: SIS5597/5598, SIS530/620,
    SIS6326/AGP/DVD, SIS300/305, SIS630/730, SIS540, SIS315, SIS315H,
    SIS315PRO/E, SIS550, SIS650/M650/651/740, SIS330(Xabre),
    SIS660/[M]661[F|M]X/[M]670/[M]741[GX]/[M]760[GX]/[M]761[GX]/[M]770[GX],
    SIS340
    (II) SIS: driver for XGI chipsets: Volari Z7 (XG20),
    Volari V3XT/V5/V8/Duo (XG40)
    (II) Primary Device is: PCI 01@00:00:0
    (WW) Falling back to old probe method for sis
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:0:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:1:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:1) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:5) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:6) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:7) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:1) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:2) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:4:0) found
    (--) Assigning device section with no busID to primary device
    (--) Chipset SIS650/M650/651/740 found
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
    [4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]


    NOTE: I am guessing that it can't find a pci/agp address as the chip in hardwired onto the mobo

    snippets of kdm log

    WW) SIS: No matching Device section for instance (BusID PCI:0@0:0:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:1:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:1) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:5) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:6) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:2:7) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:0) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:1) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:3:2) found
    (WW) SIS: No matching Device section for instance (BusID PCI:0@0:4:0) found
    kdmgreet(5048) KLocalePrivate::initEncoding: Cannot resolve system encoding, defaulting to ISO 8859-1.

    Problems finding the on mobo video??

    and

    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""
    > Using last definition
    > Warning: Duplicate shape name ""


    I changed from the more propriertary IBM keyboard to a standard LOgitech. Still flashes when I type.

    I will be shutting this puter down and going back to the other one. Try again tomorrow.

    Comment


      #62
      Re: Intel GMA915 and severe Screen Flicker

      Well...more updates and still have the flicker.

      A lot of KDM, KWIN and X in that update this morning, but evidently nothing to address this issue. Dumped Gnome on here and went back to KDE. I just like KDE4 way better. Just sad that it flickers like this. This laptop looks sooooo good running KDE4.

      Comment


        #63
        Re: Intel GMA915 and severe Screen Flicker

        I've found if you kill the kded4 process then the flickering stops. I don't know what kded4 does but my keyboard shortcuts have stopped working. Everything else seems OK.

        Edit:
        I couldn't find anything on kded4 but looked up kded and saw it's the kde deamon so know I know.
        I guess it is one of the services it's running that's causing the problem.

        Comment


          #64
          Re: Intel GMA915 and severe Screen Flicker

          OMG...you're right. No flickering!!! You're also right about the Keyboard shortcuts. Have you added this to those bug reports?

          Comment


            #65
            Re: Intel GMA915 and severe Screen Flicker

            Ok I've got further.
            The only problem is the Detecting RANDR (Monitor) changes service. If you turn that off in services in system settings the flickering stops and kded4 can still be run.

            Comment


              #66
              Re: Intel GMA915 and severe Screen Flicker

              Yep... Verified here. Thanks! I'll verify what you wrote on the Bug Report.

              Comment


                #67
                Re: Intel GMA915 and severe Screen Flicker

                No luck for me my screen problems with stopping RANDR service. I have not restarted however.

                Maybe I have a different bug. The tiny narrow bands that last maybe 100 ms have increased in length from 3 cm to now extending to all but a few mm from the right screen edge now. It is almost "trippy" when deleting text with the backspace and each letter or space deleted sets off another band.

                However, the screen has not gone to black for maybe 200 ms after scrolling with mouse on Opera, Firefox, or konsole.

                I will file a new bug report instead of my previous appending my observations to others.

                It is slow even with effects turned off on this 2.4 ghz celeron. I will be trying lenny - kde for this older computer. KDE3.5.9. kernel 2.6.26, a very recent apt, etc.

                I see that moonrise has similar hardware (intel gma 3100. 2.2 ghz intel dualcore, etc.) to my newer computer. I turned on Hardy backports for it and will stick with hardy till the new year on it.

                Comment


                  #68
                  Re: Intel GMA915 and severe Screen Flicker

                  Yes! Finally!

                  ilowman4president

                  Comment


                    #69
                    Re: Intel GMA915 and severe Screen Flicker

                    My 'flicker' problem disappeared following the most recent updates but as I mentioned before it was more of a constant on-screen noise rather than a flicker so I am not sure if the 2 are related.
                    Kubuntu 20.04(AMD64)/KDE 5

                    Comment


                      #70
                      Re: Intel GMA915 and severe Screen Flicker

                      Originally posted by AdamTomlins
                      Yes! Finally!

                      ilowman4president
                      I'll second that!

                      Flicker gone now, apart from when going through the KDE 4.1 splash screen. I also recall that I had earlier seen messages to the effect that RANDR had crashed.

                      Oddly enough I was starting to get used to gnome!

                      Comment


                        #71
                        Re: Intel GMA915 and severe Screen Flicker

                        I fought real hard to stay with KDE4. This helps. Still flickers at initial log in, but now way more usable.

                        Comment


                          #72
                          Re: Intel GMA915 and severe Screen Flicker

                          I gave up. I could not stand the black skinny lines appearing for every keystroke. I did not file new bug report because I can not reproduce it. I wiped / /var and /tmp.

                          lenny-kde went on very easily, rock solid video, and it is ever so much faster. It really breathed new life into a five year old computer. My faster machine is still running kubuntu.

                          Comment


                            #73
                            Re: Intel GMA915 and severe Screen Flicker

                            Originally posted by paxmark1
                            I gave up. I could not stand the black skinny lines appearing for every keystroke. I did not file new bug report because I can not reproduce it. I wiped / /var and /tmp.
                            It's still a beta release.....this message is posted on the Kubuntu site:

                            NOTE: This is a beta release. Pre-release versions of Intrepid are NOT encouraged for anyone needing a stable system or for anyone who is not comfortable running into occasional, even frequent, breakage. Pre-release versions of Intrepid ARE recommended for Kubuntu developers and those who want to help in testing, reporting, and fixing bugs.

                            Hopefully you'll come back when the official release comes out but don't let a beta spoil your opinion of KDE4 on Kubuntu!
                            Kubuntu 20.04(AMD64)/KDE 5

                            Comment


                              #74
                              Re: Intel GMA915 and severe Screen Flicker

                              I had the same problem and resolved it by stopping the RANDR process too. I also have the "minimal" xorg.conf and have a booting problem. Is there any definitive answer regarding the status of xorg.conf? Is it used or not?
                              Let&#39;s disconnect these cables, Overturn these tables, <br />This place don&#39;t make sense to me no more<br />Can you tell me what we&#39;re waiting for, Señor?: Bob Dylan<br />Registered Ubuntu User # 23094

                              Comment


                                #75
                                Re: Intel GMA915 and severe Screen Flicker

                                Well what I have fount is that it is a xrandr problem.

                                What I did is that I did a xrandr --output "monitor" --off on all the monitors I was not using. And the flickering went away.

                                This means though that there is no dualscreen possibility's as of yet in this release, until this issue is addressed.

                                Comment

                                Working...
                                X