On Mon, Feb 11, 2019 at 08:20:20AM -0800, Steve Kargl wrote:
> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> > Anyone have any idea which recent change broke the
> > drm-legacy-kmod port. This is why I raised an issue
> > with removal of drm2 from src/sys. How is suppose
> > to
On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote:
> >
> > The patch allows the port to be built.
> >
> > kldloading the i915kms module causes a 'black screen
> > of death'
> >
> Hi!
> I assume you load the kernel module either manually with kldload or
> using kld_list in rc.conf,
On Mon, Feb 11, 2019 at 09:01:55PM +, Graham Perrin wrote:
> On 11/02/2019 20:42, Steve Kargl wrote:
>
> > Are you building on i386 or x86_64?
>
> $ uname -a
> FreeBSD momh167-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT r343931
> GENERIC-NODEBUG amd64
amd64 == x86_64 --> no problem as
On 11/02/2019 20:42, Steve Kargl wrote:
> On Mon, Feb 11, 2019 at 08:40:01PM +, Graham Perrin wrote:
>
>> On 11/02/2019 16:20, Steve Kargl wrote:
>>
>>> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
>>>
Anyone have any idea which recent change broke the
On Mon, Feb 11, 2019 at 08:40:01PM +, Graham Perrin wrote:
> On 11/02/2019 16:20, Steve Kargl wrote:
>
> > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> >
> >> Anyone have any idea which recent change broke the
> >> drm-legacy-kmod port. This is why I raised an issue
>
On 11/02/2019 16:20, Steve Kargl wrote:
> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
>
>> Anyone have any idea which recent change broke the
>> drm-legacy-kmod port. This is why I raised an issue
>> with removal of drm2 from src/sys. How is suppose
>> to be fixed?
>
> It was
On Mon, Feb 11, 2019 at 06:42:29PM +0100, Niclas Zeising wrote:
> On 2/11/19 6:36 PM, Steve Kargl wrote:
> >
> > The patch allows the port to be built.
> >
> > kldloading the i915kms module causes a 'black screen
> > of death'
> >
> > I'll note that there seems to be a race condition in
> >
On 2/11/19 6:36 PM, Steve Kargl wrote:
On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote:
On 2/11/19 5:20 PM, Steve Kargl wrote:
On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
Anyone have any idea which recent change broke the
drm-legacy-kmod port. This is why I
On Mon, Feb 11, 2019 at 06:05:03PM +0100, Niclas Zeising wrote:
> On 2/11/19 5:20 PM, Steve Kargl wrote:
> > On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> >> Anyone have any idea which recent change broke the
> >> drm-legacy-kmod port. This is why I raised an issue
> >> with
> On Mon, Feb 11, 2019 at 04:33:24PM +, Johannes Lundberg wrote:
> >
> > On 2/11/19 4:23 PM, Niclas Zeising wrote:
> > > On 2/11/19 5:20 PM, Steve Kargl wrote:
> > >> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> > >>> Anyone have any idea which recent change broke the
> >
On 2/11/19 5:20 PM, Steve Kargl wrote:
On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
Anyone have any idea which recent change broke the
drm-legacy-kmod port. This is why I raised an issue
with removal of drm2 from src/sys. How is suppose
to be fixed?
It was r343567. The
On Mon, Feb 11, 2019 at 04:33:24PM +, Johannes Lundberg wrote:
>
> On 2/11/19 4:23 PM, Niclas Zeising wrote:
> > On 2/11/19 5:20 PM, Steve Kargl wrote:
> >> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> >>> Anyone have any idea which recent change broke the
> >>>
On 2/11/19 4:23 PM, Niclas Zeising wrote:
> On 2/11/19 5:20 PM, Steve Kargl wrote:
>> On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
>>> Anyone have any idea which recent change broke the
>>> drm-legacy-kmod port. This is why I raised an issue
>>> with removal of drm2 from src/sys.
Hi Steve,
This looks like breakage from unifying PAE and non-PAE kernels in r343567.
CCing kib@ for context.
Cheers,
-Enji
> On Feb 11, 2019, at 08:12, Steve Kargl
> wrote:
>
> Anyone have any idea which recent change broke the
> drm-legacy-kmod port. This is why I raised an issue
> with
On 2/11/19 5:20 PM, Steve Kargl wrote:
On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
Anyone have any idea which recent change broke the
drm-legacy-kmod port. This is why I raised an issue
with removal of drm2 from src/sys. How is suppose
to be fixed?
It was r343567. The
On 2/11/19 5:12 PM, Steve Kargl wrote:
Anyone have any idea which recent change broke the
drm-legacy-kmod port. This is why I raised an issue
with removal of drm2 from src/sys. How is suppose
to be fixed?
--- ttm_bo_manager.o ---
cc -O2 -pipe -march=core2 -fno-strict-aliasing -march=core2
On Mon, Feb 11, 2019 at 08:12:05AM -0800, Steve Kargl wrote:
> Anyone have any idea which recent change broke the
> drm-legacy-kmod port. This is why I raised an issue
> with removal of drm2 from src/sys. How is suppose
> to be fixed?
>
It was r343567. The merging of PAE and NO PAE pmap.h
by
Anyone have any idea which recent change broke the
drm-legacy-kmod port. This is why I raised an issue
with removal of drm2 from src/sys. How is suppose
to be fixed?
--- ttm_bo_manager.o ---
cc -O2 -pipe -march=core2 -fno-strict-aliasing -march=core2 -Werror -D_KERNEL
-DKLD_MODULE -nostdinc
18 matches
Mail list logo