12.3 Install hangs at X display manager - help please!

English Install/Boot/Login
#1

Hello!

My fresh 12.3-32 install on older hardware will boot with X11failsafe, but hangs solidly here without it:

[OK] Started SuSEfirewall12 phase 2…
[OK] Started /etc/init.d/boot.local Compatibility
[OK] Started LSB: X Display Manager.

I’ve transplanted kernel parameters between the grub recovery string and the regular string. Only X11failsafe is necessary to get 12.3 to boot.

With X11failsafe, the video driver loaded is low resolution. This is what I want to fix.

In anticipation of a gfxcard driver problem, I’m including the results of hwinfo --gfxcard.

root[504] hwinfo --gfxcard
20: PCI(AGP) 200.0: 0300 VGA compatible controller (VGA)        
  [Created at pci.319]
  Unique ID: B35A.+L_3McDnc90
  Parent ID: vSkL.UFGjxxbnmrA
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: graphics card
  Model: "Matrox G450"
  Vendor: pci 0x102b "Matrox Graphics, Inc."
  Device: pci 0x0525 "MGA G400 AGP"
  SubVendor: pci 0x102b "Matrox Graphics, Inc."
  SubDevice: pci 0x0541 "G450"
  Revision: 0x82
  Driver: "matrox_w1"
  Driver Modules: "matrox_w1"
  Memory Range: 0xf4000000-0xf5ffffff (ro,non-prefetchable)
  Memory Range: 0xec800000-0xec803fff (rw,non-prefetchable)
  Memory Range: 0xec000000-0xec7fffff (rw,non-prefetchable)
  Memory Range: 0xec820000-0xec83ffff (ro,non-prefetchable,disabled)
  IRQ: 10 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v0000102Bd00000525sv0000102Bsd00000541bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: mga
  Driver Info #1:
    XFree86 v4 Server Module: mga
    3D Support: yes
    Extensions: dri
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #11 (PCI bridge)

Primary display adapter: #20
root[505]

I have run sax3 which created the 99- config files in /etc/X11/xorg.conf.d. Also I have a depricated xorg.conf for this hardware. I think xllfailsafe is preventing either of these display options from being used.

If I have to live with xllfailsafe can I change the display resolution with either randx or xrandx?

My 12.3 install is up to date with Online Updates! Any suggestions? Heboland.

#2

If you boot using x11failsafe, the configuration is read from /etc/X11/xorg.conf.install, so you should set your display options there.
Have you tried adding “nomodeset” to the boot command line instead of “x11failsafe”? (then the normal configuration files would be used)

Also, it would be good if you would post your /var/log/Xorg.0.log when X fails to start, so we could see what goes wrong…

And have you tried to remove your “depricated xorg.conf”? (just rename it)
Maybe it contains options that no longer work and prevent X from starting… (at least it overrides the config files in /etc/X11/xorg.conf.d)

#3

Thank you wolfi323!

Adding just nomodeset to the grub regular boot line does not boot with either the depricated xorg.conf or the 99- sax3 files. I tried them independently once with no 99s and once with the 99s, but renaming xorg.conf.

Regarding the log files, it looks to me like /var/log/Xorg.0.log pretains to the current boot if viewed from level 5 There is also a log.old that looks to be the previous boot log.

Let’s see if I have room to include the whole /var/log/Xorg.0.log.old.

    28.753] 
