Re: sudoedit for doas?

[jungle boogie]

Thus said Michael on Thu, 01 Mar 2018 08:39:51 +0100

‎What is a sudoedit alternative?
I mean: what should it do?



You can edit the file with a text editor, like vim.

Worth reading:
https://undeadly.org/cgi?action=article=20160913101323

Re: sudoedit for doas?

[michael]

‎What is a sudoedit alternative? 
I mean: what should it do?




  Originalnachricht  
Von: Hess THR
Gesendet: Mittwoch, 28. Februar 2018 07:51
An: misc@OpenBSD.org; t...@openbsd.org
Betreff: sudoedit for doas?

Hello, 

hmm, I went through the relevant man pages: 

https://man.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/doas.1
https://man.openbsd.org/doas.conf.5

but I cannot find a sudoedit alternative for the "doas". 

Are there any? 

Many thanks. 

Re: Suddenly Trojta mail application on my computer can't sent e-mail.

[Carson Chittom]

"f...@freddyfisker.dk"  writes:

> I have been using Trojita for more than 2 years without problems, but now I 
> can't sent mails any more.
>
> It's OpenBSD 6.1 and Trojita 0.7p1 I am using.
>
> When I try to sent an e-mail, there is coming a window with the text: Host 
> not found.
>
> Then the mail is in Trojita folder: Sent
>
> But the mail is not sent.
>
> This mail is sent from my webmail.

I recommend verifying with your mail administrator the SMTP server and
settings you should be using.  The fact that you happen to be running
OpenBSD seems to be irrelevant, based on your problem statement.

Re: gif(4) changes vs tunnelbroker

[Andreas Bartelt]

On 03/01/18 00:30, David Gwynne wrote:



On 1 Mar 2018, at 02:22, Andreas Bartelt  wrote:

On 02/27/18 22:35, Pavel Korovin wrote:

On 02/28, David Gwynne wrote:

what is the status of sysctl net.inet.ipip ?

David, thank you! That was easy :)
Sorry for the noise.
$ sysctl net.inet.ipip.allow
net.inet.ipip.allow=0
# sysctl -w net.inet.ipip.allow=1
net.inet.ipip.allow: 0 -> 1
$ ping6 www.google.com
PING www.google.com (2a00:1450:4013:c01::67): 56 data bytes
64 bytes from 2a00:1450:4013:c01::67: icmp_seq=0 hlim=48 time=40.500 ms
64 bytes from 2a00:1450:4013:c01::67: icmp_seq=1 hlim=48 time=40.645 ms
^C


I'm also observing a breakage of a previously working IPv6 tunnelbroker config 
on current (problem introduced since at least Feb, 23rd).

The combination of two things made it work again (or at least works around the 
underlying problem):
1) sysctl net.inet.ipip.allow=1 [not yet documented at 
www.openbsd.org/faq/current.html]
2) removing ``set state-policy if-bound'' from my pf.conf [which always worked 
before with the same tunnelbroker setup]

According to pflog(4), a ping6 to some destination now looks buggy to me:
- outgoing icmp6 echo request is only visible on gif(4)
- incoming icmp6 echo reply is only visible on the underlying physical 
interface of gif(4)
which blocks the ping6 in the case of ``set state-policy if-bound''.


i found what i think is the problem.

it turns out the net.inet.ipip.allow sysctl was a red herring. it controls the 
processing of ipip by the network stack, it is not related to whether gif 
should accept packets. the problem was i got the mapping of ip addresses in 
incoming packets to the addresses on the tunnels wrong.

this should be fixed in src/sys/net/if_gif.c r1.112.



yes, thanks -- it now works again with state-policy if-bound in pf.conf 
and net.inet.ipip.allow=0

Install OpenBSD on imac - radeon drm problems

[Manuel Solis Vazquez]

Dear All,

Since i love OBSD, for instance i have it in my panasonic cf-30, dell
precision 690 and a samsung Laptop, i would like to install it in an imac
mid 2011.

The problem is that after install, the first boot always goes blank.

What happened is:
- The install goes as perfect as always.
- When it comes to the first boot, it shows the "error:
[drm:pid0:radeon_read_platform_bios] *ERROR* bios size zero or checksum
mismatch" and CRASH!!!
- I did boot -c, but it freezes on UKC> prompt and do not let me disable
the radeondrm, actually i could only shut it down by the button or power
outlet.
- I did install both 6.2 and 27feb current snapshot and it came with the
same error.

I did boot from the bsd.rd of the installer, but i couldn't save the
dmesg.txt,
as i can see the USB by "sysctl hw.disknames" and it shows something like
"sd0, rd0, sd1, sd2" (sd0 internal disk, rd0 ramdisk, sd1 usb installer,
sd2 usb to backup the dmesg)
but when i do a "disklabel sd2" it returns "no directory" so i could not do
something like:
#disklabel sd2
#mount /dev/sd2a /mnt
#dmesg > /mnt/dmesg.txt
to back up the info and add it to this mail.

Could you please give me a hint ?

Thank you so much in advance :)

Manuel Solis

PD Silly tought: can i manually install the firmware for the radeon card
from the installer shell?
like some creepy thing as: cp raderon.fw
rsd0a:/usr/AllDriverGoesHereWhenItBootsSoItWontCrashAgain/
(it is intentionally silly command but you get the idea)

Re: noip freezes my 6.0

[Nick Holland]

On 02/28/18 02:06, Hess THR wrote:
> Hello, 
> 
> pkg_add ...pub/OpenBSD/6.0/packages/amd64/no-ip-2.1.9p4.tgz
...
> How can I help the community, how to debug this problem? (before opening a 
> low-level bugreport, want to make it a more quality report)

Step 1: upgrade to a 6.2-current snapshot.  Nothing is being looked at
or thought about in the 6.0 world.  6.3 is coming soonish.  That's the
only place a fix will happen, if it is an OpenBSD problem.  It will not
be fixed in 6.2 or 6.1, and certainly not something as old as 6.0.

