X crash after update do SLED11 SP2

[plamenstoyanov]

Yesterday i have upgraded SLED 11 from SP1 to SP2. Update went fine, but after reboot i ended up in console (which brought some good memories, but…)
I got the following error:
(EE) Failed to load module “freetype” (module does not exist, 0)
(EE) intel(0): failed to set mode: Invalid argument

Fatal server error:
AddScreen/ScreenInit failed for driver 0

It looks like there’s a problem with the intel video driver (with the new kernel?)
SaX was unable to produce working config, so i ended up dusting some old flies and rewrote /etc/X11/xorg.conf to very basic config, using VESA driver.

I would appreciate every suggestion.

SLED in installed on HP EliteBook 8440p

HW configuration:

[code]# x86info
x86info v1.29. Dave Jones 2001-2011
Feedback to davej@redhat.com.

Found 4 identical CPUs
Extended Family: 0 Extended Model: 2 Family: 6 Model: 37 Stepping: 5
Type: 0 (Original OEM)
CPU Model (x86info’s best guess): Core i7 (Nehalem) [Clarkdale/Arrandale]
Processor name string (BIOS programmed): Intel(R) Core™ i5 CPU M 520 @ 2.40GHz

Total processor threads: 4
This system has 1 dual-core processor with hyper-threading (2 threads per core) running at an estimated 2.40GHz
[/code]

# lspci |grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)

part of the dmesg, concerning graphics:

[  900.206221] [drm] Initialized drm 1.1.0 20060810
[  900.234402] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[  900.234410] i915 0000:00:02.0: setting latency timer to 64
[  900.311727] i915 0000:00:02.0: irq 47 for MSI/MSI-X
[  900.311733] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[  900.311735] [drm] Driver supports precise vblank timestamp query.
[  900.311779] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[  902.542282] checking generic (c0000000 1ff0000) vs hw (c0000000 10000000)
[  902.542287] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[  902.542384] Console: switching to colour dummy device 80x25
[  902.543049] fbcon: inteldrmfb (fb0) is primary device
[  902.543214] Console: switching to colour frame buffer device 160x56
[  902.543221] fb0: inteldrmfb frame buffer device
[  902.543223] drm: registered panic notifier
[  902.626556] acpi device:0e: registered as cooling_device4
[  902.626811] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input19
[  902.626924] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[  902.627073] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[  902.664134] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
[  904.469216] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
[  904.469598] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
[  904.469601] detected fb_set_par error, error code: -22
[  904.469627] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
[  904.479014] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]
[  906.665728] intel ips 0000:00:1f.6: i915 driver attached, reenabling gpu turbo

# lsmod |grep i915
i915                  484462  6 
drm_kms_helper         42228  1 i915
drm                   247897  2 i915,drm_kms_helper
i2c_algo_bit           13368  1 i915
i2c_core               35840  4 i915,drm_kms_helper,drm,i2c_algo_bit
intel_agp              18386  1 i915
intel_gtt              24458  3 i915,intel_agp
video                  19436  1 i915
button                 13907  1 i915

Best Regards,
Plamen Stoyanov

[malcolmlewis]

@plamenstoyanov

Yesterday i have upgraded SLED 11 from SP1 to SP2. Update went fine, but
after reboot i ended up in console (which brought some good memories,
but…)
I got the following error:
(EE) Failed to load module “freetype” (module does not exist, 0)
(EE) intel(0): failed to set mode: Invalid argument

Hi
I have a DELL Latitude E5510 which is pretty much the same as your
system same cpu, video. I did a fresh install though and asside from no
dmesg errors I have the following modules loaded against i915;

i2c_core               35840  5
i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit

What about you ~/.xsession-errors file?

What do you see installed from the output of;

zypper se -i freetype

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 5 days 19:58, 2 users, load average: 0.00, 0.02, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

Hi Malcolm,

i haven’t find any relevant info in .xsession-errors.

# zypper se -i freetype
Refreshing service 'nu_novell_com'.
Loading repository data...
Reading installed packages...

S | Name              | Summary                       | Type   
--+-------------------+-------------------------------+--------
i | freetype          | TrueType Font Engine          | package
i | freetype-32bit    | TrueType Font Engine          | package
i | freetype2         | A TrueType Font Library       | package
i | freetype2-32bit   | A TrueType Font Library       | package
i | sledsp1-freetype2 | Security update for freetype2 | patch  

i have uploaded Xorg.1.err on susepaste:

http://susepaste.org/58170157

Failing xorg.conf
http://susepaste.org/87263858

[malcolmlewis]

@plamenstoyanov

Hi Malcolm,

i haven’t find any relevant info in .xsession-errors.

Code:

zypper se -i freetype

Refreshing service ‘nu_novell_com’.
Loading repository data…
Reading installed packages…

S | Name | Summary | Type
–±------------------±------------------------------±-------
i | freetype | TrueType Font Engine | package
i | freetype-32bit | TrueType Font Engine | package
i | freetype2 | A TrueType Font Library | package
i | freetype2-32bit | A TrueType Font Library | package
i | sledsp1-freetype2 | Security update for freetype2 | patch

---

Hi
If you change to runlevel 3 and rerun sax2;

su -
init 3
sax2 -r -m 0=intel
init 5 && exit

How does that go?

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 5 days 20:35, 2 users, load average: 0.01, 0.17, 0.16
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

i did, but no change.
Here’s the SaX.log
http://susepaste.org/85542352

[malcolmlewis]

@plamenstoyanov

i did, but no change.
Here’s the SaX.log
http://susepaste.org/85542352

Hi
Can you run the command;

xrandr

I think it doesn’t know which screen to connect to. Do you have a
Fn+key to cycle through the display outputs?

Also when running sax2, are you setting/checking the screen in use?

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 0:42, 2 users, load average: 0.04, 0.04, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

Hi Malcolm,
i have disconnected the external monitor, when i realized i can’t get the intel driver running.

xrandr displays:

# xrandr 
Screen 0: minimum 640 x 480, current 1600 x 900, maximum 1600 x 900
default connected 1600x900+0+0 0mm x 0mm
   1600x900        0.0* 
   1366x768        0.0  
   1024x768        0.0  
   800x600         0.0  
   640x480         0.0  

SaX has some problem detecting the notebook monitor, because in generated config you can see things like:

Section "Monitor"
  HorizSync    31-60
  Identifier   "Monitor[0]"
  ModelName    "Unknown"
  Option       "DPMS"
  VendorName   "Unknown"
  VertRefresh  50-75
  UseModes     "Modes[0]"
EndSection

.....

  SubSection "Display"
    Depth      8
    Modes      "800x600" 
    Virtual    3840 1200
  EndSubSection

[malcolmlewis]

@plamenstoyanov

Hi Malcolm,
i have disconnected the external monitor, when i realized i can’t get
the intel driver running.

xrandr displays:

Code:

xrandr

Screen 0: minimum 640 x 480, current 1600 x 900, maximum 1600 x 900
default connected 1600x900+0+0 0mm x 0mm
1600x900 0.0*
1366x768 0.0
1024x768 0.0
800x600 0.0
640x480 0.0

---

SaX has some problem detecting the notebook monitor, because in
generated config you can see things like:

Code:

Section “Monitor”
HorizSync 31-60
Identifier “Monitor[0]”
ModelName “Unknown”
Option “DPMS”
VendorName “Unknown”
VertRefresh 50-75
UseModes “Modes[0]”
EndSection

…

SubSection “Display”
Depth 8
Modes “800x600”
Virtual 3840 1200
EndSubSection

---

Hi
So if you drop to runlevel 3 and re run the sax command (the one I
gave previously) can you manually select the screen, as in select LCD
and your default 1600x900 resolution and it passes testing?

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 1:40, 2 users, load average: 0.07, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

Hi Malcolm,
i have submitted an SR to novell support team. They also think the problem is with the intel driver.
After the upgrade, there was some packages from the nvidia repo, concerning glx, which i removed.
currently SaX generates proper xorg.conf, but the problem with the intel driver still stands.
i.e. SaX detects the monitor, sets the correct modes, detects the gfxcard correctly, sets the modes, but when I try to run X with generated config i still get:

(EE) intel(0): failed to set mode: Invalid argument

Fatal server error:
AddScreen/ScreenInit failed for driver 0

Support guy from Novell told me, that he escalated to intel driver maintainers, but still no result.

I’m unable to find info addressing the issue on google and the situation is getting absurd.
Is there any way to start the X in some kind of debug mode, so i can find what exactly is the problem of the intel driver?

here: http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLED/11-SP2/ is stated:

6.2.5. Graphics Drivers Using KMS

Beginning with SLE11-SP1, we switched to use KMS (Kernel Mode Setting) for Intel graphics support. This means that mode setting is now done in kernel space instead of user space (X driver).

If—in rare cases—the new driver concept does not work for you, create an X.Org configuration manually:

Boot into failsafe mode without X (add "3" to the failsafe mode options) and run 'sax2 -r -m 0=fbdev' to create an fbdev based xorg.conf.

Then disable KMS permanently by setting the NO_KMS_IN_INITRD sysconfig variable to "yes" and run mkinitrd.

Finally, reboot again (normal mode) to activate this new X.Org configuration. 