X.Org X Server 1.13.2
Release Date: 2013-01-24
    28.753] X Protocol Version 11, Revision 0
    28.753] Build Operating System: openSUSE SUSE LINUX
    28.754] Current Operating System: Linux linux-hga9.heboland 3.7.10-1.1-default #1 SMP Thu Feb 28 15:06:29 UTC 2013 (82d3f21) i686
    28.754] Kernel command line: BOOT_IMAGE=/vmlinuz-3.7.10-1.1-default root=UUID=589e0749-679e-4c7a-9e4d-262e8c81f05e resume=/dev/disk/by-id/ata-ST320414A_3EC03W50-part5 splash=off quiet showopts nomodeset
    28.754] Build Date: 21 February 2013  09:52:18AM
    28.754]  
    28.754] Current version of pixman: 0.28.2
    28.754]     Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    28.754] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    28.754] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 13 20:54:26 2013
    28.755] (==) Using config file: "/etc/X11/xorg.conf"
    28.755] (==) Using config directory: "/etc/X11/xorg.conf.d"
    28.755] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    28.863] Parse error on line 43 of section Files in file /etc/X11/xorg.conf
    Ignoring obsolete keyword "InputDevices".
    28.863] Parse error on line 44 of section Files in file /etc/X11/xorg.conf
    Ignoring obsolete keyword "InputDevices".
    28.864] (==) ServerLayout "Layout[all]"
    28.864] (**) |-->Screen "Screen[0]" (0)
    28.864] (**) |   |-->Monitor "Monitor[0]"
    28.864] (**) |   |-->Device "Device[0]"
    28.864] (**) |-->Input Device "Keyboard[0]"
    28.864] (**) |-->Input Device "Mouse[1]"
    28.864] (**) Option "ZapWarning" "on"
    28.865] (**) Option "AllowMouseOpenFail" "on"
    28.865] (**) Option "Xinerama" "off"
    28.865] (==) Automatically adding devices
    28.865] (==) Automatically enabling devices
    28.865] (==) Automatically adding GPU devices
    28.865] (WW) The directory "/usr/share/fonts/local" does not exist.
    28.865]     Entry deleted from font path.
    28.865] (WW) The directory "/usr/share/fonts/URW" does not exist.
    28.865]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/PEX" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/latin2/misc" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/latin2/75dpi" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/latin2/100dpi" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/latin2/Type1" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/latin7/75dpi" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/baekmuk" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/japanese" does not exist.
    28.941]     Entry deleted from font path.
    28.941] (WW) The directory "/usr/share/fonts/kwintv" does not exist.
    28.941]     Entry deleted from font path.
    28.946] (WW) The directory "/usr/share/fonts/CID" does not exist.
    28.946]     Entry deleted from font path.
    28.946] (WW) The directory "/usr/share/fonts/ucs/misc" does not exist.
    28.946]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/ucs/75dpi" does not exist.
    28.947]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/ucs/100dpi" does not exist.
    28.947]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/hellas/misc" does not exist.
    28.947]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/hellas/75dpi" does not exist.
    28.947]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/hellas/100dpi" does not exist.
    28.947]     Entry deleted from font path.
    28.947] (WW) The directory "/usr/share/fonts/hellas/Type1" does not exist.
    28.947]     Entry deleted from font path.
    28.953] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
    28.953]     Entry deleted from font path.
    28.953] (WW) The directory "/usr/share/fonts/xtest" does not exist.
    28.953]     Entry deleted from font path.
    28.958] (WW) The directory "/opt/kde3/share/fonts" does not exist.
    28.958]     Entry deleted from font path.
    28.958] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
    28.958]     Entry deleted from font path.
    28.958] (**) FontPath set to:
    /usr/share/fonts/misc:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/Type1,
    /usr/share/fonts/Speedo,
    /usr/share/fonts/cyrillic,
    /usr/share/fonts/truetype,
    /usr/share/fonts/uni:unscaled,
    /usr/share/fonts/misc:unscaled,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/ghostscript/,
    /usr/share/fonts/cyrillic:unscaled,
    /usr/share/fonts/truetype/,
    built-ins
    28.958] (==) ModulePath set to "/usr/lib/xorg/modules/updates,/usr/lib/xorg/modules"
    28.960] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    28.960] (WW) Disabling Keyboard[0]
    28.960] (WW) Disabling Mouse[1]
    28.960] (II) Loader magic: 0x8261620
    28.960] (II) Module ABI versions:
    28.960]     X.Org ANSI C Emulation: 0.4
    28.960]     X.Org Video Driver: 13.1
    28.960]     X.Org XInput driver : 18.0
    28.960]     X.Org Server Extension : 7.0
    28.962] (--) PCI:*(0:2:0:0) 102b:0525:102b:0541 rev 130, Mem @ 0xf4000000/33554432, 0xec800000/16384, 0xec000000/8388608, BIOS @ 0x????????/131072
    28.962] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    28.962] Initializing built-in extension Generic Event Extension
    28.963] Initializing built-in extension SHAPE
    28.963] Initializing built-in extension MIT-SHM
    28.963] Initializing built-in extension XInputExtension
    28.963] Initializing built-in extension XTEST
    28.963] Initializing built-in extension BIG-REQUESTS
    28.963] Initializing built-in extension SYNC
    28.963] Initializing built-in extension XKEYBOARD
    28.963] Initializing built-in extension XC-MISC
    28.963] Initializing built-in extension SECURITY
    28.963] Initializing built-in extension XINERAMA
    28.963] Initializing built-in extension XFIXES
    28.963] Initializing built-in extension RENDER
    28.963] Initializing built-in extension RANDR
    28.963] Initializing built-in extension COMPOSITE
    28.963] Initializing built-in extension DAMAGE
    28.963] Initializing built-in extension MIT-SCREEN-SAVER
    28.963] Initializing built-in extension DOUBLE-BUFFER
    28.963] Initializing built-in extension RECORD
    28.963] Initializing built-in extension DPMS
    28.963] Initializing built-in extension X-Resource
    28.963] Initializing built-in extension XVideo
    28.963] Initializing built-in extension XVideo-MotionCompensation
    28.963] Initializing built-in extension XFree86-VidModeExtension
    28.963] Initializing built-in extension XFree86-DGA
    28.963] Initializing built-in extension XFree86-DRI
    28.963] Initializing built-in extension DRI2
    28.964] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    28.973] (II) LoadModule: "dbe"
    28.973] (II) Module "dbe" already built-in
    28.974] (II) LoadModule: "extmod"
    28.974] (II) Module "extmod" already built-in
    28.974] (II) LoadModule: "glx"
    28.992] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    28.996] (II) Module glx: vendor="X.Org Foundation"
    28.996]     compiled for 1.13.2, module version = 1.0.0
    28.996]     ABI class: X.Org Server Extension, version 7.0
    28.996] (==) AIGLX enabled
    29.000] Loading extension GLX
    29.000] (II) LoadModule: "dri"
    29.000] (II) Module "dri" already built-in
    29.000] (II) LoadModule: "mga"
    29.018] (II) Loading /usr/lib/xorg/modules/drivers/mga_drv.so
    29.038] (II) Module mga: vendor="X.Org Foundation"
    29.038]     compiled for 1.13.1, module version = 1.6.2
    29.038]     Module class: X.Org Video Driver
    29.038]     ABI class: X.Org Video Driver, version 13.1
    29.038] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
    mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
    mgag200 SE A PCI, mgag200 SE B PCI, mgag200 EV Maxim,
    mgag200 ER SH7757, mgag200 eW Nuvoton, mgag200eH, mgag400, mgag550
    29.039] (++) using VT number 7

    29.039] (EE) mga: The PCI device 0x525 at 02@00:00:0 has a kernel module claiming it.
    29.039] (EE) mga: This driver cannot operate until it has been unloaded.
    29.039] (EE) No devices detected.
    29.039] 