Step 2: give your hardware a good workout.  Building the system from
source might be a good way.  What you describe could just be marginal hw
or a power glitch or a bad disk which fails during the 1:30am daily
self-checks, and got lucky once when you also happened to turn off the
no-ip app.  This really does sound more like a hw issue than an OS or
application issue.

Step 3: contact the port maintainer.  Maybe they are aware of something.
 Do not do this before steps 1 and 2 are complete, however.

After that, file a proper bug report.

Nick.

Re: Black screen when starting Xorg with new laptop.

[George Ramirez]

Sure. But I am not sure in which state you want me to send them. I
haven't disabled inteldrm like pstern suggested. tbh, I wouldn't know
how to do that yet. What I did do was upgrade to the latest snapshot
from February 28th and  give it another syspatch but that didn't fix
the problem. Here is my dmesg and Xorg.0.log.

On Wed, Feb 28, 2018 at 4:11 PM, Noth  wrote:
> Can you boot without X running, copy /var/log/Xorg.0.log and dmesg to a usb
> stick or another machine and then upload those to this thread? This is an
> ongoing acpi issue with inteldrm I believe, it stopped working in 6.2 for
> Skylake and newer intel GPUs. No change in sight...
>
>
> Noth
>
>
> On 26/02/18 23:11, George Ramirez wrote:
>>
>> Sadly this didn't work. I tried the keys for the screen brightness but
>> nothing changed.
>>
>> On Thu, Feb 22, 2018 at 3:29 PM, Andrew  wrote:
>>
>>> On 02/22/18 09:27, George Ramirez wrote:
>>>
 with intel 620 UHD graphics. At first, the console shows with underscan,
 then the resolution changes to the native one, and finally it goes
 black.

>>> It's a frustrating problem because there are no errors and it seemingly
>>> doesn't work. I bet X is actually running properly but xbacklight
>>> somehow ended up = 0. Tap the "brightness" key on your keyboard a couple
>>> times and see if it illuminates the display properly. On my ThinkPad
>>> it's [Fn]+[Home]. Also check out man xbacklight(1). Good luck !!!
>>>
>


dmesg
Description: Binary data
# cat /var/log/Xorg.0.log
[23.819] (--) checkDevMem: using aperture driver /dev/xf86
[23.842] (--) Using wscons driver on /dev/ttyC4
[23.860] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[23.861] X Protocol Version 11, Revision 0
[23.861] Build Operating System: OpenBSD 6.2 amd64 
[23.861] Current Operating System: OpenBSD novao.home 6.2 GENERIC.MP#15 amd64
[23.861] Build Date: 27 February 2018  10:32:31PM
[23.861]  
[23.861] Current version of pixman: 0.34.0
[23.861]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[23.861] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[23.861] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Mar  1 02:40:44 2018
[23.862] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
[23.863] (==) No Layout section.  Using the first Screen section.
[23.863] (==) No screen section available. Using defaults.
[23.863] (**) |-->Screen "Default Screen Section" (0)
[23.863] (**) |   |-->Monitor ""
[23.863] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[23.864] (==) Automatically adding devices
[23.864] (==) Automatically enabling devices
[23.864] (==) Not automatically adding GPU devices
[23.864] (==) Max clients allowed: 256, resource mask: 0x1f
[23.868] (==) FontPath set to:
/usr/X11R6/lib/X11/fonts/misc/,
/usr/X11R6/lib/X11/fonts/TTF/,
/usr/X11R6/lib/X11/fonts/OTF/,
/usr/X11R6/lib/X11/fonts/Type1/,
/usr/X11R6/lib/X11/fonts/100dpi/,
/usr/X11R6/lib/X11/fonts/75dpi/
[23.868] (==) ModulePath set to "/usr/X11R6/lib/modules"
[23.868] (II) The server relies on wscons to provide the list of input devices.
If no devices become available, reconfigure wscons or disable AutoAddDevices.
[23.868] (II) Loader magic: 0x351bf42000
[23.868] (II) Module ABI versions:
[23.868]X.Org ANSI C Emulation: 0.4
[23.868]X.Org Video Driver: 23.0
[23.868]X.Org XInput driver : 24.1
[23.868]X.Org Server Extension : 10.0
[23.868] (--) PCI:*(0:0:2:0) 8086:5917:1558:1313 rev 7, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64
[23.868] (II) LoadModule: "glx"
[23.870] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[23.877] (II) Module glx: vendor="X.Org Foundation"
[23.877]compiled for 1.19.6, module version = 1.0.0
[23.877]ABI class: X.Org Server Extension, version 10.0
[23.877] (==) Matched modesetting as autoconfigured driver 0
[23.877] (==) Assigned the driver to the xf86ConfigLayout
[23.877] (II) LoadModule: "modesetting"
[23.878] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so
[23.878] (II) Module modesetting: vendor="X.Org Foundation"
[23.878]compiled for 1.19.6, module version = 1.19.6
[23.878]Module class: X.Org Video Driver
[23.878]ABI class: X.Org Video Driver, version 23.0
[23.878] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[23.879] (**) 

Re: Please explain the pkg_check F option, thank you.

[Marc Espie]

On Wed, Feb 28, 2018 at 07:48:34PM +, Zsolt Kantor wrote:
> Thanks Sebastien, I just figured out this. Now everything is clear.
> If I may propose something . . . those "Not found" items even if it is not an 
> error, is a little bit misleading . . . From a simple user's point of view 
> the pkg_check -F in normal circumstances should return cleanly. Maybe an 
> extra option for pkg_check in future that tells to show those "Not found" 
> items (by default not to show).
> 

Nope. That's the whole point of pkg_check -F

Notice that it's an option. You enabled it, you want to check the files
on your machine further.

There is definitely some handholding needed afterwards.

Re: gif(4) changes vs tunnelbroker

[David Gwynne]

