[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ppc
Subject:    Re: Xpmac and KDM/XDM Problem
From:       "Andrew B. Arthur" <arthur99 () global2000 ! net>
Date:       2000-01-02 21:30:08
[Download RAW message or body]


On Fri, 31 Dec 1999, you wrote::
 
> Try starting Xpmac and once you get that funny dark blue screen, you
> Apple-Control-F1 key combination to switch back to the console and please copy
> whatever error messages appear and forward them to me or the list.

The error messages don't appear in the console that I started it in (all I see
is [root@localhost /root]). Plus even if they did on my machine I would only get
about 1/2 second to read them.

> That should hopefully give us some hint about what exactly is messing up.

It never even occured to me to check /var/log/messages to find the error, since
it wasn't printing it in error into the console where kdm (as root of
course) was started nor in ~/.xession-errors. But here it is (and some stuff
before and after in case it helps), taken verbiam from that log file:

Jan  2 15:50:00 localhost PAM_pwdb[408]: (su) session closed for user AArthur
Jan  2 15:50:14 localhost PAM_pwdb[653]: (su) session opened for user AArthur by \
                root(uid=0)
Jan  2 15:50:27 localhost PAM_pwdb[653]: (su) session closed for user AArthur
Jan  2 15:52:38 localhost PAM_pwdb[373]: authentication failure; LOGIN(uid=0) -> root \
                for login service
Jan  2 15:52:39 localhost login[373]: FAILED LOGIN 1 FROM (null) FOR root, \
                Authentication failure
Jan  2 15:52:41 localhost PAM_pwdb[373]: (login) session opened for user root by \
                LOGIN(uid=0)
Jan  2 16:07:21 localhost PAM_pwdb[820]: (su) session opened for user AArthur by \
                root(uid=0)
Jan  2 16:10:29 localhost PAM_pwdb[820]: (su) session closed for user AArthur
Jan  2 16:11:01 localhost kdm: extra arguments on command line:
Jan  2 16:11:01 localhost kdm:  "--nodaemon"
Jan  2 16:11:01 localhost kdm:  
Jan  2 16:11:04 localhost kdm[860]: Server for display :0 terminated unexpectedly: 1 
Jan  2 16:11:17 localhost last message repeated 7 times
Jan  2 16:11:17 localhost kdm[884]: IO Error in XOpenDisplay 
Jan  2 16:11:17 localhost kdm[860]: Display :0 cannot be opened 
Jan  2 16:11:18 localhost kdm[860]: Server for display :0 terminated unexpectedly: 1 
Jan  2 16:11:25 localhost last message repeated 4 times
Jan  2 16:11:25 localhost kdm[899]: IO Error in XOpenDisplay 
Jan  2 16:11:25 localhost kdm[860]: Display :0 cannot be opened 
Jan  2 16:14:51 localhost syslogd 1.3-3: restart.

Here is what startx gives me normally using Xpmac (with -mach64 and
-fp "unix/:-1","unix/:7101"):

Xpmac / X Window System (X11R6.3)
Release Date: October 28, 1999

Running in mode=0 depth=16; req mode=0 depth=0
Using VT 7
Mapped frame buffer (physaddr 0x1800800 size 0x180010) at 0x30027800
Warning: Mach 64 base assumed at 0x817ffc00
Mach64 detected. Mapping register... 
Mapped physaddr 0x817ffc00 size 0x1000 at 0x30015c00
Mach64 successfully mapped. Starting acceleration...
mach64CreateGC:Unsupported depth: 8. Using cfbCreateGC instead.
mach64CreateGC:Unsupported depth: 24. Using cfbCreateGC instead.
kpanel: waiting for a windowmanager
kpanel: ok, commencing initialization

waiting for X server to shutdown.

[root@localhost /root]#

I noticed that /var/log/xdm.log was blank. Below is the dmesg video info:

MacOS display is /bandit/ATY,264V             flags are as for the -l option
Using unsupported 1024x768 ATY,264VT at 81800800, depth=16, pitch=2048
Console: switching to colour frame buffer device 128x48
fb0: Open Firmware frame buffer device on /bandit/ATY,264V             flags are as \
for the -l option

Here is the kernel info:
Linux version 2.2.14pre9 (paulus@argo.linuxcare.com.au) (gcc version egcs-2.91.66 \
19990314 (egcs-1.1.2 release)) #11 Fri Nov 26 15:07:00 EST 1999

The kernel I built my self (version 2.2.14pre14, I think) (the version from
rsync linuxcare.com.au::linux-pmac-stable) has the same problem.

Thanks Again. I feel stupid for not including any log files, it didn't occur to
me at first to check/grep around /var/log/* for relavent info. I hope this
helps.

Thanks,

Andrew B. Arthur
arthur99@global2000.net
AIM: aarthurppc


** Sent via the linuxppc-user mail list. See http://lists.linuxppc.org/


[prev in list] [next in list] [prev in thread] [next in thread]