From owner-freebsd-stable Sun Dec 26 9:45: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from green.excel.net (excel.net [156.46.156.2]) by hub.freebsd.org (Postfix) with ESMTP id BACBB15063; Sun, 26 Dec 1999 09:44:56 -0800 (PST) (envelope-from kevin@tarvalon.net) Received: from fdl0042.excel.net (kevin@fdl0042.excel.net [156.46.102.170]) by green.excel.net (8.9.3/8.9.3) with ESMTP id LAA16112; Sun, 26 Dec 1999 11:44:50 -0600 (CST) Date: Sun, 26 Dec 1999 11:44:48 -0600 (CST) From: Kevin Entringer To: questions@freebsd.org Cc: stable@freebsd.org Subject: Re: X11 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the suggestion. I suspect that this was the problem, however X is still not working. The following no happens: Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) Dec 26 11:29:14 discord Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb ol "crypt"] Dec 26 11:29:14 discord Xwrapper: adding faulty module: /usr/lib/pam_unix.so Regards, Kevin On Sun, 26 Dec 1999, Cy Schubert - ITSD Open Systems Group wrote: > In message , Kevi > n Entringer writes: > > I just did a make world to 3.4-STABLE. Now I'm having problems with > > X11, version 3.3.5. Whenever I try to start it I get the following: > > > > kevin@discord:/home/kevin# startx > > > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > xinit: unexpected signal 2 > > > > In /var/log/messages it says the following: > > > > Dec 26 04:45:53 discord Xwrapper: no modules loaded for `xserver' service > > Dec 26 04:46:08 discord Xwrapper: no modules loaded for `xserver' service > > Dec 26 04:46:16 discord su: kevin to root on /dev/ttyv4 > > Dec 26 04:46:18 discord Xwrapper: no modules loaded for `xserver' service > > > > I've got no idea how to fix this. Any suggestions would be appreciated. > > > > Please cc any replies directly to me. > > I did not see this problem when I was testing 3.3-STABLE and nor did I > see it when I upgraded to 3.4-RELEASE. I did however see this problem > when I upgraded from the previous port of XF86 3.3.5 to the current > port of XF86 3.3.5 which now supports PAM. > > What you are seeing are PAM messages for modules that have not been > loaded. To have PAM load the required modules, add the following to > your pam.conf: > > # If we don't match anything else, default to using getpwnam(). > other auth required pam_unix.so try_first_pass > other account required pam_unix.so try_first_pass > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca > ITSD > Province of BC > "e**(i*pi)+1=0" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message