Re: Need help to install OpenBSD 5.9 macppc via pxe

2016-04-07 Thread Fred

On 04/07/16 13:09, Solène Rapenne wrote:

Hello,

I am trying to install OpenBSD 5.9 on an old mac mini (which actually
runs FreeBSD and was using OpenBSD before). So, I choosed the network
way for installation and followed the installation instructions. I get
an error when loading /bsd.rd (picture at the end)

I have my dhcp/tftp/nfs server with address 192.168.1.5 (running
freebsd), files for 5.9 are under /usr/local/www/thttpd/

-rw-r--r--  1 root  wheel  1552 Feb 26 14:59 SHA256
-rw-r--r--  1 root  wheel  1715 Feb 26 14:59 SHA256.sig
-rw-r--r--  1 root  wheel  53657599 Feb 26 11:52 base59.tgz
-rw-r--r--  1 root  wheel184634 Feb 26 11:17 boot.mac
-rw-r--r--  1 root  wheel   7787638 Apr  7 12:48 bsd
-rw-r--r--  1 root  wheel   7807488 Apr  7 12:49 bsd.mp
-rw-r--r--  1 root  wheel   8549933 Apr  7 11:28 bsd.rd
-rw-r--r--  1 root  wheel  6917 Feb 26 11:17 bsd.tbxi
-rw-r--r--  1 root  wheel  54197476 Feb 26 11:53 comp59.tgz
-rw-r--r--  1 root  wheel   2812954 Feb 26 11:53 game59.tgz
-rw-r--r--  1 root  wheel   8991150 Feb 26 11:53 man59.tgz
-rw-r--r--  1 root  wheel 64800 Feb 26 11:17 ofwboot
-rw-r--r--  1 root  wheel  23869487 Feb 26 14:53 xbase59.tgz
-rw-r--r--  1 root  wheel  40014023 Feb 26 14:53 xfont59.tgz
-rw-r--r--  1 root  wheel  17159113 Feb 26 14:54 xserv59.tgz
-rw-r--r--  1 root  wheel   4528018 Feb 26 14:54 xshare59.tgz

my /etc/exports :
/usr/local/www/thttpd/ -alldirs -ro -mapall=nobody -network 192.168.1.0/24


my dhcpd.conf (isc-dhcpd) :

allow booting;
allow bootp;
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.20 192.168.1.50;
  option broadcast-address 192.168.1.255;
}

host macmini {
  next-server 192.168.1.5;
  option subnet-mask 255.255.255.0;
  option routers 192.168.1.5;
  option root-path "192.168.1.5:/usr/local/www/thttpd";
  fixed-address 192.168.1.22;
  hardware ethernet 00:14:51:1f:52:70;
}



I can mount the nfs from the freebsd of the mac mini and get files, so
the NFS is fine. The PXE is fine as it load ofwboot. The DHCP is fine
too as it get an IP.

But it can't find /bsd.rd which is at the root of the nfs export. What
is wrong with my setup ?

Picture of the boot in the open firmware
http://i.zcraft.fr/960991460029255.jpg

Kind regards



Try tcpdumping the connection and see why it thinks the file doesn't exist.

It might be the / try does:
 boot enet:, ofwboot bsd.rd
change the behaviour?

hth

Fred



Re: PKG_PATH - SOLVED

2016-04-07 Thread Teno Deuter
yes indeed.

Thank you

On Fri, Apr 8, 2016 at 12:03 AM, Antoine Jacoutot  wrote:
> On Thu, Apr 07, 2016 at 11:49:11PM +0200, Teno Deuter wrote:
>> I run 'pkg_add' with 'doas' and I get only:
>>
>> Can't find [the package] I try to install. Doesn't say anything about
>> 'root'.
>>
>> Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version
>> this wasn't the case. Is that due to 'doas'?
>
> doas resets the environment.
> If you want to keep PKG_PATH then use something like this in doas.conf:
> permit keepenv { PKG_PATH } nopass :wheel
>
>
> --
> Antoine



Re: PKG_PATH

2016-04-07 Thread Antoine Jacoutot
On Thu, Apr 07, 2016 at 11:49:11PM +0200, Teno Deuter wrote:
> I run 'pkg_add' with 'doas' and I get only:
> 
> Can't find [the package] I try to install. Doesn't say anything about
> 'root'.
> 
> Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version
> this wasn't the case. Is that due to 'doas'?

doas resets the environment.
If you want to keep PKG_PATH then use something like this in doas.conf:
permit keepenv { PKG_PATH } nopass :wheel


-- 
Antoine



Re: PKG_PATH

2016-04-07 Thread Teno Deuter
I run 'pkg_add' with 'doas' and I get only:

Can't find [the package] I try to install. Doesn't say anything about
'root'.

Also, why 'pkg_add' has to be run as root only? In previous OpenBSD version
this wasn't the case. Is that due to 'doas'?

Thank you


On Thu, Apr 7, 2016 at 11:17 PM, Mihai Popescu  wrote:

> > just installed a 5.9 AMD64 version and get issues with adding packages
> as a
> > regular system user. 'env' shows me the correct setting for PKG_PATH but
> > seems that the user environment isn't able to contact the source.
>
> "Get issues" is not a valid problem report. I am getting issues with
> my stomach right now, but this will never tell you what is my problem.
> Post the exact message(s) you get.
>
> You should get something like this:
>
> $ pkg_add -vn test
> pkg_add should be run as root
> Can't find test
>
> This is telling you what to do in order to fix that "issue".
>
> > As long as I change to 'root', everything works fine!
>
> Isn't it obvious?
>
> It may sound crazy, but OpenBSD does not allow any user to install
> packages directly, much like Linux or Windows.



Re: PKG_PATH

2016-04-07 Thread Pedro Tender
And how are you installing packages as a non root user?
On Apr 7, 2016 22:08, "Teno Deuter"  wrote:

> Hi,
>
> just installed a 5.9 AMD64 version and get issues with adding packages as a
> regular system user. 'env' shows me the correct setting for PKG_PATH but
> seems that the user environment isn't able to contact the source.
>
> As long as I change to 'root', everything works fine!
>
> Thank you for your support