> On 1 Mar 2018, at 02:22, Andreas Bartelt  wrote:
> 
> On 02/27/18 22:35, Pavel Korovin wrote:
>> On 02/28, David Gwynne wrote:
>>> what is the status of sysctl net.inet.ipip ?
>> David, thank you! That was easy :)
>> Sorry for the noise.
>> $ sysctl net.inet.ipip.allow
>> net.inet.ipip.allow=0
>> # sysctl -w net.inet.ipip.allow=1
>> net.inet.ipip.allow: 0 -> 1
>> $ ping6 www.google.com
>> PING www.google.com (2a00:1450:4013:c01::67): 56 data bytes
>> 64 bytes from 2a00:1450:4013:c01::67: icmp_seq=0 hlim=48 time=40.500 ms
>> 64 bytes from 2a00:1450:4013:c01::67: icmp_seq=1 hlim=48 time=40.645 ms
>> ^C
> 
> I'm also observing a breakage of a previously working IPv6 tunnelbroker 
> config on current (problem introduced since at least Feb, 23rd).
> 
> The combination of two things made it work again (or at least works around 
> the underlying problem):
> 1) sysctl net.inet.ipip.allow=1 [not yet documented at 
> www.openbsd.org/faq/current.html]
> 2) removing ``set state-policy if-bound'' from my pf.conf [which always 
> worked before with the same tunnelbroker setup]
> 
> According to pflog(4), a ping6 to some destination now looks buggy to me:
> - outgoing icmp6 echo request is only visible on gif(4)
> - incoming icmp6 echo reply is only visible on the underlying physical 
> interface of gif(4)
> which blocks the ping6 in the case of ``set state-policy if-bound''.

i found what i think is the problem.

it turns out the net.inet.ipip.allow sysctl was a red herring. it controls the 
processing of ipip by the network stack, it is not related to whether gif 
should accept packets. the problem was i got the mapping of ip addresses in 
incoming packets to the addresses on the tunnels wrong.

this should be fixed in src/sys/net/if_gif.c r1.112.

sorry for the inconvenience.

dlg

Re: Please explain the pkg_check F option, thank you.

[Chris Bennett]

