Boot failure with AMD core unlock solved

Before you criticize me for buying a triple core instead of a quad core, I want you to know that my situation seems to only conflict with Arch.
I have an AMD Athlon II x3. If I unlock the 4th core, Linux live CDs boot up just fine, Windows XP boots fine, Windows 7 boots fine, and as long as any OS completely boots up it runs flawlessly for hours with constant load. However, Arch will fail to boot IMMEDIATELY after unlocking cores. IIRC, the Arch setup CD also fails to boot. I have a small feeling that GRUB has something to do with it, but whenever I attempt to install GRUB2 I'm never able to boot again.
As another note, I can't seem to get IOMMU to work with Arch. With Debian based distros it works immediately, but I can't find anything on how to enable it with Arch. I get this impression that there's a lot of missing Kernel entries in Arch which are causing these CPU problems, and possibly others.
Last edited by schmidtbag (2011-09-27 16:16:30)

schmidtbag wrote:
R00KIE wrote:Not much of an idea then, get /proc/config.gz from the distros that work and the one from arch, compare them and see if you can spot what might be causing the problem. No other ideas here.
debian doesn't have that file, did you mistake it for something different?
I know some distros don't have it but I wasn't aware debian is one of them (I use arch everyday and I try to manage a few centos boxes and that's all), that is an option can be enabled/disabled when building the kernel and it can be quite useful when trying to figure out why something doesn't work (such as seeing which drivers were built and which option was selected when there are multiple choices), however I guess it might have security implications since anyone can find out which options were selected when building the running kernel and some combinations may have yet uncovered/unpublished/undisclosed security exploits.

Similar Messages

Msi Z87-GD65 Booting Failure With eSATA Drives

Hi Folks,
Before I go down the (probably ill-fated) Customer Service path I thought I'd address the forum here on a little problem I'm having with my Z87-GD65.
IN essence, if I have a hard drive connected to my eSATA port the PC won't boot. I'm using an ICYDOCK 4 bay external enclosure (MB561US-4SB if interested). If the drive itself is on but the HD trays are ejected then it boots. If any of the drives are secured then it'll hang at a post-BIOS/pre-Windows screen where all I get is a blinking cursor for about 30 seconds and then it disappears to a plain black screen. If the device is powered off then it boots.
I've checked the BIOS with one of the HDs running and it doesn't appear within my boot list - in fact, except for one selection in the bios allowing me to disable eSATA there really isn't much I can do there.
I've upgraded my BIOS to 1.30 from 1.00 and the process seems to move a bit further - now I get the oh-so-pretty ugly Windows logo and that's all.
When I do actually boot the PC with the ICYDOCK off then I'm able to get into Windows normally, and turn on the ICYDOCK. After a few seconds all 4 hard drives report in and everything's fine.
I've been using this ICYDOCK for about a year and a half, with 2 other motherboards (neither were an MSI) and i7 cores, and neither of them caused me any issues. I remember that neither of those boards had the port multiplier eSATA capability so I had to buy a controller card with that capability. I could probably dig that up and see if the problem remains.
In case you're wondering, if it helps, I built a Msi Z87-GD65/4770 i7 - based PC with 2 internal 2TB Hard Drives, and 16gb RAM. I already mentioned the ICYDOCK. I used LiveUpdate to install all the latest drivers & BIOS before uninstalling it.
I build & repair PCs for a living so I'm pretty familiar with what's going on with the system. I figure that there must be something happening between the BIOS and Windows "handoff" of the ICYDOCK, but I'm damned if I can figure out just what.

More information please. PSU, OS being used, etc..
Live Update is best uninstalled. Flash UEFI/BIOS the safer way;
https://forum-en.msi.com/index.php?topic=169827.0
Recommend to download drivers and utilities from the MSI Websites and install manually.
>> Posting Guide <<

Boot Failure with HP HDD

I have an old Vectra VL420 mini tower which I've used to install 3 different operating systems on 5 different IDE Ultra ATA hard drives from different manufacturers. The drives range in size from 40G to 200G.
I have a second, socket 370, system which I built myself using an ASUS TUV4X motherboard. I have used this system to install two different operating systems, each on its own drive.
Both systems run without issue, but here's the rub:
1) I can boot my Vectra with the drives from my home-built system, but...
2) I cannot boot the home-built system with any one of the Windows (Win 2k Pro and XP home) drives from the Vectra, nor can I slave any one of the Vectra's Windows drives to it.
3) I have one drive with an old Red Hat OS that will boot either system.
4) The home-built will not boot if I swap its optical drive with one from the Vectra.
When I try to boot the home-built with the Vectra loaded Windows drives the sequence of events is always the same:
1) Power on...
2) Fans come on and drives start to spin up. This last for about 2 or 3 seconds before...
3) The system shuts itself off (power off). It doesn't even stay up long enough for a BIOS screen to appear.
This also happens when I swap the optical drive with the Vectra's.
I get the impression that the motherboard takes one quick look at the hardware, doesn't like what it sees, and shuts down.
I've spent a lot of time with the TUV4X owner's manual trying to see if there was some parameter in the BIOS or some switch/jumper on the motherboard that would solve this issue. I'm reasonably certain this is a dead end.
I'm beginning to think that there's something peculiar about the way HP formats drives. Perhaps it even modifies the firmware on them.
Any ideas?
Thanks in advance,
Pat