Fatal server error:
    29.039] no screens found
    29.039] (EE) 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
    29.039] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    29.040] (EE)

The log was from a failed boot attempt using nomodeset and xorg.conf in /etc/X11.

Your suggestion of using x11failsafe and modifying xorg.conf.install, this seems to me could result in sudden death if the system won’t boot from x11failsafe either.

I think I can put a symlink in /etc/X11 named xorg.conf.install that points to either the original or the modified version of xorg.conf.install. If I go dark, I can change that link from level 3.

So again if I have the room here, I’ll include the xorg.conf.install and the depricated xorg.conf. My question then would be how to merge the xorg.conf into the install file. Here’s the xorg.conf.install!

Section "Device"
  Identifier "vboxvideo"
  Driver  "vboxvideo"
EndSection

Section "Screen"
  Identifier "vboxvideo"
  Device "vboxvideo"
EndSection


Section "Device"
  Identifier "vmware"
  Driver  "vmware"
EndSection

Section "Screen"
  Identifier "vmware"
  Device "vmware"
EndSection


Section "Device"
  Identifier "modesetting"
  Driver  "modesetting"
EndSection
Section "Screen"
  Identifier "modesetting"
  Device "modesetting"
EndSection


Section "Device"
  Identifier "fbdev"
  Driver  "fbdev"
EndSection
Section "Screen"
  Identifier "fbdev"
  Device "fbdev"
EndSection


Section "Device"
  Identifier "vesa"
  Driver  "vesa"
