Re: New Kernel Image

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 04 Feb 2006 15:11:07 -0500
Robert Locke <lists@xxxxxxxxx> wrote:

> On Sat, 2006-02-04 at 14:19 -0500, Ernest wrote:
> > New Kernel image 2.6.15-1.1830_FC4
> > is causing problems with gdm.
> > 
> > After boot:
> > the kernel is running, but gdm has crashed at the point where a user
> > login screen should appear.
> > All that appears is a blue background speckled with white dots. It
> > might be that gdm has not crashed, but the boot process has left
> > something in an incompatible state. 
> > 
> > It is possible to login to this machine, from another desktop, using
> > ssh. Once logged onto the fedora system and issuing the command
> > "gdm-restart", the gdm user login screen appears on the fedora
> > system console. 
> > 
> > What has changed between 2.6.15-1.1830_FC4
> > and 2.6.14-1.1656.FC4?  
> > 
> > Where do I start?
> > What information is needed?
> > 
> > System is an older Gateway PIII, 384MB RAM, ATI Radeon graphics card
> > in the AGP slot. 
> > X.org detects and configures this video card properly. The earlier
> > kernel worked fine, until the system was booted with  kernel
> > 2.6.15-1. Now kernel 2.6.14-1 exhibits the same problem. 
> > 
> 
> You might want to check the archives for the last couple of days.  The
> problem for some, like me, is actually with the new udev, that was
> installed along with the new kernel.  In fact, a simple terminal
> switch was enough to get my gdm login visible.  Ctrl-Alt-F1 followed
> by Ctrl-Alt-F7.  If it is the same as my problem, you may notice that
> the text mode terminal login is tiny print, something about probing
> and activating fb....
> 
> I fixed mine with an update that should be released shortly to
> module-init-tools.  You can get it early by doing the following:
> 
> yum --enablerepo=updates-testing update module-init-tools
> 
> Good luck,
> 
> --Rob
> 
I have made the update from "testing" and the problem still exists. The
computer is freezing and i have to hard reboot. the last messages in
the system log are:

ainit: Memory: Failed to release Semaphore
ainit: Error: No such file or directory
ainit: Memory: Failed to release SHM segment
ainit: Error: No such file or directory

so long...


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux