From owner-freebsd-x11@freebsd.org Sat Oct 19 15:21:15 2019 Return-Path: Delivered-To: freebsd-x11@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E673C167710 for ; Sat, 19 Oct 2019 15:21:15 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: from mail-wr1-x443.google.com (mail-wr1-x443.google.com [IPv6:2a00:1450:4864:20::443]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46wRSW1fGYz4Lj4 for ; Sat, 19 Oct 2019 15:21:15 +0000 (UTC) (envelope-from mms.vanbreukelingen@gmail.com) Received: by mail-wr1-x443.google.com with SMTP id t16so4076762wrr.1 for ; Sat, 19 Oct 2019 08:21:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:autocrypt:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=GNfwIISVIJxCKs+7vVpsJzdH2mQfRj+lHzZlHDxU5jQ=; b=pqZXk3d1MC1qePKozu2izitl/B42WKtJbI2SM0Q+juTx1+CCyjN36lNH8InZTmlS7E mNErwpZ9+C9Wg8vw6+daBeW88sxLksLL3IrLit64XoFKqdaIckVc3T99pntBOHFNeYEJ vmH1r28mqfcrXcwdC5GMOgk5yR3AtdJUIqu2HadzoT5BI5+/YwzWdoWLKSVcyE15/3WA krfiio2qOO/eV5OPAu1qWvF5uoLRlSN+M9Rav1Ws91qMtF92G2XSYnfQxyoaAUgpxGbe zKJrs63KCfOhinfxEBoMmhk84jukhlWrS68iiEGVHIfQrNLF+8VMEb/RxCyVchufAFfS 6BWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:autocrypt:message-id :date:user-agent:mime-version:in-reply-to:content-language; bh=GNfwIISVIJxCKs+7vVpsJzdH2mQfRj+lHzZlHDxU5jQ=; b=GpIeIFuaSnVY9308dxbEKhwtO2Odv1UGtqZn3DmED/9IGsHR2RhNaiE4EfCtGnRK49 lB7c+RYLBchJxtTvGz5LXJTdFCIjbreQBe9pzuIamcGjOAPYzmZtDYIYKT+MlE/44hun WsXSzcMKA422v5UEkwWQVkAiZIJn0aeDEqN2MNUUjerhe119i6C+vueKCqMwpAwkqNTr Xay57o9JUat1UO7u8Gr9RzgWIoJk/lpKVeU7tVcrDZJahF7u08lt+TIVKdxbPKG/6Ho7 N51ohFHtr+5iyD0hb+0KvY5KY30RS9QKUgJrNSMabfcp2DqptowmTjBn8kcxlCw5QJyj uSEg== X-Gm-Message-State: APjAAAVIhIu9aDI7Fqia6PHEV93OHG96B+pI/r2nPsBvs3oOGjP5yOpT 5T+aQ7bOfOsR6+NptyanAAI= X-Google-Smtp-Source: APXvYqx2Zhk7a71olOXyeCEr6qwsGm5biSJbmDs1bhXXY+3JtWSBWI/xIIi5tzVEGyOBTTWk1ruSHA== X-Received: by 2002:a5d:5407:: with SMTP id g7mr11715665wrv.242.1571498472838; Sat, 19 Oct 2019 08:21:12 -0700 (PDT) Received: from [10.211.1.165] (softbank126027043233.bbtec.net. [126.27.43.233]) by smtp.gmail.com with ESMTPSA id t6sm12707717wmf.8.2019.10.19.08.21.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 19 Oct 2019 08:21:12 -0700 (PDT) Subject: Re: freebsd-x11 Digest, Vol 776, Issue 5 To: freebsd-x11@freebsd.org, gljennjohn@gmail.com, pete@nomadlogic.org References: From: Miranda van den Breukelingen Autocrypt: addr=mms.vanbreukelingen@gmail.com; keydata= mQENBF15YdABCACeVSct9hO3acIXXrq5oBNoJS97wodji7Fxsiktq5Kv9fYjMMmziVwrQfnc hVx2CFjdiSy+qcS5Z9C06epa/V+Biheqk9o2s8czbWvQ3yi5nUEt7vDfvQoQi3wx3sXZc6n2 PggQ3vttlmHD5C4tHRdZ8xtgOmptlBPcSc6FQz+8X/ZqSj+M693hh2+1x4tcgzC7+vRfUYQ1 Sb67gnCI0bRfTiZ64b+hc6h5ckfdGbpsAtqd7ONE+229mz7dKuxW80lkgEy8AIq6oxC8aUtr DkYfX22Y1sXFUe3zeK6rSZ3zaMBOFpCBgVGIVDlmW0I+EfDOuvvteYNSNLYQM0FpdQdZABEB AAG0PE1pcmFuZGEgdmFuIGRlbiBCcmV1a2VsaW5nZW4gPG1tcy52YW5icmV1a2VsaW5nZW5A Z21haWwuY29tPokBTgQTAQgAOBYhBMU4R56TpaNzhPLJLUOjIjfzR+HfBQJdeWHQAhsDBQsJ CAcCBhUKCQgLAgQWAgMBAh4BAheAAAoJEEOjIjfzR+Hf+8UIAI3sAA77kdBmc3R8xGGBAT8o Zq7sYU5Q3g/2fTUwHdM9zFT9dix+Mr5fAw1WrmCcLg3c51hX4kn8BWWfgqdvmsalFbFPOhcf C+kZlYTKi2vjpdLsYM7tRIpuYbmGg6R8qJdCuL5T+XsjhlKDG43MtATqe0imIsQPaO7Y/nut rDSqv0pKGmrbtm05BrYrBz9p7oyI+ZVqcp4Tt0bKkuszWLJCoG1iKkXqzABPVTxIrDJBUhax ldMQtvpuHhCBwifeS88tBoPb9/vWlTtgKfLEiHEPWyvSChLase+KazkrVGOzXsGyBqkqT4MQ VfzikUg6+asUko1D7/rPkgyWXdhzdNm5AQ0EXXlh0AEIAM6M06GDtFVkLdeCDuG4bvynwpyM jhYf5uilC/y/l9rDBcAnRHzHS0DUg5ylG4lO+OjPlzyg6QBfboae82Nl1RBHjFYHBYSyuwVf eZt471qoICEPJ1elkWsmZsN6Lr+1oOjGa0kEAUktwSeONcPynhQpc+6tlzNFNeJAnED8W6LF Ih7Bp7l6fi0FOiiVAF14nLAhXfox4LvIuXGgOhWJyEoa7+NVunADI0JKb3ecCjJP/1V7Lj58 qIviP0cLCe0rwMbG3L3X6h7/X7eN2O8kVztgFfd1x+MzPmP+Eabg2EQejfetvu0rnZnpDpL7 HT1433V0vNJ8YQidDc15IZBTTKsAEQEAAYkBNgQYAQgAIBYhBMU4R56TpaNzhPLJLUOjIjfz R+HfBQJdeWHQAhsMAAoJEEOjIjfzR+HfK0sIAI4FY1f2eh7ZlJMyZ5e8P/XPjJ+ROlw8tnpS PhL8me4Vw44voiNc92pla9Q0bsJCQJlPzajvFC8hLGBbbLq3n+VEDWygBmHFCRAjxOuyoRz7 txoRlc84q1kh4sbR647c/m8Qss5X+hmrkGWiy0b5CnbE41zqY/Yyha0KYhumR/LvhQiERKEV zAl7kSh51DWiGdY6zYiByG49v/bZ3M4APyNN4lGw3jvlh0H2v+RwVlHy+cG7BooEfPlhFhGa ECLrISAYg10xRmplT1Vp4X4Wuj3vvJKHqi/H6J/jOZQVzP/Gs0kWLqBLdhExace6sJtGOU4P zmQL5smZ9pAKnApwEI0= Message-ID: Date: Sat, 19 Oct 2019 17:20:58 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Rspamd-Queue-Id: 46wRSW1fGYz4Lj4 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=pqZXk3d1; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mmsvanbreukelingen@gmail.com designates 2a00:1450:4864:20::443 as permitted sender) smtp.mailfrom=mmsvanbreukelingen@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (2.59), ipnet: 2a00:1450::/32(-2.84), asn: 15169(-2.09), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-x11@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2019 15:21:16 -0000 Today's Topics: > 1. Problems with AMDGPU and two grafic cards > (Miranda van den Breukelingen) > 2. Re: Problems with AMDGPU and two grafic cards (Gary Jennejohn) > 9. Re: Problems with AMDGPU and two grafic cards > (Miranda van den Breukelingen) > > > > On 10/18/19 2:55 AM, Miranda van den Breukelingen wrote: > >> Oct 18 05:48:02 freebsd13 kernel: drmn0: failed to link firmware kerne= l >> module with mapped name: radeon_si58_mc_bin >> Oct 18 05:48:02 freebsd13 kernel: radeon/si58_mc.bin: could not load >> firmware image, error 2 >> Oct 18 05:48:02 freebsd13 syslogd: last message repeated 1 times >> Oct 18 05:48:02 freebsd13 kernel: drmn0: failed to load firmware with >> name: radeon/si58_mc.bin >> Oct 18 05:48:02 freebsd13 kernel: drmn0: si_mc: Failed to load firmwar= e >> "radeon/si58_mc.bin" >> Oct 18 05:48:02 freebsd13 kernel: drmn0: Failed to load mc firmware! >> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_init] sw_init = of >> IP block failed -2 >> Oct 18 05:48:02 freebsd13 kernel: drmn0: amdgpu_device_ip_init failed >> Oct 18 05:48:02 freebsd13 kernel: drmn0: Fatal error during GPU init >> Oct 18 05:48:02 freebsd13 kernel: [drm] amdgpu: finishing device. Pete Wright wrote: > so this is odd, it looks like it can't load the appropriate firmware > for your graphics card.=C2=A0 on my system with is using the > drm-current-kmod and gpu-firmware-kdmod packages the following > firmware module is available "amdgpu_si58_mc_bin.ko", but i do not see > a corresponding radeon kernel mod though. > > are you using the drm-current-kmod port/pkg or the drm-legacy-kmod on > your system?=C2=A0 also, sorry if i missed this earlier in the thread -= > which graphics adapter is this? > > -p=20 Hi Pete,=C2=A0 did BIOS update,=C2=A0 has been critical.=C2=A0 in the meantime with lot = o'luck I got the scfb-driver to work but only in 1024x76 (but the bios-logo starting in 1920x1280) and with 'dbus-launch kstart5 plasmashell' I have a root-login to plasmashell.=C2=A0 I guess I can add further video-modes to the driver in xorg.conf or set the boot kernel option for 1920x1280 but now, after two days with just 3 hours of sleep, I'm too tired and grateful enough it did graphics at all.= =C2=A0 The CD-medium has been from february and didn't do 'mode 5' on loaders prompt,=C2=A0 the one I have now is setting up /usr/src with 1920x1080 (I= just thought on 1280x1024, that's a resolution where you really need an expensive screen.=C2=A0 It's a ASUS r7240-o4gd5-L (GB, DVI, HDMI, Active, LP) and the Ryzen 7 has 2700MhZ. X.=C2=A0 Ok, so I think for that graphics adapter you should ensure you are using the "radeonkms" kernel module, can you confirm you have this set in your rc.conf? kld_list=3D"radeonkms" If you have tried booting using that kernel module can you share the output of "dmesg | grep drm" assuming that it is different than the previous dmesg you posted in this thread?=C2=A0 if it is the same, then I= 'm not sure why the firmware is failing to load and will have to defer to others on the list. cheers, -p now I'm having a functional new system from scratch working except the grafic; it's the latest builtworld and kernel reversion on a GENRIC CURRENT with drm-kmod-devel, built llvm-devel and with mode=3D3 on the loader prompt I can reach 1920x1080 text mode. Here are the logs: https://pastebin.com/sFxdnt9v The main problems are a) still both GPUs are been recognized (not adjustable in UEFI BIOS and I can't take a laser sword cutting out the part of the motherboard, where GPU is situated, can I? and b) (II) AMDGPU(0:) [KMS] drm report modesetting isn't supported. when starting the server. I'm simply on end with nerves; cursing the whole day; sleeping badly. So tell me now what to do? Miranda > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 17 Oct 2019 16:36:48 +0200 > From: Miranda van den Breukelingen > To: freebsd-x11@freebsd.org > Subject: Problems with AMDGPU and two grafic cards > Message-ID: <76704353-023d-347d-5704-335582473082@gmail.com> > Content-Type: text/plain; charset=3Dutf-8 > > I don't know exactly what's going wrong with my graphics: from the > beginning: there is an onboard graphic card, that can't be explicitly > enabled/disabled in UEFI BIOS as up to further development on Ryzen 7s > APUs, where GPU isn't on processor on my ASUS B350 Prime as far as > manuals in the web tell me. > > BSD recognizes both cards and tries to initialize both of them what's > ending up with 'mixing up new and old fw'. I tried with Trident as > grafical installer works and the drm-driver does it's best but finally > ending up with something like no modesetting-support; can paste content= > of dmesg if necessary. Deluded a bit and the scfb driver doesn't do at > all. I # the card 1 with identifier..., then the same with card 0; > results still: no screens found. > > I'm using CURRENT generic. Any suggestions? > > MvB > > > On 2019-10-17 14:00, freebsd-x11-request@freebsd.org wrote: >> Send freebsd-x11 mailing list submissions to >> ?? ?freebsd-x11@freebsd.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> ?? ?https://lists.freebsd.org/mailman/listinfo/freebsd-x11 >> or, via email, send a message with subject or body 'help' to >> ?? ?freebsd-x11-request@freebsd.org >> >> You can reach the person managing the list at >> ?? ?freebsd-x11-owner@freebsd.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of freebsd-x11 digest..." >> >> >> Today's Topics: >> >> ??? 1. Re: wacom on X1 Yoga 3rd generation not detected (Mathias Picke= r) >> ??? 2. Re: wacom on X1 Yoga 3rd generation not detected (Jan Beich) >> ??? 3. Re: wacom on X1 Yoga 3rd generation not detected (Jan Beich) >> ??? 4. FreeBSD ports you maintain which are out of date >> ?????? (portscout@FreeBSD.org) >> ??? 5. Xwayland broken after update (raichoo) >> ??? 6. Re: Xwayland broken after update (raichoo) >> >> >> ----------------------------------------------------------------------= >> >> Message: 1 >> Date: Wed, 16 Oct 2019 18:00:18 +0200 >> From: Mathias Picker >> To: Jan Beich >> Cc: "freebsd-x11\@freebsd.org" >> Subject: Re: wacom on X1 Yoga 3rd generation not detected >> Message-ID: <86sgnsznn1.fsf@virtual-earth.de> >> Content-Type: text/plain; charset=3Dutf-8; format=3Dflowed >> >> >> Jan Beich writes: >> >>> Mathias Picker writes: >>> >>>> Hi all, >>>> >>>> webcamd says that a wacom stylus should be automatically >>>> detected by >>>> devd. >>>> This does not work on my 3rd gen X1 Yoga on 12-stable >>>> >>>> I?ve installed >>>> xf86-input-evdev-2.10.6_4 >>>> xf86-input-wacom-0.37.0 >>>> webcamd-5.3.7.1 >>> devd-based hotplug is the least stable. While bug 196678 may >>> help better >>> switch to xf86-input-libinput + UDEV (bug >>> 222609). xf86-input-wacom can >>> optionally be deinstalled as libinput uses libwacom but on my >>> Bamboo P&T >>> doing so breaks touchpad. xf86-input-evdev, xf86-input-keyboard, >>> xf86-input-mouse are redundant if xf86-input-libinput is used. >> Thanks, >> >> it?s now working with the libinput patch! This could really be in >> the port, I wonder why it isn?t. >> >> I still need to reconfigure the keyboard (win-key seems different, >> my exwm-setup doesn?t quite work) but that should be simple, I?m >> just out of time for now. >> >> Cheers, Mathias >> >> > > > > ------------------------------ > > Message: 2 > Date: Thu, 17 Oct 2019 17:32:04 +0200 > From: Gary Jennejohn > To: Miranda van den Breukelingen > Cc: freebsd-x11@freebsd.org > Subject: Re: Problems with AMDGPU and two grafic cards > Message-ID: <20191017173204.3a14266d@ernst.home> > Content-Type: text/plain; charset=3DUS-ASCII > > On Thu, 17 Oct 2019 16:36:48 +0200 > Miranda van den Breukelingen wrote: > >> I don't know exactly what's going wrong with my graphics: from the >> beginning: there is an onboard graphic card, that can't be explicitly >> enabled/disabled in UEFI BIOS as up to further development on Ryzen 7s= >> APUs, where GPU isn't on processor on my ASUS B350 Prime as far as >> manuals in the web tell me. >> >> BSD recognizes both cards and tries to initialize both of them what's >> ending up with 'mixing up new and old fw'. I tried with Trident as >> grafical installer works and the drm-driver does it's best but finally= >> ending up with something like no modesetting-support; can paste conten= t >> of dmesg if necessary. Deluded a bit and the scfb driver doesn't do at= >> all. I # the card 1 with identifier..., then the same with card 0; >> results still: no screens found. >> >> I'm using CURRENT generic. Any suggestions? >> > This ASUS main board does support Ryzen CPUs with integrated > graphics if the BIOS is recent enough. > > That's why it has HDMI/DVI/VGA connectors on the back. > > Does your CPU have G or GE as part of its name? Then it has > integrated graphics and you should NOT be using a separate > graphics card. > > I have one of these boards with a Ryzen 5 WITHOUT integrated > graphics so I do use a (NVIDIA) graphics card. >