I updated my fedora 11 kernel version 2.6.30.5-43.fc11.i586 and when I restart, it doesn't boot. Here's how I updated. What I wanted to do was to install manpages-dev. So I go to system-> Administration-> Software sources and tick the last (fedora rawhide) and run yum update. I tried to boot from old kernel 2.6.29.6-217-2.8.fc11.i586 but still the same. I'm afraid I won't be able to boot fedora.
View 9 Replies
After I have updated fedora 12, I have had to reboot but every time when I boot fedora I get a forced filesystem check. I get that the system was 40 times mounted this why it must be checked, when it get to 84,6 or 84,7 it reboot. How to cancel the check.
View 6 Replies View RelatedI have successfully installed Fedora 12 today on a Dell M6400 from a live usb stick. Everything went very well. After the installation I rebooted, and updated the system. Then rebooted again, and now I get this message. No bootable partition in table. Apparently something in the update is broken... Is there a buggy kernel version I should be aware of? Should mention that I have two disks in a hardware raid 1. I left a none-bootable USB key in the computer when rebooting.
View 1 Replies View RelatedI have been running FC13 for some time now without any problems on my HP dc5800 Microtower. Recently I ran a software update, and when I rebooted the machine I got a blank screen with only a blinking underscore in the upper-left corner. Rebooted several times to no avail. I thought perhaps I had made a mistake, so I just reinstalled. I have tried reinstalling several times now with both 32-bit and 64-bit FC13, each time with the same result: everything works fine up until I install software updates; then after the next reboot I get a blank screen with the blinking underscore. I see the POST screen, and then it just goes blank. It doesn't seem to respond to any keyboard/mouse input; I eventually have to hold down the power button to make it power off.
View 5 Replies View RelatedI am new to linux but have install fedora 14 twice on my computer now and about to go for three. The first time I installed it, ran the updates using yum update, downloaded and installed wireless driver b43 then tried to change boot order to boot to win 7 first and thought I messed it up when I did that. It took over 20 minutes just to boot up and log in and about 10 minutes just to open a terminal window. So re-installed it had a friend who is very good with fedora change the boot order, then did the yum updates and wireless driver install again today. Now when I reboot my computer it no longer automatically boots to windows, and does not even give me the option to boot to fedora.
I believe it's the grub menu but the boot menu that I used to get if i wanted to change the boot to fedora is now a different color (white & black) and doesn't list the option to boot to fedora. Currently I do not have the DVD I used to install and was hoping there was a way to fix it without re-installing it. The boot menu does give me the options of hitting 'e' to edit something or 'a' to edit the kernel arguments, and I have no idea what either of them are. But the 'a' does not do anything, 'e' brings me to another menu option with chainloader and rvnotify or something similar. And there are more buttons to edit stuff and 'b' to boot from the choices but they both boot to win 7 not fedora.
I took a perfectly functioning Fedora 10 install on my Dell D410 laptop and did "yum update" on it. Now when it boots, all I get is POST and then the single word "GRUB" on the screen. What'd I do? How do I recover?
View 3 Replies View RelatedI just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
What can I do?
Everything seems to be fine and everything boots up in fedora 11 still; However, the recent updates to my system really hangs my boot time up and it takes a while for it to boot strangely... don't know what exactly could be going on really, but it's doing this for the current and previous kernel of F11. I'm on Fedora 11 32bit x86. My log file: [URL]
View 14 Replies View RelatedIt seems today's kernel update has given a few people some difficulty - but my symptoms seem pretty unique.
* I go through GRUB normally. I 'esc' out of plymouth, and watch my services start. I get message 'mdadm: No arrays found in config file'. Don't remember seeing this before, don't have any RAID devices.
* Next, my file-system gets re-mounted in read-write mode (don't know if this is normal or not). Then, my services begin to start-up. My last service is 'crond'. All services start normally. When it gets to 'crond' the [OK] status is never reported. Visually, the screen flickers a few times, stops, then nothing happens. I can type characters though, and they do show up.
* If I then shutdown my computer by pressing the power button, the shutdown procedure begins. 'crond' shuts down successfully (indicating it started just fine), and the computer goes down normally.
* I don't believe this is an NVIDIA issue. I rescue-moded and changed my XORG.conf to the basic VESA driver to eliminate this possibility.
* Worst of all -- No older kernels work now either. They behave in the same way. When I try to boot to other run-levels, no luck either. This tempts me to think the problem might be file-system related and the re-generation of grub.conf threw something off?
The girlfriend did an update a few nights ago. Besides removing her NVidia drivers, it also installed kernel version 2.6.27.29-170.2.78.fc10.i686.
That kernel was causing problems. Now it won't boot at all. How do we remove that kernel altogether?
If we remove it, would simply doing another update from the previous (still working) kernel just try to reinstall that bad kernel?
My computer is a dual boot between windows xp and fedora 12. I am using grub and my first boot selection default was windows. My computer has the following specs:
-AMD athlon xp 2400+ at stock speed 2.0Ghz
-640mb of ram, 2x256mb, 1x128mb, all 266mhz speed
-250gb SATA harddrive, seagate
-Nvidia GeForce 4mx AGP video card
-ASUS A7V600 rev. 1.00 motherboard
I booted up fedora 12 today(12/17/2009) and did a fedora software update (task bar->system->administration->software update). It said it found 94 new updates release on (12/16/09), so click update, and the computer did its updates and reboot. Now my grub boot loader is messed up (boot default was windows, now its not) and random apps crash, like gedit, so I can't edit my grub settings to boot to windows and linux is now useless because apps keep crashing. As of right now I am using another computer to post this. I know one of the updates was a Fedora 12 kernel update. And the new updated fedora 12 "automatic bug reporting tool" does not work any more, after the update.
Some ideas I have, but I have no idea how to do them:
-uninstall last updates
-repairand/or restore bad files
This is important because I need to use some of the apps/programs for work.
I've run today command: "sudo yum update"
and I've noticed that the new kermel have been installed (2.6.31.12-174.2.3.fc12.x86_64).
After that installation .. my camputer has several errors while booting and it doesn't want to start. So while booting I can see Code...
I ran the update through yum (replicated results twice) and whenever I boot to the new kernel it either freezes on the F logo or screen goes black right after f logo. No commands work whatsoever (tried em all). I can boot to an older kernel (2.6.33.3-85.fc13.x86_64). the ones that fail are: 2.6.33.6-147.fc13.x86_64 and 2.6.33.6-147.2.4.fc13.x86_64.
The Fedora error system gave me a bug report I submitted, here's what I got:
Package: kernel
Latest Crash:Tue 03 Aug 2010 09:46:33 PM
Command: not_applicable
Reason: BUG: unable to handle kernel NULL pointer dereference at 00000000000005b8
Bug Reports:Kernel oops report was uploaded
I was having problems performing an update yesterday that failed on dovecot dependancies and after a few tries I removed dovecote (it wasn't being used) from the installation and tried again. Everything seemed to be going OK then the update (about 160MB) hung and the screen went black a few times and I think then shutdown automatically. The PC then fails to reboot and displayes the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" I have tried to get the PC to boot with the super grub disc but without success (probably my in experience) I have also tried a suggestion from one of the forums to start the PC with a live CD and typed su -c 'grub-install /dev/sda at the terminal again without sucess. I have looked at the files with the live CD there are grub, menu and kernel files there (some are in lost + found, b ut don't know wheer these should be so have not changed anything.
Is there an easy way for the in-experienced to repair the boot process ?
The PC is a pentium 4 running Fedora 13
There is a 200MB boot partition formated as Ext3
and a 19GB partition formated as a LVM with Ext4
There is a CD drive but no DVD
Everything has worked OK for the past year through two online upgrades.
After updating my kernel from 2.6.34.7-56.fc13.i686 to 2.6.34.7-61.fc13.i686 I can't boot anymore. The error message says: "No root device found Boot has failed, sleeping forever."
I'm booting from 2.6.34.7-56.fc13.i686 now but I would like to sort this thing out. What should I do? File a bug? I never did that, so I don't know where to go.
After running update last night from 2.6.35.9-64 to 2.6.35.10-68 my laptop fails to start. Boot process goes most of the way to startup and then hangs just before login screen. Not sure what else to give as far as info.
View 12 Replies View RelatedI just ran yum update, which installed about 47 packages. When I try to restart, the Linux boot loader is not being read. Apparently, the old Windows 7 boot loader that came installed on this machine is still somewhat intact on the hard drive, because when it boots, it tries to start Windows. I put in a Red Hat 5 rescue disk...but the rescue disk can't find a Linux file system on my hard drive.
Fedora 13
Dell Latitude E6500
Also...the disk is encrypted.
(Not the swap or /boot)
However, I have had this issue with Windows computers as well, I just don't know how to beat around this problem and fix it with the new OS.
For starters, I have a Sony Vaio laptop (VGN-NS295J) that's running a ATI Mobility 3430 Video card on F14 64bit.
From the beginning, my device was not recognized with a good driver, so I started jumping through hoops reading forums of how to properly install this driver and get rid of the on board video. After I was successful (so I thought) I rebooted my system, and now after Fedora finishes loading the operating system, the screen goes gray and I can start typing in whatever I want.
I can still log in by Ctrl+Alt+F2 or whatever it is, but I'm stuck to text, and don't know my way around well enough yet.
I believe the issue is that it's trying to treat my laptop as two moniters, or defaulted my monitor incorrectly perhaps? At least this is what always happened to me in the past with Windows.
I just fresh installed F14 today, so I don't have anything of importance on the HD.
*UPDATE* Okay, so i've figured out hitting escape lists two versions of Linux there off the boot. The top one repeats the message I've just given, and the second one will go to the Fedora screen right after the boot (where it fills the emblem diagonally), then the screen flashes like it's starting to run my video card, and the screen goes black.
Just did the most recent set of updates late yesterday (kernel and Nvidia). Since the update I cannot get to a login screen - just blinking cursor. In fact the cursor blinks for a bit then disapears only to reappear as if there are repeated attempts to complete a process unsuccessfully.
The update replaced the xorg.conf. I tied a couple of revisions, inlcuding replacing it with the earlier working xorg.conf. No luck.
Hardware is MSI K9N6GM board with Nvidia Geforce 6100 nforce 430.
I have recently updated my Fedora 11 installation which replaced my older 167 kernel with the newer 217 kernel. However, the 217 kernel will not boot completely. It will show the splash loading screen, and then will switch to a rapidly blinking cursor. This cursor blinks for about 5 seconds and then disappears. I can access terminals using ALT+F2, etc. I can log in to these terminals, but init commands do not complete (something about a binary handler). I'm not sure if something is conflicting with an update to X or what is wrong. The most recent kernel that I managed to get to work was Kernel 167, however I cannot find this kernel for download.
Sys info:
AMD Athlon 64 X2 4800+
3GB RAM
nVidia GeForce 8600GT with proprietary drivers
320GB Hard Disk with windows and linux partitions
Fedora 11 32-bit i586
I have a new Fedora 11 install with all updates working on my: Dell XPS M1330 laptop with nVidia GeForce 8400M GS
I wanted to install compiz fusion on Gnome so I followed these step by step instructions from:
Fedora refused to boot, locking up during the process.
Here is what happens...
After updates I had 3 options at boot up:
A) If I choose the TOP one (newest) it will boot up to a black screen and nothing else, I get a white block which moves with mouse. I cant get a shell and any key I hit just echoes back...ctr-alt-del will result in normal shutdown process displaying.
If I watch the services start (F1) I see all -OK- except: nvidia.ko: Driver already enabled
The boot continues with all OK until it gets to:
STARTING atd:
at which time the screen flashes for about 7 seconds and locks up.
B) If I choose MIDDLE boot option and watch the boot process I see most services start OK except:
-[OK]
Checking for module nvidia.ko [FAILED]
nvidia.ko for kernel 2.6.30.8-64.fc11.i686.PAE was not found [WARNING]
The nvidia driver will not be enabled until found [WARNING]
Driver already disabled
-[OK]
Then the services continue on with [OK] until a few seconds later the screen halts with a mess of colors and symbols on screen and system stops booting. Any key pressed simply echoes back with no other result. Again ctrl-alt-del refreshes screen and shutdown of services proceeds normally.
I tried to update my f12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK but when I restated my computer it spit up an error and wouldn't boot"Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory"Luckily the old kernel still works.
I do have the disk encryption set, could this be related to that? Updated my laptop today with the xx.6-145.f12.PAE kernel and now it's borked to. Same problems.12/07/2009OK today's kernel update seemedto fix the problems and now all is well, execpt for my inkscape not working problem. But I put ubuntu 9.10 in a VBox and it works. So for now that's my work around.
After a recent "yum update", my laptop screen locks up during graphical boot. I use rhgb on the kernel line. The container on the screen fills up with charge and then the screen locks. I have to use the power button to reboot. If I press ESC when the boot splash appears (i.e., boot in text mode), it works.
If I set plymouth to "details" mode using
$ plymouth-set-default-theme details --rebuild-initrd
It boots up correctly. This is equivalent to a text boot screen. I doubt whether it is a video driver problem. I reinstalled the nvidia driver and it is working. I also reinstalled plymouth and plymouth-themes-*.
I have a dual boot of fedora 12 and vista. Everything worked fine until I tried to install a new booting theme. Here is what I did:
su -
yum install plymouth-plugin-{fade-throbber,label,space-flares,throbgress,two-step}
yum install plymouth-theme-{charge,fade-in,solar,spinfinity}
[code]...
Just finished a security update, (Fedora 12) and it said I had to restart the computer to have it take effect. When I restarted, all I got was the "Compaq" logo....forever. No Grub2 (it's a three system set up), no bios, just the brand name of the box. Even worse, when I tried going at it with a live cd, the same thing; the bios never loads, so no live cd fix.
View 6 Replies View RelatedI am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
Hello, i recently update the kernel in fedora through the GUI update manager and after restarting the new kernel wouldn't boot and i had to reboot into the old one. it freezes right after Plymouth finishes and the login screen should show up it just completely freezes, i do have proprietary nvidia drivers could it be that?
View 9 Replies View RelatedI upgraded the kernel of my machine with a yum update, and now it will not boot. I am running Fedora 14 on a 64 bit machine. I really really need it to boot. Help!
I did Ctrl+Alt+F2 and managed to log in. I have kernel x86_64 2.6.35.12-90.fc14 installed. How do I log in as usual? I never get to a login screen.
I have just updated my kernel to version 2.6.38.8-35 in Fedora 15, it now refuses to boot that kernel. I just get a lot of text on the screen and nothing happens. I can ctrl-alt-fn to get to a prompt, but I do not know how to fix the nvidia problem.
When I edit Xorg.conf and replace 'nvidia' with 'nv' the new kernel boots but only to fallback mode, trying to then re-install the nvidia drivers shows them to be already installed and I can get no further.
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.
