[This is based on buildworld buildkernel and installing.]
I've updated to:
# uname -apKU
FreeBSD pine64 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 #17 r338921M: Mon Sep 24
19:19:08 PDT 2018
markmi@pine64:/usr/obj/cortexA53_clang/arm64.aarch64/usr/src/arm64.aarch64/sys/GENERIC-NODBG
arm64 aarch64 120
El día Monday, September 24, 2018 a las 09:01:34PM +0200, Michael Gmelin
escribió:
> >> On 24/09/2018 13:21, Matthias Apitz wrote:
> >> Re/ i915kms, I have to load it with kldload by hand. If I load it via
> >> loader.conf, the cyapa devices (both) say 'Unable to bring the device
> >> out of boot
On 24 Sep, blubee blubeeme wrote:
> This issue seemed to have come up in the past:
> https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068870.html
>
>
> Jail name: amd64_cur
> Jail version: 12.0-ALPHA7 1200084
> Jail vcs version: r338898
> Jail arch: amd64
> Jai
On 23 September 2018 at 07:31, Michael Tuexen wrote:
> Using this patch I was able to build/install world and kernel on an i386
> system.
> However, after removing it, I can't build world then. When trying to compile a
> kernel "the old way" I end up with:
>
> tuexen@head:~/head/sys/i386/conf % c
> On 24. Sep 2018, at 15:08, Andriy Gapon wrote:
>
>> On 24/09/2018 13:21, Matthias Apitz wrote:
>> Re/ i915kms, I have to load it with kldload by hand. If I load it via
>> loader.conf, the cyapa devices (both) say 'Unable to bring the device
>> out of bootstrap'.
>
> That's probably because
Yes. Thank you.
24.09.2018 21:28, Ed Maste пишет:
> On 24 September 2018 at 06:43, Alex V. Petrov wrote:
>> ===> lib/libc (cleandir)
>> make[4]: "/usr/src/lib/libc/Makefile" line 26: i386 libc requires linker
>> ifunc support
>> *** Error code 1
>
> Please try r338903.
>
--
-
Alex.
__
Am 24.09.2018 um 14:50 schrieb Andrey V. Elsukov:
On 24.09.2018 11:31, Harry Schmalzbauer wrote:
Hello,
unfortunately this is far beyond my scope and I forgot to report in time.
If this is begnin, feel free to ignore, but in any case I'd appreciate
any comments.
Hi,
I posted a review targete
On 23 Sep 2018, at 22:10, David P. Discher wrote:
I say yes, especially if we wish to support a IPv6 only system at some
point in the future … which seemed to be a “think” of the few
major IPv6 advocates in the industry.
I guess best practice, this should suck in rc.* config files, and use
v
On 9/21/2018 10:53 PM, Eric van Gyzen wrote:
> I would like to build a Ryzen desktop. Can anyone recommend a good
> motherboard?
I like the ASUS X370-PRO (currently BIOS 04/19/2018).
igb0 for the onboard nic
igb0@pci0:7:0:0:class=0x02 card=0x85f01043 chip=0x15398086
rev=0x03 hdr=0x00
On 23 September 2018 at 21:18, wrote:
>
> Howdy!
>
> Since a couple months ago, the world on -CURRENT cannot be built using
> the normal procedure:
>time env LD=ld.lld make -j6 buildworld buildkernel
The normal procedure shouldn't need any LD= overrides; is there
something unique in your b
On 24 September 2018 at 06:43, Alex V. Petrov wrote:
> ===> lib/libc (cleandir)
> make[4]: "/usr/src/lib/libc/Makefile" line 26: i386 libc requires linker
> ifunc support
> *** Error code 1
Please try r338903.
___
freebsd-current@freebsd.org mailing lis
On 24/09/2018 13:21, Matthias Apitz wrote:
> Re/ i915kms, I have to load it with kldload by hand. If I load it via
> loader.conf, the cyapa devices (both) say 'Unable to bring the device
> out of bootstrap'.
That's probably because you use device hints to configure cyapa, but i2c bus
numbers are d
On 24.09.2018 11:31, Harry Schmalzbauer wrote:
> Hello,
>
> unfortunately this is far beyond my scope and I forgot to report in time.
> If this is begnin, feel free to ignore, but in any case I'd appreciate
> any comments.
Hi,
I posted a review targeted to fix this problem:
htt
--
>>> stage 2.1: cleaning up the object tree
--
cd /usr/src; MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= CC="cc -target
i386-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/i386.i38
El día Monday, September 24, 2018 a las 12:46:17PM +0300, Michael Gmelin
escribió:
> > What could be wrong?
>
> Do you by any chance use vt(4) in vga textmode (hw.vga.textmode=1)?
>
> vt doesn’t support hardware mouse cursors, so no cursor in text mode (see
> https://wiki.freebsd.org/Newcons)
> On 24. Sep 2018, at 12:42, Matthias Apitz wrote:
>
>> El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz
>> escribió:
>>
>>
>> Hello,
>>
>> I've booted a fresh r338641 from an USB key on my Acer C720, and have
>> the required modules loaded at boot (cyapa and ig4) an
> On 24. Sep 2018, at 11:31, Matthias Apitz wrote:
>
>
> Hello,
>
> I've booted a fresh r338641 from an USB key on my Acer C720, and have
> the required modules loaded at boot (cyapa and ig4) and the values for cyapa
> in
> /boot/device.hints, as I do use them in r314251. The moused is runni
El día Monday, September 24, 2018 a las 10:31:38AM +0200, Matthias Apitz
escribió:
>
> Hello,
>
> I've booted a fresh r338641 from an USB key on my Acer C720, and have
> the required modules loaded at boot (cyapa and ig4) and the values for cyapa
> in
> /boot/device.hints, as I do use them in
Hello,
I've booted a fresh r338641 from an USB key on my Acer C720, and have
the required modules loaded at boot (cyapa and ig4) and the values for cyapa in
/boot/device.hints, as I do use them in r314251. The moused is running as
/usr/sbin/moused -p /dev/cyapa0 -t ps/2
but no mouse pointer is
Hello,
unfortunately this is far beyond my scope and I forgot to report in time.
If this is begnin, feel free to ignore, but in any case I'd appreciate
any comments.
uma_zalloc_arg: zone "1024" with the following non-sleepable locks held:
exclusive sleep mutex xforms_list (IPsec transforms lis
20 matches
Mail list logo