From owner-freebsd-x11@freebsd.org Sun Apr 10 21:00:32 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E097BB0B8B2 for ; Sun, 10 Apr 2016 21:00:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id CD9CF1A6D for ; Sun, 10 Apr 2016 21:00:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id CCF9EB0B8B1; Sun, 10 Apr 2016 21:00:32 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCAC5B0B8B0 for ; Sun, 10 Apr 2016 21:00:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AC24A1A67 for ; Sun, 10 Apr 2016 21:00:32 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3AL01Tc070502 for ; Sun, 10 Apr 2016 21:00:32 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201604102100.u3AL01Tc070502@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: x11@FreeBSD.org Subject: Problem reports for x11@FreeBSD.org that need special attention Date: Sun, 10 Apr 2016 21:00:32 +0000 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 10 Apr 2016 21:00:33 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 188833 | [suspend/resume] Suspend/resume with Intel GMA HD 1 problems total for which you should take action. From owner-freebsd-x11@freebsd.org Tue Apr 12 09:11:16 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFBBDB0D046 for ; Tue, 12 Apr 2016 09:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A10C61684 for ; Tue, 12 Apr 2016 09:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3C9BGxP092949 for ; Tue, 12 Apr 2016 09:11:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 09:11:16 +0000 X-Bugzilla-Type: request X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 09:11:16 -0000 Raphael Kubo da Costa has asked freebsd-x11@FreeBSD.org for maintainer-feedback: Bug 208559: x11/xorg-server: X will not start https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 From owner-freebsd-x11@freebsd.org Tue Apr 12 09:11:16 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8286B0D048 for ; Tue, 12 Apr 2016 09:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8B1F1685 for ; Tue, 12 Apr 2016 09:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3C9BGxR092949 for ; Tue, 12 Apr 2016 09:11:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 09:11:16 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rakuco@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: assigned_to cc short_desc flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 09:11:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 Raphael Kubo da Costa changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-ports-bugs@FreeBSD. |freebsd-x11@FreeBSD.org |org | CC| |freebsd-x11@FreeBSD.org Summary|x11/xorg: X will not start |x11/xorg-server: X will not | |start Flags| |maintainer-feedback?(freebs | |d-x11@FreeBSD.org) --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 13:11:05 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06460B0DC55 for ; Tue, 12 Apr 2016 13:11:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB32F2000 for ; Tue, 12 Apr 2016 13:11:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3CDB45T034923 for ; Tue, 12 Apr 2016 13:11:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 13:11:05 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: serio.jeffrey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 13:11:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 serio.jeffrey@riseup.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |serio.jeffrey@gmail.com --- Comment #1 from serio.jeffrey@riseup.net --- (In reply to donaldcallen from comment #0) Try installing xf86-video-fbdev, and see if it works then. I've had a simil= ar issue with dmesg reporting "Warning, couldn't open module fbdev". --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 13:31:58 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BF85B0D435 for ; Tue, 12 Apr 2016 13:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C8F51CDD for ; Tue, 12 Apr 2016 13:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3CDVwR7092938 for ; Tue, 12 Apr 2016 13:31:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 13:31:58 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: donaldcallen@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 13:31:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 --- Comment #2 from donaldcallen@gmail.com --- (In reply to serio.jeffrey@riseup.net from comment #1) Umm, the error I encountered was RADEON(0): [drm] Failed to open DRM device for pci:0000:00:01.0: No such fi= le or directory You are suggesting doing another install of FreeBSD (I have Arch Linux installed on the machine now) and installing the fbdev driver to fix this? = I'm sorry, but that doesn't make a lot of sense. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 14:01:06 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8D0CB0C253 for ; Tue, 12 Apr 2016 14:01:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 995781B0C for ; Tue, 12 Apr 2016 14:01:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3CE16dr063874 for ; Tue, 12 Apr 2016 14:01:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 14:01:06 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: serio.jeffrey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 14:01:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 --- Comment #3 from serio.jeffrey@riseup.net --- Do whatever you want. I'm just making a suggestion. I had a similar issue w= ith Xorg not starting, and part of the dmesg log contained that bit about fbdev= , as yours does (search the attachment for 'fbdev' to see it). I installed xf86-video-fbdev and it somehow started working. It really was that simple.= I can't help that you now have Arch Linux installed. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 14:04:35 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3431B0C422 for ; Tue, 12 Apr 2016 14:04:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3D921DBA for ; Tue, 12 Apr 2016 14:04:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3CE4ZO3093078 for ; Tue, 12 Apr 2016 14:04:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 14:04:36 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: serio.jeffrey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 14:04:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 --- Comment #4 from serio.jeffrey@riseup.net --- (In reply to donaldcallen from comment #2) Also, I'm not saying this is a fix for your problem. It is at most a tempor= ary workaround. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 14:07:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF17FB0C53A for ; Tue, 12 Apr 2016 14:07:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFA7E1EA8 for ; Tue, 12 Apr 2016 14:07:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3CE7fKS097021 for ; Tue, 12 Apr 2016 14:07:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-x11@FreeBSD.org Subject: [Bug 208559] x11/xorg-server: X will not start Date: Tue, 12 Apr 2016 14:07:42 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: serio.jeffrey@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-x11@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 14:07:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208559 --- Comment #5 from serio.jeffrey@riseup.net --- (In reply to serio.jeffrey@riseup.net from comment #4) And I'm not guaranteeing that it will help your situation. I'm saying it ju= st worked for me, and suggesting you try it. If it doesn't work then forget ab= out it. Now that you have Arch Linux installed and have a working system, maybe it's not worth the trouble any more. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-x11@freebsd.org Tue Apr 12 17:52:07 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CAACB0D8A7 for ; Tue, 12 Apr 2016 17:52:07 +0000 (UTC) (envelope-from docteurchaouki@server.212communication.com) Received: from mx.212communication.com (server.212communication.com [68.168.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D93C133E for ; Tue, 12 Apr 2016 17:52:06 +0000 (UTC) (envelope-from docteurchaouki@server.212communication.com) Received: from docteurchaouki by server.212communication.com with local (Exim 4.86_1) (envelope-from ) id 1aq10I-0045EB-Fb for freebsd-x11@freebsd.org; Tue, 12 Apr 2016 12:17:27 -0400 To: freebsd-x11@freebsd.org Subject: Notice to Appear X-PHP-Script: docteurchaouki.com/post.php for 198.173.64.97 Date: Tue, 12 Apr 2016 16:17:26 +0000 From: "State Court" Reply-To: "State Court" Message-ID: <23d41c7b6450e7d58471f61b52e135b0@docteurchaouki.com> X-Priority: 3 MIME-Version: 1.0 X-OutGoing-Spam-Status: No, score=0.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.212communication.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [919 933] / [47 12] X-AntiAbuse: Sender Address Domain - server.212communication.com X-Get-Message-Sender-Via: server.212communication.com: authenticated_id: docteurchaouki/from_h X-Authenticated-Sender: server.212communication.com: charlie.hess@docteurchaouki.com Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 17:52:07 -0000 Notice to Appear, You have to appear in the Court on the April 20. Please, prepare all the documents relating to the case and bring them to Court on the specified date. Note: The case will be heard by the judge in your absence if you do not come. The Court Notice is attached to this email. Kind regards, Charlie Hess, Clerk of Court. From owner-freebsd-x11@freebsd.org Tue Apr 12 19:20:07 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 559CFB0DA98 for ; Tue, 12 Apr 2016 19:20:07 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16B60184C for ; Tue, 12 Apr 2016 19:20:06 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aq3r0-00085A-Td; Tue, 12 Apr 2016 22:20:02 +0300 Subject: Re: kloadload i915kms cause kernel core dump To: =?UTF-8?B?5om/5oGp5b6Q?= References: Cc: freebsd-x11@FreeBSD.org From: Arto Pekkanen Message-ID: <570D4A62.8010705@kapsi.fi> Date: Tue, 12 Apr 2016 22:20:02 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="89v1Qr4cbsTKdUrSJlVlbT74EMaL1AKJ0" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 19:20:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --89v1Qr4cbsTKdUrSJlVlbT74EMaL1AKJ0 Content-Type: multipart/mixed; boundary="StapjhqghVJJu3dhjqxscow0Q7EPp5uBi" From: Arto Pekkanen To: =?UTF-8?B?5om/5oGp5b6Q?= Cc: freebsd-x11@FreeBSD.org Message-ID: <570D4A62.8010705@kapsi.fi> Subject: Re: kloadload i915kms cause kernel core dump References: In-Reply-To: --StapjhqghVJJu3dhjqxscow0Q7EPp5uBi Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This topic has been discussed already many times before, so I am just going to link the relevant Handbook article: https://www.freebsd.org/doc/handbook/x-config.html Read through the section "Setting the Video Driver in a File" To set the Intel=C2=AE driver in a configuration file: Example 5.1. Select Intel=C2=AE Video Driver in a File /usr/local/etc/X11/xorg.conf.d/driver-intel.conf Section "Device" Identifier "Card0" Driver "intel" # BusID "PCI:1:0:0" EndSection If more than one video card is present, the BusID identifier can be uncommented and set to select the desired card. A list of video card bus IDs can be displayed with pciconf -lv | grep -B3 display. =2E.. and in your case, you MUST set the BusID attribute or X won't be able to figure out which device to configure. On 09.04.2016 09:31, =E6=89=BF=E6=81=A9=E5=BE=90 wrote: > Hi, everyone. >=20 > I'using a Hasee laptop Model:K580S-i7 D0. It has a optimus dual cards, = one > is Intel HD4000, the other nvidia GT650M. There is no option in BIOS to= > disable optimus. >=20 > I follow the link https://wiki.freebsd.org/Graphics. >=20 > I've the problem enabling intel card. > When I just use "intel" driver in xorg.conf, X won't start, compaining = no > device detected. I can only use the "vesa" driver, this way, X starts w= ell, > But I cannot switch back to console. When I pressed Alt-Shift-F1, it ju= st > went black, no response to any key but pressing power putton for 5 seco= nds. >=20 > Everytime trying loading i915kms kernel module, the kernel core dumps. > If i compiled the module into kernel or put it in /boot/loader.conf or > /etc/rc.conf, It will core dump in next booting process. > If I manully kldload the module, kernel will core dump right after i pr= ess > Enter. >=20 > I don't know why and how to resolve this. > Any help will be appreciated! Thanks. >=20 >=20 >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --StapjhqghVJJu3dhjqxscow0Q7EPp5uBi-- --89v1Qr4cbsTKdUrSJlVlbT74EMaL1AKJ0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcNSmIACgkQTBivhqtJa24KagEAhBiL6oB48EbsSCBN5jEaD4vt UNmFyTfw0HMaVOJQsdgA/iWoB9VY1nYoiJLrM4t2JZ+LbKFQM2SFHrZNjf2zZnvo =iwsJ -----END PGP SIGNATURE----- --89v1Qr4cbsTKdUrSJlVlbT74EMaL1AKJ0-- From owner-freebsd-x11@freebsd.org Tue Apr 12 19:57:37 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F027B0CC5A for ; Tue, 12 Apr 2016 19:57:37 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8361D1CFF for ; Tue, 12 Apr 2016 19:57:37 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1460491054869303.6786380262174; Tue, 12 Apr 2016 12:57:34 -0700 (PDT) Date: Tue, 12 Apr 2016 12:57:34 -0700 From: Matthew Macy To: "freebsd-x11@freebsd.org" Message-ID: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> Subject: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 12 Apr 2016 19:57:37 -0000 There seems to be some confusion about the state of drm-next-3.9. All the work is currently going on in jmd's fork of freebsd-base-graphics: https://github.com/iotamudelta/freebsd-base-graphics The emphasis has been on bringing i915 and the drm code in dev/drm2 closer to upstream as opposed to a simple driver refresh. I'm currently implementing missing linuxkpi bits and hope to actually be testing in the next week or so. As of this moment there is nothing available for general consumption. I very much hope to have this phase done before code freeze. I will update the list as soon as there is anything to test. Until then, hold your horses. The next phase will be more interesting to anyone who isn't simply waiting on bug fixes for Haswell support. My plan is to update DRM to 4.6 and import amdgpu and amdkfd support. I would like to be able to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu support is difficult to come up with. But certainly it will _not_ be any earlier than end of May. -M From owner-freebsd-x11@freebsd.org Wed Apr 13 14:32:13 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51CCDB0F35E for ; Wed, 13 Apr 2016 14:32:13 +0000 (UTC) (envelope-from mashomee@gmail.com) Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (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 C16A4127A for ; Wed, 13 Apr 2016 14:32:12 +0000 (UTC) (envelope-from mashomee@gmail.com) Received: by mail-lf0-x244.google.com with SMTP id p81so7580528lfb.3 for ; Wed, 13 Apr 2016 07:32:12 -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; bh=5vY1tAYbEfM0T4tumVna0uAEa+09E3L1sSzqcmEGi5k=; b=KhyqhZahn33uNmuMjuofLzrEyG1kCXEpp/mRMPwsvxPviqXBHETVdnS1dw8GkqeKoU bH087eUVuOCRoj5zcJUtPqqEZE/TPWDKAKENCyp++S46bVmft+gY19GwM25Azu1rtQ6v tShNMYG1pwwkuqM3jVEpfOdHWw8ei2ztGxzXPC0tqnwsIzOQaEruzYwrDXYazPvKWQTT mZgHsaHtT69JyiXXt3nkw/vfULM2LQ3U6EyAhfdM58NQlNmcP4egGuWKxJfo/qhjSJEM VXeki/A9xqZ3eU2vMdlw1JUY4OONOo6LTIUuI8uNNKPuHDIYlptvydVRa0fhwNBx4zbW 51sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=5vY1tAYbEfM0T4tumVna0uAEa+09E3L1sSzqcmEGi5k=; b=e1LbyCOzVQRGYRuKgMRfz1DSmbGwROxob84PGtgrRWSUjL5DSmENUFYOFsrvR0+9Rj UUYPdJ6+1sdQkh/XLJI3QGm8wpIlvBCJekLMDvcK6g7He0fPqtP9InqNabiQRnMLJulR sdAL+xpNCxgSTCBDGpkbZc9h2E0AWMTUj2eRH4pmdSQeIuw9YT6fCBk96wV/MF9O0MDc M/DNos0nMfV6+rLrQNE/MznqangVVkFIhDrxN6xpR+OG69V7jrd81ot5QumHchUHoea+ +8meDOLgRPw5nZH+sRmB4GKK5Vq2eLq+AepvDv0qEaNiQasch2YidPkLZmj0tyXcxEuF kIMw== X-Gm-Message-State: AOPr4FVJ+lNNNprFaXgxa9q7oNq0AGH6bBUWUpdWjDhWLcm+binEUvjzWII3FrnA/WnPtNygDTuDXN19ecCzAg== MIME-Version: 1.0 X-Received: by 10.112.73.40 with SMTP id i8mr4064271lbv.101.1460557930463; Wed, 13 Apr 2016 07:32:10 -0700 (PDT) Received: by 10.25.15.105 with HTTP; Wed, 13 Apr 2016 07:32:10 -0700 (PDT) In-Reply-To: <570D4A62.8010705@kapsi.fi> References: <570D4A62.8010705@kapsi.fi> Date: Wed, 13 Apr 2016 22:32:10 +0800 Message-ID: Subject: Re: kloadload i915kms cause kernel core dump From: =?UTF-8?B?5om/5oGp5b6Q?= To: Arto Pekkanen Cc: freebsd-x11@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 13 Apr 2016 14:32:13 -0000 Thanks for your reply! I've already done the stuff listed in https://www.freebsd.org/doc/handbook/x-config.html. vgapci1@pci0:0:2:0: class=3D0x030000 card=3D0x0934152d chip=3D0x0166808= 6 > rev=3D0x09 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '3rd Gen Core processor Graphics Controller' > class =3D display > subclass =3D VGA > bar [10] =3D type Memory, range 64, base 0xd3000000, size 4194304, > enabled > bar [18] =3D type Prefetchable Memory, range 64, base 0xc0000000, s= ize > 268435456, enabled > bar [20] =3D type I/O Port, range 32, base 0x5000, size 64, enabled > cap 05[90] =3D MSI supports 1 message > cap 01[d0] =3D powerspec 2 supports D0 D3 current D0 > cap 13[a4] =3D PCI Advanced Features: FLR TP > Here is my xorg.conf Section "Device" > Identifier "Card0" > Driver "vesa" > BusId "PCI:0:2:0" > EndSection > I've changed driver to "vesa", because as long as I use "intel", kernel core dumped at once because of the "i915kms" driver! I've just want know how to make intel driver works for me. Thank you. On Wed, Apr 13, 2016 at 3:20 AM, Arto Pekkanen wrote: > This topic has been discussed already many times before, so I am just > going to link the relevant Handbook article: > https://www.freebsd.org/doc/handbook/x-config.html > > Read through the section "Setting the Video Driver in a File" > > To set the Intel=C2=AE driver in a configuration file: > > Example 5.1. Select Intel=C2=AE Video Driver in a File > /usr/local/etc/X11/xorg.conf.d/driver-intel.conf > > Section "Device" > Identifier "Card0" > Driver "intel" > # BusID "PCI:1:0:0" > EndSection > > If more than one video card is present, the BusID identifier can be > uncommented and set to select the desired card. A list of video card bus > IDs can be displayed with pciconf -lv | grep -B3 display. > > ... and in your case, you MUST set the BusID attribute or X won't be > able to figure out which device to configure. > > On 09.04.2016 09:31, =E6=89=BF=E6=81=A9=E5=BE=90 wrote: > > Hi, everyone. > > > > I'using a Hasee laptop Model:K580S-i7 D0. It has a optimus dual cards, > one > > is Intel HD4000, the other nvidia GT650M. There is no option in BIOS to > > disable optimus. > > > > I follow the link https://wiki.freebsd.org/Graphics. > > > > I've the problem enabling intel card. > > When I just use "intel" driver in xorg.conf, X won't start, compaining = no > > device detected. I can only use the "vesa" driver, this way, X starts > well, > > But I cannot switch back to console. When I pressed Alt-Shift-F1, it ju= st > > went black, no response to any key but pressing power putton for 5 > seconds. > > > > Everytime trying loading i915kms kernel module, the kernel core dumps. > > If i compiled the module into kernel or put it in /boot/loader.conf or > > /etc/rc.conf, It will core dump in next booting process. > > If I manully kldload the module, kernel will core dump right after i > press > > Enter. > > > > I don't know why and how to resolve this. > > Any help will be appreciated! Thanks. > > > > > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > > > From owner-freebsd-x11@freebsd.org Wed Apr 13 23:18:52 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9123FB0ECD5 for ; Wed, 13 Apr 2016 23:18:52 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 522281AB1 for ; Wed, 13 Apr 2016 23:18:52 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqU3c-00047M-2t; Thu, 14 Apr 2016 02:18:48 +0300 Subject: Re: kloadload i915kms cause kernel core dump To: =?UTF-8?B?5om/5oGp5b6Q?= References: <570D4A62.8010705@kapsi.fi> Cc: freebsd-x11@freebsd.org From: Arto Pekkanen Message-ID: <570ED3D2.1020604@kapsi.fi> Date: Thu, 14 Apr 2016 02:18:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vg2pne7Xh6R7vxkmbK5WVEfDpXl2BBF1v" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 13 Apr 2016 23:18:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vg2pne7Xh6R7vxkmbK5WVEfDpXl2BBF1v Content-Type: multipart/mixed; boundary="hj6UOMLT0cPc6ABRVepNfKn3gNXbdpmhO" From: Arto Pekkanen To: =?UTF-8?B?5om/5oGp5b6Q?= Cc: freebsd-x11@freebsd.org Message-ID: <570ED3D2.1020604@kapsi.fi> Subject: Re: kloadload i915kms cause kernel core dump References: <570D4A62.8010705@kapsi.fi> In-Reply-To: --hj6UOMLT0cPc6ABRVepNfKn3gNXbdpmhO Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable If the kernel core dumps when X.org loads the i915kms driver, then there is a bug in the driver itself. The best course of action would be to make a PR. The PR should contain a full description of your hardware, full "pciconf -lvbe" output, description of actions that reproduce a kernel panic, /var/log/Xorg.0.log just before kernel panic and then a link to the core dump itself. To obtain an initial core dump, please follow these instructions: https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ker= neldebug.html#kerneldebug-obtain You can submit a PR here: https://bugs.freebsd.org/bugzilla/enter_bug.cgi After the initial PR has been submitted, the developers will sooner or later contact you and provide more information on what need be done. Do note that I have an Ivy Bridge laptop, and the i915kms + X.org work flawlessly without any problems. It is rather peculiar that it core dumps on your laptop with the same chipset. Thus it is just best let the developers figure it out. On 13.04.2016 17:32, =E6=89=BF=E6=81=A9=E5=BE=90 wrote: > Thanks for your reply! >=20 > I've already done the stuff listed in > https://www.freebsd.org/doc/handbook/x-config.html. > >=20 >=20 > vgapci1@pci0:0:2:0: class=3D0x030000 card=3D0x0934152d > chip=3D0x01668086 rev=3D0x09 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '3rd Gen Core processor Graphics Controller' > class =3D display > subclass =3D VGA > bar [10] =3D type Memory, range 64, base 0xd3000000, size > 4194304, enabled > bar [18] =3D type Prefetchable Memory, range 64, base > 0xc0000000, size 268435456, enabled > bar [20] =3D type I/O Port, range 32, base 0x5000, size 64, e= nabled > cap 05[90] =3D MSI supports 1 message > cap 01[d0] =3D powerspec 2 supports D0 D3 current D0 > cap 13[a4] =3D PCI Advanced Features: FLR TP >=20 >=20 > Here is my xorg.conf >=20 > Section "Device" > Identifier "Card0" > Driver "vesa" > BusId "PCI:0:2:0" > EndSection >=20 > I've changed driver to "vesa", because as long as I use "intel", kernel= > core dumped at once because of the "i915kms" driver! > I've just want know how to make intel driver works for me. > Thank you. > =20 >=20 >=20 > On Wed, Apr 13, 2016 at 3:20 AM, Arto Pekkanen > wrote: >=20 > This topic has been discussed already many times before, so I am ju= st > going to link the relevant Handbook article: > https://www.freebsd.org/doc/handbook/x-config.html >=20 > Read through the section "Setting the Video Driver in a File" >=20 > To set the Intel=C2=AE driver in a configuration file: >=20 > Example 5.1. Select Intel=C2=AE Video Driver in a File > /usr/local/etc/X11/xorg.conf.d/driver-intel.conf >=20 > Section "Device" > Identifier "Card0" > Driver "intel" > # BusID "PCI:1:0:0" > EndSection >=20 > If more than one video card is present, the BusID identifier can be= > uncommented and set to select the desired card. A list of video car= d bus > IDs can be displayed with pciconf -lv | grep -B3 display. >=20 > ... and in your case, you MUST set the BusID attribute or X won't b= e > able to figure out which device to configure. >=20 > On 09.04.2016 09:31, =E6=89=BF=E6=81=A9=E5=BE=90 wrote: > > Hi, everyone. > > > > I'using a Hasee laptop Model:K580S-i7 D0. It has a optimus dual > cards, one > > is Intel HD4000, the other nvidia GT650M. There is no option in > BIOS to > > disable optimus. > > > > I follow the link https://wiki.freebsd.org/Graphics. > > > > I've the problem enabling intel card. > > When I just use "intel" driver in xorg.conf, X won't start, > compaining no > > device detected. I can only use the "vesa" driver, this way, X > starts well, > > But I cannot switch back to console. When I pressed Alt-Shift-F1,= > it just > > went black, no response to any key but pressing power putton for = 5 > seconds. > > > > Everytime trying loading i915kms kernel module, the kernel core d= umps. > > If i compiled the module into kernel or put it in /boot/loader.co= nf or > > /etc/rc.conf, It will core dump in next booting process. > > If I manully kldload the module, kernel will core dump right afte= r > i press > > Enter. > > > > I don't know why and how to resolve this. > > Any help will be appreciated! Thanks. > > > > > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing = list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to > "freebsd-x11-unsubscribe@freebsd.org > " > > >=20 >=20 --hj6UOMLT0cPc6ABRVepNfKn3gNXbdpmhO-- --vg2pne7Xh6R7vxkmbK5WVEfDpXl2BBF1v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcO09IACgkQTBivhqtJa26pGAD/ZlAeQ4y4ef5pvgkJQJJKGEM+ QDxBnBPdLwUtHEwSbnUA+wcHr+hjckaSqgNR57vOR0xN6Ao7bqdlauwojLPYttax =+zBj -----END PGP SIGNATURE----- --vg2pne7Xh6R7vxkmbK5WVEfDpXl2BBF1v-- From owner-freebsd-x11@freebsd.org Wed Apr 13 23:22:33 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD04FB0EF63 for ; Wed, 13 Apr 2016 23:22:33 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 704A31E60 for ; Wed, 13 Apr 2016 23:22:33 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqU7D-0004rG-QG; Thu, 14 Apr 2016 02:22:31 +0300 Subject: Re: x11/nvidia-driver versions 358.16 and above - lockup when X server starts To: Bengt Ahlgren References: Cc: freebsd-x11@freebsd.org From: Arto Pekkanen Message-ID: <570ED4B7.6050703@kapsi.fi> Date: Thu, 14 Apr 2016 02:22:31 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Oqxi85csVgM6UGNF9ruqsUI4OuobOQJj1" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 13 Apr 2016 23:22:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Oqxi85csVgM6UGNF9ruqsUI4OuobOQJj1 Content-Type: multipart/mixed; boundary="UlLS7wQW7gVBlhs5c9JHCJ2aaJuAgThRj" From: Arto Pekkanen To: Bengt Ahlgren Cc: freebsd-x11@freebsd.org Message-ID: <570ED4B7.6050703@kapsi.fi> Subject: Re: x11/nvidia-driver versions 358.16 and above - lockup when X server starts References: In-Reply-To: --UlLS7wQW7gVBlhs5c9JHCJ2aaJuAgThRj Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable At this point I'd just follow the mentioned bugzilla link and wait for answer from nVidia. If you get a reply from nVidia, posting it to bugzilla might help. You could also discuss this in the nVidia forums, but I am not sure that helps. On 08.04.2016 22:18, Bengt Ahlgren wrote: > There seems to be a locking problem in the newer nvidia drivers (358.16= > and above that have the new nvidia-modeset.ko module). These are not i= n > the ports tree, but a port patch is being worked on to update it: >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201340 >=20 > With a WITNESS kernel, my system always locks up when the X server > starts after printing this: >=20 > Apr 8 19:44:11 ivy kernel: acquiring duplicate lock of same type: "os.= lock_sx" > Apr 8 19:44:11 ivy kernel: 1st os.lock_sx @ nvidia_os.c:593 > Apr 8 19:44:11 ivy kernel: 2nd os.lock_sx @ nvidia_os.c:593 > Apr 8 19:44:11 ivy kernel: KDB: stack backtrace: > Apr 8 19:44:11 ivy kernel: db_trace_self_wrapper() at db_trace_self_wr= apper+0x2b/frame 0xfffffe06651c7410 > Apr 8 19:44:11 ivy kernel: kdb_backtrace() at kdb_backtrace+0x39/frame= 0xfffffe06651c74c0 > Apr 8 19:44:11 ivy kernel: witness_checkorder() at witness_checkorder+= 0xe24/frame 0xfffffe06651c7550 > Apr 8 19:44:11 ivy kernel: _sx_xlock() at _sx_xlock+0x75/frame 0xfffff= e06651c7590 > Apr 8 19:44:11 ivy kernel: os_acquire_mutex() at os_acquire_mutex+0x32= /frame 0xfffffe06651c75b0 > Apr 8 19:44:11 ivy kernel: _nv014117rm() at _nv014117rm+0x18/frame 0xf= ffffe000a188e60 > Apr 8 19:44:11 ivy kernel: dmapbase() at 0xfffff80011527800 >=20 > The X server gets at least this far: >=20 > [ 164.014] (=3D=3D) NVIDIA(0): Depth 24, (=3D=3D) framebuffer bpp 32 > [ 164.014] (=3D=3D) NVIDIA(0): RGB weight 888 > [ 164.014] (=3D=3D) NVIDIA(0): Default visual is TrueColor > [ 164.014] (=3D=3D) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)= > [ 164.015] (**) NVIDIA(0): Enabling 2D acceleration >=20 > Without WITNESS, it locks up perhaps 1/3 of the time, and works fine > afterways if it didn't. I run FreeBSD 10.3-PRERELEASE amd64 r296673 on= > a desktop with a Z77 motherboard and a GeForce GTX 550 Ti. >=20 > Is there anything that the FreeBSD community can do with this info? I > have submitted a problem report to NVIDIA. >=20 > Bengt > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --UlLS7wQW7gVBlhs5c9JHCJ2aaJuAgThRj-- --Oqxi85csVgM6UGNF9ruqsUI4OuobOQJj1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcO1LcACgkQTBivhqtJa27vegD9HGMcQtMksK3nOrNT+5WXDh6e vbsKRXNDcZ2v18//+1kBAIBIL6bmlAG7N+pHFVcrGytakpsQSjGIC/uEq+ipYa1D =PY/c -----END PGP SIGNATURE----- --Oqxi85csVgM6UGNF9ruqsUI4OuobOQJj1-- From owner-freebsd-x11@freebsd.org Thu Apr 14 04:14:05 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24977B0FE2F for ; Thu, 14 Apr 2016 04:14:05 +0000 (UTC) (envelope-from jeremy.m.cox@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 D7F7D1D4D for ; Thu, 14 Apr 2016 04:14:04 +0000 (UTC) (envelope-from jeremy.m.cox@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id n130so26340970qke.3 for ; Wed, 13 Apr 2016 21:14:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=HqPJX2b95cH1iolMTRy22FmmeaPO/PGV0lAB4tAcJyI=; b=E8EABbJSh/GRMUAZ05yZ8pV24IGFQVVZmudv8waDzeUeZ+3r1txFyfOQw9fiSJhwhp MUlfwJhIMbJI9K9F1yLWEjcUZPudwNNSzJhxFgrqIbGLgH4fUgOHA+xmjs5ENtppnkil E2plEYTFDm8PHrh120WkWVKeK2XJ6KPcuFN2Jxo8lT4bb6WeWG1MEIWQp1jP2rb4TroD v5UDfn9CAWRHGETNpIooCz4JJ2L+RACHjqiE6U09JUygcYtdItnf9S4JvF1d9xmPQZv4 u0oB0ryN4/AAbPmMakOsK7qvguKeo0PkICDp3ZuAawgEJWWMBMlTjoAQtRR9yArqK72x 4jNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HqPJX2b95cH1iolMTRy22FmmeaPO/PGV0lAB4tAcJyI=; b=NO8jYwDlbm0Pkgl7LspANfYzTDNKxZcbf2WVsCNlnXWNG34gtc0QYkisgPuI7rXQHR e53vg6oh3MqYQDtC6U0TDfHgjEdudUghTRy5P4B7YwF0+M9xUW7LkydtThaa2982+2U8 uYxNobM38GI0b0YYQYcMY4aVJnXOh6fS8GE3JBfeCqVfpatS9/GOPxihhiGwmaF3VCtR 3oXGfZgk4jxIBu9e8wO889vitapHLbJaf0oS1MfGWYYjdGWRjghnJcgEudbiC8U1XIYB J5jzx7e3kWSST3NqvYtJwinnE2sAtwqtPAF5Ll/CFCjjsoWQ5fQLM4FN7I49rr+wW5X6 psJg== X-Gm-Message-State: AOPr4FUbgx9tlCssor/XkGWTK7HInrSn6bexo21E646c210nbRgViZGNrDGPgWgoUGYuOisiHq/EPxxzBov/FA== X-Received: by 10.55.78.207 with SMTP id c198mr15603832qkb.34.1460607243910; Wed, 13 Apr 2016 21:14:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.172.136 with HTTP; Wed, 13 Apr 2016 21:13:44 -0700 (PDT) From: Jeremy Date: Wed, 13 Apr 2016 23:13:44 -0500 Message-ID: Subject: 10.3 stable successfully running Haswell graphics To: freebsd-x11@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 04:14:05 -0000 Thanks for all of your hard work at FreeBSD. And thanks to *Masachika ISHIZUKA's *Haswell patch I am running my Haswell graphics on FreeBSD 10.3 stable (r297531M) using Xorg Server version 1.18.3 and KDE 4.14.3. The only issue I had was trying to get Xorg Server to start with my Nvidia card installed in my computer and Haswell graphics selected by the computer BIOS as the primary video, (but without my Nvidia card being used at all). I tried modifying the Xorg.conf file with BUSID and also tried removing the Nvidia configure lines from Xorg.conf but nothing worked, and it wouldn't start. I finally had to physically remove the Nvidia card to get the Haswell graphics to work. Other than that, the Haswell graphics works like a charm. Again, thank you all for your hard work! regards, Jeremy Cox From owner-freebsd-x11@freebsd.org Thu Apr 14 16:25:36 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CC77A93917 for ; Thu, 14 Apr 2016 16:25:36 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1DA719F7 for ; Thu, 14 Apr 2016 16:25:35 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqk5D-0005tf-Ic; Thu, 14 Apr 2016 19:25:31 +0300 Subject: Re: 10.3 stable successfully running Haswell graphics To: Jeremy References: Cc: freebsd-x11@FreeBSD.org From: Arto Pekkanen Message-ID: <570FC47B.1060302@kapsi.fi> Date: Thu, 14 Apr 2016 19:25:31 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DrvXiESaja46e7VpTxXWgqBFEOIHaAj4m" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 16:25:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DrvXiESaja46e7VpTxXWgqBFEOIHaAj4m Content-Type: multipart/mixed; boundary="N5Lj0b2OuPdsEelpsXnRkwc9wwUdwlh5G" From: Arto Pekkanen To: Jeremy Cc: freebsd-x11@FreeBSD.org Message-ID: <570FC47B.1060302@kapsi.fi> Subject: Re: 10.3 stable successfully running Haswell graphics References: In-Reply-To: --N5Lj0b2OuPdsEelpsXnRkwc9wwUdwlh5G Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable When the nVidia card was attached, did kldloading i915ikms cause kernel panic? Or was the problem merely X.org not detecting the intel GPU device= ? A person just before posted that their laptop with both intel and nVidia GPUs has kernel panic upon loading i915kms, even though the laptop Ivy Bridge chipset should be fully supported even in 10.3 without patches. Summa summarum: the DRM/KMS stack seems to misbehave with nVidia GPUs. This need to be fixed. More data required for devs. If you want to help, you could run FreeBSD HEAD from a USB stick and test if intel is usable with nVidia attached, and if not, report PR to the developers so they can fix this problem. On 14.04.2016 07:13, Jeremy wrote: > Thanks for all of your hard work at FreeBSD. And thanks to *Masachika > ISHIZUKA's *Haswell patch I am running my Haswell graphics on FreeBSD 1= 0.3 > stable (r297531M) using Xorg Server version 1.18.3 and KDE 4.14.3. >=20 > The only issue I had was trying to get Xorg Server to start with my Nvi= dia > card installed in my computer and Haswell graphics selected by the comp= uter > BIOS as the primary video, (but without my Nvidia card being used at al= l). > I tried modifying the Xorg.conf file with BUSID and also tried removing= the > Nvidia configure lines from Xorg.conf but nothing worked, and it wouldn= 't > start. I finally had to physically remove the Nvidia card to get the > Haswell graphics to work. Other than that, the Haswell graphics works l= ike > a charm. >=20 > Again, thank you all for your hard work! > regards, >=20 > Jeremy Cox > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --N5Lj0b2OuPdsEelpsXnRkwc9wwUdwlh5G-- --DrvXiESaja46e7VpTxXWgqBFEOIHaAj4m Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcPxHsACgkQTBivhqtJa25frQD+M5xsjmhc+MMlAgka/i7YlHlF jNsknqaw171Jeq4U3HcA/1J0uOz9SpKZWxV1AKgSjbPaxP9rmw/FM7oZdikNeUth =0Kd8 -----END PGP SIGNATURE----- --DrvXiESaja46e7VpTxXWgqBFEOIHaAj4m-- From owner-freebsd-x11@freebsd.org Thu Apr 14 18:53:51 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AC12ADA1AB for ; Thu, 14 Apr 2016 18:53:51 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D121A1937 for ; Thu, 14 Apr 2016 18:53:50 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqmOh-0002fG-54; Thu, 14 Apr 2016 21:53:47 +0300 Subject: Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy , "freebsd-x11@freebsd.org" References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> From: Arto Pekkanen Message-ID: <570FE736.6030803@kapsi.fi> Date: Thu, 14 Apr 2016 21:53:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="w2WCdTelWcAfCWobcXqcJfbvjKq90TfV4" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 18:53:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --w2WCdTelWcAfCWobcXqcJfbvjKq90TfV4 Content-Type: multipart/mixed; boundary="twS5hbJ5hRPJvW37sNbpTV1lLfvEFMm66" From: Arto Pekkanen To: Matthew Macy , "freebsd-x11@freebsd.org" Message-ID: <570FE736.6030803@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> In-Reply-To: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> --twS5hbJ5hRPJvW37sNbpTV1lLfvEFMm66 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Thanks for the heads up :) I am especially interested in the GPGPU support for AMDs, since this would actually make FreeBSD x86 rigs very useful for power efficient cluster computing. Thus far cheapest alternatives (on x86 hardware) have been based on Windows or Linux. On 12.04.2016 22:57, Matthew Macy wrote: > There seems to be some confusion about the state of drm-next-3.9. All t= he work is currently going on in jmd's fork of freebsd-base-graphics: >=20 > https://github.com/iotamudelta/freebsd-base-graphics >=20 > The emphasis has been on bringing i915 and the drm code in dev/drm2 cl= oser to upstream as opposed to a simple driver refresh. I'm currently imp= lementing missing linuxkpi bits and hope to actually be testing in the ne= xt week or so.=20 >=20 > As of this moment there is nothing available for general consumption. I= very much hope to have this phase done before code freeze. I will update= the list as soon as there is anything to test. Until then, hold your hor= ses. >=20 > The next phase will be more interesting to anyone who isn't simply wait= ing on bug fixes for Haswell support. My plan is to update DRM to 4.6 and= import amdgpu and amdkfd support. I would like to be able to do GPGPU wo= rk using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu support is difficu= lt to come up with. But certainly it will _not_ be any earlier than end o= f May. >=20 > -M >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --twS5hbJ5hRPJvW37sNbpTV1lLfvEFMm66-- --w2WCdTelWcAfCWobcXqcJfbvjKq90TfV4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcP5zYACgkQTBivhqtJa26FowD/fkyqUzJRGP4eDsAETNantAG1 stuYJU6ZO1DCeLgYJ6IBAJtnCGy+jkF8zbjZOJv7jKTLJgF8VKpMW2KuO9rJYLvF =T7zE -----END PGP SIGNATURE----- --w2WCdTelWcAfCWobcXqcJfbvjKq90TfV4-- From owner-freebsd-x11@freebsd.org Thu Apr 14 19:08:36 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D7BAADA6D5 for ; Thu, 14 Apr 2016 19:08:36 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 002E410F7 for ; Thu, 14 Apr 2016 19:08:35 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1460660903580171.0346539385971; Thu, 14 Apr 2016 12:08:23 -0700 (PDT) Date: Thu, 14 Apr 2016 12:08:23 -0700 From: Matthew Macy To: "Arto Pekkanen" Cc: Message-ID: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> In-Reply-To: <570FE736.6030803@kapsi.fi> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 User-Agent: Zoho Mail X-Mailer: Zoho Mail Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 19:08:36 -0000 =20 =20 Thanks for the heads up :)I am especially interested in the GPG= PU support for AMDs, since thiswould actually make FreeBSD x86 rigs very us= eful for power efficientcluster computing. Thus far cheapest alternatives (= on x86 hardware) havebeen based on Windows or Linux.Can I count you as a vo= lunteer to help jmd with user level runtime support? :D-MOn 12.04.2016 22:5= 7, Matthew Macy wrote:> There seems to be some confusion about the state of= drm-next-3.9. All the work is currently going on in jmd's fork of freebsd-= base-graphics:> > https://github.com/iotamudelta/freebsd-base-graphics> > T= he emphasis has been on bringing i915 and the drm code in dev/drm2 closer = to upstream as opposed to a simple driver refresh. I'm currently implementi= ng missing linuxkpi bits and hope to actually be testing in the next week o= r so. > > As of this moment there is nothing available for general consumpt= ion. I very much hope to have this phase done before code freeze. I will up= date the list as soon as there is anything to test. Until then, hold your h= orses.> > The next phase will be more interesting to anyone who isn't simpl= y waiting on bug fixes for Haswell support. My plan is to update DRM to 4.6= and import amdgpu and amdkfd support. I would like to be able to do GPGPU = work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu support is difficu= lt to come up with. But certainly it will _not_ be any earlier than end of = May.> > -M> > _______________________________________________> freebsd-x11@= freebsd.org mailing list> https://lists.freebsd.org/mailman/listinfo/freebs= d-x11> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.or= g">=20 =20 =20 =20 =20 From owner-freebsd-x11@freebsd.org Thu Apr 14 20:30:24 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79DE2AEC6CA for ; Thu, 14 Apr 2016 20:30:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3AF8D10F5 for ; Thu, 14 Apr 2016 20:30:24 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqnu9-0005ol-RS; Thu, 14 Apr 2016 23:30:21 +0300 Subject: Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> Cc: freebsd-x11@freebsd.org From: Arto Pekkanen Message-ID: <570FFDD8.1080700@kapsi.fi> Date: Thu, 14 Apr 2016 23:30:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="B09IxhN945GF4JM2m52Chim4cNXHrt2SJ" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 20:30:24 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ Content-Type: multipart/mixed; boundary="A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI" From: Arto Pekkanen To: Matthew Macy Cc: freebsd-x11@freebsd.org Message-ID: <570FFDD8.1080700@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> In-Reply-To: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> --A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Can't promise anything for certain. I don't have a Radeon chip or a spare rig right now, but I might get one later. If not, I might be able to fix a cheap, older laptop with a Radeon GPU. I've no experience systems level programming or anything like that. I was thinking more about *coin mining or SETI@Home, you know, the kinda entry level, brick layer stuff wannabe hackers run on their petty home servers. I could try enabling AMD GPGPU option in some *coin miner in the ports tree, or if there is no such miner app available try to port one for FreeBSD, provided that the required libraries are made available at the time. On 14.04.2016 22:08, Matthew Macy wrote: >=20 >=20 > Thanks for the heads up :) >=20 > I am especially interested in the GPGPU support for AMDs, since thi= s > would actually make FreeBSD x86 rigs very useful for power efficien= t > cluster computing. Thus far cheapest alternatives (on x86 hardware)= have > been based on Windows or Linux. >=20 >=20 > Can I count you as a volunteer to help jmd with user level runtime > support? :D >=20 >=20 > -M >=20 >=20 >=20 > On 12.04.2016 22:57, Matthew Macy wrote: > > There seems to be some confusion about the state of drm-next-3.9.= > All the work is currently going on in jmd's fork of > freebsd-base-graphics: > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > The emphasis has been on bringing i915 and the drm code in > dev/drm2 closer to upstream as opposed to a simple driver refresh. > I'm currently implementing missing linuxkpi bits and hope to > actually be testing in the next week or so. > > > > As of this moment there is nothing available for general > consumption. I very much hope to have this phase done before code > freeze. I will update the list as soon as there is anything to test= =2E > Until then, hold your horses. > > > > The next phase will be more interesting to anyone who isn't simpl= y > waiting on bug fixes for Haswell support. My plan is to update DRM > to 4.6 and import amdgpu and amdkfd support. I would like to be abl= e > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgp= u > support is difficult to come up with. But certainly it will _not_ b= e > any earlier than end of May. > > > > -M > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing = list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to > "freebsd-x11-unsubscribe@freebsd.org > " > > >=20 --A07V0MebMp7D13X0f5Xc4MtQQPRrt2SLI-- --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcP/dgACgkQTBivhqtJa26iQgD9HXw+9inEtrtWRPmDLnkNKSe0 29+vnKaW5q4KoHbRRcsA/3i7UDqx+wn34O3552/yIEEXIAE13cD0QrLVDyYB8EEh =pDdy -----END PGP SIGNATURE----- --B09IxhN945GF4JM2m52Chim4cNXHrt2SJ-- From owner-freebsd-x11@freebsd.org Thu Apr 14 20:38:42 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDA49AEC979 for ; Thu, 14 Apr 2016 20:38:42 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A138D16FE for ; Thu, 14 Apr 2016 20:38:42 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1460666316879886.2253694925103; Thu, 14 Apr 2016 13:38:36 -0700 (PDT) Date: Thu, 14 Apr 2016 13:38:36 -0700 From: Matthew Macy To: "Arto Pekkanen" Cc: "" Message-ID: <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> In-Reply-To: <570FFDD8.1080700@kapsi.fi> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 20:38:42 -0000 ---- On Thu, 14 Apr 2016 13:30:16 -0700 Arto Pekkanen wrote ---- > Can't promise anything for certain. I don't have a Radeon chip or a > spare rig right now, but I might get one later. If not, I might be able > to fix a cheap, older laptop with a Radeon GPU. > > I've no experience systems level programming or anything like that. I > was thinking more about *coin mining or SETI@Home, you know, the kinda > entry level, brick layer stuff wannabe hackers run on their petty home > servers. I could try enabling AMD GPGPU option in some *coin miner in > the ports tree, or if there is no such miner app available try to port > one for FreeBSD, provided that the required libraries are made available > at the time. The HSA/HCC code that I'm looking at only supports Fiji chips. An older Radeon won't buy you anything unless you can piece together the OpenCL bits. -M > On 14.04.2016 22:08, Matthew Macy wrote: > > > > > > Thanks for the heads up :) > > > > I am especially interested in the GPGPU support for AMDs, since this > > would actually make FreeBSD x86 rigs very useful for power efficient > > cluster computing. Thus far cheapest alternatives (on x86 hardware) have > > been based on Windows or Linux. > > > > > > Can I count you as a volunteer to help jmd with user level runtime > > support? :D > > > > > > -M > > > > > > > > On 12.04.2016 22:57, Matthew Macy wrote: > > > There seems to be some confusion about the state of drm-next-3.9. > > All the work is currently going on in jmd's fork of > > freebsd-base-graphics: > > > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > > > The emphasis has been on bringing i915 and the drm code in > > dev/drm2 closer to upstream as opposed to a simple driver refresh. > > I'm currently implementing missing linuxkpi bits and hope to > > actually be testing in the next week or so. > > > > > > As of this moment there is nothing available for general > > consumption. I very much hope to have this phase done before code > > freeze. I will update the list as soon as there is anything to test. > > Until then, hold your horses. > > > > > > The next phase will be more interesting to anyone who isn't simply > > waiting on bug fixes for Haswell support. My plan is to update DRM > > to 4.6 and import amdgpu and amdkfd support. I would like to be able > > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu > > support is difficult to come up with. But certainly it will _not_ be > > any earlier than end of May. > > > > > > -M > > > > > > _______________________________________________ > > > freebsd-x11@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > To unsubscribe, send any mail to > > "freebsd-x11-unsubscribe@freebsd.org > > " > > > > > > > From owner-freebsd-x11@freebsd.org Thu Apr 14 20:53:13 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AF7DAECFF8 for ; Thu, 14 Apr 2016 20:53:13 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45CB812C2 for ; Thu, 14 Apr 2016 20:53:13 +0000 (UTC) (envelope-from isoa@kapsi.fi) Received: from 91-159-15-56.elisa-laajakaista.fi ([91.159.15.56] helo=[192.168.255.143]) by mail.kapsi.fi with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1aqoGF-00037Y-Du; Thu, 14 Apr 2016 23:53:11 +0300 Subject: Re: clarifying the state of drm-next-3.9 and next steps To: Matthew Macy References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> Cc: freebsd-x11@freebsd.org From: Arto Pekkanen Message-ID: <57100336.8080101@kapsi.fi> Date: Thu, 14 Apr 2016 23:53:10 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MtXU9raWWgMobiJjtufSnqFjsug5e3pJs" X-SA-Exim-Connect-IP: 91.159.15.56 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 20:53:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MtXU9raWWgMobiJjtufSnqFjsug5e3pJs Content-Type: multipart/mixed; boundary="KWdTEnn6FqdQPnx1TjJh6bGcaUc31Wwc1" From: Arto Pekkanen To: Matthew Macy Cc: freebsd-x11@freebsd.org Message-ID: <57100336.8080101@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> In-Reply-To: <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> --KWdTEnn6FqdQPnx1TjJh6bGcaUc31Wwc1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ah okay ... hmmm, that would mean Radeon R9 -series gfx cards right? In that case I'll have to see if I can get such a card somewhere dirt cheap. No promises though. If I happen to get Fiji architecture based device somewhere I would help in testing AMD GPGPU. On 14.04.2016 23:38, Matthew Macy wrote: >=20 >=20 >=20 > ---- On Thu, 14 Apr 2016 13:30:16 -0700 Arto Pekkanen = wrote ----=20 > > Can't promise anything for certain. I don't have a Radeon chip or a > > spare rig right now, but I might get one later. If not, I might be a= ble > > to fix a cheap, older laptop with a Radeon GPU. > >=20 > > I've no experience systems level programming or anything like that. = I > > was thinking more about *coin mining or SETI@Home, you know, the kin= da > > entry level, brick layer stuff wannabe hackers run on their petty ho= me > > servers. I could try enabling AMD GPGPU option in some *coin miner i= n > > the ports tree, or if there is no such miner app available try to po= rt > > one for FreeBSD, provided that the required libraries are made avail= able > > at the time. > =20 > The HSA/HCC code that I'm looking at only supports Fiji chips. An older= Radeon won't buy you anything unless you can piece together the OpenCL b= its. >=20 > -M >=20 > =20 > > On 14.04.2016 22:08, Matthew Macy wrote: > > >=20 > > >=20 > > > Thanks for the heads up :) > > >=20 > > > I am especially interested in the GPGPU support for AMDs, sinc= e this > > > would actually make FreeBSD x86 rigs very useful for power eff= icient > > > cluster computing. Thus far cheapest alternatives (on x86 hard= ware) have > > > been based on Windows or Linux. > > >=20 > > >=20 > > > Can I count you as a volunteer to help jmd with user level run= time > > > support? :D > > >=20 > > >=20 > > > -M > > >=20 > > >=20 > > >=20 > > > On 12.04.2016 22:57, Matthew Macy wrote: > > > > There seems to be some confusion about the state of drm-next= -3.9. > > > All the work is currently going on in jmd's fork of > > > freebsd-base-graphics: > > > > > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > > > > > The emphasis has been on bringing i915 and the drm code in > > > dev/drm2 closer to upstream as opposed to a simple driver refr= esh. > > > I'm currently implementing missing linuxkpi bits and hope to > > > actually be testing in the next week or so. > > > > > > > > As of this moment there is nothing available for general > > > consumption. I very much hope to have this phase done before c= ode > > > freeze. I will update the list as soon as there is anything to= test. > > > Until then, hold your horses. > > > > > > > > The next phase will be more interesting to anyone who isn't = simply > > > waiting on bug fixes for Haswell support. My plan is to update= DRM > > > to 4.6 and import amdgpu and amdkfd support. I would like to b= e able > > > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/= amdgpu > > > support is difficult to come up with. But certainly it will _n= ot_ be > > > any earlier than end of May. > > > > > > > > -M > > > > > > > > _______________________________________________ > > > > freebsd-x11@freebsd.org mai= ling list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > > To unsubscribe, send any mail to > > > "freebsd-x11-unsubscribe@freebsd.org > > > " > > > > > > >=20 > >=20 > >=20 >=20 --KWdTEnn6FqdQPnx1TjJh6bGcaUc31Wwc1-- --MtXU9raWWgMobiJjtufSnqFjsug5e3pJs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlcQAzYACgkQTBivhqtJa2788wD+OIayVXXc0peU7JLxAgmggpEK 7WlDASfZ51q3kwJahVEBAMKQ2OKskiG9mJBFA+5ouMZhOv2n4BiPv8ioX5E2jIxj =Xjoi -----END PGP SIGNATURE----- --MtXU9raWWgMobiJjtufSnqFjsug5e3pJs-- From owner-freebsd-x11@freebsd.org Thu Apr 14 20:55:51 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8EE95ADA0DA for ; Thu, 14 Apr 2016 20:55:51 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 816CC134D for ; Thu, 14 Apr 2016 20:55:50 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1460667346187601.6163148563185; Thu, 14 Apr 2016 13:55:46 -0700 (PDT) Date: Thu, 14 Apr 2016 13:55:45 -0700 From: Matthew Macy To: "Arto Pekkanen" Cc: "" Message-ID: <154168eebfa.120e8391b214980.2542727951982765933@nextbsd.org> In-Reply-To: <57100336.8080101@kapsi.fi> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> <57100336.8080101@kapsi.fi> Subject: Re: clarifying the state of drm-next-3.9 and next steps MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 20:55:51 -0000 ---- On Thu, 14 Apr 2016 13:53:10 -0700 Arto Pekkanen wrote ---- > Ah okay ... hmmm, that would mean Radeon R9 -series gfx cards right? Yes. > In that case I'll have to see if I can get such a card somewhere dirt > cheap. No promises though. > > If I happen to get Fiji architecture based device somewhere I would help > in testing AMD GPGPU. Polaris is coming out shortly, at which point lower-end Fiji cards will probably come down in price. -M > On 14.04.2016 23:38, Matthew Macy wrote: > > > > > > > > ---- On Thu, 14 Apr 2016 13:30:16 -0700 Arto Pekkanen wrote ---- > > > Can't promise anything for certain. I don't have a Radeon chip or a > > > spare rig right now, but I might get one later. If not, I might be able > > > to fix a cheap, older laptop with a Radeon GPU. > > > > > > I've no experience systems level programming or anything like that. I > > > was thinking more about *coin mining or SETI@Home, you know, the kinda > > > entry level, brick layer stuff wannabe hackers run on their petty home > > > servers. I could try enabling AMD GPGPU option in some *coin miner in > > > the ports tree, or if there is no such miner app available try to port > > > one for FreeBSD, provided that the required libraries are made available > > > at the time. > > > > The HSA/HCC code that I'm looking at only supports Fiji chips. An older Radeon won't buy you anything unless you can piece together the OpenCL bits. > > > > -M > > > > > > > On 14.04.2016 22:08, Matthew Macy wrote: > > > > > > > > > > > > Thanks for the heads up :) > > > > > > > > I am especially interested in the GPGPU support for AMDs, since this > > > > would actually make FreeBSD x86 rigs very useful for power efficient > > > > cluster computing. Thus far cheapest alternatives (on x86 hardware) have > > > > been based on Windows or Linux. > > > > > > > > > > > > Can I count you as a volunteer to help jmd with user level runtime > > > > support? :D > > > > > > > > > > > > -M > > > > > > > > > > > > > > > > On 12.04.2016 22:57, Matthew Macy wrote: > > > > > There seems to be some confusion about the state of drm-next-3.9. > > > > All the work is currently going on in jmd's fork of > > > > freebsd-base-graphics: > > > > > > > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > > > > > > > The emphasis has been on bringing i915 and the drm code in > > > > dev/drm2 closer to upstream as opposed to a simple driver refresh. > > > > I'm currently implementing missing linuxkpi bits and hope to > > > > actually be testing in the next week or so. > > > > > > > > > > As of this moment there is nothing available for general > > > > consumption. I very much hope to have this phase done before code > > > > freeze. I will update the list as soon as there is anything to test. > > > > Until then, hold your horses. > > > > > > > > > > The next phase will be more interesting to anyone who isn't simply > > > > waiting on bug fixes for Haswell support. My plan is to update DRM > > > > to 4.6 and import amdgpu and amdkfd support. I would like to be able > > > > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu > > > > support is difficult to come up with. But certainly it will _not_ be > > > > any earlier than end of May. > > > > > > > > > > -M > > > > > > > > > > _______________________________________________ > > > > > freebsd-x11@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > > > To unsubscribe, send any mail to > > > > "freebsd-x11-unsubscribe@freebsd.org > > > > " > > > > > > > > > > > > > > > > > > > From owner-freebsd-x11@freebsd.org Thu Apr 14 21:10:41 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B56FADA71B for ; Thu, 14 Apr 2016 21:10:41 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) Received: from nm18-vm0.bullet.mail.bf1.yahoo.com (nm18-vm0.bullet.mail.bf1.yahoo.com [98.139.213.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFF3C1291 for ; Thu, 14 Apr 2016 21:10:40 +0000 (UTC) (envelope-from Scoobi_doo@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460668232; bh=s2XnbtdGstIegyDiK2A7rjSa4xridNxrNOsigaQndXE=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From:Subject; b=kTcy6FifIWY91AJkxxPw7gt5l7UkHLOXSBI/dT28BRPC4eSb5IR8yvhNQh8Os30q1qQKz2L4O3e+wwOVRhZWbCROultgA9cQIJRN98krx1PPgN6PPA7MwQyOe9LbaybQsUqw83+qGr1EinHyFBKcI0DeovSR0OTBg/S9SopZpxi78MGQ7YuLNo3ojk8tBBRiJIexOIuPth0cwF8WAmq+7hCETo74sAVaoLCkW/1nTUzielFGUHavh314dWsfs9mDM83CE6MXSpGkUHjfQWdB7IYrxOT/4LO0aAxH7UuzDmF1DeXMOrLqLKoD1Cz0qqyFN/kPz9fHgaVDq7cyiJ3i1Q== Received: from [66.196.81.173] by nm18.bullet.mail.bf1.yahoo.com with NNFMP; 14 Apr 2016 21:10:32 -0000 Received: from [98.139.211.199] by tm19.bullet.mail.bf1.yahoo.com with NNFMP; 14 Apr 2016 21:10:32 -0000 Received: from [127.0.0.1] by smtp208.mail.bf1.yahoo.com with NNFMP; 14 Apr 2016 21:10:32 -0000 X-Yahoo-Newman-Id: 659385.70585.bm@smtp208.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 9dRQPaUVM1mBqJZ02DjEGt8zll.NWH1SBdbpclIWjAXEAef o0WNqdYMWgkqgYRZVYdOhB4cG.kxmcZtOyJQWlrZfU2hsPR6PB8T7eHbnIdP FF4MV8xwCz8Pz7yjbjt8RGEDdLVE127G8Zs6T8FGqZAQGZI6VopQh8JaEqzy KQ21y6Xf5g6fyTaghWdzI8CN7Yzr4rix__8_6vg3XSxT9OBEYVkaZG_kkxAJ IIqXiPCJdq2OC_xGQ9OTUPDm.mJeJbURels4J6xp15o99kV71fCuAC31YKO7 72isqMNHK2XezzfJ4Vglv3q1H8E6spTZjw0rEMFHpLhNPE2oc_6fTgpyjjBn PWGtLjmYDKTt1m4t0XdfNaqv5rbaX5DpN4rBFeQccABHrlU00_ZhZ4C4h4fg NuvO.PBMvebVuPRZuwmX30ShKM8iV1vqrTPAqKpsk30yXuVlu2U5.LRottRy _D60eu7ZFPsviwWd1U7_941B.38pngMrppAyC74NA1NYEbXznfN5Q.td1._M QSPM2sVeidiOEZNEPhYfytCnOIYIc77HYUA-- X-Yahoo-SMTP: 9sPoSQ2swBBlERuQ.0vs8XLc_MeClW0- Subject: AMD GPUs (was Re: clarifying the state of drm-next-3.9 and next steps) To: Matthew Macy , Arto Pekkanen References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> <57100336.8080101@kapsi.fi> <154168eebfa.120e8391b214980.2542727951982765933@nextbsd.org> Cc: "" From: Anthony Jenkins Message-ID: <57100747.8060003@yahoo.com> Date: Thu, 14 Apr 2016 17:10:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <154168eebfa.120e8391b214980.2542727951982765933@nextbsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 21:10:41 -0000 On 04/14/2016 04:55 PM, Matthew Macy wrote: > ---- On Thu, 14 Apr 2016 13:53:10 -0700 Arto Pekkanen wrote ---- > > Ah okay ... hmmm, that would mean Radeon R9 -series gfx cards right? > > Yes. > > > In that case I'll have to see if I can get such a card somewhere dirt > > cheap. No promises though. > > > > If I happen to get Fiji architecture based device somewhere I would help > > in testing AMD GPGPU. > > Polaris is coming out shortly, at which point lower-end Fiji cards will probably come down in price. > > -M I have a Radeon HD 8610G, trying to get set up to port the Linux radeonkms files over (or does amdgpu cover my card?). Happy to help test anything. Anthony > > On 14.04.2016 23:38, Matthew Macy wrote: > > > > > > > > > > > > ---- On Thu, 14 Apr 2016 13:30:16 -0700 Arto Pekkanen wrote ---- > > > > Can't promise anything for certain. I don't have a Radeon chip or a > > > > spare rig right now, but I might get one later. If not, I might be able > > > > to fix a cheap, older laptop with a Radeon GPU. > > > > > > > > I've no experience systems level programming or anything like that. I > > > > was thinking more about *coin mining or SETI@Home, you know, the kinda > > > > entry level, brick layer stuff wannabe hackers run on their petty home > > > > servers. I could try enabling AMD GPGPU option in some *coin miner in > > > > the ports tree, or if there is no such miner app available try to port > > > > one for FreeBSD, provided that the required libraries are made available > > > > at the time. > > > > > > The HSA/HCC code that I'm looking at only supports Fiji chips. An older Radeon won't buy you anything unless you can piece together the OpenCL bits. > > > > > > -M > > > > > > > > > > On 14.04.2016 22:08, Matthew Macy wrote: > > > > > > > > > > > > > > > Thanks for the heads up :) > > > > > > > > > > I am especially interested in the GPGPU support for AMDs, since this > > > > > would actually make FreeBSD x86 rigs very useful for power efficient > > > > > cluster computing. Thus far cheapest alternatives (on x86 hardware) have > > > > > been based on Windows or Linux. > > > > > > > > > > > > > > > Can I count you as a volunteer to help jmd with user level runtime > > > > > support? :D > > > > > > > > > > > > > > > -M > > > > > > > > > > > > > > > > > > > > On 12.04.2016 22:57, Matthew Macy wrote: > > > > > > There seems to be some confusion about the state of drm-next-3.9. > > > > > All the work is currently going on in jmd's fork of > > > > > freebsd-base-graphics: > > > > > > > > > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > > > > > > > > > The emphasis has been on bringing i915 and the drm code in > > > > > dev/drm2 closer to upstream as opposed to a simple driver refresh. > > > > > I'm currently implementing missing linuxkpi bits and hope to > > > > > actually be testing in the next week or so. > > > > > > > > > > > > As of this moment there is nothing available for general > > > > > consumption. I very much hope to have this phase done before code > > > > > freeze. I will update the list as soon as there is anything to test. > > > > > Until then, hold your horses. > > > > > > > > > > > > The next phase will be more interesting to anyone who isn't simply > > > > > waiting on bug fixes for Haswell support. My plan is to update DRM > > > > > to 4.6 and import amdgpu and amdkfd support. I would like to be able > > > > > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu > > > > > support is difficult to come up with. But certainly it will _not_ be > > > > > any earlier than end of May. > > > > > > > > > > > > -M > > > > > > > > > > > > _______________________________________________ > > > > > > freebsd-x11@freebsd.org mailing list > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > > > > To unsubscribe, send any mail to > > > > > "freebsd-x11-unsubscribe@freebsd.org > > > > > " > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" -- Anthony Jenkins From owner-freebsd-x11@freebsd.org Thu Apr 14 21:13:33 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A15AAADA97B for ; Thu, 14 Apr 2016 21:13:33 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from sender163-mail.zoho.com (sender163-mail.zoho.com [74.201.84.163]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8EF3C17D6 for ; Thu, 14 Apr 2016 21:13:33 +0000 (UTC) (envelope-from mmacy@nextbsd.org) Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1460668407472622.1823850670023; Thu, 14 Apr 2016 14:13:27 -0700 (PDT) Date: Thu, 14 Apr 2016 14:13:27 -0700 From: Matthew Macy To: "Anthony Jenkins" Cc: "Arto Pekkanen" , "" Message-ID: <154169f1e5f.b98b7f12215801.4199002365350040402@nextbsd.org> In-Reply-To: <57100747.8060003@yahoo.com> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> <570FFDD8.1080700@kapsi.fi> <154167f380a.11029a097214164.5670903735512919638@nextbsd.org> <57100336.8080101@kapsi.fi> <154168eebfa.120e8391b214980.2542727951982765933@nextbsd.org> <57100747.8060003@yahoo.com> Subject: Re: AMD GPUs (was Re: clarifying the state of drm-next-3.9 and next steps) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 21:13:33 -0000 > > Polaris is coming out shortly, at which point lower-end Fiji cards will probably come down in price. > > > > -M > > I have a Radeon HD 8610G, trying to get set up to port the Linux > radeonkms files over (or does amdgpu cover my card?). Happy to help > test anything. It's probably still covered by Radeon as it's a representative of their older VLIW architecture: http://www.notebookcheck.net/AMD-Radeon-HD-8610G.93719.0.html > Anthony > > > > On 14.04.2016 23:38, Matthew Macy wrote: > > > > > > > > > > > > > > > > ---- On Thu, 14 Apr 2016 13:30:16 -0700 Arto Pekkanen wrote ---- > > > > > Can't promise anything for certain. I don't have a Radeon chip or a > > > > > spare rig right now, but I might get one later. If not, I might be able > > > > > to fix a cheap, older laptop with a Radeon GPU. > > > > > > > > > > I've no experience systems level programming or anything like that. I > > > > > was thinking more about *coin mining or SETI@Home, you know, the kinda > > > > > entry level, brick layer stuff wannabe hackers run on their petty home > > > > > servers. I could try enabling AMD GPGPU option in some *coin miner in > > > > > the ports tree, or if there is no such miner app available try to port > > > > > one for FreeBSD, provided that the required libraries are made available > > > > > at the time. > > > > > > > > The HSA/HCC code that I'm looking at only supports Fiji chips. An older Radeon won't buy you anything unless you can piece together the OpenCL bits. > > > > > > > > -M > > > > > > > > > > > > > On 14.04.2016 22:08, Matthew Macy wrote: > > > > > > > > > > > > > > > > > > Thanks for the heads up :) > > > > > > > > > > > > I am especially interested in the GPGPU support for AMDs, since this > > > > > > would actually make FreeBSD x86 rigs very useful for power efficient > > > > > > cluster computing. Thus far cheapest alternatives (on x86 hardware) have > > > > > > been based on Windows or Linux. > > > > > > > > > > > > > > > > > > Can I count you as a volunteer to help jmd with user level runtime > > > > > > support? :D > > > > > > > > > > > > > > > > > > -M > > > > > > > > > > > > > > > > > > > > > > > > On 12.04.2016 22:57, Matthew Macy wrote: > > > > > > > There seems to be some confusion about the state of drm-next-3.9. > > > > > > All the work is currently going on in jmd's fork of > > > > > > freebsd-base-graphics: > > > > > > > > > > > > > > https://github.com/iotamudelta/freebsd-base-graphics > > > > > > > > > > > > > > The emphasis has been on bringing i915 and the drm code in > > > > > > dev/drm2 closer to upstream as opposed to a simple driver refresh. > > > > > > I'm currently implementing missing linuxkpi bits and hope to > > > > > > actually be testing in the next week or so. > > > > > > > > > > > > > > As of this moment there is nothing available for general > > > > > > consumption. I very much hope to have this phase done before code > > > > > > freeze. I will update the list as soon as there is anything to test. > > > > > > Until then, hold your horses. > > > > > > > > > > > > > > The next phase will be more interesting to anyone who isn't simply > > > > > > waiting on bug fixes for Haswell support. My plan is to update DRM > > > > > > to 4.6 and import amdgpu and amdkfd support. I would like to be able > > > > > > to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdgpu > > > > > > support is difficult to come up with. But certainly it will _not_ be > > > > > > any earlier than end of May. > > > > > > > > > > > > > > -M > > > > > > > > > > > > > > _______________________________________________ > > > > > > > freebsd-x11@freebsd.org mailing list > > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > > > > > To unsubscribe, send any mail to > > > > > > "freebsd-x11-unsubscribe@freebsd.org > > > > > > " > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > -- > Anthony Jenkins > > From owner-freebsd-x11@freebsd.org Thu Apr 14 23:30:32 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4915ADA2E2 for ; Thu, 14 Apr 2016 23:30:32 +0000 (UTC) (envelope-from jeremy.m.cox@gmail.com) Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 7F93211D3 for ; Thu, 14 Apr 2016 23:30:32 +0000 (UTC) (envelope-from jeremy.m.cox@gmail.com) Received: by mail-qg0-x230.google.com with SMTP id c6so72749689qga.1 for ; Thu, 14 Apr 2016 16:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+lZb0N6r2NmzALNQGCYzdegIae3v3gSSaP1JQ58ljwk=; b=opl0zeRMIdcPaB9FPRR2G+tXoazHMxD0LguRkxOBlP16w/lQoRJfrEw+jLzluIBWTm TZnHvnqILgGhcV9PZlU7SPO8Eg7OBz7q+eZE0Rk8hi0ClTYTqHzUe5XNm2wRzXUH/dlo O1s16yhMmFIPk62QzT4jMLVhj9RP7G3XXTtYynWjfiIoziVaKvFL9fO6gfJgCIru1FeX jwRURMOBUbgWX5SbKs7fkUFN1OcoNVCySMEKMdrYpiZk1wbHUYVRuFFMD9QcdQm6DIBH XXqHNFfe0HGJfTPDjHP2vvaSb7F9bSNUKc5FGYYDv79pOmUAJnZYSBvrJTx91fkElLt/ 6oyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+lZb0N6r2NmzALNQGCYzdegIae3v3gSSaP1JQ58ljwk=; b=du0nwicPDefC72nyAs0W/vLgcKyMQhEVBQnAIHLW/OCpBXhH3rhOWNT8ezsdUhCz59 7jJzQ4n/AoMaqa3oJjve5yv7fYKDlVB18WBVOtcm8ufJpJ98fg5JQv95EbJwA9MaWm9V IcF3xpwJdGZRaRGMY3JLttCR3LjTx+SeiyIzRw7jD3Ox3jizwHqVpcAE4agzffFRYb0N wh855WLolTfVYJTagLCBgu+LJT6fwfQ9MzJRHaZAretEM72KHnadRJAhGgORuFKBvC4K m3e5XvarJoU2tyYzdcDY8nS+/t6uc7QTAdx4vSdB1PHNazgFj6CYi8yC/I+gsknqq3lk zn5A== X-Gm-Message-State: AOPr4FUJo8NNrl/36vKgwhzFIAh8MK9Dik6aCRamtiB+W5CdBUVtc5VN0Yb0s1oAuDHijMnytXNBF+6N+yHI1w== X-Received: by 10.140.181.137 with SMTP id c131mr22883127qha.94.1460676631410; Thu, 14 Apr 2016 16:30:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.172.136 with HTTP; Thu, 14 Apr 2016 16:30:12 -0700 (PDT) In-Reply-To: <570FC47B.1060302@kapsi.fi> References: <570FC47B.1060302@kapsi.fi> From: Jeremy Date: Thu, 14 Apr 2016 18:30:12 -0500 Message-ID: Subject: Re: 10.3 stable successfully running Haswell graphics To: Arto Pekkanen Cc: freebsd-x11@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 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, 14 Apr 2016 23:30:32 -0000 When the nVidia card was attached, did kldloading i915ikms cause kernel panic? Or was the problem merely X.org not detecting the intel GPU device? I wish I would have kept the dmesg log for that period. But if I remember correctly, both video devices were detected by FreeBSD, the Nvidia Card and the iGPU from Intel. I actually have the xorg.log.., I'll clip some of it except for the relevant information: [ 2462.054] X.Org X Server 1.17.4 Release Date: 2015-10-28 [ 2462.054] X Protocol Version 11, Revision 0 [ 2462.054] Build Operating System: FreeBSD 10.3-PRERELEASE amd64 [ 2462.054] Current Operating System: FreeBSD riotskates 10.3-PRERELEASE FreeBSD 10.3-PRERELEASE #0 r297531M: Mon Apr 4 00:05:47 CDT 2016 root@riotskates:/usr/obj/usr/src/sys/I915 amd64 [ 2462.055] Build Date: 03 April 2016 08:06:13PM [ 2462.055] [ 2462.055] Current version of pixman: 0.34.0 [ 2462.055] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. ... [ 2462.058] (II) Module ABI versions: [ 2462.058] X.Org ANSI C Emulation: 0.4 [ 2462.058] X.Org Video Driver: 19.0 [ 2462.058] X.Org XInput driver : 21.0 [ 2462.058] X.Org Server Extension : 9.0 [ 2462.058] (!!) More than one possible primary device found [ 2462.058] (--) PCI: (0:0:2:0) 8086:0412:103c:2af3 rev 6, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/65536 [ 2462.058] (--) PCI: (0:1:0:0) 10de:11c2:196e:104c rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/134217728, 0xe8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/65536 [ 2462.059] (II) "glx" will be loaded. This was enabled by default and also specified in the config file. [ 2462.059] (II) LoadModule: "glx" [ 2462.059] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 2462.089] (II) Module glx: vendor="NVIDIA Corporation" [ 2462.089] compiled for 4.0.2, module version = 1.0.0 [ 2462.089] Module class: X.Org Server Extension [ 2462.089] (II) NVIDIA GLX Module 346.96 Sun Aug 23 21:29:48 PDT 2015 [ 2462.089] (II) LoadModule: "nvidia" [ 2462.090] (II) Loading /usr/local/lib/xorg/modules/drivers/nvidia_drv.so [ 2462.091] (II) Module nvidia: vendor="NVIDIA Corporation" [ 2462.091] compiled for 4.0.2, module version = 1.0.0 [ 2462.091] Module class: X.Org Video Driver [ 2462.091] (II) NVIDIA dlloader X Driver 346.96 Sun Aug 23 21:08:26 PDT 2015 [ 2462.091] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 2462.091] (--) Using syscons driver with X support (version 0.x) [ 2462.091] (--) using VT number 9 [ 2462.091] (EE) No devices detected. [ 2462.092] (EE) Fatal server error: [ 2462.092] (EE) no screens found(EE) [ 2462.092] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 2462.092] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 2462.092] (EE) [ 2462.092] (EE) Server terminated with error (1). Closing log file. The error from Xorg was more than one possible primary device found, no devices detected, no screens found. Even though I selected the primary video as the iGPU from Intel thru the BIOS, it looks like Xorg was confused. The kernel never did panic though, Xorg just never started. I am using a desktop computer, and the Nvidia card was an addon I originally intended to use only as a GPGPU thru Windows. But It became my video card for FreeBSD while I waited for the Haswell port to be completed. Regards, Jeremy Cox On Thu, Apr 14, 2016 at 11:25 AM, Arto Pekkanen wrote: > When the nVidia card was attached, did kldloading i915ikms cause kernel > panic? Or was the problem merely X.org not detecting the intel GPU device? > > A person just before posted that their laptop with both intel and nVidia > GPUs has kernel panic upon loading i915kms, even though the laptop Ivy > Bridge chipset should be fully supported even in 10.3 without patches. > > Summa summarum: the DRM/KMS stack seems to misbehave with nVidia GPUs. > This need to be fixed. More data required for devs. > > If you want to help, you could run FreeBSD HEAD from a USB stick and > test if intel is usable with nVidia attached, and if not, report PR to > the developers so they can fix this problem. > > On 14.04.2016 07:13, Jeremy wrote: > > Thanks for all of your hard work at FreeBSD. And thanks to *Masachika > > ISHIZUKA's *Haswell patch I am running my Haswell graphics on FreeBSD > 10.3 > > stable (r297531M) using Xorg Server version 1.18.3 and KDE 4.14.3. > > > > The only issue I had was trying to get Xorg Server to start with my > Nvidia > > card installed in my computer and Haswell graphics selected by the > computer > > BIOS as the primary video, (but without my Nvidia card being used at > all). > > I tried modifying the Xorg.conf file with BUSID and also tried removing > the > > Nvidia configure lines from Xorg.conf but nothing worked, and it wouldn't > > start. I finally had to physically remove the Nvidia card to get the > > Haswell graphics to work. Other than that, the Haswell graphics works > like > > a charm. > > > > Again, thank you all for your hard work! > > regards, > > > > Jeremy Cox > > _______________________________________________ > > freebsd-x11@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" > > > > From owner-freebsd-x11@freebsd.org Fri Apr 15 15:14:20 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04FD8AEEC76 for ; Fri, 15 Apr 2016 15:14:20 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B98021DB6 for ; Fri, 15 Apr 2016 15:14:19 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1ar5Rm-001zmq-Mh>; Fri, 15 Apr 2016 17:14:14 +0200 Received: from x5ce108f0.dyn.telefonica.de ([92.225.8.240] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from ) id <1ar5Rm-004AqV-9a>; Fri, 15 Apr 2016 17:14:14 +0200 Date: Fri, 15 Apr 2016 17:14:36 +0200 From: "O. Hartmann" To: Matthew Macy Cc: "Arto Pekkanen" , freebsd-x11@freebsd.org Subject: Re: clarifying the state of drm-next-3.9 and next steps Message-ID: <20160415171436.4f984922.ohartman@zedat.fu-berlin.de> In-Reply-To: <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> References: <1540c0ceea9.126b592b988423.8774357707501817476@nextbsd.org> <570FE736.6030803@kapsi.fi> <154162c9e5e.def07e19164201.9142009646778346084@nextbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/im+sBQVCp1KIxZRvQJj=Wtz"; protocol="application/pgp-signature" X-Originating-IP: 92.225.8.240 X-ZEDAT-Hint: A X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2016 15:14:20 -0000 --Sig_/im+sBQVCp1KIxZRvQJj=Wtz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 14 Apr 2016 12:08:23 -0700 Matthew Macy schrieb: > =20 >=20 > =20 > Thanks for the heads up :)I am especially interested in the G= PGPU support > for AMDs, since thiswould actually make FreeBSD x86 rigs very useful for = power > efficientcluster computing. Thus far cheapest alternatives (on x86 hardwa= re) havebeen > based on Windows or Linux.Can I count you as a volunteer to help jmd with= user level > runtime support? :D-MOn 12.04.2016 22:57, Matthew Macy wrote:> There seem= s to be some > confusion about the state of drm-next-3.9. All the work is currently goin= g on in jmd's > fork of freebsd-base-graphics:> > https://github.com/iotamudelta/freebsd-= base-graphics> > > The emphasis has been on bringing i915 and the drm code in dev/drm2 cl= oser to > > upstream as opposed to a simple driver refresh. I'm currently implement= ing missing > > linuxkpi bits and hope to actually be testing in the next week or so. >= > As of this > > moment there is nothing available for general consumption. I very much = hope to have > > this phase done before code freeze. I will update the list as soon a s = there is > > anything to test. Until then, hold your horses.> > The next phase will = be more > > interesting to anyone who isn't simply waiting on bug fixes for Haswell= support. My > > plan is to update DRM to 4.6 and import amdgpu and amdkfd support. I wo= uld like to be > > able to do GPGPU work using HIP/HSA on my AMD cards. An ETA on 4.6/amdg= pu support is > > difficult to come up with. But certainly it will _not_ be any earlier t= han end of > > May.> > -M> > _______________________________________________> > > freebsd-x11@freebsd.org mailing list> > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11> To unsubscribe,= send any mail > > to "freebsd-x11-unsubscribe@freebsd.org">=20 >=20 > =20 > =20 >=20 > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" ???? Unreadable reply! --Sig_/im+sBQVCp1KIxZRvQJj=Wtz Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXEQVcAAoJEOgBcD7A/5N8XmkH+wfrWG6fF4FyekoVfPbt09rC Zyjx7BcQiQrZcVP5p9NI5UGshdLqfBcC7U2qBE44bnS6p75JdxDZ4eSrcgTHmSRd 51TLg3sKw3xGkS3Pse3gyT/hqYNxe43F2OiOTBmYDYDxcbBmiL7/vhSP1mo4E0vn 2B7soamzNwOENQa5kDoMT6kYj1p+rV2cCCrK51ellfmgnqBG/txpi5jclSAXLIjF ScKtNVsTpNe8BRAaBvFZ6naFjI1a5lSvlbKfO9jpbhY9xvesdaLY0z2AEzknUfhi LGVSnVXzM0xuc17bQwrG6RKIza2uz0U3XxtwK4CigLE4G1kzYVUFgZMDPQ2175c= =2ZWN -----END PGP SIGNATURE----- --Sig_/im+sBQVCp1KIxZRvQJj=Wtz-- From owner-freebsd-x11@freebsd.org Fri Apr 15 17:46:16 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 193F9AEDCD8 for ; Fri, 15 Apr 2016 17:46:16 +0000 (UTC) (envelope-from john.michaels@top-page-ranking.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 082EC18FD for ; Fri, 15 Apr 2016 17:46:16 +0000 (UTC) (envelope-from john.michaels@top-page-ranking.com) Received: by mailman.ysv.freebsd.org (Postfix) id 03D13AEDCD6; Fri, 15 Apr 2016 17:46:16 +0000 (UTC) Delivered-To: x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03747AEDCD5 for ; Fri, 15 Apr 2016 17:46:16 +0000 (UTC) (envelope-from john.michaels@top-page-ranking.com) Received: from node1.sunriseindiaok.in (node1.sunriseindiaok.in [192.161.51.133]) by mx1.freebsd.org (Postfix) with ESMTP id E5B2218FC for ; Fri, 15 Apr 2016 17:46:15 +0000 (UTC) (envelope-from john.michaels@top-page-ranking.com) Received: from NishantRF (unknown [122.177.166.70]) by node1.sunriseindiaok.in (Postfix) with ESMTPA id 4627C2925812 for ; Fri, 15 Apr 2016 12:23:46 -0400 (EDT) From: "John Michaels" To: Subject: Pay only when we rank your keywords on top... Date: Fri, 15 Apr 2016 21:49:14 +0530 Message-ID: <20b8401d19733$29234a80$7b69df80$@top-page-ranking.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdGXMTsGImsRsEd0SLe5KhnU7Yyf3g== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2016 17:46:16 -0000 Greetings, In the world of Google, we have to be ready to act fast. A single tweak to an algorithm can destroy everything you've built and force us to re-adapt quickly. These changes happen on an almost daily basis. Does Google's constant algorithm change makes you worry? We can help you. We have special service model "Pay-for-performance SEO" where you just need to pay one time only set-up fee and after that pay only when we rank your keywords on top. Activities to be performed for your website: . Keyword Analysis . Competitor Analysis . SEO Analysis report . Finding & fixing all the technical errors from the website . On-page optimization (Designing stuff) . Adding landing pages if required. . Social Media Optimization etc. . Off page optimization (Promotional stuff with other website to get quality Back links). . Content Writing . Reputation Management We are a Digital Marketing Agency, driven by a team of 200+ technology specialists, has enabled thousands of clients to gain a prominent presence on Google and other leading search engines. Our SEO strategies were designed from the beginning to give you visibility, relevance, and results. Intrigued? Just reply to this email with your requirement (keywords) and phone number so that we can discuss this in detail. Kind Regards, John Michaels Business Development Manager ResultFirst Inc. Head Office: San Jose, CA 95120 Note: Though this is not an automated email, we are sending these emails to all those people whom we find eligible of using our services. To unsubscribe from future mails (i.e., to ensure that we do not contact you again for this matter), please reply "UNSUBSCRIBE".