Re: x11/nvidia-driver no longer works under -current (r338323)

[tech-lists]

On 26/08/2018 13:05, John wrote:

Hi,

On Sun, 26 Aug 2018, at 13:02, Tomoaki AOKI wrote:

Hi, John.
It's broken again by r338318. (Previously broken by r338107.)

If your previous src rev is older, you could be bitten by these.
If so, update ports tree at latest rev and try the latest single patch
below [1]. The patch itself is [2], applicable on top of /usr/ports.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230780
[2] https://bz-attachments.freebsd.org/attachment.cgi?id=196559


awesome, thank you I'll try that and let you know how I get on.



Thanks again, it's all working now :D

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Current and nvidia-driver again

[tech-lists]

On 28/08/2018 10:14, Alex V. Petrov wrote:

/usr/src Revision: 338342


===>  Building for nvidia-driver-390.77


Hi,

Have you tried applying the patch at 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230780 ? Update your 
ports tree first.


Apply it in /usr/ports

It worked for me on r338323

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

github freebsd and svn freebsd

[tech-lists]

Hello list,

What's the difference between github freebsd and svn freebsd, other than 
one is on github and the other is on svn?


How does one transcode or translate a git commit reference into a svn 
reference number?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

how to enforce one version of python

[tech-lists]

Hi,

There are a number of ports that seem to have their own preferential 
flavour of python, and some for example want to install python27 and 
python36 in the same place, and it's a pain when using portupgrade or 
similar tools.


I have this in my /etc/make.conf:

DEFAULT_VERSIONS+= python=2.7

Is this incorrect? I assume it must be, as for example devel/pylint 
(pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

change in uname -a behaviour between 12-ALPHA5 and 12-ALPHA7

[tech-lists]

Hello,

uname -a used to show a string including the date and where the kernel 
was compiled:


FreeBSD 12.0-ALPHA5 #0 r338518: Fri Sep  7 02:13:14 UTC 2018 
r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC


It no longer does:

root@REDACTED:/etc# uname -a
FreeBSD REDACTED.REDACTED.org 12.0-ALPHA7 FreeBSD 12.0-ALPHA7 r338903 
REDACTED  amd64


How can I get the old behaviour back?

thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: change in uname -a behaviour between 12-ALPHA5 and 12-ALPHA7

[tech-lists]

On 26/09/2018 14:34, Andrey Fesenko wrote:

See WITH_REPRODUCIBLE_BUILD
https://lists.freebsd.org/pipermail/freebsd-current/2018-September/071125.html


Thanks, I was unaware of the change till now. Somehow missed that thread.

I had to add the line WITHOUT_REPRODUCIBLE_BUILD="YES"
to /etc/src.conf. I could not see WITH_REPRODUCIBLE_BUILD in man 
src.conf. So this means at least in -current r338903 that 
WITHOUT_REPRODUCIBLE_BUILD="NO" is the default, iow REPRODUCIBLE_BUILD 
is on by default unless everything is recompiled 
WITHOUT_REPRODUCIBLE_BUILD="YES".

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Enabling the WITH_REPRODUCIBLE_BUILD knob for 12.0-REL

[tech-lists]

On 11/09/2018 20:35, Ed Maste wrote:

On 11 September 2018 at 07:35, Tomoaki AOKI  wrote:

I prefer releng, rather than stable, to make it default.
Binary releases requiring reproducible builds are built from
release and releng branches.


This might be the reasonable long-term strategy, but we don't yet have
experience running through the release process with it enabled. I
would like to enable it by default on the branch, at least initially,
to avoid discovering issues only immediately prior to the release.


Hi,

Personally I think this should (after testing on -current) be enabled 
only where binary-only updates (for everything) are anticipated. Then 
again, I don't run a binary-only system despite having to manage more 
than 16 systems. One reason is the hardware is all different, so 
different things are enabled in the kernel. The other reason is that I 
can reduce a machines security overhead if only what is required is 
available. This all requires source builds. So, I want to know where and 
when each system was compiled. Why lose this information by default?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

best linux emulation for 12-current

[tech-lists]

Hi,

Which is the better package for linux emulation on 12-alpha8 - c6 or c7? 
Or something else?


Emulation is for boinc_client to take linux work

thanks
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

drm confusion / xorg / AMD RX580 GPU

[tech-lists]

Hi,

context: 12-alpha8, amd64, xorg, AMD rx580 card

As per /usr/ports/UPDATING, I have installed graphics/drm-kmod which has
installed drm-next-kmod-4.11.g20180822

As per pkg message, it's loaded with this line in /etc/rc.conf:

kld_list="amdgpu"

But even though I get a graphical display, this shows in the X.org.0.log:

[91.379] (II) LoadModule: "ati"
[91.379] (II) Loading /usr/local/lib/xorg/modules/drivers/ati_drv.so
[91.379] (II) Module ati: vendor="X.Org Foundation"
[91.379]compiled for 1.18.4, module version = 18.1.0
[91.379]Module class: X.Org Video Driver
[91.379]ABI class: X.Org Video Driver, version 20.0
[91.382] (II) LoadModule: "amdgpu"
[91.383] (WW) Warning, couldn't open module amdgpu
[91.383] (II) UnloadModule: "amdgpu"
[91.383] (II) Unloading amdgpu
[91.383] (EE) Failed to load module "amdgpu" (module does not exist, 0)

$ kldstat
Id Refs AddressSize Name
 1   86 0x8020  13341b0 kernel
 21 0x81536000   3ace18 zfs.ko
 32 0x818e3000 a500 opensolaris.ko
 41 0x81a22000   159978 amdgpu.ko
 51 0x81b7c00075d70 drm.ko
 64 0x81bf200010570 linuxkpi.ko
 73 0x81c0300011300 linuxkpi_gplv2.ko
 82 0x81c15000  6c0 debugfs.ko
 91 0x81c16000 80db amdgpu_polaris10_mc_bin.ko
101 0x81c1f000 441d amdgpu_polaris10_pfp_bin.ko
111 0x81c24000 441b amdgpu_polaris10_me_bin.ko
121 0x81c29000 241b amdgpu_polaris10_ce_bin.ko
131 0x81c2c000 5d3d amdgpu_polaris10_rlc_bin.ko
141 0x81c320004042d amdgpu_polaris10_mec_bin.ko
151 0x81c730004042f amdgpu_polaris10_mec2_bin.ko
161 0x81cb4000 331f amdgpu_polaris10_sdma_bin.ko
171 0x81cb8000 3321 amdgpu_polaris10_sdma1_bin.ko
181 0x81cbc0005bbfd amdgpu_polaris10_uvd_bin.ko
191 0x81d1800028d1d amdgpu_polaris10_vce_bin.ko
201 0x81d410001fe51 amdgpu_polaris10_k_smc_bin.ko
211 0x81d61000 1800 uhid.ko
221 0x81d63000 2368 ums.ko
231 0x81d66000399d8 linux.ko
242 0x81da 2d98 linux_common.ko
251 0x81da300034008 linux64.ko

Need to know:

1. is this the right/fastest/best driver for this card?

2. how can I tell if it's using all its capability?

3. I'd like this card to crunch with boinc. What determines if this is
possible? is it freebsd, boinc, the card driver, the project boinc is on
or something else?

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech lists]

Hi,

On 08/10/2018 14:06, Warner Losh wrote:
> You need "/boot/kernel/amdgpu.ko" here
> 
> Warner

The instructions in pkg-message (at the time, haven't updated ports in a
day or so) contradict this:

$ cd /usr/ports/graphics/drm-next-kmod/
$ ls
Makefiledistinfopkg-descr   pkg-message
pkg-plist   work
$ less pkg-message

[snip]
The drm-next-kmod port can be enabled for amdgpu (for AMD GPUs starting
with the HD7000 series / Tahiti) or i915kms (for Intel APUs starting
with HD3000 / Sandy Bridge) through kld_list in /etc/rc.conf. radeonkms
for older AMD GPUs can be loaded and there are some positive reports if
EFI boot is NOT enabled (similar to amdgpu).

For amdgpu: kld_list="amdgpu"
For Intel: kld_list="/boot/modules/i915kms.ko"
For radeonkms: kld_list="/boot/modules/radeonkms.ko"

Please ensure that all users requiring graphics are members of the
"video" group.

Older generations are supported by the stable kms modules (radeonkms /
i915kms) in base.
[/snip]

svnlite info shows /usr/ports at r481442. Shall I make bug report?

thanks,

-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech lists]

On 08/10/2018 19:55, Johannes Dieterich wrote:
>> 1. is this the right/fastest/best driver for this card?
> Yes, amdgpu kernel module and amdgpu DDX

aha I didn't know about the xf86-video-amdgpu DDX requirement. OK, have
installed that :D

>> 3. I'd like this card to crunch with boinc. What determines if this is
>> possible? is it freebsd, boinc, the card driver, the project boinc is on
>> or something else?
> Depends what the boinc client uses. OpenCL - you will need graphics/clover 
> which is not officially supported by AMD but may work. ROCm/HIP - won't work.
 ok thnks for that. I saw no option for boinc_client to use OpenCL when
building the port, so I installed opencl first, then linux-c7 (was c6
before) then built boinc-client ensuring the option to take linux work
was selected. The boinc project is World Community Grid.

I'm not able to immediately test as it's a friend's computer. He says it
"displays great" but I'm looking for a way to quantify that. Hence the
question how to test the cards capabilities.

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech-lists]

On 08/10/2018 19:55, Johannes Dieterich wrote:

Depends what the boinc client uses. OpenCL - you will need graphics/clover 
which is not officially supported by AMD but may work. ROCm/HIP - won't work.


Hi,

What is ROCm/HIP ?

thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech-lists]

On 09/10/2018 14:33, Johannes Lundberg wrote:


Hi

Let me know if you manage to get GPU processing working. I haven't 
explored the option so much but from what I've seen so far, there 
doesn't seem to be much GPU work available for *nix systems. I'm also on 
WCG.


Hi,

OK the error message for missing firmware has gone from the X.org.0.log 
but I see "could not load firmware image" in /var/log/messages and 
unfortunately the GPU still isn't available to crunch from boincmgr:


Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_pfp.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_me.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_ce.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_rlc.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_mec.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_mec2.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: drmn0: fence driver on ring 0 use gpu 
addr 0x00020008, cpu addr 0x0xf8002f4f1008


[snip]

Oct  8 22:51:08 asrock kernel: drmn0: fence driver on ring 9 use gpu 
addr 0x00020098, cpu addr 0x0xf8002f4f1098

Oct  8 22:51:08 asrock kernel: i_size_write unimplemented
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_sdma.bin: could not load 
firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_sdma1.bin: could not 
load firmware image, error 2

Oct  8 22:51:08 asrock syslogd: last message repeated 1 times
Oct  8 22:51:08 asrock kernel: drmn0: fence driver on ring 10 use gpu 
addr 0x000200a8, cpu addr 0x0xf8002f4f10a8

Oct  8 22:51:08 asrock kernel: i_size_write unimplemented
Oct  8 22:51:08 asrock kernel: drmn0: fence driver on ring 11 use gpu 
addr 0x000200b8, cpu addr 0x0xf8002f4f10b8

Oct  8 22:51:08 asrock kernel: i_size_write unimplemented
Oct  8 22:51:08 asrock kernel: amdgpu/polaris10_uvd.bin: could not load 
firmware image, error 2


[etc]

and then this:

Oct  8 22:51:08 asrock kernel: amdgpu: [powerplay] [AVFS] Something is 
broken. See log!


Unfortunately it doesn't say which log.

[snip]

Oct  8 22:51:08 asrock kernel: amdgpu: [powerplay] Can't find requested 
voltage id in vdd_dep_on_sclk table!
Oct  8 22:51:08 asrock kernel: amdgpu: [powerplay] VDDCI is larger than 
max VDDCI in VDDCI Voltage Table!

