Re: Boot failure, amd64 (HP EliteBook 650 G10)

Hi Graham, On 3/9/24 10:52, Graham Perrin wrote: amd64. AFAICT the EliteBook 650 G10 was introduced around May 2023. Does anything in the three photographs tally with a report in Bugzilla? Any overlap with

Re: Unable to boot -CURRENT on Thinkpad P16s G2

On 2/28/24 21:10, Philipp Ost wrote: [boot log stripped] Does anyone have any suggestions on how to proceed at this point? [...] Short follow-up: disabling uart0 and uart1 at the loader prompt allowed us to boot and install FreeBSD (the -CURRENT snapshot from 2024-02-29 in case it matters

Unable to boot -CURRENT on Thinkpad P16s G2

Hi everyone, we have a Lenovo Thinkpad P16s Gen2 (Type 21K9) here with an AMD Ryzen 7 CPU which we would like to install FreeBSD on. Alas, it won't boot. The FreeBSD 15-CURRENT amd64 snapshot from February 22 hangs after: [...] acpi_acad0: on acpi0 battery0: on acpi0 A verbose boot provides

Re: pxeboot binary is too big on FreeBSD (>640KBytes)

On 2/21/22 18:18, Simon J. Gerraty wrote: Toomas Soome wrote: Why should pxeboot have ZFS support? Well, the feature X can be helpful for recovery purposes. The root cause is not the feature X itself, but the size limit. And the unfortunate fact, the size limit is not fixed, but depends on th

Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden

On 9/9/21 9:15 PM, FreeBSD User wrote: [...] What has changed in the recent 14-CURRENT OpenSSH update that dramatically that working schematics do not work any more? OpenSSH has been updated to v8.7p1: https://cgit.freebsd.org/src/commit/?id=19261079b74319502c6ffa1249920079f0f69a72 One of th

Re: drm-kmod kernel crash fatal trap 12

On 6/10/21 5:13 PM, Bakul Shah wrote: On Jun 10, 2021, at 7:13 AM, Thomas Laus wrote: The drm-kmod module is the latest from the pkg server. It all worked this past Monday after the recent drm-kmod update. This is what I did: git clone https://github.com/freebsd/drm-kmod ln -s $PWD/drm-kmod

Re: cron(8) improvement

Warren Block schrieb: [...] ie either the file is named such that it is ignored by cron (preferable IMO) or the entries in them are commented out. Why not just use an additional entry in rc.conf? rsnapshot_cron="YES" (If there is a /usr/local/etc/cron.d/rsnapshot, add it to cron on start/rest