Hi dragnoak,
I'm talking about the USB cable that came with my Navigon 72 Plus. I bought this GPS navigator 2 years ago, which means that I used the cable 8 times (I update the maps 4 times/year), always on my X220t.
I plugged it into the A520's USB 3 port for the first time last week. You know what happened.
I said that the cable has been "destroyed" because I don't know the right English word, but you should understand what that means: the cable stopped working during the first half hour. After that I tried to connect my GPS to the X220t, but to no avail.
Same thing happened to my "pass-through" e-cigarette (it is equipped with a micro-USB port at the bottom). After a few hours the red LED next to the port turned off and the battery stopped charging. I had to order a new cable.
Neither the GPS nor the e-cigarette were damaged, only the cables. Strange things happen sometimes...
I have no doubt that your USB 3 ports work like a charm. Mine don't, since day 1. My external USB 3 compatible HDD is plugged into a USB 2 port, otherwise I can't save anything onto it (just read). In short, I have two useless USB 3 ports. I am not complaining, just talking about a fact.
@TLC2013,
I apologize for using your topic to report my own issues...
X220t | i7 | 320GB HDD | 8GB RAM | WIN7 PRO
IdeaCenter A520 | i5 | 1 TB HDD | 6GB RAM | WIN8.1

New P7N SLI Platinum Boot Issue with PS/2 Keyboard [Solved but RAID problem now]

This issue taken me back !!!! Never thought I might face issue with a PS/2 Keyboard.
Here it is.. I just assembled my new system...
P7N SLI Platinum Motherboard
E8400 CPU
EVGA 256-P2-N751-TR GeForce 8600 GT Video Card
Creative Soundblaster Audio Card
So, before I boot, I connected good old PS/2 Keyboard. The POST Screen comes up that says Press DEL to enter BIOS Setup... but then, it reboots.. indefinitely... I have no idea why it does that. However, if I boot the PC with no PS/2 Keyboard connected, POST screen comes up and that's it.. (no reboot). So, you see, I cannot proceed further in anyway.... I cannot go beyond POST without a keyboard, but then with the keyboard it reboots indefinitely... kinda catch 22 situation
Any suggestion / ideas that anyone can offer here???

Hello Folks... it took long time to "solve the issue that had to begin with"....
I purchased a cheapo Celeron processor to get into the BIOS and update it... but it didn't even work... I couldn't boot at all. So, I called MSI and they asked me to RMA it. They replaced my MOBO with the latest BIOS - which was good news
So, now, I'm able to boot - good news...
Now, this is an upgrade for me.... from my previous MOBO. My boot drive was RAIDed (RAID 0). So, now, I will have to RAID my drives again and run Win XP repair. I was able to RAID my drives and all good... now, I went into Windows installation and did F6 to install NVIDIA Raid.... but, here is my problem, when the prompt asks me to input the floppy drive, and when I did it.... it re-prompts me to put the floppy drive again... I see that the floppy drive is read... but, for some reason it doesn't detect the files in there properly.... I downloaded nVidia C72+MCP55 SATA RAID / AHCI Driver (For floppy driver) for windows xp 32-bit and copied the sataraid folder contents into the floppy. Now, here I am stuck again....
Anybody experienced this problem?

