12.3 graphic display issues

benbowc · May 4, 2013, 11:29am

I see reference to problems with the mode setting etc. in OS 12.3. I have been attempting to get a running copy of 12.3 after my system upgrade from 12.1 that worked well seemed to have failed. I got the blinking cursor treatment with the Graphics Interface Reached message the last thing displayed. I installed Bodhi for fun and run into similar issues but could get it going in recovery mode. I tried that with Opensuse and it works also. I am posting the Xorg.0.log from when it fails. I’m confused as to what to do. Can anyone point me to what is actually going wrong and what has changed since 12.1 to prevent this working.


   125.424] 
X.Org X Server 1.13.2
Release Date: 2013-01-24
   125.424] X Protocol Version 11, Revision 0
   125.424] Build Operating System: openSUSE SUSE LINUX
   125.424] Current Operating System: Linux linux-lsad.site 3.7.10-1.4-desktop #1 SMP PREEMPT Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) x86_64
   125.424] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-1.4-desktop root=UUID=e2d24e22-11b8-4eab-b80a-16de3e730e13 resume=/dev/disk/by-id/ata-HDS721025CLA382_39M4511_42C0463IBM_JPA270H82P24EL-part2 splash=silent quiet showopts
   125.424] Build Date: 21 February 2013  10:01:18AM
   125.424]  
   125.424] Current version of pixman: 0.28.2
   125.424]     Before reporting problems, check [X.Org Wiki - Home](http://wiki.x.org)
    to make sure that you have the latest version.
   125.424] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
   125.424] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May  4 21:03:41 2013
   125.438] (==) Using config directory: "/etc/X11/xorg.conf.d"
   125.438] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
   125.506] (==) No Layout section.  Using the first Screen section.
   125.506] (==) No screen section available. Using defaults.
   125.506] (**) |-->Screen "Default Screen Section" (0)
   125.506] (**) |   |-->Monitor "<default monitor>"
   125.519] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
   125.519] (==) Automatically adding devices
   125.519] (==) Automatically enabling devices
   125.519] (==) Automatically adding GPU devices
   125.627] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
   125.627]     Entry deleted from font path.
   125.639] (==) FontPath set to:
    /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
   125.639] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
   125.639] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
   125.639] (II) Loader magic: 0x801c20
   125.639] (II) Module ABI versions:
   125.639]     X.Org ANSI C Emulation: 0.4
   125.639]     X.Org Video Driver: 13.1
   125.639]     X.Org XInput driver : 18.0
   125.639]     X.Org Server Extension : 7.0
   125.640] (II) config/udev: Adding drm device (/dev/dri/card0)
   125.641] (--) PCI:*(0:3:2:0) 1a03:2000:1014:03ce rev 16, Mem @ 0xfb000000/8388608, 0xfb800000/131072, I/O @ 0x0000d000/128
   125.641] (II) Open ACPI successful (/var/run/acpid.socket)
   125.651] Initializing built-in extension Generic Event Extension
   125.651] Initializing built-in extension SHAPE
   125.651] Initializing built-in extension MIT-SHM
   125.651] Initializing built-in extension XInputExtension
   125.651] Initializing built-in extension XTEST
   125.651] Initializing built-in extension BIG-REQUESTS
   125.651] Initializing built-in extension SYNC
   125.651] Initializing built-in extension XKEYBOARD
   125.651] Initializing built-in extension XC-MISC
   125.651] Initializing built-in extension SECURITY
   125.651] Initializing built-in extension XINERAMA
   125.651] Initializing built-in extension XFIXES
   125.651] Initializing built-in extension RENDER
   125.651] Initializing built-in extension RANDR
   125.651] Initializing built-in extension COMPOSITE
   125.651] Initializing built-in extension DAMAGE
   125.651] Initializing built-in extension MIT-SCREEN-SAVER
   125.651] Initializing built-in extension DOUBLE-BUFFER
   125.651] Initializing built-in extension RECORD
   125.651] Initializing built-in extension DPMS
   125.651] Initializing built-in extension X-Resource
   125.651] Initializing built-in extension XVideo
   125.651] Initializing built-in extension XVideo-MotionCompensation
   125.651] Initializing built-in extension XFree86-VidModeExtension
   125.651] Initializing built-in extension XFree86-DGA
   125.651] Initializing built-in extension XFree86-DRI
   125.651] Initializing built-in extension DRI2
   125.651] (II) "glx" will be loaded by default.
   125.651] (II) LoadModule: "dri2"
   125.651] (II) Module "dri2" already built-in
   125.651] (II) LoadModule: "glamoregl"
   125.663] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
   125.827] (II) Module glamoregl: vendor="X.Org Foundation"
   125.827]     compiled for 1.13.2, module version = 0.5.0
   125.827]     ABI class: X.Org ANSI C Emulation, version 0.4
   125.827] (II) LoadModule: "glx"
   125.843] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
   125.856] (II) Module glx: vendor="X.Org Foundation"
   125.856]     compiled for 1.13.2, module version = 1.0.0
   125.856]     ABI class: X.Org Server Extension, version 7.0
   125.856] (==) AIGLX enabled
   125.857] Loading extension GLX
   125.857] (==) Matched ast as autoconfigured driver 0
   125.857] (==) Matched ast as autoconfigured driver 1
   125.857] (==) Matched modesetting as autoconfigured driver 2
   125.857] (==) Matched fbdev as autoconfigured driver 3
   125.857] (==) Matched vesa as autoconfigured driver 4
   125.857] (==) Assigned the driver to the xf86ConfigLayout
   125.857] (II) LoadModule: "ast"
   125.858] (II) Loading /usr/lib64/xorg/modules/drivers/ast_drv.so
   125.862] (II) Module ast: vendor="X.Org Foundation"
   125.862]     compiled for 1.13.1, module version = 0.97.0
   125.862]     Module class: X.Org Video Driver
   125.862]     ABI class: X.Org Video Driver, version 13.1
   125.862] (II) LoadModule: "modesetting"
   125.862] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
   125.867] (II) Module modesetting: vendor="X.Org Foundation"
   125.867]     compiled for 1.13.1, module version = 0.6.0
   125.867]     Module class: X.Org Video Driver
   125.867]     ABI class: X.Org Video Driver, version 13.1
   125.867] (II) LoadModule: "fbdev"
   125.868] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
   125.878] (II) Module fbdev: vendor="X.Org Foundation"
   125.878]     compiled for 1.13.1, module version = 0.4.3
   125.878]     Module class: X.Org Video Driver
   125.878]     ABI class: X.Org Video Driver, version 13.1
   125.878] (II) LoadModule: "vesa"
   125.878] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
   125.881] (II) Module vesa: vendor="X.Org Foundation"
   125.881]     compiled for 1.13.1, module version = 2.3.2
   125.881]     Module class: X.Org Video Driver
   125.881]     ABI class: X.Org Video Driver, version 13.1
   125.881] (II) AST: Driver for ASPEED Graphics Chipsets: ASPEED Graphics Family,
    ASPEED Graphics Family, ASPEED AST1180 Graphics
   125.881] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
   125.881] (II) FBDEV: driver for framebuffer: fbdev
   125.881] (II) VESA: driver for VESA chipsets: vesa
   125.881] (++) using VT number 7

   125.881] (WW) Falling back to old probe method for ast
   125.881] (--) Assigning device section with no busID to primary device
   125.881] (--) Assigning device section with no busID to primary device
   125.881] (WW) AST: More than one matching Device section found: Autoconfigured Video Device ast
   125.881] (--) Chipset ASPEED Graphics Family found
   125.881] (EE) ast: The PCI device 0x2000 at 03@00:02:0 has a kernel module claiming it.
   125.882] (EE) cirrus: This driver cannot operate until it has been unloaded.
   125.882] (WW) Falling back to old probe method for modesetting
   125.882] (WW) Falling back to old probe method for fbdev
   125.882] (II) Loading sub module "fbdevhw"
   125.882] (II) LoadModule: "fbdevhw"
   125.882] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
   125.888] (II) Module fbdevhw: vendor="X.Org Foundation"
   125.888]     compiled for 1.13.2, module version = 0.0.2
   125.888]     ABI class: X.Org Video Driver, version 13.1
   125.888] (WW) Falling back to old probe method for vesa
   125.888] (EE) No devices detected.
   125.888] 
