MS-6580 - Warm Boot Fails

Can anyone explain why this MB won't warm boot when overclocked? It doesn't seem to matter if I OC mildly or aggressively...any OC at all and I have to perform a cold boot to bring the system back online. I read something about GBIT mainboard incorrectly lowering the CPU voltage down to its default 1.5v on a warm boot resulting in similar hangs; only on a cold boot would the proper voltages be restored. Could this be what's happening here?
D-Bracket indicates "Memory Detection Test" Failed. I verified that DDR voltage is at 2.7. Tried juggling the DIMMS around. Tried with one alone; then the other. No change in behavior. The only thing that has any impact that I can tell is not to overclock the FSB *at all* - up or down. That seems a bit unreasonable. Memory is Corsair CMX512-3200C2PT (x2).
Thanks,
J

I've had my vCore set as high as 1.70v, although it really doesn't need much more than 1.55v to run at 2.7Ghz. My experiments with adjusting the vCore, while it does affect overall system stability, it has no impact on this particular problem with warm booting.
Temps @ 2.7 and 1.55v - 39-42C Idle, 48-50 Load
Temps @ 2.7 and 1.65v - 46-48C Idle, 58-60 Load
Cheers,
J

Similar Messages

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)

Thinkpad T520 - 4239CTO cold vs warm boot menu (Windows 7 Pro)

I have a curious situation. I replaced the hard disk in the above named Thinkpad with and Intel 530 SSD (250 MB). The OS is a fully patched Windows 7 Pro. Just for the record, to ensure full details are revealed: The new disk was, as recommended on the Lenovo site, activated as a GPT disk, the original was MBR. The BIOS option is Legacy boot (MBR) or UEFI (no MBR) or both. If I selected the UEFI only, I could not boot to or install the OS from the recovery disks. If I selected both, with legacy first or UEFI first, the recovery DVD's would boot and the inbstall would proceed without issue. This si where the trouble starts: Upon completion of the install, a number of anomalies appear. Regardless of the legacy/UEFI setting on the BIOS, if I warm boot, the options menu appears (tabbed with boot options and application options). I have no way out of this as another warm boot just returns me to that menu. If I cold boot, the proper boot sequence occurs and Windows loads properly, but only if the BIOS is set to BOTH for Legacy/UEFI. If it is set to either Legacy only or UEFI only on a cold boot, I get the option menu with the boot/applications tabs but the applications tab now includes the BIOS menu. If I cold boot with both Legacy and UEFI enabled, it boots to Windows and disk manager reveals that the disk is GPT but it appears to have an MBR. My conclusion is that the BIOS is confused because the disk is in some sort of amorphous MBR AND GPT state or something. I am concerned about aggressively pursuing one path or another (forcing a GPT disk by removing the MBR, for example) and getting into more trouble. I wonder if the Lenovo factory recovery disks are incapable of installing on a GPT disk and if that is the issue. Any comments or help is appreciated. Thank you