No longer able to boot - failure with /boot

I recently, due to a hard drive change, rebuilt my desktop. Every now and again, since then, it hasn't booted. I just logged into root and rebooted; figuring I'd sort it out at some point.
Only, now it won't boot at all. When I go through journalctl -xb I get the following errors (the ellipsis, in case it isn't clear, indicate an number of lines with no error in between the error messages):
Job dev-sda2.device/start timed out.
Timed out waiting for device dev-sda2.device.
Dependency failed for /boot.
Dependency failed for Local File Systems.
Triggering OnFailure= dependencies of local-fs.target.
Dependency failed for File System Check on /dev/sda2
and also, much later in the logs:
Failed at step EXEC spawning /bin/plymouth: No such file or directory
My initial assumption would have been that the relevant drive is failing, but I only recently ran a check on the drives (a few days ago and since the rebuild) and all was fine and dandy - but I had already been seeing these errors on a periodic basis. Only now, as I said, they happen at every boot and I never get as far as login.
Thanks in advance for any help.

I ran the extended smartmontools test on the disk today and it returned with no errors. However, the error log for the disk did contain the following:
Complete error log:
SMART Error Log Version: 1
Warning: ATA error count 21 inconsistent with error log pointer 5
ATA Error Count: 21 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 21 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:12:12.224 READ DMA
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:12:12.224 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 0a 01:12:12.224 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 20 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:11:26.048 READ DMA
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:11:26.048 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:11:26.048 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 19 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:10:16.816 READ DMA
27 00 00 00 00 00 e0 08 01:08:51.584 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:08:51.584 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:08:51.584 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:08:51.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 18 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.384 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.384 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.384 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.352 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.352 READ DMA EXT
Error 17 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.288 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.288 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.288 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.272 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.272 READ DMA EXT
Does this mean my disk is dying? That would be very annoying after just rebuilding from another failed disk!

W530 Boot Failure with out any BSOD

I bought my thinkpad w530 in Oct. 2012. It works perfect until recent month.
At the beginning, it can't wake up in the sleep mode. If I connect the AC power, it reset the BIOS time.
And nowadays, when i power off this laptop, it can't boot. And I remove and setup the battery, It restored. But if I first connect the ac power/dock, and remove-setup the battery, the BIOS time is reseted.
I updated all my drivers. The failure is still here. I wonder if oneday it died forever?
Thinkpad W530 2lu, 32G DDR 3 Kinston, 500G HDD. K2000m

Can you try resetting your BIOS settings to defaults?
It's also possible that your CMOS battery is depleted, in which case you would have to replace it.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Windows XP system boot failure with \Boot\BCD status 0xc000000f

I have a ThinkCenter M52 purchased secondhand from my employer. It was originally loaded with Vista but was upgraded to Windows XP before I got it. (The recovery partition on the HDD is still Vista.) For the 15 months since I bought I have had no problems. I had to reboot earlier this week because of a software upgrade and now I get:
File: \Boot\BCD
Status 0xc000000f
An error occurred while attempting to read the boot configuration data
From Google searches this is a Vista error, somehow the XP configuration has been lost. I have tried using a partition manager, BOOTCFG from an XP install disc, BartPE. I have run out of ideas, how do I fix this?

Did you check your HDD for errors?Try using Lenovo's hard drive quick test
http://www-307.ibm.com/pc/support/site.wss/MIGr-70578.html#boot
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Registry/boot problem with K8T Neo mobo (solved)