Fatal server error:
   125.888] no screens found
   125.888] (EE) 
Please consult the The X.Org Foundation support 
     at [X.Org Wiki - Home](http://wiki.x.org)
 for help. 
   125.888] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
   125.888] (EE)

oldcpu · May 4, 2013, 12:05pm

I note this:

125.641] (–) PCI:*(0:3:2:0) 1a03:2000:1014:03ce rev 16, Mem @ 0xfb000000/8388608, 0xfb800000/131072, I/O @ 0x0000d000/128
…
125.881] (II) AST: Driver for ASPEED Graphics Chipsets: ASPEED Graphics Family,
ASPEED Graphics Family, ASPEED AST1180 Graphics
…
** 125.881] (WW) AST: More than one matching Device section found: Autoconfigured Video Device ast**
125.881] (–) Chipset ASPEED Graphics Family found
** 125.881] (EE) ast: The PCI device 0x2000 at 03@00:02:0 has a kernel module claiming it.
125.882] (EE) cirrus: This driver cannot operate until it has been unloaded.**

the error in red is a bit troubling … I do not suppose you know what kernel module has already claimed your graphic card/PCI device 1a03:1014 ?

Still, I also note AST graphics have a different nominal driver where the unpackaged version is nominally here: xorg/driver/xf86-video-ast - X.org xf86-video-ast driver.

