I think my HD is failing

Began ~ 7-2009
Spinning Beach Ball of Death(SBBD), Freezes, only manual (Power button) shut down worked
Got worse,more frequent
Multiple times; repair permissions, verify disk, used Leopard DVD to boot & run Repair disk
Got worse, sometimes failed to boot & had to shut down again. Sometimes “?” folder on attempted boot so had to use option key & reselect default Disk to boot.
9-4-2009 Failed to repair disk
Bought Disk Warrior 9-4-2009, Rebuilt file directory
Concerned about file corruption (maybe in TM backups also) decided to reinstall O.S.
1st tried Archive & Install Leopard --FAILED- plan was to fix Leopard 10.8 & once fixed update to Snow Leopard. “The Installer was unable to import your user directory from the previous system. You will need to create a new account.” I did & updated to 10.5.8, saw that it worked--seemed OK. But did not transfer my files yet. (Have TM backup)
Decided to leave my HD partitioned (Boot Camp) & Erase Macintosh HD & Install Snow Leopard
Did NOT restore old complete system, User folder, etc since concerned about transferring any corruption.
It worked. Spent hours transferring TM files to new Snow Leopard.
Migration Assistant FAILED to Work DID NOT “see” my LaCie Ext. H.D. (WAS on Desktop)
Used Disks or Web to reinstall most applications over many hours.
1X Snow Leopard failed to wake from Sleep. Had to hard stop/start SL. Apple discussions show this happened to many others. I turned off sleep hard disk till Apple fixes sleep issue. Updated to 10.6.1. -- during restart got Apple logo changed to circle with slash & froze. Did manual power shut down start & booted OK to 10.6.1.
9-12-2009--Finally, when almost finished restoring system same PROBLEM began again! SBB, freezes (10-30 seconds at 1st) Slow & failed hard restarts. Often freeze after 5 minutes no matter what I am doing including nothing, no apps open.
Used Disk Utility booting from Snow Leopard to repair disk 2x in last 24 hours & 3rd time failed to repair disk! (Says reformat disk)
Used Disk Warrior 4.2 once again to repair directory. 3rd time in 48 hours?
Mac not useable; freezes, booting problems, directory continually needs rebuilding, Disk Utility cannot repair disk.
I suspect HD failure as cause. Do not think software since I tried booting into Windows Boot Camp partition & in 5 minutes got blue screen saying: “A process crucial to system operation has unexpectedly terminated...” Now cannot boot into Windows without getting this blue screen. Don’t see how any Mac partition software issue can affect a separate working Windows partition.

I’m updating to help others who may read this later. Brought iMac into Apple Store for Genius Bar appt. Monday AM, 9-14-2009. I had already checked the two Authorized Apple repair facilities via phone on the drive over. Either one would replace my HD with any HD I wanted if they could get it. No 15 minute appt. needed. Cost would be less (once I finally found out the cost of HD replacement from Apple store) One would do it in two hours & the other in 1-2 days. This would certainly be the way to go for typical HD replacement for most. Call ahead, decide what HD (larger?) you want & ask how long your Mac will be in the shop & the total cost. Be aware, some shops will quote you just the price of the HD itself leaving out the labor cost & appearing less expensive than the other shops -- so ask for the total cost. BTW, it is true that the Apple store will NOT replace your HD with anything other than the original type of HD whether your Mac is in or out of warranty & whether you do or do not have Apple Care. So, if you want to upgrade to a larger HD, do NOT use the Apple Store. Use an AASP.
I arrive at the Genius Bar for my 15 minute apt. (with plans to get verification of the HD failure & a price quote for HD replacement & then immediately drive my iMac to the AASP that said he can replace it with a larger HD in two hours) I explain the SBBD, frequent freezes, forced manual power offs, failure to boot, Repair DIsk failures, Disk Warrior multiple rebuild directory, etc. I explained about the failed Archive & Install & having to resort to Erase & install Snow Leopard. Told about the reappearance of the same exact troubles several hours after the new install. Finally I showed my printout from Smart Utility 2.1 ; “Overall Smart Status FAILING -- Yellow. Pending Bad sector 1 ID # 197”
The tech ran Disk Warrior himself & ran a different utility to check the HD status (which actually passed?) But, he said given my Smart Utility failure & all that I have done to trouble shoot he will accept that the HD has failed. He quoted a price about $80-100 higher than the AASP & then stunned me by saying that even though I do not have Apple Care & my warranty was up 10 months ago --they will replace the HD at N/C! He said it should not have failed so soon. Fantastic! Downside is that they are out of stock on 50 GB HDs & the repair will take 3-5 days. I didn’t get my iMac back until Friday evening 9-18-2009. (I know from watching web videos of iMac HD replacements it is a 20 minute job.)
BTW, after I got it home & reinstalled my stuff, I again D/L Smart Utility 2.1 & ran it twice & it showed RED (not yellow as b4) failure. Shows ID # 190 Airflow Temperature Celsius as “failing now.” Yet, the Apple Verify disk shows everything fine. Having MUCH trouble believing that coincidentally, my NEW HD would immediately FAIL w/o any symptoms at all -- I searched & found another utility to test my HD. “Smart Reporter 2.4” which works with Snow Leopard & is free. This sits in your menu bar & monitors your SMART status. My HD passed & still is “green.” So I think the Smart Utility 2.1 may be over sensitive & have given a false positive.
In any event, I now have a bootable backup with Carbon Copy Cloner on an external HD so if any future problems & recovery will be much easier/faster.
It was somewhat slow to recover my data since I was very careful in case I had any file corruption. I reinstalled all my apps manually from disk or web. I had a bit of trouble with Time Machine (TM) when I went to restore my documents folder. I clicked on the most recent backup for documents, pictures, movies, videos & they all were restored with a red “X” on the folder & the folder could not be opened in Snow Leopard! I ended up just using the TM HD as a volume & manually dragging over the contents of those folders to my empty documents, pictures, etc. folder. That worked. Also, I kept the Snow Leopard folder appearance which looks different than the TM backup folders which are Leopard. I did have an issue where if I opened a document & tried to change it, I didn’t have permission & had to manually go into info & change it to read write one by one so I ended up changing the entire documents folder permissions at once. Also, I was getting strange pop-up windows when I’d click on a sub folder & get a message that the alias doesn’t point to anything--but it was NOT an alias, no arrow, I never had created aliases of folders. Either changing permission for the entire documents folder ‘fixed’ this or it just isn’t happening anymore.
Now my Mac is back & working just fine with Snow Leopard. I have not been able to restore either my Boot Camp Windows installation or my VMware virtual machine of the Windows Boot Camp to date. I did back up my Boot Camp Windows partition using Winclone but not to an external HD, Just backed it up to my Mac HD & then it was copied to TM but attempts to restore from the TM winclone file have failed & no help from the Winclone user forums. I went into the external HD used for TM & just chose that winclone file to restore FROM but no help. I am not attempting to use the TM software to restore Windows which I know doesn’t work. I reinstalled VMware Fusion & TM did save the virtual machine but it will not work. No help from the VMware Fusion user forums so I don’t know if the issue is the lack of a restored Boot Camp Windows installation, a Snow Leopard incompatibility issue or what. So, I will most likely have to reinstall Windows onto Boot Camp again from scratch & them create a new Virtual machine also. Reinstall the Windows programs & manually restore Windows files which I also saved onto an external drive just in case. Much trouble that I had thought would be avoided by using Winclone. It is better to clone Windows onto an external hard drive but I didn’t see anywhere where this was required.

