Date: Wed, 20 Jun 2001 10:04:36 +0300 From: Peter Pentchev <roam@orbitel.bg> To: "Hartmann, O." <ohartman@klima.physik.uni-mainz.de> Cc: freebsd-ports@freebsd.org Subject: Re: XFree 4.1.0 problem Message-ID: <20010620100436.D558@ringworld.oblivion.bg> In-Reply-To: <Pine.BSF.4.33.0106192351140.4109-100000@klima.physik.uni-mainz.de>; from ohartman@klima.physik.uni-mainz.de on Wed, Jun 20, 2001 at 12:03:20AM %2B0200 References: <Pine.BSF.4.33.0106192351140.4109-100000@klima.physik.uni-mainz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010620100436.D558>