P6NGM no longer boots after clearing CMOS?

Hi all, hope you can help me with this.
I got a new graphics card today (PoV 9800GT), I put it in my P6NGM (not exactly sure which version, uATX, it has VGA and DVI out, but no HDMI) and it didn't work, I would get the regular boot beeps but no signal. Onboard card was working fine, so I was scratching my head trying to figure it out
Thought I'd clear the CMOS to see if it made a difference, so I turned the PC off, moved the jumper over, left it a little while, turned it back on and... nothing. Fans kick up but I get no beeps and no signal even on the onboard card now.
Only thing I can think of is when I first bought the mobo I found out it doesn't support 45nm CPUs as standard, so my E8400 wouldn't work. I borrowed my brother's 65nm c2d, updated the bios and after that my 45nm chip worked fine. Can clearing the CMOS somehow revert the bios version or has this got nothing to do with it?
Many thanks.

Quote from: chef jeff on 25-March-10, 20:34:12
Really? How does that work? I see no supplemental power necessary. However, nowadays it all needs a 12v rail. Used to be most of it ran off the 5v rail, but no more. Can't know that unless you tell us. Too much guessing here. Please post your full system specifications.
Yes there's a few models out there now that have this, mostly on 45nm dies. Zotac do a similar one too.
Quote
The Point Of View GeForce 9800 GT Green Edition low power design reduces power consumption by up to 30% compared to a standard GeForce 9800 GT graphics card and no longer requires a supplementary power connector from your PSU, yet still delivers the same great 9800 GT-class performance as previous versions.
http://www.overclockers.co.uk/showproduct.php?prodid=GX-025-PV

Similar Messages

Z77A-GD65 Wont Boot Without Clearing CMOS. Gets Error 32.

Hi!
I just switched GPU from 2x 7950 to 980.
I cleared drivers etc etc and was powering down my pc for the replacement. took out the cards and put in the 980.
When i later was trying to boot, i got debug error 32, which is early cpu initialization. So i checked all the cables and tried again. Same thing.
Took everything out and reinserted it again. Same error. even tried the to take out each ram to see. Still nothing.
I later cleared cmos and the computer booted. but then when i restart i doesnt boot until power everything down and clear cmos again.
Do you guys have any idea?
My specs are
Z77A-GD65
2500k CPU (Now after clearing CMOS at stock speed)
Corsair Vengance 2x4GB RAM
850W Bronze psu

Quote from: Nichrome on 30-January-15, 15:01:36
Tryreplacing battery. Also could try to run it with single Ram stick and outside of the case.
I Couldn't wait so i went to town and bought me a battery, didn't change anything.
I've tried running a single RAM in each slot, just to try. no change there. Still error 32.
I've also test it outside the case now and still no difference.
Otherwise i've noticed i can boot if i press the reset button exact when debug code 55 shows. It's really weird. doing this way all bios settings are still there and i can test my pc with OC. I've played Dying Light on it this way with no problem at all. except this annoying code 32 who reappers everytime i restart my computer and hinders it to boot...
EDIT: Also sometimes (very rare), it starts at first boot.

Wont boot unless clearing cmos

JBAT1
Ok here's the story in full.
Received K8T Neo2-FIR - was completely DOA along with a working 3000 90nm.
Received working K8T Neo2-FIR, got system to post after 5 hours of work (including 1.30 hours to watch Open Range whilst angered).
Post Showed 'invalid bios checksum' etc, the board now has 3.31 bios and still it will not post, will not even boot to be precise. It won't kick in fans etc UNLESS the jbat1 is set to CLEAR CMOS. Then the system works fine other than not retaining any bios settings.
I have now installed Windows XP Pro 64bit along with the 64bit drivers, unfortunately cannot use any MSI tools. I am going to update to the latest RC1 of XP64 pro as soon as Microsoft sort out the error in the download page/server.
Anybody got any clue to solving my problem? Oh and i can't run my Kingmax 3700 in dual channel, infact i dont think i can run 2 sticks in single channel either. (2x512MB).

