Re: ThinkPad battery charge control

On Thu, 2024-04-25 at 21:54 -0400, Malte Dehling wrote: > Hi, > > I've added some things to the thinkpad acpi driver to allow modifying > battery charging behavior: keep charge within a range, force > discharge, > disable charging on AC. I think something like this would be good to > have in

NetBSD 10.0 crashing on shutdown

I have a few amd64 systems which ran NetBSD-10_BETA and used XFCE4/slim from pkgsrc-2023Q4 for the desktop. All of these ran absolutely solidly with no problems whatsoever. I upgraded a test system to NetBSD-10.0 keeping the same packages and that worked fine. On that basis I upgraded my main

Re: Firefox with webcam

On Mon, 2024-03-11 at 10:15 +0100, Hauke Fath (SPG) wrote: > Hi, > > has anybody had any recent success in using a webcam with Firefox? > > Sites like claim to detect the webcam > (it's a > logitech whatzit, attached as uvideo0), but are missing access > permissions.

Re: Firefox with webcam

On Mon, 2024-03-11 at 10:15 +0100, Hauke Fath (SPG) wrote: > Hi, > > has anybody had any recent success in using a webcam with Firefox? > > Sites like claim to detect the webcam > (it's a > logitech whatzit, attached as uvideo0), but are missing access > permissions.

Re: problem getting hostapd and bridging to work

Just to provide a heads up to others thinking of using the rpi model B as an access point gateway: DON'T The bottom line is that the built-in ethernet usmsc(4) on this board does not seem to support bridging - I find this utterly mindboggling so I think it's worth outlining what I did to come to

Re: problem getting hostapd and bridging to work

On Tue, 2023-07-18 at 21:08 -0500, David Young wrote: > On Tue, Jul 18, 2023 at 06:56:43PM +0100, Dave Tyson wrote: > > /etc/ifconfig.run0 > > apbridge > > up > > run(4) may not support `hostap` mode? > > David > Thanks for the heads up. Yes the r

problem getting hostapd and bridging to work

I have been trying to set up a simple wireless access point using rpi model B under NetBSD 10.0-BETA and seem to be failing miserably. Can someone hit me with a cluebat :-) Basically I have ethernet coming into the rpi usmsc0 10/100 interface and a USB D-Link DWA-140 to provide the wireless

support for Raspberry Pi zero 2 w

Can someone take a look at PR kern/57498 which includes patches and links to resources to provide a native dtb for the rpi02w and also update the rpi firmware so it will boot up. Dmesg after updates below. Note although the wifi chip is now visible the rpi02w uses the synatics syn43436 and this

Anyone having a problem with cross building arm* tools on current?

With a very recent checkout of NetBSD-current I am seeing a failure to build tools on arm6, aarch64 (and probably arm7), build.sh bombs out: dependall-dtc ===> .(with: dependall-makestrs dependall-makekeys dependall-cvslatest) dependall ===> makestrs nbmake[2]: nbmake[2]: don't know how to

Re: touch screen support

On Mon, 2023-05-29 at 08:39 +, Michael van Elst wrote: > dty...@anduin.org.uk (Dave Tyson) writes: > > > I guess these touch screens need some calibration to set the x/y > > bounds > > and maybe some mods to the driver. Can anyone hit me with a cluebat >

Re: touch screen support

On Sun, 2023-05-28 at 23:22 +, Taylor R Campbell wrote: > > Date: Sun, 28 May 2023 23:57:38 +0100 > > From: Dave Tyson > > > > [60.731037] uhidev0 at uhub0 port 1 configuration 1 interface 0 > > [60.731037] uhidev0: wch.cn (0x1a86) USB2IIC_CTP_CONTROL &

touch screen support

I have a couple of devices which report a touch screen present, but don't attach it correctly, failing with "touchscreen has no range report" This is under NetBSD-10 BETA (but I expect similar results in current) 1) Samsung DP700A3D all-in-one PC I use this my normal desktop and everything

Re: Raid and UEFI

On Wednesday 30 Nov 2022 20:26:51 Rhialto wrote: > On Sun 27 Nov 2022 at 23:10:45 +0000, Dave Tyson wrote: > > Sadly I discovered that the HP Proliant microserver the installation > > was for doesn't grok UEFI and only deals with bios booting. I did have > > an attempt

Re: Raid and UEFI

On Mon, 2022-11-21 at 08:07 +0100, Martin Husemann wrote: > > I have a GPT setup on two disks, both disks have a EFI system > partition > first and then a RAID partition for the rest of the disk. The > bootloader > is available in both EFI partitions. > > The raid then is further partitioned

Re: Raid and UEFI

On 21 November 2022 07:07:51 GMT, Martin Husemann wrote: On Sun, Nov 20, 2022 at 10:14:03PM +, Dave Tyson wrote: I was pondering switching to UEFI and was trying to work out if a similar redundant setup is even possible. I have a GPT setup on two disks, both disks have a EFI system

Raid and UEFI

I currently have a server which has the boot and data disks mirrored using raidframe. The O/S filesystems (/, /usr, /var) are all located in raid0a on wd0/wd1. data is located 1n raid1a on wd2/wd3. wd0/wd1 layout is standard mbr and both disks have bootblocks so the system will boot off either

Re: question about enumeration of buses on arm systems with dtb files

On Sunday 03 Apr 2022 13:08:43 Michael van Elst wrote: > campbell+netbsd-tech-k...@mumble.net (Taylor R Campbell) writes: > >I think usually it's first-come-first-serve according to the ordering > >in the device tree (that is, in a pre-order traversal, which is the > >same as the sequential order

question about enumeration of buses on arm systems with dtb files

I am trying to understand the enumeration of the GPIO pins on a RPI-zero-2 which boots up and runs under current. The DTS lists i2c0 with gpio pins 0 & 1 and i2c1 with gpio pin 2 & 3. These appear to be the only i2c interfaces defined (unless there are others hidden in the dtsi files). These

Re: Raspberry Pi camera under NetBSD current

On Monday 01 Nov 2021 09:42:57 Michael van Elst wrote: > dty...@anduin.org.uk (Dave Tyson) writes: > >> Trying to access the camera with raspistill however ends in a crash > >> in the vchiq driver. > > > >Thanks for the data point. I guess there may be significan

Re: Raspberry Pi camera under NetBSD current

On Wednesday 27 Oct 2021 20:07:53 Dave Tyson wrote: > On Wednesday 27 Oct 2021 18:28:31 Michael van Elst wrote: > > dty...@anduin.org.uk (Dave Tyson) writes: > > >I have been trying to get the raspberry pi camera to work on a model B > > >under a recent current snapshot.

Re: Raspberry Pi camera under NetBSD current

On Wednesday 27 Oct 2021 18:28:31 Michael van Elst wrote: > dty...@anduin.org.uk (Dave Tyson) writes: > >I have been trying to get the raspberry pi camera to work on a model B > >under a recent current snapshot. > > > > NetBSD 9.99.88 (RPI) #0: Fri Sep 24

Raspberry Pi camera under NetBSD current

I have been trying to get the raspberry pi camera to work on a model B under a recent current snapshot. NetBSD 9.99.88 (RPI) #0: Fri Sep 24 18:47:29 UTC 2021 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/RPI As standard booting off the sdcard works fine with the default

Re: help getting SPI interface to work

On Monday 20 Sep 2021 09:34:21 Michael van Elst wrote: > dty...@anduin.org.uk (Dave Tyson) writes: > >/dev/spi0 is defined which is a good start:: > > > >[ 1.03] sun4ispi0 at simplebus1: SPI > >[ 1.03] sun4ispi0: interrupting on GIC irq 42 > >[

help getting SPI interface to work

Having managed to get the I2C interface on a Banana pi running a recent current snapshot [talking to at least one device correctly] I decided to try /dev/spi0 is defined which is a good start:: [ 1.03] sun4ispi0 at simplebus1: SPI [ 1.03] sun4ispi0: interrupting on GIC irq 42

Re: Question about using I2C_IOCTL_EXEC to read data over I2C

On Tuesday 17 Aug 2021 10:32:50 Jason Thorpe wrote: > > On Aug 17, 2021, at 10:28 AM, Dave Tyson wrote: > > > > The device appears at address 0x77 (it's a BMP085) with i2cscan, the data > > sheet indicates the read address=0xEF/write address=0xEE. I just put 0x77

Question about using I2C_IOCTL_EXEC to read data over I2C

I am trying to get data from a temperature/pressure sensor connected via i2c to a banana pi running NetBSD current. I understand the I2C protocol but I am having a bit of difficulty understanding what appears on the wire when the I2C_IOCTL_EXEC is called with the various op commands. By trial

Re: Orange pi support for i2c

On Sunday 08 Aug 2021 08:31:57 Martin Husemann wrote: > On Sat, Aug 07, 2021 at 09:54:40PM +0000, Dave Tyson wrote: > > One other issue I noted with the latter two boards is that ethernet no > > longer works - this may be related to changes to the phy support > > intr

Re: Orange pi support for i2c

On Saturday 07 Aug 2021 23:50:09 Tobias Nygren wrote: > On Sat, 07 Aug 2021 21:54:40 + > > Dave Tyson wrote: > > The Banana pi seems to work OK with i2c with light testing, but I would > > really like a more 'lightweight' platform like the Orange pi zero or > > Or

Orange pi support for i2c

I have been testing a few SOC systems for i2c support as I have a need to replace a failing weather station. Tried a raspberry pi B on the latest current and that seems to still suffer the problem outlined in PR48855 which has been closed, but need to be reopened. The Banana pi seems to work

Re: Script command under NetBSD-current

On Tuesday 15 Jun 2021 08:15:12 RVP wrote: > On Mon, 14 Jun 2021, Dave Tyson wrote: > > NetBSD cruncher2.anduin.org.uk 9.99.83 NetBSD 9.99.83 (GENERIC) #2: Tue > > Jun 8 19:42:49 GMT 2021 > > r...@cruncher2.anduin.org.uk:/usr/obj/sys/arch/amd64/compile/GENERIC amd64 > >

Script command under NetBSD-current

I thought I noticed an issue with the script command under NetBSD-current a few weeks ago, but recently stumbled on it again. This is under: NetBSD cruncher2.anduin.org.uk 9.99.83 NetBSD 9.99.83 (GENERIC) #2: Tue Jun 8 19:42:49 GMT 2021

Re: problem with USER_LDT in current 9.99.81

On Monday 26 Apr 2021 19:36:00 Dave Tyson wrote: > On Tuesday 27 Apr 2021 04:22:22 matthew green wrote: > > Dave Tyson writes: > > > I have wine 4.4 working under NetBSD 9.99.23 amd64 (> 1 year ago) and > > > recently tried against a recent current - 9.99.81. &

Re: problem with USER_LDT in current 9.99.81

On Tuesday 27 Apr 2021 04:22:22 matthew green wrote: > Dave Tyson writes: > > I have wine 4.4 working under NetBSD 9.99.23 amd64 (> 1 year ago) and > > recently tried against a recent current - 9.99.81. > > > > Wine now complains: > > i386_set_ldt: Operation n

problem with USER_LDT in current 9.99.81

I have wine 4.4 working under NetBSD 9.99.23 amd64 (> 1 year ago) and recently tried against a recent current - 9.99.81. Wine now complains: i386_set_ldt: Operation not permitted Did you reconfigure the kernel with "options USER_LDT"? but GENERIC has the option enabled and strings on the kernel

Re: kevent monitoring of file system changes

On Sunday 14 Mar 2021 18:29:58 Mouse wrote: > > 1) If I am monitoring a file, for example, called 'a' and I copy > > another file over it then I get a write event and an extend event. > > If I copy the same file over it again I would have thought I should > > just get a write event as the file

kevent monitoring of file system changes

I have been looking at using kevent to monitor writes to file in order to detect and stream any changes. I have compiled and run the code given in the kevent man page on NetBSD-8 and NetBSD-9.1 and it seems to work OK, but I have a few questions :-) 1) If I am monitoring a file, for example,