Re: PKG_PATH

2016-04-07 Thread Mihai Popescu
> just installed a 5.9 AMD64 version and get issues with adding packages as a
> regular system user. 'env' shows me the correct setting for PKG_PATH but
> seems that the user environment isn't able to contact the source.

"Get issues" is not a valid problem report. I am getting issues with
my stomach right now, but this will never tell you what is my problem.
Post the exact message(s) you get.

You should get something like this:

$ pkg_add -vn test
pkg_add should be run as root
Can't find test

This is telling you what to do in order to fix that "issue".

> As long as I change to 'root', everything works fine!

Isn't it obvious?

It may sound crazy, but OpenBSD does not allow any user to install
packages directly, much like Linux or Windows.



pureftpd virtual users TLS

2016-04-07 Thread Teno Deuter
Hi,

installed the chrooted version of pureftpd on a 5.9 AMD64 setting and face
following issues:

1.
TLS with system users works fine but not for the virtual ones! Only plain
ftp!

2.
seems that the service doesn't always refer to the 'pure-ftpd.conf'! To be
more specific.I did define the path of 'pureftpd.pdb' in the configuration
file but if I don't use the '-lpuredb' switch in the daemon flags doesn't
find it. Also, uncommenting :

AltLog w3c:/var/log/pureftpd.log

doesn't have any effect either. That file never gets created!

Thank you for your support.



PKG_PATH

2016-04-07 Thread Teno Deuter
Hi,

just installed a 5.9 AMD64 version and get issues with adding packages as a
regular system user. 'env' shows me the correct setting for PKG_PATH but
seems that the user environment isn't able to contact the source.

As long as I change to 'root', everything works fine!

Thank you for your support



Re: man pages diff

2016-04-07 Thread Jason McIntyre
On Thu, Apr 07, 2016 at 10:13:02PM +0200, Ingo Schwarze wrote:
> Hi,
> 
> Jason McIntyre wrote on Thu, Apr 07, 2016 at 08:35:52PM +0100:
> > On Thu, Apr 07, 2016 at 03:15:01PM -0400, Rob Pierce wrote:
> 
> >> Change "super user" to "superuser".
> 
> > hmm. you have the weight of the man pages behind you, since they
> > overwhelmingly use "superuser".
> 
> In that case, ...
> 
> > the trouble is, i don;t think "super
> > user" is wrong, and i'm reluctant to do this...
> > 
> > i've made changes like this before, when we have a real majority of
> > spelling leading one way. but they always creep back in. i think we
> > should just accept that we can spell things more than one way sometimes.
> > 
> > but then grep ;(
> > 
> > jmc, indecisive...
> 
>  ... just commit it, in particular when the work was already done.
> 
> Sure, it's not a big deal either way, and it doesn't do much harm
> if a few spelling variants creep back in, no need to waste a lot
> of time paying attention that they don't, but if we can improve
> consistency almost for free, why not?
> 
> It can also help developers who look for spelling help in existing
> pages if they find consistent usage.  That tends to reduce the time
> spent trying to figure out whether there is a preferred form.  On
> the other hand, consistency doesn't slow down people who don't care
> as long as we don't yell at them.
> 
> Yours,
>   Ingo
> 

hi.

as far as i'm concerned, "super user" is not wrong. that's the rub. we
have lots of alternate spellings in english, and i don;t see the point
of trying to enforce one or the other. if they were spelled differently
within the same page, then yes, fair enough.

for me, there's not a clear enough benefit to make the change. and i
don;t like to somehow enforce spelling in a particular way.

jmc

> 
> > > Index: src/share/man/man4/pty.4
> > > ===
> > > RCS file: /cvs/src/share/man/man4/pty.4,v
> > > retrieving revision 1.21
> > > diff -u -p -r1.21 pty.4
> > > --- src/share/man/man4/pty.4  21 Nov 2015 08:04:20 -  1.21
> > > +++ src/share/man/man4/pty.4  7 Apr 2016 19:12:07 -
> > > @@ -298,7 +298,7 @@ device nodes following the naming conven
> > >  .Ox .
> > >  Since
> > >  .Pa ptm
> > > -impersonates the super user for some operations it needs to perform
> > > +impersonates the superuser for some operations it needs to perform
> > >  to complete the allocation of a pseudo terminal, the
> > >  .Pa /dev
> > > -directory must also be writeable by the super user.
> > > +directory must also be writeable by the superuser.
> > > 
> > > Index: src/share/man/man5/login.conf.5
> > > ===
> > > RCS file: /cvs/src/share/man/man5/login.conf.5,v
> > > retrieving revision 1.62
> > > diff -u -p -r1.62 login.conf.5
> > > --- src/share/man/man5/login.conf.5   30 Mar 2016 06:58:06 -  
> > > 1.62
> > > +++ src/share/man/man5/login.conf.5   7 Apr 2016 19:12:07 -
> > > @@ -683,7 +683,7 @@ to indicate if the user is in group whee
> > >  Some authentication types require the user to be in group wheel when 
> > > using
> > >  the
> > >  .Xr su 1
> > > -program to become super user.
> > > +program to become superuser.
> > >  .El
> > >  .Pp
> > >  When the authentication program is executed,
> > > 
> > > Index: src/usr.sbin/cron/crontab.1
> > > ===
> > > RCS file: /cvs/src/usr.sbin/cron/crontab.1,v
> > > retrieving revision 1.33
> > > diff -u -p -r1.33 crontab.1
> > > --- src/usr.sbin/cron/crontab.1   26 Oct 2015 15:50:06 -  1.33
> > > +++ src/usr.sbin/cron/crontab.1   7 Apr 2016 19:12:07 -
> > > @@ -65,7 +65,7 @@ be listed in the
> > >  .Pa /var/cron/cron.deny
> > >  file in order to use
> > >  .Nm .
> > > -If neither of these files exists then only the super user
> > > +If neither of these files exists then only the superuser
> > >  will be allowed to use
> > >  .Nm .
> > >  .Em NOTE :



Re: xbacklight / screen brightness

2016-04-07 Thread Mark Kettenis
> There are a few instances of this bug. You can also see it with cpu
> frequency and audio volume.
> 
> Most drivers maintain soft state that should mirror the hardware
> state. Except when it doesn't. Sometimes the driver has a bug,
> sometimes the hardware lies, sometimes something else goes
> wrong. The many layers of abstraction and acpi don't help either.

There are defenitely machines out there where the acpi implementation
sufferes from exactly this problem.  The AML method that reports back
the current brightness level doesn't actually query the hardware, but
simply reports back the soft state.  And that soft state isn't
properly initialized!  It wouldn't surprise me if Windows never
actually calls that method, or at least always explicitly sets the
level it wants withour querying the hardware.

> It's a bug and it's worth reporting as much info about your hardware as
> possible, but don't expect a quick fix. As a workaround, just run 'xbacklight
> 50 ; xbacklight 100' or whatever you want.

Or better, add lines like:

display.brightness=50
display.brightness=100

to /etc/wsconsctl.conf.

To be able to fix problems like this we need dmesg and acpidump
output.  If you use sendbug(1) to file a bug report, that information
is automatically included if you run it as root.  As a bonus, the mail
gets sent to an address that developers actually read...



Re: v5.9 fails to boot Wyse Thin client (AMD G-T48E)

2016-04-07 Thread Mark Kettenis
> Hello everybody,
> 
> I tried to install OpenBSD v5.9 but as soon as kernel loads
> the screen goes black. Cannot enter into UKC> either.
> hd0a:5.9/amd64/bsd.mp dropped into debugger with some radeon errors.

Without those error messages there is not much we can do for you.



Re: man pages diff

2016-04-07 Thread Ingo Schwarze
Hi,

Jason McIntyre wrote on Thu, Apr 07, 2016 at 08:35:52PM +0100:
> On Thu, Apr 07, 2016 at 03:15:01PM -0400, Rob Pierce wrote:

>> Change "super user" to "superuser".

> hmm. you have the weight of the man pages behind you, since they
> overwhelmingly use "superuser".

In that case, ...

> the trouble is, i don;t think "super
> user" is wrong, and i'm reluctant to do this...
> 
> i've made changes like this before, when we have a real majority of
> spelling leading one way. but they always creep back in. i think we
> should just accept that we can spell things more than one way sometimes.
> 
> but then grep ;(
> 
> jmc, indecisive...

 ... just commit it, in particular when the work was already done.

Sure, it's not a big deal either way, and it doesn't do much harm
if a few spelling variants creep back in, no need to waste a lot
of time paying attention that they don't, but if we can improve
consistency almost for free, why not?

It can also help developers who look for spelling help in existing
pages if they find consistent usage.  That tends to reduce the time
spent trying to figure out whether there is a preferred form.  On
the other hand, consistency doesn't slow down people who don't care
as long as we don't yell at them.

Yours,
  Ingo


> > Index: src/share/man/man4/pty.4
> > ===
> > RCS file: /cvs/src/share/man/man4/pty.4,v
> > retrieving revision 1.21
> > diff -u -p -r1.21 pty.4
> > --- src/share/man/man4/pty.421 Nov 2015 08:04:20 -  1.21
> > +++ src/share/man/man4/pty.47 Apr 2016 19:12:07 -
> > @@ -298,7 +298,7 @@ device nodes following the naming conven
> >  .Ox .
> >  Since
> >  .Pa ptm
> > -impersonates the super user for some operations it needs to perform
> > +impersonates the superuser for some operations it needs to perform
> >  to complete the allocation of a pseudo terminal, the
> >  .Pa /dev
> > -directory must also be writeable by the super user.
> > +directory must also be writeable by the superuser.
> > 
> > Index: src/share/man/man5/login.conf.5
> > ===
> > RCS file: /cvs/src/share/man/man5/login.conf.5,v
> > retrieving revision 1.62
> > diff -u -p -r1.62 login.conf.5
> > --- src/share/man/man5/login.conf.5 30 Mar 2016 06:58:06 -  1.62
> > +++ src/share/man/man5/login.conf.5 7 Apr 2016 19:12:07 -
> > @@ -683,7 +683,7 @@ to indicate if the user is in group whee
> >  Some authentication types require the user to be in group wheel when using
> >  the
> >  .Xr su 1
> > -program to become super user.
> > +program to become superuser.
> >  .El
> >  .Pp
> >  When the authentication program is executed,
> > 
> > Index: src/usr.sbin/cron/crontab.1
> > ===
> > RCS file: /cvs/src/usr.sbin/cron/crontab.1,v
> > retrieving revision 1.33
> > diff -u -p -r1.33 crontab.1
> > --- src/usr.sbin/cron/crontab.1 26 Oct 2015 15:50:06 -  1.33
> > +++ src/usr.sbin/cron/crontab.1 7 Apr 2016 19:12:07 -
> > @@ -65,7 +65,7 @@ be listed in the
> >  .Pa /var/cron/cron.deny
> >  file in order to use
> >  .Nm .
> > -If neither of these files exists then only the super user
> > +If neither of these files exists then only the superuser
> >  will be allowed to use
> >  .Nm .
> >  .Em NOTE :



add "route" promise to pledge.2

2016-04-07 Thread Rob Pierce
I wasn't sure of where to put it in the list.

How is this?

Rob

Index: pledge.2
===
RCS file: /cvs/src/lib/libc/sys/pledge.2,v
retrieving revision 1.27
diff -u -p -r1.27 pledge.2
--- pledge.211 Mar 2016 06:36:51 -  1.27
+++ pledge.27 Apr 2016 20:00:19 -
@@ -80,7 +80,8 @@ Only the
 and
 .Dv FIONBIO
 operations are allowed by default.
-Use of the "tty" and "ioctl" promises receive more ioctl requests.
+Use of the "tty", "ioctl", "route", "pf" and "audio" promises receive more 
ioctl
+requests.
 .Pp
 .It Xr chmod 2
 .It Xr fchmod 2
@@ -493,6 +494,21 @@ process:
 .Xr setrlimit 2 ,
 .Xr getpriority 2 ,
 .Xr setpriority 2 .
+.It Va "route"
+Allows a subset of
+.Xr ioctl 2
+operations on network interfaces:
+.Pp
+.Dv SIOCGIFADDR ,
+.Dv SIOCGIFFLAGS ,
+.Dv SIOCGIFMETRIC ,
+.Dv SIOCGIFGMEMB ,
+.Dv SIOCGIFRDOMAIN ,
+.Dv SIOCGIFDSTADDR_IN6 ,
+.Dv SIOCGIFNETMASK_IN6 ,
+.Dv SIOCGNBRINFO_IN6 ,
+.Dv SIOCGIFINFO_IN6 ,
+.Dv SIOCGIFMEDIA .
 .It Va "pf"
 Allows a subset of
 .Xr ioctl 2



USB problem

2016-04-07 Thread Liviu Daia
I have an APU1.C router monitoring an UPS through an USB cable.
Today I upgraded the UPS to a different model, and the router can't see
it:

uhub3: port 5, set config 0 at addr 2 failed
uhub3: device problem, disabling port 5

(full dmesg below).

The USB port on the router and the cable are fine, since they worked
with the old UPS.  The USB port on the new UPS seems fine too, since I
can see it on a Linux machine:

$ lsusb -s 1:9 -v
Bus 001 Device 009: ID 10af:0001 Liebert Corp. PowerSure PSA UPS
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x10af Liebert Corp.
  idProduct  0x0001 PowerSure PSA UPS
  bcdDevice0.14
  iManufacturer  19 
  iProduct1 
  iSerial 2 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   34
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID  10.01
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength 511
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval 232

Any idea?

Regards,

Liviu Daia


OpenBSD 5.9-current (GENERIC.MP) #1981: Thu Mar 31 14:51:55 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2098520064 (2001MB)
avail mem = 2030616576 (1936MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e16d820 (7 entries)
bios0: vendor coreboot version "4.0" date 09/08/2014
bios0: PC Engines APU
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT
acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) 
PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) 
UOH4(S3) UOH5(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD G-T40E Processor, 1000.12 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD G-T40E Processor, 1000.00 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu1: 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
acpiprt0 at acpi0: bus -1 (AGPB)
acpiprt1 at acpi0: bus -1 (HDMI)
acpiprt2 at acpi0: bus 1 (PBR4)
acpiprt3 at acpi0: bus 2 (PBR5)
acpiprt4 at acpi0: bus 3 (PBR6)
acpiprt5 at acpi0: bus -1 (PBR7)
acpiprt6 at acpi0: bus 5 (PE20)
acpiprt7 at acpi0: bus -1 (PE21)
acpiprt8 at acpi0: bus -1 (PE22)
acpiprt9 at acpi0: bus -1 (PE23)
acpiprt10 at acpi0: bus 0 (PCI0)
acpiprt11 at acpi0: bus 4 (PIBR)
acpicpu0 at acpi0: C2(0@100 io@0x841), C1(@1 halt!), PSS
acpicpu1 at acpi0: 

Re: man pages diff

2016-04-07 Thread Jason McIntyre
On Thu, Apr 07, 2016 at 03:15:01PM -0400, Rob Pierce wrote:
> Change "super user" to "superuser".
> 
> Rob
> 

hmm. you have the weight of the man pages behind you, since they
overwhelmingly use "superuser". the trouble is, i don;t think "super
user" is wrong, and i'm reluctant to do this...

i've made changes like this before, when we have a real majority of
spelling leading one way. but they always creep back in. i think we
should just accept that we can spell things more than one way sometimes.

but then grep ;(

jmc, indecisive...

> Index: src/share/man/man4/pty.4
> ===
> RCS file: /cvs/src/share/man/man4/pty.4,v
> retrieving revision 1.21
> diff -u -p -r1.21 pty.4
> --- src/share/man/man4/pty.4  21 Nov 2015 08:04:20 -  1.21
> +++ src/share/man/man4/pty.4  7 Apr 2016 19:12:07 -
> @@ -298,7 +298,7 @@ device nodes following the naming conven
>  .Ox .
>  Since
>  .Pa ptm
> -impersonates the super user for some operations it needs to perform
> +impersonates the superuser for some operations it needs to perform
>  to complete the allocation of a pseudo terminal, the
>  .Pa /dev
> -directory must also be writeable by the super user.
> +directory must also be writeable by the superuser.
> 
> Index: src/share/man/man5/login.conf.5
> ===
> RCS file: /cvs/src/share/man/man5/login.conf.5,v
> retrieving revision 1.62
> diff -u -p -r1.62 login.conf.5
> --- src/share/man/man5/login.conf.5   30 Mar 2016 06:58:06 -  1.62
> +++ src/share/man/man5/login.conf.5   7 Apr 2016 19:12:07 -
> @@ -683,7 +683,7 @@ to indicate if the user is in group whee
>  Some authentication types require the user to be in group wheel when using
>  the
>  .Xr su 1
> -program to become super user.
> +program to become superuser.
>  .El
>  .Pp
>  When the authentication program is executed,
> 
> Index: src/usr.sbin/cron/crontab.1
> ===
> RCS file: /cvs/src/usr.sbin/cron/crontab.1,v
> retrieving revision 1.33
> diff -u -p -r1.33 crontab.1
> --- src/usr.sbin/cron/crontab.1   26 Oct 2015 15:50:06 -  1.33
> +++ src/usr.sbin/cron/crontab.1   7 Apr 2016 19:12:07 -
> @@ -65,7 +65,7 @@ be listed in the
>  .Pa /var/cron/cron.deny
>  file in order to use
>  .Nm .
> -If neither of these files exists then only the super user
> +If neither of these files exists then only the superuser
>  will be allowed to use
>  .Nm .
>  .Em NOTE :



Re: xbacklight / screen brightness

2016-04-07 Thread Riccardo Mottola

Hi Ted,

On 04/07/16 16:22, Ted Unangst wrote:

Most drivers maintain soft state that should mirror the hardware state. Except
when it doesn't. Sometimes the driver has a bug, sometimes the hardware lies,
sometimes something else goes wrong. The many layers of abstraction and acpi
don't help either.


I supposed something like this.



It's a bug and it's worth reporting as much info about your hardware as
possible, but don't expect a quick fix. As a workaround, just run 'xbacklight
50 ; xbacklight 100' or whatever you want.


It is not "critical", just inconvenient!
I copy below my dmesg.
What other information could you need? Xorg information about the 
detected video card? In the log I see a mention about backlight:

[   136.527] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, 
Q35, Q33,

GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[   136.527] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[   136.527] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[   136.527] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 
5200, 6200, P6300

[   136.527] (II) VESA: driver for VESA chipsets: vesa
[   136.537] (II) intel(0): Using Kernel Mode Setting driver: i915, 
version 1.6.0 20080730

[   136.537] (WW) Falling back to old probe method for vesa
[   136.538] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD 
Graphics 3000
[   136.538] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, 
sse4.2, avx
[   136.538] (II) intel(0): Creating default Display subsection in 
Screen section

"Default Screen Section" for depth/fbbpp 24/32
[   136.538] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[   136.538] (==) intel(0): RGB weight 888
[   136.538] (==) intel(0): Default visual is TrueColor
[   136.543] (II) intel(0): Output LVDS1 has no monitor section
[   136.559] (--) intel(0): Found backlight control interface wscons 
(type 'platform') for output LVDS1

[   136.559] (II) intel(0): Enabled output LVDS1
[   136.559] (II) intel(0): Output VGA1 has no monitor section
[   136.559] (II) intel(0): Enabled output VGA1
[   136.559] (II) intel(0): Output HDMI1 has no monitor section
[   136.559] (II) intel(0): Enabled output HDMI1
[   136.559] (II) intel(0): Output DP1 has no monitor section
[   136.559] (II) intel(0): Enabled output DP1
[   136.559] (--) intel(0): Using a maximum size of 64x64 for hardware 
cursors

[   136.559] (II) intel(0): Output VIRTUAL1 has no monitor section
[   136.559] (II) intel(0): Enabled output VIRTUAL1
[   136.559] (--) intel(0): Output LVDS1 using initial mode 1366x768 on 
pipe 0

[   136.559] (==) intel(0): TearFree disabled
[   136.559] (==) intel(0): DPI set to (96, 96)

dmesg:
OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
9d

real mem = 4209762304 (4014MB)
avail mem = 4078280704 (3889MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xacdb6000 (25 entries)
bios0: vendor Hewlett-Packard version "68SRR Ver. F.41" date 05/22/2013
bios0: Hewlett-Packard HP ProBook 4530s
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SSDT SSDT SLIC SSDT SSDT
acpi0: wakeup devices LANC(S0) EHC1(S0) EHC2(S0) PCIB(S5) RP02(S4) 
ECF0(S4) RP03(S4) RP04(S5) WNIC(S5) RP06(S0) NIC_(S0) RP07(S4) RP08(S0) 
HST1(S5)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2494.69 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2494.34 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz, 2494.34 

man pages diff

2016-04-07 Thread Rob Pierce
Change "super user" to "superuser".

Rob

Index: src/share/man/man4/pty.4
===
RCS file: /cvs/src/share/man/man4/pty.4,v
retrieving revision 1.21
diff -u -p -r1.21 pty.4
--- src/share/man/man4/pty.421 Nov 2015 08:04:20 -  1.21
+++ src/share/man/man4/pty.47 Apr 2016 19:12:07 -
@@ -298,7 +298,7 @@ device nodes following the naming conven
 .Ox .
 Since
 .Pa ptm
-impersonates the super user for some operations it needs to perform
+impersonates the superuser for some operations it needs to perform
 to complete the allocation of a pseudo terminal, the
 .Pa /dev
-directory must also be writeable by the super user.
+directory must also be writeable by the superuser.

Index: src/share/man/man5/login.conf.5
===
RCS file: /cvs/src/share/man/man5/login.conf.5,v
retrieving revision 1.62
diff -u -p -r1.62 login.conf.5
--- src/share/man/man5/login.conf.5 30 Mar 2016 06:58:06 -  1.62
+++ src/share/man/man5/login.conf.5 7 Apr 2016 19:12:07 -
@@ -683,7 +683,7 @@ to indicate if the user is in group whee
 Some authentication types require the user to be in group wheel when using
 the
 .Xr su 1
-program to become super user.
+program to become superuser.
 .El
 .Pp
 When the authentication program is executed,

Index: src/usr.sbin/cron/crontab.1
===
RCS file: /cvs/src/usr.sbin/cron/crontab.1,v
retrieving revision 1.33
diff -u -p -r1.33 crontab.1
--- src/usr.sbin/cron/crontab.1 26 Oct 2015 15:50:06 -  1.33
+++ src/usr.sbin/cron/crontab.1 7 Apr 2016 19:12:07 -
@@ -65,7 +65,7 @@ be listed in the
 .Pa /var/cron/cron.deny
 file in order to use
 .Nm .
-If neither of these files exists then only the super user
+If neither of these files exists then only the superuser
 will be allowed to use
 .Nm .
 .Em NOTE :



v5.9 fails to boot Wyse Thin client (AMD G-T48E)

2016-04-07 Thread Pekka Niiranen

Hello everybody,

I tried to install OpenBSD v5.9 but as soon as kernel loads
the screen goes black. Cannot enter into UKC> either.
hd0a:5.9/amd64/bsd.mp dropped into debugger with some radeon errors.

Freebsd installer starts but screen is barely readable.
NetBSD installs and rund fine but one needs to unplug
and replug USB keyboard and mouse after login: prompt appears.

-pekka-
-- NetBSD dmesg log 

Last login: Thu Apr  7 01:05:58 2016 from 192.168.12.2
NetBSD 7.0 (GENERIC.201509250726Z)

Welcome to NetBSD!

pekkawyse$ dmesg
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.

NetBSD 7.0 (GENERIC.201509250726Z)
total memory = 3940 MB
avail memory = 3808 MB
kern.module.path=/stand/amd64/7.0/modules
timecounter: Timecounters tick every 10.000 msec
RTC BIOS diagnostic error 0x80
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
WYSE D CLASS (Rev 1)
mainbus0 (root)
ACPI: RSDP 0xf00e0 24 (v02 3.0E  )
ACPI: XSDT 0xa73cf120 74 (v01 3.0E   WYSEACPI 0003 PTEC 0002)
ACPI: FACP 0xa73c3000 F4 (v04 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: DSDT 0xa73c5000 00970D (v01 WYSE   WYSEACPI 1000 PTEC 0002)
ACPI: FACS 0xa735d000 40
ACPI: HPET 0xa73c2000 38 (v01 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: APIC 0xa73c1000 5E (v02 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: MCFG 0xa73c 3C (v01 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: SBST 0xa73bf000 30 (v01 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: UEFI 0xa73be000 3E (v01 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: UEFI 0xa73bd000 42 (v01 PTL  COMBUF 0001 PTL  0001)
ACPI: SSDT 0xa73bb000 00168E (v02AMD ALIB 0001 MSFT 0400)
ACPI: SSDT 0xa73ba000 000F15 (v01AMDSB800 0001 INTL 20061109)
ACPI: UEFI 0xa73b9000 000102 (v01 WYSE   WYSEACPI 0002 PTL  0002)
ACPI: All ACPI Tables successfully acquired
ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x21, 24 pins
cpu0 at mainbus0 apid 0: AMD G-T48E Processor, id 0x500f20
cpu1 at mainbus0 apid 1: AMD G-T48E Processor, id 0x500f20
acpi0 at mainbus0: Intel ACPICA 20131218
acpi0: X/RSDT: OemId <3.0E  ,WYSEACPI,0003>, AslId 
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed0-0xfed00400)
timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
MEMR (PNP0C02) at acpi0 not configured
pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
midi0 at pcppi1: PC speaker
sysbeep0 at pcppi1
attimer1 at acpi0 (TIME, PNP0100): io 0x40-0x43 irq 0
pckbc1 at acpi0 (KBC0, PNP0303) (kbd port): io 0x60,0x64 irq 1
pckbc2 at acpi0 (MSE0, PNP0F13) (aux port): irq 12
SYSR (PNP0C02) at acpi0 not configured
MEM (PNP0C01) at acpi0 not configured
acpivga0 at acpi0 (VGA): ACPI Display Adapter
acpiout0 at acpivga0 (LCD, 0x0110): ACPI Display Output Device
acpiout0: brightness levels: 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 
32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 64 66 68 70 72 74 76 78 
80 82 84 86 88 90 92 94 96 98 100

acpivga0: connected output devices:
acpivga0:   0x0100: Ext. Monitor, head 0, bios detect
acpivga0:   0x0110 (acpiout0): LCD Panel, head 0, bios detect
acpivga0:   0x0200: TV, head 0
acpivga0:   0x0210: Unknown Output Device, head 0, bios detect
acpivga0:   0x0220: Unknown Output Device, head 0, bios detect
acpiacad0 at acpi0 (ACAD, ACPI0003): ACPI AC Adapter
acpifan0 at acpi0 (Z0F0, PNP0C0B-0): ACPI Fan
acpifan1 at acpi0 (Z0F1, PNP0C0B-1): ACPI Fan
acpifan2 at acpi0 (Z0F2, PNP0C0B-2): ACPI Fan
acpifan3 at acpi0 (Z0F3, PNP0C0B-3): ACPI Fan
acpitz0 at acpi0 (THZ0): cpu0
acpitz0: active cooling level 0: 80.0C
acpitz0: active cooling level 1: 50.0C
acpitz0: active cooling level 2: 0.0C
acpitz0: active cooling level 3: 0.0C
acpitz0: levels: critical 115.0 C, passive 98.0 C
ACPI: Enabled 5 GPEs in block 00 to 1F
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] 
(20131218/hwxface-646)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] 
(20131218/hwxface-646)

attimer1: attached to pcppi1
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 0x1022 product 0x1510 (rev. 0x00)
radeon0 at pci0 dev 1 function 0: vendor 0x1002 product 0x9804 (rev. 0x00)
hdaudio0 at pci0 dev 1 function 1: HD Audio Controller
hdaudio0: interrupting at ioapic0 pin 19
hdafg0 at hdaudio0: ATI R6xx HDMI
hdafg0: HDMI00 2ch: Digital Out [Jack]
hdafg0: 2ch/0ch 32000Hz 44100Hz 48000Hz PCM16 AC3
ahcisata0 at pci0 dev 17 function 0: vendor 0x1002 product 

Re: xbacklight / screen brightness

2016-04-07 Thread Matej Nanut
Ted Unangst  wrote:
> It's a bug and it's worth reporting as much info about your hardware as
> possible, but don't expect a quick fix. As a workaround, just run
'xbacklight
> 50 ; xbacklight 100' or whatever you want.
>

Hello, I've an ASUS K53SV and the brightness also behaves oddly.

Values for "wsconsctl display.brightness" between 2 and 100 set it to
8/10. 1 sets it to 7/10 and 0 sets it to 0/10. After assignment, it
always prints "100%".

xbacklight works the same way, except that setting it to 100 doesn't
do anything at all, and -get always prints 100 (with a bunch of
decimals).

Using the keyboard keys works, and allows setting the brightness to
max. But the setting is forgotten after DPMS triggers or after
switching to a TTY. Every change with the keys or with xbacklight
takes a little moment to happen, while it is instant with wsconsctl.

I'm not sure if it's relevant, but the audio keys don't work, and
neither they nor the backlight keys show up with xev(1). I built the
kernel with ACPIASUS_DEBUG and WSKBD_DEBUG, but no messages are
printed on these events.

Also, the same problem used to be present on Linux, but got fixed at
some point since I started using OpenBSD more than a year ago, so I
have no idea which version fixed it.

I'd like to try fixing this, but I don't know which drivers/files are
responsible for these things in my case. Can you give me a hint?

Matej

$ dmesg
OpenBSD 5.9-current (compile) #0: Tue Apr  5 20:06:57 CEST 2016
matej@puffy:/home/matej/openbsd/compile
real mem = 8479825920 (8086MB)
avail mem = 8218599424 (7837MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xebc30 (100 entries)
bios0: vendor American Megatrends Inc. version "K53SV.315" date 09/26/2011
bios0: ASUSTeK Computer Inc. K53SV
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP APIC HPET ECDT MCFG SSDT SSDT SSDT
acpi0: wakeup devices P0P1(S4) EHC1(S3) USB1(S3) USB2(S3) USB3(S3)
USB4(S3) EHC2(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) PXSX(S4)
PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.34 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X
SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X
SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.01 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X
SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X
SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 0, core 3, package 0
cpu4 at mainbus0: apid 1 (application processor)
cpu4: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.01 MHz
cpu4:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,X
SAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu4: 256KB 64b/line 8-way L2 cache
cpu4: smt 1, core 0, package 0
cpu5 at mainbus0: apid 3 (application processor)
cpu5: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195.01 MHz
cpu5:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX

bsd.rd fails to boot up on libreboot x200: how to find out why?

2016-04-07 Thread silent_wanderer
I have a Thinkpad X200 laptop with libreboot 20150518 (latest stable 
release).


Libreboot is basically coreboot + grub2 without bios services and with 
no text console.


GRUB is able to load openbsd kernels from all filesystems it knows 
including FFS.


If I load 5.9/amd64/bsd or bsd.mp kernels they boot up fine to the 
console, giving this warning in early boot up:

warning: no entropy supplied by boot loader
It is not unexpected, since GRUB does not support providing entropy to 
the bsd kernel yet.


But if I try to load /bsd (is it a kernel at all? seems to be gzip 
archive with some elf) or /5.9/amd64/bsd.rd kernels, they do not boot 
up. After several seconds the machine reboots without any messages on 
the screen at all and grub menu reappears.


I have also tested i386 kernels (rd and mp). They do not make machine 
reboot but do not show anything either. Perhaps they were built without 
framebuffer support. Possibly they work under hood, but I need to make 
them use usb serial console to check it.


Since I see nothing on the screen and the laptop has no hardware com 
port, I have decided to try with USB-serial adapter. The adapter works 
with OpenBSD after full boot if I issue cd /dev ; sh MAKEDEV ttyU0, but 
I do not know how to specify it to the kernel to use for debug. GRUB 
allows to specify only com0 - com3 as serial console in the command 
line. If I specify kopenbsd -h com0 option nothing is sent to the port 
even with working kernels.


Is it possible at all to use USB serial port as console?

Do you have any idea, what is difference between bsd.rd and bsd kernels 
that the first one does not start at all on same machine?


Do I have any feasible options to get serial console to this laptop?

I think that if I unpack bsd.rd and edit /etc/ttys it might help, but I 
did not find any information about bsd.rd structure, such as supposed 
offset of embedded image, its format and so on.


elfrdsetroot(8) is mentioned in man rd, but http://man.openbsd.org does 
not have a manpage for it.




Re: xbacklight / screen brightness

2016-04-07 Thread Ted Unangst
Riccardo Mottola wrote:
> "xbacklight" tells me however "100".
> if I lower it with "-set 90" I actually notice it gets brighter, setting 
> it to "-set 100" .. it goes to full brightness.
> 
> It looks as if initially the value is read back incorrect from a status 
> register?

There are a few instances of this bug. You can also see it with cpu
frequency and audio volume.

Most drivers maintain soft state that should mirror the hardware state. Except
when it doesn't. Sometimes the driver has a bug, sometimes the hardware lies,
sometimes something else goes wrong. The many layers of abstraction and acpi
don't help either.

It's a bug and it's worth reporting as much info about your hardware as
possible, but don't expect a quick fix. As a workaround, just run 'xbacklight
50 ; xbacklight 100' or whatever you want.



[solved] sendmail mx question

2016-04-07 Thread Markus Rosjat

Hi,

the problem is solved and of course it wasn't me :)

after a few debugging sessions with christoph Viethen is it offical I 
behave like I should or at least my mx. Turns out the other side had a 
firewall that basically blocked the traffic to my server (yeah even 
whitelisting me in the begining didnt help).


Fun part, the admin on the other end admited that he wasnt able to send 
mails to my mx ...


thank god for enterpise solution like watchguard ... they keep 
everything away :) but after a few clicks the data began to flow!


So thanks for all the help, especially to chris (from one german to 
another lol)


Regards

Markus

Am 06.04.2016 um 16:43 schrieb Markus Rosjat:

Hi Craig,

yeah my server is fine in general but maybe the other adin just has some
sort of own ways to blacklist so I might be on there list. I'll check
this too but it seems it could be a routing problem to since the other
mx sometimes talk and sometimes not (checked from other location to
connect and I was able to connect only once).

So I'll give the "nice" guy on the other and of the line a last hint and
then I just leave it because I pretty much ruled all things that could
go wrong out on my end.

Regards

Am 06.04.2016 um 16:25 schrieb Craig Skinner:

Hi Markus,

On 2016-04-06 Wed 09:29 AM |, Markus Rosjat wrote:

Okay with some help from Christoph Viethen I did some testing and
connfirmed
a few things

- sendmail -bt gave me the right order of the mx to talk to
- I couldn't connect to the server with nc
- I couldn't ping the server
- nslookup gave me the correct IP to the server

what really confuses me, and I only did that to have some other tool
checking if it can connect to the mx in question, is the fact that a
site
like mxtoolbox can talk to the mx.



They've probably got your IP address in a blacklist of some sort.
Check your mail server's IP address on http://multirbl.valli.org/lookup/
(You might need to be delisted.)

Otherwise, try traceroute (-I) from your mail server to theirs to find
where the trail ends.

Then contact them by phone/fax/freemail with your problem report.

Cheers.





--
Markus Rosjatfon: +49 351 8107223mail: ros...@ghweb.de

G+H Webservice GbR Gorzolla, Herrmann
Königsbrücker Str. 70, 01099 Dresden

http://www.ghweb.de
fon: +49 351 8107220   fax: +49 351 8107227

Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before 
you print it, think about your responsibility and commitment to the 
ENVIRONMENT




Need help to install OpenBSD 5.9 macppc via pxe

2016-04-07 Thread Solène Rapenne

Hello,

I am trying to install OpenBSD 5.9 on an old mac mini (which actually 
runs FreeBSD and was using OpenBSD before). So, I choosed the network 
way for installation and followed the installation instructions. I get 
an error when loading /bsd.rd (picture at the end)


I have my dhcp/tftp/nfs server with address 192.168.1.5 (running 
freebsd), files for 5.9 are under /usr/local/www/thttpd/


-rw-r--r--  1 root  wheel  1552 Feb 26 14:59 SHA256
-rw-r--r--  1 root  wheel  1715 Feb 26 14:59 SHA256.sig
-rw-r--r--  1 root  wheel  53657599 Feb 26 11:52 base59.tgz
-rw-r--r--  1 root  wheel184634 Feb 26 11:17 boot.mac
-rw-r--r--  1 root  wheel   7787638 Apr  7 12:48 bsd
-rw-r--r--  1 root  wheel   7807488 Apr  7 12:49 bsd.mp
-rw-r--r--  1 root  wheel   8549933 Apr  7 11:28 bsd.rd
-rw-r--r--  1 root  wheel  6917 Feb 26 11:17 bsd.tbxi
-rw-r--r--  1 root  wheel  54197476 Feb 26 11:53 comp59.tgz
-rw-r--r--  1 root  wheel   2812954 Feb 26 11:53 game59.tgz
-rw-r--r--  1 root  wheel   8991150 Feb 26 11:53 man59.tgz
-rw-r--r--  1 root  wheel 64800 Feb 26 11:17 ofwboot
-rw-r--r--  1 root  wheel  23869487 Feb 26 14:53 xbase59.tgz
-rw-r--r--  1 root  wheel  40014023 Feb 26 14:53 xfont59.tgz
-rw-r--r--  1 root  wheel  17159113 Feb 26 14:54 xserv59.tgz
-rw-r--r--  1 root  wheel   4528018 Feb 26 14:54 xshare59.tgz

my /etc/exports :
/usr/local/www/thttpd/ -alldirs -ro -mapall=nobody -network 
192.168.1.0/24



my dhcpd.conf (isc-dhcpd) :

allow booting;
allow bootp;
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
 range 192.168.1.20 192.168.1.50;
 option broadcast-address 192.168.1.255;
}

host macmini {
 next-server 192.168.1.5;
 option subnet-mask 255.255.255.0;
 option routers 192.168.1.5;
 option root-path "192.168.1.5:/usr/local/www/thttpd";
 fixed-address 192.168.1.22;
 hardware ethernet 00:14:51:1f:52:70;
}



I can mount the nfs from the freebsd of the mac mini and get files, so 
the NFS is fine. The PXE is fine as it load ofwboot. The DHCP is fine 
too as it get an IP.


But it can't find /bsd.rd which is at the root of the nfs export. What 
is wrong with my setup ?


Picture of the boot in the open firmware 
http://i.zcraft.fr/960991460029255.jpg


Kind regards



Re: T420s 5.9/amd64 fan control?

2016-04-07 Thread Tor Houghton
On Wed, Apr 06, 2016 at 11:27:11AM -0700, Mike Larkin wrote:
> 
> Someone else recently reported this same issue was fixed by a bios upgrade.
> 
> I'd start there first.
> 

Thanks!

A BIOS update did the tricki (dmesg attached).

Tor

OpenBSD 5.9 (GENERIC.MP) #1888: Fri Feb 26 01:20:19 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 8450076672 (8058MB)
avail mem = 8189784064 (7810MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (65 entries)
bios0: vendor LENOVO version "8CET61WW (1.41 )" date 02/18/2016
bios0: LENOVO 4176A11
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT 
SSDT UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP5(S4) EHC1(S3) 
EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2492.31 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.91 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus 5 (EXP4)
acpiprt5 at acpi0: bus 13 (EXP5)
acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 98 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model "42T4847" serial  8815 type LION oem "Panasonic"
acpibat1 at acpi0: BAT1 model "45N1041" serial  1540 type LiP oem "SONY"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 
1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1600x900
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
puc0 at pci0 dev 22 function 3 "Intel 6 Series KT" rev 0x04: ports: 1 com
com4 at puc0 port 0 apic 2 int 19: ns16550a, 16 byte fifo
com4: probed fifo depth: 0 bytes
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address 
f0:de:f1:fa:65:5f
ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 6 Series HD Audio" rev 0x04: msi
azalia0: codecs: Conexant CX20590, 

xbacklight / screen brightness

2016-04-07 Thread Riccardo Mottola

Hi,

I noticed that on an HP 4530 laptop (using the intel video card, the 
extra video card which wasn't properly initialized and used in OpenBSD 
is directly disabled in the bios) comes up both in console and in X with 
a pretty dim screen brightness.


"xbacklight" tells me however "100".
if I lower it with "-set 90" I actually notice it gets brighter, setting 
it to "-set 100" .. it goes to full brightness.


It looks as if initially the value is read back incorrect from a status 
register?


Anyone else has a similar problem?

It appears very similar to what is happening on my ThinkPad.. there 
however I can't go up with brightness excepbt by putting the laotp to 
sleep and resuming it.


Riccardo



Re: ports(7) has a 404 link

2016-04-07 Thread Jason McIntyre
On Wed, Apr 06, 2016 at 02:20:03PM +0200, Sol??ne Rapenne wrote:
> Hi
> 
> Dead link in ports(7)
> 

fixed, thanks.
jmc

> 
> Index: ports.7
> ===
> RCS file: /cvs/src/share/man/man7/ports.7,v
> retrieving revision 1.106
> diff -u -p -r1.106 ports.7
> --- ports.7 24 Nov 2015 21:27:03 -  1.106
> +++ ports.7 6 Apr 2016 12:16:25 -
> @@ -743,7 +743,7 @@ List of users and groups created by port
>  The
>  .Ox
>  Ports System:
> -.Lk http://www.openbsd.org/faq/ports/ports.html
> +.Lk http://www.openbsd.org/faq/faq15.html
>  .Pp
>  The
>  .Ox