There is an openSUSE xf86-video-ast packaged version, which you can find in the OSS (?) repository. I note this link: software.opensuse.org:

If not already installed, imho you should install that openSUSE packaged xf86-video-ast rpm, reboot and test.

benbowc · May 4, 2013, 12:45pm

I’ll give it a try. Report back ASAP.
Thanks

wolfi323 · May 4, 2013, 6:49pm

Your recovery mode not working seems to be this bug:
https://bugzilla.novell.com/show_bug.cgi?id=809361

To make it work, you apparently need to change /etc/X11/xorg.conf.install:

Workaround is to remove the sections for “modesetting” driver and the reference to them in screen section.

Oh, and you could try to remove the sections for “ast” as well… (you didn’t mention what graphics card you use)

benbowc · May 4, 2013, 11:14pm

Recovery mode is working, its a regular x start up that is failing. It appears there must be some bug introduced in 12.3 that stops the driver claiming the PCI slot or some sort of ordering issue. Here is a recovery mode startup log:


   152.867] 
X.Org X Server 1.13.2
Release Date: 2013-01-24
   152.867] X Protocol Version 11, Revision 0
   152.867] Build Operating System: openSUSE SUSE LINUX
   152.867] Current Operating System: Linux linux-lsad.site 3.7.10-1.4-desktop #1 SMP PREEMPT Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) x86_64
   152.867] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.7.10-1.4-desktop root=UUID=e2d24e22-11b8-4eab-b80a-16de3e730e13 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
   152.867] Build Date: 21 February 2013  10:01:18AM
   152.867]  
   152.867] Current version of pixman: 0.28.2
   152.867]     Before reporting problems, check [X.Org Wiki - Home](http://wiki.x.org)
    to make sure that you have the latest version.
   152.867] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
   152.867] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May  4 22:55:52 2013
   152.867] (==) Using config file: "/etc/X11/xorg.conf.install"
   152.867] (==) Using config directory: "/etc/X11/xorg.conf.d"
   152.867] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
   152.882] (==) ServerLayout "Layout"
   152.882] (**) |-->Screen "vboxvideo" (0)
   152.882] (**) |   |-->Monitor "<default monitor>"
   152.882] (**) |   |-->Device "vboxvideo"
   152.882] (==) No monitor specified for screen "vboxvideo".
    Using a default monitor configuration.
   152.882] (**) |-->Screen "vmware" (1)
   152.882] (**) |   |-->Monitor "<default monitor>"
   152.882] (**) |   |-->Device "vmware"
   152.882] (==) No monitor specified for screen "vmware".
    Using a default monitor configuration.
   152.882] (**) |-->Screen "modesetting" (2)
   152.882] (**) |   |-->Monitor "<default monitor>"
   152.882] (**) |   |-->Device "modesetting"
   152.882] (==) No monitor specified for screen "modesetting".
    Using a default monitor configuration.
   152.882] (**) |-->Screen "fbdev" (3)
   152.882] (**) |   |-->Monitor "<default monitor>"
   152.883] (**) |   |-->Device "fbdev"
   152.883] (==) No monitor specified for screen "fbdev".
    Using a default monitor configuration.
   152.883] (**) |-->Screen "vesa" (4)
   152.883] (**) |   |-->Monitor "<default monitor>"
   152.883] (**) |   |-->Device "vesa"
   152.883] (==) No monitor specified for screen "vesa".
    Using a default monitor configuration.
   152.883] (==) Automatically adding devices
   152.883] (==) Automatically enabling devices
   152.883] (==) Automatically adding GPU devices
   152.996] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
   152.996]     Entry deleted from font path.
   153.008] (==) FontPath set to:
    /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
   153.008] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
   153.008] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
   153.008] (II) Loader magic: 0x801c20
   153.008] (II) Module ABI versions:
   153.008]     X.Org ANSI C Emulation: 0.4
   153.008]     X.Org Video Driver: 13.1
   153.008]     X.Org XInput driver : 18.0
   153.008]     X.Org Server Extension : 7.0
   153.010] (--) PCI:*(0:3:2:0) 1a03:2000:1014:03ce rev 16, Mem @ 0xfb000000/8388608, 0xfb800000/131072, I/O @ 0x0000d000/128
   153.010] (II) Open ACPI successful (/var/run/acpid.socket)
   153.010] Initializing built-in extension Generic Event Extension
   153.010] Initializing built-in extension SHAPE
   153.010] Initializing built-in extension MIT-SHM
   153.010] Initializing built-in extension XInputExtension
   153.010] Initializing built-in extension XTEST
   153.010] Initializing built-in extension BIG-REQUESTS
   153.010] Initializing built-in extension SYNC
   153.010] Initializing built-in extension XKEYBOARD
   153.010] Initializing built-in extension XC-MISC
   153.010] Initializing built-in extension SECURITY
   153.010] Initializing built-in extension XINERAMA
   153.011] Initializing built-in extension XFIXES
   153.011] Initializing built-in extension RENDER
   153.011] Initializing built-in extension RANDR
   153.011] Initializing built-in extension COMPOSITE
   153.011] Initializing built-in extension DAMAGE
   153.011] Initializing built-in extension MIT-SCREEN-SAVER
   153.011] Initializing built-in extension DOUBLE-BUFFER
   153.011] Initializing built-in extension RECORD
   153.011] Initializing built-in extension DPMS
   153.011] Initializing built-in extension X-Resource
   153.011] Initializing built-in extension XVideo
   153.011] Initializing built-in extension XVideo-MotionCompensation
   153.011] Initializing built-in extension XFree86-VidModeExtension
   153.011] Initializing built-in extension XFree86-DGA
   153.011] Initializing built-in extension XFree86-DRI
   153.011] Initializing built-in extension DRI2
   153.011] (II) "glx" will be loaded by default.
   153.011] (II) LoadModule: "dri2"
   153.011] (II) Module "dri2" already built-in
   153.011] (II) LoadModule: "glamoregl"
   153.023] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
   153.033] (II) Module glamoregl: vendor="X.Org Foundation"
   153.033]     compiled for 1.13.2, module version = 0.5.0
   153.033]     ABI class: X.Org ANSI C Emulation, version 0.4
   153.033] (II) LoadModule: "glx"
   153.033] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
   153.033] (II) Module glx: vendor="X.Org Foundation"
   153.033]     compiled for 1.13.2, module version = 1.0.0
   153.033]     ABI class: X.Org Server Extension, version 7.0
   153.033] (==) AIGLX enabled
   153.033] Loading extension GLX
   153.033] (II) LoadModule: "vboxvideo"
   153.038] (WW) Warning, couldn't open module vboxvideo
   153.038] (II) UnloadModule: "vboxvideo"
   153.038] (II) Unloading vboxvideo
   153.038] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
   153.038] (II) LoadModule: "vmware"
   153.039] (II) Loading /usr/lib64/xorg/modules/drivers/vmware_drv.so
   153.176] (II) Module vmware: vendor="X.Org Foundation"
   153.176]     compiled for 1.13.1, module version = 13.0.0
   153.176]     Module class: X.Org Video Driver
   153.176]     ABI class: X.Org Video Driver, version 13.1
   153.176] (II) LoadModule: "modesetting"
   153.177] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
   153.177] (II) Module modesetting: vendor="X.Org Foundation"
   153.177]     compiled for 1.13.1, module version = 0.6.0
   153.177]     Module class: X.Org Video Driver
   153.177]     ABI class: X.Org Video Driver, version 13.1
   153.177] (II) LoadModule: "fbdev"
   153.178] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
   153.178] (II) Module fbdev: vendor="X.Org Foundation"
   153.178]     compiled for 1.13.1, module version = 0.4.3
   153.178]     Module class: X.Org Video Driver
   153.178]     ABI class: X.Org Video Driver, version 13.1
   153.178] (II) LoadModule: "vesa"
   153.179] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
   153.179] (II) Module vesa: vendor="X.Org Foundation"
   153.179]     compiled for 1.13.1, module version = 2.3.2
   153.179]     Module class: X.Org Video Driver
   153.179]     ABI class: X.Org Video Driver, version 13.1
   153.179] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710
   153.179] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
   153.179] (II) FBDEV: driver for framebuffer: fbdev
   153.179] (II) VESA: driver for VESA chipsets: vesa
   153.179] (++) using VT number 7

   153.179] (EE) open /dev/dri/card0: No such file or directory
   153.179] (WW) Falling back to old probe method for modesetting
   153.179] (EE) open /dev/dri/card0: No such file or directory
   153.179] (II) Loading sub module "fbdevhw"
   153.179] (II) LoadModule: "fbdevhw"
   153.180] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
   153.180] (II) Module fbdevhw: vendor="X.Org Foundation"
   153.180]     compiled for 1.13.2, module version = 0.0.2
   153.180]     ABI class: X.Org Video Driver, version 13.1
   153.180] (**) FBDEV(1): claimed PCI slot 3@0:2:0
   153.180] (II) FBDEV(1): using default device
   153.180] (WW) Falling back to old probe method for vesa
   153.180] (EE) Screen 0 deleted because of no matching config section.
   153.180] (II) UnloadModule: "modesetting"
   153.180] (II) FBDEV(0): Creating default Display subsection in Screen section
    "fbdev" for depth/fbbpp 24/32
   153.180] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
   153.180] (==) FBDEV(0): RGB weight 888
   153.180] (==) FBDEV(0): Default visual is TrueColor
   153.180] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
   153.180] (II) FBDEV(0): hardware: VESA VGA (video memory: 5120kB)
   153.180] (II) FBDEV(0): checking modes against framebuffer device...
   153.180] (II) FBDEV(0): checking modes against monitor...
   153.180] (--) FBDEV(0): Virtual size is 1280x1024 (pitch 1280)
   153.180] (**) FBDEV(0):  Built-in mode "current": 131.1 MHz, 80.3 kHz, 76.6 Hz
   153.180] (II) FBDEV(0): Modeline "current"x0.0  131.09  1280 1312 1472 1632  1024 1028 1032 1048 -hsync -vsync -csync (80.3 kHz b)
   153.180] (==) FBDEV(0): DPI set to (96, 96)
   153.180] (II) Loading sub module "fb"
   153.180] (II) LoadModule: "fb"
   153.181] (II) Loading /usr/lib64/xorg/modules/libfb.so
   153.196] (II) Module fb: vendor="X.Org Foundation"
   153.196]     compiled for 1.13.2, module version = 1.0.0
   153.196]     ABI class: X.Org ANSI C Emulation, version 0.4
   153.196] (**) FBDEV(0): using shadow framebuffer
   153.196] (II) Loading sub module "shadow"
   153.196] (II) LoadModule: "shadow"
   153.197] (II) Loading /usr/lib64/xorg/modules/libshadow.so
   153.207] (II) Module shadow: vendor="X.Org Foundation"
   153.207]     compiled for 1.13.2, module version = 1.1.0
   153.207]     ABI class: X.Org ANSI C Emulation, version 0.4
   153.207] (II) UnloadModule: "vmware"
   153.207] (II) Unloading vmware
   153.240] (II) UnloadModule: "vesa"
   153.240] (II) Unloading vesa
   153.240] (==) Depth 24 pixmap format is 32 bpp
   153.240] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel)
   153.258] (==) FBDEV(0): Backing store disabled
   153.259] (==) FBDEV(0): DPMS enabled
   153.259] (==) RandR enabled
   153.273] (II) AIGLX: Screen 0 is not DRI2 capable
   153.273] (II) AIGLX: Screen 0 is not DRI capable
   153.495] (II) AIGLX: Loaded and initialized swrast
   153.495] (II) GLX: Initialized DRISWRAST GL provider for screen 0
   ...........