On Wed, Feb 28, 2018 at 07:58:22PM +, Zsolt Kantor wrote:
> 
> 
> By the way. For a simple user (I'm using OpenBSD just for fun, and learning) 
> it is worth to enable the weekly script, or not?
> 

Absolutely! For "fun", check to see all of the things it does.

Do you need to run it weekly? You can decide that for yourself.
I always run it immediately after an install or upgrade.
And I run it again after adding the packages I use.
/bin/sh /etc/weekly

Did you write a useful script and you forgot where you put it?
locate cool_script.pl
Then you can edit it or possibly want to run it securely?
/usr/bin/perl /usr/local/sbin/cool_script.pl
instead of evil hacker's /usr/bin/cool_script.pl that does nasty things!
try echo $PATH to see what version gets run first.

OpenBSD is a lot of fun and a fantastic system to learn the "right" way
to do things.

My advice is to read a few man pages every day for every program in the
base install.

Also, if you don't like reading man pages as they come up, read man
mandoc and see how you can make them html or pdf, etc.

Have fun! I do.
Chris Bennett

Re: Lenovo X130e blank video at boot.rd

[j]

On 2018-02-28 11:18, Stefan Sperling wrote:



The x130e can boot in either UEFI or legacy mode.

I have 'UEFI/Legacy Boot' set to 'Both' and 'UEFI/Legacy Boot Priority'
set to 'Legacy First'.

Maybe this issue only happens with UEFI?


Yes, that does it.  "Legacy First" resolves the problem.  FYI so did the 
Feb 27 snapshot in "UEFI first" mode.


Thanks everyone for your assistance!


--John

Re: Please explain the pkg_check F option, thank you.

[Zsolt Kantor]

By the way. For a simple user (I'm using OpenBSD just for fun, and learning) it 
is worth to enable the weekly script, or not?

Thanks,
Zsolt

Re: Please explain the pkg_check F option, thank you.

[Zsolt Kantor]

Thanks Sebastien, I just figured out this. Now everything is clear.
If I may propose something . . . those "Not found" items even if it is not an 
error, is a little bit misleading . . . From a simple user's point of view the 
pkg_check -F in normal circumstances should return cleanly. Maybe an extra 
option for pkg_check in future that tells to show those "Not found" items (by 
default not to show).



On Wednesday, February 28, 2018 9:06 PM, Sebastien Marie  
wrote:



On Wed, Feb 28, 2018 at 06:56:17PM +, Zsolt Kantor wrote:

> Another question.
> pkg_check -F uses pkg_locate script to locate package files, directories.
> pkg_locate uses locate to do that.
> Question: If I use pkg_locate bsd.rd nothing is returned, but if I use locate 
> bsd.rd the ramdisk kernel is returned. Why? Is pkg_locate not working 
> correctly? Or I'm missing something?

pkg_locate uses a database populated with all files from ports
(installed packages or not).

locate uses a database populated with updatedb, and it contains only
files installed on filesystem (it is updated weekly).

so pkg_locate bsd.rd searchs if a file "bsd.rd" exists in some port
(installed or not); whereas locate bsd.rd searchs if a file "bsd.rd"
exists in current filesystem.

-- 
Sebastien Marie

Re: Lenovo X130e blank video at boot.rd

[Klemens Nanni]

On Wed, Feb 28, 2018 at 07:18:46PM +0100, Stefan Sperling wrote:
> On Wed, Feb 28, 2018 at 11:23:20AM -0500, Allan Streib wrote:
> > j...@bitminer.ca writes:
> > 
> > > Just for laughs I booted an OpenBSD 4.2 CD, circa 1997 (and five years 
> > > older than the hardware) and while it recognized few devices it did show 
> > > all video correctly.  The video device vga1 shows as vendor "ATI" 
> > > unknown product 0x9806 rev 0x00.
> > 
> > That release predates the introduction of the framebuffer console.
> > 
> > I have had a problem since that started, the video mode selected is
> > incorrect and I see the boot messages in VGA mode until the framebuffer
> > console is activated, then the screen goes blank and pops up a message
> > complaining about the video mode. I have to do a blind login and then
> > run startx. Never learned how to disable wsdisplay and keep the simple
> > 80x24 console.
> > 
> > Allan
> 
> The x130e can boot in either UEFI or legacy mode.
> 
> I have 'UEFI/Legacy Boot' set to 'Both' and 'UEFI/Legacy Boot Priority'
> set to 'Legacy First'.
> 
> Maybe this issue only happens with UEFI?
Most likely.

I have no such board around to test but this sounds similar to what I
experienced with a ThinkPad X121e:

https://marc.info/?l=openbsd-tech=150457245320842=2

Try setting different video and/or GOP modes as described in to see
whether this is just another cripled UEFI setup.

https://marc.info/?l=openbsd-tech=150557217729175=2

Re: Please explain the pkg_check F option, thank you.

[Sebastien Marie]

On Wed, Feb 28, 2018 at 06:56:17PM +, Zsolt Kantor wrote:
> Another question.
> pkg_check -F uses pkg_locate script to locate package files, directories.
> pkg_locate uses locate to do that.
> Question: If I use pkg_locate bsd.rd nothing is returned, but if I use locate 
> bsd.rd the ramdisk kernel is returned. Why? Is pkg_locate not working 
> correctly? Or I'm missing something?

pkg_locate uses a database populated with all files from ports
(installed packages or not).

locate uses a database populated with updatedb, and it contains only
files installed on filesystem (it is updated weekly).

so pkg_locate bsd.rd searchs if a file "bsd.rd" exists in some port
(installed or not); whereas locate bsd.rd searchs if a file "bsd.rd"
exists in current filesystem.

-- 
Sebastien Marie

Re: Please explain the pkg_check F option, thank you.

[Zsolt Kantor]

Another question.
pkg_check -F uses pkg_locate script to locate package files, directories.
pkg_locate uses locate to do that.
Question: If I use pkg_locate bsd.rd nothing is returned, but if I use locate 
bsd.rd the ramdisk kernel is returned. Why? Is pkg_locate not working 
correctly? Or I'm missing something?

Re: Lenovo X130e blank video at boot.rd

[Stefan Sperling]

On Wed, Feb 28, 2018 at 11:23:20AM -0500, Allan Streib wrote:
> j...@bitminer.ca writes:
> 
> > Just for laughs I booted an OpenBSD 4.2 CD, circa 1997 (and five years 
> > older than the hardware) and while it recognized few devices it did show 
> > all video correctly.  The video device vga1 shows as vendor "ATI" 
> > unknown product 0x9806 rev 0x00.
> 
> That release predates the introduction of the framebuffer console.
> 
> I have had a problem since that started, the video mode selected is
> incorrect and I see the boot messages in VGA mode until the framebuffer
> console is activated, then the screen goes blank and pops up a message
> complaining about the video mode. I have to do a blind login and then
> run startx. Never learned how to disable wsdisplay and keep the simple
> 80x24 console.
> 
> Allan

The x130e can boot in either UEFI or legacy mode.

I have 'UEFI/Legacy Boot' set to 'Both' and 'UEFI/Legacy Boot Priority'
set to 'Legacy First'.

Maybe this issue only happens with UEFI?

Re: Lenovo X130e blank video at boot.rd

[Allan Streib]

j...@bitminer.ca writes:

> Just for laughs I booted an OpenBSD 4.2 CD, circa 1997 (and five years 
> older than the hardware) and while it recognized few devices it did show 
> all video correctly.  The video device vga1 shows as vendor "ATI" 
> unknown product 0x9806 rev 0x00.

That release predates the introduction of the framebuffer console.

I have had a problem since that started, the video mode selected is
incorrect and I see the boot messages in VGA mode until the framebuffer
console is activated, then the screen goes blank and pops up a message
complaining about the video mode. I have to do a blind login and then
run startx. Never learned how to disable wsdisplay and keep the simple
80x24 console.

Allan

Re: gif(4) changes vs tunnelbroker

[Andreas Bartelt]

On 02/27/18 22:35, Pavel Korovin wrote:

On 02/28, David Gwynne wrote:

what is the status of sysctl net.inet.ipip ?


David, thank you! That was easy :)
Sorry for the noise.

$ sysctl net.inet.ipip.allow
net.inet.ipip.allow=0
# sysctl -w net.inet.ipip.allow=1
net.inet.ipip.allow: 0 -> 1
$ ping6 www.google.com
PING www.google.com (2a00:1450:4013:c01::67): 56 data bytes
64 bytes from 2a00:1450:4013:c01::67: icmp_seq=0 hlim=48 time=40.500 ms
64 bytes from 2a00:1450:4013:c01::67: icmp_seq=1 hlim=48 time=40.645 ms
^C


I'm also observing a breakage of a previously working IPv6 tunnelbroker 
config on current (problem introduced since at least Feb, 23rd).


The combination of two things made it work again (or at least works 
around the underlying problem):
1) sysctl net.inet.ipip.allow=1 [not yet documented at 
www.openbsd.org/faq/current.html]
2) removing ``set state-policy if-bound'' from my pf.conf [which always 
worked before with the same tunnelbroker setup]


According to pflog(4), a ping6 to some destination now looks buggy to me:
- outgoing icmp6 echo request is only visible on gif(4)
- incoming icmp6 echo reply is only visible on the underlying physical 
interface of gif(4)

which blocks the ping6 in the case of ``set state-policy if-bound''.

Re: Black screen when starting Xorg with new laptop.

[Noth]

Can you boot without X running, copy /var/log/Xorg.0.log and dmesg to a 
usb stick or another machine and then upload those to this thread? This 
is an ongoing acpi issue with inteldrm I believe, it stopped working in 
6.2 for Skylake and newer intel GPUs. No change in sight...



Noth


On 26/02/18 23:11, George Ramirez wrote:

Sadly this didn't work. I tried the keys for the screen brightness but
nothing changed.

On Thu, Feb 22, 2018 at 3:29 PM, Andrew  wrote:


On 02/22/18 09:27, George Ramirez wrote:


with intel 620 UHD graphics. At first, the console shows with underscan,
then the resolution changes to the native one, and finally it goes black.


It's a frustrating problem because there are no errors and it seemingly
doesn't work. I bet X is actually running properly but xbacklight
somehow ended up = 0. Tap the "brightness" key on your keyboard a couple
times and see if it illuminates the display properly. On my ThinkPad
it's [Fn]+[Home]. Also check out man xbacklight(1). Good luck !!!



[65.893] (--) checkDevMem: using aperture driver /dev/xf86
[65.912] (--) Using wscons driver on /dev/ttyC4
[65.931] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[65.931] X Protocol Version 11, Revision 0
[65.931] Build Operating System: OpenBSD 6.2 amd64 
[65.931] Current Operating System: OpenBSD ghost.nineinchnetworks.ch 6.2 GENERIC.MP#10 amd64
[65.931] Build Date: 21 February 2018  09:42:35PM
[65.931]  
[65.931] Current version of pixman: 0.34.0
[65.931] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[65.931] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[65.931] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 27 00:01:56 2018
[65.932] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
[65.933] (==) No Layout section.  Using the first Screen section.
[65.933] (==) No screen section available. Using defaults.
[65.933] (**) |-->Screen "Default Screen Section" (0)
[65.933] (**) |   |-->Monitor ""
[65.934] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[65.934] (==) Automatically adding devices
[65.934] (==) Automatically enabling devices
[65.934] (==) Not automatically adding GPU devices
[65.934] (==) Max clients allowed: 256, resource mask: 0x1f
[65.940] (==) FontPath set to:
	/usr/X11R6/lib/X11/fonts/misc/,
	/usr/X11R6/lib/X11/fonts/TTF/,
	/usr/X11R6/lib/X11/fonts/OTF/,
	/usr/X11R6/lib/X11/fonts/Type1/,
	/usr/X11R6/lib/X11/fonts/100dpi/,
	/usr/X11R6/lib/X11/fonts/75dpi/
[65.940] (==) ModulePath set to "/usr/X11R6/lib/modules"
[65.940] (II) The server relies on wscons to provide the list of input devices.
	If no devices become available, reconfigure wscons or disable AutoAddDevices.
[65.940] (II) Loader magic: 0x137d86742000
[65.940] (II) Module ABI versions:
[65.940] 	X.Org ANSI C Emulation: 0.4
[65.940] 	X.Org Video Driver: 23.0
[65.940] 	X.Org XInput driver : 24.1
[65.940] 	X.Org Server Extension : 10.0
[65.941] (--) PCI:*(0:0:2:0) 8086:1916:1028:0704 rev 7, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64
[65.941] (II) LoadModule: "glx"
[65.942] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[65.952] (II) Module glx: vendor="X.Org Foundation"
[65.952] 	compiled for 1.19.6, module version = 1.0.0
[65.952] 	ABI class: X.Org Server Extension, version 10.0
[65.952] (==) Matched modesetting as autoconfigured driver 0
[65.952] (==) Assigned the driver to the xf86ConfigLayout
[65.952] (II) LoadModule: "modesetting"
[65.952] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so
[65.953] (II) Module modesetting: vendor="X.Org Foundation"
[65.953] 	compiled for 1.19.6, module version = 1.19.6
[65.953] 	Module class: X.Org Video Driver
[65.953] 	ABI class: X.Org Video Driver, version 23.0
[65.953] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[65.953] (**) modeset(0): claimed PCI slot 0@0:2:0
[65.953] (II) modeset(0): using default device
[65.954] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[65.954] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[65.954] (==) modeset(0): RGB weight 888
[65.954] (==) modeset(0): Default visual is TrueColor
[65.954] (II) Loading sub module "glamoregl"
[65.954] (II) LoadModule: "glamoregl"
[65.955] (II) Loading /usr/X11R6/lib/modules/libglamoregl.so
[65.968] (II) Module glamoregl: vendor="X.Org Foundation"
[65.968] 	compiled for 1.19.6, module version = 1.0.0
[65.968] 	ABI class: X.Org ANSI C Emulation, version 0.4
[65.968] (II) 

Re: Lenovo X130e blank video at boot.rd

[j]

On 2018-02-28 06:51, Stefan Sperling wrote:

On Tue, Feb 27, 2018 at 04:53:06PM -0700, j...@bitminer.ca wrote:




My x130e has no problems booting -current miniroot62.fs from USB.
Video works fine ("ATI Radeon HD 6310"). dmesg below.

Did you boot from OpenBSd powered-off state or soft reboot after 
running

Windows? It's possible that Windows leaves devices in a state where
OpenBSD cannot use them.

BTW this machine used to be an E-450 as well, however something broke
on the mainboard so the system would not see the battery anymore.
At the time I could only find an E-300 mainboard to replace it but it's
been working fine since.


Just for laughs I booted an OpenBSD 4.2 CD, circa 1997 (and five years 
older than the hardware) and while it recognized few devices it did show 
all video correctly.  The video device vga1 shows as vendor "ATI" 
unknown product 0x9806 rev 0x00.


Thanks for the hint on power cycling; however I always have had to 
restart from power off to get the choice of boot device.


And here is another hint: after booting with "-c" the screen goes blank 
even before the UKC> prompt.


I will try -current next.


--John



OpenBSD 6.2-current (RAMDISK_CD) #11: Tue Feb 27 17:20:47 MST 2018

dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD

real mem = 3849388032 (3671MB)
avail mem = 3728969728 (3556MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf9d00 (58 entries)
bios0: vendor LENOVO version "8RET52WW (1.15 )" date 11/15/2011
bios0: LENOVO 305162G
acpi0 at bios0: rev 4
acpi0: tables DSDT FACP SLIC HPET APIC MCFG UEFI UEFI SSDT SSDT UEFI
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD E-300 APU with Radeon(tm) HD Graphics, 1297.51 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,RDTSCP,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: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PB4_)
acpiprt2 at acpi0: bus 1 (PB5_)
acpiprt3 at acpi0: bus 2 (PB6_)
acpiprt4 at acpi0: bus 3 (PB7_)
acpiprt5 at acpi0: bus 4 (P2P_)
acpiprt6 at acpi0: bus -1 (SPB0)
acpiprt7 at acpi0: bus -1 (SPB1)
acpiprt8 at acpi0: bus -1 (SPB2)
acpiprt9 at acpi0: bus -1 (SPB3)
acpiec0 at acpi0
acpicpu at acpi0 not configured
acpitz at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C0E" at acpi0 not configured
"LEN0026" at acpi0 not configured
"LEN0068" at acpi0 not configured
"ACPI0003" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"PNP0C0D" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00
vga1 at pci0 dev 1 function 0 "ATI Radeon HD 6310" rev 0x00
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
"ATI Radeon HD 6310 HD Audio" rev 0x00 at pci0 dev 1 function 1 not 
configured

ppb0 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
rtwn0 at pci1 dev 0 function 0 "Realtek 8188CE" rev 0x01: msi
rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R, address 9c:b7:0d:e1:11:6d
ppb1 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
alc0 at pci2 dev 0 function 0 "Attansic Technology L1D" rev 0xc0: msi,
address 04:7d:7b:31:00:6e
atphy0 at alc0 phy 0: AR8035 10/100/1000 PHY, rev. 0
ppb2 at pci0 dev 7 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci3 at ppb2 bus 3
rtsx0 at pci3 dev 0 function 0 "Realtek RTS5209 Card Reader" rev 0x01: 
msi

sdmmc0 at rtsx0: 4-bit, dma
ahci0 at pci0 dev 17 function 0 "ATI SBx00 SATA" rev 0x00: apic 2 int
19, AHCI 1.2
ahci0: port 0: 3.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  SCSI3
0/direct fixed naa.5001b4496652afc1
sd0: 122104MB, 512 bytes/sector, 250069680 sectors, thin
ohci0 at pci0 dev 18 function 0 "ATI SB700 USB" rev 0x00: apic 2 int
18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 
17

usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "ATI EHCI root hub" rev
2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "ATI SB700 USB" rev 0x00: apic 2 int
18, version 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "ATI SB700 USB2" rev 0x00: apic 2 int 
17

usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "ATI EHCI root hub" rev
2.00/1.00 addr 1
"ATI SBx00 SMBus" rev 0x42 at pci0 dev 20 

Re: Supermicro SuperServer E200-9A

[Mike]

On 2/27/2018 6:00 PM, li...@wrant.com wrote:
> Tue, 27 Feb 2018 10:42:42 -0500 Mike 
>> On 2/27/2018 8:51 AM, Stuart Henderson wrote:
>>> On 2018/02/27 08:30, Rupert Gallagher wrote:  
 Not new at all. 

 https://www.servethehome.com/intel-atom-c3338-benchmarks-why-denverton-is-so-sweet/

 https://www.servethehome.com/intel-atom-c3558-linux-benchmarks-and-review/

 https://www.servethehome.com/
 intel-atom-c3958-16-core-top-end-embedded-qat-linux-benchmarks-and-review/ 
  
>>>
>>> Launch date q3 '17 is pretty new.
>>>   
>>
>> fwiw, for a couple of years, I've been running what could be considered
>> the prior model of that motherboard, the A1SRi-2758F.  OpenBSD has no
>> issues running on it. I use CLI elusively, no X stuff..
> 
> Hi Mike,
> 

Hi.

> 
> Evasively this has not affected your system mainboard, very interesting:
> 
> https://www.servethehome.com/intel-atom-c2000-series-bug-quiet/
> https://www.google.com/search?q=atom+c2758+sudden+death
> 
> The fault affects various makers, manifests itself in dead system board.
> 
> https://www.supermicro.com/products/motherboard/atom/x10/a1sri-2758f.cfm
> https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture_4
> 

I returned my two boards to SuperMicro about a year ago, and they
affected the fix on both of them and returned them to me.  SuperMicro
was even very flexible in the scheduling to fit within the spare board
constraints that I have.  And there was no charge except for the cost to
ship the boards to them.

Re: Please explain the pkg_check F option, thank you.

[Vijay Sankar]

Quoting Marc Espie :


On Tue, Feb 27, 2018 at 10:14:51PM +, Zsolt Kantor wrote:
What exactly does the pkg_check -F option?  If I use it, it does  
some filesystem check, and some "Locating unknown files".


At the end I get: "Locating unknown files: ok", "Locating unknown  
directories: ok", and a long list of "not found" directories and  
files, like below.

Not found:
/boot
/bsd
/bsd.rd
/bsd.sp
/bsd.syspatch61
/etc/X11/xenodm/authdir
. . . .


Those are objects that are expected on a normal system, but that are not
there, see the locate(8) dbs under /usr/lib/locate/src.db and
/usr/X11R6/lib/locate/xorg.db

Not having /bsd and /bsd.rd   seems really strange.


I am using 6.2 -current from

builder.ftlcloud.ca$ sysctl kern.version
kern.version=OpenBSD 6.2-current (GENERIC.MP) #6: Sun Feb 18 20:12:24 CST 2018
vi...@builder.ftlcloud.ca:/usr/src/sys/arch/amd64/compile/GENERIC.MP

and ran pkg_check -F

Not much going on on the package build system

builder.ftlcloud.ca$ w
 6:53AM  up 9 days, 10:40, 3 users, load averages: 0.49, 0.26, 0.11
USERTTY FROM  LOGIN@  IDLE WHAT
vijayp0 10.0.0.1546:49AM 0 /usr/bin/perl  
/usr/sbin/pkg_check -F
vijayp1 10.72.3.61   Tue01PM 17:16 /usr/bin/ftp -V -m -C -o  
/usr/ports/

vijayp2 10.0.0.1546:52AM 0 w

