Won't boot after kernel upgrade

I installed Arch and attempted to upgrade the kernel. I had to remove these pkgs because the depended on previous kernel:
ipw3945
madwifi
ndiswrapper
rt2500
tiacx
After kernel upgrade, won't boot:
Root device '....' doesn't exist, attempting to create it.
ERROR: Failed to parse block device name for '....'
ERROR: unable to create/detect root device '.......'
Dropping to recovery shell...
This is the final error messages after making the following attempts to correct the problem:
Added rootfstype=ext3 to kernel line.
Added rootdelay=8 (then 20) t6o kernel line.
Replaced UUID moniker with /dev/sda1 (SATA drive).
Checked /dev/ in recovery shell, no HD's listed.
Checked /etc/mkinitcpio.conf and it has sata listed under HOOKS.
Bill

userlander wrote:did you try the fallback kernel?
Yes, same result as with the upgraded kernel.

Similar Messages

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

Mac mini won't boot after RAM upgrade.

Tried installing new RAM in my Mac Mini, 512MB stock to 2GB of Crucial. Followed the directions to a T, grounded myself the whole time.
Things I've tried so far:
1. Resetting the PRAM, no luck.
2. Holding option at start-up, shows no icon.
3. Holding shift, no luck.
4. Holding X, nothing.
How do I get it to accept a CD if it won't boot?

Welcome to Apple Discussions!
You clearly have a problem, but you don't describe exactly what that is other than that your mini won't boot after the upgrade. What happens when it starts up? Does it attempt to start and hang up on the grey or blue screens, or does it start beeping at you almost immediately after you try and start it up, and also flash the power light?
If the former, then you may have dislodged a connector while working inside the system, in which case opening it up and checking that everything is firmly connected would be the first thing to do. If the latter, then the beeping/light flashing is the system telling you it has failed the power-on self test and the pattern of beeps/lights indicates why. In your case likely the system can't find workable memory. In that instance, opening the system and ensuring that the RAM is firmly and fully seated would be a good step, and if the mini continues to fail, then replacing the new RAM with the original to test that the system will then start.
It is not likely that anything had damaged your MacOS install in the process of upgrading, thus normally no reason to need to boot to CD as a result of a RAM issue.

[SOLVED] can't boot after kernel upgrade

I'm on 3.5.4-1-ARCH, then I upgrade to linux-3.5.6-1 and reboot. The result is a message that cant load "autofs4" module. And a "uname -r" says me: 3.5.4-1-ARCH instead of 3.5.6!!
I've tried to run depmod after the upgrade with de same result.
Last edited by siot (2012-10-09 20:11:23)

It sounds as if the new kernel did not find its way to your boot partition. This could have been because the boot partition was not mounted when you did the upgrade (in which case the file is in the /boot mount point of your root partition) or that you are not booting from the partition you are expecting (Do you, per chance, have two boot partitions?)
Regardless, boot from an install media and fix it from the command line. if the files are in /boot of the root partition rather then one the boot partition, mount both volumes and just move the files. If there are multiple boot partitions, move the files to the correct partition. Once you reboot, fix the /etc/fstab to point to the correct boot partition.

AP350 won't boot after IOS upgrade

I have an AP350 and after I upgraded the IOS to 12.2.15-JA it won't boot. In monitor mode it tells me there are no bootable images available. I see the new image there. I was having issues with the authentication on this box. This was the reason to upgrade the box to begin with. Now I have more problems here. If anyone can help please I could use it. The old directory where 12.2.13-JA1 was in is not there and the new image is not in a directory either if that helps.

Please read the attachment. It shows you how to recover IOS from bootstrap. Specifically, please go to "Using the MODE button" in "Reloading the Access Point Image"
As a side note, you cannot use HTTP interface to upgrade IOS software starting 12.2(15)JA. Below is from release notes:
TFTP Required to Upgrade 1200 Series Access Points to this Release
Software upgrades fail when you use the web-browser interface to install Cisco IOS Release 12.2(15)JA on 1200 series access points. The image size exceeds the access point's 4-MB restriction for software upgrades. Use TFTP to upgrade your 1200 series access point to this release. For complete instructions on using TFTP to upgrade access point software, see the "Working with Software Images" section on page 20-18 in the Cisco IOS Software Configuration Guide for Cisco Aironet Access Points.

Satellite A200 PSAEOE won't boot after memory upgrade

Hi, I am first time here.
I have bought a Toshiba A200 PSAE0E-03J02JDR with 2 GB ram memory. I bought a pair of Corsair ram (2*2GB VS2GSDS667D2). After I installed the memory the computer won't boot. I have intel 945 chipset, which is capable of 4 gb (manual page1-2). The bios version is 1.8 from 2007.
Can anyone help me, please.
Message was edited by: ovidiu marian