Hi Ran,
Thanks!
I haven't tried it yet.
In the meantime i did more testing and found out that even with only Power Manager version 2.41a installed the latest Intel Pro wireless driver also supported by lenovo is not stabel and FN-F5 or windows network connection also fails to switch the radio back on after a reboot when the radio has been turned off first ;-(
Reading http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-67283
over and over I decide to revert back to the old Intel wireless driver listed on this page.
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67256
Reinstalled ThinkVantage Access Connections for Window Vista version 5.12
I tested it again........ IT WORKS!!!
Please try this combination:
BIOS Version: 1.15
Bluetooth with Enhanced Data Rate Software II for Windows Vista Version: 6.2.0.5000
ThinkVantage Active Protection System for Windows Vista 32-bit, XP, 2000 Version: 1.62
ThinkPad Power Management driver for Windows Vista, XP, 2000, Me, 98 SE Version: 1.52
ThinkVantage Productivity Center Pack Version: 3.02
Power Manager for Windows Vista Version: 2.41a
ThinkVantage Access Connections for Windows Vista Version 5.12 !!
Intel Wireless LAN (11abgn, abg, bg) for Windows Vista 11.05.0 API
Regards,
Ritchy
Message Edited by Ritchy on 01-14-2009 11:56 PM

Warm boot / MUP.sys hang - possible success

Hi,
This post is for information and to hopefully save a lot of pain from others suffering my problems. However, this appears to be partly an XP software / drivers issue, so the causes of my problems may not be the same things as for others who are suffering the same symptoms. However, I'd appreciate feedback from other people who have had similar problems.
I've been suffering regularly from warm (and cold) boot hangs - these occur after POST and RAID setup screens, and I either get a black screen or the Windows logo (part transparent). When choosing safe or debugging mode, the problem always occurs after MUP.sys. There is a big thread about MUP.sys hangs at Annoyances.com, which identifies a number of possible causes / solutions, many of which appear (to me) to be unlikely. These include:
1) Problems with USB2.0 (conflicts or a lack of power) - Remove USB devices and try to boot again
2) Problems with Power distribution (either a weak power supply or poor power distribution across the board causing instability in either memory, Processor, or USB) - Solution may be to up core voltage slightly.
3) The Windows XP setup used an "ACPI Uniprocessor PC" instead of one of the other options - either change the setting or toggle (enable / disable) the ACPI setting on your mobo (Note, articles I have seen do not recommend changing these settings, but it seems that both Hardware and Software need to match ACPI settings (on or off) for it to boot)
4) Issues with the BIOS - try setting to defaults / adjusing various settings
5) Software installation / drivers causing conflicts. - Appears possible, but is certainly not clear-cut. [Note: My boot issues often get worse after I install something new]
6) Miscellaneous others (including cluttered drives, virus infestation, etc)
At one point this evening, I simply left my PC in its "hung" state, and came back to it later. Eventually (after more than 1/2 hr, I believe) the machine DID boot into Windows, but my SATA RAID array had disappeared from my disk list (I have XP installed on a normal IDE partition, and use a RAID array for programmes & media files).
It has proved of great help to me to ensure I had the "Bootlog" setting enabled. This writes a file to ntbtlog.txt in the windows directory, and you can sometimes interrogate this to see where the boot was failing. Of course, other times XP never gets to write to the file, soit can prove useless. In my case, the log showed the system apparently failing at the "processor" installation, with good boots usually showing "Loaded driver \SystemRoot\System32\DRIVERS\AmdK8.sys" immediately after MUP.sys, while bad boots showing "Did not load driver ACPI Uniprocessor PC" immediately after MUP.sys.
This does not provide infallible evidence that it is *that* driver that is the problem, but it may be an indication.
The issue of missing my SATA RAID disk also made me check those drivers, and I noted that the NVidia 4.24 XP RAID and IDE driver were dated 13/1/04, which was identical to that in my System32/Drivers directory. However, I then saw that the MSI 5.03 drivers were more recent - the IDE drivers in that distribution are dated 3/6/04.
This confused me as I had already installed the 5.03 drivers (the install programme initially "hung" on the SW drivers, and I had to run in Safe mode under "Windows 2000 compatibility" in order to make it run). I was therefore a bit annoyed to find that the IDE drivers had not "taken".
I therefore browsed to the directory and chose "install" from right-clicking the XXX.inf files. However, this also made no difference, and my System folders stubbornly maintained the 13/1/04 drivers despite a reboot and another try to install using the main MSI / NVidia install programme.
In the end, I manually selected each IDE and RAID device from device manager and forced a driver update, pointing the update programme at the MSI driver directory. This finally caused the driver update (which does appear to have sorted out some of my problems).
However, I still had some boot failures, and took Creative's advice ( http://dmzweb4.europe.creative.com/htmlhelp/general/acpi.htm ) and downgraded my "ACPI Uniprocessor PC" driver to an "Advanced configuration and Power Interface (ACPI) PC". In hindsight I am not certain this was the correct move, as it appears to be a one-way process (without doing a re-install of Windows) and is not recommended by microsoft (see http://support.microsoft.com/default.aspx?kbid=309283 ).
I also considered the possibility of the processor not getting enough juice (should be unlikely with a 33A 12V power supply) and I upped the core voltage to 1.55.
I have had a boot hang since the voltage was upped, so I'm not convinced of its help. However, with all 3 "solutions" applied, I have had 4 good boots now. I'm hopeful the problem will at least be helped, if not solved.
Anyone got any additional helpful thoughts?
Cheers,
David

I am having this exact issue and I have no idea what to do!
When I restart, (warm boot) I will often hang after POST.
When I cold boot, I never hang after POST.
When I get to the windows loading, I get the windows logo, but faded. (It changes from black to the Windows logo, and it dies somewhere inbetween.)
About 1 in 5 boots I will work.
I'm using the latest drivers for everything, and this is a fresh install of XP SP2 onto a RAID 0 array.
(MSI K8N Neo2 Platinum)
Help!

Hyper-V 2012 R2 new VM with ISO in DVD boot failed - default SCSI not IDE

Hi, have created some VMs fine on 2008R2 and 2012 Hyper-V but now onto 2012 R2, am using the Gen 2 VM and hitting install error when booting them from the 2012R2 RTM .ISO (downloaded straight from Technet) loaded into virtual DVD:
I see from http://social.technet.microsoft.com/Forums/windowsserver/en-US/53f901e4-5bd0-4e13-80a2-bca2f57b15e9/hyperv-unable-to-boot-from-cd-or-iso-in-vm-machine?forum=winserverhyperv that Hyper-V seems unable to boot from a synthetic SCSI until guest OS actually
installed - so Catch-22! But I can't add an IDE Controller because it's not on the list:
I tried the Integration Services and it seems fine on the Settings (including ticking the only one unticked - Guest Services) although if you need to run them from the DVD, it has the same problem - you can see them loaded (or the Win2012R2 ISO) in the DVD
Media but you can't make them run through booting on SCSI!
The physical drives are SATA not SCSI but presumably no matter as Hyper-V runs SCSI virtually, but why does Hyper-V default to SCSI and how do I get the DVD to run off an IDE instead if that is the way to install a base OS from .ISO? Or is there an easier
way than all this?
TIA, Phil.

I found this article:
http://blogs.technet.com/b/jhoward/archive/2013/11/11/hyper-v-generation-2-virtual-machines-part-9.aspx
I hope this help.
"...yes, we’re acutely aware that the generation 2 EFI boot loader messages persist on the screen and it can be a little confusing. Essentially what the generation 2 virtual machine did was:
Attempt to boot from the CD SCSI device containing the Windows 8 ISO. This is where the ‘Press any key…’ message came from. As no key was pressed, we went to the next boot entry. (And this is where we didn’t clear the message from the EFI CD boot loader)
I didn’t press F12 (in fact, this VM wasn’t connected to a network), so network boot failed
The SCSI VHDX is raw with no partitioning or file system, so this too failed
So why did the generation 1 virtual machine start setup from the Windows media? The answer is simply that it’s the way Windows media is built, and it’s inconsistent between the PCAT and EFI loaders.
However, it’s relatively simple to solve if you want to avoid the press any key message. In fact, we almost have all the pieces from previous parts. In particular, part 4 where we injected keyboard drivers into the Windows 8 media.
If you loopback mount Windows 8 or 8.1 RTM media, and navigate to the \efi\microsoft\boot directory, you will see there are two versions of cdboot.efi
The default version, cdboot.efi prompts for a keypress. The unused version, cdboot_noprompt.efi doesn’t prompt.
So it’s fairly simple to create modified media which uses the noprompt version. First, copy the contents of the ISO to a working directory, rename cdboot.efi to cdboot_prompt.efi, and rename cdboot_noprompt.efi to cdboot.efi.
Do the same with efisys.bin and efisys_prompt.bin
Then re-use our oscdimg command (in an elevated deployment and imaging tools environment) from part 4 to recreate the media.
Best Regards:
Tamás

Boot Failed, Single User FSCK couldn't load, mounting Macintosh HD failed, repair and verify returns no errors, and i need to transfer my data before starting over - HELP!!!!

Lets break down the facts here: My machine is an Intel-Based iMac running Mavericks - 1TB Hitachi Hard Drive
1. Was running an initial baseline image with Time Machine when the computer froze - waited hours - nothing got better and no functions were possible (force quit, etc.)
2. Hard Reboot
3. Upon reboot, the iMac was unable to load the log-in screen. The image was a folder with a "?" on it.
4. Rebooted with option key held down and selected Macintosh HD - Boot Failed
5. Restarted and Rebooted with Command R held down
6. Ran Disk Verify and Disk Repair - returned errors round one.
7. Ran Disk Verify and Disk Repair - Returned no Errors
8. Restart - Boot failed - the "NO" symbol replaced the apple symbol
9. Reboot with Command R
10. Attempt to mount Macintosh HD
11. Mount Failed.
12. Shutdown
13. Connect Firwire to Host computer and Target Computer
14. Boot with Command T
15. TDM entered - Host Machine cannot read Target Hard Drive
16. Shutdown
17. Boot with Command S
18. Endless loop created - Multiple errors including:
     - failed to open create the journal retval 0
     - could not read 512 bytes for the journal header - Return 22
     - Errorno 19
     - hfs_mounterror return: 22
Short of springing for a software online, I have no idea what the next steps are to getting my data moved from the Macintosh HD to my external so I can just reformat and install the OS again. Any help would be greatly appreciated, this is is a serious headache and I cannot lose my data - Thats what I was backing it up for in the first place!!!!

You may not have the luxury of having another Mac but you must know someone who does. You need to boot your Mac into target disk mode. This is going to be your best bet as far as saving your files. Keep in mind that everytime you mess with this computer you are further endangering your data. Also, once your Mac is booted as a target disk, it may be possible to mount it on a windoze computer just to copy your files to another drive. I used to have one here and if i still did I would try this for you but I "offed" it in favor on running windoze (Parallels) on my MBP. But, one way or another, you need to get next to another computer.

Satellite A660 - Will not boot up and HDD boot fail

Hi,
firstly thanks for your time.
Model: Satellite A660 (PSAW3A-07U00R)
The problem started yesterday, the computer was going slow as an application closed, so I held the off button untill the pc turned off. When I restarded the laptop it went to a screen saying: Start windows normally or repair Windows (recomended)
When started normally it just hangs at a blank screen, the repair Windows recommends a system restore to earlier point which didnt work. As it just hangs again. I tried pressing F8 and starting in safe mode but again it just hangs. Then after a few times trying safe mode and another system restore the computer then hangs when I press F8. After this the computer goes past the Toshiba logo screen with F2 and F12 options (which both still work), and then it comes up boot failed then goes blank and comes with boot failed bootfailed with some numbers and letters, then it goes to a small box titled boot menu with 4 options.These are
HDD/SSD Toshiba MK6465GSX
CD/DVD MAT****ABD-CMB UJ141ES
FDD
LAN
If I press ESC it goes through the bootfailed loop and ends up at same screen, if I press enter on "HDD/SSD Toshiba MK6465GSX" then it quickly comes back to screen and at the bottom it says [HDD/SSD Toshiba MK6465GSX] is failed.
I dont understand why it got worse over time. Can anyone think of why this has happend and more importantly how can I get my pc working again? Note: holding 0 then starting does nothing for me atm
regards, Matthew

