Re: HEADS-UP: OpenSSL 1.1.1 in 12.0
On Wed, Oct 10, 2018 at 08:35:28PM -0400, Ed Maste wrote: > On Wed, 10 Oct 2018 at 18:11, O. Hartmann wrote: > > > > security/libssh > > This one is open as PR 228895. > I don't need to be personally CC'd on every port that fails to build. I'm keeping an eye on them. I do not need the extra email noise. I'm primarily trying to get us through this hurdle. Your patience is appreciated. Glen signature.asc Description: PGP signature
Re: HEADS-UP: OpenSSL 1.1.1 in 12.0
Here are a few more: devel/gnome-vfs comms/kermit security/php56-openssl net-im/telegram textproc/htmldoc > On Oct 10, 2018, at 5:35 PM, Ed Maste wrote: > > On Wed, 10 Oct 2018 at 18:11, O. Hartmann wrote: >> >> security/libssh > > This one is open as PR 228895. > > If there are other ports that you're trying to build and are failing > with OpenSSL 1.1.1 please check PR 228865 and 231931 to see if it is > already listed as a dependency. > > You can see all of the ports that have been identified so far: > https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=228865_resolved=1 > https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=231931_resolved=1 > > If it's not already listed please submit a new PR for it, making it a > blocker of 228865. If it is already listed feel free to add a comment > to the port's PR (in order to help prioritize ongoing work on the open > reports). > ___ > 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-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: HEADS-UP: OpenSSL 1.1.1 in 12.0
On Wed, 10 Oct 2018 at 18:11, O. Hartmann wrote: > > security/libssh This one is open as PR 228895. If there are other ports that you're trying to build and are failing with OpenSSL 1.1.1 please check PR 228865 and 231931 to see if it is already listed as a dependency. You can see all of the ports that have been identified so far: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=228865_resolved=1 https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=231931_resolved=1 If it's not already listed please submit a new PR for it, making it a blocker of 228865. If it is already listed feel free to add a comment to the port's PR (in order to help prioritize ongoing work on the open reports). ___ 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: HEADS-UP: OpenSSL 1.1.1 in 12.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 9 Oct 2018 23:37:02 -0400 Michael Butler schrieb: > On 10/9/18 11:14 PM, Michael Butler wrote: > > On 10/9/18 5:34 PM, Glen Barber wrote: > >> OpenSSL has been updated to version 1.1.1 as of r339270. > >> > >> It is important to rebuild third-party packages before running: > >> > >> # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > >> > >> Thank you for your patience while this work was in progress, and thank > >> you to all involved for their hard work in getting things ready for this > >> update. > > > > So far, I've found two ports that will no longer build. They are: > > > > net-mgmt/net-snmp > > security/opencryptoki > > > > I simply chose those that were linked to /usr/lib/libssl.so.8 where the > > openssl update creates libssl.so.9. There may be more I haven't found yet, > > add multimedia/ffmpeg to this list .. > > imb > > ___ > 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" security/libssh - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW754oQAKCRDS528fyFhY lGy4AfkBPCItbFuIsX5HZTWLyCSq8L7rU+4cnb77b8iYeKEBT7pThY1jm9F+ZeSz uepHL6iZoRqwdiXReasafUeXgSbRAf9jCRsfjIq5xq8Gxgm8AtFdabhEQ0y3Nb2B zZ349A0UwalA/bL+1SZ3y0RaICnsT4LzngB/Cn3fxCqu0nXDxLKG =0Rcl -END PGP SIGNATURE- ___ 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 12 PowerPC won’t boot at all.
This probably seems to come from the loader geli support. If I rebuild loader with WITHOUT_LOADER_GELI=1 set, everything is fine. Could anyone else who is having trouble try to reproduce that? -Nathan On 10/5/18 1:38 PM, Andreas Tobler wrote: > On 04.10.18 13:34, Alex McKeever wrote: >> Subject says it all, that and it inverts the boot selector when >> selected. Tested it on my eMac G4 1.25 GHz (Retail). Last version of >> FreeBSD that works for me is 11.1, as 11.2 doesn’t boot all the way >> (hangs on cryptosoft0) > > What image did you try? ALPHA8 should boot, but is not stable yet. If > there will be an APLHA9, it should boot and should be stable, at least > it is here. > > Andreas > ___ > 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-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
r339289 buildworld stopped in /usr/src/secure/lib/libcrypto
building shared library libcrypto.so.9 cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -Wl,--version-script=/usr/src/secure/lib/libcrypto/Version.map -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libcrypto.so.9.full -Wl,-soname,libcrypto.so.9 `NM='nm' NMFLAGS='' lorder cpt_err.pico cryptlib.pico ctype.pico cversion.pico ex_data.pico init.pico mem.pico mem_dbg.pico mem_sec.pico o_dir.pico o_fips.pico o_fopen.pico o_init.pico o_str.pico o_time.pico threads_pthread.pico uid.pico x86_64cpuid.pico aes_cfb.pico aes_ecb.pico aes_ige.pico aes_misc.pico aes_ofb.pico aes_wrap.pico aes-x86_64.pico aesni-mb-x86_64.pico aesni-sha1-x86_64.pico aesni-sha256-x86_64.pico aesni-x86_64.pico bsaes-x86_64.pico vpaes-x86_64.pico aria.pico a_bitstr.pico a_d2i_fp.pico a_digest.pico a_dup.pico a_gentm.pico a_i2d_fp.pico a_int.pico a_mbstr.pico a_object.pico a_octet.pico a_print.pico a_sign.pico a_strex.pico a_strnid.pico a_time.pico a_type.pico a_utctm.pico a_utf8.pico a_verify.pico ameth_lib.pico asn1_err.pico asn1_gen.pico asn1_item_list.pico asn1_lib.pico asn1_par.pico asn_mime.pico asn_moid.pico asn_mstbl.pico asn_pack.pico bio_asn1.pico bio_ndef.pico d2i_pr.pico d2i_pu.pico evp_asn1.pico f_int.pico f_string.pico i2d_pr.pico i2d_pu.pico n_pkey.pico nsseq.pico p5_pbe.pico p5_pbev2.pico p5_scrypt.pico p8_pkey.pico t_bitst.pico t_pkey.pico t_spki.pico tasn_dec.pico tasn_enc.pico tasn_fre.pico tasn_new.pico tasn_prn.pico tasn_scn.pico tasn_typ.pico tasn_utl.pico x_algor.pico x_bignum.pico x_info.pico x_int64.pico x_long.pico x_pkey.pico x_sig.pico x_spki.pico x_val.pico async.pico async_err.pico async_posix.pico async_wait.pico bf_cfb64.pico bf_ecb.pico bf_ofb64.pico bf_skey.pico bf_enc.pico b_addr.pico b_dump.pico b_print.pico b_sock.pico b_sock2.pico bf_buff.pico bf_lbuf.pico bf_nbio.pico bf_null.pico bio_cb.pico bio_err.pico bio_lib.pico bio_meth.pico bss_acpt.pico bss_bio.pico bss_conn.pico bss_dgram.pico bss_fd.pico bss_file.pico bss_log.pico bss_mem.pico bss_null.pico bss_sock.pico blake2b.pico blake2s.pico m_blake2b.pico m_blake2s.pico bn_add.pico bn_blind.pico bn_const.pico bn_ctx.pico bn_depr.pico bn_dh.pico bn_div.pico bn_err.pico bn_exp.pico bn_exp2.pico bn_gcd.pico bn_gf2m.pico bn_intern.pico bn_kron.pico bn_lib.pico bn_mod.pico bn_mont.pico bn_mpi.pico bn_mul.pico bn_nist.pico bn_prime.pico bn_print.pico bn_rand.pico bn_recp.pico bn_shift.pico bn_sqr.pico bn_sqrt.pico bn_srp.pico bn_word.pico bn_x931p.pico rsaz-avx2.pico rsaz-x86_64.pico rsaz_exp.pico x86_64-gcc.pico x86_64-gf2m.pico x86_64-mont.pico x86_64-mont5.pico buf_err.pico buffer.pico cmll_cfb.pico cmll_ctr.pico cmll_ecb.pico cmll_ofb.pico cmll-x86_64.pico cmll_misc.pico c_cfb64.pico c_ecb.pico c_enc.pico c_ofb64.pico c_skey.pico chacha-x86_64.pico cm_ameth.pico cm_pmeth.pico cmac.pico cms_asn1.pico cms_att.pico cms_dd.pico cms_enc.pico cms_env.pico cms_err.pico cms_ess.pico cms_io.pico cms_kari.pico cms_lib.pico cms_pwri.pico cms_sd.pico cms_smime.pico c_zlib.pico comp_err.pico comp_lib.pico conf_api.pico conf_def.pico conf_err.pico conf_lib.pico conf_mall.pico conf_mod.pico conf_sap.pico conf_ssl.pico ct_b64.pico ct_err.pico ct_log.pico ct_oct.pico ct_policy.pico ct_prn.pico ct_sct.pico ct_sct_ctx.pico ct_vfy.pico ct_x509v3.pico cbc_cksm.pico cbc_enc.pico cfb64ede.pico cfb64enc.pico cfb_enc.pico ecb3_enc.pico ecb_enc.pico fcrypt.pico ofb64ede.pico ofb64enc.pico ofb_enc.pico pcbc_enc.pico qud_cksm.pico rand_key.pico set_key.pico str2key.pico xcbc_enc.pico des_enc.pico fcrypt_b.pico dh_ameth.pico dh_asn1.pico dh_check.pico dh_depr.pico dh_err.pico dh_gen.pico dh_kdf.pico dh_key.pico dh_lib.pico dh_meth.pico dh_pmeth.pico dh_prn.pico dh_rfc5114.pico dh_rfc7919.pico dsa_ameth.pico dsa_asn1.pico dsa_depr.pico dsa_err.pico dsa_gen.pico dsa_key.pico dsa_lib.pico dsa_meth.pico dsa_ossl.pico dsa_pmeth.pico dsa_prn.pico dsa_sign.pico dsa_vrf.pico dso_dlfcn.pico dso_err.pico dso_lib.pico curve25519.pico curve448.pico curve448_tables.pico ec2_oct.pico ec2_smpl.pico ec_ameth.pico ec_asn1.pico ec_check.pico ec_curve.pico ec_cvt.pico ec_err.pico ec_key.pico ec_kmeth.pico ec_lib.pico ec_mult.pico ec_oct.pico ec_pmeth.pico ec_print.pico ecdh_kdf.pico ecdh_ossl.pico ecdsa_ossl.pico ecdsa_sign.pico ecdsa_vrf.pico eck_prn.pico ecp_mont.pico ecp_nist.pico ecp_oct.pico ecp_smpl.pico ecx_meth.pico eddsa.pico f_generic.pico f_impl.pico scalar.pico ecp_nistz256-x86_64.pico ecp_nistz256.pico x25519-x86_64.pico eng_all.pico eng_cnf.pico eng_ctrl.pico eng_dyn.pico eng_err.pico eng_fat.pico eng_init.pico eng_lib.pico eng_list.pico eng_openssl.pico eng_pkey.pico eng_rdrand.pico eng_table.pico tb_asnmth.pico tb_cipher.pico tb_dh.pico tb_digest.pico tb_dsa.pico tb_eckey.pico tb_pkmeth.pico tb_rand.pico tb_rsa.pico err.pico err_all.pico err_prn.pico bio_b64.pico bio_enc.pico bio_md.pico bio_ok.pico c_allc.pico c_alld.pico cmeth_lib.pico digest.pico e_aes.pico
Re: HEADS-UP: OpenSSL 1.1.1 in 12.0
On Tue, 9 Oct 2018 at 23:15, Michael Butler wrote: > > On 10/9/18 5:34 PM, Glen Barber wrote: > > OpenSSL has been updated to version 1.1.1 as of r339270. > > > > It is important to rebuild third-party packages before running: > > > > # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > > > > Thank you for your patience while this work was in progress, and thank > > you to all involved for their hard work in getting things ready for this > > update. > > So far, I've found two ports that will no longer build. They are: > > net-mgmt/net-snmp > security/opencryptoki You can see the list of ports affected by OpenSSL via PRs 228912, 228865, and 231931. Probably the most convenient view is PR 228865's dependency tree: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=228865_resolved=1 Several of these have patches that could use testing and/or review. ___ 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: HEADS-UP: OpenSSL 1.1.1 in 12.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 9 Oct 2018 23:37:02 -0400 Michael Butler schrieb: > On 10/9/18 11:14 PM, Michael Butler wrote: > > On 10/9/18 5:34 PM, Glen Barber wrote: > >> OpenSSL has been updated to version 1.1.1 as of r339270. > >> > >> It is important to rebuild third-party packages before running: > >> > >> # make -C /usr/src delete-old && make -C /usr/src delete-old-libs > >> > >> Thank you for your patience while this work was in progress, and thank > >> you to all involved for their hard work in getting things ready for this > >> update. > > > > So far, I've found two ports that will no longer build. They are: > > > > net-mgmt/net-snmp > > security/opencryptoki > > > > I simply chose those that were linked to /usr/lib/libssl.so.8 where the > > openssl update creates libssl.so.9. There may be more I haven't found yet, > > add multimedia/ffmpeg to this list .. > > imb > > ___ > 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" dns/samba-nsupdate net/liboauth - -- O. Hartmann Ich widerspreche der Nutzung oder Übermittlung meiner Daten für Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG). -BEGIN PGP SIGNATURE- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCW74s5wAKCRDS528fyFhY lIftAgCn+d7Z0semQwgugPFWnTyuPcIRo0iaPdRQC+DZKndZiPNVEu9hzanPokd5 /kiBWup+5zfTXLHoczuu/1uxCTydAf0Ydn7nXg7imLrBGFHMUoWDe7D3lEipp9oa glsBP11oUpwQFTDu3gQgHPBn/VqZgsV9koBpkDpQ3otOAVTyJ8YM =e+AB -END PGP SIGNATURE- ___ 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?
On 10/10/18 4:24 PM, Slawa Olhovchenkov wrote: > On Wed, Oct 10, 2018 at 02:57:39PM +0100, tech-lists wrote: > >> 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 > > 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. And you need a high quality HDMI 2.0 cable which is not too long. All too often, people can't get 4K on HDMI because of bad cables. -cpghost. > ___ > 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" > smime.p7s Description: S/MIME Cryptographic Signature
Re: is 4k desktop possible on freebsd-12?
On Wed, Oct 10, 2018 at 02:57:39PM +0100, tech-lists wrote: > 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 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. ___ 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?
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?
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?
On Wed, Oct 10, 2018 at 11:18 AM tech-lists wrote: > 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? > > Hi What is the actual problem? Do you get any 4K modes listed when you run 'xrandr' ? 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...). 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-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?
On Wed, Oct 10, 2018 at 11:17:03AM +0100, tech-lists wrote: > > 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? for 4K@60FPS you need DP connection. ___ 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: Trouble building world
make.conf: CPUTYPE?=native KERNCONF=CUSTOM LINKER_FEATURES=Mfilter src.conf: WITHOUT_ATM=1 WITHOUT_AUTHPF=1 WITHOUT_BOOTPARAMD=1 WITHOUT_BOOTPB=1 WITHOUT_BSNMP=1 WITHOUT_HAST=1 WITHOUT_FLOPPY=1 WITHOUT_GAMES=1 WITHOUT_GPIB=1 WITHOUT_IPX=1 WITHOUT_IPFILTER=1 WITHOUT_IPFW=1 WITHOUT_PMC=1 WITHOUT_NCP=1 WITHOUT_NIS=1 WITHOUT_OFED=1 WITHOUT_PPP=1 WITHOUT_RADIUS_SUPPORT=1 WITHOUT_RBOOTD=1 WITHOUT_RCMDS=1 WITHOUT_TALK=1 WITHOUT_TELNET=1 WITHOUT_VI=1 I'm doing the standard "make buildworld" On 10/8/18 1:43 AM, Dimitry Andric wrote: > On 7 Oct 2018, at 23:28, Eric McCorkle wrote: >> >> I'm having some trouble building world from current. The problem looks >> to be various tools' c++ files not including string.h, and therefore >> missing defs. >> >> Is there some critical update step I missed somewhere? > > If the headers are there, usually the problem is that you are overriding > CFLAGS and/or CXXFLAGS in a way so that makefiles can't add or remove > flags. What are the contents of your /etc/make.conf and /etc/src.conf, and > how > are you exactly invoking buildworld? > > -Dimitry > signature.asc Description: OpenPGP digital signature
is 4k desktop possible on freebsd-12?
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"
