Side note: we are collecting all bug reports for the new DRM/KMS that
should be fixed before the 10.0 release here:
https://wiki.netbsd.org/releng/netbsd-10/
If you know of any other PRs that should be listed there, please let me know.
Martin
On Sun, Jan 08, 2023 at 11:28:18AM +, Chavdar Ivanov wrote:
> This morning I upgraded the instance to my yesterday's build - as of
> 07/01/2023. Now Xorg dumps core as follows:
Can you show the output of
readelf -l /usr/X11R7/lib/modules/dri/i965_dri.so
for the new build? It probably has
On Sun, Jan 08, 2023 at 01:15:01PM +, Chavdar Ivanov wrote:
> As far as I understand it, there was a change with the dynamic loader at
> this time?
Yes, and after the ld.elf_so change the default linker options were adjusted,
which makes testing this now a bit tricky (you can't just downgrad
On Mon, Jan 02, 2023 at 12:17:11PM +1100, matthew green wrote:
> oh yeah - this is only going to break r/o src tree builds, which is
> also something i use as much as possible.
Note that the official daily builds also use this (and have been failing
since new binutils have been enabled for x86).
Hey folks,
after the EA changes are in current now and all tests look good, we can
finally move on and branch for netbsd-10. Proposed date is next wednsday.
We have quite a few things to finish before the final release, but this
gets things moving - and I hope it will not take more than three
On Fri, Dec 09, 2022 at 10:03:46AM +0100, Matthias Petermann wrote:
> compatibility. However, if I understand correctly, this only affects new
> installations? If I migrate an existing NetBSD 9 to 10, nothing changes in
> the file system format. I.e. as long as I do not actively initite the
>
On Thu, Dec 15, 2022 at 08:35:42PM -0500, Jan Schaumann wrote:
> This, then would speak in favor of leaving the tools
> in pkgsrc.
Yes, and stop there. No point in automating more - just like the
web files are generated by various tools from the meta-pkgs/netbsd-www
pkg, the IANA-derived files
On Thu, Dec 15, 2022 at 07:59:35PM +, Thomas Mueller wrote:
> I will want to update my NetBSD installation from 9.99.82 from source
> and am inclined toward 10.99.1 rather than 10.0_BETA. I use "cvs up
> -dP -A" to update the source on base system and pkgsrc, currently am on
> native X.
As
On Sat, Dec 17, 2022 at 01:41:18AM -0500, Tom Lane wrote:
> but I suppose that just reflects a branch existing in the CVS repo.
Yes, and also that pullup ticket queues for -10 exist.
> I don't see any sign of the branch being supported at, say,
>
> https://nycdn.netbsd.org/pub/NetBSD-daily/
>
Just to wrap up this thread:
- branch will probably happen in the next ~10h
- default file system for new installations will be FFSv2
I will update docs and extend the wiki page about FFS2ea to show how to
switch later, and also provide installation instructions how to select
FFSv2ea right
On Thu, Dec 22, 2022 at 08:05:02AM +0530, Mayuresh wrote:
> Ok. So, it appears the -bios image has become redundant now. Or hasn't it?
No, there are BIOSes out there that don't work with the hybrid bootloader.
Martin
On Sat, Dec 10, 2022 at 03:28:14PM +0100, Reinoud Zandijk wrote:
> related, I think we should really iron out all installation issues that
> plagued NetBSD before and were scorned on say Slashdot i.e. provide easy
> install/live images with a gui installed, with optional extra variants with
> say
On Mon, Nov 21, 2022 at 10:10:57PM -0800, Chuck Silvers wrote:
> yes, there should be a way to tell sysinst to create UFS2ea rather than UFS2
> (or vice-versa if we make UFS2ea the default in sysinst). this was on my
> list of outstanding issues but I think I was thinking that Martin would
> take
On Thu, Jan 19, 2023 at 05:33:03AM +, Thomas Mueller wrote:
> >From /usr/src/UPDATING,
>
> Recent changes:
> ^^^
>
> 20230112:
> New binutils require an updated ld.elf_so. If you are doing
> (unsupported) in-place self builds (with the -E flag to build.sh),
>
On Fri, Feb 24, 2023 at 06:22:50PM -0500, Tom Lane wrote:
> So it doesn't seem to be a problem with DNS infrastructure, but the
> installer doing something wrong.
You should be able to test this again easily w/o doing a real installation
and gather more information by using the Utility
On Fri, Mar 31, 2023 at 02:10:46PM +0200, Thomas Klausner wrote:
> g++ in -current doesn't get this symbol when you include limits.h
> (which lua does, since this is still C code) because of (from
> /usr/include/machine/limits.h):
>
> #if defined(_ISOC99_SOURCE) || (__STDC_VERSION__ - 0) >=
On Fri, Mar 31, 2023 at 03:30:56PM -, Michael van Elst wrote:
> There is magic involved.
You mean: there are bugs - bah :-/
Martin
On Fri, Mar 31, 2023 at 02:27:17PM -, Michael van Elst wrote:
> c++ also doesn't define __STDC_VERSION__ nor _ISOC99_SOURCE.
It defines the former but not the latter:
> c++ -dM -E - < /dev/null | fgrep __STDC_VERSION__
#define __STDC_VERSION__ 201710L
> c++ -dM -E - < /dev/null | fgrep
On Wed, Feb 15, 2023 at 03:09:37PM +0100, Christian Groessler wrote:
> Hi,
>
> probably known and considered not important, but I wanted to mention that
> I'm getting warnings like this when building a release:
Sounds like a local problem - what is in your $GZIP (and why)?
Martin
On Thu, Feb 16, 2023 at 06:18:54AM +1300, Lloyd Parkes wrote:
> I saw this too. I think the way we select the gzip compression level (using
> the GZIP environment variable) is now deprecated for some reason.
I have not seen it anywhere, but I see we set GZIP=-9n for pax -z
in
On Thu, Feb 16, 2023 at 06:37:36AM +1300, Lloyd Parkes wrote:
> Oh, it's used to pass the compression level though pax to gzip. That's
> explain it. Maybe we should switch to --use-compress-program="nbgzip
> -LEVEL"???
The problem is that we only have ${TOOLDIR}/nbpax, but that invokes gunzip
via
On Thu, Jul 06, 2023 at 10:10:37PM -0400, Lwazi Dube wrote:
> ec->ec_flags |= ETHER_F_ALLMULTI;
> -ETHER_UNLOCK(ec);
I fixed it slightly different, thanks for catching it!
Martin
On Sun, Jul 09, 2023 at 02:52:01PM +0100, David Brownlee wrote:
> Does anyone know offhand what alignment Linux/FreeBSD/OpenBSD pick for
> MBR formatting?
You should avoid MBR :-)
I don't know other systems defaults, but sysinst uses 4k for small
disks and 2m for bigger, unless you switch to
On Sun, Jul 09, 2023 at 08:54:56PM +0100, David Brownlee wrote:
> In practice I think it would be better not to penalise current use of
> "small" (120GB SSD or 64GB or or CF/USB devices) for an edge case of
> older hardware
I am not sure what you see as penalty here.
I think two factors made the
On Sun, Jun 04, 2023 at 02:40:16PM +0200, Thomas Klausner wrote:
> Hi!
>
> I just tried updating my -current but the build failed:
>
> build.sh -j 32 -x -V MKDEBUG=yes -V MKDEBUGLIB=yes -V MKLLVM=yes -V
> NOGCCERROR=yes -T /usr/obj/tools.gcc -m amd64 -O /usr/obj/src.amd64 -D
>
On Wed, Jun 07, 2023 at 08:55:46AM +1200, Lloyd Parkes wrote:
> The httpd manual page describes how to invoke Lua scripts, but these
> aren't CGI scripts. The manual page also describes how to invoke CGI
> scripts of course.
I would try a special document root for the port 80 instance and
place
On Mon, Jul 31, 2023 at 11:59:12PM +0200, logothesia wrote:
> route(8) for a while, and all my attempts to coax it into inserting a
> route to an interface in a different subnet than the gateway's so far
> have failed.
route add -iface
should work.
> > I expect that you will need to dig
On Sun, Jul 30, 2023 at 10:05:15AM +0200, Jan-Hinrich Fessel wrote:
> Hej there,
>
> tried that on several fresh installations now with src grabbed via cvs
> checkout. No one else seeing this?
> I am somewhat lost in how to fix this apart from modifying the source list
> (md.amd64 that would
On Sun, Jul 30, 2023 at 03:18:32PM +0200, Jan-Hinrich Fessel wrote:
> Oh yes:
> build.sh command:./build.sh -U -j 2 -M /usr/obj -O /usr/obj -R
> /usr/src/releasedir.NetBSD-10.99.6-amd64 -D
> /usr/obj/destdir.NetBSD-10.99.6-amd64 -X /usr/xsrc -x -V MKCOMPAT=no release
> install-image
>
>
On Sat, Aug 12, 2023 at 06:41:14AM -0500, John D. Baker wrote:
> The recent mega-pull-up of heimdal, bind, and OpenSSL 3.0 to
> NetBSD-10.0_BETA:
>
> https://mail-index.netbsd.org/source-changes/2023/08/11/msg146890.html
>
> breaks builds which set MKNSD=YES.
Should be fixed now.
Martin
On Wed, Jun 21, 2023 at 02:20:25PM +0200, Sagar Acharya wrote:
> Also, linux doesn't have fsck_ffs and debian had support for ufs in ufsutils
> a long time ago.
>
> I highly recommend that for such cases you have a small standalone source
> which can be built for correcting such errors which
On Wed, Jun 21, 2023 at 12:12:35PM +0200, Sagar Acharya wrote:
> My NetBSD system has gotten corrupted. How do I mount my NetBSD partition on
> voidlinux?
The typical recovery doesn't involve any other OS. If your kernel
works and finds the / partition you can "boot -sa" and select
/rescue/init
On Wed, Jun 21, 2023 at 08:39:45PM +0200, Sagar Acharya wrote:
> I am on a NetBSD 10 install now after sabotaging my fully good alpine due to
> constraints of sd card. The memory card from which I want to retrieve data is
> mounted at sd0
>
> $ fsck_ffs /dev/sd0a
> /dev/rsd0a[1] Floating point
On Wed, Jun 21, 2023 at 08:43:45PM +0200, Sagar Acharya wrote:
> $ dkctl sd0 listwedges
> /dev/rsd0: no wedges configured
>
> What are wedges? I get sectors which are 512 bytes long on physical disk.
With "dkctl sd0 addwedge " you can use arbitrary "partitions" on disk sd0
without modifying
On Thu, Jun 22, 2023 at 03:47:27PM +0200, Sagar Acharya wrote:
> I need something to repair this ufs2 partition.
You did not answer the partitioning questions and it is hard to follow
what you are doing and seeing.
You can repair it easily with NetBSD's fsck(8).
You can analyze it close with
On Sat, Jul 01, 2023 at 05:47:53PM -0400, Andrew Cagney wrote:
> just fyi, had to tweak this when building; to be honest I'm a bit puzzled
Yes, puzzling - it is not clear what standard apple tools default to
after latest updates.
The easy fix is to use HOST_CFLAGS= (or is it HOST_CXXFLAGS?)
On Thu, Dec 21, 2023 at 04:59:36PM +0100, Fekete Zoltán wrote:
> Is there any usb wifi chipset left on the list without a maintainer? I could
> take one for my study if I could purchase hardware for that. Might be a
> win-win.
I think we have everything covered for the USB chipsets where we
On Thu, Dec 21, 2023 at 07:51:07AM +0100, Fekete Zoltán wrote:
> Is anybody working on the same driver?
> Has anybody tried it so far?
> Is there any known hard limitation which blocks the porting to NetBSD?
We have patches for that chipset for the new FreeBSD based wifi stack
(and I have
On Sun, Dec 31, 2023 at 02:19:01PM +, Chavdar Ivanov wrote:
> As far as I could tell, the only place where this is defined in the system is
> in
>
> nm /usr/libexec/lto-wrapper | grep unlink_if
> 0006a842 T unlink_if_ordinary
>
> No idea about this, my google-fu apparently is not
On Fri, Dec 22, 2023 at 08:06:40AM +0700, Robert Elz wrote:
> Date:Thu, 21 Dec 2023 20:26:29 +0100
> From:=?ISO-8859-1?Q?Fekete_Zolt=E1n?=
> Message-ID: <8bc45468-b662-4615-9c61-9981bd2b1...@minux.hu>
>
> | Using USB would have been a good starting point from a
On Mon, Dec 25, 2023 at 12:58:27PM -0500, xuser wrote:
> Does any one know how to setup ip forwarding on netbsd?
In /etc/sysctl.conf add:
net.inet.ip.forwarding=1
net.inet6.ip6.forwarding=1
Martin
On Thu, Jan 25, 2024 at 10:52:30AM +0100, Adam wrote:
> > All builds are working again, if this still fails for you there must be
> > a local problem in your setup.
> >
> > Martin
>
> My setup is cross-building NetBSD on macOS.
But that doesn't explain the issues you are seeing, no host tools
On Sat, Jan 27, 2024 at 02:49:09AM +0700, Robert Elz wrote:
> | It doesn't accept implicit function declarations.
>
> Yes, that's fine - you do not need to explain the issue, we all
> understand that --- but there's supposed to be a prototype for
> the function, it isn't intended to be
On Fri, Jan 26, 2024 at 09:09:30PM +0100, Adam wrote:
> Simple and elegant. No hacks involved.
Because the declaration in the relevant header is already there, and
the order does not matter. But the #ifdef around the declaration needs
to do the right thing. No need to move things around and its
On Sat, Jan 27, 2024 at 03:33:06PM +0700, Robert Elz wrote:
> Now that Christos moved the function around, that declaration in the
> header is just noise, and could be removed.
Yes, that would be consistent then (but isn't it against the new style
rules?)
Martin
On Thu, Feb 01, 2024 at 03:13:42PM +, RVP wrote:
> This looks like a bug in NetBSD. Minimal reproducer:
>
> ```
> $ cat tit
> tit|TermInfo Test,
> # if the second number is >32767, it disappears!
> use=num, use=max,
> # putting the bigger one first makes "promotion" happen.
> #
On Fri, Jan 26, 2024 at 03:03:24AM +0700, Robert Elz wrote:
> Date:Thu, 25 Jan 2024 20:12:36 +0100
> From:Adam
> Message-ID:
>
> | Correct, _LIBC_INTERNAL is not defined for tools/compat.
>
> I wonder what the difference is between your environment, and
> a
On Thu, Jan 25, 2024 at 09:20:50AM +0100, Adam wrote:
> Reverting lib/libc/hash/md2/md2.c to v1.7 fixes the build.
All builds are working again, if this still fails for you there must be
a local problem in your setup.
Martin
On Fri, Jan 26, 2024 at 04:42:43PM +0100, Adam wrote:
> % cat /tmp/pkgsrc/obj.aarch64/tools/compat/md2.d
[..]
> md2.o:
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/assert.h
> md2.o: /dist/src/tools/compat/md2.h
> md2.o:
On Sat, Jan 20, 2024 at 10:50:27AM +0100, Adam wrote:
> NetBSD-current fails to build on aarch64.
>
> Please, help :)
As you can see here:
https://releng.NetBSD.org/cgi-bin/builds.cgi
it was not only evbarm/aarch64 affected, but all builds were broken.
Robert fixed it in the meantime.
On Sat, Jan 20, 2024 at 05:19:25PM +0700, Robert Elz wrote:
> Not that particular one I didn't, didn't know about that particular
> breakage, will look at it now.
Oops, mixed the breakage - but thanks for fixing it now :-)
Martin
On Sun, Nov 19, 2023 at 02:44:04PM +0100, Lizbeth Mutterhunt, Ph.D wrote:
> As axen0 fails to connect, I want to try the wlan0, but it won?t be able to
> make a wlan0. I can?t find the iwm module in kernel config. Does it be named
> differently (I?ve got it from FreeBSD) or is just the
On Thu, Apr 25, 2024 at 10:43:43PM -, Christos Zoulas wrote:
> Thank you. I think there should be one compat set list, not one
> for each machine_arch, and only have a ad or md machine specific
> file for the parts that are different. I.e. there should be a
> base32/mi and a base32/shl.mi
On Sat, May 04, 2024 at 12:12:35AM +0300, Andrius V wrote:
> corrupted as well). After some actions crash is not reproducible
> anymore though. I guess issue can be considered as some kind of fluke.
Did you run a forced fsck on the file system?
I usually boot single user and then do something
On Tue, May 14, 2024 at 05:39:21PM +, nia wrote:
> > Which reminds me: whatever happened to the new wifi project?
[..]
> So, still ongoing, just slowly
Yes, sorry about that - it will get a lot more attention now that 10.0,
9.4 and 8.3 are out of the door.
Martin
On Sat, Jun 01, 2024 at 06:41:19PM +0100, Chavdar Ivanov wrote:
> ptyfsoldnodes fix:
> [1] Bad system call ${HOST_SH} "${MAKEDEV_DIR}/MAKEDEV" -s
You need to run a new kernel before you install new userland.
In this case you hit the new version of dup3(2) which crashes on the
old
601 - 656 of 656 matches
Mail list logo