All you people looking here on this dead thread.....
Toshiba A660 laptops are renowned for having hard drive fails and boot up problems after grinding to a halt.
My solution (after losing 3 hard drives [and a terabyte of family treasured times]) is the following.
Use MALWAREBYTES (free download and use for 28 days)
Scan and fix. Mine found over 300 trojans that 2013 Norton 360 could not find.
Re-boot into safe mode.
SCAN again.
Re-boot and empty the malwarebytes repair files it retains...
Run Norton/McAfee (whichever you have) and you should still have no issues.
Make a back-up repair disc. Ooooops......no you cant...........at least my laptop can`t.
I don`t know why.....
Tell me tosh..... why does windows x64 refuse to allow me to make a system boot disc (even though the laptop is all driver updated and Windows updated)?
Uninstall MalwareBytes when Norton/McAfee tells you there will be a conflict between the two programs.
It tells you to re-boot after uninstalling it.
Then when it re-boots you get a black screen. You cannot even get to bios. You think ytour laptop is turned into a brick frisbee. You pull out the battery in frustration after five minutes.
You replace and re-boot....but again you get no bios or boot up.... you think its destroyed the Bios or graphics somehow....youo can hear the hard-drive but you have no clue whats going on..
Around this time you shake the laptop in frustration.....
Calm down.
Switch on and leave FIFTEEN MINUTES....Ten of which will be a Black nothing screen with maybe a single white underscore line in the top left corner.LEAVE IT ALONE.
Make a sunday dinner for ten people....When you go back to the computer it will be up and running.
When you re-boot again, it will be dead black for five minutes...then boots up... you still think it has a problem... LEAVE IT.
When you reboot again it should work perfect (assuming you have not been overheating it by using it on a cushion on your lap and overheating the insides [use a laptop fan tray]) if you have not shaken your hard drive or caused scrambled damage by pulling the power fifty times like some people do.
I have lost three hard drives and thousands of Gigabytes of treasured family memories discovering the secret the hard way.
Enjoy.
Buy a different brand next time.
ALL Windows system files should be on a SWITCHED (to update) version of Windows.
Spinning drives should be for Data only.

Windows 7 32bit - will not load on warm boot.

I have the same problem on two PCs. They are both HP Workstations xw4600. I have the latest BIOS (786F3 1.22 A) and have tried with the older BIOS as well before upgrading. They will not start Windows 7 with a warm boot (restart). They just repeatedly restart over and over again. I have to turn off the computer and cold start in order to log into Windows, which after doing so Windows works just fine.
UPDATE:
I solved this issue by fixing the startup with the Windows 7 disk (took a couple of tries)) now it works normally.

This issue can be caused by corrupted cookies or cookies that are blocked.
*check the permissions on the about:permissions page and in "Tools > Page Info > Permissions"
*https://support.mozilla.org/kb/fix-login-issues-on-websites-require-passwords
Clear the cache and remove cookies only from websites that cause problems.
"Clear the Cache":
*Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
"Remove Cookies" from sites causing problems:
*Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: "Show Cookies"

New Error - Unable to Create Any Backups (com.adobe.versioncue.boot - Failed to start com.adobe.vers

A new error just started showing up in my Vc logs: com.adobe.versioncue.boot - Failed to start com.adobe.versioncue.backup.schedule.
Since the report of this error, I am unable to create any kind of Version Cue backups. Has anyone else seen this error?
I had hoped that a simple reboot would alleviate the problem, but it didn't. The error occurs during Vc startup (boot). It's a little odd that Vc was mostly fine until I rescheduled my Windows Backup (ntbackup.exe) to run 90 minutes earlier, and failed to tell Diskeeper to also not auto-defrag 90 minutes earlier. (In other words, it's possible that Diskeeper did its thing the same time ntbackup was running.)
Running Windows XP SP3. I'm going to try a repair install of Vc in a few moments.

Update 2: ntbackup restore of System State to day before last successful Vc backup failed to correct the problem. I can't even run a manual backup.
Can anyone tell me how to determine the ClassPath used by Vc?
There is no stack trace from this error - the exception is caught and handled, so Vc continues to run after creating the single log entry posted in Msg-1 above. By knowing the ClassPath, I may be able to restore the corrupted Java JARs, if that is the root of this problem.
I'd really hate to have to (ntbackup) restore the whole computer back to last Monday...

Boot failed: solaris server does not boot

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

Zones not booting - failed to create devlinks: Interrupted system call

I just installed the latest 10_Recommended cluster with 118833-36 kernel patch and now my zones won't boot. I get the error:
(root)Yes Master?> zoneadm list -iv
ID NAME STATUS PATH
0 global running /
- samba installed /export/home/zones/samba
- web installed /export/home/zones/web
- dhcp installed /export/home/zones/dhcp
- dns installed /export/home/zones/dns
- vs1 installed /zdata/zones/vs1
- dss installed /zdata/zones/dss
- test installed /zdata/zones/test
(root)Yes Master?> zoneadm -z test boot
failed to create devlinks: Interrupted system call
console setup: device initialization failed
zoneadm: zone 'test': could not start zoneadmd
zoneadm: zone 'test': call to zoneadmd failed
Also, running devfsadm or drvconfig;devlinks from the global zone will core dump.
Any ideas..??
tia..

First, you gotta change your prompt to something less embarrassing when you post to a public forum :)
I'd forget about the zones problem and focus on why devfsadm core dumps -- that's the core of the problem (no pun intended...no, really!).
First, review the install logs of all the patches installed during the recent service (/var/sadm/patch/*/log). Even if they all show a good completion, check the messages they generated, sometimes they have errors that aren't bad enough to cause a complete failure of the patch. The KJP (118833-36) is probably a good one to start with.
Next I'd "truss" the devfsadm command while it core dumps then get a stack trace of the core (run "adb <corefile>" and type "$C" -- that's old school, I'm sure mdb is much cooler...).
Throw some of the strings from those against sunsolve and see if something sticks.
Good luck!

Boot failed:Enter Filename [/kernel/sparcv9/unix]

Hi All,
one of my support person who has administrator previlages tried move the contents of root to trash directory, in the middle it got hung,and he had restrted the server.
Now the solaris does not boot. It says
boot failed
Enter Filename [platform/sun4v/kernel/sparcv9/unix]
and what ever we enter there it says boot cannot read.
ELF64 read error.
Please suggest some workaround, nearly 200 users are down, actually it is our licnese server.

Hi,
What you could try is the following :
Boot the system from the solaris cd into single user mode.
Find out what the disk is you need to mount and mount it under /a
After you have done this you can see if you can move back the stuff that was moved from the root directory to the trash.
If that works then you could try and boot again from the disk to see if everything works again.
Nico

Boot fail. Invalid signature

Just turned my tv and box on and it says boot fail. Invalid signature. Can anyone suggest what I do?

Switch it off and try it again. Do this a few times if this still persists then I'm afraid dead may have a dead box.
Before phoning however try this :
Factory Reset
Switch off the Vision+ box at the mains socket
Hold down the front panel OK and down arrow buttons
Switch on the power to the Vision+ box
Allow the box to start up (about 15 seconds)
Release the OK and down arrow buttons
The Vision+ box will then contact the servers to get a new copy of its firmware
This will take around 30 minutes
Life | 1967 Plus Radio | 1000 Classical Hits | Kafka's World
Someone Solved Your Question?
Please let other members know by clicking on ’Mark as Accepted Solution’
Helpful Post?
If a post has been helpful, say thanks by clicking the ratings star.

Is or is not "Application & Driver Recovery DVD" bootable? - SafeMode boot fails-corrupt CryptUI.dll

I'm trying to recover my daughter's Pavilion dm4-3170se. My daughter had not made a recovery disk and has no recent back-up of her data file set.
Problems (and what I have done so far) are quite parallel to what the user reported in this amazingly detailed post:
Difference is that in Safe Mode boot (command line or not), Windows boot fails on a dll, specifically CryptUI.DLL.
While amazingly detailed post user isn't getting into Windows boot, I am...for about 30 DLLs before it chokes on the corrupted one. I have tried a number of other things to get past it to no avail.
My daughter's original Recovery Disc set bought the farm when her house burned. So I ordered and got a replacement set from HP. I am loathe to use it before recovering her data files because she will lose maybe 40% of her professional work.
The delivered Recovery Disc set includes an "Application and Driver Recovery DVD". Given >20 years of Wintel machine tradition, I'm presuming it's bootable. Amazingly Detailed Post user got hers to boot from her DVD drive. But configuring the BIOS to seek the DVD drive as the first boot choice doesn't get it to boot after two tries.
Before I pour more time into this, I'd like the Collective Wisdom here.
Q1: Is this HP disc, numbered 691822-B22, meant to be bootable?
Q2a: If it is, do you imagine I can use the command line interface to copy identifed-as-bad DLL(s) to the HD?
Q2b: If it isn't, why the, er, gollygoshdarn isn't it? Must be an actual reasonable thing...
Thanks for all insights based on experience.
This question was solved.
View Solution.

Hi:
Any HP application and driver DVD I have ever used is not bootable.
It should autorun from the windows desktop once windows has been reinstalled.
That is the only question I can answer of the ones you asked.
Suggestion...
Make your own W7 installation ISO from the link below.
Use that to install W7 and do not delete any partitions or format the drive.
Windows will install and create a Windows.old folder of the current operating system.
Then you can copy any files you need from the Windows.old folder after W7 is installed.
Once you are sure you got what you need, run the recovery disk set to restore the hard drive to its out of the box condition.
Link to W7 ISO files is below. Use the W7 x64 home premium file from the SP1 Media Refresh listing.
http://forums.mydigitallife.info/threads/14709-Windows-7-Digital-River-direct-links-Multiple-Languag...
Then use this tool to transfer the iso file onto a DVD or 4 GB USB flash drive. The tool will also make the iso file bootable.
http://www.microsoftstore.com/store/msusa/html/pbPage.Help_Win7_usbdvd_dwnTool

U530 boot failed

I have a Lenovo U530 laptop that intermittently encounters a 'boot failed' error.
This has happened 6 times in a 4 month period. Each time it has occurred I have clicked
through the following 5 screens until it requested a system restart:
1. EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. [Ok]
2. EFI Network 0 for IPv6 (08-9E-01-F5-44-D4) boot failed. [Ok]
3. Default Boot Device Missing or Boot Failed.
     Insert Recovery Media and HIT any key
     Then Select 'Boot Manager' to choose a new Boot          [Ok]
     Device or to Boot Recovery Media
4. Boot Manager
     Boot Option Menu
     EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. (this line is selected)
     EFI Network 0 for IPv6 (08-9E-01-F5-44-D4) boot failed. [Ok]
     ^ and v to change option, ENTER to select an option
5. EFI Network 0 for IPv4 (08-9E-01-F5-44-D4) boot failed. [Ok]
Screen 6: No bootable device -- Please restart system
At this point I power off, then on via the power switch and it boots normally.
I am aware of the suggestions to boot from a recovery drive but that is not my problem.
I am able to successfully boot by powering off/on.
I would like to figure out what is causing this. Any suggestions on what steps to take
to diagnose this the next time it occurs?
Lenovo phone support has been of no help.
TIA
Luke

If you are not connecting to a lan at boot up try to disable "PXE boot to Lan" in the bios. Else temporarily disable it. Once booted try running in command prompt with admin rights "sfc /scannow". Do not include the quotation mark. You might also try running chkdsk to check the hdd for defects.

MS-6580 - Warm Boot Fails

Similar Messages

Maybe you are looking for