Z68A-GD65 (G3) fails to boot with new Gigabyte Radeon HD 7950 OC

Hi,
I have a problem with my new Gigabyte AMD Radeon HD 7950 (GV-R795WF3-3GD):
My system fails to boot with this GPU, with the old Radeon HD 4850 everything works fine.
Here are my system specs:
MSI Z68A-GD65 (G3)
CPU: Intel Core i5-2500K
RAM: 8Gb DDR3-RAM (Corsair)
power supply: be quiet! Pure Power L7 530W
What I have already tried to fix the problem:
-CMOS Reset
-other PCI-e slot
-other power supply (old 750W)
Nothing worked.
Do I need a Bios update? My current version is V23.7, but I'm not sure whether I can use the latest versions because my CPU is a SandyBridge...

We can't help you woth your vga as it is no MSI product. You can try latest bios for your board (http://www.msi.com/product/mb/Z68A-GD65--G3-.html#/?div=BIOS) because the latest bios versions for G3 boards are working well with Sandy and Ivy. If latest bios should not help and you like to downgrade the bios we can give you the needed files if you ask here.

Similar Messages

After replacing a failed hard drive with new one I inadvertently created a different account name(home/user) than the one in the Time Machine backup. Now I cannot restore the photos in iPhoto. What are my options?

After replacing a failed hard drive with new one I inadvertently created a different account name(home/user) than the one in the Time Machine backup. Now I cannot restore the photos in iPhoto. What are my options?

The best thing to do would be to start over. Use Setup Assistant this time.
Boot into Recovery, launch Disk Utility, and erase the startup volume. This operation will destroy all data on the volume. Quit Disk Utility and install OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.
When you reboot, you'll be prompted to go through the initial setup process. That’s when you transfer the data from one of your backups. For a walkthrough, see here:
Using Setup Assistant
Don't transfer the Guest account, if it was enabled on the old system.
Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with proxy servers, or with networks that require a certificate for authentication.

IBook G4 fails to boot with internal HD installed, works when removed

The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
The long version–
Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
+same error message a bit faster than one every 3 seconds+
Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
Thanks!

I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

MacBook Pro won't boot with new hard drive, but a different MacBook Pro will

So here are the details. My friend and I both have 13-inch Mid 2010 MacBook Pro's. Same processor and specs since they were purchased at the same time, but originally had 250 GB hard drives. His hard drive failed and needed a new one. Put a 500 GB Seagate Momentus 5400.6 in his computer, and tried using a flash drive with "Install OS X Mavericks" on it to install Mavericks on his new hard drive. No matter what, it wouldn't install. I finally was able to install OS X 10.9.4 on it by connecting the new hard drive to my computer with a USB hard drive enclosure. I put the hard drive back inside his computer and it wouldn't boot (stuck on the gray screen with apple logo and a spinning wheel). I then attached to the hard drive to his computer externally with the USB enclosure, and then it booted and worked perfectly.
So, it seemed like the problem was with something inside his computer, but then I switched our drives, and that doesn't seem to be the case anymore. I put my original hard drive into his computer, and his new hard drive into my computer, and they both booted and worked perfectly, so I have no idea why his computer will not boot with the new hard drive internally.
To summarize, his computer boots with: 1) new hard drive connected externally (won't work if it's internal), and 2) my hard drive internally
but my computer boots with: 1) new hard drive connected externally AND internally, and 2) my hard drive internally.
Both hard drives have OS X 10.9.4 installed
If anyone has any idea what's causing this and how to make his computer work with the new hard drive internally that would be greatly appreciated.

