Freeze during GDM

[Nemros]

I've been a RH and Fedora supporter for a long time but for some time it's like the quality of the releases has been going down.

I was happy to install FC10 on my laptop, was looking forward to it. Did the install, everything went fine and bootup and login were ok. 1-5 minutes after login complete freeze. After a doing some research (and having an ati card) I found nomodeset to be the solution for my problem.

It was ok because it worked. Then I found another stupid evolution bug when importing my stuff which I found a solution on the ubuntu forums.

Now my current problem is that fedora did some updates yesterday and today I can't even login to GDM. With / without nomodeset GDM freezes just as it starts.

Now I don't have a rescue CD with me and I need to access my files and work. I can't even do that. Kerneloops or how u call it warned me about sending some reports to kernel devs etc etc etc.

I'm really dissapointed in the quality of the release. I'm now forced to work in Windows. When linux doesn't work go with windows. What's the point in having a free OS if it doesn't work? (And arguements about fedora being bleeding edge don't count)

[rustyprivate]

calm down sir, boot in single user mode, read the logs
paste it in here

[Nemros]

I'm calm, just dissapointed.

There are no logs, the GDM and Xorg logs are empty for today. Do you need any other logs?

[rustyprivate]

then start gdm manually and provide us with console's output

[Nemros]

Unfortunately I know how to get around linux but I'm not a guru and I don't know everything.

I've started single mode by adding nomodeset single in grub and then tried to run gdm manually by simply running: gdm. I got an error: Could not connect to system bus.

However i did switch to my normal user and tried to start gnome (startx). This command actually did make Xorg generate a log which I have attached.

Now what I found curious is that I couldn't use my mouse or keyboard (no input) but gnome was still loading (animations and hdd led was on) and then nothing. I cannot test remote access (see if it is a freeze).

My best guess at this time is that somehow the input events (i know the switched them to some new thing) might be broken. I'm not sure.

If you want extra info from me just type the commands you want me to run and I will get you the output.

Thanks

Xorg.zip

[rustyprivate]

under root type
/etc/init.d/gdm start

if it fails gimme the output and then try this under USER

nano .xinitrc
then paste this:
gnome-session

then close editor and save file

then type this under USER
xinit

if it fails gimme the output

[Nemros]

I can tell you /etc/init.d/gdm <- does not exist, it was the first thing I've tried to do to start gdm.

I will try the others

[Nemros]

You can officially kill me

I did > xinit > out.txt
I tried even > logsave out.txt xinit

Nothing. The output was always empty. I did get some output on the screen. And each time I ran xinit it did the same thing as startx command and it froze.

The only explanation I have is that keyboard and mouse events don't occur in gdm or gnome. Especially since my mouse was frozen, keyboard the same and it was loading and starting gnome... which means overall the laptop was working.

I think I will have to wait 1-2 weeks until a newer patched version of whatever is wrong will be posted.

Thank you for all the help you've provided so far.

[pedromatiello]

We might be hitting the same bug.

Sometimes it won't even let me have keyboard input on init 3. Even plymouth boot screen gets locked.

I reported this, but there's no reply from the developers so far.
https://bugzilla.redhat.com/show_bug.cgi?id=474357

This is a pity. F10 is very nice. I hope it doesn't take long to stabilize on my hardware.

[Nemros]

I've managed to obtain some log files for gdm and x11. I've attached them. I hope someone can help me.

x11.txt
greeter.txt

[ajacques]

I'm having the same problem on a Thinkpad X31 following a recent yum update. This is Fedora 10.

The symptoms are the following. The machine boots normally but when GDM loads, one sees only the outline of the login window on a dark background. The mouse moves, but impossible to change virtual terminals and Ctrl-Alt-Backspace does not restart the X server. I have to turn off the machine at that point.

The last message in Xorg.0.log is fifty or so lines of "(EE) RADEON(0): Idle timed out, resetting engine..." Of course I'm not too familiar with which logs one should consult when the problem is with X or Gnome.

If I boot into runlevel 3, I can log in and run xinit. Interestingly enough, that starts my alternate window manager -- even opens an xterm -- but I still can't do anything. It accepts no keyboard input at that point. If I use root privileges to switch to runlevel 5, I can see GDM starting but it gives the same symptoms as if I booted directly to runlevel 5 -- the frame of the login window is drawn, with no other text or graphics, and keyboard input is rejected.

[vuurst]

Hi,

I am now busy installed F10 for the thith time. It wors correctly when installed, it boot correctly. But when I have updated F10 with yum from fedora and livna, the boot stalls at the screen saying Fedora 10 in white, on the moment GDM is about to start....

If someone can tell me how to prevent this from happening.... I would be very pleased.

John

[ajacques]

Christ... I reinstalled Fedora 10 with the netinst image on CD and I guess that the installation uses the updated files... It's broken on the new installation too. Why did they have to go and do this...

[Algernon]

I'm seeing this on two systems.

First was my laptop (IBM X31 like previously mentioned) which is a fresh install to Fedora10. After today's update I'm unable to log into the system.
http://nurmenniemi.homeip.net/mythwe...Mobility_M6_LY

Another is an upgrade from Fedora 9 to F10 which I started before I noticed these problems. The symptoms are identical to the laptop.
http://nurmenniemi.homeip.net/mythwe...g.Intel_82845G

I'm able to login via ssh from a another system, and the servers seems to be fine on the machine.

any clues would be appreciated...

Another error here...
https://bugzilla.redhat.com/show_bug.cgi?id=477140

[Algernon]

Update to the situation for these two systems I have available.

by creating and adding the method described here
https://bugzilla.redhat.com/show_bug.cgi?id=469292

The specific comment is #20 where by adding a options to xorg.conf the behaviour changes and this improved the situation for me. There might be a performance hit involved with this but almost anything is better than the previous situation...

Relevant lines in xorg.conf are here

Section "Device"
	Identifier  "Videocard0"
	Driver      "radeon"
	Option      "AccelMethod" "XAA"
EndSection

Naturally in the case of the intel driver line is changed to point to "Intel"

Don't know why but this seem to be the temporary solution for me...