[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

I don't run current anymore. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

#7 from Yusuf Yaman --- Created attachment 259903 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=259903&action=edit the wand is closer to menu.webp Hi, I don't know how was it looking before when I use 14.2-RELEASE but i am on 15.0-CURRENT now and the beastie's wand

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 Marek Zarychta changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

FreeBSD-15.0-CURRENT-arm64-aarch64-zfs.vhd.xz fails to boot under Hyper-V v2 on Windows 11 Pro; possibly tied to: "stand: add comconsole backwards compatibility shim for aarch64"

In order to try to help test: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285681 I again tried to get main FreeBSD booting on the Windows DevKit 2023 under Windows 11 Pro, this time using: FreeBSD-15.0-CURRENT-arm64-aarch64-zfs.vhd.xz (expanded to .vhd and then the .vhd converted to

Re: Expected OpenSSL versions in 14-stable and 15-current

Van: "Enji Cooper (yaneurabeya)" Datum: maandag, 17 maart 2025 02:34 Aan: Minsoo Choo CC: FreeBSD CURRENT Onderwerp: Re: Expected OpenSSL versions in 14-stable and 15-current > On Mar 12, 2025, at 4:19PM, Minsoo Choo wrote: > > OpenSSL 3.5 LTS alpha has been just release

Re: Expected OpenSSL versions in 14-stable and 15-current

until 14-stable's end-of-life date? > > [1] https://github.com/openssl/openssl/releases/tag/openssl-3.5.0-alpha1 > [2] https://en.wikipedia.org/wiki/OpenSSL#Major_version_releases > [3] https://www.freebsd.org/security/#sup Hi Minsoo, It makes sense to upgrade to 3.5 o

-fstack-clash-protection triggers something in setfstab() (was: Re: Strange file access issue in a recent -current (but not with the previous BE))

Am 2025-02-26 16:20, schrieb Alexander Leidinger: Hi, the working system is from 2025-01-25-141603, the non working system is from 2025-02-21-115311. I'm not sure what the issue is exactly. I have traced down the change of behavior to ---snip--- if not LIBC.setfstab(fstab_file_path.encode()

Expected OpenSSL versions in 14-stable and 15-current

OpenSSL 3.5 LTS alpha has been just released [1]. The expected EOL date of OpenSSL 3.0 LTS is September 7th 2026 [2]. FreeBSD 15 is expected to be release in December 2025, and FreeBSD 14.5 is expected to be released in September 2026. 14-stable will be see its EOL on November 30th, 2028 [3]. W

Inaccuracies in 15.0-CURRENT documentation versus wayland+sway in practice

/run/user/`id -u` OK, so then I execute sway(1) and I get the lovely blue background. When I do a ls /var/run​ there's no user​ directory there. There is​ an xdg​ directory that contains the id -c​ of the user that ran sway. Now, I grant that I'm running 15.0-CURRENT against document

Re: No working interface bce0 after updating to CURRENT of March 1

rst, bce0. I changed the lines now to ifconfig_bce0="inet 192.168.178.5 netmask 255.255.255.0" # ifconfig_bce1="inet 192.168.178.6 netmask 255.255.255.0" defaultrouter="192.168.178.1" plugged in the cable again into the first port and all is fine, but unclear why i

Re: No working interface bce0 after updating to CURRENT of March 1

I had a wild guess and plug'ed in the RJ-45 into the server's 2nd port, modified /etc/rc.conf, booted and all was fine: $ ssh 192.168.178.5 $ uname -a FreeBSD jet 15.0-CURRENT FreeBSD 15.0-CURRENT #0 main-n275738-7ee310c80ea7: Sun Mar 2 01:13:00 CET 2025 guru@jet:/usr/obj/usr

Re: No working interface bce0 after updating to CURRENT of March 1

Hi You wrote : -- # netstat -rn Routing tables Internet: DestinationGatewayFlags Netif Expire default192.168.178.1 UGS*bce0* 127.0.0.1 link#3 UH lo0 192.168.178.0/24 link#2

No working interface bce0 after updating to CURRENT of March 1

Hello, Last night I updated a server from a 14.0-CURRENT amd64 1400094 #2 main-n264568-1d7ffb373c9d-dirty: Wed Sep 6 07:13:22 CEST 2023 to the CURRENT of March 1, 2025. All went fine. # git clone https://git.freebsd.org/src.git /usr/src # cd /usr/src # make -j8 buildworld

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 Mark Johnston changed: What|Removed |Added Status|New |Open -- You are receiving this ma

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 --- Comment #6 from Alexander Ziaee --- That color ASCII loader is just so beautiful. If I knew how to make the relevant file, I would add this back as an option, maybe `gfx-ascii.lua`. -- You are receiving this mail because: You are on t

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 --- Comment #5 from Marek Zarychta --- (In reply to Warner Losh from comment #4) I am booting this machine from BIOS and exceptionally it's drawing beastie, so an error in the text version logo is reported here. -- You are receiving this

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 --- Comment #4 from Warner Losh --- So this problem is with a BIOS loader, that's been compiled to enable graphics, correct? But the problems aren't present for the text version? cc'd manu since he made the alleged breaking changes. --

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org,

[Bug 285044] legacy BIOS loader: lua gfx logos on 15-CURRENT are broken

|logos gfx logos on |logos on 15-CURRENT are |15-CURRENT are broken |broken -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 285044] legacy BIOS loader: lua logos gfx logos on 15-CURRENT are broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285044 Marek Zarychta changed: What|Removed |Added CC||curr...@freebsd.org -- You are r

Strange file access issue in a recent -current (but not with the previous BE)

Hi, the working system is from 2025-01-25-141603, the non working system is from 2025-02-21-115311. I'm not sure what the issue is exactly. I have traced down the change of behavior to ---snip--- if not LIBC.setfstab(fstab_file_path.encode()): ---snip--- In the working case LIBC.setfstab re

Re: Very poor -CURRENT boot performance on AMD

Hi Jung-uk Kim, On Thu, Feb 20, 2025 at 5:22 AM Jung-uk Kim wrote: > On 25. 2. 19., Mohammad Noureldin wrote: > > --snip-- > This happens because UEFI framebuffer access from boot loader is very > slow. Once the kernel is loaded and booted, everything is okay because > we properly set memory a

Re: Very poor -CURRENT boot performance on AMD

Hi Rupesh, On Thu, Feb 20, 2025 at 5:11 AM Rupesh Pilania wrote: > Hi Mohammad, > > I tried the same build on VMware and it came up very fast. I don't have > any AMD Ryzen based hw to confirm the behaviour. > IMO you should raise a PR. > [image: image.png] > > Thanks & Regards > Rupesh Pilania >

Re: Very poor -CURRENT boot performance on AMD

Hi Maku, On Thu, Feb 20, 2025 at 3:47 AM Maku Bex wrote: > Hi Mohammad, > > > > The performance issue(s) have been noted on the UPDATING file. Here is a > snippet: > > > > > > NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW: > > FreeBSD 15.x has many debugging features turned on, in both

Error messages in 15.0-CURRENT (n275524-8dc0889..)

Folks, I built a GENERIC kernel "hot off the presses" as of the commits cited above. I am surprised that I'm still getting error messages in dmesg​ about: - Firmware errors - i915/skl_dmc_ver1_27.bin: could not load binary firmware /boot/firmware/i915/skl_dmc_ver1_27.bin either (repeats) - drm

Re: Very poor -CURRENT boot performance on AMD

On 25. 2. 19., Mohammad Noureldin wrote: Hi, I've installed -CURRENT using snapshot "FreeBSD-15.0-CURRENT- amd64-20250213-6156da866e7d-275409" on an HP EliteBook 845 G10 with AMD Ryzen 5 7540U. Both when booting from the install media and when booting from disk after insta

Re: Very poor -CURRENT boot performance on AMD

ightbird.com> wrote: > Hi, > > I've installed -CURRENT using snapshot > "FreeBSD-15.0-CURRENT-amd64-20250213-6156da866e7d-275409" on an HP > EliteBook 845 G10 with AMD Ryzen 5 7540U. > > Both when booting from the install media and when booting from disk after &

RE: Very poor -CURRENT boot performance on AMD

Gbnw2KQIJAQu1m9zEP5XdWmFi SvGg1NHW2kzqAvFsG37flbwrGRu5fmTnS/LZ/oPzOCuwU6F+o1q0E7gLwFwnzD93 riKeabdd =iCV+ -END PGP PUBLIC KEY BLOCK- From: owner-freebsd-curr...@freebsd.org On Behalf Of Mohammad Noureldin Sent: Wednesday, February 19, 2025 9:34 PM To: Freebsd current Subject: Very poor -CURREN

Very poor -CURRENT boot performance on AMD

Hi, I've installed -CURRENT using snapshot "FreeBSD-15.0-CURRENT-amd64-20250213-6156da866e7d-275409" on an HP EliteBook 845 G10 with AMD Ryzen 5 7540U. Both when booting from the install media and when booting from disk after installation I get a very poor boot performance up un

Re: HEADS UP: NFS changes coming into CURRENT early February

to be incorrect, so disregard it. I think we should focus on the dead connection leak, where NFS RPC layer doesn't process garbage collecting of a TCP connection unless it actually needs to make a write on it, described here: https://lists.freebsd.org/archives/freebsd-current/2025-January/

Re: HEADS UP: NFS changes coming into CURRENT early February

nd running rpcbind(8)) > are affected. You would need to recompile & reinstall both the world and the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specific > revisions that break AP

