Re: OpenBSD 6.1 on Lenovo P50

2017-05-22 Thread ulises314 
> On Mon, May 22, 2017 at 07:29:53PM +0200, L. Jankok wrote:
>> Anybody running OpenBSD on a Lenovo P50 laptop?
>> I am looking for tips and experiences.
>
> I don't have one but I looked up the specs online.
>
> I would not recommend this machine for OpenBSD because it has
> an Nvidia GPU. If you can live with sloppy 2D graphics because
> all you're doing is typing into an xterm, then it might be tolerable.
> The Intel 8260 wifi card is supported so you'd have network.
>
> Intel and Radeon GPUs are more likely to be supported already
> (to some degree at least) and in the future. I would prefer
> models with such GPUs instead.
>
>

That's a pretty powerful laptop, why don't run openBSD in a virtual
machine?

Re: No 008 patch on ftp.eu.openbsd.org yet

2017-05-22 Thread Andreas Kusalananda Kähäri 
The mirror is now updated it seems, at least patch 008 is there.

Regards,
Kusalananada

On Sun, May 21, 2017 at 10:28:30AM +0200, Andreas Kusalananda Kähäri wrote:
> Hi,
> 
> I had to switch to ftp.openbsd.org to get the 008 patch for -stable
> since my preferred mirror, ftp.eu.openbsd.org, doesn't seem to be
> updating.  The timestamp file says last update was run on 1495188001
> (Fri May 19 12:00:01 CEST 2017).
> 
> There is no contact address in
> https://ftp.eu.openbsd.org/pub/OpenBSD/README so I'm hoping that someone
> who know someone who knows how the mirroring is performed will spot this
> and get them to fix it.
> 
> I would also be interested in knowing how often this mirror is
> *supposed* to update (usually it's something like every two hours,
> right?).
> 
> 
> 
> Regards,
> Kusalananda
>

Re: OpenBSD 6.1 on Lenovo P50

2017-05-22 Thread Stefan Sperling 
On Mon, May 22, 2017 at 07:29:53PM +0200, L. Jankok wrote:
> Anybody running OpenBSD on a Lenovo P50 laptop?
> I am looking for tips and experiences.

I don't have one but I looked up the specs online.

I would not recommend this machine for OpenBSD because it has
an Nvidia GPU. If you can live with sloppy 2D graphics because
all you're doing is typing into an xterm, then it might be tolerable.
The Intel 8260 wifi card is supported so you'd have network.

Intel and Radeon GPUs are more likely to be supported already
(to some degree at least) and in the future. I would prefer
models with such GPUs instead.

OpenBSD 6.1 on Lenovo P50

2017-05-22 Thread L. Jankok 
Hi there,

 

Anybody running OpenBSD on a Lenovo P50 laptop?

I am looking for tips and experiences.

 

Regards,

 

LJ

 

-- 

Shall artificial plants be given artificial water?

mime headers quoted-printable

2017-05-22 Thread Walter Alejandro Iglesias 
Hello everyone,

With mailx(1) in mind and resurrecting the few I know about C I wrote
the code pasted below.  It encodes mail headers in MIME quoted-printable
format.  Unless I'm missing something it complies with all stated here:

https://www.ietf.org/rfc/rfc2047.txt

You can pipe to it a line or the whole meassage, it only processes
headers leaving the body untouched.  The problem is, so far, it assumes
all 8bit chars are utf8.  Even when openbsd now only supports utf8
locale you can still enter iso-latin characters while your LC_CTYPE is
set to C, what means if eventually you judge it could be adapted to
patch mailx some non valid utf8 characters check would be mandatory.

So at this point I'm not sure it'll be a good deal since, as far as I
know, to make it able to check for non valid UTF-8 characters would take
more lines of code than the program itself.

I wrote also an encoder to the body, a base64 version and some decoders
but for now I'll show you only this one to not clutter the message.

I'd appreciate your opinion and advice about what can I do from now
(don't hesitate in being frank if you think it's useless).


/*
 * MIME encode mail headers quoted-printable.
 *
 * BUG: it assumes all non ascii characters are UTF-8.
 */

#include 

#define ASCII   0x7f
#define IN  1
#define OUT 0

