Re: pcengines apu boards

[Douglas Ray]

On 1/12/17 11:48 AM, Paul B. Henson wrote:

From: Eike Lantzsch
Sent: Thursday, November 30, 2017 3:12 PM

here: APU2C4 with one SATA drive of 6TB and one 4TB via USB3 and an

Hmm, I didn't think the apu2 had USB3, but double checking the specs I see
it does. My friend that said he had an APU2 must actually have an original
APU, as his board doesn't have USB3. Yeah, the external xHCI USB3 ports work
fine on my APU3, it's the EHCI ones that are screwed up, they are only
available via two internal headers or if you use the Mini PCI slot. There
probably aren't very many people that are routing the internal USB headers
to external connectors, so unless somebody is using a USB Mini PCI expansion
card on an APU2/3, they probably aren't using the EHCI controller.

Thanks for the info.



On the APU3a4 the internal USB headers were broken.
I had email from pcengines (March 2017) saying this would
be addressed in the APU3b series., but we went for APU2.

Have you asked pcengines if your internal USB
headers are fully functional?


Douglas Ray

Separators [Was: lighter sleep]

[Douglas Ray]

North American? ...

On 22/09/15 12:45 AM, Mark Kettenis wrote:

From: Christian Weisgerber 
Date: Mon, 21 Sep 2015 14:29:03 + (UTC)

On 2015-09-21, Stefan Sperling  wrote:


The function that parses funny numbers is iswdigit() which gets a wchar_t.
But sleep(1) doesn't need that.


The sole somewhat realistic use of i18n in sleep(1) is the decimal
separator, so you could do

$ sleep 1,5

in an appropriate locale.  Of course the current code doesn't support
that.


And fortunately POSIX agrees with our implementation:

   The following operand shall be supported:

   time
 A non-negative decimal integer specifying the number of
 seconds for which to suspend execution.

You could argue that the thousands separator should be supported though:

   $ sleep 1.000.000

if your locale is something vaguely european, and

   # sleep 1,000,000

for the north-americans.


I grew up with "," separators as British Commonwealth, not
North American.  The Commonwealth does extend beyond Canada;
the British Empire precedes the USA; so you might just call
"," (as 10^3 separators) British, Commonwealth or non-Euro.

Douglas (Australia)


But let's not go there...

Re: preserving editor files

[Douglas Ray]

I also have the symptom reported by Jean-Frangois SIMON (misc, 177504, 8 
Sept 2010):


Peter N. M. Hansteen peter at bsdly.net writes:


 Jean-Frangois SIMON jfsimon1981 at gmail.com writes:

  At start-up the OS stays several minutes on preserving editor files.
 
  Could you please inform me what to do about this  what is the 
system

  then doing ? Is it normal ?

 It's recovering vi's temporary files (from /var/tmp somewhere if
 memory serves), and it's a part of the normal startup sequence:

 peter at deeperthought:~$ sudo grep preserving /etc/*
 /etc/rc:echo 'preserving editor files.';
/usr/libexec/vi.recover
 /etc/termcap:# eyeball, the translation was correct and perfectly 
information-preserving.

 peter at deeperthought:~$ file /usr/libexec/vi.recover
 /usr/libexec/vi.recover: a /usr/bin/perl -w script text executable

 Several minutes sounds like a lot, was the last shutdown not a clean one?

 - P


It is near 10 minutes pause in boot-up if the script has *anything*
to process in /var/tmp/vi.recover/ - more than 5, closer to 10.

The next thing in /etc/rc is the network daemon startup, and those diags 
don't
appear on console or in /var/log/ until after /usr/libexec/vi.recover 
has waited

out whatever it is waiting for.

I'm running OpenBSD 5.0 (the amd release).  Jean-Frangois wasn't.

I see the script uses sendmail.   I haven't configured that yet.

ta
Douglas

Re: Any NC107i/broadcom ether follow-up?

[Douglas Ray]

Brian, I was greatly relieved that you showed it can work.

My problem was late night brain-fade.   I'd disabled the interface in BIOS.

(I can't see why HP call it NC107i.
You can see the broadcom chip on the motherboard.)

cheers,
Douglas

Any NC107i/broadcom ether follow-up?

[Douglas Ray]

Any word  on support for the HP ethernet NC107i controllers?

I see queries about it have come to this list several times over the past couple 
of years.


The HP ProLiant servers describe their ethernet as NC107i.
Debian and FreeBSD have this implemented as a broadcom BCM5723.

I've just tried OpenBSD 5.0 on an HP ProLiant N40L (cpu upgrade of N36L) 
microserver.

No luck in generic i386 or amd64.

thanks,
Douglas

Re: man page sources?

[Douglas Ray]

Ingo and Jason, thanks...


On 23/10/2011 11:14 PM, Ingo Schwarze wrote:

Hi Douglas,

Jason McIntyre wrote on Sat, Oct 22, 2011 at 03:27:11PM +0100:

On Sun, Oct 23, 2011 at 01:01:41AM +1100, Douglas Ray wrote:

OpenBSD 4.9 has /usr/share/man/cat* populated, but not
/usr/share/man/man[0-9n] .

What options are there to populate man[0-9n]/ ?
A complete build of kernel and userland seems extreme.


That wouldn't even help you: The 4.9 build system does not
install source manuals.


I am particularly grateful for this warning.
I had not yet started the builds, and my CPUs are not new-ish.

I am also delighted to hear that 5.0 will resume BSD custom.


You need *not* worry about the preformatted versions
becoming outdated:  The man(1) utility automatically shows the
newer one if both a source and preformatted version of the same
manual are installed.

(... and has done so since BSD 4.3, I believe [URM 1986];
at least, not documented in 4.2 [URM 1984])

now: populating man/man[]
I see the task is tedious and repetitive:  ie, scriptable.

(ta, Ingo, for thinking to include the inverse script)

If I get anywhere useful, might there be any interest in
posting a manman49.tgz on ftp.openbsd.org? ... a small
addendum, for those of us bitten by OpenBSD 4.9's little
excursion from BSD habit?

Thanks again,
Douglas Ray

man page sources?

[Douglas Ray]

OpenBSD 4.9 has /usr/share/man/cat* populated, but not
/usr/share/man/man[0-9n] .

What options are there to populate man[0-9n]/ ?
A complete build of kernel and userland seems extreme.

The man49.tgz set contains only the cat* content.
(Was that intended?)

The src49.tgz set has a small subset in it's src/share/man
subdirs.

thanks,
Douglas Ray

where's the dmesg archive?

[Douglas Ray]

Those dmesg(8)s everyone posts to dm...@openbsd.org - where are they archived?

thanks,
Douglas

Re: where's the dmesg archive?

[Douglas Ray]

On 9/09/2011 9:58 PM, Fred Crowson wrote:

On 9 September 2011 12:21, Douglas Raydoug...@cpan.org  wrote:

Those dmesg(8)s everyone posts to dm...@openbsd.org - where are they
archived?

thanks,
Douglas


Some people have put dmesgs online at:

http://www.nycbug.org/index.php?NAV=dmesgd;SQLIMIT=20

superb!
Thanks Otto and Fred.

hth

Fred

__ Information from ESET NOD32 Antivirus, version of virus signature 
database 6449 (20110909) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com