Fedora :: 2.6.32.14-127.fc12 Kernel Is Slow After Upgrading?
Jun 16, 2010After updating to 2.6.32.14-127.fc12 kernel my computer is slow.
View 4 RepliesAfter updating to 2.6.32.14-127.fc12 kernel my computer is slow.
View 4 RepliesI have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
I'd like to reproduce the way I got to f12 from f11, but obviously to f13 basically I started out on the f11 rawhide repos, then as f12 got released a yum update updated my fedora-release and then hey presto I was automatically upgraded to f12 final release if I now turn on my rawhide repos, as f13 is nearing completion, will I be updated to the latest f13 release (RC3 I believe) and then as f13 gets released my fedora-release will be updated and i will then be upgraded to f13 final as happened before?I don't want to download a whole dvd iso and then upgrade when f13 is final, I'd like to do a gradual transition ie..
f12 -> f13 RC3 via rawhide
f13 RC3 -> f13 Final via yum update
Following this from the wiki: It states Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update. How do you ensure that its the last package to update?
First install the new fedora 13 gpg key. You may wish to verify this package against [URL] and the fedora ssl certificate.
rpm --import [URL]
Upgrade all packages with
yum update yum
yum clean all
yum --releasever=13 distro-sync
- Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update ... YMMV.
- Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.
I've been trying to upgrade my installation for some time now and just can't quite get it right. I would upgrade from the DVD but the installer hangs when it says "Looking for installation images on CD device /dev/sr0". However, that's not really my question. I've resorted to the upgrade instructions as found at [URL]. If I don't use the '--skip-broken' option it complains about the following:
abrt-gui-0.0.11-1.fc12.x86_64 from fedora
abrt-libs-1.0.6-1.fc12.x86_64 from updates
samba-3.4.5-55.fc12.x86_64 from updates
samba-client-3.4.5-55.fc12.x86_64 from updates
samba-common-3.4.5-55.fc12.x86_64 from updates
samba-winbind-3.4.5-55.fc12.x86_64 from updates
samba-winbind-clients-3.4.5-55.fc12.x86_64 from updates
If I use the skip broken option, it then complains about:
Transaction Check Error:
file /usr/share/locale/de/LC_MESSAGES/cryptsetup.mo from install of cryptsetup-luks-1.1.0-0.4.fc12.x86_64 conflicts with file from package cryptsetup-luks-1.0.6-7.fc11.i586
file /usr/share/locale/sv/LC_MESSAGES/cryptsetup.mo from install of cryptsetup-luks-1.1.0-0.4.fc12.x86_64 conflicts with file from package cryptsetup-luks-1.0.6-7.fc11.i586
file /usr/share/man/man8/cryptsetup.8.gz from install of cryptsetup-luks-1.1.0-0.4.fc12.x86_64 conflicts with file from package cryptsetup-luks-1.0.6-7.fc11.i586
I can't seem to remedy this problem. There were other conflicts but I just removed those packages. When I attempt to remove 'cryptsetup-luks' it then tells me it's going to remove something like 200 others which did not sound like a good idea.
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
View 10 Replies View RelatedI only began using Linux with the release of FC8. I've upgraded into every new version (upgrade, no clean installs), after the new versions had been out a while. I struggle with command lines, updates, cups and other very cool tools that are only difficult because they have so many options. I'm Windows guy at work, a system admin and db administrator, plus the company expert on Excel. But, all in all, I hate Windows, and I'm loving Fedora, even if I struggle.
This last upgrade really kicked me in the pants. The first thing I noticed was all of my software sources were gone. I did some research around the forum and tried a few things, but it's still not working. Unfortunately, I may have uninstalled Yum in the process, but not rpm. I've tried to re-install the yum packages, but still no luck.
This morning before leaving for work I noticed that a boot log indicated that cups had failed. I went in to restart the service (through gui) and it said it was running. So I stopped the service and re-started. I tried to access port 631 through Firefox and it wouldn't open. I need to check the firewall to see if it's an open port, but beyond that I don't know.
Now I'm wondering if I should just do a clean install. I haven't done this, mainly because I didn't want to hassle with setting up my printer again (although, it's a Brother and they have the drivers and good instructions), and I didn't want to lose any emails that I've received via Thunderbird. The printer is really a non-issue now, as I'll have to set it up anyway. I have a backup of the /usr folder and all the documents. Question is, if I restore the Thunderbird folder after a clean install, would it bring back my email?
Does any one have a way to speed up the internet on Fedora 12? I have a dual boot system with Vista x64 on the flip-side, and my wireless connection there is just fine. But when I get on this side, it goes back to the dial-up days (yes I said the DU word). yum updates seem to be just fine, and e-mail seems to be fine. just firefox is slow. And now that I put the x64 Flash in (thanks to leigh123linux), with that working too it seems even a little slower again.
View 3 Replies View RelatedNot wanting to speculate why, in the repositories, Fedora doesn't *also* provide a on-KVM enabled kernel counterpart to the default KVM enabled kernel that *is* supplied, I must say I'm frustrated that they haven't done this simple thing.
Considering that everyone who upgrades to KVM enabled FC12 from a previous non-KVM release of Fedora (like FC10) ... considering that these people will be guaranteed to no
longer be able to run VirtualBox or VMWare Workstation after upgrading, is a disappointing oversight by / or intent of Fedora (one that manifests in *lost productivity*).
And try though you may to install the kernel source RPM and compile it after running "make xconfig" to disable KVM support, you usually can't! Fedora kernel compile attempts often die very early in the "make" process, indicating something like ...
"Kernel compile error: No rule to make target `missing-syscalls'
or some other silliness. And when you successfully compile a "kernel.org" kernel, and try to boot it, you get all kinds of missing library errors (etc).
Given that it would be simple to provide both a KVM enabled kernel (as they do), and also a non-KVM enabled kernel (which they don't) so the rest of us can seamlessly continue to run VirtualBox and/or VMWare Workstation after an upgrade - and avoid getting entangled with deciding whether use KVM or XEN for guest O/S's... it's a frustrating misstep to not have done this basic thing (i.e. include a non-KVM kernel). It was a rude awakening when we tried to launch VirtualBox only to have it fail after the upgrade.
Anyway, has anyone successfully compiled their own kernel for FC12 and not get errors after boot? If so, which sources did you use; and what kernel version? In the meantime I'll try out other kernels and compile options.
I just upgraded to Fedora 12 x86_64 via yum upgrade. However I have problems with booting. The new FC12 kernel won't boot. Boot output is something like
Code:
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sda to RAID set "sil_ajabaccaaidg
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sdb to RAID set "sil_ajabaccaaihe
No root device found Boot has failed
I resized boot partition to 400MB, formatted it as ext4 and recopied all files, modified fstab to update boot partition's UUID. Tried to set a boot flag on boot, still, I can only boot with the old kernel from Fedora 11. Is it a Fedora 12 kernel's bug or something wrong with my setup? I don't use any RAID, and the sil error is present with Fedora 11 kernel also.
Having just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 2.6.32.19-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
View 10 Replies View RelatedI have some programs, that will only install on i586 architecture (opposed to x86_64). My CPU is 64-bit architecture. Can I install FC12/11 with i586 kernel on the hardware? How? Any disadvantages except the fact that I'm supposedly not able to use the 64-bit feature of the CPU?
View 3 Replies View RelatedI can't seem to find the kernel source for 2.6.31.12-174.2.22.fc12.i686. This should be a simple task, what am I missing?
View 5 Replies View RelatedForgive me if I have posted this in the wrong forum, first time poster with Fedora. I have been using Linux for some time now, mostly Mint, but Fedora 12 @ work. Anyway, I receive the following error in my /var/log/boot.log:
Code:
nvidia.ko for kernel 2.6.32.9-70.fc12.i686 was not found
and the driver does not load (My xorg.conf file is not loaded), but once I am at a
[code]...
Use 2.6.32.11-99.fc12.i686 kernel,
A package needs same kernel source to build.
Add/Remove Software show only: 2.6.32.12-115.fc12... & 2.6.31.5-127.fc12...
How to get kernel-devel-2.6.32.11-99.fc12.i686?
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
I'd like to have a shot at building FBReader 12.1 from source for use within F12 (kernel 2.6.31.9-174.fc12.i686.PAE) but am having problems locating the following .rpm files:
libz and libbz2 -- libraries for zip and bzip2 (de)compression
libfribidi -- for bidirectional text support
lincurl, version >= 7.17 -- for network libraries integration
I had fedora 12 installed on a Macbook pro Intel first generation with ATI Radeon graphics card (see the attachment). Compiz crash when trying to watch *.wmv movie codified with wmvvc1dmo on kernel-PAE-2.6.32.9-67.fc12.i686. I want to convert the film to *.mpg, then I download the mplayer codecs in order to see the film, I can do it without problems with the on kernel-PAE-2.6.31.12-174.2.22.fc12.i686. But I updated my system last Saturday and when I was trying to see the movie again the computer began to respond really slow, then I began to close applications and when I tried to restart I got the message: "compiz is not responding".
I tried again but the same problem. Other thing that I noticed is that when the computer go to sleep, when I wake up it, the display show horizontal black spikes, it is like it doesn't have the appropriate refreshing rate. I think that the problem is related with the acceleration on graphic card. Yesterday, I booted on kernel-PAE-2.6.31.12-174.2.22.fc12.i686, and I watched the film, and the wake up was without problems. That is the reason I call it a regression.
[Code]...
kernel-2.6.32.10-90.fc12 seems to break 802.11n with my intel 4965 chip on my thinkpad t61p. Anyone else seeing the same thing? iwconfig shows extremely low bit rate. dmesg doesn't show anything at all unusual.
View 10 Replies View RelatedI had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10
(hd0, 1) 120GB : /home
(hd0, 2) 30GB : /
> First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
---
default=0
timeout=0
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
hiddenmenu
[Code].....
I just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).
Installation went fine, but upon the initial boot, I get:
Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)
I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from
we want to upgrade the kernel on Fedora 12 .but problem is , while doing 'make install' , it gives error as 'mkinitrd' is not available .which is required during 'make install'how to run 'make install' command on Fedora 12 without 'mkinitrd' utility.
View 9 Replies View RelatedI've never compiled a kernel before and I'm in need of the 2.6.28 kernel (two words: macbook aluminium).
I guess my biggest question is, will this guide work well for F10? I would hate to get half-way through it just to find out that F10 does something different than F08 or F09. Is there anything that you experts can see right away that would possibly be disastrous? If things do come to worse, I can simply select the previous kernel at GRUB boot right?
Or will the Fedora team be releasing the update soon through the package manager? Is there a way I can activate the development version and only get the kernel update?
I upgraded, using package manager, to the latest kernel (2.6.35.10-72); I upgraded also kmod-nvidia and kmod-wl to the latest version, and the upgrade worked.After restarting the PC, though, it wouldn't boot Fedora: it stops at:"setting hostname for <my laptop's name>:[OK]"then it simply hangs there. It doesn't move, it doesn't boot, it doesn't ask for a login and it doesn't let me use command line.I can, however, boot and run Fedora fine if I select the previous kernel from the GRUB menu.Anybody can give me a hint to find the cause of the problem?
View 2 Replies View RelatedMy new Thinkpad often overheat and shutting down suddenly.Today I download the F14 DVD and upgrade my F13 with it.
View 6 Replies View RelatedWhat are the precautions and procedure do i need to follow while upgrading the Kernel?
Please let me know the complete details of a procedure of upgrading a kernel in a production environment?
I have a tricky problem which I could soIve with a c program. I wrote one and found I didnt have gcc so I tried to install it. I was told I needed to install packages. I acknowledged and an error was generated gcc-4.4.2-7.fc12.i686 requires libgomp = 4.4.2-7.fc12 I try to install libgomp and go round again.
View 2 Replies View RelatedI installed kernel 2.6.32.9-67 via a yum update this morning. When I rebooted, the machine appeared to freeze with a single blinking underscore cursor. I used a live CD to edit grub.conf and reboot into the old kernel, which started normally. Later, I tried booting into the new kernel via grub again. After about two minutes, the blinking cursor is replaced by the normal boot screens and the machine works fine. This is on a seven year old PC with AMD Althon XP 2000+, 768MB RAM, VIA KT400 chipset and the NVIDIA 173xx driver from RPM Fusion.
View 6 Replies View RelatedI'm fairly new to linux Red Hat. We are running Rhel 3 on our VM's. We ran into a issue, (Bug 121801 - athlon-smp kernel does not support >4GB of RAM. what the stepos are to upgrade the existing kernel to the new i686? .
View 3 Replies View RelatedI have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....