https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
--- Comment #5 from Martin Birgmeier ---
Try this patch on /boot/lua/drawer.lua:
--- /boot/lua/drawer.lua2024-05-10 18:42:55.0 +0200
+++ /tmp/drawer.lua 2024-11-02 07:49:23.444324000 +0100
@@ -210,7 +210,7 @@
if
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282481
--- Comment #2 from Ronald Minnich ---
oops. Sorry. hit some kind of glitch.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282482
Mark Linimon changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282481
--- Comment #1 from Mark Linimon ---
*** Bug 282482 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282482
Ronald Minnich changed:
What|Removed |Added
Summary|Need to be able to specify |Need to be able to specify
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282482
Bug ID: 282482
Summary: Need to be able to specify NFS mounport and not use
port mapper
Product: Base System
Version: Unspecified
Hardware: Any
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282481
Bug ID: 282481
Summary: Need to be able to specify NFS mounport and not use
port mapper
Product: Base System
Version: Unspecified
Hardware: Any
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
Bjoern A. Zeeb changed:
What|Removed |Added
Status|Open|In Progress
Version|Un
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
--- Comment #4 from Evgenii Khramtsov <2khramt...@gmail.com> ---
(In reply to Bjoern A. Zeeb from comment #3)
> Also if you have no DEBUG kernel (or no INVARIANTS) *__m may not be used in a
> function but only declared, which leads to an e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
Bjoern A. Zeeb changed:
What|Removed |Added
Status|New |Open
--- Comment #3 from Bjoern A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282309
Kevin Bowling changed:
What|Removed |Added
Keywords||IntelNetworking
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
--- Comment #5 from Ed Maste ---
(In reply to Alexander Ziaee from comment #4)
Yes - beep(1) is now in the base system. The missing piece is to connect the
event from vt to triggering beep.
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
--- Comment #4 from Alexander Ziaee ---
There's just this: https://reviews.freebsd.org/D32672
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
--- Comment #3 from Ed Maste ---
> So, bell ring only works on "pc speaker"?
Both sc(4) and vt(4) have kernel support only for the "pc speaker," calling
sysbeep().
vt(4) can also generate a notification when the bell needs to ring, but I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
--- Comment #2 from Yusuf Yaman ---
(In reply to Ed Maste from comment #1)
I am using a desktop computer and I don't have any "pc speaker" installed on my
motherboard. So, bell ring only works on "pc speaker"? I thought I could hear
it thro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
Evgenii Khramtsov <2khramt...@gmail.com> changed:
What|Removed |Added
CC||b...@free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
Bug ID: 282479
Summary: LinuxKPI: lockdep_is_held() user
doesn't build after LLVM 19 import
Product: Base System
Version: Unspecified
Hardware: Any
O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282479
--- Comment #2 from Evgenii Khramtsov <2khramt...@gmail.com> ---
__diagused was added to lockdep_is_held() parameters after base 5c92f84bb607
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Bug ID: 282478
Summary: [ipfilter] Silence a lock upon service stop
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282414
--- Comment #2 from Wolfram Schneider ---
(In reply to Wolfram Schneider from comment #1)
Actually, it seems that debian calls "col -b -p -x" when stdout is not a TTY.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282414
Wolfram Schneider changed:
What|Removed |Added
Status|New |Open
--- Comment #1 from Wolfr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282184
John Baldwin changed:
What|Removed |Added
Status|New |Open
Assignee|b...@freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
Alexander Ziaee changed:
What|Removed |Added
Status|New |Open
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282474
Bug ID: 282474
Summary: bell: unable to enable bell
Product: Base System
Version: 14.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349
Bug 203349 depends on bug 204837, which changed state.
Bug 204837 Summary: kbdcontrol -b (bell control) does not work with vt(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204837
What|Removed |Added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027
Bug 231027 depends on bug 204837, which changed state.
Bug 204837 Summary: kbdcontrol -b (bell control) does not work with vt(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204837
What|Removed |Added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204837
Ed Maste changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281713
Ed Maste changed:
What|Removed |Added
Status|New |In Progress
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281713
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f65c19a242de322930f6a1cd7d5e6bf3ce19ce42
commit f65c19a242de322930f6a1cd7d5e6bf3ce19ce42
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
--- Comment #4 from jakub_l...@mailplus.pl ---
(In reply to Martin Birgmeier from comment #3)
No beastie here, just defaults. Ascii border is garbled as previously with
ports.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
--- Comment #3 from Martin Birgmeier ---
(In reply to jakub_lach from comment #1)
This commit is certainly the root cause: LOADER_BIOS_TEXTONLY has been turned
on.
Do you have loader_logo="beastie" in /boot/loader.conf? - This is what I h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
Martin Birgmeier changed:
What|Removed |Added
CC||d8zne...@aon.at
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274538
--- Comment #4 from Edward Tomasz Napierala ---
https://reviews.freebsd.org/D47391
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281713
--- Comment #5 from Ed Maste ---
> BTW is there any documentation of these escape sequences that may need
> updating as
> well?
Unsure - I did not find `\[[=%d.%dB]` documented.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197876
cr...@rlwinm.de changed:
What|Removed |Added
CC||cr...@rlwinm.de
--- Comment #6 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192223
tsg168 changed:
What|Removed |Added
CC||mas308...@gmail.com
--- Comment #2 from t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193442
tsg168 changed:
What|Removed |Added
CC||mas308...@gmail.com
--- Comment #1 from t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190942
Oleksandr Tymoshenko changed:
What|Removed |Added
CC||d...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
--- Comment #1 from jakub_l...@mailplus.pl ---
I've noticed
https://cgit.freebsd.org/src/commit/?h=stable/14&id=4d3b05a8530e42f7494dd3fbab8d017adb433b14
but it shouldn't brake font? I don't recall I've set anything nonstandard part
from auto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282465
Bug ID: 282465
Summary: Corrupted bootloader font after update to 14.2-STABLE
#0 stable/14-4e8444d575 after 26 October
Product: Base System
Version: 14.1-STABLE
Hardw
43 matches
Mail list logo