Oct  8 22:51:08 asrock kernel: [drm] ring test on 1 succeeded in 25 usecs

[snip]

PS. A tip for not having your custom Linux-enabled boinc-client pkg 
overwritten every time you run pkg upgrade, do 'pkg lock boinc-client' :)


I build/update from ports, partly because of things like that ;)
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech-lists]

On 10/10/2018 00:13, Johannes Dieterich wrote:



On Tuesday, October 9, 2018, tech-lists wrote:

On 08/10/2018 19:55, Johannes Dieterich wrote:

Depends what the boinc client uses. OpenCL - you will need graphics/clover 
which is not officially supported by AMD but may work. ROCm/HIP - won't work.


Hi,

What is ROCm/HIP ?

https://github.com/RadeonOpenCompute/ROCm

Our open acceleration stack. HIP is a kernel language akin to CUDA.


But the page says the RX580 is supported:

[quote]

ROCm officially supports AMD GPUs that have use following chips:

GFX8 GPUs
"Fiji" chips, such as on the the AMD Radeon R9 Fury X and 
Radeon Instinct MI8
"Polaris 10" chips, such as on the AMD Radeon RX 580 and Radeon 
Instinct MI6
"Polaris 11" chips, such as on the AMD Radeon RX 570 and Radeon 
Pro WX 4100

GFX9 GPUs
"Vega 10" chips, such as on the AMD Radeon Radeon RX Vega 64 
and Radeon Instinct MI25


[unquote]

Is this incorrect?

thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: drm confusion / xorg / AMD RX580 GPU

[tech-lists]

On 10/10/2018 00:19, tech-lists wrote:

[unquote]

Is this incorrect?


ah or do you mean it won't work with BOINC?

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

is 4k desktop possible on freebsd-12?

[tech-lists]

Hi,

I'm trying to get xorg to display 4k. The context is:

FreeBSD 12.0-ALPHA8 r339084 amd64
ports r481640
AMD RX580 GPU
Asus X99 Extreme3 mobo
cpu: intel e5-2699v4
48GB RAM
Samsung UE48JU6410U monitor connected via HDMI

drm-next-kmod-4.11.g20180822
libdrm-2.4.93,1
xf86-video-amdgpu-18.1.0
xf86-video-ati-18.1.0,1
xf86-video-openchrome-0.6.0_3
xf86-video-scfb-0.0.4_7
xf86-video-vesa-2.4.0_2
linux_base-c7-7.4.1708_6 and all its xorg/mesa libs

/var/log/Xorg.0.log has this:

[  3470.966] (II) AMDGPU(0): Printing probed modes for output HDMI-A-0
[  3470.966] (II) AMDGPU(0): Modeline "1920x1080"x60.0  148.50  1920 
2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[  3470.966] (II) AMDGPU(0): Modeline "1680x1050"x59.9  119.00  1680 
1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[  3470.966] (II) AMDGPU(0): Modeline "1600x900"x60.0  108.00  1600 1624 
1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)


but further along we have this:

[  3474.097] (II) AMDGPU(0): EDID vendor "SAM", prod id 3140
[  3474.097] (II) AMDGPU(0): Using EDID range info for horizontal sync
[  3474.097] (II) AMDGPU(0): Using EDID range info for vertical refresh
[  3474.097] (II) AMDGPU(0): Printing DDC gathered Modelines:
[  3474.098] (II) AMDGPU(0): Modeline "3840x2160"x0.0  297.00  3840 4016 
4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz eP)
[  3474.098] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 
2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[  3474.098] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 
1056  600 601 605 628 +hsync +vsync (37.9 kHz e)


and

[  3474.211] (II) AMDGPU(0): Printing DDC gathered Modelines:
[  3474.211] (II) AMDGPU(0): Modeline "3840x2160"x0.0  297.00  3840 4016 
4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz eP)
[  3474.211] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 
2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[  3474.211] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 
1056  600 601 605 628 +hsync +vsync (37.9 kHz e)


so would this indicate the card is 4k capable but the HDMI port on the 
card is not? Or the port on the monitor? Or something else?


thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: is 4k desktop possible on freebsd-12?

[tech-lists]

On 10/10/2018 14:00, Johannes Lundberg wrote:

Hi

What is the actual problem? Do you get any 4K modes listed when you run 
'xrandr' ?


The problem is, I'd like 4k output but it seems I'm not getting it even 
though the card and monitor are both capable of it. Problem also is my 
lack of expertise in this area.


xrandr output:

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected primary (normal left inverted right x axis y 
axis)

DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y 
axis) 1872mm x 1053mm

1920x1080 60.00*
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1280x800 59.91
1152x864 75.00
1280x720 60.00
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32
640x480 75.00 72.81 66.67 59.94
720x400 70.08
DVI-D-0 disconnected (normal left inverted right x axis y axis)
$

I've been running 4K@60FPS on an external display for a long time on my 
Intel laptops. However, that requires DP output. Your HDMI output is 
most likely limited to 30 FPS (but should still display 4K resolution...).


Would that work at 30 fps given that Xorg.0.log shows the following:

[  3474.097] (II) AMDGPU(0): Printing DDC gathered Modelines:
[  3474.098] (II) AMDGPU(0): Modeline "3840x2160"x0.0  297.00  3840 4016
4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz eP)

[  3474.211] (II) AMDGPU(0): Printing DDC gathered Modelines:
[  3474.211] (II) AMDGPU(0): Modeline "3840x2160"x0.0  297.00  3840 4016
4104 4400  2160 2168 2178 2250 +hsync +vsync (67.5 kHz eP)

ie, 4k @67.5kHz card output if I'm understanding correctly.

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: is 4k desktop possible on freebsd-12?

[tech-lists]

On 10/10/2018 13:45, Slawa Olhovchenkov wrote:

for 4K@60FPS you need DP connection.


problem is monitor only has HDMI. I'm not sure it'll 4k@30fps is an 
acceptable mode for it; need to check


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: is 4k desktop possible on freebsd-12?

[tech-lists]

On 10/10/2018 15:24, Slawa Olhovchenkov wrote:

You need check HDMI 2.0 available on video card and monitor.
For HDMI 1.4 you need check of support both card and monitor support 4K@24.


Yes, the card, cable and monitor are all capable of 4k@30fps. The cable 
and monitor were tested by connecting a laptop running linux mint. This 
gave a 4k display @ 30fps. So for some reason, the card (AMD RX580) 
isn't sending 4k.


Is there a resource explaining how/can anyone tell me how to make the 
card send 4k? The xorg section of the handbook unfortunately hasn't been 
much help.


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: is 4k desktop possible on freebsd-12?

[tech-lists]

On 11/10/2018 10:18, Johannes Lundberg wrote:

Do you have anything configured in /etc/X11/xorg.conf?


no. But there's a section in the handbook I missed; am reading it now

thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: is 4k desktop possible on freebsd-12?

[tech lists]

On 10/10/2018 11:17, tech-lists wrote:
> I'm trying to get xorg to display 4k. The context is:
> 
> FreeBSD 12.0-ALPHA8 r339084 amd64
> ports r481640
> AMD RX580 GPU
> Asus X99 Extreme3 mobo
> cpu: intel e5-2699v4
> 48GB RAM
> Samsung UE48JU6410U monitor connected via HDMI
> 
> drm-next-kmod-4.11.g20180822

Hi, just to follow up to this,

I'd run out of time to work on this so installed latest ubuntu desktop,
then ran xrandr and it showed 4k as the top resolution. I didn't have to
make any modifications:

[snip]
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
HDMI-A-0 connected primary 1920x1080+0+0 (normal left inverted right x
axis y axis) 1872mm x 1053mm
   3840x2160 30.00 +  25.0024.0029.9723.98
   4096x2160 30.0025.0024.0029.9723.98
[/snip]

and then, additionally, installed boinc-client-opencl and boinc was able
to see the GPUand use it for crunching.

On FreeBSD I couldn't see a way of making the boinc client OpenCL-aware.

On the plus side, FreeBSD was much more stable on this hardware than
Ubuntu. Had to disable hyperthreading in the BIOS to stop it crashing
every few hrs on Ubuntu.

It would be interesting to know, if possible, what Ubuntu is doing that
FreeBSD isn't on this hardware.

thanks to all who replied/tried to help,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

make buildkernel doesn't

[tech-lists]

Hi,

fbsd 13-current r346053 amd64

make buildkernel fails near the start here:

awk -f /usr/src/sys/tools/usbdevs2h.awk /usr/src/sys/dev/usb/usbdevs -d
--- genoffset.o ---
cc: error: no such file or directory: 'FLAGS'
*** [genoffset.o] Error code 1

more detail at
https://rpi3.zyxst.net/errors/13-current/r346053/20190409-kernbuildfail.txt

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Inability to build FreeBSD-current amd64

[tech-lists]

On Wed, May 15, 2019 at 06:46:04AM +, Thomas Mueller wrote:

Hi Tom,
Are you using any nonstandard build options/modes?
Cheers!
-Enji


I don't think I am using any nonstandard build options/modes.


[...]


Build didn't even start when I had WITHOUT_MANCOMPRESS on.



Trouble occurs before there is any attempt to build the kernel.


hi,

What do you do before buildworld?

I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again, then in
/usr/src I'll do this:

make -j32 cleanworld && make -j32 cleandir && make -j32 clean

before make buildworld. it's probably overkill but it'll for sure clean
away any cruft

[1] make sure they get deleted without error. I've encountered
bad_file_descriptor error in ccache dir before and it caused all kinds
of errors when building, which looked like build errors but obv. were
not.

--
J.


signature.asc
Description: PGP signature

old 12-CURRENT snapshot

[tech-lists]

Hi,

I'm looking for an old 12-CURRENT snapshot from around r317212 or before. I've
looked at ftp-archive.freebsd.org but nothing there would fit. Are there other
locations for this kind of thing that I've not considered?

thanks,
--
J.


signature.asc
Description: PGP signature

kernel options

[tech-lists]

Hi,

In -HEAD there is a generic kernel GENERIC-NODEBUG. The syntax of
OPTIONS appears to be NOOPTIONS. Is there an inverse for DEVICE ?

For example, there is a line

device  fdc

in GENERIC. Would NODEVICE negate it?

I didn't see anything in NOTES to confirm.

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

onboard wifi raspberry pi3 and aarch64/freebsd-current

[tech-lists]

Hello lists,

[x-posted to freebsd-arm because this question appears to be equally
relevant there]

Does the onboard wireless on the raspberry pi 3 work in 12-current-aarch64?

If not, are there plans afoot to make it work?

many thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

inetd startup script missing from /etc/rc.d in both -current and 11-stable

[tech-lists]

Hello current@,

>From https://www.freebsd.org/doc/handbook/network-inetd.html I should be
able to start inetd like this:

service inetd start

...after enabling it in /etc/rc.conf. The inetd options look like this:

inetd_enable="YES"
inetd_program="/usr/sbin/inetd"
inetd_flags="-wW -C 60"

The problem is that the startup script doesn't exist in /etc/rc.d. I get
this error:

# service inetd start
inetd does not exist in /etc/rc.d or the local startup
directories (/usr/local/etc/rc.d), or is not executable

