Fedora :: Cannot Boot Into Usual Display Settings After Kernel Update
Jul 19, 2010
Since doing the update which included kernel "2.6.32.16-141 fc12-i686 PAE" I can no longer boot into my usual 1280x960 desktop. I can set it using NVidia settings but even though this offers to modify xorg.conf it fails to do so. I have tried running as root and it doesn't then give an error message but when I look at xorg. conf there is no section.showing any specific screen size. It worked ok before the update. In case it is relevant the video card is a Quadro FX1400 with KDE. Also the whole program seems rather unstable since the update.
View 10 Replies
ADVERTISEMENT
Jun 16, 2011
I 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.
View 4 Replies
View Related
Jul 14, 2009
I 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?
View 3 Replies
View Related
Aug 10, 2009
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?
View 12 Replies
View Related
Jan 21, 2010
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...
View 7 Replies
View Related
Aug 4, 2010
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
View 14 Replies
View Related
Nov 15, 2010
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.
View 5 Replies
View Related
Dec 19, 2010
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 Related
Aug 23, 2009
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
View 2 Replies
View Related
Dec 1, 2009
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.
View 14 Replies
View Related
Feb 11, 2011
I 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.
View 14 Replies
View Related
Apr 12, 2011
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 Related
Jul 12, 2011
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.
View 13 Replies
View Related
Mar 14, 2010
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.
View 9 Replies
View Related
Mar 17, 2010
After updating to version 2.6.31-20-generic, my desktop computer with an ATi HD4850 graphics card, using the fglrx driver, now won't boot to X. It goes through the boot process and displays the splash screen, but after that there is nothing on the screen. Choosing an older kernel version from GRUB doesn't make a difference. I don't even know how to diagnose the problem properly. I can boot into recovery mode and get to the command line, however, starting x from there only leaves me with a blank screen.
so the source of the problem is that I had installed the catalyst driver from amd.com, which needs to be reinstalled with every kernel update. I didn't know this in advance, so now I'd like a way to revert back to fglrx from the repos. Sadly, the community docs only seem to cover the graphical way of doing this, which is kind of useless to me at the moment.The ATi driver docs gave me a way to uninstall the catalyst driver using only the command line. So now I've booted back into Ubuntu and selected to install the fglrx driver from System → Hardware Drivers. However, now when I boot up, I get the message: "(EE) Unable to initialize PCS database
View 3 Replies
View Related
Nov 26, 2009
It appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.
View 3 Replies
View Related
Sep 4, 2010
I have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update.
Anyone else having this problem?
View 8 Replies
View Related
Mar 24, 2010
I'm not sure what caused it, but it happened right after running 'yum update'. It may be because it installed a new kernel, and there are now two kernels listed in my grub.conf and at boot; 2.6.31 and 2.6.32. System boots through a list of things it's starting up and stalls out at ATL or ADL or ADM maybe. It hangs there for a minute or so then flickers. This happens every time at boot. It's a bit difficult to post more information since I can't get past that part of the boot process, and I can't seem to be able to skip it either. It may be worth mentioning that this is a mini-itx motherboard. Intel Atom 330 1.6, 2GB DDR2, onboard GeForce 9400m. It's a zotac ionitx-a-u. I've installed a fresh copy of Fedora 12 lxde.
View 3 Replies
View Related
May 5, 2011
I'm trying to get my secondary display (DVI-Out) working on a laptop (built-in monitor & external display) and I'm afraid I made quite the mess of it installing the proprietary driver only to learn that my old ATI card is no longer supported and having to clean that up and reinstall the original distro driver!Anyways, I reverted back to the open source driver and all is ok. That is until I reboot. If I reboot with the DVI display connected then both displays are brought up in 640x480 res and look terrible.
What do I have to do to be able to leave my DVI display connected when I start up the machine and get it to render the way it does when I plug in the display after the machine is running?I suspect I need to create an xorg.conf file but these fancy modern Linuxes these days don't come with one (or maybe they no longer need it anymore).
View 2 Replies
View Related
Feb 23, 2010
Finally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-2.6.31.12-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
View 4 Replies
View Related
May 13, 2011
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies
View Related
Dec 31, 2008
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Code:
View 3 Replies
View Related
Jun 19, 2009
I've just installed the new Fedora 11 (just released) through a Live CD having 3 partitions created:
"/boot" - ext3,
"/" - lvm (part 1)
swap - lvm (part 2)
now, I want to add my new Fedora system entry to my "central" lilo.conf, resident on another linux distribution. So, i've done
[Code]...
my lilo fedora entry boots fine but... at the middle of "after boot" loading the system hangs and stops the usual driver detection, etc (normally, it hangs on the CDROM detection or USB 2.0 camera detection).
View 10 Replies
View Related
Jul 4, 2010
I recently installed Fedora 13 64 bit with KDE and everything works perfectly with the exception of display properties. I have two monitors which I have setup as multiple displays here is the result of xrandr when all is good.
Screen 0: minimum 320 x 200, current 2960 x 1050, maximum 8192 x 8192
VGA-0 connected 1280x1024+1680+0 (normal left inverted right x axis y axis) 310mm x 230mm
1280x1024 60.0*
1152x864 75.0
1024x768 85.0 75.1 75.0 70.1 60.0
832x624 74.6 75.0
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 66.7 60.0
720x400 87.8 70.1
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 433mm x 271mm
1680x1050 60.0*+
1280x1024 75.0 60.0
1440x900 59.9
1280x800 59.8
1152x864 75.0
1280x720 60.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
However when I log out and back in it reverts to cloned displays with xrandr output
Screen 0: minimum 320 x 200, current 1152 x 864, maximum 8192 x 8192
VGA-0 connected 1152x864+0+0 (normal left inverted right x axis y axis) 310mm x 230mm
1280x1024 60.0
1152x864 75.0*
1024x768 85.0 75.1 75.0 70.1 60.0
832x624 74.6 75.0
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 66.7 60.0
720x400 87.8 70.1
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1152x864+0+0 (normal left inverted right x axis y axis) 433mm x 271mm
1680x1050 60.0 +
1280x1024 75.0 60.0
1440x900 59.9
1280x800 59.8
1152x864 75.0*
1280x720 60.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
I'm have an ATI Radeon 3450 HD graphics card and I believe I installed the mesa driver as the proprietary one simply won't install.
View 3 Replies
View Related
Jun 17, 2010
I have just installed KDE 4.4 on Fedora 12 in addition to GNOME. The default Display resolution is the highest available. I changed it to a lower resolution. However, when I reboot, the resolution switches back to the default setting.
View 10 Replies
View Related
Aug 8, 2011
installed Fedora 14 on my desktop a couple of days ago. For the most part, it seems to be fine, but I've got a problem with the 'put display to sleep when inactive for' setting. From the desktop, I've tried going to system/preferences/power management, where I've set the display to go to sleep when inactive for 30 minutes - however, it instead goes to sleep after five minutes. The same applies whether I set it to 10m, 30m, 1hr or never.
Having looked online, someone mentioned gconf-editor as a fix to another issue, so I decided to give that a try as well. Under /apps/gnome-power-manager/timeout, I tried setting sleep_display_ac, sleep_display_battery and sleep_display_ups each to 1800 ("The amount of time in seconds before the display goes to sleep" - 30mins, by my maths) on the off-chance that the OS had incorrectly detected the power source, but the display again went to sleep after five minutes.
If it makes any difference, I'm not using a screensaver, and I think the kernel I have installed is 2.6.35.13-92.fc14.i686 (that's what's given in System Monitor). I've also tried running yum update, again just on the off-chance it'd fix something, but everything is up to date.
View 10 Replies
View Related
Feb 22, 2016
I've recently noted that the boot process in my Jessie installation is occasionally taking longer than usual, not dramatically as in "really hanging", but still noticeably slower, during which some messages are printed along the lines of
Code: Select alla starting job is running (2 of 5) and also after that, once lightdm (I'm using the MATE desktop) comes up the screen gets painted slower as well.
Unfortunately, once the system is up and running there's no longer trace in the logs (either traditional syslogs or journalctl) of such messages, however what comes to mind is that I've just recently enabled persistent logging in systemd: could this be the reason of such (occasional) slower boot process?
Other than that, what else could cause such behaviour? What should I eventually check to ensure things are OK?
View 11 Replies
View Related
Jan 7, 2011
Before I begin, here are some computer specs:
Toshiba Satellite C655
2 GB Ram
250 GB HDD
Intel Celeron 900 Joules / 2.2 GHz
64 bit
So, a little backstory. For christmas I got a new laptop with Windows 7, and while Win7 is a good operating system, I wanted to try Ubuntu and see which one I liked better. I installed the 32 bit version, because I understand people run 32 bit Ubuntu on 64 bit machines with out problems. For the first few days, everything was going amazing and I was pretty much using only Ubuntu (I had a dual boot with WIn7). One day, I opened my lid to find that the log in screen wouldn't appear, so I restarted.
I wish I could remember what error I got, but everytime grub tried to load Ubuntu, it wouldn't load, it just gave me some error (it may have been a kernel panic, not sure). So I went into windows, burned a windows repair disc, and fixed the MBR to be the windows boot loader instead of grub, then deleted the Ubuntu partition. Shortly after, I tried the 64 bit Ubuntu installation, and it wouldn't even boot up after the first boot (unfortunately, can't remember the error I got then either). So I repeated the MBR fix for Windows, and just stuck with Windows for a while. However, a new problem arose. Every now and then (and in time, more frequently) everything would freeze, for 1 to 2 seconds.
It couldn't have been my RAM or anything, the computer was blazing fast when I got it. The windows boot also took much much longer than usual, until it just wouldn't boot at all. I had my father (who's much more knowledgeable at computers) to do something, and he loaded into an earlier recovery partition ran a program called CCleaner, which supposedly fixed it. However, the problem was still there, and it got worse. I tried CHKDSK, it didn't do anything. The random freeze ups kept happing more frequently and became more and more bothersome. Eventually my computer just wouldn't boot up, it would just be a blank screen after the 'Toshiba' logo.
I eventually called Toshiba and they said that I apparently deleted the original recovery partition, and needed a Windows install disc, which I don't have so I have to buy one. Until then, I decided to just do a complete install of Ubuntu (64 bit), since I figured if I just did a complete fresh install removing everything, it would fix it. Well, turns out it had the same freeze up problem. I then tried a clean install of 32 bit Ubuntu. No luck, still periodical freeze ups, sometimes if the freeze ups are longer the screen will go grey. Before all this mess Ubuntu ran perfectly. I'm fearing that it may be my hard drive that's the problem, but I'm not entirely sure. So, is there anything I can do to restore my laptop to full health with out buying a new hard drive? Unless the hard drive isn't the problem, but I don't see what else is. EDIT: I tried memtest. Here are the results: It says 'Pass complete, no errors'. What do you guys think?
View 9 Replies
View Related
Jan 28, 2010
I am using GeForce 7600 GSNot using the Nvidia X driver message you know... I searched all over, and seen this problem on many searches but no resolve issues.I want to be able to connect my tv, I use to be able to when I first installed Ubuntu and now IdK.
View 3 Replies
View Related
May 2, 2015
After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
View 9 Replies
View Related