There were no "errors" when pkg_check was run using the root account  
but it gave detailed information that helped me understand what was  
wrong with everything I am doing :) Thank you very much for pkg_check.


When running pkg_check using the user account that I use to build  
ports, I did get the type of errors the OP mentioned.


DETAILS BELOW AS ROOT

builder.ftlcloud.ca# pkg_check -F
Packing-list sanity: ok
Direct dependencies: ok
Reverse dependencies: ok
Files from packages: ok
--- e2fsprogs-1.42.12p4 ---
/usr/local/include/et/com_err.h doesn't link to /usr/local/include/com_err.h
/usr/local/man/man3/uuid_generate_random.3 doesn't link to  
/usr/local/man/man3/uuid_generate.3
/usr/local/man/man3/uuid_generate_time.3 doesn't link to  
/usr/local/man/man3/uuid_generate.3

/usr/local/man/man5/ext3.5 doesn't link to /usr/local/man/man5/ext2.5
/usr/local/man/man5/ext4.5 doesn't link to /usr/local/man/man5/ext2.5
/usr/local/man/man8/fsck.ext2.8 doesn't link to /usr/local/man/man8/e2fsck.8
/usr/local/man/man8/fsck.ext3.8 doesn't link to /usr/local/man/man8/e2fsck.8
/usr/local/man/man8/fsck.ext4.8 doesn't link to /usr/local/man/man8/e2fsck.8
/usr/local/man/man8/fsck.ext4dev.8 doesn't link to  
/usr/local/man/man8/e2fsck.8

/usr/local/man/man8/mkfs.ext2.8 doesn't link to /usr/local/man/man8/mke2fs.8
/usr/local/man/man8/mkfs.ext3.8 doesn't link to /usr/local/man/man8/mke2fs.8
/usr/local/man/man8/mkfs.ext4.8 doesn't link to /usr/local/man/man8/mke2fs.8
/usr/local/man/man8/mkfs.ext4dev.8 doesn't link to  
/usr/local/man/man8/mke2fs.8

/usr/local/sbin/findfs doesn't link to /usr/local/sbin/e2label
/usr/local/sbin/fsck.ext2 doesn't link to /usr/local/sbin/e2fsck
/usr/local/sbin/fsck.ext3 doesn't link to /usr/local/sbin/e2fsck
/usr/local/sbin/fsck.ext4 doesn't link to /usr/local/sbin/e2fsck
/usr/local/sbin/fsck.ext4dev doesn't link to /usr/local/sbin/e2fsck
/usr/local/sbin/mkfs.ext2 doesn't link to /usr/local/sbin/mke2fs
/usr/local/sbin/mkfs.ext3 doesn't link to /usr/local/sbin/mke2fs
/usr/local/sbin/mkfs.ext4 doesn't link to /usr/local/sbin/mke2fs
/usr/local/sbin/mkfs.ext4dev doesn't link to /usr/local/sbin/mke2fs
/usr/local/sbin/tune2fs doesn't link to /usr/local/sbin/e2label
--- g95-4.9.4p7 ---
/usr/local/bin/x86_64-unknown-openbsd6.2-egfortran doesn't link to  
/usr/local/bin/egfortran

--- gawk-4.2.0 ---
/usr/local/bin/gawk-4.2.0 doesn't link to /usr/local/bin/gawk
--- gcc-4.9.4p7 ---
/usr/local/bin/x86_64-unknown-openbsd6.2-egcc doesn't link to  
/usr/local/bin/egcc
/usr/local/bin/x86_64-unknown-openbsd6.2-egcc-ar doesn't link to  
/usr/local/bin/egcc-ar
/usr/local/bin/x86_64-unknown-openbsd6.2-egcc-nm doesn't link to  
/usr/local/bin/egcc-nm
/usr/local/bin/x86_64-unknown-openbsd6.2-egcc-ranlib doesn't link to  
/usr/local/bin/egcc-ranlib
/usr/local/bin/x86_64-unknown-openbsd6.2-gcc-4.9.4 doesn't link to  
/usr/local/bin/egcc

--- iodbc-3.52.12 ---
/usr/local/man/man1/iodbctestw.1 doesn't link to  
/usr/local/man/man1/iodbctest.1

--- libexecinfo-0.3p0v0 ---
/usr/local/man/man3/backtrace_symbols.3 doesn't link to  
/usr/local/man/man3/backtrace.3
/usr/local/man/man3/backtrace_symbols_fd.3 doesn't link to  
/usr/local/man/man3/backtrace.3

--- python-3.6.4 ---
/usr/local/bin/python3.6m doesn't link to /usr/local/bin/python3.6
.
.
.

In dbus-1.12.2p0v0:x11/dbus,-main:
/etc/machine-id
In isc-dhcp-server-4.3.6p0:net/isc-dhcp,-main:
/var/db/dhcpd.leases
In libxml-2.9.7:textproc/libxml,-main:
/var/db/xmlcatalog
In 

Re: Supermicro SuperServer E200-9A

[Rupert Gallagher]

Here is my take away of the day: avoid reading from Anton, because he jumped to 
conclusions about the C3000 series after his narrow experience with an Atom 
D525.

Note on the side: the C3000 introduced a patch to the known C2000 bug.

R

Re: Lenovo X130e blank video at boot.rd

[Stefan Sperling]