Re: HEADS UP: NFS changes coming into CURRENT early February

On Tue, Jan 28, 2025 at 09:14:00PM -0800, Gleb Smirnoff wrote: T> Second, with the patch the M_RPC leak count for me is 2. And I found that these T> two items are basically is a clnt_vc that belongs to a closed connection: T> T> f80029614a80 tcp4 0 0 10.6.6.9.772 10.6.6.9.204

Re: HEADS UP: NFS changes coming into CURRENT early February

On Mon, Jan 27, 2025 at 06:10:42PM -0800, Rick Macklem wrote: R> I think I've found a memory leak, but it shouldn't be a show stopper. R> R> What I did on the NFS client side is: R> # vmstat -m | fgrep -i rpc R> # mount -t nfs -o nfsv4,tls nfsv4-server:/ /mnt R> # ls --lR /mnt R> --> Then I networ

Re: HEADS UP: NFS changes coming into CURRENT early February

nd running rpcbind(8)) > are affected. You would need to recompile & reinstall both the world and the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specific > revisions that break AP

Re: HEADS UP: NFS changes coming into CURRENT early February

.g. running rpc.tlsclntd(8) or rpc.tlsservd(8)) as well as users of > > network lock manager (e.g. having 'options NFSLOCKD' and running rpcbind(8)) > > are affected. You would need to recompile & reinstall both the world and > > the > > kernel together. Of

Re: HEADS UP: NFS changes coming into CURRENT early February

nd running rpcbind(8)) > are affected. You would need to recompile & reinstall both the world and the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specific > revisions that break AP

Re: HEADS UP: NFS changes coming into CURRENT early February

On Thu, Jan 23, 2025 at 02:42:54PM -0800, Rick Macklem wrote: R> > The code is posted on phabricator, reviews D48547 through D48552. R> > Reviewers are very welcome! R> > R> > I share my branch on Github. It is usually rebased on today's CURRENT: R> > R>

Re: HEADS UP: NFS changes coming into CURRENT early February

nd running rpcbind(8)) > are affected. You would need to recompile & reinstall both the world and the > kernel together. Of course this is what you'd normally do when you track > FreeBSD CURRENT, but better be warned. I will post hashes of the specific > revisions that break AP

HEADS UP: NFS changes coming into CURRENT early February

recompile & reinstall both the world and the kernel together. Of course this is what you'd normally do when you track FreeBSD CURRENT, but better be warned. I will post hashes of the specific revisions that break API/ABI when they are pushed. Longer version: last year I tried to check-in a

USB massive disconnections with FreeBSD 15.0-CURRENT

, try to reset the USB stack and finally reboot. I attach part of the log messages uname -a FreeBSD defiant 15.0-CURRENT FreeBSD 15.0-CURRENT main-n273400-5e5e4e1cf0c3 GENERIC amd64 Nov  6 15:23:27 defiant dhclient[10922]: New Routers (em0): 192.168.66.1 Nov  6 18:30:15 defiant kernel: drmn0

[Bug 197921] scheduler: Allow non-migratable threads to bind to their current CPU

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197921 Mark Linimon changed: What|Removed |Added Keywords|needs-patch | -- You are receiving this mail be

