Re: Committer needed: www/p5-Net-Curl build breakage
Hi! > I've made a patch to update p5-Net-Curl to fix the failing build. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245322 > > If a committer could please take care of this, it would be much appreciated. Done. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Committer needed: www/p5-Net-Curl build breakage
Hi all, I've made a patch to update p5-Net-Curl to fix the failing build. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245322 If a committer could please take care of this, it would be much appreciated. Thanks, Andrew ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Porting of Smallstep CA
On Tue, Apr 7, 2020 at 2:08 PM Markus Wipp wrote:
>
> Hi all,
>
> I would like to create a port of the CA tool (basically two ports: cli and
> certificates) found on
> https://github.com/smallstep
> https://smallstep.com/
>
> What I tried so far was:
> 1) make it on my machine without the ports infrastructure. This basically
> works fine and without any errors and modifications needed ( I just do a
> gmake bootstrap and then a gmake build )
> 2) tried to create a port using the guide at
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html
> 3) tried Slow porting, but I think I’m not really understanding how and where
> to begin
>
> The main issue is, that I don’t really know what I have to do here, to
> achieve what’s required to correctly build the port.
> It is the very first time I’m trying to create a port.
Hi Markus,
You're on the right track here. The next step is that none of the
stuff where go fetches a remote module can happen. All packages on the
cluster (and the vast majority of end-user-built sets) are built using
poudriere (ports-mgmt/poudriere), which shuts down all external
traffic during builds.
The port needs to specify all dependent modules. Take a look at
another go port, like www/gohugo for an idea of how this works.
net/geoipupdate is similar to what you're doing, where it needs go
modules, but is built with gmake.
You're misusing a couple constructs, but if you copy the framework in
geoipupdate and gohugo you'll resolve most of them (also, define
NO_WRKSUBDIR instead of setting WRKSRC=WRKDIR).
I'm not sure where golint is entering in, but it needs to not be
there. Linting is for upstream developers, and has no purpose for
end-user builds.
Does that help to get you started?
# Adam
>
> My Makefile looks like this:
>
> # $FreeBSD $
>
> PORTNAME= step-cli
> DISTVERSIONPREFIX= v
> DISTVERSION=0.14.0-rc.4
> CATEGORIES= security
> MASTER_SITES=
> https://github.com/smallstep/cli/releases/download/v${DISTVERSION}/
> #PKGNAMESUFFIX= 0.14.0-rc.4
> DISTNAME= ${PORTNAME}_${DISTVERSION}
> MAINTAINER= mw@wipp.bayern
> COMMENT=Smallstep step-ca command line client
> LICENSE=APACHE20
>
> #WRKSRC=${WRKDIR}/step-cli
> WRKSRC= ${WRKDIR}/
> NO_WRKSUBDIR= yes
>
> BUILD_DEPENDS= go>1:lang/go \
> bash>5:shells/bash \
> curl>7:ftp/curl \
> golint:devel/golint
>
> USES= gmake
> MAKE_ARGS= build
>
>
> .include
>
>
> When I try to run make stage on this I get:
> root@pkgbuild:/usr/ports/security/step-cli # make stage
> ===> Building for step-cli-0.14.0.r.4
> gmake[1]: Entering directory '/usr/ports/security/step-cli/work'
> /bin/sh: golangci-lint: not found
> gmake[1]: *** [make/common.mk:101: lint] Error 127
> gmake[1]: *** Waiting for unfinished jobs
> go: finding module for package
> github.com/envoyproxy/protoc-gen-validate/tests/harness/cases/go
> go: finding module for package github.com/shurcooL/github_flavored_markdown
> go: finding module for package github.com/samuel/go-zookeeper/zk
> go: finding module for package github.com/mozilla/scribe
> go: finding module for package golang.org/x/mobile/event/lifecycle
> go: finding module for package github.com/lyft/protoc-gen-star
> go: finding module for package github.com/ethereum/go-ethereum/ethclient
> go: finding module for package github.com/BurntSushi/xgb
> go: finding module for package github.com/ethereum/go-ethereum/rlp
> go: finding module for package github.com/oklog/oklog/pkg/group
> go: finding module for package github.com/influxdata/influxdb1-client/v2
> go: finding module for package gopkg.in/yaml.v1
> go: finding module for package github.com/hashicorp/consul/api
> go: finding module for package github.com/openzipkin/zipkin-go
> go: finding module for package github.com/iancoleman/strcase
> go: finding module for package github.com/BurntSushi/xgb/shm
> go: finding module for package golang.org/x/mobile/event/key
> go: finding module for package golang.org/x/image/math/fixed
> go: finding module for package github.com/gorilla/mux
> go: finding module for package github.com/ianlancetaylor/demangle
> go: finding module for package
> github.com/openzipkin-contrib/zipkin-go-opentracing
> go: finding module for package go.mozilla.org/mozlog
> go: finding module for package github.com/nats-io/nats.go
> go: finding module for package
> github.com/envoyproxy/protoc-gen-validate/tests/harness/go
> go: finding module for package github.com/Sirupsen/logrus
> go: finding module for package bitbucket.org/creachadair/shell
> go: finding module for package
>
Porting of Smallstep CA
Hi all,
I would like to create a port of the CA tool (basically two ports: cli and
certificates) found on
https://github.com/smallstep
https://smallstep.com/
What I tried so far was:
1) make it on my machine without the ports infrastructure. This basically works
fine and without any errors and modifications needed ( I just do a gmake
bootstrap and then a gmake build )
2) tried to create a port using the guide at
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html
3) tried Slow porting, but I think I’m not really understanding how and where
to begin
The main issue is, that I don’t really know what I have to do here, to achieve
what’s required to correctly build the port.
It is the very first time I’m trying to create a port.
My Makefile looks like this:
# $FreeBSD $
PORTNAME= step-cli
DISTVERSIONPREFIX= v
DISTVERSION=0.14.0-rc.4
CATEGORIES= security
MASTER_SITES=
https://github.com/smallstep/cli/releases/download/v${DISTVERSION}/
#PKGNAMESUFFIX= 0.14.0-rc.4
DISTNAME= ${PORTNAME}_${DISTVERSION}
MAINTAINER= mw@wipp.bayern
COMMENT=Smallstep step-ca command line client
LICENSE=APACHE20
#WRKSRC=${WRKDIR}/step-cli
WRKSRC= ${WRKDIR}/
NO_WRKSUBDIR= yes
BUILD_DEPENDS= go>1:lang/go \
bash>5:shells/bash \
curl>7:ftp/curl \
golint:devel/golint
USES= gmake
MAKE_ARGS= build
.include
When I try to run make stage on this I get:
root@pkgbuild:/usr/ports/security/step-cli # make stage
===> Building for step-cli-0.14.0.r.4
gmake[1]: Entering directory '/usr/ports/security/step-cli/work'
/bin/sh: golangci-lint: not found
gmake[1]: *** [make/common.mk:101: lint] Error 127
gmake[1]: *** Waiting for unfinished jobs
go: finding module for package
github.com/envoyproxy/protoc-gen-validate/tests/harness/cases/go
go: finding module for package github.com/shurcooL/github_flavored_markdown
go: finding module for package github.com/samuel/go-zookeeper/zk
go: finding module for package github.com/mozilla/scribe
go: finding module for package golang.org/x/mobile/event/lifecycle
go: finding module for package github.com/lyft/protoc-gen-star
go: finding module for package github.com/ethereum/go-ethereum/ethclient
go: finding module for package github.com/BurntSushi/xgb
go: finding module for package github.com/ethereum/go-ethereum/rlp
go: finding module for package github.com/oklog/oklog/pkg/group
go: finding module for package github.com/influxdata/influxdb1-client/v2
go: finding module for package gopkg.in/yaml.v1
go: finding module for package github.com/hashicorp/consul/api
go: finding module for package github.com/openzipkin/zipkin-go
go: finding module for package github.com/iancoleman/strcase
go: finding module for package github.com/BurntSushi/xgb/shm
go: finding module for package golang.org/x/mobile/event/key
go: finding module for package golang.org/x/image/math/fixed
go: finding module for package github.com/gorilla/mux
go: finding module for package github.com/ianlancetaylor/demangle
go: finding module for package
github.com/openzipkin-contrib/zipkin-go-opentracing
go: finding module for package go.mozilla.org/mozlog
go: finding module for package github.com/nats-io/nats.go
go: finding module for package
github.com/envoyproxy/protoc-gen-validate/tests/harness/go
go: finding module for package github.com/Sirupsen/logrus
go: finding module for package bitbucket.org/creachadair/shell
go: finding module for package
github.com/envoyproxy/protoc-gen-validate/tests/harness/gogo
go: finding module for package sourcegraph.com/sourcegraph/appdash/opentracing
go: finding module for package github.com/remyoudompheng/go-misc/zipfs
go: finding module for package github.com/benlaurie/gds-registers/register
go: finding module for package github.com/BurntSushi/xgb/render
go: finding module for package github.com/shurcooL/gopherjslib
go: finding module for package github.com/openzipkin/zipkin-go/reporter/http
go: finding module for package golang.org/x/mobile/event/paint
go: finding module for package sourcegraph.com/sourcegraph/appdash
go: finding module for package github.com/VividCortex/gohistogram
go: finding module for package github.com/shurcooL/httpfs/vfsutil
go: finding module for package github.com/remyoudompheng/go-misc/weechat
go: finding module for package github.com/miekg/dns
go: finding module for package golang.org/x/mobile/event/mouse
go: finding module for package github.com/lyft/protoc-gen-star/lang/go
go: finding module for package gopkg.in/gcfg.v1
go: finding module for package github.com/jgautheron/goconst
go: finding module for package github.com/otiai10/copy
D22521: new ports: Nvidia headless/hybrid graphics ("Optimus" support) needs commit / review
Hello all, The work by myself and other users of Nvidia-gfx laptops to patch the driver to work for us has been stuck in review for a few months now. The reason for review of what would normally be a routine new-ports bug submission is that changes to x11/nvidia-driver/Makefile are needed to avoid redundancy in the new ports. The maintainer, danfe@ has indicated to me that he needed more time to review, but I've asked for an indication of a timeframe and haven't heard back for over two weeks. I don't know whether maintainer-timeout is relevant here since the changes to x11/nvidia-driver/Makefile are nonfunctional with respect to that port; all that happens is to make it behave correctly as a master for the new slave port. Could a ports committer please look into this? https://reviews.freebsd.org/D22521 Hope danfe@ is well. Thanks. Theron ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Running tests in ports Makefiles?
On Tuesday, April 7, 2020 11:35:38 AM EDT Adam Weinberger wrote: > Optional tests should never be run during a normal build. There is a > "do-test:" target for that purpose. Can you fold the test suite into > that target? Yeah it would be completely possible to use that target for the tests, and thanks for pointing that out as I don't see it listed under Section 5.13.3.12 of the Porter's Handbook [0]. I just didn't know if this was common place to do so with FreeBSD ports. The only thing I have to compare it with is Arch Linux's build system where if a packages PKGBUILD file defines a `check` function [1] then it is called during the build process automatically. I know comparing apples to oranges, hence why I wanted to know what is commonplace/acceptable here. [0]: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ makefile-options.html [1]: https://wiki.archlinux.org/index.php/Creating_packages#check() signature.asc Description: This is a digitally signed message part.
Re: Running tests in ports Makefiles?
On Tue, Apr 7, 2020 at 5:17 AM Adam Jimerson wrote: > > Hello all, > > Hopefully a quick question, is it common place in the ports tree to run tests > for the software being ported in the Makefile or should we just expect/ > encourage upstream to do tests for FreeBSD and leave it at that? > > I ask because one of the ports that I am maintaining is written in Go, uses > the standard test suite that is built into the Go tool chain which means no > additional dependencies to be able to add this only a slightly longer build > time, currently `make package` takes 27.8 seconds on a system with a 16 CPU > cores and 32 Gb ram. Optional tests should never be run during a normal build. There is a "do-test:" target for that purpose. Can you fold the test suite into that target? # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Linux-foldingathome
@lbutlr wrote: On 07 Apr 2020, at 06:36, Yuri Pankov wrote: @lbutlr wrote: # service fahclient start Starting fahclient. 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed to open '/proc/bus/pci/devices': No such file or directory: No such file or directory 13:33:52:ERROR:Exception: Could not read link /proc/self/exe It is looking for /compat/linux/proc -- if it isn't mounted and you aren't on recentish -current 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 Isn’t recent enough, I guess? Correct, I mean the following commit in HEAD (so 13.0-CURRENT only, at the moment): https://svnweb.freebsd.org/base?view=revision=354458 where all required mounts are done by rc script, you should follow the pkg-message for linux_base-c7 port. Thank you, that solved the issue and the client is running now. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Linux-foldingathome
On 07 Apr 2020, at 06:36, Yuri Pankov wrote: > @lbutlr wrote: >> # service fahclient start >> Starting fahclient. >> 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed >> to open '/proc/bus/pci/devices': No such file or directory: No such file or >> directory >> 13:33:52:ERROR:Exception: Could not read link /proc/self/exe > It is looking for /compat/linux/proc -- if it isn't mounted and you aren't on > recentish -current 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64 Isn’t recent enough, I guess? > where all required mounts are done by rc script, you should follow the > pkg-message for linux_base-c7 port. Thank you, that solved the issue and the client is running now. -- Support bacteria - they're the only culture some people have. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Linux-foldingathome
Based on the error message I assume you have to mount procfs (and maybe linprocfs), See the respective man pages. You also have to enable Linux support (sysrc linux_enable=YES ; service linux start). -m > On 7. Apr 2020, at 14:33, @lbutlr wrote: > > Has anyone had any experience with installing the port > biology/linux-foldingathome? > > After installing it and editing the configuration file I try to start it and > get the following: > > # service fahclient start > Starting fahclient. > 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed to > open '/proc/bus/pci/devices': No such file or directory: No such file or > directory > 13:33:52:ERROR:Exception: Could not read link /proc/self/exe > /usr/local/etc/rc.d/fahclient: WARNING: failed to start fahclient > > /proc/ is empty. > > There were no errors when installing the port. > > # kldstat > Id Refs AddressSize Name > 1 57 0x8020 2448d90 kernel > 21 0x82649000 3a99a8 zfs.ko > 32 0x829f3000 a5b8 opensolaris.ko > 41 0x82f11000 4260 ng_ubt.ko > 56 0x82f16000 9e30 netgraph.ko > 62 0x82f2 91b8 ng_hci.ko > 73 0x82f2a000 9c0 ng_bluetooth.ko > 81 0x82f2b000 cad0 ng_l2cap.ko > 91 0x82f380001ba00 ng_btsocket.ko > 101 0x82f54000 21c0 ng_socket.ko > 111 0x82f57000 acf mac_ntpd.ko > 121 0x82f58000 18a0 uhid.ko > 131 0x82f5a000 1aa0 wmt.ko > 141 0x82f5c000 2928 ums.ko > 151 0x82f5f00035b20 linux64.ko > 163 0x82f95000 3178 linux_common.ko > 171 0x82f99000 494c linprocfs.ko > 181 0x82f9e000 1eae linsysfs.ko > > > -- > Traveling through hyperspace ain't like dusting crops, boy. > > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Linux-foldingathome
@lbutlr wrote: Has anyone had any experience with installing the port biology/linux-foldingathome? After installing it and editing the configuration file I try to start it and get the following: # service fahclient start Starting fahclient. 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed to open '/proc/bus/pci/devices': No such file or directory: No such file or directory 13:33:52:ERROR:Exception: Could not read link /proc/self/exe /usr/local/etc/rc.d/fahclient: WARNING: failed to start fahclient /proc/ is empty. There were no errors when installing the port. # kldstat Id Refs AddressSize Name 1 57 0x8020 2448d90 kernel 21 0x82649000 3a99a8 zfs.ko 32 0x829f3000 a5b8 opensolaris.ko 41 0x82f11000 4260 ng_ubt.ko 56 0x82f16000 9e30 netgraph.ko 62 0x82f2 91b8 ng_hci.ko 73 0x82f2a000 9c0 ng_bluetooth.ko 81 0x82f2b000 cad0 ng_l2cap.ko 91 0x82f380001ba00 ng_btsocket.ko 101 0x82f54000 21c0 ng_socket.ko 111 0x82f57000 acf mac_ntpd.ko 121 0x82f58000 18a0 uhid.ko 131 0x82f5a000 1aa0 wmt.ko 141 0x82f5c000 2928 ums.ko 151 0x82f5f00035b20 linux64.ko 163 0x82f95000 3178 linux_common.ko 171 0x82f99000 494c linprocfs.ko 181 0x82f9e000 1eae linsysfs.ko It is looking for /compat/linux/proc -- if it isn't mounted and you aren't on recentish -current where all required mounts are done by rc script, you should follow the pkg-message for linux_base-c7 port. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Linux-foldingathome
Has anyone had any experience with installing the port biology/linux-foldingathome? After installing it and editing the configuration file I try to start it and get the following: # service fahclient start Starting fahclient. 13:33:52:WARNING:Exception: Failed to open '/proc/bus/pci/devices': Failed to open '/proc/bus/pci/devices': No such file or directory: No such file or directory 13:33:52:ERROR:Exception: Could not read link /proc/self/exe /usr/local/etc/rc.d/fahclient: WARNING: failed to start fahclient /proc/ is empty. There were no errors when installing the port. # kldstat Id Refs AddressSize Name 1 57 0x8020 2448d90 kernel 21 0x82649000 3a99a8 zfs.ko 32 0x829f3000 a5b8 opensolaris.ko 41 0x82f11000 4260 ng_ubt.ko 56 0x82f16000 9e30 netgraph.ko 62 0x82f2 91b8 ng_hci.ko 73 0x82f2a000 9c0 ng_bluetooth.ko 81 0x82f2b000 cad0 ng_l2cap.ko 91 0x82f380001ba00 ng_btsocket.ko 101 0x82f54000 21c0 ng_socket.ko 111 0x82f57000 acf mac_ntpd.ko 121 0x82f58000 18a0 uhid.ko 131 0x82f5a000 1aa0 wmt.ko 141 0x82f5c000 2928 ums.ko 151 0x82f5f00035b20 linux64.ko 163 0x82f95000 3178 linux_common.ko 171 0x82f99000 494c linprocfs.ko 181 0x82f9e000 1eae linsysfs.ko -- Traveling through hyperspace ain't like dusting crops, boy. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Running tests in ports Makefiles?
Hello all, Hopefully a quick question, is it common place in the ports tree to run tests for the software being ported in the Makefile or should we just expect/ encourage upstream to do tests for FreeBSD and leave it at that? I ask because one of the ports that I am maintaining is written in Go, uses the standard test suite that is built into the Go tool chain which means no additional dependencies to be able to add this only a slightly longer build time, currently `make package` takes 27.8 seconds on a system with a 16 CPU cores and 32 Gb ram. signature.asc Description: This is a digitally signed message part.
Re: amdgpu panics
On 2020-04-07 12:09, Grzegorz Junka wrote: Is it expected that drm doesn't work on 12.1-RELEASE Yes, for now. You can diff: /usr/src/sys/compat/linuxkpi Between the two to see the differences. --HPS ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 07/04/2020 09:55, Hans Petter Selasky wrote: On 2020-04-07 11:35, Grzegorz Junka wrote: kern.osrelease: 12.1-RELEASE-p3 Hi, This is not 12.1-STABLE! Yes, you can use a 12.1-STABLE kernel with the 12.1-RELEASE. Can you try this: rm -rf /usr/src cd /usr svn checkout https://svn.freebsd.org/base/stable/12 /usr/src cd /usr/src make buildkernel -j6 make installkernel -j6 cd /usr/ports/graphics/drm-fbsd12.0-kmod make all deinstall install clean cd /usr/ports/graphics/gpu-firmware-kmod make all deinstall install clean Then reboot, and try to test the driver again. I'm sorry to say, you _need_ -stable or -current for now, when using the new DRM stuff! That right, it isn't STABLE. I stated that in one of my previous emails: > I might be able to recompile everything with 12.1-STABLE instead of 12.1-RELEASE-p3 but that might take a while so preferably would like to try what's possible before embarking on that adventure. I followed on your previous advice to recompile world and GENERIC kernel instead of using my custom VENUS kernel. Trying with STABLE instead was a separate thread. I understood those are alternatives. Is it expected that drm doesn't work on 12.1-RELEASE even if the kernel and packages are compiled from sources? I remember being able to load amdgpu.ko on 12.0-RELEASE. Why this no longer works? Is 12.1-RELEASE expected to work again at some point, maybe with p4? GrzegorzJ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 2020-04-07 11:35, Grzegorz Junka wrote: kern.osrelease: 12.1-RELEASE-p3 Hi, This is not 12.1-STABLE! Yes, you can use a 12.1-STABLE kernel with the 12.1-RELEASE. Can you try this: rm -rf /usr/src cd /usr svn checkout https://svn.freebsd.org/base/stable/12 /usr/src cd /usr/src make buildkernel -j6 make installkernel -j6 cd /usr/ports/graphics/drm-fbsd12.0-kmod make all deinstall install clean cd /usr/ports/graphics/gpu-firmware-kmod make all deinstall install clean Then reboot, and try to test the driver again. I'm sorry to say, you _need_ -stable or -current for now, when using the new DRM stuff! --HPS ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 07/04/2020 09:29, Hans Petter Selasky wrote: On 2020-04-07 11:19, Grzegorz Junka wrote: 25 3 0x83109000 76570 drm.ko Please also double check, that you've loaded /boot/modules/drm.ko and not /boot/kernel/drm.ko ! ll /boot/modules/ | grep drm -r-xr-xr-x 1 root wheel 757152 Jan 17 15:51 drm.ko* ll /boot/kernel | grep drm -r-xr-xr-x 1 root wheel 165376 Jan 17 15:38 drm.ko* -r-xr-xr-x 1 root wheel 535328 Jan 17 15:38 drm2.ko* Yes, I am loading with kldload /boot/modules/drm.ko /boot/modules/amdgpu.ko If I try kldload /boot/kernel/drm.ko /boot/modules/amdgpu.ko I am getting error: Apr 7 09:36:49 venus kernel: KLD amdgpu.ko: depends on drmn - not available or version mismatch Apr 7 09:36:49 venus kernel: linker_load_file: /boot/modules/amdgpu.ko - unsupported file type and kldload fails ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 07/04/2020 09:21, Hans Petter Selasky wrote: Try: sysctl -a | grep linuxkpi That finally crashed the system. After restart I loaded the modules again and tried without grep. This is how far it goes: root@venus:/home/g # sysctl -a kern.ostype: FreeBSD kern.osrelease: 12.1-RELEASE-p3 kern.osrevision: 199506 kern.version: FreeBSD 12.1-RELEASE-p3 GENERIC kern.maxvnodes: 1164970 kern.maxproc: 70804 kern.maxfiles: 2093468 kern.argmax: 262144 Then nothing. I am loading the modules with: kldload /boot/modules/drm.ko /boot/modules/admgpu.ko as you told me in an earlier email. Without loading the modules this is what I am getting: root@venus:~ # sysctl -a | grep linuxkpi -> nothing root@venus:~ # sysctl -a | grep compat kern.features.compat_freebsd7: 1 kern.features.compat_freebsd6: 1 kern.features.compat_freebsd5: 1 kern.features.compat_freebsd4: 1 kern.features.geom_part_ebr_compat: 1 kern.features.compat_freebsd_32bit: 1 hw.snd.compat_linux_mmap: 0 dev.uart.0.%desc: 16550 or compatible dev.vgapci.0.%desc: VGA-compatible display compat.linux32.maxvmem: 0 compat.linux32.maxssiz: 67108864 compat.linux32.maxdsiz: 536870912 compat.linux.oss_version: 198144 compat.linux.osrelease: 2.6.32 compat.linux.osname: Linux compat.ia32.maxvmem: 0 compat.ia32.maxssiz: 67108864 compat.ia32.maxdsiz: 536870912 root@venus:~ # sysctl -a kern.ostype: FreeBSD kern.osrelease: 12.1-RELEASE-p3 kern.osrevision: 199506 kern.version: FreeBSD 12.1-RELEASE-p3 GENERIC kern.maxvnodes: 1164970 kern.maxproc: 70804 kern.maxfiles: 2093468 kern.argmax: 262144 kern.securelevel: -1 ... (and so on, cutting as it's too long) GrzegorzJ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 2020-04-07 11:19, Grzegorz Junka wrote: 25 3 0x83109000 76570 drm.ko Please also double check, that you've loaded /boot/modules/drm.ko and not /boot/kernel/drm.ko ! ll /boot/modules/ | grep drm -r-xr-xr-x 1 root wheel 757152 Jan 17 15:51 drm.ko* ll /boot/kernel | grep drm -r-xr-xr-x 1 root wheel165376 Jan 17 15:38 drm.ko* -r-xr-xr-x 1 root wheel535328 Jan 17 15:38 drm2.ko* --HPS ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
Try: sysctl -a | grep linuxkpi ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 07/04/2020 09:16, Hans Petter Selasky wrote: On 2020-04-07 11:06, Grzegorz Junka wrote: On 07/04/2020 08:54, Hans Petter Selasky wrote: On 2020-04-07 10:27, Grzegorz Junka wrote: Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with v3.1.27! Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Maybe there is a problem configuring the display ports! Can you dump the output from: sysctl -a compat.linuxkpi Maybe there is some knob you need to flip to turn on the monitor! root@venus:~ # sysctl -a compat.linuxkpi sysctl: unknown oid 'compat.linuxkpi' Is this after loading the amdgpu driver? Can you show: kldstat Yes, I am still in the root ssh session that survived the blanked screen. root@venus:~ # kldstat Id Refs Address Size Name 1 142 0x8020 2448f20 kernel 2 1 0x8264a000 3a99a8 zfs.ko 3 2 0x829f4000 a5b8 opensolaris.ko 4 1 0x82f11000 494c linprocfs.ko 5 3 0x82f16000 3178 linux_common.ko 6 1 0x82f1a000 88d8 tmpfs.ko 7 1 0x82f23000 15d20 if_iwm.ko 8 1 0x82f39000 fb11f iwm3168fw.ko 9 1 0x83035000 2668 intpm.ko 10 1 0x83038000 b50 smbus.ko 11 1 0x83039000 18a0 uhid.ko 12 1 0x8303b000 2928 ums.ko 13 1 0x8303e000 1aa0 wmt.ko 14 1 0x8304 cd70 snd_uaudio.ko 15 1 0x8304d000 4260 ng_ubt.ko 16 6 0x83052000 9e30 netgraph.ko 17 2 0x8305c000 91b8 ng_hci.ko 18 3 0x83066000 9c0 ng_bluetooth.ko 19 1 0x83067000 cad0 ng_l2cap.ko 20 1 0x83074000 1ba00 ng_btsocket.ko 21 1 0x8309 21c0 ng_socket.ko 22 1 0x83093000 3df60 linux.ko 23 1 0x830d1000 35b20 linux64.ko 24 1 0x83107000 1aa0 fdescfs.ko 25 3 0x83109000 76570 drm.ko 26 5 0x8318 10eb0 linuxkpi.ko 27 4 0x83191000 12f30 linuxkpi_gplv2.ko 28 2 0x831a4000 6d0 debugfs.ko 30 1 0x833f6000 f181 ttm.ko 31 1 0x83406000 2c1 amdgpu_vega10_gpu_info_bin.ko 32 1 0x83407000 27d07 amdgpu_vega10_sos_bin.ko 33 1 0x8342f000 1e377 amdgpu_vega10_asd_bin.ko 34 1 0x8344e000 4047f amdgpu_vega10_acg_smc_bin.ko 35 1 0x8348f000 55f7 amdgpu_vega10_pfp_bin.ko 36 1 0x83495000 45f5 amdgpu_vega10_me_bin.ko 37 1 0x8349a000 25f5 amdgpu_vega10_ce_bin.ko 38 1 0x8349d000 4477 amdgpu_vega10_rlc_bin.ko 39 1 0x834a2000 41887 amdgpu_vega10_mec_bin.ko 40 1 0x834e4000 41889 amdgpu_vega10_mec2_bin.ko 41 1 0x83526000 4579 amdgpu_vega10_sdma_bin.ko 42 1 0x8352b000 457b amdgpu_vega10_sdma1_bin.ko 43 1 0x8353 5c337 amdgpu_vega10_uvd_bin.ko 44 1 0x8358d000 2a797 amdgpu_vega10_vce_bin.ko GrzegorzJ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 2020-04-07 11:06, Grzegorz Junka wrote: On 07/04/2020 08:54, Hans Petter Selasky wrote: On 2020-04-07 10:27, Grzegorz Junka wrote: Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with v3.1.27! Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Maybe there is a problem configuring the display ports! Can you dump the output from: sysctl -a compat.linuxkpi Maybe there is some knob you need to flip to turn on the monitor! root@venus:~ # sysctl -a compat.linuxkpi sysctl: unknown oid 'compat.linuxkpi' Is this after loading the amdgpu driver? Can you show: kldstat --HPS ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 07/04/2020 08:54, Hans Petter Selasky wrote: On 2020-04-07 10:27, Grzegorz Junka wrote: Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with v3.1.27! Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Maybe there is a problem configuring the display ports! Can you dump the output from: sysctl -a compat.linuxkpi Maybe there is some knob you need to flip to turn on the monitor! root@venus:~ # sysctl -a compat.linuxkpi sysctl: unknown oid 'compat.linuxkpi' GrzegorzJ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 2020-04-07 10:27, Grzegorz Junka wrote: Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with v3.1.27! Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Maybe there is a problem configuring the display ports! Can you dump the output from: sysctl -a compat.linuxkpi Maybe there is some knob you need to flip to turn on the monitor! --HPS ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Obsolete port
Hello Ports, The devel/pear-channel-phpunit port is obsolete. See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242220 Can somebody have a look at this? Best regards, Marc Veldman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: amdgpu panics
On 06/04/2020 23:49, Hans Petter Selasky wrote: On 2020-04-07 00:07, Grzegorz Junka wrote: Is it possible to at least gather some debug info where this happens? I don't think there is any core dumped if the system doesn't panic? Can you SSH to this machine and get dmesg? I sent the dmesg after booting privately as it was quite long. One interesting thing I just noticed is that the halt is not a complete halt. The system responds to ping and an ssh user session was active, in the sense that I could do ls -l and get a response. But it hung as soon as I tried su. Same with initiating any new ssh session - the system responds with prompt for password but after that nothing happens. This is the content of the messages log starting at the moment when I try to load the modules: Apr 7 07:54:30 venus kernel: [drm] amdgpu kernel modesetting enabled. Apr 7 07:54:30 venus kernel: drmn0: on vgapci0 Apr 7 07:54:30 venus kernel: vgapci0: child drmn0 requested pci_enable_io Apr 7 07:54:30 venus syslogd: last message repeated 1 times Apr 7 07:54:30 venus kernel: [drm] initializing kernel modesetting (VEGA10 0x1002:0x687F 0x1002:0x0B36 0xC0). Apr 7 07:54:30 venus kernel: [drm] register mmio base: 0xFD10 Apr 7 07:54:30 venus kernel: [drm] register mmio size: 524288 Apr 7 07:54:30 venus kernel: [drm] PCI I/O BAR is not found. Apr 7 07:54:30 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_gpu_info.bin Apr 7 07:54:30 venus kernel: [drm] probing gen 2 caps for device 1022:1471 = 700d03/e Apr 7 07:54:30 venus kernel: [drm] probing mlw for device 1002:687f = 400d03 Apr 7 07:54:30 venus kernel: [drm] UVD is enabled in VM mode Apr 7 07:54:30 venus kernel: [drm] UVD ENC is enabled in VM mode Apr 7 07:54:30 venus kernel: [drm] VCE enabled in VM mode Apr 7 07:54:30 venus kernel: ATOM BIOS: 113-D0500500-104 Apr 7 07:54:30 venus kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit Apr 7 07:54:30 venus kernel: drmn0: VRAM: 8176M 0x00F4 - 0x00F5FEFF (8176M used) Apr 7 07:54:30 venus kernel: drmn0: GTT: 256M 0x00F6 - 0x00F60FFF Apr 7 07:54:30 venus kernel: Successfully added WC MTRR for [0xe000-0xefff]: 0; Apr 7 07:54:30 venus kernel: [drm] Detected VRAM RAM=8176M, BAR=256M Apr 7 07:54:30 venus kernel: [drm] RAM width 2048bits HBM Apr 7 07:54:30 venus kernel: [TTM] Zone kernel: Available graphics memory: 33495488 kiB Apr 7 07:54:30 venus kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB Apr 7 07:54:30 venus kernel: [TTM] Initializing pool allocator Apr 7 07:54:30 venus kernel: [drm] amdgpu: 8176M of VRAM memory ready Apr 7 07:54:30 venus kernel: [drm] amdgpu: 8176M of GTT memory ready. Apr 7 07:54:30 venus kernel: i_size_write unimplemented Apr 7 07:54:30 venus kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536 Apr 7 07:54:30 venus kernel: [drm] PCIE GART of 256M enabled (table at 0x00F40080). Apr 7 07:54:31 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sos.bin Apr 7 07:54:32 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_asd.bin Apr 7 07:54:32 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_acg_smc.bin Apr 7 07:54:33 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_pfp.bin Apr 7 07:54:33 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_me.bin Apr 7 07:54:34 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_ce.bin Apr 7 07:54:34 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_rlc.bin Apr 7 07:54:35 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_mec.bin Apr 7 07:54:35 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_mec2.bin Apr 7 07:54:35 venus kernel: i_size_write unimplemented Apr 7 07:54:35 venus syslogd: last message repeated 9 times Apr 7 07:54:36 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sdma.bin Apr 7 07:54:36 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sdma1.bin Apr 7 07:54:36 venus kernel: [drm] use_doorbell being set to: [true] Apr 7 07:54:36 venus kernel: i_size_write unimplemented Apr 7 07:54:36 venus kernel: [drm] use_doorbell being set to: [true] Apr 7 07:54:36 venus kernel: i_size_write unimplemented Apr 7 07:54:37 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_uvd.bin Apr 7 07:54:37 venus kernel: [drm] Found UVD firmware Version: 65.29 Family ID: 17 Apr 7 07:54:37 venus kernel: [drm] PSP loading UVD firmware Apr 7 07:54:37 venus kernel: i_size_write unimplemented Apr 7 07:54:37 venus syslogd: last message repeated 2 times Apr 7 07:54:37 venus kernel: drmn0:
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ emulators/mame | 0.212 | mame0220 +-+ emulators/mess | 0.212 | mame0220 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