On Tue, Feb 27, 2018 at 04:53:06PM -0700, j...@bitminer.ca wrote:
> I am replacing my ancient X60 with an X130e of lesser age.  This model is
> previously found as working on misc.
> 
> When trying to install 6.2 (release) over Windows 10 there is no video to
> see.
> 
> By booting miniroot62.fs from USB the kernel loads, but the "OpenBSD 6.2
> " and subsequent boot messages do not appear.  The video is blank
> (apparently backlit but no text is present.)  The biosboot loader messages
> prior to that do appear for a few seconds.  The USB stick activity light
> does blink as if things are happening normally.
> 
> Same result for 6.1 and 5.9.
> 
> The three video options: Native video, VGA and HDMI video outputs show the
> same biosboot lines and then the screen blanks.  A couple of different
> monitors on the VGA output show "unsupported format" or somesuch suggesting
> the video signal is not a standard format.
> 
> There is no serial port on this hardware.  The BIOS is updated to the
> latest.  I'm going to try to obtain a dmesg with blindly typing against the
> install script (blessed OpenBSD with a simple install CLI!)
> 
> I'm wondering if there is something to be enabled/disabled in boot_config
> that would help.  I don't quite understand why video would blank out once
> the kernel gets control (src/sys/arch/amd64/amd64/consinit.c and machdep.c)
> since nothing looks like it is touching video configuration.  This seems to
> be way before any video driver gets control.
> 
> The Windows 10 "about" page says this is AMD E-450 APU with Radeon HD
> Graphics.  The Hardware page says "AMD Radeon HD 6320 Graphics".
> 
> Does anyone have further advice?
> 
> thanks
> 
> John
> 

My x130e has no problems booting -current miniroot62.fs from USB.
Video works fine ("ATI Radeon HD 6310"). dmesg below.

Did you boot from OpenBSd powered-off state or soft reboot after running
Windows? It's possible that Windows leaves devices in a state where
OpenBSD cannot use them.

BTW this machine used to be an E-450 as well, however something broke
on the mainboard so the system would not see the battery anymore.
At the time I could only find an E-300 mainboard to replace it but it's
been working fine since.

OpenBSD 6.2-current (RAMDISK_CD) #11: Tue Feb 27 17:20:47 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 3849388032 (3671MB)
avail mem = 3728969728 (3556MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf9d00 (58 entries)
bios0: vendor LENOVO version "8RET52WW (1.15 )" date 11/15/2011
bios0: LENOVO 305162G
acpi0 at bios0: rev 4
acpi0: tables DSDT FACP SLIC HPET APIC MCFG UEFI UEFI SSDT SSDT UEFI
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD E-300 APU with Radeon(tm) HD Graphics, 1297.51 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,RDTSCP,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: apic clock running at 199MHz
cpu0: mwait min=64, max=64, IBE
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PB4_)
acpiprt2 at acpi0: bus 1 (PB5_)
acpiprt3 at acpi0: bus 2 (PB6_)
acpiprt4 at acpi0: bus 3 (PB7_)
acpiprt5 at acpi0: bus 4 (P2P_)
acpiprt6 at acpi0: bus -1 (SPB0)
acpiprt7 at acpi0: bus -1 (SPB1)
acpiprt8 at acpi0: bus -1 (SPB2)
acpiprt9 at acpi0: bus -1 (SPB3)
acpiec0 at acpi0
acpicpu at acpi0 not configured
acpitz at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C0E" at acpi0 not configured
"LEN0026" at acpi0 not configured
"LEN0068" at acpi0 not configured
"ACPI0003" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"PNP0C0D" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 14h Host" rev 0x00
vga1 at pci0 dev 1 function 0 "ATI Radeon HD 6310" rev 0x00
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
"ATI Radeon HD 6310 HD Audio" rev 0x00 at pci0 dev 1 function 1 not configured
ppb0 at pci0 dev 5 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci1 at ppb0 bus 1
rtwn0 at pci1 dev 0 function 0 "Realtek 8188CE" rev 0x01: msi
rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R, address 9c:b7:0d:e1:11:6d
ppb1 at pci0 dev 6 function 0 "AMD AMD64 14h PCIE" rev 0x00: msi
pci2 at ppb1 bus 2
alc0 at pci2 dev 0 function 0 "Attansic Technology L1D" rev 0xc0: msi, address 
04:7d:7b:31:00:6e
atphy0 at alc0 phy 0: AR8035 10/100/1000 PHY, rev. 0
ppb2 at pci0 dev 7 function 0 "AMD AMD64 14h PCIE" 

Re: Please explain the pkg_check F option, thank you.

[Sebastien Marie]

On Wed, Feb 28, 2018 at 12:51:46PM +0100, Marc Espie wrote:
> On Tue, Feb 27, 2018 at 10:14:51PM +, Zsolt Kantor wrote:
> > What exactly does the pkg_check -F option?  If I use it, it does some 
> > filesystem check, and some "Locating unknown files".
> > 
> > At the end I get: "Locating unknown files: ok", "Locating unknown 
> > directories: ok", and a long list of "not found" directories and files, 
> > like below.
> > Not found:
> > /boot
> > /bsd
> > /bsd.rd
> > /bsd.sp
> > /bsd.syspatch61
> > /etc/X11/xenodm/authdir
> > . . . . 
> 
> Those are objects that are expected on a normal system, but that are not
> there, see the locate(8) dbs under /usr/lib/locate/src.db and 
> /usr/X11R6/lib/locate/xorg.db   
> 
> Not having /bsd and /bsd.rd   seems really strange.
> 

hum ? for me, it is the opposite.

pkg_check looks at {src,xorg}.db and PKG_DB for the list of expected
files. But these files aren't in these lists, so it reports them as "not
found" in the list of expected files.

For /bsd{,.rd} it is normal: the files don't come with usual sets but
are copied "as it".

-- 
Sebastien Marie

Re: Please explain the pkg_check F option, thank you.

[Marc Espie]

On Tue, Feb 27, 2018 at 10:14:51PM +, Zsolt Kantor wrote:
> What exactly does the pkg_check -F option?  If I use it, it does some 
> filesystem check, and some "Locating unknown files".
> 
> At the end I get: "Locating unknown files: ok", "Locating unknown 
> directories: ok", and a long list of "not found" directories and files, like 
> below.
> Not found:
> /boot
> /bsd
> /bsd.rd
> /bsd.sp
> /bsd.syspatch61
> /etc/X11/xenodm/authdir
> . . . . 

Those are objects that are expected on a normal system, but that are not
there, see the locate(8) dbs under /usr/lib/locate/src.db and 
/usr/X11R6/lib/locate/xorg.db   

Not having /bsd and /bsd.rd   seems really strange.