System won't boot. INIT: No inittab file found Enter runlevel:

After the latest update that changed how intel ucode is updated, my system won't boot.
I think I missed a line when I edited "/etc/grub.d/10_linux" and ran grub-mkconfig -o /boot/grub/grub.cfg.
Any ideas on how to fix this?
I can't run grub-mkconfig from another machine, as it uses the live kernel info.
Any help would be greatly appreciated. Otherwise I'll have to reinstall

TheSaint wrote:
SyXbiT wrote:
But I still get the error:
system won't boot. INIT: No inittab file found
Enter runlevel:
It seems to me that you've an old Arch version. inittab is deprecated AFAIK.
What is the Arch iso version?
That would probably be mid-2012 at the very latest I think as that's when I remember completely moving over to systemd...
@SyXbiT: Are you using the current Arch install ISO?

Similar Messages

Can't boot after system update - INIT: No inittab file found

Hi i've a pc where i installed arch linux more than one year ago
Its a:
PentiumII 400mhz
192mb ram
2 harddrives (don't know if i use them as a lvm or if each consists of 2 partitions used as mountpoints)
graphic card nvidia TNT2
i wanted to update it using "pacman -Syu" but it didnt worked because TNT2 needed nvidia legacy treiber 71xx don't work with kernel > 2.6.26
so i removed currently used nvidia treiber with pacman and installed the xf86-nv driver using pacman...
after that i think i updated just the kernel (pacman -S kernel26)
and than the system (pacman -Syu)
that was successfully....but after my reboot the shock
INIT: No inittab file found
Enter runlevel:
doesnt matter what runlevel i try i can't get further
what should i do now? please help me and provide me something like a step by step guide

menhir wrote:
what kind of live cd should i use?
is there a arch live cd that has the initscripts package include that i don't require to have my wlan working?
where can i find a good tutorial for "chroot" rescue in my case?
Just use the Arch installation disc

[SOLVED] boot failure: No inittab file found

Hi,
While trying to upgrade my system according to the recent /usr/bin intervention, I managed to get into an unbootable state:
INIT: No inittab file found
Enter runlevel:
This is because, stupidly, I'd simply removed initscripts. (I thought I'd properly completed the systemd and all previous migrations, considering my system up to date, and figured initscripts was an obsolete remnant.)
pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
returned
grub 0.97-21
grub 0.97-21
consolekit 0.4.6-4
initscripts 2012.10.1-1
So I (again, stupidly) removed consolekit and initscripts and upgraded GRUB (by installing grub-bios and following the guide). I then proceeded to upgrade as described in the intervention notice.
This, of course, resulted in the following error on rebooting:
INIT: No inittab file found
Enter runlevel:
I've since spent hours trying to repair the system with a live system (booting arch off a thumb drive) and arch-chroot - but
I don't know what I should install to make things work again
I haven't managed to figure out how to install packages while offline (despite reading through the guide)
Any assistance would be immensely appreciated!
Last edited by FND (2013-06-09 17:23:15)

Thanks for the quick response!
Frankly, I'm not quite sure what to make of that link (thus revealing my general ignorance... ).
Here's my /etc/boot/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_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
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=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch 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-ad4103fa-d940-47ca-8506-301d8071d467' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
else
search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/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 ###
### 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 ###

[SOLVED] Switch to systemd - Now system won't boot

I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the
init=/bin/systemd
line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?
Last edited by fettouhi (2013-12-08 14:42:04)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

Btrfs: System won't boot anymore after unclean shutdown

Hi,
I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
I have my root partition as BTRFS and no /boot partition.
After an unclean shutdown the system won't boot anymore.
GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
Then, I have to start a Live CD and do:
btrfsck /dev/sda3
After that the system boots correctly.
I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
What can I do?
Thanks

