RE: EXT MAIL : log rotation with syslogng on netbsd 10
Thanks RVP will test this out.. I was manually running the pid but had to redo
this everytime the device was restarted .. so seems like your item1 change is
the solution. I did change the version # in the conf file earlier ..
-Original Message-
From: RVP
Sent: Tuesday, June 11, 2024 4:50 AM
To: Derrick Lobo
Cc: netbsd-users
Subject: RE: EXT MAIL : log rotation with syslogng on netbsd 10
On Tue, 11 Jun 2024, Derrick Lobo wrote:
> Anyone knows what could be wrong here.. is there a new logrotate for netbsd
> 10 which does not work with syslogng
>
Installed syslog-ng just now and newsyslog rotated the logs just fine.
I had only to make 2 fairly obvious changes:
1. In /etc/rc.d/syslogng, change the default pidfile name:
```
# pidfile="/var/run/${ngname}.pid"
pidfile="/var/run/syslogd.pid"
```
(I was too lazy to fix-up /etc/newsyslog.conf for syslog-ng...)
2. Add a `@version: 3.38' directive at the start of the syslog2ng-generated
/usr/pkg/etc/syslog-ng/syslog-ng.conf file:
```
$ head /usr/pkg/etc/syslog-ng/syslog-ng.conf
@version: 3.38
options { dir_perm(0755); perm(0644); chain_hostnames(no);
keep_hostname(yes); };
source local {
unix-dgram("/var/run/log");
udp(ip(0.0.0.0) port(514));
internal();
};
$
```
-RVP
RE: EXT MAIL : log rotation with syslogng on netbsd 10
On Tue, 11 Jun 2024, Derrick Lobo wrote:
Anyone knows what could be wrong here.. is there a new logrotate for netbsd 10
which does not work with syslogng
Installed syslog-ng just now and newsyslog rotated the logs just fine.
I had only to make 2 fairly obvious changes:
1. In /etc/rc.d/syslogng, change the default pidfile name:
```
# pidfile="/var/run/${ngname}.pid"
pidfile="/var/run/syslogd.pid"
```
(I was too lazy to fix-up /etc/newsyslog.conf for syslog-ng...)
2. Add a `@version: 3.38' directive at the start of the syslog2ng-generated
/usr/pkg/etc/syslog-ng/syslog-ng.conf file:
```
$ head /usr/pkg/etc/syslog-ng/syslog-ng.conf
@version: 3.38
options { dir_perm(0755); perm(0644); chain_hostnames(no);
keep_hostname(yes); };
source local {
unix-dgram("/var/run/log");
udp(ip(0.0.0.0) port(514));
internal();
};
$
```
-RVP
RE: EXT MAIL : log rotation with syslogng on netbsd 10
Anyone knows what could be wrong here.. is there a new logrotate for netbsd 10 which does not work with syslogng From: netbsd-users-ow...@netbsd.org On Behalf Of Derrick Lobo Sent: Monday, May 27, 2024 12:48 PM To: netbsd-users Subject: EXT MAIL : log rotation with syslogng on netbsd 10 The log rotation using syslogng on netbsd10 does not seem to work. Has anyone noticed this issue.. Lots stop rotating using newsyslog.. the very next day.. (we moved from syslog to syslogng more than a year ago and had no issues with newsyslog.. we didn't have to change anything in newsyslog at that time to make the logs rotated.. but with netbsd10- upgrade the log rotate just stopped CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Re: How to mount a PCMCIA hard drive
I have an old Latitude CP of ~2000 vintage with 2 cardbus slots. wi(4) works. Unfortunately other PCMCIA network card drivers seems to have bitrotted indeed. Neither mhzc(4), nor ne(4) work. Something changed at the interface/ether level, I guess. From my notes, I also experienced issues with PCMCIA and CF cards in both NetBSD 9.3 and 10 i386. This was my attempt to upgrade a 1998 Toshiba laptop from NetBSD 5.1 to 10. In the end, I had to use a USB storage stick. I'll have to dig out my old laptop to get you a better dmesg, but this was at least one of the errors: wdc2:0:0: lost interupt The same PCMCIA + CF card works fine on NetBSD 5.1. -Joel
Re: How to mount a PCMCIA hard drive
On Mon, Jun 10, 2024 at 16:42:52 -0700, Joel wrote: > > I have an old Latitude CP of ~2000 vintage with 2 cardbus slots. > > wi(4) works. Unfortunately other PCMCIA network card drivers seems to > > have bitrotted indeed. Neither mhzc(4), nor ne(4) work. Something > > changed at the interface/ether level, I guess. > > > From my notes, I also experienced issues with PCMCIA and CF cards in both > NetBSD 9.3 and 10 i386. This was my attempt to upgrade a 1998 Toshiba laptop > from NetBSD 5.1 to 10. In the end, I had to use a USB storage stick. I'll > have to dig out my old laptop to get you a better dmesg, but this was at > least one of the errors: wdc2:0:0: lost interupt > > The same PCMCIA + CF card works fine on NetBSD 5.1. http://gnats.netbsd.org/56403 ? I thought that was fixed. -uwe
Re: How to mount a PCMCIA hard drive
On Tue, Jun 11, 2024 at 01:56:22 +0700, Robert Elz wrote: > Date:Mon, 10 Jun 2024 03:58:30 +0300 > From:Valery Ushakov > Message-ID: > > | a CF card in a PCMCIA slot: > > I used to have systems with PCMCIA - I formed the impression (at the > time - several (major) NetBSD releases ago) that old sytle PCMCIA support > kind of bit-rotted about the time that CF support was being added. I have tested my Jornada relatively recently (a couple of years ago, with current that would eventually become 10) and it worked. CF is the only storage option there, so I would have noticed :) Unfortunately it's the CF itself that bit-rotted (the nice large 2GB one), so I only could test a minimal installation on a 256MB card. I have an old Latitude CP of ~2000 vintage with 2 cardbus slots. wi(4) works. Unfortunately other PCMCIA network card drivers seems to have bitrotted indeed. Neither mhzc(4), nor ne(4) work. Something changed at the interface/ether level, I guess. I seem to recall that freebsd(?) taught wi(4) WPA so that it can be used with modern access points. It requires updated firmware and I managed to flash the new one, that is supposed to support WEP, to one of my cards (there's a windows xp tool and i happened to had an xp machine with pcmcia slot) but have no idea if WPA indeed works (it still works with the old driver). -uwe
Re: How to mount a PCMCIA hard drive
On Mon, 10 Jun 2024 00:58:30 + (UTC) Valery Ushakov wrote: > On Sun, Jun 09, 2024 at 15:55:17 +0300, Erkki Ruohtula wrote: > > > On Sun, 9 Jun 2024 12:28:12 + (UTC) > > Martin Husemann wrote: > > > > > On Sun, Jun 09, 2024 at 01:47:45PM +0300, Erkki Ruohtula wrote: > > > > I have a "Centennial MicroDrive", 340 Mb that does into a PCMCIA > > > > card slot. Inserting it into the T23, I get these dmesg messages > > > > > > > > [ 6743.118863] wdc2 at pcmcia1 function 0: > > > PERIPHERALS, ATA > > > > CARD> [ 6743.118863] wdc2: i/o mapped mode > > > > [ 6743.618871] atabus2 at wdc2 channel 0 > > > > [ 8339.023384] atabus2: detached > > > > [ 8339.023384] wdc2: detached > > > > > > There should be a drive on that "atabus2", without the drive you > > > can not access the card. > > > > > > Not sure why no drive is detected in your case. > > > > I assumed wdc2 is the drive here. But then one would expect it to > > say "wdc2 at atabus2", not the other way round. I guess I better try > > finding another machine with Windows or Linux where I can test if > > the MicroDrive hardware itself is OK. It is many years since I last > > used it. But machines with PCMCIA slots are getting scarce. > > "wdc" is the "C"ontroller, the drives are "wd". E.g. from a dmesg > from Jornada 690 from from https://dmesgd.nycbug.org - a CF card in a > PCMCIA slot: > > wdc0 at pcmcia1 function 0: > wdc0: memory mapped mode > atabus0 at wdc0 channel 0 > wd0 at atabus0 drive 0 > wd0: > wd0: drive supports 1-sector PIO transfers, LBA48 addressing > wd0: 30535 MB, 62041 cyl, 16 head, 63 sec, 512 bytes/sect x 62537328 > sectors wd0: 32-bit data port Thanks, now I know what to look for. So the "wd0:" lines show features probed from the drive. This failed so maybe the drive is broken. Erkki
Re: How to mount a PCMCIA hard drive
Date:Mon, 10 Jun 2024 03:58:30 +0300 From:Valery Ushakov Message-ID: | a CF card in a PCMCIA slot: I used to have systems with PCMCIA - I formed the impression (at the time - several (major) NetBSD releases ago) that old sytle PCMCIA support kind of bit-rotted about the time that CF support was being added. kre
Re: How to mount a PCMCIA hard drive
On Sun, Jun 09, 2024 at 15:55:17 +0300, Erkki Ruohtula wrote: > On Sun, 9 Jun 2024 12:28:12 + (UTC) > Martin Husemann wrote: > > > On Sun, Jun 09, 2024 at 01:47:45PM +0300, Erkki Ruohtula wrote: > > > I have a "Centennial MicroDrive", 340 Mb that does into a PCMCIA > > > card slot. Inserting it into the T23, I get these dmesg messages > > > > > > [ 6743.118863] wdc2 at pcmcia1 function 0: > > ATA > > > CARD> [ 6743.118863] wdc2: i/o mapped mode > > > [ 6743.618871] atabus2 at wdc2 channel 0 > > > [ 8339.023384] atabus2: detached > > > [ 8339.023384] wdc2: detached > > > > There should be a drive on that "atabus2", without the drive you can > > not access the card. > > > > Not sure why no drive is detected in your case. > > I assumed wdc2 is the drive here. But then one would expect it to > say "wdc2 at atabus2", not the other way round. I guess I better try > finding another machine with Windows or Linux where I can test if the > MicroDrive hardware itself is OK. It is many years since I last used it. > But machines with PCMCIA slots are getting scarce. "wdc" is the "C"ontroller, the drives are "wd". E.g. from a dmesg from Jornada 690 from from https://dmesgd.nycbug.org - a CF card in a PCMCIA slot: wdc0 at pcmcia1 function 0: wdc0: memory mapped mode atabus0 at wdc0 channel 0 wd0 at atabus0 drive 0 wd0: wd0: drive supports 1-sector PIO transfers, LBA48 addressing wd0: 30535 MB, 62041 cyl, 16 head, 63 sec, 512 bytes/sect x 62537328 sectors wd0: 32-bit data port -uwe
Re: How to mount a PCMCIA hard drive
On Sun, 9 Jun 2024 12:28:12 + (UTC) Martin Husemann wrote: > On Sun, Jun 09, 2024 at 01:47:45PM +0300, Erkki Ruohtula wrote: > > I have a "Centennial MicroDrive", 340 Mb that does into a PCMCIA > > card slot. Inserting it into the T23, I get these dmesg messages > > > > [ 6743.118863] wdc2 at pcmcia1 function 0: > ATA > > CARD> [ 6743.118863] wdc2: i/o mapped mode > > [ 6743.618871] atabus2 at wdc2 channel 0 > > [ 8339.023384] atabus2: detached > > [ 8339.023384] wdc2: detached > > There should be a drive on that "atabus2", without the drive you can > not access the card. > > Not sure why no drive is detected in your case. I assumed wdc2 is the drive here. But then one would expect it to say "wdc2 at atabus2", not the other way round. I guess I better try finding another machine with Windows or Linux where I can test if the MicroDrive hardware itself is OK. It is many years since I last used it. But machines with PCMCIA slots are getting scarce. Erkki
Re: How to mount a PCMCIA hard drive
On Sun, Jun 09, 2024 at 01:47:45PM +0300, Erkki Ruohtula wrote: > I have a "Centennial MicroDrive", 340 Mb that does into a PCMCIA card > slot. Inserting it into the T23, I get these dmesg messages > > [ 6743.118863] wdc2 at pcmcia1 function 0: CARD> [ 6743.118863] wdc2: i/o mapped mode > [ 6743.618871] atabus2 at wdc2 channel 0 > [ 8339.023384] atabus2: detached > [ 8339.023384] wdc2: detached There should be a drive on that "atabus2", without the drive you can not access the card. Not sure why no drive is detected in your case. Martin
Re: DVD+R DL disk
Thanks On Sat, Jun 8, 2024 at 6:30 PM Brad Spencer wrote: > > Todd Gruhn writes: > > > Wow -- Thanks. > > > > > > I was playing with 'cd-info'. > > What can I use here? I did this: > > > > gandalf# cd-info > > cd-info > > cd-info version 2.1.0 x86_64--netbsd > > Copyright (c) 2003-2005, 2007-2008, 2011-2015, 2017 R. Bernstein > > This is free software; see the source for copying conditions. > > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > > PARTICULAR PURPOSE. > > CD location : /dev/rcd0d > > CD driver name: NetBSD > >access mode: no access method > > > > Vendor : ASUS > > Model : DRW-24F1ST d > > Revision: 1.00 > > Hardware : CD-ROM or DVD > > [snip] > > > Disc mode is listed as: DVD+R DL > > ++ WARN: error in ioctl(CDIOREADTOCHEADER): Invalid argument > > > > cd-info: Can't get first track number. I give up. > > gandalf# > > > > > I have never used cd-info... the output for the modes seems lacking... > there are more modes in the world than it mentions... just install > cdrecord and ask it (it supports everything from CDs to BR media and > pretty much all modes of DVD anything), or try to burn something greater > than 4.5GB and less than 8GB with cdrecord (a quirk in cdrecord is that > if your image you are burning would fit on a DVD+R media and you have a > DVD+R DL media in the drive, it will complain at you letting you know > that your image would fit on the smaller media and maybe not allow the > burn). Or, you can do a net search using your favorite search engine on > the model of the drive. A very brief search on 'DRW-24F1ST' shows that > device to be a multidrive and it appears to be able to deal with DVD+R > DL media just fine (newegg seems to think so, in any case). > > Since you have +R or +R DL media you will be doing the "take a image and > burn the whole thing" ... the same would be true for -R or -R DL media, > sort of thing. If you had +RW (especially) or -RW media (maybe) you > could get away with using growisofs (in the dvd+rw-tools package in > pkgsrc) that would let you append to the read/write media. > > > > -- > Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: DVD+R DL disk
Todd Gruhn writes: > Wow -- Thanks. > > > I was playing with 'cd-info'. > What can I use here? I did this: > > gandalf# cd-info > cd-info > cd-info version 2.1.0 x86_64--netbsd > Copyright (c) 2003-2005, 2007-2008, 2011-2015, 2017 R. Bernstein > This is free software; see the source for copying conditions. > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > PARTICULAR PURPOSE. > CD location : /dev/rcd0d > CD driver name: NetBSD >access mode: no access method > > Vendor : ASUS > Model : DRW-24F1ST d > Revision: 1.00 > Hardware : CD-ROM or DVD [snip] > Disc mode is listed as: DVD+R DL > ++ WARN: error in ioctl(CDIOREADTOCHEADER): Invalid argument > > cd-info: Can't get first track number. I give up. > gandalf# > I have never used cd-info... the output for the modes seems lacking... there are more modes in the world than it mentions... just install cdrecord and ask it (it supports everything from CDs to BR media and pretty much all modes of DVD anything), or try to burn something greater than 4.5GB and less than 8GB with cdrecord (a quirk in cdrecord is that if your image you are burning would fit on a DVD+R media and you have a DVD+R DL media in the drive, it will complain at you letting you know that your image would fit on the smaller media and maybe not allow the burn). Or, you can do a net search using your favorite search engine on the model of the drive. A very brief search on 'DRW-24F1ST' shows that device to be a multidrive and it appears to be able to deal with DVD+R DL media just fine (newegg seems to think so, in any case). Since you have +R or +R DL media you will be doing the "take a image and burn the whole thing" ... the same would be true for -R or -R DL media, sort of thing. If you had +RW (especially) or -RW media (maybe) you could get away with using growisofs (in the dvd+rw-tools package in pkgsrc) that would let you append to the read/write media. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: DVD+R DL disk
Wow -- Thanks. I was playing with 'cd-info'. What can I use here? I did this: gandalf# cd-info cd-info cd-info version 2.1.0 x86_64--netbsd Copyright (c) 2003-2005, 2007-2008, 2011-2015, 2017 R. Bernstein This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. CD location : /dev/rcd0d CD driver name: NetBSD access mode: no access method Vendor : ASUS Model : DRW-24F1ST d Revision: 1.00 Hardware : CD-ROM or DVD Can eject : Yes Can close tray: Yes Can disable manual eject : Yes Can select juke-box disc : No Can set drive speed : No Can read multiple sessions (e.g. PhotoCD) : Yes Can hard reset device : Yes Reading Can read Mode 2 Form 1 : Yes Can read Mode 2 Form 2 : Yes Can read (S)VCD (i.e. Mode 2 Form 1/2) : Yes Can read C2 Errors : Yes Can read IRSC : Yes Can read Media Channel Number (or UPC) : Yes Can play audio : Yes Can read CD-DA : Yes Can read CD-R : Yes Can read CD-RW : Yes Can read DVD-ROM: Yes Writing Can write CD-RW : Yes Can write DVD-R : Yes Can write DVD-RAM : Yes Can write DVD-RW: No Can write DVD+RW: No __ Disc mode is listed as: DVD+R DL ++ WARN: error in ioctl(CDIOREADTOCHEADER): Invalid argument cd-info: Can't get first track number. I give up. gandalf# On Sat, Jun 8, 2024 at 5:28 PM Brad Spencer wrote: > > Todd Gruhn writes: > > > This thing holds 8.6GB. > > > > How do I talk to it? Does my CD/DVD drive right to this? > > > > Can I only write 4.7GB to this thing? > > > cdrecord from pkgsrc will work just fine for these disks and you will be > able to use all of it. I use them all of the time. > > You more or less make a iso, udf or whatever image using whatever tool > you want and then use cdrecord to write the image onto the disk. > > > > -- > Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: DVD+R DL disk
Todd Gruhn writes: > This thing holds 8.6GB. > > How do I talk to it? Does my CD/DVD drive right to this? > > Can I only write 4.7GB to this thing? cdrecord from pkgsrc will work just fine for these disks and you will be able to use all of it. I use them all of the time. You more or less make a iso, udf or whatever image using whatever tool you want and then use cdrecord to write the image onto the disk. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
Re: strange issues with building ArcticFox - full rebuilds everytime
On Fri, 7 Jun 2024, Riccardo Mottola wrote: I actually executed in an xterm, interrupted after a couple of minutes and checked the scrollback - configure is rerun. This does not happen on linux or FreeBSD. OK. I have the cause and a workaround. You can do a proper fix based on it: It's the NetBSD shell, /bin/sh (and also /bin/ksh). On NetBSD's /bin/sh: LINENO RANDOM SECONDS START_TIME ToD change every time you do a `set' and so these will be different for every run of `mach build'. This is enough to cause a full rebuild. NetBSD's /bin/ksh has RANDOM and SECONDS. FreeBSD's /bin/sh has none of these. The same with dash(1) on Linux. bash(1) has LINENO RANDOM & SECONDS, but, it _doesn't_ expose it in a `set'. You have to ask for it explicitly--echo $SECONDS, etc--so `mach build' works correctly with bash too. Setting SHELL=/usr/pkg/bin/dash and CONFIG_SHELL=/usr/pkg/bin/dash doesn't seem to help at all, so the workaround is this: pkgin -y in dash cp /usr/pkg/bin/dash ~/bin/sh env PATH=$HOME/bin:$PATH ./mach build That causes dash(1) to be used always and everything seems to work without a full rebuild. HTH, -RVP
Re: Memory leaks in c/pthread libraries
On Thu, Jun 06, 2024 at 04:05:03PM +0200, J. Hannken-Illjes wrote: > > On 6. Jun 2024, at 00:55, Greg Troxel wrote: > > > > Brian Marcotte writes: > > > >> Since upgrading to NetBSD-10, we've seen memory leaks in several > >> daemons which use libpthread: > > > > > > > I am seeing the leak with gpg-agent and mariadbd. I don't run the rest > > on 10. > > For me it is spamass-milter. On an amd64, 10.0, 56 days up: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND > 387 root 85026G 236M poll/0 0:50 0.00% 0.00% > spamass-mil > > On amd64 a vsize of 26G is only nasty, on my i386 mail server the > milter dies every few days at ~2G :-) > > I have a small test (p2.c, attached) that shows the leak. It is > always a combination of pthread_create()/pthread_detach(). Using > pthread_join() instead of pthread_detach() doesn't have the problem. > > All started with this commit: > > https://mail-index.netbsd.org/source-changes/2020/01/27/msg113341.html > > Undoing part of this commit (diff attached) makes the leak disappear > for me. I'm not sure if this is fix or it just plasters another bug, > I'm not very familiar with the lwp lifecycle. > > At least I'm sure pthread__deadqueue fills with dead pthreads and > the mapped stacks are the memory leak observed. Ah-ha! Now I know why my toy code didn't replicate the issue - there's a required race between thread creates and exits. My code was effectively waiting for the child thread to exit before creating the next thread... Thanks for filling in the gap! -- Paul Ripke "Great minds discuss ideas, average minds discuss events, small minds discuss people." -- Disputed: Often attributed to Eleanor Roosevelt. 1948.
Re: strange issues with building ArcticFox - full rebuilds everytime
On Fri, 7 Jun 2024, Riccardo Mottola wrote: I actually executed in an xterm, interrupted after a couple of minutes and checked the scrollback - configure is rerun. This does not happen on linux or FreeBSD. Well, Linux systems usually have bash and a lot of the scripts in Arctic-Fox hard-code `#!/bin/bash'. And, as for FreeBSD, it's test(1) understands `==' as a synonym for `='. I noticed this failure too in the error messages. However, these may not be the issue at all: Just as an idea, I checked dates: -rwxr-xr-x 1 multix users 221 Jun 6 01:24 configure -rw-r--r-- 1 multix users 1154 Mar 5 01:29 configure.in -rw-r--r-- 1 multix users 873016 Jun 6 01:25 old-configure -rw-r--r-- 1 multix users 253669 Jun 6 01:19 old-configure.in the ".in" files are suspiciously new, as in the previous run. But I didn't update them. Comparing to linux, I see they are not touched since the last commit to them: -rwxr-xr-x 1 multix users 221 May 29 16:08 configure -rw-r--r-- 1 multix users 1154 Feb 19 11:24 configure.in -rw-r--r-- 1 multix users 874090 May 29 16:08 old-configure -rw-r--r-- 1 multix users 253669 May 29 15:30 old-configure.in the checked out repository is the same... Just to be sure, I yanked the build dir and retried. no avail. I tried to compile both the 44.0 release and the latest source, and while the build didn't get to the compile stage, rerunning `mach build' after it fails the first time doesn't trigger configure at all on my setup. Error log for the 2nd run attached (owing probably to some missing dependency which was not checked for; everything that `mach build' complained about, I installed from binary packages). If I do a `mach clobber', then confgure is, of course, re-run on the next `mach build'. -RVP err.log.gz Description: Arctic-Fox-master build error log.
Re: Memory leaks in c/pthread libraries
Oh, I haven't noticed that message. Good. Juergen, can you please commit the fix? Jaromir Le jeu. 6 juin 2024 à 23:32, Brian Marcotte a écrit : > > > @@ -457,11 +455,9 @@ pthread_create(pthread_t *thread, const > > [...] > > > > Can you try if the leak is gone if you only revert this part of the patch? > > That's the same as what J. Hannken-Illjes posted. I'm already using this > and I don't see any leaks yet. > > Thanks. > > -- > - Brian
Re: Add compatible laptops to the wiki
> Date: Thu, 6 Jun 2024 20:50:22 +0200 > From: Ramiro Aceves > > El 6/6/24 a las 18:56, Théophile Dudreuilh escribió: > > Hello, > > > > Hi Théophile, that would be a very good idea as the current Wiki page is > a bit poor. It would be nice when you are looking for a computer that > works fine in NetBSD. I use NetBSD on a ThinkPad with an NVIDIA sticker. It would be helpful to know there is a driver and that it is working correctly. -- vl
Re: pkg_rolling-replace and mismatched version
Hi, Greg Troxel wrote: I am pretty convinced that something is wrong with your system. just for the record. I had an obsolete |PKG_DBDIR| in |/etc/pkg_install.conf| set to /var/db/pkg That was probably the root of evil, of a half-assed transition - by miracle it worked until I tried to upgrade. Let's start from scratch! Riccardo
Re: pkg_rolling-replace and mismatched version
Hi, Greg Troxel wrote: Riccardo Mottola writes: sudo pkg_add -v /usr/packages/All/perl-5.38.2.tgz pkg_add: no pkg found for '/usr/packages/All/perl-5.38.2.tgz', sorry. pkg_add: 1 package addition failed -rw-r--r-- 1 root wheel 18M May 17 18:32 perl-5.38.2.tgz run "tar tfvz" on it and see what's inside. The archive is corrupted... not a valid tar file. That's not good I wonder if these SS4 and SS20 have stability issues. I removed the binary file, it will be rebuilt. Check that you have only one PKG_DBDIR (/usr/pkg/pkgdb, and not /var/db/pkg). I am pretty convinced that something is wrong with your system. I have both. Strange. I migrated all by boxen back then. I did some scary now: sudo rm -rf /var/db/pkg* sudo rm -rf /usr/pkg and I hope this is enough to start over make-installing each package from scratch. I will also discard binary packages created on this system for safety, since it could be inconsistent. Riccardo
Re: framebuffer console on old ATI
Hi Michael Michael wrote: did so. Still get a black screen. Before going black, I am able to see a "failed". Also, it hangs, because if I wait some time I can't login remotely (left dhcp on). This is odd, but it's a data point at least. Before trying to recompile the kernel once again, I tried external monitor with RADEON_BIOS_INIT It doesn't hang. I get some garbage blue pixels in the first lines of the screen, but e.g. caps-lock works! Powering down did not, so the machine did not complete a boot, but is not totally dead. This is different than without screen - there it is "dead". Does it hang without RADEONFB_BIOS_INIT as well? I recompiled a radeonfb* kernel again without init. Internal screen: freeze, no caps-lock action External screen: blue garbage on top of the screen, caps-lock active. Same behaviour as with init. If it doesn't and you just get no useful output - does the laptop in question have a VGA or DVI output? If it does, could you plug something into it? Yes it has classic VGA and I reported above how it behaves. The reason I'm asking is, most/maybe all radeons have at least two outputs, how they're wired to connectors, LCDs etc. is up to the vendors. Normally there is a table in the video BIOS telling us exactly what is connected to what. That's what RADEONFB_BIOS_INIT tries to find. If we get it wrong we may very well end up with a black display. On macppc we don't have a connector table but pretty much all *Books wire up the internal display in exactly the same way, there are a few exceptions but we can distinguish those from the model string in OF. Thats a possible explanation. Also it probably misdetects the external screen size The other possible cause would be some endianness screwup, radeonfb has been used mostly on macppc and sparc64, and not much else. IIRC some brave soul made it work on alpha a while ago, but it got pretty much zero testing on x86. That could be an explanation, if someone can check if it still works on alpha, we would have endianness information. So the machine probably doesn't have a video BIOS, just like most Apple *Books. Strange.. .it is a fairly standard Pentium4M PC which did run Windows XP... Does Xorg run with a radeon driver on any OS at all? If so, could you send me the xorg.0.log from such a thing? That should give at least a hint on what we get wrong. Xorg runs with NetBSD and default kernel. Log attached. It is only very very slow in startup, like blank screen with white cursor on top and for several seconds, then garbage... then mouse pointer. also xrand doesn't display a second monitor if attached.. never noticed since I didn't try, but since I was testing, I tried. I remember xrand displaying LVDS, VGA and such on other systems, here not. "default" and no monitor. Internal monitor is 1024x768 classic [ 646.081] (II) VESA(0): initializing int10 [ 646.082] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [ 646.096] (II) VESA(0): VESA BIOS detected [ 646.096] (II) VESA(0): VESA VBE Version 2.0 [ 646.096] (II) VESA(0): VESA VBE Total Mem: 16320 kB [ 646.096] (II) VESA(0): VESA VBE OEM: ATI MOBILITY RADEON 7500 [ 646.096] (II) VESA(0): VESA VBE OEM Software Rev: 1.0 [ 646.096] (II) VESA(0): VESA VBE OEM Vendor: ATI Technologies Inc. [ 646.096] (II) VESA(0): VESA VBE OEM Product: P7 [ 646.096] (II) VESA(0): VESA VBE OEM Product Rev: 01.00 [ 646.109] (II) VESA(0): virtual address = 0xaf80, VGAbase = 0xaf7f physical address = 0xe800, size = 16711680 [ 646.321] (II) VESA(0): Setting up VESA Mode 0x123 (1024x768) [ 648.893] (==) VESA(0): Default visual is TrueColor [ 649.210] (==) VESA(0): Backing store enabled [ 649.292] (==) VESA(0): DPMS enabled Riccardo [ 591.666] X.Org X Server 1.21.1.9 X Protocol Version 11, Revision 0 [ 591.667] Current Operating System: NetBSD orthanc.westernesse.arda 10.0 NetBSD 10.0 (GENERIC) #0: Thu Mar 28 08:33:33 UTC 2024 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/i386/compile/GENERIC i386 [ 591.667] [ 591.775] Current version of pixman: 0.38.4 [ 591.775] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 591.775] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 592.218] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 7 00:59:32 2024 [ 593.000] (II) Loader magic: 0xe59c80 [ 593.001] (II) Module ABI versions: [ 593.001] X.Org ANSI C Emulation: 0.4 [ 593.001] X.Org Video Driver: 25.2 [ 593.001] X.Org XInput driver : 24.4 [ 593.001] X.Org Server Extension : 10.0 [ 593.436] (--) PCI:*(1@1:0:0) 1002:4c57:1014:0517 rev 0, Mem @ 0xe800/134217728, 0xd010/65536, I/O @ 0x3000/256 [ 593.638] (==) Using default built-in configuration (39 lines) [ 593.638] (==) --- Start of built-in
Re: Memory leaks in c/pthread libraries
> @@ -457,11 +455,9 @@ pthread_create(pthread_t *thread, const > [...] > > Can you try if the leak is gone if you only revert this part of the patch? That's the same as what J. Hannken-Illjes posted. I'm already using this and I don't see any leaks yet. Thanks. -- - Brian
Re: pkg_rolling-replace and mismatched version
Riccardo Mottola writes: > sudo pkg_add -v /usr/packages/All/perl-5.38.2.tgz > pkg_add: no pkg found for '/usr/packages/All/perl-5.38.2.tgz', sorry. > pkg_add: 1 package addition failed > > -rw-r--r-- 1 root wheel 18M May 17 18:32 perl-5.38.2.tgz run "tar tfvz" on it and see what's inside. > Mystery is that lintpkgsrc did check: > > => Full dependency perl>=5.36: found perl-5.36.0 > But pkg_info told me it wasn't there.. how can this check pass? > > eowyn$ perl > -sh: perl: not found > > > I thus got perl from the prebuild binaries and installed it. Now > lintpgsrc is running... it will take some time on this oldie. But I > wonder what's going on. Check that you have only one PKG_DBDIR (/usr/pkg/pkgdb, and not /var/db/pkg). Check for directories in PKG_DBDIR that are empty, or otherwise irregular. find / -name perl and see if it is in /usr/local or some other place. I am pretty convinced that something is wrong with your system.
Re: strange issues with building ArcticFox - full rebuilds everytime
Hi, RVP wrote: My first guess is that configure is re-run unneeded, leading thus to a major recompile. You could make the 2nd & 3rd lines of configure this and confirm: echo >&2 dying... exit 1 I actually executed in an xterm, interrupted after a couple of minutes and checked the scrollback - configure is rerun. This does not happen on linux or FreeBSD. Just as an idea, I checked dates: -rwxr-xr-x 1 multix users 221 Jun 6 01:24 configure -rw-r--r-- 1 multix users 1154 Mar 5 01:29 configure.in -rw-r--r-- 1 multix users 873016 Jun 6 01:25 old-configure -rw-r--r-- 1 multix users 253669 Jun 6 01:19 old-configure.in the ".in" files are suspiciously new, as in the previous run. But I didn't update them. Comparing to linux, I see they are not touched since the last commit to them: -rwxr-xr-x 1 multix users 221 May 29 16:08 configure -rw-r--r-- 1 multix users 1154 Feb 19 11:24 configure.in -rw-r--r-- 1 multix users 874090 May 29 16:08 old-configure -rw-r--r-- 1 multix users 253669 May 29 15:30 old-configure.in the checked out repository is the same... Just to be sure, I yanked the build dir and retried. no avail. Riccardo
Re: pkg_rolling-replace and mismatched version
Hi! replying to myself. I wanted to run lintpkgsrc too I think maybe perl is missing? I have my locally build binary package. However, it doesn't install. sudo pkg_add -v /usr/packages/All/perl-5.38.2.tgz pkg_add: no pkg found for '/usr/packages/All/perl-5.38.2.tgz', sorry. pkg_add: 1 package addition failed -rw-r--r-- 1 root wheel 18M May 17 18:32 perl-5.38.2.tgz Mystery is that lintpkgsrc did check: => Full dependency perl>=5.36: found perl-5.36.0 But pkg_info told me it wasn't there.. how can this check pass? eowyn$ perl -sh: perl: not found I thus got perl from the prebuild binaries and installed it. Now lintpgsrc is running... it will take some time on this oldie. But I wonder what's going on. Riccardo
Re: pkg_rolling-replace and mismatched version
Hi Greg! thanks for replying... Greg Troxel wrote: It sounds like you are not having a pkg_rolling-replace problem, in that the underlying make replace does not work. Please see the pkg_rolling-replace man page where it asks that problems with a make replace (that was ordered reasonably) not be reported as pkg_rolling-replace issues. I didn't mean it is a pkg_rolling-replace issue, it is just started from that. If make replace itself fails, the problem is underlying. In this case it appears to do nothing. I thought the order of packages rebuilt could be wrong. I thought that perhaps the pkg tools need to be updated first? so I tried "make replace" in pkg_install => Automatic manual page handling => Generating post-install file lists => Checking file-check results for pkg_install-20240307 => Creating binary package /usr/pkg-workdir/pkgtools/pkg_install/work/.packages/pkg_install-20240307.tgz ===> Building binary package for pkg_install-20240307 => Creating binary package /usr/packages/All/pkg_install-20240307.tgz ===> Replacing for pkg_install-20240307 *** Error code 1 Stop. make[1]: stopped in /usr/pkgsrc/pkgtools/pkg_install *** Error code 1 Stop. make: stopped in /usr/pkgsrc/pkgtools/pkg_install this is for certain not a very helpful error! I would suggest checking your pkgdb (that you only have one, rebuild, rebuild-tree, check). I did build & rebuild, but since I manually removed some packages to ease the burden of upgrade, I reissued it. Didn't think to run check - good point. pkg_admin check finds issues: e.g. pkg_admin: x11-links-1.35: Symlink `/usr/pkg/share/x11-links/include/xorg/BT.h' exists and is in +CONTENTS but target does not exist! pkg_admin: x11-links-1.35: Symlink `/usr/pkg/share/x11-links/include/xorg/IBM.h' exists and is in +CONTENTS but target does not exist! but there are several failed checksums, e.g.: ../usr/pkg/lib/libffi.a fails MD5 checksum ./usr/pkg/bin/libtool fails MD5 checksum ./usr/pkg/lib/libpkgconf.a fails MD5 checksum ./usr/pkg/lib/libhistory.a fails MD5 checksum /usr/pkg/lib/libreadline.a fails MD5 checksum I rebuilt libtool and readline manually, they replaced fine! But still I cannot replace pkg_install Riccardo
Re: framebuffer console on old ATI
Hi John & Michael, since I borrowed the monitor of my workstation to do tests for radeonfb I also thougt to take the time and test what the radeondrm would do with an external monitor! set bool radeon_pci_ignore_r100_r200 = false; and recompile (commenting out radeonfb* just not to mix things up! At boot... I get a framebuffer high resolution console with a nice font! It is "correct" in size for the external 24" display and just displays a part clipped on the internal 13" display. Progress! Clearly, there is some display misdetection... it did not "switch" completely.. kind of bad mirroring, but with the resolution of the external one. It should have used internal resolution for mirror or drive only the external monitor. Monitor setup in BIOS is set to use VGA as default and that works for the BIOS and bootmanager. Try more? X11! Doesn't work. I get "ordered" garbage on the screen. Since the system is not stalled, I can telnet in and check dmesg. These appear at regular intevals [ 216.997284] radeon0: autoconfiguration error: error: ring 0 stalled for more than 82140msec [ 216.997284] radeon0: warn: GPU lockup (current fence id 0x0007 last fence id 0x002d on ring 0) [ 217.497291] radeon0: autoconfiguration error: error: ring 0 stalled for more than 82640msec [ 217.497291] radeon0: warn: GPU lockup (current fence id 0x0007 last fence id 0x002d on ring 0) [ 217.997299] radeon0: autoconfiguration error: error: ring 0 stalled for more than 83140msec [ 217.997299] radeon0: warn: GPU lockup (current fence id 0x0007 last fence id 0x002d on ring 0) out of test, I tried then rebooting again this radeon test kernl without external display, I get a perfect working internal console. It spits out this information [ 5.304228] [drm] initializing kernel modesetting (RV200 0x1002:0x4C57 0x1014:0x0517 0x00). [ 5.304228] [drm] register mmio base: 0xd010 [ 5.304228] [drm] register mmio size: 65536 [ 5.314229] radeon0: GTT: 64M 0xE000 - 0xE3FF [ 5.314229] radeon0: VRAM: 128M 0xE800 - 0xEFFF (16M used) [ 5.314229] [drm] Detected VRAM RAM=80M, BAR=128M [ 5.314229] [drm] RAM width 64bits DDR [ 5.314229] Zone kernel: Available graphics memory: 535062 KiB [ 5.314229] [drm] radeon: 16M of VRAM memory ready [ 5.314229] [drm] radeon: 64M of GTT memory ready. [ 5.314229] radeon0: WB disabled [ 5.324301] radeon0: fence driver on ring 0 use gpu addr 0xe000 and cpu addr 0x0xdb9a1000 [ 5.324301] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 5.324301] [drm] Driver supports precise vblank timestamp query. [ 5.324301] radeon0: interrupting at irq 11 (radeon0) [ 5.324301] [drm] radeon: irq initialized. [ 5.324301] [drm] Loading R100 Microcode [ 5.394230] [drm] radeon: ring at 0xE0001000 [ 5.394230] [drm] ring test succeeded in 1 usecs [ 5.404243] [drm] ib test succeeded in 0 usecs [ 5.404243] [drm] Panel ID String: 1024x768 [ 5.404243] [drm] Panel Size 1024x768 [ 5.404243] [drm] No TV DAC info found in BIOS [ 5.404243] [drm] Radeon Display Connectors [ 5.404243] [drm] Connector 0: [ 5.404243] [drm] VGA-1 [ 5.404243] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 5.404243] [drm] Encoders: [ 5.404243] [drm] CRT1: INTERNAL_DAC1 [ 5.404243] [drm] Connector 1: [ 5.404243] [drm] DVI-D-1 [ 5.404243] [drm] HPD1 [ 5.404243] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 5.404243] [drm] Encoders: [ 5.404243] [drm] DFP1: INTERNAL_TMDS1 [ 5.404243] [drm] Connector 2: [ 5.404243] [drm] LVDS-1 [ 5.404243] [drm] Encoders: [ 5.404243] [drm] LCD1: INTERNAL_LVDS [ 5.404243] [drm] Connector 3: [ 5.404243] [drm] SVIDEO-1 [ 5.404243] [drm] Encoders: [ 5.404243] [drm] TV1: INTERNAL_DAC2 [ 5.444234] radeondrmkmsfb0 at radeon0 [ 5.444234] [drm] Initialized radeon 2.50.0 20080528 for radeon0 on minor 0 [ 5.444234] radeondrmkmsfb0: framebuffer at 0xe804, size 1024x768, depth 16, stride 2048 [ 5.544232] wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 what changed ot my first test? I don't know.. except I took the care to disable nouveau... but that shouldn't matter Interestingly here we see 4 connectors... but I only have VGA and SVIDEO as ports, so I guess DVI is internal? no HDMI/DVI port available and we don't know what is being used. X11 with internal video? it comes up fairly quickly (compared to the standard kernel, where I report that it does work, but takes a long time with a black screen, some garbage...) and I get a working mousr cursor on a black backround, nothing else telnet in and dmesg shows: [ 253.288036] radeon0: warn: GPU lockup (current fence id
Re: Memory leaks in c/pthread libraries
Most of the patch I don't understand, but this seems like this might
be causing some leaks:
@@ -457,11 +455,9 @@ pthread_create(pthread_t *thread, const
if (!PTQ_EMPTY(__deadqueue)) {
pthread_mutex_lock(__deadqueue_lock);
PTQ_FOREACH(newthread, __deadqueue, pt_deadq) {
- /* Still running? */
+ /* Still busily exiting, or finished? */
if (newthread->pt_lwpctl->lc_curcpu ==
- LWPCTL_CPU_EXITED ||
- (_lwp_kill(newthread->pt_lid, 0) == -1 &&
- errno == ESRCH))
+ LWPCTL_CPU_EXITED)
break;
}
if (newthread)
Can you try if the leak is gone if you only revert this part of the patch?
Jaromir
Le jeu. 6 juin 2024 à 20:13, Brian Marcotte a écrit :
>
> > All started with this commit:
> >
> > https://mail-index.netbsd.org/source-changes/2020/01/27/msg113341.html
> >
> > Undoing part of this commit (diff attached) makes the leak disappear
>
> I'm trying this now. I can already see it's helping these:
>
> gpg-agent
> opendmarc
> dkimpy_milter (python3)
>
> I'm also trying it with mariadb, but it may take a few days to see if
> the leak is gone.
>
> Thanks for looking into this.
>
> --
> - Brian
>
Re: Add compatible laptops to the wiki
El 6/6/24 a las 18:56, Théophile Dudreuilh escribió: Hello, Hi Théophile, that would be a very good idea as the current Wiki page is a bit poor. It would be nice when you are looking for a computer that works fine in NetBSD. We wait for the experts to answer. Regards. I would like to know if it is possible to add laptops to the list on the wiki (https://wiki.netbsd.org/laptops/). I have several laptops that are relatively compatible with NetBSD 10.0, and it would be nice to have a slightly refreshed list for x64. Here is the hw-probe link for the test I did on Dell Precision 7520 i7-7920HQ a few months ago, among others. https://bsd-hardware.info/?probe=48232bd1d6 Ethernet, Wifi, Display, Sound... All basic functionalities are OK on these laptops (the 7720 i7-7820HQ and i7-7920HQ are good too). As always, disable "Switchable Graphics" in UEFI/BIOS beforehand... I have plenty of other laptops that run well, for which I will publish the tests on bsdhardware if needed. I regularly test quite a lot of hardware. Best regards, Théophile Dudreuilh (majekla on UnitedBSD)
Re: Memory leaks in c/pthread libraries
> All started with this commit: > > https://mail-index.netbsd.org/source-changes/2020/01/27/msg113341.html > > Undoing part of this commit (diff attached) makes the leak disappear I'm trying this now. I can already see it's helping these: gpg-agent opendmarc dkimpy_milter (python3) I'm also trying it with mariadb, but it may take a few days to see if the leak is gone. Thanks for looking into this. -- - Brian
Re: Memory leaks in c/pthread libraries
> On 6. Jun 2024, at 00:55, Greg Troxel wrote: > > Brian Marcotte writes: > >> Since upgrading to NetBSD-10, we've seen memory leaks in several >> daemons which use libpthread: > > > I am seeing the leak with gpg-agent and mariadbd. I don't run the rest > on 10. For me it is spamass-milter. On an amd64, 10.0, 56 days up: PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND 387 root 85026G 236M poll/0 0:50 0.00% 0.00% spamass-mil On amd64 a vsize of 26G is only nasty, on my i386 mail server the milter dies every few days at ~2G :-) I have a small test (p2.c, attached) that shows the leak. It is always a combination of pthread_create()/pthread_detach(). Using pthread_join() instead of pthread_detach() doesn't have the problem. All started with this commit: https://mail-index.netbsd.org/source-changes/2020/01/27/msg113341.html Undoing part of this commit (diff attached) makes the leak disappear for me. I'm not sure if this is fix or it just plasters another bug, I'm not very familiar with the lwp lifecycle. At least I'm sure pthread__deadqueue fills with dead pthreads and the mapped stacks are the memory leak observed. -- J. Hannken-Illjes - hann...@mailbox.org p2.c Description: Binary data 001_pthread_revert.diff Description: Binary data signature.asc Description: Message signed with OpenPGP
Re: pkg_rolling-replace and mismatched version
It sounds like you are not having a pkg_rolling-replace problem, in that the underlying make replace does not work. Please see the pkg_rolling-replace man page where it asks that problems with a make replace (that was ordered reasonably) not be reported as pkg_rolling-replace issues. I would suggest checking your pkgdb (that you only have one, rebuild, rebuild-tree, check). Also, when you upgrade NetBSD from 9 to 10, you can run old packages, but you cannot (soundly, in general) run a mixed package set. So you need to mark all packages rebuild=YES or do something equivalent.
Re: Memory leaks in c/pthread libraries
Brian Marcotte writes: > Since upgrading to NetBSD-10, we've seen memory leaks in several > daemons which use libpthread: > > gpg-agent > opendmarc > dkimpy_milter (python3) > syslog-ng (in some cases) > mysqld > mariadbd > > In most cases, the daemons leak as they are used, but running this > will show the leak just sitting there: > > gpg-agent --daemon > > I opened PR#57831 on this issue back in January. > > Has anyone noticed this? I am seeing the leak with gpg-agent and mariadbd. I don't run the rest on 10. gpg-agent had a SIZE of 17G with a reasonable rss, after 2h21h of uptime. This is a machine where gpg is basically not in used. So it's pretty bad. And, on a RPI4 also with 10: 4212 mariadb 850 3734M 130M poll/0145:16 0.00% 0.00% mariadbd since 26May. bad, but not nearly as much.
Re: conditional nat using ! negation
thank you,
I haven't tried it yet, because my original intention was to use NetBSD
npf instead of FreeBSD pf in a large environment (HPC datacenter),
this because apparently npf can take advantage of multi-core CPUs way
better than PF on other *BSD systems.
I will test it and see if the negation effectively works.
Thanks a lot
Rick
On 6/1/24 1:24 PM, Martin Husemann wrote:
On Wed, May 29, 2024 at 11:33:28AM +0200, fddi wrote:
So for example, nat any clients from 172.16.10.0/23, 172.16.1.0/24 to any
desination NOT matching 131.241.0.0/16, thus traffic to 131.241.0.0/16 is
supposed to be routed and not natted.
$pub_if = "vioif0"
map $pub_if dynamic any -> inet4($pub_if) pass family inet4 from {
172.16.10.0/23, 172.16.1.0/24 } to ! 131.241.0.0/16
but this is what "npfctl validate" or "npfctl show" is showing:
map vioif0 dynamic any -> 131.154.4.29 pass family inet4 from {
172.16.10.0/23, 172.16.1.0/24 } to 131.241.0.0/16
The negation mark (!) is ignored
At quick glance it seems the generated bpf byte code is correct, but the
pretty printer used in "validate" and "show" misses the destination inversion
option (there is code that should show it, but it seems to be buggy).
You can see the difference between the version with and without the ! by
doing something like:
npfctl debug -c npf.conf > out.neg
then removing the ! and try again:
npfctl debug -c npf.conf > out.positive
and then diff -u the two out.* files.
Have you tried if your NAT works?
Please file a PR with the details, there defintively is a bug if
"show" or "validate" don't show a rule that could be used for input.
Martin
Re: conditional nat using ! negation
On Wed, May 29, 2024 at 11:33:28AM +0200, fddi wrote:
> So for example, nat any clients from 172.16.10.0/23, 172.16.1.0/24 to any
> desination NOT matching 131.241.0.0/16, thus traffic to 131.241.0.0/16 is
> supposed to be routed and not natted.
>
> $pub_if = "vioif0"
> map $pub_if dynamic any -> inet4($pub_if) pass family inet4 from {
> 172.16.10.0/23, 172.16.1.0/24 } to ! 131.241.0.0/16
>
> but this is what "npfctl validate" or "npfctl show" is showing:
>
> map vioif0 dynamic any -> 131.154.4.29 pass family inet4 from {
> 172.16.10.0/23, 172.16.1.0/24 } to 131.241.0.0/16
>
> The negation mark (!) is ignored
At quick glance it seems the generated bpf byte code is correct, but the
pretty printer used in "validate" and "show" misses the destination inversion
option (there is code that should show it, but it seems to be buggy).
You can see the difference between the version with and without the ! by
doing something like:
npfctl debug -c npf.conf > out.neg
then removing the ! and try again:
npfctl debug -c npf.conf > out.positive
and then diff -u the two out.* files.
Have you tried if your NAT works?
Please file a PR with the details, there defintively is a bug if
"show" or "validate" don't show a rule that could be used for input.
Martin
Re: Memory leaks in c/pthread libraries
On Thu, May 23, 2024 at 03:09:02PM -0400, Brian Marcotte wrote: > Since upgrading to NetBSD-10, we've seen memory leaks in several > daemons which use libpthread: > > gpg-agent > opendmarc > dkimpy_milter (python3) > syslog-ng (in some cases) > mysqld > mariadbd > > In most cases, the daemons leak as they are used, but running this > will show the leak just sitting there: > > gpg-agent --daemon > > I opened PR#57831 on this issue back in January. > > Has anyone noticed this? I haven't noticed this in anything I run; but I can replicate your findings with `gpg-agent --daemon`. ktruss shows it's doing an internal health check, which requires creating a couple of detached pthreads, seems to wait/post on a POSIX semaphore, not much else of interest - and leaks ~20KiB per cycle. I couldn't replicate any leaks in some toy code that creates detached threads and similar ops on a POSIX semaphore; nor could I figure out how to do any useful jemalloc tracing. I can't figure out what it's doing that's triggering the leak. This is on netbsd-10, amd64, btw. -- Paul Ripke "Great minds discuss ideas, average minds discuss events, small minds discuss people." -- Disputed: Often attributed to Eleanor Roosevelt. 1948.
Re: framebuffer console on old ATI
On Thu 30 May 2024 at 10:44:10 -0400, Michael wrote: > Does Xorg run with a radeon driver on any OS at all? If so, could you > send me the xorg.0.log from such a thing? That should give at least a > hint on what we get wrong. With NetBSD 9 I used to run my amd64 machine with Driver "radeon" and that worked perfectly. That was with a Radeon HD 5450. With 10, I tried that at the start as well but there were some problems[1] so I switched to Driver "modesetting". (Which had different problems but they are fixed in -current) I don't think I have a Xorg.0.log from that, but I do have a Xorg.1.log where I ran the Xorg from 9 on 10, with radeon driver (or it might have been the "ati" driver, but I've been told that it just indirects to one of three other drivers, such as radeon). I appended it below, in case it is useful. [1] I forgot the details [285668.319] X.Org X Server 1.20.5 X Protocol Version 11, Revision 0 [285668.319] Build Operating System: NetBSD/amd64 9.3 - The NetBSD Foundation, Inc. [285668.319] Current Operating System: NetBSD murthe.falu.nl 10.0 NetBSD 10.0 (GENERIC) #0: Thu Mar 28 08:33:33 UTC 2024 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 [285668.319] Build Date: 03 March 2019 07:11:23AM [285668.319] [285668.319] Current version of pixman: 0.38.4 [285668.319]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [285668.319] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [285668.319] (==) Log file: "/var/log/Xorg.1.log", Time: Wed May 1 21:21:11 2024 [285668.320] (==) Using config file: "/etc/X11/xorg.conf" [285668.320] (==) ServerLayout "X.org Configured" [285668.320] (**) |-->Screen "Screen0" (0) [285668.320] (**) | |-->Monitor "Monitor0" [285668.320] (**) | |-->Device "Card0" [285668.320] (**) |-->Input Device "Mouse0" [285668.320] (**) |-->Input Device "Keyboard0" [285668.320] (**) Option "DontZap" "false" [285668.320] (**) Option "DontZoom" "false" [285668.320] (**) Option "DisableVidModeExtension" "false" [285668.320] (==) Not automatically adding devices [285668.320] (==) Not automatically enabling devices [285668.320] (==) Not automatically adding GPU devices [285668.320] (==) Max clients allowed: 256, resource mask: 0x1f [285668.320] (WW) The directory "/usr/pkg/lib/X11/fonts/TTF" does not exist. [285668.320]Entry deleted from font path. [285668.320] (WW) The directory "/usr/pkg/lib/X11/fonts/misc/" does not exist. [285668.320]Entry deleted from font path. [285668.320] (WW) The directory "/usr/pkg/lib/X11/fonts/Type1/" does not exist. [285668.320]Entry deleted from font path. [285668.320] (WW) The directory "/usr/pkg/lib/X11/fonts/75dpi/" does not exist. [285668.320]Entry deleted from font path. [285668.320] (WW) The directory "/usr/pkg/lib/X11/fonts/100dpi/" does not exist. [285668.320]Entry deleted from font path. [285668.320] (**) FontPath set to: /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/, /usr/local/X11/fonts/TrueType/beos, /usr/local/X11/fonts/TrueType/enabled, /usr/pkg/share/fonts/X11/misc, /usr/pkg/share/fonts/X11/TTF, /usr/X11R7/lib/X11/fonts/misc/, /usr/X11R7/lib/X11/fonts/TTF/, /usr/X11R7/lib/X11/fonts/Type1/, /usr/X11R7/lib/X11/fonts/75dpi/, /usr/X11R7/lib/X11/fonts/100dpi/ [285668.320] (**) ModulePath set to "/usr/X11R7/lib/modules" [285668.320] (II) Loader magic: 0x1b308fa60 [285668.320] (II) Module ABI versions: [285668.320]X.Org ANSI C Emulation: 0.4 [285668.320]X.Org Video Driver: 24.0 [285668.320]X.Org XInput driver : 24.1 [285668.320]X.Org Server Extension : 10.0 [285668.327] (--) PCI:*(1@1:0:0) 1002:68f9:1002:010a rev 0, Mem @ 0x9000/268435456, 0xa022/131072, I/O @ 0x3000/256, BIOS @ 0x/131072 [285668.327] (II) "glx" will be loaded. This was enabled by default and also specified in the config file. [285668.327] (II) LoadModule: "dbe" [285668.327] (II) Module "dbe" already built-in [285668.327] (II) LoadModule: "dri" [285668.327] (II) Module "dri" already built-in [285668.327] (II) LoadModule: "extmod" [285668.327] (II) Module "extmod" already built-in [285668.327] (II) LoadModule: "glx" [285668.327] (II) Loading /usr/X11R7/lib/modules/extensions/libglx.so [285668.327] (II) Module glx: vendor="X.Org Foundation" [285668.327]compiled for 1.20.5, module version = 1.0.0 [285668.327]ABI class: X.Org Server Extension, version 10.0 [285668.327] (II) LoadModule: "record" [285668.327] (II) Module "record" already built-in [285668.327] (II) LoadModule: "shadow" [285668.328] (II) Loading
Re: NetBSD 10.0 installation cd boot hangs
On Thu, 30 May 2024, e...@tilde.team wrote: On Tue, May 28, 2024 at 08:51:00PM +, RVP wrote: In your BIOS, can switch the drive controller to `AHCI' instead of whatever it is now (probably IDE)? -RVP It is a SATA drive, and no opportunities to change anything regarding the drive in the BIOS. Not the drive: change the drive-controller mode if possible. The `ahcisata' driver should get used here rather than `viaide', I think. -RVP
Re: HAXM + NVMM is doable ?
On Thu, 30 May 2024 at 16:41, Mario Marietto wrote: > > At the moment , can NVMM be used in conjunction with QEMU as an > accelerator ? I use it all the time on -current. > > On Thu, May 30, 2024 at 3:41 PM James Cave wrote: >> >> Hi, Mario, >> >> Intel discontinued development of HAXM last year because all the >> major operating systems include hypervisor backends of their own. >> As a result, QEMU removed the HAXM backend in version 8.2. >> >> Looking at pkgsrc.se, I see that the CVS log for the emulators/haxm >> package mentions a quick fix to get it to build on an old version >> of -current, but also mentions that "this package seems to have >> other potential issues." I wouldn't expect it to work well with >> NetBSD 10. >> >> ~ James > > > > -- > Mario. --
Re: HAXM + NVMM is doable ?
At the moment , can NVMM be used in conjunction with QEMU as an accelerator ? On Thu, May 30, 2024 at 3:41 PM James Cave wrote: > Hi, Mario, > > Intel discontinued development of HAXM last year because all the > major operating systems include hypervisor backends of their own. > As a result, QEMU removed the HAXM backend in version 8.2. > > Looking at pkgsrc.se, I see that the CVS log for the emulators/haxm > package mentions a quick fix to get it to build on an old version > of -current, but also mentions that "this package seems to have > other potential issues." I wouldn't expect it to work well with > NetBSD 10. > > ~ James > -- Mario.
Re: framebuffer console on old ATI
Hello, On Thu, 23 May 2024 09:11:17 + Riccardo Mottola wrote: > Michael wrote: > > Did it crash or did if continue booting? If it continued to boot > > radeonfb likely got the wiring of outputs to displays wrong. > > With that, please try with options RADEONFB_BIOS_INIT, which adds code > > to scan the BIOS for output info. This is not enabled by default > > because most hardware we run radeonfb on doesn't have a PC BIOS. Should > > probably be on by default on x86. > > did so. Still get a black screen. Before going black, I am able to see a > "failed". > Also, it hangs, because if I wait some time I can't login remotely (left > dhcp on). This is odd, but it's a data point at least. Does it hang without RADEONFB_BIOS_INIT as well? If it doesn't and you just get no useful output - does the laptop in question have a VGA or DVI output? If it does, could you plug something into it? The reason I'm asking is, most/maybe all radeons have at least two outputs, how they're wired to connectors, LCDs etc. is up to the vendors. Normally there is a table in the video BIOS telling us exactly what is connected to what. That's what RADEONFB_BIOS_INIT tries to find. If we get it wrong we may very well end up with a black display. On macppc we don't have a connector table but pretty much all *Books wire up the internal display in exactly the same way, there are a few exceptions but we can distinguish those from the model string in OF. I know RADEONFB_BIOS_INIT works on macppc because I have an r360 card with both OF and a PC BIOS in ROM, and with it radeonfb correctly identifies both outputs as DVI. The other possible cause would be some endianness screwup, radeonfb has been used mostly on macppc and sparc64, and not much else. IIRC some brave soul made it work on alpha a while ago, but it got pretty much zero testing on x86. > thanks to easy videos with iPhones... I was able to extract a frame: > > radeonfb0: BIOS initialization failed So the machine probably doesn't have a video BIOS, just like most Apple *Books. Does Xorg run with a radeon driver on any OS at all? If so, could you send me the xorg.0.log from such a thing? That should give at least a hint on what we get wrong. have fun Michael
Re: HAXM + NVMM is doable ?
Hi, Mario, Intel discontinued development of HAXM last year because all the major operating systems include hypervisor backends of their own. As a result, QEMU removed the HAXM backend in version 8.2. Looking at pkgsrc.se, I see that the CVS log for the emulators/haxm package mentions a quick fix to get it to build on an old version of -current, but also mentions that "this package seems to have other potential issues." I wouldn't expect it to work well with NetBSD 10. ~ James
Re: NetBSD 10.0 installation cd boot hangs
On Tue, May 28, 2024 at 01:26:53PM +0100, Stephen Borrill wrote: > On Mon, 27 May 2024, e...@tilde.team wrote: > > > On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote: > I think Benny meant ? at the boot device: prompt, not the boot prompt. We > know that the boot loader can read the CD as it has loaded the kernel. Your > problem with this is the next paragraph though: > OK, I understand now. I wasn't sure if the 'boot device:' was a prompt, but it make sense. > Yes, this has been a problem since I don't know when. USB keyboards often > fail to operate at this point. Without a PS/2 keyboard (or serial console), > you may be stuck. I see. The computer is unfortunately to new to have any PS/2 ports, serial console might be better. The amd64 installation CD does not have serial console support by default it seems? > > You could try an older installation CD for laughs. In the olden days, the > installation ramdisk was embedded in the INSTALL kernel, so at least it > would start even if you couldn't read the install sets from the CD. > > You could try loading amd64/installation/miniroot/miniroot.kmod from the > boot loader. > > Or just boot from USB... > I just did that. I cannot boot from a USB memory stick (the BIOS does not seem to be able to?); but I can boot from a USB CD drive that I had lying around. Booting from that progresses a bit further than the earlier impasse, but eventually ends with a kernel panic. I'm happy to supply further details if anyone is interested, but I don't think I can figure this out myself. > > I don't know where 'fd1' comes from - there is only one floppy drive. > > Not sure, but it wouldn't surprise if those were hard-wired in on the BIOS That would make sense. /Emil
Re: NetBSD 10.0 installation cd boot hangs
On Tue, May 28, 2024 at 08:51:00PM +, RVP wrote: > On Thu, 23 May 2024, e...@tilde.team wrote: > > > [ 301.7983080] waiting for devices: atabus1 atabus2 atabus3 > > viaide0 channel 1: reset failed for drive 0 > > > > In your BIOS, can switch the drive controller to `AHCI' instead of whatever > it is now (probably IDE)? > > -RVP It is a SATA drive, and no opportunities to change anything regarding the drive in the BIOS. Emil
Re: strange issues with building ArcticFox - full rebuilds everytime
On Tue, 28 May 2024, Riccardo Mottola wrote: My first guess is that configure is re-run unneeded, leading thus to a major recompile. Any ideas? You could make the 2nd & 3rd lines of configure this and confirm: echo >&2 dying... exit 1 -RVP
Re: ffmpeg6 drawtext option question
Hello, Thank you very much for the heads up on this. I will go ahead and recompile. In the meantime I read around a bit and found a work around by using ffmpeg instead of ffmpeg6. The necessary features for what I needed are apparently compiled in by default so it just works out of the box. On 28/05/24 at 08:40P, RVP wrote: On Tue, 28 May 2024, Michael Lowery Wilson wrote: However, I get the below result instead: [AVFilterGraph @ 0x7eb5fb57f580] No such filter: 'drawtext' [vost#0:0/libx264 @ 0x7eb5fb53a500] Error initializing a simple filtergraph Error opening output file timestamped-recording.mp4. That error message is correct; there's no `drawtext' filter compiled in: $ ffmpeg6 -filters 2>&1 | fgrep drawtext $ Which points toward an issue with the drawtext filter. I have checked and my version of ffmpeg6 is compiled with the --enable-libfreetype flag by default, which is required for the drawtext filter: https://ayosec.github.io/ffmpeg-filters-docs/3.3.9/Filters/Video/drawtext.html According to the current docs. you also need `--enable-libharfbuzz' now: https://ffmpeg.org/ffmpeg-filters.html#drawtext-1 Can you recompile with libharfbuzz added, then tell the pkgsrc folks if that works? -RVP Michael
Re: View / test *-ttf fonts
Another way is to use xfontsel -scaled The -scaled option allows you to choose the sizes for scaled fonts, which usually list their sizes as 0. > On May 25, 2024, at 3:05 PM, Todd Gruhn wrote: > > It did not impress me. > > It shows me that I can see all the characters. > > I can't see what a font looks like, are different sizes. > > Now do I see / test this? > > On Sat, May 25, 2024 at 8:22 PM Thomas D. Dean wrote: >> >> On 5/25/24 07:22, Todd Gruhn wrote: >>> Is there a way to view the *-ttf fonts? >>> So I know what it will look like ... >> >> xfd >> >> Tom Dean >>
Re: NetBSD 10.0 installation cd boot hangs
On Thu, 23 May 2024, e...@tilde.team wrote: [ 301.7983080] waiting for devices: atabus1 atabus2 atabus3 viaide0 channel 1: reset failed for drive 0 In your BIOS, can switch the drive controller to `AHCI' instead of whatever it is now (probably IDE)? -RVP
Re: ffmpeg6 drawtext option question
On Tue, 28 May 2024, Michael Lowery Wilson wrote: However, I get the below result instead: [AVFilterGraph @ 0x7eb5fb57f580] No such filter: 'drawtext' [vost#0:0/libx264 @ 0x7eb5fb53a500] Error initializing a simple filtergraph Error opening output file timestamped-recording.mp4. That error message is correct; there's no `drawtext' filter compiled in: $ ffmpeg6 -filters 2>&1 | fgrep drawtext $ Which points toward an issue with the drawtext filter. I have checked and my version of ffmpeg6 is compiled with the --enable-libfreetype flag by default, which is required for the drawtext filter: https://ayosec.github.io/ffmpeg-filters-docs/3.3.9/Filters/Video/drawtext.html According to the current docs. you also need `--enable-libharfbuzz' now: https://ffmpeg.org/ffmpeg-filters.html#drawtext-1 Can you recompile with libharfbuzz added, then tell the pkgsrc folks if that works? -RVP
Re: Fontconfig and variable fonts
On Tue 28 May 2024 at 16:38:04 +0300, Valery Ushakov wrote: > Arch wiki has e.g. (haven't tried it myself): > > > https://wiki.archlinux.org/title/Font_configuration/Examples#Enable_typographic_features Ah, interesting find, thank you! "Features" are somewhat similar to "variables". So one hope that somehow this can be specified in a font name, so it can be used in naive programs that only really know about a font name and perhaps a size. The font I am interested in by way of example is Recursive, from https://www.recursive.design/ . It has 5 font "variations" (where you can select some value along an interval of an "axis") and some 24 "features" (essentially boolean variations, one can think). The two programs I'm (again by ways of example) I'm interested in are XTerm and Vim (gtk2 or 3). It turns out that XTerm uses fontconfig directly but Vim uses pango. And they have different syntax for font names... E.g. font size: "FooFont-10" for fontconfig; "FooFont 10" for pango. "FooFont:matrix=0.9 0 0 1" for setting a transformation matrix in fontconfig. This doesn't seem to be possible with pango. For font variations, https://docs.gtk.org/Pango/type_func.FontDescription.from_string.html says it's "Cantarell Italic Light 15 `wght`=200", but that isn't true. It is actually "Cantarell Italic Light 15 @wght=200" as can be in the pango source code if you search for pango_font_description_from_string. pango-view --text "Hello, world!" --font 'Recursive 30 @CASL=0.5,slnt=-20' seems to work, but if I use such a font name in Vim :set guifont=Recursive\ 10\ @slnt=-10,wght=800 then somehow only the first variation seems to be taken into account. Maybe the variations can be specified in the xml fontconfig file in a way similar to the features... > -uwe -Olaf. -- ___ Olaf 'Rhialto' Seibert \X/ There is no AI. There is just someone else's work. --I. Rose signature.asc Description: PGP signature
Re: Fontconfig and variable fonts
On Sun, May 26, 2024 at 22:32:13 +0200, Rhialto wrote: > But is it actually documented anywhere how this can be used? I have > searched for years (literally) and never found even a hint. Nothing > at all. Arch wiki has e.g. (haven't tried it myself): https://wiki.archlinux.org/title/Font_configuration/Examples#Enable_typographic_features -uwe
Re: NetBSD 10.0 installation cd boot hangs
On Mon, 27 May 2024, e...@tilde.team wrote: On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote: On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote: This is technically not a hang. The kernel did not find the device to boot from, so it is waiting for you to enter one. Are you expecting the device on the SATA bus? -- Benny I guess it should show up in the viaide controller, but: viaide0 channel 1: reset failed for drive 0 says it did not work well. You could try to list the available devices by entering ? at the boot prompt (but I guess your CD will be missing). Thanks both. My understanding of the boot process is rudimentary, so I don't quite uniderstand this: Somehow it does find the boot device (in some sense) since it does start the boot process - so why is it complaining about the "boot device: "? I think Benny meant ? at the boot device: prompt, not the boot prompt. We know that the boot loader can read the CD as it has loaded the kernel. Your problem with this is the next paragraph though: Also: I don't know if it has technically hanged, but I cannot type anything (even though there is a cursor at the end of "root device: " and the computer is not responding to any keyboard input that I have tried, so I have to hard restart it by pressing the power button for a long time. Yes, this has been a problem since I don't know when. USB keyboards often fail to operate at this point. Without a PS/2 keyboard (or serial console), you may be stuck. You could try an older installation CD for laughs. In the olden days, the installation ramdisk was embedded in the INSTALL kernel, so at least it would start even if you couldn't read the install sets from the CD. You could try loading amd64/installation/miniroot/miniroot.kmod from the boot loader. Or just boot from USB... typing 'dev' at the boot prompt gives the following output: disk hd0 size 223 GB disk fd0 fd0a disk fd1 fd1a default cd0a I don't know where 'fd1' comes from - there is only one floppy drive. Not sure, but it wouldn't surprise if those were hard-wired in on the BIOS. -- Stephen
Re: NetBSD 10.0 installation cd boot hangs
On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote: > On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote: > > This is technically not a hang. The kernel did not find the device to boot > > from, so it is waiting for you to enter one. Are you expecting the device on > > the SATA bus? -- Benny > > > > I guess it should show up in the viaide controller, but: > > > viaide0 channel 1: reset failed for drive 0 > > says it did not work well. > > You could try to list the available devices by entering > > ? > > at the boot prompt (but I guess your CD will be missing). Thanks both. My understanding of the boot process is rudimentary, so I don't quite uniderstand this: Somehow it does find the boot device (in some sense) since it does start the boot process - so why is it complaining about the "boot device: "? Also: I don't know if it has technically hanged, but I cannot type anything (even though there is a cursor at the end of "root device: " and the computer is not responding to any keyboard input that I have tried, so I have to hard restart it by pressing the power button for a long time. typing 'dev' at the boot prompt gives the following output: disk hd0 size 223 GB disk fd0 fd0a disk fd1 fd1a default cd0a I don't know where 'fd1' comes from - there is only one floppy drive. /Emil
Re: cvs and older versions of a file
On 5/26/24 12:03, Todd Gruhn wrote: I messed up a .Xresources . How do I tell cvs to give me a previous copy? Did you set up cvs to track your .Xresources file? Or are you referring to a specific resource file from NetBSD? I just want to make sure before you get a long thread of helpful people that answer the exact question (how to revert a change), but miss the broader picture as it were :-) Staffan OpenPGP_signature.asc Description: OpenPGP digital signature
Re: View / test *-ttf fonts
> Am 25.05.2024 um 20:23 schrieb Todd Gruhn : > > Is there a way to view the *-ttf fonts? > So I know what it will look like ... I think gfontsel (part of Gtk) allows you to select and preview a font. Now what would be cool is if there were a preview on pkgsrc.se :) -- Benny
Re: GTX-1660 prob
On Sat, 16 Dec 2023 14:49:22 + Todd Gruhn wrote: > I thing I found it in dmesg.root: > > NVIDIA product 1aed (miscellaneous serial bus, revision 0xa1) at pci1 > dev 0 function 3 not configured > > S, what is it? > How do I fix it? You have to look-up in the support matrix if we've gotten support for it/wait that we do. But nouveau is enabled by default so I think we just don't I don't know if it is supported upstream (i.e. on Linux) yet (nor will be, there is that too :/ It's long shot, but I don't know if Sylpheed AND I have to re-subscribe to the list :p) Cheers, Hope it helps! -- Germain Le Chapelain
Re: View / test *-ttf fonts
On Sat, May 25, 2024 at 02:22:30PM +, Todd Gruhn wrote: Is there a way to view the *-ttf fonts? So I know what it will look like ... The only way I know of is using xclock(1), for example: % xclock -geometry 720x60+50+260 \ -digital -face "FONT NAME:pixelsize=40" \ -render -update 5 -bg white -fg black HTH
Re: View / test *-ttf fonts
On Sat 25 May 2024 at 19:05:46 +, Todd Gruhn wrote: > I can't see what a font looks like, are different sizes. > > Now do I see / test this? xfd -fa "Monospace-24" will give you size 24. At the top of the window it will show you the "real" name of the font it used (Monospace is some sort of alias or shortcut). -Olaf. -- ___ Olaf 'Rhialto' Seibert \X/ There is no AI. There is just someone else's work. --I. Rose signature.asc Description: PGP signature
Re: cvs and older versions of a file
On Sun, May 26, 2024 at 09:03:11AM +, Todd Gruhn wrote: I messed up a .Xresources . How do I tell cvs to give me a previous copy? It has been a long time since I used cvs, but you can try: % cvs log .Xresources Find the rev you want to diff with then % cvs diff -rREV .Xresources That is from an old memory, but cvs is rather close to rcs(1) which I use a lot and I think cvs arguments are close to what rcs(1) uses. HTH
Re: View / test *-ttf fonts
It did not impress me. It shows me that I can see all the characters. I can't see what a font looks like, are different sizes. Now do I see / test this? On Sat, May 25, 2024 at 8:22 PM Thomas D. Dean wrote: > > On 5/25/24 07:22, Todd Gruhn wrote: > > Is there a way to view the *-ttf fonts? > > So I know what it will look like ... > > xfd > > Tom Dean >
Re: View / test *-ttf fonts
On 5/25/24 07:22, Todd Gruhn wrote: Is there a way to view the *-ttf fonts? So I know what it will look like ... xfd Tom Dean
Re: getconf LONG_BIT in NetBSD
El 21 de mayo de 2024 17:05:12 CEST, Rhialto escribió: >On Mon 20 May 2024 at 22:20:30 +0200, Ramiro Aceves wrote: >> AC_PREREQ(2.50) >> AC_INIT(xmain.c) >> AC_MSG_CHECKING([OS]) >> AC_CONFIG_FILES([Makefile]) >> AC_CONFIG_FILES([ft245.c]) >> BITS=`(getconf LONG_BIT)` Here >> AC_SUBST(BITS) > Thanks Rihalto for answering. Sorry for delay, no free time to play with NetBSD in the last days. >I have also seen some programs that just want to know the "bitness" so >that they can call the library they produced "libfoo32" or "libfoo64" Yes, you are right, I think that is the reason. >That seems to be out of some sort of habit for MSWindows or even Linux >programs. But for NetBSD this is almost never relevant since pretty much >all programs you build and run are for the "natural" size. In my case, I >had to teach the packages to just create and use "libfoo" without >numbers. > >If this is the case for this package, you could try and do the same. > >If the packge wants to know the bitness so that it can use the right >types for typedefs or something like that, then you could change it to >use int32_t and int64_t unconditionally. > >In both cases I would call this bugs and would report upstream. Even if >you only determine that one of these scenarios is what's happening, and >you don't manage to fix it. > >-Olaf. After talking with upstream we agreed making the fewest changes in the code just to make it work. Upstream suggested to add fixes to make it work under FreeBSD cause years ago it worked in that OS (they have a port for an older version) first and after that, try NetBSD. In the former I could get it work at least partially. So we are moving towards the goal...not too much free time, we move slowly. Learning many thinks, I am very newbie in every aspect. Regards. Ramiro.
Re: NetBSD 10.0 installation cd boot hangs
On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote: > This is technically not a hang. The kernel did not find the device to boot > from, so it is waiting for you to enter one. Are you expecting the device on > the SATA bus? -- Benny > I guess it should show up in the viaide controller, but: > viaide0 channel 1: reset failed for drive 0 says it did not work well. You could try to list the available devices by entering ? at the boot prompt (but I guess your CD will be missing). Martin
Re: NetBSD 10.0 installation cd boot hangs
Am 23.05.24 um 18:43 schrieb e...@tilde.team: The installation hangs after a while; I'm copying the last bit of the messages below: [ 2.6297051] ukbd0 at uhidev0 [ 2.6297051] wskbd1 at ukbd0 mux 1 [ 61.6629741] waiting for devices: atabus1 atabus2 atabus3 [ 121.6968080] waiting for devices: atabus1 atabus2 atabus3 [ 181.7306411] waiting for devices: atabus1 atabus2 atabus3 [ 241.7644750] waiting for devices: atabus1 atabus2 atabus3 [ 301.7983080] waiting for devices: atabus1 atabus2 atabus3 viaide0 channel 1: reset failed for drive 0 [ 311.2736479] WARNING: system needs entropy for security; see entropy(7) [ 311.2736479] swwdog0: software watchdog initialized [ 311.2736479] WARNING: 1 error while detecting hardware; check system log. [ 311.2736479] boot device: [ 311.2736479] root device: This is where it hangs. Happy to hear any suggestions. This is technically not a hang. The kernel did not find the device to boot from, so it is waiting for you to enter one. Are you expecting the device on the SATA bus? -- Benny
Re: NetBSD 10 and framebuffer consoles setup vs 9.3 (font, multiple...)
On Fri, May 24, 2024 at 11:19:35PM +0200, Martin Neitzel wrote: > EDID provides both a coarse display size (height & width in cm) as > part of the "EDID Basic display parameters" and mm-exact sizes > along with every "EDID Detailed Timing Descriptor" (which also > specify the size in pixels). So yes: it *is* possible to derive > the DPI from the EDID info. Indeed, this is what the kernel already does when selecting a font...
Re: NetBSD 10 and framebuffer consoles setup vs 9.3 (font, multiple...)
ST> That of course means being able to read the DPI from somewhere, but isn't ST> that a thing that EDID does? RVP> There's no DPI present in the EDID data, as far as I know (DisplayID RVP> has horiz. and vert. pixel counts which could be used in combination RVP> with the display size values). EDID provides both a coarse display size (height & width in cm) as part of the "EDID Basic display parameters" and mm-exact sizes along with every "EDID Detailed Timing Descriptor" (which also specify the size in pixels). So yes: it *is* possible to derive the DPI from the EDID info. Martin Neitzel Ref: https://en.wikipedia.org/wiki/Extended_Display_Identification_Data
Re: Set font size on EMACS-29.3 (not pkgsrc)
On 5/24/24 22:18, Todd Gruhn wrote: I downloaded emacs-29.9.tar.gp an installed it. I think the fonts used in the GUI at top, are too small. I wish to use larger fonts -- but how? Use Mwm.*.*.* -- or do this with /bin/ksh ./configure ?? BTW -- I want EMACS and etc , outside of pkgsrc. Try putting something like this in your ~/.emacs.el: (when window-system (set-frame-font "Dejavu Sans Mono 12" t)) ; or whatever TTF font you have installed
Re: framebuffer console on old ATI
Hi, John D. Baker wrote: Interesting that this works for you. I have several machines with the ATI ES1000 rev. 0x02 (RN50) video device: HP DL380G5, HP ML310G4, IBM x3650, Dell PowerEdge 2850 and they all exhibit the "almost-black-on-black" video problem when booting a kernel built with the patch applied and radeondrmkms, etc. enabled. when you have black on black, the computer is still functioning correctly... e.g. it responds to keyboard (caps-lock) and most important it responds to network and you can telnet/ssh into it. Mine does not.. this is what worries me, I think something else is misconfigured or misinitialized. Riccardo
Re: framebuffer console on old ATI
Hi Martin, Martin Neitzel wrote: A zillion thanks to John Baker for mailing this! I changed this on my old HP Proliant DL360 G6 with its ATI ES1000 (RV100) onboard graphics two weeks ago and --voila-- instant karma! I envy you! I have a newer chip but it still doesn't like to run :) Riccardo
Re: Bluetooth wheel mouse and X11
On Thu, 23 May 2024, jo...@sdf.org wrote: I confirmed the output is the same with /dev/wsmouse -- no wsmoused or X. Here is output for 1) some scrolling, 2) left then right button click, and 3) a bunch of moving the mouse around: So, the mouse actually _is_ generating scroll events when one moves the mouse. Might need some quirk handling (see btms_fixup_elecom() in dev/bluetooth/btms.c). Let's see what Linux does for this. Can you tell me what the vendor and product IDs of the mouse are? For reference, here's what my Logitech G304 connected via its USB dongle (NetBSD doesn't recognize my Bluetooth controller yet) reports for the same actions: ``` scroll: -1 (up) scroll: -1 (up) scroll: -1 (up) scroll: 1 (down) scroll: 1 (down) scroll: 1 (down) press: 0 release: 0 press: 2 release: 2 move: -1 (down) move: -1 (down) move: -1 (down) move: -1 (down) move: -1 (down) move: -1 (left) move: -1 (down) move: -1 (down) move: 1 (up) move: -1 (left) move: -1 (left) move: -1 (left) move: -1 (left) move: -1 (left) move: -1 (left) move: -1 (left) ``` -RVP
Re: Bluetooth wheel mouse and X11
> > Can you run this program on the console (no X; no wsmoused) and see if it > reports any scroll events when you move the mouse? Run on /dev/wsmouse2 > first, then on /dev/wsmouse. Both should report the same type of events, I > think. I confirmed the output is the same with /dev/wsmouse -- no wsmoused or X. Here is output for 1) some scrolling, 2) left then right button click, and 3) a bunch of moving the mouse around: cat mousetest.out move: -1 (left) scroll: 256 (down) delta-w: -256 (left) scroll: -1 (up) delta-w: 1 (right) press: 0 move: 1 (right) scroll: -257 (up) delta-w: 257 (right) release: 0 move: -1 (left) scroll: 256 (down) delta-w: -256 (left) move: -1 (left) scroll: 256 (down) delta-w: -256 (left) move: 1 (right) scroll: -256 (up) delta-w: 256 (right) move: 1 (right) scroll: -256 (up) delta-w: 256 (right) scroll: -2 (up) delta-w: 2 (right) press: 2 release: 2 move: -1 (left) move: -2 (down) scroll: 256 (down) delta-w: -256 (left) move: 1 (right) scroll: -256 (up) delta-w: 256 (right) move: -11 (left) move: 6 (up) scroll: 2816 (down) delta-w: -2816 (left) move: -36 (left) move: 16 (up) scroll: 9216 (down) delta-w: -9216 (left) move: -7 (left) move: 21 (up) scroll: 1792 (down) delta-w: -1792 (left) move: 22 (right) move: 23 (up) scroll: -5632 (up) delta-w: 5632 (right) move: 96 (right) move: 16 (up) scroll: -24576 (up) delta-w: 24576 (right) move: 56 (right) move: -23 (down) scroll: -14336 (up) delta-w: 14336 (right) move: 59 (right) move: -46 (down) scroll: -15104 (up) delta-w: 15104 (right) move: 69 (right) move: -66 (down) scroll: -17664 (up) delta-w: 17664 (right) move: 55 (right) move: -67 (down) scroll: -14080 (up) delta-w: 14080 (right) move: 35 (right) move: -67 (down) scroll: -8960 (up) delta-w: 8960 (right) move: 2 (right) move: -58 (down) scroll: -512 (up) delta-w: 512 (right) move: -40 (left) move: -48 (down) scroll: 10240 (down) delta-w: -10240 (left) move: -86 (left) move: -20 (down) scroll: 22016 (down) delta-w: -22016 (left) move: -121 (left) move: 10 (up) scroll: 30976 (down) delta-w: -30976 (left) move: -139 (left) move: 39 (up) scroll: -29952 (up) delta-w: 29952 (right) move: -156 (left) move: 64 (up) scroll: -25600 (up) delta-w: 25600 (right) move: -153 (left) move: 86 (up) scroll: -26368 (up) delta-w: 26368 (right) move: -118 (left) move: 102 (up) scroll: 30208 (down) delta-w: -30208 (left) move: -70 (left) move: 115 (up) scroll: 17920 (down) delta-w: -17920 (left) move: 3 (right) move: 96 (up) scroll: -768 (up) delta-w: 768 (right) move: 54 (right) move: 86 (up) scroll: -13824 (up) delta-w: 13824 (right) move: 112 (right) move: 72 (up) scroll: -28672 (up) delta-w: 28672 (right) move: 176 (right) move: 48 (up) scroll: 20480 (down) delta-w: -20480 (left) move: 226 (right) move: 16 (up) scroll: 7680 (down) delta-w: -7680 (left) move: 216 (right) move: -19 (down) scroll: 10240 (down) delta-w: -10240 (left) move: 186 (right) move: -57 (down) scroll: 17920 (down) delta-w: -17920 (left) move: 134 (right) move: -93 (down) scroll: 31232 (down) delta-w: -31232 (left) move: 61 (right) move: -122 (down) scroll: -15616 (up) delta-w: 15616 (right) move: -21 (left) move: -113 (down) scroll: 5376 (down) delta-w: -5376 (left) move: -90 (left) move: -99 (down) scroll: 23040 (down) delta-w: -23040 (left) move: -141 (left) move: -74 (down) scroll: -29440 (up) delta-w: 29440 (right) move: -192 (left) move: -44 (down) scroll: -16384 (up) delta-w: 16384 (right) move: -222 (left) move: -8 (down) scroll: -8704 (up) delta-w: 8704 (right) move: -249 (left) move: 34 (up) scroll: -1792 (up) delta-w: 1792 (right) move: -223 (left) move: 63 (up) scroll: -8448 (up) delta-w: 8448 (right) move: -199 (left) move: 88 (up) scroll: -14592 (up) delta-w: 14592 (right) move: -156 (left) move: 111 (up) scroll: -25600 (up) delta-w: 25600 (right) move: -96 (left) move: 126 (up) scroll: 24576 (down) delta-w: -24576 (left) move: -18 (left) move: 148 (up) scroll: 4608 (down) delta-w: -4608 (left) move: 59 (right) move: 117 (up) scroll: -15104 (up) delta-w: 15104 (right) move: 133 (right) move: 103 (up) scroll: 31488 (down) delta-w: -31488 (left) move: 193 (right) move: 84 (up) scroll: 16128 (down) delta-w: -16128 (left) move: 237 (right) move: 42 (up) scroll: 4864 (down) delta-w: -4864 (left) move: 279 (right) move: -1 (down) scroll: -5888 (up) delta-w: 5888 (right) move: 243 (right) move: -55 (down) scroll: 3328 (down) delta-w: -3328 (left) move: 204
Re: Bluetooth wheel mouse and X11
On Wed, 22 May 2024, Joel wrote:
wsmuxctl -f 0 -l
wsmouse0
wsmouse2
Can you run this program on the console (no X; no wsmoused) and see if it
reports any scroll events when you move the mouse? Run on /dev/wsmouse2
first, then on /dev/wsmouse. Both should report the same type of events, I
think.
-RVP
--- START mousetest.c ---
/**
* 64-bit systems: hexdump -e '24/1 "%02x " "\n"' /dev/wsmouseN
* 32-bit systems: hexdump -e '20/1 "%02x " "\n"' /dev/wsmouseN
*/
#include
#include
#include
#include
#include
#include
int
main(int argc, char* argv[])
{
struct wscons_event e[16], *ep;
char* dev;
int fd;
if (argc != 2) {
fprintf(stderr, "Usage: %s mouse-dev\n", getprogname());
exit(EXIT_FAILURE);
}
dev = argv[1];
if ((fd = open(dev, O_RDONLY)) == -1)
err(EXIT_FAILURE, "%s: open failed", dev);
for (;;) {
ssize_t i, n;
if ((n = read(fd, e, sizeof e)) <= 0) {
close(fd);
err(EXIT_FAILURE, "%s: packet read failed", dev);
}
if (n % sizeof(e[0])) {
close(fd);
err(EXIT_FAILURE, "%s: partial packet read", dev);
}
n /= sizeof(e[0]);
for (i = 0, ep = e; i < n; i++, ep++) {
switch (ep->type) {
case WSCONS_EVENT_MOUSE_UP:
printf(" release: %d\n", ep->value);
break;
case WSCONS_EVENT_MOUSE_DOWN:
printf(" press: %d\n", ep->value);
break;
case WSCONS_EVENT_MOUSE_DELTA_X:
printf("move: %d (%s)\n", ep->value, ep->value < 0 ?
"left" : "right");
break;
case WSCONS_EVENT_MOUSE_DELTA_Y:
printf("move: %d (%s)\n", ep->value, ep->value < 0 ?
"down" : "up");
break;
case WSCONS_EVENT_MOUSE_ABSOLUTE_X:
printf(" loc X: %d\n", ep->value);
break;
case WSCONS_EVENT_MOUSE_ABSOLUTE_Y:
printf(" loc Y: %d\n", ep->value);
break;
case WSCONS_EVENT_MOUSE_DELTA_Z:
printf(" scroll: %d (%s)\n", ep->value, ep->value < 0 ?
"up" : "down");
break;
case WSCONS_EVENT_MOUSE_ABSOLUTE_Z:
printf(" loc Z: %d\n", ep->value);
break;
case WSCONS_EVENT_MOUSE_DELTA_W:
printf(" delta-w: %d (%s)\n", ep->value, ep->value < 0 ?
"left" : "right");
break;
case WSCONS_EVENT_MOUSE_ABSOLUTE_W:
printf(" loc W: %d\n", ep->value);
break;
case WSCONS_EVENT_HSCROLL:
printf("H-scroll: %d\n", ep->value);
break;
case WSCONS_EVENT_VSCROLL:
printf("V-scroll: %d\n", ep->value);
break;
default:
printf("Unknown: %u %d\n", ep->type, ep->value);
break;
}
}
}
return 0;
}
--- END mousetest.c ---
Re: framebuffer console on old ATI
JDB> Interesting that this works for you. I have several machines with the JDB> ATI ES1000 rev. 0x02 (RN50) video device: HP DL380G5, HP ML310G4, IBM JDB> x3650, Dell PowerEdge 2850 and they all exhibit the "almost-black-on-black" JDB> video problem when booting a kernel built with the patch applied and JDB> radeondrmkms, etc. enabled. In case it helps, this works for me with netbsd-10-stable and the one-line change. pcictl(1) says 001:03:0: ATI Technologies ES1000 (VGA display, revision 0x02) Here is the pertaining dmesg block: [drm] initializing kernel modesetting (RV100 0x1002:0x515E 0x103C:0x31FB 0x02). [drm] register mmio base: 0xf5ff [drm] register mmio size: 65536 radeon0: VRAM: 128M 0xE800 - 0xEFFF (64M used) radeon0: GTT: 512M 0xC800 - 0xE7FF [drm] Detected VRAM RAM=80M, BAR=128M [drm] RAM width 16bits DDR Zone kernel: Available graphics memory: 9007199253233986 KiB Zone dma32: Available graphics memory: 2097152 KiB [drm] radeon: 64M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] PCI GART of 512M enabled (table at 0x451D2000). radeon0: WB disabled radeon0: fence driver on ring 0 use gpu addr 0xc800 and cpu addr 0x0xa6bfc272f000 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. radeon0: interrupting at ioapic0 pin 23 (radeon0) [drm] radeon: irq initialized. [drm] Loading R100 Microcode [drm] radeon: ring at 0xC8001000 [drm] ring test succeeded in 1 usecs [drm] ib test succeeded in 0 usecs [drm] No TV DAC info found in BIOS [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA-1 [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [drm] Encoders: [drm] CRT1: INTERNAL_DAC1 [drm] Connector 1: [drm] VGA-2 [drm] DDC: 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c 0x6c [drm] Encoders: [drm] CRT2: INTERNAL_DAC2 radeondrmkmsfb0 at radeon0 [drm] Initialized radeon 2.50.0 20080528 for radeon0 on minor 0 radeondrmkmsfb0: framebuffer at 0xe804, size 1280x1024, depth 16, stride 2560 wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 Monitor is a trusty old "ViewSonic VPS191s". (I like these because they can still sync-on-green and work with old SGI gear.) Martin Neitzel
Re: framebuffer console on old ATI
On Thu, 23 May 2024, Martin Neitzel wrote: > Another late responder, a happy one, though: > > > > The following patch (against -current from about 4 years ago) will > > > enable matching R100/R200 devices: > > > > > > +Index: sys/external/bsd/drm2/radeon/radeon_pci.c > > > [...] > > > + /* Set this to false if you want to match R100/R200 */ > > > +-bool radeon_pci_ignore_r100_r200 = true; > > > ++bool radeon_pci_ignore_r100_r200 = false; > > A zillion thanks to John Baker for mailing this! I changed this > on my old HP Proliant DL360 G6 with its ATI ES1000 (RV100) onboard > graphics two weeks ago and --voila-- instant karma! > > I get now the radeon framebuffer console with proper 1280x1024 > resolution and clearly readable text (green, black, and white all > as they should be); X11 also improved: 640x480 vga/vesa before, > 1280x1024 radeon gfx now. Interesting that this works for you. I have several machines with the ATI ES1000 rev. 0x02 (RN50) video device: HP DL380G5, HP ML310G4, IBM x3650, Dell PowerEdge 2850 and they all exhibit the "almost-black-on-black" video problem when booting a kernel built with the patch applied and radeondrmkms, etc. enabled. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: framebuffer console on old ATI
Another late responder, a happy one, though: > > The following patch (against -current from about 4 years ago) will > > enable matching R100/R200 devices: > > > > +Index: sys/external/bsd/drm2/radeon/radeon_pci.c > > [...] > > + /* Set this to false if you want to match R100/R200 */ > > +-bool radeon_pci_ignore_r100_r200 = true; > > ++bool radeon_pci_ignore_r100_r200 = false; A zillion thanks to John Baker for mailing this! I changed this on my old HP Proliant DL360 G6 with its ATI ES1000 (RV100) onboard graphics two weeks ago and --voila-- instant karma! I get now the radeon framebuffer console with proper 1280x1024 resolution and clearly readable text (green, black, and white all as they should be); X11 also improved: 640x480 vga/vesa before, 1280x1024 radeon gfx now. Thanks again, Martin Neitzel
Re: Mailing List Oddity
Hello Alistair, ASB> Why is there a regional-london mailing list but no regional-uk? AGC> I think mainly because a number of us were working in London, > and with the occasional guest visitor swanning in, enlightening > us, then exiting stage left, we used regional-london to arrange > meetups. Ah, in part to catching people passing through then. AGC> ...(just taking one superlative region at random, Glasgow, to > prove my point beyond question). But a regional-weegie list > might not have as much of a pull as regional-london. Either city might attract people with an interest in underground trains! :-) AGC> Now onto the vexing questions of whether the uk is a region at > all, why regional-uk would not work for the poor folks in the > Isle of Man... I paused when typing 'regional-uk' to wonder whether regional- wales, regional-scotland might attract more of an audience. Perhaps our userbase is small enough to keep meetup announcements in netbsd- users without clogging it up too much. AGC> why London, Ohio, USA folks are always late for regional-london > get-togethers, regions where abs would deliver vaxen to, etc Don't forget London, Ontario, Canada! Come to think of it, there's a Cardiff, Illinois, USA too. regional-cardiff-no-the-other-one -Andy Ball
Re: intel videocard performance degraded severely after 9.4 update
Sorry for the multiple-posts.. apparently SeaMonkey sent out drafts while I was composing the message! Very strange.
Re: framebuffer console on old ATI
Hi John sorry for the late reply... needed some NetBSD hack time to find to patch and recompile the kernel. John D. Baker wrote: > On Tue, 7 May 2024, Riccardo Mottola wrote: > > That looks like the same description of the radeon device in my T42 > ThinkPad: IN some sense the T43 is successor of the T30... I'd expect yours to be a little bit newer. But all these R/RV/RS revisions are confusing. > (radeondrm0 is the legacy UMS "radeondrm* at drm?" device) > > As an R*200 device, it is not matched by the DRM2 code in NetBSD. > >> Since I am endeavouring in compiling a kernel, I might try enabling it, >> if you tell me how. Just as a test, maybe magic happens. > > The following patch (against -current from about 4 years ago) will > enable matching R100/R200 devices: > > > +Index: sys/external/bsd/drm2/radeon/radeon_pci.c > +=== > +RCS file: /cvsroot/src/sys/external/bsd/drm2/radeon/radeon_pci.c,v > +retrieving revision 1.14 > +diff -u -p -r1.14 radeon_pci.c > +--- sys/external/bsd/drm2/radeon/radeon_pci.c24 Jan 2020 11:44:27 > - 1.14 > sys/external/bsd/drm2/radeon/radeon_pci.c28 May 2020 23:49:44 > - > +@@ -126,7 +126,7 @@ extern const struct pci_device_id *const > + extern const size_t radeon_n_device_ids; > + > + /* Set this to false if you want to match R100/R200 */ > +-bool radeon_pci_ignore_r100_r200 = true; > ++bool radeon_pci_ignore_r100_r200 = false; > + > + static bool > + radeon_pci_lookup(const struct pci_attach_args *pa, unsigned long *flags) > This patch was a little hard to read, looks like a patch of a patch? But the core is to swap true to false. in a match. I did... However, it does not work properly. During boot, when FB should attach, the whole scren displays garbage. It is not hi-res garbage, the screen still looks like being in VGA resolution and contains just blocks of green and white stripes (as of the console dmesg). So indeed the code does not seem to handle my RS250 without further tweaks! > > I really don't know. My understanding is that on OpenBSD and various > Penguin-OSes, these older ATI devices work fine. Indeed and we shouldn't be "of less" :) :) > I saw your message about trying "radeonfb* at pci?" in your kernel config. For that I am just trying Michael's suggestions, after having enabled again radeon_pci_ignore_r100_r200 Will report there. For most users it would be probably to have drm working... but let's start getting a framebuffer at all. Riccardo
Re: framebuffer console on old ATI
Hi, Michael wrote: > Did it crash or did if continue booting? If it continued to boot > radeonfb likely got the wiring of outputs to displays wrong. > With that, please try with options RADEONFB_BIOS_INIT, which adds code > to scan the BIOS for output info. This is not enabled by default > because most hardware we run radeonfb on doesn't have a PC BIOS. Should > probably be on by default on x86. did so. Still get a black screen. Before going black, I am able to see a "failed". Also, it hangs, because if I wait some time I can't login remotely (left dhcp on). thanks to easy videos with iPhones... I was able to extract a frame: radeonfb0: BIOS initialization failed hmm... looks like the option was not enough, I did not do it correctly or there is a further bug. Riccardo
Re: intel videocard performance degraded severely after 9.4 update
Hi, trying and testing... I can get even more scarier errors from i915. I tried various combination of enabling wifi before/after As you can see, the buffer underrun appears after some moments, after I completed login. So we have 1) CPU Pipe A FIFO underrun 2) CPU Pipe B FIFO underrun 3) failed to load DMA map for stolen object: -22 4) failed to load DMA map for stolen object: -22 again 5) after a while CPU Pipe A FIFO underrun again are there other old i915 owners? [ 5.327841] kern info: [drm] Memory usable by graphics device = 128M [ 5.337843] kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 5.337843] kern info: [drm] Driver supports precise vblank timestamp query. [ 5.337843] i915drmkms0: interrupting at irq 11 (i915drmkms0) [ 5.367842] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun [ 5.367842] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe B FIFO underrun [ 5.377843] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem_stolen.c:555)i915_pages_create_for_stolen] *ERROR* failed to load DMA map for stolen object: -22 [ 5.377843] kern info: [drm] initialized overlay support [ 5.427842] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem_stolen.c:555)i915_pages_create_for_stolen] *ERROR* failed to load DMA map for stolen object: -22 [ 5.437847] intelfb0 at i915drmkms0 [ 5.437847] intelfb0: framebuffer at 0xdc295000, size 1024x768, depth 32, stride 4096 [ 6.067853] wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 [ 6.078116] wsmux1: connecting to wsdisplay0 [10.377920] wsdisplay0: screen 1 added (default, vt100 emulation) [10.387923] wsdisplay0: screen 2 added (default, vt100 emulation) [10.387923] wsdisplay0: screen 3 added (default, vt100 emulation) [10.387923] wsdisplay0: screen 4 added (default, vt100 emulation) [15.507997] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun
Re: intel videocard performance degraded severely after 9.4 update
Hi, nia wrote: > What are the permissions on /dev/dri/*? > > Does your user have the ability to write to the devices? it should: R51$ ls -l /dev/dri* total 0 crw-rw 1 root wheel 180, 0 Aug 8 2018 card0 crw-rw 1 root wheel 180, 1 Aug 8 2018 card1 crw-rw 1 root wheel 180, 2 Aug 8 2018 card2 crw-rw 1 root wheel 180, 3 Aug 8 2018 card3 R51$ groups users wheel
Re: Mailing List Oddity
On Wed, May 22, 2024 at 11:58 Andrew Ball wrote: > Why is there a regional-london mailing list but no regional-uk? -Andy > > I think mainly because a number of us were working in London, and with the occasional guest visitor swanning in, enlightening us, then exiting stage left, we used regional-london to arrange meetups. Definitely not looking down on the areas outside London, most of which are far superior anyway, although they're all on the road less travelled (just taking one superlative region at random, Glasgow, to prove my point beyond question). But a regional-weegie list might not have as much of a pull as regional-london. Just saying My personal opinion is that regional lists work best for metropolitan area scale coordination Now onto the vexing questions of whether the uk is a region at all, why regional-uk would not work for the poor folks in the Isle of Man, why London, Ohio, USA folks are always late for regional-london get-togethers, regions where abs would deliver vaxen to, etc Best, Alistair PS. If there's a good crowd anywhere who would benefit from a (metro-area?) mailing list for coordination, let's hear about them
Re: Mailing List Oddity
Andrew Ball writes: > Why is there a regional-london mailing list but no regional-uk? -Andy I would not assume there is any particular reason. There is a regional-boston list but it has not, in the last many years, had any useful traffic. I think it got deleted but I'm not sure. And I was probably the moderator. Overall, this is a clue!
Re: NetBSD 10 and framebuffer consoles setup vs 9.3 (font, multiple...)
On Thu, 11 Apr 2024, Riccardo Mottola wrote: For 4K displays maybe, but on any laptop I have at hand - without prehaps a "Retina" or equivalent display, the small font is readable enough and actually the more information makes installing, merging files reading dmesg much much easier. Up to my HD display on 22" standard font is fine. Maybe it is just which threshold you consider "high enough". On a laptop with a 14" screen and a 1920x1200 display, I find the default 8x16 font unreadable. And, the scrolling is unbearably slow. While installing, you can escape into the shell, then do: wsconsctl -dw font=Boldface Will try at the next run - it works in normal boot. Perhaps an installer option could be also useful? like keyboard setup, display setup. Like Slackware, eh? Sure; plus, sometimes the kernel picks the wrong font-size for the resolution (presented by DRMKMS, I think--genfb doesn't seem to have this issue) and the console ends up with less than 80x25 cells: https://mail-index.netbsd.org/netbsd-users/2024/05/10/msg031151.html On Thu, 11 Apr 2024, Staffan Thomén wrote: RVP wrote: and the system will now use the larger font if you have a high enough display. Otherwise, you would end up with an unreadable chars. on, say, 4K displays. Surely this should be against the display density? (i.e. DPI) Well, DPI is tricky ;). I assume you mean the DPI you get from the max. res. / display size? And, that the max. res. _actually_ covers the whole screen, edge-to-edge? That of course means being able to read the DPI from somewhere, but isn't that a thing that EDID does? There's no DPI present in the EDID data, as far as I know (DisplayID has horiz. and vert. pixel counts which could be used in combination with the display size values). And, DPI changes based on current display res., screen orientation, whether the H & V timings are padded multiples of 8, etc. -RVP
Re: GENERIC_KASLR Boot Page Fault in 10.0
On Fri, 5 Apr 2024, Isaac wrote: Whether I choose to install the GENERIC_KASLR kernel via the installation menu, or follow the steps at https://wiki.netbsd.org/security/kaslr/, the result is the same. The installation succeeds, but when booting the kernel it crashes during the "jumping to kernel" stage with a page fault. The GENERIC kernel works fine. I can reproduce this on real HW too. The 9.4 KASLR kernel works with the /prekern from 10.99.10; the 10.99.10 KASLR kernel fails to boot. Looks like a regression. Please file a PR for this. -RVP
Re: Bluetooth wheel mouse and X11
> Are you connected to the G4 using ssh -X or something? Ah yes, sorry about that. I lazily ssh'd from WSL2 to copy/paste more easily. Here's the output directly from the G4 with only the BT Microsoft Wedge mouse attached: xinput list _ Virtual core pointer id=2 [master pointer (3)] _ _ Virtual core XTEST pointer id=4 [slave pointer (2)] _ _ /dev/wsmouse id=7 [slave pointer (2)] _ Virtual core keyboard id=3 [master keyboard (2)] _ Virtual core XTEST keyboard id=5 [slave keyboard (3)] _ /dev/wskbd id=6 [slave keyboard (3)] xinput list-props 2 Device 'Virtual core pointer': Device Enabled (165): 1 Coordinate Transformation Matrix (166): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 xinput list-props 4 Device 'Virtual core XTEST pointer': Device Enabled (165): 1 Coordinate Transformation Matrix (166): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 XTEST Device (269): 1 xinput list-props 7 Device '/dev/wsmouse': Device Enabled (165): 1 Coordinate Transformation Matrix (166): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (272): 0 Device Accel Constant Deceleration (273): 1.00 Device Accel Adaptive Deceleration (274): 1.00 Device Accel Velocity Scaling (275): 10.00 WS Pointer Middle Button Emulation (276): 2 WS Pointer Middle Button Timeout (277): 50 wsmuxctl -f 0 -l wsmouse0 wsmouse2 wsconsctl -am -f /dev/wsmouse2 type=bluetooth scroll.reverse=0 scroll.distance.x=12 scroll.distance.y=12 repeat.buttons=none repeat.delay.first=0 repeat.delay.decrement=0 repeat.delay.minimum=0 2. Have you tried these same mice on an amd64 system? Yes, and sure enough, on my NetBSD 10 AMD64 build machine I see the same (incorrect) scrolling behavior. I guess I should keep my Microsoft BT mice inside their Windows world :) But FWIW, I use these same Microsoft BT mice on Debian Linux and they work correctly. Appreciate all of your help. -Joel
Re: Bluetooth wheel mouse and X11
On Tue, 21 May 2024, jo...@sdf.org wrote: Can you describe a few things so that I can understand your setup. 1. The Xorg.0.log indicates that you're running Xorg on a macppc: X.Org X Server 1.21.1.9 X Protocol Version 11, Revision 0 [ 156.997] Current Operating System: NetBSD macppc 10.0 NetBSD 10.0 (MACMINIG4) #7: Sun May 12 15:16:25 PDT 2024 joelp@xxx:/home/joelp/netbsd10-src/obj/sys/arch/macppc/compile/MACMINIG4 macppc but xinput thinks it's connected to a Wayland server: xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. _ Virtual core pointer id=2[master pointer (3)] _ _ Virtual core XTEST pointerid=4[slave pointer (2)] _ _ xwayland-pointer:19 id=6[slave pointer (2)] _ _ xwayland-relative-pointer:19 id=7[slave pointer (2)] _ Virtual core keyboard id=3[master keyboard (2)] _ Virtual core XTEST keyboard id=5[slave keyboard (3)] _ xwayland-keyboard:19 id=8[slave keyboard > Are you connected to the G4 using ssh -X or something? 2. Have you tried these same mice on an amd64 system? 3. Can you post the output of: wsmuxctl -f 0 -l then that of wsconsctl -am -f /dev/wsmouseN on the bluetooth mouse? -RVP
Re: getconf LONG_BIT in NetBSD
On Mon 20 May 2024 at 22:20:30 +0200, Ramiro Aceves wrote: > AC_PREREQ(2.50) > AC_INIT(xmain.c) > AC_MSG_CHECKING([OS]) > AC_CONFIG_FILES([Makefile]) > AC_CONFIG_FILES([ft245.c]) > BITS=`(getconf LONG_BIT)` Here > AC_SUBST(BITS) I have also seen some programs that just want to know the "bitness" so that they can call the library they produced "libfoo32" or "libfoo64". That seems to be out of some sort of habit for MSWindows or even Linux programs. But for NetBSD this is almost never relevant since pretty much all programs you build and run are for the "natural" size. In my case, I had to teach the packages to just create and use "libfoo" without numbers. If this is the case for this package, you could try and do the same. If the packge wants to know the bitness so that it can use the right types for typedefs or something like that, then you could change it to use int32_t and int64_t unconditionally. In both cases I would call this bugs and would report upstream. Even if you only determine that one of these scenarios is what's happening, and you don't manage to fix it. -Olaf. -- ___ Olaf 'Rhialto' Seibert \X/ There is no AI. There is just someone else's work. --I. Rose signature.asc Description: PGP signature
Re: Bluetooth wheel mouse and X11
> Can you post your Xorg.0.log, that should make things clear. > xinput list WARNING: running xinput against an Xwayland server. See the xinput man page for details. _ Virtual core pointer id=2[master pointer (3)] _ _ Virtual core XTEST pointerid=4[slave pointer (2)] _ _ xwayland-pointer:19 id=6[slave pointer (2)] _ _ xwayland-relative-pointer:19 id=7[slave pointer (2)] _ Virtual core keyboard id=3[master keyboard (2)] _ Virtual core XTEST keyboard id=5[slave keyboard (3)] _ xwayland-keyboard:19 id=8[slave keyboard > > xinput list-props > xinput list-props 2 WARNING: running xinput against an Xwayland server. See the xinput man page for details. Device 'Virtual core pointer': Device Enabled (113): 1 Coordinate Transformation Matrix (115): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 macppc:/home/joelp$ xinput list-props 6 WARNING: running xinput against an Xwayland server. See the xinput man page for details. Device 'xwayland-pointer:19': Device Enabled (113): 1 Coordinate Transformation Matrix (115): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (238): 0 Device Accel Constant Deceleration (239): 1.00 Device Accel Adaptive Deceleration (240): 1.00 Device Accel Velocity Scaling (241):10.00 cat /var/log/Xorg.0.log [ 156.990] X.Org X Server 1.21.1.9 X Protocol Version 11, Revision 0 [ 156.997] Current Operating System: NetBSD macppc 10.0 NetBSD 10.0 (MACMINIG4) #7: Sun May 12 15:16:25 PDT 2024 joelp@xxx:/home/joelp/netbsd10-src/obj/sys/arch/macppc/compile/MACMINIG4 macppc [ 156.997] [ 157.008] Current version of pixman: 0.38.4 [ 157.011]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 157.013] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 157.019] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 20 18:49:01 2024 [ 157.067] (II) Loader magic: 0x1ae0e28 [ 157.067] (II) Module ABI versions: [ 157.067]X.Org ANSI C Emulation: 0.4 [ 157.067]X.Org Video Driver: 25.2 [ 157.067]X.Org XInput driver : 24.4 [ 157.067]X.Org Server Extension : 10.0 [ 157.082] (WW) xf86EnableIO -1 [ 157.082] (II) xf86EnableIO: 0x [ 157.082] (WW) Can't map IO space! (9) [ 157.082] (--) PCI:*(0@0:16:0) 1002:5962:1002:5962 rev 1, Mem @ 0x9800/134217728, 0x9000/65536, I/O @ 0x0400/256, BIOS @ 0x/131072 [ 157.083] (==) Using default built-in configuration (21 lines) [ 157.083] (==) --- Start of built-in configuration --- [ 157.083]Section "Device" [ 157.083]Identifier "Builtin Default ati Device 0" [ 157.083]Driver "ati" [ 157.083]EndSection [ 157.083]Section "Screen" [ 157.083]Identifier "Builtin Default ati Screen 0" [ 157.083]Device "Builtin Default ati Device 0" [ 157.083]EndSection [ 157.083]Section "Device" [ 157.083]Identifier "Builtin Default wsfb Device 0" [ 157.083]Driver "wsfb" [ 157.083]EndSection [ 157.083]Section "Screen" [ 157.084]Identifier "Builtin Default wsfb Screen 0" [ 157.084]Device "Builtin Default wsfb Device 0" [ 157.084]EndSection [ 157.084]Section "ServerLayout" [ 157.084]Identifier "Builtin Default Layout" [ 157.084]Screen "Builtin Default ati Screen 0" [ 157.084]Screen "Builtin Default wsfb Screen 0" [ 157.084]EndSection [ 157.084] (==) --- End of built-in configuration --- [ 157.084] (==) ServerLayout "Builtin Default Layout" [ 157.084] (**) |-->Screen "Builtin Default ati Screen 0" (0) [ 157.084] (**) | |-->Monitor "" [ 157.086] (**) | |-->Device "Builtin Default ati Device 0" [ 157.086] (==) No monitor specified for screen "Builtin Default ati Screen 0". Using a default monitor configuration. [ 157.086] (**) |-->Screen "Builtin Default wsfb Screen 0" (1) [ 157.086] (**) | |-->Monitor "" [ 157.087] (**) | |-->Device "Builtin Default wsfb Device 0" [ 157.087] (==) No monitor specified for screen "Builtin Default wsfb Screen 0". Using a default monitor configuration. [ 157.087] (==) Automatically adding devices [ 157.087] (==) Automatically enabling devices [ 157.087] (==) Not automatically adding GPU devices [ 157.087] (==) Automatically binding GPU devices [ 157.101] (==) Max clients allowed: 256, resource mask: 0x1f [
Re: Bluetooth wheel mouse and X11
On Tue, 21 May 2024, jo...@sdf.org wrote:
2. See if it has `Option "EmulateWheel"' and/or `Option
"EmulateWheelButton"'
is set if the input driver is "mouse"?
I tried those options and I could not get this to change the behavior.
Those should, actually, _not_ be set ;-)
When I created an xorg.conf, I used "wsmouse".
I meant the Xorg input driver ("mouse" or "ws" on NetBSD), not the device the
driver is using.
Can you post your Xorg.0.log, that should make things clear.
Oh nice, Iain also suggested xev. I can now confirm that simply moving the
mouse causes multiple events. I noticed that the scroll action on the
mouse does not produce any events.
Hmm. Simply moving the mouse should generate only MotionNotify events; and
using the mouse-wheel only should generate only ButtonPress & ButtonRelease
events, typically button 5 for a down-scroll & button 4 for up-scroll.
MotionNotify event, serial 25, synthetic NO, window 0xa1,
root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315),
state 0x0, is_hint 0, same_screen YES
ButtonPress event, serial 25, synthetic NO, window 0xa1,
root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315),
state 0x0, button 5, same_screen YES
ButtonRelease event, serial 25, synthetic NO, window 0xa1,
root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315),
state 0x1000, button 5, same_screen YES
So, that's both motion and down-scroll buttons.
Can you also show the output of:
xinput list
and,
xinput list-props
-RVP
Re: Bluetooth wheel mouse and X11
> 1. Can you post your xorg.conf and /var/log/Xorg.0.log? Right now I don't have an xorg.conf in /etc/X11. > 2. See if it has `Option "EmulateWheel"' and/or `Option > "EmulateWheelButton"' > is set if the input driver is "mouse"? I tried those options and I could not get this to change the behavior. When I created an xorg.conf, I used "wsmouse". > 3. Run xev -event mouse > /tmp/xev.log, then a) first move the mouse only, > then > b) use the scroll-wheel only? Post the xev.log file, too. Oh nice, Iain also suggested xev. I can now confirm that simply moving the mouse causes multiple events. I noticed that the scroll action on the mouse does not produce any events. Here is the xev log for moving the mouse (made sure I moved X and Y) and trying to scroll (which did not produce events): Outer window is 0xa1, inner window is 0xa2 EnterNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141270, (175,138), root:(333,315), mode NotifyNormal, detail NotifyAncestor, same_screen YES, focus YES, state 0 MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141270, (175,138), root:(333,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141270, (175,138), root:(333,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141270, (175,138), root:(333,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141281, (173,138), root:(331,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141281, (173,138), root:(331,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141281, (173,138), root:(331,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141304, (169,138), root:(327,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141304, (169,138), root:(327,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141304, (169,138), root:(327,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141315, (168,138), root:(326,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141315, (168,138), root:(326,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141315, (168,138), root:(326,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141383, (166,138), root:(324,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141383, (166,138), root:(324,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141383, (166,138), root:(324,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141394, (164,138), root:(322,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141394, (164,138), root:(322,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141394, (164,138), root:(322,315), state 0x1000, button 5, same_screen YES MotionNotify event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141405, (162,138), root:(320,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa1, root 0x3a6, subw 0x0, time 11141405,
Re: Bluetooth wheel mouse and X11
On Thu, 16 May 2024, jo...@sdf.org wrote: When I launch X11, the BT mouse seems to work by simply moving the cursor around. But once the cursor is over a window, I noticed that the X,Y motion is also triggering scrolling. It's as if the mouse motion is generating scroll wheel events. My USB mouse works perfectly under X (/dev/wsmouse) and the wheel scrolling works as expected. I tried various /etc/X11/xorg.conf mouse settings (including ZAxisMapping) but nothing prevents the weird scrolling. 1. Can you post your xorg.conf and /var/log/Xorg.0.log? 2. See if it has `Option "EmulateWheel"' and/or `Option "EmulateWheelButton"' is set if the input driver is "mouse"? 3. Run xev -event mouse > /tmp/xev.log, then a) first move the mouse only, then b) use the scroll-wheel only? Post the xev.log file, too. -RVP
Re: Bluetooth wheel mouse and X11
Hi Iain > great! which mouse did you use btw? It seems I collected some Microsoft BT mice over the years! All 3 Microsoft mice I have exhibit the same behavior. The last one I tried is a portable one called a Wedge Touch Mouse. Here's the btconfig ubt0 inquiry output: 1: bdaddr xx:xx:xx:xx:xx:xx (mouse) : name "Microsoft Wedge Touch Mouse" : class [0x002580] Peripheral Mouse : page scan rep mode 0x01 : clock offset 87 : rssi 0 They all have scrolling (the Wedge is touch sensitive). Here's my USB BT device: [ 6.109991] ubt0 at uhub2 port 1 [ 6.109991] ubt0: Realtek (0x0b05) ASUS USB-BT500 (0x190e), rev 1.10/2.00, addr 2 > On the Bluetooth front, my question would be does the mouse actually send > scroll events? You can find this out with sysutils/hcicump in that the > reports sent will include them. the only way I can conceieve that your > situation occurs is if it is sending both scroll and movement at the same > time somehow > I installed hcidump and received output. Unfortunately, I don't know enough about this yet to make sense -- will do some reading. I pasted the first few lines of output below of me moving (not scrolling) the mouse around. The output appears the same in X or console. > On the X fton, is X registering scroll events? you can perhaps find this > out with xev(1) I'm not sure how.. > I couldn't get any output for this, but I'll keep trying. Thanks for your suggestions for debugging, I have some reading to do at least now :) -Joel hcidump output: hcidump -r wedge.hcidump HCI sniffer - Bluetooth packet analyzer ver 5.66-netbt btsnoop version: 1 datalink type: 1002 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active > HCI Event: Max Slots Change (0x1b) plen 3 handle 4 slots 3 > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x02 interval 18 Mode: Sniff > HCI Event: Mode Change (0x14) plen 6 status 0x00 handle 4 mode 0x00 interval 0 Mode: Active
Re: getconf LONG_BIT in NetBSD
On 5/20/24 19:16, Greg A. Woods wrote: At Sun, 19 May 2024 22:08:27 +0200, Ramiro Aceves wrote: Subject: getconf LONG_BIT in NetBSD I have been playing with an autoconf ./configure script that I want get running in several OSes. The script uses "getconf LONG_BIT" to get the bits of the system. What is the purpose of this test in the context where it is needed? I would think that if it's a C program then there's no need ever for any autoconf test. Just write pure portable C that uses properly. Hello Greg, thanks for answering. If you want to take a look: https://www.sm5bsz.com/linuxdsp/archive/lir05-02.zip It is a very good SDR radio receiver program. It works in Linux and in Windows (MinGW) with several commercial radio receivers. configure.ac: AC_PREREQ(2.50) AC_INIT(xmain.c) AC_MSG_CHECKING([OS]) AC_CONFIG_FILES([Makefile]) AC_CONFIG_FILES([ft245.c]) BITS=`(getconf LONG_BIT)` ... 3630 lines of very long configure.ac script that uses $BITS variable several times to make some decisions. ... ... ... Regards. Ramiro. -- Greg A. Woods Kelowna, BC +1 250 762-7675 RoboHack Planix, Inc. Avoncote Farms
Re: getconf LONG_BIT in NetBSD
On 5/20/24 07:38, PHO wrote:
On 5/20/24 12:28, Aryabhata wrote:
The `limits.h` header file in C provides the necessary information
about system limits, including `LONG_BIT`. You can write a small C
program to print the value of `LONG_BIT`.
Create a simple C program that includes the `limits.h` header and
prints the value of `LONG_BIT`.
#include
#include
int main() {
printf("LONG_BIT: %d\n", LONG_BIT);
return 0;
}
This will output the number of bits in a "long" integer on your system.
Or use AC_COMPUTE_INT. You can do something like
AC_COMPUTE_INT([var], [LONG_BIT], [#include ])
Hello PHO,
Many thanks, I have not tried it yet, not free time today but it seems
to be a very good solution.
Regards!
Re: getconf LONG_BIT in NetBSD
On 5/20/24 05:28, Aryabhata wrote:
The `limits.h` header file in C provides the necessary information about
system limits, including `LONG_BIT`. You can write a small C program to
print the value of `LONG_BIT`.
Create a simple C program that includes the `limits.h` header and prints
the value of `LONG_BIT`.
#include
#include
int main() {
printf("LONG_BIT: %d\n", LONG_BIT);
return 0;
}
This will output the number of bits in a "long" integer on your system.
Hello Aryabhata,
Thanks so much for the suggestion!
Regards.
On Mon, 20 May, 2024, 1:38 am Ramiro Aceves, > wrote:
Hello,
I have been playing with an autoconf ./configure script that I want get
running in several OSes. The script uses "getconf LONG_BIT" to get the
bits of the system.
I see that "getconfg LONG_BIT" works in other systems such as Linux
and
FreeBSD but in NetBSD I have tried it and it does not work:
netbsd-nuc$ getconf LONG_BIT
getconf: LONG_BIT: unknown variable
I read this on limits (3) man page about LONG_BIT:
XSI Limits
Also the X/Open System Interface Extension (XSI) specifies few
limits. In NetBSD these are limited to LONG_BIT (the number of bits in
long), WORD_BIT (the number of bits in a “word”), and few limits
related
to float and double.
How can I get the value of the LONG_BIT variable?
Thanks you very much.
Regards.
Re: getconf LONG_BIT in NetBSD
On 5/20/24 00:47, Valery Ushakov wrote:
On Sun, May 19, 2024 at 22:08:27 +0200, Ramiro Aceves wrote:
I see that "getconf LONG_BIT" works in other systems such as Linux and
FreeBSD but in NetBSD I have tried it and it does not work:
netbsd-nuc$ getconf LONG_BIT
getconf: LONG_BIT: unknown variable
I read this on limits (3) man page about LONG_BIT:
XSI Limits
Also the X/Open System Interface Extension (XSI) specifies few limits.
In NetBSD these are limited to LONG_BIT (the number of bits in long),
WORD_BIT (the number of bits in a “word”), and few limits related to float
and double.
How can I get the value of the LONG_BIT variable?
Pedantically speaking, LONG_BIT is not a "conf" variable, so the
question is where you draw the line for getconf(1)? What should be
returned for LONG_BIT on a system that can run both 32-bit and 64-bit
code (amd64/i386, sparc64/sparc, etc).
Thanks UWE for the explanation.
I have a Debian and a FreeBSD installation along with NetBSD in the same
computer and both return 64 bits for the LONG_INT variable.
Looking a bit closer at the Open Group text for getconf(1) and
friends, I think they intend this kind of stuff to be onbtained via
POSIX_V7_WIDTH_RESTRICTED_ENVS getconf/confstr() and getconf -v
argument.
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/getconf.html
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/c99.html#tag_20_11_13_04
We don't support getconf -v and it seems a bit clunky and posixy
anyway. What's wrong with doing it the autoconf way by running the
compiler you are going to use? :)
The configure.ac script that has the "getconf LONG_BIT" belongs to this
program:
https://www.sm5bsz.com/linuxdsp/archive/lir05-02.zip
This software works for Windows (MinGW) and Linux. I have been trying to
compile it also in FreeBSD and NetBSD. I have had preliminary compiling
success in both OS. Once $BITS variable is obtained is used many times
to do conditional programing along the script.
AC_PREREQ(2.50)
AC_INIT(xmain.c)
AC_MSG_CHECKING([OS])
AC_CONFIG_FILES([Makefile])
AC_CONFIG_FILES([ft245.c])
BITS=`(getconf LONG_BIT)` Here
AC_SUBST(BITS)
#setterm -term linux -back white
#setterm -term linux -fore black
OS=`uname`
AC_SUBST(OS, "${OS}")
MACHINE=$(uname -m)
CPU="CPU_INTEL"
if test "$MACHINE" = "armv5l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv6l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv7l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "aarch64"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "evbarm"; then < Added for NetBSD in the RPi
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv8l"; then
...
...
...
Regards.
Ramiro.
-uwe
Re: Programming Motif / mwm
On Sat, May 18, 2024 at 07:57:37PM +, Todd Gruhn wrote: Thanks John. New Q. Whatif I want the mwm menu*fontList stuff bigger? If I understand you, you would update ~/.Xdefaults with the new fonts and restart mwm. You can get fonts bye executing xfontsel(1), see its manual for detail. John On Sat, May 18, 2024 at 5:20???PM John McCue wrote: On Sat, May 18, 2024 at 10:46:18AM +, Todd Gruhn wrote: >I want to tweek the menu used in Motif. > >I want it larger; can I make the fonts bigger? > >I believe there is no 'f.font' . Is it possible to do this? >Then how? mwm us configured using ~/.Xdefaults, for example this can be done for fonts. Mwm*title*fontList:-*-terminus-bold-r-normal-*-22-*-*-*-*-*-*-* Mwm*menu*fontList: -*-terminus-bold-r-normal-*-22-*-*-*-*-*-*-* Mwm*feedback*fontList: -*-terminus-bold-r-normal-*-22-*-*-*-*-*-*-* Mwm*rclock*title*fontList: -*-terminus-bold-r-normal-*-10-*-*-*-*-*-*-* Mwm*rclock*title*font: -*-terminus-bold-r-normal-*-10-*-*-*-*-*-*-* If you search you should be able to find a complete configuration guide. I had the pdf a long time ago but have since lost it. Regards,
