Machine specifics: Win Vista with Ubuntu 10.04 installed via Wubi. Upgraded from 10.04 to 10.10 - killed Grub. Following other posts, I booted off a 10.04 Live CD and ran boot_info_script. The results are below. It's telling me core.img cannot be found - can someone please tell me what to do next (before I blunder on and make things worse!)
[Code]...
I used wubi to install the dual booting, after I have upgrade from 10.04 to 10.10 when I launch linux it goes direct to grup.
View 4 Replies View RelatedI upgraded to 10.04 but now i can't boot windows 7 from the grub. what can i do?
View 9 Replies View RelatedHad v9.x installed alongside Windows XP SP3 install. Have not used it that much since install.
Got the bug to upgrade to v10.
Went through the upgrade process, everything seemed fine.
At the end of the install process asked which dev to install GRUB onto - I selected only one drive, the wrong one of course, and the reboot failed.
Boots up with:
Have LiveCD running now to post. Ran Info_boot Script.sh - results below.
Will reinstalling v10 from Live CD fix this? Will this use Wubi or just go through normal install process? Or is there an easier fix to install GRUB on the correct drive to get the dual boot choice of Windows XP and Ubuntu back.
Naturally I need to get back to Windows ASAP - it's the net gateway and print server for my home/office setup.
Boot Info Summary:
I upgraded my dell inspiron 6000 from ubuntu 10.04 to 10.10 then rebooted and now I am stuck at the grub prompt. I am able to boot from a flash drive and have run the boot script. This laptop did not have a dual boot system on it but it did have windows on it at one time, converted to ubuntu.
View 9 Replies View RelatedThe Grub Windows XP selection only gets "Starting ..." and then, nothing. Ran boot info (ref. below)
Updated Grub:
$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.32-31-generic
Found kernel: /boot/vmlinuz-2.6.32-30-generic
Found kernel: /boot/vmlinuz-2.6.31-23-generic
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done .....
The upgrade finished, did a y to reboot and it boots to memtest, no sign of the grub screen at all.
View 2 Replies View RelatedInstalled Ubuntu 10.04 a week ago or so (using wubi.)Tried to upgrade to 10.10 from within Ubuntu using the update manager.Now the PC will only boot to grub rescue.When booting, this is what i get:error: no such device: cd200414-0606-4d7d-8c08-004e9b5dc92d.grub rescue>Three commands work: ls, set and insmod.The ls command only yields: (hd0)(no partitions like (hd0,1), (hd0,5), etc.)
View 4 Replies View RelatedI've been a Windows users since waaaay back when (ahh...Windows for Workgroups 3.1). I've tried Linux in the past (Mandrake many years ago), but didn't feel it was quite ready to be a Windows substitute for me.A couple of weeks ago, I downloaded the latest version of Ubuntu (10.04) and installed it in a dual boot setup with Windows XPSP3. All seemed to be running well, until it came time to install updates in the Update Manager. First an update for GRUB, which promptly killed GRUB and left me with "Minimal BASH-like line editing is supported" message and a GRUB prompt. After booting up the Windows XP install CD, I was able to rewrite the MBR and get back into Windows.
I deleted the Ubuntu installation and reinstalled it, making sure I didn't allow it to update GRUB after finishing up. The other updates listed installed fine and I was able to dual boot with ease.Another round of updates were listed yesterday when I booted up in Ubuntu, I made sure not to include the GRUB update, downloaded and installed them, rebooted and was faced with "Minimal BASH-like line editing is supported" again. Argh. Once again I had to pull out the Windows CD and run FIXMBR to resolve the boot problem.I'll admit to being tempted to just go back to Windows completely (while not perfect, atleast I can get it to boot after updates 99.9% of the time) and forget the idea of running Linux if I'm going to be faced with having to reinstall the OS everytime because something killed the boot loader.
I had just finished upgrading my system to 10.04 and it restarted my pc and now i can't boot my pc anymore All i have is this at the beginning
[Code]....
I'm at my wit's end with Windows this morning. I upgraded to Lucid a few days ago. Everything went very smoothly. Then I spent the greater part of Friday and Saturday "upgrading" to Windows 7 from Vista. I chose the "update" option which was only supposed to update to 7 rather than overwrite the entire HD. Now, GRUB doesn't load and I don't see my Linux partition. HOWEVER, it appears as though the partitions are still there! When I look in Winbloze at the HDs, it shows the Windoze HD as the partition size I made it when installing Ubuntu.
Any ideas on how to recover the awesomeness that is Ubuntu from this situation? Or do I need to install it fresh?
I am a linux noob and have been searching for a couple months to a fix for my problem but now I just need I have two hard drives. One with vista and the other with ubuntu, storage space, and some other partition. I was dual booting windows and ubuntu jaunty jackalope then one day I decided it would be fun to upgrade to 10.04 so I did. When I tried loading windows from grub it just showed a blinking cursor forever. And while attempting to fix the problem by adding windows to the grub menu.lst file it dissapeared from the grub options.
[Code]...
Just upgraded to 10.04.1 today and after I turn on the computer it goes to a screen asking for my username and password. Have tried to input my details but with no success.
I also tried pressing 'ALT-F7', but still no look, just takes me to a black screen with nothing.
I apologize for this being somewhat vague but it happened several months ago and I don't currently have access to the laptop. But here goes anyway:Perfectly working dual-boot system with XP and Ubuntu 8.04. I also think I had installed a different boot loader (or maybe just a GRUB editor?). This was several years ago. I upgraded Ubuntu to 10.04 and I remember it asking me if I wanted to overwrite probably menu.lst. I said no when I should have said yes and now XP still loads fine but neither version of Ubuntu will load at all. I wish I had access to the machine so I could say what the error message is, but I don't and I forget.So I expect that menu.lst is just pointing to the wrong place but I'm not sure how to fix it. Can I boot from a live CD and edit menu.lst? Just thought about that.No biggie but I cannot screw up the XP aspect since that's major drama.
View 2 Replies View RelatedI have an ancient laptop, an IBM T-20 with a Pentium 3 and 250 megs of RAM, which works great for blogging and email. I have used Ubuntu on it for nearly four years now. Last night I upgraded from 8.10 to 9.04 and now it won't get to the log-in screen. The BIOS splash screen appears, then the GRUB screen, then the Ubuntu trademark screen appears, with the horizontal progress indicator scrolling from left to right. And when it gets all the way to the right, the screen goes blank. Then the screen flashes twice, as if it's trying to display in a resolution it doesn't support, and then it goes blank again. The HD activity light flashes about every five seconds and the keyboard is unresponsive.
View 1 Replies View RelatedLong story short my roommate has been using KDE 4.4.2 for a few weeks and enjoying it, so I figured I would give it a shot when I saw this on the Kubuntu front page. I added ppa:kubuntu-ppa/backports to my software sources and asked kpackage kit to look for updates, it found a bunch, plus around 25 blocked updates. I figured they were blocked because they depended on some other update I was about to install. I told it to start updates and left it on its own for a while. About halfway through KDE crash handler popped up saying the network manager crashed, so I told it to restart, plugged into my wired connection, and continued updates. Once it finished, their were still 25 blocked updates to I figured a restart was in order. Once I restart I get to the log in screen, log in, and then I am prompted with this message by the KDE Crash Handler:
[Code]...
Have amd64 with 8.10 upgraded twice to 9.10 that hangs at "mountall:job failed to start, could not access PID files---ect,ect,starting timidity--alsa midi emulation" after installing ultimate 2.0 (8.10) as the secound OS. still will boot to ultimate 2.0, but booting to any version of original install results in above crash.Anyone know what is broken? Boot seems to start but then crashes at the above mentioned line.
View 4 Replies View Relatedfrom Ubuntu 8.04.2, kernel 2.6.24-24-lpia to Ubuntu 8.04.2, kernel 2.6.24-27-lpia Drivers Lost / Missing: Wireless via USB, Printer, Webcam, Sound, etc. No indication whatsoever there would be problems with the upgrade except for the changes in /boot/grub/menu.lst which I merged by hand to avoid problems.
Please advise:
A) What to do next?
B) Where in the Ubuntu bugs do I open this bug?
Ive just upgraded to 11.04 using the update manager and now ive no boot menu and when I restart I just get a message on my monitor that says "out of range"
Ive tried Shift+alt+f7, ctrl+alt+f1 and pressing shift on startup. Ive also followed the advice on a help thread on here to edit /etc/default/grub and comment out GRUB_HIDDEN_TIMEOUT=00 (except on mine there was only one '0' and it was already commented out!!) and now im completely stuck. Im running in the live CD environment at the moment
I had F15 installed in my hard drive, I liked it very much and everything was going great until I installed that damned XP in another partition (same HDD). Now here is the problem.
This XP does not let me choose the OS I wish to run at the boot-time and just boots itself. I am a beginner with Linux OS.
I'm completely new to Ubuntu and only installed yesterday for the first time. The install worked fine. After booting it asked me to install updates. I did this and now when I boot i get:
Gave up waiting for root device. Common Problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough)
- Check root= (did the system wait for the right device)
- Missing modules (cat /proc/modules: ls /dev)
ALERT! /dev/disk/by-uuid/blah blah does not exist. Dropping to a shell Now I've tried searching through the forums and I've seen people with similar problems however none of the solutions suggested to them have worked. The only thing that may work if it is explained to me how to do it is in Grub 2 it is looking for a UUID. Now I tried editing this on startup to /dev/sda5 instead and it loads. Only thing is I read that this is temporary and would have to do it each time which means it's a workaround not a solution. As I explained at the start, first time of using Ubuntu and so far haven't been particularly impressed as I have another problem with the processor being used up by loads of 'udevd
Root LUKS to be broken by apt-get update? This did happen to me on 3 different laptops, both on previous install (from Debian 8.0), and also on clean installs (Debian 8.1), repeatedly.
When I reboot, grub starts, but then it cannot find the root file system (I end up with the emergency console).
Code: Select allLoading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
Loading, please wait...
[many seconds waiting]
ALERT! /dev/mapper/sda2_crypt does not exists.
modprobe: modprobe ehci-orion not found in modules.dep
This is the most simple, clean, conservative install ever, no closed driver.
But LUKS on the root file system:
Code: Select allone ext4 partition on /boot
one ext4 partition on / (trough LUKS, all defaults)
There is no LVM.
All the 3 laptops killed at different time, when updating. Clean install is fine until the first update.
Booting on the rescue system allows me to see everything.
Code: Select all$ update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-3.16.0-4-amd64
Found initrd image: /boot/initrd.img-3.16.0-4-amd64
No volume groups found
How can I recover from this?
While doing some basic tweaks, nautilus, panel, display etc I got a pop-up: Additional Firmware Required "to make hardware in this computer function correctly". No more detail than that. Like signing a blank check so I said "go for it". When I rebooted the display was hosed. Like the refresh rate was wrong. So off to xorg.conf to fix it. There is no xorg.conf. After four hours of searching forums and google I gave up and reinstalled (only an hour). This time I made a backup (cp -a) before letting F12 fix the non-existent problem. Tried again very carefully to be sure that what killed the display was the additional firmware. True. That kills my display. Only problem is the backup cp -a when copied back in would boot but would not let me log in!? I could boot "single" change the password, but it said that was already the password.
for me F12 is a "one-day-distro". I have multiple partitions with Ubuntu, Mandriva, SuSE, Slitaz ... My first Linux was Fedora Core 4 and I will try the next Fedora release. For now back to Ubuntu 9.04. I'm still testing 9.10. My graphics is on-board Intel. I think it's 965G chipset. This is a Dell E520N. How would I tell what not to do that firmware addition?
I upgraded a week ago to ubuntu 10.10 (amd64). I was unable to boot in 2.6.35-22 so I have been using 2.6.32-25. I tried again last night after installing updates to 2.6.35-22. Still no luck.I gave up since this was much like what happened a week ago and I couldn't find any solutions then. (I ran memtest then.)
View 3 Replies View RelatedThe software manager has been nagging me to upgrade from 9.10 to 10.04 for some time now. I finally gave in and clicked on Upgrade. After the upgrade completed, my computer won't start. It just flashes Ubuntu for a split second and goes to a black screen. I happen to have the 10.04 CD from Canonical, and I tried that, and it won't launch the installer either; just a logo and a black screen. Since I can't even get to the terminal to diagnose and fix whatever's wrong, I'm installing 9.10 from the CD that I ordered from Canonical a long time ago. I went through all the graphical options just like the first time I installed 9.10, and it's in the process of installing right now.
I don't really have time to futz with it because I need my laptop for when I go and visit my mum for Thanksgiving. Maybe I'll try after the holidays if I can get some feedback on what might have gone wrong with 10.04.
I've looked in the grub.cfg file, and it has :
Code:
#
### BEGIN /etc/grub.d/30_os-prober ###
[code]....
I have a 10.04 installation upgraded from 9.10 somewhere around the first beta.However, since a couple weeks I have the problem that I cannot use nano anymore.
Code:
mypc:~$ nano
Segmentation fault
I've tried to do apt-get remove nano then installed but stil the same,Even tried apt-get purge but with no avail.
I upgraded 9.10 to 10.04 and now it won't boot. The way 9.10 used to boot was after turning on the computer it would go through the bios screen and then a screen would come up and list both operating systems, Windows Xp and Ubuntu. XP would be highlighted and would normally boot if I did not change the highlighted area. If I changed the highlighted area to Ubuntu it would boot into Ubuntu 9.10. Now after doing the upgrade, it gets to the same screen with the two operating systems listed.
When I change the highlighted to Ubuntu an error message is briefly displayed and then it goes back to the screen that lists both operating systems. I think the error message says something like couldn't find Ubuntu, or something similiar to that. Windows XP runs fine when I highlight Windows XP in that first screen, but I want to be able to run Ubuntu. I have Ubuntu on a secondary drive, but shouldn't it have rewritten the upgraded files on that same drive that had 9.10 on it?
I upgraded the Ubuntu 10.04, and afterwards I can't print. Cups won't detect printers, hp-setup won't, hp-probe won't. Tried rebooting, reinstalling HPLIP, & CUPS. Installed latest version of HPLIP. did a purge of HPLIP and CUPS, and reinstalled, rebooted.
View 4 Replies View RelatedI had upgraded to 10.04 but can not use kernel 2.6.32-22.32+, I had to go back to kernel 2.6.31-21. because of the default video driver had change from the one kernel to the other, and I do not know how the correct it. In 2.6.32-22 the font would change and to a smaller size and I can barely view anything because it looks like some two year old puke a box of crayons all over the screen.
Second issue is it does not matter what power-saving mode I am in, in 5 minutes time it with go into suspension. Or right after coming out of hibernate, it will go into suspension indefinitely and no coming out of it and must to a hard boot.