Re: Problem running fully virtualized NetBSD under the new XenServer 6.2

[Chavdar Ivanov]

Unfortunately it doesn't fix it - the device is still present in
exactly the same way as before.


Chavdar


On 28 June 2013 14:29, Chavdar Ivanov ci4...@gmail.com wrote:
 No, thanks indeed; I did notice yesterday that there was an update,
 but it never came to me that my problem may be connected to it...

 Chavdar

 On 28 June 2013 12:18, Stephen Borrill net...@precedence.co.uk wrote:
 On Fri, 28 Jun 2013, Chavdar Ivanov wrote:

 Citrix released XenServer 6.2 (now completely free  open source - see
 XenServer.org). I was unable to start any of my NetBSD guests running
 fully virtualized (the PV hosts continue to run fine as before). The
 problem is that the kernel somehow finds one (or in some instances,
 two) non-existent disks:


 Have you put on hotfix 1?

 http://support.citrix.com/article/CTX138186

 --
 Stephen




 --
 



-- 

Re: Various size of (Project) ideas for NetBSD and pkgsrc

[Chavdar Ivanov]

The bit a about Hyper-V- all source is now part of FreeBSD-current tree
following Microsoft policy  changes few weeks ago, together with Citrix and
NetApp. I tested the first alpha a few weeks ago and it seems to be working
very well. The synthetic network adapter performance is the  best I have
tried so far. The SCSI adapter also works,  as well as time sync, shutdown
and heartbeat.

Chavdar
 On 29 Sep 2013 02:09, Ryo ONODERA ryo...@yk.rim.or.jp wrote:

 Hi,

 I have (or have heard) some ideas for NetBSD and pkgsrc.
 Can someone add them to http://wiki.netbsd.org/projects/all-flat/
 with good English and proper classification, if it seems ok?
 I cannot be mentor, because of lack of ability sadly.


 (1) Add UEFI boot support for NetBSD/amd64
 I do not have newer PC, but I have heard newer PC uses UEFI to boot OSes
 instead of BIOS.
 Boot with UEFI should be added to NetBSD/amd64 (I do not know whether UEFI
 is
 available for i386 or not).
 I have seen EFI support option in Oracle VirtualBox.
 No newer PC may not be needed for development.

 (2) Create multiple packages from one pkgsrc package directory
 For example, pkgsrc/fonts/harfbuzz has icu option and theoretically
 non-icu part and icu part can be separate package, but splitting
 only icu part from harfbuzz is difficult in configure/build stage.
 In rpm (Red Hat package manager) case, build once and multiple packages is
 created is realized with custom do-install target.
 build once means reduce of build time.

 (3) Restore MIPS support for NetBSD 6 and current
 Sadly all my MIPS device is not usable with NetBSD 6 and current.
 If NetBSD 7 is released, NetBSD 5 support is dropped, and
 I cannot use supported NetBSD/mips on any MIPS hardware.
 In this case, I have spare NetBSD/cobalt machine (Cobalt raq), and
 I can send it to project worker worldwide.

 (4) Add OSS4 support to NetBSD
 I want to use newer wine (pkgsrc/emulators/wine). But according to
 pkgsrc/doc/TODO, OSS3 support is dropped and I cannot use newer wine
 anymore.
 Adding OSS4 support makes me happy.

 (5) Add XFS support to NetBSD
 I have heard Red Hat Enterprise Linux will use XFS as standard filesystem.
 Accessing Linux's filesystem is useful and important feature.
 At least I am not sticky to BSD licensed version.
 I feel treating like ZFS is good idea.

 (6) Porting Chromium web browser to NetBSD
 I have not tested build of Chromium (open source edition of Google Chrome),
 and I have a few experience about Google Chrome.
 Chromium may be useful web browser for NetBSD.

 (7) Apache OpenOffice for NetBSD
 I have completely no idea about Apache OpenOffice.
 It may be one of the most important application.

 (8) Porting NetBSD to some FPGA CPU board
 OpenCores' OpenRISC 1200, Xilinx's MicloBlaze, Altera NIOS II is
 available for FPGA board.
 At least OpenRISC 1200 and MicroBlaze have Linux support.
 Supporting these architecture is interesting for NetBSD.
 (I have no idea about NetBSD/nios2 status.)

 (9) Add Microsoft's Hyper-V support to NetBSD
 There is two types of Hyper-V, Windows Server 2012's Hyper-V
 and Windows Server 2012R2's Hyper-V.
 I have heard Windows Server 2012's Hyper-V is supported on
 FreeBSD. But I cannot find the code for it.
 Similar to NetBSD/azure?
 http://wiki.netbsd.org/projects/project/netbsd_on_microsoft_azure/

 (10) Porting Broadcom's brcmfmac and brcmsmac WiFi driver to NetBSD
 brcmfmac and brcmsmac are ISC licensed Linux driver for Broadcom's
 WiFi adapter.
 My MacBook Air mid 2012 has brcmfmac or brcmsmac device.
 Supporting the device makes me happy.
 Web page is in 500 - Internal Server Error now sadly.
 http://wireless.kernel.org/en/users/Drivers/brcm80211

 (11) Improve NetBSD/evbearm support
 As you know, NetBSD/evbearm has some problems.
 http://gnats.netbsd.org/48130 , for Kirkwood
 http://gnats.netbsd.org/48193 and http://gnats.netbsd.org/48215 for
 pkg_add

 (14) commit mail of www.pkgsrc.org wiki
 I have heard some difficulties, but I do not know it in detail.

 (15) user-editable wiki site
 If wiki.NetBSD.org is not suitable for this purpose.
 Different URL (even non-NetBSD.org domain name) should be considered.

 (16) Updating compat_linux
 I cannot run firefox's Linux binary with compat_linux.

 (17) DTrace's syscall provider
 I cannot test riz@'s DTrace syscall provider patch.
 But syscall provider support should be added to NetBSD.

 (18) Porting valgrind to NetBSD
 I have heard only old version is available.

 (19) Support some Linux infrastructure that is used by Gnome
 systemd or other mechanism is used by Gnome related software.
 I do not know much about them, but sometimes I encounter systemd or
 similar mechanism are not found error when creating pkgsrc packages.
 I am discouraged with the error.

 (20) Add inotify interface to NetBSD
 Some software that targets Linux use inotify, I have heard
 *BSD has kqueue support and it should be used.
 But implementing Linux compatible inotify with kqueue or similar is useful
 for using 

Re: linux emulation

[Chavdar Ivanov]

Same under -current amd64 from yesterday.

Chavdar


On 18 October 2013 14:57, Patrick Welche pr...@cam.ac.uk wrote:
 I just came across the following on a NetBSD-6.1.2/amd64 with current
 pkgsrc:

 # /emul/linux32/sbin/ldconfig -r /emul/linux32
 # /emul/linux/sbin/ldconfig -r /emul/linux
 [1]   Abort trap (core dumped) /emul/linux/sbin/ldconfig -r /emul/linux

 Not many clues - ends with

   6424   6424 ldconfig CALL  lstat64(0x7f7fe120,0x7f7ff190)
   6424   6424 ldconfig NAMI  /emul/linux/lib64/libnss_nis.so.2
   6424   6424 ldconfig RET   lstat64 0
   6424   6424 ldconfig CALL  open(0x7f7fe120,0,0x1b6)
   6424   6424 ldconfig NAMI  /emul/linux/lib64/libnss_nis.so.2
   6424   6424 ldconfig RET   open 4
   6424   6424 ldconfig CALL  fstat64(4,0x7f7fe030)
   6424   6424 ldconfig RET   fstat64 0
   6424   6424 ldconfig CALL  mmap(0,0xcd78,1,1,4,0)
   6424   6424 ldconfig RET   mmap 140187598270464/0x7f7ff7ff3000
   6424   6424 ldconfig CALL  munmap(0x7f7ff7ff3000,0xcd78)
   6424   6424 ldconfig RET   munmap 0
   6424   6424 ldconfig CALL  close(4)
   6424   6424 ldconfig RET   close 0
   6424   6424 ldconfig CALL  rt_sigprocmask(1,0x7f7fe000,0,8)
   6424   6424 ldconfig RET   rt_sigprocmask 0
   6424   6424 ldconfig CALL  gettid
   6424   6424 ldconfig RET   gettid 6424/0x1918
   6424   6424 ldconfig CALL  tgkill(0x1918,0x1918,6)
   6424   6424 ldconfig RET   tgkill 0
   6424   6424 ldconfig PSIG  SIGABRT SIG_DFL: code=SI_LWP sent by pid=6424, 
 uid=0)
   6424   6424 ldconfig NAMI  ldconfig.core


 ?

 Cheers,

 Patrick



-- 

Re: wpi0: fatal firmware error

[Chavdar Ivanov]

Hi,




On 5 November 2013 22:11, Béla bela.nam@gmail.com wrote:
 Hello fellow NetBSD users,

 I have dabbled with NetBSD in VirtualBox for some time now and today I
 decided to install NetBSD-amd64 version 6.1.2 on my Thinkpad T61 laptop.
 The T61 comes with the Intel(R) PRO/Wireless 3945ABG wireless card - or
 wpi, NetBSD seems to have the appropriate driver for it, and necessary
 firmware is also made available(I used the wpi-firmware2-2.14.4 binary
 package from pkgsrc). But, whenever I bring the interface up(ifconfig
 wpi0 up), I get this error:

 wpi0: fatal firmware error

 I also tried the old firmware wpi-firmware-1.13, with no more success; I
 get the same error.



I used to have a T61p (now, sadly, the NVidia graphics card saw the
best of it). I've never done anything to download firmware to this one
- it just works out of the box (i.e. after clean -current installation
from CD, configuring wpa_supplicant and enabling dhcpcd). The wireless
card in it is identical to yours.  It has been extremely reliable
(well, I've never lost connection to my home router and to some may be
10 others I've connected it). Obviously I haven't tried 6.1.2 (when
that was out, the laptop was already dead).

 Any ideas how to make this wireless card work?
 Does anybody run NetBSD with this wifi card?

 BTW, I have not configured dhcpd/dhclient or wpa_supplicant yet; I see
 no reason to, first I need to get the firmware working.

I've never tried to manually configure the card (or any other
wireless, for that matter). I just configure wpa_supplicant and dhcpcd
(earlier dhclient) and it just works. Although I run -current usually.

Chavdar

-- 

Re: How to boot installed system from a usb disk? (Warning: newbie)

[Chavdar Ivanov]

On 5 November 2013 21:09, Ottavio Caruso
ottavio2006-usenet2...@yahoo.com wrote:
 Hello and first post here.

Hi,


 Coming from the Linux world (Slackware lately) I find the Netbsd
 documentation a bit terse. I have researched this topic on both the
 Netbsd online guide and the install.html file but I couldn't find an
 answer.

 My goal is to install the 64bit port from a usb image onto a local
 partition of my drive (currently Win 7 Home) but I don't want to
 install the bootloader yet. I want to be able to boot from a usb disk
 (either the installation one or a different one). My questions are:

 1) At the stage Installing the boot selector:
 http://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-partitions

 should I select no?

Doesn't really matter - you can always bring back Windows 7 boot
afterwards. But yes, if you want to keep the state of the boot, say
no  here.


 2) If so, how would I then boot the installed system? Should I drop to
 command line prompt and type some commands?

You can boot any partition from Windows 7 boot selector - I've done it
at the time, something along the lines of
http://alien.slackbook.org/blog/adding-linux-to-the-windows7-boot-menu/
should do it (the example is for Linux, of course, but if you install
NetBSD boot block in its partition, not on the MBR, it'l be the same).


 3) How would one normally create a USB boot rescue disk on Netbsd?

NetBSD build.sh script has live-image and install-image targets; I am
not aware of these being regularly published, I have a NetBSD
Xen3_DOMU VM running under XenServer setup to do overnight updates and
builds of the ISOs; on it I occasionally run the live-image and
install-image targets (live-image is also the best if one wants to try
NetBSD on the Raspberry PI). The live-image of course can be used as a
rescue system (frankly speaking, I've never had the need of one so
far).

If tha machine is what you have got at the moment, you could setup a
VirtualBox NetBSD VM under Windows 7 to create the install-image and
live-image targets (it will be slow, but should work).


 4) When I change my mind and install the bootselector on the hard
 drive, how would I make sure it wouldn't overwrite the Windows boot
 sector?

It will never overwrite the partition boot record; it will overwrite
the MBR if you say it so. It is pretty esy to recover that anyway.

My (now dead) ThinkPad T61p used to boot on bare metal simultaneously
(i.e. without disk swapping) Windows 7, Windows 8, Solaris 11 and
NetBSD-current. In this case the main bootloader had to be grub2 from
Solaris11. I first installed Windows 7 on the first hard disk (one can
install second hard disk in a tray replacing the DVD), shrank the
large W7 partition (and was left with two primary partitions already
used). NetBSD had to use another primary partition (it cannot boot
from a logical one, unfortunately). I then created and extended
partition, which I split between the Solaris 11 installation and small
(~15GB) FAT32 partition, used as common store for all the OSes
installed. Solaris 11 can install into and boot from a logical
partition, but using its grub2 setup is necessary (however, the
installation of Solaris 11 recognizes all other partitions and creates
the necessary grub entries). The last bit was to install Windows 8 on
a second disk, which forced its boot setup on top of the Windows 7 BCD
entries, letting me choose between Windows 7 and Windows 8; after that
it was the simple matter of reinstating Solaris 11 Grub2 control over
the MBR to be able to choose between S11, NetBSD or Windows; if I
select the latter, I had one more choice to make from the Windows menu
- 7 or 8.

A bit crazy, but worked well until the machine packed up.


 Many thanks in advance.

 --
 Ottavio

Chavdar

-- 

Re: NetBSD remains stagnant as Charles Hannum said?

[Chavdar Ivanov]

Don't feed the troll.

Chavdar

On 16 January 2014 03:05, Thomas Mueller mueller6...@bellsouth.net wrote:

 NetBSD is Not dead,
   eg NetBSD's urtwn wlan driver was adopted by FreeBSD but Net
   has newer code than Free, last I looked 1 or 2 months back.
   Long may *BSDs ( Linux etc) thrive  co-operate :-)

 Cheers,
 Julian

 Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com

 Good point.  Although NetBSD struggles to be compatible with my hardware, and 
 I wouldn't expect to build a really productive system as I might with FreeBSD 
 or Linux, I see enough changes that I never said NetBSD was stagnant.

 I see possibly useful source code in NetBSD, and OpenBSD too, such as athn(4) 
 and re(4) drivers, with a view to porting to FreeBSD.

 Even though OpenBSD is incompatible with my hardware for lack of GPT and USB 
 3.0 support, I could download the current src tree to compare to FreeBSD and 
 NetBSD, even if I don't have the platform to compile it and don't want to do 
 all the heavy work on USB sticks.

 FreeBSD, OpenBSD and DragonFlyBSD have re(4) driver, but they don't connect 
 with the Ethernet on MSI Z77 MPOWER motherboard, while NetBSD and Linux are 
 successful.

 Tom




-- 

Re: Install i386 or amd64?

[Chavdar Ivanov]

Wrong on account of Windows 8.1 being 64-bit only. You are mistaken with
server 2012 and up, which are only 64-bit.

Otherwise at this time and age I fail to see reason to use the 32-bit
versions on anything modern enough (I only have a couple of old PCs left
over to die in peace which are not 64-bit capable).

Chavdar

Re: netbsd random reboot

[Chavdar Ivanov]

Just FYI, my instance looks like:

➜  ~  uname -a
NetBSD ip-172-31-12-50.eu-west-1.compute.internal 6.1.4 NetBSD 6.1.4
(XEN3_DOMU) amd64
➜  ~  uptime
 2:27PM  up 105 days,  5:32, 7 users, load averages: 0.00, 0.02, 0.00

It is the small (free) one, though.

Chavdar Ivanov

On 9 October 2014 08:31, Manuel Bouyer bou...@antioche.eu.org wrote:
 On Wed, Oct 08, 2014 at 11:30:21AM -0400, el kalin wrote:
 hi all...

 i have a netbsd 6 on ec2 (aws - amazon web services) like:
 NetBSD  6.0 NetBSD 6.0 (XEN3_DOMU) amd64

 I would recommend upgrading to 6.1.5. Lots of fixes have been in since
 6.0, including a few ones that could explain your reboots.

 --
 Manuel Bouyer bou...@antioche.eu.org
  NetBSD: 26 ans d'experience feront toujours la difference
 --



-- 

Re: Installing truble with Netbsd 6.1.5 on Windows8.1 with HyperV

[Chavdar Ivanov]

Old story. Have a look at
https://mail-index.netbsd.org/current-users/2013/04/24/msg022584.html .

Basically you have to disable ACPI and SMP (stop to boot prompt and do
'boot netbsd -12). Nevertheless the emulated Tulip is not that great, and
with SMP not working the options become less and less.

FreeBSD 10.1 has Hyper-V support out of the box; Freebsd 9.3 - after a
minor setup. I guess the issue is not that important for NetBSD
development, porting of the whole FreeBSD suite would not be trivial as far
as I can see it.

I can try -current later.

Chavdar Ivanov

On Wed, 29 Apr 2015 at 14:50 Maurizio Caloro mau...@gmx.ch wrote:

 Hello
 i want to Install NetBsd6.1.5 on Windows 8.1 Hyper-V and i have two
 diffrent problems

 if i Login to session and i write anything:

 sssooo ee nnnttt
 rr liii thhh
 eemplle.



 Also me interface tlp0 dont become any IP

 dmesg ¦ grep tlp
 tlp0 at pci0 dev 19 function 0: DECchip 21240A Ethernet, pass 2.0

 tlp:   flags=8802=Broadcast,Simplex,Multicast mtu 1500
 Address: xx:xx:xx:xx:xx:xx
 Medi:   Ethernet 100BaxeTX
 Status: Active
 lo0:   flags=8049=Broadcast,Running,Multicast mtu 33192
 inet 127.0.0.1

 ACPI are Disabled

Re: Prepping to install

[Chavdar Ivanov]

You can download the USB installer from
ftp://f...@ftp.netbsd.org/pub/NetBSD/images/6.1.5/NetBSD-6.1.5-amd64-install.img.gz
. Uncompress it and dd it onto a USB stick.

I don't quite get your setup; although I have a few systems installed and
booting from RAID1 I tend now to consider the OS an easy bit to recover and
leave the more complex configurations for the data disks. You can get a
shell prompt while doing the installation; various bits and pieces have
been changed through the years as to what is actually available and usable
at this stage - this being one of the reasons I prefer simple setups.

Chavdar Ivanov


On Mon, 11 May 2015 at 23:47 William A. Mahaffey III w...@hiwaay.net wrote:



 Howdy, list :-). A (another ?) noob here. I am preparing to install
 NetBSD 6.1.5 on a new server, AMD C32 based, 4256EE CPU, Supermicro
 H8SCM mbd, 6 X 1 TB 2.5 HDD's, to be partitioned/RAIDed (software).
 Firstly, is this the correct list to post what could be a blizzard of
 noob-ish install questions ? If not, where, please ? Either way, I
 downloaded both of the 6.1.5 boot ISO's. The online docs mention
 installing from a CD or floppy, but no mention of a USB stick network
 install, my preference. Is this in fact feasible ? If so, is it
 documented anywhere ? Does the installer provide for possibly complex
 partitioning during install via shell access or something similar ? For
 reference, I am writing this on a FreeBSD 9.3Rp13 box, setup (last
 summer) similarly to what I want to do w/ this NetBSD server. This box
 has 4 X 1 TB 2.5 HDD's, partitioned into /boot, swap, /, /usr,  /home,
 with /usr  /home RAID0-ed. The installer had a point where you could
 pop into a shell  execute shell commands (or script) to complete the
 partitioning w/o any fat-fingering of delicate, tedious, repetitive
 commands. I am planning on /boot, swap, /, /usr, /var,  /home for the
 server (5 slices per drive, with / RAID1-ed from 2 partitions, /usr
 RAID1-ed from the other 4 of that size, /boot RAID1-ed from 6 slices, 1
 per drive,  /home  /var RAID5-ed from 6 slices, 1 per drive). Thanks
 in advance for any  all input.


 --

 William A. Mahaffey III

   --

 The M1 Garand is without doubt the finest implement of war
  ever devised by man.
 -- Gen. George S. Patton Jr.

Re: USB keyboard recognized during boot menu, not later

[Chavdar Ivanov]

Or get into the BIOS and check if there is an option to disable USB3.

Chavdar

On Thu, 18 Jun 2015 18:54 Christos Zoulas chris...@astron.com wrote:

 In article 20150618171824.GA12756@odin, Mayuresh  mayur...@acm.org
 wrote:
 On Sat, Jun 13, 2015 at 07:01:51AM -0400, Greg Troxel wrote:
  I would try netbsd-7 and if not a current kernel.  It seems that
  something is going wrong in how the kernel deals with the USB chipset,
  and more recent code is more likely to get this right.
 
 With i915drmkms* out of the way, I have current kernel that boots, though
 USB is not working. Tried connecting kbd, mouse, printer etc on all 3
 ports, though it does not generate any event. At boot prompt usb kbd works
 though.
 
 Attaching this to begin with. Please advise if any more inputs will help:
 
 # dmesg | grep -i usb
 vendor 8086 product 0f35 (USB serial bus, xHCI, revision 0x0e) at pci0
 dev 20 function 0 not configured
 vendor 8086 product 0f35 (USB serial bus, xHCI, revision 0x0e) at pci0
 dev 20 function 0 not configured
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0: vendor 8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
 vendor 8086 product 0f35 (USB serial bus, xHCI, revision 0x0e) at pci0
 dev 20 function 0 not configured
 usb0 at ehci0: USB revision 2.0
 uhub0 at usb0: vendor 8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
 
 # uname -a
 NetBSD hp 7.99.18 NetBSD 7.99.18 (GENERIC.201506171920Z) #0: Wed Jun 17
 20:12:20 UTC 2015
 bui...@b45.netbsd.org:
 /home/builds/ab/HEAD/amd64/201506171920Z-obj/home/source/ab/HEAD/src/sys/arch/amd64/compile/GENERIC
 amd64

 Uncomment xhci if you feel adventurous from GENERIC...

 christos

Re: NetBSD Wiki sites not available

[Chavdar Ivanov]

All seem to work fine for me.

Chavdar

On Sun, 13 Dec 2015 at 11:44 Helge Muehlmeier  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> > I get the sites if I set "httpps://" in URL manually. But if I use
> > the links from the NetBSD ports site (click on it) I get a
> > redirection error...
> >
> > I tried this with a Linux and a NetBSD box...
> >
> > Greetings, Helge
> >
> >> What error, exactly?
> >>
> >> Also clear your cache and restart your browser please.
> > I cleared my cache and restarted the browser and still get the
> > error: ... The page isn't redirecting properly
> >
> > Firefox has detected that the server is redirecting the request for
> > this address in a way that will never complete.
> >
> > This problem can sometimes be caused by disabling or refusing to
> > accept cookies. ...
>
> If I use chrome I get the following message:
>
> This webpage has a redirect loop
>
> ERR_TOO_MANY_REDIRECTS
>
> Greetings,
> Helge
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWbVnkAAoJEBgUdGKprwT5Fq4QAMersI7oR3nFCwEMWpnYRW8y
> K5rVVnjtJ+JPx0sLB/q50tQWJS6BCAqYYEsu5yi77Lgtpy+/7GjGTXzFKRIUBLx8
> AhHAW06c+XxO/Ft2vMV6gjrK6mxRo6cLMprkz2dhx5Tu4QNiwtRaHZnSXMV7EAk6
> LlH983yQWRWrp9W470lpiiuzQc22+WP7mh8waCtj8WqNEhFRiowWPFFgqzVSU4OX
> Cx6xXiQxSisTmjVT1Wube6g/JlWE7GvBrJaQaSPxmgVciNGoYq2W+xaWDD+d4qe+
> ERxe5Lfsqk0Uozu+eOhKPxYmUoL1nmbTYYUoy9eTqu2nIYRJwart4MTmODpbjisj
> Kzs0YI67nCIuX+kDdDT0+mbWCL3vAohNDFa1MLzMK04gvN7bp7Hgs+jIRZiap7uA
> LQTkZ25vrp/KrP+kpqWUkc+O4q3sx6nvbV4kRTLmfA1BnNPfuEYoObWsApFXy25h
> l0wY0hV6TXMPx9ITLFbViwpwASeQcfm/RmYd/FPCh/Hz8EwIiyJtxU6WO0Z4iWEq
> LVl+xrP2GNWWpwYdPDKYJUdP+XyQtDQ+LSyLR6r7DXgvWiDb5fIPzWdBOT+uYuwf
> +4zeQE0xqZE2vLJQPQFQsCS7ZnKyUOIhV8Yb3GuMgeMIC0/tIhTVHQp1rnl56ZyL
> vPkhJbx4IeoQhUEXB7nN
> =qLte
> -END PGP SIGNATURE-
>

Re: building current

[Chavdar Ivanov]

I've got the same:


