X11 Won't start with auto mode ..[SOLVED]

HI all,
First of all let me say that Archlinux is an awsome distribution, got my laptop installed with kdemod in no time flat.
very fast running KDE on my aging (7 yr old laptop) ..
I am now trying to install on our family computer which has an nvidia based graphic card. I had a problem trying out my
new installation (using nvidia driver, not nv) bombing with an error when trying startx.
The error was basically saying that the xorg auto-mode determination was not working. If I put a manual mode like "1024x768" in my
xorg.conf file it works fine. It  seems like the EDID detection on my Viewsonic monitor is not working.
I would like to run my monitor at higher resolutions than above, Is there a way to force EDID detection to work, or any other way to get
my monitor to display higher resolutions?
Many Thanks,
Bernie
Last edited by bmentink (2009-08-26 08:16:08)

I looked up all the resolution for the Viewsonic monitor, put them in as "Mode" , but Xorg refuses to load any of them except 1024x768.
I even tried an old xorg.conf that used to work just fine at 1680x1050 on a DreamLinux install, but refuses to with the nvidia driver installed with pacman.
In the log file, X complains that it doesn't have enough bandwidth to support the higher resolutions ..
Anyone have any other ideas .. this is nuts!
Cheers,
Bernie

Similar Messages

  • X11 won't start

    Ever since upgrading to Leper, X11 won't start. If I open the console window, the following is logged repetitively, which looks like an invalid start command that is followed by command line help. Anybody know what I can do to fix this?
    Console output:
    7/16/08 10:14:06 PM org.x.X11[404] X11.app = /usr/X11/X11.app/Contents/MacOS/X11
    7/16/08 10:14:06 PM org.x.X11[404] Unrecognized option: -launchd
    7/16/08 10:14:06 PM org.x.X11[404] use: X [:<display>] [option]
    7/16/08 10:14:06 PM org.x.X11[404] -a # mouse acceleration (pixels)
    7/16/08 10:14:06 PM org.x.X11[404] -ac disable access control restrictions
    7/16/08 10:14:06 PM org.x.X11[404] -audit int set audit trail level
    7/16/08 10:14:06 PM org.x.X11[404] -auth file select authorization file
    7/16/08 10:14:06 PM org.x.X11[404] -br create root window with black background
    7/16/08 10:14:06 PM org.x.X11[404] +bs enable any backing store support
    7/16/08 10:14:06 PM org.x.X11[404] -bs disable any backing store support
    7/16/08 10:14:06 PM org.x.X11[404] -c turns off key-click
    7/16/08 10:14:06 PM org.x.X11[404] c # key-click volume (0-100)
    7/16/08 10:14:06 PM org.x.X11[404] -cc int default color visual class
    7/16/08 10:14:06 PM org.x.X11[404] -co file color database file
    7/16/08 10:14:06 PM org.x.X11[404] -core generate core dump on fatal error
    7/16/08 10:14:06 PM org.x.X11[404] -dpi int screen resolution in dots per inch
    7/16/08 10:14:06 PM org.x.X11[404] dpms enables VESA DPMS monitor control
    7/16/08 10:14:06 PM org.x.X11[404] -dpms disables VESA DPMS monitor control
    7/16/08 10:14:06 PM org.x.X11[404] -deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
    7/16/08 10:14:06 PM org.x.X11[404] -f # bell base (0-100)
    7/16/08 10:14:06 PM org.x.X11[404] -fc string cursor font
    7/16/08 10:14:06 PM org.x.X11[404] -fn string default font name
    7/16/08 10:14:06 PM org.x.X11[404] -fp string default font path
    7/16/08 10:14:06 PM org.x.X11[404] -help prints message with these options
    7/16/08 10:14:06 PM org.x.X11[404] -I ignore all remaining arguments
    7/16/08 10:14:06 PM org.x.X11[404] -ld int limit data space to N Kb
    7/16/08 10:14:06 PM org.x.X11[404] -lf int limit number of open files to N
    7/16/08 10:14:06 PM org.x.X11[404] -ls int limit stack space to N Kb
    7/16/08 10:14:06 PM org.x.X11[404] -nolock disable the locking mechanism
    7/16/08 10:14:06 PM org.x.X11[404] -logo enable logo in screen saver
    7/16/08 10:14:06 PM org.x.X11[404] nologo disable logo in screen saver
    7/16/08 10:14:06 PM org.x.X11[404] -nolisten string don't listen on protocol
    7/16/08 10:14:06 PM org.x.X11[404] -noreset don't reset after last client exists
    7/16/08 10:14:06 PM org.x.X11[404] -reset reset after last client exists
    7/16/08 10:14:06 PM org.x.X11[404] -p # screen-saver pattern duration (minutes)
    7/16/08 10:14:06 PM org.x.X11[404] -pn accept failure to listen on all ports
    7/16/08 10:14:06 PM org.x.X11[404] -nopn reject failure to listen on all ports
    7/16/08 10:14:06 PM org.x.X11[404] -r turns off auto-repeat
    7/16/08 10:14:06 PM org.x.X11[404] r turns on auto-repeat
    7/16/08 10:14:06 PM org.x.X11[404] -render [default|mono|gray|color] set render color alloc policy
    7/16/08 10:14:06 PM org.x.X11[404] -s # screen-saver timeout (minutes)
    7/16/08 10:14:06 PM org.x.X11[404] -sp file security policy file
    7/16/08 10:14:06 PM org.x.X11[404] -su disable any save under support
    7/16/08 10:14:06 PM org.x.X11[404] -t # mouse threshold (pixels)
    7/16/08 10:14:06 PM org.x.X11[404] -terminate terminate at server reset
    7/16/08 10:14:06 PM org.x.X11[404] -to # connection time out
    7/16/08 10:14:06 PM org.x.X11[404] -tst disable testing extensions
    7/16/08 10:14:06 PM org.x.X11[404] ttyxx server started from init on /dev/ttyxx
    7/16/08 10:14:06 PM org.x.X11[404] v video blanking for screen-saver
    7/16/08 10:14:06 PM org.x.X11[404] -v screen-saver without video blanking
    7/16/08 10:14:06 PM org.x.X11[404] -wm WhenMapped default backing-store
    7/16/08 10:14:06 PM org.x.X11[404] -wr create root window with white background
    7/16/08 10:14:06 PM org.x.X11[404] -x string loads named extension at init time
    7/16/08 10:14:06 PM org.x.X11[404] -maxbigreqsize set maximal bigrequest size
    7/16/08 10:14:06 PM org.x.X11[404] +xinerama Enable XINERAMA extension
    7/16/08 10:14:06 PM org.x.X11[404] -xinerama Disable XINERAMA extension
    7/16/08 10:14:06 PM org.x.X11[404] -dumbSched Disable smart scheduling, enable old behavior
    7/16/08 10:14:06 PM org.x.X11[404] -schedInterval int Set scheduler interval in msec
    7/16/08 10:14:06 PM org.x.X11[404] +extension name Enable extension
    7/16/08 10:14:06 PM org.x.X11[404] -extension name Disable extension
    7/16/08 10:14:06 PM org.x.X11[404] -query host-name contact named host for XDMCP
    7/16/08 10:14:06 PM org.x.X11[404] -broadcast broadcast for XDMCP
    7/16/08 10:14:06 PM org.x.X11[404] -multicast [addr [hops]] IPv6 multicast for XDMCP
    7/16/08 10:14:06 PM org.x.X11[404] -indirect host-name contact named host for indirect XDMCP
    7/16/08 10:14:06 PM org.x.X11[404] -port port-num UDP port number to send messages to
    7/16/08 10:14:06 PM org.x.X11[404] -from local-address specify the local address to connect from
    7/16/08 10:14:06 PM org.x.X11[404] -once Terminate server after one session
    7/16/08 10:14:06 PM org.x.X11[404] -class display-class specify display class to send in manage
    7/16/08 10:14:06 PM org.x.X11[404] -cookie xdm-auth-bits specify the magic cookie for XDMCP
    7/16/08 10:14:06 PM org.x.X11[404] -displayID display-id manufacturer display ID for request
    7/16/08 10:14:06 PM org.x.X11[404] -kb disable the X Keyboard Extension
    7/16/08 10:14:06 PM org.x.X11[404] +kb enable the X Keyboard Extension
    7/16/08 10:14:06 PM org.x.X11[404] [+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask] ] ] ]
    7/16/08 10:14:06 PM org.x.X11[404] enable/disable accessx key sequences
    7/16/08 10:14:06 PM org.x.X11[404] -ardelay set XKB autorepeat delay
    7/16/08 10:14:06 PM org.x.X11[404] -arinterval set XKB autorepeat interval
    7/16/08 10:14:06 PM org.x.X11[404] Device Dependent Usage:
    7/16/08 10:14:06 PM org.x.X11[404] -fakebuttons : fake a three button mouse with Command and Option keys.
    7/16/08 10:14:06 PM org.x.X11[404] -nofakebuttons : don't fake a three button mouse.
    7/16/08 10:14:06 PM org.x.X11[404] -fakemouse2 <modifiers> : fake middle mouse button with modifier keys.
    7/16/08 10:14:06 PM org.x.X11[404] -fakemouse3 <modifiers> : fake right mouse button with modifier keys.
    7/16/08 10:14:06 PM org.x.X11[404] ex: -fakemouse2 "option,shift" = option-shift-click is middle button.
    7/16/08 10:14:06 PM org.x.X11[404] -keymap <file> : read the keymapping from a file instead of the kernel.
    7/16/08 10:14:06 PM org.x.X11[404] -version : show the server version.
    7/16/08 10:14:06 PM org.x.X11[404] Quartz modes:
    7/16/08 10:14:06 PM org.x.X11[404] -fullscreen : run full screen in parallel with Mac OS X window server.
    7/16/08 10:14:06 PM org.x.X11[404] -rootless : run rootless inside Mac OS X window server.
    7/16/08 10:14:06 PM org.x.X11[404] -quartz : use default Mac OS X window server mode
    7/16/08 10:14:06 PM org.x.X11[404] Options ignored in rootless mode:
    7/16/08 10:14:06 PM org.x.X11[404] -size <height> <width> : use a screen resolution of <height> x <width>.
    7/16/08 10:14:06 PM org.x.X11[404] -depth <8,15,24> : use this bit depth.
    7/16/08 10:14:06 PM org.x.X11[404] -refresh <rate> : use a monitor refresh rate of <rate> Hz.
    7/16/08 10:14:06 PM org.x.X11[404] Fatal server error:
    7/16/08 10:14:06 PM org.x.X11[404] Unrecognized option: -launchd
    7/16/08 10:14:06 PM org.x.X11[404] AbortDDX
    7/16/08 10:14:06 PM org.x.X11[404] Quitting Xquartz...
    7/16/08 10:14:18 PM com.apple.launchd[101] (org.x.X11[404]) Exited with exit code: 1

    I too am having this problem. People are all reporting different causes.
    The cause might be solved by this solution at MacOSXHints.com
    http://www.macosxhints.com/article.php?story=20080622105055862
    They sugguest removing the -launchd boot option from your Xorg plist file. I did this and it did not fix the problem for me, I still get the Unrecognized option: -launchd. But other users have reported success, so it's worth a shot.
    You might also look into what the guys in this thread (http://discussions.apple.com/thread.jspa?threadID=1402209&tstart=205) did to try to solve launching problems.

  • My PC won't start with only one push of the start button.

    hi guys my pc won't start with only one push of the start button. It takes me 1 to 10 pushes for it to start. I encountered this main bios error once when my pc started but it fixed on its own. What could be the problem?

    Hi
    The problem can be fixed by running a latest BIOS Update on your unit or if it is a mechanical issue it could be the power button itself.. you can call HP tech support if the notebook is still in warranty.. they'll be able to help you.
    Hope this helps.
    ***** Click the KUDOS Thumbs UP (Like) on the left to say 'Thanks'*****
    ****Make it easier for other people to find solutions, by marking my answer “Accept as Solution”&"Kudos"if it solves your problem.****
    -VJ
    Although I am an HP Employee, I am speaking for myself and not for HP.

  • Start with Advanced mode in Query Panel

    JDev 11.1.1.5.0 ADF BC
    I have a query panel in my form with table made from View Criteria.
    When runs, it starts with Basic mode.
    I want this to be changed to start with Advanced mode straight away.
    Is that possible?

    Hi,
    Edit the ViewCriteria. In the UI Hints tab set Search Region Mode to Advanced.
    Kevin
    Message was edited by: KevinAngus - you beat me Timo!

  • Managed server is not starting with MSI mode

    Managed server not starting with MSI mode even though we enabled the managed server independence mode
    Started the admin server and managed server first time enabled the MSI mode.
    Restarted all admin and Managed server.
    We have tested the following scenarios
    scenarios1: Stopped the Admin server and restarted the Managed server with MSI mode it comes up.
    scenarios2:Admin server is running but not able to connect to the managed server
    In this scenario
    we have removed the Network cable and restarted the managed server its throwing ldap error.
    <Aug 14, 2010 1:58:32 PM SGT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: failed to connect to server ldap://sgppsr00383:16827 (91)
    at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:515)
    at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:435) at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:274)
    at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:199)
    at netscape.ldap.LDAPConnThread.connect(LDAPConnThread.java:109)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1083) at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:954)
    at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:781)
    at weblogic.ldap.EmbeddedLDAPConnection.getAndInitDelegate(EmbeddedLDAPConnection.java:2031)
    at weblogic.ldap.EmbeddedLDAPConnection.add(EmbeddedLDAPConnection.java:1065) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.addEntry(DefaultCredentialMapperLDAPHelper.java:537)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.createOrgUnit(DefaultCredentialMapperLDAPHelper.java:432)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.verifyHierarchy(DefaultCredentialMapperLDAPHelper.java:407)
    at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.<init>(DefaultCredentialMapperLDAPHelper.java:146) at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:112)
    at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340) at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461) at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854) at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    - with nested exception:
    Managed server looking for ldap configuration from admin server.
    I have checked the all configuration file same on both managed server and admin server.
    Please let me know How to recover the managed server in this scenario.
    Edited by: user10773210 on Aug 16, 2010 11:55 PM
    Edited by: user10773210 on Aug 17, 2010 2:38 AM

    thanks for the reply....
    the managed server is pointing to jrokit_160_22_D1.1.1-3 jdk....the server has enough ram also...while running the managed server showing status 'STARTING' for long period of time...and the admin server health goes 'Warning' because of threadpool....when we stop the managed server then adminserver health becomes ok...

  • IMac won't start in Target Mode

    I'd like to retrieve some large files from my older Intel iMac, but it won't start in Target Mode. It ignores the key and starts normally. Any thoughts appreciated.

    Zap the PRAM and Reset the SMC, then try getting into TDM. Otherwise, see transfer files for other connection options.

  • Macbook Pro about 2012 won't start with out power lead in and runs very very slow Maverick OS

    Macbook Pro about 2012 won't start with out power lead in and runs very very slow Maverick OS?

    Take each of these steps as needed, and check to make sure it hasn't been fixed with a reboot afterwards before trying the next step.
    Backup your data if you haven't already:
    https://discussions.apple.com/docs/DOC-1992
    If you use Airplay, see https://discussions.apple.com/docs/DOC-6831
    If you don't use Airplay, be sure to upgrade to 10.9.2, using this update:
    http://support.apple.com/kb/DL1726
    Make sure your hard drive is not over 85% full.
    Make sure Spotlight is not indexing.
    Make sure Time Machine is not running when you do other tasks.
    Check to make sure you have not accidently/purposefully installed MacKeeper, as it will slow down your Mac:
    https://discussions.apple.com/docs/DOC-3036
    Remove any other system cache cleaning applications.
    Reset the SMC:
    http://support.apple.com/kb/ht3964
    Reset the PRAM:
    http://support.apple.com/kb/ht1379
    Check to make sure there aren't any signs the power adapter might be damaged, or the wrong one*:
    http://www.macmaps.com/frayguide.html
    If there are still issues, you may need to replace the battery:
    https://www.apple.com/batteries/replacements.html

  • SatelliteU300 Won't start with AC power connected and fully charged battery

    I just bought a U300-13U. It works great when battery is charging and AC is connected. However if left to charge up fully it won't start with AC connected. Unpluging the power or removing the battery and running on AC makes it work fine. Is this a 'feature' to stop overcharging or overheating the battery, or just a problem with this machine. I want to run with AC and battery both connected all the time as I have done with all my other laptops.
    Any help appreciated.

    Hello Andy
    Friend of mine has this small U300 and everything work well. I have had it few weeks ago to test WXp installation and it works perfectly.
    Please test it again very carefully and if the same happen again I recommend you to contact Authorized service partner in your country. Let them check your notebook. I must be honest and say that described issue sounds strange to me and please do not wait too long. Contact service as soon as possible.
    Bye and good luck!

  • [Solved] Audition won't start with [...\Preferences.cpp-253] error on windows 7/vista x64.

    Hi! You have really nice support for Audition - 3 pages of problems here and no solution. Just kidding
    So i've decided to help those poor users, that encounter the following problem (it may (or may not) arise after installing Adobe CS* with Audition already installed on the system)):
    Adobe Audition crashes at start with the following error:
    [\premiere2.0\Backend\Src\Core\Preferences.cpp-253]
    After applying the Windows XP compatibility mode error chages to:
    Adobe Audition could not find a supported audio device. Please check your device settings.
    Then it crashes like before.
    Uninstalling Adobe Premiere won't help, by the way.
    This problem is somehow related to the audition_settings.xml file in the Data folder and deleting this file solves the problem. You can aslo delete the whole folder - it will be created again on a next Adobe Audition start. Here is the path:
    C:\Users\[Your Username]\AppData\Roaming\Adobe\Audition\3.0\audition_settings.xml
    Some technical data on my system:
    OS: Windows Server 2008 R2 (don't be confused - it is in every way identical to Windows 7 x64, at least for Adobe products). I have a strong feeling that Vista x64 users may encounter that too.
    Installed Adobe products:
    1. Adobe Audition
    2. Adobe Master Suite CS5 (without premier)
    3. Adobe Acrobat X
    I hope that my post will help you solve the error in the next release!

    the primary hard disk self test fail at 01%

  • X11 won't start (sets monitor to standby) with nVidia card

    Hello everyone!
    I'm having some trouble getting my computer to work properly. Yesterday it was working perfectly, but today it would't start again. After some troubleshooting I've determined that the problem lies with X11 and the graphics driver. The bootloader, grub, and arch itself, boots perfectly in runlevel 3, but the moment you run "startx" it would appear to be loading for a while and finally the screen goes to standby mode and there is no way out of that other than reseting the computer using the reset button. I've tried uninstalling the nvidia drivers and installing nouveau drivers, but it still won't start X, this time arround, it would just hang up with a white screen.
    I've also tried removing xorg.conf and also using nvidia utility to generate a new one, but neither seems to work.
    /var/log/Xorg.0.log doesn't report any errors, it just gives different info from the configuration and the graphics card and just ends there.
    I've tried booting with a debian live USB but it would't boot either (the computer would just restart). I've also tried a Kubuntu live USB, this time arround, it would start to boot but the graphics appeared to be corrupted (strange colored noise all over the screen) and eventually it would just hang up. Using nomodeset Kubuntu finally booted (using vesa I guess?), but the same didn't work in Arch (I'm guessing because I have the nvidia drivers installed instead of nouveau).
    In conclussion, something appears to be wrong with the graphics card, I dont't know if it's a software problem or a hardware problem, as it started from one day to the other, without any upgrades in between, and it just doesn't work in any of the 3 distributions I've tested.
    Any suggestions in what to do to troubleshoot this?
    Thanks in advance,
    Santiago.-

    Xorg.0.log
    [ 35.560]
    X.Org X Server 1.14.4
    Release Date: 2013-10-31
    [ 35.560] X Protocol Version 11, Revision 0
    [ 35.560] Build Operating System: Linux 3.11.6-1-ARCH x86_64
    [ 35.561] Current Operating System: Linux arch 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
    [ 35.561] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    [ 35.562] Build Date: 01 November 2013 05:10:48PM
    [ 35.562]
    [ 35.562] Current version of pixman: 0.30.2
    [ 35.562] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 35.562] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 35.564] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 4 21:35:07 2013
    [ 35.576] (==) Using config file: "/etc/X11/xorg.conf"
    [ 35.576] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 35.577] (==) ServerLayout "Layout0"
    [ 35.577] (**) |-->Screen "Screen0" (0)
    [ 35.577] (**) | |-->Monitor "Monitor0"
    [ 35.577] (**) | |-->Device "Device0"
    [ 35.577] (**) |-->Input Device "Keyboard0"
    [ 35.577] (**) |-->Input Device "Mouse0"
    [ 35.577] (==) Automatically adding devices
    [ 35.577] (==) Automatically enabling devices
    [ 35.577] (==) Automatically adding GPU devices
    [ 35.603] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 35.603] Entry deleted from font path.
    [ 35.603] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 35.603] Entry deleted from font path.
    [ 35.603] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 35.603] Entry deleted from font path.
    [ 35.603] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 35.604] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 35.604] Entry deleted from font path.
    [ 35.604] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 35.604] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 35.604] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 35.604] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 35.604] (WW) Disabling Keyboard0
    [ 35.604] (WW) Disabling Mouse0
    [ 35.604] (II) Loader magic: 0x7fdc20
    [ 35.604] (II) Module ABI versions:
    [ 35.604] X.Org ANSI C Emulation: 0.4
    [ 35.604] X.Org Video Driver: 14.1
    [ 35.604] X.Org XInput driver : 19.1
    [ 35.604] X.Org Server Extension : 7.0
    [ 35.604] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 35.605] (--) PCI:*(0:1:0:0) 10de:0421:1682:2353 rev 161, Mem @ 0xfa000000/16777216, 0xd0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
    [ 35.606] Initializing built-in extension Generic Event Extension
    [ 35.606] Initializing built-in extension SHAPE
    [ 35.606] Initializing built-in extension MIT-SHM
    [ 35.606] Initializing built-in extension XInputExtension
    [ 35.606] Initializing built-in extension XTEST
    [ 35.607] Initializing built-in extension BIG-REQUESTS
    [ 35.607] Initializing built-in extension SYNC
    [ 35.607] Initializing built-in extension XKEYBOARD
    [ 35.607] Initializing built-in extension XC-MISC
    [ 35.608] Initializing built-in extension SECURITY
    [ 35.608] Initializing built-in extension XINERAMA
    [ 35.608] Initializing built-in extension XFIXES
    [ 35.608] Initializing built-in extension RENDER
    [ 35.608] Initializing built-in extension RANDR
    [ 35.609] Initializing built-in extension COMPOSITE
    [ 35.609] Initializing built-in extension DAMAGE
    [ 35.609] Initializing built-in extension MIT-SCREEN-SAVER
    [ 35.609] Initializing built-in extension DOUBLE-BUFFER
    [ 35.619] Initializing built-in extension RECORD
    [ 35.629] Initializing built-in extension DPMS
    [ 35.638] Initializing built-in extension X-Resource
    [ 35.647] Initializing built-in extension XVideo
    [ 35.656] Initializing built-in extension XVideo-MotionCompensation
    [ 35.665] Initializing built-in extension XFree86-VidModeExtension
    [ 35.673] Initializing built-in extension XFree86-DGA
    [ 35.682] Initializing built-in extension XFree86-DRI
    [ 35.690] Initializing built-in extension DRI2
    [ 35.690] (II) LoadModule: "glx"
    [ 35.757] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 36.111] (II) Module glx: vendor="NVIDIA Corporation"
    [ 36.111] compiled for 4.0.2, module version = 1.0.0
    [ 36.111] Module class: X.Org Server Extension
    [ 36.111] (II) NVIDIA GLX Module 325.15 Wed Jul 31 18:12:00 PDT 2013
    [ 36.126] Loading extension GLX
    [ 36.126] (II) LoadModule: "nvidia"
    [ 36.136] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 36.195] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 36.195] compiled for 4.0.2, module version = 1.0.0
    [ 36.195] Module class: X.Org Video Driver
    [ 36.197] (II) NVIDIA dlloader X Driver 325.15 Wed Jul 31 17:50:57 PDT 2013
    [ 36.197] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 36.197] (--) using VT number 2
    [ 36.248] (II) Loading sub module "fb"
    [ 36.248] (II) LoadModule: "fb"
    [ 36.259] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 36.270] (II) Module fb: vendor="X.Org Foundation"
    [ 36.270] compiled for 1.14.4, module version = 1.0.0
    [ 36.270] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.270] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 36.270] (II) Loading sub module "wfb"
    [ 36.270] (II) LoadModule: "wfb"
    [ 36.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 36.271] (II) Module wfb: vendor="X.Org Foundation"
    [ 36.271] compiled for 1.14.4, module version = 1.0.0
    [ 36.271] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.271] (II) Loading sub module "shadow"
    [ 36.271] (II) LoadModule: "shadow"
    [ 36.271] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 36.272] (II) Module shadow: vendor="X.Org Foundation"
    [ 36.272] compiled for 1.14.4, module version = 1.1.0
    [ 36.272] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 36.272] (II) Loading sub module "ramdac"
    [ 36.272] (II) LoadModule: "ramdac"
    [ 36.272] (II) Module "ramdac" already built-in
    [ 36.274] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 36.274] (==) NVIDIA(0): RGB weight 888
    [ 36.274] (==) NVIDIA(0): Default visual is TrueColor
    [ 36.274] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 36.274] (**) NVIDIA(0): Option "UseEdidDpi" "False"
    [ 36.274] (**) NVIDIA(0): Option "DPI" "96 x 96"
    [ 36.274] (**) NVIDIA(0): Enabling 2D acceleration
    [ 50.151] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [ 50.256] (II) NVIDIA(GPU-0): Display (Samsung SMB2330H (CRT-0)) does not support NVIDIA 3D
    [ 50.256] (II) NVIDIA(GPU-0): Vision stereo.
    [ 50.256] (II) NVIDIA(0): NVIDIA GPU GeForce 8500 GT (G86) at PCI:1:0:0 (GPU-0)
    [ 50.256] (--) NVIDIA(0): Memory: 1048576 kBytes
    [ 50.256] (--) NVIDIA(0): VideoBIOS: 60.86.41.00.85
    [ 50.256] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    journalctl -xb
    -- Logs begin at Sat 2013-08-17 21:55:41 ART, end at Mon 2013-11-04 22:01:35 ART. --
    Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 364.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
    Nov 04 21:59:09 arch systemd-journal[120]: Runtime journal is using 368.0K (max 100.1M, leaving 150.2M of free 1001.3M, current limit 100.1M).
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuset
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpu
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys cpuacct
    Nov 04 21:59:09 arch kernel: Linux version 3.11.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013
    Nov 04 21:59:09 arch kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    Nov 04 21:59:09 arch kernel: e820: BIOS-provided physical RAM map:
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007fbb4fff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbb5000-0x000000007fbf7fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fbf8000-0x000000007fd4bfff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd4c000-0x000000007fd51fff] ACPI data
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd52000-0x000000007fd52fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd53000-0x000000007fd54fff] ACPI data
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd55000-0x000000007fd56fff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd57000-0x000000007fd57fff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd58000-0x000000007fd5bfff] ACPI NVS
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd5c000-0x000000007fd6afff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x000000007fd6b000-0x000000007fefffff] usable
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffbfffff] reserved
    Nov 04 21:59:09 arch kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
    Nov 04 21:59:09 arch kernel: NX (Execute Disable) protection: active
    Nov 04 21:59:09 arch kernel: SMBIOS 2.4 present.
    Nov 04 21:59:09 arch kernel: DMI: /DG31PR, BIOS PRG3110H.86A.0071.2010.0318.1704 03/18/2010
    Nov 04 21:59:09 arch kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
    Nov 04 21:59:09 arch kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
    Nov 04 21:59:09 arch kernel: No AGP bridge found
    Nov 04 21:59:09 arch kernel: e820: last_pfn = 0x7ff00 max_arch_pfn = 0x400000000
    Nov 04 21:59:09 arch kernel: MTRR default type: uncachable
    Nov 04 21:59:09 arch kernel: MTRR fixed ranges enabled:
    Nov 04 21:59:09 arch kernel: 00000-9FFFF write-back
    Nov 04 21:59:09 arch kernel: A0000-E7FFF uncachable
    Nov 04 21:59:09 arch kernel: E8000-FFFFF write-protect
    Nov 04 21:59:09 arch kernel: MTRR variable ranges enabled:
    Nov 04 21:59:09 arch kernel: 0 base 000000000 mask F80000000 write-back
    Nov 04 21:59:09 arch kernel: 1 base 07FF00000 mask FFFF00000 uncachable
    Nov 04 21:59:09 arch kernel: 2 disabled
    Nov 04 21:59:09 arch kernel: 3 disabled
    Nov 04 21:59:09 arch kernel: 4 disabled
    Nov 04 21:59:09 arch kernel: 5 disabled
    Nov 04 21:59:09 arch kernel: 6 disabled
    Nov 04 21:59:09 arch kernel: 7 disabled
    Nov 04 21:59:09 arch kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Nov 04 21:59:09 arch kernel: found SMP MP-table at [mem 0x000fc620-0x000fc62f] mapped at [ffff8800000fc620]
    Nov 04 21:59:09 arch kernel: Scanning 1 areas for low memory corruption
    Nov 04 21:59:09 arch kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x00000000-0x000fffff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b2f000, 0x01b2ffff] PGTABLE
    Nov 04 21:59:09 arch kernel: BRK [0x01b30000, 0x01b30fff] PGTABLE
    Nov 04 21:59:09 arch kernel: BRK [0x01b31000, 0x01b31fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7f800000-0x7f9fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7f800000-0x7f9fffff] page 2M
    Nov 04 21:59:09 arch kernel: BRK [0x01b32000, 0x01b32fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7c000000-0x7f7fffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7c000000-0x7f7fffff] page 2M
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x00100000-0x7bffffff]
    Nov 04 21:59:09 arch kernel: [mem 0x00100000-0x001fffff] page 4k
    Nov 04 21:59:09 arch kernel: [mem 0x00200000-0x7bffffff] page 2M
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fa00000-0x7fbb4fff]
    Nov 04 21:59:09 arch kernel: [mem 0x7fa00000-0x7fbb4fff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b33000, 0x01b33fff] PGTABLE
    Nov 04 21:59:09 arch kernel: init_memory_mapping: [mem 0x7fd6b000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: [mem 0x7fd6b000-0x7fefffff] page 4k
    Nov 04 21:59:09 arch kernel: BRK [0x01b34000, 0x01b34fff] PGTABLE
    Nov 04 21:59:09 arch kernel: RAMDISK: [mem 0x37a14000-0x37d01fff]
    Nov 04 21:59:09 arch kernel: ACPI: RSDP 00000000000f03f0 00024 (v02 INTEL)
    Nov 04 21:59:09 arch kernel: ACPI: XSDT 000000007fd53f10 00044 (v01 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI: FACP 000000007fd51d90 000F4 (v04 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20130517/tbfadt-395)
    Nov 04 21:59:09 arch kernel: ACPI BIOS Warning (bug): 32/64X FACS address mismatch in FADT - 0x7FD56F40/0x000000007FD52F40, using 32 (20130517/tbfadt-522)
    Nov 04 21:59:09 arch kernel: ACPI: DSDT 000000007fd4c010 04BE9 (v01 INTEL DG31PR 00000000 INTL 20051117)
    Nov 04 21:59:09 arch kernel: ACPI: FACS 000000007fd56f40 00040
    Nov 04 21:59:09 arch kernel: ACPI: APIC 000000007fd51f10 0006C (v02 INTEL DG31PR 06222004 MSFT 00010013)
    Nov 04 21:59:09 arch kernel: ACPI: HPET 000000007fd5ad10 00038 (v01 INTEL ICH7HPET 06222004 AMI. 00000001)
    Nov 04 21:59:09 arch kernel: ACPI: MCFG 000000007fd5ac10 0003C (v01 INTEL DG31PR 06222004 MSFT 00000097)
    Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
    Nov 04 21:59:09 arch kernel: No NUMA configuration found
    Nov 04 21:59:09 arch kernel: Faking a node at [mem 0x0000000000000000-0x000000007fefffff]
    Nov 04 21:59:09 arch kernel: Initmem setup node 0 [mem 0x00000000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: NODE_DATA [mem 0x7fefb000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007d200000-ffff88007f1fffff] on node 0
    Nov 04 21:59:09 arch kernel: Zone ranges:
    Nov 04 21:59:09 arch kernel: DMA [mem 0x00001000-0x00ffffff]
    Nov 04 21:59:09 arch kernel: DMA32 [mem 0x01000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: Normal empty
    Nov 04 21:59:09 arch kernel: Movable zone start for each node
    Nov 04 21:59:09 arch kernel: Early memory node ranges
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x00001000-0x0009efff]
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x00100000-0x7fbb4fff]
    Nov 04 21:59:09 arch kernel: node 0: [mem 0x7fd6b000-0x7fefffff]
    Nov 04 21:59:09 arch kernel: On node 0 totalpages: 523496
    Nov 04 21:59:09 arch kernel: DMA zone: 64 pages used for memmap
    Nov 04 21:59:09 arch kernel: DMA zone: 21 pages reserved
    Nov 04 21:59:09 arch kernel: DMA zone: 3998 pages, LIFO batch:0
    Nov 04 21:59:09 arch kernel: DMA32 zone: 8124 pages used for memmap
    Nov 04 21:59:09 arch kernel: DMA32 zone: 519498 pages, LIFO batch:31
    Nov 04 21:59:09 arch kernel: ACPI: PM-Timer IO Port: 0x408
    Nov 04 21:59:09 arch kernel: ACPI: Local APIC address 0xfee00000
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
    Nov 04 21:59:09 arch kernel: ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
    Nov 04 21:59:09 arch kernel: IOAPIC[0]: apic_id 0, version 32, address 0xfec00000, GSI 0-23
    Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    Nov 04 21:59:09 arch kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    Nov 04 21:59:09 arch kernel: ACPI: IRQ0 used by override.
    Nov 04 21:59:09 arch kernel: ACPI: IRQ2 used by override.
    Nov 04 21:59:09 arch kernel: ACPI: IRQ9 used by override.
    Nov 04 21:59:09 arch kernel: Using ACPI (MADT) for SMP configuration information
    Nov 04 21:59:09 arch kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
    Nov 04 21:59:09 arch kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
    Nov 04 21:59:09 arch kernel: nr_irqs_gsi: 40
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbb5000-0x7fbf7fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fbf8000-0x7fd4bfff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd4c000-0x7fd51fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd52000-0x7fd52fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd53000-0x7fd54fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd55000-0x7fd56fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd57000-0x7fd57fff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd58000-0x7fd5bfff]
    Nov 04 21:59:09 arch kernel: PM: Registered nosave memory: [mem 0x7fd5c000-0x7fd6afff]
    Nov 04 21:59:09 arch kernel: e820: [mem 0x7ff00000-0xfed1bfff] available for PCI devices
    Nov 04 21:59:09 arch kernel: Booting paravirtualized kernel on bare hardware
    Nov 04 21:59:09 arch kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
    Nov 04 21:59:09 arch kernel: PERCPU: Embedded 29 pages/cpu @ffff88007f800000 s86528 r8192 d24064 u524288
    Nov 04 21:59:09 arch kernel: pcpu-alloc: s86528 r8192 d24064 u524288 alloc=1*2097152
    Nov 04 21:59:09 arch kernel: pcpu-alloc: [0] 0 1 2 3
    Nov 04 21:59:09 arch kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 515287
    Nov 04 21:59:09 arch kernel: Policy zone: DMA32
    Nov 04 21:59:09 arch kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=17d019be-e01f-4c1c-ac50-69e1f3dc0592 rw quiet 3
    Nov 04 21:59:09 arch kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: Checking aperture...
    Nov 04 21:59:09 arch kernel: No AGP bridge found
    Nov 04 21:59:09 arch kernel: Calgary: detecting Calgary via BIOS EBDA area
    Nov 04 21:59:09 arch kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Nov 04 21:59:09 arch kernel: Memory: 2045916K/2093984K available (5050K kernel code, 799K rwdata, 1696K rodata, 1140K init, 1288K bss, 48068K reserved)
    Nov 04 21:59:09 arch kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Nov 04 21:59:09 arch kernel: Preemptible hierarchical RCU implementation.
    Nov 04 21:59:09 arch kernel: RCU dyntick-idle grace-period acceleration is enabled.
    Nov 04 21:59:09 arch kernel: Dump stacks of tasks blocking RCU-preempt GP.
    Nov 04 21:59:09 arch kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
    Nov 04 21:59:09 arch kernel: NR_IRQS:8448 nr_irqs:712 16
    Nov 04 21:59:09 arch kernel: Console: colour dummy device 80x25
    Nov 04 21:59:09 arch kernel: console [tty0] enabled
    Nov 04 21:59:09 arch kernel: allocated 8388608 bytes of page_cgroup
    Nov 04 21:59:09 arch kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Nov 04 21:59:09 arch kernel: hpet clockevent registered
    Nov 04 21:59:09 arch kernel: tsc: Fast TSC calibration using PIT
    Nov 04 21:59:09 arch kernel: tsc: Detected 2399.803 MHz processor
    Nov 04 21:59:09 arch kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4801.58 BogoMIPS (lpj=7999343)
    Nov 04 21:59:09 arch kernel: pid_max: default: 32768 minimum: 301
    Nov 04 21:59:09 arch kernel: Security Framework initialized
    Nov 04 21:59:09 arch kernel: AppArmor: AppArmor disabled by boot time parameter
    Nov 04 21:59:09 arch kernel: Yama: becoming mindful.
    Nov 04 21:59:09 arch kernel: Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Nov 04 21:59:09 arch kernel: Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Nov 04 21:59:09 arch kernel: Mount-cache hash table entries: 256
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys memory
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys devices
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys freezer
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys net_cls
    Nov 04 21:59:09 arch kernel: Initializing cgroup subsys blkio
    Nov 04 21:59:09 arch kernel: CPU: Physical Processor ID: 0
    Nov 04 21:59:09 arch kernel: CPU: Processor Core ID: 0
    Nov 04 21:59:09 arch kernel: mce: CPU supports 6 MCE banks
    Nov 04 21:59:09 arch kernel: CPU0: Thermal monitoring enabled (TM2)
    Nov 04 21:59:09 arch kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
    Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
    tlb_flushall_shift: -1
    Nov 04 21:59:09 arch kernel: Freeing SMP alternatives memory: 20K (ffffffff819e6000 - ffffffff819eb000)
    Nov 04 21:59:09 arch kernel: ACPI: Core revision 20130517
    Nov 04 21:59:09 arch kernel: ACPI: All ACPI Tables successfully acquired
    Nov 04 21:59:09 arch kernel: ftrace: allocating 20100 entries in 79 pages
    Nov 04 21:59:09 arch kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    Nov 04 21:59:09 arch kernel: smpboot: CPU0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (fam: 06, model: 0f, stepping: 0b)
    Nov 04 21:59:09 arch kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
    Nov 04 21:59:09 arch kernel: perf_event_intel: PEBS disabled due to CPU errata
    Nov 04 21:59:09 arch kernel: ... version: 2
    Nov 04 21:59:09 arch kernel: ... bit width: 40
    Nov 04 21:59:09 arch kernel: ... generic registers: 2
    Nov 04 21:59:09 arch kernel: ... value mask: 000000ffffffffff
    Nov 04 21:59:09 arch kernel: ... max period: 000000007fffffff
    Nov 04 21:59:09 arch kernel: ... fixed-purpose events: 3
    Nov 04 21:59:09 arch kernel: ... event mask: 0000000700000003
    Nov 04 21:59:09 arch kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    Nov 04 21:59:09 arch kernel: smpboot: Booting Node 0, Processors #1 #2 #3 OK
    Nov 04 21:59:09 arch kernel: Brought up 4 CPUs
    Nov 04 21:59:09 arch kernel: smpboot: Total of 4 processors activated (19206.35 BogoMIPS)
    Nov 04 21:59:09 arch kernel: devtmpfs: initialized
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fbb5000-0x7fbf7fff] (274432 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd52000-0x7fd52fff] (4096 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd55000-0x7fd56fff] (8192 bytes)
    Nov 04 21:59:09 arch kernel: PM: Registering ACPI NVS region [mem 0x7fd58000-0x7fd5bfff] (16384 bytes)
    Nov 04 21:59:09 arch kernel: RTC time: 0:59:05, date: 11/05/13
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 16
    Nov 04 21:59:09 arch kernel: ACPI: bus type PCI registered
    Nov 04 21:59:09 arch kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
    Nov 04 21:59:09 arch kernel: PCI: not using MMCONFIG
    Nov 04 21:59:09 arch kernel: PCI: Using configuration type 1 for base access
    Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent fixed MTRR settings
    Nov 04 21:59:09 arch kernel: mtrr: your CPUs had inconsistent variable MTRR settings
    Nov 04 21:59:09 arch kernel: mtrr: probably your BIOS does not setup all CPUs.
    Nov 04 21:59:09 arch kernel: mtrr: corrected configuration.
    Nov 04 21:59:09 arch kernel: bio: create slab <bio-0> at 0
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Module Device)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Device)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
    Nov 04 21:59:09 arch kernel: ACPI: Added _OSI(Processor Aggregator Device)
    Nov 04 21:59:09 arch kernel: ACPI: EC: Look up EC in DSDT
    Nov 04 21:59:09 arch kernel: ACPI: Executed 1 blocks of module-level executable AML code
    Nov 04 21:59:09 arch kernel: ACPI: SSDT 000000007fd56c10 002CC (v01 AMI IST 00000001 MSFT 03000001)
    Nov 04 21:59:09 arch kernel: ACPI: Dynamic OEM Table Load:
    Nov 04 21:59:09 arch kernel: ACPI: SSDT (null) 002CC (v01 AMI IST 00000001 MSFT 03000001)
    Nov 04 21:59:09 arch kernel: ACPI: Interpreter enabled
    Nov 04 21:59:09 arch kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
    Nov 04 21:59:09 arch kernel: ACPI: (supports S0 S1 S3 S4 S5)
    Nov 04 21:59:09 arch kernel: ACPI: Using IOAPIC for interrupt routing
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for domain 0000 [bus 00-40] at [mem 0xe0000000-0xe40fffff] (base 0xe0000000)
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG at [mem 0xe0000000-0xe40fffff] reserved in ACPI motherboard resources
    Nov 04 21:59:09 arch kernel: PCI: MMCONFIG for 0000 [bus00-1f] at [mem 0xe0000000-0xe1ffffff] (base 0xe0000000) (size reduced!)
    Nov 04 21:59:09 arch kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    Nov 04 21:59:09 arch kernel: ACPI: No dock devices found.
    Nov 04 21:59:09 arch kernel: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    Nov 04 21:59:09 arch kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: ACPI _OSC control (0x1d) granted
    Nov 04 21:59:09 arch kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-1f] only partially covers this bridge
    Nov 04 21:59:09 arch kernel: PCI host bridge to bus 0000:00
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: root bus resource [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: [8086:29c1] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xfb200000-0xfb203fff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: reg 0x20: [io 0xf080-0xf09f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: reg 0x20: [io 0xf060-0xf07f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: reg 0x20: [io 0xf040-0xf05f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: reg 0x20: [io 0xf020-0xf03f]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xfb204000-0xfb2043ff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: address space collision: [io 0x0400-0x047f] conflicts with ACPI CPU throttle [??? 0x00000410-0x00000415 flags 0x80000000]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: quirk: [io 0x0500-0x053f] claimed by ICH6 GPIO
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 00ff)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x10: [io 0xf130-0xf137]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x14: [io 0xf120-0xf123]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x18: [io 0xf110-0xf117]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x1c: [io 0xf100-0xf103]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.1: reg 0x20: [io 0xf0f0-0xf0ff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf0e0-0xf0e7]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf0d0-0xf0d3]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf0c0-0xf0c7]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf0b0-0xf0b3]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf0a0-0xf0af]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.2: PME# supported from D3hot
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: [10de:0421] type 00 class 0x030000
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x10: [mem 0xfa000000-0xfaffffff]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x1c: [mem 0xf8000000-0xf9ffffff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfb000000-0xfb01ffff pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x10: [io 0xd000-0xd0ff]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x18: [mem 0xfb120000-0xfb120fff 64bit]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: reg 0x30: [mem 0xfb100000-0xfb11ffff pref]
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: supports D1 D2
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: PME# supported from D1 D2 D3hot D3cold
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: bridge window [mem 0x80000000-0xffffffff] (subtractive decode)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *7 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0
    Nov 04 21:59:09 arch kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    Nov 04 21:59:09 arch kernel: ACPI: Enabled 3 GPEs in block 00 to 1F
    Nov 04 21:59:09 arch kernel: ACPI: \_SB_.PCI0: notify handler is installed
    Nov 04 21:59:09 arch kernel: Found 1 acpi root devices
    Nov 04 21:59:09 arch kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    Nov 04 21:59:09 arch kernel: vgaarb: loaded
    Nov 04 21:59:09 arch kernel: vgaarb: bridge control possible 0000:01:00.0
    Nov 04 21:59:09 arch kernel: PCI: Using ACPI for IRQ routing
    Nov 04 21:59:09 arch kernel: PCI: pci_cache_line_size set to 64 bytes
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7fbb5000-0x7fffffff]
    Nov 04 21:59:09 arch kernel: e820: reserve RAM buffer [mem 0x7ff00000-0x7fffffff]
    Nov 04 21:59:09 arch kernel: NetLabel: Initializing
    Nov 04 21:59:09 arch kernel: NetLabel: domain hash size = 128
    Nov 04 21:59:09 arch kernel: NetLabel: protocols = UNLABELED CIPSOv4
    Nov 04 21:59:09 arch kernel: NetLabel: unlabeled traffic allowed by default
    Nov 04 21:59:09 arch kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
    Nov 04 21:59:09 arch kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
    Nov 04 21:59:09 arch kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
    Nov 04 21:59:09 arch kernel: Switched to clocksource hpet
    Nov 04 21:59:09 arch kernel: pnp: PnP ACPI init
    Nov 04 21:59:09 arch kernel: ACPI: bus type PNP registered
    Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:00: [mem 0xe0000000-0xe3ffffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0400-0x047f] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x1180-0x119f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [io 0x0500-0x053f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfec00000-0xfecfffff] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfee00000-0xfee0ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed1c000-0xfed1ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffb00000-0xffcfffff] could not be reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfc800000-0xfc800fff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xfed20000-0xfed7ffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: [mem 0xffe00000-0xffffffff] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c01 (active)
    Nov 04 21:59:09 arch kernel: system 00:02: [io 0x0290-0x029f] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0f03 PNP0f13 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:04: [dma 2]
    Nov 04 21:59:09 arch kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0700 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:05: [dma 0 disabled]
    Nov 04 21:59:09 arch kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:06: [dma 4]
    Nov 04 21:59:09 arch kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0200 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0b00 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0800 (active)
    Nov 04 21:59:09 arch kernel: system 00:09: [io 0x04d0-0x04d1] has been reserved
    Nov 04 21:59:09 arch kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0c04 (active)
    Nov 04 21:59:09 arch kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0103 (active)
    Nov 04 21:59:09 arch kernel: pnp: PnP ACPI: found 12 devices
    Nov 04 21:59:09 arch kernel: ACPI: bus type PNP unregistered
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1f.0: BAR 13: [io 0x0400-0x047f] has bogus alignment
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 15: assigned [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: BAR 15: assigned [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.0: bridge window [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: PCI bridge to [bus 03]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1c.1: bridge window [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: PCI bridge to [bus 04]
    Nov 04 21:59:09 arch kernel: pci 0000:00:1e.0: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:00: resource 7 [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfb0fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 1 [mem 0x80000000-0x801fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:02: resource 2 [mem 0x80200000-0x803fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 1 [mem 0xfb100000-0xfb1fffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:03: resource 2 [mem 0x80400000-0x805fffff 64bit pref]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 4 [io 0x0000-0x0cf7]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 5 [io 0x0d00-0xffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 6 [mem 0x000a0000-0x000bffff]
    Nov 04 21:59:09 arch kernel: pci_bus 0000:04: resource 7 [mem 0x80000000-0xffffffff]
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 2
    Nov 04 21:59:09 arch kernel: TCP established hash table entries: 16384 (order: 6, 262144 bytes)
    Nov 04 21:59:09 arch kernel: TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
    Nov 04 21:59:09 arch kernel: TCP: Hash tables configured (established 16384 bind 16384)
    Nov 04 21:59:09 arch kernel: TCP: reno registered
    Nov 04 21:59:09 arch kernel: UDP hash table entries: 1024 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 1
    Nov 04 21:59:09 arch kernel: pci 0000:00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Boot video device
    Nov 04 21:59:09 arch kernel: PCI: CLS 64 bytes, default 64
    Nov 04 21:59:09 arch kernel: Unpacking initramfs...
    Nov 04 21:59:09 arch kernel: Freeing initrd memory: 3000K (ffff880037a14000 - ffff880037d02000)
    Nov 04 21:59:09 arch kernel: Scanning for low memory corruption every 60 seconds
    Nov 04 21:59:09 arch kernel: audit: initializing netlink socket (disabled)
    Nov 04 21:59:09 arch kernel: type=2000 audit(1383613146.559:1): initialized
    Nov 04 21:59:09 arch kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
    Nov 04 21:59:09 arch kernel: zbud: loaded
    Nov 04 21:59:09 arch kernel: VFS: Disk quotas dquot_6.5.2
    Nov 04 21:59:09 arch kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    Nov 04 21:59:09 arch kernel: msgmni has been set to 4001
    Nov 04 21:59:09 arch kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    Nov 04 21:59:09 arch kernel: io scheduler noop registered
    Nov 04 21:59:09 arch kernel: io scheduler deadline registered
    Nov 04 21:59:09 arch kernel: io scheduler cfq registered (default)
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    Nov 04 21:59:09 arch kernel: pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
    Nov 04 21:59:09 arch kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: HPC vendor_id 8086 device_id 27d0 ss_vid 8086 ss_did 27d0
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.0:pcie04: service driver pciehp loaded
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: HPC vendor_id 8086 device_id 27d2 ss_vid 8086 ss_did 27d2
    Nov 04 21:59:09 arch kernel: pciehp 0000:00:1c.1:pcie04: service driver pciehp loaded
    Nov 04 21:59:09 arch kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
    Nov 04 21:59:09 arch kernel: vesafb: mode is 640x480x32, linelength=2560, pages=0
    Nov 04 21:59:09 arch kernel: vesafb: scrolling: redraw
    Nov 04 21:59:09 arch kernel: vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    Nov 04 21:59:09 arch kernel: vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90002400000, using 1216k, total 1216k
    Nov 04 21:59:09 arch kernel: Console: switching to colour frame buffer device 80x30
    Nov 04 21:59:09 arch kernel: fb0: VESA VGA frame buffer device
    Nov 04 21:59:09 arch kernel: intel_idle: does not run on family 6 model 15
    Nov 04 21:59:09 arch kernel: GHES: HEST is not enabled!
    Nov 04 21:59:09 arch kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    Nov 04 21:59:09 arch kernel: 00:05: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    Nov 04 21:59:09 arch kernel: Linux agpgart interface v0.103
    Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 Controller [PNP0f03:PS2M] at 0x60,0x64 irq 12
    Nov 04 21:59:09 arch kernel: i8042: PNP: PS/2 controller doesn't have KBD irq; using default 1
    Nov 04 21:59:09 arch kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
    Nov 04 21:59:09 arch kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
    Nov 04 21:59:09 arch kernel: mousedev: PS/2 mouse device common for all mice
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: RTC can wake from S4
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
    Nov 04 21:59:09 arch kernel: cpuidle: using governor ladder
    Nov 04 21:59:09 arch kernel: cpuidle: using governor menu
    Nov 04 21:59:09 arch kernel: drop_monitor: Initializing network drop monitor service
    Nov 04 21:59:09 arch kernel: TCP: cubic registered
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 10
    Nov 04 21:59:09 arch kernel: NET: Registered protocol family 17
    Nov 04 21:59:09 arch kernel: Key type dns_resolver registered
    Nov 04 21:59:09 arch kernel: PM: Hibernation image not present or could not be loaded.
    Nov 04 21:59:09 arch kernel: registered taskstats version 1
    Nov 04 21:59:09 arch kernel: Magic number: 5:843:960
    Nov 04 21:59:09 arch kernel: memory memory11: hash matches
    Nov 04 21:59:09 arch kernel: rtc_cmos 00:07: setting system clock to 2013-11-05 00:59:07 UTC (1383613147)
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1140K (ffffffff818c9000 - ffffffff819e6000)
    Nov 04 21:59:09 arch kernel: Write protecting the kernel read-only data: 8192k
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 1084K (ffff8800014f1000 - ffff880001600000)
    Nov 04 21:59:09 arch kernel: Freeing unused kernel memory: 352K (ffff8800017a8000 - ffff880001800000)
    Nov 04 21:59:09 arch systemd-udevd[58]: starting version 208
    Nov 04 21:59:09 arch kernel: Floppy drive(s): fd0 is 1.44M
    Nov 04 21:59:09 arch kernel: SCSI subsystem initialized
    Nov 04 21:59:09 arch kernel: ACPI: bus type USB registered
    Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver usbfs
    Nov 04 21:59:09 arch kernel: usbcore: registered new interface driver hub
    Nov 04 21:59:09 arch kernel: usbcore: registered new device driver usb
    Nov 04 21:59:09 arch kernel: ACPI: bus type ATA registered
    Nov 04 21:59:09 arch kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    Nov 04 21:59:09 arch kernel: uhci_hcd: USB Universal Host Controller Interface driver
    Nov 04 21:59:09 arch kernel: libata version 3.00 loaded.
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000f080
    Nov 04 21:59:09 arch kernel: ehci-pci: EHCI PCI platform driver
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f060
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f040
    Nov 04 21:59:09 arch kernel: FDC 0 is a post-1991 82077
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
    Nov 04 21:59:09 arch kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000f020
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: version 2.13
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: scsi0 : ata_piix
    Nov 04 21:59:09 arch kernel: scsi1 : ata_piix
    Nov 04 21:59:09 arch kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf0f0 irq 14
    Nov 04 21:59:09 arch kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf0f8 irq 15
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: MAP [
    Nov 04 21:59:09 arch kernel: P0 P2 P1 P3 ]
    Nov 04 21:59:09 arch kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: ata2: port disabled--ignoring
    Nov 04 21:59:09 arch kernel: scsi2 : ata_piix
    Nov 04 21:59:09 arch kernel: scsi3 : ata_piix
    Nov 04 21:59:09 arch kernel: ata3: SATA max UDMA/133 cmd 0xf0e0 ctl 0xf0d0 bmdma 0xf0a0 irq 19
    Nov 04 21:59:09 arch kernel: ata4: SATA max UDMA/133 cmd 0xf0c0 ctl 0xf0b0 bmdma 0xf0a8 irq 19
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 5
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: debug port 1
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xfb204000
    Nov 04 21:59:09 arch kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    Nov 04 21:59:09 arch kernel: hub 5-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 5-0:1.0: 8 ports detected
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 1-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 2-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 3-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: USB hub found
    Nov 04 21:59:09 arch kernel: hub 4-0:1.0: 2 ports detected
    Nov 04 21:59:09 arch kernel: ata4.00: ATA-8: WDC WD10EZEX-00RKKA0, 80.00A80, max UDMA/133
    Nov 04 21:59:09 arch kernel: ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    Nov 04 21:59:09 arch kernel: ata4.00: configured for UDMA/133
    Nov 04 21:59:09 arch kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD10EZEX-00R 80.0 PQ: 0 ANSI: 5
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] 4096-byte physical blocks
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write Protect is off
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    Nov 04 21:59:09 arch kernel: sda: sda1 sda2 sda3 sda4 sda5
    Nov 04 21:59:09 arch kernel: sd 3:0:0:0: [sda] Attached SCSI disk
    Nov 04 21:59:09 arch kernel: usb 3-2: new full-speed USB device number 2 using uhci_hcd
    Nov 04 21:59:09 arch kernel: tsc: Refined TSC clocksource calibration: 2399.950 MHz
    Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    Nov 04 21:59:09 arch systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    Nov 04 21:59:09 arch systemd[1]: Set hostname to <arch>.
    Nov 04 21:59:09 arch kernel: Switched to clocksource tsc
    Nov 04 21:59:09 arch systemd[1]: Failed to load default target: No such file or directory
    Nov 04 21:59:09 arch systemd[1]: Trying to load rescue target...
    Nov 04 21:59:09 arch systemd[1]: Starting Encrypted Volumes.
    Nov 04 21:59:09 arch systemd[1]: Reached target Encrypted Volumes.
    Nov 04 21:59:09 arch systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    Nov 04 21:59:09 arch systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    Nov 04 21:59:09 arch systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    Nov 04 21:59:09 arch systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Nov 04 21:59:09 arch systemd[1]: Starting Journal Socket.
    Nov 04 21:59:09 arch systemd[1]: Listening on Journal Socket.
    Nov 04 21:59:09 arch systemd[1]: Starting Setup Virtual Console...
    Nov 04 21:59:09 arch systemd[1]: Starting Apply Kernel Variables...
    Nov 04 21:59:09 arch systemd[1]: Started Set Up Additional Binary Formats.
    Nov 04 21:59:09 arch systemd[1]: Started Load Kernel Modules.
    Nov 04 21:59:09 arch systemd[1]: Mounted FUSE Control File System.
    Nov 04 21:59:09 arch systemd[1]: Mounting POSIX Message Queue File System...
    Nov 04 21:59:09 arch systemd[1]: Mounting Huge Pages File System...
    Nov 04 21:59:09 arch systemd[1]: Mounting Configuration File System...
    Nov 04 21:59:09 arch systemd[1]: Starting Journal Service...
    Nov 04 21:59:09 arch systemd[1]: Started Journal Service.
    Nov 04 21:59:09 arch systemd-journal[120]: Journal started
    -- Subject: The Journal has been started
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- The system journal process has been starting up, opened the journal
    -- files for writing and is now ready to process requests.
    Nov 04 21:59:09 arch systemd[1]: Starting Create list of required static device nodes for the current kernel...
    -- Subject: Unit kmod-static-nodes.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit kmod-static-nodes.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Kernel Socket.
    -- Subject: Unit systemd-udevd-kernel.socket has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-kernel.socket has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Listening on udev Kernel Socket.
    -- Subject: Unit systemd-udevd-kernel.socket has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-kernel.socket has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Control Socket.
    -- Subject: Unit systemd-udevd-control.socket has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-control.socket has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Listening on udev Control Socket.
    -- Subject: Unit systemd-udevd-control.socket has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udevd-control.socket has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting udev Coldplug all Devices...
    -- Subject: Unit systemd-udev-trigger.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udev-trigger.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Mounting Debug File System...
    -- Subject: Unit sys-kernel-debug.mount has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-debug.mount has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-sda4.device...
    -- Subject: Unit dev-sda4.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-sda4.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device...
    -- Subject: Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-disk-by\x2duuid-32d1daa9\x2daa59\x2d4ac1\x2da592\x2d23aa1ae655c5.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Mounting Temporary Directory...
    -- Subject: Unit tmp.mount has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tmp.mount has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started File System Check on Root Device.
    -- Subject: Unit systemd-fsck-root.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-fsck-root.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Remount Root and Kernel File Systems...
    -- Subject: Unit systemd-remount-fs.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-remount-fs.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Starting Root Slice.
    -- Subject: Unit -.slice has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit -.slice has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Created slice Root Slice.
    -- Subject: Unit -.slice has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit -.slice has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting System Slice.
    -- Subject: Unit system.slice has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system.slice has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Created slice System Slice.
    -- Subject: Unit system.slice has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit system.slice has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Expecting device dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device...
    -- Subject: Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-disk-by\x2duuid-bdf255b1\x2d60c6\x2d4714\x2d8dc8\x2d5bd057b49aaa.device has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started Apply Kernel Variables.
    -- Subject: Unit systemd-sysctl.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-sysctl.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted POSIX Message Queue File System.
    -- Subject: Unit dev-mqueue.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-mqueue.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Huge Pages File System.
    -- Subject: Unit dev-hugepages.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit dev-hugepages.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Configuration File System.
    -- Subject: Unit sys-kernel-config.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-config.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Debug File System.
    -- Subject: Unit sys-kernel-debug.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit sys-kernel-debug.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Mounted Temporary Directory.
    -- Subject: Unit tmp.mount has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit tmp.mount has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started Create list of required static device nodes for the current kernel.
    -- Subject: Unit kmod-static-nodes.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit kmod-static-nodes.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started udev Coldplug all Devices.
    -- Subject: Unit systemd-udev-trigger.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-udev-trigger.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Create static device nodes in /dev...
    -- Subject: Unit systemd-tmpfiles-setup-dev.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-tmpfiles-setup-dev.service has begun starting up.
    Nov 04 21:59:09 arch systemd[1]: Started Remount Root and Kernel File Systems.
    -- Subject: Unit systemd-remount-fs.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-remount-fs.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Starting Load/Save Random Seed...
    -- Subject: Unit systemd-random-seed.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-random-seed.service has begun starting up.
    Nov 04 21:59:09 arch kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
    Nov 04 21:59:09 arch systemd[1]: Started Load/Save Random Seed.
    -- Subject: Unit systemd-random-seed.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-random-seed.service has finished starting up.
    -- The start-up result is done.
    Nov 04 21:59:09 arch systemd[1]: Started Create static device nodes in /dev.
    -- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mail

  • X11 won't start anymore!

    Hello,
    this is a desperate call: I am at a conference with my MBP, (10.6.7, all updates done). I need Matlab for my presentation, which needs X11.
    X11 (and XQuartz) decided that they won't start anymore: the icon bounces in the dock for a while, then sits there without the little light underneath, and X11 is "non responding".
    The logs show something like this.
    I have googled and searched: similar problems once in a while appear but no posted solution.
    I tried:
    1) reinstalling XQuartz (I would reinstall X11, but how? I do not have the disks with me, I am away!)
    2) from an admin account
    3) create a new account.
    4) repair permissions.
    5) reinstall the font update from Apple that was recently issued.
    HELP PLEASE!!!
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     X11.app: DISPLAY ("/tmp/launch-bHvQen/org.macosforge.xquartz:0") does not match our id ("org.x"), unsetting.
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     X11.app: main(): argc=2
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]      argv[0] = /Applications/Utilities/X11.app/Contents/MacOS/X11.bin
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]      argv[1] = -psn_0_278596
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     Waiting for startup parameters via Mach IPC.
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     X11.app: Could not connect to server (DISPLAY is not set). Starting X server.
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     X11.app: Launching /usr/X11/bin/startx:
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]      argv[0] = /bin/sh
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]      argv[1] = -c
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]      argv[2] = /usr/X11/bin/startx
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     font_cache: Scanning user font directories to generate X11 font caches
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     font_cache: Updating FC cache
    11-05-16 5:02:01 PM     org.x.privileged_startx[20781]     font_cache: Scanning system font directories to generate X11 font caches
    11-05-16 5:02:01 PM     defaults[20791]
    The domain/default pair of (org.x.X11, dpi) does not exist
    11-05-16 5:02:01 PM     [0x0-0x44044].org.x.X11[20759]     Couldn't create cookie
    11-05-16 5:02:02 PM     org.x.privileged_startx[20781]     font_cache: Updating FC cache
    11-05-16 5:02:04 PM     [0x0-0x44044].org.x.X11[20759]     font_cache: Done
    11-05-16 5:02:04 PM     org.x.privileged_startx[20781]     font_cache: Done

    Here is the solution: there was nothing wrong with x11 per se!
    The problem was that about 30 files in /usr/bin (like gzip, egrep, hexdump etc) had been hosed (they had 0 file size).  The puzzling messages was due to the fact that startx uses hexdump, which was simply silently doing nothing (since it had 0 size!).
    I do not know what or when these files were zeroed: I suspect a recent OSX update which did not complete and I had to forcefully reboot.
    I have fixed it enough to work (copying those files from another mac), but who knows what else lurks beneath the surface of apparent serenity!
    I am actually surprised that the whole system did not stop functioning completely.
    MORALE: if something looks strange in the logs with x11 or other apps, check the file sizes  in your /usr/bin, you may be surprised too!

  • HELP! My Mother in Law's IMAC - OS 10.3 won't start in safe mode!

    She had a power outage last night, with the computer on. She just gets a screen with the apple and spinning gear. We can't start it in safe mode or with the install disc. She got something when we started up in single user mode, but she said there was no place to type in any commands - just lots of writing that does not make sense to us. PLEASE HELP!!!!!!

    sciteacher77:
    Here are three articles from Apple's Knowledge base dealing with different startup issues. Look through the first two and see if they offer any help. Then go to the third and see if you can get it to work.
    Your Mac won't start up in Mac OS X (Mac OS X 10.3.9 or earlier)
    A flashing question mark appears when you start your Mac
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck
    Good luck.
    cornelius

  • Won't start in Safe Mode

    Within the last few weeks, after upgrading to Yosemite, my 27" IMac has slowed down. The spinning wheel has begun to appear several times when either running Aperture or just typically turning on. Now the serious problem. After updating another version of the OS my IMac will not start up. It shows nothing but a white/grey screen. I have followed several step recommended in the apple communities but nothing works. I can't even get past the white screen in Safe Mode.
    please help!!!

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • Hp pavillion dv9700 won't start with Ac adapter plugged in

    Dear all,
    I have a 3 year old hp pavillion dv9700. The problem is that the computer won't turn on when i remove the batteries and leave the Ac adapter plugged in. The led that indicates that the adapter is plugged in is on, so that means that the adapter is working fine. But to be sure, I used another Ac adapter from another dv9700.
    The next thought I had that the problem might be the Ac jacket( that is connected to the motherboard ). So I dismantled 2 dv9700 laptops (one is mine, the otherone from a friend, which is by the way working fine), and toke out the Ac jacket from the laptop that was working oke and replaced it with mine(whIch wasn't booting with the Ac adapter). And still the same problem. So now I am able to say that there is something wrong with thE motherboard.
    When ever I plug in a battery that is not empty, the laptop starts up normally. The other thing that noticed is that whenever I plug in the battery the led of the Ac jacket turns on (not full bright, but somewhat dimmed). This doesn't happen normally. That means that there is somewhere a short circuit on the motherboard.
    I have looked all over the internet, but wasn't able to find someone who had the same problem as me, or a solution for it.
    Ps. It has nothing to do with the video card, because if that was the case, it wouldn't even start with the batteries.
    Already thanks, kdeo2k

    Hello @stacey71,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I have read your post on how your computer is not able to boot with the power adapter plugged in, and with no battery. Are you still able to boot into Windows with the battery installed on your notebook? I would be happy to help you, but first I would encourage you to post your product number for your computer. Below is a is an HP Support document that will demonstrate how to find your computer's product number. In addition, it will also help if you indicate which operating system you are using; and whether your operating system is 32 or 64 bit. The more information you can provide, the better!
    How Do I Find My Model Number or Product Number?
    Which Windows operating system am I running?
    Is the Windows Version on My Computer 32-bit or 64-bit?
    Please re-post with the necessary information, this way I will be able to research this further for you. I look forward to your reply!
    Cheers! 
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • Computer won't start with battery in it...

    have an Aluminum 15" Powerbook G4. I have had this since 2001, when I bought it. I recently updated to OSX. I hadn't used the computer in months and when I went to try and take care of the computer and update to OS 10.4.5 I encountered a problem. When I turned it on nothing happened. I had to turn it off, hit the reset button and then plug in the computer. THe battery was dead so I expected that. But what happened next puzzled me and still does puzzle me.
    I managed to get the computer on by holding in the power button. I heard the familiar start up sound(the sound splash if you will) and when that ended I heard this incredibly loud, white noise coming from my speaker. The noise occured about four times. I was in the room with my wife and mother and they both looked at me like 'what the heck was that?"
    Now I thought maybe this was an issue with my one battery so I uncovered my second battery and the same thing happened. It won't start up with a battery in there. I took the battery out and found that when it seemed to turn on just fine, I managed to get online and run a complete update. When it came time for the software required restart the computer started up and didn't make any noise at all.
    I guess I don't know what to do now. I ran the diagnostics on the computer, from the disk utility and it seemed to come up clean. I don't mind not having the battery in the computer but I don't always want to fix the date and time and the like.
    THis is why I'm posting.
    I also noticed tonight, when I was charging up the battery that I had to stop and take it with me someplace. When I went to turn it back on, with the battery in and it plugged in the noise came back on and I had to fix the date and time again.
    Thanks to those who post, I really appreciate it.

    not sure if this will solve your problem but you can try..
    look at the battery exchange program if your battery is eligable for the replacement or take it to the local dealer so they can check if your board sound is ok.
    PowerBook G4   Mac OS X (10.3.9)  

Maybe you are looking for

  • Securing LDAP username and password in Websphere

    Hi all, I am new to LDAP and WAS. I want to secure the username and password for my LDAP server. Right now i have two choices for using the username and password for the LDAP 1. i can put the username and password in a properties file.( but then it m

  • LabVIEW closes while VI's are still running in the background

    I have created a large application that is split between VB 6 and LV 6.1. The LabVIEW portion runs in the background, except that the VB portion can request that a LabVIEW user interface be presented on demand. Any time after this LabVIEW user interf

  • Reference multiple documents in MM to print on PO

    I need to find a way to have a part in the MM reference multiple techicinal documents that in turn will get printed on the PO. Currently just being handled in the Basic Data Text field in the MM. However i need a way to have this be easily updated/ma

  • I  wants to change the quantity in billing after PGI? plz cive me idea

    i wants to change the quantity in billing doc after pgi plz give me the ans

  • Finder Invisible Files

    Hi, I've noticed that sometimes after I expand a zip or rar archive that I can't see the extracted files in the Finder. The fies are visible under the command line but finder doesn't seem to register them. Can anyone suggest what is causing this? The