wolfi323 · May 4, 2013, 11:48pm

Sorry, I misunderstood your original post…

In recovery mode, the fbdev driver seems to be used. If you are fine with that, you could configure X to use the fbdev driver and it should start in normal mode as well then.

To find out which kernel module claims your graphics card and prevents the ast driver to work, you could run:

lspci -k

benbowc · May 5, 2013, 1:19am

wolfi323:

Sorry, I misunderstood your original post…

In recovery mode, the fbdev driver seems to be used. If you are fine with that, you could configure X to use the fbdev driver and it should start in normal mode as well then.

To find out which kernel module claims your graphics card and prevents the ast driver to work, you could run:
lspci -k

Thats OK, easily done!

I guess this doesn’t tell us much as this is a running session. However for someone who might understand this a bit better it might be useful.


lspci -k
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
        Subsystem: IBM Device 03ce
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: ehci_hcd
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation 3400 Series Chipset LPC Interface Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: lpc_ich
00:1f.2 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: ata_piix
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: i801_smbus
00:1f.5 IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller (rev 05)
        Subsystem: IBM Device 03ce
        Kernel driver in use: ata_piix
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        Subsystem: IBM Device 03ce
        Kernel driver in use: e1000e
03:02.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10)
        Subsystem: IBM Device 03ce
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
        Subsystem: Intel Corporation Device 8086
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
        Subsystem: Intel Corporation Device 8086
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
        Subsystem: Intel Corporation Device 8086
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
        Subsystem: Intel Corporation Device 8086
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
        Subsystem: Intel Corporation Device 8086
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
        Subsystem: Intel Corporation Device 8086

