Re: p5-Module-Build weirdness

Same here, system front yesterday. ps ax|grep Build | wc -l returned 893. Almost killing the system, but I am still waiting. I did the build only to try this report, I otherwise have the same package from August. Chavdar On Mon, 13 Nov 2017, 13:55 Thomas Klausner, wrote: > Hi!

Re: Remove fortune quotes attributed to or providing admiration of Adolf Hitler [pr bin/52735]

At times I thought of suggesting to draw this up to a close, perhaps move a few quotes to the offensive section to placate the PC brigade, but it seems kinda nice to follow this dialogue, which while presenting opposing opinions is still being held in a very civilised way... Cheers, Chavdar On

iwn failure on -current (XEN3_DOM0)

to be OK, I was able to start a couple of DOMUs, so the normal Xen setup with xenkernel 4.8.2 and xentools 4.8.2 appeared functional (modulo a panic when I powered off one of the DOMUs, no idea here). Any pointers? Chavdar Ivanov --

Re: iwn failure on -current (XEN3_DOM0)

> ci4...@gmail.com (Chavdar Ivanov) writes: > >>Here my point was that iwn used to work under XEN3_DOM0 a few months >>ago and is not working now, > > Hmm. iwn is working on bare metal for me. It should work on XEN3_DOM0. > >>which may indicate some problem or >

Re: iwn failure on -current (XEN3_DOM0)

On 19 November 2017 at 08:01, Michael van Elst <mlel...@serpens.de> wrote: > ci4...@gmail.com (Chavdar Ivanov) writes: > >>I used to run DOM0 on xen4.8, the wireless interface worked for the >>DOM0, although I could never make the bridge work (it worked with the >&

Re: iwn failure on -current (XEN3_DOM0)

Thanks for the tip! On Sun, 19 Nov 2017 at 18:31, <m...@netbsd.org> wrote: > On Sun, Nov 19, 2017 at 11:11:44AM +, Chavdar Ivanov wrote: > > Here my point was that iwn used to work under XEN3_DOM0 a few months > > ago and is not working now, which may indicate some prob

Re: Remove fortune quotes attributed to or providing admiration of Adolf Hitler [pr bin/52735]

I agree with you. My comment was much weaker, but the intention was the same. Chavdar Ivanov On Sat, 18 Nov 2017 at 16:41, Jaromír Doleček <jaromir.dole...@gmail.com> wrote: > I very strongly object to against anything appeasing any SJW or PC trolls, > and I'm against removing

Re: iwn failure on -current (XEN3_DOM0)

link between two floors, then the Virgin Media SH3 etc... ). So there is some regression as far as Xen is concerned around the USB subsystem. Again it may be relevant to port-xen@, so I am forwarding there as well. Chavdar Ivanov On 19 November 2017 at 22:21, Chavdar Ivanov <ci4...@gmail.

Re: Compile failure in nand.c

on your kernel since updating. > > Cheers, > Jared > > > On Tue, 14 Nov 2017, Chavdar Ivanov wrote: > >> Hi, >> >> I am getting: >> ... >> # compile nand/nand.o >> /home/sysbuild/amd64/tools/bin/x86_64--netbsd-gcc -O2 -g -std=gnu99 &

anoncvs.netbsd.org

. Yesterday I did a successful build, so it is something recent. The tcpdump trace doesn't tell me much. Do I have some local problem, or perhaps my IP has fallen into some deep hole? Chavdar Ivanov --

Re: anoncvs.netbsd.org

Thanks, I thought I had messed up something... Chavdar On 15 November 2017 at 11:46, Paul Goyette <p...@whooppee.com> wrote: > Others have reported similar issues. Waiting for admins to investigate. > > > > On Wed, 15 Nov 2017, Chavdar Ivanov wrote: > >> Hi, &

Re: anoncvs.netbsd.org

Working. Thanks. Chavdar On 15 November 2017 at 12:56, Christos Zoulas <chris...@astron.com> wrote: > In article <20171115115102.GG5815@quartz>, > Patrick Welche <pr...@cam.ac.uk> wrote: >>On Wed, Nov 15, 2017 at 11:31:05AM +, Chavdar Ivanov wrote:

Compile failure in nand.c

191:17: note: each undeclared identifier is reported only once for each function it appears in *** [nand.o] Error code 1 ... in my last few builds; I couldn't locate the missing symbol elsewhere. I am building now with the offending line #if-ed out. Chavdar Ivanov --

Xentools-4.8.2 build failure under -current

I noticed a recent bump in xentools and decided to try it; l have at the moment functioning 4.8.0. /usr/bin/iasl fails to compile tools/firmware/hvmloader/dsdt_anycpu.asl with syntax error on every occurrence of EISAID and DerefOf. Any idea why? Chavdar Ivanov

Re: netbsd-8 crash in ixg driver during booting

My (very uneducated) guess would be that for some reason adapter->num_queues does not get initialised. There have been quite a few commits recently here (although I am looking at -current, I suppose they have been done to 8 as well). Chavdar Ivanov On Thu, 9 Nov 2017 at 14:18

New amd64 8.99.6 panic

8092d485 in uvm_fault_internal () #7 0x802232b6 in trap () #8 0x80201263 in alltraps () ... Any ideas? I have reverted to 8.99.5, it is stable on this hardware. Chavdar Ivanov

Seamonkey build failure under -current

)}' crypto_kernel_load_auth_type(auth_type_t *ct, auth_type_id_t id); ^ /usr/pkgsrc/www/seamonkey/work/seamonkey-2.49.1/mozilla/config/rules.mk:882: recipe for target 'Unified_c_netwerk_srtp_src0.o' failed .. Is Seamonkey too old for -current nowadays? Chavdar Ivanov

Re: Linix Emulation

Thanks, that was it - I recall seeing something recently, as far as I remember it was a security issue. I should have checked sysctl before asking the question. Chavdar Ivanov On Wed, 25 Oct 2017 at 09:28 Robert Swindells <r...@fdy2.co.uk> wrote: > > Chavdar Ivanov <ci4...@g

Linix Emulation

said, GENERIC is unmodified and contains COMPAT_LINUX[32]. Any suggestion? Chavdar Ivanov

Re: ThinkPad T42 w/-current, no mouse in X

I used to have this on my two T61p's all the time and have asked the list previously. Switching to a text console and back sorted it usually, so I wasn't bothered too much. Using gdm, there was some kind of a trick I had to do to get the mouse working - I had move the mouse cursor around before

Intel CPU design flaw

Any comments in this part of the wood about https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/ ? Chavdar

Re: emacs user needed to help with PR bin/41954

Works perfectly well for me on -current 8.99.23 amd64 and emacs 25.3. Chavdar On Thu, 16 Aug 2018 at 06:45 Robert Elz wrote: > Hi all, > > One of the final remaining real (at least potential) sh related PRs > on my list to look at/fix is bin/41954 (from just about 9 years ago) > > A summary:

Re: no crash dumps

If you have Intel graphics, disable genfb. I had a few crash dumps, collected properly. On Tue, 28 Aug 2018 at 10:55 Robert Swindells wrote: > > Is anyone else having problems generating crash dumps ? > > The new drm code drops into ddb but typing "sync" just reboots the > system. >

Re: Build failure due to DRM intel i915

It has been been pretty good so far, actually. I also remove the old .obj directory when such big changes are introduced, the first distribution build I tried was successful. I'll repeat overnight. On Wed, 29 Aug 2018 at 12:07 Adam wrote: > > I upgraded CVS this morning (3 hours ago), built

amd64 build failure

With sources from a few hours ago on a clean (new) obj I get: # compile sa/cd9660.o /home/sysbuild/amd64/tools/bin/x86_64--netbsd-gcc -O2 -mno-red-zone -ffreestanding -fPIC -fshort-wchar -fno-strict-aliasing -fno-bu iltin -fno-stack-protector -Wno-error=unused-but-set-variable -std=gnu99

Minor sysutils/sysupgrade mod

Hi, In case someone uses sysutils/sysupgrade to upgrade to the next -current release, the above utility assumes the sets are in .tgz format. Obviously a simple global replacement of '\.tgz' with '.tar.xz' works. While it would be trivial to modify to support both, it probably is not worth the

Re: build.sh distribution failure for evbarm

On 11/03/18 04:50, m...@netbsd.org wrote: On Sat, Nov 03, 2018 at 04:44:18AM +, m...@netbsd.org wrote: Changing the actual triplets is probably a bad idea because the decisions are embedded in a lot of configure scripts in random third party code. But perhaps we need to rename things so

Panic on evbearm6

I just got: -- Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file "/home/sysbuild/src/sys/kern/subr_pool.c", line 864 Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] cpu0: Begin traceback... Nov 4

Re: Panic on evbearm6

The above panic is repeatable. On Mon, 5 Nov 2018 at 10:14, Chavdar Ivanov wrote: > > > > On 11/04/18 17:03, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > > >> This was on the original RPI Zero, 512MB RAM (dmesg shows for some >

Re: Panic on evbearm6

On 11/04/18 17:03, Michael van Elst wrote: ci4...@gmail.com (Chavdar Ivanov) writes: This was on the original RPI Zero, 512MB RAM (dmesg shows for some reason total 448MB, avail 434MB). As I said, it was running python3.7.1 tests at the time, so it may have been overloaded. It has only

Re: Panic on evbearm6

Building Go toolchain1 using /usr/pkg/go14. Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1. - I will try to rebuild go14 just in case. On Mon, 5 Nov 2018 at 10:54, Chavdar Ivanov wrote: > > The above panic is repeatable. > On Mon, 5 Nov 2018 at 10:14, C

Re: Panic on evbearm6

: > > On 04/11/2018 12:09, Chavdar Ivanov wrote: > > I just got: > > -- > > > > Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic > > assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file > > "/ho

build.sh distribution failure for evbarm

ile failed. --- The last (third) attempt was with fresh obj directory; I also did 'make cleandir' in the src directory just in case (in the past this has helped). Chavdar Ivanov --

Re: build.sh distribution failure for evbarm

the RPI kernel for the two boards I have; never went down to figure out how to restrict it building all the other evbarm kernels and images, but thought that anyway it is useful to know if they build. On Fri, 2 Nov 2018 at 13:36, Robert Swindells wrote: > > > Chavdar Ivanov wrote: > &

Re: Panic on evbearm6

2018 at 16:00, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > >And there is another one on the same system from tonight: > >--- > >panic: kernel diagnostic assertion "(armreg_fpexc_read() & VFP_FPEXC_EN) > >== 0" fa

Re: Rust, pkgsrc

On 11/07/18 09:27, Chavdar Ivanov wrote: On 11/06/18 18:50, Havard Eidnes wrote: Yes. I had a similar problem. The build would fill up the /tmp/ directory and die from exhausted resources. I had /tmp/ created with tmpfs and had a constraint of 64M. The answer for me was to create /tmp

Re: Rust, pkgsrc

On 11/07/18 10:21, Chavdar Ivanov wrote: On 11/07/18 09:27, Chavdar Ivanov wrote: On 11/06/18 18:50, Havard Eidnes wrote: Yes. I had a similar problem.  The build would fill up the /tmp/ directory and die from exhausted resources.  I had /tmp/ created with tmpfs and had a constraint

Re: Rust, pkgsrc

On 11/07/18 09:27, Chavdar Ivanov wrote: On 11/06/18 18:50, Havard Eidnes wrote: Yes. I had a similar problem.  The build would fill up the /tmp/ directory and die from exhausted resources.  I had /tmp/ created with tmpfs and had a constraint of 64M.  The answer for me was to create /tmp

Re: Rust, pkgsrc

On 11/06/18 18:50, Havard Eidnes wrote: Yes. I had a similar problem. The build would fill up the /tmp/ directory and die from exhausted resources. I had /tmp/ created with tmpfs and had a constraint of 64M. The answer for me was to create /tmp in /etc/fstab with tmpfs and no size

Re: build.sh distribution failure for evbarm

It would benefit from some clarification regarding the ARM ecosystem indeed. So far I've always used ' evbarm' for my RPI builds and wondered if I can skip the building of the rest. Anyway, with 'evbearmv6hf-el' the build completed successfully. On Fri, 2 Nov 2018 at 19:42, Greg Troxel wrote: >

Re: sysutils/lsof stopped working for non-root user

Christos Zoulas wrote: > On Sep 27, 8:51am, ci4...@gmail.com (Chavdar Ivanov) wrote: > -- Subject: Re: sysutils/lsof stopped working for non-root user > > | So is this expected and intended consequence, bug or still unfinished > | part of the project? Just curious (it runs on FreeBSD-

sysutils/lsof stopped working for non-root user

Hi, On amd64 -current from yesterday the latest lsof returns immediately if invoked by non-root user. I am sure it worked a few weeks ago. It works ok for the root. ktruss /usr/pkg/sbin/lsof returns only: fcntl(0x4, 0x3, 0)= 4194305 emul(netbsd) fcntl(0x4, 0x4, 0x41) = 0

Re: sysutils/lsof stopped working for non-root user

So is this expected and intended consequence, bug or still unfinished part of the project? Just curious (it runs on FreeBSD-current, latest CentOS, NetBSD-8). On Wed, 26 Sep 2018 at 17:33, Christos Zoulas wrote: > > In article > , > Chavdar Ivanov wrote: > >-=-

Re: sysutils/lsof stopped working for non-root user

wrote: > > On Thu, Sep 27, 2018 at 07:34:25PM -0700, John Nemeth wrote: > > On Sep 27, 2:56pm, Christos Zoulas wrote: > > } On Sep 27, 8:51am, ci4...@gmail.com (Chavdar Ivanov) wrote: > > } > > } | So is this expected and intended consequence, bug or still unfinished >

Re: xsrc build broken for most platforms.

The build maybe successful, but Xorg can't run for me with an intel 530 graphics: X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 Build Operating System: NetBSD/amd64 8.99.30 - The NetBSD Foundation, Inc. Current Operating System: NetBSD tarkus 8.99.30 NetBSD 8.99.30 (GENERIC) #1: Wed

Re: Install of 8.99.30 libcrypto.so.12 not found

I had the same earlier. I added pkg_install using /usr/sbin/pkg_add, this brought the necessary libraries for pkgin, which I then installed and setup. Obviously it didn't work from the installation cd. On Fri, 18 Jan 2019 at 01:02, Ron Georgia wrote: > > I am installing NetBSD-8.99.03-amd64.

Re: Panic on a -current from 13/12/2018

On Fri, 21 Dec 2018 at 22:05, Cherry G. Mathew wrote: > > On December 22, 2018 2:24:44 AM GMT+05:30, Chavdar Ivanov > wrote: > ... > > > >It is interesting also that when NetBSD is ran under XenServer (XCP-NG > >actually) in PV mode, benchmarked against the s

Re: Panic on a -current from 13/12/2018

sec. On Wed, 19 Dec 2018 at 12:36, Chavdar Ivanov wrote: > > The workaround is fine. In the mean time I upgraded my VirtualBox > installation to 6.0 (released yesterday) and will check again. > > While here I did some, admittedly not very scientific, benchmarks on > netw

Re: Panic on a -current from 13/12/2018

had to adjust the time after waking the host up. On Sat, 15 Dec 2018 at 10:59, Chavdar Ivanov wrote: > > Hi, > > On 8.99.27 AMD64 running under VirtualBox I got this morning the panic > in http://ci4ic4.tx0.org/ci4ic4-panic-01.png > > I have the coredump, if it is of interes

Re: Panic on a -current from 13/12/2018

active. I switched the NIC emulation for the NetBSD guest to virtio-net, now it behaves as before, surviving a hibernation. There was a VirtualBox upgrade a few weeks ago, perhaps the problem is there. On Sun, 16 Dec 2018 at 15:55, SAITOH Masanobu wrote: > > Hi. > > On 2018/12/16 18:09, Ch

Re: Panic on a -current from 13/12/2018

ed the panic thinking it may be relevant in other use cases. On Mon, 17 Dec 2018 at 07:49, Masanobu SAITOH wrote: > > On 2018/12/17 1:09, Chavdar Ivanov wrote: > > I have no idea. As I said, it is running under VirtualBox on a Windows > > 10 host; I put the host in hibernation whi

Panic on a -current from 13/12/2018

Hi, On 8.99.27 AMD64 running under VirtualBox I got this morning the panic in http://ci4ic4.tx0.org/ci4ic4-panic-01.png I have the coredump, if it is of interest. I thought it might be useful, as it is apparently in the wm driver. Chavdar --

Running NetBSD-current in PV mode under Xen

Hi, I was trying to respond to and old pr of mine - https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=47486 - and went through the installation of XCP-NG (after I found out about the existence of this project and that Citrix has apparently changed some licensing conditions after

Re: Running NetBSD-current in PV mode under Xen

fully functional virtualisation platform. A loss for Citrix, methinks. On Fri, 30 Nov 2018 at 08:38, Stephen Borrill wrote: > > On Thu, 29 Nov 2018, Chavdar Ivanov wrote: > > I was trying to respond to and old pr of mine - > > https://gnats.netbsd.org/cgi-bin/query-pr-sing

Re: issues with touchpad after update

Just to add my 2c - the Synaptics behaviour on -current has been much much better since these recent changes; I am not too bothered by the multitouch gestures, although two finger scrolling would be nice. These may work, I haven't tried changing any hw.synaptics sysctls yet. The random jumps

Re: issues with touchpad after update

Thanks, will try it as soon as I get the laptop into NetBSD, in a few hours. On Fri, 7 Dec 2018 at 07:25, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > >I am not aware if we have some support for accelleration. > > The X server does acceleration

Running NetBSD as VirtualBox VM using GPT slices

Hi, The following probably won't be of much use, but perhaps is worth mentioning. I have an HP laptop with a main nvme disk running Windows 10 and VirtualBox. There is also a GPT-partitioned second 750GB disk, holding some data plus several EFI-booting systems, one of which is NetBSD-current. I

Re: How to boot in UEFI mode: practically no documentation

Just to say that all this worked for me. I had some 100gb left free on a GPT disk with a few other systems installed and finally decided to try EFI boot, using the efi boot image from releng. I only had to create /dev entries for dk16, dk17 and dk18, 16 were not enough. I also had to disable

Re: HEADS UP: drmkms update incoming

I managed to build full distribution after initially testing the git repo. It is running fine on my HP Envy 17. As before, the NVidia microcode is missing for the GeForce GTS/950m, although it is otherwise configured, so I have to disable nouveau*; I also have to disable genfb, but after that

mysql55-client and mariadb55-client build failure

Hi, Under recent -current (from yesterday) and update pkgsrc both packages fail identically as follows: --- ] /usr/pkgsrc/databases/mysql55-client/work/mysql-5.5.62/vio/viosslfactories.c: In function 'new_VioSSLFd':

Re: openssl problem

In case somebody is interested, the above setup actually works under NetBSD, roughly following that advise, applied to the different locations and initial configuration files for nginx and php-fpm (I did install meta-pkgs/php72-extensions beforehand). On Sun, 25 Nov 2018 at 20:25, Chavdar Ivanov

openssl problem

Hi, I am trying to install InvoiceNinja(1) on -current, following the recipè on (2), using php72, php-fpm, mysql 5.7. I have got most of the components installed - nginx, php-fpm, mysql. nginx is running. When I try to configure the self-signed certificate for nginx, I am stuck at: #

Re: openssl problem

On Sun, 25 Nov 2018 at 20:12, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > ># openssl genrsa -des3 -passout pass:x -out ininja.pass.key 2048 > > >18446744073709551615:error:28078065:UI > >routines:UI_set_result_ex:result too > >smal

Re: xsrc build broken for most platforms.

На 01/03/19 в 03:29, matthew green написа: >> /usr/X11R7/lib/modules/drivers/intel_drv.so: Undefined PLT symbol >> "AllocateFontPrivateIndex" (symnum = 449) >> >> This is a build from a few hours ago. > OK, this should be fixed now, but i have a report that intel driver > is still not 100%

Recent XEN3_DOM0 begaviour

Hi, I recently restored my earlier NetBSD/XEN setup on an old(ish) HP EliteBook laptop; it all went rather well using xen packages for 4.11. I then added a couple of disks to the system (one - the internal mSATA, the other - on the tray replacing the DVD) with the intention to use the second one

Re: Recent XEN3_DOM0 begaviour

New Year! On Sun, 30 Dec 2018 at 22:03, Michael van Elst wrote: > > ci4...@gmail.com (Chavdar Ivanov) writes: > > >Hi, > > >menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz > >dom0_mem=2048M > > >Is there any means to force XEN3_DOMU to use

Re: Panic on a -current from 13/12/2018

sanobu SAITOH wrote: > > Hi! > > > > On 2018/12/17 19:38, Chavdar Ivanov wrote: > >> I went through a series of tests. It is indeed that point the panic > >> takes place, the two parts of the screendump are in > >> > >> http://ci4ic4.tx0.org/nb-panic

Re: emacs26 fails to build on current

On Thu, 24 Jan 2019 at 16:41, Riccardo Mottola wrote: > > Hi, > > when trying to update packages, emacs26 fails. > The errors are: > > => Generating post-install file lists > => Checking file-check results for emacs26-26.1nb6 > ERROR: >

Built-in vs. Modular Xorg under -current

Hi, On the same hardware (HP Envy 17, Intel 530 + NVidia 950m) I have two different installations, one using built-in Xorg, the other - Modular. The rest of the system is identical - kernel and userland - from a couple of days ago. The modular Xorg packages were built by a separate -current

Re: Built-in vs. Modular Xorg under -current

/extensions/libglx.so: Undefined symbol "glXGetProcAddressARB" (symnum = 492) Maybe I was wrong to build this with '-u', I might try a full build later. On Sun, 31 Mar 2019 at 22:00, Chavdar Ivanov wrote: > > Thanks, I'll check it out right away. > > Chavdar > >

Re: Built-in vs. Modular Xorg under -current

Thanks, I'll check it out right away. Chavdar On Sun, 31 Mar 2019 at 21:21, matthew green wrote: > > > Is there anything I might be missing or our built-in Xorg is lacking > > for this hardware? > > this may be old Mesa on your intel GPU not supporting that. > > we're very close to switching

pkgsrc/doc/guide build failure on -current (more jemalloc fallout)

Hi, I get: . -> Building pdf output [Checking tools for typesetting...OK] env SP_ENCODING=iso-8859-1 SGML_CATALOG_FILES= openjade -d /usr/pkgsrc/doc/guide/work/pkgsrc-guide-20190407/share/default.dsl -c /usr/pkgsrc/doc/guide/work/pkgsrc-guide-20190407/share/catalog -c

Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)

OK, I will file a PR against openjade. On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote: > > On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > > : > > /home/sysbuild/src/external/bsd/jemalloc/lib/../dist/src/arena.c:271: > > Failed assertion: "

Re: pkgsrc/doc/guide build failure on -current (more jemalloc fallout)

I've files pkg/54105. On Mon, 8 Apr 2019 at 09:51, Chavdar Ivanov wrote: > > OK, I will file a PR against openjade. > > On Mon, 8 Apr 2019 at 08:18, Martin Husemann wrote: > > > > On Sun, Apr 07, 2019 at 08:21:07PM +0100, Chavdar Ivanov wrote: > > > : >

Re: Built-in vs. Modular Xorg under -current

and XFCE4, but works OK under ctwm. Go figure... On Mon, 1 Apr 2019 at 07:42, Chavdar Ivanov wrote: > > The patch applied cleanly and the subsequent build finished. However, > the resulting Xorg does not even load GLX now: > ... > [ 412.701] (II) Loading /usr/X11R7/lib/modules/exten

Re: Mesa update

I was able to do a full build with a cvs update some 7 hours ago. Built-in Xorg is fine with AIGLX enabled now. On Sat, 6 Apr 2019 at 15:31, Patrick Welche wrote: > > On Sat, Apr 06, 2019 at 02:42:57PM +0100, Patrick Welche wrote: > > On Sat, Apr 06, 2019 at 05:18:58AM +1100, matthew green

Re: XEN3_DOMU no longer shutting down or rebooting

