EFI framebuffer information, then nothing

Sometimes, boot gets no further than EFI framebuffer information. Whenever this occurs, the computer will stop immediately in response to a simple, short press on the power button. The two lines preceding framebuffer information (copy typed from a photograph): staging 0xadc0 (not copying

Daily black screen of death

FYI, I'm experiencing an almost daily black screen of death panic. Kernel, world, drm-current-kmod, and gpu-firmware-kmod were all rebuilt and installed at the same time. Uname shows FreeBSD 14.0-CURRENT #0 main-n254360-eb9d205fa69: Tue Apr 5 13:49:47 PDT 2022 So, April 5th sources. The panic

Re: advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04]

On Apr 19, 2022, at 4:49 AM, Michael Schuster wrote: > Hi, > > I'm highjacking and re-purposing the previous thread, I hope that's OK > (I did change the subject ;-)) - I'm keeping some of the previous > contents for reference. > > I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and

Re: nullfs and ZFS issues

On Tue, Apr 19, 2022 at 11:47:22AM +0200, Mateusz Guzik wrote: | Try this: https://people.freebsd.org/~mjg/vnlru_free_pick.diff | | this is not committable but should validate whether it works fine As a POC it's working. I see the vnode count for the nullfs and ZFS go up. The ARC cache also goe

Re: 13-STABLE: can not cross build 13.0-RELENG and 13.1-RELENG, what on CURRENT works fine

The vdso error is fixed by cherry-picking b3b462229f972e2ed24d450d7d2f8855cdd58a87. I'm not sure about the second error, though if it's a general profile error, you make need WITHOUT_PROFILE=t in both the build and install phases. On Tue, Apr 19, 2022 at 5:46 AM FreeBSD User wrote: > I regular

Re: main-n254654-d4e8207317c results in "no pools available to import"

On 4/18/22 21:43, Graham Perrin wrote: On 12/04/2022 23:35, Dennis Clarke wrote: … at least two examples in the wild. … Not the same symptom, but caught my eye: RC3 Guided ZFS on root with encryption unmountable Beyond that, I ha

13-STABLE: can not cross build 13.0-RELENG and 13.1-RELENG, what on CURRENT works fine

I regular build for a NanoBSD appliance 13-STABLE, 13.0-RELENG and 13.1-RELENG on either 14-CURRENT and 13-STABLE. Several days ago, some changes has been made to /usr/src/Makefile.inc1, first on CURRENT and shortly after on 13. As with today, building from sources either 13.1-RELENG and 13.0-RELE

Re: nullfs and ZFS issues

Try this: https://people.freebsd.org/~mjg/vnlru_free_pick.diff this is not committable but should validate whether it works fine On 4/19/22, Mateusz Guzik wrote: > On 4/19/22, Mateusz Guzik wrote: >> On 4/19/22, Doug Ambrisko wrote: >>> I've switched my laptop to use nullfs and ZFS. Previousl

Re: nullfs and ZFS issues

On 4/19/22, Mateusz Guzik wrote: > On 4/19/22, Doug Ambrisko wrote: >> I've switched my laptop to use nullfs and ZFS. Previously, I used >> localhost NFS mounts instead of nullfs when nullfs would complain >> that it couldn't mount. Since that check has been removed, I've >> switched to nullfs

Re: nullfs and ZFS issues

On 4/19/22, Doug Ambrisko wrote: > I've switched my laptop to use nullfs and ZFS. Previously, I used > localhost NFS mounts instead of nullfs when nullfs would complain > that it couldn't mount. Since that check has been removed, I've > switched to nullfs only. However, every so often my laptop

advice sought: workflow with -CURRENT and amd GPU [Re: -CURRENT hangs since at least 2022-04-04]

Hi, I'm highjacking and re-purposing the previous thread, I hope that's OK (I did change the subject ;-)) - I'm keeping some of the previous contents for reference. I have similar HW to OP (Ryzen 7 4700 w. Renoir Graphics), and have been using a similar approach to keep the machine up to date - o

Re: -CURRENT hangs since at least 2022-04-04

On dl., abr. 18 2022, Pete Wright wrote: On 4/18/22 12:23, filis+fbsdcurr...@filis.org wrote: Hi, I'm running -CURRENT on this one desktop box which is a "Ryzen 7 4800U with Radeon Graphics", since it didn't work on 13R. I use Boot environments and on 2022-04-04 I updated it and it started