gogalthorp · May 5, 2013, 3:38am

Never heard of ASPEED. a Driver seems to be available here
https://downloadcenter.intel.com/Detail_Desc.aspx?lang=eng&DwnldID=19212

Also there is a driver in the repos. go to Yast-Software management and search for aspeed with description checked in the search.

benbowc · May 5, 2013, 4:48am

Not a mainstream brand, lots of onboard video, nic etc. This is an ibm xserver. Worked fine with 12.1 but not 12.3 and I suspect xorg is the problem. Seems really weird that a kernel module is claiming the slot. Not sure how to figure out what is doing it…

benbowc · May 5, 2013, 5:16am

OK this is getting weirder… I ran X -configure and it failed but the conf file it produced is below. Why the heck would it think there were 3 screens and multiple devices. I’m wondering if I tidy this file up and try again it might actually work???


Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    Screen      2  "Screen2" RightOf "Screen1"
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    ModulePath   "/usr/lib64/xorg/modules/updates"
    ModulePath   "/usr/lib64/xorg/modules"
    FontPath     "/usr/share/fonts/misc:unscaled"
    FontPath     "/usr/share/fonts/Type1/"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/ghostscript/"
    FontPath     "/usr/share/fonts/cyrillic:unscaled"
    FontPath     "/usr/share/fonts/misc/sgi:unscaled"
    FontPath     "/usr/share/fonts/truetype/"
    FontPath     "built-ins"