I tried with the overnight build, it seems to be OK now, works on at least two -current XEN3_DOMU guest. There were a few XCP-NG patches in between, though. On Wed, 20 Feb 2019 at 03:26, Cherry G.Mathew wrote: > > Chavdar Ivanov writes: > > > Yes, it is. This happens on: >

Re: XEN3_DOMU no longer shutting down or rebooting

On 3/1/19 в 1:02 AM, Mathew, Cherry G.: Would be could to know the dom0 versions it broke under, please. The DOMU is tCentOS 7.6, the virtualizer is XCP-NG v.7.6.

Re: XEN3_DOMU no longer shutting down or rebooting

with the other two options. Anyway, the initial topic - not rebooting NetBSD-current - now seems to have disappeared, so all is good with my 3-4 NetBSD DOMU's there. On Mon, 4 Mar 2019 at 08:28, Stephen Borrill wrote: > > On Fri, 1 Mar 2019, Chavdar Ivanov wrote: > > On 3/1/

Further jemalloc fallout

On yesterdays amd64 -current and fully updated pkgsrc, trying to build doc/guide I get: .. Writing HTML.manifest -> Building ascii output [Checking tools for typesetting...OK] /usr/bin/sed -e 's/[01];/"/g' pkgsrc.html > pkgsrc.tmp.html /usr/pkg/bin/w3m -dump -O iso-8859-1 -no-graph

xentools411 fails build

Hi, On today's -current amd64: gmake[2]: Entering directory '/usr/pkgsrc/sysutils/xentools411/work/xen-4.11.1/tools' /usr/pkg/bin/gmake -C xenpmd all gmake[3]: Entering directory '/usr/pkgsrc/sysutils/xentools411/work/xen-4.11.1/tools/xenpmd' gcc -I/usr/pkg/include -I/usr/include

Re: Further jemalloc fallout

ld it on amd64 -current as of yesterday. > > Are you sure this fix is applied? > http://cvsweb.netbsd.org/bsdweb.cgi/src/external/bsd/jemalloc/dist/src/jemalloc.c#rev1.7 > > Thanks, > rin > > On 2019/03/16 20:55, Chavdar Ivanov wrote: > > On yesterdays amd64 -

Re: Further jemalloc fallout

Still doesn't work for me with > uname -a NetBSD ymir 8.99.35 NetBSD 8.99.35 (GENERIC) #7: Sat Mar 16 13:57:26 GMT 2019 sysbuild@ymir:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC amd64 (talking about doc/guide). And neither does emacs-git, I am getting: CCLD

Re: zsh crash in recent -current

