Cold Boot Lockup (D Bracket: GGRG)
Hi Guys (first post so be gentle),
I am having a problem with my 875 motherboard on after being turned off at the wall. The D-Bracket shows RRGR which the manual says Initializing Keyboard Controller. I cant ever remember seeing this problem before installing the 2.4 bios or the extra 512mb of matched ram, plus my machine as you can see, isnt overclocked by anything which would break something.
I dont see this problem often as i only turn the computer off at the wall when i move it around or something like that.
Does anybody have any ideas why this would be happening?
Many thanks
Andrew
ps. i am away from the computer for most of the day so hopefully somebody will have an idea by tomorrow.
I emailed msi technical support and didnt get a reply back in like 1 week so i posted on here to see if anybody would have an idea while i wait thanks for your help so far guys. I will email support again.
When i upgraded the bios 3 weeks ago, i changed all the settings back to how they were before (SATA settings / Performance Settings).
Like i said, the machine is totally stable during operation, its just when the machine cold boots from no power.
hmm
Similar Messages
-
IPad revert to preconfigured saved state on cold boot?
We're looking to create a saved state for all the apps and OS settings for our many iPads that would reset automatically on a cold boot. Apple Configurator seems to require too much finagling. We're just looking for some kind of scripted solution that could recall our preconfigured settings for each iPad, restoring it to our business's preferred "pristine" condition whenever the iPad is started from a fully off state.
I've searched for this everywhere online, but I'm not finding what seems like a very common need for a business that relies on iPads.
Thanks in advance for any resources/apps/info you can provide!Is it the same keyboard you tried on all occassions?
Sometimes there is a little gap, when the I/O-port metal bracket is not in properly.
Have you tried PS2 mouse and keyboard? Is there any mentioning of this in Device Manager.
Windows is keen on having USB-things hot-plugged, while that is totally wrong for PS2-things. -
K8N Neo2 Platinum - satisfied except cold boot
My new build is doing well except for the near-famous cold-boot problem. When the box has been off for a while, I hit the power button, fans & drives spin up, the optical blinks a couple times, but no video or POST. The LEDs look like 4 green, but 2 seem dimmer, as if they're just reflecting the light from the other 2. A 5-second hiit on the power button shuts it down, hit it again and it fires right up, but stops during post with the message that it's in safe mode and to reset my (nonexistent) OCs. From this point I can F1, boot up, and run for hours. No probs unless it's off for a while. I have seen the problem since early in the build, when I powered up outside the case with just 1 stick of RAM and the LEDs (no vid or drives).
Searching the board shows a lot of people having the problem, but nobody seems to have a solution, so I went to the support site to check the knowledge-base and FAQs. Interesting to find there that A64 boards do not appear to exist. No FAQ, no option to spec socket 939 or 754 to search the KB.
Maybe if we get a number of us with the problem to post specs & observations in one thread we can spot a pattern?
I have noted that I can't just do an on-off-on. It has to spend 20-30 seconds in the lockup mode before cycling the power results in a successful boot.
BTW all, some really nice things are happening with RAM prices lately. I got my 2 gigs for US$190 delivered.
K8N Neo2 Platinum
Athlon64 3500 (130 nm)
2G (4 x 512) SuperTalent PC3200 RAM
2 120G Maxtor SATA (1 & 2) in raid0
1 160G Seagate SATA (3)
1 Sony DRU 720A 16X dual-layer DVD +/- R/RW (primary master)
PNY Verto nVidia 6800 vid
Mad Dog 600W PSU (30A on +12)Quote from: elliott on 13-April-05, 09:23:05
I'll give the bios a shot, but the idea of using the HT to slow the box down and then speeding it back up again in Winders...
Putting HT to 4 does not slow down the box... Especially if ur FSB is over 200 (if ur overclocking) like in my case: FSB=260mhz, I must put down the HT to 4 in order to run everything perfect. HT standard is 200x5=1000, in my case its 260x4=1040... as long as HT is between 800-1200... I believe there is no real time performance loss as long as u have STABILITY. I have seen a lotta people in this forum fixing stability problems just by reducing the HT when they overclocking... some cases even to HT=3. -
PowerBook G3 PDQ Loses Startup Disk on Cold Boot
I have a PowerBook G3 PDQ (266Mhz, 192MB RAM).
For the longest time it's had Mac OS X 10.1 on it, along with Mac OS 9.2.2.
I always noticed that it started up with Mac OS 9 after a cold boot, even if the startup disk was set for the OS X system folder.
So, I reformatted the disk and re-installed OS X 10.1 (being the only version of OS X i own that will run on the machine). Everything ran fine.
But after a cold boot, it lost the startup disk, and i get the flashing question mark on a floppy disk. I can hear the hard disk spin up, then down, then up, then down. Eventually the machine shuts off. I have to boot off a Mac OS 9 CD and select the OS X system folder to make it boot again.
Anyone know how to fix this?
Thanks.Like S.U. I replaced the PRAM battery on two Wallstreets (got batteries from OWC) and, although I'm very nervous about working with tiny parts, I found it to go well by following the iFixit instruction to the letter. The innards weren't nearly as fragile as I expected and I allowed plenty of time so I wouldn't feel compelled to rush.
The most serious issue I encountered was that the original battery's cable on one WS managed to get snagged under the metal battery bracket when the computer was originally assembled. This compounded the problem that the user--a cigarette smoker--had inadvertently melted the plastic between the trackpad and the front edge of the upper case. This made the case weak at that point and I had to be very careful in dislodging the stuck cable.
I had mentally made the job much more difficult than it turned out to be. Just have the right tools:
1) You may find that, to remove the heat shied screw--requires a Philips #0 screwdriver--you may need to shorten the point of the driver to better fit the shallow cuts in the screw head. The screw is soft and can easily strip out if you indiscreetly use an unmodified #0 Philips.
2) Have an old ice cube tray or egg carton handy to keep the screws sorted. -
To all:
I recently replaced my old MB and CPU (Asus a7v133/AMD 850 Mhz T-bird) with a K7T Turbo2/AMD XP 1800+ Thoroughbred. All of the other components are the same (see below), except the PSU. I replaced my old one hoping that it would solve my problem.
When I cold boot the system the fans turn on but the system does not post and the monitor remains off. If I hit the reset button on the case the system boots normally. Also about 20% of the time the system emits a constant beeping (sounds like an alarm clock) when I cold start, which goes away when I hit the reset button. I have also noticed that the system trys to boot when I flip the power switch on the PSU. I don't know if this is normal with MSI boards, but my Asus would not boot until I hit the power button on the case.
Any ideas?
Thanks,
Dave
System Specs:
K7T Turbo2 (BIOS ver. 3.6)
AMD XP 1800+ Thoroughbred
896 MB PC133 RAM (3 sticks; 512 (crucial), 256 (crucial), 128 (?))
CoolMaster CPU Fan Model#: CP5-6J31C-01
Inno3D GeForce2 MX400 (32MB)
Sony 1.44MB Floppy Drive
Maxtor 20GB HDD
Plextor CD/RW
SoundBlaster Live Value
T10/100 Ethernet Card
PS/2 Keyboard
PS/2 Mouse
PSU: Kingwin Extreme series ATX 450watts:
+3.3V @ 28A Max output
+5V @ 45A Max output
+3.3V and +5V Current = 225W
+12V @ 18A Max output
+12V Current = 216W
Max Combined Wattage = 430W
-12V @ 0.8A Max output
-5V @ 0.5A Max output
+5VSB @ 2.0A Max outputTo all:
Thank you for all of your suggestions. When I got home today I tried to boot up the system with only the 512MB RAM stick (Crucial Part #:CT64M64S4D) inserted in DIMM slot 1. The computer responded as described in the first post of this thread. I then tried the 256MB stick (Crucial Part #:CT32M64S8D75) in DIMM slot #1 and the system booted normally. I then subsequently added the other sticks of RAM in the remaining slots (512MB in slot 2 and the 128MB in slot 3). I think the 128MB stick is hitachi but not 100% sure...it might be Diahatsu (my short term memory isn't too good). I guess the 512MB stick did not seat well in DIMM slot 1.
However, my system still wants to boot up independently of the button on the case. The system will power up once I flip the PSU switch to the on position. I don't know if this is normal for MSI boards, but my Asus system would not boot until I pressed the case button. I must admit I am still unclear of the JFP1 wiring. However, I have tried the power switch and reset switch wiring in all combos and this did not solve the issue. Is there a BIOS setting or jumper somewhere that I am missing? Any more info would be useful.
Thanks again for the suggestions!
Dave
P.S.
Mauricio16,
Please read the entire thread before posting a response. As I stated earlier, I DO NOT have a D-Bracket...yet, and I HAVE tried a different PSU. Thanks for your suggestions though. Luckily it was not as an exteme of case as it could have been.
I guess both of us have learned a valuble lesson from this experience. When in doubt, reseat the RAM. -
This has happened several times when I boot my PC from cold start the Bios seems to boot fine then the XP screen comes up, the blue bars scroll and then the screen will go black and the mouse pointer should appear but sometimes the mouse pointer does not appear and I have a blank screen. If I hit restart the computer boots fine and checkdisk will run and find no problems. This happens sporadically but only from a cold boot. It has never happened from a restart. I have the latest Bios 1.3, Via 4.46 drivers, SP1, Nvidia's 40.72 along with the latest updates for my other hardware. It has happened with prior bios's and earlier drivers. I am not overclocking. Most of the bios settings are default. Memory settings are at 333 controlled by SPD.
My Rig:
AMD Athlon XP 2600 (333 fsb)
MSI KT4 Ultra
XP Professional SP-1
512 Corsair PC3500 XMS
3 Western Digital HD (2) 100Gb and (1) 30Gb
Enermax EG465AX-VE powersupply
MSI Gforce4 ti4600 128mb
Terratec DMX 6Fire Sound Card
Promise Ultra 133 TX2 card
Intel Pro/1000 MT desktop adapter
Plextor 40x12x40 CDRW
Toshiba DVD
Coolermaster ATC-110 case
CoolerMaster HHC-001 Heatpipe HSThe D-Led bracket had all 4 leds green when the XP logo screen goes blank and the mouse pointer should appear. I have installed XP a few times and swapped most of the hardware with same problem.
I also have a KT3 Ultra 2 before the KT4 Ultra and never had those cold boot problems and I was using alot of the same haredware.
Anybody with any suggestions -
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. -
Laptop screen just goes dark and i have to cold boot
Hello.
My Macbook Pro 2.66Ghz i7, running 10.8 keeps crashing, in various programmes and its getting annoying.
The screen just goes dark but the lights stay on on the keyboard (if thats any help) and i have to cold boot.
Ive got a crash log from console if anyone can help please.
Thanks for your time.
Warren
090113
Interval Since Last Panic Report: 3787974 sec
Panics Since Last Report: 14
Anonymous UUID: 32C9008D-3F1D-419E-87F5-94D22BAC66E1
Wed Jan 9 20:51:11 2013
panic(cpu 0 caller 0x9d4c9b): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xc0000000 0x7fa98000 0x0a5480a2, D0, P2/4
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x551fb888 : 0x21b837 (0x5dd7fc 0x551fb8bc 0x223ce1 0x0)
0x551fb8d8 : 0x9d4c9b (0xbea28c 0xc5a800 0xbf8e60 0x0)
0x551fb978 : 0xaef608 (0x8c37004 0x96e6004 0x100 0x6)
0x551fb9c8 : 0xae6601 (0x96e6004 0x100 0x551fb9f8 0x9c4778)
0x551fb9f8 : 0x16d29a6 (0x96e6004 0x100 0x438004ee 0x0)
0x551fbb38 : 0xb0e2b5 (0x96e6004 0x9770004 0x0 0x0)
0x551fbb78 : 0x9dde7c (0x96e6004 0x9770004 0x0 0x0)
0x551fbc18 : 0x9da55b (0x0 0x9 0x0 0x0)
0x551fbdc8 : 0x9dc42a (0x0 0x600d600d 0x702a 0x551fbdf8)
0x551fbe98 : 0x970582 (0xc1d00011 0xaa910001 0x20802040 0x551fbee0)
0x551fbef8 : 0xd3257d (0x8e53000 0x551fbf4c 0x0 0x7)
0x551fbf58 : 0xd3271a (0x8e22000 0xd39e54 0x551fbf78 0x2a45c9)
0x551fbf78 : 0x230235 (0x8e22000 0x0 0x551fbfc8 0x227cea)
0x551fbfc8 : 0x2a179c (0x863ea0 0x0 0x10 0x9073fc0)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AGPM(100.12.31)@0xd2f000->0xd39fff
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
com.apple.nvidia.nv50hal(6.4.0)@0x159c000->0x19b0fff
dependency: com.apple.NVDAResman(6.4.0)@0x96e000
com.apple.NVDAResman(6.4.0)@0x96e000->0xc5bfff
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 5344089076982
unloaded kexts:
com.apple.driver.AppleUSBUHCI 4.2.0 (addr 0x1437000, size 0x65536) - last unloaded 125829414855
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 27734116643
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AGPM 100.12.31
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.driver.AppleHDA 2.0.5f14
com.apple.driver.AppleMikeyDriver 2.0.5f14
com.apple.driver.AudioAUUC 1.57
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.driver.AppleIntelHDGraphics 6.4.0
com.apple.driver.AppleIntelHDGraphicsFB 6.4.0
com.apple.driver.SMCMotionSensor 3.0.1d2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.GeForce 6.4.0
com.apple.driver.AppleGraphicsControl 2.10.6
com.apple.driver.AppleLPC 1.5.1
com.apple.kext.AppleSMCLMU 1.5.2d10
com.apple.driver.AppleUSBTCButtons 201.6
com.apple.driver.AppleUSBCardReader 2.6.1
com.apple.driver.AppleIRController 303.8
com.apple.driver.AppleUSBTCKeyboard 201.6
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleUSBHub 4.2.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.iokit.AppleBCM5701Ethernet 3.0.5b8
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.14
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.driver.DspFuncLib 2.0.5f14
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.0.5f14
com.apple.iokit.IOHDAFamily 2.0.5f14
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleBacklightExpert 1.0.1
com.apple.driver.AppleSMC 3.1.0d5
com.apple.nvidia.nv50hal 6.4.0
com.apple.NVDAResman 6.4.0
com.apple.iokit.IONDRVSupport 2.2.1
com.apple.iokit.IOGraphicsFamily 2.2.1
com.apple.driver.AppleUSBHIDMouse 162
com.apple.driver.AppleHIDMouse 162
com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBHIDKeyboard 141.5
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBMultitouch 207.7
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0
081113
Interval Since Last Panic Report: 3787463 sec
Panics Since Last Report: 12
Anonymous UUID: 32C9008D-3F1D-419E-87F5-94D22BAC66E1
Tue Jan 8 20:23:33 2013
panic(cpu 2 caller 0x9d4c9b): NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0a2910de 0x00100000 0x00000000, BAR0 0xc0000000 0x7ff5a000 0x0a5480a2, D0, P2/4
Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)
0x55143888 : 0x21b837 (0x5dd7fc 0x551438bc 0x223ce1 0x0)
0x551438d8 : 0x9d4c9b (0xbea28c 0xc5a800 0xbf8e60 0x0)
0x55143978 : 0xaef608 (0x8e24804 0x854f004 0x100 0x2b1f6a)
0x551439c8 : 0xae6601 (0x854f004 0x100 0x551439f8 0x9c4778)
0x551439f8 : 0x16d29a6 (0x854f004 0x100 0x438004ee 0x8517800)
0x55143b38 : 0xb0e2b5 (0x854f004 0x9347004 0x0 0x0)
0x55143b78 : 0x9dde7c (0x854f004 0x9347004 0x0 0x0)
0x55143c18 : 0x9da55b (0x0 0x9 0x0 0x0)
0x55143dc8 : 0x9dc42a (0x0 0x600d600d 0x702a 0x55143df8)
0x55143e98 : 0x970582 (0xc1d00011 0xaa910001 0x20802040 0x55143ee0)
0x55143ef8 : 0xd3257d (0x8e3e000 0x55143f4c 0x0 0x7)
0x55143f58 : 0xd3271a (0x8e0e800 0xd39e54 0x55143f78 0x2a45c9)
0x55143f78 : 0x230235 (0x8e0e800 0x0 0x0 0x0)
0x55143fc8 : 0x2a179c (0x863ea0 0x0 0x10 0x905bb80)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AGPM(100.12.31)@0xd2f000->0xd39fff
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
com.apple.nvidia.nv50hal(6.4.0)@0x159c000->0x19b0fff
dependency: com.apple.NVDAResman(6.4.0)@0x96e000
com.apple.NVDAResman(6.4.0)@0x96e000->0xc5bfff
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x928000
dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x961000
dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x93f000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10K549
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 1273820200696
unloaded kexts:
com.apple.driver.AppleUSBUHCI 4.2.0 (addr 0x1437000, size 0x65536) - last unloaded 91902192143
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 24820623038
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AGPM 100.12.31
com.apple.driver.AppleMikeyHIDDriver 1.2.0
com.apple.driver.AppleHDA 2.0.5f14
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.driver.AppleMikeyDriver 2.0.5f14
com.apple.driver.AudioAUUC 1.57
com.apple.driver.AppleIntelHDGraphics 6.4.0
com.apple.driver.AppleIntelHDGraphicsFB 6.4.0
com.apple.driver.SMCMotionSensor 3.0.1d2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.GeForce 6.4.0
com.apple.driver.AppleGraphicsControl 2.10.6
com.apple.driver.AppleLPC 1.5.1
com.apple.kext.AppleSMCLMU 1.5.2d10
com.apple.driver.AppleUSBTCButtons 201.6
com.apple.driver.AppleUSBCardReader 2.6.1
com.apple.driver.AppleIRController 303.8
com.apple.driver.AppleUSBTCKeyboard 201.6
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleUSBHub 4.2.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.iokit.AppleBCM5701Ethernet 3.0.5b8
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.driver.AppleSmartBatteryManager 160.0.0
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.14
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.driver.DspFuncLib 2.0.5f14
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.0.5f14
com.apple.iokit.IOHDAFamily 2.0.5f14
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleBacklightExpert 1.0.1
com.apple.driver.AppleSMC 3.1.0d5
com.apple.nvidia.nv50hal 6.4.0
com.apple.NVDAResman 6.4.0
com.apple.iokit.IONDRVSupport 2.2.1
com.apple.iokit.IOGraphicsFamily 2.2.1
com.apple.driver.AppleUSBHIDMouse 162
com.apple.driver.AppleHIDMouse 162
com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBHIDKeyboard 141.5
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBMultitouch 207.7
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOAHCISerialATAPI 1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 6
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f16
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545050B9SA02, 465.76 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0237, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000 / 6
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000 / 3
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd130000 / 5
USB Device: Apple Optical USB Mouse, 0x05ac (Apple Inc.), 0x0304, 0xfd133000 / 7
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd132000 / 6
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000 / 4
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000 / 3Hi, Wobble Woo.
The repeated kernel panic you're experiencing is a common issue on the mid-2010 MacBook Pro 15". I have the same laptop and the same issue. It's caused by the descrete graphics card. One solution, albeit a bit disappointing and temporary, is to use an application called gfxCardStatus. It runs in the statusbar and tells you which GPU is running. You can use the application to set your laptop to use the integrated GPU only, which will put an end to your kernel panics. But if you are using applications which require heavy graphics (such as photoshop and most video games), you'll just have to count your luck.
Some other users have had their motherboard successfully replaced. Take it to an Apple Store and ask them to run a GPU test. They should find the error (a manufacture defect, it seems) and replace your motherboard, with or without warranty. I hope this helps.
Regards
Raptor -
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) -
[P6N SLI Platinum] black screen NO BOOT after D-bracket replug [RMA-SOLVED]
Quick setup specs;
P6N SLI Platinum
E6600 (box/stock 2400mhz basic)
2x 1Gb DDR2 6400 Gskill HZ
Sapphire ATI X1600Pro (PCI-e basic)
Aerocool Zero DBA 620W
(2 HDs sata, 2 Hds pata, 2 optical pata at first -all OK at first, disconnected after, so irrelevant here ,( )
(XP Pro clean new install from start)
I tried to check the forum old posts before trying to write that new one, but could not find any really related totally adequate posts so far (or i missed them, sorry if so, then -?). I could already find very useful informations on first aid usual 'rebooting' procedures to follow with minimum new boot configurations, d-bracket new LED signals etc. But so far no luck, all same, nothing better, nothing cured here for the stuation here. ,(( Also excuse my english if not perfect, i am not english either. ,(
VERY bad & sad problem here... ,(((( :
All was working perfectly great during 5 days.. the P6N SLI platinum install went GREAT initially (as normal, not a first pc built, all normally happening, so far so good, etc).... all hardwares compatible together at first (dedicated ATX 'full' 8x8 pins connector too for the cpu only for ex -all working perfect at first try. quick tensions 5V/12V under msi dual core control tool perfect too etc), was great easy going/ great strong ultra-stability feeling on the hardware side.. i was just now concentrating on the software side (no special BIOS tweaks even attempted so far, all on basics-normal e6600/ddr2 auto-settings, apart at the end ddr2 quick test -when problem occured- on 450(900?)Mhz at 2.1V, far far easy under its possible specs max anyway.. and had been working perfect for 3 days with that little ddr2 boost try -no time for special bios further tweakings now, etc), reinstalling and transfering/reorganizing slowly my necessary files/hds/softwares from old to new setup, no oc, nothing special tempted (i was planning oc, new cpu more suited fan/silver6 etc only for the end..), LAN file sharing setup done, Realtek audio setup test done, etc ; installation had been so far one of the quickest and problem free ever... explaining maybe also my fatal lack of cautioun for just (too much) 3 sec in the end after 5/- days of perfect working new ring going on.. ,((( :
At first, i also tried to immediately install the D-Bracket too to check possible hardware install problems -very useful feature i of course thought too..and wanted to try too, "in case of"..- (installing it from quick reading of the printed manual..with no colour pic coding inside..and quick error coming from there thereafter with an initial mismatch usb/jbd1 inverted plugs connections.. *both* having the exact same pins numbers and dispositions, beeing side by side on mainboard layout.. and so able to connect both headers indifferently.. so i did not see it immediately (( .. and no way to see it otherwise as such, anyway.. ,( ), just to be sure all was ok. I noticed that LED were of course, never lightning (not normal).. but as EVERYTHING else was working fine (GLAN, sound, etc etc).. i did not bother more than that -- error checking not necessary.
Till that fatal clumsy day i wanted suddenly to.. check the D-bracket too. ((((
All was working well, XP pro opened for hours as usual etc..
i had not yet totally finished to install the motherboard in the pc-case (always on desk, free in sight..)... so i could always see the connections on it. ... and i noticed that ... the colour headers codes were NOT matching (usb=yellow..).. i had just stupidly initially badly connected the D-Bracket jdb1/usb adjacent plugs (inverting them), so... And still, all had ever worked perfect.. except the D-Bracket, of course, was sending back no lights then, obviously.. so i did the fatal error.. confident all was stable enough and strong if even that initial plug error had had no consequences at all.. i did the fatal bad move to try to UNPLUG the D-Bracket connectors and put them back in right orders WITHOUT switching OFF the power supply so... like an hot USB plug, sort of, in a way. fatal error.. :( :( :(
As soon as i began to remove the usb/jdb1 connectors and put them back in normal order... the system suddenly SHUT DOWN ... no special bad noise, no special smell.. just sudden SHUT DOWN.
From there.. impossible ever to boot back again the so far perfectly working machine (((((((((((( , always same till now :
i switch on the power supply.. orange led appears on motherboard (ok)... i switch on the motherboard.. green led on motherboard appears (ok)... CPU fan begins (ok), video fan begins (ok) .... and... NOTHING.. total black video screen. no more even possibility to see the BIOS. :( total dead startup .. and the fans are going on eternally, blocked eternally in that inital startup with leds on too (no sudden shut down after a few seconds.. just.. nothing)... :(
Suprem irony.. the D-bracket LED seems to 'work' now.. "of course". Just the PC no more booting at all ^. Only thing is that only green LEDs are appearing, no red ones... simply the sequence, from start and never changing :
1. GREEN 2. GREEN
3. GREEN 4. (---) (not red, just nothing -?)
If i look in manual, it means "Testing RTC (real time clock)". I don't know exactly what it means *here*, but sounds to me it is the most basic initial first BIOS checking.. and BIOS can't be reached for even that so ; BIOS fried???? :( :(
I tried every 'standard' things recommanded usually here in older posts, for new boots recovery attempts thereafter in such 'boot errors' situations (clear cmos button pushed in every possible ways -quick, long, quick etc..-, removing little by little everything but the very minimal least energy taxing setup; keyboard, cpu, video, motherboard; 1 ddr2 nearest cpu slot.. point).. NOTHING. Worst, i tried to boot with one of those elements missing.. exact same D-Bracket lightning from start to.. eternally (123 GREEN 4-nothing). Even tried to remove the little (cmos?) KTS lithium battery for a few hours -that could work sometimes with the old already ultra-sensitive amd/nforce2 chipset bioses problems, so i tried there too-?-; same 3 green lights and fans running and nothing else happening from there.. ((
Always the same; total dead boot as above. black screen. no possible access to even bios panel. ,(((
So my desperate questions, now: of course, the origin is obvious here; all happened "by my fault" when i tried 'too quickly' to 'hot-plugging' replace correctly the D-BRACKET plugs *without* switching off the power supply... all shut down suddenly when i put back correctly the usb& jdb1 headers... :( ;
- do you think there could be any possible last HOPES to recover the situation that i had missed (a well known situation in such d-bracket handling 'common' (?) connection error, a simple trick to try i had missed ??)
- do you think i FRIED something in the process on the motherboard ?? :( :(
- do you think it is 'only' the BIOS (fried????) ?? :( :(
- do you think i could have fried a specifical external key component in the process (not necessarily motherboard) : ddr2 modules, cpu, video card????? :( :(
- is my only solution is to send the motherboard to RMA (no other ways now) ???
please, don't hesitate to give me any possible hints to try to avoid the RMA process.
can i avoid it, right now?
is that possible to fry an whole board just with such a D-Bracket 'hot plug switch' (on a so far perfectly working -light- setup - no oc, little video card, etc) ???? :( :(
That is the only C2D Intel/ddr2 motherboard i have here around. No possibility to test elements by elements for precise error checking (cpu, ddr2 modules, video card or powersupply).
Only things i could check so far are;
- the power supply (aerocool 620W zeroDBA) ;
i tested it back on my old amd xp-m nforce2 setup.. always working apparently. NOT 'fried' so, apparently. but no way of course to test for exemple the special 8x8 (or 8x4) Intel ATX cpu connector on old xp-m motherboard. But power supply NOt fried at least, apparently -?
- the video card.
no way for me to really test the pci-e card on other motherboard around but.. i tried a very old PCI VGA card.. that one works on old setup.. and on P6N, no effect, doesn't improve the situation. So, not sure the new pci-e video card isn't fried.. but a new video card doesn't correct the dead boot problem.. (
No way for me to test the ddr2 or CPU directly though.
Do you think DDR2 or CPU could have been fried in the process too ???
or just, as i fear anyway, 'simply', the motherboard BIOS fried -??? :-(
Really, thx for any suggestions..
if there could be an 'hidden' trick i did not try yet to try to recover the (initially working perfectly!!! (( ) setup, WITHOUT engaging the motherboard RMA process (at least 2 or 3 weeks lost here to wait the return..online store etc..)....
please, suggest me.. ,((
i am *really* very sad of that stupid clumsy idea to want to 'enable' the D-Bracket.. all was working great so far.. and i lost all with just that stupid idea to try an hot plug bracket reconnection without switching off the power supply it seems.. can it be possible,sigh?? all seemed so stable before that, that i.. just lost my usual cautious just 3 sec too long it seems... :-(
Thanks in advance
hoping post not too long too, but i tried to expose the situation as precisely as possible; first time i ever had such a problem with a motherboard/system install.. that is quiet ironical knowing it was also the best and quickest/easiest easy going new built i ever had so far too.. till then ,( .. and all came from the 'helper' d-bracket 'luxury second hand possible boot helper diagnostic tool' checking in the end too, here.. really hoping i can avoid an RMA process.. and no other hardware elements (apart the motherboard?) could have been damaged in the process ? ,(((hi, thx a lot for the quick answer. sorry for the length indeed (i did not know exactly how to describe the situation.. without omitting any later possibly important details).
Alas, i already tried that many times in following interesting asnwers on similar problems in old posts here; did NOTHING. ,(
But after your post, i tried it again, and removed for the remaining *hours* (6/8h?) the cmos battery as suggested again *too* so -pushed again the clear cmos button etc when battery out, then when in again, then replugging the powersupply etc; NOTHING better alas too. always same, no boot, black screen, no bios. ,(
Problem always the same, to sum up, for clarity:
power supply on => orange motherboard led is lightning up, motherboard on => green motherboard led is lightning up, cpu/video/case fans are working up as normal and.. that's all. nothing else forever. black screen. no signal. not a single chance to get again the bios setup screen.
another detail i omitted, maybe; keyboard lights are all lightnng up too.. and stay blocked in that state too. tested with 2 different keyboards, same. to shut down the leds, fans etc, only one solution, shut down the power supply button directly, at that stage.
right now, i test on barebone minimal system as recommanded too;
cpu, 1 dimm (closest cpu slot), video, keyboard. all rest disconnected.
i of course tried to reset the cmos with the 'magical red button' many times before, with power supply cable plugged out, pushed the button trying almost every possible way so far (quick, long, long sequences, short sequences etc etc)... changed NOTHING so far -is that thing working?? ,(. and right now, same after hours with cmos battery removed too. ,(
the d-bracket leds are always (now it is correctly plugged..) :
123 GREEN 4 (nothing)
"Testing RTC (real time clock)"
another 'interesting' detail is that; those leds are appearing IMMEDIATELY after the motherboard is switched on, from start (green led appearing on P6N). and it is staying as such till the end. nothing else. i tried to connect also the case speaker ; no bips, no sound signals at all too.
I also remind the system was WORKING like a dream during 5 days *before* i had that sudden TOTAL boot problem.... AND i touched almost nothing in the bios too all along, for initial security reasons too.. (i was concentrating on the software installs anyway right now, NOT on the oc side..). The ddr2 quick little change i did was also the ONLY change i tempted to simply test quickly some setting i already saw working without problem with that P6N and that kind of ram.. and it was working without problem so far too, so.. all the time idem. And it had been perfectly working for 3 days as such untouched from there; no problems at all (those memory modules have been seen on that motherboard largely at those specs, why i did that quick test anyway.. far under their possible max -micron chips). it was even working so well i forgot to put the setting back as default after that quick ram test.. so much it was stable too (even if i had not time to do real memtest test on that one - i did for many hours with the initial automatical default settings too, to check the ram quality, was perfect for many hours, so ok too, no bad ram initially too-; was so stable for all my XP software installs operations etc.. that i forgot it thereafter, to be true..why it stayed like that till that moment (incidently).. but i preferred to mention it 'just in case' though, yes. i also did not push at all the dimm voltages in the process, it was always far inside the specs at 2.05V to be exact -usual for that ram too up to those numbers easy for it. i did not push the ram voltages either so..).
The problem ONLY appears when i wanted to unplug the *initially* badly connected D-bracket headers so (inverted headers.. but that caused NO problems either so far too for the system stability.. only the LEDs were of course not working so far..) : i did the error to NOT switch off the power supply. :(
*then* immediately the system shut down... and above situation appeared. ,(
BUT all was working perfect before.. ram setting included so. ,((
So my simple questions now too ;
- do you know what means *exactly* the d-bracket message 'Testing RTC" (123 GREEN, 4 nothing).. initial bios problem, isn't it?? other ways to recover it now?? ,((
- is it a WELL KNOWN PROBLEM when we try to disconnect and replug too hastily the d-bracket headers without switching off the power supply (*my* main erorr here, it seems :( :( ) ????
... and of course, do you think it could have *fried* another key component (cpu, ram -?? why i reminded the setting, just in case-?-, video card? .. ) with that d-bracket initial disconnection error ... ,(
as i said, i have no secondary c2d/ddr2 motherboard here : no way to test the cpu and ddr2 modules on another motherboard to be sure too here. :( i absolutely can't know if they have been damaged or not, here.. :( :(
any other idea for the motherboard itself though ??? ,(
once again, thx a lot for any suggestions and precisions on that problem (is that a COMMON well known problem with the d-bracket, when we unplug and replug it without extrem care like i did -my main inattention error it seems.. mainly because all was so stable before too.. ((( - without shutting down the power supply/system FIRST ???? can it be possible 'only' that shut down all the system??? (( )
thx in advance again + -
Desktop items get unsorted after cold boot on Snow Leopard 10.6.2
The Desktop items get unsorted after cold boot on Mac OS X 10.6.2 (Snow Leopard).
I have about 25 items (mostly aliases of files or folders) on the Desktop, sorted as vertical rows on left and right side of the screen.
When the issue hits, they all get located as vertical rows on the right side of the screen, unsorted in relation to their custom relative position before the issue.
Any idea? Thanks.Hi ApMaX
According to wikipedia the .DS_Store files on Mac OS X contain the metadata for icon position and view settings. If the file permissions for the Desktop .DS_Store file were incorrect then one could assume that the icon position and view settings aren't being saved.
First let us check the permissions on the .DS_Store file for the Desktop we can do this by running the following command in Terminal (located in the Utilities folder)
ls -ld /Users/<<UserName>>/Desktop/.DS_Store
replacing <<UserName>> with the short name of your user account (name as viewed in the finder sidebar)
On my system I get the following permissions readout
-rw-------@
Further info on .DS_Store files: http://en.wikipedia.org/wiki/.DS_Store
If your permissions differ then we will look at correcting them.
J.C
Message was edited by: J.C -
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?
ThanksI 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. -
MSI E350IA-E45 USB Not recognised after cold boot.
Any one else have the same issue? My asus (Bluetooth) BT211 is not recognised after cold boot.
I also found the front USB's losing power when PC turned off. Connected them up to 5VSB to fix the issue.
MSI tech has not been back to me if this is a fault design, My motherboard issue or bios issue? Which also means to charge via front USB not work when turned off.
And to top it off I cannot find an answer to whether the Wake on Bluetooth USB is supposed to work?Quote from: mickas on 12-August-11, 20:09:58
I also found the front USB's losing power when PC turned off. Connected them up to 5VSB to fix the issue.
How did you connect up the USB ports to 5VSB?
I have a similar issue with a newer MSI board and my USB mouse; I'd have to remove and re-insert the USB connection to the mouse after each cold boot in order for it to be recognized. I did a kludge fix by looping the mouse through a powered USB hub that supplies power to connected devices even when the PC is off.
This MSI board doesn't have a hardware jumper to enable 5VSB to the USB ports, unlike other motherboards. Also, none of the "green" or wakeup settings in the BIOS would cause the USB ports to have power when the PC is off.
So, how do you connect 5VSB to the USB ports? I've heard that crossing the regular 5V rail with 5VSB is a no-no, so I can't imagine how you did it. -
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.
Maybe you are looking for
-
Double clicking on a div with contenteditable inside and iframe disables div
If i create a div that has contenteditable true on it works great on the ipad.. but put that same div inside of an iframe and if you double click it it becomes non functional. I have searched high and low for answers. I did see that there was a bug r
-
Can XBR9 series sony TV's be 3D capable with updates and glasses?
I purchased a KDL46XBR9 feb. 2010 and i've heard some talk about it being 3D capable. Is this true?
-
I am trying to watch the tutorials in Adobe TV, but have no sound. Sound working fine on all other programs, and volume on video turned up full. Any ideas?
-
Managing Office documents (content & permission) inside SharePoint 2013 document libraries
I have a document library inside my SharePoint 2013 publishing site collection. And I have the following scenario:- Someone add a word document to the document library, I can click on the word document inside the document library, and it will open in
-
Quicktime in vista using with Nvidia driver version 169.25 crashes
I've been searching the web for a long time to solve this problem, it appears that when quicktime 7.4.1 is used in vista when latest nvidia driver was install will cause the directdraw and direct 3D accelerationg to stop working, therefore the video