On Thursday, December 03, 2015 07:16:45 PM Joe Maloney wrote:
> It works! Would it be helpful if I did a pull request from github, or just
> let you guys take it from here? Thanks for helping me figure out how to get
> up, and running! This will be so much better than the framebuffer driver I
It works! Would it be helpful if I did a pull request from github, or just let
you guys take it from here? Thanks for helping me figure out how to get up,
and running! This will be so much better than the framebuffer driver I was
having to use.
Joe Maloney
> On Dec 3, 2015, at 12:33 PM, Joe
FYI it’s changed a bit more, and line 372 is now line 364 with different
options. Going to try this first which was now at line 364.
https://github.com/pkgdemon/freebsd/commit/f72323b10a9dd6da79f0dae1a6fd68823ec66f7d
Joe Maloney
> On Dec 3, 2015, at 11:58 AM, Joe Maloney wrote:
>
> Will give
Will give this a try, build an image and report back for sure. Thanks!
Joe Maloney
> On Dec 2, 2015, at 1:39 AM, Jean-Sébastien Pédron
> wrote:
>
> On 02/12/2015 02:00, John Baldwin wrote:
>> Note that at the top of the function it invokes IICBUS_TRANSFER on a
>> different
>> device when for
On 02/12/2015 02:00, John Baldwin wrote:
> Note that at the top of the function it invokes IICBUS_TRANSFER on a different
> device when force_bit_dev is true:
>
> 370 sx_xlock(&dev_priv->gmbus_sx);
> 371 if (sc->force_bit_dev) {
> 372 dumbbell
On Saturday, November 28, 2015 04:50:41 PM Joe Maloney wrote:
> Thank you. For what it’s worth I was able to grab a dump after setting that
> sysctl. It looks like this maybe the culprit?
>
> panic: _sx_xlock_hard: recursed on non-recursive sx gmbus @
> /usr/src/sys/modules/drm2/i915kms/../../
Thank you. For what it’s worth I was able to grab a dump after setting that
sysctl. It looks like this maybe the culprit?
panic: _sx_xlock_hard: recursed on non-recursive sx gmbus @
/usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/intel_iic.c:362
Since it is to large for posting here.
On 13/11/2015 18:15, Joe Maloney wrote:
> Hello,
Hi!
> 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
Hello,
please let me know if this isn’t 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 grap