Hi
The A200 series supports different chipsets;
Intel 945PM
Intel 945GM
Intel 943GML
As far as I know your notebook supports the *Intel 943GML* chipset and this chipset supports max 2GB RAM.
Take a look in your notebooks user manual *Page 18.*
Summery: 4GB RAM are not possible and therefore your notebook does not boot up.

GE60 2OC won't boot after RAM upgrade...

Hi forum
I just upgraded my laptop ge60 2oc 014ne, with two 8 GB corsair value select sticks.
Now my machine won't boot. I hit the button, the power light turns on, then the harddrive indicator lights for a while... And then it just stands there... Nothing shows on the screen..
Any help? Please..
Cheers

Quote from: NexumxRaptoR on 07-November-13, 23:58:36
another thing is that you can't put in more RAM than the notebook came shipped with right?
If it originally had 8GB over 2 slots you can't put in more than 8GB in the entire notebook right? (I thought I read something about that somewhere....)
Nope. Not true.
In most cases it's restricted by 1 of 3 things....either the CPU, the IMC (Integrated Memory Controller) or the BIOS.
MSI is pretty good about NOT restricting it via the BIOS in some way.
Usually it ends up being the IMC that restricts it, either via a maximum memory (say 32 GB) or via a maximum amount of memory per module (say 8GB).
Either way, the GE60 I believe should support up to 16GB of memory. I think it should come with 2 memory sockets. You need to ensure that they are 1.35V compatible given the fact that you have a Haswell system.
http://www.msi.com/product/nb/GE60-2OC.html#specification
Confirms that it has 2 memory sockets, and supports up to 16 GB of memory, so 2 x 8GB sticks.

IMac won't boot after ram upgrade

For some reason, my iMac late 2013 3.4Ghz quad core i5 won't boot with new ram modules added. New ram is exact same specs as original that came with the iMac. I've tested the new ones on their own in the iMac, and the system boots up fine. Same goes with just using the original ram. But when I put all 4 together, the iMac doesn't boot up. Not even the chime.
Combinations I've tried are:
1-Old
2-New
3-Old
4-New
No boot
1-New
2-Old
3-New
4-Old
No boot
1-New
2-Old
3-New
4-empty
No boot
1-Old
2-New
3-Old
4-empty
No boot
1-New
2-Old
3-Old
4-New
No boot
1-Old
2-New
3-New
4-Old
No boot
The only combinations that work are:
1-New
2-empty
3-New
4-empty
Boot good
1-Old
2-empty
3-Old
4-empty
Boot good
I just got off the phone with Apple, and they are saying all modules have to be the same size. ie. all 4GB or all 8GB. Can't mix and match sizes. Which is strange, because I've never heard of this. My Mac Pro has different speed ram modules, with different sizes in it. As long as I install ram in pairs, it runs like a charm. I've even heard the new iMacs don't have to have ram installed in pairs.
I'm wondering if slot 2 and 4 are maybe damaged? I haven't tried using just slot 2 and 4. To my understanding, you have to use 1 and 3 first. Can anyone confirm this?
Also, I've read a couple of people had to wait 30 seconds for the chime when they installed new ram in their iMacs. I didn't wait 30 sec to see if it would boot. Never heard of any Mac taking 30 sec to just chime in. lol Has anyone else experienced this? Is there a fix? Tx.

CLICKY CLICK---> iMac: How to remove or install memory
Or
Apple>About This Mac>More Info>Memory: Double click "Memory Install Instructions" at the bottom right of window.
my iMac late 2013 3.4Ghz quad core i5
Conflicting info. Your system profile shows: Mac Pro, Mac OS X (10.6.8). Please update/correct.

Brand new iMac 27 2011 won't boot after Lion upgrade

Got a brand new iMac 27 2011 yesterday and did an update to 10.6.8 first before installing OSX Lion over it...
After restarting it just shows then the "prohibitive icon" on screen and shuts down after few seconds...
It won't even boot from an USB stick with the OSX Lion image on it...
Recovery partition works but can't do a reinstall from there....
So going back to 10.6.8 now...

Just so you know I purchased brand new imac in July and did the same upgrade as you. I just installed Lion but did not have any issues. Only one concern overall though, it slowed down my new imac a bit. Not sure if there are settings or not but Leopard was faster than this. AppStore, iTunes are eating lot of memory and CPU util goes up.

Powerbook won't boot after Leopard upgrade.

I'll get the apple logo and spinning gear, then blue (kernal panic) screen, and that's as far as it will go.
I thought I recalled a problem with the Unsanity application enhancers, so I started the PB up in target disk mode and removed the one .ape...that didn't help...now I need help.
I've searched around here but cannot locate a similar discussion.
thanks

