Hi folks,
I've just basically re-installed my NetBSD/amd64 to -current of the 26st of
October and I'm running into libGL init issues:
> glxgears
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to
Hi Christos,
Thanks for your blacklistd, its soo much more lightweight that the others i've
seen in pkgsrc; really frees up my small NAS. I've installed the -current
version as in tree.
There are a few oddities though, and maybe you could enlighten me on those.
First of all your name is still
Hi folks,
i'm experiencing problems on evbarm when i try to install a package, in this
case pkg_install itself.
I've compiled the kernel and its userland using ./build.sh -mevbarmv5-el ...
and its running fine. When i try to install a package however, i get:
=== Install binary package of
On Mon, Jul 16, 2018 at 03:11:06AM +, NetBSD source update wrote:
> cvs update: `src/share/man/man4/ipkdb.4' is no longer in the repository
...
i must have missed a discussion, but why has IPKDB removed? Even if
disfunctional, it could better be repaired or at least let it work in Qemu?
Dear folks,
in my attempt to clean up make(1) I stumbled on the following duplicate code.
It was replaced by the cached_stat() addition but the old code was not
removed.
I tested the unit-test and all output is identical as well as are all ATF
tests are still passing.
If there are no objections
On Sun, Jun 24, 2018 at 10:01:42PM +0200, Reinoud Zandijk wrote:
> On Wed, May 30, 2018 at 07:11:19PM +0800, Harry Pantazis wrote:
> > Continuing..
> >
> > This first errors are located in
> > src/sys/external/bsd/drm2/dist/drm/i915/intel_ddi.c and are specific
the patch:
Index: build.sh
===
RCS file: /cvsroot/src/build.sh,v
retrieving revision 1.327
diff -u -p -r1.327 build.sh
--- build.sh2 May 2018 07:34:44 - 1.327
+++ build.sh25 Jun 2018 18:26:34 -
@@ -1027,7
On Mon, Jun 25, 2018 at 10:29:30PM +0200, Kamil Rytarowski wrote:
> I'm usually going the other direction. If I hit a problem and an issue
> is not visible from a multi-job build (multiple processes print onto the
> same screen concurrently), I go for -j1. If this is still no enough I
> change the
. That said, i'm trying to get one
if the origional developers of NiLFS2 on Linux to contemplate to port the
changes into the linux version too but i haven't had a reply yet.
Please do share your views with me and i'd really like feature requests too!
With regards,
Reinoud Zandijk
Hi folks,
On Sun, Oct 11, 2020 at 04:10:00PM +0200, Reinoud Zandijk wrote:
> qemu-system-x86_64 -m 4096 -accel nvmm -smp cpus=2 -drive \
> file=work/wd0.img,format=raw -nographic -gdb tcp::1234 -net nic -net \
> tap,ifname=tap0,script=no
>
> Now is this an qemu related prob
if any user time. When compiling on
both virtual processors in qemu I can get 70+% cpu time in systat but only
1.5% user and the rest all system time.
I'm not sure how its measured but something is off for sure or is this done by
design?
With regards,
Reinoud Zandijk
signature.asc
Description
Hi Jonathan,
On Sat, Jul 25, 2020 at 10:52:48PM +0100, Jonathan Perkin wrote:
> I needed a NetBSD-current system for testing pkgin changes, and figured I
> may as well also set it up for daily package builds.
>
> So if anybody would like a repository for the latest packages then head over
> to
On Mon, Nov 09, 2020 at 10:10:56AM +, nia wrote:
> i run into it on real hardware, thinkpad t60.
>
> my preference is:
>
> - when booting in a VM, if there is no RNG device attached,
> the system should print a warning with instructions on how
> to attach the device.
In practice this
On Sat, Nov 07, 2020 at 06:12:34PM +1100, matthew green wrote:
> this is an update on my previous testing. i've excluded
> amd64 release builds from this set, takes too long ;)
Indeed remarkable! I assume you build the same source tree on the various
versions? Did you use the benchmarking stuff
Hi folks,
On Mon, May 18, 2020 at 09:41:17PM +, Andrew Doran wrote:
> Finally got around to trying this. Having beaten on it for a while with
> real hardware I don't see any problem with swapping over NFS on 9.99.63.
>
> On Sat, May 02, 2020 at 12:06:48PM +1000, Paul Ripke wrote:
>
> > I
On Tue, Dec 29, 2020 at 10:02:44AM +, Thomas Mueller wrote:
> > On Tue, 29 Dec 2020, Thomas Mueller wrote:
> > > I tried to dd to /dev/sd2 (or whatever the number was), and it looked
> > > good on the screen, no error message, but nothing happened on the USB
> > > stick.
>
> > 3
I'd like to fix this ASAP but what is the correct way of dealing with this? Is
this an i386 failure or should code just not use bus_space_read_8() or
bus_space_write_8() ?
In the VirtIO case, it doesn't have to be written atomically though.
What I could do is define a bus_space_write_8()
On Thu, Jan 21, 2021 at 11:45:25AM +, Chavdar Ivanov wrote:
> On Sat, 21 Nov 2020 at 16:37, Chavdar Ivanov wrote:
> I see there were a few recent commits around sys/dev/pci/virtio*. Just
> to mention that the presence of a virtio scsi device in a -current
> (from yesterday) vm under
On Thu, Jan 28, 2021 at 11:56:30PM +1100, Paul Ripke wrote:
> Just tried running a newly built kernel on a GCE instance, and ran into
> this panic. The previously running kernel is 9.99.73 from back around
> October last year.
>
> Anyone else tried booting -current on GCE recently? My suspicion
Hi Paul,
On Mon, Feb 01, 2021 at 06:46:17PM +1100, Paul Ripke wrote:
> On Mon, Feb 01, 2021 at 04:18:17PM +1100, Paul Ripke wrote:
> > However, forcing the full size virtio_net_hdr results in a working kernel!
...
> > Does that give any hints?
I'll double check all header size dependent code
Dear Paul,
On Sat, Jan 30, 2021 at 10:32:13PM +1100, Paul Ripke wrote:
> On Sat, Jan 30, 2021 at 12:37:31AM +0100, Reinoud Zandijk wrote:
> > On Thu, Jan 28, 2021 at 11:56:30PM +1100, Paul Ripke wrote:
> > > Just tried running a newly built kernel on a GCE instance, and ran int
On Fri, Jan 22, 2021 at 02:23:46PM +, Chavdar Ivanov wrote:
> After the latest virtio commits I no longer get the panic; the
> virtio-scsi device is recognized and the bus is created; however, a
> disk attached to it is not seen at all.
thats interesting, since nothing changed that ought to
Hi,
On Mon, Mar 29, 2021 at 10:57:36AM +0100, Chavdar Ivanov wrote:
> One of the patches needs patching... I thought nvmm was upstreamed and
> we didn't need the patches for it?
>
> Index: patch-target_i386_nvmm_all.c
> ===
> RCS
On Mon, Apr 19, 2021 at 04:41:32AM -, Michael van Elst wrote:
> ll...@must-have-coffee.gen.nz (Lloyd Parkes) writes:
>
> >On 17/04/21 6:30 pm, Lloyd Parkes wrote:
> >> I am using the Mercurial repository at https://anonhg.NetBSD.org/src
> >> for fetching the source code because it's nice and
On Sun, Jul 18, 2021 at 10:22:50PM +0300, Andrius V wrote:
> Today I upgraded my current setup from the latest nycdn image (amd64)
> using sysinst (update flow) and I was surprised that netbsd kernel was
> copied to file with unusual /netbsdIleNEk name instead of /netbsd.
> Thus, I needed to
On Mon, Jul 19, 2021 at 08:13:19AM +0300, Andreas Gustafsson wrote:
> David Holland wrote:
> > On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote:
> > > Logs below are usually more helpful.
> >
> > Right... I wonder what happened to bracket's error-matching script; it
> > usually does
Hi,
On Sat, Apr 16, 2022 at 06:07:46AM +0200, Matthias Petermann wrote:
> > 1) nvmm seems to work well in netbsd (I haven't run it yet) and there has
> > been bug fixing.
> >
> > 2) code flows between BSDs a lot, in many directions.
> >
> > 3) You could run diff to see what's different and why.
Dear folks,
since some time I noticed that the initial graphical console has small letters
but is later reset to big letters again. Is this intentional? How can I
preserve the smaller font? The 80x25 (or x31?) is quite huge on this monitor
and I really liked the smaller fonts!
Could switching to
Hi :)
On Sun, Jun 05, 2022 at 11:52:51AM +, RVP wrote:
> On Sun, 5 Jun 2022, Reinoud Zandijk wrote:
>
> > Could switching to the big fonts be an option?
> >
>
> With both fonts compiled in you can switch between them
> using:
>
> wsconsctl -dw font='Bol
On Fri, Jun 03, 2022 at 03:32:50PM +0200, Martin Husemann wrote:
> On Mon, May 02, 2022 at 04:22:56PM +0200, Martin Husemann wrote:
> > We are planning to branch netbsd-10 in about a week from now.
>
> As you may hgqapave noticed, this did not happen.
> Those who followed the NetBSD Foundation's
On Thu, Aug 04, 2022 at 09:53:25PM +0200, Matthias Petermann wrote:
> https://man.openbsd.org/virtio.4
>
> the OpenBSD virtio driver has its origin in NetBSD. Viocon Support was added
> later and not ported back yet. I am wondering how much effort it would take
> to merge it from
>
>
Hi,
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 a complete xfce4 one with FF etc. and provide complete installs like
Hi folks,
Qemu folks are talking about possibly dropping 32 bit HOST support for Qemu so
my question is, are there users of a 32 bit system that use Qemu?
If there is enough response I can forward these to the Qemu folks or else we
might indeed see 32 bit host support dropped/deprecated...
With
Hi,
On Sun, May 21, 2023 at 02:01:22PM +, Mathew, Cherry G.* wrote:
> I'm wondering if there are any nvmm(4) users out there - I'd like to
> understand what your user experience is - expecially for multiple VMs
> running simultaneously.
>
> Specifically, I'd like to understand if nvmm based
Hi,
On Sun, May 21, 2023 at 02:01:22PM +, Mathew, Cherry G.* wrote:
> I'm wondering if there are any nvmm(4) users out there - I'd like to
> understand what your user experience is - expecially for multiple VMs
> running simultaneously.
>
> Specifically, I'd like to understand if nvmm based
Dear folks,
i've updated my tree and built myself a new kernel but it won't boot anymore
and hangs in loading the amdgpu module in the bootloader. It is the same
-current version that worked before but something must have changed.
Anyone experiencing the same?
With regards,
Reinoud
36 matches
Mail list logo
