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 PA
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
drm-legacy-kmo
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 r
I’ll take a look later today, since it’s likely related to my changes.
—
Rebecca
On January 26, 2019 at 6:43:49 PM, Yuri Pankov
(yur...@yuripv.net(mailto:yur...@yuripv.net)) wrote:
> Hi,
>
> Looks like installations from snapshot memstick images (tried all
> available ones for amd64 from
hi,
I'm trying to update things with Geramy right now. We hit a snag where his
updates broke my QCA9880 NIC in STA mode, so we're working through that
right now.
-adrian
On Mon, 11 Feb 2019 at 09:51, Ben Widawsky wrote:
> On 19-02-04 00:29:29, Anthony Jenkins wrote:
>
> [snip]
>
> Hi Adrian
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
> > boot
On 19-02-04 00:29:29, Anthony Jenkins wrote:
[snip]
Hi Adrian. I too am wondering what the plan is for this chipset. I am currently
using an awful USB wifi dongle. I can help with testing if needed - but I just
really want to know if we should expect upstream support which is relatively
stable 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 rai
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 remov
> 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 merg
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
> >>> drm-legacy-km
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 merg
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 k
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
On Mon, Feb 11, 2019 at 9:14 AM Cy Schubert wrote:
>
> On February 11, 2019 5:05:37 AM PST, Cy Schubert
> wrote:
> >Hi,
> >
> >Under the old Forth loader the line:
> >
> > include /boot/testbed/test_sys
> >
> >would load the file and execute loader commands.
> >
> >However the the Lua load
On February 11, 2019 5:05:37 AM PST, Cy Schubert
wrote:
>Hi,
>
>Under the old Forth loader the line:
>
> include /boot/testbed/test_sys
>
>would load the file and execute loader commands.
>
>However the the Lua loader results in the following:
>
>OK include /boot/testbed/amd64-current-r
>no
Hi,
Under the old Forth loader the line:
include /boot/testbed/test_sys
would load the file and execute loader commands.
However the the Lua loader results in the following:
OK include /boot/testbed/amd64-current-r
no error message
OK
Looking at the code, interp_include() expects to r
23 matches
Mail list logo
