Announcement

Collapse
No announcement yet.

Feisty strange behavior

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Feisty strange behavior

    Ever since I upgraded my laptop from Dapper to Feisty, my laptop has been acting very strange. Sometimes I will click on something and absolutely nothing happens. Sometimes I will run a program and it will start and then it will just sit there. When I click on the K menu and click log out, when the screen is supposed to turn black and white in the background slowly, it will just sit there with part of the screen black and white, but the very strange part is that when I move the mouse it will turn more of the screen black and white but when I stop moving the mouse it will stop again.

    I am running feisty on another laptop and a desktop computer and they are both working fine, but I can't figure out why this laptop acts this way. I have even tried installing feisty from scratch without upgrading.

    The only difference between this laptop and the two computers that are running fine that I can figure is that the laptop that is acting crazy has a hyper threading processor.

    Does anyone know what is causing this and/or how to fix it?
    Tags: None
    • Top
    • Bottom
    #2
    Re: Feisty strange behavior

    Well, we're kind of in the same boat: I've upgraded from Dapper to Feisty, and now also have problems! Can you have a look in the logfiles to see if there is anything untoward?
    • Top
    • Bottom

    Comment

      #3
      Re: Feisty strange behavior

      Just a shot in the dark here:

      Please let us know the specs of the problem machine ie
      processors
      Graphics Cards etc.
      Also, can you say what kernel version including type (generic/386 etc) you are running and whether you have the restricted kernel; modules installed?

      Ian
      • Top
      • Bottom

      Comment

        #4
        Re: Feisty strange behavior

        My Kernel Version is: 2.6.20-16-generic
        Processor: Hyper-threaded 3.46 GHz Mobile Pentium 4 processor with 533 MHz front-side bus and 1 MB L2 cache
        Graphics Card: ATI Radeon 9100
        Other specs can be found on the following laptop review page:
        http://www.mobilewhack.com/reviews/t...noteboook.html
        • Top
        • Bottom

        Comment

          #5
          Re: Feisty strange behavior

          I thought I posted here...
          Anyway, I bet it's an interrupt conflict. Try adding "irqpoll" to your kernel line when booting.
          For external use only.
          • Top
          • Bottom

          Comment

            #6
            Re: Feisty strange behavior

            I Appreciate the suggestion but irqpoll does not seem to have helped....
            • Top
            • Bottom

            Comment

              #7
              Re: Feisty strange behavior

              Seems like it could be graphics related. Try this:

              Start kubuntu in rescue mode

              At the prompt type dpkg-reconfigure xserver-xorg

              Hit Return

              Most folks seem to recommend selecting the option VESA (which I think is the generic option) during the configuration process. What this does is reconfigure the x server. It seems to be a common problem when installing kubuntu - sometimes people don't get to login to kde at all until doing this.

              Type startx and kde should then load (hopefully without fault!)

              Any joy?

              Ian

              • Top
              • Bottom

              Comment

                #8
                Re: Feisty strange behavior

                The Liquidator:

                I tried what you said, but when using the vesa driver, x wouldn't even start up. Thanks for the suggestion, but the open-source ati driver is the only one that I tried that seems to work. It would be nice if I could get the proprietary ati driver to work, and supposedly it should have 2D support for my graphics card, but x "cant find any screens" when I try that.

                You might be on the right track though, It seems that the system only becomes non-responsive when I'm running x, so maybe it does have something to do with the graphics driver...

                I think maybe I'll install gnome and see if that becomes non-responsive too. That way I can find out if it is a KDE problem or not...
                • Top
                • Bottom

                Comment

                  #9
                  Re: Feisty strange behavior

                  You could also run adept and make sure that you have all xorg packages relevant to ATi installed.

                  Ian
                  • Top
                  • Bottom

                  Comment

                    #10
                    Re: Feisty strange behavior

                    I just ran the ubuntu (gnome-based) feisty live CD, and it did the same thing. I still don't have a clue what is wrong but at least I know the problem is not strictly a KDE problem.
                    • Top
                    • Bottom

                    Comment

                      #11
                      Re: Feisty strange behavior

                      Please post the contents of /etc/X11/xorg.conf this may be helpful in figuring out your problem.

                      But off the top of my head without seeing the file check the following and see if you have something similar under the device section for your ATI device.

                      Section "Device"
                      Identifier "ATI RADEON 9100"
                      Driver "radeon"
                      BusID "PCI:1:0:0" #check this with lspci and enter correct value
                      Option "XAANoOffscreenPixmaps"
                      Option "AGPMode" "4"
                      Option "AGPFastWrite" "true"
                      Option "DisableGLXRootClipping" "true"
                      Option "AddARGBGLXVisuals" "true"
                      Option "AllowGLXWithComposite" "true"
                      Option "EnablePageFlip" "true"
                      EndSection

                      Section "Screen"
                      Identifier "Default Screen"
                      Device "ATI RADEON 9100"
                      Monitor "Standardbildschirm" # change this to the monitor in your file
                      # Option "HWcursor" "On" # This prevents the flickering and incorrect redrawing of the mouse
                      # Option "AddARGBGLXVisuals" "True"
                      DefaultDepth 24
                      SubSection "Display"
                      Depth 1
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      SubSection "Display"
                      Depth 4
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      SubSection "Display"
                      Depth 8
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      SubSection "Display"
                      Depth 15
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      SubSection "Display"
                      Depth 16
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      SubSection "Display"
                      Depth 24
                      Modes "1280x1024" "1024x768" "800x600" "640x480"
                      EndSubSection
                      EndSection

                      Section "Extensions"
                      Option "Composite" "Enable"
                      EndSection


                      and under Section "ServerLayout" add

                      Option "AIGLX" "true"

                      This may help you and it may not. If it does give thanks to Fintan for posting this information before when I had some problems with an ATI 9250 card.

                      You may also want to try uncommenting one or both of the options:
                      Option "HWcursor" "On" # This prevents the flickering and incorrect redrawing of the mouse
                      Option "AddARGBGLXVisuals" "True"

                      under the screen section.
                      • Top
                      • Bottom

                      Comment

                        #12
                        Re: Feisty strange behavior

                        Just before x would start I would notice this error: MP-BIOS bug: 8254 timer not connected to IO-APIC

                        I found the following thread: http://ubuntuforums.org/showthread.php?t=191355

                        and followed the directions:

                        I turned off APIC by editing /boot/grub/menu.lst

                        and adding 'noapic' to the end of the line that starts out "# defoptions="...

                        Then I ran update-grub and rebooted and so far that seems to have fixed the entire strange behavior/non-responsiveness problem
                        • Top
                        • Bottom

                        Comment

                          #13
                          Re: Feisty strange behavior

                          Hm. Mine gave the same error, but I didn't notice any problems at all.
                          For external use only.
                          • Top
                          • Bottom

                          Comment

                          Previous template Next
                          Working...
                          X