Configuring in ./intl
configure: loading cache ./config.cache
configure: error: `build_alias' has changed since the previous run:
configure:   former value:  `x86_64-unknown-netbsd7.99.26'
configure:   current value: `x86_64-unknown-netbsd7.99'
configure: error: `host_alias' has changed since the previous run:
configure:   former value:  `x86_64-unknown-netbsd7.99.26'
configure:   current value: `x86_64-unknown-netbsd7.99'
configure: error: `LDFLAGS' has changed since the previous run:


I am doing a clean build after a make cleandir now.

Chavdar


On Sun, 7 Feb 2016 at 00:55 Christos Zoulas  wrote:

> In article <191424.309660.1454792527201.javamail.ya...@mail.yahoo.com
> >,
> Darren   wrote:
> >-=-=-=-=-=-
> >
> >I've made many attempts to compile current using
> >https://wiki.netbsd.org/tutorials/how_to_build_netbsd-current/ for
> >reference.
> >I think maybe it's outdated or current has been broken for a week?
>
> What's the error?
>
> christos
>
>

Binary package missing

[Chavdar Ivanov]

Hi,

As it is a transient thing, I was reluctant to file a pr, hope somebody
notices it...

On 7.0.1 (amd64) pkgin refuses to install osabi-NetBSD, as it is for 7.0
apparently. Subsequently all packages depending on it fail to install as
well (i.e. mate).

---
# pkgin install -d osabi-NetBSD-7.0
calculating dependencies... done.

nothing to upgrade.
1 packages to be installed (0B to download, 0B to install):

osabi-NetBSD-7.0

proceed ? [Y/n]
downloading packages...
installing packages...
installing osabi-NetBSD-7.0...
The Operating System version (7.0.1) does not match 7.0
pkg_install warnings: 0, errors: 1
---

One has to go through pkgsrc again, which defeats the purpose...

repositories.conf correctly points to
http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/amd64/7.0.1/All .

Chavdar

Re: Binary package missing

[Chavdar Ivanov]

Yes, of course I know it. It doesn't look good for some casual user wanting
to keep using only binary packages, though. I have a few boxes following
-current - both NetBSD and pkgsrc - and have to reinstall osabi-NetBSD,
then x11links, lsof and a few others with each OS minor version bump. In
fact an attempt to install mate on 7.0.1 renders:


# pkgin install mate
calculating dependencies... done.

nothing to upgrade.
8 packages to be installed (0B to download, 50M to install):

osabi-NetBSD-7.0 libgtop-2.28.4nb9 mate-utils-1.14.0
mate-system-monitor-1.14.0 mate-control-center-1.14.0
mate-applets-1.14.0nb1 marco-1.14.2 mate-1.14.0

proceed ? [Y/n]
downloading packages...
installing packages...
installing osabi-NetBSD-7.0...
The Operating System version (7.0.1) does not match 7.0
installing libgtop-2.28.4nb9...
The Operating System version (7.0.1) does not match 7.0
installing mate-utils-1.14.0...
The Operating System version (7.0.1) does not match 7.0
installing mate-system-monitor-1.14.0...
The Operating System version (7.0.1) does not match 7.0
installing mate-control-center-1.14.0...
The Operating System version (7.0.1) does not match 7.0
installing mate-applets-1.14.0nb1...
The Operating System version (7.0.1) does not match 7.0
installing marco-1.14.2...
The Operating System version (7.0.1) does not match 7.0
installing mate-1.14.0...
The Operating System version (7.0.1) does not match 7.0
pkg_install warnings: 0, errors: 23
pkg_install error log can be found in /var/db/pkgin/pkg_install-err.log
reading local summary...
processing local summary...
no such installed package mate


while some 185 packages - mate's dependencies and constituents - have
already been successfully installed.

Chavdar

On Wed, 17 Aug 2016 at 17:57 Roy Bixler <rcbix...@nyx.net> wrote:

> On Wed, Aug 17, 2016 at 06:40:46AM +, Chavdar Ivanov wrote:
> > installing osabi-NetBSD-7.0...
> > The Operating System version (7.0.1) does not match 7.0
> > pkg_install warnings: 0, errors: 1
> > ---
> >
> > One has to go through pkgsrc again, which defeats the purpose...
>
> I've had problems with that package too and I've gotten used to going
> through pkgsrc to solve it.  If it's any consolation, this takes very
> little time to build (certainly nothing like qt4-libs or firefox!)
> Besides, I think that not every package is available as a binary and
> then it's also necessary to build from source.
>
> --
> Roy Bixler <rcbix...@nyx.net>
> "The fundamental principle of science, the definition almost, is this: the
> sole test of the validity of any idea is experiment."
> -- Richard P. Feynman
>

Re: Packages to NetBSD 7.0.2

[Chavdar Ivanov]

Strange... I thought the problem was because of osabi-7.0 (there is no
osabi-7.0.2), but for me 'pkgin install firefox' worked on the second
attempt. The first invocation installed everything except ffmpeg3 and
firefox itself. The same command second time installed ffmpeg3 and firefox.
The log file does not show any error, they simply haven't been processed.

This is on amd64 as well.

Chavdar


On Mon, 31 Oct 2016 at 07:11 Graham Jenkins  wrote:

> > From: netbsd-users-ow...@netbsd.org  on
> behalf of Manuel Bouyer 
> > Sent: Saturday, 29 October 2016 6:03 AM
>
> >> Hi everyone my question is When will it be available binary packages
> >> for NetBSD 7.0.2?
>
> > so what's missing is only a symlink 7.0.2 -> 7.0
>
> Umm .. pkgin would not update firefox, but would remove it.
> But neither pkgin nor pkg_add will re-install it :(
>
> Graham Jenkins
>

Re: Hypervisor advice

[Chavdar Ivanov]

For what is worth, I have used as part of my old day job VMWare, Hyper-V
and XenServer. I still have a Hyper-V server I occasionally use at home,
with the intention of replacing it with XenServer, under which NetBSD works
very well (not so yet under Hyper-V, in contrast with FreeBSD, which now
under 11.1 supports even Generation II machines, and OpenBSD, which also is
supported as of recently). The only problem is that you really need a
Windows machine for the interface program.

Chavdar Ivanov

On Sat, 29 Jul 2017 at 22:15 Andreas Beck <li...@mode42.net> wrote:

> On Sat, Jul 29, 2017 at 10:50:34AM -0700, Andy Ruhl wrote:
> > I've had a NetBSD/i386 machine that's been running since the late 90s
> > and various hardware iterations. I think it's time to move it to a
> > virtual machine. I need new hardware as well. It has about a 10 year
> > old AMD processor and 1 gig of memory. This is plenty, but the
> > hardware is getting unreliable.
> >
> > I need advice on hypervisors and if it requires certain hardware,
> > hardware advice as well.
> >
> > bhyve appeals to me for obvious reasons but I've never used it. I use
> > KVM and VMWare at work. Also VMWare Fusion on my Mac. Would prefer not
> > to pay too much if I need to pay for something. Never tried Xen but I
> > see posts about it here once in a while.
> >
> > I plan on running other stuff on the hypervisor, probably OpenBSD.
> > Possibly something else as well, maybe a NAS or something.
> >
> > Thoughts?
> >
> > Thanks.
> >
> > Andy
>
> Hi,
> I use FreeBSD 11.1 with "vm" a managment tool for bhyve.
> Im runing from "vm" netbsd and openbsd, successfully.
> Sometimes @reboot the vm's comes not fully up.
> I will try to solve the problem at a later time.
>
> Best Regards,
> Andreas
>

Re: Pulseaudio & browsers - anyone got something ELSE working?

[Chavdar Ivanov]

My firefox-54.0 was build with the default 'oss' option, sound is working
well, I have never noticed any problems. I do have pulseaudio installed as
mplayer dependency, though (mplayer also works fine). I also use vlc (video
works for about a minute, then stops with no dump), xmms (crashes
immediately) and moc (works fine), there are a few other players built
which I haven't bothered to test yet. This all is on amd64 -current,
running on an old Thinkpad t61p. I actually have many more problems with
sound under Linux on the same laptop (I rarely run it these days, after I
managed to get NetBSD run properly on it). I never really had any problems
with sound on this laptop so far.

Chavdar Ivanov

On Sun, 13 Aug 2017 at 23:07 Swift Griggs <swiftgri...@gmail.com> wrote:

>
> So, just a few years ago, we had to have flash (a security nightmare)
> setup and working to do things like play a youtube video. That sucked
> because you never knew when someone was going to bend flash over and 0wn
> your system. My best defense was click-to-play plugins so flash only
> loaded when I needed it. That worked, at least. It didn't play nice with
> the sound device and often wouldn't release it until I closed the browser,
> but it was servicable.
>
> Fast forward a few years when sites started to pull their head out of
> their flash and embrace HTML5 and the in-browser streaming video standards
> that had only been sitting there a decade or so. I'm thinking "YEA!" no
> more flash, right? Plus, Gecko browsers are open source, so they ought to
> embrace more than one sound output meathod, right? ESD, Jack1, Jack2,
> Arts, OSS, Alsa, NAS, etc.. WRONG.
>
> Well, I was half right. Sites like Youtube seem to work in just about all
> our Mozilla-based browsers (Seamonkey, Firefox*). However, there seems to
> be NO CHOICE about what kind of sound device to output to. It's Pulseaudio
> or nothing, I guess. Well, my opinion is that Pulseaudio is a miserable
> failure at everything it does, since that's been my experience. I've got
> three NetBSD systems it fails to work on altogether, or has severe
> drawbacks (like it won't release the sound device - EVER, or it won't work
> unless it's run as root, despite 666 perms on the audio devs). Plus,
> nobody seems to want to *fix* Pulseaudio. Anyone who complains is an
> idiot, according to Pottering or his ilk.
>
> Is there ANY way to get sound via a browser without Pulseaudio ? Today I
> resort to downloading with youtube-dl or something similar and playing the
> resulting file with mplayer because at least that gives me enough
> flexibility to choose my sound output and not break it (which Pulseaudio
> does OFTEN by grabbing the sound device, refusing to release it, and being
> unkillable even with kill -9 - must reboot after that).
>
> Is there any other option besides taking more abuse from Pulseaudio or
> doing the plugin-download-play-from-CLI option ? I'm using amd64 and i386
> ports. Is there a version in the panopoly of firefox versions that has
> anything-other-than-pulseaudio as an option for sound output that can
> still do HTML5 video? Has anyone found a formula that works and doesn't
> ruin the sound device until the end of time just because I played one
> HTML5 video?
>
> -Swift
>
> I'm even using SeamlessRDP to run browsers from Windows boxes. Ugh. Bleh.
> Puh. but at least I know 'rdesktop' will release the sound device!
>

Re: Can I use NetBSD as a desktop system?

[Chavdar Ivanov]

With nouveau(fb)0 the screen becomes black as soon as the kernel message
about nouveaufb0 is dispayed. Earlier (7.99.42) version works fine. On
-current Xorg is starting in the background (one can confirm the process
list after a ssh login), but the screen remains black. I haven't yet come
to see if by any chance the output is directed to the external VGA port. So
far I build a kernel without nouveau(fb), which boots and the console is
usable in text mode or with mlterm-fb, but Xorg does not start (some weird
message about not being able to start with a kernel-bound driver or
similar).

At the same time I have a separate desktop with a NVidia Quadro 600 card
which works just fine, with the level of acceleration nouveau provides.

Go figure...


Chavdar


On Wed, 19 Jul 2017 at 16:24 <co...@sdf.org> wrote:

> On Wed, Jul 19, 2017 at 03:22:51PM +, Chavdar Ivanov wrote:
> > On my T61p even the suspend key works (-current amd64). Now, only if the
> > screen wasn't blank with nouveau...
>
> Black or not backlit?
>

Re: Can I use NetBSD as a desktop system?

[Chavdar Ivanov]

On my T61p even the suspend key works (-current amd64). Now, only if the
screen wasn't blank with nouveau...

Chavdar

On Wed, 19 Jul 2017 at 11:46  wrote:

> On Wed, Jul 19, 2017 at 04:04:02PM +0530, Mayuresh wrote:
> > I have still not got this to work. Can you share your experience or URLs?
>
> sysctl -w hw.acpi.sleep.state=3
>

Re: Can I use NetBSD as a desktop system?

[Chavdar Ivanov]

This is with unmodified GENERIC, so INSECURE should be present - as I said,
the same live USB system works fine with the Quadro 600 card on the
desktop. I know about userconf, but I chose to place several test and spare
kernels in / and modify boot.cfg accordingly.

Chavdar

On Wed, 19 Jul 2017 at 16:40  wrote:

> Are you building without options INSECURE? (config -x)
> You can also add 'userconf disable nouveau*' to boot.cfg to achieve the
> same, without needing a custom kernel.
>

Re: Can I use NetBSD as a desktop system?

[Chavdar Ivanov]

On Wed, 19 Jul 2017 at 18:32 Riccardo Mottola <riccardo.mott...@libero.it>
wrote:

> Hi,
>
> Chavdar Ivanov wrote:
> > On my T61p even the suspend key works (-current amd64). Now, only if
> > the screen wasn't blank with nouveau..
>
> That sounds nice! Does your "moon" light up? :)
>

Yes, it does light up indeed.

There was - at least once, I will have to investigate further - a problem
with the iwn wireless driver after coming from sleep - I got some firmware
error which could not be sorted out by down and up-ing the interface (or
restarting dhcpcd in my case).

Later.

Chavdar


> On my HP I tried to hit the sleep kep (actual function+F5 which has the
> small moon) and the only thing I get is
>
> wskbd_translate: keycode 223 out of range
> wskbd_translate: keycode 223 out of range
>
> (twice as seen)
>
> Riccardo
>
>
>

Re: wpa_supplicant error on mac

[Chavdar Ivanov]

I could add that you could modify the type of the emulated interface in
Virtual Box settings and use the paravirtualized interface virtio, which
will be seen in your NetBSD VM as virtio0. This allegedly should work
faster, although I haven't gone through any benchmarks, but my VMs with
this setup seem to be working fine.

I have only one problem presently with such a setup - when I use a bridged
through wireless interface NetBSD VM and I connect it to a  physical NetBSD
machine attached to the same wireless network, I lose the connectivity
between the NetBSD physical machine and the (Windows 10 in my case) Virtual
Box host. I just have to ssh through another NetBSD machine connected to
the wired interface of the same WiFi spot and from there to the other
NetBSD machine and clear the arp cache.

Chavdar

On Sat, 1 Jul 2017 at 10:17 Robert Elz  wrote:

> Date:Wed, 28 Jun 2017 23:37:54 +0700
> From:Gua Chung Lim 
> Message-ID:  <20170628163753.ga1...@gmail.com>
>
> To expand on what maya@ said earlier...
>
>   | But I can use wm0 pretty fine both IPv4 and IPv6.
>   | I'm curious to know what this error means and how to fix it.
>
> Aside from turning off wpa_supplicant, as in:
>
>   | wpa_supplicant=YES
>
> wpa_supplicant=NO
>
> instead, there is nothing to fix.
>
> VirtualBox doesn't emulate any wireless networks, your NetBSD has no
> wireless interface configured, as maya said, wm0 is a wired interface
> (in this case, an emulated wired interface).
>
> The network map, if you like, is that your netbsd system has a wired
> ethernet connected to your macos host, which is bridging that wired
> network to a wireless network.
>
> You don't have to (in fact, you cannot) on NetBSD configure or control
> in any way, any of the wireless parameters.   That's all done on the
> host (MacOS in your case) where the wireless interface exists.
>
> So there is nothing (real) to fix, nothing to do, it should all just work.
>
> And if for some reason it doesn't, you can always use a virtualbox NAT
> configured network instead (though I have no idea how that would work
> for IPv6.)
>
> kre
>
>

Re: wpa_supplicant error on mac

[Chavdar Ivanov]

vioif0 - by mistake repeated the name in virtualbox form. I haven't had
much problems, except that on occasion the log gets some timeout messages,
but otherwise the connectivity remains OK.

Chavdar

On Sat, 1 Jul 2017 at 13:26 Robert Elz <k...@munnari.oz.au> wrote:

> Date:Sat, 01 Jul 2017 09:43:16 +
> From:    Chavdar Ivanov <ci4...@gmail.com>
> Message-ID:  <
> cag0ouxgvoc5qr9bwfwyemkcrqdq+p8dq_f2vn7dwqfpoate...@mail.gmail.com>
>
>   | I could add that you could modify the type of the emulated interface in
>   | Virtual Box settings and use the paravirtualized interface virtio,
> which
>   | will be seen in your NetBSD VM as virtio0.
>
> vioif0
>
> I left that suggestion out as there have been some occasional problems
> with that driver, and I am not sure if they are all fixed yet (the problems
> occur rarely)But that is what I use too.
>
> kre
>
>

Re: wpa_supplicant error on mac

[Chavdar Ivanov]

You have to select "Advanced" and then "Adapter type" - paravirtualized, if
you want to try vioif0.  [image: VirtualBox_2017-07-01_20-33-55.png]

On Sat, 1 Jul 2017 at 19:10 Gua Chung Lim <ptkris...@gmail.com> wrote:

> Thank you very much for you responding my questions.
>
> * Robert Elz (k...@munnari.oz.au) wrote:
> > To expand on what maya@ said earlier...
> >
> >   | But I can use wm0 pretty fine both IPv4 and IPv6.
> >   | I'm curious to know what this error means and how to fix it.
> >
> > Aside from turning off wpa_supplicant, as in:
> >
> >   | wpa_supplicant=YES
> >
> >   wpa_supplicant=NO
> Yes, I have tried that it has no effects. IPv6 is still OK.
> I even tried correct ssid but invalid psk, there is no effect.
>
> > instead, there is nothing to fix.
> >
> > VirtualBox doesn't emulate any wireless networks, your NetBSD has no
> > wireless interface configured, as maya said, wm0 is a wired interface
> > (in this case, an emulated wired interface).
> Yes it must be emulated bridge from host OS.
> I tried connecting mac host to "IPv4 only network".
> With the same configuration on NetBSD i.e. bridge network and IPv6 enabled.
> NetBSD guest loses IPv6 connection.
> Obviously, the bridge is emulated.
>
> > So there is nothing (real) to fix, nothing to do, it should all just
> work.
> >
> > And if for some reason it doesn't, you can always use a virtualbox NAT
> > configured network instead (though I have no idea how that would work
> > for IPv6.)
> NAT doesn't work, host is on IPv6 but guest did have only IPv4.
>
> > I left that suggestion out as there have been some occasional problems
> > with that driver, and I am not sure if they are all fixed yet (the
> problems
> > occur rarely)But that is what I use too.
> I think, it's not yet fixed.
>
> * Chavdar Ivanov (ci4...@gmail.com) wrote:
> > I could add that you could modify the type of the emulated interface in
> > Virtual Box settings and use the paravirtualized interface virtio, which
> > will be seen in your NetBSD VM as virtio0. This allegedly should work
> > faster, although I haven't gone through any benchmarks, but my VMs with
> > this setup seem to be working fine.
> There is no paravirtualized interface. My VirtualBox only has network
> options
> as listed...
>
> Not attached
> NAT
> NAT Network
> Bridge Adapter
> Internel Network
> Host-only Adapter
> Generic Driver
>
> Note! My VirtualBox is the lastest version, 5.1.22 r115126.
>
> > I have only one problem presently with such a setup - when I use a
> bridged
> > through wireless interface NetBSD VM and I connect it to a  physical
> NetBSD
> > machine attached to the same wireless network, I lose the connectivity
> > between the NetBSD physical machine and the (Windows 10 in my case)
> Virtual
> > Box host. I just have to ssh through another NetBSD machine connected to
> > the wired interface of the same WiFi spot and from there to the other
> > NetBSD machine and clear the arp cache.
> Your host is Windows 10, not Mac. NetBSD probably supports your laptop's
> NIC.
> But on a Macbook, it doesn't support.
>
> Thank you again for spending your valued time to my questions.
>
> --
> Gua Chung Lim
>
> If you desire knowledges, learn one thing everyday.
> If you desire wisdom, leave one thing everyday.
>
> -- Lao Tzu
>

Re: Cannot login via xdm after fresh install

[Chavdar Ivanov]

One small addition to the previous - after taking a checkpoint and shutting
the session manager out - which is just a logout - on the next login I got
xconsole running, but with a login prompt. Had to set 'console' to 'off'
and 'constty' to 'on' in /etc/ttys.

Chavdar

On Sun, 17 Sep 2017 at 22:48 Chavdar Ivanov <ci4...@gmail.com> wrote:

> I have been bitten by this quite a few times before, so I started
> preparing in advance a .xsession file. Looking at this thread, I decided to
> check how things are now with -current and installed a fresh overnight
> build under VirtualBox with full configuration during sysinstall, enabling
> xdm and creating a new user. Everything worked as expected, the three
> default processes were started properly, I could checkpoint a session etc.
> So whatever the reason was with the earlier versions, with 8.99.2 it seems
> just fine.
>
> The only thing which didn't work was first login with the created user -
> it didn't get the password - but I was able to login as root - again with
> xdm - and reset that password, after which the user login also worked as
> expected. That could have been a pebcak, though.
>
> Chavdar
>
>
> On Sun, 17 Sep 2017 at 20:57 Rhialto <rhia...@falu.nl> wrote:
>
>> On Sun 17 Sep 2017 at 22:43:38 +0300, Erkki Ruohtula wrote:
>> > Tried it. It does not help. In any case xsm gets run in
>> > the same enviroment as .xsession would be run, and the latter
>> > has no trouble starting twm and xterm.
>>
>> A pity.
>>
>> > I wonder if everyone using X11 on NetBSD does it by setting
>> > up .xsession before enabling xdm, so the default session
>> > never got tested...
>>
>> That was indeed what I effectively did on my most recent install... just
>> copied over my home directory. I think I did notice the same thing as
>> you did, but I didn't spend any time investigating it.
>>
>> > Erkki
>> -Olaf.
>> --
>> ___ Olaf 'Rhialto' Seibert  -- Wayland: Those who don't understand X
>> \X/ rhialto/at/falu.nl  -- are condemned to reinvent it. Poorly.
>>
>

Re: Cannot login via xdm after fresh install

[Chavdar Ivanov]

I have been bitten by this quite a few times before, so I started preparing
in advance a .xsession file. Looking at this thread, I decided to check how
things are now with -current and installed a fresh overnight build under
VirtualBox with full configuration during sysinstall, enabling xdm and
creating a new user. Everything worked as expected, the three default
processes were started properly, I could checkpoint a session etc. So
whatever the reason was with the earlier versions, with 8.99.2 it seems
just fine.

The only thing which didn't work was first login with the created user - it
didn't get the password - but I was able to login as root - again with xdm
- and reset that password, after which the user login also worked as
expected. That could have been a pebcak, though.

Chavdar


On Sun, 17 Sep 2017 at 20:57 Rhialto  wrote:

> On Sun 17 Sep 2017 at 22:43:38 +0300, Erkki Ruohtula wrote:
> > Tried it. It does not help. In any case xsm gets run in
> > the same enviroment as .xsession would be run, and the latter
> > has no trouble starting twm and xterm.
>
> A pity.
>
> > I wonder if everyone using X11 on NetBSD does it by setting
> > up .xsession before enabling xdm, so the default session
> > never got tested...
>
> That was indeed what I effectively did on my most recent install... just
> copied over my home directory. I think I did notice the same thing as
> you did, but I didn't spend any time investigating it.
>
> > Erkki
> -Olaf.
> --
> ___ Olaf 'Rhialto' Seibert  -- Wayland: Those who don't understand X
> \X/ rhialto/at/falu.nl  -- are condemned to reinvent it. Poorly.
>

*.netbsd.org down ?

[Chavdar Ivanov]

Is this so at the moment? Anyone having the same?

Re: *.netbsd.org down ?

[Chavdar Ivanov]

It was down for me for about 10-15 minutes; I thought that my IP address
might have somehow been blacklisted or something - as at one stage I was
able to access it from one of my laptops running Opera with the built-in
VPN and not from any other means (http or cvs from the other boxes, or even
chrome from the same machine).

Then it came back. Go figure. Some router somewhere might have been
rebooted...

Chavdar Ivanov

On Tue, 22 Aug 2017 at 12:24 Martin Husemann <mar...@duskware.de> wrote:

> On Tue, Aug 22, 2017 at 11:13:11AM +, Chavdar Ivanov wrote:
> > Is this so at the moment? Anyone having the same?
>
> mail.* seems to work ;-)
> www works for me too.
>
> Martin
>

Re: NetBSD-8 and graphics cards

[Chavdar Ivanov]

At this moment the HP Envy is hopeless with -current - I get 'USB device
error, port disabled'  whichever port I use, the live stick is not
recognised and I cannot even take the dmesg.boot. At the same time, on the
same laptop, 7.99.59 works reasonably OK, no USB problems, Xorg starts
using VESA on the Intel card, no dri (glxgears dumps core).

The obvious difference between the two versions are the ACPI messages -
8.99.6 issues many errors here, 7.99.59 complains about unrecognised
devices but carries on.

Not much help, but adds to the picture.

Chavdar Ivanov

On Fri, 10 Nov 2017 at 09:50 Chavdar Ivanov <ci4...@gmail.com> wrote:

> I just tested my Dell T1600 tower with Quadro 600 graphics under both
> 7.99.59 and 8.99.6 (from the 7th of November). Both work fine with dri and
> whatever 3D acceleration nouveau provides (my usual test is glxgears - to
> keep the same fps no matter the size of the window).
>
> I also have similarly working ThinkPad T61p with Quadro 570M, working fine
> as far as the graphics is concerned.
>
> None of these is new enough, though. I am about to test the live system on
> my HP Envy with both Intel HD 530 and GeForce 950M, and I am pretty sure it
> will not work as before. I will confirm later.
>
> Chavdar Ivanov
>
> On Fri, 10 Nov 2017 at 08:10 Sad Clouds <cryintotheblue...@gmail.com>
> wrote:
>
>> Hi, I'm having a lot of issues with getting Xorg running on NetBSD-8. I
>> tried two nvidia cards:
>>
>> Quadro NVS 295 - Xorg says No devices detected
>> Geforce GT 710 - NetBSD fails to boot and stops with kernel panic
>>
>> I've gone back to an old PCI card with ATI Rage 128, but this also
>> doesn't work with Xorg
>>
>> [82.232] (--) Using wscons driver on /dev/ttyE4 in pcvt
>> compatibility mode (version 3.32) [82.232] (--) using VT number 5
>> [82.241] (EE) No devices detected.
>> [82.241] (EE)
>> Fatal server error:
>> [82.241] (EE) no screens found(EE)
>>
>> I normally run Xorg -configure and copy config file
>> to /etc/X11/xorg.conf
>>
>> dmesg with ATI Rage 128:
>>
>> vga0 at pci6 dev 4 function 0: vendor 1002 product 5245 (rev. 0x00)
>> wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
>> wsmux1: connecting to wsdisplay0
>> drm at vga0 not configured
>>
>> Any idea why ATI Rage 128 does not work? I'm sure
>> it used to be supported for years with previous NetBSD versions. Am I
>> doing something wrong or DRM code does not support this card?
>> Is there a way to disable DRM and revert to old behavior?
>>
>> Are there any recent discrete graphics cards that work with NetBSD
>> DRM/KMS and Xorg?
>>
>>

Re: NetBSD-8 and graphics cards

[Chavdar Ivanov]

I just tested my Dell T1600 tower with Quadro 600 graphics under both
7.99.59 and 8.99.6 (from the 7th of November). Both work fine with dri and
whatever 3D acceleration nouveau provides (my usual test is glxgears - to
keep the same fps no matter the size of the window).

I also have similarly working ThinkPad T61p with Quadro 570M, working fine
as far as the graphics is concerned.

None of these is new enough, though. I am about to test the live system on
my HP Envy with both Intel HD 530 and GeForce 950M, and I am pretty sure it
will not work as before. I will confirm later.

Chavdar Ivanov

On Fri, 10 Nov 2017 at 08:10 Sad Clouds <cryintotheblue...@gmail.com> wrote:

> Hi, I'm having a lot of issues with getting Xorg running on NetBSD-8. I
> tried two nvidia cards:
>
> Quadro NVS 295 - Xorg says No devices detected
> Geforce GT 710 - NetBSD fails to boot and stops with kernel panic
>
> I've gone back to an old PCI card with ATI Rage 128, but this also
> doesn't work with Xorg
>
> [82.232] (--) Using wscons driver on /dev/ttyE4 in pcvt
> compatibility mode (version 3.32) [82.232] (--) using VT number 5
> [82.241] (EE) No devices detected.
> [82.241] (EE)
> Fatal server error:
> [82.241] (EE) no screens found(EE)
>
> I normally run Xorg -configure and copy config file
> to /etc/X11/xorg.conf
>
> dmesg with ATI Rage 128:
>
> vga0 at pci6 dev 4 function 0: vendor 1002 product 5245 (rev. 0x00)
> wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
> wsmux1: connecting to wsdisplay0
> drm at vga0 not configured
>
> Any idea why ATI Rage 128 does not work? I'm sure
> it used to be supported for years with previous NetBSD versions. Am I
> doing something wrong or DRM code does not support this card?
> Is there a way to disable DRM and revert to old behavior?
>
> Are there any recent discrete graphics cards that work with NetBSD
> DRM/KMS and Xorg?
>
>

Re: Can I install NetBSD on the same usb installation disk?

[Chavdar Ivanov]

 write it down
Label disk [n]?y
Label written
partition>Q<- get out

~sysbuild/release/images # fsck -fy /dev/rsd0a <- just in case
** /dev/rsd0a
** File system is already clean
** Last Mounted on /mnt/a
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
11270 files, 345422 used, 384553 free (1 frags, 48069 blocks, 0.0%
fragmentation)
~sysbuild/release/images # resize_ffs -y /dev/rsd0a<- really extend 'a'
~sysbuild/release/images # fsck -fy /dev/rsd0a <- that is needed
** /dev/rsd0a
** File system is already clean
** Last Mounted on /mnt/a
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
11270 files, 345422 used, 3523721 free (1 frags, 440465 blocks, 0.0%
fragmentation)
~sysbuild/release/images # mount /dev/sd0a /mnt/a    test the
new partition size
~sysbuild/release/images df -k /mnt/a
Filesystem1K-blocks   Used  Avail %Cap Mounted on
/dev/sd0a   7738286 6908446660528   9% /mnt/a<
looks good

Boot from this stick was also tested OK.

Obviously you can use the same technique to extend your 'a' slice and
extend and|or relocate your 'b'
swap slice on a live stick/disk. Also if you wanted, instead of
increasing the NetBSD primary
partition with fdisk at the beginning, you could create an MS-DOS
partition, format it FAT32 and use
it for other stuff.

This was lifted some times ago from the NetBSD Raspberry PI wiki.

Chavdar Ivanov


On 24 November 2017 at 15:14, Chavdar Ivanov <ci4...@gmail.com> wrote:
> Later, when I get back home.
>
>
> On Fri, 24 Nov 2017 at 15:09, Ottavio Caruso <ottavio2006-de...@yahoo.com>
> wrote:
>>
>>  On Fri 24 Nov 2017 at 07:47:49 -0700, Andy Ruhl wrote:
>> >> This is probably off topic, but I'll try anyway. I want to create a
>> >> USB install "disk", and then use another blank USB disk to install
>> >> onto.
>> >>
>> >> Does this work? I haven't tried yet. This would be nice to test things
>> >> out so I don't disrupt the internal disks.
>>
>> This is what I did when I installed NetBSD back in 2013. I did a fresh
>> installation onto a second usb stick and I tested it for a month or
>> so.
>> Painfully slow! Then I created a second partition on my main hard
>> drive and copied the files onto it.
>>
>> But.. going back to topic:
>>
>> On 24 November 2017 at 12:52, Chavdar Ivanov <ci4...@gmail.com> wrote:
>>
>> >
>> > Boot the stick single user, use fdisk to adjust the first partition to
>> > the
>> > end, use disklabel to extend the label to the en of the disk (A), then
>> > readjust the existing partitions (I move the b-partition to the end,
>> > adjusting a from the almost start to some space before the end for swap,
>> > then after writing the label use 'fsck -fy /dev/rsd0a' or wherever it
>> > is,
>> > then 'resize_ffs -y /dev/rsd0a', then again ; fsck -fy /dev/rsd0a'.
>>
>> Chavdar,
>>
>> if you don't mind, could you give me a breakdown of these commands? I
>> haven't used NetBSD fdisk in a while.
>>
>> --
>> Ottavio Caruso
>
> --
> 



-- 

Re: Can I install NetBSD on the same usb installation disk?

[Chavdar Ivanov]

Of course not.

Boot the stick single user, use fdisk to adjust the first partition to the
end, use disklabel to extend the label to the en of the disk (A), then
readjust the existing partitions (I move the b-partition to the end,
adjusting a from the almost start to some space before the end for swap,
then after writing the label use 'fsck -fy /dev/rsd0a' or wherever it is,
then 'resize_ffs -y /dev/rsd0a', then again ; fsck -fy /dev/rsd0a'.

This is my usual installation method on USB stick - I always build live
images, dump them onto a USB stick, SD card or even SATA disk, then whilst
on the NetBSD host I perform manually the above procedure, even configure
the networking etc.

Chavdar Ivanov

On Fri, 24 Nov 2017 at 08:18 Ottavio Caruso <ottavio2006-de...@yahoo.com>
wrote:

> Hi all,
>
> I have a 16GB usb stick on which I will install the usb installation
> image. This way I would waste 15GB of free space. Can I reclaim the
> free space at all? If so, can I install NetBSD on the free space?
>
> I believe one could partition the drive during instalation but I have
> no clue how.
>
> Any help appreciated.
>
> --
> Ottavio Caruso
>
>

Re: Can I install NetBSD on the same usb installation disk?

[Chavdar Ivanov]

Rereading the question - you can do the same partition expansion if
you are using the installation image, not the live image. If you want
to reuse the remaining space for another reason, then I guess you
could use fdisk to create partitions past the first NetBSD one and
format these, but I've never tried it.

On 24 November 2017 at 12:52, Chavdar Ivanov <ci4...@gmail.com> wrote:
> Of course not.
>
> Boot the stick single user, use fdisk to adjust the first partition to the
> end, use disklabel to extend the label to the en of the disk (A), then
> readjust the existing partitions (I move the b-partition to the end,
> adjusting a from the almost start to some space before the end for swap,
> then after writing the label use 'fsck -fy /dev/rsd0a' or wherever it is,
> then 'resize_ffs -y /dev/rsd0a', then again ; fsck -fy /dev/rsd0a'.
>
> This is my usual installation method on USB stick - I always build live
> images, dump them onto a USB stick, SD card or even SATA disk, then whilst
> on the NetBSD host I perform manually the above procedure, even configure
> the networking etc.
>
> Chavdar Ivanov
>
> On Fri, 24 Nov 2017 at 08:18 Ottavio Caruso <ottavio2006-de...@yahoo.com>
> wrote:
>>
>> Hi all,
>>
>> I have a 16GB usb stick on which I will install the usb installation
>> image. This way I would waste 15GB of free space. Can I reclaim the
>> free space at all? If so, can I install NetBSD on the free space?
>>
>> I believe one could partition the drive during instalation but I have
>> no clue how.
>>
>> Any help appreciated.
>>
>> --
>> Ottavio Caruso
>>
>



-- 

Re: Can I install NetBSD on the same usb installation disk?

[Chavdar Ivanov]

Later, when I get back home.


On Fri, 24 Nov 2017 at 15:09, Ottavio Caruso <ottavio2006-de...@yahoo.com>
wrote:

>  On Fri 24 Nov 2017 at 07:47:49 -0700, Andy Ruhl wrote:
> >> This is probably off topic, but I'll try anyway. I want to create a
> >> USB install "disk", and then use another blank USB disk to install
> >> onto.
> >>
> >> Does this work? I haven't tried yet. This would be nice to test things
> >> out so I don't disrupt the internal disks.
>
> This is what I did when I installed NetBSD back in 2013. I did a fresh
> installation onto a second usb stick and I tested it for a month or
> so.
> Painfully slow! Then I created a second partition on my main hard
> drive and copied the files onto it.
>
> But.. going back to topic:
>
> On 24 November 2017 at 12:52, Chavdar Ivanov <ci4...@gmail.com> wrote:
>
> >
> > Boot the stick single user, use fdisk to adjust the first partition to
> the
> > end, use disklabel to extend the label to the en of the disk (A), then
> > readjust the existing partitions (I move the b-partition to the end,
> > adjusting a from the almost start to some space before the end for swap,
> > then after writing the label use 'fsck -fy /dev/rsd0a' or wherever it is,
> > then 'resize_ffs -y /dev/rsd0a', then again ; fsck -fy /dev/rsd0a'.
>
> Chavdar,
>
> if you don't mind, could you give me a breakdown of these commands? I
> haven't used NetBSD fdisk in a while.
>
> --
> Ottavio Caruso
>
-- 

Re: [pkgsrc] ICU needs configure CFLAGS='-03'

[Chavdar Ivanov]

PKGSRC_USE_SSP=NO in /etc/mk.conf

Chavdar Ivanov

On 14 November 2017 at 14:21,  <tlaro...@polynum.com> wrote:
> On Tue, Nov 14, 2017 at 03:08:29PM +0100, Benny Siegert wrote:
>> Can you post the entire config.log?
>>
>
> Attached.
>
> (Indeed there is the info: libssp not found---what is it?)
>
> Best regards.
>
>> On Tue, Nov 14, 2017 at 3:06 PM,  <tlaro...@polynum.com> wrote:
>> > On Tue, Nov 14, 2017 at 02:04:44PM +0100, Benny Siegert wrote:
>> >> > When configure is run from pkgsrc, it fails.
>> >> >
>> >> > Not knowing the guts of the pkgsrc framework, I'm a bit at a loss to
>> >> > have a clue about what is going wrong...
>> >>
>> >> Please do the following:
>> >>
>> >> 1. Run "make configure", watch it fail.
>> >> 2. Look in work/icu-*/config.log for the failing compiler invocation.
>> >> Post the relevant bit.
>> >
>> > The only info in config.log is:
>> >
>> > configure: exit 77
>> >
>> > The relevant bit failing is the invocation of the compiler to find the
>> > extension (suffix) of the executable, that is (extract from configure):
>> >
>> > 8<---
>> > cat confdefs.h - <<_ACEOF >conftest.$ac_ext
>> > /* end confdefs.h.  */
>> >
>> > int
>> > main ()
>> > {
>> >
>> >   ;
>> >   return 0;
>> > }
>> > _ACEOF
>> > ac_clean_files_save=$ac_clean_files
>> > ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out"
>> > # Try to create an executable without -o first, disregard a.out.
>> > # It will help us diagnose broken compilers, and finding out an intuition
>> > # of exeext.
>> > { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler 
>> > works" >&5
>> > $as_echo_n "checking whether the C compiler works... " >&6; }
>> > ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
>> >
>> > # The possible output files:
>> > ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*"
>> >
>> > ac_rmfiles=
>> > for ac_file in $ac_files
>> > do
>> >   case $ac_file in
>> > *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | 
>> > *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
>> > * ) ac_rmfiles="$ac_rmfiles $ac_file";;
>> >   esac
>> > done
>> > rm -f $ac_rmfiles
>> >
>> > if { { ac_try="$ac_link_default"
>> > case "(($ac_try" in
>> >   *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
>> >   *) ac_try_echo=$ac_try;;
>> > esac
>> > eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
>> > $as_echo "$ac_try_echo"; } >&5
>> >   (eval "$ac_link_default") 2>&5
>> >   ac_status=$?
>> >   $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
>> >   test $ac_status = 0; }; then :
>> >   # Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
>> > # So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
>> > # in a Makefile.  We should not override ac_cv_exeext if it was cached,
>> > # so that the user can short-circuit this test for compilers unknown to
>> > # Autoconf.
>> > for ac_file in $ac_files ''
>> > do
>> >   test -f "$ac_file" || continue
>> >   case $ac_file in
>> > *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | 
>> > *.map | *.inf | *.dSYM | *.o | *.obj )
>> > ;;
>> > [ab].out )
>> > # We found the default executable, but exeext='' is most
>> > # certainly right.
>> > break;;
>> > *.* )
>> > if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no;
>> > then :; else
>> >ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
>> > fi
>> > # We set ac_cv_exeext here because the later test for it is not
>> > # safe: cross compilers may not add the suffix if given an `-o'
>> > # argument, so we may need to know it at that point already.
>> > # Even if this section looks crufty: it has the advantage of
>>

