From owner-freebsd-current@freebsd.org Fri Nov 13 17:15:15 2015 Return-Path: Delivered-To: freebsd-current@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 96921A2E1D7 for ; Fri, 13 Nov 2015 17:15:15 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 750B11936 for ; Fri, 13 Nov 2015 17:15:14 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1447434913-08ca040e840b8b0002-XDYc8F Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id GNCYP6ZkTAGSHsHj (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Nov 2015 09:15:14 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 From: Joe Maloney Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: EFI and i915kms questions Message-Id: <54B18FFE-063F-4F62-9343-28FDE68EE358@pcbsd.org> X-ASG-Orig-Subj: EFI and i915kms questions Date: Fri, 13 Nov 2015 11:15:13 -0600 To: freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1447434914 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.82 X-Barracuda-Spam-Status: No, SCORE=0.82 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests=MIME_QP_LONG_LINE, MIME_QP_LONG_LINE_2 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24362 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars 0.82 MIME_QP_LONG_LINE_2 RAW: Quoted-printable line longer than 76 chars X-Mailman-Approved-At: Fri, 13 Nov 2015 17:47:06 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2015 17:15:15 -0000 Hello, please let me know if this isn=E2=80=99t the best list to ask these = particular questions, and which list is. I have an Acer Travelmate P653 = model MS2352 with an Intel HD4000 (I think) Gen 3 graphics card. = Unfortunately pciconf, and dmesg do not show useful information other = than intel gen3 graphics. This laptop doesn=E2=80=99t give me the = option to disable CSM. It also boots whatever is available whether EFI = only is selected or not. FreeBSD 10.1 worked on this laptop, and loaded = i915kms properly. PCBSD has always worked, and still works even with = their 11 CURRENT images which no longer use grub. Sometime after changes in FreeBSD 10-STABLE, 10.2 onwards, and recent 11 = CURRENT the resolution no longer sets properly when using UEFI boot. It = now boots with a 640x480 resolution, and kldload i915kms results in a = black screen. I have not been able to grab a debug log, or crash dump = even with all of the debugging features turned on. I cannot ssh into = the laptop when this panic occurs, and the screen is black so I can=E2=80=99= t really see what happened. I=E2=80=99m curious if there is anything = else I can do besides enabling dumpdev or kldload -v i915kms > = output.txt that doesn=E2=80=99t give me any detail. Nothing shows up in = /var/crash or whatever the directory was. I=E2=80=99ve noticed if I compile from PCBSD=E2=80=99s fork of FreeBSD = current source on top of FreeBSD it works. I have been unable to track = down the difference at this point. I=E2=80=99ve been working on it for = a few months but I have not figured it out. I would appreciate any help = I could get in tracking down the cause to fix the problem for others. I = can=E2=80=99t seem to find that it=E2=80=99s a problem for anyone else = however after months of research. I did find one interesting thing. If I mount the EFI partition, and = replace /mnt/efi/boot/bootx64.efi (boot1.efi) with loader.efi by cp = /boot/loader.efi /mnt/efi/boot/bootx64.efi i get full 1366x768 console = resolution. I can then use scfb at least if I delete the i915kms* = drivers to start X. I tested boot1.efi on a mac, and it of course sets the proper 1920x1080 = resolution it should. I am curious what the difference is between = boot1.efi, and loader.efi. Is a device id or something missing from = boot1.efi for my laptop to set the proper resolution? It=E2=80=99s it = the fact that I can=E2=80=99t disable CSM, and it=E2=80=99s somehow = booting non EFI? Can I remove certain things don=E2=80=99t force EFI = only, or somehow force FreeBSD to disable CSM? Can I somehow roll an = EFI only release of FreeBSD for further testing? If so what would I = need to remove, or disable? Does anyone have any suggestions on what I = could try to gather dump information as well regarding the i915kms = lockup? Joe Maloney