So after switching the internal SATA cables from each computer, now we have
His computer, with my SATA cable:
1) Worked with every hard drive!
My computer, with his SATA cable:
1) Works with 1 TB Toshiba hard drive
2) Works with 500 GB Seagate hard drive
3) Works with my original hard drive
4) Flashing folder with question mark with his old hard drive
So it turns out you were right! Definitely had something to do with the SATA cables. But it's still strange that mine was able to boot with all the hard drives except the one that was originally in his. So it seems like it was some combination of his SATA cable and something else, since when his SATA cable was in his computer only 1 hard drive (my original) worked, and when it was in my computer, 3 hard drives worked. But at least its working, and I'm just gonna keep our SATA cables switched since that seems to work out fine

OS9 bootable G4 mac fails to boot with NI-DAQ4.9

We're going to use the OS9 bootable G4 machine with NI-DAQ4.9 driver. However, after the installation of NI-DAQ4.9 the G4 machine failed to boot up(Pure OS9 boot. Not classical environment). The error message said that address error occurred when the NI-DAQ was loaded during the icon parade.
We installed the OS completely newly without any other softwares and installed the NI-DAQ4.9 driver. So it must be difficult to account for the problem by any conflict with other inappropriate softwares. Minimum set of system extension plus NI-DAQ also caused the same problem.
Now I doubt the problem caused by the conflict of new G4 with NI-DAQ4.9 because other hardwares work OK (Other G3 or older G4 machines).
If anybody ca
n post any idea or solution on this problem, we'll appreciate.
(*)We need to control PCI-DIO-96 board with our homemade C-program, so NI-DAQ 4.9 is required instead of NI-DAQ 6.
Machine: PowerMacintosh G4(Single1.25G4 Processor)-Latest OS9-bootable G4 machine
NI-DAQ:4.9.4

