X301 Cold boot always reboots?

Hi,
Every time I cold boot my laptop it runs through POST, then reboots and POSTs again, then starts the OS.
It's a minor issue, but rather anoying, i.e. with fingerprint reading as you need to swipe twice.
This problem only occurs from a cold boot. When restarting the laptop this issue doesn't appear.
Anyone else have this problem?
thanks.

And yet another bump. Lenovo, can you please tell me what to do about this? This is the THIRD box already with various issues. Love the form factor but would like to have a completely working one...
Florian

Similar Messages

  • Have to restart twice on cold boot...soft reboots just fine though --

    Hi I built this NEO system and  I was coming from a 266Mhz Dell so it's really a great time.  However I am having a problem with starting from a complete shutdown.  Reboots are no problem but when I try to start the computer up from being turned off it always freezes up after POST the first time, and then boots just fine the second time.
    Everytime I turn the computer off through start>shutdown>turn off - the computer shuts down and then when I start it back up it checks memory -which i escape out of - goes through POST and then freezes up after recognizing the HDD and CDROM.  I've waited a while and it just stays frozen.  So then I turn it off again, turn it back on, and the second time it always posts and boots up just fine.  
    Also, if I just do a soft reboot from within windows it always reboots just fine.  
    Anybody know what setting I could be missing?  I have noticed that if I set PAT to turbo in BIOS CUP-Z says it is enabled in windows.  However if I shutdown and go through the "2 restarts" thing CPU-Z says it is no longer enabled.  So it does not matter what PAT is set to something is reverting on it’s own after a cold start.
    It seems like some basic setting gets changed or reverts in the bios upon a full cold shutdown, whereas it doesn't with just a soft reboot.  I don't list a case because I just have it set up on an ESD mat and use anything metal to turn it on by bridging the correct contacts.
    I'm not overclocking and have the memory set to set itself.  I think the voltages are all just set to default.
    Corecenter says:
    Fsb 203 x 17
    Vcore 1.5500
    Memory volatage 2.50
    Agp voltage 1.6
    875PNEOFIS2R bios v1.9 MS-6758
    P4 3.4 Northwood HT+
    Crucial DDR-SDRAM PC3200 512 x 2 (3-4-4-8) dual channel PAT disabled
    Seagate SATA 120GB on SER1
    ATI AIW 9800 PRO
    ATI 9200 PCI x 2
    NEC/Mitsubishi FP2141SB x 3
    Plexwriter Premium
    Samsung DVD
    Sony FDD
    Antec Truepower 550  3.3v-32a 5v-40a 12v-24a

    Wow.  Thanks for quick reply.  
    I set DDR Voltage to 2.7 in bios, loaded windows, shutdown.  Started computer and it still hung after memory test and POST.  So I held in the power button 4 seconds and shutdown.  Started again and POST and booted into windows just fine.  So it still seems to need "2 restarts" even with the DDR voltage change to 2.7!?

  • FileVault enabled; reboot on cold boot

    I enabled FileVault on my 2011 MBP 15. The following sequence occurs when I perform a cold boot:
    Power on; no issues
    Login screen appears and I enter my password
    Hangs for a bit with the grey lined wheel spinning
    System reboots
    Login screen appears and I enter my password
    OS X Lion loads without issue
    Any ideas?

    I think I've worked it out... I was running the laptop on mains power only with battery removed. Tried it with the battery installed and problem disappears, it must provide extra power at startup to spin up the HD. Laptop AC adaptor is 200W though, would have thought this would be enough...

  • Reboot when cold booting

    Hi.
    I encrypted my MBP harddrive with the new FileVault feature. Recently my MBP developed an issue where it would hang a while on the spinner when cold booting, then just reboot - and then boot just fine.
    This requires me to type in my decryption password two times. Doesn't seem healthy. I tried restoring file permissions from Disk Utility but this didn't help.
    Do you know what is causing this and perhaps how I could fix it?
    Jorijn

    It seems to be a problem with paralles desktop.
    http://www.cultofmac.com/113981/parallels-desktop-7-update-fixes-file-fault-full -disk-encryption-problems-get-it-now/
    Chris

  • WCS Access Point Reboot versus Cold Boot

    I'm aware of the process an LWAP AP goes through when a cold boot is performed, specifically dealing with 1130 access points. I've noticed that when using the reboot command in WCS, the process is much shorter than a cold boot (unplugging the AP from power and network and then plugging everything back in).
    So the question is - what is the difference between the reboot command in WCS and performing a cold boot? Does the AP retain some information during a reboot and therefore not require as much time to boot up?
    Thanks for any help...

    You can restart the access point by one of the following mehtods
    1. Remove the power and replug the power cable
    2. Using the CLI in the ap prompt type boot command. i.e [ap:boot]
    3. In the Web interface use the System Configuration Setup page to restart the access point. Click Warm Restart System Now to perform a warm restart of the access point. A warm restart reboots the access point. Click Cold Restart System Now to perform a cold restart of the access point. A cold restart is the equivalent of removing and then reapplying power for the access point.

  • ATI Graphics card not detected on cold boot, works on warm boot

    Hi All,
    I hope you can help me out with this.
    I'm using Radeon HD7850 with ATI-Catalyst.
    The issue is, if I do a cold boot (physically turn off the power, turn back on) the system won't boot into X, only tty.
    At this point, a reboot works fine.
    Or if I don't turn off the power, just shutdown and reboot (warm boot), it works ok.
    Here's the Xorg log on cold boot:
    [ 2.226]
    X.Org X Server 1.12.4
    Release Date: 2012-08-27
    [ 2.226] X Protocol Version 11, Revision 0
    [ 2.226] Build Operating System: Linux 3.4.8-1-ARCH x86_64
    [ 2.226] Current Operating System: Linux dmanPC 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 09:14:51 CEST 2012 x86_64
    [ 2.226] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=3766a71b-dbfe-4cc2-b7bd-948878b5da67 ro nomodeset quiet
    [ 2.226] Build Date: 27 August 2012 08:04:39AM
    [ 2.226]
    [ 2.226] Current version of pixman: 0.26.2
    [ 2.226] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2.226] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2.226] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 28 05:57:41 2012
    [ 2.227] (==) Using config file: "/etc/X11/xorg.conf"
    [ 2.228] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2.228] (==) ServerLayout "aticonfig Layout"
    [ 2.228] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
    [ 2.228] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
    [ 2.229] (**) | |-->Device "aticonfig-Device[0]-0"
    [ 2.229] (==) Automatically adding devices
    [ 2.229] (==) Automatically enabling devices
    [ 2.231] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 2.231] Entry deleted from font path.
    [ 2.231] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2.231] Entry deleted from font path.
    [ 2.231] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 2.231] Entry deleted from font path.
    [ 2.231] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 2.232] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 2.232] Entry deleted from font path.
    [ 2.232] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 2.232] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 2.232] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2.232] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2.232] (II) Loader magic: 0x7c8b00
    [ 2.232] (II) Module ABI versions:
    [ 2.232] X.Org ANSI C Emulation: 0.4
    [ 2.232] X.Org Video Driver: 12.1
    [ 2.232] X.Org XInput driver : 16.0
    [ 2.232] X.Org Server Extension : 6.0
    [ 2.232] (--) PCI:*(0:7:0:0) 1002:6819:1462:2730 rev 0, Mem @ 0xe0000000/268435456, 0xf7b00000/262144, I/O @ 0x0000c000/256, BIOS @ 0x????????/131072
    [ 2.232] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2.232] (II) "extmod" will be loaded by default.
    [ 2.232] (II) "dbe" will be loaded by default.
    [ 2.232] (II) "glx" will be loaded by default.
    [ 2.232] (II) "record" will be loaded by default.
    [ 2.232] (II) "dri" will be loaded by default.
    [ 2.232] (II) "dri2" will be loaded by default.
    [ 2.232] (II) LoadModule: "extmod"
    [ 2.233] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 2.233] (II) Module extmod: vendor="X.Org Foundation"
    [ 2.233] compiled for 1.12.4, module version = 1.0.0
    [ 2.233] Module class: X.Org Server Extension
    [ 2.233] ABI class: X.Org Server Extension, version 6.0
    [ 2.233] (II) Loading extension MIT-SCREEN-SAVER
    [ 2.233] (II) Loading extension XFree86-VidModeExtension
    [ 2.233] (II) Loading extension XFree86-DGA
    [ 2.233] (II) Loading extension DPMS
    [ 2.233] (II) Loading extension XVideo
    [ 2.233] (II) Loading extension XVideo-MotionCompensation
    [ 2.233] (II) Loading extension X-Resource
    [ 2.233] (II) LoadModule: "dbe"
    [ 2.233] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 2.234] (II) Module dbe: vendor="X.Org Foundation"
    [ 2.234] compiled for 1.12.4, module version = 1.0.0
    [ 2.234] Module class: X.Org Server Extension
    [ 2.234] ABI class: X.Org Server Extension, version 6.0
    [ 2.234] (II) Loading extension DOUBLE-BUFFER
    [ 2.234] (II) LoadModule: "glx"
    [ 2.234] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2.236] (II) Module glx: vendor="Advanced Micro Devices, Inc."
    [ 2.236] compiled for 6.9.0, module version = 1.0.0
    [ 2.236] (II) Loading extension GLX
    [ 2.236] (II) LoadModule: "record"
    [ 2.236] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 2.237] (II) Module record: vendor="X.Org Foundation"
    [ 2.237] compiled for 1.12.4, module version = 1.13.0
    [ 2.237] Module class: X.Org Server Extension
    [ 2.237] ABI class: X.Org Server Extension, version 6.0
    [ 2.237] (II) Loading extension RECORD
    [ 2.237] (II) LoadModule: "dri"
    [ 2.237] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 2.237] (II) Module dri: vendor="X.Org Foundation"
    [ 2.237] compiled for 1.12.4, module version = 1.0.0
    [ 2.237] ABI class: X.Org Server Extension, version 6.0
    [ 2.237] (II) Loading extension XFree86-DRI
    [ 2.237] (II) LoadModule: "dri2"
    [ 2.238] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2.238] (II) Module dri2: vendor="X.Org Foundation"
    [ 2.238] compiled for 1.12.4, module version = 1.2.0
    [ 2.238] ABI class: X.Org Server Extension, version 6.0
    [ 2.238] (II) Loading extension DRI2
    [ 2.238] (II) LoadModule: "fglrx"
    [ 2.238] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
    [ 2.262] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
    [ 2.262] compiled for 1.4.99.906, module version = 8.98.2
    [ 2.262] Module class: X.Org Video Driver
    [ 2.262] (II) Loading sub module "fglrxdrm"
    [ 2.262] (II) LoadModule: "fglrxdrm"
    [ 2.262] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 2.263] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 2.263] compiled for 1.4.99.906, module version = 8.98.2
    [ 2.263] (II) AMD Proprietary Linux Driver Version Identifier:8.98.2
    [ 2.263] (II) AMD Proprietary Linux Driver Release Identifier: 8.982
    [ 2.263] (II) AMD Proprietary Linux Driver Build Date: Jul 27 2012 20:37:56
    [ 2.263] (++) using VT number 8
    [ 2.264] (WW) Falling back to old probe method for fglrx
    [ 2.269] (II) Loading PCS database from /etc/ati/amdpcsdb
    [ 2.271] (WW) fglrx: No matching Device section for instance (BusID ) found
    [ 2.271] (EE) No devices detected.
    [ 2.271]
    Fatal server error:
    [ 2.271] no screens found
    [ 2.271]
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 2.271] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 2.271]
    Here's the same log for warm boot:
    [ 2.289] (++) using VT number 8
    [ 2.290] (WW) Falling back to old probe method for fglrx
    [ 2.295] (II) Loading PCS database from /etc/ati/amdpcsdb
    [ 2.296] (--) Chipset Supported AMD Graphics Processor (0x6819) found
    [ 2.296] (WW) fglrx: No matching Device section for instance (BusID PCI:0@6:0:1) found
    [ 2.297] (II) AMD Video driver is running on a device belonging to a group targeted for this release
    [ 2.297] (II) AMD Video driver is signed
    [ 2.297] (II) fglrx(0): pEnt->device->identifier=0x82b7a0
    [ 2.297] (II) fglrx(0): === [xdl_xs112_atiddxPreInit] === begin
    [ 2.297] (II) Loading sub module "vgahw"
    [ 2.297] (II) LoadModule: "vgahw"
    [ 2.298] (II) Loading /usr/lib/xorg/modules/libvgahw.so
    [ 2.298] (II) Module vgahw: vendor="X.Org Foundation"
    [ 2.298] compiled for 1.12.4, module version = 0.1.0
    [ 2.298] ABI class: X.Org Video Driver, version 12.1
    [ 2.298] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
    [ 2.298] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 2.298] (==) fglrx(0): Default visual is TrueColor
    [ 2.298] (**) fglrx(0): Option "OpenGLOverlay" "0"
    [ 2.298] (**) fglrx(0): Option "DPMS" "true"
    [ 2.298] (==) fglrx(0): RGB weight 888
    [ 2.298] (II) fglrx(0): Using 8 bits per RGB
    [ 2.298] (==) fglrx(0): Buffer Tiling is ON
    [ 2.299] (II) Loading sub module "fglrxdrm"
    [ 2.299] (II) LoadModule: "fglrxdrm"
    [ 2.299] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
    [ 2.299] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
    [ 2.299] compiled for 1.4.99.906, module version = 8.98.2
    [ 2.299] ukiDynamicMajor: found major device number 251
    [ 2.299] ukiDynamicMajor: found major device number 251
    [ 2.299] ukiOpenByBusid: Searching for BusID PCI:6:0:0
    [ 2.299] ukiOpenDevice: node name is /dev/ati/card0
    [ 2.299] ukiOpenDevice: open result is 11, (OK)
    [ 2.299] ukiOpenByBusid: ukiOpenMinor returns 11
    [ 2.299] ukiOpenByBusid: ukiGetBusid reports PCI:6:0:0
    [ 2.299] (**) fglrx(0): NoAccel = NO
    [ 2.299] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
    [ 2.299] (--) fglrx(0): Chipset: "AMD Radeon HD 7800 Series " (Chipset = 0x6819)
    [ 2.299] (--) fglrx(0): (PciSubVendor = 0x1462, PciSubDevice = 0x2730)
    [ 2.299] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
    [ 2.299] (--) fglrx(0): Linear framebuffer (phys) at 0xe0000000
    [ 2.299] (--) fglrx(0): MMIO registers at 0xf7c00000
    [ 2.299] (--) fglrx(0): I/O port at 0x0000c000
    [ 2.299] (==) fglrx(0): ROM-BIOS at 0x000c0000
    [ 2.300] (II) fglrx(0): AC Adapter is used
    [ 2.303] (II) fglrx(0): Primary V_BIOS segment is: 0xc000
    [ 2.303] (II) Loading sub module "vbe"
    [ 2.303] (II) LoadModule: "vbe"
    [ 2.303] (II) Loading /usr/lib/xorg/modules/libvbe.so
    [ 2.304] (II) Module vbe: vendor="X.Org Foundation"
    [ 2.304] compiled for 1.12.4, module version = 1.1.0
    [ 2.304] ABI class: X.Org Video Driver, version 12.1
    [ 2.304] (II) fglrx(0): VESA BIOS detected
    [ 2.304] (II) fglrx(0): VESA VBE Version 3.0
    [ 2.304] (II) fglrx(0): VESA VBE Total Mem: 16384 kB
    [ 2.304] (II) fglrx(0): VESA VBE OEM: AMD ATOMBIOS
    [ 2.304] (II) fglrx(0): VESA VBE OEM Software Rev: 15.17
    [ 2.304] (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2010, Advanced Micro Devices, Inc.
    [ 2.304] (II) fglrx(0): VESA VBE OEM Product: PITCAIRN
    [ 2.304] (II) fglrx(0): VESA VBE OEM Product Rev: 01.00
    [ 2.309] (II) fglrx(0): AMD Video BIOS revision 9 or later detected
    [ 2.309] (--) fglrx(0): Video RAM: 2097152 kByte, Type: GDDR5
    [ 2.309] (II) fglrx(0): PCIE card detected
    [ 2.309] (--) fglrx(0): Using per-process page tables (PPPT) as GART.
    [ 2.309] (WW) fglrx(0): board is an unknown third party board, chipset is supported
    [ 2.311] (II) fglrx(0): Using adapter: 6:0.0.
    [ 2.320] (II) fglrx(0): [FB] MC range(MCFBBase = 0xf400000000, MCFBSize = 0x80000000)
    [ 2.458] (II) fglrx(0): Interrupt handler installed at IRQ 48.
    [ 2.458] (II) fglrx(0): RandR 1.2 support is enabled!
    [ 2.458] (II) fglrx(0): RandR 1.2 rotation support is enabled!
    [ 2.458] (==) fglrx(0): Center Mode is disabled
    [ 2.458] (II) Loading sub module "fb"
    [ 2.458] (II) LoadModule: "fb"
    [ 2.458] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 2.461] (II) Module fb: vendor="X.Org Foundation"
    [ 2.461] compiled for 1.12.4, module version = 1.0.0
    [ 2.461] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2.461] (II) Loading sub module "ddc"
    [ 2.461] (II) LoadModule: "ddc"
    [ 2.461] (II) Module "ddc" already built-in
    [ 2.571] (II) fglrx(0): Finished Initialize PPLIB!
    [ 2.577] (II) fglrx(0): Output DFP1 using monitor section aticonfig-Monitor[0]-0
    [ 2.577] (II) fglrx(0): Output DFP2 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP3 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP4 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP5 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP6 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP7 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP8 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP9 has no monitor section
    [ 2.577] (II) fglrx(0): Output DFP10 has no monitor section
    [ 2.577] (II) fglrx(0): Output CRT1 has no monitor section
    [ 2.578] (II) Loading sub module "ddc"
    [ 2.578] (II) LoadModule: "ddc"
    [ 2.578] (II) Module "ddc" already built-in
    [ 2.578] (II) fglrx(0): Connected Display0: DFP10
    [ 2.578] (II) fglrx(0): Display0 EDID data ---------------------------
    [ 2.578] (II) fglrx(0): Manufacturer: SAM Model: 524 Serial#: 1280455218
    [ 2.578] (II) fglrx(0): Year: 2009 Week: 20
    [ 2.578] (II) fglrx(0): EDID Version: 1.3
    [ 2.578] (II) fglrx(0): Digital Display Input
    [ 2.578] (II) fglrx(0): Max Image Size [cm]: horiz.: 48 vert.: 27
    [ 2.578] (II) fglrx(0): Gamma: 2.20
    [ 2.578] (II) fglrx(0): DPMS capabilities: Off
    [ 2.578] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 2.578] (II) fglrx(0): First detailed timing is preferred mode
    [ 2.578] (II) fglrx(0): redX: 0.648 redY: 0.339 greenX: 0.143 greenY: 0.070
    [ 2.578] (II) fglrx(0): blueX: 0.282 blueY: 0.603 whiteX: 0.312 whiteY: 0.329
    [ 2.578] (II) fglrx(0): Supported established timings:
    [ 2.578] (II) fglrx(0): 640x480@60Hz
    [ 2.578] (II) fglrx(0): 800x600@56Hz
    [ 2.578] (II) fglrx(0): 800x600@60Hz
    [ 2.578] (II) fglrx(0): 1024x768@60Hz
    [ 2.578] (II) fglrx(0): Manufacturer's mask: 0
    [ 2.578] (II) fglrx(0): Supported standard timings:
    [ 2.578] (II) fglrx(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 2.578] (II) fglrx(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 2.578] (II) fglrx(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 2.578] (II) fglrx(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 2.578] (II) fglrx(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 2.578] (II) fglrx(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 148.5 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2.578] (II) fglrx(0): Ranges: V min: 56 V max: 60 Hz, H min: 30 H max: 81 kHz, PixClock max 175 MHz
    [ 2.578] (II) fglrx(0): Monitor name: SyncMaster
    [ 2.578] (II) fglrx(0): Serial No: HMBS500385
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 148.5 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 74.2 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 74.2 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 27.0 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 27.0 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 2.578] (II) fglrx(0): Number of EDID sections to follow: 1
    [ 2.578] (II) fglrx(0): EDID (in hex):
    [ 2.578] (II) fglrx(0): 00ffffffffffff004c2d24053232524c
    [ 2.578] (II) fglrx(0): 1413010380301b782a3851a656241248
    [ 2.578] (II) fglrx(0): 9a50542308008100814081809500a940
    [ 2.578] (II) fglrx(0): b30001010101023a801871382d40582c
    [ 2.578] (II) fglrx(0): 4500dd0c1100001e000000fd00383c1e
    [ 2.578] (II) fglrx(0): 5111000a202020202020000000fc0053
    [ 2.578] (II) fglrx(0): 796e634d61737465720a2020000000ff
    [ 2.578] (II) fglrx(0): 00484d42533530303338350a20200168
    [ 2.578] (II) fglrx(0): End of Display0 EDID data --------------------
    [ 2.578] (II) fglrx(0): EDID for output DFP1
    [ 2.578] (II) fglrx(0): EDID for output DFP2
    [ 2.578] (II) fglrx(0): EDID for output DFP3
    [ 2.578] (II) fglrx(0): EDID for output DFP4
    [ 2.578] (II) fglrx(0): EDID for output DFP5
    [ 2.578] (II) fglrx(0): EDID for output DFP6
    [ 2.578] (II) fglrx(0): EDID for output DFP7
    [ 2.578] (II) fglrx(0): EDID for output DFP8
    [ 2.578] (II) fglrx(0): EDID for output DFP9
    [ 2.578] (II) fglrx(0): EDID for output DFP10
    [ 2.578] (II) fglrx(0): Manufacturer: SAM Model: 524 Serial#: 1280455218
    [ 2.578] (II) fglrx(0): Year: 2009 Week: 20
    [ 2.578] (II) fglrx(0): EDID Version: 1.3
    [ 2.578] (II) fglrx(0): Digital Display Input
    [ 2.578] (II) fglrx(0): Max Image Size [cm]: horiz.: 48 vert.: 27
    [ 2.578] (II) fglrx(0): Gamma: 2.20
    [ 2.578] (II) fglrx(0): DPMS capabilities: Off
    [ 2.578] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 2.578] (II) fglrx(0): First detailed timing is preferred mode
    [ 2.578] (II) fglrx(0): redX: 0.648 redY: 0.339 greenX: 0.143 greenY: 0.070
    [ 2.578] (II) fglrx(0): blueX: 0.282 blueY: 0.603 whiteX: 0.312 whiteY: 0.329
    [ 2.578] (II) fglrx(0): Supported established timings:
    [ 2.578] (II) fglrx(0): 640x480@60Hz
    [ 2.578] (II) fglrx(0): 800x600@56Hz
    [ 2.578] (II) fglrx(0): 800x600@60Hz
    [ 2.578] (II) fglrx(0): 1024x768@60Hz
    [ 2.578] (II) fglrx(0): Manufacturer's mask: 0
    [ 2.578] (II) fglrx(0): Supported standard timings:
    [ 2.578] (II) fglrx(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
    [ 2.578] (II) fglrx(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 2.578] (II) fglrx(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 2.578] (II) fglrx(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 2.578] (II) fglrx(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [ 2.578] (II) fglrx(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 148.5 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2.578] (II) fglrx(0): Ranges: V min: 56 V max: 60 Hz, H min: 30 H max: 81 kHz, PixClock max 175 MHz
    [ 2.578] (II) fglrx(0): Monitor name: SyncMaster
    [ 2.578] (II) fglrx(0): Serial No: HMBS500385
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 148.5 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 74.2 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 74.2 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 27.0 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
    [ 2.578] (II) fglrx(0): Supported detailed timing:
    [ 2.578] (II) fglrx(0): clock: 27.0 MHz Image Size: 477 x 268 mm
    [ 2.578] (II) fglrx(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 2.578] (II) fglrx(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 2.578] (II) fglrx(0): Number of EDID sections to follow: 1
    [ 2.578] (II) fglrx(0): EDID (in hex):
    [ 2.578] (II) fglrx(0): 00ffffffffffff004c2d24053232524c
    [ 2.578] (II) fglrx(0): 1413010380301b782a3851a656241248
    [ 2.578] (II) fglrx(0): 9a50542308008100814081809500a940
    [ 2.578] (II) fglrx(0): b30001010101023a801871382d40582c
    [ 2.578] (II) fglrx(0): 4500dd0c1100001e000000fd00383c1e
    [ 2.578] (II) fglrx(0): 5111000a202020202020000000fc0053
    [ 2.578] (II) fglrx(0): 796e634d61737465720a2020000000ff
    [ 2.578] (II) fglrx(0): 00484d42533530303338350a20200168
    [ 2.579] (II) fglrx(0): Printing probed modes for output DFP10
    [ 2.579] (II) fglrx(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1776x1000"x50.0 148.50 1776 2304 2348 2640 1000 1004 1009 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1680x1050"x50.0 148.50 1680 2448 2492 2640 1050 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1400x1050"x60.0 162.00 1400 1664 1856 2160 1050 1201 1204 1250 +hsync +vsync (75.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1400x1050"x50.0 148.50 1400 2448 2492 2640 1050 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1600x900"x60.0 162.00 1600 1664 1856 2160 900 1201 1204 1250 +hsync +vsync (75.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1600x900"x50.0 148.50 1600 2448 2492 2640 900 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x1024"x50.0 148.50 1280 2448 2492 2640 1024 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1440x900"x50.0 148.50 1440 2448 2492 2640 900 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1440x900"x60.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x960"x50.0 148.50 1280 2448 2492 2640 960 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x800"x50.0 148.50 1280 2448 2492 2640 800 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x800"x60.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x768"x50.0 148.50 1280 2448 2492 2640 768 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x768"x60.0 83.50 1280 1352 1480 1680 768 803 809 831 -hsync +vsync (49.7 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1024x768"x50.0 148.50 1024 2448 2492 2640 768 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 2.579] (II) fglrx(0): Modeline "1152x648"x50.0 74.25 1152 1592 1632 1980 648 653 658 750 +hsync +vsync (37.5 kHz)
    [ 2.579] (II) fglrx(0): Modeline "800x600"x50.0 148.50 800 2448 2492 2640 600 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "800x600"x60.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 2.579] (II) fglrx(0): Modeline "800x600"x56.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "720x576"x60.0 148.50 720 2008 2052 2200 576 1084 1089 1125 +hsync +vsync (67.5 kHz)
    [ 2.579] (II) fglrx(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "720x480"x50.0 148.50 720 2448 2492 2640 480 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz)
    [ 2.579] (II) fglrx(0): Modeline "640x480"x50.0 148.50 640 2448 2492 2640 480 1084 1089 1125 +hsync +vsync (56.2 kHz)
    [ 2.579] (II) fglrx(0): Modeline "640x480"x60.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 2.579] (II) fglrx(0): EDID for output CRT1
    [ 2.579] (II) fglrx(0): Output DFP1 disconnected
    [ 2.579] (II) fglrx(0): Output DFP2 disconnected
    [ 2.579] (II) fglrx(0): Output DFP3 disconnected
    [ 2.579] (II) fglrx(0): Output DFP4 disconnected
    [ 2.579] (II) fglrx(0): Output DFP5 disconnected
    [ 2.579] (II) fglrx(0): Output DFP6 disconnected
    [ 2.579] (II) fglrx(0): Output DFP7 disconnected
    [ 2.579] (II) fglrx(0): Output DFP8 disconnected
    [ 2.579] (II) fglrx(0): Output DFP9 disconnected
    [ 2.579] (II) fglrx(0): Output DFP10 connected
    [ 2.579] (II) fglrx(0): Output CRT1 disconnected
    [ 2.579] (II) fglrx(0): Using exact sizes for initial modes
    [ 2.579] (II) fglrx(0): Output DFP10 using initial mode 1920x1080
    [ 2.579] (II) fglrx(0): DPI set to (96, 96)
    [ 2.579] (II) fglrx(0): Eyefinity capable adapter detected.
    [ 2.579] (II) fglrx(0): Adapter AMD Radeon HD 7800 Series has 6 configurable heads and 1 displays connected.
    [ 2.579] (==) fglrx(0): PseudoColor visuals disabled
    [ 2.579] (II) Loading sub module "ramdac"
    [ 2.579] (II) LoadModule: "ramdac"
    [ 2.579] (II) Module "ramdac" already built-in
    [ 2.579] (==) fglrx(0): NoDRI = NO
    [ 2.579] (==) fglrx(0): Capabilities: 0x00000000
    [ 2.579] (==) fglrx(0): CapabilitiesEx: 0x00000000
    [ 2.579] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
    [ 2.579] (==) fglrx(0): UseFastTLS=0
    [ 2.579] (II) fglrx(0): Desktop Vsync is enabled.
    [ 2.579] (--) Depth 24 pixmap format is 32 bpp
    [ 2.579] (II) Loading extension ATIFGLRXDRI
    [ 2.579] (II) fglrx(0): doing swlDriScreenInit
    [ 2.579] (II) fglrx(0): swlDriScreenInit for fglrx driver
    [ 2.579] ukiDynamicMajor: found major device number 251
    [ 2.579] ukiDynamicMajor: found major device number 251
    [ 2.579] ukiDynamicMajor: found major device number 251
    [ 2.579] ukiOpenByBusid: Searching for BusID PCI:6:0:0
    [ 2.579] ukiOpenDevice: node name is /dev/ati/card0
    [ 2.579] ukiOpenDevice: open result is 12, (OK)
    [ 2.579] ukiOpenByBusid: ukiOpenMinor returns 12
    [ 2.579] ukiOpenByBusid: ukiGetBusid reports PCI:6:0:0
    [ 2.579] (II) fglrx(0): [uki] DRM interface version 1.0
    [ 2.579] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:6:0:0"
    [ 2.579] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x2000
    [ 2.579] (II) fglrx(0): [uki] mapped SAREA 0x2000 to 0x7f1426d74000
    [ 2.579] (II) fglrx(0): [uki] framebuffer handle = 0x3000
    [ 2.579] (II) fglrx(0): [uki] added 1 reserved context for kernel
    [ 2.579] (II) fglrx(0): swlDriScreenInit done
    [ 2.579] (II) fglrx(0): Kernel Module Version Information:
    [ 2.579] (II) fglrx(0): Name: fglrx
    [ 2.579] (II) fglrx(0): Version: 8.98.2
    [ 2.579] (II) fglrx(0): Date: Jul 27 2012
    [ 2.579] (II) fglrx(0): Desc: AMD FireGL DRM kernel module
    [ 2.579] (II) fglrx(0): Kernel Module version matches driver.
    [ 2.579] (II) fglrx(0): Kernel Module Build Time Information:
    [ 2.579] (II) fglrx(0): Build-Kernel UTS_RELEASE: 3.5.3-1-ARCH
    [ 2.579] (II) fglrx(0): Build-Kernel MODVERSIONS: no
    [ 2.579] (II) fglrx(0): Build-Kernel __SMP__: no
    [ 2.579] (II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
    [ 2.579] (II) fglrx(0): [uki] register handle = 0x00004000
    [ 2.589] (II) fglrx(0): DRI initialization successfull
    [ 2.590] (II) fglrx(0): FBADPhys: 0xf400000000 FBMappedSize: 0x010e0000
    [ 2.591] (==) fglrx(0): Backing store disabled
    [ 2.591] (II) Loading extension FGLRXEXTENSION
    [ 2.591] (**) fglrx(0): DPMS enabled
    [ 2.591] (II) fglrx(0): Initialized in-driver Xinerama extension
    [ 2.591] (**) fglrx(0): Textured Video is enabled.
    [ 2.591] (II) LoadModule: "glesx"
    [ 2.591] (II) Loading /usr/lib/xorg/modules/glesx.so
    [ 2.601] (II) Module glesx: vendor="X.Org Foundation"
    [ 2.601] compiled for 1.4.99.906, module version = 1.0.0
    [ 2.601] (II) Loading extension GLESX
    [ 2.601] (II) fglrx(0): GLESX enableFlags = 592
    [ 2.602] (II) fglrx(0): GLESX is enabled
    [ 2.602] (II) LoadModule: "amdxmm"
    [ 2.602] (II) Loading /usr/lib/xorg/modules/amdxmm.so
    [ 2.603] (II) Module amdxmm: vendor="X.Org Foundation"
    [ 2.603] compiled for 1.4.99.906, module version = 2.0.0
    [ 2.615] (II) Loading extension AMDXVOPL
    [ 2.615] (II) Loading extension AMDXVBA
    [ 2.617] (II) fglrx(0): UVD feature is enabled(II) fglrx(0):
    [ 2.618] (II) fglrx(0): Enable composite support successfully
    [ 2.618] (WW) fglrx(0): Option "VendorName" is not used
    [ 2.618] (WW) fglrx(0): Option "ModelName" is not used
    [ 2.618] (II) fglrx(0): X context handle = 0x1
    [ 2.618] (II) fglrx(0): [DRI] installation complete
    [ 2.618] (==) fglrx(0): Silken mouse enabled
    [ 2.618] (==) fglrx(0): Using HW cursor of display infrastructure!
    [ 2.618] (II) fglrx(0): Disabling in-server RandR and enabling in-driver RandR 1.2.
    [ 2.735] (II) fglrx(0): Framebuffer compression enabled: mcAddr=0xf407a40000 width=0xa00 height=0x3267
    [ 2.735] (--) RandR disabled
    [ 2.735] (II) Initializing built-in extension Generic Event Extension
    [ 2.735] (II) Initializing built-in extension SHAPE
    [ 2.735] (II) Initializing built-in extension MIT-SHM
    [ 2.735] (II) Initializing built-in extension XInputExtension
    [ 2.735] (II) Initializing built-in extension XTEST
    [ 2.735] (II) Initializing built-in extension BIG-REQUESTS
    [ 2.735] (II) Initializing built-in extension SYNC
    [ 2.735] (II) Initializing built-in extension XKEYBOARD
    [ 2.735] (II) Initializing built-in extension XC-MISC
    [ 2.735] (II) Initializing built-in extension SECURITY
    [ 2.735] (II) Initializing built-in extension XINERAMA
    [ 2.735] (II) Initializing built-in extension XFIXES
    [ 2.735] (II) Initializing built-in extension RENDER
    [ 2.735] (II) Initializing built-in extension RANDR
    [ 2.735] (II) Initializing built-in extension COMPOSITE
    [ 2.735] (II) Initializing built-in extension DAMAGE
    [ 2.736] ukiDynamicMajor: found major device number 251
    [ 2.736] ukiDynamicMajor: found major device number 251
    [ 2.736] ukiOpenByBusid: Searching for BusID PCI:6:0:0
    [ 2.736] ukiOpenDevice: node name is /dev/ati/card0
    [ 2.736] ukiOpenDevice: open result is 13, (OK)
    [ 2.736] ukiOpenByBusid: ukiOpenMinor returns 13
    [ 2.736] ukiOpenByBusid: ukiGetBusid reports PCI:6:0:0
    [ 2.842] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0
    [ 2.857] (II) fglrx(0): Enable the clock gating!
    [ 2.872] (II) fglrx(0): Desktop Vsync is enabled.
    [ 2.872] (II) fglrx(0): Setting screen physical size to 508 x 285
    [ 2.901] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 2.901] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2.901] (II) LoadModule: "evdev"
    [ 2.901] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 2.902] (II) Module evdev: vendor="X.Org Foundation"
    [ 2.902] compiled for 1.12.3.901, module version = 2.7.3
    [ 2.902] Module class: X.Org XInput Driver
    [ 2.902] ABI class: X.Org XInput driver, version 16.0
    [ 2.902] (II) Using input driver 'evdev' for 'Power Button'
    [ 2.902] (**) Power Button: always reports core events
    [ 2.902] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 2.902] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2.902] (--) evdev: Power Button: Found keys
    [ 2.902] (II) evdev: Power Button: Configuring as keyboard
    [ 2.902] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 2.902] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 2.902] (**) Option "xkb_rules" "evdev"
    [ 2.902] (**) Option "xkb_model" "evdev"
    [ 2.902] (**) Option "xkb_layout" "us"
    [ 2.902] (**) Option "xkb_variant" "dvp"
    [ 2.913] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 2.913] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2.913] (II) Using input driver 'evdev' for 'Power Button'
    [ 2.913] (**) Power Button: always reports core events
    [ 2.913] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 2.913] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 2.913] (--) evdev: Power Button: Found keys
    [ 2.913] (II) evdev: Power Button: Configuring as keyboard
    [ 2.913] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
    [ 2.913] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 2.913] (**) Option "xkb_rules" "evdev"
    [ 2.913] (**) Option "xkb_model" "evdev"
    [ 2.913] (**) Option "xkb_layout" "us"
    [ 2.913] (**) Option "xkb_variant" "dvp"
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event14)
    [ 2.913] (II) No input driver specified, ignoring this device.
    [ 2.913] (II) This device may have been added with another device file.
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event15)
    [ 2.913] (II) No input driver specified, ignoring this device.
    [ 2.913] (II) This device may have been added with another device file.
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event16)
    [ 2.913] (II) No input driver specified, ignoring this device.
    [ 2.913] (II) This device may have been added with another device file.
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event17)
    [ 2.913] (II) No input driver specified, ignoring this device.
    [ 2.913] (II) This device may have been added with another device file.
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event18)
    [ 2.913] (II) No input driver specified, ignoring this device.
    [ 2.913] (II) This device may have been added with another device file.
    [ 2.913] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event19)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event11)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event4)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event5)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event7)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event8)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event9)
    [ 2.914] (II) No input driver specified, ignoring this device.
    [ 2.914] (II) This device may have been added with another device file.
    [ 2.914] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event12)
    [ 2.914] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
    [ 2.914] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
    [ 2.914] (**) Logitech USB Receiver: always reports core events
    [ 2.914] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event12"
    [ 2.914] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52f
    [ 2.914] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
    [ 2.914] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
    [ 2.914] (--) evdev: Logitech USB Receiver: Found relative axes
    [ 2.914] (--) evdev: Logitech USB Receiver: Found x and y relative axes
    [ 2.914] (II) evdev: Logitech USB Receiver: Configuring as mouse
    [ 2.914] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
    [ 2.914] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    [ 2.914] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 2.914] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.7/4-1.7:1.0/input/input12/event12"
    [ 2.914] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 8)
    [ 2.914] (II) evdev: Logitech USB Receiver: initialized for relative axes.
    [ 2.915] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration profile 0
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
    [ 2.915] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
    [ 2.915] (II) No input driver specified, ignoring this device.
    [ 2.915] (II) This device may have been added with another device file.
    [ 2.915] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event13)
    [ 2.915] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
    [ 2.915] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
    [ 2.915] (**) Logitech USB Receiver: always reports core events
    [ 2.915] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event13"
    [ 2.915] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52f
    [ 2.915] (--) evdev: Logitech USB Receiver: Found 1 mouse buttons
    [ 2.915] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
    [ 2.915] (--) evdev: Logitech USB Receiver: Found relative axes
    [ 2.915] (II) evdev: Logitech USB Receiver: Forcing relative x/y axes to exist.
    [ 2.915] (--) evdev: Logitech USB Receiver: Found absolute axes
    [ 2.915] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
    [ 2.915] (--) evdev: Logitech USB Receiver: Found keys
    [ 2.915] (II) evdev: Logitech USB Receiver: Configuring as mouse
    [ 2.915] (II) evdev: Logitech USB Receiver: Configuring as keyboard
    [ 2.915] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
    [ 2.915] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
    [ 2.915] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 2.915] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.7/4-1.7:1.1/input/input13/event13"
    [ 2.915] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
    [ 2.915] (**) Option "xkb_rules" "evdev"
    [ 2.915] (**) Option "xkb_model" "evdev"
    [ 2.915] (**) Option "xkb_layout" "us"
    [ 2.915] (**) Option "xkb_variant" "dvp"
    [ 2.915] (II) evdev: Logitech USB Receiver: initialized for relative axes.
    [ 2.915] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
    [ 2.915] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration profile 0
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
    [ 2.915] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
    [ 2.915] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 2.915] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2.915] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 2.915] (**) AT Translated Set 2 keyboard: always reports core events
    [ 2.915] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 2.915] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 2.915] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 2.915] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 2.915] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 2.915] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
    [ 2.915] (**) Option "xkb_rules" "evdev"
    [ 2.915] (**) Option "xkb_model" "evdev"
    [ 2.915] (**) Option "xkb_layout" "us"
    [ 2.915] (**) Option "xkb_variant" "dvp"
    [ 2.915] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 2.915] (II) No input driver specified, ignoring this device.
    [ 2.915] (II) This device may have been added with another device file.
    [ 2.917] (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments
    [ 7.513] (II) fglrx(0): EDID vendor "SAM", prod id 1316
    [ 7.513] (II) fglrx(0): Using EDID range info for horizontal sync
    [ 7.513] (II) fglrx(0): Using EDID range info for vertical refresh
    [ 7.513] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 7.513] (II) fglrx(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 7.513] (II) fglrx(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 7.513] (II) fglrx(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 10.738] (II) fglrx(0): EDID vendor "SAM", prod id 1316
    [ 10.738] (II) fglrx(0): Using hsync ranges from config file
    [ 10.738] (II) fglrx(0): Using vrefresh ranges from config file
    [ 10.738] (II) fglrx(0): Printing DDC gathered Modelines:
    [ 10.738] (II) fglrx(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
    [ 10.738] (II) fglrx(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [ 10.738] (II) fglrx(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    Here's the Xorg.conf:
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:6:0:0"
    Option "OpenGLOverlay" "0"
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "DRI"
    Mode 0666
    EndSection
    Setting the PCI BusID in Xorg.conf seems to have no effect, even if I set it to 6:0:0 or 7:0:0, its still the same.
    Do I need to set AutoAddDevices off?

    MisterAnderson wrote:Does the same happen with the opensource radeon drivers? (xf86-video-ati)
    Thanks for the reply!
    The open source driver doesn't support my card yet. I tried installing it first since its the recommended driver, but Xorg couldn't detect any display at all.
    It seems the PCI BusID is not being read from the xorg.conf file. There's auto detection everytime the PC boots.
    Last edited by hdhiman (2012-10-04 00:43:52)

  • USB Devices not working on cold boot

    On a cold boot, I get either my mouse (Microsoft Optical) or my modem (see signature) not switched on.  If I reboot, or just re-plug them in, they switch on and Windows detects them.  The modem is attached to a port on the mobo, and the mouse to a powered USB hub.  The only other device powered at boot is a joypad (Thrustmaster Dual Power 2), which always works at boot.  Devices switched off at boot are a printer/scanner, desktop light, and an extension lead for a thumb drive.
    Does anyone have a solution to this?

    Quote from: artur.aragao on 13-February-05, 11:59:04
    Expensive friend,
    Step for the same problems, where already I communicated diverse times with the support of the MSI not obtaining a definitive solution for this problem. It does not go to advance nor to make magic, therefore the problem has left of the plate-mother and not of the operational system. I have one mouse of the Microsoft who possesss led and when I give the departure in the PC the same does not light in the screen of informs of devices of the CMOS. It would have.
    Then I am obliged to remove and to place mouse of the door usb so that mouse functions. The problem is that I have that to faer this almost all time that I bind the micron.
    The bios beta that decided this problem palliative were 1.5B8.
    I see that all the ones that pass for this problem are receiving the had respect, therefore this problem already is old and no solution was adopted until the moment for the manufacturer.
    If my problem to continue, I will get rid myself of my plate and I will migrarei for another manufacturer who hears me and she respects me, therefore we make many times investment s in products that would not have to give as much migraine.
    We buy TVs and DVDs and we do not pass for problems as these.
    I was disappointed with the MSI in this part. It would go to acquire a VGA 6600GT, but today I think seriously about not buying more nothing of the MSI.
    Still more for that it occurred with the 6800GT that were being sales and in the truth they were 6800NU.What it is this?
    I advise to the friend who if not to decide its problem in at least 1 month, it speaks brazenly of its mainboard and it buys of another
    manufacturer as the ABIT or same Gibagyte.
    I have friends that they possess plates of the Gigabyte and are very happy.
    Artur de Souza Aragão
    HUH??? You did know this is an English languager board right? If not then please read the forum rules. Also note that hijacking someone else's post so you can complain is against the rules here as well.
    This is entirely a user to user forum and as such MSI is not here nor do they read it. So yopur complaints whatever they may be as we can't entirely read your post is not getting to those folks that you want to complain at. Instead you are just making the rest of us upset for no visable reason. If you want to contact MSI to copmplain may I suggest a phone call. You may also want to call someone there that actually speaks the same language so there are no miscommunications as what is happening here.
    Edit - his posts on this subject were all removed due to spamming the forum.

  • The Phenom K9A2 Platinum Cold Boot Loop with Vista 64-Bit

    I've posted about this before and I think others have as well.  I will describe it again.
    You power up the machine, it POSTS successfully and starts loading Vista 64-Bit.  You get the green progress bar and see a bunch of disk activity.  The screen flickers for a second as the kernel kicks in.  Instead of a pointer you are greeted with "NO SIGNAL" and the machine POSTS again!
    I've seen this on 2 different K9A2 Platinum boards with 3 different CPUs: 9500, 9600, and now 9850BE.
    I did some debugging last night to isolate it but I don't have a complete answer, I do have some extremely interesting news to report.  I have Vista 64-bit on my Promise SAS drives in RAID-0.  I have XP 64-bit on an IDE drive on the PATA port.  When I experience the "cold boot loop"
    as described, I go into the BIOS and switch the primary boot to XP 64-bit.  I let the system boot, which is always does successfully.  Then I restart the computer and use the BIOS to boot off the Promise RAID.  Vista 64-bit always (in 7 out of 7 tries) boots the first time no problems
    if I first boot XP 64-bit then try booting Vista.  Furthermore if I use a tool like AMD Overdrive to push the CPU, voltage, or memory to a high enough speed to freeze the computer, I can cause the cold boot loop in 7 out of 7 attempts as well.  Once the cold boot loop begins, the computer rarely boots (if I leave it for ***HOURS*** sometimes it will boot into Vista, after 100 attempts or something).
    I'm not entirely sure what this means.  It sounds like there's a sticky bit somewhere, and who knows where, that is causing the issue.  I would think not in the CPU itself, although I guess that is possible, when I switched from the 9600 to the 9850BE and powered up, I was stuck in the cold boot loop so I think I can discount the CPU.  That really just leaves the BIOS in my opinion.  Anybody have any interesting comments
    about this?

    I experienced similar problems this weekend with my rig.
    I have two WD Raptor drives, 150GB on the promise controller and SATA DVD on SB600. If I started Vista, it would boot, show POST screen, then I would see the initial Windows green bar, but after a minute with lots of disk activity then the system would reboot.
    Next, I would then be promoted to start windows normally, or start with the last known good configuration, sometimes this worked, sometime it did not. This happended for a while, until I managed to install all of the optional and recommended Vista 64bit OS patches and an updated promise raid driver. 
    Once these were installed, my system had no boot problems at all, so I would make sure your promise driver is up to date and that all the Vista 64bit OS patches, updates etc are installed.

  • MSI K8T-NEO won't post from a cold boot

    Alrighty here is my strange problem.  I have my system connected to a surge protector powerstip.  When I power my machine down I also shut off the powerstrip which cuts wall power off from the machine.  When I turn the power back on the and then fire up the computer every single time it will not POST on the first try.  The drive lights cd-roms come on but the HD's never start.  So I hold the power button in for 6 seconds, then hit it a second time, and it boots every time.  Shutting down and restarting is no problem, so long as the power is never disconnected from the system.
    Here is my configuration
    MSI K8T NEO Bios version 1.2
    Athlon 64 3200+ not overclocked
    1 512meg stick of Geil Ultra PC3200 slot 1
    1 512meg stick of Coarsair XMS3200 slot 2
    memory is running at 333mhz 2-3-3-7 all setting are set to auto
    Radeon 9500 in the AGP slot
    Sound Blaster Audigy
    Promise 100 TX4 Raid controller
    2 WD 80 gig SE HD's connected to promise controller
    1 Pioneer PD-115 16X DVD drive
    1 Liteon 411-s I believe 4x DVD Writer
    1 Zip Drive
    Using AMD boxed CPU fan
    Powered by an Antec true 430 +3.3V 28A +5V 36A +12V 20A
    According to core center +3.3 is at 3.31V, +5V is at 5.03V, +12V is at 11.76V
    So anyway its prime stable etc.  But when ever the system has been powered off, and unplugged the first time I power on it always fails to post with the d-link indicator lights indicating a CPU failure.  Hold down the power button and it reboots.  Power the machine off, but don't disconnect wall power powers back on just fine.
    This is strange, since I use the surge protector to turn off speakers, etc!  Its also annoying, I used to have a MSI K7D-L Master 2xXP CPU's with the same hardware witht eh exception of the Geil RAM, and of course cpu, and mobo and never had any problems with a cold boot.  any suggestions?

    Yeah I tried having only one stick of ram in the machine, and it hangs on a cold boot when its been unplugged/or powersupply switched off.  Reboot again and no problems.  I tried just having the geil installed, and the corsair stick installed same problem.  I have ordered a second Geil Ultra PC3200 stick so I'll have matched sticks and will be able to run at 400mhz FSB.  The lack of a manual memory speed setting overide in the bios is frustrating.  Yes I know the speed is more or less set by the CPU but there must be some override mechinism if you can slow it down....  
    I have also tried with just a video card installed, and one stick of ram to see if the problem would go away.  No GO.  One thing to mention is I had a Radeon 9700pro that I got from new egg refurbed that I had to send back becasue the card would not power on when the system was booted, unless you disconnected the power lead got the warning message, and then powered off and reconnected the power lead.  Possibly this card may have damaged something else?  OR the mobo was bad and damaged the card?  The mobo was new, the ram (geil), CPU, and 9700pro were all refurbs.  Everything else was from a previous dual processor system and was working fine.
    Both of the Western digitals are set as masters and each are on their own seperate ide channels.  The Promise FastTrack100 TX4, has 4 IDE channels and the HD's are connect to channel 1 and channel 2 on the FastTrack controller.
    Specifically what happens is if the power has been off, I turn the power on, hit the power button.  Lights come on, the cd-rom drives lights start blinking, fans come on, and I hear this kinda of poping sound out of the speakers like the kind of sound you get when you first power on the machine but it happens a second time about 2 seconds after powering on the machine, and it just sits in this kind of hung up state, hitting the reset button does nothing.  Then I power off power back on and it POSTS, and back to normal.  So long as the system is never disconnected from the power source while it is off, it will power back on the first time.  This is really strange I've never had a system do this before.  I'm beginning to wonder if I just have a bad/faulty board and ought to RMA it?

  • K7N2 Delta-L: Strange cold boot problem & solution

    My K7N2 Delta-L has a problem cold booting when the vcore is set in the bios at 1.65v of higher. After a cold boot, you get a blank black screen. I noticed that even if you run at default speeds but set the vcore to 1.65v of higher the problem still occurs. There is no problem rebooting however.
    I found the following solutions:
    1. After you power up and get a blank, hit the reset button.
    2. Don't unplug your PC. My PC is connected to a AVR and after I power down the PC I usually turn the AVR off. If i do this, than the computer will have a booting problem if I try to boot it up 30 minutes later or so. Now if I don't unplug it/power off the AVR than everything is fine.
    I don't understand why it acts the way it does though.
    Does anyone know of any other solutions?

    Have you cleared the cmos. If you do be sure you have the power turned off don't move the cmos jumper with the power on.
    I found that turning off power at power supply and unpluging, than turning on the computer the fans will spin just a little this drains all the power. Clear cmos 2-3 than return to
    1-2 position.
    Than plug the power back in and turn it back on, than try the computer again.

  • 2006 Mac Pro Cold Boot Failure

    Hi all,
    I have problems with 2006 Mac Pro. It fails cold boot at 100%, first thing in the morning only. So I'm seeking expert advice.
    The spec is,
    Xeon 5355 2.66GHz x2 (Octo cores)
    ATI Radeon 5770(Apple Genuine)
    8GB Memory(4x1GB kingston, 4x1GB OWC)
    500GBx2 1TBx2 HDDs
    I disassembled and cleaned PSU and Fans, reapplying thermal pastes on CPUs and North Bridge a month ago.
    Then I booted, system froze at desktop, so I shut it down, reset PRAM & SMC. it booted normally but the upper riser card wasn't detected at all. I cleaned the slot contact and reseated DIMM modules. It was detected after that.
    Everything worked fine for a few days but then I got random kernel panics, reseated RAM, reinstalled Snow Leopard but still got random kernel panics. Then ran AHT for a couple of hours and got an error code 4MEM/6....
    I contacted OWC and they sent me a new set of memory modules. While waiting for the replacement, no kernel panics at all but DVD drive died as well as IDE cable, so I replaced both.
    I got the replacement RAM but past a week, MP fails cold boot every morning. Below is what's happening...
    (1) With Kingston Memory, CPU B error LED is lit, I press SYS_RST, one of DIMM LED is then lit (always DIMM A1). Or sometimes, Power-LED is blinking.
    (2) With OWC memory, boots normally, then kernel panic within a few minutes.
    (3) With OWC memory, CPU B error LED is lit, I press SYS_RST, one of DIMM LED is then lit (always DIMM B1)
    *(1) with new and old riser cards
    *(3) after replaced 2 riser cards
    Replacing riser cards didn't help. After these happen, I shut down by pressing power button for seconds and it boots normally without a hitch. Never get kernel panics nor system freeze. It means when it warms up, MP just works just like it should.
    Replaced so far,
    -- IDE cable (Apple Genuine)
    -- DVD drive (Optiarc AD-7200A)
    -- 4GB (1GBx4) OWC memory
    -- RTC battery CR2032
    -- 2 riser cards
    Is the logic board dead or PSU or memory modules are still bad?
    Any ideas?
    Thanks

    I have a Mac Pro dual 2.8 ghz quad core, circa 2008. Recently, I have been required to depress the power button to end a failed cold boot, then press again to boot, usually with success.
    Every hard restart freeze, and can guarantee you end up with
    corrupt caches, corrupt file system, corrupt directory.
    Safe Boot is not effective in such cases, fsck from single user mode has a better chance.
    Booting from another hard drive, install your bought copy of Alsoft Disk Warrior to rebuild the directory (it has deep scavenge files also).
    The longer you continue to do just Safe Boot and continue using it, the more trouble and less likelihood of being able to repair the drive.
    SMART is not smart enough, it tells you about the past, not what could likely happen, or if you have had bad sectors and I/O errors.
    Have bootable backup clones and a drive that is a clean Apple OS and drivers that isn't used except for repairs and maintenance. Don't rely on just Apple Disk Repair.

  • Mac Pro cold boot failure rate at 50%

    I have a Mac Pro dual 2.8 ghz quad core, circa 2008. Recently, I have been required to depress the power button to end a failed cold boot, then press again to boot, usually with success.
    I do hear a chime, but in the failed situation, it never progresses to the login screen.
    I've reset the pram a few times, this doesn't seem to fix anything, as the system always boots if you try enough times (knock on wood).
    I've verified the s.m.a.r.t. status and the disk, it all reports back as fine.
    I am writing this post from a "safe boot" hope to see if that works on the next cold boot.
    Other posts on this forum suggest it may be a weak pram battery so I will try that, the computer is getting on in years. However a similar post on this forum was marked as answered because the problem reported stated it did not chime from the external speakers. I don't care about that! So here's a new thread about documenting and hopefully solving the actual problem.

    I have a Mac Pro dual 2.8 ghz quad core, circa 2008. Recently, I have been required to depress the power button to end a failed cold boot, then press again to boot, usually with success.
    Every hard restart freeze, and can guarantee you end up with
    corrupt caches, corrupt file system, corrupt directory.
    Safe Boot is not effective in such cases, fsck from single user mode has a better chance.
    Booting from another hard drive, install your bought copy of Alsoft Disk Warrior to rebuild the directory (it has deep scavenge files also).
    The longer you continue to do just Safe Boot and continue using it, the more trouble and less likelihood of being able to repair the drive.
    SMART is not smart enough, it tells you about the past, not what could likely happen, or if you have had bad sectors and I/O errors.
    Have bootable backup clones and a drive that is a clean Apple OS and drivers that isn't used except for repairs and maintenance. Don't rely on just Apple Disk Repair.

  • Intermittent freezes upon cold boot

    Greetings gurus,
    I've been experiencing intermittent freezes on cold boot since a few weeks. I did not have them on 10.5.4. I've only had 4 freezes and according to the CrashReporter log all are identical, as far as I can tell. I have not installed any new hardware and I have only one external thing connected and that's a Sennheiser USB headset. I'm unable to tell if all leave identical messages in other logs however.
    The *CrashReporter log* for the four occasions says that the process which broke is *coreservicesd [43]*. On each occasion, it is said that "Thread 0" crashed. This is how the beginning of that log reads (from the crash earlier today):
    *Process: coreservicesd [43]*
    *Path: /System/Library/CoreServices/coreservicesd*
    *Identifier: coreservicesd*
    *Version: ??? (???)*
    *Code Type: X86 (Native)*
    *Parent Process: launchd [1]*
    *Date/Time: 2009-01-19 20:33:26.618 +0100*
    *OS Version: Mac OS X 10.5.5 (9F33)*
    *Report Version: 6*
    *Exception Type: EXCBADACCESS (SIGBUS)*
    *Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000*
    *Crashed Thread: 0*
    The symptoms are:
    + *Menu bar* is invisible (can make out language flag, airport and bluetooth icons and bottom of menu bar).
    + Finder is unresponsive (can't open folders on the desktop and their icons are gone but not their names - relaunching the Finder does not help).
    + Applications won't launch from the Dock.
    + I can access the Restart, Sleep, Shutdown dialog box by pressing the off button on my ACD, but the Shutdown button doesn't work.
    + Holding the power button will not always force shutdown, but seems to put the computer in some sort of sleep mode (when pressing the button again the desktop will appear "greyed" out and a white progress bar will display).
    As it doesn't happen upon every cold boot I haven't been able to use the Verbose mode. I have done the following:
    + Trashed the plists of Finder and Dock
    + Fixed permissions in DU
    + Left it unplugged from the mains for a whole day
    + Reset PRAM/NVRAM
    + Using Onyx, deleted the caches under Cleaning - System and Cleaning - User (radical perhaps?)
    + Turned off all login items (AppTrap, Gmail Notifr, Fuzzy Clock, Skype)
    + Run Apple Hardware Test, normal and extended, with no errors found
    + Verified boot disk in DU while booted from the installation disk: no errors
    I tried a Safe Boot but it froze. However, it does not freeze every time.
    When it froze this evening, I found loads of the following message in Console-All Messages:
    *WindowServer[51] LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.*
    Many of them are prefaced by loginwindow[23] instead of WindowsServer.
    Below are the messages in Console-Console messages from the latest time that it froze (all of the messages). There's some talk about com.apple.UserEventAgent-Aqua which I don't understand.
    When it says that a "thread" crashes, could it be hardware-related (i.e. the processors)? But should not AHT have caught that? Or is it some corruption in the system? I have backups and clones so I'm not worried about losing data. I'm more concerned about the hardware.
    Any thoughts and ideas would be helpful.
    /p
    19-01-2009 8:33:10 PM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    19-01-2009 8:33:10 PM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
    19-01-2009 8:33:10 PM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
    19-01-2009 8:33:26 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[100]) Exited: Terminated
    19-01-2009 8:33:27 PM com.apple.launchd[1] (com.apple.coreservicesd[43]) Exited abnormally: Bus error
    19-01-2009 8:33:28 PM SystemUIServer[120] Normally SSMenuExtra would not have been loaded as a Menu Extra.
    19-01-2009 8:33:31 PM [0x0-0x2002].com.apple.iCal.helper[129] _RegisterApplication(), FAILED TO REGISTER PROCESS WITH CPS/CoreGraphics in WindowServer, err=-50
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] <CFArray 0x134a30 [
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] 0xa06981a0]>{type = mutable-small, count = 3, val
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] ues = (
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] 0 : <CFString 0x1349a0 [0xa069
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] 81a0]>{contents = "/System/Library/CoreServ
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] ices/Menu Extras/TextInput.menu"}
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] 1 : <CF
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] String 0x1349f0 [0xa06981a0]>{contents = "/
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] System/Library/CoreServices/Menu Extra
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] s/Volume.menu"}
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] 2 : <CFString 0x138910
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] [0xa06981a0]>{contents = "/System/Library/Cor
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] eServices/Menu Extras/Clock.menu"}
    19-01-2009 8:33:33 PM com.apple.UserEventAgent-Aqua[114] )}
    19-01-2009 8:33:37 PM org.ntp.ntpd[14] Error : nodename nor servname provided, or not known

    Actually, doing the following would probably fix everything; at least it has fixed every issue I have ever had.
    If Disk Utility can't fix it, you'll need a more robust utility for the repair. I would recommend DiskWarrior. It is the best at directory repairs. It rebuilds then actually replaces your old directory. I feel every Mac owner should have a copy. Make sure you get the disk so you can boot up on it to run repairs. You can also install it on another drive and run it from there to repair this one. DW works faster that way.
    I use DW once a month to try and catch errors in my system from getting too far out of hand.
    If you have a good backup, hopefully a clone of your system before you had issues, an Erase and Install may also rid you of this issue. But, beware! You will lose everything on the drive with this procedure. Let us know if you need help with that!
     Luck! DALE
    p.s. by Thomas Bryant '''' from a previous post.
    Diskwarrior is a "must have" utility and it's corrected any weird problem I've ever encountered. Anytime I have to do a forced shutdown etc. I run DW to get the directories back in tip top shape. Directory problems cause strange issues and often over the course of several weeks or months the little problems add up to finally a major problem. Tom

  • Solaris Hangs on Cold Boot

    My IDE machine hangs just after Configuration Assistant (Initializing System\Please Wait...) on a cold boot. When I press the reset button it comes up every time. This is a bit concerning - if I have a power outage, my machine won't reboot. Has anyone else had this problem??
    Cheers,
    Simon

    My IDE machine hangs just after Configuration Assistant (Initializing System\Please Wait...) on a cold boot. When I press the reset button it comes up every time. This is a bit concerning - if I have a power outage, my machine won't reboot. Has anyone else had this problem??
    Cheers,
    Simon

  • Restart manually after cold boot to POST

    as above..
    my board wouldn't post on COLD BOOT. i have to manually shutdown the PC (holding power for 10sec ) and on it again before it boots!
    im pretty certain the pc would restart on its own after the "PC diagnosis" thing at the start but mine doesn't!
    help... ITS DAMN IRRITATING!

    oh well... here goes,
    Intel Pentium Dual-Core 2160 (1800MHz/800MHz) @ 3007MHz/1336MHz, 1.4375V (VCORE), 1.45 (NCORE), 1.35V (FSB VTT)
    MSI P35 Neo-F (left this out earlier)
    2 X Patriot 1GB PC6400 DDR2-800 @ 802MHz CAS 4, 4, 4, 12 (2.05V)
    MSI Geforce 8600GT OC Edition 256MB PCI-E (580MHz/1600MHz/1188MHz @ 710MHz/1820MHz/1695MHz)
    Maxtor 300GB SATA-2 HDD (6V300F0)
    Logitech Cordless Desktop EX110
    External Western Digital MyBook 320GB USB2.0 (always connected)
    PCI GW-US54GZL USB2.0 Wireless-G Adapter
    Windows Vista Ultimate
    HEC 450W
    Tried unplugging all unneccessary peripheral but to no avail.
    Complete ORTHOS 8hrs wo problem

Maybe you are looking for

  • No Response from Application Web Server - j2ee when running a long report

    Using Oracle Application server, 10.1.2 and a j2ee application which uses Oracle Reports to create pdf report output. When a report takes 5 mins or more to be produced, the following error message occurs, ending the session. The report request howeve

  • How to settle sales order to CO-PA

    Hello all: 1. create sales order , on item level has settlement rule to PSG:CO-PA 2. in sales order click COSTING button (calculator button) to put in cost estimate 3. KB21n to record actual time for activity 4. VF01 to generate billing 5. in my bill

  • File Synch problem with timestamp

    Win2k, LabVIEW 7.0 I'm trying to do file synchronization between the data files I produced on the local disk, and a remote server. I am doing a LIST FILES on the local folder, and a LIST FILES on the remote folder. For each file, I do a GET FILE INFO

  • Loading Classes

    Hi, Here is my problem. I have a directory with several classes (foo_1, foo_2, ...) which all extend a base class (foo); I want to create a vector with an instance of each class in it. The problem is I dont know what the classes will be called or eve

  • How do I get to accept iCloud's new terms and conditions?

    I keep getting asked to view and accept new terms and conditions. When I push iWeb terms it says "cannot find server" and I cannot access iCloud.