Re: Screen brightness is reset when changing from X to console
On Mon, May 30, 2016 at 05:02:07PM +0200, Walter Alejandro Iglesias wrote: > Jonathan Gray wrote: > > > On Mon, May 30, 2016 at 02:41:59PM +0200, Walter Alejandro Iglesias wrote: > > > Stefan Sperling wrote: > > > > > > > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > > > > > And I can't reproduce this on my x220. So either this issue depends > > > > > on > > > > > specific BIOS revisions, or the description of how to reproduce the > > > > > problem > > > > > is incomplete. > > > > > > > > I've been seeing it on my x201 for a while. > > > > > > > > Isn't this the same issue as was discussed in the "ACPI thinkpad > > > > brightness > > > > regression" thread back in Feburary? It seems this was never resolved. > > > > http://marc.info/?t=14550124442&r=1&w=2 > > > > > > I've found out that setting UXA acceleration in xorg.conf solves not > > > only this issue but the one about cwm menu fonts corruption I reported > > > on May 21th. So, am I wrong assuming it's not an acpi issue but a intel > > > driver one? (Sorry if I can't be more useful, my knowledge is poor). > > > > > > But, using UXA it appears a new issue. When I exit X, I end with a > > > black empty screen and I must change manually to tty1. X shows the > > > error below: > > > > > > --- > > > X.Org X Server 1.18.3 > > > Release Date: 2016-04-04 > > > X Protocol Version 11, Revision 0 > > > Build Operating System: OpenBSD 6.0 amd64 > > > Current Operating System: OpenBSD mamuca.local 6.0 GENERIC.MP#2142 amd64 > > > Build Date: 30 May 2016 12:02:37AM > > > > > > Current version of pixman: 0.32.8 > > > Before reporting problems, check http://wiki.x.org > > > to make sure that you have the latest version. > > > Markers: (--) probed, (**) from config file, (==) default setting, > > > (++) from command line, (!!) notice, (II) informational, > > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 30 14:22:58 2016 > > > (==) Using config file: "/etc/X11/xorg.conf" > > > (II) AIGLX: Suspending AIGLX clients for VT switch > > > xinit: connection to X server lost > > > > > > waiting for X server to shut down > > > X:/usr/X11R6/lib/modules/drivers/intel_drv.so: undefined symbol > > > 'intel_sync_close' > > > lazy binding failed! > > > (EE) Segmentation fault at address 0x0 > > > (EE) > > > Fatal server error: > > > (EE) Caught signal 11 (Segmentation fault). Server aborting > > > (EE) > > > (EE) > > > Please consult the The X.Org Foundation support > > >at http://wiki.x.org > > > for help. > > > (EE) Please also check the log file at "/var/log/Xorg.0.log" for > > > additional information. > > > (EE) > > > (EE) Bus error at address 0x1b427e38efd4 > > > (EE) > > > FatalError re-entered, aborting > > > (EE) Caught signal 10 (Bus error). Server aborting > > > (EE) > > > --- > > > > > > (I've upgraded today to latest snapshot) > > > > Here's a diff that might help, compile tested only: > > > > Index: src/uxa/intel_driver.c > > === > > RCS file: /cvs/xenocara/driver/xf86-video-intel/src/uxa/intel_driver.c,v > > retrieving revision 1.2 > > diff -u -p -r1.2 intel_driver.c > > --- src/uxa/intel_driver.c 12 Apr 2015 19:42:07 - 1.2 > > +++ src/uxa/intel_driver.c 30 May 2016 13:08:02 - > > @@ -1188,7 +1188,9 @@ static Bool I830CloseScreen(CLOSE_SCREEN > > intel->dri3 = DRI_NONE; > > } > > > > +#if HAVE_DRI3 > > intel_sync_close(screen); > > +#endif > > > > xf86GARTCloseScreen(scrn->scrnIndex); > > > > YES! > > It took me a while because it's my first time compiling cvs xenocara. I > can confirm that at least at my end Jonathan's diff solves the intel UXA > issue I mentioned in my last message. > > Using UXA, changing to ttys from X is flawless, it doesn't affect the > screen brightness at all. > > Now, my question is, may I expect this diff be applied in default > xenocara build? Thanks for testing, I've committed this now and it will be in future snapshots.
Re: Screen brightness is reset when changing from X to console
Jonathan Gray wrote: > On Mon, May 30, 2016 at 02:41:59PM +0200, Walter Alejandro Iglesias wrote: > > Stefan Sperling wrote: > > > > > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > > > > And I can't reproduce this on my x220. So either this issue depends on > > > > specific BIOS revisions, or the description of how to reproduce the > > > > problem > > > > is incomplete. > > > > > > I've been seeing it on my x201 for a while. > > > > > > Isn't this the same issue as was discussed in the "ACPI thinkpad > > > brightness > > > regression" thread back in Feburary? It seems this was never resolved. > > > http://marc.info/?t=14550124442&r=1&w=2 > > > > I've found out that setting UXA acceleration in xorg.conf solves not > > only this issue but the one about cwm menu fonts corruption I reported > > on May 21th. So, am I wrong assuming it's not an acpi issue but a intel > > driver one? (Sorry if I can't be more useful, my knowledge is poor). > > > > But, using UXA it appears a new issue. When I exit X, I end with a > > black empty screen and I must change manually to tty1. X shows the > > error below: > > > > --- > > X.Org X Server 1.18.3 > > Release Date: 2016-04-04 > > X Protocol Version 11, Revision 0 > > Build Operating System: OpenBSD 6.0 amd64 > > Current Operating System: OpenBSD mamuca.local 6.0 GENERIC.MP#2142 amd64 > > Build Date: 30 May 2016 12:02:37AM > > > > Current version of pixman: 0.32.8 > > Before reporting problems, check http://wiki.x.org > > to make sure that you have the latest version. > > Markers: (--) probed, (**) from config file, (==) default setting, > > (++) from command line, (!!) notice, (II) informational, > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 30 14:22:58 2016 > > (==) Using config file: "/etc/X11/xorg.conf" > > (II) AIGLX: Suspending AIGLX clients for VT switch > > xinit: connection to X server lost > > > > waiting for X server to shut down > > X:/usr/X11R6/lib/modules/drivers/intel_drv.so: undefined symbol > > 'intel_sync_close' > > lazy binding failed! > > (EE) Segmentation fault at address 0x0 > > (EE) > > Fatal server error: > > (EE) Caught signal 11 (Segmentation fault). Server aborting > > (EE) > > (EE) > > Please consult the The X.Org Foundation support > > at http://wiki.x.org > > for help. > > (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional > > information. > > (EE) > > (EE) Bus error at address 0x1b427e38efd4 > > (EE) > > FatalError re-entered, aborting > > (EE) Caught signal 10 (Bus error). Server aborting > > (EE) > > --- > > > > (I've upgraded today to latest snapshot) > > Here's a diff that might help, compile tested only: > > Index: src/uxa/intel_driver.c > === > RCS file: /cvs/xenocara/driver/xf86-video-intel/src/uxa/intel_driver.c,v > retrieving revision 1.2 > diff -u -p -r1.2 intel_driver.c > --- src/uxa/intel_driver.c12 Apr 2015 19:42:07 - 1.2 > +++ src/uxa/intel_driver.c30 May 2016 13:08:02 - > @@ -1188,7 +1188,9 @@ static Bool I830CloseScreen(CLOSE_SCREEN > intel->dri3 = DRI_NONE; > } > > +#if HAVE_DRI3 > intel_sync_close(screen); > +#endif > > xf86GARTCloseScreen(scrn->scrnIndex); > YES! It took me a while because it's my first time compiling cvs xenocara. I can confirm that at least at my end Jonathan's diff solves the intel UXA issue I mentioned in my last message. Using UXA, changing to ttys from X is flawless, it doesn't affect the screen brightness at all. Now, my question is, may I expect this diff be applied in default xenocara build? Walter
Re: Screen brightness is reset when changing from X to console
On Mon, May 30, 2016 at 02:41:59PM +0200, Walter Alejandro Iglesias wrote: > Stefan Sperling wrote: > > > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > > > And I can't reproduce this on my x220. So either this issue depends on > > > specific BIOS revisions, or the description of how to reproduce the > > > problem > > > is incomplete. > > > > I've been seeing it on my x201 for a while. > > > > Isn't this the same issue as was discussed in the "ACPI thinkpad brightness > > regression" thread back in Feburary? It seems this was never resolved. > > http://marc.info/?t=14550124442&r=1&w=2 > > I've found out that setting UXA acceleration in xorg.conf solves not > only this issue but the one about cwm menu fonts corruption I reported > on May 21th. So, am I wrong assuming it's not an acpi issue but a intel > driver one? (Sorry if I can't be more useful, my knowledge is poor). > > But, using UXA it appears a new issue. When I exit X, I end with a > black empty screen and I must change manually to tty1. X shows the > error below: > > --- > X.Org X Server 1.18.3 > Release Date: 2016-04-04 > X Protocol Version 11, Revision 0 > Build Operating System: OpenBSD 6.0 amd64 > Current Operating System: OpenBSD mamuca.local 6.0 GENERIC.MP#2142 amd64 > Build Date: 30 May 2016 12:02:37AM > > Current version of pixman: 0.32.8 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 30 14:22:58 2016 > (==) Using config file: "/etc/X11/xorg.conf" > (II) AIGLX: Suspending AIGLX clients for VT switch > xinit: connection to X server lost > > waiting for X server to shut down > X:/usr/X11R6/lib/modules/drivers/intel_drv.so: undefined symbol > 'intel_sync_close' > lazy binding failed! > (EE) Segmentation fault at address 0x0 > (EE) > Fatal server error: > (EE) Caught signal 11 (Segmentation fault). Server aborting > (EE) > (EE) > Please consult the The X.Org Foundation support >at http://wiki.x.org > for help. > (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional > information. > (EE) > (EE) Bus error at address 0x1b427e38efd4 > (EE) > FatalError re-entered, aborting > (EE) Caught signal 10 (Bus error). Server aborting > (EE) > --- > > (I've upgraded today to latest snapshot) Here's a diff that might help, compile tested only: Index: src/uxa/intel_driver.c === RCS file: /cvs/xenocara/driver/xf86-video-intel/src/uxa/intel_driver.c,v retrieving revision 1.2 diff -u -p -r1.2 intel_driver.c --- src/uxa/intel_driver.c 12 Apr 2015 19:42:07 - 1.2 +++ src/uxa/intel_driver.c 30 May 2016 13:08:02 - @@ -1188,7 +1188,9 @@ static Bool I830CloseScreen(CLOSE_SCREEN intel->dri3 = DRI_NONE; } +#if HAVE_DRI3 intel_sync_close(screen); +#endif xf86GARTCloseScreen(scrn->scrnIndex);
Re: Screen brightness is reset when changing from X to console
Stefan Sperling wrote: > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > > And I can't reproduce this on my x220. So either this issue depends on > > specific BIOS revisions, or the description of how to reproduce the problem > > is incomplete. > > I've been seeing it on my x201 for a while. > > Isn't this the same issue as was discussed in the "ACPI thinkpad brightness > regression" thread back in Feburary? It seems this was never resolved. > http://marc.info/?t=14550124442&r=1&w=2 I've found out that setting UXA acceleration in xorg.conf solves not only this issue but the one about cwm menu fonts corruption I reported on May 21th. So, am I wrong assuming it's not an acpi issue but a intel driver one? (Sorry if I can't be more useful, my knowledge is poor). But, using UXA it appears a new issue. When I exit X, I end with a black empty screen and I must change manually to tty1. X shows the error below: --- X.Org X Server 1.18.3 Release Date: 2016-04-04 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 6.0 amd64 Current Operating System: OpenBSD mamuca.local 6.0 GENERIC.MP#2142 amd64 Build Date: 30 May 2016 12:02:37AM Current version of pixman: 0.32.8 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 30 14:22:58 2016 (==) Using config file: "/etc/X11/xorg.conf" (II) AIGLX: Suspending AIGLX clients for VT switch xinit: connection to X server lost waiting for X server to shut down X:/usr/X11R6/lib/modules/drivers/intel_drv.so: undefined symbol 'intel_sync_close' lazy binding failed! (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Bus error at address 0x1b427e38efd4 (EE) FatalError re-entered, aborting (EE) Caught signal 10 (Bus error). Server aborting (EE) --- (I've upgraded today to latest snapshot) Walter
Re: Screen brightness is reset when changing from X to console
On Sun, May 29, 2016 at 11:22:44PM +0200, Stefan Sperling wrote: > On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > > And I can't reproduce this on my x220. So either this issue depends on > > specific BIOS revisions, or the description of how to reproduce the problem > > is incomplete. > > I've been seeing it on my x201 for a while. > > Isn't this the same issue as was discussed in the "ACPI thinkpad brightness > regression" thread back in Feburary? It seems this was never resolved. > http://marc.info/?t=14550124442&r=1&w=2 It looks similar. I also see the same on my x230 but I've never found a proper way to reproduce it :-/ -- Antoine
Re: Screen brightness is reset when changing from X to console
On Sun, May 29, 2016 at 09:19:58PM +0200, Mark Kettenis wrote: > And I can't reproduce this on my x220. So either this issue depends on > specific BIOS revisions, or the description of how to reproduce the problem > is incomplete. I've been seeing it on my x201 for a while. Isn't this the same issue as was discussed in the "ACPI thinkpad brightness regression" thread back in Feburary? It seems this was never resolved. http://marc.info/?t=14550124442&r=1&w=2
Re: Screen brightness is reset when changing from X to console
Mark Kettenis wrote:
> So please be specific about your software environment (xdm or startx,
> window manager, etc.) and see if you can reproduce this with a
> minimal/default environment (startx + fvwm).
Running xinit (or startx) I could reproduce it using cwm, fvwm, fvwm2 and twm.
# ~/.xinitrc
export XLIB_SKIP_ARGB_VISUALS=1
export GTK2_RC_FILES="$HOME/.gtkrc-2.0"
export GDK_USE_XFT=1
export MOZ_DISABLE_PANGO=1
export LC_CTYPE=en_US.UTF-8
cwm_init()
{
bg='rgb:5/5/5'
fg='rgb:c/c/c'
height='24'
font=fixed
xsetroot -solid $bg
LC_CTYPE=C xclock -name docked-xclock -fg $fg -bg $bg \
-norender -font $font -digital -padding 5 \
-strftime "%A, %b %e %H:%M:%S" \
-geometry 166x${height}-0+0 &
LC_CTYPE=C xbiff -name docked-xbiff -bg $bg -fg $fg \
-geometry 28x${height}-180+0 &
LC_CTYPE=C xload -name docked-xload -bg $bg -fg $fg \
-hl $bg -nolabel -geometry 28x${height}-220+0 &
exec cwm
}
setxkbmap -model "pc105" -variant "basic" es -option "terminate:ctrl_alt_bksp"
synclient TouchpadOff=1
which xcalib >/dev/null 2>&1 && xcalib $HOME/.icc-profiles/tft.icc
xset r rate 200 50
xset mouse 0
#exec fvwm2
cwm_init
# End of ~/.xinitrc
>
> Cheers,
>
> Mark
>
>
Walter
Screen brightness is reset when changing from X to console
>Synopsis:
Screen brightness is reset when changing from X to console
>Category:
system
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-beta (GENERIC.MP) #2131: Fri May 27 21:04:15
MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
>Description:
When changing from X to console using keyboard shortcuts or
exiting X the screen brightness is reset to a very low
percentage (38%).
>How-To-Repeat:
Exiting X or changing to a tty using keyboard shortcuts (CM-Fn).
>Fix:
Unknown (adding display.brightness=50 to /etc/wsconsctl.conf
doesn't help).
dmesg:
OpenBSD 6.0-beta (GENERIC.MP) #2131: Fri May 27 21:04:15 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 6210174976 (5922MB)
avail mem = 6017359872 (5738MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version "6IET85WW (1.45 )" date 02/14/2013
bios0: LENOVO 2537EY8
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA SSDT
SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2793.52 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,SSE4.1,SSE4.2,POPCNT,AES,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, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 132MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2793.00 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,SSE4.1,SSE4.2,POPCNT,AES,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 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2793.00 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,SSE4.1,SSE4.2,POPCNT,AES,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 5 (application processor)
cpu3: Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, 2793.00 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,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 2, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
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 -1 (EXP3)
acpiprt5 at acpi0: bus 5 (EXP4)
acpiprt6 at acpi0: bus 13 (EXP5)
acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10),
C1(1000@3 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 100 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"PNP0303" at acpi0 not configured
"LEN0015" at acpi0 not configured
"SMO1200" at acpi0 not configured
acpibat0 at acpi0: BAT0 not present
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"*pnp0c14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: VID_
acpivout0 at acpivideo0: LCD0
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2793 MHz: speeds: 2534, 2533, 2399, 2266, 2133, 1999,
1866, 1733, 1599, 1466, 1333, 1199 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core Host" rev 0x02
inteldrm0 at pci0 dev 2 f
