I just installed 10.04 over my previous dual boot with Windows7 and 9.10. Went well. Now, in the Grub2 menu, there are like 14 kernels. I tried to find them in Synaptic to delete them, but they are not there! So, I went to grub.cfg and deleted the entries, updated grub, and they were back! How do I get rid of these entries?
View 6 RepliesI have recently installed the Maverick backport kernel (2.6.35 - from the lucid-updates/main repo) and while I was at it I also manually (through synaptic) got rid of some old kernels. I made sure that I kept the current Lucid kernel though (that was working fine). All seemed well (although I didn't actually check - just no errors) so I rebooted.On reboot I have lost all my Ubuntu kernel options!
I rebooted with a live cd, mounted, etc and ran
Code:
sudo update-grub
but it doesn't seem to find any kernels!
Code:
grub-install --recheck --root-directory=/media/mnt /dev/sda
Checked /boot to see if the kernels are there:
Code:
jed@lightning:/boot$ ls
abi-2.6.32-31-generic memtest86+.bin
abi-2.6.32-32-generic System.map-2.6.32-31-generic
[code]....
Even reinstalled burg (used to use it but it got broken by a kernel update long ago and never bothered to fix it as I only use Linux these days anyway)Funny thing is that BURG finds the kernels and reports no problem, but then drops to the grub-error prompt on boot.
I am using a Dell XPS m1330 with ubuntu Maverick 10.10 and with a Nvidia card. Recently I wanted to add plymouth support to my boot screens via this script: [URL].... but maybe i did something that ruined my pc and now, in GRUB, i can only see recovery kernels. The situation is this: in grub i see
linux recovery kernel 1
linux recovery kernel 2 (old one)
memtest
windows 7
My "normal" linux kernels disappeared. When I want to boot linux I use a recovery kernel, then I simply hit "resume" in the process, do the textual login and than use the command "startx" to start the system. However i'm getting no Plymouth and no normal boot. I have already tried to fix grub recreating the linux kernels, but they just don't show.
In etc/grub I don't have 05_debian_theme, but I do have it in grub.d.old.
Because I'm such a huge noob I don't want to **** anything up, but I want to be able to change theme.
I have installed Lucid Lynx more than a dozen times in the past thirty hours and I've almost got it working with RAID. The current problem is with /dev/md0 not existing when grub2 tries to access it. When I boot from the alternate CD in rescue mode, Ubuntu sees /dev/md0 as a software RAID array and I can access the files accordingly. When I boot from the grub2 bootloader, it sits for a while before spitting out "Gave up waiting for root device" and tossing me into the initramfs shell where I can see that /dev/md0 doesn't (yet) exist. What can I change within grub2's configuration to inspire it to start /dev/md0 before trying to mount it?
View 6 Replies View RelatedI am running a dual boot system with windows 7 and Ubuntu. Both have run smoothly on my machine (Core 2 quad core on Gigabyte board) I recently upgraded to 10.10 from 10.04 via the update manager within 10.04. Following the upgrade the initial boot failed at the login screen ( i simply got the purple colored screen with a white box in the center of it). Instead of trying to figure out what went wrong, I simply re-installed 10.10 from live CD on top of the upgraded Ubuntu that was failing at the login screen. The live CD install seemed to fix everything for the most part ( I did notice some quickly flashing text right before the login screen. I think it was an error message but it was too fast to read)
My problem now is that I am trying to remove some of my old kernels from the Grub2 boot screen and I cant. I have read many posts on how to remove the old kernels, but my system is proving to be difficult. The old kernels definitely show during boot, but whenever I go into Synaptic they are not there. I have downloaded Ubuntu Tweak, and they do not show in it either. I have read the information at [URL] I went to http://www.fixthecode.com/remove-hug...sts-in-ubuntu/ and thought this would fix my problem but I keep getting an error: "awk: 1: unexpected character 0xe2" when i try to run: "dpkg -l | grep ^ii | grep 2.6.3x-xx | awk -F{print $2} I am running kernel 2.6.35-22 The kernels i want to remove are 2.6.32-23 and 2.6.32-24.
I'm simply trying to remove old kernels and second rename things that are on the list. It used to take me 10 seconds with grub1, but having some difficultly with grub2. So far I went into /boot/ and removed the old kernels and then did a sudo update-grub2 and it seemed to remove all the old kernels from the list. Is this the best way or doing it or any issues on doing it this way? Second I just want to rename what boots up like Ubuntu 2.6.32-22-generic to something else. I keep read not to modify the grub.cfg, but not sure what to do? I poked around the files in /etc/grub.d/, but not sure what to do?
View 2 Replies View RelatedI followed the Grub 2 Basics steps to remove Grub 2 kernel listings.
However I'm stuck with 3 older versions that was completely_removed from Synaptic (kernel/headers/generic), but remain in grub.cfg.
Quote:
Here is my current grub.cfg:
(How do I remove *.14 *.21 *.22 from my menu entries Ubuntu-tweak is not an option for me. I like it old-school or with the tools at hand.)
Code:
I considered changing permissions for grub.cfg, but update-grub and new kernels will revert my changes.
Is it possible to add menu entries for older kernels to boot instead of the latest?
I have tried this in Ubuntu 10.04 and it hasn't worked.
This used to be possible with ease in grub legacy.
I copied the current menu entry from /boot/grub/grub.cfg and pasted it in the /etc/grub.d/ 20_custom file.
Then I changed the kernel number to the older kernel number and the initrd number too. #update-grub puts this entry into 'grub.cfg', but it doesn't work.
I get:
The old kernel is in /boot as well as the respective initrd and config files.
i initilally installed ubuntu 9.10 then installed windows 7 ,then i recovered grub2 using livecd as told in the post [URL] i did "sudo update-grub" and got windows 7 menu entry but when i select that entry windows 7 does not load but the grub2 is reloaded again.
i cant boot to windows 7.
Windows 7 have 100 mb partition "System Reserved" the grub2 points to that partition but still windows 7 not loaded.
sudo fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3c3a81f5
[Code]....
I went through so many post but I haven't found the proper answer yet hope you have an Idea1. Grub2 saves only Linux OS as last selected no Windows OS2.It is possible to boot into a cdrom (drive)?
View 2 Replies View Relatedi'm having a problem with every single kernel upgrade since 2.6.32-21.I'm currently upgraded to 10.10 using GRUB2 and LVM disk configuration and all newer kernels (up to the latest 2.6.35-23) crash with the following errors:/init: .: line 61: can't open '/scripts/functions'Kernel panic - not syncing: Attempted to kill init!Pid: 1, comm: init not taintedI've already double checked all the entries in GRUB regarding paths, etc and i can't seem to find any difference between the working 2.6.32.21 and all the others
View 6 Replies View RelatedAfter I messed up badly with my netbook I have to reinstalll the OS, it is a government property netbook that came up with Edubuntu 7.04 insalled on it. I shouldn't mess with the filesystem but I did and now I have to install Edubuntu from the beginning, but I must be sure that everything will just like I have done no change, so I am afraid that I can make some mistakes at this pointThe first thing that I want to know is: Why there are multiple kernels listed at the GRUB (v 1.5)...this is the full list:
Ubuntu, kernel 2.6.28.9 Default
Ubuntu, kernel 2.6.28.9 Default (recovery mode)
Ubuntu, kernel 2.6.28.9
[code]....
I did a "dirty install" of Maverick over my existing Lucid system. That went very well and I am having no problems with Maverick. However, this morning, I decided to clean off the old Lucid kernels. In the past, after installing a new kernel on the same Ubuntu release, I have done this by running "aptitude search 2.6.32-24", for example, then running "sudo aptitude purge" for the kernel and header files it found.
Now that I have changed releases, aptitude no longer finds the Lucid kernels installed on my system, even though they still reside in the file system and show up on the grub2 menu. So, how do I manually find everything necessary to delete for the old Lucid kernels?
Just curious as to why this would be happening, but I had been running on the Lucid kernel 2.6.32-28-generic. And when I looked in Synaptic, I noticed there were kernels 29 and 30 available. I manually installed them and deleted the older ones I had - 27 and 28. I believe I have all of the generic Lucid software sources and I get updates for everything else. Just curious as to why these kernels were not available to be installed automatically.
View 5 Replies View RelatedI have Ubuntu 8.04 (32-bits) installed on /dev/sda and Ubuntu 10.04 (64-bits) installed on /dev/sdc (this is an update from 8.04 64-bits originally installed on /dev/sdc). There is a grub on each of these two disks. Both are the old grub (prior to version 2). Here is the top kernel listing from /dev/sda:
titleUbuntu 10.04 LTS, kernel 2.6.32-24-generic (grub sur unite1)
root(hd2,0)
kernel/boot/vmlinuz-2.6.32-24-generic root=UUID=761c3d13-cc55-4117-934f-693766e122b6 ro quiet splash locale=fr_FR
initrd/boot/initrd.img-2.6.32-24-generic
quiet
[Code]...
I have this strange problem on ubuntu 10.04 64 bit, that when running update-grub, it will only put the oldest kernel into the grub menu, despite the fact that I have recent kernels around as well.
in particular:
Code:
# 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
[code]...
I'd like to see the most recent kernels in the grub menu, with the most recent being on top.
The title's not especially clear, so I'll post a screenshot of what's happening. The upgrade keeps finding instances of the same kernel; the list in the terminal is constantly scrolling down, finding 'new' instances.
It's been doing this for about half an hour now. BTW, upgrading from 64bit 9.10 to 64bit 10.04.
I have a grub menu with a ton of old kernel entries that I want to delete. I've scoured this forum, and haven't found anything that works. I've tried:
Code:"the easiest way to get rid of old kernels from grub is to uninstall the package, the post-install scripts will update grub
for example my current kernel is:
uname -a
Linux hemma 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64 GNU/Linux
then remove older kernels found in /boot like this:
sudo aptitude remove linux-image-2.6.31-15-generic" When I tried that, the output showed the package being removed, but nothing was removed from the grub menu. I tried running the kernel I supposedly removed, and it wouldn't start, which is promising, but how do I get it out of the grub menu? I've also tried using Synaptic, but that didn't work either.
I upgraded to 2.6.35-30.56 last night and now my system's a little flaky. Everything seems to be running ever-so-slightly slower and fullscreen flash is now choppy. The weird thing is the Grub menu upon bootup only shows the latest kernel, but not the previous kernels. Doing an "ls" of the /boot folder only shows this newest kernel. I'd like to revert back to the previous kernel but don't know how.
View 2 Replies View Relatedhow would i go about deleting my old kernel?i have my ubuntu machine partitioned the way gentoo would partition a drive with a seperate boot directory. my boot directory is only 200 megs so i can probably fit 4 kernels max into it and need to eject the old ones.
View 3 Replies View RelatedI am currently running a Debian 4.0 (etch) PC and I can't upgrade to a newer distribution for legacy software reasons.
It is currently running on Kernel 2.6.18-4-686 and I would like to upgrade it to Kernel 2.6.22-3-686 (whilst keeping my current Debian 4.0 Etch installation). Does anyone know how this could be possible?
Prefereably I would like to instal Kernel 2.6.22-3-686 along side my current Kernel 2.6.18-4-686 with the option to specify which kernel to use when booting.
I have had some trouble with understanding the wireless drivers. I am using backtrack 4 R1, and the reason was merely for the network and having many necessary networking dependencies already there. However I found that I am using a HAL for the ath9k and madwifi-ng drivers, thus I must patch the card and go through all of that.
The specific distribution I am using is Backtrack 4 R1 with KDE3 and ubuntu on the 2.6.34 kernel. I know I have through an update script found the wireless drivers and downloaded them, however all attempts to get it to fully work haven't helped. I checked the forums, and it doesn't seem like they consider it a backtrack specific question but a linux specific question. I performed hwinfo and it returns ath9k and the memory address, channels 1-14, wlan frequencies(2.412,2.417, 2.422, 2.427, 2.432, 2.437, 2.442, 2.447, 2.452, 2.457, 2.462, 2.467, 2.472, 2.484. I have all modes of encryption set.
I am using both ifconfig and iwconfig with a wicd frontend to access the network typically. Unfortunately I am only seeing a wlan0 and no ath0. Furthermore, I manually issue these commands I am doing so I set each aspect of the card up (i.e essid, channel, mtu, fragmentation, etc....).
Now I did shed some light upon this in the sense that I found out how to initialize the madwifi-ng hal abstraction layer via 'start airmon-ng wlan0' and then it returns.....
mon0 ath9k py0 etc. etc. etc.( this isn't exact I am unfortunately not at my computer. But the device is then able to work, however I am not sure as to why I am not able to have the ath0 device in my wireless devices if indeed everything else appears to be ath0.
I would love to change the boot order on my laptop. Mainly because it is shared, and I am the only one who uses Ubuntu (version 9.10)... So everyone keeps moaning for me to change it!
Following all the sound advice from this forum it looks easy... Except /boot/grub/menu.lst does not exist!
I installed ubuntu on my internal hard disk I experienced a problem with Grub and I just formatted all the Ubuntu Partitions and convert their format to NTFS to restore my windows (I have a backup) but now despite of I format all the Ubuntu's partitions but in the boot time, the grub exist and the grub apear I want to know where does grub exist? I installed ubuntu on the dual booter situation and it was ubuntu 9.10
View 1 Replies View RelatedFresh install of 9.10. Update all. The update froze at the very end: configuring grub-pc. I let it run like that all night before settling for a reboot while the update manager was still running. (The update also raised the kernel version.) After reboot, I tried the newer kernel [2.6.31-17-generic] at the grub menu and got this error:
Quote:
udevadm trigger is not permitted while udev is unconfigured.
udevadm settle is not permitted while udev is unconfigured.
svgalib: Cannot open /dev/mem.[code].....
And, cat /proc/modules gives me a long list of modules (too much to retype for now).So my hard drive is there. maybe some errors on the / home partition [sda6] and I can get to the root directory.
FYI: MS-win XP still boots fine from grub.
Alright, I have downloaded the upgrade for 10.04 and installed upgraded from my previous 8.04. Everything was working all fine until I had to reboot my pc. When I did i got some errors
Mount: Mounting none on /dev
It goes on to tell me that my UUID does not exist. Then it says
ALERT! Alert! /dev/disk/by-uuid/xxxxxxxx-xxxx-xxxx-xx$ does not exist. Dropping to a shell! It then drops to a very simple shell which has no flexibility and is very frustrating.
EDIT: This is the full error message
Mount: Mounting none on /dev
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)ALERT! /dev/mapper/debian-root does not exist dropping to a shell.
Just tried installing Ubuntu 10.10 from a USB device on my Windows 7 machine but something goes wrong. Far into the installation the computer restarts, asks me which operating system I want to start (it had already done this once before) and I choose Ubuntu. Then I get three alternatives:
Ubuntu, Linux 2.6.35-22-generic
Ubuntu, Linux 2.6.35-22-generic (recovery mode)
Windows 7 (loader) (on /dev/sdb1)
I pick the top choice, and get the following message:
ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell.
If I start recovery-mode i get the same message. There's some text above the message that reads "new low speed USB device using ohci_hcd and address"... Could there be a problem with the usb-drive? If I remove the USB drive I get the message: Gave up waiting for root device.
Code...
In what package does uno exist?
I have a dual boot windows XP/ubuntu 9.10 set up on one hard drive. Everything was working fine. The 9.10 install had been updated from 9.04. I recently had problems with the XP partition (XP basically collapsed) so I re-installed XP on the same partition it was on before. I then attempted to reinstall Ubuntu ( I decided I wanted a new 'clean' installation of Ubuntu as well). When I got to the partition function it refused to recognize that there is a Windows partition, or a previous ubuntu partition, but states 'No operating system installed' or similar, and offers the entire hard drive for installation. When I look at the partitions using Windows partition software the Windows and the ubuntu partitions are clearly in evidence. I have also tried to reinstall GRUB but it doesn't appear to exist.
View 3 Replies View Related