Bug 21939
Summary: | 'gdm murdered' causes reboots, system not able to stabilise | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | shivaji apte <shivaji_apte> |
Component: | gdm | Assignee: | Havoc Pennington <hp> |
Status: | CLOSED DUPLICATE | QA Contact: | Aaron Brown <abrown> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | giulioo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-12-13 09:47:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
shivaji apte
2000-12-08 09:06:29 UTC
Hmm. Not sure what linuxconf does if you choose that, I'll ask. In the meantime to get running again, type "linux 1" at the boot: prompt to start in single-user mode, edit the file /etc/inittab, change the line "id:5:initdefault:" to have a 3 instead of a 5. My initdefault is 5. Card is i810. I frequently get the "murdered" message when I switch to a tty and then try to return to X. Sometime X is there, sometime it's not and I get a new X login and all my open apps are vanished. Sometime X is F9 instead of F7. I don't know if my problem is due to gdm (as the error message seems to indicate) or to XFree4.0.1 having problems after a tty switch (like other bug reports suggests, ie bug 18651) I have found why using Linuxconf causes problems for me. Basically, the default X-server that came could give only 640x480 resolution as it couldn't detect the video ram on my i82815 based agp card. So, I had download the X-server from Intel's site (its XFCom_i810) and linked /usr/X11R6/bin/XF86_SVGA to it and also linked /etc/X11/X to /usr/X11R6/bin/XF86_SVGA. Then, everything was fine. However, when I used Linuxconf again, it resetted my custom settings and hence I was getting the problem. |