EndSection

Section "Screen"
  Identifier "vesa"
  Device "vesa"
EndSection


Section "ServerLayout"
  Identifier "Layout"
  Screen  "vboxvideo"
  Screen  "vmware"
  Screen  "modesetting"
  Screen  "fbdev"
  Screen  "vesa"
EndSection

Opps! The xorg.conf bumped this just over the character limit.

Let me try to paste the xorg.conf into a reply back to myself. To be continued! Heboland.

#4

Hello list, wolfi323! This is the continuation of my previous post that ran out of room.

Here is my xorg.conf!

# /.../
# SaX generated X11 config file
# Created on: 2010-10-29T22:50:46-0700.
#
# Version: 8.1
# Contact: Marcus Schaefer <sax@suse.de>, 2005
# Contact: SaX-User list <https://lists.berlios.de/mailman/listinfo/sax-users>
#
# Automatically generated by [ISaX] (8.1)
# PLEASE DO NOT EDIT THIS FILE!
#
Section "Files"
  FontPath     "/usr/share/fonts/misc:unscaled"
  FontPath     "/usr/share/fonts/local"
  FontPath     "/usr/share/fonts/75dpi:unscaled"
  FontPath     "/usr/share/fonts/100dpi:unscaled"
  FontPath     "/usr/share/fonts/Type1"
  FontPath     "/usr/share/fonts/URW"
  FontPath     "/usr/share/fonts/Speedo"
  FontPath     "/usr/share/fonts/PEX"
  FontPath     "/usr/share/fonts/cyrillic"
  FontPath     "/usr/share/fonts/latin2/misc:unscaled"
  FontPath     "/usr/share/fonts/latin2/75dpi:unscaled"
  FontPath     "/usr/share/fonts/latin2/100dpi:unscaled"
  FontPath     "/usr/share/fonts/latin2/Type1"
  FontPath     "/usr/share/fonts/latin7/75dpi:unscaled"
  FontPath     "/usr/share/fonts/baekmuk:unscaled"
  FontPath     "/usr/share/fonts/japanese:unscaled"
  FontPath     "/usr/share/fonts/kwintv"
  FontPath     "/usr/share/fonts/truetype"
  FontPath     "/usr/share/fonts/uni:unscaled"
  FontPath     "/usr/share/fonts/CID"
  FontPath     "/usr/share/fonts/ucs/misc:unscaled"
  FontPath     "/usr/share/fonts/ucs/75dpi:unscaled"
  FontPath     "/usr/share/fonts/ucs/100dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/misc:unscaled"
  FontPath     "/usr/share/fonts/hellas/75dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/100dpi:unscaled"
  FontPath     "/usr/share/fonts/hellas/Type1"
  FontPath     "/usr/share/fonts/misc/sgi:unscaled"
  FontPath     "/usr/share/fonts/xtest"
  FontPath     "/opt/kde3/share/fonts"
  InputDevices "/dev/gpmdata"
  InputDevices "/dev/input/mice"
EndSection

Section "ServerFlags"
  Option       "AllowMouseOpenFail" "on"
  Option       "ZapWarning" "on"
EndSection

Section "Module"
  Load         "dbe"
  Load         "extmod"
  Load         "glx"
  Load         "dri"
EndSection

Section "InputDevice"
  # Driver "kbd" will be disabled unless 'Option "AutoAddDevices" "off"' 
  # is set in "ServerFlags" section. 
  Driver       "kbd"
  Identifier   "Keyboard[0]"
  Option       "Protocol" "Standard"
  Option       "XkbLayout" "us"
  Option       "XkbModel" "microsoftpro"
  Option       "XkbRules" "xfree86"
EndSection

Section "InputDevice"
  # Driver "mouse" will be disabled unless 'Option "AutoAddDevices" "off"' 
  # is set in "ServerFlags" section. 
  Driver       "mouse"
  Identifier   "Mouse[1]"
  Option       "Buttons" "5"
  Option       "Device" "/dev/input/mice"
  Option       "Name" "Logitech Optical Wheel Mouse"
  Option       "Protocol" "explorerps/2"
  Option       "Vendor" "Sysp"
  Option       "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
  DisplaySize  345 259
  HorizSync    29-70
  Identifier   "Monitor[0]"
  ModelName    "1152X864@75HZ"
  Option       "PreferredMode" "1152x864"
  VendorName   "--> VESA"
  VertRefresh  50-75
  UseModes     "Modes[0]"
