From owner-freebsd-ports Thu Jun 21 6:38:41 2001 Delivered-To: freebsd-ports@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id 8C04037B403 for ; Thu, 21 Jun 2001 06:38:35 -0700 (PDT) (envelope-from ohartman@klima.physik.uni-mainz.de) Received: from klima.Physik.Uni-Mainz.DE (Sturm@klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.11.4/8.11.4) with ESMTP id f5LDcVG04951; Thu, 21 Jun 2001 15:38:31 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Thu, 21 Jun 2001 15:38:31 +0200 (CEST) From: "Hartmann, O." To: Peter Pentchev Cc: Subject: Re: XFree 4.1.0 problem In-Reply-To: <20010620100436.D558@ringworld.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 20 Jun 2001, Peter Pentchev wrote: All right, here I am again. My /etc/tty is simple, not even worth being posted due the fact it differs only in one point from the original: the last available tty: ttyv7 looks like ttyv0 or ttyv1 execpt it is set to 'off' In the appropriate kernel I set the maximum terminals to 8. From this point of view all things seems clear and work on each other systemn we have. We need to start our X-sessions by chooser - so I start first xdm in /etc/rc.local, then I start X-server permanently after starting xdm in /etc/rc.local. When starting the Xserver by xdm/Xservers, X resets lot of times itself (on the faulty machine) and then offers a chooser - and all virtual terminals are accessible as described (Alt-Ctrl-Fxx). It seems to make difference how xdm and X are started. I never had success in starting xdm via an entry in /etc/ttys and starting X via xdm/Xservers. The idea of our configuration is keeping the local machine accessible by X over chooser - so I need a xdm and X server. But this is actualy not the severe problem. It seems that especially this machine or FreeBSD in general has problems, with respect to other systems I focus the problem of the combination X,FBSD, AMD K7 and ASUS A7V with ATA devices. Another system without X and ATA (SCSI/160 instead) works great. :>Have you changed /etc/ttys? Can you post your /etc/ttys? :>X does not attach to the highest-numbered virtual console; it attaches :>to the first one that is allocated to it, that is, the first one that :>was free at the time X was started. If you have no getty processes :>running for virtual consoles (if you have disabled them in /etc/ttys, :>or if your /usr/libexec/getty fails to start), and xdm is configured :>to run on the first virtual console, then the described behavior :>would be normal. :> :>G'luck, :>Peter :> :>-- :>What would this sentence be like if it weren't self-referential? :> :>On Wed, Jun 20, 2001 at 12:03:20AM +0200, Hartmann, O. wrote: :>> Dear Sirs. :>> :>> Since we moved up to XFree 4.1.0 I run into a problem on one of our workstations. :>> The machine is driven by an AMD K7 800 with an ASUS K7V mainboard, 256 MB RAM :>> and an ATA drive from IBM DTLA 307030. :>> :>> We use more systems like that around here and all seem to have problems with :>> ATA - but not directly with the HDD, even with other subsystems which do not :>> appear on systems with SCSI. :>> :>> On this specific system we configured several virtual consoles - which could not :>> be accessed (while on other systems with the identical kernel we can switch :>> from the X11 system by ALT-FX to a console and back by pressing the highest :>> available FX-key representing the highest configured virt. console. That works :>> proper, without any harm. :>> :>> On this 'sick' machine this does not work - but this phenomenon occured since :>> we have this machine. I can only use the first console - but this is occupied by :>> X Server. This machine is only willing to shutdown by using -o option with shutdown, :>> without, nothing happens ... :>> :>> Well, now to my specific problem: :>> :>> We use fvwm2 2.2.5 on this machine. xdm is running, X server is started by :>> /etc/rc.local staticaly and connect via indirect query to an chooser delivering :>> XDMCP host. That worked in the past with XFree86 4.0.3 properly. :>> :>> Now X server dies when someone exits ist session and the system is only reactivateable :>> by a reboot due nobody can access the console (or we start X by network access via :>> ssh or telnet, that works fine). Does anyone has any kind of glue, hint or tip? :> -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ---------------------------------------------------------------- IT-Administration des Institut fuer Physik der Atmosphaere (IPA) ---------------------------------------------------------------- Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message