550Watt PSU
22A at 12v rail
3000+ Winchester
MSI K8T Neo2-FIR
2x IDE HDD on IDE1
1x DVDWRITER on IDE2
9700Pro
1GB Dual Channel 3700
The PSU is going to be my next purchase, i have witnessed 2 Tagan UO2's explode recently so am going to go with an Akasa 460W. To be honest the current PSU is crap quality but testing the rails and amperes output actually hits 530Watts, on load i doubt it can hit this but still has enough power to satisfty 3xmore drivers and 6case fans in another SocketA machine which takes a lot more power at the cpu.
The ram has been in all possible combinations provided by the book but i can only get it to run 1 stick. I cannot run the LIVE UPDATE tool as im using Windows 64Bit. I've got 1 hour 26mins left on the download for the latest beta so hopefully i can run the tools tomorrow.
I have tried booting the machine etc with all items unpluged and select ones etc but no luck, it will only work if the jumpers are set to clear cmos. Maybe a multimeter on the jbat would reveal whether any current is getting passed through pin 1. Long shot and hopeless i know. Theres probably a reasonabe explanation.
I've now had 3 different Bios errors on post, so i think its just screwed it with the first boot on jumper2-3.
Soft reboots work fine (it hasnt stopped to tell me bios errors) just 'NO BIOS INSTALLED' at the sata raid post screen.

KT6 Delta won't boot after clearing the BIOS

I have just put together the machine as per my signature and run into a few problems. The XP 2800 mobile is not recognised as such but as a XP1800 when I set the FSB to 133. Am I right in saying this CPU should run at 1.65 volts as it seems to wants to run at 1.75. I changed the V Core to 1.65 and it boots ok but when I tried it at 1.6 it did not want to boot, ie no video output. I no longer get the single BIOS bleep and the monitor stays on standby. This has happened before and I got it running again by clearing the CMOS and reseating the RAM but this time I have done the same and it won't boot. Is there anything else I should be doing please. Many thanks.
Having looked at the Socket A sticky I see that my diagnostic D bracket is showing 1,2 and 3 showing red and four not on at all which would seem to point at the graphics as being the problem.

Hello!
Voltages should be set to "CPU default" or similar. Your processor comes in different versions, try setting to 166 instead of 133. Always when changing processor one should clear CMOS, by powering off, unplugging power cable, and then move JBAT jumper for a short time, a minute or so.

Pavilion p6-2133w - Wont post/boot without clearing cmos first

I really need some advice guys. My dad just recemtly bought this computer from a friend (friend says it had no problems) which could be true.
I did a fresh format after downloading all drivers from HP, installed them all incuding the bios update (which i think is my problem) and now i have to clear cmos every single time before it will boot or even post, if i dont clear cmos the computer does turn on (fans have power) but the monitor stays black. When i do clear cmos the pc boots fine and the only thing i notice wrong is some files wont download thru IE (like adobe flash, says no internet connection when the adobe installer trys to download) and im getting constant sec.certificate display blocked errors thru IE other then that it runs fine.
So im assuming something went wrong installing the bios update, im praying somebody has or even knows what the original bios is supposed to be ? or someway i can fix it. I have since done another format and tried reinstalling the bios update and all other drivers but nothing changes
Any advice, opinions, or idea's would be greatly appreciated
Thanks in advance
Vito

I really need some advice guys. My dad just recemtly bought this computer from a friend (friend says it had no problems) which could be true.
I did a fresh format after downloading all drivers from HP, installed them all incuding the bios update (which i think is my problem) and now i have to clear cmos every single time before it will boot or even post, if i dont clear cmos the computer does turn on (fans have power) but the monitor stays black. When i do clear cmos the pc boots fine and the only thing i notice wrong is some files wont download thru IE (like adobe flash, says no internet connection when the adobe installer trys to download) and im getting constant sec.certificate display blocked errors thru IE other then that it runs fine.
So im assuming something went wrong installing the bios update, im praying somebody has or even knows what the original bios is supposed to be ? or someway i can fix it. I have since done another format and tried reinstalling the bios update and all other drivers but nothing changes
Any advice, opinions, or idea's would be greatly appreciated
Thanks in advance
Vito

Windows 7 no longer boots after upgrade from Lion to Mountain Lion

