From owner-freebsd-x11@freebsd.org Sun Mar 26 18:41:23 2017 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 C3398D1F27F for ; Sun, 26 Mar 2017 18:41:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::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 9C47D1DE1 for ; Sun, 26 Mar 2017 18:41:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-pg0-x230.google.com with SMTP id 21so18677482pgg.1 for ; Sun, 26 Mar 2017 11:41:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=69W1k9ZZjXN4RdRDMVKYhNVKSrTLHYrWHONr3NlMqu0=; b=MjukIU/hfhZ7d3mxfkOF2eROmb+D9gPq7fnJWf1/snkVtXPqycj2RTJVhIPqqJK6gD iNZLsnEeTaYcO67kU3FcwR8H15yH/GJWmvmkYqi1F6WQey/LGwlAFmkZ71qpOAj1kZ8/ Aii8kVtyGo9FLXfT2SwuNzbUYyy/Z0BUmp7GQ06b4M0YChnMQswtwnvfTtrM3z1z/fRP 25lDXTeVdXnp4ybQtgG6P/UkqixAtCwu5X8aMV1YE+VCeEVJPCBUi4a7enbb5fyvEi8M t3kN/3v4Tps6geuTeyQCWXWEWTsjQ4QJUNLft30SocrqAZsQ+JOW6qbNgWS7MeJ2UQx1 F8Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=69W1k9ZZjXN4RdRDMVKYhNVKSrTLHYrWHONr3NlMqu0=; b=gpFMuazxrckGgAxzMl3cKRUD/3I3JE7V90/w3WJoYoUjl6SY7yPuwHIULY99BAdsqX +8+XAlUCRBACUu2N1esO3eIOQjo7wYAnFzGcWwWzjAYJeg7Vw+y8ymQv3S/e+bNEM+yx hOPrFL8tCHGuCZfbSOKjovYF6j/iTGJIj6hocZNzRASDGCwMhBP3hDZwCSJml2KSaxXn QAQQFPn0eiuDM8aTRuUNomLSn8qbWYYpER/MHV5Ay2hHsAHmXHvUxvVDJ1GwWhdOjOKA +Kxly9w5lLWn8nQMM5oWThRZUJUg0UzBRvHYW26Z2IEf1q6UADnQnT+DIEDnMVEosj/a Ko4A== X-Gm-Message-State: AFeK/H1W89yYh71MtSCo2Id0m6St1tAspy6XJfhn2Rp6jXc0d8oB2hSidi4H3X+UI5h7xRHPNn2vFGq2l8y/jg== X-Received: by 10.99.64.4 with SMTP id n4mr19980226pga.71.1490553682765; Sun, 26 Mar 2017 11:41:22 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.100.181.165 with HTTP; Sun, 26 Mar 2017 11:41:22 -0700 (PDT) In-Reply-To: <76aaad1c-f8e2-9e00-dc69-45394988889f@gmail.com> References: <204147601.175937.1490455876595@email.1and1.co.uk> <666774101.180230.1490527693375@email.1and1.co.uk> <76aaad1c-f8e2-9e00-dc69-45394988889f@gmail.com> From: Kevin Oberman Date: Sun, 26 Mar 2017 11:41:22 -0700 X-Google-Sender-Auth: eMiTw95LNbgO0bblsBjxd9oaNMI Message-ID: Subject: Re: Xorg not starting: no screens found (intel driver + i3-4130T) To: Theron Cc: - - , x11-list freebsd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 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, 26 Mar 2017 18:41:23 -0000 On Sun, Mar 26, 2017 at 10:52 AM, Theron wrote: > On 03/26/17 07:28, - - wrote: > >> Hello Conrad & All, >> >> Thank you for the quick response. >> >> Running `sysctl kern.vty` suggested that vt was being used. However, >> clearly something was not right bases on the log section that you >> highlighted, so I added `kern.vty=vt` to `/boot/loader.conf` and that has >> partially resolved the problem! >> >> I also added `kld_list="i915kms.ko"` to `/etc/rc.conf` and removed my >> xorg.conf file... >> >> I am now getting `AIGLX: Screen 0 is not DRI2 capable`. (Please see >> Xorg.0.log below...) >> >> `glx info | grep Device` indicates that llvmpipe is being used >> >> in contrast (on my Lubuntu partition, that I am using as a stop-gap >> measure) I get: >> >> `glx info | grep Device` outputs `MESA DRI Intel (R) Haswell (0x41e)` >> >> If I specify to the intel driver, I get the no screens message that I >> mentioned previously. (I have tried with both the intel driver config >> snippet below and without it.) >> >> Section "Device" >> Identifier "Card0" >> Driver "intel" >> EndSection >> >> I have spent some time RTM and searching through the forums, but have >> been unable to solve the follow-up problem as of yet. >> >> Some of the forum posts seemed to suggest it was something to do with >> device permissions but my regular user is added to the video and wheel >> groups. >> >> Another thing I tried was restricting the resolution to 1920x1080 and >> below because I read that resolutions greater than this could be >> problematic. >> >> I have tried connecting to my monitor with various cables, just in case >> that was an issue... >> >> Could anyone help with this stage of the troubleshooting process? >> >> Thank you & regards, >> Matthew >> > Is `kld_list="i915kms.ko"` correct? I have simply [...]" i915kms" (no > extension). > Make sure i915kms is indeed loaded: > `kldstat` | grep i915` > If this is indeed the problem and you do not want to reboot just to apply > the change in rc.conf, load the module manually: > `kldload i915kms` > > "No devices detected" indicates that Xorg cannot communicate with the > module responsible for the GPU hardware. It has nothing to do with regular > user permissions or monitor connectivity. Xorg on a headless system with a > working GPU but no display outputs would be expected to give a "no screens" > error but shouldn't have any problem finding the (GPU) device. > > Theron > And, while this is almost certainly not the primary issue, be sure that only the KMS driver is loaded. You should not have i915.ko loaded. I think this has been fixed, but it has been an issue with the latest version update. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683