On 6 Nov 2024, at 17:12, Patrick M. Hausen wrote:
>
>>
>> Am 06.11.2024 um 17:10 schrieb Dimitry Andric :
>> Shouldn't you copy /boot/loader.efi instead? /boot/loader is an older
>> binary, not suitable for UEFI.
>
> Excuse me - that is what I did, other
On 6 Nov 2024, at 17:04, Patrick M. Hausen wrote:
>
> my newly installed 13.4 systems with UEFI boot show
>
> "Loader needs to be updated" in the beastie menu.
>
> root@ah003:~ # ll /boot/loader
> -r-xr-xr-x 3 root wheel 462848 Sep 13 10:05 /boot/loader*
> root@ah003:~ # freebsd-version
> 13
On 20 May 2024, at 13:00, UEMURA Tetsuya wrote:
>
> Main commit e63d20b70ee1dbee9b075f29de6f30cdcfe1abe1 corrected a typo in
> stand/liblua/lutils.h, which the typo prevents my arm loader.efi,
> specifically, loarder_lua.efi on RPi2 to boot. Can someone please MFC to
> 14-STABLE ?
https://cgit.f
On 15 Mar 2024, at 22:46, George Michaelson wrote:
>
> I feel in a bit of a corner case window regarding UEFI boot configuration,
> multiple disks, and zfs. Ignorance is not bliss.
>
> Probably it's UEFI clue more than FreeBSD clue I lack, but the target OS is a
> zfs backed FreeBSD.
>
> Whic
On 18 Feb 2024, at 13:10, David Wolfskill wrote:
>
>
> First one of these I've seen in a long time. This is amd64, using
> META_MODE:
>
> ...
> Building /common/S1/obj/usr/src/amd64.amd64/lib/libc/tests/db/Kyuafile
> Building /common/S1/obj/usr/src/amd64.amd64/lib/libc/tests/hash/h_hash
> Buil
On 13 Feb 2024, at 11:36, Filippo Moretti wrote:
>
> This is the error that I keep on getting while compiling GCC12
>
>
>
>
>
> [root@ROXY /usr/ports]# uname -a
> FreeBSD ROXY 14.0-STABLE FreeBSD 14.0-STABLE #22
> stable/14-n21-a727d8d7f50f: Fri Feb 9 22:57:13 CET 2024
> filippo@R
On 8 Jan 2024, at 21:40, mike tancsa wrote:
>
> After today's MFC of clang17, I am seeing some fallout from a few ports that
> build with clang16 on RELENG_13 but now fail. Any ideas what might be going
> on ? I have nothing in /etc/make.conf nor /etc/src.conf
..
> ld: error: version script
On 10 Jan 2024, at 13:16, mike tancsa wrote:
>
> On 1/10/2024 2:53 AM, Antoine Brodin wrote:
>> The preferred way is fixing the port by removing the undefined symbols
>>>
>>> from the linker version script in the port, but if that is not possible
>>> or difficult, add -Wl,--undefined-version to
On 8 Jan 2024, at 21:57, mike tancsa wrote:
>
> On 1/8/2024 3:40 PM, mike tancsa wrote:
>> After today's MFC of clang17, I am seeing some fallout from a few ports
>> that build with clang16 on RELENG_13 but now fail. Any ideas what might be
>> going on ? I have nothing in /etc/make.conf nor
On 29 Dec 2023, at 11:14, Harry Schmalzbauer wrote:
>
> at least since 14-release, I can't compile base/ports with CPUTYPE post
> nehalem. Any '-march' declaring AVX(*) capability leads to SIGILLing
> binaries with default -O2 CFLAGS.
> Not much of a help, but here's a ports example, but same
On 20 Dec 2023, at 11:25, Matthew Seaman wrote:
>
> I'm getting a failure building FreeBSD-base packages for stable/14 during
> buildworld in my poudriere setup:
>
> ```
> /usr/local/bin/ccache cc -target x86_64-unknown-freebsd14.0
> --sysroot=/usr/obj/usr/local/poudriere/jails/stable14base/us
On 7 Dec 2023, at 05:31, Mark Millard wrote:
>
> man arch reports:
>
> QUOTE
> Some machines support more than one FreeBSD ABI. Typically these are
> 64-bit machines, where the “native” LP64 execution environment is
> accompanied by the “legacy” ILP32 environment, which was the hist
your prompt answer:
> (lldb) target create "iridium"
> error "/usr/local/bin/iridium" doesn't contain any 'host' platform
> architectures:x86_64,i386
> Filippo
>
> On Monday, November 6, 2023 at 10:53:10 PM GMT+1, Dimitry Andric
> wrote:
On 6 Nov 2023, at 19:00, Filippo Moretti wrote:
>
> FreeBSD STING 14.0-STABLE FreeBSD 14.0-STABLE #2
> stable/14-n265685-52415bfc0adf-dirty: Mon Nov 6 17:32:23 CET 2023
> root@STING:/usr/obj/usr/src/amd64.amd64/sys/STING amd64
> When starting iridium I get Trace/BPT trap.
> There are no co
On 2 Oct 2023, at 22:00, Joel Bodenmann wrote:
>
> It seems like I finally managed to hose a FreeBSD system.
> The machine in question is my workstation at home. It has been running
> stable/13 without any problems. Yesterday I've updated to
> ef295f69abbffb3447771a30df6906ca56a5d0c0 and since th
On 25 Sep 2023, at 08:42, Frank Behrens wrote:
>
> Hi Dimitry, Yuri and also Mark, thanks for your fast responses!
>
> Am 23.09.2023 um 20:58 schrieb Yuri Pankov:
...
> # smartctl -a /dev/nvme0
> Namespace 1 Formatted LBA Size: 512
> ...
> Supported LBA Sizes (NSID 0x1)
> Id Fmt Data Metad
On 23 Sep 2023, at 18:31, Frank Behrens wrote:
>
> I created a zpool with a FreeBSD-14.0-CURRENT on February. With
> 15.0-CURRENT/14.0-STABLE from now I get the message:
>
> status: One or more devices are configured to use a non-native block size.
> Expect reduced performance.
> action
On 28 Apr 2023, at 09:40, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 28/04/2023 08:30, Dave Cottlehuber wrote:
>> On Thu, 27 Apr 2023, at 11:21, Miroslav Lachman wrote:
>
>>> After this I updated bootcode with gpart and rebooted the machine but it
>>> does not come up, cannot login via ssh
On 16 Apr 2023, at 20:32, Tom Vogt wrote:
>
> I try to compile the latest 13 stable version but it fails with an llvm error.
>
> My working version is:
> 13.2-STABLE stable/13-3cea7ca84 GENERIC amd64
>
> The version I try o compile is:
> git show -s
> commit 3e9d966ce45e3971c295a1dff7435d6b9f13
On 21 Jan 2023, at 19:55, Mathias Picker
wrote:
>
> I have this for some time, had no time to look into this, but today I deleted
> /usr/src, fetched source again, switched to stable/13, did a su -l root,
> removed /etc/make.conf and rebuild, same error.
...
> --- all_subdir_usr.sbin/bhyve ---
On 5 Jun 2022, at 17:08, Greg Balfour wrote:
>
> Running 13.1-RELEASE with everything installed from packages and aslr
> enabled, apache24 will core dump on a graceful restart after installing
> php81-extensions.
>
> Start with apache24, php81 and mod_php81 installed
> /usr/local/etc/rc.d/apache
On 8 Dec 2021, at 20:47, Jan Beich wrote:
>
> 12.3-RELEASE still uses Clang/libc++ 10 from 1 year ago. Do you plan
> to update in future as /stable/12 is supported until 2024-06-30?
>
> libc++ lags behind libstdc++ on C++20 features and sticking to an old
> version puts the entire branch on a de
On 11 Aug 2021, at 20:09, Warner Losh wrote:
>
> On Wed, Aug 11, 2021, 12:01 PM Paul Mather wrote:
>> On Aug 11, 2021, at 1:44 PM, Dimitry Andric wrote:
>>> On 11 Aug 2021, at 05:13, Eugene Grosbein wrote:
>>>>
>>>> I'm in process of upgra
On 11 Aug 2021, at 05:13, Eugene Grosbein wrote:
>
> I'm in process of upgrading very old remote FreeBSD server running
> 9.3-STABLE/amd64.
> First, I used svn to fetch stable/10 sources and performed source upgrade to
> 10.4-STABLE r369650
> and it went just fine.
>
> Now it has stock "FreeBS
24 matches
Mail list logo
