I've only a small /boot sector and rpm -qa | grep kernel kernel-2.6.31.12-174.2.22.fc12.i686 kernel-PAE-devel-2.6.32.9-70.fc12.i686 kernel-PAE-2.6.32.9-70.fc12.i686 kernel-2.6.32.9-67.fc12.i686 abrt-addon-kerneloops-1.0.8-2.fc12.i686
I'm using the PAE kernels, need the devs for nvidia kernel building,can I remove all the non PAE kernels without damage please?
yesterday I removed old kernels via. the synaptic manager- I'm 100% certain I did not removed the latest stable kernel, and the version before- I did however removed the oldest two. Now after restart I'm dead in the water- i cant get past the initial boot- the screen goes black. I i'm running ubuntu 9.10 double-booted with windows vista, and right now I cant even get into vista...
Let's say that I messed up with removing old kernels, and removed sth, that shouldn't be removed- but how does this mess up vista?
Since yesterday every time I boot up my F11 install kerneloops starts using 100% of my processor (well, one of them) and never stops (until I kill it, that is). I don't know what's going on. I can post logs, but I'm not sure what are the relevant ones here.
I am using fedora 6 and i have delete same file from home partition and i want to remove these deleted file permanently. so, nobody able to recover these file.
I am using CentOS 5.5. After upgrading i have at present 4 kernels in the menu.lst.If i try to remove any kernel, 2.6.18-194.3.1.el5.i686 via Package Manager, i am told that i am removing critical software for system functionality etc. How delete older kernels?
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?
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.
When I run yum list installed command the output shows two kernels:
[Code].....
Would it therefore be safe to remove the first kernel in the installed list to save having two kernels being updated everytime I run yum update? Or is the PAE kernel dependant upon the original?
i'm trying to reinstall LaTeX after i manually deleted all of it's directories in /usr/share, apt-get can't seem to remove or install any of the packages,
Code:
sudo apt-get install -f Reading package lists... Building dependency tree...
I'll start at the beginning. The problem i am about to describe occured in ubuntu 9.10 for the first time (https://bugs.launchpad.net/ubuntu/+bug/480850) and is ironically partly responsible for my switching to debian. which i don't regret, but it seems i can't run from the bug any longer because now it's in squeeze, so i want to fix it or make a proper bug report:
Steps to Reproduce: 1: Suspend Laptop to RAM 2: Resume from Suspend 3: Wait and see, preferably monitoring top: At some random time, ranging from immediately (black screen after resume) to several hours later, the system will become unresponsive. Switching to tty1 or Alt+Print+K does not work, Alt+Print+REISUB does work. Each freeze is anticipated by a random process (this time it was mandb, was installing something) hogging 100% of CPU, then the System becomes gradually unresponsive within a minute or so (panel, metacity, finally mouse cursor freezes too). Alternatively, in case of a black screen immediately upon resume, Alt+Print+K works (EDIT: or not), and the system remains usable. Additionally, i don't know if this is related, i noticed one process using 9999% of CPU for a second according to top, just thought i'd mention it. This bug constitutes a regression, suspend does work flawlessly on this Laptop in Lenny.
The above is how it presented itself at the beginning on a fresh squeeze install, however, after two days of trying, i additionally get kerneloops messages i did not get before (again, after at least one suspend to ram) and after that the system becomes generally unstable (random applications won't properly open or terminate, including nautilus, evolution, iceweasel). Can this be due to secondary damage from the freezes and alt+print+reisubbing repeatedly?
The good news is, apart from this probably already damaged squeeze install, i have another one on one of my playground partitons, where i avoided suspend so far, so i can still try things out there. (it's kde, but i don't think it's related to the desktop environment).
I 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 have a fairly aged Pentium 4, RAID, desktop computer with Fed 11. I started off with the 686 PAE kernel and update it whenever the update software tells me to. Some time ago I downloaded an NVidia driver which said it needed the 586 kernel so I installed that as well.I then uninstalled the NVidia driver as it caused some minorish problems without any improvement to the graphics. The bottom line is I now have the last three 686 kernels and the last three 586 kernels, which I'm pretty sure I don't need. The machine seems to run fine whichever I use with no discerable differences.My questions are, what is the difference between the two types, which should I actually use and how do I get rid of the other. It would at the very least reduce bandwidth use when updating.
My MythTV system is running under F12. It is in "appliance mode;" all configured and happily doing the PVR thing without a pressing need for upgrades.However, there is a feature in the upcoming 2.6.32 kernel that I'd like to take advantage of; internal support for a certain capture card.
I see 2.6.32 mentioned as part of the F13 release. My question is, will it also be available for F12 . . . maybe sooner than the F13 release?Another way to put this is: How wedded are Fx releases and kernel releases? Is a major kernel goalpost like 2.6.32 the reason why Fx releases are made?
operating system : fedora 15 kernel 2.6.38.8-32.fc15.x86_64 bugs : when updated with the latest update it always log into the fallback, i read somewhere that the nvidia driver version 275.09.07 does not work correctly with gnome shell so i did reinstall it and it fix the log in issue but now it gives me a screen with lots of bad mixed color after returning back from suspend. kernel 2.6.38.8-35.fc15.x86_64
bugs : it gives me this error at boot time "alg: skcipher: Failed to load transform for ecb-aes-aesni: -2" and this message does not save at boot.log anyone have any idea how to fix those issue
I have 3 kernels installed. When I look at my installed kernels with yumex or package kit all I see is the latest kernel. rpm -qa lists them and I was able to remove the oldest using rpm -e.Is this some new feature of YUMEX and package kit to only show the latest version installed?
I'm sure there is a thread on this somewhere, but after looking though the first 100+ search results, I can't seem to find it.
After a kernel update today, I noticed that new kernels are not being added to my grub menu.lst (so consequently, I was running an older kernel).
Any obvious reason why this would happen (kernels being installed normally, with yum update)? I thought the whole process was supposed to be automagic.
Would it have anything to do with the fact that I just kept my F11 menu.lst, and added a F12 kernel to it when I installed F12 (to a separate partition), then eventually (today, finally) removed the f11 kernels from it?
The latest kernel screwed up my laptop and I would like to reload the previous kernel to get back to where I was but I dont see it as available anymore... Is there an archive to pull previous versions from ?
I'm unable to boot my box since the first 2.6.34 kernel arrived.I hoped the second will fix the problem but it didn't.The display just enters in the power save mode after a second and that's it.The system boots fine with the 2.6.33.8-149.fc13.i686 kernel.The lspci result is:
Install fglrx driver for ATI but it just installed for one old kernel 2.6.34.6-54. and 2.6.34.6-54.fc13.i686 i have also kernel 2.6.34.7-56.fc13.i686.PAE, how can i compile the fglrx for it?can i just copy fglrx.ko from /lib/modules/2.6.34.6-54.fc13.i686.PAE/extra/catalyst/fglrx.ko to /lib/modules 2.6.34.7-56.fc13....
I'm running FC 13. I believe that the base install is kernel 2.6.33.6-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 2.6.34.7-56 nor 2.6.34.8-68 installed an initramfs file. Since my root volume is in LVM, I can't boot with those kernels. I saw in another post that doing a "yum install kernel" would install the missing files. I tried that and it tells me that kernel-2.6.34.8-68.fc13.x86_64 is already installed and latest version.
I ultimately want to upgrade to FC 15 because I've got a new nVidia video card and need driver 270.41.06 for fc15. My fear is that if I upgrade I might not get the initramfs files in the new versions of FC and end up with an unusable system. Is there a way to add the initramfs files for the newer kernels and/or will I have the files after an upgrade?
Starting with kernels 2.6.29.x and above (which includes 2.6.30.x and 2.6.31.x),whether obtained from "kernel.org" of from the "FC11 repository", none of theseresume properly after putting the computer to sleep (suspend)... in my case, via"pm-suspend".When I press the "On" button, I hear the fan, but get no video. And the fan neverreturns to the normal resumed, slower speed -- which it normally does after aroper resume.Eventually I have to issue "Ctrl + Alt + Delete" to reboot. So the computeris resumed to some degree (to have been able to accept that sequence), butnot all the way - no video (and who knows what else)Any ideas -- I've searched high and low. Are there new kernel parametersI have to be aware of when I do a "make oldconfig", and go from there?
Just installed Fedora 12 on my Dell Precision M4400 and I'm trying to install the Broadcom wireless driver. When I try to compile the driver, I get:make: *** /lib/modules/2.6.31.5-127.fc12.i686/build: No such file or directory. Stop.So I followed the link and /lib/modules/2.6.31.5-127.fc12.i686/build is a soft link:lrwxrwxrwx. 1 root root 47 2009-11-09 14:17 build -> ../../../usr/src/kernels/2.6.31.5-127.fc12.i686But in /usr/src/kernels all I see is:
When I went to start up the computer, the kernel usually hung at the same place on boot up, although sometimes it booted just fine. The default kernel is 2.6.31.9-174.fc12.x86_64. It's boot up arguments are:
I also have kernel 2.6.32.7-37.fc12.x86_64, 2.6.31.6-145.fc12.x86_64, 2.6.31.5-127.fc12.x86_64. I have seen the same behavior out of all four of them. Last night I ran Memtest86+ all night. It took eight passes with no memory errors. As far as hard disks go, I have two Seagate Barracuda 1.5 TB drives operating as software RAID 1 (mirroring). One of the drives does have three bad sectors. The motherboard is an Asus P6T6 WS. This morning I plugged in the GP diagnostic chip that came with it, but I'm not seeing a whole lot useful there, except that now it is just displaying "FF" non stop.
I did some poking around on the web, and it looks like "FF" is supposed to mean that the CPU isn't properly seated, which makes no sense because the system monitor software is detecting all four cores perfectly, and I have no other odd behaviors anywhere else. At this point I'm rather at a loss to understand what could be causing the difficulties. Sometimes any of the four kernels boots fine, and sometimes they don't. The funny thing is that on the blue "boot progress bar" all four kernels hang at exactly the same spot if they hang at all. After doing some more poking around, I'm relatively sure that "FF" does NOT mean that the processor isn't seated correctly. I'm going to try contacting Asus and see how far I get towards getting some good info on what the diagnostic codes mean.
Yesterday i updated fedora 13.After reboot problems started with te display driver.Scrolling sreens goes very slow and with little steps.Moving a screen from one side to the other goes also very slow.It seems there is a problem with the ATI driver.I also have problems after new kernel updates.The new kernels simply won't boot? The boot proces hangs everytime the fedora logo turns wite.
Fedora-13 will not play sound. It's definitely a kernel issue and I am not the only one from what I read elsewhere. Prior to kernel 2.6.28 audio works on this Samsung Q1 Tablet PC. Any kernels from 2.6.28 onwards will not recognize my sound card and therefore won't play sound no matter what. I've proved it running different livecds (Suse, Mandriva, PCLOS, etc.) with kernels 2.6.25, 2.6.27, etc., all with audio. How can I use/import a suitable kernel for Fedora-13 so that it will recognize my sound card (driver snd-hda-intel) on this Q1?
I have a system with one 2.6.35 kernel, one 2.6.38 kernel I built from a koji src rpm and 1 rawhide 2.6.39 kernel I installed directly with yum. Now that a newer 2.6.35 is out, I'd like to yum update my 2.6.35 kernel so I'll have those two in the 2.6.35 range. But the problem is those newer kernels (38 and 39) make yum think there's no update that's available because they have higher version numbers than the new 2.6.35.12-90 kernel. Is there someway I can make yum update to 2.6.35.12-90 anyway? I was thinking I could download the kernel and kernel-devel rpm files for 2.6.35.12-90 and do the yum install for them off the hard drive, would that work?