Similar Messages

  • Think my drive is failing............

    I have two internal drives but I think my system drive is failing as my ppc g5 tower is going to the grey restart screen at times. So I want to put a new drive in maybe 1tb. I've never done this before but I guess I will take out my second drive, put in it's place the new drive, Carbon Clone the old system drive onto the new drive and the system will then be on that. Like I say I've never cloned a system so very cautious not to get it wrong......
    Any tips please......

    I mentioned using a fast boot drive? well, I would not use the original at all except as a new backup and for emergency - something to use to run Disk Warrior.
    The Samsung F3 is fast, no doubt about it, and $9/100GB is a "steal." Get two.
    But the system boot drive has enough to do on its own and your music and audio really likes to be on their own drives.
    Any drive, other than "green" (variable and slower rpm) today is fine. Personally, I'd use just 10K VelociRaptors even if it means adding FirmTek SATA controller and have 4-5 internal drives. The cost more but really, even my 1TB WD Black Caviar is shamed into admitting it isn't as fast or as responsive.
    Upgrading your OEM 230, and look at your "B" drive, too while at it, use those as backups.

  • HT1349 i turn my machine on and we get a folder that has a question mark     we think the hard drive failed  ccan it be saved

    we would be grateful for any help

    Hello howard420,
    Thanks for using Apple Support Communities.
    For more information on this, take a look at:
    A flashing question mark appears when you start your Mac
    http://support.apple.com/kb/ts1440
    Best of luck,
    Mario

  • Apple Mobile Device Support fails to install, remains unsolved.

    i came back to the forums after a coupld of months, and this issue is still unsolved, will support please read this and answer us, it seems i am not the only one with such problems. so i will repost this issue here hoping to find a solution.
    Thank you.
    Reading through the forums, i found many with this same error, some said reinstalling solves this problem, but for me, and many others, it did not, so here is a log of the installation where the error shows, please look at it and tell us wheat to do,
    Action 8:21:17: InstallFiles. Copying new files
    Action 8:21:18: MsiRollbackInstall.
    Action 8:21:18: MsiInstallDrivers.
    DIFXAPP: ENTER: InstallDriverPackages()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'componentPath' is C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: INFO: opening HKEY_USERS 'S-1-5-21-1605124395-1919374747-2981180892-1004\Software\Microsoft\Windows\Curr entVersion\DIFxApp\Components{9AA3828A-F852-11DB-8E29-6C6B55D89593}' (User's SID: 'S-1-5-21-1605124395-1919374747-2981180892-1004') ...
    DIFXAPP: INFO: ENTER: DriverPackageInstallW
    DIFXAPP: INFO: usbaapl.inf: checking signature with catalog 'C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\USBAAPL.CAT' ...
    DIFXAPP: INFO: Driver package 'usbaapl.inf' is WHQL signed.
    DIFXAPP: ERROR: Create Driver Store entry failed. (Error code 0x6E: The system cannot open the device or file specified.)
    DIFXAPP: INFO: Successfully removed '{9AA3828A-F852-11DB-8E29-6C6B55D89593}' from reference list of driver store entry ''
    DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x52)
    DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\usbaapl.inf
    DIFXAPP: InstallDriverPackages failed with error 0x52
    DIFXAPP: RETURN: InstallDriverPackages() 82 (0x52)
    Action ended 8:21:20: InstallFinalize. Return value 3.
    Action 8:21:20: Rollback. Rolling back action:
    Rollback: MsiInstallDrivers
    Rollback: MsiRollbackInstall
    DIFXAPP: ENTER: RollbackInstall()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: This was the component where the install failure occurred. The rollback for this component must have already occurred at the time of failure. No need to rollback again
    DIFXAPP: Rollback failed with error 0x2
    DIFXAPP: RETURN: RollbackInstall() 2 (0x2)
    Rollback: Copying new files
    Rollback: Moving files
    Rollback: Creating folders
    Rollback: Removing system registry values
    Rollback: Deleting services
    Rollback: Stopping services
    Rollback: Updating component registration
    Action 8:21:41: Rollback. Rolling back action:
    Rollback: MsiInstallDrivers
    Rollback: MsiRollbackInstall
    DIFXAPP: ENTER: RollbackInstall()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for component '{9AA3828A-F852-11DB-8E29-6C6B55D89593}'
    DIFXAPP: Rollback failed with error 0x2
    DIFXAPP: RETURN: RollbackInstall() 2 (0x2)
    Rollback: Copying new files
    Rollback: Moving files
    Rollback: Creating folders
    Rollback: Removing system registry values
    Rollback: Deleting services
    Rollback: Stopping services
    Rollback: Updating component registration
    Action ended 8:22:00: INSTALL. Return value 3.
    Action ended 8:22:00: ExecuteAction. Return value 3.
    Action 8:22:00: SetupCompleteError.
    Action start 8:22:00: SetupCompleteError.
    Action 8:22:00: SetupCompleteError. Dialog created
    Action ended 8:22:03: SetupCompleteError. Return value 2.
    Action ended 8:22:03: INSTALL. Return value 3.
    === Logging stopped: 1/11/2008 8:22:03 ===
    MSI (c) (10:8C) 08:22:03:595: Product: Apple Mobile Device Support -- Installation failed.
    now i went to the directory where the driverfiles should be, and paused the installation just before it starts rolling back and made a copy of the whole thing, the driver files are being extracted, and thinking it may have failed to find them, i restarted the installation and paused it after it extracted the files, copied over my backup files to where they should be, and resumed, same thing happened, failure again.
    I stopped all the services running, (msconfig / startup and services) and that still did not help, i went through my registry for every "apple" and deleted it, after uninstalling all apple products, that did not help, i ran windows install clean up and made sure that quicktime and itunes and apple updatea re not installed, did the whole thing again, no luck.......
    Can someone please tell me what is going on, i can run it just fine on my other machine, which is running windows xp pro as well, the only thing different i did on this one was that i plugged in the Iphone before installing the software, whereas i ran the itunes installer on that one before i plugged in the iphone, and yes, i did get the iphone driver as a camera at first, and i changed it later by pointing the update driver to the same directory where applemobiledevicesupport extracted the 3 driver files :
    C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers
    and the files are usbaapl.cat , usbaapl.inf, and usbaapl.sys
    please look into this issue, i've done everything i could think of,
    Thank you.
    Windows XP Pro

    *"will support please read this and answer us"*
    These are user to user forums. Apple employees do not take part in them.

  • Apple Mobile Device Support fails to install ??

    Reading through the forums, i found many with this same error, some said reinstalling solves this problem, but for me, and many others, it did not, so here is a log of the installation where the error shows, please look at it and tell us wheat to do,
    Action 8:21:17: InstallFiles. Copying new files
    Action 8:21:18: MsiRollbackInstall.
    Action 8:21:18: MsiInstallDrivers.
    DIFXAPP: ENTER: InstallDriverPackages()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'UI Level' is 5.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'componentPath' is C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: INFO: opening HKEY_USERS 'S-1-5-21-1605124395-1919374747-2981180892-1004\Software\Microsoft\Windows\Curr entVersion\DIFxApp\Components\{9AA3828A-F852-11DB-8E29-6C6B55D89593}' (User's SID: 'S-1-5-21-1605124395-1919374747-2981180892-1004') ...
    DIFXAPP: INFO: ENTER: DriverPackageInstallW
    DIFXAPP: INFO: usbaapl.inf: checking signature with catalog 'C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\USBAAPL.CAT' ...
    DIFXAPP: INFO: Driver package 'usbaapl.inf' is WHQL signed.
    DIFXAPP: ERROR: Create Driver Store entry failed. (Error code 0x6E: The system cannot open the device or file specified.)
    DIFXAPP: INFO: Successfully removed '{9AA3828A-F852-11DB-8E29-6C6B55D89593}' from reference list of driver store entry ''
    DIFXAPP: INFO: RETURN: DriverPackageInstallW (0x52)
    DIFXAPP: ERROR encountered while installing driver package C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers\usbaapl.inf
    DIFXAPP: InstallDriverPackages failed with error 0x52
    DIFXAPP: RETURN: InstallDriverPackages() 82 (0x52)
    Action ended 8:21:20: InstallFinalize. Return value 3.
    Action 8:21:20: Rollback. Rolling back action:
    Rollback: MsiInstallDrivers
    Rollback: MsiRollbackInstall
    DIFXAPP: ENTER: RollbackInstall()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: This was the component where the install failure occurred. The rollback for this component must have already occurred at the time of failure. No need to rollback again
    DIFXAPP: Rollback failed with error 0x2
    DIFXAPP: RETURN: RollbackInstall() 2 (0x2)
    Rollback: Copying new files
    Rollback: Moving files
    Rollback: Creating folders
    Rollback: Removing system registry values
    Rollback: Deleting services
    Rollback: Stopping services
    Rollback: Updating component registration
    Action 8:21:41: Rollback. Rolling back action:
    Rollback: MsiInstallDrivers
    Rollback: MsiRollbackInstall
    DIFXAPP: ENTER: RollbackInstall()
    DIFXAPP: 'CustomActionData' property 'DIFxApp Version' is 2.1.
    DIFXAPP: 'CustomActionData' property 'componentId' is {9AA3828A-F852-11DB-8E29-6C6B55D89593}.
    DIFXAPP: 'CustomActionData' property 'flags' is 0x17.
    DIFXAPP: 'CustomActionData' property 'installState' is 2.
    DIFXAPP: 'CustomActionData' property 'ProductName' is Apple Mobile Device Support.
    DIFXAPP: 'CustomActionData' property 'ManufacturerName' is Apple Inc..
    DIFXAPP: ERROR 0x2 encountered while opening persistent-info key for component '{9AA3828A-F852-11DB-8E29-6C6B55D89593}'
    DIFXAPP: Rollback failed with error 0x2
    DIFXAPP: RETURN: RollbackInstall() 2 (0x2)
    Rollback: Copying new files
    Rollback: Moving files
    Rollback: Creating folders
    Rollback: Removing system registry values
    Rollback: Deleting services
    Rollback: Stopping services
    Rollback: Updating component registration
    Action ended 8:22:00: INSTALL. Return value 3.
    Action ended 8:22:00: ExecuteAction. Return value 3.
    Action 8:22:00: SetupCompleteError.
    Action start 8:22:00: SetupCompleteError.
    Action 8:22:00: SetupCompleteError. Dialog created
    Action ended 8:22:03: SetupCompleteError. Return value 2.
    Action ended 8:22:03: INSTALL. Return value 3.
    === Logging stopped: 1/11/2008 8:22:03 ===
    MSI (c) (10:8C) [08:22:03:595]: Product: Apple Mobile Device Support -- Installation failed.
    now i went to the directory where the driverfiles should be, and paused the installation just before it starts rolling back and made a copy of the whole thing, the driver files are being extracted, and thinking it may have failed to find them, i restarted the installation and paused it after it extracted the files, copied over my backup files to where they should be, and resumed, same thing happened, failure again.
    I stopped all the services running, (msconfig / startup and services) and that still did not help, i went through my registry for every "apple" and deleted it, after uninstalling all apple products, that did not help, i ran windows install clean up and made sure that quicktime and itunes and apple updatea re not installed, did the whole thing again, no luck.......
    Can someone please tell me what is going on, i can run it just fine on my other machine, which is running windows xp pro as well, the only thing different i did on this one was that i plugged in the Iphone before installing the software, whereas i ran the itunes installer on that one before i plugged in the iphone, and yes, i did get the iphone driver as a camera at first, and i changed it later by pointing the update driver to the same directory where applemobiledevicesupport extracted the 3 driver files :
    C:\Program Files\Common Files\Apple\Mobile Device Support\Drivers
    and the files are usbaapl.cat , usbaapl.inf, and usbaapl.sys
    please look into this issue, i've done everything i could think of,
    Thank you.

    I have the exact same problem on my workstation and previously solved it by installing iTunes on a different computer and copying all the files and registry keys to my workstation. However, it didn't solve the problem when i tried to update to itunes 7.6 ...
    Is there any solution yet?

  • Are 'read only' items causing my automatic row processing to fail?

    I have a form that uses automatic row processing to update my table.
    I recently had to add a check to lock down the fields using the read only condition where a record has been 'approved'. So, I turned off all of the fields and hid the update button.
    Now they want me to check to see if the user is a manager, and if so, allow them to see the update button, and make a single field on the form modifiable.
    I have the user identified as a manager, and can make the field accept the change (a yes/no combo box). Yet when they click the update button, the form just sits there. A branch is supposed to fire on hitting that button, taking them back to the previous report, but it doesn't happen. The source of the combo box in question uses a column on the table, and works fine when the form has all of the fields showing for modification.
    I had some validations that I finally set to never fire, thinking that they were failing and just not giving the error messages. I know a bad sql or pl/sql atatement in a validation will cause the form to just keep sitting there doing nothing, and thought it might help.
    Several of the various fields are combo boxes, several are text boxes.
    I'm stumped.
    Shall I keep the regular update button hidden whether it is a manager or not (because it has been 'approved'), and enable a new button that fires off a process to update the one field that the manager may want to change? Does making a field 'read only' always have a detrimental effect on the auto processes I've been counting on? Is that if fact what is happening now?
    Thanks in advance for any advice or comments on this.
    Clayton

    Hi, Scott.
    My version is 3.0.0.00.20
    I have received info to set up the application, though I have not activated it as yet. I'm reluctant to try to load up the various tables to make it work. It could be done.
    My workaround is to that the user (a manager) fires off to another form to show an individual record, and ask if he/she really wants to make this change. On submit, they will be taken back to the original locked down form, and I will update the single field in that process of returning them. This will actually be a plus, in that I expect to show them all of the 'duplicate' entries for that item, and show them that by 'activating' this particular item, they will 'deactivate' the one duplicate that is currently active. Or, if they are deactivating the sole item that is active, that there will in fact be no active items in the system. Convoluted as heck, but they swear this is how they've been doing business with their briefcases and file cabinets of Excel files. I'm surprise they even float at this point (these are ships we're talking about).
    This all may be due to the form originally having a next/previous/count process once arrived at my clicking on the edit button of the report of items. All of that has been hidden away, and though the fields exist of the form, they are not used. They only see the current item that they clicked on from the report.
    I read up a little on session state, as well as posts with the debug error I was getting. I'm still not on board with the whole issue of 'state'. Items stay as they are until they're changed, no? I suppose that sounds simplistic.
    One of the things that caught my eye was several combo box lists that on read only mode, showed [] square brackets. Which, in some cases is okay.
    What I'll try to do is set up a public application - for future use if nothing else. I'm going to be working on this for awhile. I have more than a bit of work to do to cleanse the data as well as get rid of the single sign on requirement (I'll assume that I should have to do this) in order to share the app.
    I know you're expecting me to have this up and running for you to look at, but I'm under the gun. And they actually like my workaround.
    I'll keep everybody informed, one way or another.
    Clayton

  • I think my hard drive is about to die, can I get some help?

    Hello!  Well, I have an iMac (I believe it's a mid 2007 model?) 20 inch, Core 2 Duo, and I believe my hard drive is failing.  It's a long story, but its more or less exactly how it played out, so bear with me.
    I noticed a few things going wonky a little while back, and started to back up data piece by piece. Well, eventually, I decided the best thing to do was to find a way to back-up my important files (I would have simply made a bootable back-up image of my HD on my external drive, but I have too many video and audio files on there to risk losing should I make it a dedicated back-up drive). Well, in transferring my files into my external drive I received Finder Error -36 (or something, may have been 036). After researching the error, it seems it commonly pops up with one of two possible cases:
    in transferring files between windows and mac formatted drives and causing an error, or
    a potentially failing hard drive.
    Fearing the worst, I ran a verify disk on Disk Utility, and it said the disk needed to be repaired. Booted from my DVD, and ran the Repair Disk. It said the disk could not be repaired, to make immediate back-ups, and reformat the drive.  Well, I hurried back over to mac to continue to attempt backing up my data to prepare for the reformat, the computer simply would no longer boot up the disk. It would go to the white screen and begin to boot, then immediately shut down. My BootCamp partition worked fine, however, except for a very similar transferring error. So I went ahead and reformatted (a quick one the first time) and Mac OS X refused to install (I am not sure if this was a DVD error as my optical drive is shot and very stubborn about reading a disc once I get one into the drive). I reformatted again, this time doing a 0 write out option.
    After an excruciating week to reformat on a 0 write out, I installed Mac OS X (Leopard this time as to opposed Snow Leopard, in case it was a scratched disc). Well, thinking I had cured the problem, I tried to update to latest version, and upon doing so, encountered an error telling me the OS could not be updated. After rebooting the system, the computer seemed to go into a permanent status of a looped reboot. It would literally restart just as soon as the disk was loaded. So I reformatted again, installed Leopard, and ran disk utility. It told me that the disk could not be verified and needs to be repaired (after passing the verification test when booted from the DVD).  Now when I am on the mac, it is incredibly slow and sluggish, and takes anywhere from 15 minutes to an hour to load iTunes, or even check e-mail on Safari. This was cause for my original concern before the Finder Error I encountered and believed it was just ram dying, but decided to get a head start on backing up files in case it was something far more serious.  Is my hard drive simply dead and needs to be replaced, or is there something else I could do?  It is currently running basic Leopard from the install disc without further updates, as it seems updating the system tends to kill it.
    Thanks for any help at all greatly appreciated.

    To be honest your post is rambling and difficult to read due to the lack of proper punctuation I only read it part way however...
    The first thing to do is a proper backup. Your system has Time Machine built into it, here is the Time Machine Tutorial. Look that over, get yourself an external HD to use as a TM drive and backup properly! This will backup all of OS X however it will NOT backup MS Windows!
    If you think your HD is failing then run Apple Hardware Test in Extended Mode and if it reports errors you can post them here.
    Roger

  • Startx on a vmware is throwing a "failed to create screen resources"

    The Bottom line error is:
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    I am trying to get a browsers running on my new Arch Linux, so I can cut and paste better for questions. I have installed xorg, chromium, firefox. If I try and start "startx", it say the server did not start. I think it is the failed to create screen resources.
    I have edit the video settings to give it 32meg of memory. Also I hack the .vmx file to enable the 3d opttion. I have installed all the vmtools (open version) Again, new to Arch Linux so I sure it is something stupid.
    Not sure if it helps but here are the errors when I try and run the browsers.
    chromium
    [320:320:1121/142755:Error:browser_main_loop.cc(209) Gtk: cannot open display:
    firefox
    (process:354): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
    Error: no display specified
    Entire log Xorg.0.log
    [ 1430.963]
    X.Org X Server 1.16.2
    Release Date: 2014-11-10
    [ 1430.965] X Protocol Version 11, Revision 0
    [ 1430.965] Build Operating System: Linux 3.17.2-1-ARCH x86_64
    [ 1430.967] Current Operating System: Linux PingBuild 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64
    [ 1430.967] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=36544952-8a9a-41c9-b169-87189310b752 rw quiet
    [ 1430.969] Build Date: 10 November 2014 07:52:13PM
    [ 1430.970]
    [ 1430.970] Current version of pixman: 0.32.6
    [ 1430.972] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 1430.972] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1430.975] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Nov 21 12:53:21 2014
    [ 1430.976] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 1430.976] (==) No Layout section. Using the first Screen section.
    [ 1430.976] (==) No screen section available. Using defaults.
    [ 1430.976] (**) |-->Screen "Default Screen Section" (0)
    [ 1430.976] (**) | |-->Monitor "<default monitor>"
    [ 1430.976] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 1430.976] (==) Automatically adding devices
    [ 1430.976] (==) Automatically enabling devices
    [ 1430.976] (==) Automatically adding GPU devices
    [ 1430.976] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 1430.976] Entry deleted from font path.
    [ 1430.976] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 1430.976] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 1430.976] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 1430.976] (II) Loader magic: 0x818d80
    [ 1430.976] (II) Module ABI versions:
    [ 1430.976] X.Org ANSI C Emulation: 0.4
    [ 1430.976] X.Org Video Driver: 18.0
    [ 1430.976] X.Org XInput driver : 21.0
    [ 1430.976] X.Org Server Extension : 8.0
    [ 1430.979] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
    [ 1430.979] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 1430.983] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
    [ 1431.010] (--) PCI:*(0:0:15:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xd8000000/67108864, 0xd0800000/8388608, I/O @ 0x000010d0/16, BIOS @ 0x????????/32768
    [ 1431.010] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 1431.010] (II) LoadModule: "glx"
    [ 1431.011] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 1431.016] (II) Module glx: vendor="X.Org Foundation"
    [ 1431.016] compiled for 1.16.2, module version = 1.0.0
    [ 1431.016] ABI class: X.Org Server Extension, version 8.0
    [ 1431.016] (==) AIGLX enabled
    [ 1431.016] (==) Matched vmware as autoconfigured driver 0
    [ 1431.016] (==) Matched vmware as autoconfigured driver 1
    [ 1431.016] (==) Matched modesetting as autoconfigured driver 2
    [ 1431.016] (==) Matched fbdev as autoconfigured driver 3
    [ 1431.016] (==) Matched vesa as autoconfigured driver 4
    [ 1431.016] (==) Assigned the driver to the xf86ConfigLayout
    [ 1431.016] (II) LoadModule: "vmware"
    [ 1431.017] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
    [ 1431.044] (II) Module vmware: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 13.0.2
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "modesetting"
    [ 1431.044] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 1431.044] (II) Module modesetting: vendor="X.Org Foundation"
    [ 1431.044] compiled for 1.16.0, module version = 0.9.0
    [ 1431.044] Module class: X.Org Video Driver
    [ 1431.044] ABI class: X.Org Video Driver, version 18.0
    [ 1431.044] (II) LoadModule: "fbdev"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 1431.045] (II) Module fbdev: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 0.4.4
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) LoadModule: "vesa"
    [ 1431.045] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 1431.045] (II) Module vesa: vendor="X.Org Foundation"
    [ 1431.045] compiled for 1.16.0, module version = 2.3.2
    [ 1431.045] Module class: X.Org Video Driver
    [ 1431.045] ABI class: X.Org Video Driver, version 18.0
    [ 1431.045] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
    [ 1431.045] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 1431.045] (II) FBDEV: driver for framebuffer: fbdev
    [ 1431.045] (II) VESA: driver for VESA chipsets: vesa
    [ 1431.045] (++) using VT number 1
    [ 1431.045] (--) controlling tty is VT number 1, auto-enabling KeepTty
    [ 1431.045] (WW) Falling back to old probe method for modesetting
    [ 1431.045] (WW) Falling back to old probe method for fbdev
    [ 1431.045] (II) Loading sub module "fbdevhw"
    [ 1431.045] (II) LoadModule: "fbdevhw"
    [ 1431.046] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 1431.046] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 1431.046] compiled for 1.16.2, module version = 0.0.2
    [ 1431.046] ABI class: X.Org Video Driver, version 18.0
    [ 1431.046] (WW) Falling back to old probe method for vesa
    [ 1431.046] (II) vmware(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 1431.046] (--) vmware(0): DRM driver version is 2.6.1
    [ 1431.046] (==) vmware(0): Depth 24, (--) framebuffer bpp 32
    [ 1431.046] (==) vmware(0): RGB weight 888
    [ 1431.046] (==) vmware(0): Default visual is TrueColor
    [ 1431.046] (--) vmware(0): Min width 1, Max Width 8192.
    [ 1431.046] (--) vmware(0): Min height 1, Max Height 8192.
    [ 1431.047] (II) vmware(0): Output Virtual1 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual2 has no monitor section
    [ 1431.047] (II) vmware(0): Output Virtual3 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual4 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual5 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual6 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual7 has no monitor section
    [ 1431.048] (II) vmware(0): Output Virtual8 has no monitor section
    [ 1431.048] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.048] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Printing probed modes for output Virtual1
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.0 42.75 800 850 900 950 600 650 700 750 -hsync +vsync (45.0 kHz eP)
    [ 1431.049] (II) vmware(0): Modeline "2560x1600"x60.0 348.50 2560 2752 3032 3504 1600 1603 1609 1658 -hsync +vsync (99.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1440"x60.0 234.00 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync (90.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1856x1392"x60.0 218.25 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync (86.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1920x1200"x59.9 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 1431.049] (II) vmware(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
    [ 1431.049] (II) vmware(0): EDID for output Virtual2
    [ 1431.049] (II) vmware(0): EDID for output Virtual3
    [ 1431.049] (II) vmware(0): EDID for output Virtual4
    [ 1431.049] (II) vmware(0): EDID for output Virtual5
    [ 1431.049] (II) vmware(0): EDID for output Virtual6
    [ 1431.049] (II) vmware(0): EDID for output Virtual7
    [ 1431.049] (II) vmware(0): EDID for output Virtual8
    [ 1431.049] (II) vmware(0): Output Virtual1 connected
    [ 1431.049] (II) vmware(0): Output Virtual2 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual3 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual4 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual5 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual6 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual7 disconnected
    [ 1431.049] (II) vmware(0): Output Virtual8 disconnected
    [ 1431.049] (II) vmware(0): Using exact sizes for initial modes
    [ 1431.049] (II) vmware(0): Output Virtual1 using initial mode 800x600
    [ 1431.049] (II) vmware(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 1431.049] (==) vmware(0): DPI set to (96, 96)
    [ 1431.049] (II) Loading sub module "fb"
    [ 1431.049] (II) LoadModule: "fb"
    [ 1431.049] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 1431.050] (II) Module fb: vendor="X.Org Foundation"
    [ 1431.050] compiled for 1.16.2, module version = 1.0.0
    [ 1431.050] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 1431.050] (II) Loading sub module "dri2"
    [ 1431.050] (II) LoadModule: "dri2"
    [ 1431.050] (II) Module "dri2" already built-in
    [ 1431.050] (II) UnloadModule: "modesetting"
    [ 1431.050] (II) Unloading modesetting
    [ 1431.050] (II) UnloadModule: "fbdev"
    [ 1431.050] (II) Unloading fbdev
    [ 1431.050] (II) UnloadSubModule: "fbdevhw"
    [ 1431.050] (II) Unloading fbdevhw
    [ 1431.050] (II) UnloadModule: "vesa"
    [ 1431.050] (II) Unloading vesa
    [ 1431.050] (==) Depth 24 pixmap format is 32 bpp
    [ 1431.050] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
    [ 1431.064] (II) vmware(0): Gallium3D XA version: 2.2.0.
    [ 1431.064] (II) vmware(0): Path of drm device is "/dev/dri/card0".
    [ 1431.064] (II) vmware(0): [DRI2] Setup complete
    [ 1431.064] (II) vmware(0): [DRI2] DRI driver: vmwgfx
    [ 1431.064] (--) vmware(0): Render acceleration is enabled.
    [ 1431.064] (==) vmware(0): Rendercheck mode is disabled.
    [ 1431.064] (--) vmware(0): Direct rendering (3D) is enabled.
    [ 1431.064] (==) vmware(0): Direct presents are disabled.
    [ 1431.064] (==) vmware(0): Hardware only presents are disabled.
    [ 1431.064] (==) vmware(0): Backing store enabled
    [ 1431.064] (==) vmware(0): Silken mouse enabled
    [ 1431.064] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 1431.064] (==) vmware(0): DPMS enabled
    [ 1431.064] (--) RandR disabled
    [ 1431.075] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 1431.075] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 1431.075] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 1431.075] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 1431.075] (II) AIGLX: Loaded and initialized vmwgfx
    [ 1431.075] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 1431.076] (EE)
    Fatal server error:
    [ 1431.076] (EE) failed to create screen resources(EE)
    [ 1431.076] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 1431.076] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 1431.076] (EE)
    [ 1431.076] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 1431.076] (WW) vmware(0): drmDropMaster failed: Invalid argument
    [ 1431.079] (EE) Server terminated with error (1). Closing log file.
    Journal since boot
    -- Logs begin at Wed 2014-11-19 16:23:50 CST, end at Fri 2014-11-21 14:25:54 CST. --
    Nov 21 14:17:03 PingBuild kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xfeff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:00.0: [8086:7190] type 00 class 0x060000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: [8086:7191] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.0: [8086:7110] type 00 class 0x060100
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: [8086:7111] type 00 class 0x01018a
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: reg 0x20: [io 0x10c0-0x10cf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: [8086:7113] type 00 class 0x068000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1000-0x103f] claimed by PIIX4 ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.3: quirk: [io 0x1040-0x104f] claimed by PIIX4 SMB
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: [15ad:0740] type 00 class 0x088000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x10: [io 0x1080-0x10bf]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:07.7: reg 0x14: [mem 0xd0000000-0xd0001fff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: [15ad:0405] type 00 class 0x030000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x10: [io 0x10d0-0x10df]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x14: [mem 0xd8000000-0xdbffffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x18: [mem 0xd0800000-0xd0ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: reg 0x30: [mem 0x00000000-0x00007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: [1000:0030] type 00 class 0x010000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x10: [io 0x1400-0x14ff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x14: [mem 0xd0040000-0xd005ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x1c: [mem 0xd0020000-0xd003ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x00003fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: [15ad:0790] type 01 class 0x060401
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: [15ad:07a0] type 01 class 0x060400
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [32] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [33] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [34] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [35] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [36] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [37] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [38] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [39] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [40] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [41] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [42] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [43] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [44] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [45] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [46] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [47] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [48] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [49] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [50] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [51] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [52] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [53] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [54] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [55] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [56] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [57] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [58] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [59] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [60] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [61] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [62] registered
    Nov 21 14:17:03 PingBuild kernel: acpiphp: Slot [63] registered
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: [8086:100f] type 00 class 0x020000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x10: [mem 0xd1020000-0xd103ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x18: [mem 0xd1000000-0xd100ffff 64bit]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x20: [io 0x2000-0x203f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: System wakeup disabled by ACPI
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000cc000-0x000cffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xc0000000-0xfebfffff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x0d00-0xfeff] (subtractive decode)
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xd3e00000-0xd3efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [mem 0xdd400000-0xdd4fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: PCI bridge to [bus 1a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xd4200000-0xd42fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [mem 0xdd600000-0xdd6fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: PCI bridge to [bus 1b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [io 0x7000-0x7fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd2700000-0xd27fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.0: bridge window [mem 0xd4700000-0xd47fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: PCI bridge to [bus 1c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [io 0xb000-0xbfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd2b00000-0xd2bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.1: bridge window [mem 0xd4a00000-0xd4afffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: PCI bridge to [bus 1d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0xf000-0xffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd2f00000-0xd2ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [mem 0xd4c00000-0xd4cfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: PCI bridge to [bus 1e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd3300000-0xd33fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [mem 0xd4e00000-0xd4efffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: PCI bridge to [bus 1f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd3700000-0xd37fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [mem 0xd5000000-0xd50fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: PCI bridge to [bus 20]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd3b00000-0xd3bfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [mem 0xd5200000-0xd52fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: PCI bridge to [bus 21]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd3f00000-0xd3ffffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [mem 0xd5400000-0xd54fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: PCI bridge to [bus 22]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd4300000-0xd43fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [mem 0xd5600000-0xd56fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *9 10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 *10 11 14 15)
    Nov 21 14:17:03 PingBuild kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 14 15) *0, disabled.
    Nov 21 14:17:03 PingBuild kernel: ACPI: Enabled 2 GPEs in block 00 to 0F
    Nov 21 14:17:03 PingBuild kernel: vgaarb: setting as boot device: PCI:0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: vgaarb: device added: PCI:0000:00:0f.0,decodes=io+mem,owns=io+mem,locks=none
    Nov 21 14:17:03 PingBuild kernel: vgaarb: loaded
    Nov 21 14:17:03 PingBuild kernel: vgaarb: bridge control possible 0000:00:0f.0
    Nov 21 14:17:03 PingBuild kernel: PCI: Using ACPI for IRQ routing
    Nov 21 14:17:03 PingBuild kernel: PCI: pci_cache_line_size set to 64 bytes
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: can't claim BAR 13 [io 0xf000-0xffff]: no compatible bridge window
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
    Nov 21 14:17:03 PingBuild kernel: e820: reserve RAM buffer [mem 0xbfef0000-0xbfffffff]
    Nov 21 14:17:03 PingBuild kernel: NetLabel: Initializing
    Nov 21 14:17:03 PingBuild kernel: NetLabel: domain hash size = 128
    Nov 21 14:17:03 PingBuild kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Nov 21 14:17:03 PingBuild kernel: NetLabel: unlabeled traffic allowed by default
    Nov 21 14:17:03 PingBuild kernel: HPET: 16 timers in total, 0 timers will be used for per-cpu timer
    Nov 21 14:17:03 PingBuild kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
    Nov 21 14:17:03 PingBuild kernel: hpet0: 16 comparators, 64-bit 14.318180 MHz counter
    Nov 21 14:17:03 PingBuild kernel: Switched to clocksource hpet
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI init
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1000-0x103f] could not be reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x1040-0x104f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: [io 0x0cf0-0x0cf1] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0303 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f13 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0400 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: [dma 2]
    Nov 21 14:17:03 PingBuild kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0700 (active)
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [io 0x1060-0x107f] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: [mem 0xd0200000-0xd03fffff] has been reserved
    Nov 21 14:17:03 PingBuild kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 21 14:17:03 PingBuild kernel: pnp: PnP ACPI: found 10 devices
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [io 0x1000-0x0fff] to [bus 08] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [io 0x1000-0x0fff] to [bus 09] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [io 0x1000-0x0fff] to [bus 0a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [io 0x1000-0x0fff] to [bus 0e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [io 0x1000-0x0fff] to [bus 0f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [io 0x1000-0x0fff] to [bus 10] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [io 0x1000-0x0fff] to [bus 11] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [io 0x1000-0x0fff] to [bus 12] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [io 0x1000-0x0fff] to [bus 16] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [io 0x1000-0x0fff] to [bus 17] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [io 0x1000-0x0fff] to [bus 18] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bridge window [io 0x1000-0x0fff] to [bus 19] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: bridge window [io 0x1000-0x0fff] to [bus 1a] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: bridge window [io 0x1000-0x0fff] to [bus 1d] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: bridge window [io 0x1000-0x0fff] to [bus 1e] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: bridge window [io 0x1000-0x0fff] to [bus 1f] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: bridge window [io 0x1000-0x0fff] to [bus 20] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: bridge window [io 0x1000-0x0fff] to [bus 21] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: bridge window [io 0x1000-0x0fff] to [bus 22] add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:0f.0: BAR 6: assigned [mem 0xc0000000-0xc0007fff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:10.0: BAR 6: assigned [mem 0xc0008000-0xc000bfff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: no space for [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:02:00.0: BAR 6: assigned [mem 0xd1010000-0xd101ffff pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: PCI bridge to [bus 02]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [io 0x2000-0x3fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xd1000000-0xd23fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:11.0: bridge window [mem 0xdc400000-0xdc9fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: PCI bridge to [bus 03]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [io 0x4000-0x4fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd2400000-0xd24fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.0: bridge window [mem 0xd4400000-0xd44fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: PCI bridge to [bus 04]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [io 0x8000-0x8fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd2800000-0xd28fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.1: bridge window [mem 0xd4800000-0xd48fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: PCI bridge to [bus 05]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [io 0xc000-0xcfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xd2c00000-0xd2cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.2: bridge window [mem 0xdcb00000-0xdcbfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: PCI bridge to [bus 06]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xd3000000-0xd30fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.3: bridge window [mem 0xdcd00000-0xdcdfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: PCI bridge to [bus 07]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xd3400000-0xd34fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.4: bridge window [mem 0xdcf00000-0xdcffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: PCI bridge to [bus 08]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xd3800000-0xd38fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.5: bridge window [mem 0xdd100000-0xdd1fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: PCI bridge to [bus 09]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xd3c00000-0xd3cfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.6: bridge window [mem 0xdd300000-0xdd3fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: PCI bridge to [bus 0a]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xd4000000-0xd40fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:15.7: bridge window [mem 0xdd500000-0xdd5fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: PCI bridge to [bus 0b]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [io 0x5000-0x5fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd2500000-0xd25fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.0: bridge window [mem 0xd4500000-0xd45fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: PCI bridge to [bus 0c]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [io 0x9000-0x9fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd2900000-0xd29fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.1: bridge window [mem 0xd4900000-0xd49fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: PCI bridge to [bus 0d]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [io 0xd000-0xdfff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd2d00000-0xd2dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.2: bridge window [mem 0xd4b00000-0xd4bfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: PCI bridge to [bus 0e]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd3100000-0xd31fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.3: bridge window [mem 0xd4d00000-0xd4dfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: PCI bridge to [bus 0f]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd3500000-0xd35fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.4: bridge window [mem 0xd4f00000-0xd4ffffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: PCI bridge to [bus 10]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd3900000-0xd39fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.5: bridge window [mem 0xd5100000-0xd51fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: PCI bridge to [bus 11]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd3d00000-0xd3dfffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.6: bridge window [mem 0xd5300000-0xd53fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: PCI bridge to [bus 12]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd4100000-0xd41fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:16.7: bridge window [mem 0xd5500000-0xd55fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: PCI bridge to [bus 13]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [io 0x6000-0x6fff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd2600000-0xd26fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.0: bridge window [mem 0xd4600000-0xd46fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: PCI bridge to [bus 14]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [io 0xa000-0xafff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xd2a00000-0xd2afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.1: bridge window [mem 0xdca00000-0xdcafffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: PCI bridge to [bus 15]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [io 0xe000-0xefff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xd2e00000-0xd2efffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.2: bridge window [mem 0xdcc00000-0xdccfffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: PCI bridge to [bus 16]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xd3200000-0xd32fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.3: bridge window [mem 0xdce00000-0xdcefffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: PCI bridge to [bus 17]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xd3600000-0xd36fffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.4: bridge window [mem 0xdd000000-0xdd0fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: PCI bridge to [bus 18]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xd3a00000-0xd3afffff]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.5: bridge window [mem 0xdd200000-0xdd2fffff 64bit pref]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: PCI bridge to [bus 19]
    Nov 21 14:17:03 PingBuild kernel: pci 0000:00:17.6: bri

    Trilby wrote:
    Thanks, that all sounds correct to me, unfortunalte I can't provide more help as I've never used vmware.  But a couple pointers for pacman use:
    There is no need to use that pipe, `pacman -Q <searchterm>` will work.
    The reason you don't see the mouse package is that grep is case sensitive.  `pacman -Q | grep -i vmware` should also show the mouse package, but this would be much easier as `pacman -Qs vmware` which allows pacman to do the search.  Pacman's search is case-insensitive by default and is a bit more effient that listing all packages and grepping through them.
    Got it. Yes using the 'vmware' the vmmouse shows up. Also searching 'svga' shows Mesa DRI drivers. That is another advantage for letting pacman search, since my search term was svga and what was dispalayed did not have that in the string, pacman search can see behind the covers. :-)
    All this learning is good, now if I could just figure out why 'startx' is failing to create screen resource. ;-)
    Question, does it matter what tty it starts on? I am using 0 (obvious from the log name), could that be an issue? Just thinking out loud.

  • Another failed upgrade form 40/10 to 80/20 - lost ...

    I signed up for BT Infinity Option 2 (unlimited) back in October 2011, and the service was installed, worked consistently well at around 28Mbs down / 5 Mbs up. So far so good.
    The BT website offered the option of upgrading from the 40/10 service to the 80/20 service for no charge providing that you agreed to extend your contract term to a new 18 months, so, on the 6th May, I did just that. During the ordering process, the system suggested that around 51Mbs would be a realistic download speed for my line on the new 80/20 service. 
    On the 9th May my order was marked as complete, the home hub and modem restarted themselves during the night, and come the morning... nothing. Same old 28Mbs speed. 
    The line needs to train up they say, so wait 10 days. Day 1 - 28Mps, Day 2 - 28.Mps....Day 10 28Mps. Same consistent 28Mps day in day out. 
    Surely if the line is training, I should expect to see some variation? Apparently not - it's 12 days for the training to complete, so wait longer. It makes no sense to me that I would see absolutely no variation in speed if the line was really training.
    I've been bounced around department to department, they've run multiple (un-necessary in my view) line tests, I'd swear they don't really listen anyway to what the problem is, but just go on a robotic 'speed issue blah blah' bender every time you call.
    I can't see a way out of this - no one will take end to end responsibility for my case. I can't bear to call them again and jump through the same hoops of resetting, testing and explaining the situation for an hour or two just to end up with the same 'sorry - can't help you'.

    Well, I spend an hour or so on the 'chat' with the help team last weekend, testing, rebooting, replugging and was left with yet another - give it 24 more hours. He promised to go away and check with the Billing Team, Order Management Desk and Customer Options team to see if there was anything blocking the migration and call me back the next day.
    Guess what? A full week later - no phone call, no difference.
    This is woeful customer service - I feel like a victim of fraud - being duped into an extension to the contract when BT has neither the means or the desire to deliver the service. I understand things don't always go smoothly, but for the love of god, it should not be *this* difficult to have something done about it.
    Transcript of the last conversation posted in the hope someone else will find it useful...
    Vinay Kulkarni: Hello. I'm Vinay Kulkarni. Thanks for that information, I'll check it and get back to you in a moment.
    Vinay Kulkarni: Hello David.
    David Thompson: Hi
    David Thompson: The BT website offered the option of upgrading from the 40/10 service to the 80/20 service for no charge providing that you agreed to extend your contract term to a new 18 months, so, on the 6th May, I did just that (Order No. BTCDxxxxxx8). During the ordering process, the system suggested that around 51Mbs would be a realistic download speed for my line on the new 80/20 service. It also informed me that the new service would be activated within 3 working days, and there would be a short interruption to my service overnight.
    David Thompson: I have repeatedly run speedtest.net sessions on the line, and, while I understand that during the initial 10 day 'training' period, line speed will fluctuate, at no point what so ever, has the line speed every increased above the 28Mbs download, which also suggests to me that I have not been migrated onto the new platform, or an artificial cap is somehow being applied. It is now 10 days since the migration was completed, so the training period will now be complete, and still - not a single result above 28Mps.
    Vinay Kulkarni: Good Morning. I am afraid that I have not been trained on BT Infinity concerns. However, there is a specialized team who will be able to assist you in regard to the above query. Would you like to speak to them?
    David Thompson: Yes
    Vinay Kulkarni: I will transfer your chat now.
    Vinay Kulkarni has disconnected.
    Atanu : Hello. I'm Atanu . Thanks for that information, I'll check it and get back to you in a moment.
    David Thompson: Hi - can you see the 'old' conversation above before I was transferred, or do I need to copy and paste it for you?
    Atanu : Hi David, I am just reading it. Please give me a minute.
    David Thompson: okay - no problem.
    David Thompson: I should add that the 28Mps download I refer to has been the steady speed that I achieved ever since BT infinity (40/10) service was first installed in 2011.
    Atanu : Ok David, I really apologise for the inconvenience. Please don't worry, I will take care of the issue and solve it for you.
    Atanu : I'm just waiting for your account details to load. Won't be long.
    Atanu : Thank you for your patience David. I will check the line and resolve it for you.
    David Thompson: ok - I just really want to know if the account has been upgraded - I don't think the line is 'faulty' as I get the 28Mbs consistently - I just think it's capped.
    Atanu : Yes, the account has been upgraded on 09/05/2012 and it is not capped at all. Please tell me are you at your home as I need to perform some tests in the line to identify the fault and solve the issue.
    David Thompson: I am at home - are you saying it has been upgraded to the 80/20 service from the 40/10 service?
    Atanu : Yes. Now I will check out where is the fault.
    David Thompson: okay
    Atanu : Normally it is the first 10 to 12 days when the connection sets in a stabilisation period.
    David Thompson: I understand that, but the speed before the upgrade was a consistent 28mbs; the speed after the upgrade (and during the stabilisation period) was a consistent 28Mps - to me, it looks like nothing has changed.
    Atanu : Yes, that is the issue I want to check properly.
    David Thompson: okay but please don't tell me to wait *another* 10-12 days to see if it makes a difference -
    which is the ONLY reply I have had to date.
    Atanu : No, you do not have to wait for more than 2 days.
    David Thompson: I really do not think this is a stabilisation issue - if it where I would have seen performance both better and worse than the original 28Mps.
    David Thompson: I remain convinced that there is no fault on my line, rather I simply have either not been migrated at all, or migrated back on to my original service by accident, or only partially migrated and some settings remain set that are limiting my speed to that of the 40/10 service.
    Atanu : Do you any VPN in the Bt connection?
    David Thompson: Does your system make a distinction between the two Infinity services - ie. the 40/10 service and the new 80/20 service? I note the order (BTCDxxxxxx8) makes reference to the 40/10 service - which is the one I was already on.
    David Thompson: No VPN
    Atanu : Ok. Please restart the BT Home Hub by press the power button
    Atanu : Wait for 5 seconds and restart it.
    David Thompson: I will lose this conversation won't I?
    Atanu : No, you will not. I am assuring it. Don't wait for more than 10 seconds.
    David Thompson: okay - just the home hub, not the white 'modem' box too?
    Atanu : Both.
    David Thompson: okay - doing it now.
    Communication with the RightNow Chat service has been lost. Please wait while attempts are made to restore the connection.
    Disconnection in 240 seconds. Connection resumed.
    Atanu : If the chat disconnects. David Thompson: done
    Atanu : Thank you. Wait till the lights be steady.
    David Thompson: t
    David Thompson: it's all back and lights are steady (well apart from the Lan1 one, but that's to be expected)
    Atanu : Ok. Please check if the speed is better now?
    David Thompson: speed is still the exact same 28Mbs
    Atanu : It is a wired connection you are using. Right?
    David Thompson: wired or wireless, it makes no difference - both report the same.
    Atanu : But is it a wired connection now?
    David Thompson: I'll test again with the laptop - give me 1 min
    Atanu : Thank you.
    David Thompson: 27.71Mbs with a laptop plugged directly into the homehub
    Atanu : Please tell me the operating system in the computer?
    David Thompson: That one is Windows 7
    Atanu : Thank you. The system is saying the speed is being devided.
    David Thompson: Divided?
    Atanu : May I close the wireless connection for some time?
    David Thompson: What do you mean by divided?
    Atanu : The connection is been shared by more than one computer .
    David Thompson: Well of course it is! Which is why I normally do all my test very early in the morning when I am the only user (I have three kids!). My early morning tests are where I'm basing my 28Mbs from
    David Thompson: Do you want me to disconnect all wired and wireless users and re-test?
    Atanu : Yes. Please keep just 1 computer connected and check the speed through BT Speed tester.
    David Thompson: okay - this chat will temporarily disconnect again then.
    Atanu : Can we keep this computer connected?
    Communication with the RightNow Chat service has been lost. Please wait while attempts are made to restore the connection.
    Disconnection in 240 seconds.
    Connection resumed.
    David Thompson: Hmm - that did not work.
    David Thompson: When I disabled wireless on the hub (from the wired connection) the hub just froze and I needed to power down to get it back to life
    David Thompson: I'l get a longer cable!
    Atanu : Ok. Please take your time.
    David Thompson: Are you able to disable wireless from your end - each time I do it here the hub hangs. I've taken off all other Wired connections?
    David Thompson: And it will be via the laptop, so which connection will die when you kill wireless
    David Thompson: so you will need to turn it on again within the 240 seconds
    David Thompson: That said, the wireless connections are not doing much at all at the moment - they certainly won't be consuming any significant bandwidth
    Atanu : Ok.
    David Thompson: Do you want me to run speed test now or wait until you kill the wireless - it's all iPad and iPod
    doing nothing on the wireless - this PC and the other one sitting idle next to me, so no real activity? Atanu : Not an issue. Please run the speedtester now.
    David Thompson: 29.3Mbs down / 4.51 Mps up from the wired laptop connected to the Hub
    Atanu : Thank you.
    Atanu : David, I will run some line tests now. Please make it sure that nobody is using the landline for next 7 minutes.
    David Thompson: okay
    Atanu : Hello David, have you faced any connection dropping issue apart from the slow speed?
    David Thompson: No - the line has been perfect - no latency issue, solid connections. The only issue is I have not seen any increase in speed above the 38Mbs. I honestly don't think it's a faulty line.
    David Thompson: Which is why I think the migration has failed in some way - I'm sure somewhere in the system there is a flag saying that I'm still in the 40/10 service and that's capping throughput
    David Thompson: Even the older BT speed checker thinks I should be expecting around 29Mbs against the 51Mps the 80/20 service thought I should get, so it is picking that number up from somewhere.
    Atanu : Ok. the system is showing that this is the maximum speed you will get.
    David Thompson: Why did the upgrade process suggest 51mbs for the 80/20 system then?
    David Thompson: If 29 is all I will every get, why extend the contract on the basis of the 51mbs?
    Atanu : It is the speed available in Exchange. The engineers check the speed in your premises before they provide the Infinity service. But since the line is in the last day of stabilisation, I request
    Atanu : You to wait for just 1 more day and check the speed. I will call you tomorrow by teh same time to check the speed.
    David Thompson: I'm not clear on this. There are two service levels of BT Infinity yes? the 40/10 service and the 80.20 service?
    David Thompson: *80/20
    Atanu : Yes.
    David Thompson: I've been on the 40/20 system since 2011; The theoretical maximum at time of order was around 30Mps and I've always got around 28Mps on that service. That's fine. Now when I placed the order for the 80/20 upgrade, the theoretical max was 51mps, so I'm pretty certain I would see some reasonable speed increase above the 28Mbs. The fact that I have not seen *any* uplift (even 5-10Mps) at *any* time - especially during quiet periods seems really odd to me.
    David Thompson: So I think there is a problem there. If however, it turns out that the prediction system is so really awful and can get is so wrong (when it used to be reasonably accurate), then why trick me in to extended my contract for no reason.
    David Thompson: I don't think BT would do the latter, so I'm convinced (still) its just a problem of the migration.
    David Thompson: I'll wait another 24 hours, but I don;t think this is going to fix itself.
    Atanu : Ok. in that case you need to confirm it form the Billing section as the migration first shows in the Billing. Atanu : I will call you tomorrow
    David Thompson: okay
    Atanu : And confirm with the Billing team, the Order Management Desk, Customer Options Team that if there is
    any issue in the migration.
    David Thompson: Just to be clear - you are going to check with the other teams yeah? Not me?
    Atanu : Please tell me at what time should I call you?
    Atanu : Yes. I will.
    David Thompson: Anytime after 7am is fine by me
    Atanu : ok. all the teams open after 9 am.
    David Thompson: Okay - I'll await your call after 9am; Thanks for your help and patience on this.
    Atanu : Thank you for your patience. It is our responsibility to provide you the proper speed.
    David Thompson: Okay - until tomorrow - bye-bye
    You have disconnected. 

  • The right mouse button on my 8740w has failed (clicks but no result, i.e Cut/Copy/Paste/Delete menu

    My right mouse button clicks but no result, i.e Cut/Copy/Paste/Delete menu does not appear.
    I think the hardware has failed.
    Note the mousepd is not the issue.  The right button is the problem
    Left button works fine

    Same deal with me except the right button has failed twice. You may find that if you push on it past the click with a bit more force it will respond. They swapped the hardware and same thing occurred.
    HP should be ashamed that they would put such awful mouse hardware on its flagship product. Whoever designed it should be fired.
    If HP had any customer loyalty they would offer a hardware update and offer it to those who are still under warranty.
    Suffice to say I will never, ever purchase an HP workstation again.
    Good luck.

  • Intel iMac with failed LogicBoard - can I use it as display for my MacMini?

    I have a Intel iMac with failed logic board (the display comes up while booting sometimes and sometimes, it doesn't). I bought a Mac Mini afterwards. I connected it to a Dell monitor with HDMI and the results aren't great. I experience interminttent video losses (Grains on screen every 1 minute or so).
    So, I am now thinking about using my failed intel Imac as a display. Will it work?

    No, the failed imac is dead until you replace the logic board.

  • Call failed

    I am having an intermittant problem with calls failing.
    It happened several days ago, when trying to call a number I call often. I kept getting "call failed" (I tried numerous times to call). I tried powering phone off and on, and reseating sim card. Nothing worked. I gave up. When I called same number several hours alter, it was fine.
    This morning I tried to return a call from a client - not a number programmed into my contacts - I just hit return call from a message she had left. I got call failed repeatedly. I powered phone off and on and tried dialing number from keypad. No luck. I gave up, got a cup of tea, then tried again and it went through fine.
    Also - with both of these - when i couldn't place call, I tried another number and call went through fine, But when I went back to number I was trying to reach, "call failed"
    Any ideas? Once I chalked up to a fluke, but now it's been twice in several days. I was near an apple store wed night and asked the guy in the genius bar - he told me that my address book was probably corrupt on my computer and I should reinstall - but this morning's "call failed" number isn't in my address book.
    Katie

    If it is believed that something regarding the contact is corrupt in the address book, I would think it would always fail on that particular contact. However, the next step in troubleshooting, since you said you already tried powering the phone off/on, is to do a reset. Hold the Home button and the sleep/wake button together, wait until you see the Apple logo and then release. The phone will restart. If that doesn't seem to correct the error, the next step would be a restore. Connect the phone to iTunes, make sure you sync first so you get a current backup file. Then press the restore button. You can do it from a backup first. If that doesn't correct it, then restore as a new phone, and then sync your information back. If that doesn't do it, then an appointment at the Genius bar would be in order. As far as the genius bar goes though, I saw you were there, but didn't say what they might have done.
    Hope this helps you.

  • T440s and System Restore "Recovery Failed"

    I bought recently T440s with 16GB cache drive and 500GB disk. I had been able to install new SSD (Samsung 840 EVO 500GB) but I cannot restore Lenovo system from Disks. 
    I had to copy disks to USB drive because T440s don't have optical drive. Laptop is booting from USB but once I'm accepting aggreement (EULA) I have information "Recovery Failed".
    I have exactly same problem like here: 
    https://forums.lenovo.com/t5/T400-T5...g/td-p/1250937
    I disconnect M.2 16GB mSATA drive but still same error: Recovery failed. Do I have to use external DVD drive ?
    Solved!
    Go to Solution.

    Hi,
    Are you talking about Lenovo factory recovery media?
    I've tried copying Lenovo recovery media to USB flash drive to do a recovery - using every trick I could think of - and always failed   It may be possible, but I'm not the only one who has tried without success. I don't think the recovery software will run correctly when booted that way.
    An external DVD drive may be your only hope.
    Z.
    The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc.  The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • G5 Superdrive failing?

    Never had a problem with my Superdrive until last night.
    It started first when I tried to burn a CD of some Mp3s. The drive would open, then shut almost imediately, then iTunes would hang, and it would take multiple Force Quits to get it to quit.
    I rebooted, then tried to just mount a piece of media to burn a data CD.
    Whenever I try to open the drive to insert media, it will open off the keyboard, then almost immediately it will shut, making it impossible to get a piece of media in it.
    Do you think the drive is failing? It seems more like a software thing as, as it was originally making iTunes crash.
    Again, I never had a single issue with it until yesterday.

    Matthias,
    I never knew Media Access Control chips needed batteries:
    http://discussions.apple.com/click.jspa?searchID=-1&messageID=2441666
    Anyway, your mileage may vary on batteries. It is true some machines don't need new clock batteries much longer than others.

  • Failed 10.5.4 installation

    My 10.5.4 installation got stuck on "writing package receipt". About says I have 10.5.4 but I checked the booms folder and the com file isn't there. But I think 10.5.3 failed back when too (the com file is also missing). I want to download the combo file to update it but what should I do regarding 10.5.3?
    Should I:
    a) Download .3 combo file and install that and then download .4 and install it?
    OR
    b) Only download and install .4
    Thanks!

    Welcome to the Apple forums:
    When the 10.5.3 failed, it was a warning that something was wrong. Never update a system that does not run perfectly.
    That being said, if you download the huge combo 10.5.4 update which includes all previous updates, it might help.
    Here's the link:
    http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1054comboupdate .html
    Again, never go past a step that fails. Always fix things as they show up - they only get worse with time and eventually bite.

Maybe you are looking for