Videocard issues in ML

Hi all
just upgraded to ML on my macbook pro 15 2010
and after booting i see that there is an issue with the videocard
it glitches so badly that i can barely see anything on the screen
stuff is rendered incorrectly and so on
something like this only the whole screen is affected and it's realy hard to see anything
http://forums.macrumors.com/attachment.php?attachmentid=295704&d=1311521842
or
http://i267.photobucket.com/albums/ii287/bac52/IMG_3339.jpg
tried resetting SMC - didn't help
any ideas?
thanks, James

I had so many problems with almost all the hardware on my MBP. 
Problem was solved by removing duplicate empty .kext files. I had so many of them, the machine took over 25min to boot!
No one at apple could help, all they could tell me was that the install was incorrect. Anyway, three TM restores and three ML upgrades, the exact same problem.
I used cocktail to put verbose mode on and I could see all of the 'empty' kext errors when booting, so i went into the extensions folder and started to take out all of the duplicated kext files.
This fixed 100% of all of my issues (no BT, no magic pad, no display resolutions, no usb, no firewire etc).
You can see all of the duplicates below.
After a reboot, everything was fixed, please do not attempt this unless you recognise the risks and you have a valid and TESTED TimeMachine backup!
Please use this information at your discretion.

Similar Messages

  • Videocard issues 21.5" iMac 2011

    my iMac 2011 21.5" intel powered,started. Of with pixels screen after monitor on sleep mode,then screen completely went blank,I've tried online help but wasnt useful at all,can i get it fixed without paying  as if heard that the 27"iMac had same videocard problems and apple offered a replacement parts program for this,hope you guys can help me with this issue

    Sorry man, an Ivy Bridge CPU will never work with an iMac the of that generation, I have heard that people are successful in swapping out the old Sandy Bridge CPU for a more powerful one of the same generation, such as the i7-2600 or something similiar.
    Put this into consideration before deciding if a cpu upgrade is worth the cost.
    However by all means purchase a RAM upgrade as mentioned by rkaufmann above.

  • Windows 7 x64 Pro, desktop GUI fails to display correctly, or crashes, when High RAM load, and even after. HW changed, same issue. Please Help.

    Hi Guys,
    I have have this horror issue with my PC. I have even changed the hardware configuration and the problem still persists. My PC fails to display the desktop correctly after using highly RAM intensive applications, especially Chrome, but even after getting
    the chance to close it, or waiting for it to crash by itself, the PC is still not able to display correctly the GUI, even on other browser/applications as shown in the screenshots. 
    1st Hardware Config:
    Intel Core2Quad Q9450
    4x2GB DDR2
    MSI P43 motherboard
    Ati Radeon x550 video card
    Software used, that seemed important for me to mention:
    NOD32 v4.2
    Comodo Firewall 5.12
    Chrome
    Screenshot Captor
    SpeedFan
    Other mentions:
    Aero is disabled, because I've considered that it's one of the causes.
    So, I've considered that it's a RAM issue or a videocard issue, and I've upgraded to:
    Intel Core i7 3770k
    4x8GB DDR3
    Asus P8Z77V-LX motherboard
    Intel GPU integrated in the 3770k CPU
    The problem just happened 2 times on this rig also, and the RAM was not even coming close to  it's maximum capacity of 31.7GB. It was at ~20GB's.
    Also, this is another videocard(Intel's integrated GPU), so we can exclude the videocard from the suspects.
    My suspects:
    1) some desktop manager bugs, or other similar issue
    2)  video memory allocation - I'm still suspecting that it can be caused by the amount of RAM dedicated to the videocard, currently, I think  that it is at 256MB.
    3) some poorly designed components of Chrome/Screenshot Captor - still very questionable since there are enough resources on this system, so there should be no fight over resources. And when the system is barely used there are no issues.
    4) Adobe Shockwave Flash - maybe this one????
    I have attached a set of 20 screenshots here, these were taken on the 1st configuration of my PC, using Q9450:
    http://imgur.com/a/Mc8hI#4
    Notice how it distorts the image by duplicating it and showing it in a smaller space, or how does it displays those black rectangles. In those moments, the PC is fully functional(the apps are running the background), without being slowish or something, but
    you can hardly control it like that. For example, I've tried to remove the mouse from the USB, and then I've insterted it back, the image was not displayed correctly, but the mouse was recognised instantly and the pointer was controlable.
    Same thing still happens on the new configuration. Please advise me.
    LE: OS is Windows 7 x64 SP1 Professional and it's Geniune. There is no cracked software on this PC. No games. I've tried to maintain it as clean as possible.

    Hi,
    First, please be ensured that you have installed the latest drivers and all the updates.
    Then check whether this issue will not in
    Safe Mode. If it didn’t occurred, I suggest you narrow down the cause in
    Clean Boot mode.
    In addition, try to create a new profile to see how it works.
    Hope this helps.
    Vincent Wang
    TechNet Community Support

  • MSI P35 Neo2-FR S3/USB Problems & Remote Desktop Video Problem

    I recently received a new board back from RMA (my old one wouldn't post at all) and decided to re-install Windows XP back on it after verifying that it was working, and now I'm having a few issues with the board that were fine and working with the old board.
    Firstly, I used to wake the system up from sleep using my USB keyboard when hitting "enter". Now it won't wake up with usb, and occasionally when waking it up with the power button, either my mouse or keyboard will not respond (both are USB). I then need to put the system back to sleep using the power button (I have xp set to sleep when pushed) and wake it up again to get the USB devices working. I have re-installed Windows XP, changed the ACPI BIOS settings to wake up using all devices, enabled/disabled legacy USB, downgraded the BIOS to 1.8 which I was running on my old board, and tried every USB slot on the board, all while running the exact same hardware that was on my previous board. Any help?
    Secondly, I have the board/windows set to wake from S3 when attempting to reach it remotely. I can login fine, but when I get home to check the system, the screen is black. It's still running, and I can reach it again through RDC, but I can't seem to wake it up locally. The only way to correct the screen is by hitting the power button to put it to sleep, and then hitting it again to get it out of S3. This seems like a videocard issue, and I have tried using older versions of the nvidia driver but I always seem to have the same problem. Oddly, when I run tests at home using my laptop everything is fine and the video is displayed after logging off, but it seems to only be happening when I'm using it from my work computer. I would need to run some more tests to verify this though, and I assume that after some time using my laptop it would do the same thing. (the tests were run going outside of the lan and coming back in, from an S3 state). Video card drivers I tried were, 178.24 (oct. 15th), 178.13 (sep. 25th), 175.16 (may 13th).
    Any help would be greatly appreciated. Thank you.
    kk
    MSI Neo2-FR (BIOS 1.9 & 1.8)
    Core2Quad Q6600
    Geforce 8800GT
    Mushkin 2x1GB 9200 (running at 1066)
    Antec Neo HE 550 watt PS
    Windows XP Pro SP3

    Thanks for the reply kourosh. I have used both the 1.9 (latest) and downgraded to the 1.8 BIOS that I was using on the board pre-RMA as stated in my initial post. It just doesn't make sense that I had everything working properly with the old board, and with the new board that I received back from MSI, things just don't work. I'm using the exact same hardware and have done multiple re-installs with different drivers etc.
    I doubt that part two is a networking problem as I stated in my initial post that I'm testing by going outside of the LAN and coming back in from outside. I think it has more to do with waking it up remotely multiple times (eg. wake up remotely-->sleep-->wake up again-->sleep again-->possible black screen error), but I haven't had the time to do all of the testing.
    I just find it strange that these things are not working as they were, and I'm beginning to blame the board again as I know how they SHOULD be working on the same exact board.
    Anyway... thanks again for the reply.
    kk

  • In need of serious help - BomFatalErrors?

    I usually leave my mac on, with the screen the only thing that sleeps, and restart when I need to for updates etc. Never had an issue with that, however when I came back from last weekend to work, my iMac was sitting there with it's sleep light on (typical) but did not respond to mouse or keyboard activity. I had to restart the comp, but hard restart, and when it started up, I got stuck at a black screen 95% of the time. I had to keep my fingers crossed at startup to finally hear a chime and see the gray startup screen, at which point I had to hold down the Option key to select my Mac Disk for Startup (had boot camp too, which I think had something to do with all this...). Once I was in my Mac OSX OS, I could do some things like open Mail and Safari, but when I'd open anything else, the program would quit before starting. Then things would get really funky in Mail or Safari, followed by a Kernal Panic (which is much more emphatic than the blue screen of death). I ended up removing my boot camp partition using BC Assistant, but that was followed up by another kernal panic. AppleCare is sending a repair guy to change the logic board and powersupply, but in the meantime I thought it was something else...
    After booting up from the restore/install DVDs that came with the iMac, I wiped the HD clean, checked it for errors and everything and started to reinstall a fresh osx install. Now I get something I've never seen before: BomFatalError - cpio read error. I can't imagine I have a bad install disk, bad hardware, all these things going on at once. I am a die hard mac fan, and I am quite frustrated by this. I guess this is the price we pay for switching to PC parts
    Anyhow, does anyone have a suggestion regarding if this in fact is a hardware issue or what? If anyone has seen this and noticed it's a HDD issue or RAM issue or videocard issue, that would be great.
    Sorry for the long post...

    Most manufacturers, Apple included, reserve the right to repair or replace at their discretion. But Apple has a great reputation for honoring their warranty and there is plenty of testimony just here in this one Intel forum that they work hard to make it right.
    It has always taken longer to get the parts for repair because the supply stream is to China to build new Macs, so parts have to be diverted out of the normal stream to various parts of the world for repair.

  • 2008 Mac Pro stuck at Light Blue/Dark Blue screen! HELP

    Hi, I've had my Mac Pro dual 2.8 Ghz Quad Core w/ the standard Radeon XT card, since the end of 08, and I haven't added ANY hardware to it, since.
    over the past year or so, i'll be working on my Mac Pro, and all of a sudden, it locks up, and a faint washed out, pink checkerboard pattern goes down my screen, but sound will still play, obviously forcing me to power down. SO, my problem now, is --> Just a couple of days ago, it finally did it for the last time.. I shut down, and now when I boot up, it either A) hangs at the white loading screen w/ gray apple and spinning YouTube style loading animation, or B), when I try the CMD+Option+P, R option, upon start up, or hold down Right-Click on mouse on startup, it just goes to the light blue screen (Which it always normally did before when it'd boot up), then it switches over to a darker-shade blue screen, with a dark colored Youtube style loading animation...Oh, and I can't open up the Superdrive no matter -what- I do, so I can't boot from CD? It responds to the key combinations, but not the eject key?!
    Is this a videocard issue? At first I thought so, but clearly I do seem to need a new videocard, with the pink checkerboard thing happening..but I am REALLY hoping this isn't a hard drive problem.I have so many things I'll be devasted if they're lost for good.
    Any advice would be GREATLY appreciated. I did search for this issue and I found similar issues, but it was always slightly different than my problem
    THANKS,
    Matt

    When i turn the computer on, on the RAM rack it has a red light but it only stays lit a couple seconds, then goes away.
    That's normal.  It's only a problem if one or more stay lit.
    Did you try the video card reseat yet?
    As for the optical drive; you pull the carrier out (as far as the cables would let you or unplug it) and you say you can't unscrew the drive from the carrier?  It's the only screws I think are in there so I am not sure what other screws you are trying to undo.  But if you leave the carrier hanging out, and you try to eject the tray, does it try to do it.  The reason I ask is the problem might only be that the carrier isn't exactly lined up with the bezel and that might be what's blocking it from opening when fully mounted.
    After this, I am not sure what else to suggest, so yes, you may need to get professional repair.

  • MSI K8T Neo2 F 939 pin, any known video or other driver issues?

    Using a MSI K8T Neo2 F, AMD 64 3500+ winchestor, 1gb DDR400 3200 memory, New WD 740GD SATA HDD, ATI 9800 GT Pro 256 videocard. Fresh XP Pro SP2 install with all the update, latest Via 4 in 1s.
    Seems like my problems began when I upgraded video drivers to either Cat 4.9s or 5.1s (ATI Radeon 9800 GT Pro 256) in order to get Doom3 running as it wouldn't run on the v 3.4 drivers that came on the cd-rom with the videocard.
      HL2 would play fine with those old drivers. After upgrading to newer drivers, HL2 and Doom 3 (which now at least plays) won't play for more than 5 minutes yet other games will. The same videocard (perhaps 3 months old now) with cat 4.9 drivers ran perfectly in my old system so I know the videocard's still OK.
      I can use a restore point prior to installing the newer drivers BUT that doesn't solve the problem as to why I can't use the newer drivers.
    I've heard where some have problems with XP SP2 vs SP1. Anyone here have opinions on that?
      I have spare HDDs so I can use one with another fresh XP install, even try just SP1 if that'd matter? Doing that would eliminate hardware as being an issue.
    It's now not just games either, it'll crash doing Turbotax and other (not demanding) times when not gaming. Games put alot of demand on any system.
    Have also tryed another PSU, now an Antec Truepower 430W vs a cheaper brand 550W. Not heat related as I've tryed this with a house fan blowing on high directly at the mobo, cpu side (cover's off).
      I've been trying to solve this for about a month now and it's very annoying.
      I ran Memtest for 8 hours last night, no errors so the memory's OK. I'm now running another test program called Prime95 via advice from someone at Anandtech.com. http://forums.anandtech.com/messageview.aspx?catid=32&threadid=1513208
      If ANYONE here has seen anything like this relating to this motherboard (which I suspect might be a problem?), please share your thoughts.
                   Thanks

    Can you explain where I'll find "VPU recover (adapter settings)"? In display settings or ATIs cat. control center, guessing? I'm at work now but will check that soon.
      AGP fast-write has been off.
     As for going back to older video drivers, it did seem OK with the old Cat. v3.4 drivers that came on the videocards driver cd-rom and played HL2 fine with those drivers HOWEVER, Doom3 doesn't run with those older drivers and needs the newer drivers to function.
      When it crashes, the screen usually goes to black (not BSOD). Sometimes it'll just freeze with skipping sound for a few seconds before going black, sometimes it'll reboot but usually I just reboot it. Can't 3 finger solute to task manager or Esc out of it either.

  • Issue with MacBook Air and nouveau

    Hi.
    I've installed Arch Linux on MacBook Air with Nvidia 320M videocard. Proprietary nvidia driver does not work at all and nouveau has video artefacts (photo attached because screenshot pictures haven't any problems): horizontal noisy black lines and wrong colors on the left two thirds of screen.
    /var/log/Xorg.0.log
    [ 4.374]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 4.374]
    X.Org X Server 1.11.99.903 (1.12.0 RC 3)
    Release Date: 2012-02-11
    [ 4.374] X Protocol Version 11, Revision 0
    [ 4.374] Build Operating System: Linux 3.2.6-2-ARCH x86_64
    [ 4.374] Current Operating System: Linux nikimac 3.2.6-2-ARCH #1 SMP PREEMPT Thu Feb 16 10:10:02 CET 2012 x86_64
    [ 4.374] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/disk/by-uuid/639277e8-a2f3-4313-b3e6-81eeb1453e85 ro init=/bin/systemd quiet
    [ 4.374] Build Date: 18 February 2012 05:06:59PM
    [ 4.374]
    [ 4.374] Current version of pixman: 0.24.4
    [ 4.374] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4.374] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4.374] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 21 16:55:39 2012
    [ 4.380] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4.382] (==) No Layout section. Using the first Screen section.
    [ 4.382] (==) No screen section available. Using defaults.
    [ 4.382] (**) |-->Screen "Default Screen Section" (0)
    [ 4.382] (**) | |-->Monitor "<default monitor>"
    [ 4.382] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 4.382] (==) Automatically adding devices
    [ 4.382] (==) Automatically enabling devices
    [ 4.392] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 4.393] Entry deleted from font path.
    [ 4.402] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 4.402] Entry deleted from font path.
    [ 4.402] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 4.402] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 4.402] Entry deleted from font path.
    [ 4.402] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 4.402] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 4.402] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4.402] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4.402] (II) Loader magic: 0x7cf1e0
    [ 4.402] (II) Module ABI versions:
    [ 4.402] X.Org ANSI C Emulation: 0.4
    [ 4.402] X.Org Video Driver: 12.0
    [ 4.402] X.Org XInput driver : 16.0
    [ 4.402] X.Org Server Extension : 6.0
    [ 4.404] (--) PCI:*(0:2:0:0) 10de:08a3:106b:00d3 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00001000/128, BIOS @ 0x????????/131072
    [ 4.404] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 4.404] (II) LoadModule: "extmod"
    [ 4.414] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 4.415] (II) Module extmod: vendor="X.Org Foundation"
    [ 4.415] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.415] Module class: X.Org Server Extension
    [ 4.415] ABI class: X.Org Server Extension, version 6.0
    [ 4.415] (II) Loading extension MIT-SCREEN-SAVER
    [ 4.415] (II) Loading extension XFree86-VidModeExtension
    [ 4.415] (II) Loading extension XFree86-DGA
    [ 4.415] (II) Loading extension DPMS
    [ 4.415] (II) Loading extension XVideo
    [ 4.415] (II) Loading extension XVideo-MotionCompensation
    [ 4.415] (II) Loading extension X-Resource
    [ 4.415] (II) LoadModule: "dbe"
    [ 4.415] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 4.416] (II) Module dbe: vendor="X.Org Foundation"
    [ 4.416] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.416] Module class: X.Org Server Extension
    [ 4.416] ABI class: X.Org Server Extension, version 6.0
    [ 4.416] (II) Loading extension DOUBLE-BUFFER
    [ 4.416] (II) LoadModule: "glx"
    [ 4.416] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 4.419] (II) Module glx: vendor="X.Org Foundation"
    [ 4.419] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.419] ABI class: X.Org Server Extension, version 6.0
    [ 4.419] (==) AIGLX enabled
    [ 4.419] (II) Loading extension GLX
    [ 4.420] (II) LoadModule: "record"
    [ 4.420] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 4.420] (II) Module record: vendor="X.Org Foundation"
    [ 4.420] compiled for 1.11.99.903, module version = 1.13.0
    [ 4.420] Module class: X.Org Server Extension
    [ 4.420] ABI class: X.Org Server Extension, version 6.0
    [ 4.420] (II) Loading extension RECORD
    [ 4.420] (II) LoadModule: "dri"
    [ 4.421] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 4.422] (II) Module dri: vendor="X.Org Foundation"
    [ 4.422] compiled for 1.11.99.903, module version = 1.0.0
    [ 4.422] ABI class: X.Org Server Extension, version 6.0
    [ 4.422] (II) Loading extension XFree86-DRI
    [ 4.422] (II) LoadModule: "dri2"
    [ 4.423] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 4.425] (II) Module dri2: vendor="X.Org Foundation"
    [ 4.425] compiled for 1.11.99.903, module version = 1.2.0
    [ 4.425] ABI class: X.Org Server Extension, version 6.0
    [ 4.425] (II) Loading extension DRI2
    [ 4.425] (==) Matched nouveau as autoconfigured driver 0
    [ 4.425] (==) Matched nvidia as autoconfigured driver 1
    [ 4.425] (==) Matched nv as autoconfigured driver 2
    [ 4.425] (==) Matched vesa as autoconfigured driver 3
    [ 4.425] (==) Matched fbdev as autoconfigured driver 4
    [ 4.425] (==) Assigned the driver to the xf86ConfigLayout
    [ 4.425] (II) LoadModule: "nouveau"
    [ 4.425] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 4.429] (II) Module nouveau: vendor="X.Org Foundation"
    [ 4.429] compiled for 1.11.99.902, module version = 0.0.16
    [ 4.429] Module class: X.Org Video Driver
    [ 4.429] ABI class: X.Org Video Driver, version 12.0
    [ 4.429] (II) LoadModule: "nvidia"
    [ 4.429] (WW) Warning, couldn't open module nvidia
    [ 4.429] (II) UnloadModule: "nvidia"
    [ 4.429] (II) Unloading nvidia
    [ 4.429] (EE) Failed to load module "nvidia" (module does not exist, 0)
    [ 4.429] (II) LoadModule: "nv"
    [ 4.429] (WW) Warning, couldn't open module nv
    [ 4.429] (II) UnloadModule: "nv"
    [ 4.429] (II) Unloading nv
    [ 4.429] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 4.429] (II) LoadModule: "vesa"
    [ 4.429] (WW) Warning, couldn't open module vesa
    [ 4.429] (II) UnloadModule: "vesa"
    [ 4.429] (II) Unloading vesa
    [ 4.429] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 4.430] (II) LoadModule: "fbdev"
    [ 4.430] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 4.431] (II) Module fbdev: vendor="X.Org Foundation"
    [ 4.431] compiled for 1.11.99.903, module version = 0.4.2
    [ 4.431] ABI class: X.Org Video Driver, version 12.0
    [ 4.431] (II) NOUVEAU driver
    [ 4.431] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 4.431] RIVA TNT (NV04)
    [ 4.431] RIVA TNT2 (NV05)
    [ 4.431] GeForce 256 (NV10)
    [ 4.431] GeForce 2 (NV11, NV15)
    [ 4.431] GeForce 4MX (NV17, NV18)
    [ 4.431] GeForce 3 (NV20)
    [ 4.431] GeForce 4Ti (NV25, NV28)
    [ 4.431] GeForce FX (NV3x)
    [ 4.431] GeForce 6 (NV4x)
    [ 4.432] GeForce 7 (G7x)
    [ 4.432] GeForce 8 (G8x)
    [ 4.432] GeForce GTX 200 (NVA0)
    [ 4.432] GeForce GTX 400 (NVC0)
    [ 4.432] (II) FBDEV: driver for framebuffer: fbdev
    [ 4.432] (++) using VT number 7
    [ 4.437] drmOpenDevice: node name is /dev/dri/card0
    [ 5.343] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
    [ 5.343] drmOpenDevice: node name is /dev/dri/card0
    [ 5.343] drmOpenDevice: open result is 7, (OK)
    [ 5.343] drmOpenByBusid: drmOpenMinor returns 7
    [ 5.343] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
    [ 5.343] (II) [drm] nouveau interface version: 0.0.16
    [ 5.343] (WW) Falling back to old probe method for fbdev
    [ 5.343] (II) Loading sub module "fbdevhw"
    [ 5.343] (II) LoadModule: "fbdevhw"
    [ 5.343] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 5.344] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 5.344] compiled for 1.11.99.903, module version = 0.0.2
    [ 5.344] ABI class: X.Org Video Driver, version 12.0
    [ 5.344] (II) Loading sub module "dri"
    [ 5.344] (II) LoadModule: "dri"
    [ 5.344] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 5.344] (II) Module dri: vendor="X.Org Foundation"
    [ 5.344] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.344] ABI class: X.Org Server Extension, version 6.0
    [ 5.344] (II) NOUVEAU(0): Loaded DRI module
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
    [ 5.344] drmOpenDevice: node name is /dev/dri/card0
    [ 5.344] drmOpenDevice: open result is 8, (OK)
    [ 5.344] drmOpenByBusid: drmOpenMinor returns 8
    [ 5.344] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
    [ 5.344] (II) [drm] DRM interface version 1.4
    [ 5.344] (II) [drm] DRM open master succeeded.
    [ 5.344] (--) NOUVEAU(0): Chipset: "NVIDIA NVaf"
    [ 5.344] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.344] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 5.344] (==) NOUVEAU(0): RGB weight 888
    [ 5.344] (==) NOUVEAU(0): Default visual is TrueColor
    [ 5.344] (==) NOUVEAU(0): Using HW cursor
    [ 5.344] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 5.345] (==) NOUVEAU(0): Page flipping enabled
    [ 5.379] (II) NOUVEAU(0): Output eDP-1 has no monitor section
    [ 5.540] (II) NOUVEAU(0): Output DP-1 has no monitor section
    [ 5.559] (II) NOUVEAU(0): EDID for output eDP-1
    [ 5.559] (II) NOUVEAU(0): Manufacturer: APP Model: 9cdf Serial#: 0
    [ 5.559] (II) NOUVEAU(0): Year: 2010 Week: 35
    [ 5.559] (II) NOUVEAU(0): EDID Version: 1.3
    [ 5.559] (II) NOUVEAU(0): Digital Display Input
    [ 5.559] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 29 vert.: 18
    [ 5.559] (II) NOUVEAU(0): Gamma: 2.20
    [ 5.559] (II) NOUVEAU(0): No DPMS capabilities specified
    [ 5.559] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 5.559] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 5.559] (II) NOUVEAU(0): redX: 0.593 redY: 0.342 greenX: 0.331 greenY: 0.573
    [ 5.559] (II) NOUVEAU(0): blueX: 0.152 blueY: 0.133 whiteX: 0.313 whiteY: 0.329
    [ 5.559] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 5.559] (II) NOUVEAU(0): Supported detailed timing:
    [ 5.559] (II) NOUVEAU(0): clock: 91.5 MHz Image Size: 286 x 179 mm
    [ 5.559] (II) NOUVEAU(0): h_active: 1440 h_sync: 1504 h_sync_end 1546 h_blank_end 1652 h_border: 0
    [ 5.559] (II) NOUVEAU(0): v_active: 900 v_sync: 903 v_sync_end 909 v_blanking: 926 v_border: 0
    [ 5.559] (II) NOUVEAU(0): Unknown vendor-specific block 1
    [ 5.559] (II) NOUVEAU(0): LP133WP1-TPA1
    [ 5.559] (II) NOUVEAU(0): Monitor name: Color LCD
    [ 5.559] (II) NOUVEAU(0): EDID (in hex):
    [ 5.559] (II) NOUVEAU(0): 00ffffffffffff000610df9c00000000
    [ 5.559] (II) NOUVEAU(0): 23140103801d12780aef059757549227
    [ 5.559] (II) NOUVEAU(0): 22505400000001010101010101010101
    [ 5.559] (II) NOUVEAU(0): 010101010101c223a0d450841a30402a
    [ 5.559] (II) NOUVEAU(0): 36001eb3100000180000000100061030
    [ 5.559] (II) NOUVEAU(0): 00000000000000000a20000000fe004c
    [ 5.559] (II) NOUVEAU(0): 503133335750312d54504131000000fc
    [ 5.559] (II) NOUVEAU(0): 00436f6c6f72204c43440a202020001f
    [ 5.559] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 5.559] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 5.559] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.559] (II) NOUVEAU(0): Printing probed modes for output eDP-1
    [ 5.559] (II) NOUVEAU(0): Modeline "1440x900"x59.8 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.559] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 5.559] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 5.559] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 5.560] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 5.720] (II) NOUVEAU(0): EDID for output DP-1
    [ 5.720] (II) NOUVEAU(0): Output eDP-1 connected
    [ 5.720] (II) NOUVEAU(0): Output DP-1 disconnected
    [ 5.720] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 5.720] (II) NOUVEAU(0): Output eDP-1 using initial mode 1440x900
    [ 5.720] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 5.720] (--) NOUVEAU(0): Virtual size is 1440x900 (pitch 0)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1440x900": 91.5 MHz (scaled from 0.0 MHz), 55.4 kHz, 59.8 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1440x900"x59.8 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 5.720] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
    [ 5.720] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 5.720] (**) NOUVEAU(0): Display dimensions: (290, 180) mm
    [ 5.720] (**) NOUVEAU(0): DPI set to (126, 127)
    [ 5.720] (II) Loading sub module "fb"
    [ 5.720] (II) LoadModule: "fb"
    [ 5.720] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 5.721] (II) Module fb: vendor="X.Org Foundation"
    [ 5.721] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.721] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.721] (II) Loading sub module "exa"
    [ 5.721] (II) LoadModule: "exa"
    [ 5.722] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 5.722] (II) Module exa: vendor="X.Org Foundation"
    [ 5.722] compiled for 1.11.99.903, module version = 2.5.0
    [ 5.722] ABI class: X.Org Video Driver, version 12.0
    [ 5.722] (II) Loading sub module "shadowfb"
    [ 5.722] (II) LoadModule: "shadowfb"
    [ 5.722] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 5.723] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 5.723] compiled for 1.11.99.903, module version = 1.0.0
    [ 5.723] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 5.723] (II) UnloadModule: "fbdev"
    [ 5.723] (II) Unloading fbdev
    [ 5.723] (II) UnloadSubModule: "fbdevhw"
    [ 5.723] (II) Unloading fbdevhw
    [ 5.723] (--) Depth 24 pixmap format is 32 bpp
    [ 5.728] (II) NOUVEAU(0): Opened GPU channel 2
    [ 5.728] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 5.728] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 5.728] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 5.729] (II) NOUVEAU(0): GART: 64MiB available
    [ 5.736] (II) NOUVEAU(0): GART: Allocated 16MiB as a scratch buffer
    [ 5.738] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 5.738] (II) EXA(0): Driver registered support for the following operations:
    [ 5.738] (II) Solid
    [ 5.738] (II) Copy
    [ 5.738] (II) Composite (RENDER acceleration)
    [ 5.738] (II) UploadToScreen
    [ 5.738] (II) DownloadFromScreen
    [ 5.738] (==) NOUVEAU(0): Backing store disabled
    [ 5.738] (==) NOUVEAU(0): Silken mouse enabled
    [ 5.738] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 5.738] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 5.738] (==) NOUVEAU(0): DPMS enabled
    [ 5.738] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 5.738] (--) RandR disabled
    [ 5.738] (II) Initializing built-in extension Generic Event Extension
    [ 5.738] (II) Initializing built-in extension SHAPE
    [ 5.738] (II) Initializing built-in extension MIT-SHM
    [ 5.738] (II) Initializing built-in extension XInputExtension
    [ 5.738] (II) Initializing built-in extension XTEST
    [ 5.738] (II) Initializing built-in extension BIG-REQUESTS
    [ 5.738] (II) Initializing built-in extension SYNC
    [ 5.738] (II) Initializing built-in extension XKEYBOARD
    [ 5.738] (II) Initializing built-in extension XC-MISC
    [ 5.738] (II) Initializing built-in extension SECURITY
    [ 5.738] (II) Initializing built-in extension XINERAMA
    [ 5.738] (II) Initializing built-in extension XFIXES
    [ 5.738] (II) Initializing built-in extension RENDER
    [ 5.738] (II) Initializing built-in extension RANDR
    [ 5.738] (II) Initializing built-in extension COMPOSITE
    [ 5.738] (II) Initializing built-in extension DAMAGE
    [ 5.799] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 5.799] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 5.799] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 5.799] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 5.800] (II) AIGLX: Loaded and initialized nouveau
    [ 5.800] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 5.805] (II) NOUVEAU(0): NVEnterVT is called.
    [ 6.217] (II) NOUVEAU(0): Setting screen physical size to 381 x 238
    [ 6.217] resize called 1440 900
    [ 6.272] (II) XKB: Reusing cached keymap
    [ 6.274] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 6.274] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.274] (II) LoadModule: "evdev"
    [ 6.274] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 6.275] (II) Module evdev: vendor="X.Org Foundation"
    [ 6.275] compiled for 1.11.99.902, module version = 2.6.99
    [ 6.275] Module class: X.Org XInput Driver
    [ 6.275] ABI class: X.Org XInput driver, version 16.0
    [ 6.275] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.275] Option "XkbRules" "evdev"
    [ 6.275] Option "XkbModel" "evdev"
    [ 6.275] Option "XkbLayout" "us"
    [ 6.275] Option "_source" "server/udev"
    [ 6.275] Option "name" "Power Button"
    [ 6.275] Option "path" "/dev/input/event3"
    [ 6.275] Option "device" "/dev/input/event3"
    [ 6.275] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.275] Option "driver" "evdev"
    [ 6.275] (**) Power Button: always reports core events
    [ 6.275] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 6.275] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.275] (--) evdev: Power Button: Found keys
    [ 6.275] (II) evdev: Power Button: Configuring as keyboard
    [ 6.275] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 6.275] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 6.275] (**) Option "xkb_rules" "evdev"
    [ 6.275] (**) Option "xkb_model" "evdev"
    [ 6.275] (**) Option "xkb_layout" "us"
    [ 6.301] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
    [ 6.301] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 6.301] (II) Using input driver 'evdev' for 'Video Bus'
    [ 6.301] Option "XkbRules" "evdev"
    [ 6.301] Option "XkbModel" "evdev"
    [ 6.301] Option "XkbLayout" "us"
    [ 6.301] Option "_source" "server/udev"
    [ 6.301] Option "name" "Video Bus"
    [ 6.301] Option "path" "/dev/input/event4"
    [ 6.301] Option "device" "/dev/input/event4"
    [ 6.301] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input4/event4"
    [ 6.301] Option "driver" "evdev"
    [ 6.301] (**) Video Bus: always reports core events
    [ 6.301] (**) evdev: Video Bus: Device: "/dev/input/event4"
    [ 6.301] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 6.301] (--) evdev: Video Bus: Found keys
    [ 6.301] (II) evdev: Video Bus: Configuring as keyboard
    [ 6.301] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2b/LNXVIDEO:00/input/input4/event4"
    [ 6.301] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 6.301] (**) Option "xkb_rules" "evdev"
    [ 6.301] (**) Option "xkb_model" "evdev"
    [ 6.301] (**) Option "xkb_layout" "us"
    [ 6.301] (II) XKB: Reusing cached keymap
    [ 6.301] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 6.302] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 6.302] (II) Using input driver 'evdev' for 'Power Button'
    [ 6.302] Option "XkbRules" "evdev"
    [ 6.302] Option "XkbModel" "evdev"
    [ 6.302] Option "XkbLayout" "us"
    [ 6.302] Option "_source" "server/udev"
    [ 6.302] Option "name" "Power Button"
    [ 6.302] Option "path" "/dev/input/event1"
    [ 6.302] Option "device" "/dev/input/event1"
    [ 6.302] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 6.302] Option "driver" "evdev"
    [ 6.302] (**) Power Button: always reports core events
    [ 6.302] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 6.302] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 6.302] (--) evdev: Power Button: Found keys
    [ 6.302] (II) evdev: Power Button: Configuring as keyboard
    [ 6.302] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 6.302] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 6.302] (**) Option "xkb_rules" "evdev"
    [ 6.302] (**) Option "xkb_model" "evdev"
    [ 6.302] (**) Option "xkb_layout" "us"
    [ 6.302] (II) XKB: Reusing cached keymap
    [ 6.302] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
    [ 6.302] (II) No input driver specified, ignoring this device.
    [ 6.302] (II) This device may have been added with another device file.
    [ 6.302] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 6.302] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 6.302] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 6.302] Option "XkbRules" "evdev"
    [ 6.303] Option "XkbModel" "evdev"
    [ 6.303] Option "XkbLayout" "us"
    [ 6.303] Option "_source" "server/udev"
    [ 6.303] Option "name" "Sleep Button"
    [ 6.303] Option "path" "/dev/input/event2"
    [ 6.303] Option "device" "/dev/input/event2"
    [ 6.303] Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 6.303] Option "driver" "evdev"
    [ 6.303] (**) Sleep Button: always reports core events
    [ 6.303] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 6.303] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 6.303] (--) evdev: Sleep Button: Found keys
    [ 6.303] (II) evdev: Sleep Button: Configuring as keyboard
    [ 6.303] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2"
    [ 6.303] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 6.303] (**) Option "xkb_rules" "evdev"
    [ 6.303] (**) Option "xkb_model" "evdev"
    [ 6.303] (**) Option "xkb_layout" "us"
    [ 6.303] (II) XKB: Reusing cached keymap
    [ 6.303] (II) config/udev: Adding input device Apple Inc. Apple Internal Keyboard / Trackpad (/dev/input/event10)
    [ 6.303] (**) Apple Inc. Apple Internal Keyboard / Trackpad: Applying InputClass "evdev keyboard catchall"
    [ 6.303] (II) Using input driver 'evdev' for 'Apple Inc. Apple Internal Keyboard / Trackpad'
    [ 6.303] Option "XkbRules" "evdev"
    [ 6.303] Option "XkbModel" "evdev"
    [ 6.303] Option "XkbLayout" "us"
    [ 6.303] Option "_source" "server/udev"
    [ 6.303] Option "name" "Apple Inc. Apple Internal Keyboard / Trackpad"
    [ 6.303] Option "path" "/dev/input/event10"
    [ 6.303] Option "device" "/dev/input/event10"
    [ 6.303] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input10/event10"
    [ 6.304] Option "driver" "evdev"
    [ 6.304] (**) Apple Inc. Apple Internal Keyboard / Trackpad: always reports core events
    [ 6.304] (**) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Device: "/dev/input/event10"
    [ 6.304] (--) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Vendor 0x5ac Product 0x240
    [ 6.304] (--) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Found keys
    [ 6.304] (II) evdev: Apple Inc. Apple Internal Keyboard / Trackpad: Configuring as keyboard
    [ 6.304] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input10/event10"
    [ 6.304] (II) XINPUT: Adding extended input device "Apple Inc. Apple Internal Keyboard / Trackpad" (type: KEYBOARD, id 10)
    [ 6.304] (**) Option "xkb_rules" "evdev"
    [ 6.304] (**) Option "xkb_model" "evdev"
    [ 6.304] (**) Option "xkb_layout" "us"
    [ 6.304] (II) XKB: Reusing cached keymap
    [ 6.304] (II) config/udev: Adding input device bcm5974 (/dev/input/event6)
    [ 6.304] (**) bcm5974: Applying InputClass "evdev touchpad catchall"
    [ 6.304] (**) bcm5974: Applying InputClass "Multitouch Touchpad"
    [ 6.304] (II) LoadModule: "multitouch"
    [ 6.304] (II) Loading /usr/lib/xorg/modules/input/multitouch.so
    [ 6.305] (II) Module multitouch: vendor="X.Org Foundation"
    [ 6.305] compiled for 1.11.99.903, module version = 0.1.0
    [ 6.305] Module class: X.Org XInput Driver
    [ 6.305] ABI class: X.Org XInput driver, version 16.0
    [ 6.305] (II) Using input driver 'multitouch' for 'bcm5974'
    [ 6.305] Option "_source" "server/udev"
    [ 6.305] Option "name" "bcm5974"
    [ 6.305] Option "path" "/dev/input/event6"
    [ 6.305] Option "device" "/dev/input/event6"
    [ 6.305] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/event6"
    [ 6.305] Option "driver" "multitouch"
    [ 6.305] (**) bcm5974: always reports core events
    [ 6.306] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/event6"
    [ 6.306] (II) XINPUT: Adding extended input device "bcm5974" (type: TOUCHPAD, id 11)
    [ 6.306] (II) device control: init
    [ 6.306] (**) Option "Device" "/dev/input/event6"
    [ 6.311] (II) multitouch: devname: bcm5974
    [ 6.311] (II) multitouch: devid: 5ac 240 1
    [ 6.311] (II) multitouch: caps: left mtdata ibt
    [ 6.311] (II) multitouch: 0: min: 0 max: 2048
    [ 6.311] (II) multitouch: 1: min: 0 max: 2048
    [ 6.311] (II) multitouch: 2: min: 0 max: 2048
    [ 6.311] (II) multitouch: 3: min: 0 max: 2048
    [ 6.311] (II) multitouch: 4: min: -16384 max: 16384
    [ 6.311] (II) multitouch: 5: min: -4620 max: 5140
    [ 6.311] (II) multitouch: 6: min: -150 max: 6600
    [ 6.336] (II) pointer_control
    [ 6.336] (**) bcm5974: (accel) keeping acceleration scheme 1
    [ 6.336] (II) pointer_property
    [ 6.336] (II) pointer_property
    [ 6.336] (**) bcm5974: (accel) acceleration profile 0
    [ 6.336] (II) pointer_property
    [ 6.336] (II) pointer_property
    [ 6.336] (**) bcm5974: (accel) acceleration factor: 2.000
    [ 6.336] (**) bcm5974: (accel) acceleration threshold: 4
    [ 6.337] (II) device control: on
    [ 6.337] (**) Option "Device" "/dev/input/event6"
    [ 6.342] (II) pointer_property
    [ 6.342] (II) pointer_property
    [ 6.342] (II) config/udev: Adding input device bcm5974 (/dev/input/mouse0)
    [ 6.342] (**) bcm5974: Applying InputClass "Multitouch Touchpad"
    [ 6.342] (II) Using input driver 'multitouch' for 'bcm5974'
    [ 6.342] Option "_source" "server/udev"
    [ 6.342] Option "name" "bcm5974"
    [ 6.342] Option "path" "/dev/input/mouse0"
    [ 6.342] Option "device" "/dev/input/mouse0"
    [ 6.342] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/mouse0"
    [ 6.342] Option "driver" "multitouch"
    [ 6.342] (**) bcm5974: always reports core events
    [ 6.342] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/input/input6/mouse0"
    [ 6.342] (II) XINPUT: Adding extended input device "bcm5974" (type: TOUCHPAD, id 12)
    [ 6.342] (II) device control: init
    [ 6.342] (**) Option "Device" "/dev/input/mouse0"
    [ 6.342] (EE) multitouch: cannot configure device
    [ 6.342] (EE) Couldn't init device "bcm5974"
    [ 6.342] (II) UnloadModule: "multitouch"
    [ 6.342] (II) config/udev: Adding input device Built-in iSight (/dev/input/event9)
    [ 6.342] (**) Built-in iSight: Applying InputClass "evdev keyboard catchall"
    [ 6.342] (II) Using input driver 'evdev' for 'Built-in iSight'
    [ 6.342] Option "XkbRules" "evdev"
    [ 6.343] Option "XkbModel" "evdev"
    [ 6.343] Option "XkbLayout" "us"
    [ 6.343] Option "_source" "server/udev"
    [ 6.343] Option "name" "Built-in iSight"
    [ 6.343] Option "path" "/dev/input/event9"
    [ 6.343] Option "device" "/dev/input/event9"
    [ 6.343] Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.1/usb1/1-6/1-6:1.0/input/input9/event9"
    [ 6.343] Option "driver" "evdev"
    [ 6.343] (**) Built-in iSight: always reports core events
    [ 6.343] (**) evdev: Built-in iSight: Device: "/dev/input/event9"
    [ 6.343] (--) evdev: Built-in iSight: Vendor 0x5ac Product 0x850a
    [ 6.343] (--) evdev: Built-in iSight: Found keys
    [ 6.343] (II) evdev: Built-in iSight: Configuring as keyboard
    [ 6.343] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.1/usb1/1-6/1-6:1.0/input/input9/event9"
    [ 6.343] (II) XINPUT: Adding extended input device "Built-in iSight" (type: KEYBOARD, id 12)
    [ 6.343] (**) Option "xkb_rules" "evdev"
    [ 6.343] (**) Option "xkb_model" "evdev"
    [ 6.343] (**) Option "xkb_layout" "us"
    [ 6.343] (II) XKB: Reusing cached keymap
    [ 6.343] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
    [ 6.343] (II) No input driver specified, ignoring this device.
    [ 6.343] (II) This device may have been added with another device file.
    [ 6.343] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event8)
    [ 6.343] (II) No input driver specified, ignoring this device.
    [ 6.343] (II) This device may have been added with another device file.
    [ 6.344] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event11)
    [ 6.344] (II) No input driver specified, ignoring this device.
    [ 6.344] (II) This device may have been added with another device file.
    [ 6.344] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
    [ 6.344] (II) No input driver specified, ignoring this device.
    [ 6.344] (II) This device may have been added with another device file.
    [ 6.369] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 6.369] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 6.369] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.550] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.550] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.550] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.754] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.754] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.754] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 7.963] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 7.963] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 7.963] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 8.165] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 8.165] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 8.165] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 8.364] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 8.364] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 8.364] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.133] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.133] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.133] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.359] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.359] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.359] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.560] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.560] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.560] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.760] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.760] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.760] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 16.961] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 16.961] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 16.961] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 17.159] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 17.159] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 17.159] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    [ 18.008] (II) pointer_control
    [ 18.830] (II) NOUVEAU(0): EDID vendor "APP", prod id 40159
    [ 18.830] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 18.830] (II) NOUVEAU(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz eP)
    nvidiafb works fine, but it has no dri and has problems with suspend.
    How to resolve this problem with nouveau? Is it crtc-related or not? Playing with xrandr does not have any effect (except resolution change).
    Last edited by nikicat (2012-02-22 15:00:18)

    I had an issue with my MBA seeing my HP printer and could find no good reason for the issue.  In the end I deleted the printers WiFi connection and then turned around and set it up on my WiFi network all over again.  My MBA now finds the printer every time.  Okay ...so I don't actually know why it didn't work the first time, but it does now.  Again, there was no apparent issue with either the HP printer or the MBA being connected to WiFi in the first place, but something different must have occurred in software/hardware the second time. 

  • Ram Issues with a Hp Pavilion a6357c or maybe the amd athlon 64 5000+

    I am really not sure if I am in the area-of a post like this. Please excuse my grammar and spelling"will try and use spell check"...
    I got this computer from a friend of mine.Total nightmare. Was told all it needs is a hard drive and maybe a video card..Boy was that not the issue. I first got it and plugged it-make sure it would boot to bios..Nothing computer turned on-fans and all..Nothing on the screen. To make a long story short...I found an old ps2 mouse..The mouse was defective...with that mouse plugged in-computer wouldn't even boot to bios..Fixed that issue. Got into bios and all was good. Next step..Video card-Bought a new pny 9500 GT and a TTGI 550 power supply....swaped it all out and it works great...Than found a hard drive SATA 2...everthing installed and ready to place an operating system on....
     Windows 7 64 bit--Installed great...But when it came up to the start up---Freeze--blue screen...Ok thought maybe it was the ram.....ended up taking all the old ram out and replace it with some DDR2 6300--or what ever the max was...total of 6 gb...still issue...freezing--decided to boot into safe mode---all good and ran great....checked Ram-stress test-checked every little hardware--stress test-no issues...Booted back up out of safe mode... Same issues....ok--lets just try Windows 7 32 bit.....
    Windows 7 32 bit.....Install went great-no issues....updated and all the sp's...but underload----bluescreen....played and played with it...but the blue screen were all over the place...back into safe mode and checked all the drivers--and devices....Ok lets just go back to what the system had----windows Vista....
     Again----everything boot and installed perfect...This time was a liitle more stable...updates--all the sp's all the drivers.....
    Blue screen underload......Ok maybe my ram is at fault.......
    It ended up stable and working perfect---single channel mode-2 gb in the first slot....I tried every way to put the ram in.....
    found out--ok---only stable in single channel mode...anytime I added ram--for dual channel...Fail under load....Put the 2 gb stick or a 1 gb stick any any of the other slots-by itself---perfect stable and running great...I was even able to add another 1 gb stick with the 2 gb stick---but it had to be in single channel....tried to add more in single channel and fail....3 is it and it is not all the way stable--but stable enough to run...2 gb stick by itself---perfect.........
    Did some digging---maybe it is the memory controller...But can not find any post with this issue---I keep finding people asking the quesion--and there storys match...But no answers and it seems that the just get a walk around.....
    I have narrowed it down..It has to me the intergrated memory controller on the chip....so i think...I could just purchase a new one and swap it out........But here is the issue...........
    Safe Mode will take all the ram-dual channel---single channel..anyway.......But so will linix-----Only has this issue with Windows....
    The other werid item too---My had drive say scis drive or something along that lines--Not sata.....and again-I can not find a post to explain why......
    Please understand----Stress test on Ram-cpu-motherboard--videocard----everthing--is perfect no issues...PSU is perfect---checked it out in another sytem---no issues....I am at my witts end with this thing and I have got nowhere......
    It is working great with just a 2 gb stick of ram---very fast and very responsive....But adding extra ram really bothers me...Not because--it make a differance-Just because I don't know...
    Can somebody out there school me.....I have tried everything........

    Sorry all-But i never got a reply to this situation. But I am done. I ended up running threw tons of post and tons of threads. I can tell you that when people ask a question. There is always some smart A--, telling them something that has nothing to do with the current situation. I guess alot of people out there think they know everything- and have nothing to do-but mess with the people like me when they are stumped. Anyways...I ended up running a computer check in or after bios...I think they call it burned in-HP....what ever-the last straw when you can not figure it out..Ran it with one stick---than with all the sticks..Everytime--it claimed that there was nothing wrong..But when I tried to restart it--boom blue screen..with the mulyi sticks of ram. So when I couldn't find an solution online...I stoped using the words HP a6357c.. and just typed the issue..Funny thing the issue kept poping up--and with the same motherboard or processor...and again-nobody ever came up with a solution..Most of the post claimed the issue was the power supply....ot the ram timming..But I know better..Not to mention people kept saying-buy the tool from ebay to check wattage usuage.....Bam----wattage...Did a simple check with harware monitor...my 3.5 or 3.3 rail was running at 1.78....enought to power one stick of ram---not 2...or barley enough to power a 1 gb stick and a 2 gb stick in single channel mode...Again-people were blaming--PSU"not my case".Ram Timming.."not my case".........Then I found a person with the same make and model.....Look for fat or bad capasitors...Never thought of that.....Guess what------That is what I found....No body but a thread-one thread has explained...If you have this same issue-Look at the capasitors...Maybe this is a defective motherboard--you can not find it on the site anyway-no specs nada..like it was a mistake..So if you have one just like this- I have a feeling-you will run into this issue-in one way or another..I just don't understand why both companys have no fix--or no--recall info..No answers to problems on these....now I have a big black paper weight.....sorry for my spelling and grammer-just so mad..the net was no help on this

  • PDF Files Issues

    Here is the situation.
    Installed Max OSX 10.5.
    Caused a problem with printing pdf files on a Canon imageclass MF4150, resolved by installing a new printer driver (UFRII_V150MacOSX) & fax driver (FaxV160MaxOSX.dmg) dl'd from Canon.
    Now I cannot view any pdf files. I use Adobe Acrobat V.8.1.1 all I get is a grey screen with the adobe logo in the centre.
    Apparently there will be another update to acrobat in January that may deal with the issue.
    Is there some way (other than downloading each and every pdf to my computer in order to view them? Perhaps a videocard driver update as well? Any suggestions?

    So the best workaround I've found so far is to just go into Acrobat/preferences on the left side click "internet" and uncheck the box that says to open acrobat files using safari <your version> and do a re-start.
    It just opens the pdf file in Acrobat then.
    Seems to work for me.

  • PowerMac G4 1.42 Dual - Kernel Panics and other issues

    Hi,
    I have a PowerMac G4 1.42ghz that has a number of problems.
    Firstly, it kernel panics somewhat frequently. Not consistently on one app, but completely randomly. For example, I came home one day to find that it had woken from sleep and had a kernel panic message over my screensaver. It mostly kernel panics while using it though.
    It also does something weird where it logs itself out randomly. The screen goes blue and returns me to the login window. Sometimes I can log back in, other times not. This happens on both network and local accounts.
    I also noticed that in System Profiler that my L3 cache is failed. but I figure it should be able to operate without it.
    Oh, and 2 of my RAM slots cause the computer to boot with Open Firmware errors.
    Things I've tried:
    Reset PRAM/PMU. No change.
    Installed 10.5 on another hard drive. No change.
    Swapped out videocard for a PCI one. No change.
    Swapped out RAM with known good RAM. No change.
    Installed 10.4. Haven't had the logout issue, but have had apps crash and kernel panics.
    I'm pretty sure my problems are either motherboard or CPU related. I just want to know which one to try replacing first.

    The only external devices I have connected are my Aluminum keyboard and mighty mouse. I occasionally plug in my iPod touch.
    Here's three kernel panics.
    Tue Sep 29 18:24:36 2009
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000095D0798 PC=0x00000000000B4A84
    Latest crash info for cpu 0:
    Exception state (sv=0x4778fc80)
    PC=0x000B4A84; MSR=0x00001030; DAR=0x095D0798; DSISR=0x40000000; LR=0x000B48B8; R1=0x0000BF80; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x000B48B8
    backtrace terminated - frame not mapped or invalid: 0xBFFFD230
    Proceeding back via exception chain:
    Exception state (sv=0x4778fc80)
    previously dumped as "Latest" state. skipping...
    BSD process name corresponding to current thread: Finder
    Mac OS version:
    9L30
    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
    System model name: PowerMac3,6
    System uptime in nanoseconds: 3867053504449
    unloaded kexts:
    com.apple.iokit.IOSerialFamily 9.4 - last unloaded 9820196330
    Tue Sep 29 17:19:11 2009
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000409878 PC=0x00000000000B4FE0
    Latest crash info for cpu 0:
    Exception state (sv=0x3b535500)
    PC=0x000B4FE0; MSR=0x00009030; DAR=0x00409878; DSISR=0x0A000000; LR=0x0031EE70; R1=0x42B17AC0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x0031EE5C 0x0031F134 0x0031F3E4 0x0032037C 0x0031C7CC 0x003203F4
    0x003203F4 0x0033D710 0x0037DB44 0x0008E9FC 0x0002C100 0x00024B58 0x000B45CC 0x6765723E
    Proceeding back via exception chain:
    Exception state (sv=0x3b535500)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x42b21c80)
    PC=0x9330B1F8; MSR=0x0200F030; DAR=0xF029AC58; DSISR=0x40000000; LR=0x93312120; R1=0xBFFFE9F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    9L30
    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
    System model name: PowerMac3,6
    System uptime in nanoseconds: 127374271862
    Mon Sep 28 19:54:18 2009
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000409878 PC=0x00000000000B4FE0
    Latest crash info for cpu 0:
    Exception state (sv=0x3b535500)
    PC=0x000B4FE0; MSR=0x00009030; DAR=0x00409878; DSISR=0x0A000000; LR=0x0031EE70; R1=0x42B17AC0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x0031EE5C 0x0031F134 0x0031F3E4 0x0032037C 0x0031C7CC 0x003203F4
    0x003203F4 0x0033D710 0x0037DB44 0x0008E9FC 0x0002C100 0x00024B58 0x000B45CC 0x6765723E
    Proceeding back via exception chain:
    Exception state (sv=0x3b535500)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x42b21c80)
    PC=0x9330B1F8; MSR=0x0200F030; DAR=0xF029AC58; DSISR=0x40000000; LR=0x93312120; R1=0xBFFFE9F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    9L30
    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
    System model name: PowerMac3,6
    System uptime in nanoseconds: 127374271862

  • K8N Platinum Video and S-ATA issues

    hey,
    here is my problem: i bought some hardware 3 weeks ago, including:
    A64 3800+ (Venice), MSI K8N Neo4 Platinum (MS-7125), Leadtek PX6800 GT TDH (265MB), Be Quiet! 450 Watt Titanium S1.3
    in exchange for my old system (2500+, Abit K7N, ATi Radeon 9800SE AiW, 320W Enermax PSU)
    the hardware change went great, had no errors after the exchange, windows xp (sp2) worked for 2 weeks. though, some things are errorous like the nForce eth being detected but no drivers installed, nForce raid not being detected - stuff like that probably resulting from a missing format c: and really clean install.
    now things get quite strange. a friend of mine gave me 2 of his s-ata hdds (both maxtor, one 160gb and the other 200gb) - after plugging them onto the nforce s-ata raid, i was still able to get into the bios (at this time it was the biosversion the board shipped with) but the keyboard was locked (or the pc froze after entering the bios - can't tell for sure). unplugged the drives - and it was working again.
    let's get to the main problem. after the problems above i thought "well, ok, let's reset the cmos, maybe i configured it wrong" so i shut down my pc and pushed the "clear cmos" button - then i did a normal boot, i heared the "beep", everything was just fine - but my TFT stayed black. i had a similar situation on my old board, so i disconnected the psu and removed the battery for 10 seconds. boot: display worked again. i immediately checked my bios (which was indeed resetted) but did not change anything. reboot -> black screen. now, the funny thing is.. the gfx card got 2 dvi and 1 s-video output (one dvi and s-video were connected) so i checked my tv - guess what, i saw the POST  now i knew the board was "working" and my assumptions of which the black screen results in a crashed videocard/mobo were wrong. i sat there and watched windows xp boot up - and suddenly (after the xp vga drivers have been loaded i guess) my tft displays the image!
    now this is VERY odd and tbh i really don't know what to say. anyways, i started msi liveupdate and downloaded/installed the latest official bios update (via winflash because i don't have a floppy anymore) to see if that might fix something. it didn't.
    and now here i am, desperate and confused because i don't know whether or not it's a mobo or gfx issue - all i know is that it suddenly appeared after the cmos clear (sadly there's no "description" of whether you should press that button when the pc is shut off, psu is disconnected, mobo is running its post whatever) and i can't find a logical reason for this behaviour
    to add another detail to the story, after i found out the video output was sent via s-video, i tried all combinations (dvi1 connected, dvi2 not, s-video not / dvi1 not, dvi2 connected, s-video not / dvi1 + 2 not, s-video connected / etc.) but the only source i can get the post from (until WinXP loads) is the s-video out.
    i think maybe it could be the gfx card's bios, which loads up BEFORE the post begins (leadtek welcome screen, ram counts itself -> post -> os) but i'm not sure about it either
    ANY help is very appreciated
    *edit* i forgot to mention: it worked before! after hitting this nifty little button, the display problems began...

    Quote from: Supershanks on 03-June-05, 20:24:49
    Hi llamalein,
    Welcome to the forum.
    thx
    Quote
    1) Your monitor issue is not uncommon see Syar's post hereWon't boot, please help.
    thanks, i'll try it as soon as i'm at home though i'm quite sure it wont work 
    Quote
    3) Exactly which K8N Platinum have you I know it's a 939 but Neo4(7 versions) or neo2(2-4 versions)
    yarr, i am so worried i already forget to post the right specs it's the K8N Neo4 Platinum (MS-7125) (as described here
    Quote
    4) Please post your full specs  - we don't know what your OS is currently running on what optical drives - look arounf the forum for the format. also include the amps on the 3.3v,5v,12v rails for your power supplyu.
    PSU data (as supplied by the manufacturer):
    #  3,3V: 28A
    # 5V: 45A
    # 12V: 22A
    # -5V:: 0.8A
    # -12V:: 1.0A
    # 5Vsb:: 2.5A
    HDDs:
    ide1m - Samsung SP1614N
    ide1s - Samsung SP1614N
    ide2m - Plextor DVD Burner
    IDE Controller:
    ide3m - Samsung SP1614N
    ide3s - Some old Western Digital HDD (80/7200)
    (m = master, s = slave)
    WXPP is located on ide1m

  • K8N Neo3 Issues (At the end of my rope)

    The parts I have are as follows:
    1x K8N Neo3 MOBO
    1x Sapphire x1600 Radeon Video Card 512MB PCIE
    1x AMD64 Sempron +3000 (Socket 754)
    1x WD 100GB HDD
    1x WD 250GB HDD
    2x DRAM Master PC3200 DDR400 Memory Modules
    1x DWL D-Link 11.0Mbps Wireless USB Adapter
    1x LiteOn 16X DVD Dual Drive (ATAPI/E-IDE)
    Some things to note:
    All of the parts have been tested in other machines and work perfectly. I'm currently running XP Pro on a 15gig partition on the 100GB HDD. All of the drivers are installed on this partition as well as firefox. On the other partition on that drive, I have 3DMark05 and windows media player classic installed. Both partitioned were made after formatting the entire drive. On the 250GB HDD, I have some anime and various wallpapers. Hardware acceleration currently set to two notches left of full. All of the drivers are up to date, and I have flashed the BIOS.
    The problems:
    First off, my CD driver could not read CDs all too well. In the middle of installation I'd get tons of errors which was odd considering the fact that the CD (XP Pro) worked in other comps. After I flashed the BIOS however, this problem was removed, or rather, it pops up less frequently.
    Another issue I'm having is with the memory. Both memory modules work well, and were memtested with no errors, however, unless I go to Advanced Chipset Features in the BIOS and enter into DRAM Configuration and change the timing mode to manual, set the Memclock Index Value to 250MHZ and the CAS# Latency to 3, I can't boot into XP. Instead, it'll clear POST, and then pretend like it's going to take me to XP, and then reboot. On the issue with memory, it's interesting to note that with my old sempron processor (AMD 3200+), I don't have to change any BIOS settings to get the RAM to work.
    The next problem on the list is with my video card. As mentioned previously, it's a Sapphire x1600 Radeon 512MB PCIE and I can't get it to work on this system for the life of me. I tested the card in a friend's computer (uninstalled his drivers and installed mine before attempting) and it worked like a dream. In mine however, whenever I go to run a graphic intensive program such as 3DMark05, it locks up after about 10 seconds, some times sooner. Occaisonaly VPU will kick in, but usually I have to perform a reboot. Even the little car animation in catalyst control center locks up my computer. It's interesting to note however that when watching anime, that I can usually go about 2 or 3 episodes before my computer freezes up on me, or just reboots.
    It's interesting to note that my computer has not rebooted on me while surfing the net, or typing stuff up.
    Another issue is that it seems like I can't go 10 or 15 minutes without something shutting down, such as firefox, or msn messenger due to errors. I've reinstalled windows and formatted twice now, and I'm still continually getting conflicts. I'm not sure if this issue might be tied into the ones I'm having with the motherboard, or if that even makes sense, but considering the fact I wasn't having these issues till I switched to this one, I'm ready to put the blame on it.
    My theories:
    My current theory is that there is a device driver conflict somewhere. After much searching, reinstalling, and a lot of crying, I've not been able to figure out what the video card is conflicting with. While this issue might be better dealt with on some ATI fourm, ATI has not such fourm I could find, and since I'm having issues with the board overall, I figured I'd post it here.
    I have no theory as to why one processor would have me to change bios setting to get the RAM to work, and why another wouldn't.
    I have no theory as to why I can watch anime, but not play games.
    What I'm hoping for:
    I'm open to any possible solutions to the problems I'm currently experiencing, and would even be grateful for possible causes if no solution can be met. If all else fails, and I can't get anything to work, (even though all the other parts work on other boards), I'll assume the board is faulty and just RMA it considering the fact that the people I bought it from don't accept returns.

    Quote from: Xfraze on 03-February-06, 19:26:38
    I plan to get a 450W PSU today and see if that helps, I have my fingers crossed though. Last time I though my computer had a power issue, it turned out the problem was somthing else and I forkedout some cash for nothing.
    Yep, that happens ... that is why I always recommend to try it out with a borrowed PSU first. Still, I have the feeling that things are moving in the right direction Maybe it is time to take a closer look at the videocard - you have any idea of the temperature of the card under stress - or about the temperatures in the computer in general? CPU temp, case temp, etc?

  • Wine directx9 issues

    Hello, guys.
    Some games that other people run just fine on my pc won't run.
    The latest problem - problem with Heroes of might and magic 5. When I try to run the game I get wine
    popup window with message: "error failed to initialize direct3d9". I tried clean wine installation because
    I thought maybe other programs thrashed my bottle but it did not help.
    And this:
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,0,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,9,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,18,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,27,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,36,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,45,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,54,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,63,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,72,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,81,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,90,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,99,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,108,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,117,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,126,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,135,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,144,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,153,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,162,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,171,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,180,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,189,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,198,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,207,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,216,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,225,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,234,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,243,2): stub!
    fixme:win:SetLayeredWindowAttributes (0x20026,0x00000000,252,2): stub!
    fixme:win:EnumDisplayDevicesW ((null),0,0x32f7fc,0x00000000), stub!
    There is a similar problem in discussed in appdb but they did not find solution.
    So I'm asking if there is a way to configure wine directx capabilities?
    I know that wine supports directx7 and I'm fine with it, I don't want to install 9c
    because I had similar problem with Call of duty 2 and installation of directx did
    not solve anything.
    som additional info:
    Wine version: wine-1.1.2
    Videocard: Nvidia Geforce 6600GT
    Videocard Driver version: 173.14.09-4
    Thanks,
    Any suggestions are appreciated.

    Dheart wrote:Did you check wine's appdb?
    And also by clean wine installation you mean new .wine directory?
    Yes.
    I checked appdb and they do not know anything about this certain issue.
    I also tried to run in wine 0.9.50 and got:
    err:module:import_dll Library d3dx9_25.dll (which is needed by L"C:\\Heroes5\\Heroes of Might and Magic V - Tribes of the East\\bin\\H5_Game.exe") not found
    err:module:LdrInitializeThunk Main exe initialization for L"C:\\Heroes5\\Heroes of Might and Magic V - Tribes of the East\\bin\\H5_Game.exe" failed, status c0000135

  • Hdmi sound problem since videocard upgrade to R9 290x.

    Hello
    i recently upgraded my videocard from Radeon 6870 to R9 290x. Since the upgrade the hdmi audio playback sound realy delayed und noisy.
    aplay -l
    **** Liste der Hardware-Geräte (PLAYBACK) ****
    Karte 0: SB [HDA ATI SB], Gerät 0: ALC889 Analog [ALC889 Analog]
    Sub-Geräte: 0/1
    Sub-Gerät #0: subdevice #0
    Karte 0: SB [HDA ATI SB], Gerät 1: ALC889 Digital [ALC889 Digital]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 3: HDMI 0 [HDMI 0]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 7: HDMI 1 [HDMI 1]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 8: HDMI 2 [HDMI 2]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 9: HDMI 3 [HDMI 3]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 10: HDMI 4 [HDMI 4]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    Karte 1: Generic [HD-Audio Generic], Gerät 11: HDMI 5 [HDMI 5]
    Sub-Geräte: 1/1
    Sub-Gerät #0: subdevice #0
    lspci -v |grep Audio
    00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
    01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8
    cat /proc/asound/card*/code*|grep Codec
    Codec: Realtek ALC889
    Codec: ATI R6xx HDMI
    Some one with the same problem here?

    Hubrisnxs wrote:
    Ahhhhh,  Most tv's have a couple or more,  you may want to try Component cables then,  You can call Verizon or open a live chat, they may send you some for free, or they may point you towards their website www.verizon.com/fiosaccessories
    I'd open a live chat and see if I could get them for free personally, but they are also very cheap at www.amazon.com  
    They are HD cables that support upto 1080p 
    GEEZ, I can't be the only person having this issue. I will try 1 call to them to see what they say. Thanks for your input.

Maybe you are looking for