From owner-freebsd-x11@FreeBSD.ORG Tue Mar 31 02:03:29 2015 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C2868E0 for ; Tue, 31 Mar 2015 02:03:29 +0000 (UTC) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDECADBD for ; Tue, 31 Mar 2015 02:03:28 +0000 (UTC) Received: by lagg8 with SMTP id g8so2198207lag.1 for ; Mon, 30 Mar 2015 19:03:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AytJ/6IO9qvwtRXEk92/kwb9dLo/jhAPaK3dom/Uhp0=; b=WbU8DrbhfKMvfD27HajObCgoGbkXkribQocdjgYU7eliuHNPhyBDgx/l8PdDZK7HNG kt0DTknuJGFqNgOzdN82M1fw/IpMMrvDIY0nU6SJ21S50GGyNm+CaKPCU309RejuAGmz QCVJjyUR4uuMXr1ihzbwsN0nA5iCCdyqLHE1MjKES1dcCq+Eojm6WP5pPqH2mQzaJ/Lx Qg7tV8g9LRPZunuy9RYkv5t74phf5dj826PJNSQ2aJnqN/cLhXrGg6tZb7LFYGSsEFrO tqiVEOxHartDU8SWdvrQ95wNuGlNGTqtvO9ZlbFdFA8fO5af9Xv3RpyGwLE+kFaKPai4 3R+w== MIME-Version: 1.0 X-Received: by 10.112.170.100 with SMTP id al4mr29165063lbc.42.1427767406304; Mon, 30 Mar 2015 19:03:26 -0700 (PDT) Received: by 10.112.140.69 with HTTP; Mon, 30 Mar 2015 19:03:26 -0700 (PDT) In-Reply-To: <5519DD3A.9030507@cox.net> References: <5519DD3A.9030507@cox.net> Date: Mon, 30 Mar 2015 23:03:26 -0300 Message-ID: Subject: Re: Xorg is making the machine freezes when exit From: Vinicius Abrahao To: "John D. Hendrickson" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 02:03:29 -0000 On Mon, Mar 30, 2015 at 8:33 PM, John D. Hendrickson wrote: > > question: can you switch to VT before you exit X11 ? > > No, when I press ctrl+alt+Fx all frezes, ping to this machine stop to respond too. > /etc/X11/xorg.conf > > the xorg.conf file: https://gist.github.com/vinnix/563e41f052de822fe445 and Xorg.0.log file: https://gist.github.com/vinnix/d40a869bbb8e8bffd819 if it may help. > check X.org and look to see if there are advice on your card about issues > > I will thake a look carefuly in the X.org site, try to found something related. I also find this interesting URL, https://wiki.freebsd.org/Graphics/WITH_NEW_XORG , at the end of this, a table with something about "VT switching" (what I believe that is my problem). > ### for this question (the first) > > i'm going to ask: > > did you have a (telnet) in and run a video mode restorer program ? or > maybe have one run when X exits ? > > If I understand your question well, I am not accessing X by any other programs. Just using the normal "startx", directly on the console of the machine in question. The CPU is a i5/4xxx if that matters. What I also can see in https://wiki.freebsd.org/Graphics is ["Haswell" , note: See Update i915 GPU driver to Linux 3.8 ]. > whateelse happens at X exit? if it's a kernel video mode support who > knows what braindamage it "could be" - you need to find a way to show us > (by logs) an error message. (but i bet if you use VESA support it works) > > when X exits, by switching to VT (with ctrl+alt+f1 key) or just exit: 10/stable: the monitor (that is plugged in VGA port) turns the sinal LED as off (from blue to orange). 11/current: the screen freezes (but also the entire machine as far as I know, because network stop to respond). > freeBSD has new "class permissions" and pam and such and integrated into > kernel even. perhaps when X exits - freeBSD has an auth problem it cannot > resolve and freezes. > > yeah, that sounds a new stuff to me. I will go more deeper in to this topics, recently I move to -current to se if I could help others with somes tests, patches, etc.. > remember the "reason" (i never beleived them) X.org is needed for new > video cards is they respect no rules on the hardware BUS or with X11's > requests. they said X.org was needed to resolve video card hangs for new > cards. but that's still and issue: but they deleted all old video card > support. so i'm sure they got their card to work, maybe. mine: they > damaged. > > sure, X.org can do that. Certainly is not a easy task manage delicate code with "moody" cards. now I will try two more test, run only with "vesa" driver, and then try also to plug on TV by HDMI port (yes, the mother board has 4 video exits: VGA, HDMI, DVI and DisplayPort). And just see what happens. thanks in advance for your time and help, vinnix