|
 Linux on PowerPC FAQ-O-Matic : X Windows :
something been murdered!?!?!? |
Whenever I try to start LinuxPPC, it gets throught the main sequence but then just before I get to the login screen, it says something has been murdered about 5 times and then says something like x isa respwning to fast and has been disabled for 5 minutes. What should I do?
watchenman@bigfoot.com |
That probably means that something is wrong with your XWindows installation. When the system boots, there is an entry in /etc/inittab (near the bottom) to try starting the XWindows package that is on your system. If the attempt fails, it immediately tries again..and again, and again, and again, until the system realizes something's wrong and shuts it up for a while.
Either try reinstalling your XWindows, or simply comment out (put "#"'s at the beginning of the relevant lines) the XWindows stuff in /etc/inittab, and it should be fixed.
fconcolor@internet-frontier.net |
I got the same error after I edited my /etc/X11/gdm/gdm.conf file and rebooted.
To fix the problem, I had to somehow get out of the default runlevel 5 (graphical interface), get into runlevel 3 (command line interface), change the /etc/X11/gdm/gdm.conf file back the way it was and then reboot.
Here are the specific steps that worked for me:
1) Power off computer
2) Power back on the computer and at the BootX window, under "More kernel arguments:", type in "linux 3" (without quotes)
(Note: During the boot process it will probably fix some problems on your root partition and that's fine. Instead of the error message or the graphical login screen you'll just be presented with a command-line logon prompt.)
3) Logon as root
4) Using any command line text editor such as pico, edit whatever file you messed with that caused the error (in my case it was the /etc/X11/gdm/gdm.conf file)
5) Enter the startx command and you should be back in business
Hope that helps.
Cheers,
Derek
derek@bbdo.com.hk |
According to /var/run/gdm.pid, gdm was already running ("pid") but seems to have been murdered mysteriously: is the error message I get repeatedly.
Yes, if you type "linux 3" (without the quotes) in the login prompt, you can login and run without Xwindows.
This problem has suddenly occurred after LinuxPPC has been installed on the Blue&White G3 for 5 days. Since it was running successfully, I have not messed with gdm.conf or anything else other than the files in my user account. Can I get Xwindows working without reinstalling anything? if not, is it possible to reinstall Xwindows only?
c.greenshields@ic.ac.uk |
Exact same problem on a Powerbook Lombard 333. everything was working fine, and then today (3 days after installation), I got this error message. I can boot with the paramater "single".
ktag@ireland.com |
I too had this problem. That is Linux boots on my iMac, tries
to start X and fails (several times) but than shuts up for 5 minutes.
I can login without X but cannot start it (gdm, whatever). All
complain about it already running.
I did not mess with any files either. This is 3 weeks after the
install.
Any ideas how to fix?
goldman@ucla.edu |
Ok, I had this problem with my Lombard (see previous posts). I used the new installer (1.1.3 or 1.3) and that's going to be 4 weeks without a problem... I even start to play with it (updated GTK, changed E-Themes... added more users). I still works. Hopefully that's the solution.
ktag@ireland.com |
I have just install Release 5 on a 7600 PPC, and have from the start received this message. I noticed that when I use a video driver (option on BootX) window. I can login and operate any manager, but, i receive mouse trails. When I say use NO Video Driver I get someting has been murdered error message. Still looking for solution.
kiaina@naoj.org |
To fix this on my B&W G3 Rev1, I excuted Xautoconfig.
I use the novideo check in boot X 1.1.3.
This can be done two ways.
1) Login as root after the murdering stops. Then execute Xautoconfig, then reboot.
2) Under Kernel options in BootX 1.1.3, type single.
After you get to a prompt type:
/usr/X11R6/bin/Xautoconfig
then reboot.
Next time you login you should encounter a red hat login screen. I got this solution off the linux ppc news group.
andyking@yahoo.com |
Another candidate for this problem is a mis-configured mouse. I accidentally
told the X server that my ADB mouse to a USB mouse, and I started getting
this "respawned too many times" problem
Solution: reconfigure the mouse with 'mouseconfig'.
James
fl_aggie@hotmail.com |
| [Append to This Answer] |
Problem Starting X Windows