Upgrade kernel beyond not booting anymore

Hi
upgraded with pacman -Syu without paying much attention to the output I guess. I had the beyond kernel. After a reboot I get the following error:
Unpacking Linux .. Ok, booting kernel
Initial ramdisk loading Modules ...
BUG: unable to handle kernel paging request at virtual address 0002005c
eip:
*pde=000000
Oops:0000[#1]
PREEPTXMP
Modules in : ide_cd
it's possible that I copied some of the output incorrectly, since I did it by hand.
Any suggestions would be welcome.
Thank you

Use Arch install cd to go back in & fix problems
check lilo/grub, mkinitcpio.conf ...
HTH

Similar Messages

Lenovo 3000 N200 0769 A42 not booting anymore

Hi,
We have a Lenovo 3000 N200 0769 A42 that is not booting anymore. Concretely, when the on/off button is pressed, the fan goes on for a few seconds, the HD led is switched on and the CDrom is running for a few second too, then nothing else, except the "On" led that remains switched on...
I tried this: http://forums.lenovo.com/t5/Lenovo-3000-and-Value-line/Help-How-to-reset-CMOS-on-3000-N200-model-076... to no avail.
I removed the keyboard and unplugged for one minute the only plug I found with red and black wires, to no avail either...
The computer seems dead... Any suggestion to reanimate it?
Thanks in advance,
Pierre

Hi, Thank for the reply.
There is nothing displayed on the screen and no access to the Bios.
I did tried to reset the motherboard after having removed the AC power, the battery, the HD and the RAM (by short cutting two exposed metal traces labelled CLRP1 and by unplugging the battery cable found behind the keyboard. To no avail...
I realize that the url given in my first post does not work. Here it is:
http://forums.lenovo.com/t5/Lenovo-3000-and-Value-line/Help-How-to-reset-CMOS-on-3000-N200-model-076...
Thanks again for the suggestion. Any other?
Pierre

Windows 7 does not boot anymore

Hi,
I have windows 7 operating system installed in my notebook. But suddenly my notebook is not booting anymore. I do have a backup image saved in a external hard drive, but can not install windows from there.
How can I re install windows 7 as I do not have a backup DVD.
Can anyone help me out?

Hay Munir
And how you have installed Win7 for the first time?
Jeka is absolutely right. You cannot start OS installation from image saved on external HDD.
I dont know which notebook model do you have but for Win7 installation you can use Microsoft installation disc. If your notebook model is supported for Win7 all necessary drivers, tools and utilities you can find on Toshiba support page. Just follow the link given by Jeka.

I made changes in the single user mode - now my MacBook Pro does not boot anymore.

Hello apple support community,
I made changes in the single user mode and my MacBook Pro does now not boot anymore. It displays a grey bar and the "work in progress" wheel. My intention was to change my admin password following these steps:
http://www.macyourself.com/2009/08/03/how-to-reset-your-mac-os-x-password-withou t-an-installer-disc/
however, I have to admit that there was a typo sneaking in - oops!
Any idea how I can undo changes made in the single user mode?
Thanks in advance for your support - I hope I don't sound to nooby
Till

Hello, Till1234.
Thank you for visiting Apple Support Communities.
Here is a troubleshooting article that I would recommend going through when experiencing this issue.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/TS2570
Cheers,
Jason H.

Upgrading to maverick not booting

Hi,
I have a mac pro 4.1 and I am trying to upgrade to maverick, it is nor working,
I have a drive with a maverick osx working already on another mac 4.1 with an Atti,
I tried this drive on my other mac pro with an Nvidia quadro 4000 and it does not boot the wheel stays spining,
I have tried cloning my hard drive and upgrading from 10.8.2 (this is woring on my mac) to 10.8.3 combo
the same thing happens the wheel stays spining after rebooting and it does not start
I have no Pci cards on my mac,
I have tried with 1Gb Ram , with 2 Gb Ram , with 4 GB Ram nothing is wortking
any help?
thanks
Ariana

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Satellite C850-1j1 does not boot anymore

my laptop Satellite C850-1j1 doesn't boot anymore.
Happened after partition changes. shows a error screen telling me the computer needs to be repaired using recoverymedia,
I've got a working hirens boot cd and usb (tested on other comp.) but the laptop is not responding
op. system win 8 64 bit brandnew.
suggestions are welcome

Hi
The message says that you have to install the system again using recovery media
As far as I know the notebook was preinstalled with the WIN 8 64BIT system.
You can use the HDD recovery option
Power on the unit and press F12.
Then choose HDD recovery option appearing in the boot menu.
Follow the instruction on the screen
Good luck!

[SOLVED] Kernel will not boot. No early hooks, nothing...

I am having some serious trouble getting my machine to boot. It never even gets to ":: running early hooks (udev)."
I normally shut it down every night, but I recently kept in on for a few days straight. I was having some trouble with a USB flash drive being read-only in Windows 8 in VirtualBox. I shut down Windows 8 and then arch wouldn't even read the flash drive. I'm pretty sure that pacman updated the kernel since I last shut down the machine, so I decided to restart just for good measure. I never got back in...
I am UEFI booting, running LVM on top of LUKS on top of two Samsung 830 256GB SSDs in mdadm raid 0. I have encrypted root and no swap. I have /boot mounted on a 512MB FAT32 partition and use a straight efibootmgr entry to start the system. It has worked fine until today.
My mkinitcpio.conf has
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are run. Advanced users may wish to specify all system modules in this array.
MODULES="ahci dm_mod dm_crypt aes_x86_64 raid0"
# BINARIES
# This setting includes any additional binaries a given user may wish into the CPIO image. This is run last, so it may be used to override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
## ORIGINAL ##HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
HOOKS="base udev autodetect sata mdadm usbinput keymap encrypt lvm2 filesystems fsck shutdown"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
My kernel parameters are
cryptdevice=/dev/md1:RootVault root=/dev/RootArray/VolRoot ro rootfstype=ext4 init=/bin/systemd add_efi_memmap initrd=initramfs-linux.img
I can boot fine from the Arch install media via UEFI at which point I can luksOpen, activate the lvm volumes, mount everything, and chroot in like normal. I have:
rebuilt the initramfs
reinstalled linux, mkinitcpio, and udev
erased and recreated the efibootmgr entry
tried to boot straight from the UEFI shell
slimmed down to minimal hooks in mkinitcpio
tried nomodeset and mem=4G kernel parameters
tried booting the kernel with debugging enabled at various levels
I get nothing at all every time. I boot up to a black screen with a static white cursor in the top left.
I am happy to offer any more necessary information and I would be extremely grateful for any suggestions. Thanks.
Last edited by matthew02 (2012-11-02 15:14:46)

lesto wrote:
same problem here with a stock kernel. solver rolling back to 3.6.3-1 by livecd.
seems a problem with AMD cpu. solution here https://bbs.archlinux.org/viewtopic.php?id=151686
I had just rolled back my kernel and was about to comment here that it worked when I saw your post. I had actually skimmed that other post, but since mem=4G didn't work for me, I didn't figure it applied. I suppose I should have read it more thoroughly. Thanks for the help everyone!

MAC Mini A1176 (MA607B/A) Kernel Panic / Not Booting

Hello,
I have a mac mini MA607B/A 1.66/2x1GB/60GB HDD, that is not booting. It Chimes and hands on the apple logo.
I searched this forum and I performed every solution I found. The mac is still doing the same thing.
I also changed the battery but no joy.
I inserted the CD that came with the MAC mini and it does exactly the same while booting from the cd.
I did a H/W check by holding the CMD+D keys and all tests were passed successfuly !!!
I booted in Verbiose mode and I have attached the log as a photo in this thread.
I really have no clue why it gives a kernel panic on CPU...
Temperature seems to be normal and the fan is working.
Any suggestions how to resolve this?

Hi,
Thank you for your reply.
I tried to boot in Open Firmware mode but it crashes almost imediately.
I have also Installed OSX 10.6 on an external usb hard drive of mine and tried to boot from that and it does exactly the same. I noticed that the external hard drive's light is on and binking while the computer is loading which means that it reads OS files. and after a while when the MAC freezes, the light goes completely off like there is no power supplied to it.
It does exactly the same thing even if i put the original disc that came with it and try to boot from that.
I entered Verbose mode again and now it always freezes after the "AppleIntelCPUPowerManagementClient: Ready" line
Also the keyboard is not responding and the lighs of the keyboard are off as well.

After 10.5 upgrade Mac will not boot from hard drive

I just upgraded to 10.5 Leopard but my mac will not boot from the hard drive even after selecting my hard drive as the startup disk. The mac will start to boot but will cut itself off before the boot is complete. I have to leave the Leopard disk in the mac and hold down C to get the mac to turn on but it only allows me to install the software again.

instead of archive and install you might first want to try restoring your system using TM to some time point before your failed 10.5.1 upgrade. Then try upgrading to 10.5.1 again. I would suggest downloading the full 110 MB upgrade and installing it manually rather than doing it through the software upgrade menu.
You can download the upgrade here:
http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1051update.html

Not booting anymore

dyld: Library not loaded: /usr/lib/libuncurses.5.4.dylib
Referenced from: /bin/sh
Reason: Image not found
I have two iMacs that I purchased off ebay, neither came with OS disc but have OS X 10.4.10 on them. The one had this error it went to the gray apple and then to a black screen with the error listed above.
The other one had no problems whatsoever. I can't reinstall the OS because he did not include the disc in the sale.
Any Ideas would be helpful.
null

Hi all.
I have a same problem.
In the details:
1. I download and install MacBook EFI Firmware Update.
2. I do all for instruction.
3. When mac is restarting i saw green lines on my desktop and black warning dialog(Restart your computer... bla-bla-bla)
4. When i restart mac again he is not booting. I saw black screen after gray with apple. It was written on the screen:
hfsswapHFSPlusBTInternalNode: unrecognized catalog record type(0x0000; record #13)
node=26912 fileID=4 volume=os device=root_device
hfsswapHFSPlusBTInternalNode: unrecognized catalog record type(0x0000; record #13)
node=26912 fileID=4 volume=os device=root_device
hfsswapHFSPlusBTInternalNode: unrecognized catalog record type(0x0000; record #13)
node=26912 fileID=4 volume=os device=root_device
dyld:Library not loaded: usr/lib/libcurses.54.dylib
referenced from: /bin/sh
reason:image not found
5. I try cmdopt+pr - dont help.
6. command+S - same stack trace.
7. I boot from MacOs DVD and run Disc Utility - after i click on "Repair Disc" this program write next:
Verify and repair disk "os"
Checking HFS Plus volume.
Checking Extents Overflow file.
Cheking catalog file.
Invalid key length
Volume check failed
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
8. I try Hardware Test from MacOS DVD - he is not found any problem.
9. In Safe Mode system dont boot too.
I find next way:
1. Reinstall a system. Minus - i dont have a backup.(( I dont wont "Erase and Install". Can i leave a folder "User" with all my documents and applications?
2. Boot from Firmware Restoration CD if a problem is in MacBook EFI Firmware Update. But i dont have other mac near to itself and i can't burn this program to disc. Can i do this on Windows?
Help me please. I'm very afflicted.
P.s. My Mac is MacBook 2.1
P.p.s Sorry for my bad english.
Message was edited by: travmik
Message was edited by: travmik

[SOLVED] Kernel will not boot after update to 3.1.5

Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
Last edited by bolshevik (2011-12-16 14:31:19)

bolshevik wrote:
Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
If you foolishly interrupted the initramfs creation after a kernel upgrade and didn't regenerate it manually, you earned this.
You'll need to find a live CD so you can chroot to your install and rerun mkinitcpio.

Mac Mini Server Hd disappeared. Will not boot anymore!

I have a Mac Mini Server about 3 years old running Leopard. I noticed that my server HD had disappeared and was not even showing in disk utilities. The 2nd HD which I had setup for backup was still there and presumably bootable. I checked with disk utlty and disk was not there. Finder was not showing it either So I rebooted hoping it would come back, but I got a message like this:
panic (cpu 0 caller 0x47f5ad): "Process 1 exec of /sbin/launchd failed, errno 85\n"@/SourceCache/xnu/xnu-1504.15.3/bsd/kern/kern_exex.c:3145
Debugger called: <panic>
(Then a backtrace)
BSD Proces name corresponding to current thread: init
Mac OS Version:
Not yet set
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3-1/RELEASE_I386
System model 6,1 (Mac-F2268EC8)
Now I cant boot into my system at all. This mac mini has no DVD. I do have other macs I can use and have all the original DVDs.
Any steps I can use to fix or recover from this error?
Thank you

Which Tiger Install DVD do you have...?
1. I think that, that model originally came with 10.4.10 and so you will need either the original 10.4.10 install disc or a later retail (Leopard or Snow Leopard) upgrade DVD.
2. In addition, a new (HDD, Hybrid Drive or SSD) must first be Partitioned GUID Partition Table and Formatted Mac OS Extended (Journaled) before OS X can be installed.

X220t does not boot anymore after a few times running, does not get past BIOS

I just bought a x220t and want to use it with Win8.1. I had before upgraded my x201t to win8 with no problem at all.
After a few succesfull runs in wich I do the patching it stops booting completely. I can't even push F8. It will only go to Bios in witch I have fidled a bit, but nothing works. I have tried a fesh install for three times. It does boot an USB DVD drive with the origiganal win 8.1 disk, but it can't fix my problems.
I have an I7 version whith Intel 160GB ssd. I did a lenovo check, all clear, I dit an Intel SSD check, all clear. Unfiortunatiely I have delated the restore partition. I am on the latest BIOS (1.39)
Sometimes I get in to the Lenovo boot menu, with no result. I want to rip out my hairs!
Any help?

Hi thomas1921,
Not an answer to your specific question, but I'm very surprised that a BIOS update would break DVD booting. Have you tried pressing F1 at boot to get to BIOS Setup and examining / changing the boot order? Or pressing F12 at boot to select the boot device? (Think the F12 feature must be enabled in BIOS Setup.)
Results of Your Ideal Business-Class Laptop survey, concluded 2009-07-29.
Did someone help you?
Say thanks! with a kudo.
Even better: Pay it forward, help someone else.

Upgraded kernel and cant boot now

So yesterday I upgraded udev and the kernel. Now when I boot arch cant activate swap and when it trys to run a FS check it fails. I read somthing on changing /dev/discs/disc0/part3 to /dev/hda3. How do I do this. I looked at Grub and it is set to /dev/hda3. After the FS check fails it let me into my filesystem but for Read Only. Can anyone help ?

sysboy wrote:I used vi to open /etc/fstab and does have the wrong lines for my partitions. But like I said I have read only privs when I get into my FS ( i am root btw )
that may well be because you haven't a matching entry for the root= append parameter to the kernel in fstab. that's why it only mounts you root-fs in ro. see if removing "ro" from the append parameters in menu.lst helps, if so, cat /proc/partitions to find out about your partition layout. then modify menu.lst and/or fstab according to that.
good luck!

Custom kernel does not boot.

Hi all, I recently changed to a laptop HP Pavilion G4, I installed Arch Linux and it works perfect, but I want to compile my own kernel to optimize the system a bit more.
I compiled a kernel in Gentoo sometimes, but I have no arch problems, I used the traditional method of compilation and all good, but I have a simple problem starting.
The kernel runs in "initramfs loading" and nothing happens, do not get errors or anything like that.
This is an image of what I have in /boot and /usr/lib/modules:
http://ompldr.org/vaDY0ZA/image.png
In case you wondered if you think the initramfs with mkinitcpio:
mkinitcpio -k 3.2.9-custom -g /boot/initramfs-compiled.img
And kernel config:
General setup --->
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
The grub I think I have it configured correctly, these are the lines of the default kernel and the kernel compiled.
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-5de5f584-af2b-47ff-84d6-c7adf842892f' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 5de5f584-af2b-47ff-84d6-c7adf842892f
else
search --no-floppy --fs-uuid --set=root 5de5f584-af2b-47ff-84d6-c7adf842892f
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=5de5f584-af2b-47ff-84d6-c7adf842892f ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux compiled' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-compiled-true-5de5f584-af2b-47ff-84d6-c7adf842892f' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 5de5f584-af2b-47ff-84d6-c7adf842892f
else
search --no-floppy --fs-uuid --set=root 5de5f584-af2b-47ff-84d6-c7adf842892f
fi
echo 'Loading Linux compiled ...'
linux /boot/vmlinuz-compiled root=UUID=5de5f584-af2b-47ff-84d6-c7adf842892f ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-compiled.img
I appreciate any help

But you are not going to achieve a faster boot by eliminating modules that are not going to be used/loaded anyway. I can see a faster boot being achieved if you were compiling in order to eliminate the need for an initramfs, but it seems taht you are still using one anyway (besides, there are advantages to having and initramfs). The modules you don't use will simply take up disk space, udev probes your hardware and only applies what you need.
Also if you think about the time you will save with your boot relative to the time it takes to configure and compile the kernel, it is not really worth it. Say you only take compilation into account and it takes five minutes. Then say that results in an amazing 2 second decrease in boot time. It would take 150 boots to make that compilation worth the time. Then with Arch's rolling release model, you will likely have a kernel update long before you ever get there.
I think a better idea might be to simply optimize what goes in your initramfs. Falconindy made this blog post (reluctantly it seems) about just that. I tried it before I started using device-mapper functions (which then require a bunch more stuff), and it actually made a noticeable difference. The beauty of this is that the configuration will stay consistent between kernel versions, and will automatically be built after every kernel update.
Edit: Also, you really should check out the CK kernel, as graysky has made it so damn easy its ridiculous. And it is pretty functionally amazing.
Last edited by WonderWoofy (2013-01-25 01:42:01)

Upgrade kernel beyond not booting anymore

Similar Messages

Maybe you are looking for