Find the answer to your Linux question:
Results 1 to 4 of 4
Hello. I have recently installed Fedora Core 1. It has run great for me for the last few months, but that is when I was first introduced to linux so ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2004
    Location
    Raleigh NC USA
    Posts
    4

    Linux Boot Errors


    Hello. I have recently installed Fedora Core 1. It has run great for me for the last few months, but that is when I was first introduced to linux so I am still kind of a noob.

    Anyways, I tried to install the nvidia drivers for linux to my computer. They stated that they require multi-user mode (So the x display isnt' running) I edited my /etc/inittab file to mode three, and rebooted fine in to text mode. Then I went to install the drivers and they said they needed the kernal source code to re-compile it for the drivers. I did not know where to direct it yet, so when it asked if I wanted to quit or direct the driver installation to the surce kernal code, i quit.
    as far as i know I *thought* it had not done anything yet.

    So here is when it hit me. I go to restart and it gives me the following list of errors.

    INIT: version 2.85 booting
    INIT: /etc/inittab[8]: missing action field
    INIT: /etc/inittab[19]: missing action field
    INIT: /etc/inittab[22]: missing action field
    INIT: /etc/inittab[30]: missing action field
    INIT: /etc/inittab[33]: missing action field
    INIT: /etc/inittab[39]: missing action field
    INIT: /etc/inittab[42]: missing action field
    INIT: /etc/inittab[43]: missing action field
    INIT: /etc/inittab[51]: missing action field
    INIT: /etc/inittab[54]: missing action field
    INIT: /etc/inittab[55]: missing action field
    INIT: /etc/inittab[56]: missing action field
    "NIT: cannot execute "/etc/rc.d/rc.sysinit
    INIT: Entering runlevel: 1
    Entering non-interactive startup
    INIT: no more processes left in this runlevel

    So then I went into linux rescue mode off the cd and typed in chroot /mnt/sysimage to mount the system under root.

    I used vim to look at the /etc/inittab file to see if the driver installation had changed anything in it and it was still as it had been before. (the default inittab file)

    It gives the same error message for boot mode 3 and 5 (multiuser and graphical)

    What else is it looking for if the inittab file is still the same? is it looking for something new in the inittab file?

    if you want to look at my current *default* inittab file it is HERE

    Thanks for any help,
    Ben

  2. #2
    Linux Engineer Nerderello's Avatar
    Join Date
    Apr 2003
    Location
    North East England
    Posts
    1,190
    I'll have a look at my own Fedora core 1 initab when I get home this evening.

    For future reference. To get the nvidia modules (so that you can have nvidia instead of nv in your xf86config) you need either to have a kernel that the *.run script knows about or you need to have the source code of the kernel that you are running (so that the script can compile using bits of it). To run in mode 3, all you need to do is
    Code:
    telinit 3
    and to run back in graphical mode 5 all you do is
    Code:
    telinit 5
    see you later
    Nerderello

    Use Suse 10.1 and occasionally play with Kubuntu
    Also have Windows 98SE and BeOS

  3. #3
    Linux Engineer Nerderello's Avatar
    Join Date
    Apr 2003
    Location
    North East England
    Posts
    1,190
    here's the source from my working Fedora Core 1 /etc/initab :-
    Code:
    #
    # inittab       This file describes how the INIT process should set up
    #               the system in a certain run-level.
    #
    # Author&#58;       Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
    #               Modified for RHS Linux by Marc Ewing and Donnie Barnes
    #
    
    # Default runlevel. The runlevels used by RHS are&#58;
    #   0 - halt &#40;Do NOT set initdefault to this&#41;
    #   1 - Single user mode
    #   2 - Multiuser, without NFS &#40;The same as 3, if you do not have networking&#41;
    #   3 - Full multiuser mode
    #   4 - unused
    #   5 - X11
    #   6 - reboot &#40;Do NOT set initdefault to this&#41;
    # 
    id&#58;5&#58;initdefault&#58;
    
    # System initialization.
    si&#58;&#58;sysinit&#58;/etc/rc.d/rc.sysinit
    
    l0&#58;0&#58;wait&#58;/etc/rc.d/rc 0
    l1&#58;1&#58;wait&#58;/etc/rc.d/rc 1
    l2&#58;2&#58;wait&#58;/etc/rc.d/rc 2
    l3&#58;3&#58;wait&#58;/etc/rc.d/rc 3
    l4&#58;4&#58;wait&#58;/etc/rc.d/rc 4
    l5&#58;5&#58;wait&#58;/etc/rc.d/rc 5
    l6&#58;6&#58;wait&#58;/etc/rc.d/rc 6
    
    # Trap CTRL-ALT-DELETE
    ca&#58;&#58;ctrlaltdel&#58;/sbin/shutdown -t3 -r now
    
    # When our UPS tells us power has failed, assume we have a few minutes
    # of power left.  Schedule a shutdown for 2 minutes from now.
    # This does, of course, assume you have powerd installed and your
    # UPS connected and working correctly.  
    pf&#58;&#58;powerfail&#58;/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
    
    # If power was restored before the shutdown kicked in, cancel it.
    pr&#58;12345&#58;powerokwait&#58;/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
    
    
    # Run gettys in standard runlevels
    1&#58;2345&#58;respawn&#58;/sbin/mingetty tty1
    2&#58;2345&#58;respawn&#58;/sbin/mingetty tty2
    3&#58;2345&#58;respawn&#58;/sbin/mingetty tty3
    4&#58;2345&#58;respawn&#58;/sbin/mingetty tty4
    5&#58;2345&#58;respawn&#58;/sbin/mingetty tty5
    6&#58;2345&#58;respawn&#58;/sbin/mingetty tty6
    
    # Run xdm in runlevel 5
    x&#58;5&#58;respawn&#58;/etc/X11/prefdm -nodaemon
    which, apart from the "5" on the id line, doesn't look to different from yours.

    Can you confirm that there are no "wierd" characters in your initab file.

    Nerderello

    Use Suse 10.1 and occasionally play with Kubuntu
    Also have Windows 98SE and BeOS

  4. #4
    Linux Engineer Nerderello's Avatar
    Join Date
    Apr 2003
    Location
    North East England
    Posts
    1,190
    your PC doesn't seem to like the lines that are blank (for instance lines 8 and 19).

    So try deleting those lines and see what happens.

    Nerderello

    Use Suse 10.1 and occasionally play with Kubuntu
    Also have Windows 98SE and BeOS

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •