Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Sep 2019 07:50:38 +0900 (JST)
From:      Masachika ISHIZUKA <ish@amail.plala.or.jp>
To:        zeising@freebsd.org
Cc:        freebsd-current@freebsd.org
Subject:   Re: hang up with r352239 and r352386 with i5-7500
Message-ID:  <20190919.075038.1687549947501964479.ish@amail.plala.or.jp>
In-Reply-To: <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org>
References:  <20190917.235930.528406816270492485.ish@amail.plala.or.jp> <20190918.171520.1850897233083712866.ish@amail.plala.or.jp> <5fa15ee8-a1cb-37e7-b954-c50b1cd0a8d9@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

>>>>>>>> Can you please use absolute paths to i915kms.ko anyway, just to test?
>>
  [snip]
>>
>>    Now, drm-current-kmod is working fine on r352467 by your patch.
>> 
> 
> Hi!
> I just updated the port with the fix I suggested earlier, hopefully it
> works.  It will take some time before it shows up as packages, but
> there is no problems building drm-current-kmod from ports even if
> packages are used for the rest of the system.

  It is good working drm-current-kmod-4.16.g20190918 in port tree.
  Thank you very much.
-- 
Masachika ISHIZUKA



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190919.075038.1687549947501964479.ish>