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
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
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
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
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:
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
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
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
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
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
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
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
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
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
>
>
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
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
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
> >
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:
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
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
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
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
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
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.
>
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
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
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
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
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
> >
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
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
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
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
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
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
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
> >[
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
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
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.
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
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
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
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
43 matches
Mail list logo
