From owner-freebsd-x11@freebsd.org Tue Mar 8 05:17:43 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 D4975AC3D74 for ; Tue, 8 Mar 2016 05:17:43 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 6367A779 for ; Tue, 8 Mar 2016 05:17:43 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id n186so114967676wmn.1 for ; Mon, 07 Mar 2016 21:17:43 -0800 (PST) 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=Y2Nk98k9HxRpOeSQVIrRERB7NKdnLDorG5VnDqkn1HM=; b=RjQTCKqfEAsDWntDPLYcB6JsM7g5VXqtMprMrcyySGUDLlE8bCB/abtNe8cyKE/KSD TD/UafaTDtGXndLnJ4VzD7Pm8Oi7PZIWizldA73n/NU12po3HiLqL5/bbZiG4K5fanye xPOXE3TCT5yq7yRNnadyMYUKLY7yZujM8Z3ps8EDeOTWr4NwOjIfT6aZOqJZldygzeR/ eX4lmlIDITzaSBFKnzxAw9rqeXSqX4U1PTmFM9sqXcArdYtgKI/8jBTCiYzkz7kM6n4J HAgzcJbjOTSTqxe2rkQjeeXSMzKwYub36vUjKloVBII+aKizr5JIfU1rvQNR9CtS1OHC ni6w== 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=Y2Nk98k9HxRpOeSQVIrRERB7NKdnLDorG5VnDqkn1HM=; b=DBnXIx7USQklth8inln0BdiEjgMAbkuN5tSPxTd9bCattHCjAk5mEpCumXV/rBwDk7 ylIZ8W7Q68SITPct52IOaDcQhaI3VuCXTf4UwSczKQ484KeoLCXtoVQXSKQKUzGnPHO+ Zl8lfs7uN9hUQJ2ZrZdkw3UvFC09WYlsqQOqxR2fQY77KjuR4o4isNVtQgCfRudGZOLa 3GPCsYCItgilWz7JYQqzGcgVJWeV32fxl+P5gnymIiQa8aMoZFwBTEnZtY9E2X4y6/lf RFfOLW6zp+yoXVX/8odfGA52KxxE184WWG2WpH+xCZvtWJyZWsXM3F46y395d5WtDFtz RwLQ== X-Gm-Message-State: AD7BkJLt1oaBl3+ZSVFmtFA816zMt3hlESElfsJYNGmNDaBTp742c4jqPcB2QxoVMA/quio3wQC2CQDSZtlpng== MIME-Version: 1.0 X-Received: by 10.28.214.11 with SMTP id n11mr15891312wmg.31.1457414261465; Mon, 07 Mar 2016 21:17:41 -0800 (PST) Received: by 10.194.23.104 with HTTP; Mon, 7 Mar 2016 21:17:41 -0800 (PST) In-Reply-To: <56DD81B6.6060300@gmail.com> References: <20160307125412.6a10931c@freyja.zeit4.iv.bundesimmobilien.de> <56DD81B6.6060300@gmail.com> Date: Tue, 8 Mar 2016 06:17:41 +0100 Message-ID: Subject: Re: Intel Brasswell, NUC, iGPU and VESA driver on CURRENT From: Ben Woods To: Alexander Mishurov 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: Tue, 08 Mar 2016 05:17:44 -0000 On Monday, 7 March 2016, Alexander Mishurov wrote: > Hi, you should use x11-drivers/xf86-video-scfb. This driver similar to > VESA for UEFI mode. > > Also, there's branch for GPUs up to Haswell > > https://wiki.freebsd.org/Graphics/Update%20i915%20GPU%20driver%20to%20Linux%203.8 > > N3050 use ValleyView graphics, if i'm not wrong; unfortunately it isn't > supported yet. > > On 07/03/16 14:54, O. Hartmann wrote: > >> We got a bunch of new hardware for certain purposes and equipted with >> modern >> CPUs and iGPUs. FreeBSD still lacks in kernel support for Intel CPUs >> beyond >> IvyBridge based iGPUs or moderate modern GPUs dur to some KMS issues. On >> three >> years old hardware with Intel Haswell and HD4XXX iGPU I still use the VESA >> driver running X11 (very poor performance). Now, on Braswell and Boradwell >> settop boxes, I'd like to use also VESA driver to have graphical support. >> >> The boxes are all booted via UEFI! >> >> Starting VESA fails with something like: >> >> [...] >> (II) VESA(0): initializing int10 >> (EE) VESA(0): V_BIOS address 0x0 out of range >> (II) UnloadModule: vesa >> [...] >> >> Google says this is probably due to UEFI not getting the correct hardware >> informations, but since I have a high-resolution console (vt()), I guess >> the >> FBSD kernel knows about the EFI support? >> >> Is there a solution with VESA for that issue? >> >> This problem is with all barebone PCs I use, a Intel NUC with N3050 CPU >> and a >> Zotac Mini with recent Boradwell CPU. >> >> Please CC me! >> >> Thank you very much in advance and kind regards, >> >> Oliver >> > Indeed, using scfb should work for you instead of vesa. I previously provided someone on this list with some instructions on how to use get FreeBSD working with the scfb driver. See here: http://lists.freebsd.org/pipermail/freebsd-x11/2016-February/017154.html Good luck! Regards, Ben -- -- From: Benjamin Woods woodsb02@gmail.com