Re: boot.cfg syntax question
On Sun, 5 Jun 2022, Thomas Klausner wrote:
Did I misunderstand the man page or is there a bug here?
Alrighty, this patch fixes it for me (also fixes PR# 53128):
---START---
diff -urN sys/arch/i386/stand/efiboot.orig/boot.c
sys/arch/i386/stand/efiboot/boot.c
--- sys/arch/i386/stand/efiboot.orig/boot.c 2021-09-07 11:41:31.0
+
+++ sys/arch/i386/stand/efiboot/boot.c 2022-06-05 06:50:39.139514564 +
@@ -453,8 +453,10 @@
} else {
int i;
+#if 0
if (howto == 0)
bootdefault();
+#endif
for (i = 0; i < NUMNAMES; i++) {
bootit(names[i][0], howto);
bootit(names[i][1], howto);
---END---
-RVP
x86 console size
Dear folks, since some time I noticed that the initial graphical console has small letters but is later reset to big letters again. Is this intentional? How can I preserve the smaller font? The 80x25 (or x31?) is quite huge on this monitor and I really liked the smaller fonts! Could switching to the big fonts be an option? With regards, Reinoud
Re: boot.cfg syntax question
On Sun, Jun 05, 2022 at 06:59:23AM +, RVP wrote:
> On Sun, 5 Jun 2022, Thomas Klausner wrote:
>
> > Did I misunderstand the man page or is there a bug here?
> >
>
> Alrighty, this patch fixes it for me (also fixes PR# 53128):
>
> ---START---
> diff -urN sys/arch/i386/stand/efiboot.orig/boot.c
> sys/arch/i386/stand/efiboot/boot.c
> --- sys/arch/i386/stand/efiboot.orig/boot.c 2021-09-07 11:41:31.0
> +
> +++ sys/arch/i386/stand/efiboot/boot.c2022-06-05 06:50:39.139514564
> +
> @@ -453,8 +453,10 @@
> } else {
> int i;
>
> +#if 0
> if (howto == 0)
> bootdefault();
> +#endif
> for (i = 0; i < NUMNAMES; i++) {
> bootit(names[i][0], howto);
> bootit(names[i][1], howto);
> ---END---
Thanks, I've filed PR 56862 for this.
Thomas
Re: boot.cfg syntax question
Hello,
thanks for bringing this up. I just wanted to add another data point here:
https://mail-index.netbsd.org/netbsd-users/2021/02/03/msg026523.html
To me it looks like the same issue - nice to read this has been solved
with the patch and looking forward to test it.
Kind regards
Matthias
Am 05.06.2022 um 08:59 schrieb RVP:
On Sun, 5 Jun 2022, Thomas Klausner wrote:
Did I misunderstand the man page or is there a bug here?
Alrighty, this patch fixes it for me (also fixes PR# 53128):
---START---
diff -urN sys/arch/i386/stand/efiboot.orig/boot.c
sys/arch/i386/stand/efiboot/boot.c
--- sys/arch/i386/stand/efiboot.orig/boot.c 2021-09-07
11:41:31.0 +
+++ sys/arch/i386/stand/efiboot/boot.c 2022-06-05 06:50:39.139514564
+
@@ -453,8 +453,10 @@
} else {
int i;
+#if 0
if (howto == 0)
bootdefault();
+#endif
for (i = 0; i < NUMNAMES; i++) {
bootit(names[i][0], howto);
bootit(names[i][1], howto);
---END---
-RVP
Re: x86 console size
On Sun, 5 Jun 2022, Reinoud Zandijk wrote: Could switching to the big fonts be an option? With both fonts compiled in you can switch between them using: wsconsctl -dw font='Boldface 16x32' wsconsctl -dw font=Boldface -RVP
Re: boot.cfg syntax question
On Sun, Jun 05, 2022 at 12:53:09AM +, RVP wrote: > On Sun, 5 Jun 2022, Thomas Klausner wrote: > > > However, when I press '3' in that config, I get a kernel where nouveau > > is disabled. > > > > Did I misunderstand the man page or is there a bug here? > > > > Looks like a bug when a bare `boot' is encountered. Work around it by > forcing a kernel filename: > > --- boot.cfg.orig 2022-06-05 00:48:51.47679 + > +++ boot.cfg2022-06-05 00:49:18.797459000 + > @@ -1,6 +1,6 @@ > -menu=Boot without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot > +menu=Boot without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot /netbsd > menu=Boot old without nouveau:rndseed /var/db/entropy-file;userconf disable > nouveau*;boot /netbsd.old > -menu=Boot normally:rndseed /var/db/entropy-file;boot > +menu=Boot normally:rndseed /var/db/entropy-file;boot /netbsd > menu=Boot single user:rndseed /var/db/entropy-file;boot -s > menu=Drop to boot prompt:prompt > default=1 Yes, this works around the issue for me. Thanks! Thomas
Re: NetBSD Xen guest freezes system + vif MAC address confusion (NetBSD 9.99.97 / Xen 4.15.2)
Hello Manuel, Am 27.05.2022 um 20:39 schrieb Manuel Bouyer: On Fri, May 27, 2022 at 02:06:59PM +0200, Matthias Petermann wrote: Anyway, Once I try to "xl console" I did only get a fragment: ``` ganymed$ doas xl console net [ 1.000] cpu_rng: rdrand [ 1.000] entropy: ready [ 1.000] Copyright (c) 1996, 1997, 1998, 1999, ``` At the "1999," the Dom0 became frozen, again. A recent change caused xenconsoled to hang, and possibly xenstore to miss events too. Should be fixed with src/sys/arch/xen/xen/xenevt.c 1.65 But the hang on the filesystem remains for me. Today I continued my tests and reinstalled NetBSD 9.99.97 (built from the sources of 30.05.2022). Xentools and Xenkernel are still the same as in my initial case (from 29.04.2022). Differences from the build of 05/25/2022: - I can now start a DomU without any problems and install e.g. a NetBSD in it. This had previously already led to a freeze of the system, so this part of the issue seems to be resolved too me When shutting down the DomU, the whole system still hangs. If I understood your mail from 30.05.2022 (HEAD UP - NetBSD 9.99.x dom0 needs a Xen tool patch) correctly, I need new Xen tools or a manual patch for this part of the problem. I will try the latter today. Thanks for all the effort you guys put into supporting Xen on NetBSD so well! Many greetings Matthias
Potential iostat output format change
I find that I don't much like one aspect of the format of iostat -d
output, consider:
wd0 wd1 wd4
KB/t t/s MB/s KB/t t/s MB/s KB/t t/s MB/s
15.98 18 0.286 14.26 871 12.13 14.22 853 11.84
0.0000 0.000 0.0000 0.000 0.0000 0.000
0.0000 0.000 0.5000 0.000 0.5000 0.000
0.0000 0.000 0.0000 0.000 0.0000 0.000
0.0000 0.000 0.0000 0.000 0.0000 0.000
0.0000 0.000 0.0000 0.000 0.0000 0.000
Notice how visually, that looks like one column, followed by two
groups of 3 columns, followed by another group of 2 columns.
In reality, of course, it is 3 groups of 3 columns, but the
leading white space in the t/s column makes that appear to be
a separator.
It seemed to me that just swapping the KB/t and t/s columns
would make that problem go away, so I did that - but then I
also noticed that 4 columns (plus one guaranteed blank) for
t/s is absurdly insufficient these days, I can get 15K t/s
on rotating rust without trying hard, easily 20K t/s on a
sata ssd, and 75K t/s on nvme. That column needs more space,
so I did that as well.
The result is:
wd0 wd1 wd4
t/s KB/t MB/s t/s KB/t MB/s t/s KB/t MB/s
18 15.98 0.286 869 14.26 12.09 850 14.22 11.81
0 0.000 0.000 0 0.000 0.000 0 0.000 0.000
0 0.000 0.000 0 0.000 0.000 0 0.000 0.000
0 0.000 0.000 0 0.000 0.000 0 0.000 0.000
0 0.000 0.000 0 0.000 0.000 0 0.000 0.000
0 0.000 0.000 0 0.000 0.000 0 0.000 0.000
which to me just looks better, easier to spot the columns, and
more space for t/s (the decimal point moves around in the KB/t
and MB/s columns so they aren't as much of an issue).
Of course, once I did that, I had to look at the -D output, and
adjust that as well, and then modify both again when -I is included.
I won't bore you by showing the differences (but my guess is that
no-one has used -I in ages, its output columns were not nearly wide
enough for the info it was printing - give it a few drives, and the
headings would be on top of the wrong columns).
A patch which makes this happen is appended, for you to try. This is
against HEAD, but iostat hasn't altered in ages, so it should apply
cleanly on -9, and perhaps -8 as well.
Note: it is not finished, I haven't (yet) done anything about the
code that works out how many drives there is space to display, which
definitely will need adjusting. I also haven't fixed my other pet
hate, that it displays the drives in the order it finds them from
the kernel, rather than the order given on the command line (when
drives are specified there). Further, with -I, the totals probably
need to auto-scale - now it simply always prints MB, which will result
in very bit numbers, quite quickly - I thought of having (per drive)
scaling apply each time the header lines are output - if the number
to be printed is getting too big for MB, switch to GB, and then TB, and ...
(systems which are up a long time can easily reach total transfer
volumes where counts even in TB start getting too big to manage).
(An additional option to show totals from when iostat starts, rather
than from boot, might also be useful).
Anyway, let me know what you think - is this worth finishing, or will
the changes break people's scripts (or something similar) - or do you
just prefer it the current way.
kre
Index: iostat.c
===
RCS file: /cvsroot/src/usr.sbin/iostat/iostat.c,v
retrieving revision 1.67
diff -u -r1.67 iostat.c
--- iostat.c8 Apr 2018 11:37:31 - 1.67
+++ iostat.c6 Jun 2022 04:18:15 -
@@ -287,14 +287,20 @@
if (ISSET(todo, SHOW_STATS_1)) {
for (i = 0; i < ndrive; i++)
- if (cur.select[i])
- (void)printf("%9.9s ", cur.name[i]);
+ if (cur.select[i]) {
+ if (ISSET(todo, SHOW_TOTALS))
+ (void)printf("");
+ (void)printf(" %9.9s ", cur.name[i]);
+ }
}
if (ISSET(todo, SHOW_STATS_2)) {
for (i = 0; i < ndrive; i++)
- if (cur.select[i])
- (void)printf("%9.9s ", cur.name[i]);
+ if (cur.select[i]) {
+ if (ISSET(todo, SHOW_TOTALS))
+ (void)printf(" ");
+ (void)printf(" %9.9s ", cur.name[i]);
+ }
}
if (ISSET(todo, SHOW_CPU))
@@ -310,16 +316,20 @@
for (i = 0; i < ndrive; i++)
if (cur.select[i]) {
Interesting output from npfctl
Hi, One of my blocklist files ended up with a duplicate entry, and npfctl reload had this to say: npfctl reload npfctl: ?8t?f??K???H?5d? 6e 70 66 63 74 6c 3a 20 83 38 11 74 e5 66 90 e8 |npfctl: .8.t.f..| 0010 4b f3 ff ff 48 8d 35 64 a6 0a|K...H.5d..| NetBSD-9.99.97 from 23-May-2022, amd64. Any ideas? John
daily CVS update output
Updating src tree: P src/doc/3RDPARTY P src/sys/conf/files P src/sys/dev/pci/ixgbe/ixgbe_82598.c P src/sys/dev/pci/ixgbe/ixgbe_api.c P src/sys/dev/pci/ixgbe/ixgbe_common.c P src/sys/uvm/uvm_map.c P src/tests/usr.bin/ld/t_section.sh Updating xsrc tree: Killing core files: Updating release-8 src tree (netbsd-8): U doc/CHANGES-8.3 P sys/arch/atari/atari/stalloc.c Updating release-8 xsrc tree (netbsd-8): Updating release-9 src tree (netbsd-9): P crypto/external/bsd/openssh/dist/sshkey-xmss.c P crypto/external/bsd/openssh/dist/version.h U doc/CHANGES-9.3 P sys/arch/atari/atari/stalloc.c Updating release-9 xsrc tree (netbsd-9): Updating file list: -rw-rw-r-- 1 srcmastr netbsd 43253381 Jun 6 03:09 ls-lRA.gz