Re: Freezes with FreeBSD 15.0-CURRENT since 3 weeks

10:40 *Aan:* freebsd-current@freebsd.org *Onderwerp:* Freezes with FreeBSD 15.0-CURRENT since 3 weeks Hi, Since 2 or 3 weeks I start experiencing system freezes on an and64 Lenovo Thinkbook laptop I'm using as my daily desktop PC. I'm running FreeBSD current using pkg base

Re: Freezes with FreeBSD 15.0-CURRENT since 3 weeks

: dinsdag, 22 oktober 2024 10:40 Aan: freebsd-current@freebsd.org Onderwerp: Freezes with FreeBSD 15.0-CURRENT since 3 weeks Hi, Since 2 or 3 weeks I start experiencing system freezes on an and64 Lenovo Thinkbook laptop I'm using as my daily desktop PC. I'm running FreeBSD current

Freezes with FreeBSD 15.0-CURRENT since 3 weeks

Hi, Since 2 or 3 weeks I start experiencing system freezes on an and64 Lenovo Thinkbook laptop I'm using as my daily desktop PC. I'm running FreeBSD current using pkg base_weekly to grab updates (currently main-n273070-6d42d5dbdd67). The full hardware details are here: https://wiki.f

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 09/10/2024 07:35, Paul Floyd wrote: … ld-elf.so.1: Shared object "libmd.so.6" not found, … pkgbase context: |

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 10-10-24 11:16, Konstantin Belousov wrote: If you can determine not just the number of taken locks, but also the specific locks that were taken, perhaps you can check that this is the libc exit lock? For the moment I've turned off the check for FreeBSD 15 and above. At present the ExeCo

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 07:34:31PM +, Paul Floyd wrote: > > > On 09-10-24 08:50, Konstantin Belousov wrote: > > > Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the > > backtrace to determine the situation. > > We don't read .gnu.version and the version number hasn't

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 09-10-24 08:50, Konstantin Belousov wrote: Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the backtrace to determine the situation. We don't read .gnu.version and the version number hasn't changed as far as I can see. I can check osreldate to get an idea of the

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 10:27:22AM +0200, Paul Floyd wrote: > > > > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov > > wrote: > > > On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > > > The biggest problem is with Helgrind. All apps now generate an extra > > error > > > > > > ==68593

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

> > > I can probably check whether it's the main thread (I assume that this code > doesn't run on subsidiary threads) > No it looks like it can be any thread. A+ Paul

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

> > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov > wrote: > On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > > The biggest problem is with Helgrind. All apps now generate an extra > error > > > > ==68593== Thread #1: Exiting thread still holds 1 lock > > ==68593==at 0x4BBB5DA:

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > Hi > > I don't often update my 15-0-CURRENT VM. I did last week and I'm getting > several issues. > > Firstly, a bit annoying, both pkg and ksh93 fail to run, giving. > ld-elf.so.1: Shared object &quo

Problems with FreeBSD-15.0-CURRENT-amd64-20241003

Hi I don't often update my 15-0-CURRENT VM. I did last week and I'm getting several issues. Firstly, a bit annoying, both pkg and ksh93 fail to run, giving. ld-elf.so.1: Shared object "libmd.so.6" not found, required by "ksh93" Next I'm getting a lot of ne

Re: change in /usr/bin/bc with CTRL-d no longer exit [fixed in -CURRENT]

Am 16.09.24 um 17:01 schrieb Cy Schubert: In message , Warner Losh writes: [...] The irony here is that i fixed thus very bug 2 or 3 years ago. Warner It's curious (or maybe not) how some bugs keep returning with a time and time again. Version 7.0.2 has just been committed to -CU

looking for feedback on the CURRENT stabilization cycle

Hi, we've been running the stabilization week of FreeBSD/main aka CURRENT since February. And it has been public since March. So we have had 5 cycles already and 4 were public. I'm eager to get some feedback from people who had been positively or negatively affected by this

random USB detach in CURRENT

Hi, Since a couple of weeks I'm start seeing random USB detach for all my devices once in a while. The issue doesn't occurs so often and there is no other details in the var log. I'm able to recover all my devices by just unplugging and re-plug the devices. I'm runni