EndSection

Section "Modes"
  Identifier   "Modes[0]"
  Modeline     "1024x768" 81.80 1024 1080 1192 1360 768 769 772 802
  Modeline     "1024x768" 76.16 1024 1080 1192 1360 768 769 772 800
  Modeline     "1024x768" 69.71 1024 1080 1184 1344 768 769 772 798
  Modeline     "1024x768" 64.11 1024 1080 1184 1344 768 769 772 795
  Modeline     "1024x600" 63.20 1024 1080 1184 1344 600 601 604 627
  Modeline     "1024x600" 58.10 1024 1072 1176 1328 600 601 604 625
  Modeline     "1024x600" 53.78 1024 1072 1176 1328 600 601 604 623
  Modeline     "1024x600" 48.96 1024 1064 1168 1312 600 601 604 622
  Modeline     "800x600" 48.91 800 840 920 1040 600 601 604 627
  Modeline     "800x600" 45.50 800 840 920 1040 600 601 604 625
  Modeline     "800x600" 42.11 800 840 920 1040 600 601 604 623
  Modeline     "800x600" 38.22 800 832 912 1024 600 601 604 622
  Modeline     "768x576" 45.51 768 808 888 1008 576 577 580 602
  Modeline     "768x576" 41.66 768 800 880 992 576 577 580 600
  Modeline     "768x576" 38.56 768 800 880 992 576 577 580 598
  Modeline     "768x576" 34.96 768 792 872 976 576 577 580 597
  Modeline     "640x480" 30.72 640 664 728 816 480 481 484 502
  Modeline     "640x480" 28.56 640 664 728 816 480 481 484 500
  Modeline     "640x480" 25.95 640 656 720 800 480 481 484 499
  Modeline     "640x480" 23.86 640 656 720 800 480 481 484 497
  Modeline     "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900
EndSection

Section "Screen"
  DefaultDepth 24
  SubSection "Display"
    Depth      15
    Modes      "1152x864" "1024x768" "1024x600" "800x600" "768x576" "640x480" 
  EndSubSection
  SubSection "Display"
    Depth      16
    Modes      "1152x864" "1024x768" "1024x600" "800x600" "768x576" "640x480" 
  EndSubSection
  SubSection "Display"
    Depth      24
    Modes      "1152x864" "1024x768" "1024x600" "800x600" "768x576" "640x480" 
  EndSubSection
  SubSection "Display"
    Depth      8
    Modes      "1152x864" "1024x768" "1024x600" "800x600" "768x576" "640x480" 
  EndSubSection
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
EndSection

Section "Device"
  BoardName    "G450"
  Driver       "mga"
  Identifier   "Device[0]"
  VendorName   "Matrox"
EndSection

Section "ServerLayout"
  Identifier   "Layout[all]"
  InputDevice  "Keyboard[0]" "CoreKeyboard"
  InputDevice  "Mouse[1]" "CorePointer"
  Option       "Clone" "off"
  Option       "Xinerama" "off"
  Screen       "Screen[0]"
EndSection

Section "DRI"
    Group      "video"
    Mode       0660
EndSection

Section "Extensions"
EndSection

OK, I think I have answered all of your questions. Can these xorg files be merged in some practical way?

What do you make of what I posted back? Heboland.

#5

So there’s your error msg. Some kernel module is loaded which is locking the gfx card.
I have only seen this before with the proprietary nvidia driver, when the nouveau kernel module was not blacklisted…

Well, could you post the output of “lspci -k”, when X fails to start, to see which kernel module that is?

You could also try to change

Driver   "mga"

to

Driver   "vesa"

in xorg.conf or xorg.conf.d/99-… respectively. X should start then (but without hw acceleration of course, just like failsafe)

And another question: Did you try to boot with your system **before **you ran sax3?
If you didn’t, please try to remove those 99-… files sax3 created (and xorg.conf) and see if it works then.

#6

On 2013-04-14 02:46, wolfi323 wrote:
> If you boot using x11failsafe, the configuration is read from
> /etc/X11/xorg.conf.install, so you should set your display options
> there.