Re: NetBSD on Amazon EC2

[Chavdar Ivanov]

Please check the following thread:

http://mail-index.netbsd.org/port-xen/2017/10/23/msg009097.html

Chavdar Ivanov

On Sat, 4 Nov 2017 at 13:03 r0ller <r0l...@freemail.hu> wrote:

> Hi All,
>
> Mine doesn't work either and rebooting it again does not help:(
>
> Best regards,
> r0ller
>
>  Eredeti levél 
> Feladó: Abhinav Upadhyay < er.abhinav.upadh...@gmail.com (Link -> mailto:
> er.abhinav.upadh...@gmail.com) >
> Dátum: 2017 november 4 08:05:07
> Tárgy: Re: NetBSD on Amazon EC2
> Címzett: Eric Haszlakiewicz < haw...@gmail.com (Link -> mailto:
> haw...@gmail.com) >
>
> On Sat, Nov 4, 2017 at 2:49 AM, Eric Haszlakiewicz <haw...@gmail.com>
> wrote:
> > Up until today I was running a NetBSD server on Amazon's EC2 service,
> > but then I restarted it because Amazon told me they'd be forcing a
> > restart soon anyway, to "deploy important updates".
> > Of course, when I tried to start it back up, it failed. Trying to
> > start a brand new instance using the available NetBSD AMIs
> > (NetBSD-i386-7.0-201511211930Z-20151121-1234 (ami-9f8090fe)) also
> > fails in a similar way, specifically with errors like:
> >
> > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-barrier.
> > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-flush-cache.
> > and
> > xc_dom_probe_bzimage_kernel: kernel is not a bzImage
> >
> > Do these errors ring a bell with anyone?
> > Does anyone have a working AMI that I can use?
> Yes, my instance also was rebooted last night (automatically by AWS
> for maintenance) and now unreachable. No idea how to get it back.
> (Didn't try creating new instance)
> -
> Abhinav

Re: Installing NetBSD (8.0_BETA) on GPT disk and EFI

[Chavdar Ivanov]

s:/etc/fdisk:/etc/fstab:   # ;^]

On Sun, 3 Dec 2017 at 09:31 Petar Bogdanovic  wrote:

> On Sun, Dec 03, 2017 at 02:21:31AM +0200, Iliyan Stoyanov wrote:
> >
> > I decided to abandon the use of the installer and just drop to a shell
> and
> > proceed by hand. I use gpt to create a 512MB efi partition, and then
> proceed to
> > create a swap one, and 3 more FFS partitions. When I try to use those in
> the
> > installer, I always reach some errors and can not move forward with the
> > installation of the sets. If I try to use the partitioning tool from the
> menu I
> > always end up loosing the EFI partition, which I wan't there, no matter
> if I'm
> > gonna use it or not. After creating the partitions in the console, dkctl
> shows
> > the wedges properly, I create FS on them with newfs, but in the end,
> even if I
> > chose to use current partition table, the installer doesn't like it and
> I can't
> > install NetBSD successfully.
>
> If you already did all the partitioning manually, you could also just
> `tar xpzf' the sets and adjust /etc/rc.conf & /etc/fdisk.
>
> Last two steps would then be `installboot' and `gpt biosboot'.
>
> I was migrating the rootfs of a netbsd-6 box yesterday; here are the
> gpt, dkctl, newfs, installboot steps I did:
>
>   $ sudo gpt show wd0
>   start   size  index  contents
>   0  976773168
>
>   $ sudo gpt create wd0
>
>   $ sudo gpt show wd0
>   start   size  index  contents
>   0  1 PMBR
>   1  1 Pri GPT header
>   2 32 Pri GPT table
>  34  976773101
>   976773135 32 Sec GPT table
>   976773167  1 Sec GPT header
>
>   $ sudo gpt add -b 2048 -t ffs wd0
> Partition added, use:
> dkctl wd0 addwedge  2048 976771087 
> to create a wedge for it
>
>   $ sudo gpt label -i 1 -l netbsd-root wd0
> partition 1 on rwd0d labeled netbsd-root
>
>   $ sudo gpt show wd0
>   start   size  index  contents
>   0  1 PMBR
>   1  1 Pri GPT header
>   2 32 Pri GPT table
>  34   2014
>2048  976771087  1  GPT part - NetBSD FFSv1/FFSv2
>   976773135 32 Sec GPT table
>   976773167  1 Sec GPT header
>
>   $ sudo dkctl wd0 addwedge netbsd-root 2048 976771087 ffs
> dk4 created successfully.
>
>   $ sudo newfs -O2 /dev/rdk4
> /dev/rdk4: 476939.0MB (976771080 sectors) block size 32768, fragment
> size 4096
> using 643 cylinder groups of 741.75MB, 23736 blks, 46848
> inodes.
> super-block backups (for fsck_ffs -b #) at:
> 192, 1519296, 3038400, 4557504, 6076608, 7595712, 9114816, 10633920,
> (...)
>
> .(...)
>
>   $ sudo installboot -v -o console=com0,speed=115200,timeout=5 /dev/dk4
> /usr/mdec/bootxx_ffsv2
> File system: /dev/dk4
> Primary bootstrap:   /usr/mdec/bootxx_ffsv2
> Ignoring PBR with invalid magic in sector 0 of `/dev/dk4'
> Boot options:timeout 5, flags 0, speed 115200, ioaddr 0,
> console com0
>
>   $ sudo gpt biosboot -c /usr/mdec/gptmbr.bin -i 1 wd0
>
>
> /etc/fdisk would then contain something like:
>
> NAME=netbsd-root / ffs rw 0 1
>
>
> Hope that helps,
> Petar
>

Re: DHCP client: dhclient vs dhcpcd ?

[Chavdar Ivanov]

On Wed, 31 Jan 2018 at 12:57, KIRIHARA Masaharu 
wrote:

>
> Hello,
>
> NetBSD has two DHCP clients; dhclient(8) and dhcpcd(8).
> What's the difference?
> Which is better to use?
>
> In https://www.netbsd.org/docs/network/dhcp.html ,
> dhclient is appeared.
>
> In https://www.netbsd.org/docs/guide/en/chap-net-practice.html ,
> dhcpcd is appeared.
>
> I'm confused...
>
>
> Thanks,
>
> ---
> KIRIHARA,

Dhcpcd has been the preferred client for some time; I recall discussions
about retiring dhclient.

> Masaharu
>
> --

Re: 7_STABLE build fails

[Chavdar Ivanov]

I have been using sysutils/sysbuild and sysupdate for quite some time. One
spends a few minutes setting up, then the procedure is consistent. I used
to build everything overnight, sysupdate in the morning.

Chavdar

On Sat, 3 Feb 2018, 19:14 Gua Chung Lim,  wrote:

> * Gua Chung Lim (gua.chung...@gmail.com) wrote:
> > * Fekete Zoltn (fekete.zol...@minux.hu) wrote:
> > > Appending -u after -U does solve the problem?
> > I fixed it. I simply do ./build.sh kernel=GENERIC, without any options.
> >
> > lim@netbsd:~% uname -a
> > NetBSD netbsd.localdomain 7.1_STABLE NetBSD 7.1_STABLE (GENERIC) #0: Sat
> Feb  3 21:55:51 +07 2018  
> root@netbsd.localdomain:/usr/obj/sys/arch/amd64/compile/GENERIC
> amd64
> >
> > I'm now building distribution.
> > To see if it gets compiled.
> build distribution completed. :-)
>
> But I still doubt some questions.
> Normally I cvs source tree once a month. And I do this procedure in order.
> ref:
> http://www.netbsd.org/docs/guide/en/chap-updating.html#updating-procedure
>
> # cd /usr/src
> # cvs update -Pd (I always adhere with _STABLE.)
> # ./build.sh -r -O ../obj -T ../tools -U distribution
> # ./build.sh -O ../obj -T ../tools -U kernel=GENERIC
> # mv /netbsd /netbsd.old
> # mv /usr/obj/sys/arch/amd64/compile/GENERIC/netbsd /
> # shutdown -r now
> Distribution was compiled and kernel was compiled and installed. Then
> reboot.
> # cd /usr/src
> # ./build.sh -O ../obj -T ../tools -U install=/
> # /usr/sbin/etcupdate [-s /usr/src]
> # shutdown -r now
> The procedure above works most of the times, except this time.
>
> This time my first build distribution failed (I didn't log).
> I did googling, someone said "kernel should be built prior to
> distribution".
> But ONLY build kernel WITHOUT any options i.e. ./build.sh kernel=GENERIC
> works.
> And I change some order i.e. build and install kernel before build
> distribution.
> And install distribution after reboot. This procudure works for this time.
>
> My questions are...
> 1. In correct order, which one to build first between kernel and
> distribution?
> 2. When to build distribution? I was told, sometimes build distribution is
> not required.
> 3. When to use options -O ../obj -T ../obj? As sometimes without options
> it compiles.
> 4. On fresh installed system from iso, is ./build.sh tools always required?
>
> build.sh is only a script, ./build.sh -help is not much detailed as man
> pages.
>
> Thank you,
>
> --
> Gua Chung Lim
>
> To live is to love.
>

Re: booting from gpt/raid?

[Chavdar Ivanov]

My HP Envy laptop boots netbsd in both efi and bios modes, from internal
sata disk and external usb one. Both modes are enabled simultaneously. My
default efi boot is rEFInd, works fine for me. I installed NetBSD-current
on some free space at the end of a gpt disk which already contained a
couple of Linux distributions and some Windows data, following the outline
described above. rEFInd also automatically recognises other systems on
external disks and can boot them (usually; in some cases this didn't work,
e.g. with a Fedora on some external mbr disk, in which case I had to get in
front of rEFInd with F9 and choose the disk directly).

So obviously it depends on the bios/efi capabilities.


On Wed, 4 Jul 2018 at 08:51, Thomas Mueller  wrote:

> from MLH:
>
> > Well, not so great. Once the bios detects an EFI boot drive on the
> > system, it attempts to load that, regardless of any other non-EFI
> > boot drive you specify. So to boot from the temp non-EFI boot drive,
> > the EFI drives have to be disconnected until the NetBSD boot loader
> > has started and then I apply power to the EFI drives to bring them
> > up and then boot NetBSD.
>
> > Somewhere in that scenario, to boot from the non-EFI drive, NetBSD
> > started requiring to run /var/run/lvm and it wouldn't run.  The
> > only way I could boot from that drive was to 'update' the os from
> > cd again, so something apparently got hosed. No idea what.
>
> > Needless to say, the EFI drives didn't boot. Not sure why yet.
> > "Booting Operating System" showed then the cursor moved down,
> > possibly attempting to display something, then kept cycling back
> > and from bwtween those two.
>
> My systems have UEFI, but I can boot USB sticks in non-EFI mode.
>
> I can boot the System Rescue CD either way (UEFI or non-UEFI), written to
> USB stick.
>
> Maybe it depends on the motherboard?
>
> Tom
>

Re: NetBSD disk performance on VirtualBox

[Chavdar Ivanov]

I ran my tests with our dd and also with /usr/pkg/gnu/bin/dd, supposedly
the same or similar enough to the one in Centos; there was no significant
difference between the two. The fastest figure came on the system disk when
it was attached to an IDE controller with ICH6 chipset. about 180MB/sec.
All other combinations return between 110 and 160 MB/sec. Tried
with/without host os cache, also there is a setting that the disk is solid
state. No apparent difference.

My host system is build 17120, so that may explain something. Not the
difference in figures though, comparing to Centos.

Chavdar

On Mon, 19 Mar 2018 at 23:06  wrote:

> On Mon, Mar 19, 2018 at 02:58:06PM +0100, Fekete Zolt?n wrote:
> > Any setting which influence the test and I didn't apply?
>
> yes, need to figure out what to make GNU dd behave the same.
> It has different defaults.
>

Re: NetBSD disk performance on VirtualBox

[Chavdar Ivanov]

I managed to get mine to about 180MB/sec, host i/o cache didn't make much
difference, but I switched to ICH9 chipset and ICH6 SATA controller... Hold
on, I just realised my root device is on an IDE controller, not SATA, which
must have been the default setting for NetBSD in VirtualBox. I'll check
using SATA.

My Centos VM returns some 600MB/sec.

Chavdar


On Mon, 19 Mar 2018 at 22:39 Sad Clouds  wrote:

> On Mon, 19 Mar 2018 16:17:33 +0100
> Martin Husemann  wrote:
>
> > On Mon, Mar 19, 2018 at 12:06:44PM +, Sad Clouds wrote:
> > > Hello, which virtual controller do you use in VirtualBox and do you
> > > have "Use Host I/O Cache" selected on that controller? If yes, then
> > > you need to disable it before running I/O tests, otherwise it
> > > caches loads of data in RAM instead of sending it to disk.
> >
> > I am not sure it makes sense to benchmark the host IO performance in
> > this context ;-)
> >
> > However: I have the default settings, PIIX4. This is netbsd-8 GENERIC,
> > as of a few days ago.
> >
> > Turning off the host IO cache makes no measurable difference for me.
> >
> > Martin
>
> Hmm... something strange is going on here, I can't get anywhere close
> to the throughput that you're getting on a NetBSD-8 VM, and I use
> similar settings. I'm running VirtualBox 5.2.8 and changing "Use Host
> I/O Cache" made no difference for me, max throughput is always around 50
> MBytes/sec.
>

Re: NetBSD disk performance on VirtualBox

[Chavdar Ivanov]

Well, testing with a file of zeroes is not a very good benchmark - see the
result for OmniOS/CE below:

➜  xci dd if=/dev/zero of=out bs=100 count=1000
1000+0 records in
1000+0 records out
10 bytes transferred in 0.685792 secs (1458168149 bytes/sec)


So I decided to switch to previously created random contents and move it
with dd between two different disks. Here is what I get:
---
Centos 7.4  XFS
➜  xci dd if=/dev/urandom of=rand.out bs=100 count=1000
1000+0 records in
1000+0 records out
10 bytes (1.0 GB) copied, 9.6948 s, 103 MB/s
➜  xci dd if=rand.out of=/data/rand.out bs=100
1000+0 records in
1000+0 records out
10 bytes (1.0 GB) copied, 2.49195 s, 401 MB/s
OmniOS CE - ZFS
➜  xci dd if=/dev/urandom of=rand.out bs=100 count=1000
1000+0 records in
1000+0 records out
10 bytes transferred in 16.982885 secs (58882812 bytes/sec)
➜  xci dd if=/dev/urandom if=rand.out of=/data/testme/rand.out  bs=100
1000+0 records in
1000+0 records out
10 bytes transferred in 21.341659 secs (46856713 bytes/sec)
NetBSD-current amd64 8.99.12 --- FFS
➜  sysbuild   dd if=/dev/urandom of=rand.out bs=100 count=1000
1000+0 records in
1000+0 records out
10 bytes transferred in 32.992 secs (30310378 bytes/sec)
➜  sysbuild dd if=rand.out of=/usr/pkgsrc/rand.out bs=100
1000+0 records in
1000+0 records out
10 bytes transferred in 23.535 secs (42489908 bytes/sec)


OmniOS/ZFS and NetBSD/FFS results are comparable, the Centos/XFS one is a
bit hard to explain.

This is on the same Windows 10 host as before.

Chavdar

On Mon, 19 Mar 2018 at 23:16 Chavdar Ivanov <ci4...@gmail.com> wrote:

> I ran my tests with our dd and also with /usr/pkg/gnu/bin/dd, supposedly
> the same or similar enough to the one in Centos; there was no significant
> difference between the two. The fastest figure came on the system disk when
> it was attached to an IDE controller with ICH6 chipset. about 180MB/sec.
> All other combinations return between 110 and 160 MB/sec. Tried
> with/without host os cache, also there is a setting that the disk is solid
> state. No apparent difference.
>
> My host system is build 17120, so that may explain something. Not the
> difference in figures though, comparing to Centos.
>
> Chavdar
>
> On Mon, 19 Mar 2018 at 23:06 <m...@netbsd.org> wrote:
>
>> On Mon, Mar 19, 2018 at 02:58:06PM +0100, Fekete Zolt?n wrote:
>> > Any setting which influence the test and I didn't apply?
>>
>> yes, need to figure out what to make GNU dd behave the same.
>> It has different defaults.
>>
>

Re: NetBSD disk performance on VirtualBox

[Chavdar Ivanov]

On Tue, 20 Mar 2018, 12:30 Sad Clouds, <cryintotheblue...@gmail.com> wrote:

> Hello, a few comments on your tests:
>
> - Reading from /dev/urandom could be a bottleneck, depending on how that
> random data is generated. Best to avoid this, if you need random data, try
> to use a bench tool that can quickly generate dynamic random data.
>

Obviously. I pre-created the file and measured the transfer between two
filesystems on different disks.

>
> - Writing to ZFS can give all sorts of results, i.e. it may be doing
> compression, encryption, deduplication., etc. You'd need to disable all
> those features in order to have comparable results to NetBSD local file
> system.
>

Ditto. Included for comparison only - e.g. see the figure when reading
/dev/zero - it is almost instantaneous.

Subsequently I did some FreeBSD tests as well, those were in line with
NetBSD.

Anyway, nothing so far explains Martin's results being just a tad below
those of Linux and everyone else getting speeds 5-6 times slower.

>
> - I think by default, dd does not call fsync() when it closes its output
> file, with GNU dd you need to use conv=fsync argument, otherwise you could
> be benchmarking writing data to OS page cache, instead of virtual disk.
>

Right.

>
>
>
>
> On Tue, Mar 20, 2018 at 9:20 AM, Chavdar Ivanov <ci4...@gmail.com> wrote:
>
>> Well, testing with a file of zeroes is not a very good benchmark - see
>> the result for OmniOS/CE below:
>> 
>> ➜  xci dd if=/dev/zero of=out bs=100 count=1000
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes transferred in 0.685792 secs (1458168149 bytes/sec)
>> 
>>
>> So I decided to switch to previously created random contents and move it
>> with dd between two different disks. Here is what I get:
>> ---
>> Centos 7.4  XFS
>> ➜  xci dd if=/dev/urandom of=rand.out bs=100 count=1000
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes (1.0 GB) copied, 9.6948 s, 103 MB/s
>> ➜  xci dd if=rand.out of=/data/rand.out bs=100
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes (1.0 GB) copied, 2.49195 s, 401 MB/s
>> OmniOS CE - ZFS
>> ➜  xci dd if=/dev/urandom of=rand.out bs=100 count=1000
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes transferred in 16.982885 secs (58882812 bytes/sec)
>> ➜  xci dd if=/dev/urandom if=rand.out of=/data/testme/rand.out  bs=100
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes transferred in 21.341659 secs (46856713 bytes/sec)
>> NetBSD-current amd64 8.99.12 --- FFS
>> ➜  sysbuild   dd if=/dev/urandom of=rand.out bs=100 count=1000
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes transferred in 32.992 secs (30310378 bytes/sec)
>> ➜  sysbuild dd if=rand.out of=/usr/pkgsrc/rand.out bs=100
>> 1000+0 records in
>> 1000+0 records out
>> 10 bytes transferred in 23.535 secs (42489908 bytes/sec)
>> 
>>
>> OmniOS/ZFS and NetBSD/FFS results are comparable, the Centos/XFS one is a
>> bit hard to explain.
>>
>> This is on the same Windows 10 host as before.
>>
>> Chavdar
>>
>> On Mon, 19 Mar 2018 at 23:16 Chavdar Ivanov <ci4...@gmail.com> wrote:
>>
>>> I ran my tests with our dd and also with /usr/pkg/gnu/bin/dd, supposedly
>>> the same or similar enough to the one in Centos; there was no significant
>>> difference between the two. The fastest figure came on the system disk when
>>> it was attached to an IDE controller with ICH6 chipset. about 180MB/sec

Re: NetBSD disk performance on VirtualBox

[Chavdar Ivanov]

I'd be also interested in your setup - on a W10 hosted VBox (latest) on a
fast M.2 disk I get approximately 5 times slower values, on -current amd64,
having disks attached to SATA, SAS and NVMe controllers (almost the same,
the SAS one is a little slower than the rest, but nowhere near your
figures. :

➜  xci df -k
Filesystem1K-blocks   Used  Avail %Cap Mounted on
/dev/wd0a  1118162294947681127774  89% /  < SATA
kernfs1  1  0 100% /kern
ptyfs 1  1  0 100% /dev/pts
procfs4  4  0 100% /proc
tmpfs786316  0 786316   0% /var/shm
/dev/sd0e  16515150   103666325322762  66% /usr/pkgsrc
/dev/ld0a  16515182   117123583977066  74% /usr/pkg
/dev/sd1a  33030380   294898041889058  93% /home/sysbuild
➜  xci dd if=/dev/zero of=out bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 11.497 secs (91204314 bytes/sec)
➜  xci cd /usr/pkg
➜  pkg dd if=/dev/zero of=out bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 11.303 secs (92769707 bytes/sec)
➜  pkg cd /usr/pkgsrc
➜  pkgsrc dd if=/dev/zero of=out bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 11.854 secs (88457567 bytes/sec)
➜  pkgsrc cd /home/sysbuild
➜  sysbuild dd if=/dev/zero of=out bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 11.776 secs (89043478 bytes/sec)
---

Chavdar Ivanov

On Mon, 19 Mar 2018 at 08:33 Martin Husemann <mar...@duskware.de> wrote:

> On Sun, Mar 18, 2018 at 03:45:48PM +, Sad Clouds wrote:
> > Hello, using 'log' or both 'async, log' does not improve things much,
> > i.e. it's around 30-50 MBytes/sec:
> >
> > localhost# mount | grep wd0a
> > /dev/wd0a on / type ffs (asynchronous, log, local)
> >
> > localhost# dd if=/dev/zero of=out bs=1m count=1000
> > 1000+0 records in
> > 1000+0 records out
> > 1048576000 bytes transferred in 21.330 secs (49159681 bytes/sec)
>
> I get:
>
> amd64-test# mount
> /dev/wd0a on / type ffs (local)
> kernfs on /kern type kernfs (local)
> ptyfs on /dev/pts type ptyfs (local)
> procfs on /proc type procfs (local)
> tmpfs on /var/shm type tmpfs (local)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 2.634 secs (398092634 bytes/sec)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 2.634 secs (398092634 bytes/sec)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 2.691 secs (389660349 bytes/sec)
> amd64-test# mount -u -o async /
> amd64-test# mount
> /dev/wd0a on / type ffs (asynchronous, local)
> kernfs on /kern type kernfs (local)
> ptyfs on /dev/pts type ptyfs (local)
> procfs on /proc type procfs (local)
> tmpfs on /var/shm type tmpfs (local)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 0.755 secs (1388842384 bytes/sec)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 0.765 secs (1370687581 bytes/sec)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 0.756 secs (1387005291 bytes/sec)
> amd64-test# mount -u -o noasync /
> amd64-test# mount -u -o log /
> amd64-test# mount
> /dev/wd0a on / type ffs (log, local)
> kernfs on /kern type kernfs (local)
> ptyfs on /dev/pts type ptyfs (local)
> procfs on /proc type procfs (local)
> tmpfs on /var/shm type tmpfs (local)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 2.787 secs (376238249 bytes/sec)
> amd64-test# dd if=/dev/zero of=out bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred in 2.714 secs (386358142 bytes/sec)
>
>
> .. and this is close to what I expected (in relative timings).
>
> Martin
>

Re: Tip regarding nvidia optimus (dual graphics nvidia/intel) and efiboot

[Chavdar Ivanov]

That's what I was doing since the last drmkms updates on my HP Envy
with Intel 530 and NVidia Geforce GT 950M - I have 'disable genfb;
disable nouveau; disable nouveaufb' in my boot.cfg; the other way
doesn't work, the 950M is not recognized yet.

I've got some weird problems though - I can't use gdm or xdm. The
former does not receive the keyboard focus at all, so one cannot input
username / password, the latter lets me start typing a username, but
then it starts and endless repeat of one of the characters from the
name; in both cases I have to press the power button to start shutdown
(switching to alternative console doesn't work at this moment for some
reason). xfce4 works ery well for me, when started with 'startxfce4',
which obviously starts the X server, but if I logout and find myself
in the console, the keyboard is in some weird state whereby each press
generates two characters - as if using UTF terminal emulator.
On Sun, 7 Oct 2018 at 20:57,  wrote:
>
> (thanks ryoon for a hint)
>
> To boot it with graphical acceleration on uefiboot, I need to disable
> genfb specifically.
> That is, drop to boot prompt, type
> > userconf disable genfb
> > boot
>
> you can add this to /boot.cfg too.
>
> Otherwise it tries genfb for the nvidia card, and i915 for intel, which
> doesn't work well because they are physically dependent cards, and I get
> a blank screen after mode switch.
>
> Another option is to disable i915drmkms, then I am left with the nvidia
> genfb.



-- 

Re: Unbound chroot via rc difficulties getting started

[Chavdar Ivanov]

I have one RPI model B, running 8.99.2, which has been running my home
DNS server since, well, 8.99.2 (it had some 10 months uptime until the
fuse tripped for some reason)...  I don't remember doing anything
special to make is start chrooted (there was already
"unbound_chrootdir=/var/chroot/unbound" in /etc/defaults/rc.conf),
except creating the link "cd /etc; ln -s
/var/chroot/unbound/etc/unbound unbound" after the unbound_migrate was
ran.
On Mon, 24 Sep 2018 at 08:00, qab smith  wrote:
>
> Unbound initially was not able to start for me in chroot using rc scripts. 
> After reading the manuals, my interpretation was to set an unbound_chrootdir 
> in the rc.conf, which I guess is read as part of the precmd, and maybe an 
> unbound_chrootdir flag is needed to specify the absolute path to the conf in 
> chroot (as well as the chrootdir parameter in the unbound.conf).
>
> # rc.conf snippet
> unbound=YES
> unbound_chrootdir="/var/chroot/unbound"
> unbound_flags="-c /var/chroot/unbound/etc/unbound/unbound.conf"
>
> # ls -la /var/chroot/unbound/etc/unbound/
> total 48
> drwxr-xr-x  2 _unbound  _unbound512 Sep 22 21:33 .
> drwxr-xr-x  3 _unbound  _unbound512 Jul 17 22:07 ..
> -rw-r--r--  1 _unbound  _unbound280 Sep 22 23:07 unbound.conf
>
> I could get unbound to start in chroot if I just launched unbound from the 
> command line, but using the rc start command gave me this error:
>
> # /etc/rc.d/unbound start
> /etc/rc.d/unbound: WARNING: /etc/unbound/unbound.conf is not readable.
>
> I later made some progress when I copied the unbound.conf outside the chroot 
> into /etc/unbound, and then used rc start to run it normally. (I was 
> compromising until I could figure out the chroot.) The rc script has a 
> migration function the copied the /etc files again to the chroot dir and now 
> unbound with chroot works now with rc!  But I thought I already had the files 
> in the right place to begin with.  :^/
>
> # /etc/rc.d/unbound start
> Migrating /etc/unbound to /var/chroot/unbound/etc/unbound
> Starting unbound.
>
> I don’t understand why it would not work with the chroot paths already there, 
> until I simply copied the conf file to the non-chroot etc.  I’m a little new 
> and feel like I may be misunderstanding how the man pages and example conf is 
> describing how this should works, so I would appreciate any guidance.
>
> Thanks in advance!



-- 

Re: ZFS development questions

[Chavdar Ivanov]

On Tue, 15 Jan 2019 at 13:16, Gua Chung Lim  wrote:
>
> * n...@n0.is (n...@n0.is) wrote:
> > Hi,
> >
> > since FreeBSD recently announced to move to using ZFSonLinux as their 
> > upstream source
> > for ZFS 
> > (https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072422.html),
> > what has been the development of ZFS in NetBSD so far? Did you use the same 
> > sources?
> > Regardless of the answer, is using ZFSoLinux a consideration for future 
> > development?
> ZFS is not BSD.
> It is CDDL. see 
> https://en.wikipedia.org/wiki/Common_Development_and_Distribution_License
> FreeBSD doesn't care much about the license.
> But we do, I think.
>

Nothing to do with the licence. ZFS is CDDL under every system. NetBSD
already has ZFS. I've used it in the past with mixed success; it used
to fail for me under higher load, the last few tries were OK, though.

The thread is about switching to ZoL as upstream, as opposed to
Illumos - mainly due to the apparently heavy process there - I'd guess
inherited, at least partially, from Sun, as well as the statement that
a great deal of ZFS innovation now comes from ZoL, perhaps because it
has the widest commercial support base. The discussion is if this move
might bring unwanted linuxisms to FreeBSD by the back door - the
proposed solution being splitting ZFS code in MI/MD parts. We'll see.

> --
> Gua Chung Lim
>
> "UNIX is basically a simple operating system,
> but you have to be a genius to understand the simplicity."
> -- Dennis M. Ritchie
>


-- 

Re: libstdc++.so.7 is missing

[Chavdar Ivanov]

Good luck building midori from source. I have tried at least three
times on recent -current with current and updated pkgsrc with no luck
whatsoever. The latest is this afternoon - webkit-gtk does not build:

[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/__/__/DerivedSources/WebKit/unified-sources/UnifiedSource61.cpp.o
[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/__/__/DerivedSources/WebKit/unified-sources/UnifiedSource62.cpp.o
[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/WebProcess/WebPage/gtk/AcceleratedSurfaceX11.cpp.o
[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/__/__/DerivedSources/WebKit/unified-sources/UnifiedSource63.cpp.o
[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/__/__/DerivedSources/WebKit/unified-sources/UnifiedSource64.cpp.o
[ 92%] Building CXX object
Source/WebKit/CMakeFiles/WebKit.dir/__/__/DerivedSources/WebKit/unified-sources/UnifiedSource65.cpp.o
[ 92%] Linking CXX shared library ../../lib/libwebkit2gtk-4.0.so
[ 92%] Built target WebKit
Scanning dependencies of target WebKit2-4-gir
gmake[2]: *** No rule to make target 'JavaScriptCore-4.0.gir', needed
by 'WebKit2-4.0.gir'.  Stop.
gmake[1]: *** [CMakeFiles/Makefile2:1318:
Source/WebKit/CMakeFiles/WebKit2-4-gir.dir/all] Error 2
gmake: *** [Makefile:152: all] Error 2
*** Error code 2
.

Last time I was able to build it, perhaps six months ago, it just
crashed, so I left it for later. Then again, I run -current, doing
updates usually twice a week, also following -current pkgsrc, doing
usually monthly pkg_rolling-replace, so problems are to be expected.

However, while earlier versions of firefox used to be, shall I say,
flaky, and crash in random places, the last 2-3 updates have been very
stable for me, right now on 64.0.2. Rust takes a long to build, for
sure, and is updated way too often, but at the end firefox seems fine.

On Sun, 20 Jan 2019 at 19:00, Pedro Pinho  wrote:
>
> Just found another missing package from 2018Q4, gimp is not available as a
> binary package.
>
> Den sön 20 jan. 2019 kl 17:34 skrev Pedro Pinho :
>
> > The symlink was just a test, I've removed it as I got another missing
> > library.
> >
> > Here's the output of ldd /usr/pkg/bin/midori https://pastebin.com/h6wbXvBu
> > and the output of ldd /usr/pkg/lib/lib*.so https://pastebin.com/UPT68xaw
> > the last one, i.e. ldd /usr/pkg/bin gives just read error: Operation not
> > supported by device
> >
> > I see if I get the time to compile midori from pkgsrc later today.
> >
> > Den sön 20 jan. 2019 kl 14:58 skrev Greg Troxel :
> >
> >> Pedro Pinho  writes:
> >>
> >> > Back at home!
> >> > I've just erased my disk using gpsrted-live usb and made a fresh install
> >> > from the image here,
> >> >
> >> http://ftp.fr.netbsd.org/pub/NetBSD-daily/netbsd-8/201901151910Z/images/
> >> >
> >> > NetBSD 8.0 STABLE arch amd64
> >> >
> >> > Pointed pkgin to
> >> > http://ftp.fr.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/8.0/All/
> >> >
> >> > and pulled my binary packages. Launching midori from xterm outputs
> >> > libstdc++.so.7 is missing. Tried symlinking libsrdc++.so.8 to
> >> > libstdc++.so.7 to no avail. Can't launch midori.
> >>
> >> Don't add symlinks like that.  It's just going to make a mess.
> >>
> >> Somebody -- perhaps it will be you -- has to understand what is going on



--

Re: Dell R7425 with AMD Ryzen dmesg

[Chavdar Ivanov]

That's one tasty morsel, curious to time build.sh -m 128 on a memory disk...

On Tue, 25 Dec 2018 at 07:55, Manuel Bouyer  wrote:
>
> Hello,
> for fun, attached is the dmesg of NetBSD-current on a Dell R7425 with
> 2 AMD Ryzen 16-core/32 threads CPUs.
>
> Everything seems to be supported (the disk and network controllers are
> for sure). Sensors reports only 8 CPU temps (maybe that's the number of dies),
> but reported values looks right:
>Current  CritMax  WarnMax  WarnMin  CritMin  Unit
> [amdzentemp0]
>cpu0 temperature:36.000  degC
> [amdzentemp1]
>cpu1 temperature:35.750  degC
> [amdzentemp2]
>cpu2 temperature:35.250  degC
> [amdzentemp3]
>cpu3 temperature:36.000  degC
> [amdzentemp4]
>cpu4 temperature:39.000  degC
> [amdzentemp5]
>cpu5 temperature:35.750  degC
> [amdzentemp6]
>cpu6 temperature:37.000  degC
> [amdzentemp7]
>cpu7 temperature:39.000  degC
> [ipmi0]
>Exhaust Temp:31.133   80.342   75.3218.0343.013  degC
>   GPU8 Temp:   N/A
>   GPU7 Temp:   N/A
>   GPU6 Temp:   N/A
>   GPU5 Temp:   N/A
>   GPU4 Temp:   N/A
>   GPU3 Temp:   N/A
>   GPU2 Temp:   N/A
>   GPU1 Temp:   N/A
> Status1: FALSE
>  Status: FALSE
>   Intrusion:  TRUE
>   Voltage 2:   228.976 V
>   Voltage 1:   N/A
>Fan6:  4680840  480   RPM
>Fan5:  4800840  480   RPM
>Fan4:  4680840  480   RPM
>Fan3:  4800840  480   RPM
>Fan2:  4800840  480   RPM
>Fan1:  4800840  480   RPM
>  Inlet Temp:19.081   47.201   43.1843.013   -7.030  degC
>   Temp1:39.167   95.407  3.013  degC
>Temp:36.154   95.407  3.013  degC
> [mfii0]
> mfii0 BBU state:  TRUE
>   mfii0 BBU voltage: 3.975 V
>   mfii0 BBU current: 0.000 A
>   mfii0 BBU temperature:30.000  degC
> mfii0:0:online
>
> Tip: if you want to use serial console on this machine, with the physical
> serial connector on the rear, you have to set it up as com2 in BIOS (com1 in
> NetBSD), and hardwire the console to 0x2f8 in the NetBSD's boot loader.
> Every other configuration I tried (especially trying to get the physical
> serial connector routed to com1/0x3f8) failed.
>
> --
> Manuel Bouyer 
>  NetBSD: 26 ans d'experience feront toujours la difference
> --



-- 

Running NetBSD as VirtualBox VM using GPT slices

[Chavdar Ivanov]

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
boot it only from time to time to build -current for various architectures
plus for pkgsrc upgrades - I haven't been able to get Xorg work in any way
on this machine (Intel 530 + NVidia GeForce 950M; FreeBSD 12 works fine, I
can provide info and testing in case someone has time to add support for
this more than two years old laptop). I run several NetBSD VMs under
VirtualBox Windows setup and it came to my mind that I should be able to
run my bare-metal system under VirtualBox. This turned out to be trivial,
as follows:
- Find out the physical disk in use - #1 here
C:\temp> wmic diskdrive list brief
CaptionDeviceIDModel
Partitions  Size
SDXC Card  \\.\PHYSICALDRIVE2  SDXC Card
1   62536803840
WDC WD7500BPKX-00HPJT0 \\.\PHYSICALDRIVE1  WDC WD7500BPKX-00HPJT0
 11  750153761280
SanDisk SD7SN6S-512G-1006  \\.\PHYSICALDRIVE0  SanDisk SD7SN6S-512G-1006
4   512105932800
"
# Check the partitions - 9,10 and 11 are those used by NetBSD, 9 being the
EFI partition
C:\temp> vboxmanage internalcommands listpartitions -rawdisk
\\.\PhysicalDrive1
Number  Type   StartCHS   EndCHS  Size (MiB)  Start (Sect)
1   0x00  0   /0  /0   0   /0  /0  61440 2048
2   0x00  0   /0  /0   0   /0  /0   8192125831168
3   0x00  0   /0  /0   0   /0  /0 102400142608384
4   0x00  0   /0  /0   0   /0  /0512352323584
5   0x00  0   /0  /0   0   /0  /0 30353372160
6   0x00  0   /0  /0   0   /0  /0200967772160
7   0x00  0   /0  /0   0   /0  /0   1024968181760
8   0x00  0   /0  /0   0   /0  /0 130887970278912
9   0x00  0   /0  /0   0   /0  /0128   1238335488
10  0x00  0   /0  /0   0   /0  /0 102400   1238597632
11  0x00  0   /0  /0   0   /0  /0   8220   1448312832
# Create a vmdk containing only the three interesting for us partitions
C:\temp> VBoxManage internalcommands createrawvmdk -filename
 c:\temp\a.vmdk -rawdisk \\.\PhysicalDrive1 -partitions 9,10,11

The last command will create a.vmdk and a-pt.vmdk. After that one creates a
usual NetBSD-amd64 VM with the VirtuaBox interface, using the new vmdk as
the system disk (a.vmdk, not a-pt.vmdk). Of course, as the system is EFI,
ine will have to enable the EFI boot for the VM.

One only has to reconfigure the networking after reboot. I'll try to figure
out how to use different network configurations depending on whether the
boot is physical or virtual.

And I can run Xorg when I boot the VM, which might be useful for some
pkgsrc development...

(I've stolen the method from
https://stackoverflow.com/questions/34371180/virtualbox-fail-to-bootup-guest-from-gpt-physical-partition#
and
applied it to NetBSD in EFI mode, no need to install any boot loaders).

Chavdar

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

[Chavdar Ivanov]

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
nouveau, the geforce 950m apparently is still unsupported and I get 'no
console device'. I haven't been able to get X running on this laptop, but
the rest seems fine.

Chavdar

On Tue, 29 May 2018, 09:34 Martin Husemann,  wrote:

> On Tue, May 29, 2018 at 08:15:43AM +, Thomas Mueller wrote:
> > Where do I find documentation on how to boot NetBSD amd64 or possibly
> i386 in UEFI mode?
>
> I'm working on a wiki page (and will change the NetBSD 8.0 install docs
> to point to that).
>
> I can't answer how to boot into alternative operating systems (haven't
> tried
> that yet). But the basic installation goes like this:
>
>  - You want to boot from the uefi usb install image. This requires "secure
>boot" to be disabled. Some firmwares require you to set a firmware
>password before allowing to disable that
>
> Assuming you have a scratch disk (called wd0) you want to fully use for
> NetBSD you
> do something like:
>
>  gpt destroy wd0
>  gpt create wd0
>  gpt add -a 2m -l "EFI system" -t efi -s 128m wd0
>  gpt add -a 2m -l NetBSD -t ffs -s 118g wd0 # replace 118g as
> needed
>  gpt add -a 2m -l swap -t swap wd0  # this will use all remaining space
>  dkctl wd0 listwedges
>
> Now note which dk* is the EFI one and newfs it (also note the ffs one
> for later, see below):
>
>  newfs_msdos /dev/rdk3  # replace dk3 with proper device
>
> Then make it bootable:
>
>  mount -t msdos /dev/dk3 /mnt
>  mkdir -p /mnt/EFI/boot
>  cp /usr/mdec/*.efi /mnt/EFI/boot
>  umount /mnt
>
> I have sysinst changes that will allow the remaining part to be handled
> by sysinst in NetBSD 8.0 (hope to finsih that soon).
>
> But for now you will have to install manually. Check the dkctl output
> for which dk* is the ffs one and newfs/mount it:
>
>  newfs -O 2 dk4 # replace dk4 by approrpiate device, see above
>  mount -o async /dev/dk4 /mnt
>  cd /mnt
>
> Now extract (with tar xpzf) all sets you want, including the appropriate
> kernel. Also:
>
>  cp /usr/mdec/boot .# copy secondary bootloader (XXX is this needed
> for uefi)?
>  cd dev
>  sh MAKEDEV all
>  vi /etc/fstab
>
> A fstab could look like:
>
> NAME=NetBSD /   ffs rw  1 1
> NAME=swap   noneswapsw,dp   0 0
> kernfs  /kern   kernfs  rw
> ptyfs   /dev/pts ptyfs  rw
> procfs  /proc   procfs  rw
> tmpfs /var/shmtmpfs   rw,-m1777,-sram%25
>
> Finally set rc_configured=YES in /mnt/etc/rc.conf, plus add hostname=
> and whatever settings you need.
>
> Now reboot, remove install usb medium, and watch NetBSD boot from uefi.
>
> Martin
>

Re: rmt(8)

[Chavdar Ivanov]

Historically the remote tape path:

% grep '/etc/rmt' /usr/src/sbin/dump/pathnames.h
#define   _PATH_RMT   "/etc/rmt"

On Thu, 10 Jan 2019 at 03:22,  wrote:
>
> Hello list,
>
> I'm just curious why there is a link to /usr/sbin/rmt in /etc?
>
> deathstar$ ls -l /etc | grep rmt
> lrwxr-xr-x   1 root  wheel  13 Jul 17 09:59 rmt -> /usr/sbin/rmt
>
> edgar



-- 

Re: Booting NetBSD 8 install image on PC Engines apu2d4 via serial console goes blank

[Chavdar Ivanov]

If I were you, I woiuld have tried the live image with dhcpcd enabled
(+ sshd etc. ), you should be able to get your IP address from the
dhcp server. Just in case, I'd gone with -current as well.

On Sun, 30 Dec 2018 at 15:59, J. Lewis Muir  wrote:
>
> I'm trying to install NetBSD 8 on a PC Engines apu2d4
>
>   https://www.pcengines.ch/apu2d4.htm
>
> via a USB thumb drive with a NetBSD 8 install image
>
>   
> https://cdn.netbsd.org/pub/NetBSD/NetBSD-8.0/images/NetBSD-8.0-amd64-install.img.gz
>
> via a serial console where I can get to the welcome screen of the
> installer image
>
>   Welcome to the NetBSD/amd64 8.0 installation image
>   
> ===
>
>   ACPI (Advanced Configuration and Power Interface) should work on all modern
>   and legacy hardware.  However if you do encounter a problem while booting,
>   try disabling it and report a bug at http://www.NetBSD.org/.
>
>1. Install NetBSD
>2. Install NetBSD (no ACPI)
>3. Install NetBSD (no ACPI, no SMP)
>4. Drop to boot prompt
>
>   Choose an option; RETURN for default; SPACE to stop countdown.
>   Option 1 will be chosen in 0 seconds.
>
>   Option: [1]:
>
> and I press Space and then Enter to start the install, and it shows
> some numbers with a spinner and then shows
>
>   18010904+813996+1283156 [1191264+821120+12847-
>
>  but then the screen goes blank.
>
> Does anyone know what I can try to get this to work?
>
> I tried the "no ACPI" and "no ACPI, no SMP" install choices, but that
> didn't help.
>
> The apu2d4 says the serial port baud rate is 115200 which is what I
> successfully used to communicate with the apu2d4.  Will the boot image
> kernel work with this baud rate?  If not, is there a way to change it
> by dropping to the boot prompt?  Or do I need to build a custom kernel
> with the baud rate set to 115200?
>
> Thank you!
>
> Lewis



-- 

Re: Links crashed when open a https site?

[Chavdar Ivanov]

To avoid the message about the invalid certificate, install
‘security/mozilla-certificates’.

On Mon, 14 Jan 2019 at 11:20, Csányi Pál  wrote:

> Martin Husemann  ezt írta (időpont: 2019. jan.
> 14., H, 11:00):
> >
> > On Mon, Jan 14, 2019 at 10:53:59AM +0100, Csányi Pál wrote:
> > > Although, he stopped at this point: https://imgur.com/a/QDcvqVS
> > >
> > > What can I do to proceed?
> >
> > There are no postinstall issues that failed (or is that cut off the
> image)?
> > Looks like everything is fine and you can just hit enter to continue.
>
> I proceed, and do a reboot.
> I can boot with the upgraded NetBSD system.
>
> Now I tried the following with links:
> links https://duckduckgo.com
> Links says:
> Invalid certificate etc. etc.
> After I hit Yes I can browse this https site of DucjDuckGo.
>
> Problem SOLVED. Thanks!!
>
> Best, Pal
>
-- 

Package binaries for NetBSD 7.2

[Chavdar Ivanov]

Hi,

NetBSD 7.2 was released a few weeks ago. Are there any plans to bulk
build pkgsrc for this version? I tried to use
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/7.1_2018Q2/All/ ,
this generally works, but there are a number of newer shared libraries
in 7.2 which block the installation of many packages, e.g.:


n72# pkgin install -f curl
calculating dependencies...done.
/usr/lib/libwind.so.0, needed by curl-7.61.1 is not present in this system.
/usr/lib/libroken.so.19, needed by curl-7.61.1 is not present in this system.
/usr/lib/libkrb5.so.26, needed by curl-7.61.1 is not present in this system.
/usr/lib/libhx509.so.5, needed by curl-7.61.1 is not present in this system.
/usr/lib/libheimntlm.so.4, needed by curl-7.61.1 is not present in this system.
/usr/lib/libheimbase.so.1, needed by curl-7.61.1 is not present in this system.
/usr/lib/libgssapi.so.10, needed by curl-7.61.1 is not present in this system.
/usr/lib/libcom_err.so.7, needed by curl-7.61.1 is not present in this system.
/usr/lib/libasn1.so.9, needed by curl-7.61.1 is not present in this system.


Chavdar

(I normally use only -current and obviously build my own packages, but
wanted to have a few virtual machines with the current released
versions for reference).

-- 

Re: Package binaries for NetBSD 7.2

[Chavdar Ivanov]

Well, I am aware of all these options to solve the immediate problem,
should I need it; I did it to find out how it would have panned out
for someone perhaps coming from a different background and wanting to
try the release. For insance, one gets the option to add binary
packages installation during normal sysinst, which obviously doesn't
work for 7.2 as of now. My point was that it would be desireable to
make some sort of coordination between operating system announces and
the corresponding pkg bulk builds. I realise this is not as easy as it
sounds, counting the number of supported architectures and platforms,
but perhaps something could be done for the major ones. Again, I
understand it is a matter of available resources and priorities and
also that the average NetBSD user is generally able to sort out
problems like this by himself, so it is not that big of a deal.
On Mon, 17 Sep 2018 at 20:34, Benny Siegert  wrote:
>
> On Mon, Sep 17, 2018 at 7:37 PM Greg Troxel  wrote:
>
> > > I can't answer to any specific plans on this front...  It's
> > > conceivable that the bulk builds will switch to 7.2 at some
> > > point.
> >
> > It's unfortunate that this happened; generally the plan for release
> > branches is not to have ABI changes.  But sometimes that's really
> > difficult to avoid depending on how upstream packages behave.  One
> > netbsd-7 system i have has newer libraries from about May, and I didn't
> > notice this issue.
>
> How about switching the -7 builders to 7.2 after 2018Q3 comes out?
>
> --
> Benny



-- 

Re: modular-xorg...my latest

[Chavdar Ivanov]

Try https://wiki.netbsd.org/pkgsrc/x11/ .

On Sat, 16 Mar 2019 at 19:45, Bob Bernstein  wrote:
>
> Included is my latest 'make' in modular-xorg. All feedback,
> encouragement, excoriation and/or condemnation will be carefully
> reviewed! 
>
> --snip--
> Script started on Sat Mar 16 15:16:25 2019
> ===> Skipping vulnerability checks.
> WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
> WARNING: To fix run: `/usr/pkg/sbin/pkg_admin -K /usr/pkg/pkgdb 
> fetch-pkg-vulnerabilities'.
> ===> Installing dependencies for modular-xorg-1.12.4nb1
> => Build dependency cwrappers>=20150314: found cwrappers-20180325
> => Full dependency modular-xorg-server>=1.12.4: NOT found
> => Verifying reinstall for ../../x11/modular-xorg-server
> => Bootstrap dependency digest>=20010302: found digest-20190127
> ===> Skipping vulnerability checks.
> WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
> WARNING: To fix run: `/usr/pkg/sbin/pkg_admin -K /usr/pkg/pkgdb 
> fetch-pkg-vulnerabilities'.
> => Checksum SHA1 OK for xorg-server-1.20.4.tar.bz2
> => Checksum RMD160 OK for xorg-server-1.20.4.tar.bz2
> => Checksum SHA512 OK for xorg-server-1.20.4.tar.bz2
> ===> Installing dependencies for modular-xorg-server-1.20.4
> ==
> The supported build options for modular-xorg-server are:
>
> debug dtrace inet6
>
> The currently selected options are:
>
> inet6
>
> You can select which build options to use by setting PKG_DEFAULT_OPTIONS
> or the following variable.  Its current value is shown:
>
> PKG_OPTIONS.modular-xorg-server (not defined)
>
> ==
> ==
> The following variables will affect the build process of this package,
> modular-xorg-server-1.20.4.  Their current value is shown below:
>
> * VARBASE = /var
>
> Based on these variables, the following variables have been set:
>
> * XKB_OUTPUT_DIR = /var/db/xkb
>
> You may want to abort the process now with CTRL-C and change their value
> before continuing.  Be sure to run `/usr/pkg/bin/bmake clean' after
> the changes.
> ==
> => Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.6nb2
> => Tool dependency gmake>=3.81: found gmake-4.2.1nb1
> => Tool dependency pkgconf-[0-9]*: found pkgconf-1.4.1nb1
> => Build dependency tradcpp-[0-9]*: found tradcpp-0.5.3
> => Build dependency x11-links>=1.13: found x11-links-1.15
> => Build dependency cwrappers>=20150314: found cwrappers-20180325
> => Full dependency xkbcomp-[0-9]*: found xkbcomp-1.4.2
> => Full dependency xkeyboard-config-[0-9]*: found xkeyboard-config-2.26
> => Full dependency xcb-util-keysyms>=0.3.9: found xcb-util-keysyms-0.4.0
> ===> Overriding tools for modular-xorg-server-1.20.4
> ===> Extracting for modular-xorg-server-1.20.4
> ===> Patching for modular-xorg-server-1.20.4
> => Applying pkgsrc patches for modular-xorg-server-1.20.4
> ===> Creating toolchain wrappers for modular-xorg-server-1.20.4
> ===> Configuring for modular-xorg-server-1.20.4
> => Modifying GNU configure scripts to avoid --recheck
> => Replacing config-guess with pkgsrc versions
> => Replacing config-sub with pkgsrc versions
> => Replacing install-sh with pkgsrc version
> => Adding run-time search paths to pkg-config files.
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... /usr/bin/awk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether make supports the include directive... yes (GNU style)
> checking for x86_64--netbsd-gcc... cc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether cc accepts -g... yes
> checking for cc option to accept ISO C89... none needed
> checking whether cc understands -c and -o together... yes
> checking dependency style of cc... gcc3
> checking how to run the C preprocessor... cc -E
> checking for grep that handles long lines and -e... (cached) /usr/bin/grep
> checking for egrep... (cached) /usr/bin/egrep
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h 

Re: My packages are SO hosed.

[Chavdar Ivanov]

I pointed out the old link to the wiki to underline you need X11_TYPE
type be modular in order to actually build modular_xorg, otherwise you
get all these errors about missing packages - which are actually
present, but in the built-in Xorg, which defies the purpose in the
first place. I also mentioned earler about pkgtools/osabi (this has
been discussed earlier, seems to be too finegrained for use with
-current, but can be disregarded), in a sence that I always manually
rebuild osabi for the tiny version of -current prenestly in use,
together with all those depending on it (always x11-links, net-snmp,
lsof in my case), then do anything with pkg_rolling-replace or a long
build like this one.

I am also building modular Xorg on a clean pkgsrc -current box, having
some problems from time to time (e.g. cmake refused to build and had
to edit its configuration files to complete it), but there is no more
problem with the missing .pc files. My initial plan after I finish the
build is to install a new -current instance under VirtualBox, but
without the X sets, then pkgin the newly built modular Xorg  (it has
vboxvideo driver). After that I might try it with a new USB setup on
real hardware.

On Sun, 17 Mar 2019 at 08:48, Sad Clouds  wrote:
>
> On Sun, 17 Mar 2019 00:46:55 -0400
> Bob Bernstein  wrote:
>
> > My spidey-sense is warning me that my pkg collection is seriously
> > corrupt, and that I ought to give equally serious consideration to
> > beginning over again, with a fresh install of -current.
> >
> > Buy, sell, or hold?
> >
> > Thank you,
>
> What exactly are you attempting to do? If you want to get pkgsrc going
> but you have some corruption issues??, just remove manually all your
> existing packages, i.e.
>
> rm -rf /usr/pkg
> rm -rf /var/db/pkg
>
> and start from scratch. It's as simple as that. But then I don't know
> how and where you install your packages. If you build them yourself
> from source, then you should know exactly where they are located. If
> you install binary packages from NetBSD public locations, then all
> packages and database live in the well known locations.
>
> >From your previous email, it seems you're building from source, but I
> can't tell if only one package install gives you errors, or if this
> happens for other packages as well. Have you tried running "pkg_info
> -a"? and looking for the package name? If you're not building and
> installing packages in a chroot, then you will be overwriting
> previously installed packages and possibly causing conflicts. Is this
> what may be happening here?
>


-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

BTW I finally finished a full modular-xorg build. Starting some tests now.
..
pkpkg_info modular-xorg-1.12.4nb1
Information for modular-xorg-1.12.4nb1:

Comment:
Modular Xorg meta-package

Requires:
modular-xorg-server>=1.12.4
modular-xorg-drivers>=1.12
modular-xorg-libs>=1.0
modular-xorg-apps>=1.5
modular-xorg-fonts>=1.1
modular-xorg-utils>=1.0
xorg-docs-[0-9]*

Description:
This is the modular Xorg meta-package for installing the various
libs, drivers, fonts, and apps from the modular Xorg project.

Homepage:
http://xorg.freedesktop.org/
...

On Fri, 15 Mar 2019 at 19:51, Bob Bernstein  wrote:
>
> On Fri, 15 Mar 2019, Chavdar Ivanov wrote:
>
> > BTW what is the NVidia hardware on this machine?
>
> From Windows while it was still running on the box:
>
> nVidia:
> GeForce 6150SE nForce 430
>
> Thanks for giving modular-xorg a build try. I look forward to
> your results.
>
> --
> Bob Bernstein



-- 

Re: Userconf & DRM driver (Was Re: Panic: no console device)

[Chavdar Ivanov]

Try 'disable nouveau'. In the past I also had to 'disable genfb' on my
Intel/NVidia Optimus laptop. Now it works - with intel drm, still
without 3D accelleration - without disabling anything.

I have another laptop with only radeonfb, a FireGL mobile card, which
otherwise should have worked, but any attempt to use it hard-restes
the laptop, so I have
'userconf=disable radeon*' in /boot.cfg .

On Thu, 7 Mar 2019 at 19:54, Bob Bernstein  wrote:
>
> Hi Michael. I have taken the liberty of ressurecting this post in
> order to get a tad more help with its suggestion. I hope I haven't
> violated any list etiquette in the process.
>
> On Mon, Feb 25, 2019 at 12:34:25PM -, Michael van Elst wrote:
>
> > It's probably trying to use a graphics card that isn't supported.
> > In that case you could try to intercept the bootloader to get a
> > prompt and 'boot netbsd -c'. This will start in userconf mode where,
> > assuming the keyboard works, you can disable the DRM driver for
> > your graphics card. When you quit userconf mode, it will then
> > fall back to use the plain VGA driver.
>
> How can I identify the specific driver in question? Perhaps userconf
> itself has a way of doing this? Is there some hallmark token for
> which I should search dmest?
>
> --
> Bob Bernstein



-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

Strange. Up untill connection.c I have more or less the same notes and
warnings, but then I get:

  CC connection.o
os/connection.c: In function 'ErrorConnMax':
os/connection.c:646:18: warning: assignment discards 'const' qualifier
from pointer target type [-Wdiscarded-qualifiers]
  iov[1].iov_base = NOROOM;
  ^
  CC io.o
  CC osinit.o
  CC WaitFor.o
  CC lbxproxytrans.o
  CCLD   lbxproxy
  GENlbxproxy.1


and the build completes without an error. I can't see anything
relevant in /etc/mk.conf except I have

CCACHE_DIR?=/usr/pkg/.ccache
PKGSRC_COMPILER=ccache gcc

but I doubt any link. Otherwise I have:

# uname -a
NetBSD nbuild.lorien.lan 8.99.35 NetBSD 8.99.35 (XEN3_DOMU) #13: Sun
Mar 17 02:07:55 GMT 2019
sysbu...@nbuild.lorien.lan:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/XEN3_DOMU
amd64
# gcc --version
gcc (nb1 20190119) 7.4.0

On Mon, 18 Mar 2019 at 07:59, Bob Bernstein  wrote:
>
> On Sun, Mar 17, 2019 at 06:39:11PM +, Chavdar Ivanov wrote:
>
> > BTW I finally finished a full modular-xorg build. Starting some
> > tests now.
>
> Perhaps I can follow in your footsteps.
>
> I started all over again Sunday morning: new install of -current,
> new cvs of pkgsrc, etc. I did quite well:
>
> $ pkg_info |grep ^modular
> modular-xorg-server-1.20.4 Modular X11 server from modular X.org
> modular-xorg-drivers-1.19.0nb4 Modular Xorg driver meta-package
> modular-xorg-libs-1.5nb1 Modular Xorg library meta-package
> modular-xorg-xephyr-1.20.4 Xephyr server based on kdrive from modular X.org
>
> However, a fly did find the ointment when it was lbxproxy's turn:
>
> "cc1: some warnings being treated as errors"
>
> I used to know what CFLAG will turn that off, but it's been a long
> time. Thanks if you can help get me over this hump.
>
> I'll stick the output in here:
>
> --
> These are not the droids you are looking for.



-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

I can't say much about the compiler version, I think I've seen some
relatively recent changes. I have two pkgsrc build hosts - one with
X11_TYPE modular, using the earlier version, the other - without
X11_TYPE, using the later - failing for you - version, so I can't
really test it ( or so I *think*, it being an operative word ),
without messing the one using built-in Xorg (the test systems use
pkgin for installation).

The interesting (and for tech-x11 as well) thing might be that I
tested my HP Envy 17 laptop with modular Xorg (using an 8GB USB stick
with live-image from yesterday, removing /usr/X11R7 and pkgin
installation of modular Xorg, surprisingly faster working than one
might expect) and compared the Xorg log files. While similar, there
were differences important enough to make me switch to modular Xorg
permanently. My NVidia 950M was apparently not yet supported by the
DRI2 infrstructure, but the built-in Xorg still recognizes it, loads
the nouveau module, eventually failing and unloading it, to let the
Intel driver carry on - which it does, and works, with the expection
of AIGLX failing. The modular Xorg log file does not show any
reference to the NVidia card (I took it off the xorg.conf file), AIGLX
succeeds. The server versions of both the built-in and modular Xorg
are the same.

Right now I am building xfce4 with modular Xorg, after that I will
switch to modular ( should be as easy as hiding the old /usr/pkg,
/var/dg/pkg, /usr/X11R7, making two copies of /etc/rc.conf to account
for the different installed packages, installing and running pkgin
from the new modular Xorg build host; this will give me the
opportunity to swap easily between the two Xorg options with the
corresponding set of dependent packages).


On Mon, 18 Mar 2019 at 18:27, Bob Bernstein  wrote:
>
> I installed ccache and made my /etc/mk.conf look like yours:
>
> X11_TYPE=modular
> CCACHE_DIR?=/usr/pkg/.ccache
> PKGSRC_COMPILER=ccache gcc
>
> ...and cd'd to /usr/pkgsrc/x11/lbxproxy to do a 'make clean
> clean-depends'. I ran aground on the same warning-treated-as-error
> as before. What I notice is we are using "slightly" different
> versions of gcc.
>
> Yours:
> > # gcc --version
> > gcc (nb1 20190119) 7.4.0
>
> Mine:
> # gcc --version
> gcc (nb2 20190226) 7.4.0
>
> And for the record:
> # uname -a
> NetBSD nebby.localdomain 8.99.35 NetBSD 8.99.35 (GENERIC) #0: Fri
> Mar 15 22:09:21 UTC 2019
> mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>
> I will take the liberty again to attach the make output.
>
> Thank you!
>
> --
> Bob Bernstein
>


-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

I also tried to build modular-xorg, so far it has been a bit of a
disaster with many .pc packages showing as missing, some of them
actually avalable in the built-in X, but not all. Just in case, I cvs
updated my pkgsrc tree and am running pkg_rolling-replace at the
moment in order to reattempt building modular-xorg later. I had it
built perhaps 6 months ago for some other machine, not recently.

On Fri, 15 Mar 2019 at 14:41, Chavdar Ivanov  wrote:
>
> x11/pixman installs pkgconf package (confusion between 'pkgsrc'
> package and package in the 'pkgconf' context). X11/pixman does not
> depend on modular Xorg. I would try to rerun the modular-xorg
> installation after cleaning the work folders as some configure scripts
> might have failed detecting it.
>
>  pkgconf --path pixman-1
> /usr/pkg/lib/pkgconfig/pixman-1.pc
>
> > pkg_info -L pixman
> Information for pixman-0.38.0:
>
> Files:
> /usr/pkg/include/pixman-1/pixman-version.h
> /usr/pkg/include/pixman-1/pixman.h
> /usr/pkg/lib/libpixman-1.la
> /usr/pkg/lib/libpixman-1.a
> /usr/pkg/lib/libpixman-1.so
> /usr/pkg/lib/libpixman-1.so.0
> /usr/pkg/lib/libpixman-1.so.0.38.0
> /usr/pkg/lib/pkgconfig/pixman-1.pc
>
> BTW what is the NVidia hardware on this machine?
>
> On Fri, 15 Mar 2019 at 14:18, Bob Bernstein  wrote:
> >
> > On Thu, 14 Mar 2019, Chavdar Ivanov wrote:
> >
> > > When I do rolling replace I usually manually install osabi and
> > > dependents in advance.
> >
> > Any thoughts on this odd "pixman-1" pkg which showed up in a
> > subsequent make attempt in /modular-xorg?
> >
> > --
> > ,[ IMPORTANT ]---
> > | This email is intended for the use of the individual
> > | addressee(s) named above and may contain information that
> > | is confidential, privileged or unsuitable for overly
> > | sensitive persons with low self-esteem, no sense of humour
> > | or irrational metaphysical beliefs.
> > `
> >
>
>
> --
> 



-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

When I do rolling replace I usually manually install osabi and dependents
in advance.

On Thu, 14 Mar 2019 at 20:16, Bob Bernstein 
wrote:

> I am aiming at a successful pkgsrc build of modular-xorg. I posted
> an error log yesterday to tech-x11. Overall, I'm trying to get
> nouveau and X to function on this machine. (-current boots via
> userconf disabling nouveau.)
>
> As a rule I eschew cross-posting, but the traffic volume is low, and
> the error seems like it will be deemed to merit attention.
>
> I upgraded to -current 8.99.35, and cvs -A up'd my pkgsrc tree.
> Then I ran pkg_rolling-repace -rsuv. As noted, it ran aground in
> osabi. Here is the output:
>
> Script started on Thu Mar 14 15:55:05 2019
> RR> Checking for mismatched installed packages using pkg_chk
> rr> devel/pkgconf - pkgconf-1.4.1nb1 < pkgconf-1.6.0
> rr> mail/mutt - mutt-1.11.3 < mutt-1.11.4
> rr> pkgtools/osabi - osabi-NetBSD-8.0 < osabi-NetBSD-8.99.35 (has binary
> package)
> ** Unable to read PKGCHK_CONF
> '/usr/pkgsrc/pkgchk_update-nebby.localdomain.conf'
> RR> Excluding the following mismatched packages:
> rr> EXCLUDE=[]
> RR> Checking for rebuild-requested installed packages (rebuild=YES)
> RR> Checking for unsafe installed packages (unsafe_depends_strict=YES)
> RR> Packages to rebuild:
> rr> MISMATCH_TODO=[pkgconf mutt osabi-NetBSD]
> rr> REBUILD_TODO=[]
> rr> UNSAFE_TODO=[]
> RR> Building dependency graph for installed packages
> RR> Tsorting dependency graph
> RR> Selecting osabi-NetBSD (pkgtools/osabi) as next package to replace
> RR> Checking if osabi-NetBSD has new depends...
> RR> Replacing osabi-NetBSD-8.0
> ===> Cleaning for osabi-NetBSD-8.99.35
> ===> Skipping vulnerability checks.
> WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
> WARNING: To fix run: `/usr/pkg/sbin/pkg_admin -K /var/db/pkg
> fetch-pkg-vulnerabilities'.
> ===> Installing dependencies for osabi-NetBSD-8.99.35
> => Build dependency cwrappers>=20150314: found cwrappers-20180325
> ===> Overriding tools for osabi-NetBSD-8.99.35
> ===> Extracting for osabi-NetBSD-8.99.35
> ===> Patching for osabi-NetBSD-8.99.35
> ===> Creating toolchain wrappers for osabi-NetBSD-8.99.35
> ===> Installing for osabi-NetBSD-8.99.35
> => Generating pre-install file lists
> => Automatic manual page handling
> => Generating post-install file lists
> => Checking file-check results for osabi-NetBSD-8.99.35
> => Creating binary package
> /usr/pkgsrc/pkgtools/osabi/work/.packages/osabi-NetBSD-8.99.35.tgz
> ===> Building binary package for osabi-NetBSD-8.99.35
> => Creating binary package
> /usr/pkgsrc/packages/All/osabi-NetBSD-8.99.35.tgz
> ===> Replacing for osabi-NetBSD-8.99.35
> ===> Updating using binary package of osabi-NetBSD-8.99.35
> /usr/bin/env  /usr/pkg/sbin/pkg_add -K /var/db/pkg -U -D
> /usr/pkgsrc/pkgtools/osabi/work/.packages/osabi-NetBSD-8.99.35.tgz
> pkg_add: Can't open +CONTENTS of depending package x11-links-1.12
> pkg_add: 1 package addition failed
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/pkgsrc/pkgtools/osabi
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/pkgsrc/pkgtools/osabi
> *** Error code 1
>
> Stop.
> make: stopped in /usr/pkgsrc/pkgtools/osabi
> *** 'make replace' failed for package osabi-NetBSD.
> *** Please read the errors listed above, fix the problem,
> *** then re-run pkg_rolling-replace to continue.
> - osabi-NetBSD
>
> Script done on Thu Mar 14 15:55:52 2019
>
> Thank you.
>
>
> --
> In our age there is no such thing as 'keeping out of
> politics'. All issues are political issues, and
> politics itself is a mass of lies, evasions, folly,
> hatred, and schizophrenia.
>
>   George Orwell "Politics and the English Language" (1946)
>
-- 

Re: xfce4 startup issue

[Chavdar Ivanov]

The last few days on -current pkgsrc I upgraded gnome, xfce4 and mate
on -current (amd64, atm from an hour ago). They all seem to work fine;
I did install avahi, hal and dbus as per the gnome's MESSAGE, but
found that xfce4 works without the former two; I always start xfce4
with 'startxfce4', for some reason I don't see the xfce4 session from
gdm. Minor annoyance is that file name clash between the themes
required for gnome and the other two -

...
---Feb 09 23:05:34: installing gnome-themes-standard-3.20.2nb8...
pkg_add: Conflicting PLIST with gnome-themes-2.32.1nb24:
share/icons/HighContrast/index.theme
...


On Sat, 9 Feb 2019 at 22:39, Robert Nestor  wrote:
>
> I’m still trying to isolate the problem I’m seeing.  Did notice that hal is 
> no longer dragged in when I install xfce4 from current or 2018Q4, so I’ve 
> eliminated it in my install.  Avahi was being pulled in when I installed 
> seamonkey, so I’ve disabled it for the time being.  Where I am now is testing 
> with 2018Q4 packages.  With dbus disabled xfce comes up and more or less 
> runs. (Mouse clicks and window movement is really hit or miss.)  With dbus 
> enabled xfce hangs at the autostart point but it takes a long time to get 
> there and I’m not finding any errors in the logs.  Haven’t tried the same 
> install using current versions of packages, but it’s on my list of things to 
> do.



-- 

Re: Clock Unsynchronized

[Chavdar Ivanov]

I remember having problems sometimes ago when my NetBSD machines were
around 8.99.25 or so (my timeserver is an RPI Model B still on
8.99.2). I haven't had these problems for a while, but all my -current
machines are on 8.99.32.

Chavdar

On Mon, 28 Jan 2019 at 15:51, Patrick Welche  wrote:
>
> Just noticed (NetBSD-8.99.26/amd64):
>
> ntpd[1575]: kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized
>
> This is after a ntpdate which succeeded in catching up the 3/4 hour
> that clock was behind by. I haven't seen this error before...
>
> Is ACPI-Fast a good choice? (I didn't choose...)
>
> # sysctl kern.timecounter
> kern.timecounter.choice = TSC(q=-100, f=2666902400 Hz) clockinterrupt(q=0, 
> f=100 Hz) ichlpcib0(q=1000, f=3579545 Hz) ACPI-Fast(q=1000, f=3579545 Hz) 
> lapic(q=-100, f=266767233 Hz) i8254(q=100, f=1193182 Hz) dummy(q=-100, 
> f=100 Hz)
> kern.timecounter.hardware = ACPI-Fast
> kern.timecounter.timestepwarnings = 0
>
>
> Cheers,
>
> Patrick



-- 

Re: minidisplay-port on T440s working?

[Chavdar Ivanov]

01/25/19, 11:32, Robert Elz:
> Date:Fri, 25 Jan 2019 09:10:31 +
> From:David Brownlee 
> Message-ID:  
> 
>
>   | Interestingly when I boot Windows with the BIOS locked to Intel only, VGA
>   | is also the only port that works. my
A few notes, to add to the clutter...

On my HP Envy 17 (Intel 530, NVidia GeForce 950M) xrandr says
...
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis
y axis) 382mm x 215mm
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
1060mm x 626mm
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
...

whn I connect it to my old(ish) Samsung TV; on boot, the TV starts to
mirror the panel after the framebuffer fonts get loaded, X also works
fine (I suppose the second monitor can be made as desktop extension
rather than a mirror, but as I do not intend to actually use it, I
didn't bother to find out how for now, probably another 'Xorg
-configure' with the second monitor and then some tweak).
>
> Perhaps the hardware is built with the Intel GPU only connected to the VGA
> port, and it is expected that the nvidia GPU will be used when you're 
> connecting to anything else?
>
> For comparison I have a no-name (but not cheap, it is a well configured
> laptop) with both Intel (Kaby-Lake) and Nvidia chips, and in it, using only
> intel, xrandr says ...
>
> eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm 
> x 194mm
> DP1 disconnected (normal left inverted right x axis y axis)
> DP2 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> HDMI2 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
>
> I deleted lines about the available resolutions on the eDP1 (which is
> the display).   There is no VGA, but the NetBSD current kernel
> finds all the rest - though one of the HDMI's has no (visible)
> external connector   I had the HDMI connected to a 4K
> resolution display a few months ago, and that worked fine.
> I have not yet tried the external DP ports (two apparent sockets
> for those exist).   I have no idea what VIRTUAL1 represents!
>
> Unfortunately (or perhaps not) the nvidia is just ...
> [   1.0045648] vendor 10de product 1c8d (3D display, revision 0xa1) at pci1 
> dev 0 function 0 not configuredn
Mine is recognized, but not served:
...
nouveau0 at pci1 dev 0 function 0: vendor 10de product 139a (rev. 0xa2)
nouveau0: info: NVIDIA GM107 (1171a0a2)
nouveau0: autoconfiguration error: error: bios: unable to locate usable
image
nouveau0: autoconfiguration error: error: bios ctor failed, -22
nouveau0: autoconfiguration error: unable to create nouveau device: 22
...

(at least now, since perhaps 8.99.29, I don't have to disable nouveau*;
earlier it used to lead to panic).

>
> The point of this is that I believe that the Intel driver in current
> handles most of this OK, or at least seems to for me.   That is,
> except I have no clue what to do to make it load firmware.
> I do have what I believe are the correct files, installed in
> what ought to be the right place...So DRM is not working.
>
> [   5.4026955] kern error: 
> [drm:(/readonly/release/testing/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:636)i915_firmware_load_error_print]
>  *ERROR* failed to load firmware i915/kbl_dmc_ver1.bin (0)
> [   5.4026955] kern error: 
> [drm:(/readonly/release/testing/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.c:651)i915_firmware_load_error_print]
>  *ERROR* The driver is built-in, so to load the firmware you need to
> [   5.4026955] kern error: 
> [drm:(/readonly/release/testing/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc_loader.c:560)guc_fw_fetch]
>  *ERROR* Failed to fetch GuC firmware from i915/kbl_guc_ver9_14.bin (error -2)
> [   5.4085285] kern error: 
> [drm:(/readonly/release/testing/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw]
>  *ERROR* Failed to initialize GuC, error -5 (ignored)
>
>
> ls -la /libdata/firmware/i915
> total 560
> drwxr-xr-x   2 root  wheel 512 Sep 15 13:46 .
> drwxr-xr-x  20 root  wheel 512 Sep 15 13:33 ..
> -rw-r--r--   2 kre   wheel8616 Sep 15 13:32 kbl_dmc_ver1.bin
> -rw-r--r--   2 kre   wheel8616 Sep 15 13:32 kbl_dmc_ver1_01.bin
> -rw-r--r--   1 kre   wheel8840 Sep 15 13:34 kbl_dmc_ver1_04.bin
> -rw-r--r--   1 kre   wheel  142656 Sep 15 13:37 kbl_guc_ver9_14.bin
> -rw-r--r--   1 kre   wheel  147776 Sep 15 13:45 kbl_guc_ver9_39.bin
> -rw-r--r--   1 kre   wheel  218688 Sep 15 13:46 kbl_huc_ver02_00_1810.bin
>
> hw.firmware.path = 
> /libdata/firmware:/usr/libdata/firmware:/usr/pkg/libdata/firmware:/usr/pkg/libdata

I am in the same place:
...
i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 191b (rev. 0x06)
kern info: [drm] Memory usable by graphics device = 4096M
kern info: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

Re: minidisplay-port on T440s working?

[Chavdar Ivanov]

Many thanks for the suggestion; I will try them, at least to get some
experience with xrandr, which I hadn't used in anger before.

As far as the microcode is concerned, I tried a few hours ago to use
the files which get delivered by 'apt install firmware-misc-nonfree'
on debian-stretch, but the interesting ones were exactly the same as
those I got from the git repository. Perhaps the loading process under
NetBSD itself needs some work; I had a look

As far as the dual card setup is concerned, besides NetBSD and Windows
10 I occasionaly run on the same laptop OpenSUSE tumbleweed, RedHat
7.6 and a few Ubuntu flavours; the mess is more or less the same
everywhere (except Windows 10, in all honesty), and perhaps on the
Ubuntu setup. As you mentioned above regarding the lack of NVidia
hardware recognition, I am also happy that now at least the nouveau
driver doesn't cause a panic any more; looking at some earlier mail
conversations in this space it seems a new version of the dri2 stuff
needs to be ported in order to get the latest nouveau driver to work
under NetBSD, but at least now the system is stable.

On Fri, 25 Jan 2019 at 15:57, Robert Elz  wrote:
>
> Date:Fri, 25 Jan 2019 14:43:59 +
> From:    Chavdar Ivanov 
> Message-ID:  
>
>   | rather than a mirror, but as I do not intend to actually use it, I
>   | didn't bother to find out how for now, probably another 'Xorg
>   | -configure' with the second monitor and then some tweak).
>
> On another system where I have two more or less permanently
> connected monitors, I have this in xorg.conf
>
> Section "ServerLayout"
> Identifier "X.org Configured"
> Screen  0  "Screen0" 0 0
> Screen  1  "Screen1" RightOf "Screen0"
> InputDevice"Mouse0" "CorePointer"
> InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> (along with definitions for Screen0 & Screen1)   I have no idea
> if Xorg --configure can make anything like that, I did it by hand.
>
> But on my laptop, I just use xrandr to move things around.
> Provided the virtual desktop is big enough (mine says:
>
>Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
>
> and 32Kx32K is plenty, you could have 8 4K monitors side by side with
> that) all it should take is a command like
>
> xrandr --output HDMI1 --right-of eDP1
>
> though there might need to be additional args to get things "just right",
> and perhaps to pick a resolution, etc.   xrandr has lots of options...
>
> You can also do --left-of --above or --below, and --rotate, --reflect
> and much much more.
>
> The "Screen 0: ..." "current" values will just get bigger as there are
> real screens to cause it.   Note that it is always a rectangle though,
> if the monitors have different resolutions, you tend to end with areas
> of "dead" space, which looks to applications (like window managers)
> like usable screen real estate, but for which there is no monitor
> to display the pixels.   That's unavoidable I think (though playing
> with resolutions and scaling might sometimes help).
>
>   | Where should I get the microcode from?
>
> I got the files I have from some intel site I believe, just from a google
> search for i915 firmware, or the expected filenames, or something
> (it was months ago, when Kaby Lake support got added to NetBSD)
> and then some poking around.
>
> Most of what I have there is irrelevant, I am confident of that,
> I added them just because they were available, and "just in case".
> Two files should be all that is needed.
>
>   | https://github.com/wkennington/linux-firmware/tree/master/i915, wasn't
>   | sure if there is other canonical place to get them from (apparently they
>   | are not in src/sys/dev/microcode).
>
> No, they were not there.
>
> kre
>


-- 

Re: Video Driver for Intel - resolution stuck at 800x600

[Chavdar Ivanov]

On Fri, 1 Feb 2019 at 12:36, Ron Georgia  wrote:
>
> " Why not just run NetBSD-current if that works with your card?"
> A most excellent question, with a relatively embarrassing answer: I am not 
> sure how to keep NetBSD-current, current. I am part of the NetBSD-current 
> mailing list and read about different issues others are experiencing; 
> however, I do not really know how to update the base OS or apply a particular 
> (suggested) patch. I did read the " Tracking NetBSD-current" page, but it 
> seems confusing to me.

It is very easy. Install from pkgsrc sysutils/sysbuild and
sysutils/sysupgrade and follow the description. Basically you have a
new user - sysbuild - whose home folder contains src and xsrc; I also
make the usual softlinks from /usr/[x]src. By default it creates a
cron job running cvs update overnight; in the morning you can update
the system using sysupgrade. I usually stop the cron job and run the
update manually whenever there is something of interest, perhaps 3-4
times a week. There are a few quirks running -current as opposed to
released or stable version, but in my view they are worth it.
Generally -current has been very reliable for me, the periods when one
cannot build it or there are some other - driver or kernel level -
problems are fairly rare. From time to time you may have to clean the
obj folder as the process doesn't account for all possible changes. I
don't remember the last time I ran build.sh manually; also on the same
machine I do builds for amd64, i386 and evbarm. So far inplace upgrade
with sysutils/sysupgrade hasn't failed for me, and I do it on systems
which I need daily (like the one I use for my invoice issuing
website).

>
> Thank you for responding. I'll try current again.
>
> On 2/1/19, 7:22 AM, "Sad Clouds"  wrote:
>
> On Thu, 31 Jan 2019 20:46:17 -0500
> Ron Georgia  wrote:
>
> > All,
> > Here is my dmesg for my machine: https://pastebin.com/RdmGu29k
> > Here is my Xorg.0.log: https://pastebin.com/xQw4rwsx
> >
> > clement$ uname -a
> > NetBSD clement.ronverbs.dev 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17
> > 14:59:51 UTC 2018
> > mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> > amd64
> >
> > I installed NetBSD 8.0, using the UEFI install image. Install went
> > smoothly; however, the video driver fails. I did X -configure and
> > copied the resulting xorg.conf.new file to /etc/X11/xorg.conf... but
> > that fails as well. The driver is intel.
> >
> > Section "Device"
> > Identifier  "Card0"
> > Driver  "intel"
> > BusID   "PCI:0:2:0"
> > EndSection
> >
> > If I change the driver to "wsfb" it works, but only with 800x600
> > resolution. I tried to build the xf86-video-wsfb driver from source
> > but got the following error:
> >
> > Package dependency requirement 'randrproto >= 1.6.0' could not be
> > satisfied. Package 'randrproto' has version '1.5.0', required version
> > is '>= 1.6.0'
> > Honestly, I am not sure how to upgrade randrproto. What's in pkgsrc
> > is version 1.5.0.
> >
> > I did install NetBSD 8.99.30 and the video worked perfectly.
> > Maybe two question then:
> >
> > How do I update randrproto?
> > Or, how do I pull in the video drivers used by NetBSD current?
> >
> > Ron Georgia
> > “90% of my problems are due to ignorance, the other 10% is because I
> > just don’t know any better.”
> >
>
> Maybe NetBSD-8 does not support your graphics card? Why not just run
> NetBSD-current if that works with your card?
>
>
>


-- 

Re: osabi in -current in some difficulty?

[Chavdar Ivanov]

x11/pixman installs pkgconf package (confusion between 'pkgsrc'
package and package in the 'pkgconf' context). X11/pixman does not
depend on modular Xorg. I would try to rerun the modular-xorg
installation after cleaning the work folders as some configure scripts
might have failed detecting it.

 pkgconf --path pixman-1
/usr/pkg/lib/pkgconfig/pixman-1.pc

> pkg_info -L pixman
Information for pixman-0.38.0:

Files:
/usr/pkg/include/pixman-1/pixman-version.h
/usr/pkg/include/pixman-1/pixman.h
/usr/pkg/lib/libpixman-1.la
/usr/pkg/lib/libpixman-1.a
/usr/pkg/lib/libpixman-1.so
/usr/pkg/lib/libpixman-1.so.0
/usr/pkg/lib/libpixman-1.so.0.38.0
/usr/pkg/lib/pkgconfig/pixman-1.pc

BTW what is the NVidia hardware on this machine?

On Fri, 15 Mar 2019 at 14:18, Bob Bernstein  wrote:
>
> On Thu, 14 Mar 2019, Chavdar Ivanov wrote:
>
> > When I do rolling replace I usually manually install osabi and
> > dependents in advance.
>
> Any thoughts on this odd "pixman-1" pkg which showed up in a
> subsequent make attempt in /modular-xorg?
>
> --
> ,[ IMPORTANT ]---
> | This email is intended for the use of the individual
> | addressee(s) named above and may contain information that
> | is confidential, privileged or unsuitable for overly
> | sensitive persons with low self-esteem, no sense of humour
> | or irrational metaphysical beliefs.
> `
>


-- 

Re: Laptop Recommendations for NetBSD?

[Chavdar Ivanov]

I boot - from the laptop F9 - select efi file to boot - bootx64.efi.
boot.cfg is on the root filesystem, as usual. The two Linux
installations on the same disk have some grub, but I don't use it to
boot anything besides them. It all just came to pass without any
problems for me on this laptop, as far as the EFI and NetBSD setup is
concerned; I also generally followed the same guide.

On Tue, 25 Jun 2019 at 06:39, Thomas Mueller  wrote:
>
> from Jason Mitchell:
>
> > > How do you set up to boot NetBSD using UEFI?
>
> > > I am trying to set up UEFI to boot FreeBSD, NetBSD, and future 
> > > installation of Linux, even Haiku if I can cross-compile that.
>
> > > I succeeded booting FreeBSD by UEFI, but NetBSD attempt hung early 
> > > (8.99.46 amd64).
>
> > Tom
>
> > Tom,
>
> > I’m assuming you followed the guide below. It worked for me on 8.0 on amd64 
> > and obviously worked for the person who wrote the guide.
>
> > https://wiki.netbsd.org/Installation_on_UEFI_systems/
>
> > Maybe try 8.1_STABLE?
>
> > HTH,
>
> > Jason M.
>
> > P.S. FYI, A direct email to you bounced.
>
> I followed the method from that guide  but was not using sysinst.
>
> I see, in /usr/mdec, bootx64.efi and bootia32.efi for NetBSD amd64, and 
> bootia32.efi but no bootx64.efi for NetBSD i386.  Those two bootia32.efi 
> files are not identical even on NetBSD amd64 and i386 built from the same 
> source tree.  I even see the two dosboot.com files differ in size.
>
> I couldn't get the boot prompt to recognize  dev wedge:WD2G18 ; I am using 
> GPT.
>
> Or would I need BTINFO_ROOTDEVICE wedge:WD2G18 ?
>
> I don't know where I would put a boot.cfg file on the EFI system partition.
>
> I received your message through the netbsd-users list but not direct from 
> you, don't know how your iPhone mail is set up.
>
> Tom
>


-- 

Re: Laptop Recommendations for NetBSD?

[Chavdar Ivanov]

Another fairly regular and reasonably happy NetBSD laptop user here.
HP Envy 17" 2016 vintage with Intel 530 graphics and NVidia GeForce
950M, latter detected, but unsuported. Intel DRM accelerated graphics
now works very well, with only a few disappearing horizontal streaks
with gdm and kdm (xdm now looks perfect). 3D acceleration, full screen
video all work well, there are no problems with the Wifi (very
reliable, I do all my upgrades from another system on my LAN via it,
also use pkgin over it). Sound is working as expected. The
installation of NetBSD is on a GPT labeled disk and uses UEFI,
performed following the abovementioned link - basically, I added a
second disk to the laptop, converted it under Windows 10 to GPT, then
initially installed OpenSUSE Tumbleweed on it, added some partition as
add-on for Windows, then installed RedHat 7.4, after which, having
some 100GB leftover,  I decided to try the UEFI NetBSD installation (I
always use -current of the moment and update using sysupgrade 2-3
times a week). Initially I had to disable nouveau, as it caused a
panic during boot; later this problem was solved.  At some stage I
installed rEFInd to get the nice OS graphics choice screens; with the
EFI version of the time it was possible to choose a default .efi file
to boot from; later I upgraded the laptoip to the latest version of
the EFI (F.51), this default option was lost, so now I have to choose
which efi file to boot after hitting F9, which is a bit of a pain, as
I have to traverse through the EFI hierarchy (there are four EFI
partitions altogether... ).

Overall, as long as it is not the latest and greatest, there is a
reasonably good chance to get NetBSD running on a wide range of
devices, as we know well. I've had several attempts to get FreeBSD (of
different versions and distributions) and OpenBSD on this laptop, but
there were always problems (I had Trident on an external USB3 disk for
a while, an upgrade rendered it unusable; OpenBSD didn't like the
hardware as well). I use at present Firefox 67.04, although midori and
epiphany are also available and working reasonably well. There is also
an older HP Elite laptop with broken glass and non functioning FireGL
graphics, setup as a development server for NetBSD-current, which also
works well; this is also used for virtualisation via qemu-nvmm and vnc
display.

Chavdar

On Mon, 24 Jun 2019 at 11:49, Riccardo Mottola
 wrote:
>
> Hi,
>
> David Brownlee wrote:
> > I'm another NetBSD ThinkPad user - T530 which is supported quite well.
> > My main use is IntelliJ IDEA java development.
> > My main gripe would be Firefox crashing on trying to load some sites
> > (eg maps.google.com) :/
>
> this is a little bit off-topic: does the crash happen also on a
> Workstation? I suppose it is a more general Firefox issue and even more
> broadly: browser support which coes beyond Chrome on Windows or Linux.
> Only Firefox is left and there too, things are less optimal beyond the
> "major" OS.
>
> ArcticFox loads maps.google.com but also openstreetmaps :)
>
> Riccardo



-- 

Re: libwnck3 fails to build

[Chavdar Ivanov]

Disable introspection or define DISPLAY.

On Sat, 27 Apr 2019 at 18:16, Andy Ball  wrote:

> Hello,
>
> I am unable to build meta-pkgs/xfce4 on NetBSD/amd64 7.2
> because it depends on devel/libwnck3, which fails to build.
> I welcome any suggestions.
>
> Thanks,
>   - Andy Ball.
>
>
> => Bootstrap dependency digest>=20010302: found digest-20160304
> ===> Skipping vulnerability checks.
> WARNING: No /var/db/pkg/pkg-vulnerabilities file found.
> WARNING: To fix run: `/usr/sbin/pkg_admin -K /var/db/pkg
> fetch-pkg-vulnerabilities'.
> => Checksum SHA1 OK for libwnck-3.24.1.tar.xz
> => Checksum RMD160 OK for libwnck-3.24.1.tar.xz
> => Checksum SHA512 OK for libwnck-3.24.1.tar.xz
> ===> Installing dependencies for libwnck3-3.24.1nb5
> => Tool dependency glib2-tools-[0-9]*: found glib2-tools-2.56.1
> => Tool dependency libtool-base>=2.4.2nb9: found libtool-base-2.4.6
> => Tool dependency gmake>=3.81: found gmake-4.1nb3
> => Tool dependency pkgconf-[0-9]*: found pkgconf-1.3.5
> => Build dependency x11-links>=1.13: found x11-links-1.13
> => Build dependency cwrappers>=20150314: found cwrappers-20170611
> => Full dependency glib2>=2.34.0: found glib2-2.56.2nb1
> => Full dependency gobject-introspection>=1.34.0: found
> gobject-introspection-1.56.1
> => Full dependency startup-notification>=0.12nb2: found
> startup-notification-0.12nb3
> => Full dependency gtk3+>=3.24.1nb2: found gtk3+-3.24.1nb3
> ===> Overriding tools for libwnck3-3.24.1nb5
> ===> Extracting for libwnck3-3.24.1nb5
> ===> Patching for libwnck3-3.24.1nb5
> ===> Creating toolchain wrappers for libwnck3-3.24.1nb5
> ===> Configuring for libwnck3-3.24.1nb5
> => Generating pkg-config file for builtin expat package.
> => Modifying GNU configure scripts to avoid --recheck
> => Replacing config-guess with pkgsrc versions
> => Replacing config-sub with pkgsrc versions
> => Replacing install-sh with pkgsrc version
> => Adding run-time search paths to pkg-config files.
> => Fixing locale directory references.
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g
> wheel
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... build-aux/install-sh -c -d
> checking for gawk... /usr/bin/awk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether UID '0' is supported by ustar format... yes
> checking whether GID '0' is supported by ustar format... yes
> checking how to create a ustar tar archive... gnutar
> checking whether make supports nested variables... (cached) yes
> checking whether to enable debugging... no
> checking build system type... x86_64--netbsd
> checking host system type... x86_64--netbsd
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for x86_64--netbsd-gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking whether gcc understands -c and -o together... yes
> checking dependency style of gcc... gcc3
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for grep that handles long lines and -e... (cached) /usr/bin/grep
> checking for egrep... (cached) /usr/bin/egrep
> checking for fgrep... /usr/bin/grep -F
> checking for ld used by gcc...
> /usr/pkgsrc/devel/libwnck3/work/.cwrapper/bin/ld
> checking if the linker (/usr/pkgsrc/devel/libwnck3/work/.cwrapper/bin/ld)
> is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... (cached) 262144
> checking how to convert x86_64--netbsd file names to x86_64--netbsd
> format... func_convert_file_noop
> checking how to convert x86_64--netbsd file names to toolchain format...
> func_convert_file_noop
> checking for /usr/pkgsrc/devel/libwnck3/work/.cwrapper/bin/ld option to
> reload object files... -r
> checking for x86_64--netbsd-objdump... no
> checking for objdump... objdump
> checking how to recognize dependent libraries... match_pattern
> /lib[^/]+(\.so|_pic\.a)$
> checking for x86_64--netbsd-dlltool... no
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for x86_64--netbsd-ar... no
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for x86_64--netbsd-strip... no
> checking for strip... strip
> checking for x86_64--netbsd-ranlib... no
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking 

Re: libwnck3 fails to build

[Chavdar Ivanov]

I just had it a few days pop on me building something else, on
-current, forgot what exactly.

Pray excuse my ignorance, but what is introspection and does it being
disabled effect the resulting packages in any end-user observable way?

On Sat, 27 Apr 2019 at 18:37, Martin Husemann  wrote:
>
> On Sat, Apr 27, 2019 at 06:28:28PM +0100, Chavdar Ivanov wrote:
> > Disable introspection or define DISPLAY.
>
> Huh, why is that broken again? (btw: it has been finally fixed upstream
> a week or so ago).
>
> Martin



-- 

Re: libwnck3 fails to build

[Chavdar Ivanov]

Do you actually *have* DISPLAY pointing to a functional and accepting
connections X server? I my case I used to start VcXsrv on a Windows 10
machine with disabled client control; nothing ever was shown on
screen, but the build finished.

On Sat, 27 Apr 2019 at 19:40, Andy Ball  wrote:
>
>
> Hello Chavdar,
>
>CI> Disable introspection or define DISPLAY. ??
>
> I tried setting DISPLAY to :1.0 but that didn't seem to help.
> What is introspection and how do I disable it?

I have no idea what introspection is, sorry. I asked too.

To quote my earlier mail (from 29th of January this year:
...
To summarize - one can't have a package build with introspection
enabled AND no DISPLAY set AND xfce4-conf installed on the build
system. Take any one of these and the build succeeds.


One can disable it if it is in the options.mk list, i.e if 'make
show-options' suggests it. I presently have, at least on one system
right now:

PKG_OPTIONS.cogl += -introspection
PKG_OPTIONS.clutter += -introspection
PKG_OPTIONS.clutter-gtk0.10 += -introspection

(I was building gnome-games earlier today when I had to do this;
months ago I had much more, but I lost the disk and didn't have any
backup of the configuration files).

>
> Thanks,
>   - Andy Ball
>


--

Re: upgrade - what will happen?

[Chavdar Ivanov]

На 2019-04-29 в 21:04, Greg A. Woods написа:
> At Sun, 28 Apr 2019 11:02:30 +0200, Benny Siegert  wrote:
> Subject: Re: upgrade - what will happen?
>> When you upgrade, the old library versions stay around, so old
>> packages continue to work -- with the exception of things depending on
>> osabi, which might break.
> Isn't there's one small caveat about old shared library versions?
>
> Postinstall(8), which will be run by sysinst during an upgrade, or if
> you do a manual upgrade and then similarly run "postinstall fix" as is
> recommended, will remove "obsolete" files, including old system shared
> libraries. 

No, it won't. At least, id doesn't remove them for me, I update my
systems all the time with sysupgrade, which invokes postinstall. E.g., I
still have

libssh.so.32.0 libssh.so.33.0 libssh.so.34.0.


>
> --
>   Greg A. Woods 
>
> +1 250 762-7675   RoboHack 
> Planix, Inc.  Avoncote Farms 
> libssh.so.32.0

Re: pkg/54123 (crash trying 'pkgin upgrade' with locally built pkg_summary)

[Chavdar Ivanov]

On Sat, 20 Apr 2019 at 07:16, Greg A. Woods  wrote:
>
> [[ I tried sending this to gnats-admin, but it hasn't appeared yet, and
> in any case folks here might have answers or suggestions too. ]]
>
> At Wed, 17 Apr 2019 23:32:40 +0100, Jonathan Perkin  
> wrote:
> Subject: Re: pkg/54123 (crash trying 'pkgin upgrade' with locally built 
> pkg_summary)
> >
> > While pkgin shouldn't crash and should be able to handle bad input, it
> > should be pointed out that this use-case is not expected to work at all,
> > and any fix will simply enforce that.  Your pkg_summary files should be
> > generated from binary package files, not installed packages.
>
> Hmmm... OK, so how should I generate the pkg_summary file for my limited
> archive of locally built binary packages?
>
> I couldn't find much info anywhere about handling the server-side of
> things for pkgin, so I RTFM'ed and just did what it says in
> pkg_summary(5):
>
>  The pkg_summary file can be generated using the pkg_info(1) －X option.
>  For example, the following will list this data for all installed pack‐
>  ages:
>
>pkg_info ‐X ‐a

I have always used

cd /usr/pkgsrc/packages/All ; ( for i in *.tgz; pkg_info -X $i )  |
bzip2 > pkg_summary.bz2

This gives me the older versions of packages as well, should I need
them (and I do - e.g. qemu-3.1.0nb4.tgz was produced from
wip/qemu-nvmm, whereas qemu-3.1.0nb5.tgz from emulators/qemu, a rather
different one, ten times the size).

I still get errors using this repo on occasion, usually some
dependencies not caught for upgrade, so I have to examine the log file
and first go through their update - again with pkgin - repeating the
initial installation at the end. It is not ideal, but usable. I
normally setup the repo to be accessed via anonymous ftp, but also via
nfs.



>
> And I hoped that a file of the same name was of the kind that pkgin
> would be happy to use.
>
> Pkgin did seem to happily suck up the file, and "pkgin avail" gives me a
> nice list corresponding to all the binary packages I should have
> available.  It's just the attempt to install one of them that failed.
>
> I.e. there are binaries for all the installed packages in PKG_PATH --
> that's the point, after all, as I am trying to use pkgin to install
> those binaries on other local systems.  (Indeed I now rely on the way
> pkgsrc uses DESTDIR to create a binary package that's then installed as
> the last step, even on the build machine.)
>
> (and yes, PKG_PATH is set when I run "pkg_info -X -a", if that matters)
>
> One caveat I have locally is that these binary packages may not all for
> the same OS version and/or they may not all be in the same PKG_PATH
> location, since it is -current, and I've built different packages at
> different times while upgrading the OS from time to time (and though I
> often use pgk_rolling-replace with its '-B' option on the build machine,
> that doesn't seem to find absolutely everything that's not for the same
> OS version and rebuild it).
>
> So, I'm not sure if I should be simply linking together all the
> compatible OS version binary package directories, or not.  With pkg_add
> I can't put multiple repositories in PKG_PATH, and presumably not for
> "pkg_info -X" either, though it is hinted that repositories.conf can
> contain a list of locations, though it's not clear if there can only be
> one per $arch and/or $osrelease, nor is it clear what happens if
> different installed packages were built for different (but nominally
> compatible) $osrelease values.  (The issue for me is that I'll likely
> never manage to build everything I want all together at once with the
> exact same OS release -- and I don't want to care about this as long as
> the installed binaries run, and after all that's part of the point of
> using NetBSD is that the ABI is stable for the most part, and even if
> I've built packages on an old release that needs a COMPAT option, I
> might want to include them in the stable of binary packages that I make
> available for pkgin.  I only really want to use pkgin for its ease of
> managing upgrades, since for the initial installs it is not much
> different for me to just use pkg_add directly, provided I really can
> start with an empty /var/db/pkgin database and have it rebuilt to
> account for such manually installed packages.)
>
> --
> Greg A. Woods 
>
> +1 250 762-7675   RoboHack 
> Planix, Inc.  Avoncote Farms 



-- 

Re: amd64 SBCs on which NetBSD would run ?

[Chavdar Ivanov]

I was thinking of buying https://dlidirect.com/products/atomic-pi ,
which should work, but is apparently out of stock. Looks rather
appealing, though.

As far as RPI and pkgsrc, I have the original RPI Zero with pkgsrc, it
does what I need it for, although from time to time I have to reokace
the sd cards. It builds the packages for another RPI Model B, which
works as DNS/FTP/HTTP/time server at home; they both are on early
versions of -current.

On Sat, 4 May 2019 at 06:05, Mayuresh  wrote:
>
> I am using RPI2 with NetBSD for a certain requirement. There are some
> rough edges (wifi support, usb hub not working, media player not working
> etc.) Besides it's too slow to do any builds of pkgsrc.
>
> Was wondering whether there are SBC boards where I can use my amd64
> packages compiled on other devices. The board itself need not have a high
> end configuration (RPI like configuration is good enough) - just that
> NetBSD should work on it and it should have amd64 arch.
>
> Tried searching, but most SBCs seem arm based. Among those that are amd64
> based it's hard to figure out whether NetBSD would support it.
>
> Please do share recommendations / experiences.
>
> Mayuresh



-- 

Re: amd64 SBCs on which NetBSD would run ?

[Chavdar Ivanov]

Well, it's horses for courses... Some may need or require i386/amd64
architecture. It is certainly the cheapest Intel-based board I have
seen advertised. Anyway, yesterday some of the order options were
still available, today everything is shown as out of stock. I still
intend to monitor UK availability and perhaps try it. As it is running
different Linux versions and able to run Windows 10, chances are that
it will run NetBSD-current out of the box, albeit with lack of support
of some of the devices, i.e. sensors. If it doesn't, then it still
could be used with one of the Linux distributions for something, so it
wouldn't be a total loss.

On Sat, 4 May 2019 at 10:32, Sad Clouds  wrote:
>
> On Sat, 4 May 2019 09:53:32 +0100
> Chavdar Ivanov  wrote:
>
> > I was thinking of buying https://dlidirect.com/products/atomic-pi ,
> > which should work, but is apparently out of stock. Looks rather
> > appealing, though.
>
> Look at the size of that heatsink and the max speed is 1.9GHz. I have
> similar size on an old Intel Xeon. Raspberry Pi 3 at 1.4GHz is far more
> compact and probably not that much slower.



-- 

Re: libwnck3 fails to build

[Chavdar Ivanov]

See one earlier discussion here:
https://mail-index.netbsd.org/pkgsrc-users/2019/01/29/msg028005.html .
There were some others as well.

As far as I can see it, some of the introspection options have been
removed, but not all. And ofcourse, the build should complete without
the presence of a valid and accepting DISPLAY. I can't suggest if it
is an upstream problem or there is some need of additional
configuration in the pkgsrc platform.

On Sun, 28 Apr 2019 at 09:29, Andy Ball  wrote:
>
>
> Hello Chavdar,
>
>CI> Do you actually *have* DISPLAY pointing to a functional
>  > and accepting connections X server?
>
> It's the only X server running on this host and serves up a
> desktop via VNC.  I haven't tested whether it accepts connections
> from root, who is performing the make.  Is it old-fashioned of me
> to believe that a command-line compiler should not depend on the
> presence of an X server?
>
> -Andy Ball
>


-- 

Re: misc/calibre fails to start

[Chavdar Ivanov]

I built it on a amd64 -current system, as of two days ago. It also is used
to build NetBSD for the two test systems, one a VirtualBox guest with xfce4
and ctwm, the other an HP laptop with kde4, mate, xfce4 and ctwm.

I have usually PYTHON_VERSION_DEFAULT set to 37, but for tje time of the
build I commented it out, python versions can cause problems with some
builds.

Both systems have functional AIGLX. Xorg is the in tree, I haven't tried it
yet on a system with modular Xorg.


On Wed, 24 Apr 2019, 21:49 Bob Bernstein,  wrote:

>
>
> On 2019-04-23 04:17, Chavdar Ivanov wrote:
>
> > For what is worth, I just built the same version on -current amd64,
> > -current pkgsrc. It works fine for me.
>
> So that I might gain some understanding of how the environment in which
> I am attempting to launch calibre may differ from yours, would you be
> kind enough to provide some information about your system?
>
> For example, what X do you run? Do you use a display manager? A
> window-manager, or a "desktop?"
>
> I boot into the CLI and then launch xorg with startx. My ~.xinitrc file
> calls icewm and little else:
>
> % cat .xinitrc
> xrdb ~/.Xresources
> #/usr/pkg/bin/xscreensaver &
> #exec lxsession
> #exec xfce4-session
> icewm-session
>
>
> --
> What can be asserted without evidence can be
> dismissed without evidence.
>  Hitchens' Razor
>
>
>

Re: netbsd : internals : bach book : good to start-off?

[Chavdar Ivanov]

The second chapter of the above is available at
https://download.freebsd.org/ftp/doc/en/books/design-44bsd/book.pdf .

On Mon, 22 Apr 2019 at 19:18, Greg A. Woods  wrote:
>
> At Mon, 22 Apr 2019 05:08:54 GMT, Mayuresh Kathe  wrote:
> Subject: Re: netbsd : internals : bach book : good to start-off?
> >
> > i have no knowledge of any operating system internals, leave alone unix.
> > so, since bach's book is so light (in terms of page count) and affordable
> > i thought it would be a good starting-off point into operating system
> > internals.
>
> I think Bach's book is quite approachable for anyone who knows C, and it
> is still a very good guide to the general principles of any Unix-like
> monolithic kernel operating system.  I like Bach's writing style, and he
> gives many examples of how various system services are used, as well as
> describing how they are implemented.  Unfortunately it was written in
> the middle of the Unix wars and at a time when the kernel in particular
> was still mostly proprietary, so it doesn't include any actual code
> examples from any Unix kernel and instead pseudo-code is presented to
> describe kernel algorithms.
>
> There is a actually a book that very nearly focuses on early NetBSD (and
> FreeBSD, before they diverged so much), and that's McKusick, Bostic,
> Karels, and Quarterman's "The Design and Implementation of the 4.4BSD
> Operating System", published 1996 by Addison-Wesley.  ISBN: 0201549794 /
> ISBN-13: 9780201549799.  Used copies are available from Alibris.com for
> a reasonable price.  I've found this edition to be better than the newer
> FreeBSD-specific editions, at least from a NetBSD perspective, though it
> is also somewhat more dated.
>
> --
> Greg A. Woods 
>
> +1 250 762-7675   RoboHack 
> Planix, Inc.  Avoncote Farms 



-- 

Re: More ZFS testing in 9.0_BETA

[Chavdar Ivanov]

FYI - as I mentioned it elsewhere - I modified my qemu-nvmm VMs from
GPT slices and raw files to zvols without any problems. My next test
would be to see if I can ISCSI-share a zvol - which should work.
Later.

On Thu, 15 Aug 2019 at 13:25, Brad Spencer  wrote:
>
>
> I did some more ZFS testing in 9.0_BETA, sorry for the length.  There
> are a lot of advantages and use cases in getting ZFS more completely
> integrated into the NetBSD universe.  Raidframe+LVM is great too, but
> there are things that are harder to do with it.
>
> One of the purposes of these tests was to see how NetBSD ZFS interacted
> with other ZFS implementations in other OSs.  The following was done:
>
> "zfs export pool" created from NetBSD and "zfs import pool" into FreeBSD
> and SmartOS.  Both of these worked completely as expected. with full
> read and write on the pools.  There are ZFS features not enabled on
> pools created with NetBSD, but this does not appear to be a problem.  As
> long as a "zfs upgrade pool" is not performed you can import and export
> as much as you wish.  I have not tried any Linux implementations.
>
> Going the other direction did not work quite as expected.
>
> On pools created on FreeBSD, the ZFS features that are turned on will
> not allow the pool to import as writable on NetBSD.  This is not really
> an unexpected thing, given that features on turned on in FreeBSD that
> are not in NetBSD.  The pool will import readonly and appears to work as
> expected in that case.  It should be possible to create pools in FreeBSD
> with features disabled that will allow a better import.
>
> For SmartOS, pools created there will (might??  I only use the
> filesystems I presented to the ISO) have a GPT header attached to them.
> When NetBSD sees that, by default, it will create wedges.  As a general
> thing, this wouldn't be a problem.  However, "zpool import" does not
> appear to see dk devices or refuses to deal with them and thus no pools
> were noticed for import.  You can sort of force the issue by creating a
> directory with symlinks to the /dev/dkN devices in them and then do a
> "zpool import -d /dev/directory".  When this is attempted, the DOMU
> guest I was using panicked:
>
> panic: kernel diagnostic assertion "seg <= BLKIF_MAX_SEGMENTS_PER_REQUEST" 
> failed: file "/usr/src/sys/arch/xen/xen/xbd_xenbus.c", line 1032
>
> I am running an older 8.99.xx with Xen 4.8.x, but as this was from the
> guest, I suspect that a bug is still present.  From the BT, it appears
> that it tried to do the import, but failed somewhere in the lower level
> disk routines.  I did not try doing this with FreeBSD.
>
>
> Other things of note:
>
> Assuming you want to have separate /var and /usr, trying to use ZFS for
> those is a challenge.  One of the biggest issues is that /zbin/zfs and
> /zbin/zpool have linked against shared libraries in /usr/lib.  This is
> probably not for the best.  Further, mostly because of this, you can't
> reasonably have a /etc/rc.d/zfs start the module and make it usable for
> critical_filesystems in /etc/rc.conf (you can fake it out by putting the
> contents of the shared libraries in /usr/lib and then mount over it, but
> that is a bit ugly).  Having /var and /usr use LVM is possible mostly
> because /etc/rc.d/lvm exists and is started before critical_filesystems.
> ZFS should probably work the same way.
>
> Another item is that mountpoint=legacy really does not work.  Right now,
> there is neither support in the general mount system call for ZFS nor
> does a /sbin/mount_zfs exist.  You can actually get some of this effect
> by a simple shell script in /sbin called mount_zfs that translates the
> request into a "/sbin/zfs set mountpoint=XXX" call followed by a "zfs
> mount XXX".  I wrote a quick and dirty one of these, and with a quick
> and dirty /etc/rc.d/zfs, it will allow the effect (mostly) having /var
> and /usr be from a ZFS pool.
>
> An unexpected problem was with /var in this configuration, however.  For
> reasons that are not entirely obvious postfix will not start if /var is
> from a ZFS pool.  It errors in an unexpected way when trying to start
> postfix master.  I did not have time to do a full ktrace to see what it
> was trying to use, but something is not quite supported, or not
> supported in the same way as a FFS.
>
> An alternative might be to use a zvol with a FFS in it for /var.  This
> mostly does work as expected from the command line interactively.
> However, it won't work from boot because of a couple of problems.
>
> 1) The names of the devices confuse fsck and it fails on boot.  The zvol
> will be called something like /dev/zvol/dsk/pool/volname in fstab and
> fsck will want to try and clean /dev/zvol/dsk/pool/rvolname which is
> wrong for ZFS zvols.  You need to use /dev/zvol/rdsk/pool/volname.  You
> can put a symlink in and it will mostly work, but that is highly manual.
> LVM has a symlink tree it creates that points the devices at the right
> places in /dev/mapper which 

Re: More ZFS testing in 9.0_BETA

[Chavdar Ivanov]

On Thu, 15 Aug 2019 at 13:53, Chavdar Ivanov  wrote:
>
> FYI - as I mentioned it elsewhere - I modified my qemu-nvmm VMs from
> GPT slices and raw files to zvols without any problems. My next test
> would be to see if I can ISCSI-share a zvol - which should work.

It does, as expected, but is a bit slow. I tested using something
called IsMyHDOk, the resulting benchmark was 17.7; using a ZVOL
FreeNAS target over the same slowish connection I get 42.2; for
comparison on the same laptop the second rusty SATA HDD gives me
175.7, whilst the first M.2 SATA gives me  972.1.

It is in no way the right way to use iSCSI - the laptop is connected
wirelessly to an access point; the adapter clams current speed 866.7
mb/s (?), which then links to the upstairs room via a powerline
adapter, advertised az 1gb/s, but which has never given me anything
better than about 130mb/s - but then the link to the FreeNAS zvol goes
through the same route and on top of this FreeNAS is a XCP-NG guest,
whereas the NetBSD laptop is using a gigabit Ethernet to a local
switch beyond the powerline adapter...


> Later.
>
> On Thu, 15 Aug 2019 at 13:25, Brad Spencer  wrote:
> >
> >
> > I did some more ZFS testing in 9.0_BETA, sorry for the length.  There
> > are a lot of advantages and use cases in getting ZFS more completely
> > integrated into the NetBSD universe.  Raidframe+LVM is great too, but
> > there are things that are harder to do with it.
> >
> > One of the purposes of these tests was to see how NetBSD ZFS interacted
> > with other ZFS implementations in other OSs.  The following was done:
> >
> > "zfs export pool" created from NetBSD and "zfs import pool" into FreeBSD
> > and SmartOS.  Both of these worked completely as expected. with full
> > read and write on the pools.  There are ZFS features not enabled on
> > pools created with NetBSD, but this does not appear to be a problem.  As
> > long as a "zfs upgrade pool" is not performed you can import and export
> > as much as you wish.  I have not tried any Linux implementations.
> >
> > Going the other direction did not work quite as expected.
> >
> > On pools created on FreeBSD, the ZFS features that are turned on will
> > not allow the pool to import as writable on NetBSD.  This is not really
> > an unexpected thing, given that features on turned on in FreeBSD that
> > are not in NetBSD.  The pool will import readonly and appears to work as
> > expected in that case.  It should be possible to create pools in FreeBSD
> > with features disabled that will allow a better import.
> >
> > For SmartOS, pools created there will (might??  I only use the
> > filesystems I presented to the ISO) have a GPT header attached to them.
> > When NetBSD sees that, by default, it will create wedges.  As a general
> > thing, this wouldn't be a problem.  However, "zpool import" does not
> > appear to see dk devices or refuses to deal with them and thus no pools
> > were noticed for import.  You can sort of force the issue by creating a
> > directory with symlinks to the /dev/dkN devices in them and then do a
> > "zpool import -d /dev/directory".  When this is attempted, the DOMU
> > guest I was using panicked:
> >
> > panic: kernel diagnostic assertion "seg <= BLKIF_MAX_SEGMENTS_PER_REQUEST" 
> > failed: file "/usr/src/sys/arch/xen/xen/xbd_xenbus.c", line 1032
> >
> > I am running an older 8.99.xx with Xen 4.8.x, but as this was from the
> > guest, I suspect that a bug is still present.  From the BT, it appears
> > that it tried to do the import, but failed somewhere in the lower level
> > disk routines.  I did not try doing this with FreeBSD.
> >
> >
> > Other things of note:
> >
> > Assuming you want to have separate /var and /usr, trying to use ZFS for
> > those is a challenge.  One of the biggest issues is that /zbin/zfs and
> > /zbin/zpool have linked against shared libraries in /usr/lib.  This is
> > probably not for the best.  Further, mostly because of this, you can't
> > reasonably have a /etc/rc.d/zfs start the module and make it usable for
> > critical_filesystems in /etc/rc.conf (you can fake it out by putting the
> > contents of the shared libraries in /usr/lib and then mount over it, but
> > that is a bit ugly).  Having /var and /usr use LVM is possible mostly
> > because /etc/rc.d/lvm exists and is started before critical_filesystems.
> > ZFS should probably work the same way.
> >
> > Another item is that mountpoint=legacy really does not work.  Right now,
> > there is neither support in the general mount system call for ZFS 

Re: State of ZFS in 9.0_BETA

[Chavdar Ivanov]

On Sat, 10 Aug 2019 at 21:07, Greg Troxel  wrote:
>
> Chavdar Ivanov  writes:
>
> > On Sat, 10 Aug 2019 at 17:19, Martin Husemann  wrote:
> >>
> >> On Sat, Aug 10, 2019 at 06:17:50PM +0200, Hauke Fath wrote:
> >> > On Thu, 8 Aug 2019 16:46:46 +0200, Marc Baudoin wrote:
> >> > > ZFS has been updated for 9.0_BETA.
> >> >
> >> > On the same topic, is there a perspective for
> >> >
> >> > file-system ZFS # Solaris ZFS
> >> >
> >> > (i.e. a monolithic, non-module kernel)?
> >>
> >> I think this is not possible due to licensing issues.
> >
> > IANAL, but as far as I understand it, nothing in the CDDL licence
> > precludes the static inclusion of ZFS into the NetBSD kernel.
> >
> > If someone develops a product on the basis of the NetBSD kernel AND
> > this product includes modifications of the CDDL-licensed parts of the
> > kernel THEN he will be obliged to publish the source code of only the
> > files under CDDL (a file-based license) which have been modified. So
> > it introduces an element of obligation above and beyond one expects to
> > have when using a BSD-licensed software, but does not taint the rest
> > of the system in any way.
> >
> > I personally don't see a problem in having GENERIC+ZFS kernel
> > configuration, if this were technically feasible. But, e.g., if a
> > commercial entity decides to produce a SAN appliance based on NetBSD
> > and using ZFS, and if any CDDL-licensed files have been modified,
> > their source code will have to be produced.
>
> Perhaps true, but if the module scheme works for normal cases, little is
> gained for NetBDS to distribute a kernel like that, and it adds
> complexity thinking about licenses.

Of course.

I was thinking that if ZFS were in the kernel, it might be easier to
get ZFS root.

-- 

Re: State of ZFS in 9.0_BETA

[Chavdar Ivanov]

On Sat, 10 Aug 2019 at 17:19, Martin Husemann  wrote:
>
> On Sat, Aug 10, 2019 at 06:17:50PM +0200, Hauke Fath wrote:
> > On Thu, 8 Aug 2019 16:46:46 +0200, Marc Baudoin wrote:
> > > ZFS has been updated for 9.0_BETA.
> >
> > On the same topic, is there a perspective for
> >
> > file-system ZFS # Solaris ZFS
> >
> > (i.e. a monolithic, non-module kernel)?
>
> I think this is not possible due to licensing issues.

IANAL, but as far as I understand it, nothing in the CDDL licence
precludes the static inclusion of ZFS into the NetBSD kernel.

If someone develops a product on the basis of the NetBSD kernel AND
this product includes modifications of the CDDL-licensed parts of the
kernel THEN he will be obliged to publish the source code of only the
files under CDDL (a file-based license) which have been modified. So
it introduces an element of obligation above and beyond one expects to
have when using a BSD-licensed software, but does not taint the rest
of the system in any way.

I personally don't see a problem in having GENERIC+ZFS kernel
configuration, if this were technically feasible. But, e.g., if a
commercial entity decides to produce a SAN appliance based on NetBSD
and using ZFS, and if any CDDL-licensed files have been modified,
their source code will have to be produced.

https://web.archive.org/web/20091006181308/http://opensolaris.org/os/about/faq/licensing_faq/#CDDL-combo

>
> Martin


Chavdar
-- 

Fwd: More ZFS testing in 9.0_BETA

[Chavdar Ivanov]

-- Forwarded message -
From: Chavdar Ivanov 
Date: Sat, 24 Aug 2019 at 23:54
Subject: Re: More ZFS testing in 9.0_BETA
To: Jason Mitchell 


gpt can see properly zvols:
...
# gpt show /dev/zvol/dsk/pail/iscsia
 start  size  index  contents
 0 1 PMBR
 1 1 Pri GPT header
 232 Pri GPT table
34 32734  1  GPT part - Windows reserved
 32768  62877696  2  GPT part - Windows basic data
  62910464  4063 Unused
  6291452732 Sec GPT table
  62914559 1 Sec GPT header
# gpt show /dev/zvol/dsk/pail/nbsd
GPT not found, displaying data from MBR.

start size  index  contents
01 MBR
1   62 Unused
   63  8388545  1  MBR part 169 (active)
...

whereas disklabel/fdisk/dkctl/vnconfig apparently are not able:
...
# disklabel  /dev/zvol/dsk/pail/nbsd
disklabel: ioctl DIOCGDINFO: Inappropriate ioctl for device
# vnconfig -c vnd0 /dev/zvol/dsk/pail/nbsd
vnconfig: /dev/rvnd0: VNDIOCSET: Operation not supported
.

Is there any particular reason for this or is a matter of adding
support for ZFS/ZVols to both? I suppose I could iSCSI-share them and
then connect, but it looks somewhat convoluted...

Chavdar

(apologies for the incorrect 'reply' address earlier).


BTW the iSCSI route to access the zvols from the NetBSD system itself
actually works fine.

Chavdar

On Thu, 15 Aug 2019 at 19:04, Chavdar Ivanov  wrote:
>
> Ok, thanks. I didn’t have any idea about that.
>
> On Thu, 15 Aug 2019 at 18:31, Jason Mitchell  wrote:
>>
>> Hello,
>>
>> Just as an FYI, I’ve done lots of testing with powerline and you have to 
>> divide the number they give you by 7. They send the same data 7 times, so 
>> the adapter could send 1 Gbit, but you’ll only ever get 142Mbit.
>>
>> Thanks,
>>
>> Jason M.
>>
>> Sent from my iPhone
>>
>> > On Aug 15, 2019, at 9:14 AM, Chavdar Ivanov  wrote:
>> >
>> >> On Thu, 15 Aug 2019 at 13:53, Chavdar Ivanov  wrote:
>> >>
>> >> FYI - as I mentioned it elsewhere - I modified my qemu-nvmm VMs from
>> >> GPT slices and raw files to zvols without any problems. My next test
>> >> would be to see if I can ISCSI-share a zvol - which should work.
>> >
>> > It does, as expected, but is a bit slow. I tested using something
>> > called IsMyHDOk, the resulting benchmark was 17.7; using a ZVOL
>> > FreeNAS target over the same slowish connection I get 42.2; for
>> > comparison on the same laptop the second rusty SATA HDD gives me
>> > 175.7, whilst the first M.2 SATA gives me  972.1.
>> >
>> > It is in no way the right way to use iSCSI - the laptop is connected
>> > wirelessly to an access point; the adapter clams current speed 866.7
>> > mb/s (?), which then links to the upstairs room via a powerline
>> > adapter, advertised az 1gb/s, but which has never given me anything
>> > better than about 130mb/s - but then the link to the FreeNAS zvol goes
>> > through the same route and on top of this FreeNAS is a XCP-NG guest,
>> > whereas the NetBSD laptop is using a gigabit Ethernet to a local
>> > switch beyond the powerline adapter...
>> >
>> >
>> >> Later.
>> >>
>> >>> On Thu, 15 Aug 2019 at 13:25, Brad Spencer  wrote:
>> >>>
>> >>>
>> >>> I did some more ZFS testing in 9.0_BETA, sorry for the length.  There
>> >>> are a lot of advantages and use cases in getting ZFS more completely
>> >>> integrated into the NetBSD universe.  Raidframe+LVM is great too, but
>> >>> there are things that are harder to do with it.
>> >>>
>> >>> One of the purposes of these tests was to see how NetBSD ZFS interacted
>> >>> with other ZFS implementations in other OSs.  The following was done:
>> >>>
>> >>> "zfs export pool" created from NetBSD and "zfs import pool" into FreeBSD
>> >>> and SmartOS.  Both of these worked completely as expected. with full
>> >>> read and write on the pools.  There are ZFS features not enabled on
>> >>> pools created with NetBSD, but this does not appear to be a problem.  As
>> >>> long as a "zfs upgrade pool" is not performed you can import and export
>> >>> as much as you wish.  I have not tried any Linux implementations.
>> >>>
>> >>> Going the other direction did not work quite as expected.
>> >>>
>> >>> On poo

Re: Zfs on NetBSD

[Chavdar Ivanov]

For quite a while I hadn't tried ZFS under NetBSD; it used to crash
for me years ago under load and didn't seem much in the focus of the
development, I think it is fair to say. Following this thread, I
decided to give it a go. There was presently unused 32GB mSATA card in
one of my laptops, which I unmounted; there was no need to clean the
labels at all.
On -current 8.99.51 from a few days ago everything seem to be working
fine for me:
...
modload zfs
modstat zfs
zpool create tank /dev/wd2d
zpool status
df -k
ls -la /tank
zfs create tank/t1
zfs create tank/t2
zfs create tank/t3
df -k
zpool status
zpool scrub tank
zpool status
.
Some 13GB worth of packages were also tarred over with reasonable speed.

I am not sure if 'zpool scrub' actually does something, though - even
when there is some data on the disk, the subsequent 'zpool status'
claims the scrub has finished straight away:
...
# zpool status tank
  pool: tank
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:23:47 2019
config:

NAMESTATE READ WRITE CKSUM
tankONLINE   0 0 0
  wd2d  ONLINE   0 0 0

errors: No known data errors
# zpool scrub tank
# zpool status tank
  pool: tank
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:32:08 2019
config:

NAMESTATE READ WRITE CKSUM
tankONLINE   0 0 0
  wd2d  ONLINE   0 0 0

errors: No known data errors
..

Chavdar

On Sun, 28 Jul 2019 at 07:54, Greg Troxel  wrote:
>
> Ron Georgia  writes:
>
> > Yes, I do have /dev/zfs.
> > $ ll /dev/zfs
> > crw---  1 root  wheel  190, 0 Jul 21 15:23 /dev/zfs
> >
> > I did find the zfs.mod, but get this error when trying to load it.
> > $ sudo modload /stand/amd64/8.1/modules/zfs/zfs.kmod
> > modload: /stand/amd64/8.1/modules/zfs/zfs.kmod: Program version wrong
> >
> > Which makes sense since I am booting kernel 8.99.51 NetBSD 8.99.51 (GENERIC)
> > I did pull down the sets for NetBSD 8.99.51 (GENERIC) and unpacked 
> > base.tar.xz and modules.tar.xz. Then I copied the contents of stand to 
> > /stand/amd64/8.99.51. (Should I remove /stand/amd64/8.1?)
>
> Basically, you need consistent kernel and modules.  So if you have moved
> to current permanently, yes, delete the 8.1 modules.
>
> Also, to run current zfs, it seems overwhelmingly likely that you want
> to run the zfs userland binaries from current, not from 8.1.
>
> You may want to look at the various schemes for in-place updating, such
> as INSTALL-NetBSD from pkgsrc/sysutils/etcmanage (my take on how to do
> it), and sysupgrade (somebody else's take).
>
> I unpack all the sets except etc/xetc, unpack etc/xetc into
> /usr/netbsd-etc, and then merge the etc changes.
>
> > [ 11951.1654531] WARNING: module error: module `zfs' built for `80100', 
> > system `899005100'
> > [ 12310.9533135] WARNING: module error: module `zfs' built for `80100', 
> > system `899005100'
> > [ 12509.3029082] WARNING: module error: recursive load failed for `zfs' 
> > (`solaris' required), error 2
> > [  30.9168505] WARNING: module error: incompatible module class for `zfs' 
> > (3 != 2)
> > [  30.9769426] WARNING: module error: incompatible module class for `zfs' 
> > (3 != 2)
>
> That really looks like you are loading 8.1 modules.  rm them, and maybe
> you will get a different error.
>


-- 

Re: Zfs on NetBSD

[Chavdar Ivanov]

On second thought, ' zpool scrub' worked as expected; the amount
initially copied was not enough to notice it.

It does tak a lot of memory, though - as expected, during the tar copy:
...
Memory: 8387M Act, 4101M Inact, 40K Wired, 38M Exec, 12G File, 31M Free
... (on a 20GB laptop).

On Sun, 28 Jul 2019 at 12:35, Chavdar Ivanov  wrote:
>
> For quite a while I hadn't tried ZFS under NetBSD; it used to crash
> for me years ago under load and didn't seem much in the focus of the
> development, I think it is fair to say. Following this thread, I
> decided to give it a go. There was presently unused 32GB mSATA card in
> one of my laptops, which I unmounted; there was no need to clean the
> labels at all.
> On -current 8.99.51 from a few days ago everything seem to be working
> fine for me:
> ...
> modload zfs
> modstat zfs
> zpool create tank /dev/wd2d
> zpool status
> df -k
> ls -la /tank
> zfs create tank/t1
> zfs create tank/t2
> zfs create tank/t3
> df -k
> zpool status
> zpool scrub tank
> zpool status
> .
> Some 13GB worth of packages were also tarred over with reasonable speed.
>
> I am not sure if 'zpool scrub' actually does something, though - even
> when there is some data on the disk, the subsequent 'zpool status'
> claims the scrub has finished straight away:
> ...
> # zpool status tank
>   pool: tank
>  state: ONLINE
>   scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:23:47 2019
> config:
>
> NAMESTATE READ WRITE CKSUM
> tankONLINE   0 0 0
>   wd2d  ONLINE   0 0 0
>
> errors: No known data errors
> # zpool scrub tank
> # zpool status tank
>   pool: tank
>  state: ONLINE
>   scan: scrub repaired 0 in 0h0m with 0 errors on Sun Jul 28 13:32:08 2019
> config:
>
> NAMESTATE READ WRITE CKSUM
> tankONLINE   0 0 0
>   wd2d  ONLINE   0 0 0
>
> errors: No known data errors
> ..
>
> Chavdar
>
> On Sun, 28 Jul 2019 at 07:54, Greg Troxel  wrote:
> >
> > Ron Georgia  writes:
> >
> > > Yes, I do have /dev/zfs.
> > > $ ll /dev/zfs
> > > crw---  1 root  wheel  190, 0 Jul 21 15:23 /dev/zfs
> > >
> > > I did find the zfs.mod, but get this error when trying to load it.
> > > $ sudo modload /stand/amd64/8.1/modules/zfs/zfs.kmod
> > > modload: /stand/amd64/8.1/modules/zfs/zfs.kmod: Program version wrong
> > >
> > > Which makes sense since I am booting kernel 8.99.51 NetBSD 8.99.51 
> > > (GENERIC)
> > > I did pull down the sets for NetBSD 8.99.51 (GENERIC) and unpacked 
> > > base.tar.xz and modules.tar.xz. Then I copied the contents of stand to 
> > > /stand/amd64/8.99.51. (Should I remove /stand/amd64/8.1?)
> >
> > Basically, you need consistent kernel and modules.  So if you have moved
> > to current permanently, yes, delete the 8.1 modules.
> >
> > Also, to run current zfs, it seems overwhelmingly likely that you want
> > to run the zfs userland binaries from current, not from 8.1.
> >
> > You may want to look at the various schemes for in-place updating, such
> > as INSTALL-NetBSD from pkgsrc/sysutils/etcmanage (my take on how to do
> > it), and sysupgrade (somebody else's take).
> >
> > I unpack all the sets except etc/xetc, unpack etc/xetc into
> > /usr/netbsd-etc, and then merge the etc changes.
> >
> > > [ 11951.1654531] WARNING: module error: module `zfs' built for 
> > > `80100', system `899005100'
> > > [ 12310.9533135] WARNING: module error: module `zfs' built for 
> > > `80100', system `899005100'
> > > [ 12509.3029082] WARNING: module error: recursive load failed for `zfs' 
> > > (`solaris' required), error 2
> > > [  30.9168505] WARNING: module error: incompatible module class for `zfs' 
> > > (3 != 2)
> > > [  30.9769426] WARNING: module error: incompatible module class for `zfs' 
> > > (3 != 2)
> >
> > That really looks like you are loading 8.1 modules.  rm them, and maybe
> > you will get a different error.
> >
>
>
> --
> 



-- 

Re:

[Chavdar Ivanov]

I just did a quick test of 8.99.51 amd64 from yesterday (self-built, but
with no changes) to see how the EFI/GPT installation works using the latest
sysinstall (good work, Martin). This was done under VirtualBox, using a
newly created NetBSD/amd64 VM with EFI enabled.

Everything worked as it should for me this time, I didn't have to resort to
manual creation of the GPT partitions etc. as described elsewhere. Even
pkgin setup worked first time (I have a local pkgin repo using either ftp
or nfs, the test was using ftp).

On my present laptop I have been running NetBSD in EFI mode for quite some
time, but the installation was manual, following the sequence described in
the post about NetBSD on EFI.  It is on a secondary disk, shared with
instances of OpenSUSE/tumbleweed, RedHat 7.6 (the upgrade to 8.0 failed, so
I reverted), and one GPT partition for some Windows data. The primary disk
is also GPT, but it holds only Windows 10.



On Mon, 29 Jul 2019 at 06:18, Thomas Mueller  wrote:
>
> > Emmanuel Dreyfus  wrote:
>
> > > - in UEFI mode, bootstrap does not read boot.cfg and while it sees the
> > > GPT partitions, it is unable to access a RAID that has a GPT inside.
It
> > > can access a RAID that has a disklabel inside, though, but that does
not
> > > help for > 2 TB.
>
> > Reading the sources, I find that boot.cfg should be stored in the EFI
> > partion as /EFI/NetBSD/boot.cfg and ineed if it is at this location, EFI
> > bootstrap finds it.
>
> > I still have the problem with accessing a RAIDframe containing a GPT.
>
> > Emmanuel Dreyfus
>
> Where in the source tree would I find the stuff on booting EFI?
>
> I have NetBSD installations for both amd64 and i386, am also curious
about /usr/mdec/bootx64.efi and bootia32.efi .
>
> I see FreeBSD 12-STABLE and HEAD (13-current) include efibootmgr.
>
> When I tried to boot NetBSD-current by UEFI, I had trouble specifying the
root partition in a way that the boot loader would understand, finally got
that far, but NetBSD (current amd64) hung after the first line of screen
output.
>
> Tom
>


-- 

-- 

Re: State of ZFS in 9.0_BETA

[Chavdar Ivanov]

On Fri, 9 Aug 2019 at 21:41, Benny Siegert  wrote:
>
> Is root-on-zfs supported at all? I do not need a ZFS-capable
> bootloader, I can load the kernel from a different partition via GRUB,
> but can the zpool be at the root?

Something needs to load the module and mount the pools...

>
> On Fri, Aug 9, 2019 at 9:54 PM Chavdar Ivanov  wrote:
> >
> > FYI I switched all my nvmm virtual machines to use zvols under
> > -current, seems to be working rather well. I haven't yer tried
> > snapshotting them, I'll do that later, but so far haven't had any
> > problems, including performancewise. Previously they used either gpt
> > partitions or disk images.
> >
> > On Fri, 9 Aug 2019 at 06:28, Alistair Crooks  wrote:
> > >
> > > Working with a VM. Added 1 CPU and 3GB memory to the instance, 4 GB RAM 
> > > total
> > >
> > > Added a 50GB disk, presents as wd2
> > >
> > > Commands (edited to show kinda relevant ones) I also have a full backup 
> > > of my home dir in case I fat fingered anything
> > >
> > >   9986  19:24dmesg
> > >   9987  19:24sudo zpool create z /dev/wd2d
> > >   9989  19:25sudo zfs create z/home
> > >   9990  19:30sudo zfs set compression=lz4 z/home
> > >   9991  19:30sudo zfs set atime=off z/home
> > >   9992  19:30sudo zpool get all z
> > >   9993  19:31sudo zfs get all z/home
> > >   9994  19:31df
> > >   9995  19:31du -h ~agc/
> > >   9996  19:32cd /home
> > >   9998  19:32sudo pax -rwpe . /z/home/
> > >     19:33df
> > >  1  19:35cd /
> > >  10004  19:36sudo rm -rf /home
> > >  10007  19:37sudo zfs snapshot z/home@20190802
> > >  10009  19:38sudo zfs list
> > >  10011  19:38ls -al /z/home
> > >  10012  19:38ls -al /z
> > >  10013  19:39sudo zfs set mountpoint=/home z/home
> > >
> > > This is all on 9.99.something, BTW, but near enough to 9.0_BETA
> > >
> > > On Thu, 8 Aug 2019 at 10:55, Ron Georgia  wrote:
> > >>
> > >> How did you move your home directory? Did you create /tank/home then 
> > >> symlink the /home -> /tank/home?
> > >>
> > >>
> > >>
> > >> From: Alistair Crooks 
> > >> Date: Thursday, August 8, 2019 at 11:53 AM
> > >> To: Ronald Georgia 
> > >> Cc: Marc Baudoin , NetBSD Users  
> > >> 
> > >> Subject: Re: State of ZFS in 9.0_BETA
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Thu, 8 Aug 2019 at 07:52, Ronald Georgia  wrote:
> > >>
> > >> Same here. I have two 9BETA machines using zfs. Both have a mirrored 
> > >> pool of two disks. So far things seem to be working. This weekend I will 
> > >> be testing snapshots and send/receive.
> > >>
> > >>
> > >>
> > >> BTW, nice job with zfs.
> > >>
> > >>
> > >>
> > >> On Thu, Aug 8, 2019 at 10:47 AM Marc Baudoin  
> > >> wrote:
> > >>
> > >> Hi,
> > >>
> > >> ZFS has been updated for 9.0_BETA.  I've tried it and it seems
> > >> usable (I couldn't make it work in 8.0 so it's a real progress).
> > >> Now I'd like to know what's its state in 9.0_BETA (still
> > >> experimental, quite stable, production ready --- might be too
> > >> early) and what's the goal for the future?
> > >>
> > >> Thanks.
> > >>
> > >>
> > >>
> > >> I have no idea of official status, but I've moved the home directory on 
> > >> my main development machine to zfs, and am extremely happy so far with 
> > >> the results - snapshots and compression ftw
> > >>
> > >>
> > >>
> > >> Having said that, I did have issues copying some larger files from ffs 
> > >> to zfs until I added more memory.
> > >>
> > >>
> > >>
> > >> Best,
> > >>
> > >> Alistair
> >
> >
> >
> > --
> > 
>
>
>
> --
> Benny



-- 

Re: State of ZFS in 9.0_BETA

[Chavdar Ivanov]

FYI I switched all my nvmm virtual machines to use zvols under
-current, seems to be working rather well. I haven't yer tried
snapshotting them, I'll do that later, but so far haven't had any
problems, including performancewise. Previously they used either gpt
partitions or disk images.

On Fri, 9 Aug 2019 at 06:28, Alistair Crooks  wrote:
>
> Working with a VM. Added 1 CPU and 3GB memory to the instance, 4 GB RAM total
>
> Added a 50GB disk, presents as wd2
>
> Commands (edited to show kinda relevant ones) I also have a full backup of my 
> home dir in case I fat fingered anything
>
>   9986  19:24dmesg
>   9987  19:24sudo zpool create z /dev/wd2d
>   9989  19:25sudo zfs create z/home
>   9990  19:30sudo zfs set compression=lz4 z/home
>   9991  19:30sudo zfs set atime=off z/home
>   9992  19:30sudo zpool get all z
>   9993  19:31sudo zfs get all z/home
>   9994  19:31df
>   9995  19:31du -h ~agc/
>   9996  19:32cd /home
>   9998  19:32sudo pax -rwpe . /z/home/
>     19:33df
>  1  19:35cd /
>  10004  19:36sudo rm -rf /home
>  10007  19:37sudo zfs snapshot z/home@20190802
>  10009  19:38sudo zfs list
>  10011  19:38ls -al /z/home
>  10012  19:38ls -al /z
>  10013  19:39sudo zfs set mountpoint=/home z/home
>
> This is all on 9.99.something, BTW, but near enough to 9.0_BETA
>
> On Thu, 8 Aug 2019 at 10:55, Ron Georgia  wrote:
>>
>> How did you move your home directory? Did you create /tank/home then symlink 
>> the /home -> /tank/home?
>>
>>
>>
>> From: Alistair Crooks 
>> Date: Thursday, August 8, 2019 at 11:53 AM
>> To: Ronald Georgia 
>> Cc: Marc Baudoin , NetBSD Users  
>> 
>> Subject: Re: State of ZFS in 9.0_BETA
>>
>>
>>
>>
>>
>>
>>
>> On Thu, 8 Aug 2019 at 07:52, Ronald Georgia  wrote:
>>
>> Same here. I have two 9BETA machines using zfs. Both have a mirrored pool of 
>> two disks. So far things seem to be working. This weekend I will be testing 
>> snapshots and send/receive.
>>
>>
>>
>> BTW, nice job with zfs.
>>
>>
>>
>> On Thu, Aug 8, 2019 at 10:47 AM Marc Baudoin  wrote:
>>
>> Hi,
>>
>> ZFS has been updated for 9.0_BETA.  I've tried it and it seems
>> usable (I couldn't make it work in 8.0 so it's a real progress).
>> Now I'd like to know what's its state in 9.0_BETA (still
>> experimental, quite stable, production ready --- might be too
>> early) and what's the goal for the future?
>>
>> Thanks.
>>
>>
>>
>> I have no idea of official status, but I've moved the home directory on my 
>> main development machine to zfs, and am extremely happy so far with the 
>> results - snapshots and compression ftw
>>
>>
>>
>> Having said that, I did have issues copying some larger files from ffs to 
>> zfs until I added more memory.
>>
>>
>>
>> Best,
>>
>> Alistair



-- 

Re: Device timeout reading fsbn ...

[Chavdar Ivanov]

atactl, mistype.

On Tue, 1 Oct 2019 at 14:41, Thomas Mueller  wrote:
>
>
> mueller6...@twc.com ("Thomas Mueller") writes, and Michael van Elst responds:
>
> > >> sysctl -w hw.wd0.use_ncq=0
>
> > >Actually that would be wd1 in my case as opposed to wd0, but is there any 
> > >danger in using this sysctl, could it make the hard drive go bad more 
> > >quickly?
>
> > There is no danger, it prevents the driver from queuing more than one
> > request to the drive. That's how older netbsd versions behaved.
>
> > While a bad disk can't be ruled out, I tend to suspect a firmware or
> > driver bug that gets exercised with NCQ. That would explain why there
> > is no error with older netbsd.
>
>
> > >I guess I still need to move things over to the Hitachi hard drive, 
> > >including user data that could not be reinstalled.
>
> > Backing up the data is of course the first thing. But please also check
> > the disk with smartmontools or 'atatctl wd1 smart status' to see if itself
> > reports problems.
>
> Do you know when (what version) NCQ was introduced to NetBSD?  Was it before 
> or after 7.99.1?
>
> What is atatctl?  "which atatctl" shows nothing.  Is atatctl part of 
> smartmontools?
>
> I don't have smartmontools installed but could run it from the System Rescue 
> CD or build in NetBSD (or FreeBSD or Linux?) on the Hitachi hard drive.
>
> Firmware or driver bug could explain why the Western Digital Green hard drive 
> might be adversely affected but not all other hard drives.
>
> I believe Western Digital discontinued the Green hard drives because of 
> technical or performance problems.
>
> Tom
>


-- 

Re: VirtualBox guest support

[Chavdar Ivanov]

On Sun, 15 Dec 2019 at 04:53, Malcolm Herbert  wrote:
>
> On Fri, 13 Dec 2019, at 00:46, Valery Ushakov wrote:
> > This is the semi-periodic reminder that Virtual Box Guest Additions do
> > support NetBSD, the code has been in the public VirtualBox repository
> > for more than 3 years (but vboxfs support *is* indeed missing).
>
> Valery - apologies, I may have missed such a reminder ... in this the lack of 
> vboxsf is a minor nuisance as NFS works just as well in most cases but 
> requires configuration on the host end for support.
>
> > GA have not been packaged though. ...
>
> ... does this mean I might be able to build from source on the host itself?  
> Many of the other bento VMs do this as a matter of course as part of their 
> build, so this isn't a show-stopper either

Following earlier explanation from uwe@ I have setup a build
environment for the additions. With a few minor patches, it works
every time. My NetBSD guests - mostly -current - now all run under
VirtualBox 6.1 with the corresponding additions.

>
> > ... The main obstacle is that kernel
> > modules need access to some non-public kernel headers to be built.
>
> I'm not sure I understand this last bit - non-public kernel headers from the 
> NetBSD side or the VirtualBox side?

Basically you need /usr/src and /usr/xsrc on the build host.

Display device can be either VBoxVGA, VBoxSVGA (they appear identical
within the guest) or VMSVGA (which used to have a problem with the
mouse not registering events, but now works just fine). VirtualBox
allows accelerated 3D to be selected only in VBoxVGA mode for NetBSD
systems, even if they say this combination has been removed from the
release; it still works for me.

>
> Regards,
> Malcolm
>
> --
> Malcolm Herbert
> m...@mjch.net

Chavdar Ivanov.



-- 

Re: problems upgrading go112 (and go111) on NetBSD-8.99.32/amd64

[Chavdar Ivanov]

FYI I just rebuilt go112 using updated go14 as a bootstrap on two days
old amd64 -current.

On Mon, 15 Apr 2019 at 12:58, Benny Siegert  wrote:
>
> Try rebuilding lang/go14 perhaps?
>
> You could also try editing lang/go112/Makefile and setting
> GOROOT_BOOTSTRAP to /usr/pkg/go111.
>
> On Sun, Apr 14, 2019 at 11:26 PM Greg A. Woods  wrote:
> >
> > So, the following has been happening (and for go111), but I don't
> > understand the errors, nor have I any clue as to their cause.
> >
> > Note that I do have Go 1.11.1 installed and working A-OK on this same
> > machine, but built against somewhat older OS.
> >
> > 13:31 [510] $ go version
> > go version go1.11.1 netbsd/amd64
> >
> > 13:43 [516] $ /usr/sbin/pkg_info -Q BUILD_HOST go111
> > NetBSD future 7.99.34 NetBSD 7.99.34 (XEN3_DOMU) #2: Sun Jul  9 
> > 15:31:37 PDT 2017  
> > woods@future:/build/woods/future/current-amd64-amd64-obj/building/work/woods/m-NetBSD-current/sys/arch/amd64/compile/XEN3_DOMU
> >  amd64
> >
> > The host is now a reasonably recent current build (running in a Xen
> > domU):
> >
> > NetBSD future 8.99.32 NetBSD 8.99.32 (XEN3_DOMU) #0: Mon Feb  4 
> > 15:01:05 PST 2019  
> > woods@future:/build/woods/future/current-amd64-amd64-obj/building/work/woods/m-NetBSD-current/sys/arch/amd64/compile/XEN3_DOMU
> >  amd64
> >
> > The only thing that I think I've done since upgrading (and upgrading
> > other packages) is to run "postinstall fix obsolete" to clean out a
> > bunch of old cruft, most notably old libraries (there was more than a
> > couple of years of cruft lying about).
> >
> > When building the go111 package I encounter very similar errors.
> >
> > I'm posting here instead of just submitting a PR or issue on github
> > because I've been unable to find very much at all relating to these
> > errors, and I don't know how to diagnose it much deeper.  On the other
> > hand I'll be first to admit that my installation isn't quite standard
> > (it's definitely not an out-of-the-stock-ISO install), and so I would
> > really like to dig deeper to find the root cause of the problem as I'm
> > guessing this is a problem specific to my system and not something more
> > generic as I've found no other complaints about upgrading Go on
> > NetBSD/amd64.
> >
> > The only thing that's close seems to be about the confusing nature of
> > some of the linker errors:  https://github.com/golang/go/issues/29852
> > (but that's unrelated to the root cause of the specific errors I see)
> >
> > (Adding '-v' to the "make.bash" invocation doesn't really show anything
> > more useful or interesting at all, especially not the exact command-line
> > that's failing.)
> >
> > 13:21 [506] $ cd lang/go112
> > /usr/pkgsrc/lang/go112
> > 13:21 [507] $ make clean
> > ===> Cleaning for go112-1.12.1nb1
> > make13:21 [508] $ make
> > => Bootstrap dependency digest>=20010302: found digest-20180917
> > => Checksum SHA1 OK for go1.12.1.src.tar.gz
> > => Checksum RMD160 OK for go1.12.1.src.tar.gz
> > => Checksum SHA512 OK for go1.12.1.src.tar.gz
> > ===> Installing dependencies for go112-1.12.1nb1
> > => Tool dependency gtar-base>=1.13.25: found gtar-base-1.30
> > => Build dependency go14-1.4*: found go14-1.4.3nb7
> > => Full dependency bash-[0-9]*: found bash-4.4.019
> > => Full dependency perl>=5.0: found perl-5.28.0nb2
> > ===> Overriding tools for go112-1.12.1nb1 (in 
> > /var/package-obj/woods/lang/go112/work/.tools)
> > ===> Extracting for go112-1.12.1nb1
> > /bin/rm -r -f 
> > /var/package-obj/woods/lang/go112/work/go/test/fixedbugs/issue27836*
> > ===> Patching for go112-1.12.1nb1
> > => Applying pkgsrc patches for go112-1.12.1nb1
> > No such line 530 in input file, ignoring
> > ===> Creating toolchain wrappers for go112-1.12.1nb1
> > => Creating AS wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/as
> > ==> Searching for 'AS' program in: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin:/var/package-obj/woods/lang/go112/work/.buildlink/bin:/var/package-obj/woods/lang/go112/work/.gcc/bin:/var/package-obj/woods/lang/go112/work/.tools/bin:/usr/pkg/bin:/home/more/woods/go/bin:/home/more/woods/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/X11R7/bin:/usr/games:
> > ==> using '/usr/bin/as' for AS wrapper script
> > => Creating CC wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/gcc
> > => Linking CC wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/cc
> > => Linking CC wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/ada
> > => Creating CPP wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/cpp
> > => Creating CXX wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/c++
> > => Linking CXX wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/g++
> > => Linking CXX wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/CC
> > => Linking CXX wrapper: 
> > /var/package-obj/woods/lang/go112/work/.wrapper/bin/cxx
> 

Re: Another NVMM question

[Chavdar Ivanov]

Any chance you are trying to install Windows 10/64 ? AFAIK it still
doesn't run with nvmm. The 32-bit version is fine. though.

On Wed, 9 Oct 2019 at 16:47, Kamil Rytarowski  wrote:
>
> On 09.10.2019 17:37, Robert Nestor wrote:
> > Got a few systems installed and running under NVMM in NetBSD 9.0, but ran 
> > into this playing with a Windows installation.  It appears to be coming 
> > from NVMM and I’m curious if this is a current limitation in NVMM or are 
> > there some QEMU parameters which can be used to circumvent this.
> >
> > NetBSD Virtual Machine Monitor accelerator is operational
> > qemu-system-x86_64: NVMM: Mem Assist Failed [gpa=0xb8040]
> > qemu-system-x86_64: NVMM: Failed to execute a VCPU.
> >
>
> I would need to check into the code, but it could miss a cpu instruction
> in the decoder.
>
> Please file a bug report for it. There will be need for a proper
> reproduction steps and specification of your hardware and Window image.
>


-- 

Re: ZFS chroot cannot open dev nodes

[Chavdar Ivanov]

On Wed, 12 Feb 2020 at 12:16, Roy Marples  wrote:
>
> I'm experimenting with ZFS on a new server.
> Trying to get root on ZFS, but it's not working with device nodes.
>
> Here are exact steps from the real root on FFS.
> There is a zfs mount on /tank/ROOT.
>
> # cd /tmp
> # mknod null c 2 2
> # echo test >null
> # cd /tank/ROOT/tmp
> # mknod null c 2 2
> # echo test >null
> -sh: cannot create null: error 22
>
> Any clue as to why?
> zfs gets devices shows that every mount has it set to on and mount does not
> report the nodev option, so it *should* work.
>
> What am I missing? Does anyone else see this?
>
> This is NetBSD-9.0_RC2 if that helps.

Same on -current from 15 minutes ago, but I guess it was expected.

>
> Roy



-- 

Re: ZFS chroot cannot open dev nodes

[Chavdar Ivanov]

Works now, thanks.

On Thu, 13 Feb 2020 at 17:02, J. Hannken-Illjes  wrote:
>
> > On 12. Feb 2020, at 14:26, Chavdar Ivanov  wrote:
> >
> > On Wed, 12 Feb 2020 at 12:16, Roy Marples  wrote:
> >>
> >> I'm experimenting with ZFS on a new server.
> >> Trying to get root on ZFS, but it's not working with device nodes.
> >>
> >> Here are exact steps from the real root on FFS.
> >> There is a zfs mount on /tank/ROOT.
> >>
> >> # cd /tmp
> >> # mknod null c 2 2
> >> # echo test >null
> >> # cd /tank/ROOT/tmp
> >> # mknod null c 2 2
> >> # echo test >null
> >> -sh: cannot create null: error 22
> >>
> >> Any clue as to why?
> >> zfs gets devices shows that every mount has it set to on and mount does not
> >> report the nodev option, so it *should* work.
> >>
> >> What am I missing? Does anyone else see this?
> >>
> >> This is NetBSD-9.0_RC2 if that helps.
> >
> > Same on -current from 15 minutes ago, but I guess it was expected.
>
> Please try again with Rev. 1.57 of
> src/external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vnops.c
>
> --
> J. Hannken-Illjes - hann...@eis.cs.tu-bs.de - TU Braunschweig
>
>


--