Re: Is anyone using libzfs_core on 15-CURRENT?

On Wed, Jun 19, 2024 at 06:34:24PM +0100, David Chisnall wrote: > Hi all, > > I have some code using libzfs_core that works fine on 13, but seems not to on > 15-CURRENT. The lzc_snapshot function is failing with exactly the same nv > list argument. It is failing with errno 2 (E

Is anyone using libzfs_core on 15-CURRENT?

Hi all, I have some code using libzfs_core that works fine on 13, but seems not to on 15-CURRENT. The lzc_snapshot function is failing with exactly the same nv list argument. It is failing with errno 2 (ENOENT) from the ZFS ioctl (and not returning an nvlist of errors). My understanding is

Re: CURRENT: exec_machdep.c:80:2: error: KDB must be enabled in order for DDB

et this error while perfoming "make -jX > buildworld > buildkernel": > > [...] > /usr/src/sys/amd64/amd64/exec_machdep.c:80:2: error: KDB must be enabled in > order for DDB to > work! 80 | #error KDB must be enabled in order for DDB to work! > | ^ > [...]

CURRENT: exec_machdep.c:80:2: error: KDB must be enabled in order for DDB

DDB to work! 80 | #error KDB must be enabled in order for DDB to work! | ^ [...] Apart from the recommendation not to disable KDB in CURRENT, is there a way to disable debugging features and mimik a stable branch? Thanks in advance, oh -- O. Hartmann

Re: CURRENT kernel crash beyond git: 02d15215cef2

On 26/05/2024 13:45, Herbert J. Skuhra wrote: … No, idea why the fix hasn't been committed yet: … A few hours earlier: uma: Fix improper uses of UMA_MD_SMALL_ALLOC · freebsd/freebsd-src@d25ed65 HTH

Re: CURRENT kernel crash beyond git: 02d15215cef2

Am Sun, 26 May 2024 14:45:37 +0200 "Herbert J. Skuhra" schrieb: > On Sun, May 26, 2024 at 02:35:16PM +0200, FreeBSD User wrote: > > Hello, > > > > boxes running CURRENT are last good with FreeBSD 15.0-CURRENT #44 > > main-n270400-02d15215cef2: Sat May 25

Re: CURRENT kernel crash beyond git: 02d15215cef2

On Sun, May 26, 2024 at 02:35:16PM +0200, FreeBSD User wrote: > Hello, > > boxes running CURRENT are last good with FreeBSD 15.0-CURRENT #44 > main-n270400-02d15215cef2: > Sat May 25 10:56:09 CEST 2024 amd64. Customized kernel. > > After that commit, booting the kernel dies

Re: bsdinstall wifi setup is broken on CURRENT

On 18/05/24 11:33, Alfonso S. Siciliano wrote: On 5/16/24 20:40, Renato Botelho wrote: I saw some users on a .br group complaining bsdinstall was failing to setup wifi network on 15.0 snapshots and tried it myself.  I was able to reproduce the problem and also noticed another one. Thank you

Re: bsdinstall wifi setup is broken on CURRENT

On 18/05/24 11:33, Alfonso S. Siciliano wrote: On 5/16/24 20:40, Renato Botelho wrote: I saw some users on a .br group complaining bsdinstall was failing to setup wifi network on 15.0 snapshots and tried it myself.  I was able to reproduce the problem and also noticed another one. Thank you

Re: bsdinstall wifi setup is broken on CURRENT

On 5/16/24 20:40, Renato Botelho wrote: I saw some users on a .br group complaining bsdinstall was failing to setup wifi network on 15.0 snapshots and tried it myself.  I was able to reproduce the problem and also noticed another one. Thank you for your report, the video is highly appreciate

Re: bsdinstall wifi setup is broken on CURRENT

Renato Botelho writes: > I'm not sure about a good way to test it on a running system instead. Update your source tree, build and install world, run `sudo bsdconfig`, scroll down and select “Network Management”, then select “Wireless Networks”. DES -- Dag-Erling Smørgrav - d...@freebsd.org

Re: bsdinstall wifi setup is broken on CURRENT

Hello Renato, I will give it a try this weekend with bhyve since I have a passtrhu for iwlwifi card. Cheers, Renato Botelho escreveu (quinta, 16/05/2024 à(s) 19:56): > On 16/05/24 15:47, Jessica Clarke wrote: > > On 16 May 2024, at 19:40, Renato Botelho wrote: > >> > >> I saw some users on a

bsdinstall wifi setup is broken on CURRENT

Thank you for the information. The right email address is i...@aktionheizung.de Pay information exclusively to this email address. Thanks - On 16 May 2024, at 19:40, Renato Botelho wrote: I saw some users on a .br group complaining bsdinstall was

Re: bsdinstall wifi setup is broken on CURRENT

On 16/05/24 15:47, Jessica Clarke wrote: On 16 May 2024, at 19:40, Renato Botelho wrote: I saw some users on a .br group complaining bsdinstall was failing to setup wifi network on 15.0 snapshots and tried it myself. I was able to reproduce the problem and also noticed another one. I notic

Re: bsdinstall wifi setup is broken on CURRENT

On 16 May 2024, at 19:40, Renato Botelho wrote: > > I saw some users on a .br group complaining bsdinstall was failing to setup > wifi network on 15.0 snapshots and tried it myself. I was able to reproduce > the problem and also noticed another one. > > I noticed Network Selection screen only

bsdinstall wifi setup is broken on CURRENT

I saw some users on a .br group complaining bsdinstall was failing to setup wifi network on 15.0 snapshots and tried it myself. I was able to reproduce the problem and also noticed another one. I noticed Network Selection screen only shows one line, it's not beautiful to navigate through item

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help]

