Jump to content

ac_dispatcher

OTW
  • Posts

    499
  • Joined

  • Last visited

Posts posted by ac_dispatcher

  1. Are we talking about a lilo bootsplash? Here is my bootsplash.

     

     

    I forget what Linux webite I got the pic from. Nice Linux mascot though :cheesy:

     

    Edit:

    Never mind file attachment didnt work

     

    Edit #2:

    File was to big - fixed it :headbang:

    post-1694-1095082163_thumb.jpg

  2. I have no doubt you are correct. In the Caracter Devices Section:

     

    The following cards have drivers in the 2.6 kernel:

     

    3dfx Banshee/Voodoo3+ - 3dfx Banshee or Voodoo3 (or later)

    3dlabs GMX 2000 - old gamma driver

    ATI Rage 128 - ATI Rage 128 graphics card

    ATI Radeon - ATI Radeon graphics card both PCI and AGP versions

    Matrox g200/g400 - Matrox G200, G400 or G450

    SiS video cards - SiS 630 or compatible video chipset

     

    I have a ATI Mobility M6 LY. Compiled it all in the kernel (ALI/ATI/Radeon) and Direct Rendering works everytime. I got stuck in that no mans land - ATI now has drivers but its post 7000 series (I think 7000)

     

    8500 and up maybe?

     

    Anyway after I started useing the 2.6 kernel I lost Direct Rendering. I tried everything I could find in the Gentoo forums.(first went to 2.6 in Gentoo). Found the answer in the kernel compile. :lol:

  3. Finally got xorg 6.8 and transparency to work in Gentoo.

     

    Found great info here:

     

    http://gentoo-wiki.com/TIP_Xorg_X11_and_Tranparency

     

    I must admit my 32mb Radoen card is really getting pushed to do it. Computer has slowed a bit. Not sure If I can keep it running all the time.

     

     

     

    This is the link to my desktop via Xorg 6.7 no transparency:

    http://mandrakeusers.org/index.php?act=Att...ype=post&id=982

     

    Attached is my new Desktop :thumbs:

     

    Check out the shading and transparency. Xorg 6.8 rocks :headbang:

    post-1694-1094999572_thumb.jpg

  4. May seem like overkill here about etc-update - but - When I do a emerge -u world I first tar up the whole darn /etc directory.

     

    Its not that big and dont take but a second. Then I rename it to that days date and save it to a backup.

     

    That way if something goes wrong I can track the changes from one emerge -u to another. May seem like overkill but Ive killed my Gentoo system to many times being lazy with etc-update. "-5" anyone?

     

    I also agree about the Gentoo board. Im a member their but I dont post much, most have been asked already. Plus youll get a few RTFM or search the forum postings if you get a bit lazy.

     

     

     

     

    How many of you run ~x86? I do - and still rock solid. If find nitro-sources are best on my lappy. :cheesy:

  5. I have another thing to try. Now Im not positive this is the case but. I don't do the "Display" section like Mandrake does. My reason/findings:

     

    This is your XF86Config-4:

     

     
       Subsection "Display" 
          Depth 24 
          Virtual 1280 1024 
      EndSubsection

     

    This is mine:

     

     
       Subsection "Display" 
          Depth 24 
          Modes "1280x1024" "1024x768" "800x600" "640x480" 
      EndSubsection

     

    This is what I have found through trail and error (with NWN). From what I found if you have "Virtual 1280 1024" is basically locks that screen resolution. If you have "Modes "1280x1024" "1024x768" "800x600" "640x480"" it will allow programs to resize X for its needs.

     

    Now for the record I didn't read this no where I just saw it on another XF86Config and tried it - and it worked. Thru trial and error I came up with the conclusion. Give that a try.

  6. Im not at my computer right now but if I remember correctly X11 fowarding needs to be turned on.

     

    Found this on google:

    Before establishing the ssh connection the xserver must be started and the environment variable DISPLAY must be set for ssh.

    $ DISPLAY=localhost:0.0

    $ export DISPLAY

    $ ssh -Y remotehost

     

    or

     

    $ DISPLAY=localhost:0.0 ssh -Y remotehost

     

    The parameter -Y enables trusted X11 Forwarding. This is available since OpenSSH 3.8. If you have an older version of ssh you will have to use -X.

     

    Make sure you're not starting ssh with the parameter -x (lowercase). This disables X11Forwarding.

     

    Check that X11Forwarding is not disabled in the openssh client configuration.

     

    The configfiles are by default ~/.ssh/config and /etc/ssh_config. The file in the home directory overrides settings in the global one.

     

    The configfile is split into various sections starting with "Host wildcard". The section applies to all hosts where wildcard matches the hostname.

     

    If this section contains an entry "ForwardX11 no" then X11Forwarding is disabled. To enable it change the entry to:

     

    ForwardX11 yes

     

    I ripped the whole thing from a web site try some of that

  7. Im working until Monday. Ill work on a uber newbie style kernel config / compile for DRM.

     

    Looks like it will have to include basic kernel compile, lilo setup, and XF86Config-4 (or xorg.conf) setup. Might take a day or two but Ill start on it Monday..

  8. Need some more info:

     

    open a terminal (konsole in KDE):

     

    $glxinfo

     

    post the output

     

    $glxgears

     

    after about 5 lines of output stop it and copy it here

     

    Finally

    Copy&post your /etc/X11/XF86Config-4 here

  9. Open a terminal (konsole in KDE) :

     

    Change to root

     

    $su

    [enter password if needed]

     

     

    Looks like your module is loaded ok with lsmod. When in doubt do it command line I always say:

     

    # ifconfig eth0 ${IP_ADDR} broadcast ${BROADCAST} netmask ${NETMASK} up

     

    so based of your data:

     

    #ifconfig eth0 192.168.0.150 broadcast 192.168.0.255 netmask 255.255.255.0 up

     

    then do:

    # route add default gw ${GATEWAY}

     

    based of your data:

     

    #route add default gw 192.168.0.100

     

    #ping -c 3 www.yahoo.com

     

    Odd that you have:

    /etc/resolv.conf

    domain wtcsu.pri

    search wtcsu.pri

    nameserver 192.168.0.1

    nameserver 192.168.0.150

    nameserver 192.168.0.100

    You are running a DNS all all three computers? Dont you have you DNS from you internet provider? That one is probably the most important one to have. In a DCHP system it is automatically set but in a static network YOU must provide the DNS.

     

    If you have your ISP Domain Name Server then just:

     

    #nameserver ***.***.***.*** >> /etc/resolv.conf

     

    Where the *** are enter the address.

     

    If any of yours may be a name sever its PC#2( IP : 192.168.0.100) cause that is your gateway. Can PC #1 reach the internet? To check for a nameserver problem to. Try this

     

    #ping -c 3 www.yahoo.com

    Does it work? then try:

    #ping -c 3 216.109.117.205

     

    You just pinged Yahoo - one with the use of a DNS and one without. If the second one worked you need to set a DNS in the hosts file. Also Hope it helps

     

    AC

  10. What you will find with a lot of older cards is this:

     

    The 2.4 kernel played nice with the older ATI cards (pre 7000)

     

    The 2.6 kernels are another matter. I have a ATI Mobility M6 LY. I worked MANY hours trying to get DRM to work with this card with the 2.6 kernel. I have it now, problem solved. You see I read TONS of postings on load this first or that first try this drive or that. In the end I figured it out.

     

    The 2.6 kernel has useable drivers for your card. With the 2.4 you never used the internal drivers, with the 2.6 its about the only way you'll get direct rendering to work. Im not talking loading kernel modules Im talking a custom kernel compile with the chipset, agpgart, and video card built into the kernel.

     

    >>>

    I've been thinking on writing a HOW-TO get DRM (3d Acceleration) working on older cards. Not sure if you have DRI working?

     

    open a terminal (konsole) and type:

     

    $glxinfo | grep direct

     

    What do you get?

     

    here is mine:

    acdispatcher@arora ~ $ glxinfo | grep direct

    direct rendering: Yes

     

    If you don't have that (except those who have nividia cards) you don't have DRI or 3d acceleration

    .

     

    The following cards have drivers in the 2.6 kernel:

     

    3dfx Banshee/Voodoo3+ - 3dfx Banshee or Voodoo3 (or later)

    3dlabs GMX 2000 - old gamma driver

    ATI Rage 128 - ATI Rage 128 graphics card

    ATI Radeon - ATI Radeon graphics card both PCI and AGP versions

    Matrox g200/g400 - Matrox G200, G400 or G450

    SiS video cards - SiS 630 or compatible video chipset

     

     

    Ill write a HOW to if a few people here need it. I give no guarantees on making it work but it could be fun :P

     

    Basically it will be a How-To compile a custom kernel step by step for video card DRI purposes. I cant start it for a few days (work) if anyone needs it. I don't want to do it either if no one needs it.

     

     

    Notes on DRI / DRM

     

    What is DRI?

    The Direct Rendering Infrastructure (dri.sourceforge.net), also known as the DRI, is a framework for allowing direct access to graphics hardware in a safe and efficient manner. It includes changes to the X server, to several client libraries and to the kernel. The first major use for the DRI is to create fast OpenGL implementations.

     

    What is XFree-DRM and how does it relate to regular XFree86?

    XFree-DRM is an enhancement to XFree86 that adds 3D acceleration for cards by adding the kernel module necessary for direct rendering.

     

    People who can't get direct rendering working with just XFree. XFree-DRM works for 3dfx, gamma, i8x0, matrox, rage128, radeon, mach64 (as of xfree-drm-4.3.0-r7) and sis300 series drivers. Since the 2.4 kernels' Direct Rendering Manager (DRM) doesn't support XFree 4.3, the xfree-drm package is needed. If you're using a 2.6 kernel, its DRM supports XFree 4.3.

     

    XFree or now a days Xorg :P

     

    Thats why you need to get DRM working via the kernel with the new 2.6 kernels.

     

     

    Sorry so :offtopic:

  11. Yep Im already on that.

     

    #emerge -u xorg-x11

     

    One thing to check (got me)

     

    in your /etc/X11/xorg.conf

     

    if it has:

     Identifier "Keyboard1"
       Driver "Keyboard"

     

    Change it to:

    Identifier "Keyboard1"
       Driver "kbd"

     

     

    Shadows look better, so does some transparancy stuff. Very smooth :headbang::headbang:

  12. No dont think so. As long as you had the kernel source installed. Which I dont think you could have installed the nvidia driver without it.

     

    As bad is this sounds (im gonna get flamed) reboot your computer. If it still doesnt work post for XF86 log here.

     

    its in /var/log/XF86.....log

     

    Cant remember the exact name to it (I use xorg).

     

    DRI turns off on me sometimes when I reset my X sever to much. The only way to get it back is to reboot.

     

     

    ./flame vest

     

     

    Ive been up all night. I got to go to bed. Ill check back in about 6 hours. Someone else may try to help.

     

    Also remember GIYF

     

    (google is your friend)

  13. Try something - might not make a difference but its worth a shot (wont hurt)

     

    In the XF86Config-4 change:

     

    DefaultColorDepth 15

     

    to

     

    DefaultColorDepth 16

  14. open a terminal (konsole)

     

    type

    $ su

    [enter password if needed]

    #kwrite

     

    you will notice the terminal will change from a "$" to a "#" when you become root. When kwrite opens open the /etc/X11/XF86Config-4 and edit it.

     

    AC

  15. The stuff inside the quotes "" are freeform, meaning you can type what you want. It is for info only.

     

    When you boot does a white NVIDIA screen appear?

     

    also I think your missing the dri section. Im not talking about "Load dri"

     

    under the "Module" section put this in

     

    Section "DRI"

        Mode 0666

    EndSection

     

    So your stuff will look like:

     

    Section "Module"

        Load "dbe" # Double-Buffering Extension

        Load "v4l" # Video for Linux

          Load "extmod"

          Load "type1"

          Load "freetype"

          Load "glx" # 3D layer

    EndSection

     

    Section "DRI"

        Mode 0666

    EndSection

     

    Section "InputDevice"

          Identifier "Keyboard1"

          Driver "Keyboard"

          Option "XkbModel" "pc105"

          Option "XkbLayout" "en_US"

          Option "XkbOptions" ""

    EndSection

     

    and so on......

     

    I dont have a Nvidia card (I used to have a MX 440)

    Give that a go

×
×
  • Create New...