I got similar problem: https://forum-en.msi.com/index.php?threadid=40752&sid=
Though my error message is: "Windows could not start because the following file is missing or corrupt:\WINNT\SYSTEM32\CONFIG\SYSTEM"
I did NOT have this problem before i enabled the Realtek gigabit ethernet controller in BIOS.. But now when it is enabled everything runs/installs/reboots fine... until i shut down and when i turn power on next day i get that error message.
So: when Realtek 8169/8110 gigabit ethernet NIC is enabled in BIOS, necessary drivers installed and system shut down, registry get corrupted while shutting down.
I had AMI BIOS 1.1 when got this first time (after enabling realtek), flashing to 1.2 didn't help.
I also tried newest realtek 8169/8110 drivers (5.611.1231.2003) instead of original (5.606.811.2003)(they're still in msi neo-fis2r page i see) but it didn't help either.
So, any suggestions? i believe the integrated realtek causes the problem because it didn't occur before i enabled it from bios->integrated stuff... or is there any other possible reason?
oh, msinfo32 says that radeon 9800XT, IEEE1394 controller (firewire in audigy2) and realtek controller share the same IRQ 16.. i removed firewire controller but it didn't help.. could radeon and realtek sharing the same IRQ be the problem?

Didn't try the external yet, i'll still try something with this.
:: Do you have a home network setup, or connect straight to modem?
straight to modem.
i doubt it is the audigy, it worked before... and i've disabled everything i don't need like onboard audio, onboard 1394.. (never installed 'em)
i noticed one thing: all people with similar problems are running win2000 SP4, you run XP so it's ok.
MS knowledge base says "If one or two registry hives consistently become corrupted for no reason, the problem probably occurs at shutdown and is not discovered until you try to load the registry hive at the next restart. In this scenario, the registry hive is written to disk when you shut down the computer, and this process may stop the computer or a component in the computer before the writing is completed." http://support.microsoft.com/default.aspx?scid=kb;en-us;822705
so something (realtek?) is writing to the registry while i shut down the pc.
i'm gonna disable realtek before shutdown & see if it boots without errors... if it does, i'll just have to disable it *always* before shutdown.... sounds like driver error for me?

Frequent lockups and boot problems with 8-core Nehalem

I just received my new Nehalem Mac Pro and have had tons of crashes already and right now I am staring at a black screen waiting for it to boot. I think it's a problem with the Radeon 4870 drivers since the last crash was while I was using Mudbox RC (I'm an Autodesk beta tester). I originally thought it was the RAM I bought from Crucial but it's a problem with the Apple supplied memory too.

Check the instructions for reset SMC.
Hardware part of testing? with Mac Pro 2009 I'd guess a lot of things could break (and 10.6 will force using 64-bit drivers).
Strip out everything but stock items. AHT should be on the boot drive as well and holding down 'd' will bring it up - if you can get that far along.

T530 with N-6300 boot failure 1802

Hi,
I got a nice T530 with built in 6205 Wireless LAN. As I tried to replace with N-6300 there comes the Hardware boot failure with error 1802 (incompatible PCI device). I just wonder as the N-6300 is in the compatibility list and the third antenna was also already built in. Is there any workaround to get this running?
regards
Solved!
Go to Solution.

I picked up the N6300 with FRU 60Y3233 from http://www.ebay.ca/itm/1pc-Ultimate-N-6300-633ANHMW-FRU-60Y3233-Wireless-Card-for-IBM-Thinkpad-Intel...
The card works flawlessly out of the box and utilizes all 3 antennae.
Just in case someone was looking for an answer here.

System boot failure after upgrade from linux3.13.8-1 to linux3.14.6-1

I have tried to update the kernel again from 3.13 to 3.14 again, but no luck.
My arch system boot failure with black screen, tried [ctrl]+[alt]+[F1-6] and nothing happen, no any recure shell prompt out.
Then I boot with kernel debug parameters
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
althrough the screen was black, when I reboot and chroot into my system,
I entered the following to find any error messages, please see the link below:
journalctl -b -0 >> ~/3.13_no_problem.log
journalctl -b -1 >> ~/3.14-6_nodebug.log
journalctl -b -2 >> ~/3.14-6_debug.log
3.13_no_problem.log: http://pastebin.com/EQ2Mucq8
3.14-6_nodebug.log: http://pastebin.com/18TRZVRp
3.14-6_debug.log: http://pastebin.com/0QZJBPnf
In both 3.14 journal messages, I found some similar error message:
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:00 arch-desktop kernel: [drm:cypress_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
I searched on internet, I think this is caused by my graphic card(ATI 5750), but I have no idea to solve it
I don't know my system boot failure due to these error or another things.
my PC specs:
motherbroad - gigabyte GA-P55A-UD3 (bios ver - F11)
cpu - i5-750
display - ati 5750
os - arch 64bit
Currently, I have downgraded back to 3.13.
I hope someone can give me some idea,
Thanks
Last edited by samtai (2014-06-17 12:17:02)

As there are errors associated with ntpd, I would temporarily disable the ntpd service and also ipv6.
If they are not the only problem, at least your logs would be easier to examine for other problems.

Disk Boot Failure [solved]

I'm installing arch on a rebuilt system, but I cannot get it to boot. I have pared the system down to a a SCSI card, a video card, a single hard drive, an IDE CD, a SCSI tape drive, and a floppy. I have tried my standard installation partitioning scheme, and the automatic version.
No matter what I do, while the system seems to install correctly, when I reboot I get a Disk Boot Failure.
I've zeroed the drive, I've tried an fdisk /mbr, I've run a Maxtor burn-in test which came back fine. I'm convinced it isn't the drive. The standard menu.lst uses root (0,0) and the kernel in /dev/discs/disc0/part3 after an automatic installation. I mounted the /boot partition set up by the auto install, and the grub directory and files are there.
What am I missing?
Last edited by timm (2009-05-04 22:11:42)

I think it's solved.
Everybody who was mentioning the BIOS got me looking in there, but I found nothing out of the ordinary. I decided to try to install Windows 2K to see if that would boot, which it did flawlessly. I reinstalled arch, and go the disk failure. Back to the BIOS.
This is an IDE hard drive; the only thing SCSI is the tape drive.
What I found was that the access on the hard drive was set to Auto, which I had seen before but didn't think to be a problem. I tried changing that to LBA (which is what I thought Auto would do on a drive like this), and suddenly arch comes up just fine.
I have a couple of RocketRaid cards that I'm installing, and will be playing around with the SCSI as well. I'm going to play with things a bit more, but unless I can make it fail with some other tweaking, that BIOS setting appears to have been the problem.
Thanks to everyone for their help!

1 core only on MSI NEO PLANTIUM 7125 WITH Dual core 4400 +AMD

Need your help. Im using xp 64bit on MSI NEO PLANTIUM 7125 WITH Dual core 4400 +AMD and cant seem to get the 2nd core activiated even after flashing the bios to Award BOS release 1.5.I also installed the latest driver for the cpu. Im using only the default settings in the bios. Can anyone tell me the correct settings in the bios to make the 2nd core run and also how can i tell its running im currently using everest benchmark tool for that but unsure its the right tool. Also i have 4 512 kingston ram sticks.
Thanks
Jack

Quote from: jbnetdev on 24-July-05, 18:47:16
Need your help. Im using xp 64bit on MSI NEO PLANTIUM 7125 WITH Dual core 4400 +AMD and cant seem to get the 2nd core activiated even after flashing the bios to Award BOS release 1.5.I also installed the latest driver for the cpu. Im using only the default settings in the bios. Can anyone tell me the correct settings in the bios to make the 2nd core run and also how can i tell its running im currently using everest benchmark tool for that but unsure its the right tool. Also i have 4 512 kingston ram sticks.
Thanks
Jack
SOLVED IT !!. You have to flash the bios to the most current version. Then i used ntune software to optimize the system and last iwnet into the bios and selected optimize settings F7 rebooted and fixed !!!

I am running Photoshop CC 2014 on Windows 8.1 with an AMD quad core processor and AMD E1-2100 APU with AMD Radeon HD 8210 Graphics Card. I have installed the latest driver version 13.152.0.0. When I activate puppet warp, the mesh appears over the image an

I am running Photoshop CC 2014 on Windows 8.1 with an AMD quad core processor and AMD E1-2100 APU with AMD Radeon HD 8210 Graphics Card. I have installed the latest driver version 13.152.0.0. When I activate puppet warp, the mesh appears over the image and I can place the first pin. However, when I go to add the second pin, Photoshop crashes. I have tried with on a new, blank file, with just a few lines on it, but, as soon as I place the first pin, the image disappears, and then, as soon as I click anywhere else in the image, Photoshop crashes. I have followed all the online advice about settings under the Preferences/Performance interface, but nothing fixes the problem. Can anyone please help?

BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand, such as your platform (Mac or Win), exact versions of your OS, of Photoshop and of Bridge, machine specs, such as total installed RAM, scratch file HDs, video card specs, what troubleshooting steps you have taken so far, what error message(s) you receive, if having issues opening raw files also the exact camera make and model that generated them, etc., someone may be able to help you.
A screen shot could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

[SOLVED]Dual boot problem with an Asus UX31A (EFI)

I never did an EFI install before and I still don't understand how it works however following the Zenbook wiki, I have successfully installed Arch. Now I can't boot Windows 7 anymore. I am using grub2, have installed os-prober. Grub menu has windows 7 entry but when used prompts a wrong EFI file path error.
My partition table is:
[root@zenbook sonay]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 200M 0 disk
├─sda2 8:2 0 128M 0 disk
├─sda3 8:3 0 98.6G 0 disk
├─sda4 8:4 0 4G 0 disk
├─sda5 8:5 0 90.7G 0 disk
├─sda6 8:6 0 512M 0 disk /boot/efi
├─sda7 8:7 0 3.9G 0 disk
├─sda8 8:8 0 10G 0 disk
├─sda9 8:9 0 200M 0 disk /boot
└─sda10 8:10 0 30.3G 0 disk /
sdc 8:32 0 931.5G 0 disk
└─sdc1 8:33 0 931.5G 0 disk /run/media/sonay/My Passport
/dev/sda1 used to be Windows 7 EFI partition. Gparted says it is flagged as boot.
What I did to install arch:
Partitioned /dev/sda5 with windows disk manager to create linux partitions and formatted the new partitions with gparted as the noob I am.
created /dev/sda6 for EFI boot
created /dev/sda9 for boot partition
created /dev/sda10 as root.
Did not touch
/dev/sda1 which was the EFI partition named SYSTEM
/dev/sda2 which was windows boot partition
/dev/sda3 which was windows C:,
/dev/sda4 and /dev/sda7 which I don't know what they used to be (possible for Asus fast wake up or swap whatever)
/dev/sda8 which is recovery partition.
I did not touch any grub files, except /etc/default/grub
[sonay@zenbook ~]$ cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
Finally my /boot/grub/grub.cfg is:
[sonay@zenbook ~]$ cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
[sonay@zenbook ~]$ cat /boot/grub/grub.cfg
cat: /boot/grub/grub.cfg: Permission denied
[sonay@zenbook ~]$ su
Password:
[root@zenbook sonay]# cat /boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt10'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt10 --hint-efi=hd0,gpt10 --hint-baremetal=ahci0,gpt10 cf66f05a-418c-4517-a0e0-af01b3be4a67
else
search --no-floppy --fs-uuid --set=root cf66f05a-418c-4517-a0e0-af01b3be4a67
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=1
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
else
search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
else
search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 5246C0D846C0BE4B
else
search --no-floppy --fs-uuid --set=root 5246C0D846C0BE4B
fi
chainloader +1
menuentry 'Windows Recovery Environment (loader) (on /dev/sda8)' --class windows --class os $menuentry_id_option 'osprober-chain-3C98C9B298C96B4A' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt8 --hint-efi=hd0,gpt8 --hint-baremetal=ahci0,gpt8 3C98C9B298C96B4A
else
search --no-floppy --fs-uuid --set=root 3C98C9B298C96B4A
fi
drivemap -s (hd0) ${root}
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
SOLUTION:
first I needed to mount Windows EFI partition which was /dev/sda1, so :
mount /dev/sda1 /mnt
Then issue the following commands and take note of the outputs:
grub-probe --target=fs_uuid /mnt/EFI/Microsoft/Boot/bootmgfw.efi
which outputs: 18DF-E58E and
grub-probe --target=hints_string /mnt/EFI/Microsoft/Boot/bootmgfw.efi
which outputs: --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Finally edit the os-prober entry to the following in /boot/grub/grub.cfg
menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 18DF-E58E
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
Last edited by sonay (2012-10-07 18:20:20)

grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
--hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Sorry, no need to anymore. Thanks anyways.
Last edited by sonay (2012-10-07 18:08:39)

Boot failure with AMD core unlock *solved*

Similar Messages

Maybe you are looking for

Boot failure with AMD core unlock solved