Re: Raspberri PI 2

[Yves Bovard]

Hello Andy

Yes I tried but the error remains. Another info, /usr/pkgsrc is a NFS mount
(rw).

Yves

2015-09-19 2:49 GMT+02:00 Andy Ruhl :

>
> On Sep 18, 2015 3:01 PM, "Yves Bovard"  wrote:
> >
> > Hello everybody!
> >
> > I have trouble in using pkgsrc on a Raspberri Pi 2 with Netbsd 7.0 RC2.
> When I want to compile pytho34, I have the following error:
> > => Bootstrap dependency digest>=20010302: NOT found
> > => Verifying reinstall for ../../pkgtools/digest
> > ===> Checking for vulnerabilities in digest-20121220
> > ===> Installing dependencies for digest-20121220
> > ===> Overriding tools for digest-20121220
> > ===> Extracting for digest-20121220
> > ===> Patching for digest-20121220
> > ===> Creating toolchain wrappers for digest-20121220
> > ===> Configuring for digest-20121220
> > => 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
> > configure: error: cannot find sources (digest.c) in . or ..
> > *** Error code 1
> >
> > Stop.
> > make[2]: stopped in /usr/pkgsrc/pkgtools/digest
> > *** Error code 1
> >
> > Stop.
> > make[1]: stopped in /usr/pkgsrc/pkgtools/digest
> > *** Error code 1
> >
> > Stop.
> > make: stopped in /usr/pkgsrc/lang/python34
> >
> > I just finished the installation, ran
> >
> > cvs -q -z2 -d anon...@anoncvs.netbsd.org:/cvsroot checkout -P pkgsrc
> >
> >
> >
> > And right after I tried to install python34 which ended with the
> previous error
> >
> > What am I missing?
> >
> > Yves Bovard
>
> Well, you're synching current so there could be issues. Did you try a
> stable branch?
>
> Andy
>

Re: Raspberri PI 2

[Andy Ruhl]

On Sep 18, 2015 3:01 PM, "Yves Bovard"  wrote:
>
> Hello everybody!
>
> I have trouble in using pkgsrc on a Raspberri Pi 2 with Netbsd 7.0 RC2.
When I want to compile pytho34, I have the following error:
> => Bootstrap dependency digest>=20010302: NOT found
> => Verifying reinstall for ../../pkgtools/digest
> ===> Checking for vulnerabilities in digest-20121220
> ===> Installing dependencies for digest-20121220
> ===> Overriding tools for digest-20121220
> ===> Extracting for digest-20121220
> ===> Patching for digest-20121220
> ===> Creating toolchain wrappers for digest-20121220
> ===> Configuring for digest-20121220
> => 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
> configure: error: cannot find sources (digest.c) in . or ..
> *** Error code 1
>
> Stop.
> make[2]: stopped in /usr/pkgsrc/pkgtools/digest
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/pkgsrc/pkgtools/digest
> *** Error code 1
>
> Stop.
> make: stopped in /usr/pkgsrc/lang/python34
>
> I just finished the installation, ran
>
> cvs -q -z2 -d anon...@anoncvs.netbsd.org:/cvsroot checkout -P pkgsrc
>
>
>
> And right after I tried to install python34 which ended with the previous
error
>
> What am I missing?
>
> Yves Bovard

Well, you're synching current so there could be issues. Did you try a
stable branch?

Andy

Re: Why doesn't NetBSD recognize my entries in /etc/hosts?

[Johnny Billquist]

On 2015-09-19 00:48, Eric Haszlakiewicz wrote:

On September 18, 2015 5:22:43 PM EDT, Johnny Billquist  
wrote:

Hum. That's what *text* mode in ftp is there for... :-)
The various conventions on how text files indicate newlines in
different
operating systems should not carry across. Someone running ftp in
binary
mode when they shouldn't? :-)


Which, afaik, doesn't apply to things fetched over http.  Don't get stuck on the fact 
that the tool mentioned happens to be called "ftp", which historically had 
features that are questionable for current usages.


http is a different protocol, right. Questionable features? Well, 
obviously transferring text as text, without the idiosyncrasies of 
individual OSes carrying over is, in my mind, not a questionable 
feature, but a really good one.


http actually tries to also solve this problem, but with the content 
metadata. But http is a poor protocol, where lots of things can, and do 
go wrong.



While perhaps convenient occasionally, in my experience having a file transfer tool 
"adjust" your file, especially by default and silently, has led to more 
problems than it solves.


Problem is that people seems to never have understood when to transfer 
files in binary, and when in text mode. And it has carried over to all 
kind of things.
Now, the solution to people not understanding the problem, or the tools, 
is not to try and ignore the problem.


But that is just my opinion. :-)

Johnny

Massive interrupt storm when DPMS active

[Mike Pumford]

Running NetBSD-7.0-RC3 from a few days ago I've noticed that I get an 
interrupt storm but only when running X and DPMS has powered off the screen.


When the screen is blank the interupt rate on pin16 is around 36000 per 
seconds as shown on this systat vmstat snapshot:


36374 ioapic0 pin 16


When the screen is active:

2 ioapic0 pin 16

This is an amd64 system:

cpu0 at mainbus0 apid 0: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, id 
0x306c3


i915drmkms0 at pci0 dev 2 function 0: vendor 0x8086 product 0x0412 (rev. 
0x06)

drm: Memory usable by graphics device = 2048M
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
i915drmkms0: interrupting at ioapic0 pin 16 (i915)
intelfb0 at i915drmkms0
i915drmkms0: info: registered panic notifier
i915drmkms0: More than 8 outputs detected via ACPI
intelfb0: framebuffer at 0x80011c71a000, size 1920x1080, depth 32, 
stride 7680


XOrg reports the display as:

[94.305] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD 
Graphics 4600
[94.305] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, 
sse4.2, avx, avx2
[94.305] (II) intel(0): Creating default Display subsection in 
Screen section


I also seem to be getting a stream of these messages to the dmesg buffer:

DRM error in intel_uncore_check_errors: Unclaimed register before interrupt
DRM error in intel_uncore_check_errors: Unclaimed register before interrupt
DRM error in intel_uncore_check_errors: Unclaimed register before interrupt

These also stop when the DPMS is deactivated.

Any suggestions on how to fix this or any additional information I can 
provide to help fix this is appreciated.


Mike