Perhaps better to copy that file to xorg.conf and modify that one.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#7

Thanks for the input, guys!

wolfi323, I wanted to clarify two things. The xorg.log came from a failed attempt to use the included xorg.conf, not the 99- sax3 files. You can see in that file, mga is the driver. The second thing is that the included xorg.conf was working fine on 12.1-32. I could try changing those mga lines in the xorg.conf.

Since I saw your response, I googled the mga line you highlighted. This may not mean anything, but there is a Debian bug filed as follows:


Package: xserver-xorg-video-mga Version: 1:1.5.0-2 Severity: important  Dear Maintainer,  The check introduced in -2 to not start the driver when the g200se KMS module is active, is too broad: apparently it only checks whether the device is claimed by any other driver -- but that is also the case when matroxfb is active, which should *not* prevent mga from starting.  -antrik-

Well, could you post the output of “lspci -k”, when X fails to start, to see which kernel module that is]

When X fails to start, the system is hung at the boot lines shown in the original post. My only recourse from this is ^ ALT DEL and the system reboots.

robin_listas, I need a more specific understanding of the pronouns you used in your statement! I think you are suggesting to copy xorg.conf.install to xorg.conf. This in my opinion is a safer approach as it allows the original xorg.conf.install in place for x11failsafe boots.

Let me see if you guys think that the xserver Debian bug could apply to 12.3. Heboland.

#8

Yes, I was aware of that. I just wanted to know if you already tried to boot without xorg.conf and without those 99-* files in place (i.e. if it works with the default config).

Since I saw your response, I googled the mga line you highlighted. This may not mean anything, but there is a Debian bug filed as follows:

Package: xserver-xorg-video-mga Version: 1:1.5.0-2
Severity: important
 Dear Maintainer,
The check introduced in -2 to not start the driver when the g200se KMS module is active, is too broad: apparently it only checks whether the device is claimed by any other driver -- but that is also the case when matroxfb is active, which should *not* prevent mga from starting.  -antrik-

I found that bug as well and a similar one for gentoo. That’s why I asked for the output of ‘lspci -k’…

When X fails to start, the system is hung at the boot lines shown in the original post. My only recourse from this is ^ ALT DEL and the system reboots.

You should be able to get to a text login when you press Ctrl+Alt+F1.
But on second thought, ‘lspci -k’ should yield the same result when you’re booting with x11failsafe, so you can do it inside X as well.
And I’m only interested in the lines about your gfx card, you don’t need to post the full output…:wink:

I think you are suggesting to copy xorg.conf.install to xorg.conf. This in my opinion is a safer approach as it allows the original xorg.conf.install in place for x11failsafe boots.

That wouldn’t help you, because xorg.conf.install only lists some drivers, which then are tried one after the other by X.
Just change the “Driver” line in your xorg.conf and you should have the same result…

Let me see if you guys think that the xserver Debian bug could apply to 12.3.

Quite possible, although openSUSE 12.3 contains v1.6.2 of the mga driver. You could try to blacklist the offending kernel module and see if the “mga” driver works then…
Do this by creating a file in /etc/modprobe.d (the name doesn’t really matter, you could use “blacklist-matroxfb” f.e.) with the following content:

blacklist matroxfb

(of course, you have to substitute “matroxfb” with the module you want to blacklist)

#9

wolfi323 I didn’t get much farther.

I changed the mga entry in the xorg.conf to vesa and still no boot without kernel parameter x11failsafe. I changed it back again!

You were right that lspci -k gives the same result from the text console after a hang as from level 5 after a failsafe boot. you didn’t tell me what to filter for, so I used matrox and mga. Screening for gfx doesn’t get any hits.

This is what I got; should I have filtered more?:

root[508] lspci -k | grep -i matrox > /home/frank/Downloads/lspcik.txt
02:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G400/G450 (rev 82)
    Subsystem: Matrox Electronics Systems Ltd. Millennium G450 Dual Head
    Kernel driver in use: matrox_w1
root[509] lspci -k | grep -i mga >> /home/frank/Downloads/lspcik.txt
02:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G400/G450 (rev 82)

A couple of other thoughts include, is the 12.1 version of the mga driver the same in 12.3? It’s possible the matrox card is in the AGP slot rather than the PCI. It’s plugged into the top slot in the tower.

