Hello Warner,
I've encountered the following issue:
drm-kmod refuses to build, complains about vm_page_next() not being
defined. Also, when I tried installing drm-kmod or drm-66-kmod packages,
the kmods didn't want to work, complained about some symbols not being
there.
There does exist a f
Just did exactly that.
As I've mentioned before on wireless@, my AX201 doesn't want to work
with compat.linuxkpi.iwlwifi_disable_11ac=0. It doesn't seem to find the
access point and says something in the lines of:
Mar 24 22:09:16 hamster kernel: iwlwifi0: ERROR: lkpi_ic_scan_start:
hw_scan ret
Also, would like to thank Gleb for this awesome initiative!
To me, this stabilization week is a great way to see where the
development is going, and a great safe way to experience FreeBSD-CURRENT.
On 24.03.2025 13:00, Gleb Smirnoff wrote:
Hi FreeBSD/main users & developers:
This is an aut
On Friday 29 May 2015 16:35:35 Gleb Smirnoff wrote:
> Hi!
>
> As part of the "opaque ifnet project" [1], we are doing some code shake
> with all IEEE802.11 (read WiFi) drivers. The drivers, that provide a parent
> interface for the wlan(4) interface.
>
> The core idea is that parent device
On Sunday 26 October 2014 14:18:47 Dimitry Andric wrote:
>
> Your config executable is too old. Most likely, you need to run "make
> kernel-toolchain" first.
>
Thank you very much, that helped.
--
wbr, Maxim Filimonov
c...@bein.link
___
freebsd-curre
I'm trying to build the current FreeBSD kernel, and that's what I get:
% sudo make buildkernel
--
>>> Kernel build for GENERIC started on Sun Oct 26 01:39:13 MSK 2014
--
===> GE
On Saturday 20 September 2014 13:24:08 Ian Lepore wrote:
> Since it's happening only on that hardware, there's a good chance the
> problem is in the allwinner a10/a20 clock driver, not in the general
> eventtimer code. In fact, looking at the code it appears that a
> divide-by-16 is being set in t
Hello everyone,
Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
to be precise). The problem was that the load average was above 2. Including
the fact that the board has 2 CPU cores, that's strange. Also, the network
throughput was way too slow: from 3 kilobytes per
Hello everyone,
Recently, I encountered a problem with -CURRENT on an ARM board (cubieboard2
to be precise). The problem was that the load average was above 2. Including
the fact that the board has 2 CPU cores, that's strange. Also, the network
throughput was way too slow: from 3 kilobytes per
