Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm new to Linux, other than windows.I've tried OpenSuze. Do to limited user knowledge on my part I opted to use Ubuntu after talking to other users of Ubuntu. Now out of 3 window OS's & 3 Linux distros I can only run Ubuntu live CD and install Ubuntu 9.1 (but not boot from).I was originality attempting a Dual boot with Vista but have aborted that cause.
Ubuntu hangs at a flashing courser after the system boots. I have not seen how Ubuntu boot manager is suppose to look like other than this blue screen and from the live CD.
I have installed, reinstalled using both default and user partitioning.
The disk utility and gpart both confirm the MBR is in the partition table. To take it a step futher I was able to down load a script from Sorceforge confirming the MBR is installed.I've also ran the Segate "Tools For Dos" being the drives are Seagate, it hangs at start up displaying an error code Invalid Opcode. This code also appears on the other drive I've attempted to try to use as boot drive.I now have two drive that I'm unable to boot an OS from the present 500G and 1TB (1TB presently is disconnected). Here is the boot "Inf Script Summary" of my present installation attempt. Just a thought, in viewing an other post a usb drive was going to be Zero written,using code,would this be a way for me to correct my issues from the live CD, if so I would need some coaching.
I've managed to generate good size bag of worms!
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.
#
# 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,1)
search --no-floppy --fs-uuid --set c5d396e2-783e-40ab-a3e3-a937f3445bed
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-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set c5d396e2-783e-40ab-a3e3-a937f3445bed
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=c5d396e2-783e-40ab-a3e3-a937f3445bed 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,1)
search --no-floppy --fs-uuid --set c5d396e2-783e-40ab-a3e3-a937f3445bed
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=c5d396e2-783e-40ab-a3e3-a937f3445bed 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 ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### 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 ###
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=c5d396e2-783e-40ab-a3e3-a937f3445bed / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=bd4a1480-dc6c-46e5-8cf9-201edfea4eba none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
=================== sda1: Location of files loaded by Grub: ===================
Well it appears the GRUB installation did not turn out that great. See if by using LILO it will boot otherwise attempt to reinstall GRUB. I had this problem and I just wiped Linux and did a fresh installation:C. I hope you dont need to format and re install good luck.
Firstly, many thanks for providing the right sort of useful information. (Unusual for a first-post).
So, a very warm welcome to LQ!
The 'buntu 9.10s offer an ext4 filesystem, which you have chosen for your boot partition on /dev/sda1. Understandable, as it was offered, but I'm staying with ext3 for now.
AFIK grub2 (Well, 1.97, if you are going to be picky) is the only bootloader that will boot an ext4 filesystem at the moment. That's why 9.10 uses grub2 which is particular, fussy and still buggy . lilo will not boot ext4
Looking at your grub.cfg I notice this insmod ext2
When I think it needs to say insmod ext4
You are not supposed to edit grub.cfg, but it's worth a try at this stage as it could
take us weeks to debug grub2 and meanwhile you cannot boot a nice OS. So...
Boot from a live 'buntu 9.10 CD
Open a terminal and
Mount your /root/boot partition somewhere:
Code:
# Make a mountpoint
sudo mkdir /x
# Then mount the partition at the mountpoint
sudo mount -t ext4 /dev/sda1 /x
# Make a backup of the original file
sudo cp /x/boot/grub/grub.cfg /x/boot/grub/grub.cfg.orig
# Make grub.cfg writeable (it isn't, it's a "developers know what they are doing" joke, I think)
sudo chmod +w /x/boot/grub/grub.cfg
# Edit the file with nano
sudo nano /x/boot/grub/grub.cfg
DownArrow to this bit
Code:
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,1)
change the ext2 to ext4
Change it for the "Recovery mode" entry as well, whilst you are at it.
Save the file (There's a menu to help you, but it's CTRL-O RETURN CTRL-X)
Unmount the root partition
Code:
cd
umount /x
Reboot.
Any better?
[No need to email me, I am auto-notified about further posts to this thread, and will respond when I am able.]
Tredegar
Viewed your reply,I've got some home work to do before moving on (New Waters)...don't need to be Wasting your time, also new work week at the salt mine... will be able to invest more time the up coming weekend.Looking forward to getting this resolved... it was getting close to a gravity check!
.. will be able to invest more time the up coming weekend.
Thanks for your follow-up post.
I completely understand.
You are not wasting anyone's time here. If you ask sensible questions, and provide
relevant information to help us to help you (and you have done this), you'll find you will receive
a lot of useful advice from LQ.
Please follow up with a post here with what you have tried, when you are ready and have the time, and we'll do our best to help you further.
Good new and Bad news. The Good, found the cause of the problem.... the hard drive is the issue, last weekend i purchased a new drive and on a whim installed Ubuntu on it with out a hitch. The bad, out a hard drive, and sound issues...attempting to research a solution. I have sound on the logtech usb head phones (works with skype,CD media and streaming off the internet).Here is the instaled sound card on an Asus P5Q-E mother board. I'm in route to the sound section. I still will do my home work so as to learn how to do the task you requested for the previous issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.