freebsd-x11 Digest, Vol 776, Issue 5

Sat Oct 19 15:21:16 UTC 2019

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 kernel
>> 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 firmware
>> "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 <gmc_v6_0> 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.  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?  also, sorry if i missed this earlier in the thread -
> which graphics adapter is this?
>
> -p 
Hi Pete, 

did BIOS update,  has been critical.  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. 

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. 

The CD-medium has been from february and didn't do 'mode 5' on loaders
prompt,  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. 

It's a ASUS r7240-o4gd5-L (GB, DVI, HDMI, Active, LP) and the Ryzen 7
has 2700MhZ. X. 

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="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?  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=3 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 <mms.vanbreukelingen at gmail.com>
> To: freebsd-x11 at freebsd.org
> Subject: Problems with AMDGPU and two grafic cards
> Message-ID: <76704353-023d-347d-5704-335582473082 at gmail.com>
> Content-Type: text/plain; charset=utf-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 at freebsd.org wrote:
>> Send freebsd-x11 mailing list submissions to
>> ?? ?freebsd-x11 at 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 at freebsd.org
>>
>> You can reach the person managing the list at
>> ?? ?freebsd-x11-owner at 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 Picker)
>> ??? 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 at 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 <Mathias.Picker at virtual-earth.de>
>> To: Jan Beich <jbeich at FreeBSD.org>
>> Cc: "freebsd-x11\@freebsd.org" <x11 at freebsd.org>
>> Subject: Re: wacom on X1 Yoga 3rd generation not detected
>> Message-ID: <86sgnsznn1.fsf at virtual-earth.de>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>>
>> Jan Beich writes:
>>
>>> Mathias Picker <Mathias.Picker at virtual-earth.de> 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 <gljennjohn at gmail.com>
> To: Miranda van den Breukelingen <mms.vanbreukelingen at gmail.com>
> Cc: freebsd-x11 at freebsd.org
> Subject: Re: Problems with AMDGPU and two grafic cards
> Message-ID: <20191017173204.3a14266d at ernst.home>
> Content-Type: text/plain; charset=US-ASCII
>
> On Thu, 17 Oct 2019 16:36:48 +0200
> Miranda van den Breukelingen <mms.vanbreukelingen at gmail.com> 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 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?
>>
> 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.
>