I got a late 2011 MacBook Pro, on which I installed Windows 7 with Boot Camp. After I upgraded from Lion to Mountain Lion, I can no longer boot Windows. If I keep the option button pressed during boot I only get the OS X and recovery options, and if I choose to boot Windows from the system preferences pane, I get a message that says that no bootable device was found. However, I'm sure that the partition is still there, because I can see it in finder and browse the files normally. How can I boot Windows again?

"Easier" in this case as an alternative is defined as repartitioning/reformatting your disk, and restoring from backups (which for most people also means starting from scratch with Boot Camp Assistant and Windows since most users aren't backing that environment up).
What you did is, in my opinion, easier and faster. But if you don't know what you're doing can lead to data loss. But then, by definition, blowing away your disk and starting over with a restored backup begins with data loss!

Leopard USB install no longer boots after software update

Hi all,
I have recently installed Leopard onto a USB partition in order to perform maintenance on my main Leopard installation. Installation proceeds without a problem however after downloading software updates the USB partition will not boot successfully, despite there being no problems with the disk / volume structures / apparently anything at all. In desperation I also tried to install Tiger, which worked, however I have the same problem after updating - it will not boot! I don't think my hardware is at fault - Techtool Pro tells me all is in order.
Has anyone had this problem and if so, how did you fix it?
Thanks,
Jason

I just installed Leopard onto a USB 2.0 external hard drive for a dual-boot. It booted fine at 10.5.1 but is taking ridiculously long to boot after 10.5.2 (I just got it to finally boot after the update while waiting more than 40 minutes!).
It seems that you may want to attempt booting several times - maybe turning off the machine in between or booting to the internal OS first and then to the external. Can't help you much beyond that as this is my introductory experience with this mess.

No signal after clearing CMOS

Hey,
I was having problems and so chose to clear the cmos (using the jumper). Now there is no signal on monitor!
Just to make sure that it was cuz of clearing cmos, I had another computer with the problem so I did it to that one too lol. And that one also now shows NO signal on monitor. The monitor is working I've tested it with other comps. The picture was showing until i cleared cmos.
the two motherboards I have the problem on are:
MS-7267 Ver: 3.0
PM8M3-V H
Any help is appreciated. Everything is powering up, only thing is that nothing shows up on the monitor, and the monitor is in the "stand by" "yellow light" state.
Thank You

sorry to hear you got double wammy from your mobo but be frank with us did you turn the power off before changing the jumpers setting or 240volt to power supply was still connected on both occasions?? if power was connected you might have caused some damage to your mobo?? lets hope not.
try this if you have time and patient.
1-unplug the pc.
2-Remove all memory and insert only one in the slot1 which is closest to cpu. if you can try to interchange the memory if they fit.
3-change the jumper setting to position where it clears the cmos and please leave it for at least 30 second and not ten. then after 30 second put the jumpers in the original position (make sure you get this right).
4-then plug the pc and power it.
there are occasions where static charges do prevent mobo from working. it has happened to me, and i thought that i had lost the mobo yet it worked a few days later??
lets hope this gets you going.
good luck
p.s do make sure you connect the speakers to mobo, from bip bip sound you may be able to tell the kind of fault you have .

Can\'t boot without clearing cmos (kt3 ultra2)

Hi,
My kt3 ultra2 board won't boot up unless I clear the CMOS. I am using the following basic configuration:
Athlon 1800+ w/ alpha pal8045 heatsink
256 mb of samsung pc2700 ram
Radeon 8500LE graphics card
My psu is a 400W powmax. Here are the specs from the side of the unit:
3.3V 28A
5V 30A
12V 25A
my cpu temp peaks at 40C and the cmos battery is at 3.39V.
I am running at default settings w/ cpu fsb=100. Everytime I power up the computer (from cold start) I need to clear the CMOS. Otherwise, the D-Link lights hang on memory detection test.
Doing a soft reboot (ctrl - alt - del) once it starts up does not cause it to hang.
Either way once the thing boots it says:
CMOS/GPNV Checksum Bad
(does any one know if this could be why it's scewing up)
What could be causing this problem? Any help would be appreciated.
Thank you

I bought one of these boards about 2 weeks ago and have had terrible problems with my geforce 4 concerning exactly the same issue. Now from the support forums i have been reading, everyone seems to say different things. Either change your ram, power supply, graphics card (how would you feel if someone told you to change your geforce 4 ti4600 that you paid £300 for?)
Now lets face it, motherboards shouldn't have to be picky about components should they? Power supplies are "power supplies" at the end of the day, and yes sometimes there are good and bad makes and models, but it shouldn't stop someone from using a regular bog standard power supply. My thoughts and concerns about the KT3 Ultra 2 is that the motherboard manufacturer is in the wrong here and do not seem to be doing anything about it.
I've worked with PC's for about 4-5 years and have used many makes and models of motherboard and been able to get them working successfully every time, however the MSI KT3 Ultra 2 board is plagued with problems and it's about time someone did something about it. How would you feel if i sold you a car that would only go 10 miles and then stop working?
Matthew

Cannot boot without clearing cmos

Hi! Hope someone cann help.
My system is:
MSI K&T266 pro2-A
AMD Athlon XP2000+
40G Maxotr 133
ATI Radeon8500
256M Nanya ddr2100
Noname dvd and floppy and case w/ ample cooling
350W antec psu
Windows 98 se
The only way to get the system running is to clear the cmos. After booting up everything seems to work fine, but as it is new(n-board and cpu and hd), I have not really tested it. The system shuts down fine, but will not boot. When I try to restart from a running win98, I get a blank screen but all fans and drives continue to be powered.
Can someone please help
THNX

read the sticky and also
get memtest86 and check ram http://www.majorgeek.com
check cooler clip faces psu

K7n2 delta2 platinum - changed FSB and can't boot or clear CMOS

Hi all,
specs first:
KnN2 Delta2 Platinum board
Athalon Barton 2800 XP
2 sticks of 256 pc 3200 ram and one stick of 512 pc3200
Last night I went into the bios of my new board, and unthinkingly set to CELL settings to manual and jacked up the FSB way up. Shouldn't have been working on my computer after a 12 hour shift. :( Anyway, it didn't boot when I reset. I tried clearing my CMOS and have unplugged the power, taken out the battery and the whole shabang in the CMOS clearing faq, but its still not giving me any beep codes or anything at all. I suspect my CMOS isin't clearing, however I'm wondering if its possible I've fried my new barton 2800 XP, my board, my ram, or all of the above. :( :(. I've read a ton of other delta boards having a safe mode jumper, j10, which will reset the fsb setting to 100 mhz, but can't find it anywhere for the delta2 platinum.
It was booting and getting into my OS before this, can anyone help?
Thanks in advance.

Quote
Originally posted by axeluktoo
Hi,
Muncher23: Hmm, I've seen this before only recently - no solution - as yet, that I know of. You could try putting a lower FSB CPU in the mobo and then clear the CMOS - it might default to the CPU's lower FSB setting. Might work, then again may not.
Yes, this worked, however it was an acident. To test my chip I threw in my 1800 xp chip, cleared the CMOS again (which apparently was working fine) and suddenly it started posting beep codes. I assumed that meant I had burned my 2800 and returned it to the place of purchase. They threw it on a board and said it was posting fine, but I got my money back anyway. Going to go pick up another 2800 this weekend probably.
Anyway, I havn't actually tried the insert method. Oh, and yea, I jacked the FSB up to 300 or so... I think I'm somewhat confused, as I've got a 333 chip in a 2800 so I think I've mistaken something fundamental here.
Quote
I suspect my CMOS isin't clearing
Actually, it probably is clearing. On earlier K7N2, when the CMOS is cleared everything is set to default EXCEPT the FSB setting, that's why it's usually necessary when the FSB has been pushed too high by the user, to use the FSB Jumper (SAFE/USER) to reset the FSB to default.
I fail to see the wisdom of removing this jumper from later boards!
You should also try substituting your CPU with another - just to make sure it isn't the CPU that's at fault.
Sorry I wasn't of more help.
Axel [/quote]

Bootcamp will no longer boot after deleting partition #3 of my new Mac Mini. What happened? Was it the way I tried to reclaim the HDD space for Mac?

Here's my dilemma. I have a new Mac Mini - a week old. I installed Windows 7 on it using Mac's Bootcamp assistant. I then set up and configured my Windows 7 world and everything worked fine. No issues logging in between Lion or Win7 via the restart/option key procedure. Well, yesterday I split my Mac HD partition one more time to create a third partition (was created as an "extra", e.g. possible future partition for another operating system). After creating it, I then decided that I didn't really need it. So I deleted it in Disk Utility and attempted to drag the Mac HD partition line downward so as to "fill in the gap" and reclaim the lost hardrive space. It seemed as if I could reclaim about 1 gig or so, but I figured...oh well.
Well, the Mac HD partition seems to work just fine, but now I've noticed that I can't get into the Bootcamp partition anymore. It wont boot. If I try to verify the partition [doesn't even give me "repair" as an option), then it fails and gives me the following error message: "verify volume failed. invalid request." When I go to the Startup Disk option in my System Preferences section, it displays the bootcamp partition as a folder and not as a drive anymore.
I'm assuming that I messed up some permissions or lost some vital links during my attempted resizing/reclaiming of harddrive space. How do I fix this without having to reload either all of my Mac info or all or my Win7 info? I'd hate to consider the last two days of my life loading this crap up a complete loss.
Thanks in advance!

Thanks for checking in, BDAQua.
Problem solved.
In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
"If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
Gratefully,
tupester

W520 No Longer Boots After POST

Out of the blue, when I opened up my W520 it just stayed at a black screen and saw no hard drive activity. I had to power it off and when I turned it back on it showed the Lenovo splash, then the Intel PXE boot, and then saw a cursor blink once and then it just stayed black. Waited about 20 minutes and still the same thing. The bluetooth light stayed lit, but that was about it.
Did this about 3 more times and still the same thing.
I took out the hard drive and verified that it was still working on another computer.
I'm about to take a Windows 7 repair disc and see if there is some boot issues, but I can't even get the Safe Mode screen to pop up.

Looks to might be an issue with the hard drive after all. I put in a known working Hitachi 2.5" drive that had Windows 7 on it and it booted right up.
So right now, I'm making a repair disc for Windows 8.1 to see if it is an actual Windows issue. If it doesn't find anything, I'll have to run HD diagnostics.

My iMac will no longer boot after half installing Maverick (only the essentials package was opened). How can I reboot it back to 10.8.5?

I was able to get a copy of OS X 10.9, but it wasn't the one straight from the App Store (which is free and I wish I knew before I got this other copy, but oh well). There is nothing wrong with the copy, it just simply doesn't initiate the install when you double click on it.
I installed one of the packages (essentials) off file, but not all the rest of them. For some reason the other packages weren't opening because it wasn't accepting my password, so I restarted the computer to see if that would make anything better.
It didn't. It now boots to the grey apple screen and stays stuck loading. I assume because only some of the install disk was installed, it doesn't really know what to do. But how do I fix this? How do I unistall the essentials package so that it goes back to normal?
I tried booting it whilst holding down "Command+Option+P+R" and it takes me to a limbo area where you can access disk utility. Within disk utility I can see that everything is still there.
What is the process to get it back to normal (I previously had 10.8.5).
Please help!

Thanks for checking in, BDAQua.
Problem solved.
In the docs that came with my Powerlogix accelerator card, I found this sentence buried:
"If you reset the PRAM, the NVRAM code for OS9 compatibility is cleared, so you will have to boot from the Firmawre Update CD and perform this process again in order to boot in OS9."
The "process" it's referring to is the process of setting up the NVRAM for booting into OS9 from the CD.
Fortunately, I was able to find the disk, and it worked as expected. I can now, once again boot into OS9.
Conclusion: My (unadvised) attempt to load Leopard on this old machine apparently reset the PRAM on the accelerator card and cleared the NVRAM code for OS9 boot. Although I did attempt to reset the NVRAM via Open Firmware, it did not reset it on the accelerator card.
So, thank you BDAQua, for your "Ah yes" . . . that's all I needed to steer me in the right direction.
Gratefully,
tupester

System no longer boots after hard-reboot.

After I installed GNOME 3 from [testing] the system compleatly locked up, so I took out the battery and plugged it back in. Now at every boot I get this message.
Since fixing a netbook is a huge pain (no CD drive) I took out the 2.5" drive and installed it in my other Arch desktop. What files should I copy over to fix this?

Do I have to now uninstall the kernel26 and install it again when I'm done?
[root@localhost ROOT_ARCH]# chroot . /bin/bash
[root@localhost /]# pacman -Q mkinitcpio
mkinitcpio 0.6.9-1
[root@localhost /]# uname -a
Linux localhost 2.6.38-ARCH #1 SMP PREEMPT Wed Mar 30 08:47:36 CEST 2011 x86_64 Pentium(R) Dual-Core CPU E5400 @ 2.70GHz GenuineIntel GNU/Linux
[root@localhost /]# wget http://schlunix.org/archlinux/core/os/i686/mkinitcpio-0.6.8-1-any.pkg.tar.xz
--2011-04-10 13:42:53-- http://schlunix.org/archlinux/core/os/i686/mkinitcpio-0.6.8-1-any.pkg.tar.xz
Resolving schlunix.org... 75.119.219.151
Connecting to schlunix.org|75.119.219.151|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18332 (18K) [application/x-tar]
Saving to: “mkinitcpio-0.6.8-1-any.pkg.tar.xz”
100%[==========================================================================================================================================================================================>] 18,332 90.7K/s in 0.2s
2011-04-10 13:42:54 (90.7 KB/s) - “mkinitcpio-0.6.8-1-any.pkg.tar.xz” saved [18332/18332]
[root@localhost /]# pacman -U mkinitcpio-0.6.8-1-any.pkg.tar.xz
warning: downgrading package mkinitcpio (0.6.9-1 => 0.6.8-1)
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: kernel26: requires mkinitcpio>=0.6.8-2
[root@localhost /]#
EDIT: I used the wrong version, it worked now.
[root@localhost /]# wget http://schlunix.org/archlinux/core/os/i686/mkinitcpio-0.6.8-2-any.pkg.tar.xz
--2011-04-10 13:58:26-- http://schlunix.org/archlinux/core/os/i686/mkinitcpio-0.6.8-2-any.pkg.tar.xz
Resolving schlunix.org... 75.119.219.151
Connecting to schlunix.org|75.119.219.151|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18324 (18K) [application/x-tar]
Saving to: “mkinitcpio-0.6.8-2-any.pkg.tar.xz”
100%[==========================================================================================================================================================================================>] 18,324 71.4K/s in 0.3s
2011-04-10 13:58:27 (71.4 KB/s) - “mkinitcpio-0.6.8-2-any.pkg.tar.xz” saved [18324/18324]
[root@localhost /]# pacman -U mkinitcpio-0.6.8-2-any.pkg.tar.xz
warning: downgrading package mkinitcpio (0.6.9-1 => 0.6.8-2)
resolving dependencies...
looking for inter-conflicts...
Targets (1): mkinitcpio-0.6.8-2
Total Download Size: 0.00 MB
Total Installed Size: 0.22 MB
Proceed with installation? [Y/n]
(1/1) checking package integrity [####################################################################################] 100%
(1/1) checking for file conflicts [####################################################################################] 100%
(1/1) upgrading mkinitcpio [####################################################################################] 100%
warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
New optional dependencies for mkinitcpio
xz: Use lzma compression for the initramfs image
[root@localhost /]# mv /etc/mkinitcpio.conf.pacnew /etc/mkinitcpio.conf
[root@localhost /]# mkinitcpio -p kernel26
==> Building image "default"
==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [autodetect]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26.img'...SUCCESS
==> SUCCESS
==> Building image "fallback"
==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
:: Begin build
:: Parsing hook [base]
:: Parsing hook [udev]
:: Parsing hook [pata]
:: Parsing hook [scsi]
:: Parsing hook [sata]
:: Parsing hook [filesystems]
:: Generating module dependencies
:: Generating image '/boot/kernel26-fallback.img'...SUCCESS
==> SUCCESS
[root@localhost /]#
Last edited by infested999 (2011-04-10 18:03:25)

P6NGM no longer boots after clearing CMOS?

Similar Messages

Maybe you are looking for