Re: stable/13, vm page counts do not add up
On Tue, 13 Apr 2021 17:18:42 -0400 Mark Johnston wrote: > > P.S. > > I have not been running any virtual machines. > > I do use nvidia graphics driver. > In past I had report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238698 Now I switch to AMD and got only ~1Gb memory allocated by xorg. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 23:38:02 + Johannes Dieterich wrote: > > /usr/ports/graphics/drm-kmod > > /usr/ports/graphics/drm-stable-kmod > > /usr/ports/graphics/drm-legacy-kmod > > /usr/ports/graphics/drm-next-kmod > > /usr/ports/graphics/drm-devel-kmod > > > > Too many drm... > Which is why there is graphics/drm-kmod which will install the most > recent recommended DRM for your OS version. Could you try that? It install graphics/drm-stable-kmod. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU Bristol Ridge graphics support
On Mon, 1 Oct 2018 01:04:20 +0200 Wolfgang Zenker wrote: > > drm-next requires FreeBSD 12, I do not try it yet. > > that is no longer true; drm-next requires at least FreeBSD 11.2 now Got kernel panic on amdgpu load. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 23:21:36 + Johannes Dieterich wrote: > > drm-next requires FreeBSD 12, I do not try it yet. > It requires a FreeBSD version equal or higher than 1101511, could you > provide sysctl kern.osrelease? kern.osrelease: 11.2-STABLE /usr/ports/graphics/drm-kmod /usr/ports/graphics/drm-stable-kmod /usr/ports/graphics/drm-legacy-kmod /usr/ports/graphics/drm-next-kmod /usr/ports/graphics/drm-devel-kmod Too many drm... ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 20:37:07 + Johannes Dieterich wrote: > > finishing device. [TTM] Memory type 2 has not been initialized > > device_attach: drmn0 attach returned 22 > Just to make sure, the gpu-firmware port is installed > and /boot/modules contains these files the load is looking for? Which > drm port gets installed if you use the new graphics/drm-kmod > metaport? If it is next, could you try with that? # pkg version -v | grep gpu gpu-firmware-kmod-g20180825= up-to-date with index xf86-video-amdgpu-1.3.0_3 = up-to-date with index # pkg version -v | grep kmod drm-stable-kmod-g20180822 = up-to-date with index gpu-firmware-kmod-g20180825= up-to-date with index # ls /boot/modules/ | grep carrizo -r-xr-xr-x 1 root wheel13K Aug 26 21:20:06 2018 amdgpu_carrizo_ce_bin.ko* -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 amdgpu_carrizo_me_bin.ko* -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 amdgpu_carrizo_mec_bin.ko* -r-xr-xr-x 1 root wheel 261K Aug 26 21:20:06 2018 amdgpu_carrizo_mec2_bin.ko* -r-xr-xr-x 1 root wheel21K Aug 26 21:20:06 2018 amdgpu_carrizo_pfp_bin.ko* -r-xr-xr-x 1 root wheel23K Aug 26 21:20:06 2018 amdgpu_carrizo_rlc_bin.ko* -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 amdgpu_carrizo_sdma_bin.ko* -r-xr-xr-x 1 root wheel15K Aug 26 21:20:06 2018 amdgpu_carrizo_sdma1_bin.ko* -r-xr-xr-x 1 root wheel 270K Aug 26 21:20:06 2018 amdgpu_carrizo_uvd_bin.ko* -r-xr-xr-x 1 root wheel 176K Aug 26 21:20:06 2018 amdgpu_carrizo_vce_bin.ko* drm-next requires FreeBSD 12, I do not try it yet. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 18:12:01 + Johannes Dieterich wrote: > > I try drm-stable-kmod-g20180822 but it fail to load, as I > > understand. > That should work, could you post the error messages? I assume you > followed the instructions in the port? # kldload /boot/modules/amdgpu.ko [drm] Initialized [drm] amdgpu kernel modesetting enabled. drmn0: on vgapci0 vgapci0: child drmn0 requested pci_enable_io vgapci0: child drmn0 requested pci_enable_io [drm] initializing kernel modesetting (CARRIZO 0x1002:0x9874 0x1002:0x1E20 0xE2). [drm] register mmio base: 0xFE90 [drm] register mmio size: 262144 [drm] doorbell mmio base: 0xF000 [drm] doorbell mmio size: 8388608 [drm:amdgpu_device_init] Unable to find PCI I/O BAR [drm] probing mlw for device 1002:9874 = 0 [drm] UVD is enabled in physical mode [drm] VCE enabled in physical mode [drm:amdgpu_atombios_init] Unable to find PCI I/O BAR; using MMIO for ATOM IIO ATOM BIOS: BRISTOL [drm] GPU post is not needed Zone kernel: Available graphics memory: 3104154 kiB Zone dma32: Available graphics memory: 2097152 kiB [TTM] Initializing pool allocator drmn0: VRAM: 2048M 0x - 0x7FFF (2048M used) drmn0: GTT: 3031M 0x8000 - 0x00013D7667FF [drm] Detected VRAM RAM=2048M, BAR=256M [drm] RAM width 64bits UNKNOWN [drm] amdgpu: 2048M of VRAM memory ready [drm] amdgpu: 3031M of GTT memory ready. [drm] GART: num cpu pages 776038, num gpu pages 776038 [drm] PCIE GART of 3031M enabled (table at 0x0004). [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] amdgpu: irq initialized. amdgpu: powerplay initialized [drm] Connector DP-1: get mode from tunables: [drm] - kern.vt.fb.modes.DP-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-1: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-2: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-2 [drm] - kern.vt.fb.default_mode [drm] AMDGPU Display Connectors [drm] Connector 0: [drm] DP-1 [drm] HPD1 [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b [drm] Encoders: [drm] DFP1: INTERNAL_UNIPHY [drm] Connector 1: [drm] HDMI-A-1 [drm] HPD2 [drm] DDC: 0x486c 0x486c 0x486d 0x486d 0x486e 0x486e 0x486f 0x486f [drm] Encoders: [drm] DFP2: INTERNAL_UNIPHY [drm] Connector 2: [drm] HDMI-A-2 [drm] HPD3 [drm] DDC: 0x4870 0x4870 0x4871 0x4871 0x4872 0x4872 0x4873 0x4873 [drm] Encoders: [drm] DFP3: INTERNAL_UNIPHY1 amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 amdgpu/carrizo_pfp.bin: could not load firmware image, error 2 amdgpu/carrizo_me.bin: could not load firmware image, error 2 amdgpu/carrizo_me.bin: could not load firmware image, error 2 amdgpu/carrizo_ce.bin: could not load firmware image, error 2 amdgpu/carrizo_ce.bin: could not load firmware image, error 2 amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 amdgpu/carrizo_rlc.bin: could not load firmware image, error 2 amdgpu/carrizo_mec.bin: could not load firmware image, error 2 amdgpu/carrizo_mec.bin: could not load firmware image, error 2 amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 amdgpu/carrizo_mec2.bin: could not load firmware image, error 2 drmn0: fence driver on ring 0 use gpu addr 0x8010, cpu addr 0x0xf800444aa010 drmn0: fence driver on ring 1 use gpu addr 0x8020, cpu addr 0x0xf800444aa020 drmn0: fence driver on ring 2 use gpu addr 0x8030, cpu addr 0x0xf800444aa030 drmn0: fence driver on ring 3 use gpu addr 0x8040, cpu addr 0x0xf800444aa040 drmn0: fence driver on ring 4 use gpu addr 0x8050, cpu addr 0x0xf800444aa050 drmn0: fence driver on ring 5 use gpu addr 0x8060, cpu addr 0x0xf800444aa060 drmn0: fence driver on ring 6 use gpu addr 0x8070, cpu addr 0x0xf800444aa070 drmn0: fence driver on ring 7 use gpu addr 0x8080, cpu addr 0x0xf800444aa080 drmn0: fence driver on ring 8 use gpu addr 0x8090, cpu addr 0x0xf800444aa090 amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 amdgpu/carrizo_sdma1.bin: could not load firmware image, error 2 drmn0: fence driver on ring 9 use gpu addr 0x80a0, cpu addr 0x0xf800444aa0a0 drmn0: fence driver on ring 10 use gpu addr 0x80b0, cpu addr 0x0xf800444aa0b0 amdgpu/carrizo_uvd.bin: could not load firmware image, error 2 amdgpu/carrizo_uvd.bin: could not load firmware image, error 2 [drm] Found UVD firmware Version: 1.91 Family ID: 11 drmn0: fence driver on ring 11 use gpu addr 0x00681560, cpu addr 0x0xf800e0681560 amdgpu/carrizo_vce.bin: could not load firmware image, error 2 amdgpu/carrizo_vce.bin: could not
Re: APU Bristol Ridge graphics support
On Sun, 30 Sep 2018 17:04:26 + Johannes Dieterich wrote: > > A10-9700 > > Bristol Ridge Radeon R7 > > > > vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 > > chip=0x98741002 rev=0xe2 hdr=0x00 vendor = 'Advanced Micro > > Devices, Inc. [AMD/ATI]' device = 'Wani [Radeon R5/R6/R7 > > Graphics]' class = display > > subclass = VGA > Yes, I've had a Bristol Ridge as a daily driver until a few days ago. > Use the LinuxKPI based DRM from ports, if you are on CURRENT > graphics/drm-devel-kmod, and load amdgpu.ko. > I am on 11.2. I try drm-stable-kmod-g20180822 but it fail to load, as I understand. Is xf86-video-amdgpu must be used with drm-*-kmod* ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
APU Bristol Ridge graphics support
Hello! Is this graphics supported? A10-9700 Bristol Ridge Radeon R7 vgapci0@pci0:0:1:0: class=0x03 card=0x1e201002 chip=0x98741002 rev=0xe2 hdr=0x00 vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]' device = 'Wani [Radeon R5/R6/R7 Graphics]' class = display subclass = VGA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Good motherboard for Ryzen (first-gen)
On Sat, 22 Sep 2018 20:28:22 +0200 Stefan Ehmann wrote: > Minor issues: > - powerd/amdtemp don't work correctly, I'll probably retest when > 12-BETA is out Will not. We does not have rep CPU temp offset table. Not sure about thing in base, but mine AMDTemp: https://reviews.freebsd.org/D9759 have sysctl tune for temperature offset, you can use it. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Good motherboard for Ryzen (first-gen)
On Fri, 21 Sep 2018 21:53:20 -0500 Eric van Gyzen wrote: > I would like to build a Ryzen desktop. Can anyone recommend a good > motherboard? https://www.hardwareluxx.de/community/f12/pga-am4-mainboard-vrm-liste-1155146.html Any MoBo based on IR35201 or ASP1405I. > I'm planning on a first-gen, because the second-gen has similar > stability problems as the first-gen had, and AMD hasn't released > errata for the second-gen yet (as far as I know...I would love to be > wrong). > I dont see any issies with Ryzens: 1300x (25 week), 2200G, 2700x. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"