and the lines in rc.conf have no effect (inetd doesn't start).

I can, however, start it manually, as root, like this:

# inetd -wW -C 60

and it runs as expected.

This problem exists in 11-stable as well as -current. How can I fix this
please?

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: inetd startup script missing from /etc/rc.d in both -current and 11-stable

[tech-lists]

On 03/04/2017 16:07, Alexandr Krivulya wrote:
> Hi! I think you loose it after some updates. Both 11-stable and current
> contains it:
> 
> https://svnweb.freebsd.org/base/head/etc/rc.d/inetd?view=log
> https://svnweb.freebsd.org/base/stable/11/etc/rc.d/inetd?view=log
> 
> Check your src tree and install it.

Thanks for the tip. I copied it over from /usr/src/etc/rc.d

still puzzled as to why it wasn't installed though. When I upgrade, it's
make clean && make buildworld && make buildkernel && make installkernel
&& mergemaster -p

then make installworld then mergemaster.

-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: inetd startup script missing from /etc/rc.d in both -current and 11-stable

[tech-lists]

On 03/04/2017 19:01, Ngie Cooper (yaneurabeya) wrote:
> Please double check your build options. If MK_INETD=no (WITHOUT_INETD=, 
> typically) is set in src.conf, it won’t install this and other inetd-related 
> items.

...and that was it. I should have seen that (was sure I checked), sorry
for the noise. In mitigation, I'm only using inetd on one system among
many otherwise identical systems. Serves me right for using identical
src.confs, lol

many thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

swapfile query

[tech-lists]

Hello list,

(freebsd-current is r317212 on this machine)

I have a machine with 128GB RAM. When 12-current was installed, for some
reason the swap partition was set to 4GB. I see sometimes via top and
also via daily status reports that sometimes the machine runs out of
swap. It doesn't crash the machine though.

I know how to add more swap with a swapfile. My questions are:

1. should I make more than one swapfile, say 4x32GB or will it be ok
with one 128GB swapfile?

2. will the 4GB already there as swap play nice with a swapfile, or
multiple swapfiles? Or should I deactivate the 4GB swap partition first?

3. should total swap be 1x 2x or some other multiple of RAM these days?

FreeBSD and the swap partition reside on the same SSD. The swapfiles, if
created, will reside on this SSD.

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapfile query

[tech-lists]

On 19/08/2017 17:54, Cy Schubert wrote:
> Then it doesn't matter if you use one or many swapfiles and deleting the 4 
> GB won't make a difference. Just add the desired swap as required.
> 
> With 128 GB RAM you shouldn't be swapping anyway. If your system is you 
> have more serious problems than the lack of swap.

The system is a bhyve host. There are 9 guests, two of them are
freebsd-11-stable, the rest are ubuntu-14.04-LTS. Restarting some (but
not all) of the guests has the effect of decreasing swap usage. The
system also runs ZFS. The guests live on the ZFS filesystem.

The OS & swap on the host are SSD and are not part of the ZFS system.

What I'm seeing is, the host system won't touch swap for days. I guess
when the guests get busier than an as yet unknown amount, the host
starts using swap. The issue I'm having isn't so much it using swap,
it's that the used swap seemingly is not liberated after it has been
used, and I don't know exactly how to narrow it down.

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapfile query

[tech-lists]

On 19/08/2017 22:00, Cy Schubert wrote:
> An easy way to find out is to run top, type in "w", then "o" and "swap" to 
> see which processes are using swap. You'll notice that the numbers won't 
> add up. I haven't looked at this but my guess is that there may be swap 
> leak. You can verify this by replacing the swapfile (add a new and remove 
> the old).

Thanks for the tip. I need to wait (might be a few weeks) to see when it
starts eating swap again, then I'll do what you suggest. I got the
system from 94% swap in use to 39% by restarting some of the VMs, then I
was able to swapoff/swapon to empty the swapfile.

Here's a snapshot of the system in an idle state, sr is mostly above 300

procs  memory   pagedisks faults cpu
r b w  avm   fre   flt  re  pi  pofr   sr ad0 da0   insycs
us sy id
0 0 27 189G   27G   103   0   0   077  329   0   0   74   801  1663
0  0 100
0 0 27 189G   27G38   0   0   0 0  337   0   0   93   745  1997
0  0 100
0 0 27 189G   27G   187   0   0   0 0  329   0   0   90   669  1853
0  0 100
1 0 27 189G   27G38   0   0   0 0  340   0   0   83   774  1816
0  0 100
0 0 27 189G   27G37   0   0   0 1  370   0   0   77   767  1839
0  0 100
1 0 27 189G   27G48   0   0   0 0  294   1   0  125  2239  3382
0  0 100
0 0 27 189G   27G20   0   0   0 0  329   3   0   88   651  1797
0  0 100
^C

yet mem from top shows 27GB free:

last pid: 71790;  load averages:  0.11,  0.09,  0.05
up 121+03:19:29 13:55:49
99 processes:  1 running, 98 sleeping
CPU:  0.0% user,  0.0% nice,  0.1% system,  0.1% interrupt, 99.8% idle
Mem: 769M Active, 11G Inact, 21G Laundry, 64G Wired, 924M Buf, 27G Free
ARC: 60G Total, 8979M MFU, 51G MRU, 16K Anon, 153M Header, 755K Other
 60G Compressed, 62G Uncompressed, 1.04:1 Ratio, 41M Overhead
Swap: 4034M Total, 4034M Free

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: swapfile query

[tech-lists]

On 20/08/2017 08:22, Gary Jennejohn wrote:
> Depends.  I have vm.pageout_update_period=0 in /etc/sysctl.conf
> and scan rate (sr) really does reflect the true scan rate.  On
> my system sr is 0 while the system is idle.
> 
> As an aside, my system (8GB RAM) hardly ever swaps, even under
> heavy memory load.

Mine is:

root@host:~ # sysctl vm.pageout_update_period
vm.pageout_update_period: 600
root@host:~ #

I'll try with a 0 setting

-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

openbsd 6.0 or 6.1 guest on freebsd-12 (current) host

[tech-lists]

Hello freebsd-virtualization@

[also cc'd to freebsd-current],

I'd like to run openbsd 6.0 or 6.1 guest under a 12-current bhyve
system. I'd like it to run two cpus, so to use the openbsd smp kernel. I
can see, from searching various mailing lists that there have been
issues in getting openbsd to boot. Have these issues been fixed?

Also, is there a howto for this? I found one here:
http://www.allanjude.com/bsd/virtualization-host-bhyve.html but there's
no date on the document, it's not on the official freebsd sites and so
have no idea if the information is still current.

I realise that HardenedBSD has fixed some issues with this, but I can't
easily change the host to that OS unfortunately.

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: openbsd 6.0 or 6.1 guest on freebsd-12 (current) host

[tech-lists]

On 05/09/2017 22:56, Jason Tubnor wrote:
> I'm not sure of the exact issue you are referring to but I run a lot of
> OpenBSD 6.1 hosts under bhyve with GENERIC.MP .  You
> can use either the grub-bhyve style boot or UEFI, both work fine.
> 
> I have found the chyves framework (it is in packages) good for standing
> up and managing bhyve guests - with ZFS, especially for a team that are
> new to the platform.  You have to hack the following
> /usr/local/lib/chyves files:
> 
> chyves-guest-start
> chyves-properties
> chyves-resources
> 
> to get 6.1 to install and boot (I yet to push those patches upstream).
> 
> So to answer your question directly, there is currently no known issue
> in getting bhyve to run OpenBSD 6.1 on Intel or AMD platforms.  Enjoy!

Hi Jason, thanks for answering. I'll have a go at this. Up until now
I've run all my VMs longhand in a screen. Good to know openbsd works.
Have you encountered anything on openbsd in a bhyve that you've found
not to work?

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: openbsd 6.0 or 6.1 guest on freebsd-12 (current) host

[tech-lists]

On 06/09/2017 16:23, Jan Bramkamp wrote:
> I'm running OpenBSD 6.1 (with two virtual CPU cores) as bhyve guest on
> FreeBSD 11.1. The only problem I encountered is that it requires an
> external grub bootloader because the OpenBSD EFI boot code is
> incompatible with the bhyve EFI boot ROM.

Hi,

Which external grub bootloader did you use? Was it sysutils/grub2-bhyve ?

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: make installworld broke / how to recover

[tech-lists]

On Thu, Feb 22, 2018 at 03:10:17AM -0800, Jack L. wrote:

maybe try a clean buildworld, update /usr/src to the latest version, rm -rf
/usr/obj, then make buildworld && make installworld && make kernel and see
if that fixes the issue?


Is there a documented way of say booting to memstick, starting fixit,
mounting the zfs from the broken system then building/installing a 
new world? Is there enough "environment" and utilities to do this on the

fixit disk?

[never had this happen before, anticipate steep learning curve]

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

updating via svn and usb2 thumbdrives

[tech-lists]

Hi,

When updating, particularly when downloading the src or ports tree for
the first time, even though I've taken all approaches possible to speed
up access to attached usb2 drives, I'll get these errors which will
cause the update to bail:

Aports/www/py-django-otp
svn: E120106: ra_serf: The server sent a truncated HTTP response body.

where it'll remain until I restart it but sometimes it'll crash so badly
svn will demand svn cleanup on the dir I'm downloading to, like this:

Aports/www/elgg/files
svn: E120106: ra_serf: The server sent a truncated HTTP response body.
# svnlite co https://svn0.eu.FreeBSD.org/ports/head /ext/ports
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup'
for details)
svn: E155004: Working copy '/ext/ports' locked.
svn: E155004: '/ext/ports' is already locked.

So I do this:

# svnlite cleanup /ext/ports

...and I can start svnlite again.

I'm sure this has to do with the thumbdrive 'catching up' with writing.
So my question is this: Is there some switch in svnlite or some tool or
parameter I can give to the process that will either buffer or limit the
demands made of the device? It's UFS2 mounted with -o async[might be
redundant],rw and has soft-updates but no journalling.

My connection speed is 23Mbit so I'm thinking that on usb2 this might be
approaching its random write speed but i'm unsure. What's the best way
to permanently fix this?

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: best settings for usb2 and attached disks, and sdcards

[tech-lists]

On 07/03/2018 17:16, Ian Lepore wrote:
> If you have journaling enabled on the usb or sdcard filesystems, turn
> it off.

Yes, it's turned off. The new fs was made with
newfs -U -n -t. I found later that the thumb drives didn't have TRIM
functionality but didn't know for sure at the time (only found out when
a notification popped up on the console that TRIM was switched on the
filesystem but the disk didn't support it).

thanks,
-- 
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

freebsd bhyve instance does not show kernel messages after boot screen

[tech-lists]

Hello list,

context is freebsd-12 r317212 host and freebsd-11-stable r333924 guest

I run this freebsd instance in screen. I start it like this:

vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest

It starts, I get the daemon screen, then this:

/boot/kernel/kernel text=0x70572d data=0xa5648+0x340ac0 
syms=[0x8+0xc0c78+0x8+0xde421]

/boot/entropy size=0x1000
Booting...
Unhandled ps2 mouse command 0xe1

and that's it. The guest loads, is functional, I can ssh into it, etc.

Other freebsd-11 VMs started in the exact same way on the same server 
give the expected messages scrolling up when the VM starts. Why is this 
VM different and how can I fix? There was a time when the messages were 
displayed, then one day they didn't.


I've built/installed a new world/kernel on this VM to no effect.

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: freebsd bhyve instance does not show kernel messages after boot screen

[tech-lists]

On 14/06/2018 23:26, David P. Discher wrote:

Try in /boot/loader.conf of the VM :

console=userboot

or after beastie drop to loader OK promot  and try :

set console=userboot

I think 11.x should fall back to userboot in bhyve if vidconsole of 
comconsole were set.


(This is assuming non-EFI booting - using bhyveloader ).


Hi,

Thanks for trying to help. I tried it both ways - in loader.conf and 
from the loader prompt but unfortunately it didn't work. For 
clarification, here's the exact way I start the VM:


1. $ screen -S fbsd11-vm
2. $ sudo su -
3. # (cd to where vm is)
4. sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 8192M -t tap3 -d 
fbsd-guest.img fbsd-guest


