From owner-freebsd-x11@FreeBSD.ORG Sun Jul 21 09:10:18 2013 Return-Path: Delivered-To: freebsd-x11@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6EBF5FC1; Sun, 21 Jul 2013 09:10:18 +0000 (UTC) (envelope-from edwin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4926ED58; Sun, 21 Jul 2013 09:10:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6L9AIfB005018; Sun, 21 Jul 2013 09:10:18 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6L9AIO4005017; Sun, 21 Jul 2013 09:10:18 GMT (envelope-from edwin) Date: Sun, 21 Jul 2013 09:10:18 GMT Message-Id: <201307210910.r6L9AIO4005017@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-x11@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/180714: [update] [patch] graphics/libdrm to 2.4.45 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2013 09:10:18 -0000 Synopsis: [update] [patch] graphics/libdrm to 2.4.45 Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-x11 Responsible-Changed-By: edwin Responsible-Changed-When: Sun Jul 21 09:10:18 UTC 2013 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=180714 From owner-freebsd-x11@FreeBSD.ORG Sun Jul 21 09:40:02 2013 Return-Path: Delivered-To: freebsd-x11@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 02AAD778 for ; Sun, 21 Jul 2013 09:40:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id CDBF7EB5 for ; Sun, 21 Jul 2013 09:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6L9e1rC011161 for ; Sun, 21 Jul 2013 09:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6L9e1Aq011160; Sun, 21 Jul 2013 09:40:01 GMT (envelope-from gnats) Date: Sun, 21 Jul 2013 09:40:01 GMT Message-Id: <201307210940.r6L9e1Aq011160@freefall.freebsd.org> To: freebsd-x11@FreeBSD.org Cc: From: Ivan Klymenko Subject: Re: ports/180714: [update] [patch] graphics/libdrm to 2.4.45 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Ivan Klymenko List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2013 09:40:02 -0000 The following reply was made to PR ports/180714; it has been noted by GNATS. From: Ivan Klymenko To: bug-followup@FreeBSD.org, fidaj@ukr.net Cc: Subject: Re: ports/180714: [update] [patch] graphics/libdrm to 2.4.45 Date: Sun, 21 Jul 2013 12:30:00 +0300 This update is necessary. that would upgrade the port multimedia/libva-intel-driver, which is already added to ports tree. http://docs.freebsd.org/cgi/mid.cgi?74488.1374358020.16480811267322281984 ... checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for gcc... (cached) cc checking whether we are using the GNU C compiler... (cached) yes checking whether cc accepts -g... (cached) yes checking for cc option to accept ISO C89... (cached) none needed checking whether cc understands -c and -o together... (cached) yes checking dependency style of cc... (cached) gcc3 checking whether byte ordering is bigendian... no checking for ANSI C header files... (cached) yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for sin in -lm... yes checking for log2f... yes checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for DRM... no configure: error: Package requirements (libdrm >= 2.4.45) were not met: Package dependency requirement 'libdrm >= 2.4.45' could not be satisfied. Package 'libdrm' has version '2.4.44', required version is '>= 2.4.45' Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables DRM_CFLAGS and DRM_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ===> Script "configure" failed unexpectedly. Please report the problem to manuel.creach@me.com [maintainer] and attach the "/usr/ports_build/usr/ports/multimedia/libva-intel-driver/work/libva-intel-driver-1.2.0/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** Error code 1 Stop. make: stopped in /usr/ports/multimedia/libva-intel-driver ===>>> make failed for multimedia/libva-intel-driver ===>>> Aborting update From owner-freebsd-x11@FreeBSD.ORG Sun Jul 21 16:33:13 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9BFB8EAE; Sun, 21 Jul 2013 16:33:13 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id 25826948; Sun, 21 Jul 2013 16:33:12 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3bys285fxxzFTJ7; Sun, 21 Jul 2013 18:33:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UgT5g2Q0KO50; Sun, 21 Jul 2013 18:33:02 +0200 (CEST) Received: from tommy.madpilot.net (host150-189-dynamic.50-79-r.retail.telecomitalia.it [79.50.189.150]) by winston.madpilot.net (Postfix) with ESMTPSA; Sun, 21 Jul 2013 18:33:02 +0200 (CEST) Message-ID: <51EC0D3E.2060203@FreeBSD.org> Date: Sun, 21 Jul 2013 18:33:02 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130627 Thunderbird/17.0.7 MIME-Version: 1.0 To: Ivan Klymenko Subject: Re: svn commit: r323260 - in head/multimedia/libva-intel-driver: . files References: <201307182219.r6IMJtuw092537@svn.freebsd.org> <74488.1374358020.16480811267322281984@ffe16.ukr.net> <20130721122103.067d6d2a@nonamehost.local> In-Reply-To: <20130721122103.067d6d2a@nonamehost.local> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, x11@freebsd.org, ports-committers@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jul 2013 16:33:13 -0000 On 07/21/13 11:21, Ivan Klymenko wrote: > В Sun, 21 Jul 2013 01:07:00 +0300 > "fidaj " пишет: >> >> --- Оригінальне повідомлення --- >> Від кого: "Guido Falsi" >> Дата: 19 липня 2013, 01:20:09 >> >> Author: madpilot >> Date: Thu Jul 18 22:19:55 2013 >> New Revision: 323260 >> URL: http://svnweb.freebsd.org/changeset/ports/323260 >> Log: >> - Update to 1.2.0 >> >> PR: ports/180040 >> Submitted by: Myself >> Approved by: Maintainer timeout >> >> Modified: >> head/multimedia/libva-intel-driver/Makefile >> head/multimedia/libva-intel-driver/distinfo >> head/multimedia/libva-intel-driver/files/patch-src-i965_decoder_utils.c >> >> >> What the meaning of such an upgrade if the port requires a new >> version of libdrm? >> >> checking whether stripping libraries is possible... yes >> checking if libtool supports shared libraries... yes >> checking whether to build shared libraries... yes >> checking whether to build static libraries... no >> checking for gcc... (cached) cc >> checking whether we are using the GNU C compiler... (cached) yes >> checking whether cc accepts -g... (cached) yes >> checking for cc option to accept ISO C89... (cached) none needed >> checking whether cc understands -c and -o together... (cached) yes >> checking dependency style of cc... (cached) gcc3 >> checking whether byte ordering is bigendian... no >> checking for ANSI C header files... (cached) yes >> checking for special C compiler options needed for large files... no >> checking for _FILE_OFFSET_BITS value needed for large files... no >> checking for sin in -lm... yes >> checking for log2f... yes >> checking for pkg-config... /usr/local/bin/pkg-config >> checking pkg-config is at least version 0.9.0... yes >> checking for DRM... no >> configure: error: Package requirements (libdrm >= 2.4.45) were not >> met: >> >> Package dependency requirement 'libdrm >= 2.4.45' could not be >> satisfied. Package 'libdrm' has version '2.4.44', required version is >> '>= 2.4.45' >> >> Consider adjusting the PKG_CONFIG_PATH environment variable if you >> installed software in a non-standard prefix. >> >> Alternatively, you may set the environment variables DRM_CFLAGS >> and DRM_LIBS to avoid the need to call pkg-config. >> See the pkg-config man page for more details. >> ===> Script "configure" failed unexpectedly. >> Please report the problem to manuel.creach@me.com [maintainer] and >> attach the >> "/usr/ports_build/usr/ports/multimedia/libva-intel-driver/work/libva-intel-driver-1.2.0/config.log" >> including the output of the failure of your make command. Also, it >> might be >> a good idea to provide an overview of all packages installed on your >> system >> (e.g. a /usr/local/sbin/pkg-static info -g -Ea). >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/multimedia/libva-intel-driver >> >> ===>>> make failed for multimedia/libva-intel-driver >> ===>>> Aborting update > > Please update graphics/libdrm to 2.4.45 > http://www.freebsd.org/cgi/query-pr.cgi?pr=180714 > Hi, I'm sorry for my mistake. Unluckily the laptop with intel graphics I test this one on happens to have libdrm 2.4.45 already installed. This is the reason this one slipped me. I'm not stating this as a justification, it's just the "technical" reason this happened. I can't commit to graphics/libdrm without permission. Depending on the chance of this PR being committed shortly I can put back the libva-intel-driver port or just wait a little. I'm also CCing x11@ to know if I'm allowed to fix this by updating libdrm (only the WITH_NEW_XORG case, obviously) or should bring the libva-intel-driver port back. Thanks in advance for any help. -- Guido Falsi From owner-freebsd-x11@FreeBSD.ORG Mon Jul 22 11:06:56 2013 Return-Path: Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2A25B4C9 for ; Mon, 22 Jul 2013 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 018AD24BA for ; Mon, 22 Jul 2013 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6MB6tZ3053914 for ; Mon, 22 Jul 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6MB6tkh053912 for freebsd-x11@FreeBSD.org; Mon, 22 Jul 2013 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Jul 2013 11:06:55 GMT Message-Id: <201307221106.r6MB6tkh053912@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-x11@FreeBSD.org Subject: Current problem reports assigned to freebsd-x11@FreeBSD.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/180714 x11 [update] [patch] graphics/libdrm to 2.4.45 o ports/180096 x11 [patch] x11/xorg-libraries: add missing dependency o ports/180023 x11 x11-servers/xorg: xorg (WITH_NEW_XORG) on 10-CURRENT i o ports/178670 x11 x11/xorg: X does not refresh upper 1/4 screen in some a ports/178170 x11 [patch] x11-servers/xorg-server: xkb misbehaviour on k o ports/176705 x11 graphics/libGL : Fix complitation (not useability) on o ports/176703 x11 graphics/dri : Fix complitation (not useability) on AR o ports/175876 x11 [new port] x11-drivers/xf86-input-wacom: split from in o ports/175532 x11 x11/xdm: /bin/cp -n /usr/local/share/examples/xdm/Give o ports/171422 x11 graphics/libGL build error with python3.2 o ports/170852 x11 [PATCH] x11-fonts/encodings: encodings.dir includes bo o ports/170690 x11 x11-servers/xorg-server eats memory o ports/169794 x11 x11/xdm, several /usr/local/lib/X11/xdm/ files missing o ports/169561 x11 [patch] x11-toolkits/libXmu: disable specs o ports/169560 x11 [patch] x11/libICE: disable specs o ports/169559 x11 [patch] x11-fonts/fontsproto: disable specs o ports/166163 x11 graphics/dri: gthumb port crashes (SIGSEGV) within the o ports/160963 x11 [patch] x11/bigreqsproto: disable specs a ports/159792 x11 [patch] USB HID devices support for x11-drivers/xf86-i f ports/158513 x11 Broken Xvideo in x11-drivers/xf86-video-intel drivers s ports/156405 x11 x11-drivers/xf86-video-ati driver: no hardware renderi o ports/155696 x11 [patch] x11-servers/xorg-server: chase AIGLX altered d o ports/154502 x11 x11/xdm authorization failure when used with E17 windo o ports/149743 x11 x11/xorg: garbled window since Xorg-7.5 o ports/148591 x11 information note for x11-drivers/xf86-input-synaptics 25 problems total. From owner-freebsd-x11@FreeBSD.ORG Mon Jul 22 17:09:53 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4950E101 for ; Mon, 22 Jul 2013 17:09:53 +0000 (UTC) (envelope-from maskor@inbox.com) Received: from WM55.inbox.com (wm55.inbox.com [64.135.83.55]) by mx1.freebsd.org (Postfix) with SMTP id 0D9792940 for ; Mon, 22 Jul 2013 17:09:52 +0000 (UTC) Received: from inbox.com (127.0.0.1:25) by inbox.com with [InBox.Com SMTP Server] id <1307220909075.WM55> for from ; Mon, 22 Jul 2013 09:09:44 -0800 DomainKey-Signature: q=dns; a=rsa-sha1; c=nofws; d=inbox.com; s=s1; h=mime-version:date:message-id:from:subject:to:content-type; b=FYs0tQqt/ORw4xnfAubjk7QSiZYBDLvH1+MUybPA3rUyB6SeHGvgKVFvSWW4XUX0SwhT 2+lg8xpUgn6W+tIIPxuHrSvnbY6E4Q4eQyB+9Lg+nDp+TYt6qqzTvs4gbjDnsezuARQEiI bnyZspFfs7BkdFHu/lmekyaEsh6OaPB6E= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; q=dns/txt; d=inbox.com; s=s1; h=mime-version:date:message-id:subject:from:to:content-type; bh=jS97m83+PtTAZDwbO5j0yaByEkELahpNuPwbPlVhdXQ=; b=CVD6YpjNF2lxwCNdvBKIo0jisuA6ohjcCNJ8qJVFIBNr2kuOEwJz1dDP/ZNNxIJDTzyS rpXfDtUS59lzOa+3WUiLqHbx0zJVvsE2EJa3SJi58IPBOTJIhKygUOcN5t8jgvT+HBsrzU QuwWnaWEi5ErxEmL9a7OMuSp8P+9CNJGY= Mime-Version: 1.0 Date: Mon, 22 Jul 2013 09:09:43 -0800 Message-ID: <4D2570C714A.000002D0maskor@inbox.com> From: maskor maskor Subject: svn error during check out of dev-xorg ports To: freebsd-x11@freebsd.org X-Mailer: INBOX.COM X-Originating-IP: 86.212.52.135 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IWM-ACU: SHsw2K7WKhDMkSGMY8Y3b2_zTghaIydXcSYMNnrYSFL_9p7Vpf_iUt-JvvMY g7rySffBwHP9aum4yYfd1c75os1Zr7xuzb8MaQZBxnCsb1GXQ6t1w-AnxWOt HZ8qYFzT-z7ljvzI@ X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 17:09:53 -0000 Hi all, =20 I am using FreeBSD 10.0-CURRENT on amd64 PC with : X.Org X Server 1.7.7, = radeon hd 7750 and gnome3-3.6.2. I follow instructions from https://wiki.freebsd.org/Xorg but I failed to = get update Xorg ports from development repo (see command below) : =23 svn co http://trillian.chruetertee.ch/ports/browser/trunk/ svn: E170000: Sch=C3=A9ma d'URL non reconnu pour = 'http://trillian.chruetertee.ch/ports/browser/trunk' For svn URL seems unknown even with Opera ( or firefox) web browser I can = access to the X11 repo located at = http://trillian.chruetertee.ch/ports/browser/trunk/ and see its content = (ports tree) without problem. I cannot also ping http://trillian.chruetertee.ch (see command below) =23 ping http://trillian.chruetertee.ch ping: cannot resolve http://trillian.chruetertee.ch: Unknown host I cannot too traceroute http://trillian.chruetertee.ch (see command below) =23 traceroute http://trillian.chruetertee.ch traceroute: unknown host http://trillian.chruetertee.ch So I need help for fixing error =22 svn: E170000: Sch=C3=A9ma d'URL non = reconnu pour 'http://trillian.chruetertee.ch/ports/browser/trunk' =22 Thanks ____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop=21 Check it out at http://www.inbox.com/earth From owner-freebsd-x11@FreeBSD.ORG Mon Jul 22 20:26:38 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4DE0DCBB for ; Mon, 22 Jul 2013 20:26:38 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep15.mx.upcmail.net (fep15.mx.upcmail.net [62.179.121.35]) by mx1.freebsd.org (Postfix) with ESMTP id 980D522E3 for ; Mon, 22 Jul 2013 20:26:37 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep15-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20130722202635.JUWN4669.viefep15-int.chello.at@edge01.upcmail.net>; Mon, 22 Jul 2013 22:26:35 +0200 Received: from [127.0.0.1] ([178.84.132.32]) by edge01.upcmail.net with edge id 3YSa1m0140i5fp601YSaP3; Mon, 22 Jul 2013 22:26:35 +0200 X-SourceIP: 178.84.132.32 Message-ID: <51ED9575.3090807@rainbow-runner.nl> Date: Mon, 22 Jul 2013 22:26:29 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: maskor maskor Subject: Re: svn error during check out of dev-xorg ports References: <4D2570C714A.000002D0maskor@inbox.com> In-Reply-To: <4D2570C714A.000002D0maskor@inbox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 130722-2, 22-07-2013), Outbound message X-Antivirus-Status: Clean Cc: freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 20:26:38 -0000 On 22-7-2013 19:09, maskor maskor wrote: > Hi all, > > I am using FreeBSD 10.0-CURRENT on amd64 PC with : X.Org X Server 1.7.7, radeon hd 7750 and gnome3-3.6.2. > > I follow instructions from https://wiki.freebsd.org/Xorg but I failed to get update Xorg ports from development repo (see command below) : > > # svn co http://trillian.chruetertee.ch/ports/browser/trunk/ > svn: E170000: Schéma d'URL non reconnu pour 'http://trillian.chruetertee.ch/ports/browser/trunk' You need to rebuild subversion with the SERF option. See ports/UPDATING entry 20130619 for details > > For svn URL seems unknown even with Opera ( or firefox) web browser I can access to the X11 repo located at http://trillian.chruetertee.ch/ports/browser/trunk/ and see its content (ports tree) without problem. > > I cannot also ping http://trillian.chruetertee.ch (see command below) > > # ping http://trillian.chruetertee.ch > ping: cannot resolve http://trillian.chruetertee.ch: Unknown host > > I cannot too traceroute http://trillian.chruetertee.ch (see command below) Try it again with the http:// removed that should work. -Koop From owner-freebsd-x11@FreeBSD.ORG Mon Jul 22 22:42:37 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE984278 for ; Mon, 22 Jul 2013 22:42:37 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo103.cox.net (fed1rmfepo103.cox.net [68.230.241.145]) by mx1.freebsd.org (Postfix) with ESMTP id AB8EC28F7 for ; Mon, 22 Jul 2013 22:42:37 +0000 (UTC) Received: from fed1rmimpo305 ([68.230.241.173]) by fed1rmfepo103.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130722224231.RBGS3894.fed1rmfepo103.cox.net@fed1rmimpo305> for ; Mon, 22 Jul 2013 18:42:31 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo305 with cox id 3aiX1m00B2oShb201aiX6T; Mon, 22 Jul 2013 18:42:31 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.51EDB557.0134,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=R/Dd76tX c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=-sc1xts7OiMA:10 a=ktNfuVtv0skA:10 a=IkcTkHD0fZMA:10 a=05pWP5ZVAAAA:8 a=hKplxj3TifQA:10 a=6vC3HQ9qU9zgFKl85N4A:9 a=QEXdDO2ut3YA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6MFVj8D032270; Mon, 22 Jul 2013 15:31:45 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51EDB640.7060709@reynoldsnet.org> Date: Mon, 22 Jul 2013 15:46:24 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-x11@freebsd.org" X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 22:42:37 -0000 On 7/19/2013 9:15 PM, Kevin Oberman wrote: > > Did you define WITH_KMS in /etc/make.conf? Did you build libdrm with > the KMS option? > yes, to both. > There have been reports of issues with Haswell GPUs, so it still may > not work with the current KMS code, but it is worth a try. (And it > would be appreciated if you could report the results.) > since you asked .... no I have not been successful at all getting the haswell GPU to work. I took the default config file that is written out with Xorg -configure and hand-edited it to remove the second "screen" section and what-not--eliminating the VESA driver from being used for anything and only declaring something that could use the "intel" driver. No good. I still get the same "drmOpenDevice: Open failed" messages that I've quoted before and it says "no screens detected" when trying to fire up and then just goes back to the console. So, definitely it is not working. H/W is ASRock Z87 Extreme moboard. > If all else fails, you can use VESA, but it will be very slow and may > have other issues. > -- I will probably have to do that, yes, until things can get fixed. I'm upgrading to the latest 9-STABLE sources right now (originally I installed from a 9.2-PRELEASE DVD image) in hopes that something was updated. -Jr From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 10:07:47 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5150E383 for ; Tue, 23 Jul 2013 10:07:47 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (unknown [IPv6:2001:1900:2254:206a::50:123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 42F5824B7 for ; Tue, 23 Jul 2013 10:07:47 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id r6NA7lnr027268 for ; Tue, 23 Jul 2013 10:07:47 GMT (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.6/Submit) id r6NA7ltP027265; Tue, 23 Jul 2013 10:07:47 GMT (envelope-from portscout) Message-Id: <201307231007.r6NA7ltP027265@portscout.freebsd.org> Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 23 Jul 2013 10:07:47 +0000 From: portscout@FreeBSD.org To: x11@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 10:07:47 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x11@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ x11/videoproto | 2.3.1 | 2.3.2 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@FreeBSD.org Thanks. From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 10:23:46 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7C95D6D5; Tue, 23 Jul 2013 10:23:46 +0000 (UTC) (envelope-from kwm@rainbow-runner.nl) Received: from fep18.mx.upcmail.net (fep18.mx.upcmail.net [62.179.121.38]) by mx1.freebsd.org (Postfix) with ESMTP id 192DB2563; Tue, 23 Jul 2013 10:23:44 +0000 (UTC) Received: from edge01.upcmail.net ([192.168.13.236]) by viefep18-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20130723102337.EZDH26154.viefep18-int.chello.at@edge01.upcmail.net>; Tue, 23 Jul 2013 12:23:37 +0200 Received: from crashalot.rainbow-runner.nl ([178.84.132.32]) by edge01.upcmail.net with edge id 3mPc1m0250i5fp601mPcsR; Tue, 23 Jul 2013 12:23:37 +0200 X-SourceIP: 178.84.132.32 Message-ID: <51EE59A6.2020207@rainbow-runner.nl> Date: Tue, 23 Jul 2013 12:23:34 +0200 From: Koop Mast User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130630 Thunderbird/17.0.7 MIME-Version: 1.0 To: Guido Falsi Subject: Re: svn commit: r323260 - in head/multimedia/libva-intel-driver: . files References: <201307182219.r6IMJtuw092537@svn.freebsd.org> <74488.1374358020.16480811267322281984@ffe16.ukr.net> <20130721122103.067d6d2a@nonamehost.local> <51EC0D3E.2060203@FreeBSD.org> In-Reply-To: <51EC0D3E.2060203@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ivan Klymenko , svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, x11@freebsd.org, ports-committers@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 10:23:46 -0000 On 07/21/13 18:33, Guido Falsi wrote: > On 07/21/13 11:21, Ivan Klymenko wrote: >> > > Hi, > > I'm sorry for my mistake. Unluckily the laptop with intel graphics I > test this one on happens to have libdrm 2.4.45 already installed. This > is the reason this one slipped me. I'm not stating this as a > justification, it's just the "technical" reason this happened. > > I can't commit to graphics/libdrm without permission. Depending on the > chance of this PR being committed shortly I can put back the > libva-intel-driver port or just wait a little. > > I'm also CCing x11@ to know if I'm allowed to fix this by updating > libdrm (only the WITH_NEW_XORG case, obviously) or should bring the > libva-intel-driver port back. > > Thanks in advance for any help. > I updated libdrm to 2.4.46, we had that update done for a while and it pretty stable. Please be more carefull in the future about updates and running patches ports. -Koop From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 10:34:19 2013 Return-Path: Delivered-To: freebsd-x11@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6A53BBE4; Tue, 23 Jul 2013 10:34:19 +0000 (UTC) (envelope-from kwm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4355325F5; Tue, 23 Jul 2013 10:34:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6NAYJ73067343; Tue, 23 Jul 2013 10:34:19 GMT (envelope-from kwm@freefall.freebsd.org) Received: (from kwm@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6NAYIfP067342; Tue, 23 Jul 2013 10:34:18 GMT (envelope-from kwm) Date: Tue, 23 Jul 2013 10:34:18 GMT Message-Id: <201307231034.r6NAYIfP067342@freefall.freebsd.org> To: fidaj@ukr.net, kwm@FreeBSD.org, freebsd-x11@FreeBSD.org From: kwm@FreeBSD.org Subject: Re: ports/180714: [update] [patch] graphics/libdrm to 2.4.45 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 10:34:19 -0000 Synopsis: [update] [patch] graphics/libdrm to 2.4.45 State-Changed-From-To: open->closed State-Changed-By: kwm State-Changed-When: Tue Jul 23 10:33:17 UTC 2013 State-Changed-Why: Update to 2.4.46 was committed from xorg-dev repo. Closing. http://www.freebsd.org/cgi/query-pr.cgi?pr=180714 From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 11:00:52 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B479F407 for ; Tue, 23 Jul 2013 11:00:52 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A4A227A1 for ; Tue, 23 Jul 2013 11:00:52 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 53ED040002 for ; Tue, 23 Jul 2013 13:00:49 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 42D4140004; Tue, 23 Jul 2013 13:00:49 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (h-45-105.a163.priv.bahnhof.se [94.254.45.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id B96F040002; Tue, 23 Jul 2013 13:00:46 +0200 (CEST) Received: from mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) by mx.daemonic.se (Postfix) with ESMTPS id 3bzxYp2mrTz8hVn; Tue, 23 Jul 2013 13:00:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mx.daemonic.se ([10.1.0.3]) (using TLS with cipher CAMELLIA256-SHA) by mailscanner.daemonic.se (mailscanner.daemonic.se [10.1.0.6]) (amavisd-new, port 10025) with ESMTPS id gZnsiaUjL1Au; Tue, 23 Jul 2013 13:00:42 +0200 (CEST) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2001:470:dca9:0:1::4]) by mx.daemonic.se (Postfix) with ESMTPS id 3bzxYk0j6rz8hVm; Tue, 23 Jul 2013 13:00:42 +0200 (CEST) Received: from [IPv6:::1] (celes.daemonic.se [IPv6:2001:470:dca9:1::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 3bzxYj6WVwz9Ctj; Tue, 23 Jul 2013 13:00:41 +0200 (CEST) Message-ID: <51EE6256.4020902@freebsd.org> Date: Tue, 23 Jul 2013 13:00:38 +0200 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: John Reynolds Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> In-Reply-To: <51E99691.1090808@reynoldsnet.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130723-0, 2013-07-23), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV using ClamSMTP Cc: x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 11:00:52 -0000 Hi! I'll try to answer all your questions below, as well as try to answer things from your follow-up mail. Hopefully no confusion will arise. On 2013-07-19 21:42, John Reynolds wrote: > Hello all, I recently put together a new box with very new hardware--an > ASRock Z87 "haswell" board with i-4770k proc. I've successfully > installed 9.2-PRERELEASE (amd64) on it with the help of some folks on > -stable, but am having a heck of a time trying to get Xorg working. I've > used FreeBSD for years and years but have always used Nvidia cards and > their config tool always just barfed out an xorg.conf file that worked > no fuss no muss. I'm trying like crazy to get this integrated GPU to work. When buying/building computers based on new hardware, remember that it might take a little while before support for it shows up in FreeBSD. In general most things work out of the box, but sometimes that is not the case. I am not sure the Haswell GPU is supported by our graphics stack yet. > > I did some research and found out that I needed WITH_NEW_XORG=1 in > /etc/make.conf and I've got that all compiled now with a ports tree > freshly updated via portsnap. I have xorg 7.7 port and all of things it > pulls in including version 2.21.9 of the xf86-video-intel port. Yes, WITH_NEW_XORG= is needed to get modern intel graphics hardware to work with X. We are working on making this the default, but there are some things left to iron out. This versio > > Could some kind soul out there give me some pointers on what the > "preferred" method for setting up X should be at this point using the > "new" Xorg and this very new H/W? > > If I do what the handbook and other tutorials say to do and run > > Xorg -configure > > that creates me a file that defines two screens/monitors, etc. That's > great and all, but I don't use a dual-head setup. yes, I can hack the > file and take out the other monitor stuff. But my buddy who lives in the > Linux world asked me "why are you creating a xorg.conf file? I haven't > used one in YEARS. You don't hardly need one for 'modern' hardware where > everything is probable and works nicely with each other." So that got me > to wondering "yeah, why am i creating it?" In general, running without a xorg.conf should work, but there are a lot of different hardware and setups out there, and just because it works on Linux does not mean it works on FreeBSD without xorg.conf. If you want to have more control of exactly what's going on, a config is probably to prefer. If you use xorg without HAL, you must have a config at least detailing your input devices for them to work properly. The same probably goes for dual-head setups. Remember that graphics cards today have more than one output, and this maybe confuse X as well. > > So, in the expert opinion of people working actively with Xorg on this > list, what should "most people" do (most people buying 'modern' hardware > these days and not using CRT monitors from the 1980's anymore :)? I have > fired up "xinit" (using just a simplistic .xinitrc and a tmp non-root > user for testing) with the setup file created from above AND without any > setup file at all. Both seem to work. xdpyinfo shows that the resolution > is 1920x1200 which I want by default, color depth seems fine, etc. What > is the "preferred" setup style? > > Now onto the problems / questions: No matter what I do whether firing up > with the xorg.conf file or without anything, if I exit the window > manager and expect to come back to the console it doesn't do it. It just > locks the machine HARD. I searched quite a bit about this and on this > list's archives (here > ) > I see some mention that something called KMS is now being used in the > Intel driver/Xorg and that something doesn't react well with our newcons > console driver. What exactly is KMS and why is it important? Also if I > look at my Xorg.0.log file as it's firing up I get tons of messages > about dri devices not being found, etc. KMS, or Kernel Mode Setting, is the "new" way of handling graphics in X. basically a lot of stuff regarding the graphics card was previously done in userland, however this makes it hard to get working graphics acceleration and stuff, so a lot of this has moved into the kernel, which means new kernel drivers are needed. An Intel KMS driver was ported by kib@ and comitted a little over a year ago. Currently an ATI/AMD KMS driver is under development, however it will take some time before it is done. Without these drivers, we loose support for a lot of modern hardware, which is part of the reason we have two xorg distributions today. This new KMS driver isn't without some issues though. Currently, when you enable it by loading the kld (which is done when starting X) the VT console no longer works, since it doesn't understand and support KMS. This is one of the reasons that the new xorg distribution isn't the default. Once newcons is finished and pushed into the FreeBSD source tree, the console should work with KMS. This might be what you perceive as a lockup. Generally, it is possible to shut down the computer either from a xterm (or other terminal emulator) or using the powerbutton once out of X. However, there might be issues between the new graphics card and FreeBSD that makes it hang. > > [ 41.710] drmOpenDevice: node name is /dev/dri/card0 > [ 41.710] Failed to change owner or group for file /dev/dri! 2: No > such file or directory > [ 41.710] Failed to change owner or group for file /dev/dri/card0! 2: > No such file or directory > [ 41.710] drmOpenDevice: open result is -1, (No such file or directory) > [ 41.710] Failed to change owner or group for file /dev/dri/card0! 2: > No such file or directory > [ 41.710] drmOpenDevice: open result is -1, (No such file or directory) > [ 41.710] drmOpenDevice: Open failed > [ 41.710] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 This is probably normal, it is looking for the graphics card device, but can't find it. Either the kernel module didn't attached to the graphics card, or it just shows up as a different device. What does dmesg and kldstat say once you've started X? > > Is there something that must be done in a custom kernel or something to > remedy this? I have dri-8.0.5_3,2 installed and right now I am just > running the GENERIC kernel from the install. A custom kernel should not be needed. [ Snipped from another mail in the thread] > Yes, upon further inspection, what I thought was "success" I think > fall-back to using VESA. In my Xorg.0.log: > > [ 17861.411] (II) intel: Driver for Intel Integrated Graphics Chipsets: > i810, > i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, > E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, > .... > Haswell CRW Server (GT1), Haswell CRW Server (GT2), > Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2), > Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2), > Iris(TM) Pro Graphics 5200, ValleyView PO board > > So it did load the driver and at least print this out, but later on in > the file after a bunch of: > > [ 17861.959] drmOpenDevice: node name is /dev/dri/card0 > [ 17861.959] Failed to change owner or group for file /dev/dri! 2: No > such file or directory > [ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: > No such file or directory > [ 17861.959] drmOpenDevice: open result is -1, (No such file or directory) > [ 17861.959] Failed to change owner or group for file /dev/dri/card0! 2: > No such file or directory > [ 17861.959] drmOpenDevice: open result is -1, (No such file or directory) > [ 17861.959] drmOpenDevice: Open failed > [ 17861.959] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 > [ 17861.959] drmOpenDevice: node name is /dev/dri/card0 > > I see > > [ 17861.961] (II) VESA(0): initializing int10 > [ 17861.962] (II) VESA(0): Primary V_BIOS segment is: 0xc000 > [ 17861.964] (II) VESA(0): VESA BIOS detected > [ 17861.964] (II) VESA(0): VESA VBE Version 3.0 > [ 17861.964] (II) VESA(0): VESA VBE Total Mem: 262080 kB > [ 17861.964] (II) VESA(0): VESA VBE OEM: Intel(R) HSW Mobile/Desktop > Graphics Chipset Accelerated VGA BIOS > [ 17861.964] (II) VESA(0): VESA VBE OEM Software Rev: 0.0 > [ 17862.017] (==) VESA(0): Depth 24, (--) framebuffer bpp 32 > [ 17862.017] (==) VESA(0): RGB weight 888 > [ 17862.017] (==) VESA(0): Default visual is TrueColor > [ 17862.017] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0) > [ 17862.017] (II) Loading sub module "ddc" > [ 17862.017] (II) LoadModule: "ddc" > [ 17862.017] (II) Module "ddc" already built-in > [ 17862.017] (II) VESA(0): VESA VBE DDC supported > [ 17862.017] (II) VESA(0): VESA VBE DDC Level 2 > [ 17862.017] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec. > [ 17862.029] (II) VESA(0): VESA VBE DDC read successfully > .... > > I don't know if this was simply a fall-back or if my xorg.conf file is > telling it to use vesa. As I was saying, I used the file generated by > Xorg -configure and it set things up for two monitors and it has two > "Device" sections, one that uses the "intel" driver and one that uses > "vesa." I have not tried using no configuration file just yet. Looking at this log, it seems that it first loads the intel driver, but since that doesn't work, it falls back to using the VESA driver. You can try to force the use of the intel driver in xorg.conf, however, this might render your X unusable. I suggest you post your dmesg and kldstat after you've started X, to see if the intel kms kernel module is loaded and attached to the graphics card. It might very well be that the current kernel driver doesn't support haswell. Have you tried CURRENT as well? > > So, are there developers with the Haswell boards and it's just a matter > of time before kinks get worked out? Do you suggest using no xorg.conf > file? > > Also, as reported once I go into X via 'startx' on a console there's no > coming back out. If I try it is a hard wedge. I know that's being > currently worked on. If there's any kernel module or kernel config > option or something that I need to have in order to even remotely have a > chance at making this GPU work, please let me know. As of this moment > I'm just running GENERIC/amd64, but I plan on recompiling things going > forward. > It does not hard wedge, however, the console doesn't work after loading the KMS drivers, as stated above. Regards! -- Niclas From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 12:59:56 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 495709DA; Tue, 23 Jul 2013 12:59:56 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 051E92D1F; Tue, 23 Jul 2013 12:59:55 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6NCxlix056446; Tue, 23 Jul 2013 06:59:47 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6NCxlUC056443; Tue, 23 Jul 2013 06:59:47 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 23 Jul 2013 06:59:47 -0600 (MDT) From: Warren Block To: Niclas Zeising Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. In-Reply-To: <51EE6256.4020902@freebsd.org> Message-ID: References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 23 Jul 2013 06:59:47 -0600 (MDT) Cc: John Reynolds , x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 12:59:56 -0000 On Tue, 23 Jul 2013, Niclas Zeising wrote: > In general, running without a xorg.conf should work, but there are a lot > of different hardware and setups out there, and just because it works on > Linux does not mean it works on FreeBSD without xorg.conf. If you want > to have more control of exactly what's going on, a config is probably to > prefer. > If you use xorg without HAL, you must have a config at least detailing > your input devices for them to work properly. My experience is that input device sections are not needed unless custom settings are needed in them. X autodetects them fine without HAL. From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 13:29:45 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EFE78EE for ; Tue, 23 Jul 2013 13:29:45 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A43B42E6D for ; Tue, 23 Jul 2013 13:29:45 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 5E18540002 for ; Tue, 23 Jul 2013 15:29:43 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 5357A40006; Tue, 23 Jul 2013 15:29:43 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (mx.daemonic.se [IPv6:2001:470:dca9:0:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id BD32240002; Tue, 23 Jul 2013 15:29:41 +0200 (CEST) Received: from mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) by mx.daemonic.se (Postfix) with ESMTPS id 3c00sd0LDkz8hVn; Tue, 23 Jul 2013 15:29:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mx.daemonic.se ([IPv6:2001:470:dca9:0:1::3]) (using TLS with cipher CAMELLIA256-SHA) by mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) (amavisd-new, port 10025) with ESMTPS id DfcF5iKj82Sc; Tue, 23 Jul 2013 15:29:38 +0200 (CEST) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2001:470:dca9:0:1::4]) by mx.daemonic.se (Postfix) with ESMTPS id 3c00sZ4FFrz8hVm; Tue, 23 Jul 2013 15:29:38 +0200 (CEST) Received: from [IPv6:::1] (celes.daemonic.se [IPv6:2001:470:dca9:1::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 3c00sZ1vd8z9Ctj; Tue, 23 Jul 2013 15:29:38 +0200 (CEST) Message-ID: <51EE8546.6030803@freebsd.org> Date: Tue, 23 Jul 2013 15:29:42 +0200 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: Warren Block Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130723-0, 2013-07-23), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV using ClamSMTP Cc: John Reynolds , x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 13:29:46 -0000 On 2013-07-23 14:59, Warren Block wrote: > On Tue, 23 Jul 2013, Niclas Zeising wrote: > >> In general, running without a xorg.conf should work, but there are a lot >> of different hardware and setups out there, and just because it works on >> Linux does not mean it works on FreeBSD without xorg.conf. If you want >> to have more control of exactly what's going on, a config is probably to >> prefer. >> If you use xorg without HAL, you must have a config at least detailing >> your input devices for them to work properly. > > My experience is that input device sections are not needed unless custom > settings are needed in them. X autodetects them fine without HAL. I've had trouble in the past, at least with mice... Regards! -- Niclas From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 13:58:01 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BAA98BDE; Tue, 23 Jul 2013 13:58:01 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D7AC2FDE; Tue, 23 Jul 2013 13:58:01 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6NDw0EL057087; Tue, 23 Jul 2013 07:58:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6NDvxCr057084; Tue, 23 Jul 2013 07:57:59 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 23 Jul 2013 07:57:59 -0600 (MDT) From: Warren Block To: Niclas Zeising Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. In-Reply-To: <51EE8546.6030803@freebsd.org> Message-ID: References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> <51EE8546.6030803@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 23 Jul 2013 07:58:00 -0600 (MDT) Cc: John Reynolds , x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 13:58:01 -0000 On Tue, 23 Jul 2013, Niclas Zeising wrote: > On 2013-07-23 14:59, Warren Block wrote: >> On Tue, 23 Jul 2013, Niclas Zeising wrote: >> >>> In general, running without a xorg.conf should work, but there are a lot >>> of different hardware and setups out there, and just because it works on >>> Linux does not mean it works on FreeBSD without xorg.conf. If you want >>> to have more control of exactly what's going on, a config is probably to >>> prefer. >>> If you use xorg without HAL, you must have a config at least detailing >>> your input devices for them to work properly. >> >> My experience is that input device sections are not needed unless custom >> settings are needed in them. X autodetects them fine without HAL. > > I've had trouble in the past, at least with mice... Ah. PS/2 mice, maybe? I admit I have not tried one of those in a long, long time. From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 16:31:23 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 16AD1B00; Tue, 23 Jul 2013 16:31:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C8E2C28AA; Tue, 23 Jul 2013 16:31:22 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id i4so11791246oah.10 for ; Tue, 23 Jul 2013 09:31:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Cpb9p+WUdZXmrGDbrz/xKpiw5phaA0mxfGVmAfAqJZ0=; b=DW9n+ftz8ta1qMyfejUiZhcgDGf1pwX5cTZOLGVm/KM4atVYEzlGAXH1hWW2ZiiD1C ljg9k1DxjrJsCadga/f7yhncp1IduHD2eJJUCnpuV1CNI6ZhofwB/9eSJssolKiXiRcb 2wQYQ+zIc39VkDE6CjSCEHXpdzEzxAvjzSE+xnUkf62/P3qCcjb5Wv+3XHnXKUG2uKeo v6Njmi1ZIp3eaiVjq4r5qsVW7BmOi7xV4MIhJ5AcTd0/Gs66Ab61CTKcXvzWaSTcAkJB g+cVkNA1MzuSa84e0o7gpO36d1zH7/N0FYFwezr+RjpXC4TKFCtyQU42Bdmr6iaXh0vn 6n7A== MIME-Version: 1.0 X-Received: by 10.60.102.202 with SMTP id fq10mr31910663oeb.42.1374597082017; Tue, 23 Jul 2013 09:31:22 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Tue, 23 Jul 2013 09:31:21 -0700 (PDT) In-Reply-To: References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> <51EE8546.6030803@freebsd.org> Date: Tue, 23 Jul 2013 09:31:21 -0700 X-Google-Sender-Auth: lNy-CnaqthRQK1GKo8oFUWiUOYk Message-ID: Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: John Reynolds , "freebsd-x11@freebsd.org" , Niclas Zeising X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 16:31:23 -0000 On Tue, Jul 23, 2013 at 6:57 AM, Warren Block wrote: > On Tue, 23 Jul 2013, Niclas Zeising wrote: > > On 2013-07-23 14:59, Warren Block wrote: >> >>> On Tue, 23 Jul 2013, Niclas Zeising wrote: >>> >>> In general, running without a xorg.conf should work, but there are a lot >>>> of different hardware and setups out there, and just because it works on >>>> Linux does not mean it works on FreeBSD without xorg.conf. If you want >>>> to have more control of exactly what's going on, a config is probably to >>>> prefer. >>>> If you use xorg without HAL, you must have a config at least detailing >>>> your input devices for them to work properly. >>>> >>> >>> My experience is that input device sections are not needed unless custom >>> settings are needed in them. X autodetects them fine without HAL. >>> >> >> I've had trouble in the past, at least with mice... >> > > Ah. PS/2 mice, maybe? I admit I have not tried one of those in a long, > long time. > My T520 works well with the "PS/2 mouse". It's actually the TrackPoint mouse, but it looks like a PS/2 mouse to the system. I needed nothing in my config. I am using moused. The only thing in my Xorg.conf file is a list of fonts that I have added. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 17:30:22 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 32E7FAE0; Tue, 23 Jul 2013 17:30:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id E2E552B15; Tue, 23 Jul 2013 17:30:21 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3c06C95T9RzFTJV; Tue, 23 Jul 2013 19:30:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QMP-HtTwAAlJ; Tue, 23 Jul 2013 19:30:11 +0200 (CEST) Received: from tommy.madpilot.net (host108-111-dynamic.248-95-r.retail.telecomitalia.it [95.248.111.108]) by winston.madpilot.net (Postfix) with ESMTPSA; Tue, 23 Jul 2013 19:30:11 +0200 (CEST) Message-ID: <51EEBDA6.1040505@FreeBSD.org> Date: Tue, 23 Jul 2013 19:30:14 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130627 Thunderbird/17.0.7 MIME-Version: 1.0 To: Koop Mast Subject: Re: svn commit: r323260 - in head/multimedia/libva-intel-driver: . files References: <201307182219.r6IMJtuw092537@svn.freebsd.org> <74488.1374358020.16480811267322281984@ffe16.ukr.net> <20130721122103.067d6d2a@nonamehost.local> <51EC0D3E.2060203@FreeBSD.org> <51EE59A6.2020207@rainbow-runner.nl> In-Reply-To: <51EE59A6.2020207@rainbow-runner.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ivan Klymenko , svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, x11@freebsd.org, ports-committers@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 17:30:22 -0000 On 07/23/13 12:23, Koop Mast wrote: > On 07/21/13 18:33, Guido Falsi wrote: >> On 07/21/13 11:21, Ivan Klymenko wrote: >>> > >> >> Hi, >> >> I'm sorry for my mistake. Unluckily the laptop with intel graphics I >> test this one on happens to have libdrm 2.4.45 already installed. This >> is the reason this one slipped me. I'm not stating this as a >> justification, it's just the "technical" reason this happened. >> >> I can't commit to graphics/libdrm without permission. Depending on the >> chance of this PR being committed shortly I can put back the >> libva-intel-driver port or just wait a little. >> >> I'm also CCing x11@ to know if I'm allowed to fix this by updating >> libdrm (only the WITH_NEW_XORG case, obviously) or should bring the >> libva-intel-driver port back. >> >> Thanks in advance for any help. >> > > I updated libdrm to 2.4.46, we had that update done for a while and it > pretty stable. Please be more carefull in the future about updates and > running patches ports. Thanks a lot! I'm really sorry about my mistake. -- Guido Falsi From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 17:49:12 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 45071218; Tue, 23 Jul 2013 17:49:12 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D69AF2BDC; Tue, 23 Jul 2013 17:49:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6NHnA91059067; Tue, 23 Jul 2013 11:49:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6NHnA3k059064; Tue, 23 Jul 2013 11:49:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 23 Jul 2013 11:49:10 -0600 (MDT) From: Warren Block To: Kevin Oberman Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. In-Reply-To: Message-ID: References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> <51EE8546.6030803@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-831162289-1374601750=:59063" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 23 Jul 2013 11:49:10 -0600 (MDT) Cc: John Reynolds , "freebsd-x11@freebsd.org" , Niclas Zeising X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 17:49:12 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-831162289-1374601750=:59063 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 23 Jul 2013, Kevin Oberman wrote: > On Tue, Jul 23, 2013 at 6:57 AM, Warren Block wrote: > On Tue, 23 Jul 2013, Niclas Zeising wrote: > > On 2013-07-23 14:59, Warren Block wrote: > On Tue, 23 Jul 2013, Niclas Zeising wrote: > > In general, running without a xorg.conf should work, but there are a lot > of different hardware and setups out there, and just because it works on > Linux does not mean it works on FreeBSD without xorg.conf.  If you want > to have more control of exactly what's going on, a config is probably to > prefer. > If you use xorg without HAL, you must have a config at least detailing > your input devices for them to work properly. > > > My experience is that input device sections are not needed unless custom > settings are needed in them. X autodetects them fine without HAL. > > > I've had trouble in the past, at least with mice... > > > Ah.  PS/2 mice, maybe?  I admit I have not tried one of those in a long, long time. > > > My T520 works well with the "PS/2 mouse". It's actually the TrackPoint mouse, but it looks like a PS/2 mouse to the system. > > I needed nothing in my config. I am using moused. The only thing in my Xorg.conf file is a list of fonts that I have added. moused is probably the important part there. With USB mice, moused is started automatically by devd. --3512871622-831162289-1374601750=:59063-- From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 18:07:00 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D1A36A4 for ; Tue, 23 Jul 2013 18:07:00 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo202.cox.net (fed1rmfepo202.cox.net [68.230.241.147]) by mx1.freebsd.org (Postfix) with ESMTP id 5B19D2CA5 for ; Tue, 23 Jul 2013 18:07:00 +0000 (UTC) Received: from fed1rmimpo209 ([68.230.241.160]) by fed1rmfepo202.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130723180654.CGDC3842.fed1rmfepo202.cox.net@fed1rmimpo209> for ; Tue, 23 Jul 2013 14:06:54 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo209 with cox id 3u6u1m00G2oShb201u6u9N; Tue, 23 Jul 2013 14:06:54 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020201.51EEC63E.01DD,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=bI3I1oCZ c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=-sc1xts7OiMA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=hKplxj3TifQA:10 a=ugIDDCXe2HrDpqlPhkoA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6NAu6lM040519; Tue, 23 Jul 2013 10:56:06 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51EEC725.5000507@reynoldsnet.org> Date: Tue, 23 Jul 2013 11:10:45 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Niclas Zeising Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> In-Reply-To: <51EE6256.4020902@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 18:07:00 -0000 On 7/23/2013 4:00 AM, Niclas Zeising wrote: > Hi! > > I'll try to answer all your questions below, as well as try to answer > things from your follow-up mail. Hopefully no confusion will arise. thanks :) > When buying/building computers based on new hardware, remember that it > might take a little while before support for it shows up in FreeBSD. In > general most things work out of the box, but sometimes that is not the > case. I am not sure the Haswell GPU is supported by our graphics stack yet. I had a feeling that might be the case when I was contemplating doing it--but I know things will eventually get fixed. :) ... plus I just came off a very difficult project and wanted to treat myself to some nice new hardware, the risks be damned :) > In general, running without a xorg.conf should work, but there are a lot > of different hardware and setups out there, and just because it works on > Linux does not mean it works on FreeBSD without xorg.conf. If you want > to have more control of exactly what's going on, a config is probably to > prefer. OK > KMS, or Kernel Mode Setting, is the "new" way of handling graphics in > X. basically a lot of stuff regarding the graphics card was previously > done in userland, however this makes it hard to get working graphics > acceleration and stuff, so a lot of this has moved into the kernel, > which means new kernel drivers are needed. An Intel KMS driver was > ported by kib@ and comitted a little over a year ago. Currently an > ATI/AMD KMS driver is under development, however it will take some > time before it is done. Without these drivers, we loose support for a > lot of modern hardware, which is part of the reason we have two xorg > distributions today. This new KMS driver isn't without some issues > though. Currently, when you enable it by loading the kld (which is > done when starting X) the VT console no longer works, since it doesn't > understand and support KMS. This is one of the reasons that the new > xorg distribution isn't the default. Once newcons is finished and > pushed into the FreeBSD source tree, the console should work with KMS. > This might be what you perceive as a lockup. yeah, it seems like it. One other person had mentioned it was the console code that needed to understand KMS. I > Generally, it is possible to shut down the computer either from a > xterm (or other terminal emulator) or using the powerbutton once out > of X. However, there might be issues between the new graphics card and > FreeBSD that makes it hang. I can use the power button to take it down, but the filesystems are never shutdown properly when I do that for some reason. but with SU+J on the partitions now I haven't yet seen it not "fix itself" instantly upon boot. > This is probably normal, it is looking for the graphics card device, > but can't find it. Either the kernel module didn't attached to the > graphics card, or it just shows up as a different device. What does > dmesg and kldstat say once you've started X? kldstat did show the i915drm module as loaded, I remember ..... > Looking at this log, it seems that it first loads the intel driver, > but since that doesn't work, it falls back to using the VESA driver. > You can try to force the use of the intel driver in xorg.conf, > however, this might render your X unusable. I suggest you post your > dmesg and kldstat after you've started X, to see if the intel kms > kernel module is loaded and attached to the graphics card. It might > very well be that the current kernel driver doesn't support haswell. > Have you tried CURRENT as well? I have not tried -current yet. I generally have never run -current in the past except the transition from 4.x to 5.x briefly..... I'm in the midst of reconfiguring the same machine (I made a boo boo in disk partitioning and needed to fix it and reinstall the whole ball of wax again) and will look at the dmesg output after I go into X (having it fallback to the VESA driver at this point of course). Thanks for your reply! -Jr From owner-freebsd-x11@FreeBSD.ORG Tue Jul 23 21:29:26 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8F03F544 for ; Tue, 23 Jul 2013 21:29:26 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by mx1.freebsd.org (Postfix) with ESMTP id 66C052645 for ; Tue, 23 Jul 2013 21:29:26 +0000 (UTC) Received: from fed1rmimpo306 ([68.230.241.174]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130723212920.CYTH3892.fed1rmfepo101.cox.net@fed1rmimpo306> for ; Tue, 23 Jul 2013 17:29:20 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo306 with cox id 3xVK1m00F2oShb201xVK5J; Tue, 23 Jul 2013 17:29:19 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020206.51EEF5AF.0161,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=XPTuv3dE c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=-sc1xts7OiMA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=hKplxj3TifQA:10 a=Oh0ysQXEkg2vqaBr8KkA:9 a=wPNLvfGTeEIA:10 a=O37crZM1fZu-D5kj:21 a=9Ou8Qv1Dmtj7SAmW:21 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6NEIV8A042101; Tue, 23 Jul 2013 14:18:31 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51EEF696.5030505@reynoldsnet.org> Date: Tue, 23 Jul 2013 14:33:10 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Niclas Zeising Subject: Re: Need help untangling Xorg behavior on Haswell board, KMS, etc. etc. References: <51E99691.1090808@reynoldsnet.org> <51EE6256.4020902@freebsd.org> In-Reply-To: <51EE6256.4020902@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 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, 23 Jul 2013 21:29:26 -0000 > Looking at this log, it seems that it first loads the intel driver, but > since that doesn't work, it falls back to using the VESA driver. You > can try to force the use of the intel driver in xorg.conf, however, this > might render your X unusable. I suggest you post your dmesg and kldstat > after you've started X, to see if the intel kms kernel module is loaded > and attached to the graphics card. It might very well be that the > current kernel driver doesn't support haswell. Have you tried CURRENT > as well? > OK I have the machine configured again and just loaded Xorg without any config file. This is with a 9.2-BETA1 kernel/world. kldstat shows: Id Refs Address Size Name 1 32 0xffffffff80200000 15e9798 kernel 2 1 0xffffffff81a12000 9ebf linprocfs.ko 3 1 0xffffffff81a1c000 57b69 linux.ko 4 1 0xffffffff81a74000 69471 i915kms.ko 5 1 0xffffffff81ade000 197b iicbb.ko 6 4 0xffffffff81ae0000 1d46 iicbus.ko 7 1 0xffffffff81ae2000 1cc3 iic.ko 8 1 0xffffffff81ae4000 34f5c drm2.ko However, dmesg doesn't really show anything related to drm or kms or anything. Just a bunch of entries related to "pulseaudio" not being able to find something. So no real clues there. I will not be able to track -CURRENT on this box, so I'm afraid I won't be of any help there. I'll just ride-out however long it takes and use the fall-back VESA driver until patches find their way into 9-STABLE. Thanks! -jr From owner-freebsd-x11@FreeBSD.ORG Wed Jul 24 09:15:43 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 473D9824 for ; Wed, 24 Jul 2013 09:15:43 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (unknown [IPv6:2001:1900:2254:206a::50:123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 38D3A242A for ; Wed, 24 Jul 2013 09:15:43 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id r6O9Fhke012158 for ; Wed, 24 Jul 2013 09:15:43 GMT (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.6/Submit) id r6O9FhZi012153; Wed, 24 Jul 2013 09:15:43 GMT (envelope-from portscout) Message-Id: <201307240915.r6O9FhZi012153@portscout.freebsd.org> Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Wed, 24 Jul 2013 09:15:43 +0000 From: portscout@FreeBSD.org To: x11@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 09:15:43 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x11@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ x11/xorg-cf-files | 1.0.4 | 1.0.5 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@FreeBSD.org Thanks. From owner-freebsd-x11@FreeBSD.ORG Thu Jul 25 09:13:34 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CFB0280C for ; Thu, 25 Jul 2013 09:13:34 +0000 (UTC) (envelope-from portscout@FreeBSD.org) Received: from portscout.freebsd.org (unknown [IPv6:2001:1900:2254:206a::50:123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDC0829B0 for ; Thu, 25 Jul 2013 09:13:34 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id r6P9DYbB057488 for ; Thu, 25 Jul 2013 09:13:34 GMT (envelope-from portscout@portscout.freebsd.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.6/Submit) id r6P9DY18057486; Thu, 25 Jul 2013 09:13:34 GMT (envelope-from portscout) Message-Id: <201307250913.r6P9DY18057486@portscout.freebsd.org> Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Thu, 25 Jul 2013 09:13:34 +0000 From: portscout@FreeBSD.org To: x11@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 09:13:34 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/x11@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ x11/iceauth | 1.0.5 | 1.0.6 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portscout@FreeBSD.org Thanks.