The mobo does have a VGA port on it that I’ve never used. Whether it works, I’m not sure. I hate to put myself in the dark!

Regarding the blacklisting, I took a look inside /etc/modprobe.d. Right now everything in that directory is a directory. I understand if I put a file in there with the contents of blacklist xxx, the kernel will try to do that. For me the problem is what to blacklist.

If this is the bad guy "g200se KMS module"it may be necessary to leave it as is. I don’t see the matroxfb module when I search lsmod. Any suggestions how I can find the name of the conflicting module?

i’ll wait for you to react to this post. Heboland.

#10

Be sure that the on board VGA is disabled.

#11

On 2013-04-14 18:16, heboland wrote:

> robin_listas, I need a more specific understanding of the pronouns you
> used in your statement! I think you are suggesting to copy
> xorg.conf.install to xorg.conf. This in my opinion is a safer approach
> as it allows the original xorg.conf.install in place for x11failsafe
> boots.

Yes, exactly.

I don’t know if that would get your system working, but if you want to
try modifying xorg.conf.install, this approach would be safer.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#12

Thanks guys!

gogalthorp, the BIOS setting on this machine hasn’t changed since it was working on 12.1 with the xorg.conf I posted previously on this thread.

For the record, this matrox card has dual heads. I’m only using one head and it is the same head I used with 12.1.

If I were to back up and try to get the onboard VGA to work, would that help to find the mga module that is interfering with the matrox card? Heboland.

#13

Pity. Don’t know why it didn’t work. Xorg.0.log should tell, though…:wink:

This is what I got; should I have filtered more?:

root[508] lspci -k | grep -i matrox > /home/frank/Downloads/lspcik.txt
**02:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G400/G450 (rev 82)
**    Subsystem: Matrox Electronics Systems Ltd. Millennium G450 Dual Head
    Kernel driver in use: matrox_w1
root[509] lspci -k | grep -i mga >> /home/frank/Downloads/lspcik.txt
02:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G400/G450 (rev 82)

You shouldn’t filter like that because this way you only get the lines that contain that word.
Put the whole output of lspci in a file and view it with ‘less’ or an editor of your choice. Search for the highlighted line and post the next two lines below it. (esp. the line saying “Kernel driver in use:” would be interesting).

A couple of other thoughts include, is the 12.1 version of the mga driver the same in 12.3?

No. 12.1 contained v1.4.13, 12.3 contains v1.6.2…

It’s possible the matrox card is in the AGP slot rather than the PCI. It’s plugged into the top slot in the tower.

No idea. Shouldn’t matter I guess.

Regarding the blacklisting, I took a look inside /etc/modprobe.d. Right now everything in that directory is a directory.

Are you sure? There should already be some files in that directory!
Like:

ls /etc/modprobe.d/
00-system.conf               50-iwl3945.conf          50-tv.conf                
10-unsupported-modules.conf  50-iwlagn.conf           50-tv.conf.YaST2save      
50-alsa.conf                 50-nvidia.conf           99-local.conf
50-blacklist.conf            50-prism54.conf          vmware-fuse.conf
50-bluetooth.conf            50-sound.conf
50-ipw2200.conf              50-sound.conf.YaST2save

I understand if I put a file in there with the contents of blacklist xxx, the kernel will try to do that. For me the problem is what to blacklist.

Yes. We are trying to figure out what to blacklist by using ‘lspci -k’…

If this is the bad guy "g200se KMS module"it may be necessary to leave it as is. I don’t see the matroxfb module when I search lsmod. Any suggestions how I can find the name of the conflicting module?

See above. ‘lspci -k’ is supposed to show the conflicting module.

But you still haven’t answered my question:
Did you try to boot without xorg.conf and without those 99- files created by sax3 (i.e. with a default configuration)?*

#14

Your first post already told which kernel module is hogging your gfxcard: “matrox_w1”
So you could try to blacklist that one.

But in the meantime I built the mga driver package with the patch from that debian bug.
You can find it here:
Index of /repositories/home:/wolfi323:/branches:/openSUSE:/12.3:/Update/standard
Please download the correct “xf86-video-mga” package for your architecture (i586 or x86_64) and install it using:

rpm -Uvh --force *name_of_downloaded_file*

Hopefully the mga driver will work then…

