PDA

View Full Version : [ubuntu] boot error: /scripts/init-top/brltty 19 : grep not found



$p00ky
December 14th, 2009, 03:39 AM
Dear community,

I have a booting problem with the latest 2.6.31 kernels (2.6.31-16-generic and 2.6.31-17-generic).
It won't boot due to the following error: "/scripts/init-top/brltty 19 : grep not found".

I'm using Ubuntu 9.10 x64.
The system works fine if I boot on the 2.6.31-15-generic kernel.
grep can be found in /bin/grep under this kernel

I tried to delay the boot adding "rootdelay=90", but it didn't solve the problem.
The "recovery mode" of kernels 31-16 and 31-17 do not work neither.

Do you have any suggestions to fix the problem?




/usr/share/initramfs-tools/scripts/init-top/brltty

#! /bin/sh
set -e

PREREQ="framebuffer console_setup"

prereqs () {
echo "$PREREQ"
}

case $1 in
prereqs)
prereqs
exit 0
;;
esac

if grep -q braille=ask /proc/cmdline; then
brltty-setup || true
fi

exit 0
/boot/grub/grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
saved_entry=${prev_saved_entry}
save_env saved_entry
prev_saved_entry=
save_env prev_saved_entry
fi
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/white
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-17-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro quiet splash
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-17-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-17-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro single
initrd /boot/initrd.img-2.6.31-17-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-16-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro quiet splash
initrd /boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-16-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-16-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro single
initrd /boot/initrd.img-2.6.31-16-generic
}
menuentry "Ubuntu, Linux 2.6.31-15-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-15-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro quiet splash
initrd /boot/initrd.img-2.6.31-15-generic
}
menuentry "Ubuntu, Linux 2.6.31-15-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-15-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro single
initrd /boot/initrd.img-2.6.31-15-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 2682d42f-7e1b-4f38-b08d-075d4875a92c
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=2682d42f-7e1b-4f38-b08d-075d4875a92c ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set f0b0148fb0145f02
chainloader +1
}
### 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 ###

$p00ky
December 15th, 2009, 12:14 AM
Nobody?

I also wonder if it's risky to upgrade the distrib to the beta 10.04 as I have this problem with the new kernels or if it may solve the problem.

$p00ky
December 16th, 2009, 02:48 AM
It seems to be an old problem, which already occured in old ubuntu distributions, even though I did not find any solution (they all ended up formatting the hd...).

As my old kernel is still working fine, I think I can fix it without formatting, right?

Help please!

$p00ky
December 17th, 2009, 12:34 PM
I still can't boot on the kernels 16/17... help plz!

Cisco9
December 18th, 2009, 07:59 PM
I noticed that you have 31-14 in your menu. Doe IT work? It works for me. I am having a similar problem. I was told that it might be that the initramfs needs to be updated. I tried that with now success. I am stuck at 31-15.

--Cisco

$p00ky
December 20th, 2009, 08:02 AM
I noticed that you have 31-14 in your menu. Doe IT work? It works for me. I am having a similar problem. I was told that it might be that the initramfs needs to be updated. I tried that with now success. I am stuck at 31-15.

--Cisco

I guess 31-14 is working fine as it was working well before I switch to 31-15.
31-14 and 31-15 are working fine. 31-16 and 31-17 don't work.

Help plz!

$p00ky
December 22nd, 2009, 03:06 PM
help plz

$p00ky
December 26th, 2009, 08:57 PM
Still same problem here... does anyone has a clue?

$p00ky
December 28th, 2009, 03:43 PM
I cannot boot on kernels 31-16 or 31-17 for weeks... Nobody has a clue???

$p00ky
January 1st, 2010, 05:23 PM
Happy new year everybody!
My new year's wish: boot on my kernels 31-16 and 31-17!

Anyone to help me accomplish my wish? :P

opto09
January 22nd, 2010, 01:49 PM
Sorry this won't help you but I have exactly the same problem. Could I just ask how did you do the upgrade? Also did you experience problems upgrading a kernel? For instance mine often gave me 'invalid location' errors and had problems locating UUID codes.

opto09
January 26th, 2010, 03:21 AM
Well I guess the solution is simple: reinstall ubuntu. Using Karmic I've solved this problem for myself. Sorry if this doesn't help you $pooky.

As a side note I will add that if this has taught me a lesson it's that it may be worth creating a /home partition. That way Ubuntu can be reinstalled without affecting the data.