On 2024-05-08 23:53:57 (+0800), Mark Millard wrote: On Apr 29, 2024, at 20:16, Mark Millard wrote: On Apr 29, 2024, at 20:11, Mark Millard wrote: On Apr 29, 2024, at 19:54, Mark Millard wrote: On Apr 28, 2024, at 18:06, Philip Paeps wrote: On 2024-04-18 23:14:22 (+0800), Mark Millard

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, . . .] [Update to Host OSVERSION 1500018 did not help]

On Apr 29, 2024, at 20:16, Mark Millard wrote: > On Apr 29, 2024, at 20:11, Mark Millard wrote: > >> On Apr 29, 2024, at 19:54, Mark Millard wrote: >> >>> On Apr 28, 2024, at 18:06, Philip Paeps wrote: >>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: > On Apr 18, 2024, at 08

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 29, 2024, at 20:11, Mark Millard wrote: > On Apr 29, 2024, at 19:54, Mark Millard wrote: > >> On Apr 28, 2024, at 18:06, Philip Paeps wrote: >> >>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: On Apr 18, 2024, at 08:02, Mark Millard wrote: > void wrote on > Dat

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 29, 2024, at 19:54, Mark Millard wrote: > On Apr 28, 2024, at 18:06, Philip Paeps wrote: > >> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: >>> On Apr 18, 2024, at 08:02, Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : > Not sure where

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 28, 2024, at 18:06, Philip Paeps wrote: > On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: >> On Apr 18, 2024, at 08:02, Mark Millard wrote: >>> void wrote on >>> Date: Thu, 18 Apr 2024 14:08:36 UTC : >>> Not sure where to post this.. The last bulk build for arm64 app

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On 2024-04-18 23:14:22 (+0800), Mark Millard wrote: On Apr 18, 2024, at 08:02, Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7

Re: TXT Kernel linking failed on -CURRENT

Konstantin, good day! 25.04.2024 0:09, Konstantin Belousov пишет: On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote: linking kernel ld: error: undefined symbol: ktrcapfail referenced by vfs_lookup.c    vfs_lookup.o:(namei) referenced by vfs_lookup.c    vfs_look

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 26, 2024, at 18:55, Philip Paeps wrote: > On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: >> void wrote on >> Date: Thu, 18 Apr 2024 14:08:36 UTC : >> >>> Not sure where to post this.. >>> >>> The last bulk build for arm64 appears to have happened around >>> mid-March on ampere2. Is

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last completed build

Re: TXT Kernel linking failed on -CURRENT

On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote: > linking kernel > ld: error: undefined symbol: ktrcapfail > >>> referenced by vfs_lookup.c > >>>   vfs_lookup.o:(namei) > >>> referenced by vfs_lookup.c > >>>   vfs_lookup.o:(namei_setup) > >>> referenced by vfs_look

