segmentation fault

Discussion in 'Installation/Configuration' started by hotchilli, Mar 30, 2006.

  1. hotchilli

    hotchilli New Member

    ust installed sarge on hda1 as per your how toand get error with segmentation fault
    (6) journal block device drive loaded

    pivot_root: no such file or directory
    /sbin/init: 432 cannot open dev/console no such file

    kernnel panic attempted to kill init


    hda1 sarge (ext3)

    hda2 swap

    had3 ubuntu (ext3)

    hda4 extentended

    hda5 swap
    ---------------------------------------------------------------hotchlli:confused:


    fist of all here is the disk layout

    Disk /dev/hda: 40.0 GB, 40007761920 bytes
    255 heads, 63 sectors/track, 4864 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 2690 21607393+ 83 Linux
    /dev/hda2 2691 2809 955867+ 82 Linux swap / Solaris
    /dev/hda3 2810 4776 15799927+ 83 Linux
    /dev/hda4 4777 4864 706860 5 Extended
    /dev/hda5 4777 4864 706828+ 82 Linux swap / Solaris


    There was a small fat partition of 2mb with the various files which came built into the labtop it was some files to aid the installation of XP home in my acer traelmate 2200 this was /dev/had1 on /dev/hda2 there was a xp home os fat32.
    Ubuntu on /dev/hda3 has been intalled from BB 5-10 CD about january 2005
    no probs with install.

    It was all controled by ubuntu grub but now sarge grub is installed can boot
    into ubuntu no problems below is menu.list for ubuntu and below that is menu .list for sarge.
    I can start the boot into sarge but stops at the point where I get the error message as posted
    in my fist post of this thread.

    #
    Lex1:
    --------------------------------------------------------------
    ubuntu menu list
    # menu.lst - See: grub(, info grub, update-grub()
    # grub-install(), grub-floppy(),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.

    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    default 0

    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 10

    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu

    # Pretty colours
    #color cyan/blue white/blue

    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret

    #
    # examples
    #
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    #
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    #

    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below

    ## DO NOT UNCOMMENT THEM, Just edit them to your needs

    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specifiv kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    # kopt=root=/dev/hda3 ro

    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,2)

    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true

    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false

    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery mode) single
    # altoptions=(recovery mode) single

    ## nonaltoption boot targets option
    ## This option controls options to pass to only the
    ## primary kernel menu item.
    ## You can have ONLY one nonaltoptions line
    # nonaltoptions=quiet splash

    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all

    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true

    ## ## End Default Options ##

    title Ubuntu, kernel 2.6.12-10-386
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda3 ro quiet splash
    initrd /boot/initrd.img-2.6.12-10-386
    savedefault
    boot

    title Ubuntu, kernel 2.6.12-10-386 (recovery mode)
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda3 ro single
    initrd /boot/initrd.img-2.6.12-10-386
    boot

    title Ubuntu, kernel 2.6.12-9-386
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda3 ro quiet splash
    initrd /boot/initrd.img-2.6.12-9-386
    savedefault
    boot

    title Ubuntu, kernel 2.6.12-9-386 (recovery mode)
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hda3 ro single
    initrd /boot/initrd.img-2.6.12-9-386
    boot

    title Ubuntu, memtest86+
    root (hd0,2)
    kernel /boot/memtest86+.bin
    boot

    ### END DEBIAN AUTOMAGIC KERNELS LIST

    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title Other operating systems:
    root


    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/hda2
    title Microsoft Windows XP Home Edition
    root (hd0,1)
    savedefault
    makeactive
    chainloader +1
    ---------------------------------------------------------------------------------

    the sarge grub print out is in segmentation fault part 2 as will not
    fit into one post

    hc
     
  2. falko

    falko Super Moderator

    I don't see a grub stanza for Debian - only for Ubuntu and XP?
     
  3. hotchilli

    hotchilli New Member

    Last edited: Mar 30, 2006
  4. hotchilli

    hotchilli New Member

    segmentation error

    I have done two large posts today one has the menu.lst from ubuntu the other
    segmentation post large post has the sarge menu.lst

    now in one of these I think I must put a line by hand something like


    title Debian GNU/Linux, kernel 2.4.27-2-386 (on /dev/hda0)
    xstation root (hd0,0)
    xstation kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda0 ro single
    xstation initrd /boot/initrd.img-2.4.27-2-386
    xstation savedefault xstation boot

    a) i am not sure if to place this line in the sarge or ubuntu menu.lst
    b) if it will solve the segmentation fault


    hc
    forgot to mention I did I invoked this command


    bliss1@xstation:~$ sudo update-grub && sudo grub-install /dev/hda
    Password:
    Searching for GRUB installation directory ... found: /boot/grub .
    Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
    Searching for splash image... none found, skipping...
    Found kernel: /boot/vmlinuz-2.6.12-10-386
    Found kernel: /boot/vmlinuz-2.6.12-9-386
    Found kernel: /boot/memtest86+.bin
    Updating /boot/grub/menu.lst ... done
     
    Last edited: Mar 30, 2006
  5. hotchilli

    hotchilli New Member

    segmentation error

    it has been suggested that I use sare unstable for labtop.
    is this a good idea?
     
    Last edited: Mar 30, 2006
  6. till

    till Super Moderator

    Instead of using DEBIAN unstable i would use Ubuntu. In my experience its more stable then DEBIAN unstable but contains support for new hardware.
     

Share This Page