Ubuntu :: Boot Your Own System Using Latest Its Kernel And Grub Form Cd / Usb?
Aug 17, 2010I want to know how to use a grub with a compiled kernel...and perform the boot of the system using a Cd-ROM for this purpose.
View 9 RepliesI want to know how to use a grub with a compiled kernel...and perform the boot of the system using a Cd-ROM for this purpose.
View 9 RepliesI'm running Hardy 8.04 LTS 64bit. The Update Manager updated the kernel and then asked if I wanted to use the local version of the grub menu. The boot menu was getting so long I edited it to shorten it. Other options were also offered, like the builder's version, but I chose the local version and since then the new kernel doesn't show up in the boot menu. Sudo update-grub doesn't restore it to the menu.
How do I undo the local version of the boot menu so I can see the newest kernel?
Ubuntu 10.10 latest kernel 2.6.35-28.49 update is broken. update just stalls when it gets to this.Quote:
Sub-process /usr/bin/dpkg returned an error code (1)...generating grub.cfg I have tried the following to no avail..Quote: sudo apt-get install -f sudo dpkg --configure -a sudo apt-get update && sudo apt-get upgrade
I have not changed any hardware.
I can't access my grub menu (by pressing space bar on boot) to select a kernel to boot from, and I need to boot into 2.6.31 to fix an intel chip issue. How can I replace the current 2.6.32x kernel with 2.6.31, so it is the ONLY option grub can boot up with?
View 9 Replies View RelatedI'm running Ubuntu 9.04 side-by-side with Windows XP.
Today, all of a sudden my system kept freezing up, forcing me to manually power-down my computer. Well, I tried picking an earlier kernel to boot from and, sure enough, there was no longer a problem.
Where's the recovery console in 10.04? Apparently there's no Grub so holding escape to get to a boot menu to boot into a shell isn't an option for me it seems.
I just want a shell so I can remove lm-sensors or whatever package I installed that's made my system unboobatble.
My computer boots a lot slower after the last kernel update. It boots fine to the log in screen, but after I log in it is slow.
New kernel: 2.6.35-24-generic
I am running the 64-bit version of Fedora 12 on an MacBookPro5,1 Intel Core 2 Duo with 4 Gigabytes or RAM.
I updated my system to use kernel 2.6.32.16-141.fc12.x86_64. Now when I try to boot the machine to that kernel, I'm left with a blank screen except for a blinking underscore cursor in the upper left corner after going through the load progress bar animation that appears at the bottom of the scene when Fedora is booting up.
I have my system configured to use the nVidia drivers for OpenGL 3D acceleration
I have to boot to previous kernel to have a usable system.
What can I do so that the system will boot up properly with the latest kernel?
Dual Boot: Fedora 12 and XP Dell 505I've had trouble with the latest kernel update.I updated a bunch of packages recently (including Xorg and kernel), and noticed a severe flickering after the update on my center monitor (Samsung T260 - the laptop display did not exhibit the flickering behavior). I backed out all the changes and started updating package by package. After I updated the kernel (again) I rebooted and here's where the fun part is -
I no longer get anything, except the cursor. No grub menu, no grub prompt. I rebooted and ran the rescue disk and followed the procedurery and point grub at the right boot partition - see here. However (obviously or I wouldn't be posting) that failed to work. I still get a blinking cursor and dead system on boot up.
I have installed ubuntu 10.04 64 bit in April and it has worked flawlessly. However, today I ws prompted to install Kernel updates. Now when I try to boot it continually cycles between a black screen and the NVIDIA logo.
Yes I have been using the nvidia drivers previously but without incident till now.
I have tried crtl-alt-f1 but this does not stop the cycling.
I have fedora versions
2.6.30.5-43.fc11.x68_64
2.6.29.6-217.2
2.6.29.4-167
loaded on my system. Version 2.6.30.5-43 hangs after the progress bar completes with messges labeled r8169 about the ehternet link status. Version 2.6.29.6-2317.2 boots just fine. How do I remove version 2.6.30.5-43 from the system?
Debian squeeze (weekly build) with latest kernel "2.6.32-5-686"
installed the latest updates, but latest updates to "Grub pc" crashed my system... it stops before login-screen. Unfortunately i can see any error messages, the screen stays black...
i have to re-install i guess...
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code:
grub
root (hd0,3)
setup (hd0)
quit
reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code:
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 263 13316 104856255 83 Linux
/dev/sda3 * 13317 14621 10482412+ 83 Linux
After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
I've installed Ubuntu on my new desktop alongside Windows 7 (each OS is on a separate drive), I seem to have run into a small problem. Let me start with what I did:
- Unplugged 1TB drive from the PSU, BIOS was not seeing my formatted (and thus empty) 500GB drive and I couldn't put it into the boot order at all with the 1TB turned on.
- Loaded up the boot CD and was able to install Ubuntu 10.1 on my 500GB drive.
- Did a bit of configuring, shut my PC off and plugged my 1TB (with Windows 7) drive back in. I tried to see if I could now see my Ubuntu drive in BIOS but nothing is there - just the Windows drive is in the list of available drives to boot from (along with DVD-ROM and USB).
This is where I've run into my problem. What I want is to have a nice GRUB boot menu at the start like any other dual-boot system but just have the two operating systems on separate drives altogether.I did it this way because I was having issues with the advanced partition menu on the boot CD so just went ahead and followed the KISS method by unplugging the Windows drive.
I was told by a friend that if I put my Ubuntu drive into the first position in my boot order and the Windows drive in the second, then I could boot into Ubuntu and run a GRUB update command (he told me to google it) and that would create the necessary GRUB that had the entries for Windows 7 and Ubuntu.Both operating systems are 64-bit, I imagine that might make a difference in whatever help you guys can offer me. I love the hell out of both OS's and want to be able to use them interchangeably.
I installed Fedora 13 on a separate partition and it deleted all of my openSUSE entries in grub. Or the boot menu, whichever is correct. From another thread, I found these commands and tried it:
Code:
grub
root (hd0,3)
setup (hd0)
quit
reboot
hd0,3 contained one of my openSUSE installs. Everything went well and grub accepted all of these commands except quit. So I used esc and rebooted. The reboot brought up the grub shell again. I could find no way to boot anything. Then I used the 'repair installation' option from the 11.2 dvd and installed a new boot loader for /dev/sda2 which contains 11.2.
This was successful, so I went to the YaST bootloader tool and added /dev/sda3 (Milestone 5) and /dev/sda4 (Fedora) and rebooted. But these two partitions still boot into grub instead of loading the correct kernel.
I'm currently on a work trip with my Asus G72GX laptop for non-work use (I'm posting from my work laptop). Yesterday, I accidentally booted into my laptop's recovery partition (from the Grub2 bootloader). Before I realized that that's what was happening, it booted into some kind of recovery program which ended up in an error. I restarted the laptop and couldn't get into the bootloader anymore. Now, the only thing that comes up is an error -- "error: unknown filesystem." Below that, it gives me the "grub rescue>" prompt. Most of the commands that sites list for grub rescue only return "Unknown command". ls works and lists all of my partitions: (hd0), (hd0,msdos, (hd0,msdos7), etc. down to msdos1. When I "ls (hd0,msdos" (etc, etc) it says "error: unknown filesystem."
I then started looking into booting from a Live Ubuntu USB drive. I've tried 11.04 and 10.04 now and they both do the same thing. I put them on an 8GB flash drive (only 1 at any given time) using Universal USB Installer and was able to get to the Ubuntu menu (Run Ubuntu from this USB, Install Ubuntu on a Hard Disk, etc.) If I try either "Run Ubuntu" or "Install Ubuntu", the screen flickers and comes right back to that menu.BTW, my 3 operating systems are: Windows 7 HP 64-bit, Mythbuntu 10.10 64-bit, and Windows XP 32-bit. Laptop hardware: Core 2 Duo P8700 2.53GHz, 6GB RAM, Nvidia 8800 GTX video card.
I couldn't get 10.10 to boot (live or after install). I was able to install and boot 9.10 normally. Then I ran upgrade to 10.10 and I started getting the same problem trying to boot as with 10.10 disk. I found I could boot with 2.6.32 left from 9.10 but it will not boot 9.6.35 kernels. On a normal restart when automatically trying to boot the latest 9.6.35, I get this message before switching to an unresponsive black screen with no further hard drive activity:
GRUB loading
syntax error
Incorrect command
syntax error
error: file not found
[Linux-bzimage, setup=0x3400, size=0x420c50]
[Code]...
I have been searching for a solution and so far have not found anything that worked. I'm a pretty basic user so I'm not sure what is going on.
I'm remote from my system and so have to wait 2-3 days before I can get access directly, but I've noticed that when the kernel updates automatically (or forced by me), the next reboot stops at the grub page awaiting confirmation of the kernel I want to boot. grub.conf doesnt seem significantly different from that of fedora (my previos distro for this machine) and even has the default lines and times spec'd, so I can't see what's holding it up. Any ideas how I can prevent this so I can have my system auto-updating the kernel AND safe to reboot remotely?
View 1 Replies View RelatedA recent kernel upgrade broke nvidia and the network card. I figured out how to get the grub boot menu, but am having trouble figuring out how to set the default kernel to boot. I believe there used to be a file called /boot/grub/menu.lst that one could edit, but it doesn't appear to exist now.
View 2 Replies View RelatedI have Lenny, and Jaunty Jackaope installed on the same hdd. Jaunty Jackaope was installed 2nd so it has control of grub (I don't know if that is the correct expression) I want to remove Jaunty Jackalope however I know from past experience that after I do this I will no longer be able to boot into Lenny as I will get a grub error at startup. How to I give boot/grub to Lenny so that I can remove the other operating system?
View 3 Replies View RelatedThis is the third time I try unsuccessfully to install Debian as a second OS on a hard drive. When it gets to the end of the installation process the installer asks whether I want to go ahead with the Grub Boot Loader, I choose yes. The end result is however that I can't boot that partition within the hard drive -- i.e., Debian. Can someone tell me what is going on? Should I not use the Grub Boot Loader when I have more than one operating system on a machine? Should I not install Grub on the Master Boot Record (MBR)?
View 3 Replies View RelatedI've already tried Seamonkey to create a web page but can find no way to create a web form in which I want to create form fields. Before moving to Ubuntu I used Microsoft FrontPage to create web pages with form fields. This was easy to do. what is available to do the same in Ubuntu?
View 2 Replies View RelatedI used the update manager to update the kernel and whatever the other recommended updates were yesterday. I shut the computer down overnight and now when i try to boot into Ubuntu 9.10 i get a basic grub shell and when i try commands like "boot" it tells me there is no kernel loaded. I installed Ubuntu with Wubi so it is a dual boot system.
I've tried to access the Linux volume with a live OpenSuse 11 CD but there is no device to mount. It sees the entire hard-drive as if it hasn't been partitioned. I don't necessarily need to fix the installation. I just need to get my files back.
I seem to have determined a few other things about my "only gets as far as a GRUB command line" problem:To recap, sda3 (GRUB hd0,2) is the main Linux partition; sda9 (GRUB hd0,8) is the boot partition.GRUB is 0.92.Installation was from an 8.04LTS live CD (at least, that's what the envelope says it is)/"/boot/grub" (i.e., "/grub" on sd9/hd0,8) contains a "menu.lst" file. I modified it (had to do a "sudo gedit" from a command line!) to (1) comment out the line that hides the boot menu, (2) change the timeout from 3 seconds to 90, and (3) add a menu line based on my succesful manual IPL of DOS.
It still boots to a GRUB command line. If I do a "configfile /grub/menu.lst," a boot menu comes up. DOS will successfully IPL, but Linux still gets a "no setup signature found," (ditto for "recovery mode"), which suggests either a bad kernel, or a kernel that's too big for the GRUB to handle.Why would it be finding its way to grub, but not finding the boot menu file?Why would the live CD come up just fine, yet the GRUB and kernel it installs fail?
I'm currently running Karmic 9.10 in dual boot with Windows 2000. My computer has automatically updated and installed kernels 2.6.31-17, -19 and -20 (They show up in Synaptic as installed).
However, the newest kernel choice in my GRUB menu is 2.6.31-16-generic (followed by -15 and -14). These all start without any errors.
Question: Why haven't the newer updates shown up in GRUB for booting purposes?
Could it be a question that I didn't answer correctly some time back about accepting or not accepting an update or change in GRUB?
How can this be changed? The new kernels do not show up in Start-Up Manager either.
I locked the screen, came back, typed the password, screen remained black, though cursor was visible and moving. Nothing I could do to rejuvenate the screen. Had to switch to tty6, sudo shutdown -r now. Then, on reboot obtained kernel selection, it proceeded to displaying kernel messages, but froze on sdb, after 3 secs. I figured it was the usb, so turned off, removed usb cables to external hard drives, but again it froze saying something about firewire mouse, the mouse is also usb. I tried several times, but no matter what kernel I chose, I couldn't get it to boot. So I loaded puppy live cd, but now it can't access some parts of the disk. I was running utorrent and the folder with partially downloaded files can be accessed but there's nothing there (there was), and some folders can't be accessed at all.
View 2 Replies View RelatedI'm a very new Linux user, so speak slowly and don't use big words. I installed Karmic from the Live CD. It is the only OS in use on this system. I then upgraded to Ubuntu Studio using the instructions found on the wiki.
On bootup, I get a brief message stating "GRUB loading" and then the system automatically boots to the generic kernel. No GRUB menu is ever displayed. I would like the option to boot to the real-time kernel, but I have no idea how to edit the appropriate files. I've done a fair amount of reading on the subject, but I find very little information relating directly to the real-time kernel, and so I still feel like I'm too green to do it without messing something up.
I tried to update to 2.6.31-20 kernel but I think I messed it up, because when I click on it in the GRUB it starts to load but then it goes back to the dell boot up screen and I have to use the older one in order to get onto ubuntu. Is there anything I can do to fix this?
View 3 Replies View Related