Re: wip/wine64 on amd64

On Saturday 04 Apr 2020 21:44:42 Thomas Klausner wrote: > Hi! > > I've just fixed the compat32* packages so that they built for me. Then > I tried running two programs with wip/wine64 (see > https://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1) > > The first one is a c# application. wine

backporting USER_LDT to NetBSD-8

I've been playing with wine64 under NetBSD 8.1_STABLE and it works surprisingly well with a couple of windows applications I need to run. Of course NetBSD-8 doesn't have support for USER_LDT baked in and so I have been testing under a NetBSD current kernel. How much work would be involved in

Re: Recent pull to NetBSD-8 causes kernel link failure

On Thursday 12 April 2018 13:16:20 Soren Jacobsen wrote: > On 04/12 18:31, Dave Tyson wrote: > > Just CVS'ed up a test server to latest NetBSD-8 source and tried > > building a kernel. It compiles and tnen fails at the links stage: > > > > sys_ptrace_common.o: In f

Recent pull to NetBSD-8 causes kernel link failure

Just CVS'ed up a test server to latest NetBSD-8 source and tried building a kernel. It compiles and tnen fails at the links stage: sys_ptrace_common.o: In function `ptrace_listener_cb': /usr/src/sys/kern/sys_ptrace_common.c:239: undefined reference to `user_set_dbregs' *** [netbsd] Error code 1

arm make release failure when building BEAGLEBONE

This is from the current source tree a little earlier today, cross compiling arm on amd64: ./build.sh -j 4 -U -u -x -m evbearmv7hf-el -O /home/dtyson/cross/obj -T /home/dtyson/cross/tools release Might be fallout from the ata changes.. ... # compile compat/uipc_syscalls_30.o

Re: Peculiar problem with kmail on AMD64 current

On Monday 06 February 2017 09:44:17 Martin Husemann wrote: > On Sun, Feb 05, 2017 at 06:51:19PM +0000, Dave Tyson wrote: > > So it would appear that a userland program which should be insulated > > from the underlying hardware by the kernel is being affected by different > >

Re: crash with latest audio changes

On Saturday 17 Dec 2016 10:19:18 you wrote: > On Dec 17, 2:51pm, dty...@anduin.org.uk (Dave Tyson) wrote: > -- Subject: Re: crash with latest audio changes > > | On Friday 16 Dec 2016 17:03:57 you wrote: > | > On Dec 16, 9:37pm, dty...@anduin.org.uk (Dave Tyson) wrote: &g

Re: crash with latest audio changes

On Friday 16 Dec 2016 16:13:35 Christos Zoulas wrote: > In article <35284500.x7lh1kd...@cruncher.anduin.org.uk>, > > Dave Tyson <dty...@anduin.org.uk> wrote: > >I updated a DELL system from 7.99.39 (Oct 13th) to the latest current (Dec > >16th). When I bri

crash with latest audio changes

I updated a DELL system from 7.99.39 (Oct 13th) to the latest current (Dec 16th). When I bring up KDE the newer kernel panics in the audio code, works fine with older kernel. I guess this relates to the recent in-kernel mixer changes. NetBSD 7.99.50 (GENERIC) #0: Fri Dec 16 13:49:41 GMT 2016

Re: xorg.conf is read but not acted on correctly

On Saturday 10 December 2016 22:51:32 Soren Jacobsen wrote: > On 12/10 16:53, Dave Tyson wrote: > > [ 2175.541] Build Operating System: NetBSD/amd64 - > > [...] > > [ 2175.542] (WW) The directory "/usr/X11R7/share/fonts/X11/TTF" does > > not exist. >

xorg.conf is read but not acted on correctly

I normally don't bother creating a /etc/X11/xorg.conf file as the built-in defaults generally work OK. I just tried to create one using X -configure and then edited it to (a) allow for ms-ttf font and (b) set the keyboard layout "uk" I was slightly surprised that having the file xorg.conf

Re: xorg-server 1.18 ready for testing on x86 and shark

On Monday 22 Aug 2016 06:52:34 matthew green wrote: > > nbmake[13]: nbmake[13]: don't know how to make > > /usr/obj/external/mit/xorg/server/xorg-server/glamor/libglamor.a. Stop > > ah, this is a simple ordering issue i had missed due to manually > building this once.. > > please try with

Re: xorg-server 1.18 ready for testing on x86 and shark

cvs updated current src,xsrc earlier today and just had a try at building this with a clean obj directory and it blows up being unable to make libglamor.a ===> build.sh command:./build.sh -V HAVE_XORG_SERVER_VER=118 -u -U -x -T /usr/tools -O /usr/obj -j 2 release ===> build.sh started:

Issues with netstat -ia

Just upgraded an amd64 system to the latest current - checked out and compiled 8/7/16. NetBSD dell.anduin.org.uk 7.99.33 NetBSD 7.99.33 (GENERIC) #0: Fri Jul 8 15:30:25 BST 2016 r...@dell.anduin.org.uk:/usr/obj/sys/arch/amd64/compile/GENERIC amd64 I was building pkgsrc firefox 17.0.1 today

Re: nick-nhusb merge coming soon

On Wednesday 13 Apr 2016 07:59:20 Nick Hudson wrote: > Hi, > > I think the first phase of nick-nhusb is in a state ready to be > merged. I'd like to merge it in the next few days, but in the meantime > I've put some kernels for testing here: > > http://www.netbsd.org/~skrll/nick-nhusb > >

Re: nick-nhusb merge coming soon

On Wednesday 13 Apr 2016 07:59:20 Nick Hudson wrote: > Hi, > > I think the first phase of nick-nhusb is in a state ready to be > merged. I'd like to merge it in the next few days, but in the meantime > I've put some kernels for testing here: > > http://www.netbsd.org/~skrll/nick-nhusb > >

USB scanners and PR 50340

I note that PR 50340 has been closed and with the latest pkgsrc under current (amd64) my Mustek 1200 UB scanner seems to work OK - but I have comment out the uscanner device in the kernel and use it as a ugen device. It seems that this is the 'new world order' and the sane backend code to

USB crash with recent kernel on Raspberry Pi

Been playing with the latest R-Pi snapshot posted by Jun Ebihara on port-arm. Hooked up a USB webcam and tried mplayer. I thought it might fail as I have an outstanding PR-48308 with UVC cameras and it did, but with a different crash. Camera attached OK, but an ordinary user can crash kernel

Re: Latest amd64 snapshot has problems with disk sizes

This problem disappeared when a later snapshot was tried. The nightly build 201512080650Z installed perfectly so I suspect the original was corrupt or the build ran during some updates which left parts inconsistent. Dave -- = Phone: 07805784357 Open

Latest amd64 snapshot has problems with disk sizes

Just tried to install current using the latest AMD64 snapshot 201512071640Z on a blank SATA drive. Boots up off the memory stick OK and after allocating partitions it fails when trying to newfs the first partition rwd0a. An error: ioctl DIOCGMEDIASIZE failed 19 appears in the log messages

latest ntp pullup to NetBSD-7 branch seems to be schizophenic

I've just cvs'ed a server to pull in the updates to NetBSD-7 and and done a build release/build install. /usr/src/doc/CHANGES-7.1 notes that ntp has been updated to 4.2.8p4, but if I issue an ntpd --version it reports: ntpq 4.2.8p3-o Fri Oct 23 13:57:19 EDT 2015 (import) which is a bit

Re: Removing ARCNET stuffs

On 05/29/15 20:15, Gerard Lally wrote: At date and time Fri, 29 May 2015 11:09:08 -0500, J. Lewis Muir wrote: On 5/29/15 5:22 AM, David Holland wrote: Because of these trends, I've been thinking for a while now that maybe it's getting to be time to fork. Hello, David! I started using NetBSD

Re: HP Proliant Microserver N36L fails to boot under current

On 03/24/15 00:33, Michael van Elst wrote: dty...@anduin.org.uk (Dave Tyson) writes: I have an HP Proliant Microserver (N36L) which runs fine on NetBSD 7.0_BETA. I tried booting it from a recent current AMD64 image and it crashes out. The last few lines of the boot message (hand copied

HP Proliant Microserver N36L fails to boot under current

I have an HP Proliant Microserver (N36L) which runs fine on NetBSD 7.0_BETA. I tried booting it from a recent current AMD64 image and it crashes out. The last few lines of the boot message (hand copied) are: sysbeep0 at pcppi1 OMSC (PNP0C02) at acpi0 not configured RMSC (PNP0C02) at acpi0 not

Re: py-usb problems

On 02/19/15 07:49, Andreas Gustafsson wrote: Dave Tyson wrote: Not sure whether this belongs here or in pkgsrc-users. I have been trying to package the weewx weather station software which is written in python. It uses py-usb to handle the devices, but I cannot get it to see anything on the usb

Re: py-usb problems

On 02/18/15 19:05, Jonathan A. Kollasch wrote: On Wed, Feb 18, 2015 at 05:58:22PM +, Dave Tyson wrote: recent pkgsrc. /dev/usb* is readable/writeable by all What about /dev/ugen*.*? Any ugen devices in dmesg? Forgot to add that /dev/uhid0-/dev/uhid18 as also read-write all. Dave

Re: Peculier raidframe problems

On 12/20/14 11:49, Patrick Welche wrote: On Thu, Dec 18, 2014 at 08:58:24PM +, Dave Tyson wrote: I'll got a HP server running NetBSD 6.99.40 (amd64) ... If I reconstruct /dev/wd1a from /dev/wd0a then everything appears fine, but after a reboot /dev/wd1a is marked as failed again

Re: Peculier raidframe problems

On 12/19/14 00:49, Greg Troxel wrote: Does dmesg show any disk errors? Can you dd from the disk to /dev/null without errors? No disk errors reported. I started a dd of /dev/rwd1d to /dev/nulland this was over halfway through when the UPS threw a wobbler and caused a reboot. When the

Re: Peculier raidframe problems

On 12/19/14 15:10, Greg Oster wrote: On Fri, 19 Dec 2014 15:03:48 + Dave Tyson dty...@anduin.org.uk wrote: On 12/19/14 00:49, Greg Troxel wrote: Does dmesg show any disk errors? Can you dd from the disk to /dev/null without errors? No disk errors reported. I started a dd of /dev

Re: Peculier raidframe problems

On 12/19/14 15:10, Greg Oster wrote: On Fri, 19 Dec 2014 15:03:48 + Dave Tyson dty...@anduin.org.uk wrote: On 12/19/14 00:49, Greg Troxel wrote: Does dmesg show any disk errors? Can you dd from the disk to /dev/null without errors? No disk errors reported. I started a dd of /dev

Peculier raidframe problems

I'll got a HP server running NetBSD 6.99.40 (amd64) with 2 pairs of disks each configured as raid 1 mirrors. The first pair of disks has three raid partitions arranged as mirrors on wd0 and wd1. disklabel (wd0, wd1): 6 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a:

drmkms solid hang on T200 laptop booting GENERIC amd64

I have been testing current on a Lenovo T200 (type 2504) on and off for a while. I think the last successful boot of current was GENERIC from 29th October before the KMS code was add the the GENERIC config. IIRC the DRMKMS kernel from that base would hang. With GENERIC (AMD64) CVS'ed and

NetBSD current [AMD64] on a T400 laptop

Installed a 30th July snapshot of Current [AMD64] on a Lenovo T400. All went OK till I ran: X -configure which resulted in an immediate panic. CVSing up to todays sources and building/loading a new kernel gave exactly the same panic. Crash dmesg from 30th July version follows, the drm_addmap

dhcpcd, IPv6 DAD

I seem to be having a bit of bother getting a T60 laptop to get an IPv6 address correctly using dhcpcd. The basic setup I have is an ADSL router hardwired to a server (current-ish NetBSD amd64) which gets an ipv6 feed via a HE tunnel. The router hands out IPv4 addresses and the server uses

Re: dovecot2 broken on 6.99.40

On 04/15/14 16:43, Jean-Yves Moulin wrote: Hi, Sorry if this is not the right list. I prefer to post here before posting to dovecot mailing list. So, on a 6.99.40 from yesterday (and also with a 6.99.35), dovecot2 fails with: Apr 15 14:42:16 mailsrv dovecot: auth: Error: BUG:

consistent crashes in 6.99.40 - nfsio code?

I seem to be experiencing some repeatable crashes with 6.99.40 from a few days ago. This is a desktop amd64 system which talks to an HP microserver to get home filestore over NFS. The desktop had been pretty stable on 6.99.40 when the NFS server was running 6.99.23, but I upgraded the server

Re: ntpq peculiarity

On 04/02/14 08:59, Frank Kardel wrote: Hello Dave ! I tripped yesterday over a merge mishap concerning libntp/atouint.c and fixed that. It could be that this is related to what you see. Can you checkout/recompile libntp/ and recompile ntpq? Best regards, Frank Hi Frank, I've checked

ntpq peculiarity

I've noticed that the recent version of ntpq always reports peers as being stratum 0 regardless of what they really are: root(cruncher)root$ ntpq ntpq host 192.168.0.200 current host set to 192.168.0.200 ntpq pe remote refid st t when poll reach delay offset jitter

Re: Netbsd always uses wd0 has root booting from Install USB!?

weired stuff i cant use jê keyboard when I get to the root de vice part... its a ps/2 keyboard not USB... does this make any sense? the keyboard works fine in the boot part then it blinks num/capa/scrool lock and stops working :s I had exactly this problem trying to recover a HP system

Problems with hplip package under NetBSD (current 6.1)

I've been playing with the hplip package (pkgsrc-current) and found that both the hp-setup and hp-probe commands fail when trying to scan the network for printers. The problem appears to be related to setting up multicast and although I have found a workaround I have copied tech-kern for comments.

amd64 server upgrade failed - help

I have an HP proliant server (amd64) running current from about March 2013. It has all its filesystems on raid 1 sets and as well as being a fileserver also acts as a DNS server/mailserver for a few domains. I decided to do an update to fix the existing bind security problem. CVS'ed up to