EndSection

Section "Module"
    Load  "glx"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option        "Protocol" "auto"
    Option        "Device" "/dev/input/mice"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    Identifier   "Monitor0"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
EndSection

Section "Monitor"
    Identifier   "Monitor1"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
EndSection

Section "Monitor"
    Identifier   "Monitor2"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"               # <bool>]
        #Option     "kmsdev"                 # <str>
        #Option     "ShadowFB"               # <bool>]
    Identifier  "Card0"
    Driver      "modesetting"
    BusID       "PCI:3:2:0"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "ShadowFB"               # <bool>]
        #Option     "Rotate"                 # <str>
        #Option     "fbdev"                  # <str>
        #Option     "debug"                  # <bool>]
    Identifier  "Card1"
    Driver      "fbdev"
    BusID       "PCI:3:2:0"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "ShadowFB"               # <bool>]
        #Option     "DefaultRefresh"         # <bool>]
        #Option     "ModeSetClearScreen"     # <bool>]
    Identifier  "Card2"
    Driver      "vesa"
    BusID       "PCI:3:2:0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen1"
    Device     "Card1"
    Monitor    "Monitor1"
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen2"
    Device     "Card2"
    Monitor    "Monitor2"
    SubSection "Display"
        Viewport   0 0
        Depth     1
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     4
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     8
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     15
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

oldcpu · May 5, 2013, 10:14am

Any results from this ?

If it still fails, what does the /var/log/Xorg.0.log or Xorg.0.log.old file (associated with failed boot) look like ?

benbowc · May 5, 2013, 11:14am

Nothing changed. Appeared to be the exact same driver.

This is what was recorded when I did X -configuration:


..............................
 58392.326] (**) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
 58392.326] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
 58392.326] (WW) Disabling Mouse0
 58392.326] (WW) Disabling Keyboard0
 58392.326] (EE) open /dev/dri/card0: No such file or directory
 58392.326] (WW) Falling back to old probe method for modesetting
 58392.326] (EE) open /dev/dri/card0: No such file or directory
 58392.326] (II) Loading sub module "fbdevhw"
 58392.326] (II) LoadModule: "fbdevhw"
 58392.327] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
 58392.327] (II) Module fbdevhw: vendor="X.Org Foundation"
 58392.327]     compiled for 1.13.2, module version = 0.0.2
 58392.327]     ABI class: X.Org Video Driver, version 13.1
 58392.327] (**) FBDEV(1): claimed PCI slot 3@0:2:0
 58392.327] (II) FBDEV(1): using default device
 58392.327] (WW) Falling back to old probe method for vesa
 58392.447] Number of created screens does not match number of detected devices.
  Configuration failed.

oldcpu · May 5, 2013, 12:07pm

I do not know enough in this context to understand why X -configuration might be relevant.

My somewhat weak understanding is when X boots, especially with no-modeset and no configuration files specially setup, it will try one driver after another, until it finds one that works. So I don’t know enough to spot anything special in what you post. Was there a specific line that you wished to point out highlight … where you believe the meaning significant ? If so please advise, as the post content is lost on me.

It was the entire /var/log/Xorg.0.log post content that was of interest of me during a failed boot (also dmesg would be of interest) - and NOTE it is best to post the content of the log to a paste site such as SUSE Paste, give it an expiry time of 1/2 year or so, and press ‘create’, then share the URL location of the entry. That will avoid cluttering this thread with a massive post. Then if there is a specific entry you wish to point out, repost those few lines here, and maybe highlight in red the item of interest. NOTE this is only a suggestion to help improve the readability for those trying to help, and this is NOT intended to be a criticism.

