Re: RH 8.0 X server reconfig problem...

[Andrew Mathews]

tom wrote:

Greets Andrew;

Thank you for your time.  I really appreciate it.

Andrew Mathews <[EMAIL PROTECTED]> wrote:

tom wrote:

What is the next step to trouble shoot a frozen
keyboard and mouse when running a Xserver?

I'd highly recommend using a journaling file system, either ext3, reiser, or best of all XFS. An iso image of the RH 8.0 XFS installer is available from SGI at: ftp://oss.sgi.com/projects/xfs/Release-1.2pre1/installer/forRH-8.0-SGI-XFS-1.2pre1.iso

Lonnie also mentioned this. You think this the cause for the X server or keyboard to stop functioning?

<snip>
No, but if you're having to do hard resets, it will definitely provide a much higher level of safety for your system and data. Eventually, running ext2, you will have an fsck failure that may not be recoverable.

Tried. Got python errors for gnome-session, and startkde gave
me no display errors. 6 lines, which all amounted to something like the following;

xsetroot: Unable to open display ''
xrdb: Can't open display ''
xset: unable to open display ""
ksplash: cannot connect to X server
kdeinit: Aborting. $Display is not set
Warning: connect() failed: : No such file or directory
ksmserver: cannot connect to X server
Error: Can't open display:
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!

<snip>

Try /sbin/telinit 5 (This will start your default desktop manager) This is located in /etc/sysconfig/desktop and is either DESKTOP="GNOME" or DESKTOP="KDE"

I've observed that the Kudzu daemon disables the ps/2 mouse configuration on boot up. I reselect to NOT drop the configuration.

I'm attempting to disable this daemon as well now.

<snip>

Try setting /etc/sysconfig/kudzu to SAFE=yes. This will disable serial ports, monitor, and ps/2 probes.

performed this for all service levels 1-5.  Something still activates
after 2 minutes which disables keyboard if left inactive.

ps -ef show me that the kernel itself is running the apmd daemon.
It's process is 3, listed as kapmd.  Maybe a RH enginneer compiled
in the Power Management features for 2.4.18?

Normal I believe.

<snip>

Only other observations I can make at present time;
I observed the following for the unicode_start in
/var/log/messages ...

<Date><Time> localhost rc.sysinit: Loading default keymap succeeded
<Date><Time> localhost unicode_start: ^[%G
                                     ^^^^^^^  I actually get these

<Date><Time> localhost rc.sysinit: Setting default font (latacyrheb-sun16)

Eesh. Whatever you do, DON'T run /usr/bin/unicode_stop as it will make your console non-functional.

===========

I'm still reading the manuals, and they don't mention anything
other than using the GUI tools ( sigh ).

What do you suggest I do next?  I'll take any suggestions...

<snip>

I really suspect that it's something such as artsd, klauncher, or something that isn't related to apmd. Try to tail -f /var/log/messages, & /var/log/XFree86.0.log to see what the last entries are before the lockup. If rhnsd is running, kill it too, as it's unnecessary and has caused me problems before.

--
Andrew Mathews
---------------------------------------------------------------------
4:30pm up 3 min, 2 users, load average: 0.10, 0.17, 0.08
---------------------------------------------------------------------
Surprise your boss. Get to work on time.

_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users