Re: Problems with AMDGPU and two grafic cards
Miranda van den Breukelingen <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]> |
Having BIOS reversion 5220 and something changed, but not as desired. This is the log: Oct 18 05:48:02 freebsd13 kernel: [drm:drm_core_init] Initialized Oct 18 05:48:02 freebsd13 kernel: [drm] amdgpu kernel modesetting enabled. Oct 18 05:48:02 freebsd13 kernel: drmn0: <drmn> on vgapci0 Oct 18 05:48:02 freebsd13 kernel: vgapci0: child drmn0 requested pci_enable_io Oct 18 05:48:02 freebsd13 syslogd: last message repeated 1 times Oct 18 05:48:02 freebsd13 kernel: [drm:drm_minor_register] Oct 18 05:48:02 freebsd13 syslogd: last message repeated 1 times Oct 18 05:48:02 freebsd13 kernel: [drm:drm_minor_register] new minor registered 128 Oct 18 05:48:02 freebsd13 kernel: [drm:drm_minor_register] Oct 18 05:48:02 freebsd13 kernel: [drm:drm_minor_register] new minor registered 0 Oct 18 05:48:02 freebsd13 kernel: [drm] initializing kernel modesetting (OLAND 0x1002:0x6613 0x1043:0x0541 0x87). Oct 18 05:48:02 freebsd13 kernel: [drm] register mmio base: 0xFCC00000 Oct 18 05:48:02 freebsd13 kernel: [drm] register mmio size: 262144 Oct 18 05:48:02 freebsd13 kernel: [drm] PCI I/O BAR is not found. Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 0 <si_common> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 1 <gmc_v6_0> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 2 <si_ih> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 3 <amdgpu_powerplay> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 4 <dce_v6_0> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 5 <gfx_v6_0> Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_device_ip_block_add] add ip block number 6 <si_dma> Oct 18 05:48:02 freebsd13 kernel: [drm] BIOS signature incorrect 0 0 Oct 18 05:48:02 freebsd13 kernel: [drm:check_atom_bios] ATOMBIOS detected Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_atombios_init] PCI I/O BAR is not found. Using MMIO to access ATOM BIOS Oct 18 05:48:02 freebsd13 kernel: ATOM BIOS: 115-C718M00-100 Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_atombios_allocate_fb_scratch] atom firmware requested 0003ffe0 32kb Oct 18 05:48:02 freebsd13 kernel: [drm:amdgpu_atombios_get_clock_info] Changing default dispclk from 600Mhz to 625Mhz Oct 18 05:48:02 freebsd13 kernel: [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit Oct 18 05:48:02 freebsd13 kernel: [drm:gmc_v6_0_init_microcode] 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. after doing hw.syscons.disable=1, I'm getting an grafical screen, where you an see that it's booting boot not anything else, sometimes the monitor is completely off but can't find to Xorg. Here's the Xorg.log [ 120.717] (--) Log file renamed from "/var/log/Xorg.pid-4712.log" to "/var/log/Xorg.0.log" [ 120.718] X.Org X Server 1.18.4 Release Date: 2016-07-19 [ 120.718] X Protocol Version 11, Revision 0 [ 120.718] Build Operating System: FreeBSD 13.0-CURRENT amd64 [ 120.718] Current Operating System: FreeBSD freebsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r353710: Fri Oct 18 05:30:18 CEST 2019 root@freebsd13:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 [ 120.719] Build Date: 10 October 2019 06:43:10AM [ 120.719] [ 120.719] Current version of pixman: 0.38.4 [ 120.719] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 120.719] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 120.719] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 18 08:31:12 2019 [ 120.720] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [ 120.720] (==) No Layout section. Using the first Screen section. [ 120.720] (==) No screen section available. Using defaults. [ 120.720] (**) |-->Screen "Default Screen Section" (0) [ 120.720] (**) | |-->Monitor "<default monitor>" [ 120.720] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 120.720] (==) Automatically adding devices [ 120.720] (==) Automatically enabling devices [ 120.721] (==) Not automatically adding GPU devices [ 120.721] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 120.721] (==) FontPath set to: /usr/local/share/fonts/misc/, /usr/local/share/fonts/TTF/, /usr/local/share/fonts/OTF/, /usr/local/share/fonts/Type1/, /usr/local/share/fonts/100dpi/, /usr/local/share/fonts/75dpi/ [ 120.721] (==) ModulePath set to "/usr/local/lib/xorg/modules" [ 120.721] (II) The server relies on devd to provide the list of input devices. If no devices become available, reconfigure devd or disable AutoAddDevices. [ 120.721] (II) Loader magic: 0x42a010 [ 120.721] (II) Module ABI versions: [ 120.721] X.Org ANSI C Emulation: 0.4 [ 120.721] X.Org Video Driver: 20.0 [ 120.721] X.Org XInput driver : 22.1 [ 120.721] X.Org Server Extension : 9.0 [ 120.721] (WW) checkDevMem: failed to open /dev/mem (Operation not permitted) [ 120.722] (II) LoadModule: "glx" [ 120.722] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 120.724] (II) Module glx: vendor="X.Org Foundation" [ 120.724] compiled for 1.18.4, module version = 1.0.0 [ 120.724] ABI class: X.Org Server Extension, version 9.0 [ 120.724] (==) AIGLX enabled [ 120.724] (==) Matched modesetting as autoconfigured driver 0 [ 120.724] (==) Matched scfb as autoconfigured driver 1 [ 120.724] (==) Matched vesa as autoconfigured driver 2 [ 120.725] (==) Assigned the driver to the xf86ConfigLayout [ 120.725] (II) LoadModule: "modesetting" [ 120.725] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so [ 120.725] (II) Module modesetting: vendor="X.Org Foundation" [ 120.725] compiled for 1.18.4, module version = 1.18.4 [ 120.725] Module class: X.Org Video Driver [ 120.726] ABI class: X.Org Video Driver, version 20.0 [ 120.726] (II) LoadModule: "scfb" [ 120.726] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so [ 120.726] (II) Module scfb: vendor="X.Org Foundation" [ 120.726] compiled for 1.18.4, module version = 0.0.4 [ 120.726] ABI class: X.Org Video Driver, version 20.0 [ 120.727] (II) LoadModule: "vesa" [ 120.727] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so [ 120.727] (II) Module vesa: vendor="X.Org Foundation" [ 120.727] compiled for 1.18.4, module version = 2.4.0 [ 120.727] Module class: X.Org Video Driver [ 120.727] ABI class: X.Org Video Driver, version 20.0 [ 120.727] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 120.728] (II) scfb: driver for wsdisplay framebuffer: scfb [ 120.728] (II) VESA: driver for VESA chipsets: vesa [ 120.728] (--) Using syscons driver with X support (version 2.0) [ 120.728] (++) using VT number 9 [ 120.728] (WW) xf86EnableIO: Failed to open /dev/io for extended I/O(WW) Falling back to old probe method for modesetting [ 120.728] (EE) open /dev/dri/card0: Operation not supported by device [ 120.728] (WW) Falling back to old probe method for scfb [ 120.728] scfb trace: probe start [ 120.729] scfb trace: probe done [ 120.729] (EE) No devices detected. [ 120.729] (EE) Fatal server error: [ 120.729] (EE) no screens found(EE) [ 120.729] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 120.729] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 120.729] (EE) [ 120.729] (EE) Server terminated with error (1). Closing log file. after a fresh installation and a recent built of world and kernel. Do I need to change something in UE§FI BIOS? Miranda On 2019-10-17 17:32, Gary Jennejohn wrote: > On Thu, 17 Oct 2019 16:36:48 +0200 > Miranda van den Breukelingen <[email protected]> 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. > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-x11 To unsubscribe, send any mail to "[email protected]"