Now when you boot with that xf86-video-ast rpm installed, and the boot fails, can you press <CTRL><ALT><F2> and get a text login ? If so, login as a regular user, and in your /home/username directory make a record of the dmesg for later analysis:


dmesg > failed-boot-dmesg.txt

and later when rebooting with ‘nomodeset’ you can check out the content of that ‘failed-boot-dmesg.txt’ file (or what ever name you called it).

Also send the command that was suggested previous:


/sbin/lspci -k | less

[press ‘q’ to exit the ‘less’ filter]

or you can record it for later analysis:


/sbin/lspci -k > failed-boot-lspci-k.txt

and later when rebooting with ‘nomodeset’ you can check out the content of that ‘failed-boot-lspci-k.txt’ file (or what ever name you called it).

Can you see there what kernel module has claimed the device ? You may need to look for occurrences of “VGA” or some other filter to figure out what this line (noted previous) means:


 125.881] (EE) ast: The PCI device 0x2000 at 03@00:02:0 has a kernel module claiming it.

ie possible (speculative on my part) searches when in this text mode could be:


/sbin/lspci -k | grep VGA

or


/sbin/lspci -k | grep 02:

ie we are trying to determine which kernel module is occupying PCI device 0x2000 at 03@00:02:0 … and I do not know the exact syntax to find that (hence my speculation).

I’ve also thought it might be possible to edit the /var/log/xorg.conf.d/50-device.conf file, putting a call in to your ast card driver, but I don’t know the correct syntax to call that driver and also if another kernel module has seized the graphic device and refusing to share/let-it-go then such an approach likely will not work (yet).

benbowc · May 5, 2013, 12:26pm

It was the last line that was interesting:

58392.447] Number of created screens does not match number of detected devices.
Configuration failed.

This doesn’t make sense. If the configuration generator screws up what is one to do???

Sorry I didn’t know how to handle all that log file. I’m usually self sufficient and sort my troubles eventually.

I’ll have to print out your instructions and do some more testing. Stand by!

wolfi323 · May 5, 2013, 1:13pm

Well, according to your lspci output, your gfx card is not in use by any kernel module.
I can think of 2 reasons for this:

there’s a bug in the ast driver, in that it incorrectly thinks the device is in use
one of the other drivers X tries to load results in a kernel module to be loaded which grabs the device

So maybe you could check ‘lspci -k’ again on a normal boot when X failed. (You can press Ctrl+Alt+F1 to get to a text console)

Don’t do that. Using an xorg.conf isn’t recommended anymore nowadays.
Remove it and create a file in /etc/X11/xorg.conf.d/ (or edit the existing /etc/X11/xorg.conf.d/50-device.conf) with the following content:

Section "Device"
  Identifier "Default Device"
  Driver "fbdev"
EndSection

Since your recovery bootup uses fbdev, this should work then. But you could also try to use “ast” here. Maybe it works if no other driver is loaded first…

oldcpu · May 5, 2013, 3:44pm

From before I note:


 125.881] (WW) AST: More than one matching Device section found: Autoconfigured Video Device ast
 125.881] (--) Chipset ASPEED Graphics Family found
 125.881] (EE) ast: The PCI device 0x2000 at 03@00:02:0 has a kernel module claiming it.
 125.882] (EE)** cirrus**: This driver cannot operate until it has been unloaded.

… and I am asking myself, why would the ‘cirrus’ graphic driver be loaded for an ASPEED graphic device ? Is cirrus the correct graphic driver ?

This is difficult for me to understand as I don’t have the hardware. When I type “man cirrus” I get (in part):


CIRRUS(4)                                                                                                                   CIRRUS(4)

NAME
       cirrus - Cirrus Logic video driver

SYNOPSIS
       Section "Device"
         Identifier "devname"
         Driver "cirrus"
         ...
       EndSection

DESCRIPTION
       cirrus is an Xorg driver for Cirrus Logic video chips.  THIS MAN PAGE NEEDS TO BE FILLED IN.

SUPPORTED HARDWARE
       The cirrus driver supports...

with no list of supported hardware

I note cirrus comes with the graphic driver rpm “xf86-video-cirrus”. I’m thinking maybe to remove that rpm, and then see if the ‘xf86-video-ast’ rpm works for the ASPEED hardware.

wolfi323:

Don’t do that. Using an xorg.conf isn’t recommended anymore nowadays.
Remove it and create a file in /etc/X11/xorg.conf.d/ (or edit the existing /etc/X11/xorg.conf.d/50-device.conf) with the following content:
Section "Device"
  Identifier "Default Device"
  Driver "fbdev"
EndSection
Since your recovery bootup uses fbdev, this should work then. But you could also try to use “ast” here. Maybe it works if no other driver is loaded first…