7.3.1. Support Intel(R) HD Graphics 2000/3000 used in 2nd Generation Intel(R) Core™ i7/i5/i3 processor family

The processor graphics is provided in the 2nd Generation Intel(R) Core™ i7/i5/i3 processor family.

This service pack adds support for the processor graphics in the 2nd Generation Intel(R) Core™ i7/i5/i3 processor family by updating the required kernel module, xserver, xf86-video-intel driver, Mesa and dri driver.

I guess I’m fro those rare cases

[malcolmlewis]

@plamenstoyanov

Hi Malcolm,
i have submitted an SR to novell support team. They also think the
problem is with the intel driver.
After the upgrade, there was some packages from the nvidia repo,
concerning glx, which i removed.
currently SaX generates proper xorg.conf, but the problem with the
intel driver still stands.
i.e. SaX detects the monitor, sets the correct modes, detects the
gfxcard correctly, sets the modes, but when I try to run X with
generated config i still get:

Code:

(EE) intel(0): failed to set mode: Invalid argument

Fatal server error:
AddScreen/ScreenInit failed for driver 0

---

Support guy from Novell told me, that he escalated to intel driver
maintainers, but still no result.

I’m unable to find info addressing the issue on google and the
situation is getting absurd.
Is there any way to start the X in some kind of debug mode, so i can
find what exactly is the problem of the intel driver?

here: http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLED/11-SP2/
is stated:[color=blue]

6.2.5. Graphics Drivers Using KMS

Beginning with SLE11-SP1, we switched to use KMS (Kernel Mode Setting)
for Intel graphics support. This means that mode setting is now done
in kernel space instead of user space (X driver).

If—in rare cases—the new driver concept does not work for you, create
an X.Org configuration manually:

Boot into failsafe mode without X (add “3” to the failsafe mode
options) and run ‘sax2 -r -m 0=fbdev’ to create an fbdev based
xorg.conf.

Then disable KMS permanently by setting the NO_KMS_IN_INITRD
sysconfig variable to “yes” and run mkinitrd.

Finally, reboot again (normal mode) to activate this new X.Org
configuration.

7.3.1. Support Intel(R) HD Graphics 2000/3000 used in 2nd Generation
Intel(R) Core™ i7/i5/i3 processor family

The processor graphics is provided in the 2nd Generation Intel(R)
Core™ i7/i5/i3 processor family.

This service pack adds support for the processor graphics in the 2nd
Generation Intel(R) Core™ i7/i5/i3 processor family by updating the
required kernel module, xserver, xf86-video-intel driver, Mesa and dri
driver.
[/color]

I guess I’m fro those rare cases

Hi
You could try booting then with the additional grub option;

nomodeset

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 17:39, 2 users, load average: 0.00, 0.01, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

when boot with nomodeset, cannot start with driver intel:

(EE) No devices detected.

with driver “vesa” it runs ok, like before

[malcolmlewis]

@plamenstoyanov

when boot with nomodeset, cannot start with driver intel:

Code:

(EE) No devices detected.

---

with driver “vesa” it runs ok, like before

Hi
Do you have the SR number?

have you thought about backing up your data and trying a fresh install?

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 19:06, 2 users, load average: 0.02, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

Service Request: 10754470311

I have thought about that, but it will take me 2-3 days to restore my system with the current settings.
Also there’s no warranty it will work, after reinstall.
I was thinking to install SLED11SP2 on a flash drive or external disk on the same laptop and test. Haven’t got the time yet thou.

Thank you very much for the suggestions so far

[malcolmlewis]

@plamenstoyanov

Service Request: 10754470311

I have thought about that, but it will take me 2-3 days to restore my
system with the current settings.
Also there’s no warranty it will work, after reinstall.
I was thinking to install SLED11SP2 on a flash drive or external disk
on the same laptop and test. Haven’t got the time yet thou.

Thank you very much for the suggestions so far

Hi
I’ve asked my SUSE contacts to checkup on the SR status.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 19:30, 2 users, load average: 0.05, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

Thank you very much

[malcolmlewis]

@plamenstoyanov

Thank you very much

Hi
Have you provided the requested log file?

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 2 days 21:19, 2 users, load average: 0.02, 0.04, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

[plamenstoyanov]

[QUOTE=malcolmlewis;3721]Hi
Have you provided the requested log file?
[/QUOTE]

Yes, and the ones after that. Still no resolution thou.

[LarryResch]

I have a similar issue - I used the nVidia driver bundle and when I patched the kernel the driver would fail due to kernel compatibility error. Went back and installed the SuSE nvidia rpm packages and kernel updates did not cause the problem anymore. maybe that is the upgrade issue you are running into?

-L