I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
[...] INFO: task mount:612 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
Output of btrfs-check:
Checking filesystem on /dev/pixie/btrfs
UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
found 76855677062 bytes used err is 1
total csum bytes: 72928436
total tree bytes: 2092515328
total fs tree bytes: 1888452608
total extent tree bytes: 104644608
btree space waste bytes: 357251032
file data blocks allocated: 181197139968
referenced 109440282624
btrfs-progs v3.19
dmesg output:
[ 36.824998] Btrfs loaded
[ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
[ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
[ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
[ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
[ 240.335542] Not tainted 3.19.2-1-ARCH #1
[ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
[ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
[ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
[ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
[ 240.340298] Call Trace:
[ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
[ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
[ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
[ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
[ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
[ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
[ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
[ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
[ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
[ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
[ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
[ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
[ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
[ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
[ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
[ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
[ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
[ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
[ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
[ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
[ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
[ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
[ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
[ 240.342927] Not tainted 3.19.2-1-ARCH #1
[ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
[ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
[ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
[ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
[ 240.348501] Call Trace:
[ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
[ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
[ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
[ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
[ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
[ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
[ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
[ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
[ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
[ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
Last edited by ouroboros8 (2015-04-02 12:37:25)

System won't boot-no chime.

Despite repeated attempts and resetting the CUDA button, the system won't boot when start button is pressed. In the first few seconds it seems to make normal sounds; but no chime and settles into simply fan noise. This is true even if using C (with an Install CD). or Shift key. Is there anything else I can try? (I know it's actually a G3 B&W Motherboard; but I had nowhwere else to post it)

I do not remember exactly what was happening when it stopped. It may have been executing something , hung up, and wouldn't respond to the Command-Opt-Esc or I do remember one incident when it was booting up and stopped when it was partly thru "searching for local discs.
I checked the ref. article and tried to measure the voltages on the power connector. I was never quite sure what pin was what, since the colors did not jive with those in the article. At any rate 2 were approx. + 5 V (one was 4.85), the rest were essentially zero (I believe 1 or 2 were about 300 mv). I did notice that when the power connector is reconnected and start up is attempted, 3 little green lights come on on the motherboard. One goes off after a while.
I have tried the old Sonnet upgrade and have tried reseating all the RAM modules. All to no avail.
The Hard drive and all other parts seemed to be working fine prior to the failure.

System won't boot up

Help please. I have a kt6 delta running an athlon 2700+ xp chip, 512 mb ddr 400.
When I set the fsb at the correct speed for the chip (166) the system won't boot hard drive led lights up constant. dvd drive and cd-r drive each run but the system won't boot. system seems to run fine at default and 133 mhz but the chip is incorrectly identified in windows (xp pro sp1) Any Ideas whats wrong?

Hi - I have the same board with the same processor, I have not problems rebooting after changing the bus speed. But I have had problems rebooting after adding in any card PCI or AGP. the system seems to have trouble clearing the Cmos, I would try clearing the CMOS with the JBAT. it doesn’t always seem to work but I have had some luck, though I have also pulled out the battery a couple of time too..
Good luck!

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Clean install OS.10.6.8 update it completly. May be you ignored some firmware update.
I have two incedents.
My thunderbolt port stopped working after upgrading to ML 10.8. I booted from external 10.6 , 10.7 still didnt work. Then i clean installed 10.6.8 and ran software update it updated the thunderbolt firmware and all is well now. This firmware update for some reason didnt show up in ML 10.8.
Secondly , when i upgraded my Brother's Macbook from 10.5 to 10.6.3 it would install but stuck with crossed out circle. Then i downgraded checked for update found an efi update , then the 10.6.3 worked fine.

Desperate, won't boot. Screen shows file folder with question mark??

I'm out of applecare warranty. My PB G4 won't boot. All I get is a gray screen with a small file folder in the center that has a question mark alternating with a little smiling face. Does this mean that my hard drive is fried and the system can't find my OS X software to boot from?
Is there anything that I can do to remedy this? I'm desperate. This post is being performed with a Dell using Windows

If the drive appears in Disk Utility then it isn't dead. That you cannot repair it nor install the OS suggests that there's serious damage to the directory if not the partition table. If you haven't backed up recently and have data you really don't want to lose, it might be worth getting DiskWarrior to attempt repairing the drive or retrieving some data. No guarantees.
Whether you do try that or not, eventually it's back to rebooting with the CD and returning to Disk Utility. Click on the erase tab. Do you have that option? If not, click on the partition tab and select 1 partition scheme and try that. If you can erase or partition the drive you will, of course, have erased everything.
If you succeed only time will tell if the drive went south because of a hardware issue or software. So, were I you, I'd become very careful about frequently backing up the important info on your computer.

System won't boot. Could really use some help here.

I have the K8T-Neo FISR2 mobo. When I set up the system, the SATA drive was set up as drive F: (onto which I installed Windows XP Home). I added a 2nd SATA drive later, and it became C:. Both drives are plugged into the Promise SATA ports. The system has been running fine for about a year now.
I was having a problem with a program not running properly. I stopped the process and tried to restart it, but it didn't work. It was a program that drives my Logitech gaming keyboard (with LCD screen). After I rebooted, the system would load windows, then after Windows was loaded, it would load up a program when I went into it and crash. It looked like it would crash on PXHELP.DLL (something like that). I booted up into safe mode, renamed the file so it wouldn't load, and now it won't boot at all. It starts to show the Windows logo and then instantly reboots. I can't even get into Safe Mode as it does the same thing.
I tried booting from an XP CD to do a repair, but when it boots, it doesn't see the hard drives. I downloaded the Promise drivers, put them onto a floppy, and load them as Windows is booting from the CD. It seems to load the drivers, but when I choose to do a repair (or even a new install), Windows comes back and tells me that I have no hard drives attached to the computer. I just can't seem to get Windows to see those hard drives!
I could really use some advice here......

Quote from: Tiresmoke on 04-January-06, 01:36:35
Try swapping the Drive Cables. You may have one that is not engaging as well as it should.
When I let the PC boot up like normal (without booting from the CD), it sees the drives and Windows tries to load, so I don't think it's the cables. I'll make sure they're reset, but I really don't think that's it.

System won't boot after update

After installing the latest system update (from Leopard 10.5.1 to 10.5.2) on my Dual Processor PowerMac G5, I was able to restart then within 2 minutes a freeze. I couldn't force quit...had to power done.
Upon powering on, my screen hangs on the gray screen for about a minute (with the clockwise powering up status symbol), then it shuts down on its own. It won't boot into safe mode. In single user mode, it tells me there is a "disk0s2: I/O error" ... Is my hard drive dead? I've tried resetting the PRAM, resetting the PMU button, unplugging all 3rd party devices, but to no avail.
I'm hopeful I can recover files somehow. Where should I proceed? I'm not sure exactly how the internal drives work. Can I, for instance, unplug and remove the top internal drive and place the 2nd internal drive where the top one was and see if i can boot from that drive?? Thereby determining which drive has the issue? Any advice is appreciated.
Thanks so much!
Sean

Can you boot off the leopard DVD and run the disk utility disk verification on the drive? If it's a hardware problem then there's probably not much you can do. If you have a TM backup of your system then you should be ok, since you can replace the drive and then restore your system to it from the TM backup.

[SOLVED] System won't boot (boots fine in fallback mode)

HI guys,
I just rebooted my headless server for the first time in a while, but it won't boot up.
I just sits at this screen:
Please note the system does boot using fallback mode.
(also, nothing to do with the latest boot problem - systemd-sysvcompat is installed and boots fine in fallback)
Last edited by kaipee (2013-05-18 21:23:13)

That screen shot looks like its booted to me? I see a login prompt

System won't boot with incorrect date/time

Hey, I setup a computer back home for VNC, however there was a power outage and now the BIOS has reset. Unfortunately it defaults the date to 2099 for some reason, anyway now the computer won't boot (I can't remember the exact error). Anyway the trouble is I can't access that computer now, and it has no monitor hooked up, is there anyway I can force a boot with just keyboard and without setting the correct date in the BIOS (no one with access to the computer could do this).
Appreciate any help.

You can try to just press F1.
I have a similar issue with my home server, the battery on the motherboard is dead so when the pc is powered off for a while it will not remember the clock. When trying to boot the system in such a case it spits out an error where it offers to "ignore" the error if you press F1.
In my case I need to wait until my pc beeps before pressing F1, basically you need to get past the BIOS stage.
With a bit of luck it might work for you too.
Also I hope you have some ntp service running on your system to make sure the date gets set correctly on your system on bootup.
Last edited by Neburski (2014-02-19 12:35:00)

System won't boot after increased FSB to 166

I have a K7n2 board with AMD 2100+. The system was working fine until, i increased the FSB to 166. Now when i turn on the system, no beep sound and no video at all. There are power to all of the orther components. I cleared the cmos, nothing happen when i powered up. I have another system, with ECS and AMD 1800+. I swapped the CPU between the two systems. Placing the 1800+ in the K7n2, the system boot up fine. But, the board recogninzing the CPU as AMD(tm) Athlon XP 1924 mhz. It is supposed to be only 1.53 mhz. The system run fine. When placing the 2100+ back in, it won't boot.
When placing the 2100+ in the ECS board the computer boot up fine also. I eliminated the CPU problems.
Thanks for any help.

I got it to work now. I reset the safe mode(100 mhz), rebooted, go to the BIOS set to default, and reset the jumper to user mode (default 133). It work fine now.
Ignore the question, thanks.

System won't boot after switching to higher performance

I recently installed snow leopard on my 2009 MacBook Pro. Things have going going very smoothly so far. However, I have had one setback. When switching to a different energy saver mode (either from higher performance to energy saver or vice versa), the computer won't boot back up. It will sit at the blue screen with the spinning wheel. Sometimes the wheel will freeze and the dock and my desktop will show up, but the computer is frozen. This forces me to do a manual shut down. This happens about every other time I try to boot my system into a different energy saver mode. Anybody else have a problem with this?

Hi DPer & welcome to the forums...
Try resetting some of the hardware involved (PRAM~NVRAM). See this Apple KB for details, etc.:
http://support.apple.com/kb/HT1379
Can't hurt to try, and apparently this has helped others recently.
If still no joy, did you update via Software Update or did you download the combo? If you used Software Update, get the Combo updater instead and re-apply:
http://support.apple.com/kb/DL959

System won't boot. INIT: No inittab file found Enter runlevel:

Similar Messages

Maybe you are looking for