Hi Limnos...My profile says 10.4.11 since I have not gotten 10.5 to install yet. Never before had 10.5 on this PB. I was attempting to upgrade to Leopard from the retail install disc, but after the process concluded normally, the restart hung with a blue screen kernal panic.
I attempted safe boot and it would not do that either. I attempted to restart off the install DVD again, and it would not do that either. It would only boot into target disk mode. I have not tried anything else today, yet. Waiting for some advise from here, before I spin my wheels any more.

Edge 15 won't boot after BIOS upgrade

Hi everyone.
I have a Lenovo Edge 15 and I recently (as in, this morning) tried to upgrade the Bios from the support site for the Haswell i5.
I downloaded the exe, let it run and received the notification that my computer would restart. I just it do it's thing, it goes into the BIOS and appears to be install the bios fine, and then I receive a notice my laptop would restart.
But, once it restarted, it set went into a boot menu. I select the HDD where my OS is installed but the screen goes blank and then (appearantly after restarting) goes back to the boot screen.
I can get into the BIOS fine but I cannot get past the boot menu.
I tried opening my laptop, disconnecting the battery and the CMOS battery (I think it's a CMOS battery), plugged/put them back in and I still have the same issue.
Any ideas as to what the issues is?

Blink code indicated BIOS corruption. Try Roll back of BIOS:
http://h10025.www1.hp.com/ewfrf/wc/document?cc=uk&lc=en&docname=c02693833
You have to try this many times, the timing of holding the keys together is very important 1-3 seconds.
If that doesn't work I'd probably affected your hardware, you may have to contact HP.
thanks,
++Please click KUDOS / White thumb to say thanks
++Please click ACCEPT AS SOLUTION to help others, find this solution faster
**I'm a Volunteer, I do not work for HP**

PC won't boot after memory upgrade (on MSI P45D3 Platinum)

I am having a problem on my MSI P45D3 Platinum motherboard system (Dual OS: Win XP and Win 7)
Until recently I was running it on PATRIOT 2GB (2x1GB) 1600MHz DDR3 PDC32G1600LLK memory (CL7) and all was fine, though running only at 1066MHz, since I couldn't tweak the settings (latencies/voltage) in order for it to run at 1600MHz.
I wanted to add RAM but since I couldn't find the same type anywhere in my town, I decided to go for PATRIOT 4GB (2x2GB) 1600MHz DDR3 PSD34G1600KH Signature Line (CL9). However, the system never booted again (blank screen, no signal sent to monitor) after adding the two new sticks of RAM! The new RAM is working fine when I remove the old and vice versa, so I know it is not a case of defective sticks.
I must mention that I cannot fiddle with the RAM timings because I cannot even reach BIOS!
Any help will be most welcome!

Mixing different memory modules is always a gamble and likely to cause such problems. Identical modules should be used for best results.
In many cases, you can set what you want regarding memory configuration, getting the RAM mixture to work stable will simply be impossible, even though there is no defect.

MacPro 1,1 10.6.8 won't boot after kernel panic

I apologize for the long post, but figured I'd lay out the whole scenario.
I had a kernel panic in Safari yesterday. Powered down. Powered on. Message appeared saying to power down, and restart again. Did that. Then the fun started. The restart was slower than normal, with each screen (gray, blue, Snow Leopard background screen) slow to come up and move to next. Finally, it stopped on the Snow Leopard screen but the login screen never appeared.
I have my fair share of kernel panics, sometimes triggered by something Virus Barrier is guarding against, sometimes for other reasons. I regularly save the reports but can't say off the top of my head that I know of something that could be implicated in this present issue.
Since this issue surfaced, I've tried multiple interventions to no avail. I used Disk Warrior to rebuild the directory and optimize the disk, both reported by the software as successful. The SMART status of the disk was normal. Verified and repaired permissions. As is typical, some were reported but nothing noticeably out of the ordinary. Still not able to reboot.
Used Apple's Disk Utility to check the status of the drive, and ran through the other available diagnostic tests. Still not able to reboot.
Among different attempts to restart, sometimes it stopped at blue screen, sometimes at Snow Leopard default background screen image.
Reset PRAM. Still no reboot. Booted into Single user mode/verbose mode. Then fsck -fy. The second time I ran the latter, it reported "FILE SYSTEM WAS MODIFIED" and I ran fsck -fy once more.
The report on screen in Single User mode showed some things I don't know how to interpret. Lines of the report beginning with "AppleACPICPU: Processor Id= " were as follows:
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=1
AppleACPICPU: Processor Id=0 LocalApicId=7
AppleACPICPU: Processor Id=0 LocalApicId=6
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
AppleACPICPU: Processor Id=0 LocalApicId=0
Other things from the report:
• Mac Framework successfully initialized using 16384 buffer headers and 4096 cluster IO buffer headers
• BSD root: disk1s2, major 14, minor 5
• jnl: unknown-dev
• com.apple.launched 1 com.apple.launched1 *** launched[1] has started up. ***
Do things in this list look normal? Any red flags?
As it stands now, none of the measures have enabled the computer to reboot. When I power on it goes straight to the default Snow Leopard screen. Oddly, if I power it off but then later go back and hit the space bar, such as one would do when the computer has been idle and the computer or screen has gone to sleep, the computer instantly powers itself on. Likewise, trying to power on and hold down the "c" key to attempt to boot from the system CD to Disk Utility does the same thing. That's really odd. Powering on via any key on keyboard is not expected behavior!
So ... what I most want to determine is:
• Were Disk Warrior and Disk Utility mistaken in reporting that the hard drive is functioning normally? Was it actually failing?
• Did the fsck -fy routine, with the reported action "FILE SYSTEM WAS MODIFIED," hasten it to its death?
• Is it more likely that the processor or some other major hardware issue is involved?
The computer is old, and has been more fitful over the past 6 months or so, but I've also had more issues with Virus Barrier forcing kernel panics during that same time, so it's been hard to say whether it was the computer that was acting wonky or Virus Barrier causing the wonkiness.
I just need to know whether I should wipe and reformat the existing WD disk, go buy a new disk to format, or give up on the computer and order a new MacPro model to replace it. If the latter was undertaken, I would really prefer to get the old MacPro functioning long enough to have use of it while I can complete an order and get something new set up. I have some tasks that I need to be getting done and data that I need to access to take of other tasks. I have a current Time Machine back up. But now that I can't even boot from Disk Utility, it seems I will have to buy another drive to do the interim solution.
I would very, very appreciative of any expert advice.
Debbie

Hi hatter,
Good to talk with you again about my Mac Pro 1,1. Can't believe I still have this stalwart machine, but it just keeps on keepin' on.
I have a Mac Box Set with Snow Leopard. That's the disk I was using Disk Utility from. I did the hardware tests that I saw among the tools available when one boots from the disk. Could be I'm missing something.
While I was waiting for a reply from someone at Discussions, I went looking at Walmart for an SATA disk. They were completely out of them due to local storms that fried a lot of people's computers and hardware. It's a small town. Not a lot of options. So I came back home and thought I'd try again to boot from the Apple DVD. That time it worked. I was going to do a restore from the Time Machine backup, but then decided to just reinstall the OS from the DVD and see what happened. Clean seemed better than dirty, you know?
At any rate, I installed the OS - to the same WD Caviar Black hard disk. When it restarted, everything came up looking back to normal, except that I need to update to 10.6.8 and reinstall iWork apps and other Apple add-ons as needed. Oh what a relief it is!
I would like to do some hardware testing though. If you can advise, I would appreciate it.

Macbook Pro won't boot after Yosemite upgrade

I downloaded Yosemite this evening, but the installation never finished. When I get past the login screen, a loading bar will half load before the computer shuts down. I tried command option p r without success, holding the option key down while starting only gives me the option of my main drive and it doesn't work. I tried holding down command r during start, but that doesn't do anything either. Any suggestions would be appriciated.

Reinstall Lion, Mountain Lion, Mavericks or Yosemite without erasing drive
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu.
Reinstall Lion, Mountain Lion, Mavericks, or Yosemite
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

[SOLVED] Gnome 3 won't start after kernel upgrade

I have upgraded to kernel 3.0, and now I am getting the following error when I try to start gdm:
** (gdm-binary:936): WARNING **: Failed to acquire org.gnome.DisplayManager
** (gdm0binary:936): WARNING **: Could not acquire name: bailing out
Can anybody explain what the deal is?
Last edited by spiritwalker (2011-08-17 16:50:44)

theseus, thank you for the reply. I thought you can only start gnome using some kind of display manager. If I understood you correctly, I did 'telinit 5' and then 'startx' with the folowing results:
INIT: Switching to runlevel: 5
INIT: cannot execute "/usr/bin/xdm" <---- This line repeats 10 times
INIT: ID "x" respawning too fast: disabled for 5 minutes
But when I did 'who -r' I got this:
run-level 5 2011-08-16 02:26 last = 4
So I tried to start X wich resulted in the following:
http://i.imgur.com/yydcd.png
http://i.imgur.com/RNapr.png
http://i.imgur.com/NnFaM.png
Also, arch is installed in a virtual box, so I didn't install any video drivers like nvidia.
Thanks
Moderator edit:
spiritwalker, please do not post pictures of this large size: https://wiki.archlinux.org/index.php/Fo … s_and_Code
In this specific case you could have made use the log files in /var/log and posted the relevant info in [ code ] tags.
Besides, this way you will get used to work with logs, which is mandatory in Arch, imo.
Last edited by bernarcher (2011-08-17 13:33:28)

Won't boot after kernel upgrade

Similar Messages

Maybe you are looking for