You are not logged in.

#1 2007-11-09 08:57:42

lithium
Member
Registered: 2007-09-18
Posts: 78

Updated, X won't start (openchrome)

Hey all,

I just updated my system (pacman -Syu) after a brief vacation (~3 weeks). After a reboot I found that X no longer starts. Here is the error message that I get when I run startx:

ABI major version (1) doesn't match the server's version (2)
(EE) Failed to load module "via" (module requirement mismatch, 0)
(EE) No drivers available.

Fatal server error:
no screens found

I am using OpenChrome with a built in VIA chipset. Relevant portion of xorg.conf:

Section "Device"
    Identifier  "VIA Unichrome"
    Driver      "via"
    BusID       "PCI:1:0:0"
    Option         "EnableAGPDMA"
EndSection

Worked flawlessly before upgrade (other than the card sucking).

Last edited by lithium (2007-11-09 08:58:37)

Offline

#2 2007-11-09 09:57:26

retsaw
Member
From: London, UK
Registered: 2005-03-22
Posts: 132

Re: Updated, X won't start (openchrome)

A search would have found the solution for you: http://bbs.archlinux.org/viewtopic.php?id=39537

The answer is to add

Section "ServerFlags"
        Option "IgnoreABI" "True"
EndSection

to your xorg.conf

Offline

#3 2007-11-10 05:21:51

lithium
Member
Registered: 2007-09-18
Posts: 78

Re: Updated, X won't start (openchrome)

Yes indeed: That fixes it. I did try searching but I guess I skipped over that one.

Thanks.

Offline

#4 2007-11-10 07:05:28

lithium
Member
Registered: 2007-09-18
Posts: 78

Re: Updated, X won't start (openchrome)

New Problem. I tried running glxinfo to see if DRI was still working OK. The following was printed:

name of display: :0.0
libGL warning: 3D driver claims not to support visual 0x47

Then the system completely freezes. I can't CTRL+ALT+BACKSPACE, I can't even CTRL+ALT+DEL. Nothing works: I have to pull the plug. This card was working fine before so I doubt its a hardware issue.

Full xorg.conf:

Section "ServerLayout"
    Identifier     "Builtin"
    Screen         "Screen0"
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "ServerFlags"
        Option "IgnoreABI" "True"
EndSection

Section "Files"
    RgbPath      "/usr/share/X11/rgb"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
    FontPath     "/usr/share/fonts/artwiz-fonts"
    FontPath     "/usr/share/fonts/speedo"
EndSection

Section "Module"
    Load  "extmod"
    Load  "xtrap"
    Load  "record"
    Load  "dbe"
    Load  "glx"
    Load  "dri"
    Load  "freetype"
    Load  "type1"
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"
EndSection

Section "Monitor"
    Identifier   "Samsung LCD"
    VendorName   "Samsung"
    ModelName    "940BX"
    VertRefresh  60
EndSection

Section "Device"
    Identifier  "VIA Unichrome"
    Driver      "via"
    BusID       "PCI:1:0:0"
    Option         "EnableAGPDMA"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "VIA Unichrome"
    Monitor    "Samsung LCD"
    DefaultDepth    24
    SubSection "Display"
        Modes      "1280x1024"
        Virtual      1280 1024
        Depth     24
    EndSubSection
EndSection

Section "DRI"
    Mode     0666
EndSection

Last edited by lithium (2007-11-10 07:58:55)

Offline

#5 2007-11-10 21:19:09

lithium
Member
Registered: 2007-09-18
Posts: 78

Re: Updated, X won't start (openchrome)

Removed openchrome, Installed xf86-video-via. Seems to work fine. Direct rendering works as well (checked with glxinfo). Glxgears gives me ~480fps. No need for "IgnoreABI" setting.

Looks like this is a bug in openchrome.

Strangely enough I still get the "libGL warning: 3D driver claims not to support visual 0x47". Also, the first time I run glxinfo, it runs fine. Every time after that, it segfaults halfway in.

Edit: Perhaps I spoke too soon. xf86-video-via seems to freeze at other times (like when I run something through wine). Is there no stable driver for my card (K8M800 VIA/S3G)?

Last edited by lithium (2007-11-11 04:34:44)

Offline

#6 2007-11-12 09:06:51

Aakko
Member
Registered: 2007-10-23
Posts: 65

Re: Updated, X won't start (openchrome)

I have KM400 and opengl was working for me somehow. Whew days ago Mesa and ligbl was updated to 7.0.1, which completelly broke the opengl on my system. X locked up when ever I tried to start opengl-softwares. It says at the openchrome.org:

"The 3D driver that complements the openchrome driver can be obtained from the DRI project. For now you should use the Mesa-6.4 branch; the last version known to work sort of reliably is Mesa-6.4.1."

I wen't trough building mesa, libgl and unichrome-dri from Mesa-6.4.1-branch with ABS. I also compiled latest openchrome-driver from svn (be advised if you update the driver from svn you have to change the driver from via to openchrome in xorg.conf because of the name change.) Now opengl works on my system. At least I can run Wine and Blender without lockup. Compiz, Beryl etc compositing stuff will not work with openchrome because there isn't yet support for those in the driver.

Offline

#7 2007-11-13 01:33:19

lithium
Member
Registered: 2007-09-18
Posts: 78

Re: Updated, X won't start (openchrome)

Aakko wrote:

I wen't trough building mesa, libgl and unichrome-dri from Mesa-6.4.1-branch with ABS. I also compiled latest openchrome-driver from svn (be advised if you update the driver from svn you have to change the driver from via to openchrome in xorg.conf because of the name change.) Now opengl works on my system. At least I can run Wine and Blender without lockup. Compiz, Beryl etc compositing stuff will not work with openchrome because there isn't yet support for those in the driver.

Wow seems like quite a procedure. Perhaps it's just better to get a $30 nvidia card which will have better performance and support.

Why would mesa just drop support for this card?

Last edited by lithium (2007-11-13 01:35:43)

Offline

Board footer

Powered by FluxBB