First, we will want to make sure that you have the latest NI-DAQ driver that still supports C program. That driver should be v4.9.4 and can be found from the link in the previous post (or here http://www.ni.com/support/daq/mac/macversn.htm).
After verifying this, I would try to restart the computer without your hardware installed to check if it is a hardware/NI-DAQ configuration issue or if you just had a bad install of the software. If it still does not work without the hardware than you can attempt to uninstall/reinstall NI-DAQ v4.9.4.
Finally, the problem may lie with in a conflict with the extensions on your MAC. If you are familiar with troubleshooing MACs, then you can disable all but the core extensions and see if you can get the computer up and running
that way. Below are a few KnowledgeBases that discuss some of these issues:
Computer Hangs While Trying to Install NI-DAQ or LabVIEW on Macintosh
My NI-DAQ Crashes Either at Boot (4.x) or When Loading (6.x) on the Blue and White Power Macintosh G...
Regards,
Michael
Applications Engineer
National Instruments

Can't get Pc to boot with new GPU

Hello. I have a hinkstation e20 422221G with Xeon CPU x3440 @ 2.53g running win 7 ultimate. I understand this CPU has no onboard video capabilties. I have had a quadro fx 380 card in there but wanted to upgrade, so purchased an asus r7 250x I also upgraded the PSU to 500w. When I turn the PC on, the fans come on etc but no boot. I have updated bios to version 5jkt65aus which is the latest available. I also have another issue in that windows states only 1.94gb ram is usable, when infact there is 4gb. I am running win 64x and there is no maximum memory setting. Have tried to look through BIOS to see if there was perhaps a setting where memory was being reserved for video etc, but can't find it. Any suggestions? Your help would be appreciated

First things first, we don't support aftermarket PSUs or desktop/gaming video cards in these systems so there's no guarantees either will work.
With that said, does your system boot whatsoever with the new PSU installed and the rest of the system as it shipped from the factory? ie: does it boot with the new PSU and the FX380 installed? If not then your PSU either isn't pinned correctly at the main connector or isn't supplying power to the correct locations.
If the PSU does work and it's only the Asus R7 250X then the simple answer here is that the card is unsupported. This is either due to the amount of power required or that the E20 doesn't have enough addressing space in the BIOS to handle a 2GB video card. In this case, hopefully your retailer allows returns as Lenovo cannot provide a workaround for such an issue on this old of a system.
I wish I had better news for you here but trying to turn a commercial workstation into a gaming system isn't without challenges.

Cannot boot with new SSD

Installed new OWC 240G SSD in 2007 iMac. Started up with old HD in external case running OS 10.10.2. Initialized SSD with Disk Utilities, and it mounted on the desktop. Transferred contents from old HD to new SSD. Computer boots fine from old HD in external case, but does not boot with internal SSD. After displaying Apple symbol for a few seconds of the startup process, computer goes to a kernel panic and gets into a loop of retry message-Apple symbol-message-etc. The SSD shows on the desktop, but does not show as a startup disk in System Preferences pane. Disk Utilities shows drive is fine, but repair of permissions is grayed out. Window says permissions repair is only permitted on OS installed with an Apple installer. System folder on the SSD does not show the "blessed" symbol. Have tried recloning using Time Machine backup - same result. Installed eDrive on SSD with TechToolsPro, and can start up in eDrive thru TTP window, thus verifying all cabling. After booting with original internal HD installed in external case, SSD will show on desktop, but will disappear in a few minutes after a message says it was improperly ejected. Suggestions? Is there a way to access OS 10 software purchased and downloaded from Apple site?

Many possibilities here. Maybe a bad connection when you installed the drive. Maybe a bad drive. Maybe a bad SATA cable.
How did you format the drive? Should be Mac OS Extended Journaled. When you boot into the recovery drive, access disk utility from there and see if you can access the drive.
I have the same drive as you. What I did is use Disk Utility from the recovery drive of TM. I first re-formatted the SSD drive. Then I used Disk Utility to restore the whole drive of my original to the new SSD drive.
You can still download the Yosemite installer from the App Store in your purchases providing you downloaded it from the App Store already.

Booting with new aluminium keyboard

Hi,
I got the new aluminium keyboard yesterday - seems to be fine but:
While booting there were no keys recognized at all. Neither CMD-V for verbous booting messages nor ALT for selecting either MacOS or BootCamp/Windoze...
Is there still a firmware update pending?
I'm using a Intel MacMini with MacOS 10.4.10, the latest keyboard update and all other published patches and updates...
Any hints?

Hi Doug, Hi Paul,
@Doug:
It seems to me that the new keyboard is simply not recognized by the bootloader/EFI/<whatever>. The girl from AppleCare asked me to check wether booting from the installation DVD works (i.e. booting with the "c"-key pressed) - it doesn't. Booting with CMD-s into single user mode doesn't work either.
So maybe you're right concerning the "standard feature", but if there's no keyboard connected there are no features - and "not connected" and "not recognized" seems to be the same here...
The only other Mac I have probably access to is my old G4-Mini which I've sold to a friend of mine. Besides that there's a different bootloader for PowerPC I don't expect an older Mac to recognize this brand new keyboard better. OTOH my old keyboard (a Macally iKeySlim) still works on my Intel-Mini so I see no reason for distrust here.
@Paul:
Nice to know that it's not soley my problem
If I understand you right you're saying that on your iMac the keyboard is working correctly - even during boot. Is that right? So you are able to get the boot messages on the iMac when booting with CMD-v pressed (with the new aluminum keyboard of course)?
It would be fine to narrow down the problem a bit to be able to make a meaningful bugreport for the guys @Apple...
Thank you both so far!
Matthew
Message was edited by: kestrel9532

Kernels 3.10.6 and 3.10.7 fail to boot with EFI stub

Been using rEFInd for some time now. Current installed version is 0.7.1. Kernels 3.10.5 and earlier would boot without incident. Yesterday I upgraded to 3.10.6 and boot failed. As a workaround, I copied the Liquorix kernel and initramfs from my Kubuntu partition; to my mild surprise, this worked. My next test was to install the 3.10.7 Zen kernel from heftig's repository. This kernel boots fine (I added a version number string to the name of the kernel image and the initramfs so that rEFInd would automatically match them). After that, I enabled Arch testing and updated the Arch kernel to 3.10.7; this also fails to boot just like the 3.10.6 kernel did.
I'm a fan of boot text, so I've configured rEFInd in text mode only. Here's my refind.conf, with almost no changes from defaults:
timeout 20
textonly 1
use_graphics_for
scan_all_linux_kernels
And my /boot/refind_linux.conf:
"Boot to X" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=graphical.target"
"Boot to single user" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=multi-user.target"
# "Boot to recovery" "ro root=/dev/sda3 nox2apic nomodeset systemd.unit=rescue.target"
Finally, details abot my laptop -- a ThinkPad T520:
steve@t520 ~ $ inxi -xxSMCGDp
System: Host: t520 Kernel: 3.10.7-1-zen x86_64 (64 bit, gcc: 4.8.1)
Desktop: KDE 4.11.00 (Qt 4.8.5) dm: kdm Distro: Arch Linux
Machine: System: LENOVO product: 423926U version: ThinkPad T520 Chassis: type: 10
Mobo: LENOVO model: 423926U Bios: LENOVO version: 8AET63WW (1.43 ) date: 05/08/2013
CPU: Dual core Intel Core i7-2620M CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10769.3
Clock Speeds: 1: 1188.00 MHz 2: 1809.00 MHz 3: 1809.00 MHz 4: 1080.00 MHz
Graphics: Card: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0 chip-ID: 10de:1057
X.Org: 1.14.2 driver: nvidia Resolution: [email protected]
GLX Renderer: NVS 4200M/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 325.15 Direct Rendering: Yes
Drives: HDD Total Size: 1256.3GB (8.2% used)
1: id: /dev/sda model: M4 size: 256.1GB serial: 000000001140031E608A temp: 0C
2: id: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB serial: JG40006PG61HKC temp: 43C
Partition: ID: / size: 108G used: 37G (37%) fs: ext4
ID: /boot/efi size: 511M used: 3.1M (1%) fs: vfat
ID: /mnt/kubuntu size: 118G used: 59G (53%) fs: ext4
ID: swap-1 size: 9.64GB used: 0.00GB (0%) fs: swap
Last edited by steveriley (2013-08-19 05:27:15)

Steve, your picture is far too large for these forums. You are going to want to put it in some kind of a picture sharing/hosting site and link back to it. Otherwise it will end up disappeared (likely via black magic) from your post. I don't think that it provides any useful information anyway. If you want to post your kernel command line that is great. But posting a picture of a frozen screen with no output... doesn't really do much good.
Efistub has been a bit shaky since 3.6 actually. There is a monster thread about this already, the title of which references 3.6, but the content continues on through several kernel releases. Still people continually report this as being an issue. What I do is I keep a normal efi bootloader (one that doesn't rely on efistub) at the ready all the time. My choice was elilo, but since [testing] started including syslinux-efi in the syslinxu package, I have started using that... though I still have elilo set up.
Can you boot with efistub from the UEFI Shell or gummiboot? I prefer gummiboot, but I have had this problem in the past, and when I did, I was able to boot with rEFInd... which was strange. Some people even report that simply having a direct efibootmgr entry in their firmware causes it to magically work. Though there should be to reasonable explanation for this, it was confirmed by several people in the mentioned thread.

Satellite C655-S5041 won't boot with new RAM (8GB)

I recently bought some Ram from Newegg which can be found here. I installed the aforementioned Ram into my laptop following the correct method (unplug, remove battery, etc.) however when I booted my computer up I received a black screen with a blinking cursor that freezes after a few seconds shortly after the manufacturer's page is loaded.
I know for a fact that the Ram I bought is compatible with my laptop as I'm using one of the 2 sticks at the moment along with the original Ram from my laptop. Here's where I am really having issues though.
When I have just one stick of Ram I purchased installed without the original stick my computer fails to boot up also regardless of which slot the Rams in. I have tested the sticks I bought, and my computer will boot up with them, just not without the original stick that came with my computer which wouldn't be an issue except that a) there's only 2 slots, and b) my laptop can't have more than 8GB of Ram.
My BIOS is up to date (Ver1.6) and so long as I have my original stick of Ram installed my computer boots without any issues. Needless to say you can see why I'm in need of some help.
Any help would be greatly appreciated. If you need any other specifics regarding my computer or settings feel free to ask and I'll do what I can to find them out.

Satellite C655-S5047 Specifications
Satellite C655D-S5041 Specifications
Is your model is a Satellite C655-S5047, or a Satellite C655D-S5041, as there is no C655-S5041. Toshiba laptops are extremely finicky about the RAM they will accept, regardless of the advertisied compatability of other modules. It is imperative to to be percise about your model number as:
The only approved replacement RAM modules for a Satellite C655-S5047 are shown on the spec sheet:
Memory Upgrade
Part Number Description
PA3669U-1M2G Toshiba 2GB DDR2-800 Memory Module
PA3670U-1M4G Toshiba 4GB DDR2-800 Memory Module
Or the best quality compatible Kingston Memory modules. However, if this is your system, unless you are very lucky, I doubt you will find the 4GB modules available from Toshiba, Kingston, or a third party supplier. I use the same memory in my system.
The only approved replacement RAM modules for a Satellite C655D-S5041 are shown on the spec sheet:
Memory Upgrade
Part Number Description
PA3676U-1M2G Toshiba 2GB DDR3-1066 Memory Module
PA3677U-1M4G Toshiba 4GB DDR3-1066 Memory Module
Or the best quality compatible Kingston Memory modules. These modules:
Part Number: PA3677U-1M4G
Part Number: KTT1066D3/4G
You purchased DDR3-1066 modules, which might work in the Satellite C655D-S5041. However, I sincerely doubt they will work in the Satellite C655-S5047.
Mike

K8N Neo fails to boot with more than one DIMM

I have been searching the forums for a while now, and will continue, but I am really hoping for a quick resolution. My system was running fine for over a year with a pair of PC3200 512MB DIMMs. I normally leave my computer on all the time. Recently I updated my BIOS to 2.10, and the system performed a soft boot afterwards. Christmas Eve day I knew I was going to be gone the whole day and probably not need my computer until late on Christmas day. I received a very unpleasant surprise.
I attempted to boot the computer up, and I got nothing but a repeating single long beep. I did a lot of troubleshooting and discovered that the system will boot and run fine with ONE DIMM, either DIMM. My system will no longer boot with a second DIMM in either the 2 or 3 DIMM slots. This is a major bummer for me, please help.
I have not played around much with memory timings and such as of yet. It is quite a pain to put in a single DIMM, and boot the system to make a BIOS change then shut it down again and install the second DIMM to see if it works.
Thanks in advance for any help.
Scott

Go back to your previous BIOS.

ATI display driver fails to work with new kernel

Hi,
I've just upgraded from
OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64
to most current
OEL kernel-2.6.18-194.11.4.0.1.el5.x86_64
and got the problem with ATI display driver. Whenever I perform kernel upgrade, I have to recompile vendor-provided ATI display driver downloadable from AMD/ATI site, because system ATI driver, provided by OEL/RHEL as kernel module, doesn't work properly (too slow). I did that hundred times and never had a problem. This time the problem is that after upgrading to new kernel and recompiling the existing ATI display driver (Revision 10.8), it doesn't work anymore, even though it worked perfectly with previous kernel. I cannot even start X11 (glibc problem reported with stack traces!!!). The newest ATI display driver (Revision 10.9) "works" with new kernel, but display is awfully slow making any serious work impossible. It is even slower than system-provided ATI driver.
I am pretty sure the problem is in new kernel. As I have no backup of old kernel files and couldn't download the previous OEL kernel files from ULN, neither binary nor source (the files do not exist on ULN anymore, only the recent kernel files), I downloaded the previous kernel source from ftp.redhat.com, compiled the kernel and downgraded to it, recompiled ATI display driver, and everything works properly and fast as before upgrading. I can remember that ULN site used to have all kernel versions prior to actual one and cannot understand why Oracle dropped this practice. As I have an ULN account, I certainly want to have OEL patched kernel.
My question is: does anybody know how and where I can download the previous OEL kernel-2.6.18-194.11.3.0.1.el5.x86_64 binary rpm files or at least source rpm file?
Maybe Sergio or Tommy can help?
Thanks in advance.
NJ

I have experienced the same with Ubuntu some years ago - specific feature (hack?) that was implemented in the kernel was deprecated. This was used by the display driver for an onboard Intel graphics chipset. Beryl (which was subsequently merged with Compiz) turned into a horribly slow experience. As far as I recall, a subsequent kernel patch "fixed" things as a number of users were affected, of which many complained very loudly.
Anyway, I think the lesson here is that OEL is not really the correct distro to use for a desktop. A broken ATI driver for the OEL kernel? Does not really feature in the scheme of things for OEL support. Oracle Grid/RAC/Enterprise/Standard Edition do not care. Oracle's application servers (Apache, Weblogic, etc) do not care. Etc.
Sure, GUI desktop access to an OEL server is needed (like when running dbca or an installer) - but that can easily and effectively be done using vncserver for example and running twm.
You may be able to fix/work-around the problem with the current kernel update.. you may be able to roll back the update. But what about the next time when some other component does not work after a patch or an update? Surely it is a lot less stressful and frustrating to rather use a desktop distro, like Ubuntu, instead?

Won't boot with new graphics card

Hi. I have a Pavilion P7-1058uk with a Cleveland-GL8 motherboard and onboard graphics.
I bought a new monitor which has 2560x1440 resolution, greather than the onboard graphics can cope with, so have tried to upgrade with a Gigabyte GT630 card.
When I startup, I now get to the blue HP screen but no further. If I startup with F10 or ESC pressed, I get to a black screen instead. Either way, I am invited to press Esc to enter startup but pressing the key has no impact and the computer just hangs. There is a repeated cycle of very quiet clicks which sounds like the HDD drive trying to start then stopping
If I remove the graphics card and connect the monitor back to the onboard graphics then all is well again (but restricted to 1920x1080 resolution).
Perhaps stupidly I assumed it was an issue with the power supply (300W) and not enough residual oomph to run the HDD. But having upgraded that to 650W it makes no difference. I also tried downloading NVidia drivers but it won't let me install them because I can only get the computer to work without the graphics card, and Nvidia won't install because it can't detect the hardware.
Any ideas/help would be much appreciated.
Andrew
This question was solved.
View Solution.

ADR1978 wrote:
OK thanks. This card doesnt require a six pin connector but it is interesting that your comment implies that those that do still take power from the motherboard but topped up with the six pin connector. As opposed to taking all power from the six pin connector and nothing from the motherboard. I am not making a statement that equates to your analogy. All cards plugged into a motherboard I/O internal slot are powered by the motherboards power distribution subsystem.
One last question - should I have uninstalled the graphics driver for the integrated graphics or is that unnecessary? I have read that the motherboard turns the integrated graphics off when it detects a dedicated card. I have not done so and am a little wary of uninstalling the existing driver in case things still dont work and it gets tricky to revert back to where I am now.
Andrew
No. You won't need to uninstall the driver for the integrated graphics. The OS will only load the driver for the graphics card when one is installed.
Regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Windows 8.1 fails to boot with error code 0x5c after moving physical drives

Hi,
i just rearranged hard drives on my desktop PC. I removed 4 RAID drives, installed a single drive and reattached all drives into different SATA connectors on the motherboard.
After this, my PC doesn't boot. IT always fails with errorcode 0x5c. My OS is on SSD drive, which was not part of the RAID drive so it should boot up just fine - except it doesn't.
I've tried safe mode, I've tried starting with driver signature enforcement disabled - but it never does boot up properly.
What else do i do apart from reinstalling the OS?

Hi,
This error 0x5c indicates that the HAL initialization failed. A hardware abstraction layer (HAL) is an abstraction layer, implemented in software, between the physical hardware of a computer and the software that runs on that computer.
It seems that the issue can be cause by interface compatible. Please enter BIOS and change SATA to AHCI to see what’s going on.
Also, I suggest you arrange your 4 RAID drives back to original SATA connector and connect the new single drive to another to check the results.
Hope this could be helpful.
Kate Li
TechNet Community Support

P67A-GD65 (B3) will not boot with external USB DVD connected.

Damnedest thing... just put the build together last night and this was the biggest issue. If I connect my external Samsung USB DVD RW the system stops booting and only displays (B3) in the bottom right corner of my display. If I remove the USB plug the system boots and operates normally. If I connect it to the USB port after boot the system recognizes it and it works fine. The same issue occurs no matter which USB2/3 port I plug it into. I've banged around the BIOS and cannot see any issues in the boot sequence that would indicate an issue. Anyone else in das same boot?

Quote from: cadhopper on 24-March-11, 07:19:08
I just came to the forum for the same reason. I'm glad you had a thread already going. Mine is a Seagate 1.5T USB 2.0 hard drive and the screen reads 98 in the lower right corner. Hopefully MSI will get this fixed soon. Other than that the new system is running great.
They are working on it. They sent me a BETA BIOS to try out. The BIOS v1.10B3 was dated 3-17-2011 and it nearly bricked my system though. Here is the response I sent to them the other night after a few hours with a massive headache trying to bring my system back up:
Quote
Tried the new BIOS. While it did indeed fix the USB DVD boot issue and let me boot into windows it created a few new issues. After flashing the new BIOS would not recognize my old overclocking profiles from the v1.8 BIOS.. "hole" error. So I manually adjusted all the settings and saved the new settings. I copied them EXACTLY from my previous settings.. I had screenshots which I had printed out as a fool-proof guide. After rebooting I could no longer get into windows. BSOD. If I tried entering the BIOS by tapping the DEL button while booting the system would freeze at the "entering setup...." screen and never progress into the actual BIOS. I unplugged the power, waited a few minutes and held the clear CMOS button on the back panel down for a few seconds. After rebooting I no longer had video output. After much trial and error I ended up having to also unplug my LCD and cycle power on it as well to get video back. But could still bot get into the BIOS by tapping the DEL key during boot. Luckily I have a laptop with all the files on it and I was able to finally re-flash back to the v1.8 BIOS from a USB drive. I'm not sure what exactly you changed.. but I don't think this new BIOS version should leave BETA status.
To their credit they promptly responded the next AM:
Quote
There were some changes to the CPU voltage, so your overclock settings may not work properly. We are still working on a 1.A release version. It will be updated to our website soon. http://www.msi.com/product/mb/P67A-GD65--B3-.html#/?div=BIOS
I only wish they had informed me of the changes to the CPU voltage up front or included a change log so I could have made an informed decision as to whether or not I wanted to try the BETA BIOS. I was under the impression (mistakenly) that it simply addressed the USB DVD issue. I'll wait for the new release BIOS. I can live without the external USB DVD being plugged in at boot. Bricking my MOBO and having to RMA would be a far less desirable outcome. :p That said.. I'd still recommend this MOBO. It has relatively few issues and MSI support is responsive so far.

Z68A-GD65 (G3) fails to boot with new Gigabyte Radeon HD 7950 OC

Similar Messages

Maybe you are looking for