Kernel 2.6.37 was release Today (1-5-2011)

The Latest Kernel 2.6.37 was release Today. You can find it here:

The Linux Kernel Archives

With this release, you will want to read up on what you are getting. Here is a five part series about the many changes in 2.6.37:

  1. Kernel Log: Coming in 2.6.37 (Part 1) - Graphics - The H Open Source: News and Features

  2. Kernel Log: Coming in 2.6.37 (Part 2) - File systems - The H Open Source: News and Features

  3. Kernel Log: Coming in 2.6.37 (Part 3) - Network and storage hardware - The H Open Source: News and Features

  4. Minor gems: Architectures - The H Open Source: News and Features

  5. Kernel Log: Coming in 2.6.37 (Part 5) - Drivers - The H Open Source: News and Features

For anyone who would like to compile their own kernel, please check out my SAKC script here (Message #17):

S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.00

For Anyone that uses the nVidia driver, I have a script called lnvhw to help reinstall the driver here:

LNVHW - Load NVIDIA (driver the) Hard Way from runlevel 3

Thank You and Good Luck!

And of course, the correct year would be 2011. Oh well…

Thank You,

EDIT by hcvv: changed the title to 2011 to avoid confusion.

In banking and financial circles, this phenomenon is known (for those who still write checks/cheques/bank drafts) as “Checkuary” dates.


Looks like I got saved from my self by hcvv. Thanks for your help.


SeanMc98, even as I hardly ever write checks anymore, perhaps its is Forumuary and not Checkuary, but it seems to have the same symptoms. lol!

Thank You,

Compiled and installed the 2.6.37 kernel, and booted without event. No observable differences from 2.6.37-rc7, but the display is correct (unlike 2.6.37-rc8) on the Intel GMA HD. That is the good news. The “bad news” is the “black screen” problem is still present, and the workarounds function correctly.

Getting close(r), but still no cigar …

Thanks for the updates on this. I think this issue affects many users with Intel GMA HD , and will continue to affect more as time goes by. I’m hoping a fix comes soon.

Out of curiousity, are you using the factory-tested xorg-x11-driver-video (which has the Intel 2.13.902 (based on the 2.13.2 tarball)) and factory-tested Mesa also (and factory-tested xorg-1.9) ? or are you using the versions that came with openSUSE-11.3 ?

Initial testing performed with the versions from 11.3 (Intel 2.12.0). Testing today (after compile/install of 2.6.37) on the Factory Xorg (Mesa : 7.9.802-54.1, Xorg-x11-driver-video-7.6-151.4, Intel 2.13.902).

Refer to thread Kernel 2.6.37-rc8 and Display problem(s) and the submitted bug The “black screen” at boot is pre-X, although the referenced Factory Xorg does have some subsequent impact.

Will post back after testing.

Kernel 2.6.37 compiled/installed on 11.4 MS5. Problem(s) associated with kernel 2-6-37-rc8 no longer present. “Black Screen” on boot persists, and the usual workarounds function correctly.

Mesa is at 7.9.802-54.1, Xorg-x11-driver-video-7.6-154.1, and the Intel driver at 2.13,903 :

    30.811] (==) Matched intel as autoconfigured driver 0
    30.811] (==) Matched fbdev as autoconfigured driver 1
    30.811] (==) Matched vesa as autoconfigured driver 2
    30.811] (==) Assigned the driver to the xf86ConfigLayout
    30.811] (II) LoadModule: "intel"
    30.870] (II) Loading /usr/lib64/xorg/modules/drivers/
    30.888] (II) **Module intel: vendor="X.Org Foundation"
    30.888] 	compiled for 1.9.3, module version = 2.13.903
    30.888] 	Module class: X.Org Video Driver
    30.888] 	ABI class: X.Org Video Driver, version 8.0**
    30.888] (II) LoadModule: "fbdev"
    30.889] (II) Loading /usr/lib64/xorg/modules/drivers/
    30.899] (II) Module fbdev: vendor="X.Org Foundation"
    30.899] 	compiled for 1.9.3, module version = 0.4.2
    30.899] 	ABI class: X.Org Video Driver, version 8.0
    30.899] (II) LoadModule: "vesa"
    30.900] (II) Loading /usr/lib64/xorg/modules/drivers/
    30.906] (II) Module vesa: vendor="X.Org Foundation"
    30.906] 	compiled for 1.9.3, module version = 2.3.0
    30.906] 	Module class: X.Org Video Driver
    30.906] 	ABI class: X.Org Video Driver, version 8.0
    30.906] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
	Sandybridge, Sandybridge
    30.907] (II) FBDEV: driver for framebuffer: fbdev
    30.907] (II) VESA: driver for VESA chipsets: vesa
    30.907] (++) using VT number 7

    31.193] (WW) Falling back to old probe method for fbdev
    31.193] (II) Loading sub module "fbdevhw"
    31.193] (II) LoadModule: "fbdevhw"
    31.194] (II) Loading /usr/lib64/xorg/modules/
    31.207] (II) Module fbdevhw: vendor="X.Org Foundation"
    31.207] 	compiled for 1.9.3, module version = 0.0.2
    31.207] 	ABI class: X.Org Video Driver, version 8.0
    31.207] (WW) Falling back to old probe method for vesa
    31.207] drmOpenDevice: node name is /dev/dri/card0
    31.207] drmOpenDevice: open result is 9, (OK)
    31.207] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    31.207] drmOpenDevice: node name is /dev/dri/card0
    31.207] drmOpenDevice: open result is 9, (OK)
    31.207] drmOpenByBusid: drmOpenMinor returns 9
    31.207] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    31.207] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen" for depth/fbbpp 24/32
    31.207] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    31.207] (==) intel(0): RGB weight 888
    31.207] (==) intel(0): Default visual is TrueColor
    31.207] (II) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale
    31.207] (--) intel(0): Chipset: "Arrandale"
    31.207] (**) intel(0): Tiling enabled
    31.207] (**) intel(0): SwapBuffers wait enabled
    31.208] (==) intel(0): video overlay key set to 0x101fe
    31.208] (II) intel(0): Output LVDS1 using monitor section Default Monitor
    31.308] (II) intel(0): found backlight control interface /sys/class/backlight/acpi_video1
    31.308] (II) intel(0): Output VGA1 has no monitor section
    31.312] (II) intel(0): Output HDMI1 has no monitor section
    31.314] (II) intel(0): Output DP1 has no monitor section
    31.314] (II) intel(0): EDID for output LVDS1
    31.314] (II) intel(0): Manufacturer: AUO  Model: 109e  Serial#: 0
    31.314] (II) intel(0): Year: 2008  Week: 1
    31.314] (II) intel(0): EDID Version: 1.3
    31.314] (II) intel(0): Digital Display Input
    31.314] (II) intel(0): Max Image Size [cm]: horiz.: 38  vert.: 21
    31.314] (II) intel(0): Gamma: 2.20
    31.314] (II) intel(0): No DPMS capabilities specified
    31.314] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
    31.314] (II) intel(0): First detailed timing is preferred mode
    31.314] (II) intel(0): redX: 0.610 redY: 0.355   greenX: 0.333 greenY: 0.610
    31.314] (II) intel(0): blueX: 0.152 blueY: 0.100   whiteX: 0.313 whiteY: 0.329
    31.314] (II) intel(0): Manufacturer's mask: 0
    31.314] (II) intel(0): Supported detailed timing:
    31.314] (II) intel(0): clock: 110.4 MHz   Image Size:  382 x 214 mm
    31.314] (II) intel(0): h_active: 1600  h_sync: 1664  h_sync_end 1706 h_blank_end 2000 h_border: 0
    31.314] (II) intel(0): v_active: 900  v_sync: 903  v_sync_end 906 v_blanking: 920 v_border: 0
    31.314] (II) intel(0): Unknown vendor-specific block f
    31.314] (II) intel(0):  AUO
    31.314] (II) intel(0):  B173RW01 V0

Post-boot problem(s), KDE functions as with standard Xorg. The only serious problem is an apparent regression/correction/enhancement ( :sarcastic: ) in Power Management. For the display workarounds (workspace switching and/or lid closure), the power management options for lid closure action MUST be set to do nothing. Any other setting results in “suspend” loop, as well as crippling the display recovery workround(s).

Desktop effects work well, and the extensive “bad drawable” messages previously reported here (and bugzilla) appear corrected. No changes in Glxgears performance were noted, although I am not sure that any metric exists for Glxgears on the Arrandale/“Ironlake” platform.

By way of summary, the kernel 2.6.37 functions well, although the boot sequence problem(s) with the Intel GMA HD remain as before. I have tested both the distributed kernel and the 2.6.37 release on 11.3 ( and 11.4 Milestone 5 (2.6.37-12). Further, each of these configurations were tested with the distributed Xorg and the Factory (above).

My conclusion remains that Xorg is not involved in the boot “black screen” problem, although once past the boot, the Factory Xorg performs and acts well, with the exception(s) noted in Power Management.

Note to self: Next time we acquire a laptop or PC, be sure to have dual/switchable graphics !