Well, after installing the unstripped zsh+modules and ncurses, I no longer get zsh any crashes. Plus, as I mentioned, there was some jemalloc updates a couple of days ago. Hence, no idea. On Thu, 14 Mar 2019 at 05:23, matthew green wrote: > > > (while none I have ever seen actually do, the > >

Re: Further jemalloc fallout

Indeed works now. Thanks. On Sat, 16 Mar 2019 at 21:18, Rin Okuyama wrote: > > On 2019/03/17 1:08, Chavdar Ivanov wrote: > > Still doesn't work for me with > > Puzzling... > > > (talking about doc/guide). And neither does emacs-git, I am getting: > >

Re: zsh crash in recent -current

That makes perfect sense. I'll rebuild it without this flag. On Thu, 14 Mar 2019 at 12:21, Geoff Wing wrote: > > On Thursday 2019-03-14 10:57 +, ci4...@gmail.com output: > :Well, after installing the unstripped zsh+modules and ncurses, I no > :longer get zsh any crashes. Plus, as I

Re: xentools411 fails build

xentools411 builds fine now. Next I might try it with the new ocaml from wip. On Sat, 16 Mar 2019 at 16:39, Manuel Bouyer wrote: > > On Sat, Mar 16, 2019 at 04:43:43PM +0200, Andreas Gustafsson wrote: > > Martin Husemann wrote: > > > IMO the most stupid warning ever added to gcc. I would just

Modular Xorg under VirtualBox

Hi, Has anyone tried to run amd54 - current under VirtualBox, but using modular Xorg, instead of the in-tree X? I built today the latest version from Xorg and can't ficure out what to do with the mouse driver. The graphics part of it works OK, although I can't yet resizing to work (xrandr lets me

Re: xdm receives no input

/etc/ttys ? On Tue, 12 Mar 2019 at 16:32, Patrick Welche wrote: > Had a go with the shiny new X (thanks!) on the sandy bridge laptop > which no longer likes SNA but works with UX, and xdm seems to sit > at the prompt waiting for something: > > #0 0x7f7ff344285a in poll () from

Re: zsh crash in recent -current

s/gor/got/. On the other hand there were some jemalloc changes overnight, so I will update the system first and then try to get zsh crashes. On Wed, 13 Mar 2019 at 11:32, Chavdar Ivanov wrote: > > Setting INSTALL_UNSTRIPPED=yes didn't work for me for zsh and ncurses, > I still had to

Re: zsh crash in recent -current

OK, I understand. I should carry on using it to see if it will break again and perhaps get something useful. On Wed, 13 Mar 2019 at 10:09, Martin Husemann wrote: > > On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote: > > I saw the one with the trashed history as wel

Re: zsh crash in recent -current

sets. On Wed, 13 Mar 2019 at 10:23, Chavdar Ivanov wrote: > > Thanks. One has to read the manuals from time to time... > > On Wed, 13 Mar 2019 at 10:21, Patrick Welche wrote: > > > > On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote: > > > I saw the one

Re: zsh crash in recent -current

, which is one of the failing ones. On Tue, 12 Mar 2019 at 21:58, Thomas Klausner wrote: > > On Tue, Mar 12, 2019 at 03:33:26PM +, Chavdar Ivanov wrote: > > On amd64 -curent from yesterday (and a couple of days earlier) I > > started to get zsh crashes when tab-completing (

Re: zsh crash in recent -current

Thanks. One has to read the manuals from time to time... On Wed, 13 Mar 2019 at 10:21, Patrick Welche wrote: > > On Wed, Mar 13, 2019 at 10:06:42AM +, Chavdar Ivanov wrote: > > I saw the one with the trashed history as well. > > > > I don't think it is zsh's problem

Re: xdm receives no input

Awesome, thanks! That's a thing which pops up from time to time, I've had it myself. On Wed, 13 Mar 2019 at 15:04, Patrick Welche wrote: > > On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote: > > /etc/ttys ? > > Absolutely right. This laptop's xdm worked befor

postinstall fix failure on -current

Hi, On a just updated -current tree I am getting: -- # sh /usr/sbin/postinstall -s /var/cache/sysupgrade/etc.tar.xz -s /var/cache/sysupgrade/xetc.tar.xz -d / fix fontconfig Note: Creating temporary directory /tmp/_postinstall.19073.0/etc.tgz Note: Extracting files from

zsh crash in recent -current

Hi, On amd64 -curent from yesterday (and a couple of days earlier) I started to get zsh crashes when tab-completing (files, directories, packages), similar to . Core was generated by `zsh'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7cf050211540 in permmatches ()

Re: current fails to boot on VirtualBox

/sysbuild/src/sys/arch/amd64/compile/GENERIC amd64 (I was hit by the mpd not being able to start, but that was discussed elsewhere). On Sat, 16 Feb 2019 at 21:59, Chavdar Ivanov wrote: > > Thanks, I will try the suggested fix after the build completes. > > On Sat, 16 Feb 2019 at 2

Re: current fails to boot on VirtualBox

(to finish what I intended to say above) and the break apparently is not directly connected to the newly introduced Hyper-V devices in GENERIC, which came to my mind earlier. On Sun, 17 Feb 2019 at 00:00, Chavdar Ivanov wrote: > > I can confirm that the fix suggested in &

Re: current fails to boot on VirtualBox

Mine is 8.99.34 from 09/02/2019, self build, works just fine. I'll build a new kernel now to compare. On Sat, 16 Feb 2019 at 21:12, Ron Georgia wrote: > > Same here. Fails to boot on both my workstation and laptop, fell back to > 8.99.33 > > On 2/16/19, 3:15 PM, "Arto Huusko" of

<    1   2   3   4   5   6   7   >