#15

Thank you so much wolfi323!

Sorry I didn’t answer your question about the default boot! I thought I had tried that combination, but to my surprise default did boot to a 1024x768 display. That boot happened without either nomodset or x11failsafe.

I installed the 586 version of your rpm as follows:

root[508] rpm -Uvh --force Downloads/xf86-video-mga-1.6.2-2.5.1.i586.rpm 
warning: Downloads/xf86-video-mga-1.6.2-2.5.1.i586.rpm: Header V3 DSA/SHA1 Signature, key ID 598e6033: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:xf86-video-mga-1.6.2-2.5.1       #################################  50%]
Cleaning up / removing...
   2:xf86-video-mga-1.6.2-2.1.1       ################################# [100%]
root[509]

Next I moved the sax3 99-* files back into /etc/X11/xorg.conf.d and tried to boot with the default kernel modules. The boot hung at the same point.

Next I removed the sax3 99-* files and copied the xorg.conf into /etc/X11/. With your new software installed, the xorg.conf boots and gives me the higher resolution display I was looking for. From the booted xorg.conf, I copied both the xorg.0.log and xorg.0.log.old. Either is too big to post

Is there anything else you would like to see? Heboland.

#16

I guess it’s using the “vesa” driver then, just like x11failsafe does…

I installed the 586 version of your rpm as follows:

root[508] rpm -Uvh --force Downloads/xf86-video-mga-1.6.2-2.5.1.i586.rpm 
warning: Downloads/xf86-video-mga-1.6.2-2.5.1.i586.rpm: Header V3 DSA/SHA1 Signature, key ID 598e6033: NOKEY
Preparing...                          ################################# [100%]
Updating / installing...
   1:xf86-video-mga-1.6.2-2.5.1       #################################  50%]
Cleaning up / removing...
   2:xf86-video-mga-1.6.2-2.1.1       ################################# [100%]
root[509]

Next I moved the sax3 99-* files back into /etc/X11/xorg.conf.d and tried to boot with the default kernel modules. The boot hung at the same point.

Next I removed the sax3 99-* files and copied the xorg.conf into /etc/X11/. With your new software installed, the xorg.conf boots and gives me the higher resolution display I was looking for. From the booted xorg.conf, I copied both the xorg.0.log and xorg.0.log.old. Either is too big to post

Is there anything else you would like to see? Heboland.

So the mga driver from my packages works for you then?
Fine! Just keep using it and your xorg.conf (delete those 99-* files created by sax3).
This is already fixed in the latest driver version, so the mga driver should work fine for you in the next openSUSE version…

But I’d suggest you open a bugreport at http://bugzilla.novell.com/ for openSUSE 12.3.
Please mention the debian bugreport and that the patch there fixed the mga driver for you.

#17

Further to this, please note you can use your openSUSE forum username and password when entering bugzilla.

#18

Hi Guys

i’m a bit lost here - after “zypper dup”, I also have this boot problem:

“Failed to start LSB X Display Manager”

Where do I start looking to find what’s wrong?

#19

/var/log/Xorg.0.log

I guess you’re using a proprietary video driver (nvidia/fglrx)?
Try renaming /etc/X11/xorg.conf to get a graphical display again:

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

X would probably use an opensource driver then, but at least you would have a GUI.

Reinstalling your graphics driver should fix the issue…

If you use KDE from the additional KDE repo, you could also try to reinstall kdm:

sudo zypper in -f kdm
#20

On 2013-05-10 10:56, pheine wrote:
>
> Hi Guys
>
> i’m a bit lost here - after “zypper dup”, I also have this boot
> problem:
>
> “Failed to start LSB X Display Manager”
>
> Where do I start looking to find what’s wrong?

Welcome, new poster.

Your problem doesn’t look similar to the one in this thread, namely:

+++·······························
My fresh 12.3-32 install on older hardware will boot with X11failsafe,
but hangs solidly here without it:
·······························+±

I also see on other post of yours that you were using tumbleweed.

So…

First, do not hang onto an old thread, because we may assume that ALL
that was said there applies to you and that you tried ALL the advices in
that thread.

Instead, start your own new thread, or this will become very confusing.

Second. If you are still using tumbleweed, you have to ask there, not
here. That is, in the subforum dedicated to tumbleweed.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)