I’m wondering also if it may be worth while editing that file /etc/X11/xorg.conf.d/50-device.conf to instead try:

Section "Device"
  Identifier "Default Device"
  Driver "ast"
EndSection

then reboot and when rebooting try with, and also try without, the ‘nomodeset’ boot code ? I should also qualify my post by noting that it is full of a lot of speculation on my part. But I believe it ‘harmless’ and can be undone if it does not work.

consused · May 5, 2013, 4:00pm

If that doesn’t alter the situation, and if no other distro or user has filed a bug report somewhere, the only alternative is to report the bug on openSUSE’s bugzilla (see Wiki for how to check for existing reports, and filing new ones). This is not a commonly used driver, and it certainly looks like bug (if configuration doesn’t solve it).

Bearing in mind that openSUSE “packaged” the ast driver separately from the xorg-x11-driver-video collection in the OSS repo, when it was newly announced (i.e.in a Phoronix article) only one year ago as a new KMS-only linux driver. Since then it’s installed by default on openSUSE 12.2 and 12.3 (I don’t have 12.1 here).

From the change log, it was altered in September last year to “deal with XAA removal” but not repackaged for 12.2 Update. So its first public exposure for openSUSE testing was probably 12.3, and the packager may not have had access to server hardware with an aspeed card.

wolfi323 · May 5, 2013, 4:00pm

oldcpu:

From before I note:
 125.881] (WW) AST: More than one matching Device section found: Autoconfigured Video Device ast
 125.881] (--) Chipset ASPEED Graphics Family found
 125.881] (EE) ast: The PCI device 0x2000 at 03@00:02:0 has a kernel module claiming it.
 125.882] (EE)** cirrus**: This driver cannot operate until it has been unloaded.
… and I am asking myself, why would the ‘cirrus’ graphic driver be loaded for an ASPEED graphic device ? Is cirrus the correct graphic driver ?

That’s a “bug” in the ast driver. I had a look at the source code.
It seems they used the cirrus driver as template and forgot to change this error message…

To be clear: this is just a wrong message by the ast driver. The cirrus driver is not loaded.

oldcpu · May 5, 2013, 4:20pm

lol ! It illustrates how a mere typo can at times cause confusion as it can suggest an alternate credible meaning.

This graphic issue is stretching my knoweldge , which makes this interesting (for me) as I hope to learn some things.

I note this entry:


**02:00.0 **Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        **Subsystem: IBM Device** **03ce**
        Kernel driver in use: e1000e
**03:02.0** VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10)
        **Subsystem: IBM Device 03ce**

and also


 125.881] (WW) AST: More than one matching Device section found: Autoconfigured Video Device ast
 125.881] (--) Chipset ASPEED Graphics Family found
 125.881] (EE) ast: The PCI device **0x2000 at 03@00:02:0** has a kernel module claiming it.
 125.882] (EE) cirrus: This driver cannot operate until it has been unloaded.

and I ask myself, what does 0x2000 at 03:00:02:0 mean ?

Does that refer to 02:00.0 (Ethernet) or to 03:02.0 (VGA controller).

… I note on my PC 02:00.0 is used for my graphic hardware. From my PC:


oldcpu@corei7-920:~> /sbin/lspci -k | grep VGA -A1
02:00.0 VGA compatible controller: NVIDIA Corporation GT200 [GeForce GTX 260] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device 82cf

but I assume that is because of the PCI slot in which my graphic card is located.

It would be ugly if it was the Ethernet driver that was also attempting to claim the graphic card/PCI device location … but I think that not the case and my knowledge is too weak here to make an assessment.

But that also set me wondering … is the ASPEED graphic device on the motherboard ? or is it a PCI card ? If a PCI card, is there another PCI slot in which it could be placed and tried to see if it functions ? (again rather speculative on my part).

oldcpu · May 5, 2013, 4:29pm

Further to this thread, I note I note there is a new 3.7.10-1.4 kernel for openSUSE-12.2 I downloaded the new 3.7.10-1.4 kernel and looked at the change history since 28-Feb and noted this which MAY be relevant to this ast graphic thread:


* Mon Mar 04 2013 tiwai-at-suse.de
- Refresh patches.suse/SUSE-bootsplash-mgadrmfb-workaround.
  **Add the same w/a for ast and cirrus KMS, too (bnc#806990)**.
- commit fb10297

with the referenced bug report here: https://bugzilla.novell.com/show_bug.cgi?id=806990

The description of that bug report (and partial fix in the 3.7.10-1.4 kernel) does not appear to match the error messages that we have been focussing on, but still it does have me thinking that updating to that kernel version may be worth a try to see if that helps wrt the ast graphics.