Today I upgraded a few applications per the package updater and now I cannot boot with the latest kernel. It looks like the nvidia driver wouldn't work, I got a [FAILED] message, followed by two [WARNING] messages. Then the Starting atd message displayed and the screen flickered a few times, then froze. I reset with the button on the PC.
I was able to log in using an older kernel: 2.6.34.7-56.fc13.x86_64. The newer kernel that wouldn't load may have been 2.6.34.7-61.fc13.x86_64.
I looked in the boot log and it had the log from the successful log; but, not the one that failed.
Code:
[DnA@DellXPS ~]$ cat /var/log/boot.log
Welcome to Fedora
Press 'I' to enter interactive startup.
Starting udev: udevd[502]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/50-euvccam.rules:1
Booting into runlevel 3 and then issuing the $init 5, command leaves me this."binary handler for windows applications already registered" and the system hangs there.I yum removed wine, thinking that might be the issue, but that solved nothing.
Yesterday fedora automatically updated the linux kernel, and now it wont start entirely up. After the fedora logo has finished loading up the white, and it has turned into the real logo, nothing happens.However, i can boot into fedora with the old kernel via grub, so i guess it is related to the kernel update.
I just installed "f12" and the first thing I did was upgrade the operating system, so I went to System -> Administration -> actualziacion of software, after a while I put "install updates" but did not release any actualiazcion and threw me Error
Code: could not add package update for abrt-plugin-runapp-1.0.9-2.fc12(i686)updates: abrt-plugin-runapp-1.0.9-2.fc12.i686
I did my updates for F11 as I do often and afterwards booted in verbose mode to see anything different.The update was done 3 days ago and here's the log file..Starting NetworkManager daemon: ** (NetworkManager:1899): WARNING **: State file /var/lib/NetworkManager/NetworkManager.state parsing failed: (2) Error creating state directory /var/lib/NetworkManager: 13.[60G[[0;32m OK [0;39m]As noted, it says OK and the network still connects as usual but this warning msg didn't happen until the update.Is this a bug with the new Gnome Network mgr or could it be related to the new F12 release?I plan to upgrade or clean install F12 soon. Been using F11 since Aug.5 and I really like it by far the most stable Gnome of any distro I've tried. Was a KDE fan until now lol. I never liked the idea of KDE4.x but it is maturing. But-- most dists don't even offer tried-true KDE 3.5.10 anymore.ay need to fwd this issue with GnomeNetworkManager to the bug forums for Fedora/RHEL.UPDATE: I installed the updated SElinux Policy (testing) via rpmfind.net.selinux-policy 3.6.12.92.fc11.noarch.rpm and selinux-policy-targeted 3.6.12.92.fc11.noarch.rpm and the issue with the NetworkManager error went away!!I assume this package will be released as an update soon
I run F15 on my desktop PC and /var/log/dmesg is not being updated. I used preupgrade to upgrade from F14 to F15 on June 3. I boot F15 at least once per day. /var/log/dmesg has not been updated since June 3. /var/log/dmesg was being updated correctly when I ran F14. On f15, if I issue "dmesg" from the command line, I get the expected result. Is this a bug?
Is there a kickstart file somewhere or some other way or creating updated iso's for Fedora? I do a lot of installs testing stuff and it would be nice to create a new install disk every month or so. Cuts down on the update time.
Is there guide for converting ext3 to ext4 on Fedora? I use Fedora 12 which is regularly updated. How safe is procedure for data, I have only one ext3 partition on disk which has one ntfs and that ext3 partition (and also one small swap partition).
I've just allowed the update manager to update my system and now it boots as far as the login screen then immediately reboots, tried to use the installation disk repair system option but the only option it would allow was install system. anyone known how to boot into single user mode to try and fix this? or is re-installation the only option? I've discovered that hitting esc will booting gives me a more informative boot seems that udev is not loading looks terminal to me.
I set up my home server like 3 year ago on a Fedora core 4, I am running a NAT, firewall and FTP very smoothly on it. In the past 3 years, it has been doing perfectly without any modification/ upgrade. But recently, I just realized I might need a VPN server on it, but the recent release of OpenVPN doesn't support Fedora core 4 anymore, therefore I suddenly want to make an upgrade. I've read the articles/ manual for Fedora 13, yet I do not find any suggestion on how to upgrade to 13 from core 4.
how can I do an upgrade in the easiest manner as I don't want the server cease working too long (I need its NAT for my network).
I installed VirtualBox (and the virtualbox repo) a few months ago and it works brilliantly. The other day it informed me there was an update available. I downloaded: VirtualBox-3.1-3.1.2_56127_fedora11-1.x86_64.rpm from [URL]
Why doesn't yum update find these new versions of VirtualBox? Is the original repo file out of date? Here it is:
I had both 32 and 64 bit wine installed on fedora 12 and worked ok.But after I updated them from 1.1.29 to 1.1.36 from fedora repository, the 32bit wine stops working and gives the error message "wine: for some mysterious reason, the wine server failed to run." when I tried to start any windows programs which worked before.!
I am relatively new to Fedora and appreciate it is intended to be a bleeding/leading edge distribution but the continual requests to reboot the computer after updates is intrusive and seems rather odd for a unix operating system. It is often not clear to me why it is necessary when I look at the names of the items triggering the request.
I am getting no sound output on Fedora 12 (fully updated). If I switch to Windows Vista (which is also installed on the same machine), everything is fine. So, I guess I will have to configure sound from somewhere. Where should I start?
I came in to work today and updated my laptop, which is common for fedora to either update every week or bi-weekly. But now the system has a major delay that is making it unbearable, is anyone else experiencing this? I am running Fedora on a insprion 1525 with dual core pentiums, and 4gig ram.
I did my update back when F13 was first out. A lot of the F12 packages are still on the machine. Should I be concerned. My latest thing was dealing with the Kmod-Nvidia packages left behind from F12. Someone suggested removing them and once I did my updater did its job perfectly.
So, the question is do I need to remove all the F12 packages or should I wait until there is another conflict? Secondly, if I should remove them, is it a search and destroy mission or can I simply nuke them all in one grouping?
I'm currently running F11 x86 and want to update to F13 x64, so a new drive and fresh install and copy all the config & data from old drive. and Prey, a lot....I'll be installing F13 x64 later this weekend, But F14 will be out in a few months then F15 and so on.I've tried the upgrade option (x86 to x86 in the past) on the install dvd but it doesn't work and I wind up with a broken install and have to do a fresh install after saving most of the import data and config files, but I usually missing something and get hosed. Part of the problem could be using Nvidia drivers for video and several applications installed from several different repos.I've never been able to safely uninstall the Nvidia driver and still have a working system, let alone upgrade to a newer version and still get a visible desktop.
I was thinking that couldn't I just edit a yum file and point it to a new repository and have it upgrade the machine with out all the fuss?I followed a procedure once or twice on how to do a inplace upgrade, but that didn't work either. I'd like to keep the machine running the latest bits, but with all the pain and suffering I need a simpler method to do it. Is there a procedure or process I can run or follow to keep Fedora in sync with the latest release with out having to continuously swap disks, reinstall and copy critical data files?
Everyone once in a while Google drives me nuts, this is one such case.Everything I have found from Fedora or Red Hat on stateless or even diskless implementations is old as dirt. Based on Fedora Core 4 or 7. Where is the updated or current documentation for Fedora 13 or 14? With everything going to clouds one would think stateless would be a hot topic again?At least diskless should be right?
I'm trying to run some updates that require xulrnner to be updated. It appears I have xulrunner for f14 and f15 installed and the f14 one is in conflict with the update. I don't know what xulrunner is for and I'm hesitant to just do a yum remove of the f14 one as I've learned that I can cripple or kill my system if I do this to the wrong programs.
I had to uninstall f10 from my system because it would lock up my system anywhere from 1 to 5 minutes into using it and noone could tell me why.
NOW, I put 9 back on my system and after it updates everything, it locks up again. it does give me the option of the new kernel and the original install's kernel and if I choose the original to boot with, I don't have any problems.
SO, is there any way to fix it, OR to exclude the kernel and initrd from being updated?
I've been having trouble getting the latest kernel to update, due to an error resolving dependencies. I've used yumex to remove old versions of kmod-nvidia that were fc10 specific, and gotten past that. However, when I updated the kernel, yumex reported that mkinetrd failed. Checking, the newest kernel listed in grub.conf is the one I'm using, not the one I just installed. What do I need to do to get the updated kernel properly listed and ready to use?
Before going to sleep I just closed my laptop without shutting down, but the next morning when I unlocked I had no sound. Does anybody see something suspicious in the updated packages?
I've just recently started using Fedora again and have a question about BOINC.I see that Fedora 13 is using 6.10.45, but the latest recommended release is 6.10.56.What is the timing on updated RPMs for new BOINC versions? Or is there a guide to updating manually, which I've been unable to locate?