TXT Kernel linking failed on -CURRENT

Sorry for HTML-trash from previous mail :) Hi, FreeBSD Community! I have a teach with FreeBSD and use -CURRENT on my test machine. And some days ago after - git pull - make buildworld - make buildkernel There is /etc/src.conf and BSDSERV below, what can cause that error? Thanks for help! My

Kernel linking error on -CURRENT

Hi, FreeBSD Community! I have a teach with FreeBSD and use -CURRENT on my test machine.And some days ago after- git pull- make buildworld- make buildkernel There is /etc/src.conf and BSDSERV below, what can cause that error?Thanks for help! kernel building failed with such messages

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

match the modern "Jail OSVERSION" that would be used? The package builders are due for a regular refresh to newer -CURRENT dogfood. I'll do the aarch64 builders first this time. I've set /root/stop-builds on them. I'll upgrade them when they go idle. Or I'll kill

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 19, 2024, at 07:16, Philip Paeps wrote: > On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: > >> void wrote on >> Date: Thu, 18 Apr 2024 14:08:36 UTC : >> >>> Not sure where to post this.. >>> >>> The last bulk build for arm64 appears to have happened around >>> mid-March on ampere2.

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On 2024-04-18 23:02:30 (+0800), Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last completed build

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Thu, Apr 18, 2024 at 08:02:30AM -0700, Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last comple

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Apr 18, 2024, at 08:02, Mark Millard wrote: > void wrote on > Date: Thu, 18 Apr 2024 14:08:36 UTC : > >> Not sure where to post this.. >> >> The last bulk build for arm64 appears to have happened around >> mid-March on ampere2. Is it broken? > > main-armv7 building is broken and the las

pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : > Not sure where to post this.. > > The last bulk build for arm64 appears to have happened around > mid-March on ampere2. Is it broken? main-armv7 building is broken and the last completed build was the one started on Mon, 19 Feb 2024 12:32:10

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

27;t the cause, next test is the CTF stuff in the kernel... A rather obscure problem was causing this. The "last" BE had canmount set to "on" instead of "noauto". No idea how this happened, but this resulted in the "last" BE to be mounted on "zfs m

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

(For the not working Wifi chip, I use at the moment an USB-Wifi dongle, Realtek RTL8191S WLAN Adapter, which works fine). I also can't get Xorg plus twm up; it says in /var/log/Xorg.0.log at the end: .. REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270, ATI Radeon

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

On 3/29/24 16:52, Alexander Leidinger wrote: Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is something related to my setup:  - not a generic kernel  - very modular ker

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

Am 2024-03-29 18:13, schrieb Mark Johnston: On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote: Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is somet

Re: Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote: > Hi, > > sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work > (see below for the issue). As the monthly stabilisation pass didn't find > obvious issues, it is something related to my setup: > - not a gen

Multiple issues with current (kldload failures, missing CTF stuff, pty issues, ...)

Hi, sources from 2024-03-11 work. Sources from 2024-03-25 and today don't work (see below for the issue). As the monthly stabilisation pass didn't find obvious issues, it is something related to my setup: - not a generic kernel - very modular kernel (as much as possible as a module) - bind_

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

mt7921 supports all 802.11 a/b/g/n/ac and ax the compatibility code currently only supports 802.11 a/b/g modes. Support for 802.11 n/ac is to come. BUGS Certainly. SEE ALSO wlan(4), ifconfig(8), wpa_supplicant(8) HISTORY The mt7921 driver first appeared in FreeBSD 14.0. FreeBSD 14.0-CURRENTApril 18, 2023FreeBSD 14.0-CURRENT

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

El día miércoles, marzo 27, 2024 a las 10:37:48a. m. +0100, Matthias Apitz escribió: > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here > http://

Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

On Wed, Mar 27, 2024 at 12:38 PM Matthias Apitz wrote: > > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here > http://www.unixarea.de/ASUS-VivoBook-P

CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230

Hello, I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to boot FreeBSD with boot verbose messages from an USB key and I'm able to login. The /var/log/messages are here http://www.unixarea.de/ASUS-VivoBook-Pro-14-messages.txt I can identify the harddisk as nda0 (correct), bu

  1   2   3   4   5   6   7   8   9   10   >