If I transfer the VM to a freebsd-11 host (r333874) it also happens. So 
the behaviour is a property of the VM. Unless of course the issue is 
with bhyve itself on both -stable and -current.


A possible clue (but I'm really out of my depth here) is ISTR something 
like this happening if say the VM is called say fbsd-guest and is then 
subsequently launched with some other name like fbsd11guest.


Any ideas?

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: freebsd bhyve instance does not show kernel messages after boot screen

[tech-lists]

On 15/06/2018 15:02, Rodney W. Grimes wrote:

With the VM shutdown look in /dev/vmm for the same name as the VM,
if you see it there, make sure you do not have a running instnace
of it, then do:
bhyvectl --destroy --name=fbsd11-vm

You may have remanants of a prior/crashed VM hanging around
causing you issues.


Unfortunately this made no difference either.

If someone can tell me what to do to debug [1] this, I'll make a problem 
report?


[1] unfortunately debugging this particular thing is outside of my realm 
of expertise. I know how to start/stop bhyve but not much else outside 
of that.


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

ino64

[tech-lists]

Hello,

When upgrading an old-ish 12-current (r317212), as per:


20170523:
The "ino64" 64-bit inode project has been committed, which extends
a number of types to 64 bits.  In order to upgrade, carefully follow
the full procedure documented below under the heading "To rebuild
everything and install it on the current system."  Specifically, a
reboot is required after installing the new kernel before installing
world.


is there anything more specific I need to do as well, like rebuild all 
installed ports?


The system runs ZFS. It is *not* root-on-ZFS though. Is there anything 
more I need to consider for this?


The system also runs bhyve. Are there any special considerations I need 
to bear in mind for the guest VMs?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ino64

[tech-lists]

On 25/06/2018 16:37, Warner Losh wrote:
While the compat stuff generally works, there are edge cases where it 
will fail when you have a mixed environment. You're best bet is to 
reinstall all ports. If you do just a few, you'll hit the edge cases.


Hi,

What do you mean by "mixed environment"? for context, this is a remote 
server that runs sshd abd bhyve, and that's it.


I expected to have to rebuild everything. I guess portupgrade -af will 
do it?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

[tech-lists]

On 03/07/2018 19:47, Michael Butler wrote:

That would've been ..

Jun  1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: Fri Jun
1 08:25:58 EDT 2018

I'm going to build one with SVN r334862 reverted to see if that works,


Hi,

Is it working now? Am asking because a system I'd like to take from 
11-stable to 12 uses the em driver.


thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

[tech-lists]

On 03/07/2018 18:47, Michael Butler wrote:

On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
(using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
can't without the em0 interface stalling :-(

On a guess, I tried reverting SVN r335303 but that didn't help.

em0:  port 0xf080-0xf09f mem
0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
em0: attach_pre capping queues at 1
em0: using 1024 tx descriptors and 1024 rx descriptors
em0: msix_init qsets capped at 1
em0: PCIY_MSIX capability not found; or rid 0 == 0.
em0: Using an MSI interrupt
em0: allocated for 1 tx_queues
em0: allocated for 1 rx_queues
em0: Ethernet address: f0:1f:af:66:95:7e
em0: netmap queues/slots: TX 1/1024, RX 1/1024
em0: link state changed to UP

  [ initiate "zfs send" ]

em0: TX(0) desc avail = 41, pidx = 172
em0: link state changed to DOWN
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0

  .. ad nauseum ..

"ifconfig em0 down; ifconfig em0 up" doesn't help.

Any hints?


Hi,

I'm not seeing any problems using em0/saturating upstream
using 12.0-CURRENT #0 r335979
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

bhyve and freebsd memstick installer

[tech-lists]

Hello,

context: freebsd-12-current server, amd64

I usually install a freebsd guest like this:

sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img 
-i -I FreeBSD-installation-dvd1.iso guestname


I only have memstick.img - how do I either:

1. convert the memstick to dvd1.iso
2. make bhyve use the memstick installation iso (I don't think it can do 
this as the option to do so isn't in vmrun.sh)


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: bhyve and freebsd memstick installer

[tech-lists]

On 06/07/2018 18:32, Rodney W. Grimes wrote:

Untested, but since memstick is actually a "disk" image and not
a "cdrom" image you should be able to do something like
vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname

Your memstick should show up as ada0,
and your guest.img should be ada1.


Thanks for that, I'll try it next time I can.

I got round it temporarily by mounting the memstick as /dev/md1p3 and 
pointing mkisofs at that.


the -i -I thing of bhyve threw me. I thought I'd need it to point to 
bootable media.


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

aarch64-none-elf-gcc and related programs will not install

[tech-lists]

Hi,

context: 12.0-CURRENT #0 r336037 amd64 / ports r474140

I get the following when installing aarch64-none-elf-gcc and related 
programs from ports. It will build fine, just errors on install.


my /etc/make.conf looks like this:

> less /etc/make.conf
WRKDIRPREFIX=/buildports
MAKE_JOBS_NUMBER=36
WITH_CCACHE_BUILD=YES
CCACHE_DIR=/ccache
WITH_MANCOMPRESS=YES
WITHOUT_DEBUG=YES
OPTIONS_SET+=OPTIMIZED_CFLAGS
OPTIONS_SET+=ICONV
CPUTYPE?=sandybridge

It doesn't matter if /etc/make.conf is moved out of the way.

these also fail in a similar way:
devel/arm-none-eabi-gcc
sysutils/u-boot-rpi2
sysutils/u-boot-rpi3

output when trying to install:

root@REDACTED:/usr/ports/devel/aarch64-none-elf-gcc # make distclean && 
make clean && make

===>  Cleaning for aarch64-none-elf-gcc-6.4.0
===>  Deleting distfiles for aarch64-none-elf-gcc-6.4.0
===>  Cleaning for aarch64-none-elf-gcc-6.4.0
===>  License GPLv3 GPLv3RLE accepted by the user
===>   aarch64-none-elf-gcc-6.4.0 depends on file: /usr/local/sbin/pkg - 
found

=> gcc-6.4.0.tar.xz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch 
https://mirrors.kernel.org/sourceware/gcc/releases/gcc-6.4.0/gcc-6.4.0.tar.xz


[...]

/bin/sh 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/gcc-6.4.0/libgcc/../mkinstalldirs 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include
install  -m 0644 unwind.h 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include
gmake[4]: Leaving directory 
'/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/.build/aarch64-none-elf/ilp32/libgcc'
gmake[3]: Leaving directory 
'/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/.build/aarch64-none-elf/libgcc'
gmake[2]: Leaving directory 
'/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/.build/aarch64-none-elf/libgcc'
gmake[1]: Leaving directory 
'/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/.build'

> Compressing man pages (compress-man)
root@REDACTED:/usr/ports/devel/aarch64-none-elf-gcc #

root@REDACTED:/usr/ports/devel/aarch64-none-elf-gcc # make deinstall 
reinstall

===>  Deinstalling for aarch64-none-elf-gcc
===>   aarch64-none-elf-gcc not installed, skipping
===>  Installing for aarch64-none-elf-gcc-6.4.0
===>   Registering installation for aarch64-none-elf-gcc-6.4.0
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_fil.h:No 
such file or directory
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_lookup.h:No 
such file or directory
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_nat.h:No 
such file or directory
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_proxy.h:No 
such file or directory
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_scan.h:No 
such file or directory
pkg-static: Unable to access file 
/buildports/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc/aarch64-none-elf/6.4.0/include-fixed/netinet/ip_state.h:No 
such file or directory

*** Error code 74

Stop.
make[1]: stopped in /usr/ports/devel/aarch64-none-elf-gcc
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/aarch64-none-elf-gcc
root@REDACTED:/usr/ports/devel/aarch64-none-elf-gcc #

How can I fix?

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

aarch64-arm64 fails to build kernel 12-current raspberry pi 3

[tech-lists]

Hello lists [x-posted to -current where it's also relevant]

12-current-arm64 fails to build generic-nodebug kernel

context:
12.0-CURRENT #0 r336134: Mon Jul  9 GENERIC arm64 (this is the older rpi3B+)

root@rpi3:/usr/src# svnlite info
Path: .
Working Copy Root Path: /ext/src
URL: https://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 336195
Node Kind: directory
Schedule: normal
Last Changed Author: eugen
Last Changed Rev: 336195
Last Changed Date: 2018-07-11 10:41:50 +0100 (Wed, 11 Jul 2018)

Some dirs on /usr are symlinked to a 1TB external disk. Swap is on the 
external disk. Made sure there was no src.conf or make.conf present:


root@rpi3:/root# cd /etc
root@rpi3:/etc# mv src.conf old.src.conf
root@rpi3:/etc# mv make.conf old.make.conf
root@rpi3:/etc# cd /usr/src

root@rpi3:/usr/src# rm -rf /ext/obj
root@rpi3:/usr/src# mkdir /ext/obj
root@rpi3:/usr/src# ls -lah /usr
total 72
drwxr-xr-x  12 root  wheel   512B Jul 10 11:15 .
drwxr-xr-x  20 root  wheel   512B Jul 10 18:45 ..
drwxr-xr-x   2 root  wheel   7.5K Jul  9 20:45 bin
drwxr-xr-x   2 root  wheel   512B Jul 10 11:15 home
drwxr-xr-x  56 root  wheel   6.5K Jul  9 20:44 include
drwxr-xr-x  10 root  wheel16K Jul  9 20:45 lib
drwxr-xr-x   5 root  wheel   512B Jul  9 20:28 lib32
drwxr-xr-x   5 root  wheel   512B Jul  9 20:28 libdata
drwxr-xr-x   9 root  wheel   1.5K Jul  9 20:45 libexec
lrwxr-xr-x   1 root  wheel10B Jul 10 11:43 local -> /ext/local
lrwxr-xr-x   1 root  wheel 8B Jul 10 11:41 obj -> /ext/obj
lrwxr-xr-x   1 root  wheel10B Jul 10 11:41 ports -> /ext/ports
drwxr-xr-x   2 root  wheel   5.0K Jul  9 20:45 sbin
drwxr-xr-x  29 root  wheel   512B Jul  9 20:28 share
lrwxr-xr-x   1 root  wheel 8B Jul 10 11:41 src -> /ext/src
drwxr-xr-x  15 root  wheel   512B Jul  9 20:46 tests

root@rpi3:/usr/src# make -j10 cleanworld && make -j10 cleandir && make 
-j10 clean <--- just to make absolutely sure


[...]

RPI3 is just a copy of GENERIC-NODEBUG. it looks like this:

include GENERIC

ident   RPI3

nooptions   INVARIANTS
nooptions   INVARIANT_SUPPORT
nooptions   WITNESS
nooptions   WITNESS_SKIPSPIN
nooptions   DEADLKRES
nooptions   USB_DEBUG

root@rpi3:/usr/src# make -j1 buildkernel KERNCONF=RPI3

[...]

===> armv8crypto (all)
[Creating objdir 
/ext/obj/ext/src/arm64.aarch64/sys/RPI3/modules/ext/src/sys/modules/armv8crypto...]

machine -> /ext/src/sys/arm64/include
ln -sf /ext/obj/ext/src/arm64.aarch64/sys/RPI3/opt_bus.h opt_bus.h
awk -f /ext/src/sys/tools/makeobjops.awk /ext/src/sys/kern/device_if.m -h
awk -f /ext/src/sys/tools/makeobjops.awk /ext/src/sys/kern/bus_if.m -h
awk -f /ext/src/sys/tools/makeobjops.awk 
/ext/src/sys/opencrypto/cryptodev_if.m -h
cc -target aarch64-unknown-freebsd12.0 
--sysroot=/ext/obj/ext/src/arm64.aarch64/tmp 
-B/ext/obj/ext/src/arm64.aarch64/tmp/usr/bin -c -O2 -pipe 
-fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -DKLD_TIED -nostdinc 
-DHAVE_KERNEL_OPTION_HEADERS -include 
/ext/obj/ext/src/arm64.aarch64/sys/RPI3/opt_global.h -I. -I/ext/src/sys 
-I/ext/src/sys/contrib/ck/include -g -fPIC 
-I/ext/obj/ext/src/arm64.aarch64/sys/RPI3 -MD -MF.depend.genoffset.o 
-MTgenoffset.o -mgeneral-regs-only -ffixed-x18 -ffreestanding -fwrapv 
-fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual 
-Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member -std=iso9899:1999 
/ext/src/sys/kern/genoffset.c

sh /ext/src/sys/kern/genoffset.sh genoffset.o > offset.inc
cc -target aarch64-unknown-freebsd12.0 
--sysroot=/ext/obj/ext/src/arm64.aarch64/tmp 
-B/ext/obj/ext/src/arm64.aarch64/tmp/usr/bin  -O2 -pipe 
-fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -DKLD_TIED -nostdinc 
  -DHAVE_KERNEL_OPTION_HEADERS -include 
/ext/obj/ext/src/arm64.aarch64/sys/RPI3/opt_global.h -I. -I/ext/src/sys 
-I/ext/src/sys/contrib/ck/include -fno-common -g -fPIC 
-I/ext/obj/ext/src/arm64.aarch64/sys/RPI3   -MD 
-MF.depend.armv8_crypto.o -MTarmv8_crypto.o -mgeneral-regs-only 
-ffixed-x18 -ffreestanding -fwrapv -fstack-protector -gdwarf-2 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wcast-qual -Wundef 
-Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member-std=iso9899:1999 -c 
/ext/src/sys/crypto/armv8/armv8_crypto.c -o armv8_crypto.o

Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3

[tech-lists]

On 11/07/2018 17:21, Mark Millard wrote:

It seems from the quoted material that neither kernel-toolchain nor
build world was done before buildkernel . My understanding is that
the intent is that one or the other be done first. (But for aarch64
currently only buildworld works.)


Thanks for this. I'm running a buildworld now.

For how long has it been the case that buildworld is needed for 
buildkernel? Coming from amd64 and before that, i386, in situations 
where I've only wanted to install a custom kernel, I was firstly used to 
making and installing it from /sys/{i386,amd64}/conf. Then that broke a 
number of years ago. Then got used to making kernel in /usr/src with 
make buildkernel && make installkernel. And now this is broken, on 
aarch64-arm64. Nobody knows if it's accidental or policy.


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3

[tech-lists]

On 12/07/2018 19:32, Dimitry Andric wrote:

No, it's because sys/crypto/armv8/armv8_crypto_wrap.c includes
, an intrinsics header, which in turn requires .

This was introduced inhttps://svnweb.freebsd.org/changeset/base/308921,
and at the time resulted in similar build failures, specifically when
one attempted to build a new kernel, without building world or a new
toolchain first.


Hi,

Ok, it's finished building and installing. The command I used was this:

# make -j10 buildworld && make -j10 buildkernel KERNCONF=RPI3

and it all built, (so I'll close the PR I opened). Then I did make 
installkernel KERNCONF=RPI3 and because I thought might as well install 
everything now it's built, mergemaster -p and make installworld && 
mergemaster -Ui.


So I take it then, that every time I want to build a kernel, I either 
have to do the above or use make kernel-toolchain. Is this correct?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: aarch64-arm64 fails to build kernel 12-current raspberry pi 3

[tech-lists]

On 14/07/2018 11:15, Ronald Klop wrote:
What is RPI3? Mine runs GENERIC and there is no RPI3 config in 
/usr/src/sys/arm64/conf. I can find RPI2 in sys/arm/conf.


RPI3 is the same as GENERIC-NODEBUG, apart from the ident string which 
is also RPI3. (was mentioned at the start of the thread which branched off)


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

how to make ports not install xorg or dependencies

[tech-lists]

Hello,

context: freebsd-12 r336215 arm64

I don't want xorg or X11 or any of its components installed on this 
system. I install ports in the traditional way, in other words cd port 
&& make config && make install. Any ports that in a generic config want 
to install xorg libs, I want the no-x11 variant.


There used to be a way to enforce this no-xorg in make.conf but looking 
at /usr/share/examples/etc/make.conf I can find no reference to X Xorg 
x11 or xorg. I presume there's a new method. If there is, can anyone 
please tell me how?


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

boot errors since upgrading to 12-current

[tech-lists]

Hello,

context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is *not* 
root-on-zfs. It boots to an SSD. The three disks indicated below are 
spinning rust.


NAMESTATE READ WRITE CKSUM
storage ONLINE   0 0 0
  raidz1-0  ONLINE   0 0 0
ada1ONLINE   0 0 0
ada2ONLINE   0 0 0
ada3ONLINE   0 0 0

This machine was running 11.2 up until about a month ago.

Recently I've seen this flash up on the screen before getting to the 
beastie screen:


BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS drive F: is disk3
BIOS drive G: is disk4
BIOS drive H: is disk5
BIOS drive I: is disk6
BIOS drive J: is disk7

[the above is normal and has always has been seen on every boot]

read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31
read 1 from 0 to 0xcbdb1330, error: 0x31

the above has been happening since upgrading to -current a month ago

 ZFS: i/o error - all block copies unavailable
 ZFS: can't read MOS of pool storage

the above is alarming and has been happening for the past couple of 
days, since upgrading to r337682 on the 12th August.


The beastie screen then loads and it boots normally.

Should I be concerned? Is the output indicative of a problem?

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot errors since upgrading to 12-current

[tech-lists]

On 14/08/2018 21:16, Toomas Soome wrote:




On 14 Aug 2018, at 22:37, tech-lists  wrote:

Hello,

context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is
*not* root-on-zfs. It boots to an SSD. The three disks indicated
below are spinning rust.

NAMESTATE READ WRITE CKSUM storage ONLINE   0
0 0 raidz1-0  ONLINE   0 0 0 ada1ONLINE   0
0 0 ada2ONLINE   0 0 0 ada3ONLINE   0
0 0

This machine was running 11.2 up until about a month ago.

Recently I've seen this flash up on the screen before getting to
the beastie screen:

BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is
disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H:
is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7

[the above is normal and has always has been seen on every boot]

read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to
0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 
read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to
0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 
read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to

0xcbdb1330, error: 0x31

the above has been happening since upgrading to -current a month
ago

ZFS: i/o error - all block copies unavailable ZFS: can't read MOS
of pool storage

the above is alarming and has been happening for the past couple of
days, since upgrading to r337682 on the 12th August.

The beastie screen then loads and it boots normally.

Should I be concerned? Is the output indicative of a problem?



Not immediately and yes. In BIOS loader, we do all disk IO with INT13
and the error 0x31 is often hinting about missing media or some other
controller related error. Could you paste the output from loader
lsdev -v output?

The drive list appears as an result of probing the disks in
biosdisk.c. The read errors are from attempt to read 1 sector from
sector 0 (that is, to read the partition table from the disk). Why
this does end with error, would be interesting to know, unfortunately
that error does not tell us which disk was probed.


Hi Toomas, thanks for looking at this.

lsdev -v looks like this:

OK lsdev -v
disk devices:
disk0: BIOS drive C (16514064 X 512):
disk0s1: FreeBSD  111GB
disk0s1a: FreeBSD UFS 108GB
disk0s1b: FreeBSD swap3881MB

disk1: BIOS drive D (16514064 X 512):
disk2: BIOS drive E (16514064 X 512):
disk3: BIOS drive F (16514064 X 512):
disk4: BIOS drive G (2880 X 512):
read 1 from 0 to 0xcbde0a20, error 0x31
disk5: BIOS drive D (2880 X 512):
read 1 from 0 to 0xcbde0a20, error 0x31
disk6: BIOS drive D (2880 X 512):
read 1 from 0 to 0xcbde0a20, error 0x31
disk7: BIOS drive D (2880 X 512):
read 1 from 0 to 0xcbde0a20, error 0x31
OK

disk4 to disk7 corresponds with da0 to da3 which are sd/mmc devices 
without any media in. What made me notice it is it never showed the read 
1 from 0 to $random_value on 11-stable. The system runs 12-current now.


disk1 to disk3 are the hard drives making up ZFS. These are 4TB Western 
Digital SATA-3 WDC WD4001FAEX.



Since you are getting errors from data pool ‘storage’, it does not
affect the boot. Why the pool storage is unreadable - it likely has
to do about the errors above, but can not tell for sure based on the
data presented here….


Thing is, the data pool works fine when boot completes. i.e it loads 
read/write and behaves normally.


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: zpool scrub. Wtf?

[tech-lists]

On 12/08/2018 18:53, Cy Schubert wrote:

I haven't looked at it closely but from what I saw it was counting scan reads 
and issued reads. It may be a simple matter of dividing by 2.


Dividing what by 2?

scan: scrub in progress since Tue Aug  7 21:21:51 2018
804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total
0 repaired, 129,87% done, 929637 days 13:43:01 to go

I'm also seeing this problem running 12.0-ALPHA1 #0 r337682

thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot errors since upgrading to 12-current

[tech-lists]

Hello Toomas,

On 15/08/2018 07:31, Toomas Soome wrote:
Well that does explain the problem, if you look on the sizes reported… 
so your BIOS is reporting wrong sizes, is unable to access whole 4TB 
space and the zfs reader is not getting the correct data from the disks


Do you know why this was not happening on 11-stable but is happening on 
12-current?


The BIOS has not been modified since the machine was bought back in 2014.

Once booted, the whole drives in the pool are accessible:

Filesystem SizeUsed   Avail Capacity  Mounted on
storage5.8T1.1T4.8T18%/storage

The pool is raidz1-0 so this is the available size I'd expect with 3 x 
4Tb drives. Am I incorrect here?


- and is resulting with errors. Thats why you get the errors from 
‘storage’ pool and yes, this is harmless for boot because you have 
separate (small) disk for the boot.


Is it also harmless for the 'storage' pool ?

thanks,

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot errors since upgrading to 12-current

[tech-lists]

On 15/08/2018 12:49, Kyle Evans wrote:

On Wed, Aug 15, 2018 at 6:22 AM, tech-lists  wrote:

Hello Toomas,

On 15/08/2018 07:31, Toomas Soome wrote:


Well that does explain the problem, if you look on the sizes reported… so
your BIOS is reporting wrong sizes, is unable to access whole 4TB space and
the zfs reader is not getting the correct data from the disks



Do you know why this was not happening on 11-stable but is happening on
12-current?

The BIOS has not been modified since the machine was bought back in 2014.



Perhaps r335245, which fixed a logical error and completely changed
the calculations for this stuff and possibly sent you on dramatically
different path. There's not too many commits to this area that haven't
yet landed back in stable/11, fortunately.

Thanks,

Kyle Evans



Thank you Toomas and Kyle for the clarifications.

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: boot errors since upgrading to 12-current

[tech-lists]

On 15/08/2018 13:20, tech-lists wrote:

On 15/08/2018 12:49, Kyle Evans wrote:

On Wed, Aug 15, 2018 at 6:22 AM, tech-lists  wrote:

Hello Toomas,

On 15/08/2018 07:31, Toomas Soome wrote:


Well that does explain the problem, if you look on the sizes 
reported… so
your BIOS is reporting wrong sizes, is unable to access whole 4TB 
space and

the zfs reader is not getting the correct data from the disks



Do you know why this was not happening on 11-stable but is happening on
12-current?

The BIOS has not been modified since the machine was bought back in 
2014.




Perhaps r335245, which fixed a logical error and completely changed
the calculations for this stuff and possibly sent you on dramatically
different path. There's not too many commits to this area that haven't
yet landed back in stable/11, fortunately.

Thanks,

Kyle Evans



Thank you Toomas and Kyle for the clarifications.



addendum to this - installed new world and kernel r337835 and the zfs 
warning at boot seems to have disappeared. Something else odd has 
started happening though, will make a new email for it - usb keyboard no 
longer functioning at the beastie menu, but functions when boot completes.


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

usb keyboard nonfunctional at beastie menu after r337835

[tech-lists]

Hi,

context: amd64 FreeBSD 12.0-ALPHA1 #0 r337835

USB keyboard is non-functional after r337835. It's fine when booting 
completes. I'm happy to do more diagnostics if anyone can suggest any.


thanks,
--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

[tech-lists]

On 22/08/2018 05:29, Manfred Antar wrote:



On Aug 21, 2018, at 7:23 PM, Alexey Dokuchaev  wrote:

On Tue, Aug 21, 2018 at 11:22:56PM +0700, Alex V. Petrov wrote:

 Перенаправленное сообщение 
Тема: nvidia-driver build error (last ports, FreeBSD-HEAD)
Дата: Tue, 21 Aug 2018 16:41:42 +0700
От: Alex V. Petrov
Кому: FreeBSD Ports

Should be fixed as of r477761.

./danfe


It's not fixed, seems to error elsewhere now:

context: 12.0-ALPHA1 #0 r337886 / ports r477782 / empty /etc/make.conf

This is a bare metal installation.

root@desktop:/usr/ports/x11/nvidia-driver# make distclean && make clean 
&& make MAKE_JOBS_UNSAFE=yes


[...]

cc  -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.77\" 
-D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O2 
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -Wno-sign-compare 
-Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG -Werror=undef  -Werror 
-D_KERNEL -DKLD_MODULE -nostdinc  -I. -I../common/inc -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/ck/include -fno-common  -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer   -MD  -MF.depend.nvidia_subr.o 
-MTnvidia_subr.o -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse 
-msoft-float  -fno-asynchronous-unwind-tables -ffreestanding -fwrapv 
-fstack-protector -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wcast-qual 
-Wundef -Wno-pointer-sign -D__printf__=__freebsd_kprintf__ 
-Wmissing-include-dirs -fdiagnostics-show-option -Wno-unknown-pragmas 
-Wno-error-tautological-compare -Wno-error-empty-body 
-Wno-error-parentheses-equality -Wno-error-unused-function 
-Wno-error-pointer-sign -Wno-error-shift-negative-value 
-Wno-address-of-packed-member  -mno-aes -mno-avx  -std=iso9899:1999 -c 
nvidia_subr.c -o nvidia_subr.o
nvidia_subr.c:1131:41: error: too many arguments to function call, 
expected 7, have 8

sc->dma_mask, PAGE_SIZE, 0, attr);
^~~~
/usr/src/sys/vm/vm_extern.h:61:1: note: 'kmem_alloc_contig' declared here
vm_offset_t kmem_alloc_contig(vm_size_t size, int flags,
^
nvidia_subr.c:1269:45: error: too many arguments to function call, 
expected 7, have 8

sc->dma_mask, PAGE_SIZE, 0, attr);
^~~~
/usr/src/sys/vm/vm_extern.h:61:1: note: 'kmem_alloc_contig' declared here
vm_offset_t kmem_alloc_contig(vm_size_t size, int flags,
^
2 errors generated.
*** Error code 1

Stop.
make[4]: stopped in 
/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.77/src/nvidia

*** Error code 1

Stop.
make[3]: stopped in 
/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.77/src

*** Error code 1

Stop.
make[2]: stopped in 
/usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86_64-390.77

*** Error code 1

Stop.
make[1]: stopped in /usr/ports/x11/nvidia-driver
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/nvidia-driver
root@desktop:/usr/ports/x11/nvidia-driver#

--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: nvidia-driver build error (last ports, FreeBSD-HEAD)

[tech-lists]

On 22/08/2018 16:29, Alan Cox wrote:

All of kmem_alloc_attr(), kmem_alloc_contig(), and kmem_malloc() should
have their first parameter, typically kernel_arena, but sometimes
kmem_arena, removed in FreeBSD 12.

There is still one more pending change to kmem_free() that has not hit
HEAD yet.  That change will be the last.


Thank you, that's very good news. Do you have an idea when the change 
will arrive in -HEAD?


--
J.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

tracking -current, using poudriere-devel and the switch to git

[tech-lists]

Hi,

What's the repo to use now in order to track -current with a poudriere jail
via git ? i.e. in poudriere.conf, what is GIT_BASEURL ?

What's the branch name? (is it master, head, something else?)

If -current fails to compile, how do we reference it? In svn, I'd point svn
info at the sources and it would give a revision number. How is this done with
git?

At the moment, is svn behind git in terms of most recent updates, or the other
way round?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: tracking -current, using poudriere-devel and the switch to git

[tech-lists]

On Wed, Sep 09, 2020 at 04:34:20PM -0400, Ed Maste wrote:

[...lots of stuff explaining...]

thank you
--
J.


signature.asc
Description: PGP signature

AR9271L Atheros Chipset (wireless usb)

[tech-lists]

Hi,

Is AR9271L Atheros Chipset supported yet? I can't find any mention of it
directly under -current.

thanks,
--
J.


signature.asc
Description: PGP signature

in -current is svn still canonical?

[tech-lists]

Hi

As subject - is svn still canonical for -current or is it git now?
If it's not git now, when roughly is the intended switch?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: in -current is svn still canonical?

[tech-lists]

On Tue, Nov 17, 2020 at 03:04:26AM -0800, Jeffrey Bouquet wrote:

..
Can this be put up in a wiki page as well as in each UPDATING, referencing the 
wiki page?
something like

src - current   dec 2020   now  svn up /usr/src... git 
svn cleanup  git ... [ other svn-git...
src - stable may 2021  dec 2020  svn up /usr/ports
src -releasejuly 2021
ports   dec 2021
doc dec 2021


Yeah this is what I was looking for before posting here, was surprised not to find it. 
Thought something as important as this would be linked off the main page. 
--

J.


signature.asc
Description: PGP signature

Re: in -current is svn still canonical?

[tech-lists]

On Tue, Nov 17, 2020 at 10:57:51AM -0700, Warner Losh wrote:

For now, though, you might want to look at
https://github.com/bsdimp/freebsd-git-docs/ for the docs we do have,
especially
https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md which
should answer most of your questions.


Thanks for posting this. May I suggest that it is linked somewhere off the 
section of the website that deals with updating? Particularly following -current.

Like here: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html
or here: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html

where someone considering following -current would see immediately that 
changes were afoot. As well as say a link off the main site, so a casual reader 
could see, too.

--
J.


signature.asc
Description: PGP signature

git tools for building in base?

[tech-lists]

Hi,

As subject - what will there be in base to interact with the new git repo?
I mean, right now, for svn there is svnlite. What for git?

Shouldn't it be in base before the move to git? 


thanks,
--
J.


signature.asc
Description: PGP signature

Re: git tools for building in base?

[tech-lists]

Hi,

On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:

On Tue, Nov 24, 2020 at 2:19 PM tech-lists  wrote:


As subject - what will there be in base to interact with the new git repo?
I mean, right now, for svn there is svnlite. What for git?


'pkg add git' is your choice now.


Shouldn't it be in base before the move to git?


We will have got (from OpenBSD: Game Of Trees) in the future. It isn't
quite there yet, however, so it's not in base. 


Do you agree that this situation is a bad look for an *operating system* ?
Having to depend on a third-party tool to stay up-to-date and secure.

In multiple locations it is said that installing a port is *at your own 
risk*. Personally, I'd like the official updating tool to have had the 
same level of analysis (and so the same level of "risk") on it as the base OS, 
(and also be under the same licence).


I mean, shouldn't all the basic tools be present in an OS, at least in 
order to update it? And *then* migrate to the update method?


When we migrated from CVS to Subversion, we didn't grow svnlite in 
the base for many months after the conversion.


A mistake then and a mistake now with svn to git IMO.
--
J.


signature.asc
Description: PGP signature

possible usb3-connected hard drive spin down causing lag

[tech-lists]

Hi,

I have a usb3-connected harddrive. dmesg shows this:
[...]
da0:  Fixed Direct Access SPC-4 SCSI device
[...]

running current-r367806-arm64

I think it might be auto-spinning-down or auto-sleeping. It's
making initial interaction lag of 2-3 seconds. Is there a 
sysctl or something somewhere where I can tell it to never 
sleep? Or is that something I'd need to contact the 
manufacturer about? Or is there an alternative strategy 
like tmpfs. It's not a "green" drive but I guess it might

be "green" in that it's usb3 powered.

I have vfs.read_max=128 in /etc/sysctl.conf
zdb has ashift=12

In case it's relevant, the filesystem on the disk is zfs. Once
"woken up", inferaction is quick, as expected. 


thanks,
--
J.


signature.asc
Description: PGP signature

Re: possible usb3-connected hard drive spin down causing lag

[tech-lists]

On Thu, Nov 26, 2020 at 07:37:47PM +0100, Dimitry Andric wrote:

In this case it's about ATA commands being passed though the USB bridge.
Does "camcontrol identify daX" fail in your case too?

I have used quite a bunch of different USB disks, mostly from WD or
Seagate, and these come with varying qualities of USB-SATA bridges in
them. But all of them work with "camcontrol identify".


With my usb3 powered disk, camdontrol identify da0 works

some features: support  enabled value
advanced power management  yes  yes 254/0xFE
power management   yes  yes
microcode download yes  yes

loads of others

thanks for posting that script btw

--
J.


signature.asc
Description: PGP signature

Re: possible usb3-connected hard drive spin down causing lag

[tech-lists]

Hi,

It seems the issue wasn't with the hardware or the connection.
I use mutt and it's the program that was slowing everything down,
and that was down to me using new mutt with my old config. The whole
pause for 5 seconds thing was due to it scanning gigabytes of email each 
time it woke up. The fix was to review the config and change a couple of 
settings. Now there's no delay (well there is a bit but only because it's 
scanning the folders it's told to for new mail).


But looking at a hardware cause wasn't in vain. On the way to the solution, 
found a few tips through here that sped up the system generally, and learned 
a bit. So now I have a *really quick* raspberry pi4 which is rock-solid 
stable, so thanks :D


--
J.


signature.asc
Description: PGP signature

firewall choice

[tech-lists]

Hi,

What's the "best" [1] choice for firewalling these days, in the list's opinion?

There's pf, ipf and ipfw. Which is the one being most recently 
developed/updated?
I'm used to using pf, have done for over a decade. But OpenBSD's pf has diverged 
a lot more from when it first came across. There seems to be a lot more options.

Is FreeBSD's pf being actively developed still?

ipfw seems a lot more syntatically complex than pf. Is it more capable also?
I know nothing about ipf yet.

[1] up-to-date, versatile, low overhead, high throughput, IPv6-able,
traffic shaping/queueing

thanks,
--
J.


signature.asc
Description: PGP signature

Re: firewall choice

[tech-lists]

On Fri, Nov 27, 2020 at 06:17:53AM -0500, grarpamp wrote:

What's the "best" [1] choice for firewalling these days, in the list's opinion?
There's pf, ipf and ipfw.


This question comes up over years.

Consider starting and joining with people to create
a comparison page on the FreeBSD Wiki,
both a feature / capability comparison table,
and contextual paragraphs.
A mini project like that can help many users
and add their researches to it.


I'd be happy to if I knew where to start/how to start/is there a guide.
--
J.


signature.asc
Description: PGP signature

Re: possible usb3-connected hard drive spin down causing lag

[tech-lists]

On Fri, Nov 27, 2020 at 04:34:24PM +0100, Ronald Klop wrote:


Mind to share these tips, so I can use them on my RPI4? ;-)


sure!

I'll write up a simple site later, but in summary this is what 
I've done subsequent to the initial setup. E&OE, if it breaks you 
get to keep both bits, no guarantees etc etc. In no particular order:


1. in /boot/msdos/config.txt there's this:
over_voltage=6
arm_freq=2000
sdram_freq_min=3200

[I use a FLIRC case to keep it cool. you *must* use cooling for this.
Max temps I'm seeing under very heavy compiling (it runs poudriere)
is 72 degC in 25 degC ambient]

2. /usr/src /usr/ports /usr/local /usr/obj /home /var/cache/ccache
are all on the usb3 disk, seperate datasets.

3. swap is 16GB and is the first partition on the usb3 disk

4. for compiling, ccache is a must.

5. set tmp to tmpfs in /etc/fstab. I use 1GB like this:
tmpfs /tmp tmpfs rw,mode=1777,size=1024m 0 0

6. make things like mutt use this /tmp

7. enable powerd and on bootup. Make it almost always use the
overclocked speed like this in /etc/rc.conf
powerd_enable="YES"
powerd_flags="-r 1"

This makes it run @ 2GHz always without needing to set something like 
boost_turbo.

8. in /etc/sysctl.conf:
vfs.read_max=128  # default 64

9. compile mutt with kyotocabinet which uses (I think) memory mapping for cache
lookups things like that. Faster than on-disk.

10. Look up the spec of yr usb3 connected device. Does it have 4k sectors?
If it does, if you're using zfs make sure vfs.zfs.min_auto_ashift=12 in
/etc/sysctl.conf

11. if you do compile stuff it'd be worth using -j3 if you want reasonably 
responsive
interactive use from the pi while it's compiling.

Like I've said, this isn't even guaranteed to work. All I can say is it's
whats working on my rpi4/8GB now and I'm very happy with it.

--
J.


signature.asc
Description: PGP signature

Re: firewall choice

[tech-lists]

On Fri, Nov 27, 2020 at 06:11:43PM -0500, grarpamp wrote:

[...lots...]

OK thanks for that looks like I've got some reading to do
--
J.


signature.asc
Description: PGP signature

Re: rc.d/zpool runs before ada(4) attaches

[tech-lists]

On Tue, Dec 01, 2020 at 08:34:33AM -0700, Ian Lepore wrote:

On Tue, 2020-12-01 at 16:22 +0100, Ronald Klop wrote:


You can define these in /boot/loader.conf:
#kern.cam.boot_delay="1" # Delay (in ms) of root mount for CAM
bus
#kern.cam.scsi_delay="2000" # Delay (in ms) before probing SCSI

Maybe that helps.

Ronald.



Those settings control waiting before mounting root.  Harry's problem
is that root is mounted quickly, before other drives are ready for zfs.

The zpool script waits for 'disks'.  It would be nice if the cam
subsystem had something like a sysctl it set to indicate when initial
probing for disks was done, then there could be an rc.d/camprobe script
with 'PROVIDE: disks' which waits for the probing to complete.

-- Ian


kern.cam.boot_delay should still fix it because what is required is a delay
while the devices (all of the disks, zfs or not) get ready. Because root 
has to happen before disks/zfs. 
--

J.


signature.asc
Description: PGP signature

Re: CURRENT, usr/src on git, howto "mergemaster"?

[tech-lists]

On Mon, Jan 04, 2021 at 08:47:28PM +0100, Michal Meloun wrote:


Moreover mergemaster is still officially documented and recommend as
only right method in FreeBSD handbook. See
https://www.freebsd.org/doc/handbook/makeworld.html.
World is moving, we may have new tools but each deprecation should be,
in this order:
1) well announced
2) adjusted in the handbook
3) implemeted


Really +1 to this, times a thousand. Especially the 2nd point which I think
I'd be right in thinking is the source of truth? It also talks extensively 
about svn and yet 12-stable has been on git for a month nearly, and the svn 
repo has not been updated since. Not even a hint suggesting the new process, 
that the indicated process is depreciated, or a link to the newer 
process/workflow.


--
J.


signature.asc
Description: PGP signature

using git to get a particular version of src

[tech-lists]

Hi,

I have this version installed:

13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020

I'd like to get the sources for this (want to make a no-debug kernel) as I know 
this version works on this hardware. 

But -current has gone to 14 and what was -current is now 13-stable. What git 
incantation is required to get 2ed50808d2b-c254384 sources, given an empty 
/usr/src and git method of ssh://anon...@git.freebsd.org ?


thanks,
--
J.


signature.asc
Description: PGP signature

Re: using git to get a particular version of src

[tech-lists]

On Mon, Jan 25, 2021 at 04:31:13PM +, tech-lists wrote:

Hi,

I have this version installed:

13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020

I'd like to get the sources for this (want to make a no-debug kernel) as I know
this version works on this hardware.

But -current has gone to 14 and what was -current is now 13-stable. What git
incantation is required to get 2ed50808d2b-c254384 sources, given an empty
/usr/src and git method of ssh://anon...@git.freebsd.org ?


OOPS sorry seems this exact same q was asked/answered earlier, pls ignore

thanks
--
J.


signature.asc
Description: PGP signature

Re: Getting /usr/src to match specific git hash?

[tech-lists]

On Sun, Jan 24, 2021 at 01:08:05PM +0900, Yasuhiro Kimura wrote:

From: Steve Kargl 
Subject: Getting /usr/src to match specific git hash?
Date: Sat, 23 Jan 2021 19:58:52 -0800


Suppose one has an empty /usr/src.

Suppose further that one had to re-install a 32-bit
i386-*-freebsd with the 24 Dec 2020 image available
from freebsd.org.

uname -a for the booted kernel shows

% uname -a
FreeBSD mobile 13.0-CURRENT FreeBSD 13.0-CURRENT #0 \
3cc0c0d66a0-c255241(main)-dirty: Thu Dec 24 05:43:23 UTC 2020 \
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/i386.i386/sys/GENERIC i386

How does one use git to pull the exact sources that match
this specifc kernel?


cd /usr
git clone https://git.freebsd.org/src.git
cd src
git checkout 3cc0c0d66a0


I have the exact same issue. The installation I have is:

13.0-CURRENT #0 2ed50808d2b-c254384(main): Thu Nov 12 10:03:35 UTC 2020

The method described doesn't work for me for some reason:

[...]
root@rpi4:/usr # git clone https://git.freebsd.org/src.git
Cloning into 'src'...

remote: Enumerating objects: 377505, done.
remote: Counting objects: 100% (377505/377505), done.
remote: Compressing objects: 100% (26583/26583), done.
remote: Total 3831969 (delta 371848), reused 350922 (delta 350922), pack-reused 
3454464
Receiving objects: 100% (3831969/3831969), 1.14 GiB | 6.28 MiB/s, done.
Resolving deltas: 100% (3034679/3034679), done.
Updating files: 100% (85162/85162), done.
root@rpi4:/usr # cd src
root@rpi4:/usr/src # git checkout 2ed50808d2b 
error: pathspec '2ed50808d2b' did not match any file(s) known to git


thanks,
--
J.


signature.asc
Description: PGP signature

trying to make release with git-derived 14-current

[tech-lists]

Hi,

I'm trying to make release with -current on a rpi4b/8GB. Basically, I
have a working rpi4B/8GB with a no-debug kernel running -current.
However, release(7) says a lot about svn and nothing about git.

What's the method with git?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Failure of release build with release.sh on 14-CURRENT amd64

[tech-lists]

Hello,

I also tried to build a release and failed. My context is different to
yours, though. The failure error is different. Just thought I'd mention
it as "make release on -current is broken for me as well". In my
context, it ignores the installed pkg and tries, and fails to get a
-current pkg binary from the repos.

Context is raspberry pi4/8GB
git version is src.git as of 30/01/21 evening UTC

command used was: 
root@generic:/usr/src/release # sh release.sh -c arm64/RPI.conf


error:
--- installdirs-CONFSDIR ---
installing DIRS CONFSDIR
install -N /scratch/usr/src/etc  -d -m 0755 -o root  -g wheel
/scratch/etc/pkg
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
Bootstrapping pkg from
pkg+http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest, please wait...
pkg: Error fetching
http://pkg.FreeBSD.org/FreeBSD:14:aarch64/latest/Latest/pkg.txz: Not
Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports:
'ports-mgmt/pkg'.

root@generic:/usr/src/release # which pkg
/usr/sbin/pkg

--
J.


signature.asc
Description: PGP signature

Re: Failure of release build with release.sh on 14-CURRENT amd64

[tech-lists]

On Mon, Feb 01, 2021 at 09:27:44PM +, Glen Barber wrote:

On Sun, Jan 31, 2021 at 03:30:14PM +, tech-lists wrote:

Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports:
'ports-mgmt/pkg'.

root@generic:/usr/src/release # which pkg
/usr/sbin/pkg



This is because the 14.0-CURRENT packages for arm64 take a significant
amount of more time to build than x86.


Hi,

Is there a way of making it use the pkg which is already installed on the system
running make release?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Failure of release build with release.sh on 14-CURRENT amd64

[tech-lists]

On Mon, Feb 01, 2021 at 05:13:42PM -0800, Rodney W. Grimes wrote:


One could build your own local pkg repository that contained pkg
and what ever other pkg's are needed during a make release and
modify the /etc/pkg/FreeBSD.conf file to point at it as a way
to work around this .


Thanks for the suggestion, might try that. I guess here you're thinking
poudriere?

--
J.


signature.asc
Description: PGP signature

Re: gib/em driver problems?

[tech-lists]

On Wed, Feb 03, 2021 at 06:40:50PM -0800, joe mcguckin wrote:
I went out and purchased a PCIe ethernet card - it uses the em driver. 
The system boots and it is em0.


It works fine in 100Mb mode, but in gigabit mode, it does not pass any 
traffic although ifconfig reports

the card as active and that it has negotiated 1000BTX full duplex.

I have tried plugging both the igb and em cards into 2 different switches 
with the same result.


Hi,

Try manually setting the card's speed to gigabit mode, instead of it
auto-negotiating. Speaking from experience, I have known some cards to
show either packet loss or just not work at all if the speed isn't
nailed up when they are talking to some switches.
--
J.


signature.asc
Description: PGP signature

Re: 13-stable compile error when drm-kmod installed

[tech-lists]

On Wed, Feb 10, 2021 at 11:15:58AM +, M&S - Krasznai András wrote:

2.)several applications (multitail just to mention one of them) 
complain about missing ncurses libraries, e.g. libpanelw.so.5, etc. 
which are not missing from the january-29 snapshot of FreeBSD 
13-stable, that is after installing from the snapshot and installing 
the usual set of applications they do not complain about the missing 
libraries before updating world and the kernel.


Hi,

I caught this too, the ncurses thing. What I'm having to to is to
buildworld/installworld stable/13 and from there, recompile all my ports
while making sure there is nothing defined with ncurses in
/etc/make.conf.
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Thu, Mar 11, 2021 at 03:42:55PM +, Rick Macklem wrote:

I'm going to cheat and top post (the discussion looks
pretty convoluted).

- The kernel must be built with "options KERN_TLS"
- OpenSSL must be built with KTLS enabled
- These two sysctls need to be set to 1
  kern.ipc.tls.enable
  kern.ipc.mb_use_ext_pgs


Hello,

I'd like to try ktls but have found the following:

On AMD64 (stable/13) this option is present in the GENERIC kernel 
of world built about a month ago: stable/13-n244496-618dee60231 
and openssl version is 1.1.1i-freebsd


On ARM64 (stable/13) it's *not* present in a world built earlier 
today from stable/13-n244876-0b45290603b. Here, the openssl version 
is 1.1.1j-freebsd


On another ARM64 (main/14) it *is* present in main-n245445-07564e17620 
built with sources from the 11th March. openssl is 1.1.1j-freebsd here 
as well.


I'd like to have it (ktls) available on the ARM64 
stable/13-n244876-0b45290603b. Is it just a matter of adding the option, 
and then the sysctls become available? Is it "better" with openssl[-devel] 
in ports or openssl in base?


thanks,
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Sun, Mar 14, 2021 at 08:55:18PM +, Rick Macklem wrote:


Alan explains how to set it up, below.
However, I thought I'd note that maybe one person has tested KTLS
on arm64, so you should consider doing this for test purposes only.
If you do do some testing, please post with your results,
success or failure.


will do. The end-point I want is to have the arm64 machine accessible
externally for wireguard-based vpn. 


Doing it this way means that everything linked to OpenSSL will use
it. Probably a better testsituation, but expect at least the apache
server to break. (Most breakage was fixed by a recent patch to the
serf library, but I think the apache server is still broken.


I have latest serf installed with nginx. The machine, a rpi4/8GB, builds
its ports with poudriere. I have WITH_OPENSSL_KTLS= set in /etc/src.conf
and it's building a new world now.


If you want to try NFS-over-TLS, see this:
https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt



Please let us know if you try it, rick


yep, I'll try that too and post results here.

thanks :D
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Sun, Mar 14, 2021 at 11:07:23PM +, tech-lists wrote:

On Sun, Mar 14, 2021 at 08:55:18PM +, Rick Macklem wrote:


Alan explains how to set it up, below.
However, I thought I'd note that maybe one person has tested KTLS
on arm64, so you should consider doing this for test purposes only.
If you do do some testing, please post with your results,
success or failure.


will do. The end-point I want is to have the arm64 machine accessible
externally for wireguard-based vpn.


ok, upgraded to stable/13-n244890-4e535a1ba72 with ktls. now, need to
rebuild the poudriere instance and rebuild all installed ports.

--
J.




--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Sun, Mar 14, 2021 at 08:55:18PM +, Rick Macklem wrote:


Alan explains how to set it up, below.
However, I thought I'd note that maybe one person has tested KTLS
on arm64, so you should consider doing this for test purposes only.
If you do do some testing, please post with your results,
success or failure.


It's present in current kernels for both 13 and 14, amd64 and aarch64.
However, it's not present in 13's openssl.  To use it, you must either
rebuild world with  WITH_OPENSSL_KTLS=YES in /etc/src.conf,



Doing it this way means that everything linked to OpenSSL will use
it. Probably a better testsituation, but expect at least the apache
server to break. (Most breakage was fixed by a recent patch to the
serf library, but I think the apache server is still broken.


OK, it's been built and all ports recompiled and reinstalled. Things 
that use openssl on this machine are mutt (imaps) lynx (https) and 
nginx (https) and py-certbot. They all seem to work. How would I test?


thanks,
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Sun, Mar 14, 2021 at 08:55:18PM +, Rick Macklem wrote:


If you want to try NFS-over-TLS, see this:
https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt

Please let us know if you try it, rick


Hi,

I'm going to try this with 2x rpi4 machines, client on stable/13 and
server on main/14. both have zfs.

--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Tue, Mar 16, 2021 at 11:46:27PM +, Rick Macklem wrote:


Well, if you do "sysctl -a | fgrep kern.ipc.tls.stats" and it is working,
you should see the count for at least one of the "crypts" ticking up.
If they are all zero, it isn't working. That might depend on the apps
or setup and does not necessarily indicate broken.


OK. it's "not working" by those criteria on the stable/13 rpi4. 
This one has mutt (imaps) and lynx (https) installed. mutt appears to
use tlsv1.3 to connect with my email provider. 


Trying the nfs-over-tls should definitely test it. When it works, the
data on the wire after the first couple of Null RPCs is encrypted.
Also, if you start the daemons with "-v", 


This is what i'll try once buildworld etc completes on the main/14 rpi4.
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Wed, Mar 17, 2021 at 08:39:02PM +, Rick Macklem wrote:


Make sure you've done the following:
ktls_ocf - is loaded
these sysctls are set to 1
kern.ipc.tls.enable
kern.ipc.mb_use_ext_pgs


[on stable/13]

% sysctl kern.ipc.tls.enable kern.ipc.mb_use_ext_pgs
kern.ipc.tls.enable: 1
kern.ipc.mb_use_ext_pgs: 1

% kldstat | grep ktls
71 0x0135300025520 ktls_ocf.ko
% 


% sysctl -a | fgrep kern.ipc.tls.stats
kern.ipc.tls.stats.ocf.retries: 0
kern.ipc.tls.stats.ocf.separate_output: 0
kern.ipc.tls.stats.ocf.inplace: 0
kern.ipc.tls.stats.ocf.tls13_gcm_crypts: 0
kern.ipc.tls.stats.ocf.tls12_gcm_crypts: 0
kern.ipc.tls.stats.ocf.tls11_cbc_crypts: 0
kern.ipc.tls.stats.ocf.tls10_cbc_crypts: 0
kern.ipc.tls.stats.switch_failed: 0
kern.ipc.tls.stats.switch_to_sw: 0
kern.ipc.tls.stats.switch_to_ifnet: 0
kern.ipc.tls.stats.failed_crypto: 0
kern.ipc.tls.stats.corrupted_records: 0
kern.ipc.tls.stats.active: 0
kern.ipc.tls.stats.enable_calls: 535
kern.ipc.tls.stats.offload_total: 0
kern.ipc.tls.stats.sw_rx_inqueue: 0
kern.ipc.tls.stats.sw_tx_inqueue: 0
kern.ipc.tls.stats.threads: 4
% 


now to try setting up the nfs thing
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Sun, Mar 14, 2021 at 11:07:23PM +, tech-lists wrote:

On Sun, Mar 14, 2021 at 08:55:18PM +, Rick Macklem wrote:

If you want to try NFS-over-TLS, see this:
https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt



Please let us know if you try it, rick


Hi,

on the (main/14) server, /etc/rpc.tlsservd was not already there; I had
to create it. Is this correct?

version is main-n245454
--
J.


signature.asc
Description: PGP signature

Re: Getting started with ktls

[tech-lists]

On Fri, Mar 19, 2021 at 09:37:30PM +, Rick Macklem wrote:

J. wrote:

on the (main/14) server, /etc/rpc.tlsservd was not already there; I had
to create it. Is this correct?

version is main-n245454

I'll admit I have no idea what n245454 means, but the daemons were
committed to main on Feb 18, 2021.
Installing them from ports should be fine.


Hi Rick,

Does the recent reloval of wireguard have any bearing on ktls? The
reason I ask is that when I happened to see stable/13 updating, it
removed the if_wg stuff and also some nfs stuff.

thanks,
--
J.


signature.asc
Description: PGP signature

Re: systat -swap to display large swap space users

[tech-lists]

Hi,

On Fri, Apr 02, 2021 at 08:12:14PM -0400, Yoshihiro Ota wrote:

Hi,

We do not seem to have a nice way to see current swap space usage per process.
I updated systat to use libprocstat to obtain such infomation and display
along with swap devise/file stats.


Unfotunately your patch gets rejected on recent stable/13 and main/14

--
J.


signature.asc
Description: PGP signature

Re: systat -swap to display large swap space users

[tech-lists]

Hello Hiro,

On Sat, Apr 10, 2021 at 08:36:04AM -0400, Yoshihiro Ota wrote:

Hi,

How about these now?
These include extra improvements to other parts of systat.

These patches create new files.
If you already applies previosly, please check and clean up new files.


Sorry to report that for the 13.0-RELENG patch, it didn't apply cleanly.
I've not tried the others yet.

I saved the attatchment, and then uploaded it to a pristine 13-RELENG
vm. This vm was made from
https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.0/FreeBSD-13.0-RELEASE-amd64-dvd1.iso.xz

Once installed to a 256GB vm, spun the vm up and did the following:

1. install git from packages
2. cd /usr && git clone ssh://anon...@git.freebsd.org/src.git
3. cd src && git checkout releng/13.0

Then copied systat-swap-releng13.0.diff to /usr/src, then ran the
following in /usr/src:

patch < systat-swap-releng13.0.diff

output follows:

[...]

Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/Makefile b/usr.bin/systat/Makefile
|index ca3f7ed72ce..bfbe1336d29 100644
|--- a/usr.bin/systat/Makefile
|+++ b/usr.bin/systat/Makefile
--
Patching file usr.bin/systat/Makefile using Plan A...
Hunk #1 failed at 5.
Hunk #2 failed at 16.
2 out of 2 hunks failed--saving rejects to usr.bin/systat/Makefile.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/devs.c b/usr.bin/systat/devs.c
|index b293796c2c7..87d04f989ea 100644
|--- a/usr.bin/systat/devs.c
|+++ b/usr.bin/systat/devs.c
--
Patching file usr.bin/systat/devs.c using Plan A...
Hunk #1 failed at 426.
Hunk #2 failed at 433.
2 out of 2 hunks failed--saving rejects to usr.bin/systat/devs.c.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/devs.h b/usr.bin/systat/devs.h
|index cbedd844290..79a44a6c3f5 100644
|--- a/usr.bin/systat/devs.h
|+++ b/usr.bin/systat/devs.h
--
Patching file usr.bin/systat/devs.h using Plan A...
Hunk #1 failed at 2.
Hunk #2 failed at 34.
2 out of 2 hunks failed--saving rejects to usr.bin/systat/devs.h.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/extern.h b/usr.bin/systat/extern.h
|index 6e3117bece4..322065f7931 100644
|--- a/usr.bin/systat/extern.h
|+++ b/usr.bin/systat/extern.h
--
Patching file usr.bin/systat/extern.h using Plan A...
Hunk #1 failed at 168.
1 out of 1 hunks failed--saving rejects to usr.bin/systat/extern.h.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/main.c b/usr.bin/systat/main.c
|index b5a19d381ad..b84351379f4 100644
|--- a/usr.bin/systat/main.c
|+++ b/usr.bin/systat/main.c
--
Patching file usr.bin/systat/main.c using Plan A...
Hunk #1 failed at 135.
Hunk #2 failed at 206.
2 out of 2 hunks failed--saving rejects to usr.bin/systat/main.c.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/pigs.c b/usr.bin/systat/pigs.c
|index d9f3f8d4ad1..879f6548d86 100644
|--- a/usr.bin/systat/pigs.c
|+++ b/usr.bin/systat/pigs.c
--
Patching file usr.bin/systat/pigs.c using Plan A...
Hunk #1 failed at 56.
Hunk #2 failed at 90.
Hunk #3 failed at 146.
3 out of 3 hunks failed--saving rejects to usr.bin/systat/pigs.c.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/proc.c b/usr.bin/systat/proc.c
|new file mode 100644
|index 000..0def660d2dc
|--- /dev/null
|+++ b/usr.bin/systat/proc.c
--
(Creating file usr.bin/systat/proc.c...)
Patching file usr.bin/systat/proc.c using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/subs.h b/usr.bin/systat/subs.h
|new file mode 100644
|index 000..e4184be8dae
|--- /dev/null
|+++ b/usr.bin/systat/subs.h
--
(Creating file usr.bin/systat/subs.h...)
Patching file usr.bin/systat/subs.h using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|diff --git a/usr.bin/systat/swap.c b/usr.bin/systat/swap.c
|index fc44db7d7d4..44a321a5705 100644
|--- a/usr.bin/systat/swap.c
|+++ b/usr.bin/systat/swap.c
--
Patching file usr.bin/systat/swap.c using Plan A...
Hunk #1 fail