* has the i915 "black screen" boot issue returned?
@ 2011-01-26 11:37 Robert P. J. Day
2011-01-27 10:15 ` Chris Wilson
0 siblings, 1 reply; 49+ messages in thread
From: Robert P. J. Day @ 2011-01-26 11:37 UTC (permalink / raw)
To: dri-devel
after suffering through the i915 "black screen" issue for a while,
it was a relief that it finally seemed to be resolved with 2.6.37 or
something in tha vicinity. but i just built and booted a 2.6.38-rc2+
kernel on my ubuntu 10.10 system and it once again boots to a black
screen.
is this a new known issue? has anyone else seen this?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 49+ messages in thread* Re: has the i915 "black screen" boot issue returned? 2011-01-26 11:37 has the i915 "black screen" boot issue returned? Robert P. J. Day @ 2011-01-27 10:15 ` Chris Wilson 2011-01-27 10:37 ` Robert P. J. Day 2011-01-27 11:47 ` Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-27 10:15 UTC (permalink / raw) To: Robert P. J. Day, dri-devel On Wed, 26 Jan 2011 06:37:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > after suffering through the i915 "black screen" issue for a while, > it was a relief that it finally seemed to be resolved with 2.6.37 or > something in tha vicinity. but i just built and booted a 2.6.38-rc2+ > kernel on my ubuntu 10.10 system and it once again boots to a black > screen. > > is this a new known issue? has anyone else seen this? It all depends. There is a new ACPI backlight issue causing grief, aside from that and lingering issues with the legacy backlight combination mode, I don't think there was a new i915 KMS regression. (We had regressions elsewhere and finally fixed up a few old regressions for UMS and DRI1 and various other OOPS-on-boot. And suspend is a bit hit and miss.) For extra fun, it appears that sched_autocgroup can trigger a leak of pinned bo eventually hitting a BUG. That's one I'm keen to reproduce. Without knowing your chipset and seeing a dmesg, I can only guess which problem you are most likely to have hit. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 10:15 ` Chris Wilson @ 2011-01-27 10:37 ` Robert P. J. Day 2011-01-27 11:47 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 10:37 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Wed, 26 Jan 2011 06:37:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > after suffering through the i915 "black screen" issue for a while, > > it was a relief that it finally seemed to be resolved with 2.6.37 or > > something in tha vicinity. but i just built and booted a 2.6.38-rc2+ > > kernel on my ubuntu 10.10 system and it once again boots to a black > > screen. > > > > is this a new known issue? has anyone else seen this? > > It all depends. There is a new ACPI backlight issue causing grief, > aside from that and lingering issues with the legacy backlight > combination mode, I don't think there was a new i915 KMS regression. > (We had regressions elsewhere and finally fixed up a few old > regressions for UMS and DRI1 and various other OOPS-on-boot. And > suspend is a bit hit and miss.) > > For extra fun, it appears that sched_autocgroup can trigger a leak of > pinned bo eventually hitting a BUG. That's one I'm keen to reproduce. > > Without knowing your chipset and seeing a dmesg, I can only guess which > problem you are most likely to have hit. if i have time today, i'll try to bisect. i've built a 2.6.38-rc2 kernel and that seems to work fine. more in a bit while i track this down. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 10:15 ` Chris Wilson 2011-01-27 10:37 ` Robert P. J. Day @ 2011-01-27 11:47 ` Robert P. J. Day 2011-01-27 11:56 ` Chris Wilson 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 11:47 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Wed, 26 Jan 2011 06:37:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > after suffering through the i915 "black screen" issue for a while, > > it was a relief that it finally seemed to be resolved with 2.6.37 or > > something in tha vicinity. but i just built and booted a 2.6.38-rc2+ > > kernel on my ubuntu 10.10 system and it once again boots to a black > > screen. > > > > is this a new known issue? has anyone else seen this? > > It all depends. There is a new ACPI backlight issue causing grief, aside > from that and lingering issues with the legacy backlight combination mode, > I don't think there was a new i915 KMS regression. (We had regressions > elsewhere and finally fixed up a few old regressions for UMS and DRI1 and > various other OOPS-on-boot. And suspend is a bit hit and miss.) > > For extra fun, it appears that sched_autocgroup can trigger a leak of > pinned bo eventually hitting a BUG. That's one I'm keen to reproduce. > > Without knowing your chipset and seeing a dmesg, I can only guess which > problem you are most likely to have hit. here's a little more info if it's helpful. from "lspci -v": 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 031c Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at d0000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 3050 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 also, i just verified that i have a properly booting kernel based on this commit: commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 Author: Alex Deucher <alexdeucher@gmail.com> Date: Mon Jan 24 17:14:26 2011 -0500 drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq Needed for timer queries in the 3D driver. Signed-off-by: Alex Deucher <alexdeucher@gmail.com> Signed-off-by: Dave Airlie <airlied@gmail.com> i chose that commit since, right after that, there are a couple commits that are heavily i915-related: abb72c828878a2c69b2cfb33ac30007c8ecd735e 5e82ea99827f6aa122fbb08f8659e76226ce107b and those would be the next things i check. is there any other info you'd like to see? rday ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 11:47 ` Robert P. J. Day @ 2011-01-27 11:56 ` Chris Wilson 2011-01-27 12:12 ` Robert P. J. Day 0 siblings, 1 reply; 49+ messages in thread From: Chris Wilson @ 2011-01-27 11:56 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Thu, 27 Jan 2011 06:47:23 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > also, i just verified that i have a properly booting kernel based on > this commit: > > commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 > Author: Alex Deucher <alexdeucher@gmail.com> > Date: Mon Jan 24 17:14:26 2011 -0500 > > drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq > > Needed for timer queries in the 3D driver. > > Signed-off-by: Alex Deucher <alexdeucher@gmail.com> > Signed-off-by: Dave Airlie <airlied@gmail.com> > > > i chose that commit since, right after that, there are a couple > commits that are heavily i915-related: > > abb72c828878a2c69b2cfb33ac30007c8ecd735e > 5e82ea99827f6aa122fbb08f8659e76226ce107b > > and those would be the next things i check. is there any other info > you'd like to see? The only missing detail is what connector is used for the display. Xorg.log or xrandr --verbose are the easiest. That's a little scary. I'm certainly unaware of a regression post-58bbf018a70c (especially in those recent fixes) and would appreciate a bisect. Thanks! -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 11:56 ` Chris Wilson @ 2011-01-27 12:12 ` Robert P. J. Day 2011-01-27 12:17 ` Chris Wilson 0 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 12:12 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 06:47:23 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > also, i just verified that i have a properly booting kernel based on > > this commit: > > > > commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 > > Author: Alex Deucher <alexdeucher@gmail.com> > > Date: Mon Jan 24 17:14:26 2011 -0500 > > > > drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq > > > > Needed for timer queries in the 3D driver. > > > > Signed-off-by: Alex Deucher <alexdeucher@gmail.com> > > Signed-off-by: Dave Airlie <airlied@gmail.com> > > > > > > i chose that commit since, right after that, there are a couple > > commits that are heavily i915-related: > > > > abb72c828878a2c69b2cfb33ac30007c8ecd735e > > 5e82ea99827f6aa122fbb08f8659e76226ce107b > > > > and those would be the next things i check. is there any other info > > you'd like to see? > > The only missing detail is what connector is used for the display. > Xorg.log or xrandr --verbose are the easiest. i can supply those for the currently *successful* boot, is that what you're asking? because once we're into black screen territory, there's not a whole lot i can tell you. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 12:12 ` Robert P. J. Day @ 2011-01-27 12:17 ` Chris Wilson 2011-01-27 12:27 ` Robert P. J. Day ` (2 more replies) 0 siblings, 3 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-27 12:17 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Thu, 27 Jan 2011 07:12:03 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > The only missing detail is what connector is used for the display. > > Xorg.log or xrandr --verbose are the easiest. > > i can supply those for the currently *successful* boot, is that > what you're asking? because once we're into black screen territory, > there's not a whole lot i can tell you. Indeed. Fortunately the integrated hardware is unlikely to change between boots. But more interesting is if you can pin down the regressing commit. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 12:17 ` Chris Wilson @ 2011-01-27 12:27 ` Robert P. J. Day 2011-01-27 13:00 ` Robert P. J. Day 2011-01-27 13:42 ` Robert P. J. Day 2 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 12:27 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 07:12:03 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > The only missing detail is what connector is used for the display. > > > Xorg.log or xrandr --verbose are the easiest. > > > > i can supply those for the currently *successful* boot, is that > > what you're asking? because once we're into black screen territory, > > there's not a whole lot i can tell you. > > Indeed. Fortunately the integrated hardware is unlikely to change between > boots. that was sarcasm, wasn't it? :-) > But more interesting is if you can pin down the regressing commit. working on that now. here's Xorg.0.log for the current system: [ 40.877] X.Org X Server 1.9.0 Release Date: 2010-08-20 [ 40.877] X Protocol Version 11, Revision 0 [ 40.877] Build Operating System: Linux 2.6.24-28-server x86_64 Ubuntu [ 40.877] Current Operating System: Linux lynx 2.6.38-rc2+ #15 SMP Thu Jan 27 06:24:55 EST 2011 x86_64 [ 40.877] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.38-rc2+ root=/dev/mapper/lynx-root ro quiet splash [ 40.877] Build Date: 09 January 2011 12:14:27PM [ 40.877] xorg-server 2:1.9.0-0ubuntu7.3 (For technical support please see http://www.ubuntu.com/support) [ 40.877] Current version of pixman: 0.18.4 [ 40.877] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 40.877] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 40.877] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 27 06:39:06 2011 [ 40.955] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 41.012] (==) No Layout section. Using the first Screen section. [ 41.013] (==) No screen section available. Using defaults. [ 41.013] (**) |-->Screen "Default Screen Section" (0) [ 41.013] (**) | |-->Monitor "<default monitor>" [ 41.013] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 41.013] (==) Automatically adding devices [ 41.013] (==) Automatically enabling devices [ 41.039] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 41.039] Entry deleted from font path. [ 41.086] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [ 41.086] (==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 41.086] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 41.086] (II) Loader magic: 0x7d17a0 [ 41.086] (II) Module ABI versions: [ 41.086] X.Org ANSI C Emulation: 0.4 [ 41.086] X.Org Video Driver: 8.0 [ 41.086] X.Org XInput driver : 11.0 [ 41.086] X.Org Server Extension : 4.0 [ 41.087] (--) PCI:*(0:0:2:0) 8086:0046:1025:031c rev 18, Mem @ 0xd0000000/4194304, 0xc0000000/268435456, I/O @ 0x00003050/8 [ 41.087] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 41.087] (II) LoadModule: "extmod" [ 41.160] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so [ 41.167] (II) Module extmod: vendor="X.Org Foundation" [ 41.167] compiled for 1.9.0, module version = 1.0.0 [ 41.167] Module class: X.Org Server Extension [ 41.167] ABI class: X.Org Server Extension, version 4.0 [ 41.167] (II) Loading extension MIT-SCREEN-SAVER [ 41.167] (II) Loading extension XFree86-VidModeExtension [ 41.167] (II) Loading extension XFree86-DGA [ 41.167] (II) Loading extension DPMS [ 41.167] (II) Loading extension XVideo [ 41.167] (II) Loading extension XVideo-MotionCompensation [ 41.167] (II) Loading extension X-Resource [ 41.167] (II) LoadModule: "dbe" [ 41.168] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so [ 41.173] (II) Module dbe: vendor="X.Org Foundation" [ 41.173] compiled for 1.9.0, module version = 1.0.0 [ 41.174] Module class: X.Org Server Extension [ 41.174] ABI class: X.Org Server Extension, version 4.0 [ 41.174] (II) Loading extension DOUBLE-BUFFER [ 41.174] (II) LoadModule: "glx" [ 41.174] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 41.190] (II) Module glx: vendor="X.Org Foundation" [ 41.190] compiled for 1.9.0, module version = 1.0.0 [ 41.190] ABI class: X.Org Server Extension, version 4.0 [ 41.190] (==) AIGLX enabled [ 41.190] (II) Loading extension GLX [ 41.191] (II) LoadModule: "record" [ 41.191] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so [ 41.202] (II) Module record: vendor="X.Org Foundation" [ 41.202] compiled for 1.9.0, module version = 1.13.0 [ 41.202] Module class: X.Org Server Extension [ 41.203] ABI class: X.Org Server Extension, version 4.0 [ 41.203] (II) Loading extension RECORD [ 41.203] (II) LoadModule: "dri" [ 41.203] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so [ 41.215] (II) Module dri: vendor="X.Org Foundation" [ 41.215] compiled for 1.9.0, module version = 1.0.0 [ 41.215] ABI class: X.Org Server Extension, version 4.0 [ 41.215] (II) Loading extension XFree86-DRI [ 41.215] (II) LoadModule: "dri2" [ 41.215] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so [ 41.216] (II) Module dri2: vendor="X.Org Foundation" [ 41.216] compiled for 1.9.0, module version = 1.2.0 [ 41.216] ABI class: X.Org Server Extension, version 4.0 [ 41.216] (II) Loading extension DRI2 [ 41.216] (==) Matched intel as autoconfigured driver 0 [ 41.216] (==) Matched vesa as autoconfigured driver 1 [ 41.216] (==) Matched fbdev as autoconfigured driver 2 [ 41.216] (==) Assigned the driver to the xf86ConfigLayout [ 41.216] (II) LoadModule: "intel" [ 41.223] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 41.241] (II) Module intel: vendor="X.Org Foundation" [ 41.241] compiled for 1.9.0, module version = 2.12.0 [ 41.241] Module class: X.Org Video Driver [ 41.241] ABI class: X.Org Video Driver, version 8.0 [ 41.241] (II) LoadModule: "vesa" [ 41.242] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 41.256] (II) Module vesa: vendor="X.Org Foundation" [ 41.256] compiled for 1.8.99.905, module version = 2.3.0 [ 41.256] Module class: X.Org Video Driver [ 41.256] ABI class: X.Org Video Driver, version 8.0 [ 41.256] (II) LoadModule: "fbdev" [ 41.256] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 41.264] (II) Module fbdev: vendor="X.Org Foundation" [ 41.264] compiled for 1.8.99.905, module version = 0.4.2 [ 41.264] ABI class: X.Org Video Driver, version 8.0 [ 41.264] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 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, B43, Clarkdale, Arrandale, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge [ 41.265] (II) VESA: driver for VESA chipsets: vesa [ 41.265] (II) FBDEV: driver for framebuffer: fbdev [ 41.265] (++) using VT number 7 [ 41.265] (WW) Falling back to old probe method for vesa [ 41.265] (WW) Falling back to old probe method for fbdev [ 41.265] (II) Loading sub module "fbdevhw" [ 41.265] (II) LoadModule: "fbdevhw" [ 41.266] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 41.278] (II) Module fbdevhw: vendor="X.Org Foundation" [ 41.278] compiled for 1.9.0, module version = 0.0.2 [ 41.278] ABI class: X.Org Video Driver, version 8.0 [ 41.280] drmOpenDevice: node name is /dev/dri/card0 [ 41.280] drmOpenDevice: open result is 8, (OK) [ 41.280] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 41.280] drmOpenDevice: node name is /dev/dri/card0 [ 41.280] drmOpenDevice: open result is 8, (OK) [ 41.280] drmOpenByBusid: drmOpenMinor returns 8 [ 41.280] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 [ 41.280] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 41.280] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 41.280] (==) intel(0): RGB weight 888 [ 41.280] (==) intel(0): Default visual is TrueColor [ 41.280] (II) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale [ 41.280] (--) intel(0): Chipset: "Arrandale" [ 41.280] (==) intel(0): video overlay key set to 0x101fe [ 41.281] (II) intel(0): Output LVDS1 has no monitor section [ 41.281] (II) intel(0): found backlight control interface /sys/class/backlight/acpi_video1 [ 41.380] (II) intel(0): Output VGA1 has no monitor section [ 41.384] (II) intel(0): Output HDMI1 has no monitor section [ 41.385] (II) intel(0): Output DP1 has no monitor section [ 41.386] (II) intel(0): EDID for output LVDS1 [ 41.386] (II) intel(0): Manufacturer: SEC Model: 3051 Serial#: 0 [ 41.386] (II) intel(0): Year: 2008 Week: 0 [ 41.386] (II) intel(0): EDID Version: 1.3 [ 41.386] (II) intel(0): Digital Display Input [ 41.386] (II) intel(0): Max Image Size [cm]: horiz.: 39 vert.: 23 [ 41.386] (II) intel(0): Gamma: 2.20 [ 41.386] (II) intel(0): No DPMS capabilities specified [ 41.386] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 [ 41.386] (II) intel(0): First detailed timing is preferred mode [ 41.386] (II) intel(0): redX: 0.600 redY: 0.340 greenX: 0.310 greenY: 0.560 [ 41.386] (II) intel(0): blueX: 0.150 blueY: 0.130 whiteX: 0.313 whiteY: 0.329 [ 41.386] (II) intel(0): Manufacturer's mask: 0 [ 41.386] (II) intel(0): Supported detailed timing: [ 41.386] (II) intel(0): clock: 107.8 MHz Image Size: 398 x 232 mm [ 41.386] (II) intel(0): h_active: 1600 h_sync: 1648 h_sync_end 1680 h_blank_end 1892 h_border: 0 [ 41.386] (II) intel(0): v_active: 900 v_sync: 902 v_sync_end 908 v_blanking: 950 v_border: 0 [ 41.386] (II) intel(0): Unknown vendor-specific block f [ 41.386] (II) intel(0): SAMSUNG [ 41.386] (II) intel(0): 173KT01-A01 [ 41.386] (II) intel(0): EDID (in hex): [ 41.386] (II) intel(0): 00ffffffffffff004ca3513000000000 [ 41.386] (II) intel(0): 00120103802717780a859599574f8f26 [ 41.386] (II) intel(0): 21505400000001010101010101010101 [ 41.386] (II) intel(0): 010101010101202a4024618432303020 [ 41.386] (II) intel(0): 26008ee8100000190000000f00000000 [ 41.386] (II) intel(0): 00000000001eb4027400000000fe0053 [ 41.386] (II) intel(0): 414d53554e470a2020202020000000fe [ 41.386] (II) intel(0): 003137334b5430312d4130310a2000a4 [ 41.386] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 41.386] (II) intel(0): Printing DDC gathered Modelines: [ 41.386] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 41.386] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "576x432" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "680x384" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "680x384" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "720x450" (doublescan mode not supported) [ 41.386] (II) intel(0): Not using default mode "800x512" (doublescan mode not supported) [ 41.387] (II) intel(0): Not using default mode "840x525" (doublescan mode not supported) [ 41.387] (II) intel(0): Not using default mode "840x525" (doublescan mode not supported) [ 41.387] (II) intel(0): Not using default mode "960x540" (doublescan mode not supported) [ 41.387] (II) intel(0): Not using default mode "960x600" (doublescan mode not supported) [ 41.387] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported) [ 41.387] (II) intel(0): Printing probed modes for output LVDS1 [ 41.387] (II) intel(0): Modeline "1600x900"x60.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 41.387] (II) intel(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz) [ 41.387] (II) intel(0): Modeline "1360x768"x59.8 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync (47.7 kHz) [ 41.387] (II) intel(0): Modeline "1360x768"x60.0 72.00 1360 1408 1440 1520 768 771 781 790 +hsync -vsync (47.4 kHz) [ 41.387] (II) intel(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 -hsync +vsync (53.7 kHz) [ 41.387] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) [ 41.387] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) [ 41.387] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) [ 41.387] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) [ 41.387] (II) intel(0): EDID for output VGA1 [ 41.391] (II) intel(0): EDID for output HDMI1 [ 41.393] (II) intel(0): EDID for output DP1 [ 41.393] (II) intel(0): Output LVDS1 connected [ 41.393] (II) intel(0): Output VGA1 disconnected [ 41.393] (II) intel(0): Output HDMI1 disconnected [ 41.393] (II) intel(0): Output DP1 disconnected [ 41.393] (II) intel(0): Using exact sizes for initial modes [ 41.393] (II) intel(0): Output LVDS1 using initial mode 1600x900 [ 41.393] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated. [ 41.393] (II) intel(0): Kernel page flipping support detected, but forcibly disabled. [ 41.393] (**) intel(0): Display dimensions: (390, 230) mm [ 41.393] (**) intel(0): DPI set to (104, 99) [ 41.393] (II) Loading sub module "fb" [ 41.393] (II) LoadModule: "fb" [ 41.393] (II) Loading /usr/lib/xorg/modules/libfb.so [ 41.400] (II) Module fb: vendor="X.Org Foundation" [ 41.400] compiled for 1.9.0, module version = 1.0.0 [ 41.400] ABI class: X.Org ANSI C Emulation, version 0.4 [ 41.400] (II) UnloadModule: "vesa" [ 41.400] (II) Unloading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 41.400] (II) UnloadModule: "fbdev" [ 41.400] (II) Unloading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 41.400] (II) UnloadModule: "fbdevhw" [ 41.400] (II) Unloading /usr/lib/xorg/modules/libfbdevhw.so [ 41.400] (==) Depth 24 pixmap format is 32 bpp [ 41.400] (II) intel(0): [DRI2] Setup complete [ 41.400] (II) intel(0): [DRI2] DRI driver: i965 [ 41.400] (**) intel(0): Tiling enabled [ 41.400] (**) intel(0): SwapBuffers wait enabled [ 41.400] (==) intel(0): VideoRam: 262144 KB [ 41.400] (II) intel(0): Allocated new frame buffer 1600x900 stride 6656, tiled [ 41.441] (II) UXA(0): Driver registered support for the following operations: [ 41.442] (II) solid [ 41.442] (II) copy [ 41.442] (II) composite (RENDER acceleration) [ 41.442] (II) put_image [ 41.442] (II) get_image [ 41.442] (==) intel(0): Backing store disabled [ 41.442] (==) intel(0): Silken mouse enabled [ 41.442] (II) intel(0): Initializing HW Cursor [ 41.510] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. [ 41.511] (==) intel(0): DPMS enabled [ 41.511] (==) intel(0): Intel XvMC decoder enabled [ 41.511] (II) intel(0): Set up textured video [ 41.511] (II) intel(0): [XvMC] xvmc_vld driver initialized. [ 41.511] (II) intel(0): direct rendering: DRI2 Enabled [ 41.511] (--) RandR disabled [ 41.511] (II) Initializing built-in extension Generic Event Extension [ 41.511] (II) Initializing built-in extension SHAPE [ 41.511] (II) Initializing built-in extension MIT-SHM [ 41.511] (II) Initializing built-in extension XInputExtension [ 41.511] (II) Initializing built-in extension XTEST [ 41.511] (II) Initializing built-in extension BIG-REQUESTS [ 41.511] (II) Initializing built-in extension SYNC [ 41.511] (II) Initializing built-in extension XKEYBOARD [ 41.511] (II) Initializing built-in extension XC-MISC [ 41.511] (II) Initializing built-in extension SECURITY [ 41.511] (II) Initializing built-in extension XINERAMA [ 41.511] (II) Initializing built-in extension XFIXES [ 41.511] (II) Initializing built-in extension RENDER [ 41.511] (II) Initializing built-in extension RANDR [ 41.511] (II) Initializing built-in extension COMPOSITE [ 41.511] (II) Initializing built-in extension DAMAGE [ 41.511] (II) Initializing built-in extension GESTURE [ 41.633] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 41.633] (II) AIGLX: enabled GLX_INTEL_swap_event [ 41.633] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 41.633] (II) AIGLX: enabled GLX_SGI_make_current_read [ 41.633] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 41.633] (II) AIGLX: Loaded and initialized /usr/lib/dri/i965_dri.so [ 41.633] (II) GLX: Initialized DRI2 GL provider for screen 0 [ 41.634] (II) intel(0): Setting screen physical size to 423 x 238 [ 41.840] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm [ 41.856] (II) config/udev: Adding input device Power Button (/dev/input/event3) [ 41.856] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 41.856] (II) LoadModule: "evdev" [ 41.856] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [ 41.889] (II) Module evdev: vendor="X.Org Foundation" [ 41.889] compiled for 1.9.0, module version = 2.3.2 [ 41.889] Module class: X.Org XInput Driver [ 41.889] ABI class: X.Org XInput driver, version 11.0 [ 41.889] (**) Power Button: always reports core events [ 41.889] (**) Power Button: Device: "/dev/input/event3" [ 42.000] (II) Power Button: Found keys [ 42.000] (II) Power Button: Configuring as keyboard [ 42.000] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 42.000] (**) Option "xkb_rules" "evdev" [ 42.000] (**) Option "xkb_model" "pc105" [ 42.000] (**) Option "xkb_layout" "us" [ 42.000] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.003] (II) XKB: reuse xkmfile /var/lib/xkb/server-0C76CA335E924C2441A31FBFED02D59A89874CA6.xkm [ 42.004] (II) config/udev: Adding input device Video Bus (/dev/input/event7) [ 42.005] (**) Video Bus: Applying InputClass "evdev keyboard catchall" [ 42.005] (**) Video Bus: always reports core events [ 42.005] (**) Video Bus: Device: "/dev/input/event7" [ 42.070] (II) Video Bus: Found keys [ 42.070] (II) Video Bus: Configuring as keyboard [ 42.070] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD) [ 42.070] (**) Option "xkb_rules" "evdev" [ 42.070] (**) Option "xkb_model" "pc105" [ 42.070] (**) Option "xkb_layout" "us" [ 42.070] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.071] (II) config/udev: Adding input device Power Button (/dev/input/event0) [ 42.071] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 42.071] (**) Power Button: always reports core events [ 42.071] (**) Power Button: Device: "/dev/input/event0" [ 42.160] (II) Power Button: Found keys [ 42.160] (II) Power Button: Configuring as keyboard [ 42.160] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 42.160] (**) Option "xkb_rules" "evdev" [ 42.160] (**) Option "xkb_model" "pc105" [ 42.160] (**) Option "xkb_layout" "us" [ 42.160] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.160] (II) config/udev: Adding input device Lid Switch (/dev/input/event1) [ 42.160] (II) No input driver/identifier specified (ignoring) [ 42.161] (II) config/udev: Adding input device Sleep Button (/dev/input/event2) [ 42.161] (**) Sleep Button: Applying InputClass "evdev keyboard catchall" [ 42.161] (**) Sleep Button: always reports core events [ 42.161] (**) Sleep Button: Device: "/dev/input/event2" [ 42.250] (II) Sleep Button: Found keys [ 42.250] (II) Sleep Button: Configuring as keyboard [ 42.250] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD) [ 42.250] (**) Option "xkb_rules" "evdev" [ 42.250] (**) Option "xkb_model" "pc105" [ 42.250] (**) Option "xkb_layout" "us" [ 42.250] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.253] (II) config/udev: Adding input device Video WebCam (/dev/input/event5) [ 42.253] (**) Video WebCam: Applying InputClass "evdev keyboard catchall" [ 42.253] (**) Video WebCam: always reports core events [ 42.253] (**) Video WebCam: Device: "/dev/input/event5" [ 42.340] (II) Video WebCam: Found keys [ 42.340] (II) Video WebCam: Configuring as keyboard [ 42.340] (II) XINPUT: Adding extended input device "Video WebCam" (type: KEYBOARD) [ 42.340] (**) Option "xkb_rules" "evdev" [ 42.340] (**) Option "xkb_model" "pc105" [ 42.340] (**) Option "xkb_layout" "us" [ 42.340] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.341] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event8) [ 42.341] (II) No input driver/identifier specified (ignoring) [ 42.345] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4) [ 42.345] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall" [ 42.345] (**) AT Translated Set 2 keyboard: always reports core events [ 42.345] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4" [ 42.430] (II) AT Translated Set 2 keyboard: Found keys [ 42.430] (II) AT Translated Set 2 keyboard: Configuring as keyboard [ 42.430] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD) [ 42.430] (**) Option "xkb_rules" "evdev" [ 42.430] (**) Option "xkb_model" "pc105" [ 42.430] (**) Option "xkb_layout" "us" [ 42.430] (**) Option "xkb_options" "lv3:ralt_switch" [ 42.430] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6) [ 42.430] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall" [ 42.430] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall" [ 42.430] (II) LoadModule: "synaptics" [ 42.431] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so [ 42.457] (II) Module synaptics: vendor="X.Org Foundation" [ 42.457] compiled for 1.9.0, module version = 1.2.2 [ 42.457] Module class: X.Org XInput Driver [ 42.457] ABI class: X.Org XInput driver, version 11.0 [ 42.457] (II) Synaptics touchpad driver version 1.2.2 [ 42.457] (**) Option "Device" "/dev/input/event6" [ 42.830] (II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5584 [ 42.830] (II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4434 [ 42.830] (II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255 [ 42.830] (II) SynPS/2 Synaptics TouchPad: finger width range 0 - 15 [ 42.830] (II) SynPS/2 Synaptics TouchPad: buttons: left right double triple [ 43.100] (--) SynPS/2 Synaptics TouchPad: touchpad found [ 43.100] (**) SynPS/2 Synaptics TouchPad: always reports core events [ 43.260] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD) [ 43.260] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1 [ 43.260] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0 [ 43.260] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 [ 43.260] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 [ 43.430] (--) SynPS/2 Synaptics TouchPad: touchpad found [ 43.430] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [ 43.430] (II) No input driver/identifier specified (ignoring) [ 55.589] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 55.589] (II) intel(0): Printing DDC gathered Modelines: [ 55.589] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 55.596] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 55.596] (II) intel(0): Printing DDC gathered Modelines: [ 55.596] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 55.648] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 55.648] (II) intel(0): Printing DDC gathered Modelines: [ 55.648] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 55.655] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 55.655] (II) intel(0): Printing DDC gathered Modelines: [ 55.655] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 87.420] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 87.420] (II) intel(0): Printing DDC gathered Modelines: [ 87.420] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 87.710] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 87.710] (II) intel(0): Printing DDC gathered Modelines: [ 87.710] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 87.717] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 87.717] (II) intel(0): Printing DDC gathered Modelines: [ 87.717] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 87.723] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 87.723] (II) intel(0): Printing DDC gathered Modelines: [ 87.723] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 109.175] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 109.175] (II) intel(0): Printing DDC gathered Modelines: [ 109.175] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 1075.332] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 1075.332] (II) intel(0): Printing DDC gathered Modelines: [ 1075.333] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 1599.782] (II) config/udev: Adding input device USB OpticalWheel Mouse (/dev/input/event9) [ 1599.782] (**) USB OpticalWheel Mouse: Applying InputClass "evdev pointer catchall" [ 1599.782] (**) USB OpticalWheel Mouse: always reports core events [ 1599.782] (**) USB OpticalWheel Mouse: Device: "/dev/input/event9" [ 1599.840] (II) USB OpticalWheel Mouse: Found 3 mouse buttons [ 1599.840] (II) USB OpticalWheel Mouse: Found scroll wheel(s) [ 1599.840] (II) USB OpticalWheel Mouse: Found relative axes [ 1599.840] (II) USB OpticalWheel Mouse: Found x and y relative axes [ 1599.840] (II) USB OpticalWheel Mouse: Configuring as mouse [ 1599.840] (**) USB OpticalWheel Mouse: YAxisMapping: buttons 4 and 5 [ 1599.840] (**) USB OpticalWheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 1599.840] (II) XINPUT: Adding extended input device "USB OpticalWheel Mouse" (type: MOUSE) [ 1599.840] (II) USB OpticalWheel Mouse: initialized for relative axes. [ 1599.841] (II) config/udev: Adding input device USB OpticalWheel Mouse (/dev/input/mouse1) [ 1599.841] (II) No input driver/identifier specified (ignoring) [ 1894.896] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 1894.896] (II) intel(0): Printing DDC gathered Modelines: [ 1894.896] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 1899.953] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 1899.953] (II) intel(0): Printing DDC gathered Modelines: [ 1899.953] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) [ 2782.099] (II) intel(0): EDID vendor "SEC", prod id 12369 [ 2782.137] (II) intel(0): Printing DDC gathered Modelines: [ 2782.137] (II) intel(0): Modeline "1600x900"x0.0 107.84 1600 1648 1680 1892 900 902 908 950 -hsync -vsync (57.0 kHz) and here's "xrandr --verbose" Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192 LVDS1 connected 1600x900+0+0 (0x45) normal (normal left inverted right x axis y axis) 398mm x 232mm Identifier: 0x41 Timestamp: 40839 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff004ca3513000000000 00120103802717780a859599574f8f26 21505400000001010101010101010101 010101010101202a4024618432303020 26008ee8100000190000000f00000000 00000000001eb4027400000000fe0053 414d53554e470a2020202020000000fe 003137334b5430312d4130310a2000a4 BACKLIGHT: 1 (0x00000001) range: (0,9) Backlight: 1 (0x00000001) range: (0,9) scaling mode: Full aspect supported: None Full Center Full aspect 1600x900 (0x45) 107.8MHz -HSync -VSync *current +preferred h: width 1600 start 1648 end 1680 total 1892 skew 0 clock 57.0KHz v: height 900 start 902 end 908 total 950 clock 60.0Hz 1440x900 (0x46) 106.5MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.9KHz v: height 900 start 903 end 909 total 934 clock 59.9Hz 1360x768 (0x47) 84.8MHz -HSync +VSync h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.7KHz v: height 768 start 771 end 781 total 798 clock 59.8Hz 1360x768 (0x48) 72.0MHz +HSync -VSync h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 1152x864 (0x49) 81.6MHz -HSync +VSync h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz v: height 864 start 865 end 868 total 895 clock 60.0Hz 1024x768 (0x4a) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x4b) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x4c) 36.0MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz 640x480 (0x4d) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz VGA1 disconnected (normal left inverted right x axis y axis) Identifier: 0x42 Timestamp: 40839 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: HDMI1 disconnected (normal left inverted right x axis y axis) Identifier: 0x43 Timestamp: 40839 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: force_audio: 0 (0x00000000) range: (-1,1) DP1 disconnected (normal left inverted right x axis y axis) Identifier: 0x44 Timestamp: 40839 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: force_audio: 0 (0x00000000) range: (-1,1) rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 12:17 ` Chris Wilson 2011-01-27 12:27 ` Robert P. J. Day @ 2011-01-27 13:00 ` Robert P. J. Day 2011-01-27 13:42 ` Robert P. J. Day 2 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 13:00 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 07:12:03 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > The only missing detail is what connector is used for the display. > > > Xorg.log or xrandr --verbose are the easiest. > > > > i can supply those for the currently *successful* boot, is that > > what you're asking? because once we're into black screen territory, > > there's not a whole lot i can tell you. > > Indeed. Fortunately the integrated hardware is unlikely to change between > boots. But more interesting is if you can pin down the regressing commit. this commit seems to be fine: commit abb72c828878a2c69b2cfb33ac30007c8ecd735e Merge: 58bbf01 8e934db Author: Dave Airlie <airlied@gmail.com> Date: Tue Jan 25 08:41:58 2011 +1000 Merge branch 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/ke * 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/git/ic drm/i915: Prevent uninitialised reads during error state capture drm/i915: Use consistent mappings for OpRegion between ACPI and i915 drm/i915: Handle the no-interrupts case for UMS by polling drm/i915: Disable high-precision vblank timestamping for UMS drm/i915: Increase the amount of defense before computing vblank timestamp drm/i915,agp/intel: Do not clear stolen entries Remove MAYBE_BUILD_BUG_ON BUILD_BUG_ON: make it handle more cases module: fix missing semicolons in MODULE macro usage param: add null statement to compiled-in module params module: fix linker error for MODULE_VERSION when !MODULE and CONFIG_SYSFS= module: show version information for built-in modules in sysfs selinux: return -ENOMEM when memory allocation fails tpm: fix panic caused by "tpm: Autodetect itpm devices" TPM: Long default timeout fix trusted keys: Fix a memory leak in trusted_update(). keys: add trusted and encrypted maintainers encrypted-keys: rename encrypted_defined files to encrypted trusted-keys: rename trusted_defined files to trusted drm/i915: Recognise non-VGA display devices ... so moving on to the very next one, which logic suggests would be the culprit. back shortly if time permits. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 12:17 ` Chris Wilson 2011-01-27 12:27 ` Robert P. J. Day 2011-01-27 13:00 ` Robert P. J. Day @ 2011-01-27 13:42 ` Robert P. J. Day 2011-01-27 13:52 ` Chris Wilson 2 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 13:42 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 07:12:03 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > The only missing detail is what connector is used for the display. > > > Xorg.log or xrandr --verbose are the easiest. > > > > i can supply those for the currently *successful* boot, is that > > what you're asking? because once we're into black screen territory, > > there's not a whole lot i can tell you. > > Indeed. Fortunately the integrated hardware is unlikely to change between > boots. But more interesting is if you can pin down the regressing commit. for me, this appears to be the offending commit: commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) Merge: ec30f34 abb72c8 Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Tue Jan 25 10:46:14 2011 +1000 Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai * 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2 drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq drm/i915: Prevent uninitialised reads during error state capture drm/i915: Use consistent mappings for OpRegion between ACPI and i915 drm/i915: Handle the no-interrupts case for UMS by polling drm/i915: Disable high-precision vblank timestamping for UMS drm/i915: Increase the amount of defense before computing vblank timestamp drm/i915,agp/intel: Do not clear stolen entries drm/radeon/kms: simplify atom adjust pll setup drm/radeon/kms: match r6xx/r7xx/evergreen asic_reset with previous asics drm/radeon/kms: make the mac rv630 quirk generic drm/radeon/kms: fix a spelling error in an error message drm/radeon/kms: Initialize pageflip spinlocks. drm/i915: Recognise non-VGA display devices drm/i915: Fix use of invalid array size for ring->sync_seqno drm/i915/ringbuffer: Fix use of stale HEAD position whilst polling for spa drm/i915: Don't kick-off hangcheck after a DRI interrupt drm/i915: Add dependency on CONFIG_TMPFS drm/i915: Initialise ring vfuncs for old DRI paths drm/i915: make the blitter report buffer modifications to the FBC unit drm/i915: set more FBC chicken bits anything you want me to try? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 13:42 ` Robert P. J. Day @ 2011-01-27 13:52 ` Chris Wilson 2011-01-27 13:55 ` Robert P. J. Day 0 siblings, 1 reply; 49+ messages in thread From: Chris Wilson @ 2011-01-27 13:52 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > for me, this appears to be the offending commit: > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > Merge: ec30f34 abb72c8 > Author: Linus Torvalds <torvalds@linux-foundation.org> > Date: Tue Jan 25 10:46:14 2011 +1000 > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai Let's just test the other parent ec30f343d to be sure it came in with the drm merge. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 13:52 ` Chris Wilson @ 2011-01-27 13:55 ` Robert P. J. Day 2011-01-27 14:07 ` Chris Wilson 0 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 13:55 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > for me, this appears to be the offending commit: > > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > > Merge: ec30f34 abb72c8 > > Author: Linus Torvalds <torvalds@linux-foundation.org> > > Date: Tue Jan 25 10:46:14 2011 +1000 > > > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai > > Let's just test the other parent ec30f343d to be sure it came in with the > drm merge. so that's something you want me to test? checking out that commit ec30f343d and trying it? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 13:55 ` Robert P. J. Day @ 2011-01-27 14:07 ` Chris Wilson 2011-01-27 14:13 ` Robert P. J. Day ` (2 more replies) 0 siblings, 3 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-27 14:07 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Thu, 27 Jan 2011 08:55:24 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > > > for me, this appears to be the offending commit: > > > > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > > > Merge: ec30f34 abb72c8 > > > Author: Linus Torvalds <torvalds@linux-foundation.org> > > > Date: Tue Jan 25 10:46:14 2011 +1000 > > > > > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai > > > > Let's just test the other parent ec30f343d to be sure it came in with the > > drm merge. > > so that's something you want me to test? checking out that commit > ec30f343d and trying it? Yes. If abb72c8 works and 5e82ea9 does not, then ec30f34 must be at fault (since the merge looks clean), verifying that the bug was introduced between abb72c828 and ec30f34. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 14:07 ` Chris Wilson @ 2011-01-27 14:13 ` Robert P. J. Day 2011-01-27 18:40 ` Robert P. J. Day 2011-01-27 21:39 ` Robert P. J. Day 2 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 14:13 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 08:55:24 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > > > > > for me, this appears to be the offending commit: > > > > > > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > > > > Merge: ec30f34 abb72c8 > > > > Author: Linus Torvalds <torvalds@linux-foundation.org> > > > > Date: Tue Jan 25 10:46:14 2011 +1000 > > > > > > > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai > > > > > > Let's just test the other parent ec30f343d to be sure it came in with the > > > drm merge. > > > > so that's something you want me to test? checking out that commit > > ec30f343d and trying it? > > Yes. If abb72c8 works and 5e82ea9 does not, then ec30f34 must be at fault > (since the merge looks clean), verifying that the bug was introduced > between abb72c828 and ec30f34. ok, i'll try to get to that ASAP. so what i'm *expecting* is for ec30f34 to fail, then. i'll keep you posted. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 14:07 ` Chris Wilson 2011-01-27 14:13 ` Robert P. J. Day @ 2011-01-27 18:40 ` Robert P. J. Day 2011-01-27 21:39 ` Robert P. J. Day 2 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 18:40 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 08:55:24 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > > > > > for me, this appears to be the offending commit: > > > > > > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > > > > Merge: ec30f34 abb72c8 > > > > Author: Linus Torvalds <torvalds@linux-foundation.org> > > > > Date: Tue Jan 25 10:46:14 2011 +1000 > > > > > > > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai > > > > > > Let's just test the other parent ec30f343d to be sure it came in with the > > > drm merge. > > > > so that's something you want me to test? checking out that commit > > ec30f343d and trying it? > > Yes. If abb72c8 works and 5e82ea9 does not, then ec30f34 must be at fault > (since the merge looks clean), verifying that the bug was introduced > between abb72c828 and ec30f34. well, now i'm confused since it *appears* that, when i went to double-check the results, the earlier commit abb72c8 *doesn't* work, and i could swear that it did. so i'll just redo *all* of the relevant commits and report back. grrrrrr ... rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 14:07 ` Chris Wilson 2011-01-27 14:13 ` Robert P. J. Day 2011-01-27 18:40 ` Robert P. J. Day @ 2011-01-27 21:39 ` Robert P. J. Day 2011-01-27 22:33 ` Robert P. J. Day 2 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 21:39 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Thu, 27 Jan 2011, Chris Wilson wrote: > On Thu, 27 Jan 2011 08:55:24 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Thu, 27 Jan 2011, Chris Wilson wrote: > > > > > On Thu, 27 Jan 2011 08:42:19 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > > > > > for me, this appears to be the offending commit: > > > > > > > > commit 5e82ea99827f6aa122fbb08f8659e76226ce107b (now testing) > > > > Merge: ec30f34 abb72c8 > > > > Author: Linus Torvalds <torvalds@linux-foundation.org> > > > > Date: Tue Jan 25 10:46:14 2011 +1000 > > > > > > > > Merge branch 'drm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ai > > > > > > Let's just test the other parent ec30f343d to be sure it came in with the > > > drm merge. > > > > so that's something you want me to test? checking out that commit > > ec30f343d and trying it? > > Yes. If abb72c8 works and 5e82ea9 does not, then ec30f34 must be at fault > (since the merge looks clean), verifying that the bug was introduced > between abb72c828 and ec30f34. ok, i'm getting different results from this morning, not sure why, but i'm fairly confident i've isolated it to this extent. here's the salient part of the git log i'm looking at: ===== git log ===== commit abb72c828878a2c69b2cfb33ac30007c8ecd735e Merge: 58bbf01 8e934db Author: Dave Airlie <airlied@gmail.com> Date: Tue Jan 25 08:41:58 2011 +1000 Merge branch 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/g * 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/git/ickle/dr drm/i915: Prevent uninitialised reads during error state capture drm/i915: Use consistent mappings for OpRegion between ACPI and i915 drm/i915: Handle the no-interrupts case for UMS by polling drm/i915: Disable high-precision vblank timestamping for UMS drm/i915: Increase the amount of defense before computing vblank timestamps drm/i915,agp/intel: Do not clear stolen entries Remove MAYBE_BUILD_BUG_ON BUILD_BUG_ON: make it handle more cases module: fix missing semicolons in MODULE macro usage param: add null statement to compiled-in module params module: fix linker error for MODULE_VERSION when !MODULE and CONFIG_SYSFS=n module: show version information for built-in modules in sysfs selinux: return -ENOMEM when memory allocation fails tpm: fix panic caused by "tpm: Autodetect itpm devices" TPM: Long default timeout fix trusted keys: Fix a memory leak in trusted_update(). keys: add trusted and encrypted maintainers encrypted-keys: rename encrypted_defined files to encrypted trusted-keys: rename trusted_defined files to trusted drm/i915: Recognise non-VGA display devices ... commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 Author: Alex Deucher <alexdeucher@gmail.com> Date: Mon Jan 24 17:14:26 2011 -0500 drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq Needed for timer queries in the 3D driver. Signed-off-by: Alex Deucher <alexdeucher@gmail.com> Signed-off-by: Dave Airlie <airlied@gmail.com> ===== git log ===== now: * commit 58bbf018 appears to be fine, boots reliably * commit 8e934dbf causes black screen issue as you can see, rather than test the *merge* above, i decided to back up one level and test the commit that was part of that merge, and it failed. is this helpful? here's the log entry: commit 8e934dbf264418afe4d1dff34ce074ecc14280db Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Jan 24 12:34:00 2011 +0000 drm/i915: Prevent uninitialised reads during error state capture error_bo and pinned_bo could be used uninitialised if there were no active buffers. Caught by kmemcheck. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> i'm going to go on and test the merge itself, abb72c82, since i thought that was working fine earlier today. but you can see which commit now seems to fail. does this make any sense? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 21:39 ` Robert P. J. Day @ 2011-01-27 22:33 ` Robert P. J. Day 2011-01-28 8:59 ` Chris Wilson 0 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-27 22:33 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel one more observation which should nail things down: On Thu, 27 Jan 2011, Robert P. J. Day wrote: > ok, i'm getting different results from this morning, not sure why, > but i'm fairly confident i've isolated it to this extent. here's the > salient part of the git log i'm looking at: > > ===== git log ===== > > commit abb72c828878a2c69b2cfb33ac30007c8ecd735e > Merge: 58bbf01 8e934db > Author: Dave Airlie <airlied@gmail.com> > Date: Tue Jan 25 08:41:58 2011 +1000 > > Merge branch 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/g > > * 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/git/ickle/dr > drm/i915: Prevent uninitialised reads during error state capture > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > drm/i915: Handle the no-interrupts case for UMS by polling > drm/i915: Disable high-precision vblank timestamping for UMS > drm/i915: Increase the amount of defense before computing vblank timestamps > drm/i915,agp/intel: Do not clear stolen entries > Remove MAYBE_BUILD_BUG_ON > BUILD_BUG_ON: make it handle more cases > module: fix missing semicolons in MODULE macro usage > param: add null statement to compiled-in module params > module: fix linker error for MODULE_VERSION when !MODULE and CONFIG_SYSFS=n > module: show version information for built-in modules in sysfs > selinux: return -ENOMEM when memory allocation fails > tpm: fix panic caused by "tpm: Autodetect itpm devices" > TPM: Long default timeout fix > trusted keys: Fix a memory leak in trusted_update(). > keys: add trusted and encrypted maintainers > encrypted-keys: rename encrypted_defined files to encrypted > trusted-keys: rename trusted_defined files to trusted > drm/i915: Recognise non-VGA display devices > ... > > commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 > Author: Alex Deucher <alexdeucher@gmail.com> > Date: Mon Jan 24 17:14:26 2011 -0500 > > drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq > > Needed for timer queries in the 3D driver. > > Signed-off-by: Alex Deucher <alexdeucher@gmail.com> > Signed-off-by: Dave Airlie <airlied@gmail.com> > > ===== git log ===== > > now: > > * commit 58bbf018 appears to be fine, boots reliably > * commit 8e934dbf causes black screen issue > > as you can see, rather than test the *merge* above, i decided to back > up one level and test the commit that was part of that merge, and it > failed. is this helpful? here's the log entry: > > commit 8e934dbf264418afe4d1dff34ce074ecc14280db > Author: Chris Wilson <chris@chris-wilson.co.uk> > Date: Mon Jan 24 12:34:00 2011 +0000 > > drm/i915: Prevent uninitialised reads during error state capture > > error_bo and pinned_bo could be used uninitialised if there were no > active buffers. > > Caught by kmemcheck. > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > i'm going to go on and test the merge itself, abb72c82, since i > thought that was working fine earlier today. but you can see which > commit now seems to fail. does this make any sense? i did indeed test commit abb72c82 (the merge of the above), and it failed. not sure why i posted earlier today that it worked, i must have built something incorrectly. so, in conclusion: * commit 58bbf018 appears to be fine, boots reliably * commit 8e934dbf causes black screen issue * commit abb72c82 also causes black screen issue and on that note, signing off for the evening. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-27 22:33 ` Robert P. J. Day @ 2011-01-28 8:59 ` Chris Wilson 2011-01-28 9:24 ` Robert P. J. Day 2011-01-28 11:35 ` has the i915 "black screen" boot issue returned? Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 8:59 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Thu, 27 Jan 2011 17:33:04 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > one more observation which should nail things down: > > On Thu, 27 Jan 2011, Robert P. J. Day wrote: > > > ok, i'm getting different results from this morning, not sure why, > > but i'm fairly confident i've isolated it to this extent. here's the > > salient part of the git log i'm looking at: > > > > ===== git log ===== > > > > commit abb72c828878a2c69b2cfb33ac30007c8ecd735e > > Merge: 58bbf01 8e934db > > Author: Dave Airlie <airlied@gmail.com> > > Date: Tue Jan 25 08:41:58 2011 +1000 > > > > Merge branch 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/g > > > > * 'drm-intel-fixes-2' of ssh://master.kernel.org/pub/scm/linux/kernel/git/ickle/dr > > drm/i915: Prevent uninitialised reads during error state capture > > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > > drm/i915: Handle the no-interrupts case for UMS by polling > > drm/i915: Disable high-precision vblank timestamping for UMS > > drm/i915: Increase the amount of defense before computing vblank timestamps > > drm/i915,agp/intel: Do not clear stolen entries > > Remove MAYBE_BUILD_BUG_ON > > BUILD_BUG_ON: make it handle more cases > > module: fix missing semicolons in MODULE macro usage > > param: add null statement to compiled-in module params > > module: fix linker error for MODULE_VERSION when !MODULE and CONFIG_SYSFS=n > > module: show version information for built-in modules in sysfs > > selinux: return -ENOMEM when memory allocation fails > > tpm: fix panic caused by "tpm: Autodetect itpm devices" > > TPM: Long default timeout fix > > trusted keys: Fix a memory leak in trusted_update(). > > keys: add trusted and encrypted maintainers > > encrypted-keys: rename encrypted_defined files to encrypted > > trusted-keys: rename trusted_defined files to trusted > > drm/i915: Recognise non-VGA display devices > > ... > > > > commit 58bbf018a70c562437eeae121a5d021ba7fe56a5 > > Author: Alex Deucher <alexdeucher@gmail.com> > > Date: Mon Jan 24 17:14:26 2011 -0500 > > > > drm/radeon/kms: add new radeon_info ioctl query for clock crystal freq > > > > Needed for timer queries in the 3D driver. > > > > Signed-off-by: Alex Deucher <alexdeucher@gmail.com> > > Signed-off-by: Dave Airlie <airlied@gmail.com> > > > > ===== git log ===== > > > > now: > > > > * commit 58bbf018 appears to be fine, boots reliably > > * commit 8e934dbf causes black screen issue > > > > as you can see, rather than test the *merge* above, i decided to back > > up one level and test the commit that was part of that merge, and it > > failed. is this helpful? here's the log entry: > > > > commit 8e934dbf264418afe4d1dff34ce074ecc14280db > > Author: Chris Wilson <chris@chris-wilson.co.uk> > > Date: Mon Jan 24 12:34:00 2011 +0000 > > > > drm/i915: Prevent uninitialised reads during error state capture > > > > error_bo and pinned_bo could be used uninitialised if there were no > > active buffers. > > > > Caught by kmemcheck. > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > > > > i'm going to go on and test the merge itself, abb72c82, since i > > thought that was working fine earlier today. but you can see which > > commit now seems to fail. does this make any sense? > > i did indeed test commit abb72c82 (the merge of the above), and it > failed. not sure why i posted earlier today that it worked, i must > have built something incorrectly. so, in conclusion: > > * commit 58bbf018 appears to be fine, boots reliably > * commit 8e934dbf causes black screen issue > * commit abb72c82 also causes black screen issue > > and on that note, signing off for the evening. > > rday > > -- > > ======================================================================== > Robert P. J. Day Waterloo, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > ======================================================================== From: Chris Wilson <chris@chris-wilson.co.uk> Subject: Re: has the i915 "black screen" boot issue returned? To: "Robert P. J. Day" <rpjday@crashcourse.ca> Cc: dri-devel@lists.freedesktop.org Bcc: chris@chris-wilson.co.uk In-Reply-To: <alpine.DEB.2.00.1101271634260.2761@localhost6.localdomain6> References: <alpine.DEB.2.00.1101260634300.10774@localhost6.localdomain6> <b9dded$hp9kfu@orsmga002.jf.intel.com> <alpine.DEB.2.00.1101270641490.2923@localhost6.localdomain6> <b9dded$hpa5rf@orsmga002.jf.intel.com> <alpine.DEB.2.00.1101270710510.17636@localhost6.localdomain6> <1bdc18$jdgfni@fmsmga002.fm.intel.com> <alpine.DEB.2.00.1101270840380.2736@localhost6.localdomain6> <0d30dc$ksovh8@orsmga001.jf.intel.com> <alpine.DEB.2.00.1101270854420.4898@localhost6.localdomain6> <b7da2f$q8lpcn@fmsmga001.fm.intel.com> <alpine.DEB.2.00.1101271634260.2761@localhost6.localdomain6> On Thu, 27 Jan 2011 16:39:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > ok, i'm getting different results from this morning, not sure why, > but i'm fairly confident i've isolated it to this extent. here's the > salient part of the git log i'm looking at: Well, we have two endpoints, so let git attack: $ git bisect start $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5 $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e That shouldn't take more than a few recompiles to identify the troublemaker. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-28 8:59 ` Chris Wilson @ 2011-01-28 9:24 ` Robert P. J. Day 2011-01-28 9:29 ` Chris Wilson 2011-01-28 11:35 ` has the i915 "black screen" boot issue returned? Robert P. J. Day 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 9:24 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > Well, we have two endpoints, so let git attack: > > $ git bisect start > $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5 > $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e > > That shouldn't take more than a few recompiles to identify the > troublemaker. ok, i can get to that in a bit. might take a while since this system is not exactly a screamer but i'm curious -- have you heard no other reports of people running into this issue? i'm going to be embarrassed if it turns out it's something *i've* done but, at this point, it seems fairly reproducible. are there any kernel command-line parms i might try that would be informative? anything involving modesetting? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-28 9:24 ` Robert P. J. Day @ 2011-01-28 9:29 ` Chris Wilson 2011-01-28 13:53 ` has the i915 "black screen" boot issue returned? [BISECTED] Robert P. J. Day 0 siblings, 1 reply; 49+ messages in thread From: Chris Wilson @ 2011-01-28 9:29 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Fri, 28 Jan 2011 04:24:17 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > Well, we have two endpoints, so let git attack: > > > > $ git bisect start > > $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5 > > $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e > > > > That shouldn't take more than a few recompiles to identify the > > troublemaker. > > ok, i can get to that in a bit. might take a while since this > system is not exactly a screamer but i'm curious -- have you heard no > other reports of people running into this issue? i'm going to be > embarrassed if it turns out it's something *i've* done but, at this > point, it seems fairly reproducible. This is the first I'm aware of. It could just be the tip of the iceberg... > are there any kernel command-line parms i might try that would be > informative? anything involving modesetting? Sure: add drm.debug=0xe to your boot parameters (or to your modprobe conf). -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 9:29 ` Chris Wilson @ 2011-01-28 13:53 ` Robert P. J. Day 2011-01-28 14:02 ` Chris Wilson 0 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 13:53 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 04:24:17 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > > > Well, we have two endpoints, so let git attack: > > > > > > $ git bisect start > > > $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5 > > > $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e > > > > > > That shouldn't take more than a few recompiles to identify the > > > troublemaker. > > > > ok, i can get to that in a bit. might take a while since this > > system is not exactly a screamer but i'm curious -- have you heard no > > other reports of people running into this issue? i'm going to be > > embarrassed if it turns out it's something *i've* done but, at this > > point, it seems fairly reproducible. > > This is the first I'm aware of. It could just be the tip of the iceberg... the git bisection finally resolved to: BAD: b705120e GOOD: 8a327f23 so the culprit appears to be: b705120e4198315f4ae043de06c62f65e0851fd3 is the first bad commit commit b705120e4198315f4ae043de06c62f65e0851fd3 Author: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> Date: Sun Jan 23 18:17:17 2011 +0000 drm/i915: Use consistent mappings for OpRegion between ACPI and i915 The opregion is a shared memory region between ACPI and the graphics driver. As the ACPI mapping has been changed to cachable in commit 6d5bbf00d251cc73223a71422d69e069dc2e0b8d, mapping the intel opregion non-cachable now fails. As no bus-master hardware is involved in the opregion, cachable map should do no harm. Tested on a Fujitsu Lifebook P8010. Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> [ickle: convert to acpi_os_ioremap for consistency] Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> thoughts? once again, the salient output from "lspci -v": 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device 031c Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at d0000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 3050 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 13:53 ` has the i915 "black screen" boot issue returned? [BISECTED] Robert P. J. Day @ 2011-01-28 14:02 ` Chris Wilson 2011-01-28 14:10 ` Robert P. J. Day 2011-01-28 14:32 ` Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 14:02 UTC (permalink / raw) To: Robert P. J. Day; +Cc: Rafael J. Wysocki, Len Brown, linux-kernel, dri-devel On Fri, 28 Jan 2011 08:53:59 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > so the culprit appears to be: > > b705120e4198315f4ae043de06c62f65e0851fd3 is the first bad commit > commit b705120e4198315f4ae043de06c62f65e0851fd3 > Author: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > Date: Sun Jan 23 18:17:17 2011 +0000 > > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > > The opregion is a shared memory region between ACPI and the graphics > driver. As the ACPI mapping has been changed to cachable in commit > 6d5bbf00d251cc73223a71422d69e069dc2e0b8d, mapping the intel opregion > non-cachable now fails. As no bus-master hardware is involved in the > opregion, cachable map should do no harm. > > Tested on a Fujitsu Lifebook P8010. > > Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > [ickle: convert to acpi_os_ioremap for consistency] > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > thoughts? once again, the salient output from "lspci -v": Indeed looks like using ioremap_cache is not as safe as was assumed. Does diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h index 7180013..42108ab 100644 --- a/include/linux/acpi_io.h +++ b/include/linux/acpi_io.h @@ -7,7 +7,7 @@ static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, acpi_size size) { - return ioremap_cache(phys, size); + return ioremap_wc(phys, size); } int acpi_os_map_generic_address(struct acpi_generic_address *addr); fix your boot issue or do we need to go back to using uncached: + return ioremap(phys, size); -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 14:02 ` Chris Wilson @ 2011-01-28 14:10 ` Robert P. J. Day 2011-01-28 14:32 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 14:10 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 08:53:59 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > so the culprit appears to be: > > > > b705120e4198315f4ae043de06c62f65e0851fd3 is the first bad commit > > commit b705120e4198315f4ae043de06c62f65e0851fd3 > > Author: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > Date: Sun Jan 23 18:17:17 2011 +0000 > > > > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > > > > The opregion is a shared memory region between ACPI and the graphics > > driver. As the ACPI mapping has been changed to cachable in commit > > 6d5bbf00d251cc73223a71422d69e069dc2e0b8d, mapping the intel opregion > > non-cachable now fails. As no bus-master hardware is involved in the > > opregion, cachable map should do no harm. > > > > Tested on a Fujitsu Lifebook P8010. > > > > Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > [ickle: convert to acpi_os_ioremap for consistency] > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > > > > thoughts? once again, the salient output from "lspci -v": > > Indeed looks like using ioremap_cache is not as safe as was assumed. Does *sigh*. there was, in fact, an "ioremap_error" message displayed *very* early in the boot sequence, but it was generated even for successful boots so i never paid it any mind. in hindsight, might have been useful to have mentioned it. > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > index 7180013..42108ab 100644 > --- a/include/linux/acpi_io.h > +++ b/include/linux/acpi_io.h > @@ -7,7 +7,7 @@ > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > acpi_size size) > { > - return ioremap_cache(phys, size); > + return ioremap_wc(phys, size); > } > > int acpi_os_map_generic_address(struct acpi_generic_address *addr); ok, i'll make this single change and report back shortly. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] @ 2011-01-28 14:10 ` Robert P. J. Day 0 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 14:10 UTC (permalink / raw) To: Chris Wilson; +Cc: Rafael J. Wysocki, Len Brown, linux-kernel, dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 08:53:59 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > so the culprit appears to be: > > > > b705120e4198315f4ae043de06c62f65e0851fd3 is the first bad commit > > commit b705120e4198315f4ae043de06c62f65e0851fd3 > > Author: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > Date: Sun Jan 23 18:17:17 2011 +0000 > > > > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > > > > The opregion is a shared memory region between ACPI and the graphics > > driver. As the ACPI mapping has been changed to cachable in commit > > 6d5bbf00d251cc73223a71422d69e069dc2e0b8d, mapping the intel opregion > > non-cachable now fails. As no bus-master hardware is involved in the > > opregion, cachable map should do no harm. > > > > Tested on a Fujitsu Lifebook P8010. > > > > Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > [ickle: convert to acpi_os_ioremap for consistency] > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > > > > thoughts? once again, the salient output from "lspci -v": > > Indeed looks like using ioremap_cache is not as safe as was assumed. Does *sigh*. there was, in fact, an "ioremap_error" message displayed *very* early in the boot sequence, but it was generated even for successful boots so i never paid it any mind. in hindsight, might have been useful to have mentioned it. > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > index 7180013..42108ab 100644 > --- a/include/linux/acpi_io.h > +++ b/include/linux/acpi_io.h > @@ -7,7 +7,7 @@ > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > acpi_size size) > { > - return ioremap_cache(phys, size); > + return ioremap_wc(phys, size); > } > > int acpi_os_map_generic_address(struct acpi_generic_address *addr); ok, i'll make this single change and report back shortly. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 14:02 ` Chris Wilson 2011-01-28 14:10 ` Robert P. J. Day @ 2011-01-28 14:32 ` Robert P. J. Day 2011-01-28 14:36 ` Chris Wilson 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 14:32 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 08:53:59 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > so the culprit appears to be: > > > > b705120e4198315f4ae043de06c62f65e0851fd3 is the first bad commit > > commit b705120e4198315f4ae043de06c62f65e0851fd3 > > Author: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > Date: Sun Jan 23 18:17:17 2011 +0000 > > > > drm/i915: Use consistent mappings for OpRegion between ACPI and i915 > > > > The opregion is a shared memory region between ACPI and the graphics > > driver. As the ACPI mapping has been changed to cachable in commit > > 6d5bbf00d251cc73223a71422d69e069dc2e0b8d, mapping the intel opregion > > non-cachable now fails. As no bus-master hardware is involved in the > > opregion, cachable map should do no harm. > > > > Tested on a Fujitsu Lifebook P8010. > > > > Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de> > > [ickle: convert to acpi_os_ioremap for consistency] > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > > > > > thoughts? once again, the salient output from "lspci -v": > > Indeed looks like using ioremap_cache is not as safe as was assumed. Does > > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > index 7180013..42108ab 100644 > --- a/include/linux/acpi_io.h > +++ b/include/linux/acpi_io.h > @@ -7,7 +7,7 @@ > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > acpi_size size) > { > - return ioremap_cache(phys, size); > + return ioremap_wc(phys, size); > } > > int acpi_os_map_generic_address(struct acpi_generic_address *addr); that didn't appear to make a difference. same black screen issue. BTW, here's an excerpt from /var/log/dmesg for a *successful* boot (i just rebooted to 8a327f23): ... [ 24.037114] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled ... [ 27.155660] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 27.155665] i915 0000:00:02.0: setting latency timer to 64 [ 27.217407] mtrr: no more MTRRs available [ 27.217411] [drm] MTRR allocation failed. Graphics performance may suffer. [ 27.217848] ioremap error for 0xb3752000-0xb3755000, requested 0x10, got 0x0 [ 27.217933] i915 0000:00:02.0: irq 42 for MSI/MSI-X [ 27.217938] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 27.217940] [drm] Driver supports precise vblank timestamp query. ... if any of that is of any use. > fix your boot issue or do we need to go back to using uncached: > > + return ioremap(phys, size); is that the next change you want me to try? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 14:32 ` Robert P. J. Day @ 2011-01-28 14:36 ` Chris Wilson 0 siblings, 0 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 14:36 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011 09:32:04 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > fix your boot issue or do we need to go back to using uncached: > > > > + return ioremap(phys, size); > > is that the next change you want me to try? Yes. (Replacing the current return ioremap_*(phys, size).) -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] @ 2011-01-28 14:36 ` Chris Wilson 0 siblings, 0 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 14:36 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011 09:32:04 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > fix your boot issue or do we need to go back to using uncached: > > > > + return ioremap(phys, size); > > is that the next change you want me to try? Yes. (Replacing the current return ioremap_*(phys, size).) -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 14:36 ` Chris Wilson (?) @ 2011-01-28 14:51 ` Robert P. J. Day 2011-01-28 15:04 ` Chris Wilson -1 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 14:51 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 09:32:04 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > fix your boot issue or do we need to go back to using uncached: > > > > > > + return ioremap(phys, size); > > > > is that the next change you want me to try? > > Yes. (Replacing the current return ioremap_*(phys, size).) sadly, no change -- still black screen. again, rebooted successfully under commit 8a327f23. just to be clear, here's "git diff": $ git diff diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h index 7180013..e035f3c 100644 --- a/include/linux/acpi_io.h +++ b/include/linux/acpi_io.h @@ -7,7 +7,7 @@ static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, acpi_size size) { - return ioremap_cache(phys, size); + return ioremap(phys, size); } int acpi_os_map_generic_address(struct acpi_generic_address *addr); rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 14:51 ` Robert P. J. Day @ 2011-01-28 15:04 ` Chris Wilson 0 siblings, 0 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 15:04 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > sadly, no change -- still black screen. again, rebooted > successfully under commit 8a327f23. just to be clear, here's "git > diff": > > $ git diff > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > index 7180013..e035f3c 100644 > --- a/include/linux/acpi_io.h > +++ b/include/linux/acpi_io.h > @@ -7,7 +7,7 @@ > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > acpi_size size) > { > - return ioremap_cache(phys, size); > + return ioremap(phys, size); > } Ok, that implies the new mapping is fine and not the cause of the issue. Instead you have some OpRegion related regression hidden until till now because the conflicting mapping disabled it for i915. That would be easy to test by returning early in intel_opregion_setup(): diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_ index 9efccb9..8c93201 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) u32 asls, mboxes; int err = 0; + return -ENOTSUPP; + pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); if (asls == 0) { -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] @ 2011-01-28 15:04 ` Chris Wilson 0 siblings, 0 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 15:04 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > sadly, no change -- still black screen. again, rebooted > successfully under commit 8a327f23. just to be clear, here's "git > diff": > > $ git diff > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > index 7180013..e035f3c 100644 > --- a/include/linux/acpi_io.h > +++ b/include/linux/acpi_io.h > @@ -7,7 +7,7 @@ > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > acpi_size size) > { > - return ioremap_cache(phys, size); > + return ioremap(phys, size); > } Ok, that implies the new mapping is fine and not the cause of the issue. Instead you have some OpRegion related regression hidden until till now because the conflicting mapping disabled it for i915. That would be easy to test by returning early in intel_opregion_setup(): diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_ index 9efccb9..8c93201 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) u32 asls, mboxes; int err = 0; + return -ENOTSUPP; + pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); if (asls == 0) { -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:04 ` Chris Wilson (?) @ 2011-01-28 15:08 ` Robert P. J. Day 2011-01-28 15:11 ` Chris Wilson 2011-01-28 20:12 ` Rafael J. Wysocki -1 siblings, 2 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 15:08 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel, Len Brown, Rafael J. Wysocki, linux-kernel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > sadly, no change -- still black screen. again, rebooted > > successfully under commit 8a327f23. just to be clear, here's "git > > diff": > > > > $ git diff > > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > > index 7180013..e035f3c 100644 > > --- a/include/linux/acpi_io.h > > +++ b/include/linux/acpi_io.h > > @@ -7,7 +7,7 @@ > > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > > acpi_size size) > > { > > - return ioremap_cache(phys, size); > > + return ioremap(phys, size); > > } > > Ok, that implies the new mapping is fine and not the cause of the issue. > > Instead you have some OpRegion related regression hidden until till now > because the conflicting mapping disabled it for i915. > > That would be easy to test by returning early in intel_opregion_setup(): > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > b/drivers/gpu/drm/i915/intel_ > index 9efccb9..8c93201 100644 > --- a/drivers/gpu/drm/i915/intel_opregion.c > +++ b/drivers/gpu/drm/i915/intel_opregion.c > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > u32 asls, mboxes; > int err = 0; > > + return -ENOTSUPP; > + > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > if (asls == 0) { > so you want me to revert to a stock b705120e before doing the above? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:08 ` Robert P. J. Day @ 2011-01-28 15:11 ` Chris Wilson 2011-01-28 15:27 ` Robert P. J. Day 2011-01-28 20:12 ` Rafael J. Wysocki 1 sibling, 1 reply; 49+ messages in thread From: Chris Wilson @ 2011-01-28 15:11 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Fri, 28 Jan 2011 10:08:07 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > That would be easy to test by returning early in intel_opregion_setup(): > > > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > > b/drivers/gpu/drm/i915/intel_ > > index 9efccb9..8c93201 100644 > > --- a/drivers/gpu/drm/i915/intel_opregion.c > > +++ b/drivers/gpu/drm/i915/intel_opregion.c > > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > > u32 asls, mboxes; > > int err = 0; > > > > + return -ENOTSUPP; > > + > > > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > > if (asls == 0) { > > > > so you want me to revert to a stock b705120e before doing the above? Yes. (Or latter, at this point we have lots of fun ahead.) -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:11 ` Chris Wilson @ 2011-01-28 15:27 ` Robert P. J. Day 2011-01-28 15:39 ` Chris Wilson 0 siblings, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 15:27 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 10:08:07 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > That would be easy to test by returning early in intel_opregion_setup(): > > > > > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > > > b/drivers/gpu/drm/i915/intel_ > > > index 9efccb9..8c93201 100644 > > > --- a/drivers/gpu/drm/i915/intel_opregion.c > > > +++ b/drivers/gpu/drm/i915/intel_opregion.c > > > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > > > u32 asls, mboxes; > > > int err = 0; > > > > > > + return -ENOTSUPP; > > > + > > > > > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > > > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > > > if (asls == 0) { > > > > > > > so you want me to revert to a stock b705120e before doing the above? > > Yes. (Or latter, at this point we have lots of fun ahead.) victory is mine! ok, that premature return seems to have solved it, i'm up and running under this new kernel. are we getting close? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:27 ` Robert P. J. Day @ 2011-01-28 15:39 ` Chris Wilson 2011-01-28 15:54 ` Robert P. J. Day 2011-01-28 16:30 ` Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 15:39 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Fri, 28 Jan 2011 10:27:09 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > victory is mine! ok, that premature return seems to have solved it, > i'm up and running under this new kernel. are we getting close? Not even close. We just disabled functionality that was working in 2.6.37; the interaction between ACPI and gfx. What a shame. Instead of return -ENOTSUPP at the start, you can return 0 before each of the if (mboxes & MBOX_*) to narrow down which function regressed. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:39 ` Chris Wilson @ 2011-01-28 15:54 ` Robert P. J. Day 2011-01-28 16:03 ` Chris Wilson 2011-01-28 16:30 ` Robert P. J. Day 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 15:54 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 10:27:09 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > victory is mine! ok, that premature return seems to have solved it, > > i'm up and running under this new kernel. are we getting close? > > Not even close. We just disabled functionality that was working in 2.6.37; > the interaction between ACPI and gfx. What a shame. > > Instead of return -ENOTSUPP at the start, > you can return 0 before each of the if (mboxes & MBOX_*) to narrow down > which function regressed. ok, i'll see how much of that i can get to today. but at this point, are we fairly convinced that there *is* a problem? i'd hate to go through all this, only to learn at the end that it's something stupid i did. it seems odd that no one else has mentioned running into this -- have you heard no other reports? so, before i launch into this, is there anything else i might report about my system and its current setup that someone might want to know? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:54 ` Robert P. J. Day @ 2011-01-28 16:03 ` Chris Wilson 2011-01-28 16:23 ` Robert P. J. Day 2011-02-01 12:05 ` Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 16:03 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Fri, 28 Jan 2011 10:54:20 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > On Fri, 28 Jan 2011 10:27:09 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > victory is mine! ok, that premature return seems to have solved it, > > > i'm up and running under this new kernel. are we getting close? > > > > Not even close. We just disabled functionality that was working in 2.6.37; > > the interaction between ACPI and gfx. What a shame. > > > > Instead of return -ENOTSUPP at the start, > > you can return 0 before each of the if (mboxes & MBOX_*) to narrow down > > which function regressed. > > ok, i'll see how much of that i can get to today. but at this > point, are we fairly convinced that there *is* a problem? i'd hate to > go through all this, only to learn at the end that it's something > stupid i did. it seems odd that no one else has mentioned running > into this -- have you heard no other reports? We're starting to get into ACPI backlight breakage territory... We have identified that the regression was much earlier, just masked by other breakage. Let's clarify the symptoms: black panel, no backlight, no output at all (not even at shallow angles), but the machine is alive? Can you remotely access the machine and grab debug logs from when it is broken? > so, before i launch into this, is there anything else i might report > about my system and its current setup that someone might want to know? We're now just looking for telltale signs of an error. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 16:03 ` Chris Wilson @ 2011-01-28 16:23 ` Robert P. J. Day 2011-01-28 16:30 ` Chris Wilson 2011-02-01 12:05 ` Robert P. J. Day 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 16:23 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > We're starting to get into ACPI backlight breakage territory... We > have identified that the regression was much earlier, just masked by > other breakage. as additional info, i went through this for a while during the 2.6.37-rc* progression. it came, it went, it came back again. then everything was fine with both 2.6.38-rc1 and 2.6.38-rc2, and then this. this is on a gateway NV79 laptop running a fully-updated ubuntu 10.10. > Let's clarify the symptoms: black panel, no backlight, no output at > all (not even at shallow angles), but the machine is alive? exactly, same as it's always been when things fail. that the machine is still booting is obvious from lots of disk activity, culminating in the little ubuntu drum roll at the login screen. and, as i mentioned before, i do get a couple early kernel messages (/dev/pts, ureadahead), and that's where it goes black. for a *good* boot, what i would see at that point is the font size getting much smaller and the boot continuing. > Can you remotely access the machine and grab debug logs from when it > is broken? i'd love to, but can't at the moment. i'll see if i can scare up a second machine later and try it. if i can, what *precisely* would you like me to post? i'm guessing dmesg, Xorg.0.log, that sort of thing. > > so, before i launch into this, is there anything else i might > > report about my system and its current setup that someone might > > want to know? > > We're now just looking for telltale signs of an error. all right. and since we're beyond git bisection, can you post a list of say 2 or 3 tests you want me to try in order? as you're the expert here, it would make more sense for you to try to optimize the search pattern here. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 16:23 ` Robert P. J. Day @ 2011-01-28 16:30 ` Chris Wilson 2011-01-28 18:38 ` Robert P. J. Day 2011-01-29 10:02 ` Robert P. J. Day 0 siblings, 2 replies; 49+ messages in thread From: Chris Wilson @ 2011-01-28 16:30 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Fri, 28 Jan 2011 11:23:08 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > all right. and since we're beyond git bisection, can you post a > list of say 2 or 3 tests you want me to try in order? as you're the > expert here, it would make more sense for you to try to optimize the > search pattern here. If the machine is booting (just with a blank screen), then enable drm.debug=0xe, and check that it is being written to the system log files. Then boot into the broken setup, reboot and grab the debug messages saved from the previous (broken) boot. Otherwise we shall just wait for the opportunity to log in with a second machine and look for telltales before beginning exploratory surgery. -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 16:30 ` Chris Wilson @ 2011-01-28 18:38 ` Robert P. J. Day 2011-01-29 10:02 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 18:38 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 11:23:08 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > all right. and since we're beyond git bisection, can you post a > > list of say 2 or 3 tests you want me to try in order? as you're the > > expert here, it would make more sense for you to try to optimize the > > search pattern here. > > If the machine is booting (just with a blank screen), then enable > drm.debug=0xe, and check that it is being written to the system log > files. Then boot into the broken setup, reboot and grab the debug > messages saved from the previous (broken) boot. > > Otherwise we shall just wait for the opportunity to log in with a second > machine and look for telltales before beginning exploratory surgery. ok, this is what works: ========== $ git diff diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion. index 64fd644..645581f 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -495,10 +495,15 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; } + +return 0; // rday + if (mboxes & MBOX_ASLE) { DRM_DEBUG_DRIVER("ASLE supported\n"); opregion->asle = base + OPREGION_ASLE_OFFSET; ========== *first*, i added the *later* "return 0", and still got the black screen. i then added the one *above* that, and got a good boot, so one therefore concludes that it's the "SWSCI" processing that's causing the problem. of course, that says nothing about whether or not the later "ASLE" check could be re-enabled, or does that even make any sense? in any event, what's above works. next? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 16:30 ` Chris Wilson 2011-01-28 18:38 ` Robert P. J. Day @ 2011-01-29 10:02 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-29 10:02 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel i realize i already posted this to the LKML and CCed it here but, just to summarize, i have a current "git pull" kernel booting fine, with the following patch applied: diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c index 64fd644..28adc6d 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -495,6 +495,8 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; feel free to suggest more testing. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 16:03 ` Chris Wilson 2011-01-28 16:23 ` Robert P. J. Day @ 2011-02-01 12:05 ` Robert P. J. Day 2011-02-01 12:12 ` Chris Wilson 1 sibling, 1 reply; 49+ messages in thread From: Robert P. J. Day @ 2011-02-01 12:05 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel any new developments on this issue? the current kernel is working just fine with the addition of that trivial hack in drivers/gpu/drm/i915/intel_opregion.c: @@ -495,6 +495,8 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; but i'm obviously still interested in the proper resolution. let me know if you want me to do any more testing. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-02-01 12:05 ` Robert P. J. Day @ 2011-02-01 12:12 ` Chris Wilson 2011-02-01 12:56 ` Robert P. J. Day 0 siblings, 1 reply; 49+ messages in thread From: Chris Wilson @ 2011-02-01 12:12 UTC (permalink / raw) To: Robert P. J. Day; +Cc: dri-devel On Tue, 1 Feb 2011 07:05:16 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > any new developments on this issue? Not really, the only thing left to confirm is whereabouts it goes wrong. About the only routine of significance is alse_set_backlight(). Does a 'return ASLE_BACKLIGHT_FAILED;' as the first line of that function have a similar effect to the current hack? -Chris -- Chris Wilson, Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-02-01 12:12 ` Chris Wilson @ 2011-02-01 12:56 ` Robert P. J. Day 0 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-02-01 12:56 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Tue, 1 Feb 2011, Chris Wilson wrote: > On Tue, 1 Feb 2011 07:05:16 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > any new developments on this issue? > > Not really, the only thing left to confirm is whereabouts it goes wrong. > > About the only routine of significance is alse_set_backlight(). > > Does a 'return ASLE_BACKLIGHT_FAILED;' as the first line of that function > have a similar effect to the current hack? apparently, it does: @@ -150,6 +150,8 @@ static u32 asle_set_backlight(struct drm_device *dev, u32 bclp) struct opregion_asle *asle = dev_priv->opregion.asle; u32 max; +return ASLE_BACKLIGHT_FAILED; // rday + if (!(bclp & ASLE_BCLP_VALID)) return ASLE_BACKLIGHT_FAILED; gives me a good boot. this is the diff with relation to the recently tagged 2.6.38-rc3. anything else you want me to test? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:39 ` Chris Wilson 2011-01-28 15:54 ` Robert P. J. Day @ 2011-01-28 16:30 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 16:30 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel [-- Attachment #1: Type: TEXT/PLAIN, Size: 1273 bytes --] On Fri, 28 Jan 2011, Chris Wilson wrote: > On Fri, 28 Jan 2011 10:27:09 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > victory is mine! ok, that premature return seems to have solved it, > > i'm up and running under this new kernel. are we getting close? > > Not even close. We just disabled functionality that was working in > 2.6.37; the interaction between ACPI and gfx. What a shame. > > Instead of return -ENOTSUPP at the start, you can return 0 before > each of the if (mboxes & MBOX_*) to narrow down which function > regressed. are there any kernel config options i should be looking at? for better or worse, i've attached my .config file. and i'm sequentially returning 0 before each of those tests starting with the last and working my way back unless you want to prioritize which tests i should deactivate. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== [-- Attachment #2: Type: TEXT/PLAIN, Size: 104728 bytes --] # # Automatically generated make config: don't edit # Linux/x86_64 2.6.38-rc2 Kernel Configuration # Fri Jan 28 07:36:39 2011 # CONFIG_64BIT=y # CONFIG_X86_32 is not set CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_HAVE_LATENCYTOP_SUPPORT=y CONFIG_MMU=y CONFIG_ZONE_DMA=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_GENERIC_GPIO=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_DEFAULT_IDLE=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_HAVE_CPUMASK_OF_CPU_MAP=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ZONE_DMA32=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_64_SMP=y CONFIG_X86_HT=y CONFIG_X86_TRAMPOLINE=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" # CONFIG_KTIME_SCALAR is not set CONFIG_ARCH_CPU_PROBE_RELEASE=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y CONFIG_HAVE_IRQ_WORK=y CONFIG_IRQ_WORK=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_BSD_PROCESS_ACCT_V3=y CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_AUDIT_WATCH=y CONFIG_AUDIT_TREE=y CONFIG_HAVE_GENERIC_HARDIRQS=y # # IRQ subsystem # CONFIG_GENERIC_HARDIRQS=y # CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED is not set CONFIG_HAVE_SPARSE_IRQ=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_PENDING_IRQ=y # CONFIG_AUTO_IRQ_AFFINITY is not set # CONFIG_IRQ_PER_CPU is not set # CONFIG_HARDIRQS_SW_RESEND is not set CONFIG_SPARSE_IRQ=y # # RCU Subsystem # CONFIG_TREE_RCU=y # CONFIG_PREEMPT_RCU is not set # CONFIG_RCU_TRACE is not set CONFIG_RCU_FANOUT=64 # CONFIG_RCU_FANOUT_EXACT is not set CONFIG_RCU_FAST_NO_HZ=y # CONFIG_TREE_RCU_TRACE is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=18 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_CGROUPS=y # CONFIG_CGROUP_DEBUG is not set CONFIG_CGROUP_NS=y CONFIG_CGROUP_FREEZER=y CONFIG_CGROUP_DEVICE=y CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_CPUACCT=y CONFIG_RESOURCE_COUNTERS=y CONFIG_CGROUP_MEM_RES_CTLR=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED=y CONFIG_CGROUP_SCHED=y CONFIG_FAIR_GROUP_SCHED=y CONFIG_RT_GROUP_SCHED=y # CONFIG_BLK_CGROUP is not set CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y # CONFIG_SCHED_AUTOGROUP is not set CONFIG_MM_OWNER=y # CONFIG_SYSFS_DEPRECATED is not set CONFIG_RELAY=y CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_RD_BZIP2=y CONFIG_RD_LZMA=y CONFIG_RD_XZ=y CONFIG_RD_LZO=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SYSCTL=y CONFIG_ANON_INODES=y # CONFIG_EXPERT is not set # CONFIG_EMBEDDED is not set CONFIG_UID16=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_KALLSYMS_ALL=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_PCSPKR_PLATFORM=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_PERF_EVENTS=y CONFIG_PERF_COUNTERS=y # CONFIG_DEBUG_PERF_USE_VMALLOC is not set CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB_DEBUG=y # CONFIG_COMPAT_BRK is not set # CONFIG_SLAB is not set CONFIG_SLUB=y CONFIG_PROFILING=y CONFIG_TRACEPOINTS=y CONFIG_OPROFILE=m # CONFIG_OPROFILE_EVENT_MULTIPLEX is not set CONFIG_HAVE_OPROFILE=y CONFIG_KPROBES=y # CONFIG_JUMP_LABEL is not set CONFIG_OPTPROBES=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_KRETPROBES=y CONFIG_USER_RETURN_NOTIFIER=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_OPTPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_USE_GENERIC_SMP_HELPERS=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y CONFIG_HAVE_HW_BREAKPOINT=y CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y CONFIG_HAVE_USER_RETURN_NOTIFIER=y CONFIG_HAVE_PERF_EVENTS_NMI=y CONFIG_HAVE_ARCH_JUMP_LABEL=y # # GCOV-based kernel profiling # # CONFIG_GCOV_KERNEL is not set # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_SLABINFO=y CONFIG_RT_MUTEXES=y CONFIG_BASE_SMALL=0 CONFIG_MODULES=y # CONFIG_MODULE_FORCE_LOAD is not set CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_MODVERSIONS=y CONFIG_MODULE_SRCVERSION_ALL=y CONFIG_STOP_MACHINE=y CONFIG_BLOCK=y CONFIG_BLK_DEV_BSG=y CONFIG_BLK_DEV_INTEGRITY=y CONFIG_BLOCK_COMPAT=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_DEFAULT_DEADLINE is not set CONFIG_DEFAULT_CFQ=y # CONFIG_DEFAULT_NOOP is not set CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_PREEMPT_NOTIFIERS=y CONFIG_PADATA=y # CONFIG_INLINE_SPIN_TRYLOCK is not set # CONFIG_INLINE_SPIN_TRYLOCK_BH is not set # CONFIG_INLINE_SPIN_LOCK is not set # CONFIG_INLINE_SPIN_LOCK_BH is not set # CONFIG_INLINE_SPIN_LOCK_IRQ is not set # CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set CONFIG_INLINE_SPIN_UNLOCK=y # CONFIG_INLINE_SPIN_UNLOCK_BH is not set CONFIG_INLINE_SPIN_UNLOCK_IRQ=y # CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_READ_TRYLOCK is not set # CONFIG_INLINE_READ_LOCK is not set # CONFIG_INLINE_READ_LOCK_BH is not set # CONFIG_INLINE_READ_LOCK_IRQ is not set # CONFIG_INLINE_READ_LOCK_IRQSAVE is not set CONFIG_INLINE_READ_UNLOCK=y # CONFIG_INLINE_READ_UNLOCK_BH is not set CONFIG_INLINE_READ_UNLOCK_IRQ=y # CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set # CONFIG_INLINE_WRITE_TRYLOCK is not set # CONFIG_INLINE_WRITE_LOCK is not set # CONFIG_INLINE_WRITE_LOCK_BH is not set # CONFIG_INLINE_WRITE_LOCK_IRQ is not set # CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set CONFIG_INLINE_WRITE_UNLOCK=y # CONFIG_INLINE_WRITE_UNLOCK_BH is not set CONFIG_INLINE_WRITE_UNLOCK_IRQ=y # CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_FREEZER=y # # Processor type and features # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_SMP=y CONFIG_X86_X2APIC=y CONFIG_X86_MPPARSE=y CONFIG_X86_EXTENDED_PLATFORM=y # CONFIG_X86_VSMP is not set # CONFIG_X86_UV is not set CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_PARAVIRT_GUEST=y CONFIG_XEN=y CONFIG_XEN_DOM0=y CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PVHVM=y CONFIG_XEN_MAX_DOMAIN_MEMORY=128 CONFIG_XEN_SAVE_RESTORE=y # CONFIG_XEN_DEBUG_FS is not set CONFIG_KVM_CLOCK=y CONFIG_KVM_GUEST=y CONFIG_PARAVIRT=y CONFIG_PARAVIRT_SPINLOCKS=y CONFIG_PARAVIRT_CLOCK=y # CONFIG_PARAVIRT_DEBUG is not set CONFIG_NO_BOOTMEM=y # CONFIG_MEMTEST is not set # CONFIG_MK8 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set # CONFIG_MATOM is not set CONFIG_GENERIC_CPU=y CONFIG_X86_CPU=y CONFIG_X86_INTERNODE_CACHE_SHIFT=7 CONFIG_X86_CMPXCHG=y CONFIG_CMPXCHG_LOCAL=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_XADD=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_TSC=y CONFIG_X86_CMPXCHG64=y CONFIG_X86_CMOV=y CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_DEBUGCTLMSR=y CONFIG_CPU_SUP_INTEL=y CONFIG_CPU_SUP_AMD=y CONFIG_CPU_SUP_CENTAUR=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y CONFIG_CALGARY_IOMMU=y CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y CONFIG_AMD_IOMMU=y CONFIG_AMD_IOMMU_STATS=y CONFIG_SWIOTLB=y CONFIG_IOMMU_HELPER=y CONFIG_IOMMU_API=y # CONFIG_MAXSMP is not set CONFIG_NR_CPUS=64 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_IRQ_TIME_ACCOUNTING is not set # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_VOLUNTARY=y # CONFIG_PREEMPT is not set CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_X86_MCE_AMD=y CONFIG_X86_MCE_THRESHOLD=y CONFIG_X86_MCE_INJECT=m CONFIG_X86_THERMAL_VECTOR=y CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_ARCH_DMA_ADDR_T_64BIT=y CONFIG_DIRECT_GBPAGES=y CONFIG_NUMA=y CONFIG_AMD_NUMA=y CONFIG_X86_64_ACPI_NUMA=y CONFIG_NODES_SPAN_OTHER_NODES=y # CONFIG_NUMA_EMU is not set CONFIG_NODES_SHIFT=6 CONFIG_ARCH_PROC_KCORE_TEXT=y CONFIG_ARCH_SPARSEMEM_DEFAULT=y CONFIG_ARCH_SPARSEMEM_ENABLE=y CONFIG_ARCH_SELECT_MEMORY_MODEL=y CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000 CONFIG_SELECT_MEMORY_MODEL=y CONFIG_SPARSEMEM_MANUAL=y CONFIG_SPARSEMEM=y CONFIG_NEED_MULTIPLE_NODES=y CONFIG_HAVE_MEMORY_PRESENT=y CONFIG_SPARSEMEM_EXTREME=y CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y CONFIG_SPARSEMEM_VMEMMAP=y CONFIG_HAVE_MEMBLOCK=y # CONFIG_MEMORY_HOTPLUG is not set CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 # CONFIG_COMPACTION is not set CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_MMU_NOTIFIER=y CONFIG_KSM=y CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y CONFIG_MEMORY_FAILURE=y # CONFIG_HWPOISON_INJECT is not set # CONFIG_TRANSPARENT_HUGEPAGE is not set CONFIG_X86_CHECK_BIOS_CORRUPTION=y CONFIG_X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK=y CONFIG_X86_RESERVE_LOW=64 CONFIG_MTRR=y CONFIG_MTRR_SANITIZER=y CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0 CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 CONFIG_X86_PAT=y CONFIG_ARCH_USES_PG_UNCACHED=y CONFIG_EFI=y CONFIG_SECCOMP=y CONFIG_CC_STACKPROTECTOR=y CONFIG_HZ_100=y # CONFIG_HZ_250 is not set # CONFIG_HZ_300 is not set # CONFIG_HZ_1000 is not set CONFIG_HZ=100 CONFIG_SCHED_HRTICK=y CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_KEXEC_JUMP=y CONFIG_PHYSICAL_START=0x200000 CONFIG_RELOCATABLE=y CONFIG_PHYSICAL_ALIGN=0x1000000 CONFIG_HOTPLUG_CPU=y # CONFIG_COMPAT_VDSO is not set # CONFIG_CMDLINE_BOOL is not set CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y CONFIG_USE_PERCPU_NUMA_NODE_ID=y # # Power management and ACPI options # CONFIG_ARCH_HIBERNATION_HEADER=y CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_PM_ADVANCED_DEBUG is not set # CONFIG_PM_VERBOSE is not set CONFIG_CAN_PM_TRACE=y CONFIG_PM_TRACE=y CONFIG_PM_TRACE_RTC=y CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y CONFIG_SUSPEND=y CONFIG_PM_TEST_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_PM_RUNTIME=y CONFIG_PM_OPS=y CONFIG_ACPI=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROCFS_POWER=y CONFIG_ACPI_POWER_METER=m # CONFIG_ACPI_EC_DEBUGFS is not set CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=y CONFIG_ACPI_DOCK=y CONFIG_ACPI_PROCESSOR=y # CONFIG_ACPI_IPMI is not set CONFIG_ACPI_HOTPLUG_CPU=y CONFIG_ACPI_PROCESSOR_AGGREGATOR=m CONFIG_ACPI_THERMAL=y CONFIG_ACPI_NUMA=y CONFIG_ACPI_CUSTOM_DSDT_FILE="" # CONFIG_ACPI_CUSTOM_DSDT is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_PCI_SLOT=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y CONFIG_ACPI_SBS=y CONFIG_ACPI_HED=m CONFIG_ACPI_APEI=y CONFIG_ACPI_APEI_GHES=m CONFIG_ACPI_APEI_EINJ=m # CONFIG_ACPI_APEI_ERST_DEBUG is not set CONFIG_SFI=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y # # CPUFreq processor drivers # CONFIG_X86_PCC_CPUFREQ=m CONFIG_X86_ACPI_CPUFREQ=y CONFIG_X86_POWERNOW_K8=y CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_P4_CLOCKMOD=m # # shared options # CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y CONFIG_INTEL_IDLE=y # # Memory power savings # CONFIG_I7300_IDLE_IOAT_CHANNEL=y CONFIG_I7300_IDLE=m # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y CONFIG_PCI_XEN=y CONFIG_PCI_DOMAINS=y # CONFIG_PCI_CNB20LE_QUIRK is not set # CONFIG_DMAR is not set CONFIG_INTR_REMAP=y CONFIG_PCIEPORTBUS=y CONFIG_HOTPLUG_PCI_PCIE=y CONFIG_PCIEAER=y # CONFIG_PCIE_ECRC is not set # CONFIG_PCIEAER_INJECT is not set CONFIG_PCIEASPM=y # CONFIG_PCIEASPM_DEBUG is not set CONFIG_PCIE_PME=y CONFIG_ARCH_SUPPORTS_MSI=y CONFIG_PCI_MSI=y # CONFIG_PCI_DEBUG is not set CONFIG_PCI_STUB=m CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_HT_IRQ=y # CONFIG_PCI_IOV is not set CONFIG_PCI_IOAPIC=y CONFIG_ISA_DMA_API=y CONFIG_AMD_NB=y # CONFIG_PCCARD is not set CONFIG_HOTPLUG_PCI=y CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_ACPI=m CONFIG_HOTPLUG_PCI_ACPI_IBM=m CONFIG_HOTPLUG_PCI_CPCI=y CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m CONFIG_HOTPLUG_PCI_SHPC=m # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_COMPAT_BINFMT_ELF=y # CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set # CONFIG_HAVE_AOUT is not set CONFIG_BINFMT_MISC=m CONFIG_IA32_EMULATION=y # CONFIG_IA32_AOUT is not set CONFIG_COMPAT=y CONFIG_COMPAT_FOR_U64_ALIGNMENT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_HAVE_TEXT_POKE_SMP=y CONFIG_NET=y CONFIG_COMPAT_NETLINK_MESSAGES=y # # Networking options # CONFIG_PACKET=y CONFIG_UNIX=y CONFIG_XFRM=y CONFIG_XFRM_USER=m # CONFIG_XFRM_SUB_POLICY is not set # CONFIG_XFRM_MIGRATE is not set # CONFIG_XFRM_STATISTICS is not set CONFIG_XFRM_IPCOMP=m CONFIG_NET_KEY=m # CONFIG_NET_KEY_MIGRATE is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_ASK_IP_FIB_HASH=y # CONFIG_IP_FIB_TRIE is not set CONFIG_IP_FIB_HASH=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m # CONFIG_NET_IPGRE_DEMUX is not set CONFIG_IP_MROUTE=y # CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set CONFIG_IP_PIMSM_V1=y CONFIG_IP_PIMSM_V2=y # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y CONFIG_INET_AH=m CONFIG_INET_ESP=m CONFIG_INET_IPCOMP=m CONFIG_INET_XFRM_TUNNEL=m CONFIG_INET_TUNNEL=m CONFIG_INET_XFRM_MODE_TRANSPORT=m CONFIG_INET_XFRM_MODE_TUNNEL=m CONFIG_INET_XFRM_MODE_BEET=m CONFIG_INET_LRO=y CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_ADVANCED=y CONFIG_TCP_CONG_BIC=m CONFIG_TCP_CONG_CUBIC=y CONFIG_TCP_CONG_WESTWOOD=m CONFIG_TCP_CONG_HTCP=m CONFIG_TCP_CONG_HSTCP=m CONFIG_TCP_CONG_HYBLA=m CONFIG_TCP_CONG_VEGAS=m CONFIG_TCP_CONG_SCALABLE=m CONFIG_TCP_CONG_LP=m CONFIG_TCP_CONG_VENO=m CONFIG_TCP_CONG_YEAH=m CONFIG_TCP_CONG_ILLINOIS=m CONFIG_DEFAULT_CUBIC=y # CONFIG_DEFAULT_RENO is not set CONFIG_DEFAULT_TCP_CONG="cubic" CONFIG_TCP_MD5SIG=y CONFIG_IPV6=y CONFIG_IPV6_PRIVACY=y # CONFIG_IPV6_ROUTER_PREF is not set # CONFIG_IPV6_OPTIMISTIC_DAD is not set CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m # CONFIG_IPV6_MIP6 is not set CONFIG_INET6_XFRM_TUNNEL=m CONFIG_INET6_TUNNEL=m CONFIG_INET6_XFRM_MODE_TRANSPORT=m CONFIG_INET6_XFRM_MODE_TUNNEL=m CONFIG_INET6_XFRM_MODE_BEET=m CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m CONFIG_IPV6_SIT=m CONFIG_IPV6_SIT_6RD=y CONFIG_IPV6_NDISC_NODETYPE=y CONFIG_IPV6_TUNNEL=m CONFIG_IPV6_MULTIPLE_TABLES=y # CONFIG_IPV6_SUBTREES is not set # CONFIG_IPV6_MROUTE is not set CONFIG_NETLABEL=y CONFIG_NETWORK_SECMARK=y # CONFIG_NETWORK_PHY_TIMESTAMPING is not set CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_NETFILTER_ADVANCED=y CONFIG_BRIDGE_NETFILTER=y # # Core Netfilter Configuration # CONFIG_NETFILTER_NETLINK=m CONFIG_NETFILTER_NETLINK_QUEUE=m CONFIG_NETFILTER_NETLINK_LOG=m CONFIG_NF_CONNTRACK=m CONFIG_NF_CONNTRACK_MARK=y CONFIG_NF_CONNTRACK_SECMARK=y CONFIG_NF_CONNTRACK_ZONES=y CONFIG_NF_CONNTRACK_EVENTS=y CONFIG_NF_CT_PROTO_DCCP=m CONFIG_NF_CT_PROTO_GRE=m CONFIG_NF_CT_PROTO_SCTP=m CONFIG_NF_CT_PROTO_UDPLITE=m CONFIG_NF_CONNTRACK_AMANDA=m CONFIG_NF_CONNTRACK_FTP=m CONFIG_NF_CONNTRACK_H323=m CONFIG_NF_CONNTRACK_IRC=m CONFIG_NF_CONNTRACK_NETBIOS_NS=m CONFIG_NF_CONNTRACK_PPTP=m CONFIG_NF_CONNTRACK_SANE=m CONFIG_NF_CONNTRACK_SIP=m CONFIG_NF_CONNTRACK_TFTP=m CONFIG_NF_CT_NETLINK=m CONFIG_NETFILTER_TPROXY=m CONFIG_NETFILTER_XTABLES=m # # Xtables combined modules # CONFIG_NETFILTER_XT_MARK=m CONFIG_NETFILTER_XT_CONNMARK=m # # Xtables targets # # CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m CONFIG_NETFILTER_XT_TARGET_CONNMARK=m CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m CONFIG_NETFILTER_XT_TARGET_CT=m CONFIG_NETFILTER_XT_TARGET_DSCP=m CONFIG_NETFILTER_XT_TARGET_HL=m # CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set CONFIG_NETFILTER_XT_TARGET_LED=m CONFIG_NETFILTER_XT_TARGET_MARK=m CONFIG_NETFILTER_XT_TARGET_NFLOG=m CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m CONFIG_NETFILTER_XT_TARGET_NOTRACK=m CONFIG_NETFILTER_XT_TARGET_RATEEST=m CONFIG_NETFILTER_XT_TARGET_TEE=m CONFIG_NETFILTER_XT_TARGET_TPROXY=m CONFIG_NETFILTER_XT_TARGET_TRACE=m CONFIG_NETFILTER_XT_TARGET_SECMARK=m CONFIG_NETFILTER_XT_TARGET_TCPMSS=m # CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set # # Xtables matches # CONFIG_NETFILTER_XT_MATCH_CLUSTER=m CONFIG_NETFILTER_XT_MATCH_COMMENT=m CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m CONFIG_NETFILTER_XT_MATCH_CONNMARK=m CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m # CONFIG_NETFILTER_XT_MATCH_CPU is not set CONFIG_NETFILTER_XT_MATCH_DCCP=m CONFIG_NETFILTER_XT_MATCH_DSCP=m CONFIG_NETFILTER_XT_MATCH_ESP=m CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m CONFIG_NETFILTER_XT_MATCH_HELPER=m CONFIG_NETFILTER_XT_MATCH_HL=m CONFIG_NETFILTER_XT_MATCH_IPRANGE=m # CONFIG_NETFILTER_XT_MATCH_IPVS is not set CONFIG_NETFILTER_XT_MATCH_LENGTH=m CONFIG_NETFILTER_XT_MATCH_LIMIT=m CONFIG_NETFILTER_XT_MATCH_MAC=m CONFIG_NETFILTER_XT_MATCH_MARK=m CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m CONFIG_NETFILTER_XT_MATCH_OSF=m CONFIG_NETFILTER_XT_MATCH_OWNER=m CONFIG_NETFILTER_XT_MATCH_POLICY=m CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m CONFIG_NETFILTER_XT_MATCH_QUOTA=m CONFIG_NETFILTER_XT_MATCH_RATEEST=m CONFIG_NETFILTER_XT_MATCH_REALM=m CONFIG_NETFILTER_XT_MATCH_RECENT=m CONFIG_NETFILTER_XT_MATCH_SCTP=m CONFIG_NETFILTER_XT_MATCH_SOCKET=m CONFIG_NETFILTER_XT_MATCH_STATE=m CONFIG_NETFILTER_XT_MATCH_STATISTIC=m CONFIG_NETFILTER_XT_MATCH_STRING=m CONFIG_NETFILTER_XT_MATCH_TCPMSS=m CONFIG_NETFILTER_XT_MATCH_TIME=m CONFIG_NETFILTER_XT_MATCH_U32=m CONFIG_IP_VS=m CONFIG_IP_VS_IPV6=y # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_AH_ESP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y CONFIG_IP_VS_PROTO_SCTP=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS application helper # CONFIG_IP_VS_FTP=m CONFIG_IP_VS_NFCT=y # CONFIG_IP_VS_PE_SIP is not set # # IP: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV4=m CONFIG_NF_CONNTRACK_IPV4=m CONFIG_NF_CONNTRACK_PROC_COMPAT=y CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_ADDRTYPE=m CONFIG_IP_NF_MATCH_AH=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_NF_NAT_SNMP_BASIC=m CONFIG_NF_NAT_PROTO_DCCP=m CONFIG_NF_NAT_PROTO_GRE=m CONFIG_NF_NAT_PROTO_UDPLITE=m CONFIG_NF_NAT_PROTO_SCTP=m CONFIG_NF_NAT_FTP=m CONFIG_NF_NAT_IRC=m CONFIG_NF_NAT_TFTP=m CONFIG_NF_NAT_AMANDA=m CONFIG_NF_NAT_PPTP=m CONFIG_NF_NAT_H323=m CONFIG_NF_NAT_SIP=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_CLUSTERIP=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_TTL=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_SECURITY=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration # CONFIG_NF_DEFRAG_IPV6=m CONFIG_NF_CONNTRACK_IPV6=m CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_RAW=m CONFIG_IP6_NF_SECURITY=m CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_IP6=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m CONFIG_BRIDGE_EBT_ULOG=m CONFIG_BRIDGE_EBT_NFLOG=m # CONFIG_IP_DCCP is not set CONFIG_IP_SCTP=m CONFIG_NET_SCTPPROBE=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set # CONFIG_SCTP_HMAC_NONE is not set # CONFIG_SCTP_HMAC_SHA1 is not set CONFIG_SCTP_HMAC_MD5=y # CONFIG_RDS is not set # CONFIG_TIPC is not set # CONFIG_ATM is not set CONFIG_L2TP=m CONFIG_L2TP_DEBUGFS=m # CONFIG_L2TP_V3 is not set CONFIG_STP=m CONFIG_GARP=m CONFIG_BRIDGE=m CONFIG_BRIDGE_IGMP_SNOOPING=y CONFIG_NET_DSA=y CONFIG_NET_DSA_TAG_DSA=y CONFIG_NET_DSA_TAG_EDSA=y CONFIG_NET_DSA_TAG_TRAILER=y CONFIG_NET_DSA_MV88E6XXX=y CONFIG_NET_DSA_MV88E6060=y CONFIG_NET_DSA_MV88E6XXX_NEED_PPU=y CONFIG_NET_DSA_MV88E6131=y CONFIG_NET_DSA_MV88E6123_61_65=y CONFIG_VLAN_8021Q=m CONFIG_VLAN_8021Q_GVRP=y # CONFIG_DECNET is not set CONFIG_LLC=y CONFIG_LLC2=m # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_ECONET is not set CONFIG_WAN_ROUTER=m # CONFIG_PHONET is not set # CONFIG_IEEE802154 is not set CONFIG_NET_SCHED=y # # Queueing/Scheduling # CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_MULTIQ=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m CONFIG_NET_SCH_NETEM=m CONFIG_NET_SCH_DRR=m CONFIG_NET_SCH_INGRESS=m # # Classification # CONFIG_NET_CLS=y CONFIG_NET_CLS_BASIC=m CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m # CONFIG_CLS_U32_PERF is not set CONFIG_CLS_U32_MARK=y CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m CONFIG_NET_CLS_FLOW=m CONFIG_NET_CLS_CGROUP=y CONFIG_NET_EMATCH=y CONFIG_NET_EMATCH_STACK=32 CONFIG_NET_EMATCH_CMP=m CONFIG_NET_EMATCH_NBYTE=m CONFIG_NET_EMATCH_U32=m CONFIG_NET_EMATCH_META=m CONFIG_NET_EMATCH_TEXT=m CONFIG_NET_CLS_ACT=y CONFIG_NET_ACT_POLICE=m CONFIG_NET_ACT_GACT=m CONFIG_GACT_PROB=y CONFIG_NET_ACT_MIRRED=m CONFIG_NET_ACT_IPT=m CONFIG_NET_ACT_NAT=m CONFIG_NET_ACT_PEDIT=m CONFIG_NET_ACT_SIMP=m CONFIG_NET_ACT_SKBEDIT=m # CONFIG_NET_ACT_CSUM is not set # CONFIG_NET_CLS_IND is not set CONFIG_NET_SCH_FIFO=y CONFIG_DCB=y CONFIG_DNS_RESOLVER=y # CONFIG_BATMAN_ADV is not set CONFIG_RPS=y CONFIG_XPS=y # # Network testing # CONFIG_NET_PKTGEN=m CONFIG_NET_TCPPROBE=m # CONFIG_NET_DROP_MONITOR is not set # CONFIG_HAMRADIO is not set # CONFIG_CAN is not set # CONFIG_IRDA is not set # CONFIG_BT is not set CONFIG_AF_RXRPC=m # CONFIG_AF_RXRPC_DEBUG is not set CONFIG_RXKAD=m CONFIG_FIB_RULES=y CONFIG_WIRELESS=y CONFIG_WIRELESS_EXT=y CONFIG_WEXT_CORE=y CONFIG_WEXT_PROC=y CONFIG_WEXT_SPY=y CONFIG_WEXT_PRIV=y CONFIG_CFG80211=m # CONFIG_NL80211_TESTMODE is not set # CONFIG_CFG80211_DEVELOPER_WARNINGS is not set CONFIG_CFG80211_REG_DEBUG=y CONFIG_CFG80211_DEFAULT_PS=y CONFIG_CFG80211_DEBUGFS=y # CONFIG_CFG80211_INTERNAL_REGDB is not set CONFIG_CFG80211_WEXT=y CONFIG_WIRELESS_EXT_SYSFS=y CONFIG_LIB80211=m CONFIG_LIB80211_CRYPT_WEP=m CONFIG_LIB80211_CRYPT_CCMP=m CONFIG_LIB80211_CRYPT_TKIP=m # CONFIG_LIB80211_DEBUG is not set CONFIG_MAC80211=m CONFIG_MAC80211_HAS_RC=y CONFIG_MAC80211_RC_MINSTREL=y CONFIG_MAC80211_RC_MINSTREL_HT=y CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y CONFIG_MAC80211_RC_DEFAULT="minstrel_ht" CONFIG_MAC80211_MESH=y CONFIG_MAC80211_LEDS=y CONFIG_MAC80211_DEBUGFS=y # CONFIG_MAC80211_DEBUG_MENU is not set CONFIG_WIMAX=m CONFIG_WIMAX_DEBUG_LEVEL=8 CONFIG_RFKILL=y CONFIG_RFKILL_LEDS=y CONFIG_RFKILL_INPUT=y # CONFIG_NET_9P is not set # CONFIG_CAIF is not set CONFIG_CEPH_LIB=m # CONFIG_CEPH_LIB_PRETTYDEBUG is not set # # Device Drivers # # # Generic Driver Options # CONFIG_UEVENT_HELPER_PATH="" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y # CONFIG_STANDALONE is not set CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set CONFIG_SYS_HYPERVISOR=y CONFIG_CONNECTOR=y CONFIG_PROC_EVENTS=y # CONFIG_MTD is not set # CONFIG_PARPORT is not set CONFIG_PNP=y CONFIG_PNP_DEBUG_MESSAGES=y # # Protocols # CONFIG_PNPACPI=y CONFIG_BLK_DEV=y CONFIG_BLK_DEV_FD=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_CISS_SCSI_TAPE=y CONFIG_BLK_DEV_DAC960=m CONFIG_BLK_DEV_UMEM=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_DRBD=m # CONFIG_DRBD_FAULT_INJECTION is not set CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_OSD=m CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=65536 # CONFIG_BLK_DEV_XIP is not set CONFIG_CDROM_PKTCDVD=y CONFIG_CDROM_PKTCDVD_BUFFERS=8 # CONFIG_CDROM_PKTCDVD_WCACHE is not set CONFIG_ATA_OVER_ETH=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_VIRTIO_BLK=m # CONFIG_BLK_DEV_HD is not set # CONFIG_BLK_DEV_RBD is not set CONFIG_MISC_DEVICES=y CONFIG_AD525X_DPOT=m CONFIG_AD525X_DPOT_I2C=m CONFIG_IBM_ASM=m CONFIG_PHANTOM=m CONFIG_SGI_IOC4=m CONFIG_TIFM_CORE=m CONFIG_TIFM_7XX1=m CONFIG_ICS932S401=m CONFIG_ENCLOSURE_SERVICES=m # CONFIG_CS5535_MFGPT is not set CONFIG_HP_ILO=m # CONFIG_APDS9802ALS is not set CONFIG_ISL29003=m # CONFIG_ISL29020 is not set CONFIG_SENSORS_TSL2550=m # CONFIG_SENSORS_BH1780 is not set # CONFIG_SENSORS_BH1770 is not set # CONFIG_SENSORS_APDS990X is not set # CONFIG_HMC6352 is not set CONFIG_DS1682=m CONFIG_VMWARE_BALLOON=m # CONFIG_BMP085 is not set # CONFIG_PCH_PHUB is not set CONFIG_C2PORT=m CONFIG_C2PORT_DURAMAR_2150=m # # EEPROM support # CONFIG_EEPROM_AT24=m CONFIG_EEPROM_LEGACY=m CONFIG_EEPROM_MAX6875=m CONFIG_EEPROM_93CX6=m CONFIG_CB710_CORE=m # CONFIG_CB710_DEBUG is not set CONFIG_CB710_DEBUG_ASSUMPTIONS=y CONFIG_IWMC3200TOP=m # CONFIG_IWMC3200TOP_DEBUG is not set CONFIG_IWMC3200TOP_DEBUGFS=y # # Texas Instruments shared transport line discipline # CONFIG_TI_ST=m CONFIG_HAVE_IDE=y # CONFIG_IDE is not set # # SCSI device support # CONFIG_SCSI_MOD=y CONFIG_RAID_ATTRS=m CONFIG_SCSI=y CONFIG_SCSI_DMA=y CONFIG_SCSI_TGT=m CONFIG_SCSI_NETLINK=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=m CONFIG_CHR_DEV_OSST=m CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y CONFIG_CHR_DEV_SCH=m CONFIG_SCSI_ENCLOSURE=m CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y CONFIG_SCSI_SCAN_ASYNC=y CONFIG_SCSI_WAIT_SCAN=m # # SCSI Transports # CONFIG_SCSI_SPI_ATTRS=m CONFIG_SCSI_FC_ATTRS=m CONFIG_SCSI_FC_TGT_ATTRS=y CONFIG_SCSI_ISCSI_ATTRS=m CONFIG_SCSI_SAS_ATTRS=m CONFIG_SCSI_SAS_LIBSAS=m CONFIG_SCSI_SAS_ATA=y CONFIG_SCSI_SAS_HOST_SMP=y # CONFIG_SCSI_SAS_LIBSAS_DEBUG is not set CONFIG_SCSI_SRP_ATTRS=m CONFIG_SCSI_SRP_TGT_ATTRS=y CONFIG_SCSI_LOWLEVEL=y CONFIG_ISCSI_TCP=m CONFIG_ISCSI_BOOT_SYSFS=m CONFIG_SCSI_CXGB3_ISCSI=m # CONFIG_SCSI_CXGB4_ISCSI is not set CONFIG_SCSI_BNX2_ISCSI=m CONFIG_BE2ISCSI=m CONFIG_BLK_DEV_3W_XXXX_RAID=m CONFIG_SCSI_HPSA=m CONFIG_SCSI_3W_9XXX=m CONFIG_SCSI_3W_SAS=m CONFIG_SCSI_ACARD=m CONFIG_SCSI_AACRAID=m CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=8 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 CONFIG_AIC7XXX_DEBUG_ENABLE=y CONFIG_AIC7XXX_DEBUG_MASK=0 CONFIG_AIC7XXX_REG_PRETTY_PRINT=y # CONFIG_SCSI_AIC7XXX_OLD is not set CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=32 CONFIG_AIC79XX_RESET_DELAY_MS=5000 CONFIG_AIC79XX_DEBUG_ENABLE=y CONFIG_AIC79XX_DEBUG_MASK=0 CONFIG_AIC79XX_REG_PRETTY_PRINT=y CONFIG_SCSI_AIC94XX=m # CONFIG_AIC94XX_DEBUG is not set CONFIG_SCSI_MVSAS=m CONFIG_SCSI_MVSAS_DEBUG=y CONFIG_SCSI_DPT_I2O=m CONFIG_SCSI_ADVANSYS=m CONFIG_SCSI_ARCMSR=m CONFIG_SCSI_ARCMSR_AER=y CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=m CONFIG_MEGARAID_MAILBOX=m CONFIG_MEGARAID_LEGACY=m CONFIG_MEGARAID_SAS=m CONFIG_SCSI_MPT2SAS=m CONFIG_SCSI_MPT2SAS_MAX_SGE=128 # CONFIG_SCSI_MPT2SAS_LOGGING is not set CONFIG_SCSI_HPTIOP=m CONFIG_SCSI_BUSLOGIC=m CONFIG_VMWARE_PVSCSI=m CONFIG_LIBFC=m CONFIG_LIBFCOE=m CONFIG_FCOE=m CONFIG_FCOE_FNIC=m CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_EATA=m CONFIG_SCSI_EATA_TAGGED_QUEUE=y CONFIG_SCSI_EATA_LINKED_COMMANDS=y CONFIG_SCSI_EATA_MAX_TAGS=16 CONFIG_SCSI_FUTURE_DOMAIN=m CONFIG_SCSI_GDTH=m CONFIG_SCSI_IPS=m CONFIG_SCSI_INITIO=m CONFIG_SCSI_INIA100=m CONFIG_SCSI_STEX=m CONFIG_SCSI_SYM53C8XX_2=m CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 CONFIG_SCSI_SYM53C8XX_MMIO=y CONFIG_SCSI_IPR=m # CONFIG_SCSI_IPR_TRACE is not set # CONFIG_SCSI_IPR_DUMP is not set CONFIG_SCSI_QLOGIC_1280=m CONFIG_SCSI_QLA_FC=m CONFIG_SCSI_QLA_ISCSI=m CONFIG_SCSI_LPFC=m CONFIG_SCSI_LPFC_DEBUG_FS=y CONFIG_SCSI_DC395x=m CONFIG_SCSI_DC390T=m CONFIG_SCSI_DEBUG=m CONFIG_SCSI_PMCRAID=m CONFIG_SCSI_PM8001=m CONFIG_SCSI_SRP=m CONFIG_SCSI_BFA_FC=m CONFIG_SCSI_DH=y CONFIG_SCSI_DH_RDAC=m CONFIG_SCSI_DH_HP_SW=m CONFIG_SCSI_DH_EMC=m CONFIG_SCSI_DH_ALUA=m CONFIG_SCSI_OSD_INITIATOR=m CONFIG_SCSI_OSD_ULD=m CONFIG_SCSI_OSD_DPRINT_SENSE=1 # CONFIG_SCSI_OSD_DEBUG is not set CONFIG_ATA=y # CONFIG_ATA_NONSTANDARD is not set CONFIG_ATA_VERBOSE_ERROR=y CONFIG_ATA_ACPI=y CONFIG_SATA_PMP=y # # Controllers with non-SFF native interface # CONFIG_SATA_AHCI=m CONFIG_SATA_AHCI_PLATFORM=m CONFIG_SATA_INIC162X=m # CONFIG_SATA_ACARD_AHCI is not set CONFIG_SATA_SIL24=m CONFIG_ATA_SFF=y # # SFF controllers with custom DMA interface # CONFIG_PDC_ADMA=y CONFIG_SATA_QSTOR=m CONFIG_SATA_SX4=m CONFIG_ATA_BMDMA=y # # SATA SFF controllers with BMDMA # CONFIG_ATA_PIIX=y CONFIG_SATA_MV=m CONFIG_SATA_NV=m CONFIG_SATA_PROMISE=m CONFIG_SATA_SIL=m CONFIG_SATA_SIS=m CONFIG_SATA_SVW=m CONFIG_SATA_ULI=m CONFIG_SATA_VIA=m CONFIG_SATA_VITESSE=m # # PATA SFF controllers with BMDMA # CONFIG_PATA_ALI=m CONFIG_PATA_AMD=m CONFIG_PATA_ARTOP=m CONFIG_PATA_ATIIXP=m CONFIG_PATA_ATP867X=m CONFIG_PATA_CMD64X=m CONFIG_PATA_CS5520=m CONFIG_PATA_CS5530=m # CONFIG_PATA_CS5536 is not set CONFIG_PATA_CYPRESS=m CONFIG_PATA_EFAR=m CONFIG_PATA_HPT366=m CONFIG_PATA_HPT37X=m CONFIG_PATA_HPT3X2N=m CONFIG_PATA_HPT3X3=m # CONFIG_PATA_HPT3X3_DMA is not set CONFIG_PATA_IT8213=m CONFIG_PATA_IT821X=m CONFIG_PATA_JMICRON=m CONFIG_PATA_MARVELL=m CONFIG_PATA_NETCELL=m CONFIG_PATA_NINJA32=m CONFIG_PATA_NS87415=m CONFIG_PATA_OLDPIIX=m CONFIG_PATA_OPTIDMA=m CONFIG_PATA_PDC2027X=m CONFIG_PATA_PDC_OLD=m CONFIG_PATA_RADISYS=m CONFIG_PATA_RDC=m CONFIG_PATA_SC1200=m CONFIG_PATA_SCH=m CONFIG_PATA_SERVERWORKS=m CONFIG_PATA_SIL680=m CONFIG_PATA_SIS=y # CONFIG_PATA_TOSHIBA is not set CONFIG_PATA_TRIFLEX=m CONFIG_PATA_VIA=m CONFIG_PATA_WINBOND=m # # PIO-only SFF controllers # CONFIG_PATA_CMD640_PCI=m CONFIG_PATA_MPIIX=m CONFIG_PATA_NS87410=m CONFIG_PATA_OPTI=m CONFIG_PATA_RZ1000=m # # Generic fallback / legacy drivers # CONFIG_PATA_ACPI=y CONFIG_ATA_GENERIC=y CONFIG_PATA_LEGACY=m CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_AUTODETECT=y CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m CONFIG_MD_RAID10=m CONFIG_MD_RAID456=m # CONFIG_MULTICORE_RAID456 is not set CONFIG_MD_MULTIPATH=m CONFIG_MD_FAULTY=m CONFIG_BLK_DEV_DM=y # CONFIG_DM_DEBUG is not set CONFIG_DM_CRYPT=m CONFIG_DM_SNAPSHOT=y CONFIG_DM_MIRROR=y # CONFIG_DM_RAID is not set # CONFIG_DM_LOG_USERSPACE is not set CONFIG_DM_ZERO=m CONFIG_DM_MULTIPATH=y CONFIG_DM_MULTIPATH_QL=m CONFIG_DM_MULTIPATH_ST=m # CONFIG_DM_DELAY is not set CONFIG_DM_UEVENT=y # CONFIG_TARGET_CORE is not set # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # CONFIG_FIREWIRE=m CONFIG_FIREWIRE_OHCI=m CONFIG_FIREWIRE_OHCI_DEBUG=y CONFIG_FIREWIRE_SBP2=m CONFIG_FIREWIRE_NET=m # CONFIG_FIREWIRE_NOSY is not set # CONFIG_I2O is not set # CONFIG_MACINTOSH_DRIVERS is not set CONFIG_NETDEVICES=y CONFIG_IFB=m CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_MACVLAN=m # CONFIG_MACVTAP is not set CONFIG_EQUALIZER=m CONFIG_TUN=y CONFIG_VETH=m CONFIG_NET_SB1000=m CONFIG_ARCNET=m CONFIG_ARCNET_1201=m CONFIG_ARCNET_1051=m CONFIG_ARCNET_RAW=m CONFIG_ARCNET_CAP=m CONFIG_ARCNET_COM90xx=m CONFIG_ARCNET_COM90xxIO=m CONFIG_ARCNET_RIM_I=m CONFIG_ARCNET_COM20020=m CONFIG_ARCNET_COM20020_PCI=m CONFIG_MII=m CONFIG_PHYLIB=y # # MII PHY device drivers # CONFIG_MARVELL_PHY=y CONFIG_DAVICOM_PHY=y CONFIG_QSEMI_PHY=y CONFIG_LXT_PHY=y CONFIG_CICADA_PHY=y CONFIG_VITESSE_PHY=y CONFIG_SMSC_PHY=y CONFIG_BROADCOM_PHY=y # CONFIG_BCM63XX_PHY is not set CONFIG_ICPLUS_PHY=y CONFIG_REALTEK_PHY=y CONFIG_NATIONAL_PHY=y CONFIG_STE10XP=y CONFIG_LSI_ET1011C_PHY=y CONFIG_MICREL_PHY=m CONFIG_FIXED_PHY=y CONFIG_MDIO_BITBANG=y CONFIG_MDIO_GPIO=y CONFIG_NET_ETHERNET=y CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_CASSINI=m CONFIG_NET_VENDOR_3COM=y CONFIG_VORTEX=m CONFIG_TYPHOON=m CONFIG_ETHOC=m CONFIG_DNET=m CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_DE2104X_DSL=0 CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_ULI526X=m CONFIG_HP100=m # CONFIG_IBM_NEW_EMAC_ZMII is not set # CONFIG_IBM_NEW_EMAC_RGMII is not set # CONFIG_IBM_NEW_EMAC_TAH is not set # CONFIG_IBM_NEW_EMAC_EMAC4 is not set # CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set CONFIG_NET_PCI=y CONFIG_PCNET32=m CONFIG_AMD8111_ETH=m CONFIG_ADAPTEC_STARFIRE=m CONFIG_KSZ884X_PCI=m CONFIG_B44=m CONFIG_B44_PCI_AUTOSELECT=y CONFIG_B44_PCICORE_AUTOSELECT=y CONFIG_B44_PCI=y CONFIG_FORCEDETH=m CONFIG_E100=m CONFIG_FEALNX=m CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_8139CP=m CONFIG_8139TOO=m CONFIG_8139TOO_PIO=y # CONFIG_8139TOO_TUNE_TWISTER is not set CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_R6040 is not set CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SMSC9420=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m CONFIG_KS8842=m CONFIG_KS8851_MLL=m CONFIG_VIA_RHINE=m CONFIG_VIA_RHINE_MMIO=y CONFIG_SC92031=m CONFIG_ATL2=m CONFIG_NETDEV_1000=y CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set # CONFIG_DL2K is not set CONFIG_E1000=m CONFIG_E1000E=m CONFIG_IP1000=m CONFIG_IGB=m CONFIG_IGB_DCA=y CONFIG_IGBVF=m CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m CONFIG_R8169=m CONFIG_R8169_VLAN=y CONFIG_SIS190=m CONFIG_SKGE=m # CONFIG_SKGE_DEBUG is not set CONFIG_SKY2=m # CONFIG_SKY2_DEBUG is not set CONFIG_VIA_VELOCITY=m CONFIG_TIGON3=m CONFIG_BNX2=m CONFIG_CNIC=m CONFIG_QLA3XXX=m CONFIG_ATL1=m CONFIG_ATL1E=m CONFIG_ATL1C=m CONFIG_JME=m # CONFIG_STMMAC_ETH is not set # CONFIG_PCH_GBE is not set CONFIG_NETDEV_10000=y CONFIG_MDIO=m CONFIG_CHELSIO_T1=m CONFIG_CHELSIO_T1_1G=y CONFIG_CHELSIO_T3_DEPENDS=y CONFIG_CHELSIO_T3=m CONFIG_CHELSIO_T4_DEPENDS=y CONFIG_CHELSIO_T4=m CONFIG_CHELSIO_T4VF_DEPENDS=y # CONFIG_CHELSIO_T4VF is not set CONFIG_ENIC=m CONFIG_IXGBE=m CONFIG_IXGBE_DCA=y CONFIG_IXGBE_DCB=y CONFIG_IXGBEVF=m CONFIG_IXGB=m CONFIG_S2IO=m CONFIG_VXGE=m # CONFIG_VXGE_DEBUG_TRACE_ALL is not set CONFIG_MYRI10GE=m CONFIG_MYRI10GE_DCA=y CONFIG_NETXEN_NIC=m CONFIG_NIU=m CONFIG_MLX4_EN=m CONFIG_MLX4_CORE=m CONFIG_MLX4_DEBUG=y CONFIG_TEHUTI=m CONFIG_BNX2X=m CONFIG_QLCNIC=m CONFIG_QLGE=m # CONFIG_BNA is not set CONFIG_SFC=m CONFIG_BE2NET=m CONFIG_TR=y CONFIG_IBMOL=m CONFIG_3C359=m CONFIG_TMS380TR=m CONFIG_TMSPCI=m CONFIG_ABYSS=m CONFIG_WLAN=y CONFIG_LIBERTAS_THINFIRM=m # CONFIG_LIBERTAS_THINFIRM_DEBUG is not set CONFIG_LIBERTAS_THINFIRM_USB=m CONFIG_AIRO=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m CONFIG_AT76C50X_USB=m CONFIG_PRISM54=m CONFIG_USB_ZD1201=m CONFIG_USB_NET_RNDIS_WLAN=m CONFIG_RTL8180=m CONFIG_RTL8187=m CONFIG_RTL8187_LEDS=y CONFIG_ADM8211=m CONFIG_MAC80211_HWSIM=m CONFIG_MWL8K=m CONFIG_ATH_COMMON=m # CONFIG_ATH_DEBUG is not set CONFIG_ATH5K=m # CONFIG_ATH5K_DEBUG is not set CONFIG_ATH5K_PCI=y CONFIG_ATH9K_HW=m CONFIG_ATH9K_COMMON=m CONFIG_ATH9K=m CONFIG_ATH9K_DEBUGFS=y CONFIG_ATH9K_RATE_CONTROL=y CONFIG_ATH9K_HTC=m CONFIG_ATH9K_HTC_DEBUGFS=y CONFIG_AR9170_USB=m CONFIG_AR9170_LEDS=y # CONFIG_CARL9170 is not set CONFIG_B43=m CONFIG_B43_PCI_AUTOSELECT=y CONFIG_B43_PCICORE_AUTOSELECT=y # CONFIG_B43_SDIO is not set CONFIG_B43_PIO=y # CONFIG_B43_PHY_N is not set CONFIG_B43_PHY_LP=y CONFIG_B43_LEDS=y CONFIG_B43_HWRNG=y # CONFIG_B43_DEBUG is not set CONFIG_B43LEGACY=m CONFIG_B43LEGACY_PCI_AUTOSELECT=y CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y CONFIG_B43LEGACY_LEDS=y CONFIG_B43LEGACY_HWRNG=y CONFIG_B43LEGACY_DEBUG=y CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_PIO=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set # CONFIG_B43LEGACY_PIO_MODE is not set CONFIG_HOSTAP=m CONFIG_HOSTAP_FIRMWARE=y CONFIG_HOSTAP_FIRMWARE_NVRAM=y CONFIG_HOSTAP_PLX=m CONFIG_HOSTAP_PCI=m CONFIG_IPW2100=m CONFIG_IPW2100_MONITOR=y # CONFIG_IPW2100_DEBUG is not set CONFIG_IPW2200=m CONFIG_IPW2200_MONITOR=y CONFIG_IPW2200_RADIOTAP=y CONFIG_IPW2200_PROMISCUOUS=y CONFIG_IPW2200_QOS=y # CONFIG_IPW2200_DEBUG is not set CONFIG_LIBIPW=m CONFIG_LIBIPW_DEBUG=y CONFIG_IWLWIFI=m # # Debugging Options # # CONFIG_IWLWIFI_DEBUG is not set # CONFIG_IWLWIFI_DEBUGFS is not set CONFIG_IWLWIFI_DEVICE_TRACING=y CONFIG_IWLAGN=m CONFIG_IWL4965=y CONFIG_IWL5000=y CONFIG_IWL3945=m CONFIG_IWM=m # CONFIG_IWM_DEBUG is not set CONFIG_IWM_TRACING=y CONFIG_LIBERTAS=m CONFIG_LIBERTAS_USB=m CONFIG_LIBERTAS_SDIO=m # CONFIG_LIBERTAS_DEBUG is not set CONFIG_LIBERTAS_MESH=y CONFIG_HERMES=m # CONFIG_HERMES_PRISM is not set CONFIG_HERMES_CACHE_FW_ON_INIT=y CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_NORTEL_HERMES=m CONFIG_ORINOCO_USB=m CONFIG_P54_COMMON=m CONFIG_P54_USB=m CONFIG_P54_PCI=m CONFIG_P54_LEDS=y CONFIG_RT2X00=m CONFIG_RT2400PCI=m CONFIG_RT2500PCI=m CONFIG_RT61PCI=m CONFIG_RT2800PCI=m # CONFIG_RT2800PCI_RT33XX is not set CONFIG_RT2800PCI_RT35XX=y CONFIG_RT2500USB=m CONFIG_RT73USB=m CONFIG_RT2800USB=m # CONFIG_RT2800USB_RT33XX is not set # CONFIG_RT2800USB_RT35XX is not set CONFIG_RT2800USB_UNKNOWN=y CONFIG_RT2800_LIB=m CONFIG_RT2X00_LIB_PCI=m CONFIG_RT2X00_LIB_USB=m CONFIG_RT2X00_LIB=m CONFIG_RT2X00_LIB_HT=y CONFIG_RT2X00_LIB_FIRMWARE=y CONFIG_RT2X00_LIB_CRYPTO=y CONFIG_RT2X00_LIB_LEDS=y # CONFIG_RT2X00_LIB_DEBUGFS is not set # CONFIG_RT2X00_DEBUG is not set # CONFIG_RTL8192CE is not set CONFIG_WL1251=m CONFIG_WL1251_SDIO=m # CONFIG_WL12XX_MENU is not set CONFIG_WL12XX_PLATFORM_DATA=y CONFIG_ZD1211RW=m # CONFIG_ZD1211RW_DEBUG is not set # # WiMAX Wireless Broadband devices # CONFIG_WIMAX_I2400M=m CONFIG_WIMAX_I2400M_USB=m CONFIG_WIMAX_I2400M_SDIO=m CONFIG_WIMAX_IWMC3200_SDIO=y CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8 # # USB Network Adapters # CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_CDC_EEM=m CONFIG_USB_NET_CDC_NCM=m CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_SMSC75XX=m CONFIG_USB_NET_SMSC95XX=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m # CONFIG_USB_NET_CX82310_ETH is not set CONFIG_USB_HSO=m CONFIG_USB_NET_INT51X1=m CONFIG_USB_IPHETH=m CONFIG_USB_SIERRA_NET=m CONFIG_WAN=y CONFIG_LANMEDIA=m CONFIG_HDLC=m CONFIG_HDLC_RAW=m CONFIG_HDLC_RAW_ETH=m CONFIG_HDLC_CISCO=m CONFIG_HDLC_FR=m CONFIG_HDLC_PPP=m # # X.25/LAPB support is disabled # CONFIG_PCI200SYN=m CONFIG_WANXL=m # CONFIG_PC300TOO is not set CONFIG_FARSYNC=m CONFIG_DSCC4=m CONFIG_DSCC4_PCISYNC=y CONFIG_DSCC4_PCI_RST=y CONFIG_DLCI=m CONFIG_DLCI_MAX=8 CONFIG_WAN_ROUTER_DRIVERS=m CONFIG_CYCLADES_SYNC=m CONFIG_CYCLOMX_X25=y CONFIG_SBNI=m # CONFIG_SBNI_MULTILINE is not set # # CAIF transport drivers # CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_FDDI=y CONFIG_DEFXX=m # CONFIG_DEFXX_MMIO is not set CONFIG_SKFP=m CONFIG_HIPPI=y CONFIG_ROADRUNNER=m # CONFIG_ROADRUNNER_LARGE_RINGS is not set CONFIG_PPP=y CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPP_MPPE=m CONFIG_PPPOE=m CONFIG_PPPOL2TP=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLHC=y CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y CONFIG_NET_FC=y CONFIG_NETCONSOLE=m CONFIG_NETCONSOLE_DYNAMIC=y CONFIG_NETPOLL=y # CONFIG_NETPOLL_TRAP is not set CONFIG_NET_POLL_CONTROLLER=y CONFIG_VIRTIO_NET=m CONFIG_VMXNET3=m # CONFIG_ISDN is not set # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y CONFIG_INPUT_FF_MEMLESS=m CONFIG_INPUT_POLLDEV=m CONFIG_INPUT_SPARSEKMAP=m # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_EVDEV=y CONFIG_INPUT_EVBUG=m CONFIG_XEN_KBDDEV_FRONTEND=m # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ADP5588=m CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_QT2160 is not set CONFIG_KEYBOARD_LKKBD=m CONFIG_KEYBOARD_GPIO=m # CONFIG_KEYBOARD_GPIO_POLLED is not set CONFIG_KEYBOARD_TCA6416=m CONFIG_KEYBOARD_MATRIX=m CONFIG_KEYBOARD_LM8323=m CONFIG_KEYBOARD_MAX7359=m # CONFIG_KEYBOARD_MCS is not set CONFIG_KEYBOARD_NEWTON=m CONFIG_KEYBOARD_OPENCORES=m CONFIG_KEYBOARD_STOWAWAY=m CONFIG_KEYBOARD_SUNKBD=m CONFIG_KEYBOARD_XTKBD=m CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=m CONFIG_MOUSE_PS2_ALPS=y CONFIG_MOUSE_PS2_LOGIPS2PP=y CONFIG_MOUSE_PS2_SYNAPTICS=y CONFIG_MOUSE_PS2_LIFEBOOK=y CONFIG_MOUSE_PS2_TRACKPOINT=y CONFIG_MOUSE_PS2_ELANTECH=y CONFIG_MOUSE_PS2_SENTELIC=y # CONFIG_MOUSE_PS2_TOUCHKIT is not set CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_APPLETOUCH=m CONFIG_MOUSE_BCM5974=m CONFIG_MOUSE_VSXXXAA=m CONFIG_MOUSE_GPIO=m CONFIG_MOUSE_SYNAPTICS_I2C=m CONFIG_INPUT_JOYSTICK=y CONFIG_JOYSTICK_ANALOG=m CONFIG_JOYSTICK_A3D=m CONFIG_JOYSTICK_ADI=m CONFIG_JOYSTICK_COBRA=m CONFIG_JOYSTICK_GF2K=m CONFIG_JOYSTICK_GRIP=m CONFIG_JOYSTICK_GRIP_MP=m CONFIG_JOYSTICK_GUILLEMOT=m CONFIG_JOYSTICK_INTERACT=m CONFIG_JOYSTICK_SIDEWINDER=m CONFIG_JOYSTICK_TMDC=m CONFIG_JOYSTICK_IFORCE=m CONFIG_JOYSTICK_IFORCE_USB=y CONFIG_JOYSTICK_IFORCE_232=y CONFIG_JOYSTICK_WARRIOR=m CONFIG_JOYSTICK_MAGELLAN=m CONFIG_JOYSTICK_SPACEORB=m CONFIG_JOYSTICK_SPACEBALL=m CONFIG_JOYSTICK_STINGER=m CONFIG_JOYSTICK_TWIDJOY=m CONFIG_JOYSTICK_ZHENHUA=m # CONFIG_JOYSTICK_AS5011 is not set CONFIG_JOYSTICK_JOYDUMP=m CONFIG_JOYSTICK_XPAD=m CONFIG_JOYSTICK_XPAD_FF=y CONFIG_JOYSTICK_XPAD_LEDS=y CONFIG_INPUT_TABLET=y CONFIG_TABLET_USB_ACECAD=m CONFIG_TABLET_USB_AIPTEK=m CONFIG_TABLET_USB_GTCO=m # CONFIG_TABLET_USB_HANWANG is not set CONFIG_TABLET_USB_KBTAB=m CONFIG_TABLET_USB_WACOM=m # CONFIG_INPUT_TOUCHSCREEN is not set CONFIG_INPUT_MISC=y CONFIG_INPUT_AD714X=m CONFIG_INPUT_AD714X_I2C=m CONFIG_INPUT_PCSPKR=m # CONFIG_INPUT_APANEL is not set CONFIG_INPUT_ATLAS_BTNS=m CONFIG_INPUT_ATI_REMOTE=m CONFIG_INPUT_ATI_REMOTE2=m CONFIG_INPUT_KEYSPAN_REMOTE=m CONFIG_INPUT_POWERMATE=m CONFIG_INPUT_YEALINK=m CONFIG_INPUT_CM109=m CONFIG_INPUT_UINPUT=y CONFIG_INPUT_PCF50633_PMU=m CONFIG_INPUT_PCF8574=m CONFIG_INPUT_GPIO_ROTARY_ENCODER=m # CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_CMA3000 is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m CONFIG_SERIO_CT82C710=m CONFIG_SERIO_PCIPS2=m CONFIG_SERIO_LIBPS2=y CONFIG_SERIO_RAW=m CONFIG_SERIO_ALTERA_PS2=m # CONFIG_SERIO_PS2MULT is not set CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m CONFIG_GAMEPORT_L4=m CONFIG_GAMEPORT_EMU10K1=m CONFIG_GAMEPORT_FM801=m # # Character devices # CONFIG_VT=y CONFIG_CONSOLE_TRANSLATIONS=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_VT_HW_CONSOLE_BINDING=y # CONFIG_DEVKMEM is not set CONFIG_SERIAL_NONSTANDARD=y CONFIG_COMPUTONE=m CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set CONFIG_DIGIEPCA=m CONFIG_MOXA_INTELLIO=m CONFIG_MOXA_SMARTIO=m # CONFIG_ISI is not set CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_SYNCLINK_GT=m CONFIG_N_HDLC=m # CONFIG_N_GSM is not set CONFIG_RISCOM8=m CONFIG_SPECIALIX=m CONFIG_STALDRV=y CONFIG_STALLION=m CONFIG_ISTALLION=m CONFIG_NOZOMI=m # # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_SERIAL_8250_PCI=y CONFIG_SERIAL_8250_PNP=y CONFIG_SERIAL_8250_NR_UARTS=48 CONFIG_SERIAL_8250_RUNTIME_UARTS=4 CONFIG_SERIAL_8250_EXTENDED=y CONFIG_SERIAL_8250_MANY_PORTS=y CONFIG_SERIAL_8250_SHARE_IRQ=y # CONFIG_SERIAL_8250_DETECT_IRQ is not set CONFIG_SERIAL_8250_RSA=y # # Non-8250 serial port support # # CONFIG_SERIAL_MFD_HSU is not set CONFIG_SERIAL_UARTLITE=m CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_CONSOLE_POLL=y CONFIG_SERIAL_JSM=m CONFIG_SERIAL_TIMBERDALE=m CONFIG_SERIAL_ALTERA_JTAGUART=m CONFIG_SERIAL_ALTERA_UART=m CONFIG_SERIAL_ALTERA_UART_MAXPORTS=4 CONFIG_SERIAL_ALTERA_UART_BAUDRATE=115200 # CONFIG_SERIAL_PCH_UART is not set CONFIG_UNIX98_PTYS=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=0 CONFIG_HVC_DRIVER=y CONFIG_HVC_IRQ=y CONFIG_HVC_XEN=y CONFIG_VIRTIO_CONSOLE=m CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m CONFIG_IPMI_POWEROFF=m CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_TIMERIOMEM=m CONFIG_HW_RANDOM_INTEL=m CONFIG_HW_RANDOM_AMD=m CONFIG_HW_RANDOM_VIA=m CONFIG_HW_RANDOM_VIRTIO=m CONFIG_NVRAM=m CONFIG_R3964=m CONFIG_APPLICOM=m CONFIG_MWAVE=m CONFIG_RAW_DRIVER=m CONFIG_MAX_RAW_DEVS=256 CONFIG_HPET=y CONFIG_HPET_MMAP=y CONFIG_HANGCHECK_TIMER=m CONFIG_TCG_TPM=m CONFIG_TCG_TIS=m CONFIG_TCG_NSC=m CONFIG_TCG_ATMEL=m CONFIG_TCG_INFINEON=m CONFIG_TELCLOCK=m CONFIG_DEVPORT=y CONFIG_RAMOOPS=m CONFIG_I2C=m CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=m # CONFIG_I2C_MUX is not set # CONFIG_I2C_HELPER_AUTO is not set CONFIG_I2C_SMBUS=m # # I2C Algorithms # CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCF=m CONFIG_I2C_ALGOPCA=m # # I2C Hardware Bus support # # # PC SMBus host controller drivers # CONFIG_I2C_ALI1535=m CONFIG_I2C_ALI1563=m CONFIG_I2C_ALI15X3=m CONFIG_I2C_AMD756=m CONFIG_I2C_AMD756_S4882=m CONFIG_I2C_AMD8111=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NFORCE2_S4985=m CONFIG_I2C_SIS5595=m CONFIG_I2C_SIS630=m CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m # # ACPI drivers # CONFIG_I2C_SCMI=m # # I2C system bus drivers (mostly embedded / system-on-chip) # CONFIG_I2C_GPIO=m # CONFIG_I2C_INTEL_MID is not set CONFIG_I2C_OCORES=m CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_SIMTEC=m CONFIG_I2C_XILINX=m # CONFIG_I2C_EG20T is not set # # External I2C/SMBus adapter drivers # CONFIG_I2C_PARPORT_LIGHT=m CONFIG_I2C_TAOS_EVM=m CONFIG_I2C_TINY_USB=m # # Other I2C/SMBus bus drivers # CONFIG_I2C_STUB=m # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_SPI is not set # # PPS support # CONFIG_PPS=m # CONFIG_PPS_DEBUG is not set # # PPS clients support # # CONFIG_PPS_CLIENT_KTIMER is not set CONFIG_PPS_CLIENT_LDISC=m # # PPS generators support # CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y CONFIG_GPIOLIB=y # CONFIG_DEBUG_GPIO is not set CONFIG_GPIO_SYSFS=y CONFIG_GPIO_MAX730X=m # # Memory mapped GPIO expanders: # # CONFIG_GPIO_BASIC_MMIO is not set CONFIG_GPIO_IT8761E=m CONFIG_GPIO_SCH=m # CONFIG_GPIO_VX855 is not set # # I2C GPIO expanders: # CONFIG_GPIO_MAX7300=m CONFIG_GPIO_MAX732X=m CONFIG_GPIO_PCA953X=m CONFIG_GPIO_PCF857X=m CONFIG_GPIO_ADP5588=m # # PCI GPIO expanders: # CONFIG_GPIO_CS5535=m CONFIG_GPIO_LANGWELL=y # CONFIG_GPIO_PCH is not set # CONFIG_GPIO_ML_IOH is not set CONFIG_GPIO_TIMBERDALE=y CONFIG_GPIO_RDC321X=m # # SPI GPIO expanders: # # # AC97 GPIO expanders: # CONFIG_GPIO_UCB1400=y # # MODULbus GPIO expanders: # CONFIG_GPIO_JANZ_TTL=m # CONFIG_W1 is not set CONFIG_POWER_SUPPLY=y # CONFIG_POWER_SUPPLY_DEBUG is not set CONFIG_PDA_POWER=m CONFIG_TEST_POWER=m CONFIG_BATTERY_DS2782=m # CONFIG_BATTERY_BQ20Z75 is not set CONFIG_BATTERY_BQ27x00=m CONFIG_BATTERY_MAX17040=m # CONFIG_BATTERY_MAX17042 is not set CONFIG_CHARGER_PCF50633=m # CONFIG_CHARGER_ISP1704 is not set # CONFIG_CHARGER_GPIO is not set CONFIG_HWMON=y CONFIG_HWMON_VID=m # CONFIG_HWMON_DEBUG_CHIP is not set # # Native drivers # CONFIG_SENSORS_ABITUGURU=m CONFIG_SENSORS_ABITUGURU3=m CONFIG_SENSORS_AD7414=m CONFIG_SENSORS_AD7418=m CONFIG_SENSORS_ADM1021=m CONFIG_SENSORS_ADM1025=m CONFIG_SENSORS_ADM1026=m CONFIG_SENSORS_ADM1029=m CONFIG_SENSORS_ADM1031=m CONFIG_SENSORS_ADM9240=m CONFIG_SENSORS_ADT7411=m CONFIG_SENSORS_ADT7462=m CONFIG_SENSORS_ADT7470=m CONFIG_SENSORS_ADT7475=m CONFIG_SENSORS_ASC7621=m CONFIG_SENSORS_K8TEMP=m CONFIG_SENSORS_K10TEMP=m CONFIG_SENSORS_ASB100=m CONFIG_SENSORS_ATXP1=m # CONFIG_SENSORS_DS620 is not set CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_I5K_AMB=m CONFIG_SENSORS_F71805F=m CONFIG_SENSORS_F71882FG=m CONFIG_SENSORS_F75375S=m CONFIG_SENSORS_FSCHMD=m CONFIG_SENSORS_G760A=m CONFIG_SENSORS_GL518SM=m CONFIG_SENSORS_GL520SM=m # CONFIG_SENSORS_GPIO_FAN is not set CONFIG_SENSORS_CORETEMP=m CONFIG_SENSORS_PKGTEMP=m CONFIG_SENSORS_IBMAEM=m CONFIG_SENSORS_IBMPEX=m CONFIG_SENSORS_IT87=m # CONFIG_SENSORS_JC42 is not set CONFIG_SENSORS_LM63=m CONFIG_SENSORS_LM73=m CONFIG_SENSORS_LM75=m CONFIG_SENSORS_LM77=m CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m CONFIG_SENSORS_LM87=m CONFIG_SENSORS_LM90=m CONFIG_SENSORS_LM92=m CONFIG_SENSORS_LM93=m CONFIG_SENSORS_LTC4215=m CONFIG_SENSORS_LTC4245=m # CONFIG_SENSORS_LTC4261 is not set CONFIG_SENSORS_LM95241=m CONFIG_SENSORS_MAX1619=m CONFIG_SENSORS_MAX6650=m CONFIG_SENSORS_PC87360=m CONFIG_SENSORS_PC87427=m CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_SHT15=m # CONFIG_SENSORS_SHT21 is not set CONFIG_SENSORS_SIS5595=m # CONFIG_SENSORS_SMM665 is not set CONFIG_SENSORS_DME1737=m CONFIG_SENSORS_EMC1403=m # CONFIG_SENSORS_EMC2103 is not set CONFIG_SENSORS_SMSC47M1=m CONFIG_SENSORS_SMSC47M192=m CONFIG_SENSORS_SMSC47B397=m CONFIG_SENSORS_ADS7828=m CONFIG_SENSORS_AMC6821=m CONFIG_SENSORS_THMC50=m CONFIG_SENSORS_TMP102=m CONFIG_SENSORS_TMP401=m CONFIG_SENSORS_TMP421=m CONFIG_SENSORS_VIA_CPUTEMP=m CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_VT1211=m CONFIG_SENSORS_VT8231=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83791D=m CONFIG_SENSORS_W83792D=m CONFIG_SENSORS_W83793=m # CONFIG_SENSORS_W83795 is not set CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83L786NG=m CONFIG_SENSORS_W83627HF=m CONFIG_SENSORS_W83627EHF=m CONFIG_SENSORS_LIS3_I2C=m CONFIG_SENSORS_APPLESMC=m # # ACPI drivers # CONFIG_SENSORS_ATK0110=m CONFIG_SENSORS_LIS3LV02D=m CONFIG_THERMAL=y CONFIG_THERMAL_HWMON=y CONFIG_WATCHDOG=y # CONFIG_WATCHDOG_NOWAYOUT is not set # # Watchdog Device Drivers # CONFIG_SOFT_WATCHDOG=m CONFIG_ACQUIRE_WDT=m CONFIG_ADVANTECH_WDT=m CONFIG_ALIM1535_WDT=m CONFIG_ALIM7101_WDT=m # CONFIG_F71808E_WDT is not set # CONFIG_SP5100_TCO is not set CONFIG_SC520_WDT=m CONFIG_SBC_FITPC2_WATCHDOG=m CONFIG_EUROTECH_WDT=m CONFIG_IB700_WDT=m CONFIG_IBMASR=m CONFIG_WAFER_WDT=m CONFIG_I6300ESB_WDT=m CONFIG_ITCO_WDT=m CONFIG_ITCO_VENDOR_SUPPORT=y CONFIG_IT8712F_WDT=m CONFIG_IT87_WDT=m # CONFIG_HP_WATCHDOG is not set CONFIG_SC1200_WDT=m CONFIG_PC87413_WDT=m # CONFIG_NV_TCO is not set CONFIG_60XX_WDT=m CONFIG_SBC8360_WDT=m CONFIG_CPU5_WDT=m CONFIG_SMSC_SCH311X_WDT=m CONFIG_SMSC37B787_WDT=m CONFIG_W83627HF_WDT=m CONFIG_W83697HF_WDT=m CONFIG_W83697UG_WDT=m CONFIG_W83877F_WDT=m CONFIG_W83977F_WDT=m CONFIG_MACHZ_WDT=m CONFIG_SBC_EPX_C3_WATCHDOG=m # # PCI-based Watchdog Cards # CONFIG_PCIPCWATCHDOG=m CONFIG_WDTPCI=m # # USB-based Watchdog Cards # CONFIG_USBPCWATCHDOG=m CONFIG_SSB_POSSIBLE=y # # Sonics Silicon Backplane # CONFIG_SSB=m CONFIG_SSB_SPROM=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_SDIOHOST_POSSIBLE=y CONFIG_SSB_SDIOHOST=y # CONFIG_SSB_DEBUG is not set CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y CONFIG_MFD_SUPPORT=y CONFIG_MFD_CORE=m CONFIG_MFD_SM501=m # CONFIG_MFD_SM501_GPIO is not set CONFIG_HTC_PASIC3=m CONFIG_UCB1400_CORE=m CONFIG_TPS65010=m CONFIG_TPS6507X=m # CONFIG_MFD_TMIO is not set CONFIG_MFD_WM8400=m CONFIG_MFD_PCF50633=m CONFIG_PCF50633_ADC=m CONFIG_PCF50633_GPIO=m CONFIG_ABX500_CORE=y # CONFIG_AB8500_CORE is not set # CONFIG_MFD_CS5535 is not set CONFIG_MFD_TIMBERDALE=m CONFIG_LPC_SCH=m CONFIG_MFD_RDC321X=m CONFIG_MFD_JANZ_CMODIO=m # CONFIG_MFD_VX855 is not set # CONFIG_MFD_WL1273_CORE is not set CONFIG_REGULATOR=y # CONFIG_REGULATOR_DEBUG is not set # CONFIG_REGULATOR_DUMMY is not set # CONFIG_REGULATOR_FIXED_VOLTAGE is not set CONFIG_REGULATOR_VIRTUAL_CONSUMER=m CONFIG_REGULATOR_USERSPACE_CONSUMER=m CONFIG_REGULATOR_BQ24022=m CONFIG_REGULATOR_MAX1586=m CONFIG_REGULATOR_MAX8649=m CONFIG_REGULATOR_MAX8660=m # CONFIG_REGULATOR_MAX8952 is not set CONFIG_REGULATOR_WM8400=m CONFIG_REGULATOR_PCF50633=m CONFIG_REGULATOR_LP3971=m # CONFIG_REGULATOR_LP3972 is not set CONFIG_REGULATOR_TPS65023=m CONFIG_REGULATOR_TPS6507X=m # CONFIG_REGULATOR_ISL6271A is not set # CONFIG_REGULATOR_AD5398 is not set CONFIG_MEDIA_SUPPORT=m # # Multimedia core support # CONFIG_VIDEO_DEV=m CONFIG_VIDEO_V4L2_COMMON=m CONFIG_DVB_CORE=m CONFIG_VIDEO_MEDIA=m # # Multimedia drivers # CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_RC_CORE=m CONFIG_LIRC=m CONFIG_RC_MAP=m CONFIG_IR_NEC_DECODER=m CONFIG_IR_RC5_DECODER=m CONFIG_IR_RC6_DECODER=m CONFIG_IR_JVC_DECODER=m CONFIG_IR_SONY_DECODER=m CONFIG_IR_RC5_SZ_DECODER=m CONFIG_IR_LIRC_CODEC=m # CONFIG_IR_ENE is not set CONFIG_IR_IMON=m CONFIG_IR_MCEUSB=m # CONFIG_IR_NUVOTON is not set CONFIG_IR_STREAMZAP=m # CONFIG_IR_WINBOND_CIR is not set # CONFIG_RC_LOOPBACK is not set CONFIG_MEDIA_ATTACH=y CONFIG_MEDIA_TUNER=m # CONFIG_MEDIA_TUNER_CUSTOMISE is not set CONFIG_MEDIA_TUNER_SIMPLE=m CONFIG_MEDIA_TUNER_TDA8290=m CONFIG_MEDIA_TUNER_TDA827X=m CONFIG_MEDIA_TUNER_TDA18271=m CONFIG_MEDIA_TUNER_TDA9887=m CONFIG_MEDIA_TUNER_TEA5761=m CONFIG_MEDIA_TUNER_TEA5767=m CONFIG_MEDIA_TUNER_MT20XX=m CONFIG_MEDIA_TUNER_MT2060=m CONFIG_MEDIA_TUNER_MT2266=m CONFIG_MEDIA_TUNER_MT2131=m CONFIG_MEDIA_TUNER_QT1010=m CONFIG_MEDIA_TUNER_XC2028=m CONFIG_MEDIA_TUNER_XC5000=m CONFIG_MEDIA_TUNER_MXL5005S=m CONFIG_MEDIA_TUNER_MXL5007T=m CONFIG_MEDIA_TUNER_MC44S803=m CONFIG_MEDIA_TUNER_MAX2165=m CONFIG_MEDIA_TUNER_TDA18218=m CONFIG_VIDEO_V4L2=m CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_VIDEOBUF_VMALLOC=m CONFIG_VIDEOBUF_DVB=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_TVEEPROM=m CONFIG_VIDEO_TUNER=m CONFIG_V4L2_MEM2MEM_DEV=m CONFIG_VIDEO_CAPTURE_DRIVERS=y # CONFIG_VIDEO_ADV_DEBUG is not set # CONFIG_VIDEO_FIXED_MINOR_RANGES is not set CONFIG_VIDEO_HELPER_CHIPS_AUTO=y CONFIG_VIDEO_IR_I2C=m # # Audio decoders # CONFIG_VIDEO_TVAUDIO=m CONFIG_VIDEO_TDA7432=m CONFIG_VIDEO_TDA9840=m CONFIG_VIDEO_TEA6415C=m CONFIG_VIDEO_TEA6420=m CONFIG_VIDEO_MSP3400=m CONFIG_VIDEO_CS5345=m CONFIG_VIDEO_CS53L32A=m CONFIG_VIDEO_M52790=m CONFIG_VIDEO_WM8775=m CONFIG_VIDEO_WM8739=m CONFIG_VIDEO_VP27SMPX=m # # RDS decoders # CONFIG_VIDEO_SAA6588=m # # Video decoders # CONFIG_VIDEO_BT819=m CONFIG_VIDEO_BT856=m CONFIG_VIDEO_BT866=m CONFIG_VIDEO_KS0127=m CONFIG_VIDEO_OV7670=m CONFIG_VIDEO_MT9V011=m CONFIG_VIDEO_SAA7110=m CONFIG_VIDEO_SAA711X=m CONFIG_VIDEO_SAA717X=m CONFIG_VIDEO_TVP5150=m CONFIG_VIDEO_VPX3220=m # # Video and audio decoders # CONFIG_VIDEO_CX25840=m # # MPEG video encoders # CONFIG_VIDEO_CX2341X=m # # Video encoders # CONFIG_VIDEO_SAA7127=m CONFIG_VIDEO_SAA7185=m CONFIG_VIDEO_ADV7170=m CONFIG_VIDEO_ADV7175=m # # Video improvement chips # CONFIG_VIDEO_UPD64031A=m CONFIG_VIDEO_UPD64083=m # CONFIG_VIDEO_VIVI is not set CONFIG_VIDEO_BT848=m CONFIG_VIDEO_BT848_DVB=y CONFIG_VIDEO_CPIA2=m CONFIG_VIDEO_ZORAN=m CONFIG_VIDEO_ZORAN_DC30=m CONFIG_VIDEO_ZORAN_ZR36060=m CONFIG_VIDEO_ZORAN_BUZ=m CONFIG_VIDEO_ZORAN_DC10=m CONFIG_VIDEO_ZORAN_LML33=m CONFIG_VIDEO_ZORAN_LML33R10=m CONFIG_VIDEO_ZORAN_AVS6EYES=m CONFIG_VIDEO_MEYE=m CONFIG_VIDEO_SAA7134=m CONFIG_VIDEO_SAA7134_ALSA=m CONFIG_VIDEO_SAA7134_RC=y CONFIG_VIDEO_SAA7134_DVB=m CONFIG_VIDEO_MXB=m CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m # CONFIG_VIDEO_TIMBERDALE is not set CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_ALSA=m CONFIG_VIDEO_CX88_BLACKBIRD=m CONFIG_VIDEO_CX88_DVB=m CONFIG_VIDEO_CX88_MPEG=m CONFIG_VIDEO_CX88_VP3054=m CONFIG_VIDEO_CX23885=m CONFIG_VIDEO_AU0828=m CONFIG_VIDEO_IVTV=m CONFIG_VIDEO_FB_IVTV=m CONFIG_VIDEO_CX18=m CONFIG_VIDEO_CX18_ALSA=m CONFIG_VIDEO_SAA7164=m CONFIG_VIDEO_CAFE_CCIC=m # CONFIG_VIDEO_SR030PC30 is not set # CONFIG_VIDEO_VIA_CAMERA is not set CONFIG_SOC_CAMERA=m # CONFIG_SOC_CAMERA_IMX074 is not set CONFIG_SOC_CAMERA_MT9M001=m CONFIG_SOC_CAMERA_MT9M111=m CONFIG_SOC_CAMERA_MT9T031=m CONFIG_SOC_CAMERA_MT9T112=m CONFIG_SOC_CAMERA_MT9V022=m CONFIG_SOC_CAMERA_RJ54N1=m CONFIG_SOC_CAMERA_TW9910=m CONFIG_SOC_CAMERA_PLATFORM=m # CONFIG_SOC_CAMERA_OV2640 is not set # CONFIG_SOC_CAMERA_OV6650 is not set CONFIG_SOC_CAMERA_OV772X=m CONFIG_SOC_CAMERA_OV9640=m CONFIG_V4L_USB_DRIVERS=y CONFIG_USB_VIDEO_CLASS=m CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_GSPCA=m CONFIG_USB_M5602=m CONFIG_USB_STV06XX=m CONFIG_USB_GL860=m CONFIG_USB_GSPCA_BENQ=m CONFIG_USB_GSPCA_CONEX=m CONFIG_USB_GSPCA_CPIA1=m CONFIG_USB_GSPCA_ETOMS=m CONFIG_USB_GSPCA_FINEPIX=m CONFIG_USB_GSPCA_JEILINJ=m # CONFIG_USB_GSPCA_KONICA is not set CONFIG_USB_GSPCA_MARS=m CONFIG_USB_GSPCA_MR97310A=m CONFIG_USB_GSPCA_OV519=m CONFIG_USB_GSPCA_OV534=m CONFIG_USB_GSPCA_OV534_9=m CONFIG_USB_GSPCA_PAC207=m CONFIG_USB_GSPCA_PAC7302=m CONFIG_USB_GSPCA_PAC7311=m CONFIG_USB_GSPCA_SN9C2028=m CONFIG_USB_GSPCA_SN9C20X=m CONFIG_USB_GSPCA_SONIXB=m CONFIG_USB_GSPCA_SONIXJ=m CONFIG_USB_GSPCA_SPCA500=m CONFIG_USB_GSPCA_SPCA501=m CONFIG_USB_GSPCA_SPCA505=m CONFIG_USB_GSPCA_SPCA506=m CONFIG_USB_GSPCA_SPCA508=m CONFIG_USB_GSPCA_SPCA561=m # CONFIG_USB_GSPCA_SPCA1528 is not set CONFIG_USB_GSPCA_SQ905=m CONFIG_USB_GSPCA_SQ905C=m # CONFIG_USB_GSPCA_SQ930X is not set CONFIG_USB_GSPCA_STK014=m CONFIG_USB_GSPCA_STV0680=m CONFIG_USB_GSPCA_SUNPLUS=m CONFIG_USB_GSPCA_T613=m CONFIG_USB_GSPCA_TV8532=m CONFIG_USB_GSPCA_VC032X=m # CONFIG_USB_GSPCA_XIRLINK_CIT is not set CONFIG_USB_GSPCA_ZC3XX=m CONFIG_VIDEO_PVRUSB2=m CONFIG_VIDEO_PVRUSB2_SYSFS=y CONFIG_VIDEO_PVRUSB2_DVB=y # CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set CONFIG_VIDEO_HDPVR=m CONFIG_VIDEO_EM28XX=m CONFIG_VIDEO_EM28XX_ALSA=m CONFIG_VIDEO_EM28XX_DVB=m CONFIG_VIDEO_TLG2300=m CONFIG_VIDEO_CX231XX=m CONFIG_VIDEO_CX231XX_RC=y CONFIG_VIDEO_CX231XX_ALSA=m CONFIG_VIDEO_CX231XX_DVB=m CONFIG_VIDEO_USBVISION=m CONFIG_USB_ET61X251=m CONFIG_USB_SN9C102=m CONFIG_USB_PWC=m # CONFIG_USB_PWC_DEBUG is not set CONFIG_USB_PWC_INPUT_EVDEV=y CONFIG_USB_ZR364XX=m CONFIG_USB_STKWEBCAM=m CONFIG_USB_S2255=m CONFIG_V4L_MEM2MEM_DRIVERS=y CONFIG_VIDEO_MEM2MEM_TESTDEV=m # CONFIG_RADIO_ADAPTERS is not set CONFIG_DVB_MAX_ADAPTERS=8 CONFIG_DVB_DYNAMIC_MINORS=y CONFIG_DVB_CAPTURE_DRIVERS=y # # Supported SAA7146 based PCI Adapters # CONFIG_TTPCI_EEPROM=m CONFIG_DVB_AV7110=m CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET_CORE=m CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m # # Supported USB Adapters # CONFIG_DVB_USB=m # CONFIG_DVB_USB_DEBUG is not set CONFIG_DVB_USB_A800=m CONFIG_DVB_USB_DIBUSB_MB=m # CONFIG_DVB_USB_DIBUSB_MB_FAULTY is not set CONFIG_DVB_USB_DIBUSB_MC=m CONFIG_DVB_USB_DIB0700=m CONFIG_DVB_USB_UMT_010=m CONFIG_DVB_USB_CXUSB=m CONFIG_DVB_USB_M920X=m CONFIG_DVB_USB_GL861=m CONFIG_DVB_USB_AU6610=m CONFIG_DVB_USB_DIGITV=m CONFIG_DVB_USB_VP7045=m CONFIG_DVB_USB_VP702X=m CONFIG_DVB_USB_GP8PSK=m CONFIG_DVB_USB_NOVA_T_USB2=m CONFIG_DVB_USB_TTUSB2=m CONFIG_DVB_USB_DTT200U=m CONFIG_DVB_USB_OPERA1=m CONFIG_DVB_USB_AF9005=m CONFIG_DVB_USB_AF9005_REMOTE=m CONFIG_DVB_USB_DW2102=m CONFIG_DVB_USB_CINERGY_T2=m CONFIG_DVB_USB_ANYSEE=m CONFIG_DVB_USB_DTV5100=m CONFIG_DVB_USB_AF9015=m CONFIG_DVB_USB_CE6230=m CONFIG_DVB_USB_FRIIO=m # CONFIG_DVB_USB_EC168 is not set CONFIG_DVB_USB_AZ6027=m # CONFIG_DVB_USB_LME2510 is not set CONFIG_DVB_TTUSB_BUDGET=m CONFIG_DVB_TTUSB_DEC=m CONFIG_SMS_SIANO_MDTV=m # # Siano module components # CONFIG_SMS_USB_DRV=m CONFIG_SMS_SDIO_DRV=m # # Supported FlexCopII (B2C2) Adapters # CONFIG_DVB_B2C2_FLEXCOP=m CONFIG_DVB_B2C2_FLEXCOP_PCI=m CONFIG_DVB_B2C2_FLEXCOP_USB=m # CONFIG_DVB_B2C2_FLEXCOP_DEBUG is not set # # Supported BT878 Adapters # CONFIG_DVB_BT8XX=m # # Supported Pluto2 Adapters # CONFIG_DVB_PLUTO2=m # # Supported SDMC DM1105 Adapters # CONFIG_DVB_DM1105=m CONFIG_DVB_FIREDTV=m CONFIG_DVB_FIREDTV_FIREWIRE=y # CONFIG_DVB_FIREDTV_IEEE1394 is not set CONFIG_DVB_FIREDTV_INPUT=y # # Supported Earthsoft PT1 Adapters # CONFIG_DVB_PT1=m # # Supported Mantis Adapters # CONFIG_MANTIS_CORE=m CONFIG_DVB_MANTIS=m CONFIG_DVB_HOPPER=m # # Supported nGene Adapters # CONFIG_DVB_NGENE=m # # Supported DVB Frontends # # CONFIG_DVB_FE_CUSTOMISE is not set # # Multistandard (satellite) frontends # CONFIG_DVB_STB0899=m CONFIG_DVB_STB6100=m CONFIG_DVB_STV090x=m CONFIG_DVB_STV6110x=m # # DVB-S (satellite) frontends # CONFIG_DVB_CX24110=m CONFIG_DVB_CX24123=m CONFIG_DVB_MT312=m CONFIG_DVB_ZL10036=m CONFIG_DVB_ZL10039=m CONFIG_DVB_S5H1420=m CONFIG_DVB_STV0288=m CONFIG_DVB_STB6000=m CONFIG_DVB_STV0299=m CONFIG_DVB_STV6110=m CONFIG_DVB_STV0900=m CONFIG_DVB_TDA8083=m CONFIG_DVB_TDA10086=m CONFIG_DVB_TDA8261=m CONFIG_DVB_VES1X93=m CONFIG_DVB_TUNER_ITD1000=m CONFIG_DVB_TUNER_CX24113=m CONFIG_DVB_TDA826X=m CONFIG_DVB_TUA6100=m CONFIG_DVB_CX24116=m CONFIG_DVB_SI21XX=m CONFIG_DVB_DS3000=m CONFIG_DVB_MB86A16=m # # DVB-T (terrestrial) frontends # CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m CONFIG_DVB_CX22702=m CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m CONFIG_DVB_ZL10353=m CONFIG_DVB_DIB3000MB=m CONFIG_DVB_DIB3000MC=m CONFIG_DVB_DIB7000M=m CONFIG_DVB_DIB7000P=m CONFIG_DVB_TDA10048=m CONFIG_DVB_AF9013=m # # DVB-C (cable) frontends # CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_TDA10023=m CONFIG_DVB_STV0297=m # # ATSC (North American/Korean Terrestrial/Cable DTV) frontends # CONFIG_DVB_NXT200X=m CONFIG_DVB_OR51211=m CONFIG_DVB_OR51132=m CONFIG_DVB_BCM3510=m CONFIG_DVB_LGDT330X=m CONFIG_DVB_LGDT3305=m CONFIG_DVB_S5H1409=m CONFIG_DVB_AU8522=m CONFIG_DVB_S5H1411=m # # ISDB-T (terrestrial) frontends # CONFIG_DVB_S921=m CONFIG_DVB_DIB8000=m CONFIG_DVB_MB86A20S=m # # Digital terrestrial only tuners/PLL # CONFIG_DVB_PLL=m CONFIG_DVB_TUNER_DIB0070=m CONFIG_DVB_TUNER_DIB0090=m # # SEC control devices for DVB-S # CONFIG_DVB_LNBP21=m CONFIG_DVB_ISL6405=m CONFIG_DVB_ISL6421=m CONFIG_DVB_ISL6423=m CONFIG_DVB_LGS8GXX=m CONFIG_DVB_ATBM8830=m CONFIG_DVB_TDA665x=m # # Tools to develop new frontends # # CONFIG_DVB_DUMMY_FE is not set # # Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=y CONFIG_AGP_INTEL=m CONFIG_AGP_SIS=m CONFIG_AGP_VIA=m CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=16 CONFIG_VGA_SWITCHEROO=y CONFIG_DRM=m CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_TTM=m CONFIG_DRM_TDFX=m CONFIG_DRM_R128=m CONFIG_DRM_RADEON=m CONFIG_DRM_RADEON_KMS=y CONFIG_DRM_I810=m CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y CONFIG_DRM_MGA=m CONFIG_DRM_SIS=m CONFIG_DRM_VIA=m CONFIG_DRM_SAVAGE=m # CONFIG_STUB_POULSBO is not set CONFIG_VGASTATE=m CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=y CONFIG_FIRMWARE_EDID=y CONFIG_FB_DDC=m CONFIG_FB_BOOT_VESA_SUPPORT=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m # CONFIG_FB_WMT_GE_ROPS is not set CONFIG_FB_DEFERRED_IO=y CONFIG_FB_HECUBA=m CONFIG_FB_SVGALIB=m # CONFIG_FB_MACMODES is not set CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # CONFIG_FB_CIRRUS=m CONFIG_FB_PM2=m CONFIG_FB_PM2_FIFO_DISCONNECT=y CONFIG_FB_CYBER2000=m CONFIG_FB_ARC=m CONFIG_FB_ASILIANT=y CONFIG_FB_IMSTT=y CONFIG_FB_VGA16=m CONFIG_FB_UVESA=m CONFIG_FB_VESA=y CONFIG_FB_EFI=y CONFIG_FB_N411=m CONFIG_FB_HGA=m CONFIG_FB_S1D13XXX=m CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y # CONFIG_FB_NVIDIA_DEBUG is not set CONFIG_FB_NVIDIA_BACKLIGHT=y CONFIG_FB_RIVA=m CONFIG_FB_RIVA_I2C=y # CONFIG_FB_RIVA_DEBUG is not set CONFIG_FB_RIVA_BACKLIGHT=y CONFIG_FB_LE80578=m CONFIG_FB_CARILLO_RANCH=m CONFIG_FB_MATROX=m CONFIG_FB_MATROX_MILLENIUM=y CONFIG_FB_MATROX_MYSTIQUE=y CONFIG_FB_MATROX_G=y CONFIG_FB_MATROX_I2C=m CONFIG_FB_MATROX_MAVEN=m CONFIG_FB_RADEON=m CONFIG_FB_RADEON_I2C=y CONFIG_FB_RADEON_BACKLIGHT=y # CONFIG_FB_RADEON_DEBUG is not set CONFIG_FB_ATY128=m CONFIG_FB_ATY128_BACKLIGHT=y CONFIG_FB_ATY=m CONFIG_FB_ATY_CT=y CONFIG_FB_ATY_GENERIC_LCD=y CONFIG_FB_ATY_GX=y CONFIG_FB_ATY_BACKLIGHT=y CONFIG_FB_S3=m CONFIG_FB_SAVAGE=m CONFIG_FB_SAVAGE_I2C=y CONFIG_FB_SAVAGE_ACCEL=y CONFIG_FB_SIS=m CONFIG_FB_SIS_300=y CONFIG_FB_SIS_315=y CONFIG_FB_VIA=m # CONFIG_FB_VIA_DIRECT_PROCFS is not set CONFIG_FB_NEOMAGIC=m CONFIG_FB_KYRO=m CONFIG_FB_3DFX=m # CONFIG_FB_3DFX_ACCEL is not set CONFIG_FB_3DFX_I2C=y CONFIG_FB_VOODOO1=m CONFIG_FB_VT8623=m CONFIG_FB_TRIDENT=m CONFIG_FB_ARK=m CONFIG_FB_PM3=m CONFIG_FB_CARMINE=m CONFIG_FB_CARMINE_DRAM_EVAL=y # CONFIG_CARMINE_DRAM_CUSTOM is not set CONFIG_FB_GEODE=y CONFIG_FB_GEODE_LX=m CONFIG_FB_GEODE_GX=m CONFIG_FB_GEODE_GX1=m CONFIG_FB_TMIO=m CONFIG_FB_TMIO_ACCELL=y CONFIG_FB_SM501=m CONFIG_FB_UDL=m # CONFIG_FB_VIRTUAL is not set CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_FB_METRONOME=m CONFIG_FB_MB862XX=m CONFIG_FB_MB862XX_PCI_GDC=y CONFIG_FB_BROADSHEET=m CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=m CONFIG_LCD_PLATFORM=m CONFIG_BACKLIGHT_CLASS_DEVICE=y CONFIG_BACKLIGHT_GENERIC=m CONFIG_BACKLIGHT_PROGEAR=m CONFIG_BACKLIGHT_CARILLO_RANCH=m CONFIG_BACKLIGHT_MBP_NVIDIA=m CONFIG_BACKLIGHT_SAHARA=m CONFIG_BACKLIGHT_ADP8860=m CONFIG_BACKLIGHT_PCF50633=m # # Display device support # CONFIG_DISPLAY_SUPPORT=m # # Display hardware drivers # # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_VGACON_SOFT_SCROLLBACK is not set CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # CONFIG_LOGO is not set CONFIG_SOUND=m # CONFIG_SOUND_OSS_CORE is not set CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_JACK=y CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set # CONFIG_SND_SEQUENCER_OSS is not set CONFIG_SND_HRTIMER=m CONFIG_SND_SEQ_HRTIMER_DEFAULT=y CONFIG_SND_DYNAMIC_MINORS=y CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_VMASTER=y CONFIG_SND_DMA_SGBUF=y CONFIG_SND_RAWMIDI_SEQ=m CONFIG_SND_OPL3_LIB_SEQ=m # CONFIG_SND_OPL4_LIB_SEQ is not set # CONFIG_SND_SBAWE_SEQ is not set CONFIG_SND_EMU10K1_SEQ=m CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DRIVERS=y CONFIG_SND_PCSP=m CONFIG_SND_DUMMY=m # CONFIG_SND_ALOOP is not set CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_SERIAL_U16550=m CONFIG_SND_MPU401=m CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0 CONFIG_SND_SB_COMMON=m CONFIG_SND_SB16_DSP=m CONFIG_SND_PCI=y CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ASIHPI=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m CONFIG_SND_AW2=m CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_OXYGEN_LIB=m CONFIG_SND_OXYGEN=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CS5530=m CONFIG_SND_CS5535AUDIO=m CONFIG_SND_CTXFI=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_INDIGOIOX=m CONFIG_SND_INDIGODJX=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_ES1968_INPUT=y CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDA_HWDEP=y CONFIG_SND_HDA_RECONFIG=y CONFIG_SND_HDA_INPUT_BEEP=y CONFIG_SND_HDA_INPUT_BEEP_MODE=0 CONFIG_SND_HDA_INPUT_JACK=y CONFIG_SND_HDA_PATCH_LOADER=y CONFIG_SND_HDA_CODEC_REALTEK=y CONFIG_SND_HDA_CODEC_ANALOG=y CONFIG_SND_HDA_CODEC_SIGMATEL=y CONFIG_SND_HDA_CODEC_VIA=y CONFIG_SND_HDA_CODEC_HDMI=y CONFIG_SND_HDA_CODEC_CIRRUS=y CONFIG_SND_HDA_CODEC_CONEXANT=y CONFIG_SND_HDA_CODEC_CA0110=y CONFIG_SND_HDA_CODEC_CMEDIA=y CONFIG_SND_HDA_CODEC_SI3054=y CONFIG_SND_HDA_GENERIC=y CONFIG_SND_HDA_POWER_SAVE=y CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0 CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_LX6464ES=m CONFIG_SND_MAESTRO3=m CONFIG_SND_MAESTRO3_INPUT=y CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VIRTUOSO=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_USB=y CONFIG_SND_USB_AUDIO=m CONFIG_SND_USB_UA101=m CONFIG_SND_USB_USX2Y=m CONFIG_SND_USB_CAIAQ=m CONFIG_SND_USB_CAIAQ_INPUT=y CONFIG_SND_USB_US122L=m CONFIG_SND_SOC=m # CONFIG_SND_SOC_CACHE_LZO is not set CONFIG_SND_SOC_I2C_AND_SPI=m CONFIG_SND_SOC_ALL_CODECS=m CONFIG_SND_SOC_WM_HUBS=m CONFIG_SND_SOC_AD193X=m CONFIG_SND_SOC_AD73311=m CONFIG_SND_SOC_ADS117X=m CONFIG_SND_SOC_AK4535=m CONFIG_SND_SOC_AK4642=m CONFIG_SND_SOC_AK4671=m CONFIG_SND_SOC_ALC5623=m CONFIG_SND_SOC_CS42L51=m CONFIG_SND_SOC_CS4270=m CONFIG_SND_SOC_CX20442=m CONFIG_SND_SOC_L3=m CONFIG_SND_SOC_DA7210=m CONFIG_SND_SOC_MAX98088=m CONFIG_SND_SOC_PCM3008=m CONFIG_SND_SOC_SPDIF=m CONFIG_SND_SOC_SSM2602=m CONFIG_SND_SOC_TLV320AIC23=m CONFIG_SND_SOC_TLV320AIC3X=m CONFIG_SND_SOC_TLV320DAC33=m CONFIG_SND_SOC_UDA134X=m CONFIG_SND_SOC_UDA1380=m CONFIG_SND_SOC_WM8400=m CONFIG_SND_SOC_WM8510=m CONFIG_SND_SOC_WM8523=m CONFIG_SND_SOC_WM8580=m CONFIG_SND_SOC_WM8711=m CONFIG_SND_SOC_WM8727=m CONFIG_SND_SOC_WM8728=m CONFIG_SND_SOC_WM8731=m CONFIG_SND_SOC_WM8737=m CONFIG_SND_SOC_WM8741=m CONFIG_SND_SOC_WM8750=m CONFIG_SND_SOC_WM8753=m CONFIG_SND_SOC_WM8776=m CONFIG_SND_SOC_WM8804=m CONFIG_SND_SOC_WM8900=m CONFIG_SND_SOC_WM8903=m CONFIG_SND_SOC_WM8904=m CONFIG_SND_SOC_WM8940=m CONFIG_SND_SOC_WM8955=m CONFIG_SND_SOC_WM8960=m CONFIG_SND_SOC_WM8961=m CONFIG_SND_SOC_WM8962=m CONFIG_SND_SOC_WM8971=m CONFIG_SND_SOC_WM8974=m CONFIG_SND_SOC_WM8978=m CONFIG_SND_SOC_WM8985=m CONFIG_SND_SOC_WM8988=m CONFIG_SND_SOC_WM8990=m CONFIG_SND_SOC_WM8993=m CONFIG_SND_SOC_WM8995=m CONFIG_SND_SOC_WM9081=m CONFIG_SND_SOC_MAX9877=m CONFIG_SND_SOC_TPA6130A2=m CONFIG_SND_SOC_WM2000=m CONFIG_SND_SOC_WM9090=m # CONFIG_SOUND_PRIME is not set CONFIG_AC97_BUS=m CONFIG_HID_SUPPORT=y CONFIG_HID=m CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=m CONFIG_HID_PID=y CONFIG_USB_HIDDEV=y # # Special HID drivers # CONFIG_HID_3M_PCT=m CONFIG_HID_A4TECH=m # CONFIG_HID_ACRUX_FF is not set CONFIG_HID_APPLE=m CONFIG_HID_BELKIN=m CONFIG_HID_CANDO=m CONFIG_HID_CHERRY=m CONFIG_HID_CHICONY=m CONFIG_HID_PRODIKEYS=m CONFIG_HID_CYPRESS=m CONFIG_HID_DRAGONRISE=m CONFIG_DRAGONRISE_FF=y # CONFIG_HID_EMS_FF is not set CONFIG_HID_EGALAX=m CONFIG_HID_EZKEY=m CONFIG_HID_KYE=m # CONFIG_HID_UCLOGIC is not set # CONFIG_HID_WALTOP is not set CONFIG_HID_GYRATION=m CONFIG_HID_TWINHAN=m CONFIG_HID_KENSINGTON=m CONFIG_HID_LOGITECH=m CONFIG_LOGITECH_FF=y CONFIG_LOGIRUMBLEPAD2_FF=y CONFIG_LOGIG940_FF=y # CONFIG_LOGIWII_FF is not set CONFIG_HID_MICROSOFT=m CONFIG_HID_MOSART=m CONFIG_HID_MONTEREY=m # CONFIG_HID_MULTITOUCH is not set CONFIG_HID_NTRIG=m CONFIG_HID_ORTEK=m CONFIG_HID_PANTHERLORD=m CONFIG_PANTHERLORD_FF=y CONFIG_HID_PETALYNX=m CONFIG_HID_PICOLCD=m CONFIG_HID_PICOLCD_FB=y CONFIG_HID_PICOLCD_BACKLIGHT=y CONFIG_HID_PICOLCD_LCD=y CONFIG_HID_PICOLCD_LEDS=y CONFIG_HID_QUANTA=m CONFIG_HID_ROCCAT=m CONFIG_HID_ROCCAT_KONE=m # CONFIG_HID_ROCCAT_KONEPLUS is not set # CONFIG_HID_ROCCAT_PYRA is not set CONFIG_HID_SAMSUNG=m CONFIG_HID_SONY=m CONFIG_HID_STANTUM=m CONFIG_HID_SUNPLUS=m CONFIG_HID_GREENASIA=m CONFIG_GREENASIA_FF=y CONFIG_HID_SMARTJOYPLUS=m CONFIG_SMARTJOYPLUS_FF=y CONFIG_HID_TOPSEED=m CONFIG_HID_THRUSTMASTER=m CONFIG_THRUSTMASTER_FF=y CONFIG_HID_ZEROPLUS=m CONFIG_ZEROPLUS_FF=y CONFIG_HID_ZYDACRON=m CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set # # Miscellaneous USB options # # CONFIG_USB_DEVICEFS is not set # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set CONFIG_USB_SUSPEND=y # CONFIG_USB_OTG is not set CONFIG_USB_MON=y CONFIG_USB_WUSB=m CONFIG_USB_WUSB_CBAF=m # CONFIG_USB_WUSB_CBAF_DEBUG is not set # # USB Host Controller Drivers # CONFIG_USB_C67X00_HCD=m CONFIG_USB_XHCI_HCD=m # CONFIG_USB_XHCI_HCD_DEBUGGING is not set CONFIG_USB_EHCI_HCD=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_OXU210HP_HCD=m CONFIG_USB_ISP116X_HCD=m CONFIG_USB_ISP1760_HCD=m CONFIG_USB_ISP1362_HCD=m CONFIG_USB_OHCI_HCD=y # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=y CONFIG_USB_U132_HCD=m CONFIG_USB_SL811_HCD=m CONFIG_USB_R8A66597_HCD=m CONFIG_USB_WHCI_HCD=m CONFIG_USB_HWA_HCD=m # # USB Device Class drivers # CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m CONFIG_USB_WDM=m CONFIG_USB_TMC=m # # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may # # # also be needed; see USB_STORAGE Help for more info # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set CONFIG_USB_STORAGE_DATAFAB=m CONFIG_USB_STORAGE_FREECOM=m CONFIG_USB_STORAGE_ISD200=m CONFIG_USB_STORAGE_USBAT=m CONFIG_USB_STORAGE_SDDR09=m CONFIG_USB_STORAGE_SDDR55=m CONFIG_USB_STORAGE_JUMPSHOT=m CONFIG_USB_STORAGE_ALAUDA=m CONFIG_USB_STORAGE_ONETOUCH=m CONFIG_USB_STORAGE_KARMA=m CONFIG_USB_STORAGE_CYPRESS_ATACB=m # CONFIG_USB_UAS is not set # CONFIG_USB_LIBUSUAL is not set # # USB Imaging devices # CONFIG_USB_MDC800=m CONFIG_USB_MICROTEK=m # # USB port drivers # CONFIG_USB_SERIAL=m CONFIG_USB_EZUSB=y CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_AIRCABLE=m CONFIG_USB_SERIAL_ARK3116=m CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_CH341=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_CP210X=m CONFIG_USB_SERIAL_CYPRESS_M8=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_FUNSOFT=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_EDGEPORT_TI=m CONFIG_USB_SERIAL_GARMIN=m CONFIG_USB_SERIAL_IPW=m CONFIG_USB_SERIAL_IUU=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KEYSPAN_MPR=y CONFIG_USB_SERIAL_KEYSPAN_USA28=y CONFIG_USB_SERIAL_KEYSPAN_USA28X=y CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y CONFIG_USB_SERIAL_KEYSPAN_USA19=y CONFIG_USB_SERIAL_KEYSPAN_USA18X=y CONFIG_USB_SERIAL_KEYSPAN_USA19W=y CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y CONFIG_USB_SERIAL_KEYSPAN_USA49W=y CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_KOBIL_SCT=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_MOS7720=m CONFIG_USB_SERIAL_MOS7840=m CONFIG_USB_SERIAL_MOTOROLA=m CONFIG_USB_SERIAL_NAVMAN=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_OTI6858=m CONFIG_USB_SERIAL_QCAUX=m CONFIG_USB_SERIAL_QUALCOMM=m CONFIG_USB_SERIAL_SPCP8X5=m CONFIG_USB_SERIAL_HP4X=m CONFIG_USB_SERIAL_SAFE=m # CONFIG_USB_SERIAL_SAFE_PADDED is not set # CONFIG_USB_SERIAL_SAMBA is not set CONFIG_USB_SERIAL_SIEMENS_MPI=m CONFIG_USB_SERIAL_SIERRAWIRELESS=m CONFIG_USB_SERIAL_SYMBOL=m CONFIG_USB_SERIAL_TI=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_WWAN=m CONFIG_USB_SERIAL_OPTION=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_SERIAL_OPTICON=m CONFIG_USB_SERIAL_VIVOPAY_SERIAL=m CONFIG_USB_SERIAL_ZIO=m # CONFIG_USB_SERIAL_SSU100 is not set CONFIG_USB_SERIAL_DEBUG=m # # USB Miscellaneous drivers # CONFIG_USB_EMI62=m CONFIG_USB_EMI26=m CONFIG_USB_ADUTUX=m CONFIG_USB_SEVSEG=m CONFIG_USB_RIO500=m CONFIG_USB_LEGOTOWER=m CONFIG_USB_LCD=m CONFIG_USB_LED=m CONFIG_USB_CYPRESS_CY7C63=m CONFIG_USB_CYTHERM=m CONFIG_USB_IDMOUSE=m CONFIG_USB_FTDI_ELAN=m CONFIG_USB_APPLEDISPLAY=m CONFIG_USB_SISUSBVGA=m # CONFIG_USB_SISUSBVGA_CON is not set CONFIG_USB_LD=m CONFIG_USB_TRANCEVIBRATOR=m CONFIG_USB_IOWARRIOR=m CONFIG_USB_TEST=m CONFIG_USB_ISIGHTFW=m # CONFIG_USB_YUREX is not set CONFIG_USB_GADGET=m # CONFIG_USB_GADGET_DEBUG is not set # CONFIG_USB_GADGET_DEBUG_FILES is not set # CONFIG_USB_GADGET_DEBUG_FS is not set CONFIG_USB_GADGET_VBUS_DRAW=2 CONFIG_USB_GADGET_SELECTED=y # CONFIG_USB_GADGET_R8A66597 is not set # CONFIG_USB_GADGET_PXA_U2O is not set # CONFIG_USB_GADGET_M66592 is not set # CONFIG_USB_GADGET_AMD5536UDC is not set # CONFIG_USB_GADGET_CI13XXX_PCI is not set # CONFIG_USB_GADGET_NET2280 is not set # CONFIG_USB_GADGET_GOKU is not set # CONFIG_USB_GADGET_LANGWELL is not set # CONFIG_USB_GADGET_EG20T is not set CONFIG_USB_GADGET_DUMMY_HCD=y CONFIG_USB_DUMMY_HCD=m CONFIG_USB_GADGET_DUALSPEED=y CONFIG_USB_ZERO=m CONFIG_USB_AUDIO=m CONFIG_USB_ETH=m CONFIG_USB_ETH_RNDIS=y # CONFIG_USB_ETH_EEM is not set # CONFIG_USB_G_NCM is not set CONFIG_USB_GADGETFS=m CONFIG_USB_FUNCTIONFS=m CONFIG_USB_FUNCTIONFS_ETH=y CONFIG_USB_FUNCTIONFS_RNDIS=y CONFIG_USB_FUNCTIONFS_GENERIC=y CONFIG_USB_FILE_STORAGE=m # CONFIG_USB_FILE_STORAGE_TEST is not set CONFIG_USB_MASS_STORAGE=m CONFIG_USB_G_SERIAL=m CONFIG_USB_MIDI_GADGET=m CONFIG_USB_G_PRINTER=m CONFIG_USB_CDC_COMPOSITE=m # CONFIG_USB_G_MULTI is not set CONFIG_USB_G_HID=m # CONFIG_USB_G_DBGP is not set CONFIG_USB_G_WEBCAM=m # # OTG and related infrastructure # CONFIG_USB_OTG_UTILS=y CONFIG_USB_GPIO_VBUS=m CONFIG_NOP_USB_XCEIV=m CONFIG_UWB=m CONFIG_UWB_HWA=m CONFIG_UWB_WHCI=m CONFIG_UWB_I1480U=m CONFIG_MMC=y # CONFIG_MMC_DEBUG is not set # CONFIG_MMC_UNSAFE_RESUME is not set # CONFIG_MMC_CLKGATE is not set # # MMC/SD/SDIO Card Drivers # CONFIG_MMC_BLOCK=m CONFIG_MMC_BLOCK_MINORS=8 CONFIG_MMC_BLOCK_BOUNCE=y CONFIG_SDIO_UART=m # CONFIG_MMC_TEST is not set # # MMC/SD/SDIO Host Controller Drivers # CONFIG_MMC_SDHCI=m CONFIG_MMC_SDHCI_PCI=m CONFIG_MMC_RICOH_MMC=y CONFIG_MMC_SDHCI_PLTFM=m CONFIG_MMC_WBSD=m CONFIG_MMC_TIFM_SD=m CONFIG_MMC_CB710=m CONFIG_MMC_VIA_SDMMC=m # CONFIG_MMC_USHC is not set CONFIG_MEMSTICK=m # CONFIG_MEMSTICK_DEBUG is not set # # MemoryStick drivers # # CONFIG_MEMSTICK_UNSAFE_RESUME is not set CONFIG_MSPRO_BLOCK=m # # MemoryStick Host Controller Drivers # CONFIG_MEMSTICK_TIFM_MS=m CONFIG_MEMSTICK_JMICRON_38X=m CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y # # LED drivers # CONFIG_LEDS_NET5501=m CONFIG_LEDS_ALIX2=m CONFIG_LEDS_PCA9532=m CONFIG_LEDS_GPIO=m CONFIG_LEDS_GPIO_PLATFORM=y CONFIG_LEDS_LP3944=m # CONFIG_LEDS_LP5521 is not set # CONFIG_LEDS_LP5523 is not set # CONFIG_LEDS_CLEVO_MAIL is not set CONFIG_LEDS_PCA955X=m CONFIG_LEDS_REGULATOR=m CONFIG_LEDS_BD2802=m CONFIG_LEDS_INTEL_SS4200=m CONFIG_LEDS_LT3593=m CONFIG_LEDS_DELL_NETBOOKS=m CONFIG_LEDS_TRIGGERS=y # # LED Triggers # CONFIG_LEDS_TRIGGER_TIMER=m CONFIG_LEDS_TRIGGER_HEARTBEAT=m CONFIG_LEDS_TRIGGER_BACKLIGHT=m CONFIG_LEDS_TRIGGER_GPIO=m CONFIG_LEDS_TRIGGER_DEFAULT_ON=m # # iptables trigger is under Netfilter config (LED target) # # CONFIG_NFC_DEVICES is not set # CONFIG_ACCESSIBILITY is not set # CONFIG_INFINIBAND is not set # CONFIG_EDAC is not set CONFIG_RTC_LIB=y CONFIG_RTC_CLASS=y CONFIG_RTC_HCTOSYS=y CONFIG_RTC_HCTOSYS_DEVICE="rtc0" # CONFIG_RTC_DEBUG is not set # # RTC interfaces # CONFIG_RTC_INTF_SYSFS=y CONFIG_RTC_INTF_PROC=y CONFIG_RTC_INTF_DEV=y # CONFIG_RTC_INTF_DEV_UIE_EMUL is not set CONFIG_RTC_DRV_TEST=m # # I2C RTC drivers # CONFIG_RTC_DRV_DS1307=m CONFIG_RTC_DRV_DS1374=m CONFIG_RTC_DRV_DS1672=m # CONFIG_RTC_DRV_DS3232 is not set CONFIG_RTC_DRV_MAX6900=m CONFIG_RTC_DRV_RS5C372=m CONFIG_RTC_DRV_ISL1208=m # CONFIG_RTC_DRV_ISL12022 is not set CONFIG_RTC_DRV_X1205=m CONFIG_RTC_DRV_PCF8563=m CONFIG_RTC_DRV_PCF8583=m CONFIG_RTC_DRV_M41T80=m CONFIG_RTC_DRV_M41T80_WDT=y # CONFIG_RTC_DRV_BQ32K is not set CONFIG_RTC_DRV_S35390A=m CONFIG_RTC_DRV_FM3130=m CONFIG_RTC_DRV_RX8581=m CONFIG_RTC_DRV_RX8025=m # # SPI RTC drivers # # # Platform RTC drivers # CONFIG_RTC_DRV_CMOS=y CONFIG_RTC_DRV_DS1286=m CONFIG_RTC_DRV_DS1511=m CONFIG_RTC_DRV_DS1553=m CONFIG_RTC_DRV_DS1742=m CONFIG_RTC_DRV_STK17TA8=m CONFIG_RTC_DRV_M48T86=m CONFIG_RTC_DRV_M48T35=m CONFIG_RTC_DRV_M48T59=m CONFIG_RTC_DRV_MSM6242=m CONFIG_RTC_DRV_BQ4802=m CONFIG_RTC_DRV_RP5C01=m CONFIG_RTC_DRV_V3020=m CONFIG_RTC_DRV_PCF50633=m # # on-CPU RTC drivers # CONFIG_DMADEVICES=y # CONFIG_DMADEVICES_DEBUG is not set # # DMA Devices # # CONFIG_INTEL_MID_DMAC is not set CONFIG_INTEL_IOATDMA=m CONFIG_TIMB_DMA=m # CONFIG_PCH_DMA is not set CONFIG_DMA_ENGINE=y # # DMA Clients # CONFIG_NET_DMA=y # CONFIG_ASYNC_TX_DMA is not set # CONFIG_DMATEST is not set CONFIG_DCA=m CONFIG_AUXDISPLAY=y CONFIG_UIO=m CONFIG_UIO_CIF=m CONFIG_UIO_PDRV=m CONFIG_UIO_PDRV_GENIRQ=m CONFIG_UIO_AEC=m CONFIG_UIO_SERCOS3=m CONFIG_UIO_PCI_GENERIC=m CONFIG_UIO_NETX=m # # Xen driver support # CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_PLATFORM_PCI=m CONFIG_SWIOTLB_XEN=y # CONFIG_STAGING is not set CONFIG_X86_PLATFORM_DEVICES=y CONFIG_ACER_WMI=m CONFIG_ACERHDF=m CONFIG_ASUS_LAPTOP=m CONFIG_DELL_LAPTOP=m CONFIG_DELL_WMI=m CONFIG_FUJITSU_LAPTOP=m # CONFIG_FUJITSU_LAPTOP_DEBUG is not set CONFIG_HP_WMI=m CONFIG_MSI_LAPTOP=m CONFIG_PANASONIC_LAPTOP=m CONFIG_COMPAL_LAPTOP=m CONFIG_SONY_LAPTOP=m CONFIG_SONYPI_COMPAT=y # CONFIG_IDEAPAD_LAPTOP is not set CONFIG_THINKPAD_ACPI=m CONFIG_THINKPAD_ACPI_ALSA_SUPPORT=y CONFIG_THINKPAD_ACPI_DEBUGFACILITIES=y # CONFIG_THINKPAD_ACPI_DEBUG is not set # CONFIG_THINKPAD_ACPI_UNSAFE_LEDS is not set CONFIG_THINKPAD_ACPI_VIDEO=y CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y CONFIG_SENSORS_HDAPS=m CONFIG_INTEL_MENLOW=m CONFIG_EEEPC_LAPTOP=m CONFIG_EEEPC_WMI=m CONFIG_ACPI_WMI=y CONFIG_MSI_WMI=m # CONFIG_ACPI_ASUS is not set CONFIG_TOPSTAR_LAPTOP=m CONFIG_ACPI_TOSHIBA=m CONFIG_TOSHIBA_BT_RFKILL=m CONFIG_ACPI_CMPC=m CONFIG_INTEL_IPS=m # CONFIG_IBM_RTL is not set # # Firmware Drivers # CONFIG_EDD=y CONFIG_EDD_OFF=y CONFIG_FIRMWARE_MEMMAP=y CONFIG_EFI_VARS=y CONFIG_DELL_RBU=m CONFIG_DCDBAS=m CONFIG_DMIID=y CONFIG_ISCSI_IBFT_FIND=y CONFIG_ISCSI_IBFT=m # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_DEFAULTS_TO_ORDERED=y CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_EXT4_FS=y CONFIG_EXT4_FS_XATTR=y CONFIG_EXT4_FS_POSIX_ACL=y CONFIG_EXT4_FS_SECURITY=y # CONFIG_EXT4_DEBUG is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_JBD2=y # CONFIG_JBD2_DEBUG is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set # CONFIG_XFS_FS is not set # CONFIG_GFS2_FS is not set # CONFIG_OCFS2_FS is not set # CONFIG_BTRFS_FS is not set # CONFIG_NILFS2_FS is not set CONFIG_FS_POSIX_ACL=y CONFIG_EXPORTFS=m CONFIG_FILE_LOCKING=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y # CONFIG_FANOTIFY is not set CONFIG_QUOTA=y CONFIG_QUOTA_NETLINK_INTERFACE=y # CONFIG_PRINT_QUOTA_WARNING is not set # CONFIG_QUOTA_DEBUG is not set CONFIG_QUOTA_TREE=m CONFIG_QFMT_V1=m CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_QUOTACTL_COMPAT=y CONFIG_AUTOFS4_FS=m CONFIG_FUSE_FS=y CONFIG_CUSE=m CONFIG_GENERIC_ACL=y # # Caches # CONFIG_FSCACHE=m CONFIG_FSCACHE_STATS=y CONFIG_FSCACHE_HISTOGRAM=y # CONFIG_FSCACHE_DEBUG is not set # CONFIG_FSCACHE_OBJECT_LIST is not set CONFIG_CACHEFILES=m # CONFIG_CACHEFILES_DEBUG is not set # CONFIG_CACHEFILES_HISTOGRAM is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=m CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set # CONFIG_NTFS_RW is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_PROC_VMCORE=y CONFIG_PROC_SYSCTL=y CONFIG_PROC_PAGE_MONITOR=y CONFIG_SYSFS=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_CONFIGFS_FS=m CONFIG_MISC_FILESYSTEMS=y CONFIG_ADFS_FS=m # CONFIG_ADFS_FS_RW is not set CONFIG_AFFS_FS=m CONFIG_ECRYPT_FS=y CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m CONFIG_BEFS_FS=m # CONFIG_BEFS_DEBUG is not set CONFIG_BFS_FS=m CONFIG_EFS_FS=m # CONFIG_LOGFS is not set CONFIG_CRAMFS=m CONFIG_SQUASHFS=m # CONFIG_SQUASHFS_XATTR is not set # CONFIG_SQUASHFS_LZO is not set # CONFIG_SQUASHFS_XZ is not set # CONFIG_SQUASHFS_EMBEDDED is not set CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3 CONFIG_VXFS_FS=m CONFIG_MINIX_FS=m CONFIG_OMFS_FS=m CONFIG_HPFS_FS=m CONFIG_QNX4FS_FS=m CONFIG_ROMFS_FS=m CONFIG_ROMFS_BACKED_BY_BLOCK=y CONFIG_ROMFS_ON_BLOCK=y CONFIG_SYSV_FS=m CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # CONFIG_UFS_DEBUG is not set CONFIG_EXOFS_FS=m # CONFIG_EXOFS_DEBUG is not set CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y # CONFIG_NFS_V4_1 is not set CONFIG_NFS_FSCACHE=y # CONFIG_NFS_USE_LEGACY_DNS is not set CONFIG_NFS_USE_KERNEL_DNS=y # CONFIG_NFS_USE_NEW_IDMAPPER is not set CONFIG_NFSD=m CONFIG_NFSD_DEPRECATED=y CONFIG_NFSD_V2_ACL=y CONFIG_NFSD_V3=y CONFIG_NFSD_V3_ACL=y CONFIG_NFSD_V4=y CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=m CONFIG_NFS_COMMON=y CONFIG_SUNRPC=m CONFIG_SUNRPC_GSS=m CONFIG_RPCSEC_GSS_KRB5=m CONFIG_CEPH_FS=m CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set CONFIG_CIFS_WEAK_PW_HASH=y CONFIG_CIFS_UPCALL=y CONFIG_CIFS_XATTR=y CONFIG_CIFS_POSIX=y # CONFIG_CIFS_DEBUG2 is not set CONFIG_CIFS_DFS_UPCALL=y # CONFIG_CIFS_FSCACHE is not set # CONFIG_CIFS_ACL is not set CONFIG_CIFS_EXPERIMENTAL=y CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y # CONFIG_NCPFS_SMALLDOS is not set CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y CONFIG_CODA_FS=m CONFIG_AFS_FS=m # CONFIG_AFS_DEBUG is not set # CONFIG_AFS_FSCACHE is not set # # Partition Types # CONFIG_PARTITION_ADVANCED=y CONFIG_ACORN_PARTITION=y # CONFIG_ACORN_PARTITION_CUMANA is not set # CONFIG_ACORN_PARTITION_EESOX is not set CONFIG_ACORN_PARTITION_ICS=y # CONFIG_ACORN_PARTITION_ADFS is not set # CONFIG_ACORN_PARTITION_POWERTEC is not set CONFIG_ACORN_PARTITION_RISCIX=y CONFIG_OSF_PARTITION=y CONFIG_AMIGA_PARTITION=y CONFIG_ATARI_PARTITION=y CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set CONFIG_SGI_PARTITION=y CONFIG_ULTRIX_PARTITION=y CONFIG_SUN_PARTITION=y CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_SYSV68_PARTITION=y CONFIG_NLS=y CONFIG_NLS_DEFAULT="cp437" CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m CONFIG_NLS_ASCII=m CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m CONFIG_DLM=m # CONFIG_DLM_DEBUG is not set # # Kernel hacking # CONFIG_TRACE_IRQFLAGS_SUPPORT=y CONFIG_PRINTK_TIME=y # CONFIG_ENABLE_WARN_DEPRECATED is not set # CONFIG_ENABLE_MUST_CHECK is not set CONFIG_FRAME_WARN=1024 CONFIG_MAGIC_SYSRQ=y # CONFIG_STRIP_ASM_SYMS is not set CONFIG_UNUSED_SYMBOLS=y CONFIG_DEBUG_FS=y # CONFIG_HEADERS_CHECK is not set CONFIG_DEBUG_KERNEL=y # CONFIG_DEBUG_SHIRQ is not set # CONFIG_LOCKUP_DETECTOR is not set # CONFIG_HARDLOCKUP_DETECTOR is not set CONFIG_DETECT_HUNG_TASK=y # CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0 CONFIG_SCHED_DEBUG=y CONFIG_SCHEDSTATS=y CONFIG_TIMER_STATS=y # CONFIG_DEBUG_OBJECTS is not set # CONFIG_SLUB_DEBUG_ON is not set # CONFIG_SLUB_STATS is not set # CONFIG_DEBUG_KMEMLEAK is not set # CONFIG_DEBUG_RT_MUTEXES is not set # CONFIG_RT_MUTEX_TESTER is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_MUTEXES is not set CONFIG_BKL=y # CONFIG_DEBUG_LOCK_ALLOC is not set # CONFIG_PROVE_LOCKING is not set # CONFIG_SPARSE_RCU_POINTER is not set # CONFIG_LOCK_STAT is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set CONFIG_STACKTRACE=y # CONFIG_DEBUG_KOBJECT is not set CONFIG_DEBUG_BUGVERBOSE=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_VM is not set # CONFIG_DEBUG_VIRTUAL is not set # CONFIG_DEBUG_WRITECOUNT is not set CONFIG_DEBUG_MEMORY_INIT=y # CONFIG_DEBUG_LIST is not set # CONFIG_TEST_LIST_SORT is not set # CONFIG_DEBUG_SG is not set # CONFIG_DEBUG_NOTIFIERS is not set # CONFIG_DEBUG_CREDENTIALS is not set CONFIG_ARCH_WANT_FRAME_POINTERS=y CONFIG_FRAME_POINTER=y # CONFIG_BOOT_PRINTK_DELAY is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_CPU_STALL_DETECTOR is not set # CONFIG_KPROBES_SANITY_TEST is not set # CONFIG_BACKTRACE_SELF_TEST is not set # CONFIG_DEBUG_BLOCK_EXT_DEVT is not set # CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set # CONFIG_LKDTM is not set CONFIG_CPU_NOTIFIER_ERROR_INJECT=m # CONFIG_FAULT_INJECTION is not set CONFIG_LATENCYTOP=y CONFIG_SYSCTL_SYSCALL_CHECK=y # CONFIG_DEBUG_PAGEALLOC is not set CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FTRACE_NMI_ENTER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_SYSCALL_TRACEPOINTS=y CONFIG_HAVE_C_RECORDMCOUNT=y CONFIG_TRACER_MAX_TRACE=y CONFIG_RING_BUFFER=y CONFIG_FTRACE_NMI_ENTER=y CONFIG_EVENT_TRACING=y CONFIG_EVENT_POWER_TRACING_DEPRECATED=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_RING_BUFFER_ALLOW_SWAP=y CONFIG_TRACING=y CONFIG_GENERIC_TRACER=y CONFIG_TRACING_SUPPORT=y CONFIG_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y # CONFIG_IRQSOFF_TRACER is not set CONFIG_SCHED_TRACER=y CONFIG_FTRACE_SYSCALLS=y CONFIG_BRANCH_PROFILE_NONE=y # CONFIG_PROFILE_ANNOTATED_BRANCHES is not set # CONFIG_PROFILE_ALL_BRANCHES is not set CONFIG_STACK_TRACER=y CONFIG_BLK_DEV_IO_TRACE=y CONFIG_KPROBE_EVENT=y CONFIG_DYNAMIC_FTRACE=y CONFIG_FUNCTION_PROFILER=y CONFIG_FTRACE_MCOUNT_RECORD=y # CONFIG_FTRACE_STARTUP_TEST is not set CONFIG_MMIOTRACE=y # CONFIG_MMIOTRACE_TEST is not set # CONFIG_RING_BUFFER_BENCHMARK is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_FIREWIRE_OHCI_REMOTE_DMA is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_DMA_API_DEBUG is not set # CONFIG_ATOMIC64_SELFTEST is not set CONFIG_ASYNC_RAID6_TEST=m # CONFIG_SAMPLES is not set CONFIG_HAVE_ARCH_KGDB=y CONFIG_KGDB=y CONFIG_KGDB_SERIAL_CONSOLE=y # CONFIG_KGDB_TESTS is not set CONFIG_KGDB_LOW_LEVEL_TRAP=y CONFIG_KGDB_KDB=y CONFIG_KDB_KEYBOARD=y CONFIG_HAVE_ARCH_KMEMCHECK=y CONFIG_STRICT_DEVMEM=y # CONFIG_X86_VERBOSE_BOOTUP is not set CONFIG_EARLY_PRINTK=y # CONFIG_EARLY_PRINTK_DBGP is not set # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_DEBUG_STACK_USAGE is not set # CONFIG_DEBUG_PER_CPU_MAPS is not set # CONFIG_X86_PTDUMP is not set CONFIG_DEBUG_RODATA=y # CONFIG_DEBUG_RODATA_TEST is not set # CONFIG_DEBUG_SET_MODULE_RONX is not set # CONFIG_DEBUG_NX_TEST is not set # CONFIG_IOMMU_DEBUG is not set # CONFIG_IOMMU_STRESS is not set CONFIG_HAVE_MMIOTRACE_SUPPORT=y # CONFIG_X86_DECODER_SELFTEST is not set CONFIG_IO_DELAY_TYPE_0X80=0 CONFIG_IO_DELAY_TYPE_0XED=1 CONFIG_IO_DELAY_TYPE_UDELAY=2 CONFIG_IO_DELAY_TYPE_NONE=3 # CONFIG_IO_DELAY_0X80 is not set CONFIG_IO_DELAY_0XED=y # CONFIG_IO_DELAY_UDELAY is not set # CONFIG_IO_DELAY_NONE is not set CONFIG_DEFAULT_IO_DELAY_TYPE=1 # CONFIG_DEBUG_BOOT_PARAMS is not set # CONFIG_CPA_DEBUG is not set CONFIG_OPTIMIZE_INLINING=y # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set # # Security options # CONFIG_KEYS=y # CONFIG_TRUSTED_KEYS is not set # CONFIG_KEYS_DEBUG_PROC_KEYS is not set # CONFIG_SECURITY_DMESG_RESTRICT is not set CONFIG_SECURITY=y CONFIG_SECURITYFS=y CONFIG_SECURITY_NETWORK=y # CONFIG_SECURITY_NETWORK_XFRM is not set CONFIG_SECURITY_PATH=y CONFIG_LSM_MMAP_MIN_ADDR=0 CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 CONFIG_SECURITY_SELINUX_DISABLE=y CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1 # CONFIG_SECURITY_SELINUX_POLICYDB_VERSION_MAX is not set CONFIG_SECURITY_SMACK=y CONFIG_SECURITY_TOMOYO=y CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 # CONFIG_IMA is not set # CONFIG_DEFAULT_SECURITY_SELINUX is not set # CONFIG_DEFAULT_SECURITY_SMACK is not set # CONFIG_DEFAULT_SECURITY_TOMOYO is not set CONFIG_DEFAULT_SECURITY_APPARMOR=y # CONFIG_DEFAULT_SECURITY_DAC is not set CONFIG_DEFAULT_SECURITY="apparmor" CONFIG_XOR_BLOCKS=m CONFIG_ASYNC_CORE=m CONFIG_ASYNC_MEMCPY=m CONFIG_ASYNC_XOR=m CONFIG_ASYNC_PQ=m CONFIG_ASYNC_RAID6_RECOV=m CONFIG_ASYNC_TX_DISABLE_PQ_VAL_DMA=y CONFIG_ASYNC_TX_DISABLE_XOR_VAL_DMA=y CONFIG_CRYPTO=y # # Crypto core or helper # CONFIG_CRYPTO_ALGAPI=y CONFIG_CRYPTO_ALGAPI2=y CONFIG_CRYPTO_AEAD=m CONFIG_CRYPTO_AEAD2=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_BLKCIPHER2=y CONFIG_CRYPTO_HASH=y CONFIG_CRYPTO_HASH2=y CONFIG_CRYPTO_RNG=m CONFIG_CRYPTO_RNG2=y CONFIG_CRYPTO_PCOMP=m CONFIG_CRYPTO_PCOMP2=y CONFIG_CRYPTO_MANAGER=y CONFIG_CRYPTO_MANAGER2=y CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y CONFIG_CRYPTO_GF128MUL=m CONFIG_CRYPTO_NULL=m CONFIG_CRYPTO_PCRYPT=m CONFIG_CRYPTO_WORKQUEUE=y CONFIG_CRYPTO_CRYPTD=m CONFIG_CRYPTO_AUTHENC=m CONFIG_CRYPTO_TEST=m # # Authenticated Encryption with Associated Data # CONFIG_CRYPTO_CCM=m CONFIG_CRYPTO_GCM=m CONFIG_CRYPTO_SEQIV=m # # Block modes # CONFIG_CRYPTO_CBC=y CONFIG_CRYPTO_CTR=m CONFIG_CRYPTO_CTS=m CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_LRW=m CONFIG_CRYPTO_PCBC=m CONFIG_CRYPTO_XTS=m CONFIG_CRYPTO_FPU=m # # Hash modes # CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_XCBC=m CONFIG_CRYPTO_VMAC=m # # Digest # CONFIG_CRYPTO_CRC32C=m CONFIG_CRYPTO_CRC32C_INTEL=m CONFIG_CRYPTO_GHASH=m CONFIG_CRYPTO_MD4=m CONFIG_CRYPTO_MD5=y CONFIG_CRYPTO_MICHAEL_MIC=m CONFIG_CRYPTO_RMD128=m CONFIG_CRYPTO_RMD160=m CONFIG_CRYPTO_RMD256=m CONFIG_CRYPTO_RMD320=m CONFIG_CRYPTO_SHA1=m CONFIG_CRYPTO_SHA256=m CONFIG_CRYPTO_SHA512=m CONFIG_CRYPTO_TGR192=m CONFIG_CRYPTO_WP512=m CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m # # Ciphers # CONFIG_CRYPTO_AES=m CONFIG_CRYPTO_AES_X86_64=m CONFIG_CRYPTO_AES_NI_INTEL=m CONFIG_CRYPTO_ANUBIS=m CONFIG_CRYPTO_ARC4=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_CAMELLIA=m CONFIG_CRYPTO_CAST5=m CONFIG_CRYPTO_CAST6=m CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_FCRYPT=m CONFIG_CRYPTO_KHAZAD=m CONFIG_CRYPTO_SALSA20=m CONFIG_CRYPTO_SALSA20_X86_64=m CONFIG_CRYPTO_SEED=m CONFIG_CRYPTO_SERPENT=m CONFIG_CRYPTO_TEA=m CONFIG_CRYPTO_TWOFISH=m CONFIG_CRYPTO_TWOFISH_COMMON=m CONFIG_CRYPTO_TWOFISH_X86_64=m # # Compression # CONFIG_CRYPTO_DEFLATE=m CONFIG_CRYPTO_ZLIB=m CONFIG_CRYPTO_LZO=m # # Random Number Generation # CONFIG_CRYPTO_ANSI_CPRNG=m # CONFIG_CRYPTO_USER_API_HASH is not set # CONFIG_CRYPTO_USER_API_SKCIPHER is not set CONFIG_CRYPTO_HW=y CONFIG_CRYPTO_DEV_PADLOCK=y CONFIG_CRYPTO_DEV_PADLOCK_AES=m CONFIG_CRYPTO_DEV_PADLOCK_SHA=m CONFIG_CRYPTO_DEV_HIFN_795X=m CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y CONFIG_HAVE_KVM=y CONFIG_HAVE_KVM_IRQCHIP=y CONFIG_HAVE_KVM_EVENTFD=y CONFIG_KVM_APIC_ARCHITECTURE=y CONFIG_KVM_MMIO=y CONFIG_KVM_ASYNC_PF=y CONFIG_VIRTUALIZATION=y CONFIG_KVM=m CONFIG_KVM_INTEL=m CONFIG_KVM_AMD=m # CONFIG_KVM_MMU_AUDIT is not set CONFIG_VHOST_NET=m CONFIG_VIRTIO=m CONFIG_VIRTIO_RING=m CONFIG_VIRTIO_PCI=m CONFIG_VIRTIO_BALLOON=m CONFIG_BINARY_PRINTF=y # # Library routines # CONFIG_RAID6_PQ=m CONFIG_BITREVERSE=y CONFIG_GENERIC_FIND_FIRST_BIT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_GENERIC_FIND_LAST_BIT=y CONFIG_CRC_CCITT=m CONFIG_CRC16=y CONFIG_CRC_T10DIF=y CONFIG_CRC_ITU_T=m CONFIG_CRC32=y CONFIG_CRC7=m CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y CONFIG_XZ_DEC=y CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y # CONFIG_XZ_DEC_TEST is not set CONFIG_DECOMPRESS_GZIP=y CONFIG_DECOMPRESS_BZIP2=y CONFIG_DECOMPRESS_LZMA=y CONFIG_DECOMPRESS_XZ=y CONFIG_DECOMPRESS_LZO=y CONFIG_TEXTSEARCH=y CONFIG_TEXTSEARCH_KMP=m CONFIG_TEXTSEARCH_BM=m CONFIG_TEXTSEARCH_FSM=m CONFIG_HAS_IOMEM=y CONFIG_HAS_IOPORT=y CONFIG_HAS_DMA=y CONFIG_CHECK_SIGNATURE=y CONFIG_NLATTR=y CONFIG_LRU_CACHE=m CONFIG_AVERAGE=y [-- Attachment #3: Type: text/plain, Size: 159 bytes --] _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 15:08 ` Robert P. J. Day 2011-01-28 15:11 ` Chris Wilson @ 2011-01-28 20:12 ` Rafael J. Wysocki 2011-01-28 20:21 ` Robert P. J. Day 2011-01-28 20:46 ` Robert P. J. Day 1 sibling, 2 replies; 49+ messages in thread From: Rafael J. Wysocki @ 2011-01-28 20:12 UTC (permalink / raw) To: Robert P. J. Day; +Cc: Chris Wilson, dri-devel, Len Brown, linux-kernel On Friday, January 28, 2011, Robert P. J. Day wrote: > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > sadly, no change -- still black screen. again, rebooted > > > successfully under commit 8a327f23. just to be clear, here's "git > > > diff": > > > > > > $ git diff > > > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > > > index 7180013..e035f3c 100644 > > > --- a/include/linux/acpi_io.h > > > +++ b/include/linux/acpi_io.h > > > @@ -7,7 +7,7 @@ > > > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > > > acpi_size size) > > > { > > > - return ioremap_cache(phys, size); > > > + return ioremap(phys, size); > > > } > > > > Ok, that implies the new mapping is fine and not the cause of the issue. > > > > Instead you have some OpRegion related regression hidden until till now > > because the conflicting mapping disabled it for i915. > > > > That would be easy to test by returning early in intel_opregion_setup(): > > > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > > b/drivers/gpu/drm/i915/intel_ > > index 9efccb9..8c93201 100644 > > --- a/drivers/gpu/drm/i915/intel_opregion.c > > +++ b/drivers/gpu/drm/i915/intel_opregion.c > > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > > u32 asls, mboxes; > > int err = 0; > > > > + return -ENOTSUPP; > > + > > > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > > if (asls == 0) { > > > > so you want me to revert to a stock b705120e before doing the above? Alternatively, you could take the vanilla Linus' tree and replace ioremap_cache() with ioremap() in include/linux/acpi_io.h . Please try that and see if it makes a difference. Thanks, Rafael ^ permalink raw reply [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 20:12 ` Rafael J. Wysocki @ 2011-01-28 20:21 ` Robert P. J. Day 2011-01-28 20:46 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 20:21 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Chris Wilson, dri-devel, Len Brown, linux-kernel On Fri, 28 Jan 2011, Rafael J. Wysocki wrote: > On Friday, January 28, 2011, Robert P. J. Day wrote: > > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > > > On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > sadly, no change -- still black screen. again, rebooted > > > > successfully under commit 8a327f23. just to be clear, here's "git > > > > diff": > > > > > > > > $ git diff > > > > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > > > > index 7180013..e035f3c 100644 > > > > --- a/include/linux/acpi_io.h > > > > +++ b/include/linux/acpi_io.h > > > > @@ -7,7 +7,7 @@ > > > > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > > > > acpi_size size) > > > > { > > > > - return ioremap_cache(phys, size); > > > > + return ioremap(phys, size); > > > > } > > > > > > Ok, that implies the new mapping is fine and not the cause of the issue. > > > > > > Instead you have some OpRegion related regression hidden until till now > > > because the conflicting mapping disabled it for i915. > > > > > > That would be easy to test by returning early in intel_opregion_setup(): > > > > > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > > > b/drivers/gpu/drm/i915/intel_ > > > index 9efccb9..8c93201 100644 > > > --- a/drivers/gpu/drm/i915/intel_opregion.c > > > +++ b/drivers/gpu/drm/i915/intel_opregion.c > > > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > > > u32 asls, mboxes; > > > int err = 0; > > > > > > + return -ENOTSUPP; > > > + > > > > > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > > > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > > > if (asls == 0) { > > > > > > > so you want me to revert to a stock b705120e before doing the above? > > Alternatively, you could take the vanilla Linus' tree and replace > ioremap_cache() with ioremap() in include/linux/acpi_io.h . Please try that > and see if it makes a difference. been there, done that, that's all so ... this morning. i continued bisecting and playing and eventually verified the following workaround for an earlier working version of the kernel: $ git diff diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c index 64fd644..28adc6d 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -495,6 +495,8 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; this was based on a suggestion by chris wilson to deactivate the "mboxes" tests in that single source file and see what happened. adding the "return 0" above suddenly gave me a properly booting kernel. i applied the same diff to the current kernel and it's building as we speak. rday p.s. having that "return 0" *after* that test but before the next one still gave me a black screen. -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] @ 2011-01-28 20:21 ` Robert P. J. Day 0 siblings, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 20:21 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Len Brown, linux-kernel, dri-devel On Fri, 28 Jan 2011, Rafael J. Wysocki wrote: > On Friday, January 28, 2011, Robert P. J. Day wrote: > > On Fri, 28 Jan 2011, Chris Wilson wrote: > > > > > On Fri, 28 Jan 2011 09:51:01 -0500 (EST), "Robert P. J. Day" <rpjday@crashcourse.ca> wrote: > > > > sadly, no change -- still black screen. again, rebooted > > > > successfully under commit 8a327f23. just to be clear, here's "git > > > > diff": > > > > > > > > $ git diff > > > > diff --git a/include/linux/acpi_io.h b/include/linux/acpi_io.h > > > > index 7180013..e035f3c 100644 > > > > --- a/include/linux/acpi_io.h > > > > +++ b/include/linux/acpi_io.h > > > > @@ -7,7 +7,7 @@ > > > > static inline void __iomem *acpi_os_ioremap(acpi_physical_address phys, > > > > acpi_size size) > > > > { > > > > - return ioremap_cache(phys, size); > > > > + return ioremap(phys, size); > > > > } > > > > > > Ok, that implies the new mapping is fine and not the cause of the issue. > > > > > > Instead you have some OpRegion related regression hidden until till now > > > because the conflicting mapping disabled it for i915. > > > > > > That would be easy to test by returning early in intel_opregion_setup(): > > > > > > diff --git a/drivers/gpu/drm/i915/intel_opregion.c > > > b/drivers/gpu/drm/i915/intel_ > > > index 9efccb9..8c93201 100644 > > > --- a/drivers/gpu/drm/i915/intel_opregion.c > > > +++ b/drivers/gpu/drm/i915/intel_opregion.c > > > @@ -470,6 +470,8 @@ int intel_opregion_setup(struct drm_device *dev) > > > u32 asls, mboxes; > > > int err = 0; > > > > > > + return -ENOTSUPP; > > > + > > > > > > pci_read_config_dword(dev->pdev, PCI_ASLS, &asls); > > > DRM_DEBUG_DRIVER("graphic opregion physical addr: 0x%x\n", asls); > > > if (asls == 0) { > > > > > > > so you want me to revert to a stock b705120e before doing the above? > > Alternatively, you could take the vanilla Linus' tree and replace > ioremap_cache() with ioremap() in include/linux/acpi_io.h . Please try that > and see if it makes a difference. been there, done that, that's all so ... this morning. i continued bisecting and playing and eventually verified the following workaround for an earlier working version of the kernel: $ git diff diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c index 64fd644..28adc6d 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -495,6 +495,8 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; this was based on a suggestion by chris wilson to deactivate the "mboxes" tests in that single source file and see what happened. adding the "return 0" above suddenly gave me a properly booting kernel. i applied the same diff to the current kernel and it's building as we speak. rday p.s. having that "return 0" *after* that test but before the next one still gave me a black screen. -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? [BISECTED] 2011-01-28 20:12 ` Rafael J. Wysocki 2011-01-28 20:21 ` Robert P. J. Day @ 2011-01-28 20:46 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 20:46 UTC (permalink / raw) To: Rafael J. Wysocki; +Cc: Chris Wilson, dri-devel, Len Brown, linux-kernel On Fri, 28 Jan 2011, Rafael J. Wysocki wrote: > Alternatively, you could take the vanilla Linus' tree and replace > ioremap_cache() with ioremap() in include/linux/acpi_io.h . Please > try that and see if it makes a difference. as a quick followup, i applied the following simple patch: $ git diff diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c index 64fd644..28adc6d 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -495,6 +495,8 @@ int intel_opregion_setup(struct drm_device *dev) opregion->acpi = base + OPREGION_ACPI_OFFSET; } +return 0; // rday + if (mboxes & MBOX_SWSCI) { DRM_DEBUG_DRIVER("SWSCI supported\n"); opregion->swsci = base + OPREGION_SWSCI_OFFSET; to the latest tree, and it gave me a booting kernel, no black screen issue. i will not pretend to understand why that fixes the problem but it does. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply related [flat|nested] 49+ messages in thread
* Re: has the i915 "black screen" boot issue returned? 2011-01-28 8:59 ` Chris Wilson 2011-01-28 9:24 ` Robert P. J. Day @ 2011-01-28 11:35 ` Robert P. J. Day 1 sibling, 0 replies; 49+ messages in thread From: Robert P. J. Day @ 2011-01-28 11:35 UTC (permalink / raw) To: Chris Wilson; +Cc: dri-devel On Fri, 28 Jan 2011, Chris Wilson wrote: > Well, we have two endpoints, so let git attack: > > $ git bisect start > $ git bisect good 58bbf018a70c562437eeae121a5d021ba7fe56a5 > $ git bisect bad abb72c828878a2c69b2cfb33ac30007c8ecd735e > > That shouldn't take more than a few recompiles to identify the > troublemaker. it appears i have one bisection left to make but, just a bit of info, the black screen issue kicks in when the kernel tries to change the font size of the early kernel messages to a much smaller font (or at least it happens around that time). typically, regardless of the kernel, i get a couple of large font messages (/dev/pts and one other, memory fails me), at which point a good kernel will switch to a much smaller font and continue. with a "bad" kernel, the display on my laptop goes black and stays that way, despite the fact that the boot is obviously still progressing. you can decide if that is at all helpful. back to bisecting. should be getting close. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 49+ messages in thread
end of thread, other threads:[~2011-02-01 12:56 UTC | newest] Thread overview: 49+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-01-26 11:37 has the i915 "black screen" boot issue returned? Robert P. J. Day 2011-01-27 10:15 ` Chris Wilson 2011-01-27 10:37 ` Robert P. J. Day 2011-01-27 11:47 ` Robert P. J. Day 2011-01-27 11:56 ` Chris Wilson 2011-01-27 12:12 ` Robert P. J. Day 2011-01-27 12:17 ` Chris Wilson 2011-01-27 12:27 ` Robert P. J. Day 2011-01-27 13:00 ` Robert P. J. Day 2011-01-27 13:42 ` Robert P. J. Day 2011-01-27 13:52 ` Chris Wilson 2011-01-27 13:55 ` Robert P. J. Day 2011-01-27 14:07 ` Chris Wilson 2011-01-27 14:13 ` Robert P. J. Day 2011-01-27 18:40 ` Robert P. J. Day 2011-01-27 21:39 ` Robert P. J. Day 2011-01-27 22:33 ` Robert P. J. Day 2011-01-28 8:59 ` Chris Wilson 2011-01-28 9:24 ` Robert P. J. Day 2011-01-28 9:29 ` Chris Wilson 2011-01-28 13:53 ` has the i915 "black screen" boot issue returned? [BISECTED] Robert P. J. Day 2011-01-28 14:02 ` Chris Wilson 2011-01-28 14:10 ` Robert P. J. Day 2011-01-28 14:10 ` Robert P. J. Day 2011-01-28 14:32 ` Robert P. J. Day 2011-01-28 14:36 ` Chris Wilson 2011-01-28 14:36 ` Chris Wilson 2011-01-28 14:51 ` Robert P. J. Day 2011-01-28 15:04 ` Chris Wilson 2011-01-28 15:04 ` Chris Wilson 2011-01-28 15:08 ` Robert P. J. Day 2011-01-28 15:11 ` Chris Wilson 2011-01-28 15:27 ` Robert P. J. Day 2011-01-28 15:39 ` Chris Wilson 2011-01-28 15:54 ` Robert P. J. Day 2011-01-28 16:03 ` Chris Wilson 2011-01-28 16:23 ` Robert P. J. Day 2011-01-28 16:30 ` Chris Wilson 2011-01-28 18:38 ` Robert P. J. Day 2011-01-29 10:02 ` Robert P. J. Day 2011-02-01 12:05 ` Robert P. J. Day 2011-02-01 12:12 ` Chris Wilson 2011-02-01 12:56 ` Robert P. J. Day 2011-01-28 16:30 ` Robert P. J. Day 2011-01-28 20:12 ` Rafael J. Wysocki 2011-01-28 20:21 ` Robert P. J. Day 2011-01-28 20:21 ` Robert P. J. Day 2011-01-28 20:46 ` Robert P. J. Day 2011-01-28 11:35 ` has the i915 "black screen" boot issue returned? Robert P. J. Day
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.