Re: ELF binary type "3" not known.
On Mon, 20 Mar 2017 22:32:53 -0700 (PDT) Don Lewiswrote > On 20 Mar, Chris H wrote: > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I received this message during a big > > build session. I was only able to catch the one from > > x11/nvidia-driver in such a way as to actually get > > the entire message: > > > > Installing nvidia-driver-375.26_1... > > ELF binary type "3" not known. > > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > > > I built && installed emulators/linux_base-c7 *prior* > > to installing this. This is on a: > > > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > > Sun Mar 5 09:01:30 PST 2017 amd64 > > > > Should I anticipate any problems? All and all, it seems > > to work. But are there going to be some subtle repercussions? > > > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > > blob? > > You should have these kernel modules loaded: > > %kldstat | grep linux > 51 0x82643000 ac488linux.ko > 64 0x826f e5d0 linux_common.ko > 71 0x826ff000 99bb8linux64.ko > > They will get loaded on boot if you have this in /boot/loader.conf: > > linux_load="YES" > linux64_load="YES" Thanks for the reply, Don. this is what I have: # kldstat Id Refs AddressSize Name 1 20 0x8020 13c1810 kernel 23 0x815c3000 ac568linux.ko 33 0x8167 e000 linux_common.ko 41 0x8167e000 115128 nvidia-modeset.ko 52 0x81794000 ff44b8 nvidia.ko 61 0x82d11000 a954 linprocfs.ko Which seems to be missing linux64.ko Looks like I'll need to add it to loader.conf(5) and seems to me to explain the error message. Should I rebuild/install the nvidia-driver? Thanks again, Don! --Chris ___ 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: ELF binary type "3" not known.
On 20 Mar, Chris H wrote: > I'm not sure which of the two lists I'm directing > this to is the best/correct one. So I picked both. > > To the point; I received this message during a big > build session. I was only able to catch the one from > x11/nvidia-driver in such a way as to actually get > the entire message: > > Installing nvidia-driver-375.26_1... > ELF binary type "3" not known. > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > I built && installed emulators/linux_base-c7 *prior* > to installing this. This is on a: > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > Sun Mar 5 09:01:30 PST 2017 amd64 > > Should I anticipate any problems? All and all, it seems > to work. But are there going to be some subtle repercussions? > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > blob? You should have these kernel modules loaded: %kldstat | grep linux 51 0x82643000 ac488linux.ko 64 0x826f e5d0 linux_common.ko 71 0x826ff000 99bb8linux64.ko They will get loaded on boot if you have this in /boot/loader.conf: linux_load="YES" linux64_load="YES" ___ 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: ELF binary type "3" not known.
On Tue, 21 Mar 2017 13:14:56 +0800 Kevin Lowrote > On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: > > > > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > > > > > I'm not sure which of the two lists I'm directing > > > this to is the best/correct one. So I picked both. > > > > > > To the point; I received this message during a big > > > build session. I was only able to catch the one from > > > x11/nvidia-driver in such a way as to actually get > > > the entire message: > > > > > > Installing nvidia-driver-375.26_1... > > > ELF binary type "3" not known. > > > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > > > > > I built && installed emulators/linux_base-c7 *prior* > > > to installing this. This is on a: > > > > > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > > > Sun Mar 5 09:01:30 PST 2017 amd64 > > Sorry. Forgot to add the ports revision. > > > > revision 435383 > > Did you do kldload linux64 ? Thanks for the reply, Kevin. Yes. Both before building/installing nvidia-driver, and via loader.conf(5): linux_load="YES" nvidia-modeset_load="YES" Thanks again! --Chris > > > > > > > Should I anticipate any problems? All and all, it seems > > > to work. But are there going to be some subtle repercussions? > > > > > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > > > blob? > > > > > > Thanks. > > > > > > --Chris > > Kevin > ___ > 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: ELF binary type "3" not known.
On Mon, Mar 20, 2017 at 09:11:44PM -0700, Chris H wrote: > > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H"wrote > > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I received this message during a big > > build session. I was only able to catch the one from > > x11/nvidia-driver in such a way as to actually get > > the entire message: > > > > Installing nvidia-driver-375.26_1... > > ELF binary type "3" not known. > > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > > > I built && installed emulators/linux_base-c7 *prior* > > to installing this. This is on a: > > > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > > Sun Mar 5 09:01:30 PST 2017 amd64 > Sorry. Forgot to add the ports revision. > > revision 435383 Did you do kldload linux64 ? > > > > Should I anticipate any problems? All and all, it seems > > to work. But are there going to be some subtle repercussions? > > > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > > blob? > > > > Thanks. > > > > --Chris Kevin ___ 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: ELF binary type "3" not known.
On Mon, 20 Mar 2017 21:11:44 -0700 "Chris H"wrote: > On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H" wrote > > > I'm not sure which of the two lists I'm directing > > this to is the best/correct one. So I picked both. > > > > To the point; I received this message during a big > > build session. I was only able to catch the one from > > x11/nvidia-driver in such a way as to actually get > > the entire message: > > > > Installing nvidia-driver-375.26_1... > > ELF binary type "3" not known. > > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > > > I built && installed emulators/linux_base-c7 *prior* > > to installing this. This is on a: > > > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > > Sun Mar 5 09:01:30 PST 2017 amd64 > Sorry. Forgot to add the ports revision. > > revision 435383 > > > > > Should I anticipate any problems? All and all, it seems > > to work. But are there going to be some subtle repercussions? > > > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > > blob? > > > > Thanks. > > > > --Chris [...] I see this in poudriere builds, too. I haven't seen with which builds this occurs, but it occurs quite often. oh ___ 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: ELF binary type "3" not known.
On Mon, 20 Mar 2017 20:56:05 -0700 "Chris H"wrote > I'm not sure which of the two lists I'm directing > this to is the best/correct one. So I picked both. > > To the point; I received this message during a big > build session. I was only able to catch the one from > x11/nvidia-driver in such a way as to actually get > the entire message: > > Installing nvidia-driver-375.26_1... > ELF binary type "3" not known. > /bin/sh: /compat/linux/sbin/ldconfig: Exec format error > > I built && installed emulators/linux_base-c7 *prior* > to installing this. This is on a: > > FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: > Sun Mar 5 09:01:30 PST 2017 amd64 Sorry. Forgot to add the ports revision. revision 435383 > > Should I anticipate any problems? All and all, it seems > to work. But are there going to be some subtle repercussions? > > Is this a 32bit-v-64bit problem with linux_base || the nvidia > blob? > > Thanks. > > --Chris > > > ___ > 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"
ELF binary type "3" not known.
I'm not sure which of the two lists I'm directing this to is the best/correct one. So I picked both. To the point; I received this message during a big build session. I was only able to catch the one from x11/nvidia-driver in such a way as to actually get the entire message: Installing nvidia-driver-375.26_1... ELF binary type "3" not known. /bin/sh: /compat/linux/sbin/ldconfig: Exec format error I built && installed emulators/linux_base-c7 *prior* to installing this. This is on a: FreeBSD 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r314700: Sun Mar 5 09:01:30 PST 2017 amd64 Should I anticipate any problems? All and all, it seems to work. But are there going to be some subtle repercussions? Is this a 32bit-v-64bit problem with linux_base || the nvidia blob? Thanks. --Chris ___ 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: net/rubygem-signet causing poudriere to be unhappy
> On 20 Mar, 2017, at 11:53, Shawn Webbwrote: > > Hey All, > > It looks like the new net/rubygem-signet port is causing issues with > poudriere: > > Error: Duplicated origin for rubygem-signet-0.7.3: > security/rubygem-signet AND net/rubygem-signet. Rerun with -vv to see > which ports are depending on these. Yes, it is a duplicate. Torsten, please back that commit out. # 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"
net/rubygem-signet causing poudriere to be unhappy
Hey All, It looks like the new net/rubygem-signet port is causing issues with poudriere: Error: Duplicated origin for rubygem-signet-0.7.3: security/rubygem-signet AND net/rubygem-signet. Rerun with -vv to see which ports are depending on these. Thanks, -- Shawn Webb Cofounder and Security Engineer HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature