PDA

View Full Version : [all variants] Problems updating to some OS



Ronorlz
June 4th, 2010, 10:18 PM
Hi, I have tried to update to Lucid, but I have a problem with it, which also happened when I tried to install Debian Lenny and Fedora Goddard.

When I installed the OS, I did it step by step, I was careful on the partition step. But when the installation was "successful", I restarted the computer, it appeared the processor image (everything normal), a black screen appears, and it restarted. When I installed back any other OS, it says that there isn't any OS on the computer.

When I installed Fedora, it also came with some extra information, it said something about an invalid bridge.

Does anybody knows what I can do?:confused:
PS: Here's my computer hardware information:
http://lix.in/-7a0f7f

oldfred
June 4th, 2010, 10:25 PM
Welcome to the forum.

Lets see what is installed where.

Boot Info Script courtesy of forum member meierfra
Page with instructions and download:
http://bootinfoscript.sourceforge.net/
Be sure to highlight and use code tags (# in edit panel) to make it easier to read when you post the results.txt.

Ronorlz
June 4th, 2010, 10:32 PM
Ok, here it is :D


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.

sda1: __________________________________________________ _______________________

File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 8 Helena - Main
Edition
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disco /dev/sda: 203.9 GB, 203928109056 bytes
255 cabezas, 63 sectores/pista, 24792 cilindros, 398297088 sectores en total
Unidades = sectores de 1 * 512 = 512 bytes
Identificador de disco: 0x000a893d

Partition Boot Start End Size Id System

/dev/sda1 * 63 382,041,764 382,041,702 83 Linux
/dev/sda2 382,041,765 398,283,479 16,241,715 5 Extended
/dev/sda5 382,041,828 398,283,479 16,241,652 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/sda1 76d4b1bf-e813-4881-937d-25c3583918ca ext4
/dev/sda5 5552be7a-4fcd-4a5b-ba54-968766095fcf swap

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

/dev/sda1 / ext4 (rw,errors=remount-ro)


=========================== sda1/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,1)
search --no-floppy --fs-uuid --set 76d4b1bf-e813-4881-937d-25c3583918ca
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/06_mint_theme ###
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 76d4b1bf-e813-4881-937d-25c3583918ca
insmod png
if background_image /boot/grub/linuxmint.png ; then
set color_normal=white/black
set color_highlight=white/light-gray
else
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Linux Mint 8 Helena, linux 2.6.31-14-generic (/dev/sda1)" {
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 76d4b1bf-e813-4881-937d-25c3583918ca
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=76d4b1bf-e813-4881-937d-25c3583918ca ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Linux Mint 8 Helena, 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 76d4b1bf-e813-4881-937d-25c3583918ca
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=76d4b1bf-e813-4881-937d-25c3583918ca 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 ###

=============================== sda1/etc/fstab: ===============================

# /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=76d4b1bf-e813-4881-937d-25c3583918ca / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5552be7a-4fcd-4a5b-ba54-968766095fcf none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

=================== sda1: Location of files loaded by Grub: ===================


5.2GB: boot/grub/core.img
5.2GB: boot/grub/grub.cfg
.6GB: boot/initrd.img-2.6.31-14-generic
.6GB: boot/vmlinuz-2.6.31-14-generic
.6GB: initrd.img
.6GB: vmlinuz
I'm sorry if some important information is in spanish, but my OS is in spanish.

oldfred
June 4th, 2010, 11:02 PM
I see nothing in the boot script that looks out of place. Since you only have Ubuntu it will not show the menu grub.cfg unless you hold down the shift key from the end of BIOS boot until menu comes up.

If it is the video card issue:

I had to do this:
boot from the cd, press F6 and then select the nomodeset option.
then
On first boot after install, press e on getting the GRUB bootloader.
Using arrow keys navigate to and delete quiet and splash and type the word nomodeset in their place
Press Ctrl and X to boot (low graphics mode)

After I installed nvidia driver (default from pop up) then it has worked without issue.
gksudo nvidia-settings
Or it should be in System>administration>Hardware drivers.

Check BIOS for settings:
try to boot with acpi=off or nomodeset=0 on the boot line


if you've got an intel graphics card, then the usual fix is to either add i915.modeset=1 or i915.modeset=0 to your boot
Other workarounds:
https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes

ATI/Radeon
https://help.ubuntu.com/community/RadeonDriver

Lucid 10.04 KMS
https://wiki.ubuntu.com/X/KernelModeSetting
# Nvidia (this should revert you to using -nv or -vesa):
echo options nouveau modeset=0 > /etc/modprobe.d/nouveau-kms.conf

Ronorlz
June 4th, 2010, 11:14 PM
Well, right now I'm not on Ubuntu, I'm on Mint. Does that make any difference? I have an Nvidia card, but I'm not sure if its the graphics, cuz I can load the Live mode. Should I still do it?

oldfred
June 4th, 2010, 11:19 PM
Do not know, is not mint based on Ubuntu? I do not think it hurts as it is a one time boot change to add the nomodeset.

Ronorlz
June 4th, 2010, 11:52 PM
Ok, I have another question, where do I have to start? I pressed F6 on processor page, installation page, and on live mode, but nothing happened.

oldfred
June 5th, 2010, 04:57 AM
If it is installed you should hold down shift key until menu appears from BIOS boot.

Ronorlz
June 5th, 2010, 07:23 PM
If it is installed you should hold down shift key until menu appears from BIOS boot.

Then, do I install Lucid and then try this?

oldfred
June 5th, 2010, 08:22 PM
I was suggesting just trying the same instructions with mint since it is based on Ubuntu. It will not hurt anything.

If you want to install Ubuntu you can.

Ronorlz
June 5th, 2010, 11:52 PM
Well, I couldn't do it, I entered BIOS and didn't found anything:confused:

deadlockedgamer
June 5th, 2010, 11:58 PM
Well mint includes the proprietary drivers not sure but it may com pre installed. Could that be the issue? Course nvidia is usually good with linux. Try booting to live mode and using the installer on the desktop. Could also have someone check if your boot loader is in the wrong place.

Ronorlz
June 6th, 2010, 12:29 AM
Well mint includes the proprietary drivers not sure but it may com pre installed. Could that be the issue? Course nvidia is usually good with linux. Try booting to live mode and using the installer on the desktop. Could also have someone check if your boot loader is in the wrong place.

I think they come pre-installed. But I think you are trying to solve a problem which I don't have. My problem isn't Mint-related, it's Lucid-Lenny-Goddard related. I'm using Mint cuz I don't have the Karmic CD. My problem is when I install one of those 3 OS, my computer doesn't detect it, and it simply doesn't install.

Ronorlz
June 11th, 2010, 07:32 PM
May I bump? I'm sorry if I can't