int
main()
{
int c, i, n, nl, eightbit, encode, body;
unsigned char s[256];

i = n = nl = 0;
encode = eightbit = body = OUT;

while ((c = getchar()) != EOF) {
if (body == IN)
putchar(c);
else if (c == '\n' || c == ' ') {
s[i] = '\0';
if (eightbit == IN) {
if (encode == IN)
printf("=20?= ");
printf("=?UTF-8?Q?");
while (n < i) {
if (s[n] > ASCII ||
s[n] == '=' ||
s[n] == '?' ||
s[n] == '\t') {
printf("=%02X", s[n]);
} else
printf("%c", s[n]);
++n;
}
n = 0;
encode = IN;

if (c == '\n') {
printf("?=");
putchar(c);
encode = OUT;
}

eightbit = OUT;
} else {
if (encode == IN)
printf("?= ");
printf("%s", s);
putchar(c);
encode = OUT;
}
i = 0;
if (c == '\n')
++nl;
else
nl = 0;
if (nl > 1)
body = IN;
} else {
if (c > ASCII)
eightbit = IN;
s[i] = c;
++i;
}
}

return 0;
}

Re: old macbook not resuming X

2017-05-22 Thread Nils Reuße 
> Jan Stary  hat am 22. Mai 2017 um 10:41 geschrieben:
> 
> 
> Sorry for the long post.
> 
> This is current/amd64 on a MacBook2,1 (model A1181), dmesg below.
> I experience the same on a MacBook1,1 running current/i386.
> 
> On the console, each of apm -S -z -Z works, closing the lid as well.
> Each of them also resumes as expected.
> 
> On the other hand, trying to get to sleep from an xterm
> (via apm -S or -z or -Z) does not fully resume: upon resuming,
> X gets killed, the console keyboard does not reconnect properly,
> and keyboard input becomes garbage.  There is nothing to do but
> press the power button to reboot. (Or do it remotely.)
> 
> As the symptoms are the same for standby, suspend and hibernate,
> I will use suspend (apm -z) in the examples.
> 
> /var/log/messages of the console resume (good)
> and the X resume (bad) seem mostly the same (both below),
> except the naming order of the u* device being (re)attached;
> and the messages from the X suspend have some extra newlines
> in the middle of the message lines (which seems strange).
> Here is the diff lines (minus the leading timestamps):
> 
>   --- apm.goodMon May 22 09:45:56 2017
>   +++ apm.bad Mon May 22 09:46:00 2017
> 
>   -uhub0 detached
>   +uhub2 detached
> 
>   -uhub2 detached
>   +uhub3 detached
> 
>   -uhub3 detached
>   +uhub4 detached
> 
>   -uhub4 detached
>   +uhub0 detached
> 
>   -uhidev1 at uhub0 port 2 configuration 1 interface 1 "Apple Computer Apple 
> Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
>   +uhidev1 at uhub0
>   + port 2 configuration 1 interface 1 "Apple Computer Apple Internal 
> Keyboard / Trackpad" rev 2.00/0.18 addr 2
> 
>   -uhid2 at uhidev3 reportid 37: input=4, output=0, feature=0
>   +uhid2 at uhidev3 reportid 37
>   +: input=4, output=0, feature=0
> 
> 
> Please also see the Xorg log of the killed X session below.
> Firstly, it complains about /dev/xf86 and /dev/mem
> and asks for 'machdep.allowaperture=1'.
> 
>   (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
> (Operation not permitted)
> Check that you have set 'machdep.allowaperture=1'
> 
> Is that expected with inteldrm(4)?
> Is that related to the following drm errors in dmesg?
> Can it be related to the X not resuming?
> 
> drm: render error detected, EIR: 0x0010
> drm: page table error
> drm:   PGTBL_ER: 0x0102
> error: [drm:pid0:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, 
> masking
> drm: render error detected, EIR: 0x0010
> drm: page table error
> drm:   PGTBL_ER: 0x0102
> 
> The X log also says:
> 
>   (II) The server relies on wscons to provide the list of input devices.
>   If no devices become available, reconfigure wscons or disable 
> AutoAddDevices.
> 
> and later ends (when X gets killed upon resume) with
> 
>   Fatal server error:
>   [   257.752] (EE) can't switch keyboard to raw mode.
>   Enable support for it in the kernel or use for example:
> 
> Option "Protocol" "wskbd"
> Option "Device" "/dev/wskbd0"
> 
>   in your xorg.conf(5) file
> 
> 
> I don't have a xorg.conf, because X works just fine beside this.
> Apparently, it has something to do with reattaching the wskbd,
> but that's way over my head. How do I enable support for
> "raw keyboard mode" in the kernel (it that's my problem)?
> 
> How can I help debug this?
> 
>   Jan
> 
> 
> boot dmesg:
> 
> OpenBSD 6.1-current (GENERIC.MP) #0: Sat May 20 12:31:37 CEST 2017
> h...@macbook.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 3171909632 (3024MB)
> avail mem = 3070050304 (2927MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
> bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
> bios0: Apple Inc. MacBook2,1
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
> acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
> USB3(S3) USB4(S3) USB7(S3) EC__(S3)
> 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)2 CPU T7400 @ 2.16GHz, 2161.65 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
> cpu0: 4MB 64b/line 16-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
> cpu0: apic clock running at 166MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.25 MHz
> cpu1: 
>

X without a keyboard

2017-05-22 Thread Stuart Henderson 
Unsure if this is considered a bug or not, but does anyone know of a way
to get X to start without a keyboard device?

$ cat /var/log/Xorg.0.log.old
[29.180] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'
in /etc/sysctl.conf and reboot your machine
refer to xf86(4) for details
[29.180]linear framebuffer access unavailable
[29.186] (--) Using wscons driver on /dev/ttyC4
[29.194] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[29.194] X Protocol Version 11, Revision 0
[29.194] Build Operating System: OpenBSD 6.1 amd64 
[29.194] Current Operating System: OpenBSD nuc-49-158.telebizz.co.uk 6.1 
GENERIC.MP#4 amd64
[29.194] Build Date: 01 April 2017  02:00:27PM
[29.194]  
[29.194] Current version of pixman: 0.34.0
[29.194]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[29.194] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[29.194] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 22 09:08:29 
2017
[29.196] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[29.197] (==) No Layout section.  Using the first Screen section.
[29.197] (==) No screen section available. Using defaults.
[29.197] (**) |-->Screen "Default Screen Section" (0)
[29.197] (**) |   |-->Monitor ""
[29.197] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[29.198] (==) Disabling SIGIO handlers for input devices
[29.198] (==) Automatically adding devices
[29.198] (==) Automatically enabling devices
[29.198] (==) Not automatically adding GPU devices
[29.198] (==) Max clients allowed: 256, resource mask: 0x1f
[29.205] (==) 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/
[29.205] (==) ModulePath set to "/usr/X11R6/lib/modules"
[29.205] (II) The server relies on wscons to provide the list of input 
devices.
If no devices become available, reconfigure wscons or disable 
AutoAddDevices.
[29.206] (II) Loader magic: 0xd8342e33020
[29.206] (II) Module ABI versions:
[29.206]X.Org ANSI C Emulation: 0.4
[29.206]X.Org Video Driver: 20.0
[29.206]X.Org XInput driver : 22.1
[29.206]X.Org Server Extension : 9.0
[29.206] (--) PCI:*(0:0:2:0) 8086:0a16:8086:2054 rev 9, Mem @ 
0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64
[29.206] (II) LoadModule: "glx"
[29.209] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
[29.218] (II) Module glx: vendor="X.Org Foundation"
[29.218]compiled for 1.18.4, module version = 1.0.0
[29.218]ABI class: X.Org Server Extension, version 9.0
[29.219] (==) AIGLX enabled
[29.219] (==) Matched intel as autoconfigured driver 0
[29.219] (==) Matched vesa as autoconfigured driver 1
[29.219] (==) Assigned the driver to the xf86ConfigLayout
[29.219] (II) LoadModule: "intel"
[29.219] (II) Loading /usr/X11R6/lib/modules/drivers/intel_drv.so
[29.222] (II) Module intel: vendor="X.Org Foundation"
[29.222]compiled for 1.18.4, module version = 2.99.916
[29.222]Module class: X.Org Video Driver
[29.222]ABI class: X.Org Video Driver, version 20.0
[29.222] (II) LoadModule: "vesa"
[29.222] (II) Loading /usr/X11R6/lib/modules/drivers/vesa_drv.so
[29.223] (II) Module vesa: vendor="X.Org Foundation"
[29.223]compiled for 1.18.4, module version = 2.3.4
[29.223]Module class: X.Org Video Driver
[29.223]ABI class: X.Org Video Driver, version 20.0
[29.223] (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
[29.223] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[29.223] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[29.223] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, 
P6300
[29.223] (II) VESA: driver for VESA chipsets: vesa
[29.225] (II) intel(0): Using Kernel Mode Setting driver: i915, version 
1.6.0 20080730
[29.226] (WW) Falling back to old probe method for vesa
[29.227] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 
4400
[29.227] (--) intel(0): CPU: x86-64, sse2, sse3,

Re: shouldn't ping -I bypass all normal routing?

2017-05-22 Thread Gregory Edigarov 



On 21.05.17 17:16, Stuart Henderson wrote:

On 2017-05-19, Gregory Edigarov  wrote:

Hi, everybody

I've run into a strange problem while trying to implement cisco's 'ip
sla' replacement for a customer.

at an openbsd router i have

em0: 192.168.0.1/24 - local network

em1: 111.111.111.2/30 - uplink 1

em2: 222.222.222.2/30 - uplink 2

ip forwarding is on, routes received via bgp, everything work as expected.

the only problem is when something happens deep inside uplink's network:

sessions stay up, routes still present, but no traffic can pass though
uplink.

BFD would help, may be, but I stick to what i have right now.

I am trying to
ping -I 111.111.111.2 8.8.8.8

but get no answer, because route to 8.8.8.8 set through uplink2, furthermore

i see my pings on em2 with tcpdump which seems rather strange to me, as
I am enforcing the interface.

if i ping 8.8.8.8 the normal way "it works" (tm).

pinging with -I 222.222.222.2 works too.

so ?

perhaps I am overlooking something very-very basic, so help me to get
off the brake.

ping -I doesn't enforce the interface, all it does is set the source
address.  You could enforce with a PF route-to rule if you like.
well, it's ok, but then I will need to switch rules every time like:  
ping uplink1, switch pf rule, ping, switch. which is not good.
but may be i will be able to implement something with multiple routing 
tables

anyway thanks, Stuart.

old macbook not resuming X

2017-05-22 Thread Jan Stary 
Sorry for the long post.

This is current/amd64 on a MacBook2,1 (model A1181), dmesg below.
I experience the same on a MacBook1,1 running current/i386.

On the console, each of apm -S -z -Z works, closing the lid as well.
Each of them also resumes as expected.

On the other hand, trying to get to sleep from an xterm
(via apm -S or -z or -Z) does not fully resume: upon resuming,
X gets killed, the console keyboard does not reconnect properly,
and keyboard input becomes garbage.  There is nothing to do but
press the power button to reboot. (Or do it remotely.)

As the symptoms are the same for standby, suspend and hibernate,
I will use suspend (apm -z) in the examples.

/var/log/messages of the console resume (good)
and the X resume (bad) seem mostly the same (both below),
except the naming order of the u* device being (re)attached;
and the messages from the X suspend have some extra newlines
in the middle of the message lines (which seems strange).
Here is the diff lines (minus the leading timestamps):

  --- apm.good  Mon May 22 09:45:56 2017
  +++ apm.bad   Mon May 22 09:46:00 2017

  -uhub0 detached
  +uhub2 detached

  -uhub2 detached
  +uhub3 detached

  -uhub3 detached
  +uhub4 detached

  -uhub4 detached
  +uhub0 detached

  -uhidev1 at uhub0 port 2 configuration 1 interface 1 "Apple Computer Apple 
Internal Keyboard / Trackpad" rev 2.00/0.18 addr 2
  +uhidev1 at uhub0
  + port 2 configuration 1 interface 1 "Apple Computer Apple Internal Keyboard 
/ Trackpad" rev 2.00/0.18 addr 2

  -uhid2 at uhidev3 reportid 37: input=4, output=0, feature=0
  +uhid2 at uhidev3 reportid 37
  +: input=4, output=0, feature=0


Please also see the Xorg log of the killed X session below.
Firstly, it complains about /dev/xf86 and /dev/mem
and asks for 'machdep.allowaperture=1'.

  (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem
(Operation not permitted)
Check that you have set 'machdep.allowaperture=1'

Is that expected with inteldrm(4)?
Is that related to the following drm errors in dmesg?
Can it be related to the X not resuming?

drm: render error detected, EIR: 0x0010
drm: page table error
drm:   PGTBL_ER: 0x0102
error: [drm:pid0:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, 
masking
drm: render error detected, EIR: 0x0010
drm: page table error
drm:   PGTBL_ER: 0x0102

The X log also says:

  (II) The server relies on wscons to provide the list of input devices.
  If no devices become available, reconfigure wscons or disable AutoAddDevices.

and later ends (when X gets killed upon resume) with

  Fatal server error:
  [   257.752] (EE) can't switch keyboard to raw mode.
  Enable support for it in the kernel or use for example:

Option "Protocol" "wskbd"
Option "Device" "/dev/wskbd0"

  in your xorg.conf(5) file


I don't have a xorg.conf, because X works just fine beside this.
Apparently, it has something to do with reattaching the wskbd,
but that's way over my head. How do I enable support for
"raw keyboard mode" in the kernel (it that's my problem)?

How can I help debug this?

Jan


boot dmesg:

OpenBSD 6.1-current (GENERIC.MP) #0: Sat May 20 12:31:37 CEST 2017
h...@macbook.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3171909632 (3024MB)
avail mem = 3070050304 (2927MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (37 entries)
bios0: vendor Apple Inc. version "MB21.88Z.00A5.B07.0706270922" date 06/27/07
bios0: Apple Inc. MacBook2,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices ADP1(S3) LID0(S3) PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB7(S3) EC__(S3)
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)2 CPU T7400 @ 2.16GHz, 2161.65 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu0: 4MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz, 2161.25 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,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR
cpu1: 4MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2

Fatture insolute?

2017-05-22 Thread Consmos Consulting