Find the answer to your Linux question:
Page 3 of 3 FirstFirst 1 2 3
Results 21 to 23 of 23
Originally Posted by i92guboj The fdi file I told you to copy from /usr.... into /etc.... It's on the same post I told you the modifications for xorg.conf In any ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #21
    Just Joined!
    Join Date
    Apr 2009
    Posts
    13

    Quote Originally Posted by i92guboj View Post
    The fdi file I told you to copy from /usr.... into /etc.... It's on the same post I told you the modifications for xorg.conf

    In any case, I am glad that it works now. If you have problems with the localization/language of your keyboard you might need to tune that file a bit. But the bigger problem is solved now hopefully
    yes I did that to with the policy and that.

  2. #22
    Linux Guru
    Join Date
    Nov 2007
    Location
    Córdoba (Spain)
    Posts
    1,513
    The error about drm is this one:

    Code:
    drmOpenDevice: Open failed
    [drm] failed to load kernel module "i915"
    (EE) [drm] drmOpen failed.
    (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
    This can be for a number of reasons but almost always it has to do with a relevant driver not being in sync with the current xorg version. I never used the intel driver so maybe just recompiling it might fix it (if not then I am not the best one to help you with that).

    You can try:

    Code:
    emerge -1 x11-drivers/xf86-video-intel
    And see if the error goes away after restarting X.


    While you are at it, you can also do a bit of cleaning in your xorg.conf. The modules don't need to be loaded explicitly now, and the input sections can be completely eliminated as well. But always keep a backup, just in case.

    The fonts sections shouldn't be needed either.

    Code:
    Section "ServerLayout"
    Identifier ""X.org Configured
    Screen 0 "A19-3A" 0 0
    EndSection
    
    Section "Module"
    # I leave xtrap just because you had it, but if you don't
    # need it, you can remove this whole section
    Load "xtrap"
    EndSection
    
    Section "Monitor"
    Identifier "19tommer"
    VendorName "Fujitsu-Siemens"
    ModelName "A19-3A"
    EndSection
    
    Section "Device"
    ###Available Driver Options Are:-
    ###Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ###<string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ###[arg]: arg optional
    #Option "NoAccel" # [<bool>]
    #Option "SWcursor" # [<bool>]
    #Option "ColorKey" # <i>
    #Option "CacheLines" # <i>
    #Option "Dac6Bit" # [<bool>]
    #Option "DRI" # [<bool>]
    #Option "NoDDC" # [<bool>]
    #Option "ShowCache" # [<bool>]
    #Option "XvMCSurfaces" # <i>
    #Option "PageFile" # [<bool>]
    Identifier "Card0"
    Driver "intel"
    Vendorname "Intel Corporation"
    BoardName "Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    EndSection
    
    
    Section "Screen"
    Identifier "A19-3A"
    Device "Card0"
    Monitor "19tommer"
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1280x1024" "1024x768" "800x600"
    EndSubSection
    EndSection
    
    Section "DRI"
    Mode 0666
    End Section
    Maybe you can remove even the video stuff, most open source drivers don't need it either nowadays. But as said, I know nothing about intel so I won't remove. I think that the DRI section is not needed for intel cards either (maybe a leftover from an ati or something?), but I am not sure.

    This will alleviate the speech in your log files as well, which will make it easier for other people to diagnose things.

  3. #23
    Just Joined!
    Join Date
    Apr 2009
    Posts
    13
    thanks - i'll do that.

Page 3 of 3 FirstFirst 1 2 3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •