Loading ...
Sorry, an error occurred while loading the content.

Re: getting X4.0.1c thru CVS tree

Expand Messages
  • thoroughbredinjun@hotmail.com
    Hi Brett, when I do the trace option as mentioned by you, # cvs checkout -r -t xf-4_0_1c xc for the x4.0.1c version it says can t find the 4.0.1c module ,
    Message 1 of 10 , Nov 2, 2000
    • 0 Attachment
      Hi Brett,
      when I do the trace option as mentioned by you,

      # cvs checkout -r -t xf-4_0_1c xc

      for the x4.0.1c version it says can't find the 4.0.1c module , hence
      program aborts with message, "cvs checkout" aborted! But when I do
      without the -t option it works..?? Any advice? Am I doing the right
      thing to get the 4.0.1c ? What happened was I closed the LID on the
      inspiron so it slipped! So I had to ctrl-c it and then redo it again.
      I think if we set it up in the BIOS, it should work regardless of what
      OS is used? I have to try it. Another thing, there is spurious mouse
      movements with the symantec touch pad. It works ok most of the time.
      Did you experiance any difficulties? If this doesn't work with the new
      x(I hope I am getting the x4.0.1c) I think I am gonna go MANDRAKE
      which I really liked when I installed the beta version. I do not the
      know what x version the newly released 7.2 has? As for debian how is
      the installation? What's your views on it? Any pluses/minuses in
      particular?
      God, I can't wait to get the 1600x1200 :( how does it look like?
      SWEEEET , I am sure!
      thanks for your time,
      sincerely,
      rvk

      " "Disorder increases with time because we measure time in the
      direction in which disorder increases"
      - S.Hawking,Lucasian Professor of Mathematics


      --- In linux-dell-laptops@egroups.com, Brett Viren <bv@b...> wrote:
      > thoroughbredinjun@h... writes:
      > ...
      > > I am using the school
      > > network which is fast(and not 28 modem;) ). I just got back and
      it is
      > > still running!!! I mean css server: Updating blah blah
      >
      > Something is wrong. I would kill it (Ctrl-C) and then re-run with
      the
      > `-t' flag and see if that gives any enlightening diagnostics.
      Killing
      > and restarting doesn't mean that you will be regetting any thing
      that
      > did manage to be downloaded.
      >
      > Also addding `-z3' will perform compression and speed up the
      transfer
      > (if that is indeed the problem). Generally CVS works very fast (we
      > used it from NY to a remote site in the mountains of Japan and it
      was
      > often faster than ftp).
      >
      > > :( Do you get
      > > it to work at higher resolution with x4.0.1c?
      >
      > I use the Debian ``X strike force'' packages which as of today's
      > `apt-get upgrade' are up to 4.0.1d. And, yes I get full 1600x1200
      > using them (as I did with 4.0.1c).
      >
      > BTW, it *may* be possible for you to use the server from the Debian
      > package (you can unpack via `ar x package.deb') on your system.
      This
      > isn't guaranteed to work if there are major library missmatches.
      >
      > > That's the whole point
      > > of this exercise. I am getting currently with the default x4.0.1a
      that
      > > came with redhat 7.0, 1024x768 and I tried copying Jeff's r128.o
      and
      > > it worked ok, but the XF86Config made my screen caramellize since
      I
      > > would imagine they used x4.0.1c and made it work. Do you get
      > > 1600x1200? thanks for your time! I was able to get 1400x1050
      before I
      > > deleted mandrake 7.2b.
      >
      > For me, the carmallizing was related to suspending the machine by
      > closing the lid followed by stopping X or switching a VC. Turning
      > power management off in the BIOS (as suggested on this list) took
      care
      > of this.
      >
      > -Brett.
    • Brett Viren
      Warning to lurkers: this thread is getting off topic, read only at the peril of wasting your time . ... cvs cares about how its arguments are ordered.
      Message 2 of 10 , Nov 2, 2000
      • 0 Attachment
        Warning to lurkers: this thread is getting off topic, read only at the
        peril of wasting your time <grin>.

        thoroughbredinjun@... writes:
        > Hi Brett,
        > when I do the trace option as mentioned by you,
        >
        > # cvs checkout -r -t xf-4_0_1c xc

        cvs cares about how its arguments are ordered. There are two
        ``regions'', one after ``cvs'' but before the command (such as
        ``checkout'') and the other after the command. All command
        independent options come in the first region. In short you should
        type:

        cvs -t checkout -r xf-4_0_1c xc

        > Another thing, there is spurious mouse
        > movements with the symantec touch pad. It works ok most of the time.

        What is listening to the mouse port? Is it `gpm' or X? If `gpm' are
        you starting it with the `-t synps2' option or just `-t ps2'.
        I have had the jerky mouse movements only with I use `gpm -t synps2'
        but plain `gpm -t ps2' works, as does X (with GPM not running!)

        > As for debian how is
        > the installation? What's your views on it? Any pluses/minuses in
        > particular?

        The latest stable Debian (``potato'') installs very easy. You can
        look at my page if you want to go this route:

        http://minos.phy.bnl.gov/~bviren/inspiron/

        If you install Debian, I would suggest you order a CD
        (www.cheapbytes.com usually has them for a couple bucks) as it will be
        much easier than following what I did to the letter.

        I don't want to start talking too much about pros and cons of
        different distributions as it always starts a flame fest, but I will
        give you smoe personal *opinions*. Since I started using Debian 5
        years ago after switching from Slackware, I have been extreamly
        impressed with how tight and smooth the system is and each release
        just gets better. I have dabled in Red Hat a little (mostly dealing
        with friends who's systems have fallen apart) and I have not been very
        impressed with what I saw. However, I don't recommend newbies to jump
        into Debian unless they are interested in how things really work in
        the system. They have to want to learn some things and be able to
        troll through mailing lists and FAQs for info from time to time.

        One thing I am sure about is in the time you have spent so far you
        could have installed Debian and had a working system.

        -Brett.
      • thoroughbredinjun@hotmail.com
        Hi Brett + other GURUS here, First of all thanks in advance for your time. I had some trouble with newly brewed x4.0.1c with rh 7.0 Ok, problem #1 (questions
        Message 3 of 10 , Nov 14, 2000
        • 0 Attachment
          Hi Brett + other GURUS here,
          First of all thanks in advance for your time. I had some trouble with
          newly brewed x4.0.1c with rh 7.0

          Ok, problem #1 (questions galore!)
          ==============
          I have Dell Inspiron 5000e + 10Gig Hard drive + ATI Rage mobility 128
          LF(as recognised by XF86Config) + 16MB video mem + 128MB ram +
          1600x1200 LCD display dual boot with windows me

          I brewed my own X4.0.1c (don't be mistaken, my ignorance tends to
          infinity asymptotically;) ) after grabbing the source from cvs(many
          sleepless hours..) and compiled it after I installed a barebone(minus
          kde+gnome) redhat 7.0. I had by default the desktop *another level
          (fvWM)* and it worked fine tho I had only 1024 x 768 res. Now this was
          with x4.0.1a . I exited out of dektop and compiled my cvs source and
          went into su mode then did *make install >& install.log &
          everything went fine(no errors). then I overwrote
          a)XF86Config-4 with Jeff's file and his driver & did *startx*
          result --> system hung!
          b)tried Scot's XF86Config-4 file , result --> same as before :(
          c) did *setup* as su and configured (only thing I changed was monitor
          (custom) where I did specify the vertical & horizonatl refresh & scan
          rates (28-90 and 50-62)
          result --> didn't work :( :(

          I am getting errors re: fontpath in my x.err file from startx which
          is copied below:(I am sorry it is a long email, I thought you could
          just scan them off and go directly where the problem was at the end!)

          =============BEGIN X.ERR FILE===================================
          XFree86 Version 4.0.1c / X Window System
          (protocol Version 11, revision 0, vendor release 6400)
          Release Date: 28 August 2000
          If the server is older than 6-12 months, or if your card is
          newer
          than the above date, look for a newer version before reporting
          problems. (see http://www.XFree86.Org/FAQ)
          Operating System: Linux 2.2.16-22 i686 [ELF]
          Module Loader present
          (==) Log file: "/var/log/XFree86.0.log", Time: Tue Nov 14 17:36:47
          2000
          (==) Using config file: "/etc/X11/XF86Config-4"
          Markers: (--) probed, (**) from config file, (==) default setting,
          (++) from command line, (!!) notice, (II) informational,
          (WW) warning, (EE) error, (??) unknown.
          (==) ServerLayout "XFree86 Configured"
          (**) |-->Screen "Screen0" (0)
          (**) | |-->Monitor "CustomConfiguration"
          (**) | |-->Device "ATI|Rage Mobility M3 AGP 2x"
          (**) |-->Input Device "Mouse0"
          (**) |-->Input Device "Keyboard0"
          (**) XKB: layout: "us"
          (**) FontPath set to "unix/:7100"
          (==) RgbPath set to "/lib/X11/rgb"
          (==) ModulePath set to "/lib/modules"
          (--) using VT number 7

          (II) Loading /lib/modules/fonts/libbitmap.a
          (II) Module bitmap: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/libpcidata.a
          (II) Module pcidata: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 0.1.0
          (II) Loading /lib/modules/libscanpci.a
          (II) Module scanpci: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 0.1.0
          (II) Unloading /lib/modules/libscanpci.a
          (--) PCI:*(1:0:0) ATI Rage 128 Mobility LF rev 2, Mem @
          0xf8000000/26, 0xf4100000/14, I/O @ 0x2000/8
          (II) Loading /lib/modules/extensions/libGLcore.a
          (II) Module GLcore: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/libdbe.a
          (II) Module dbe: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/libdri.a
          (II) Module dri: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/linux/libdrm.a
          (II) Module drm: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/libextmod.a
          (II) Module extmod: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/libglx.a
          (II) Module glx: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/libpex5.a
          (II) Module pex5: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/extensions/librecord.a
          (II) Module record: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.13.0
          (II) Loading /lib/modules/extensions/libxie.a
          (II) Module xie: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/drivers/linux/v4l_drv.o
          (II) Module v4l: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 0.0.1
          (II) Loading /lib/modules/drivers/r128_drv.o
          (II) Module r128: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 3.1.1
          (II) Loading /lib/modules/input/mouse_drv.o
          (II) Module mouse: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) v4l driver for Video4Linux
          (II) r128: Driver for ATI Rage 128 chipset: ATI Rage 128 RE (PCI),
          ATI Rage 128 RF (AGP), ATI Rage 128 RK (PCI), ATI Rage 128 RL
          (AGP),
          ATI Rage 128 Pro PF (AGP), ATI Rage 128 Mobility LE (PCI),
          ATI Rage 128 Mobility LF (AGP)
          (--) Assigning device section with no busID to primary device
          (--) Chipset ATI Rage 128 Mobility LF (AGP) found
          (II) Loading /lib/modules/libvgahw.a
          (II) Module vgahw: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 0.1.0
          (II) r128(0): PCI bus 1 card 0 func 0
          (**) r128(0): Depth 16, (--) framebuffer bpp 16
          (II) r128(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps)
          (==) r128(0): Default visual is TrueColor
          (==) r128(0): RGB weight 565
          (II) r128(0): Using 6 bits per RGB (8 bit DAC)
          (II) Loading /lib/modules/linux/libint10.a
          (II) Module int10: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) r128(0): initializing int10
          (II) r128(0): Primary V_BIOS segment is: 0xc000
          (--) r128(0): Chipset: "ATI Rage 128 Mobility LF (AGP)" (ChipID =
          0x4c46)
          (--) r128(0): Linear framebuffer at 0xf8000000
          (--) r128(0): MMIO registers at 0xf4100000
          (--) r128(0): VideoRAM: 16384 kByte (128-bit SDR SGRAM 1:1)
          (II) r128(0): Panel dimensions: 1400x1050
          (WW) r128(0): Video BIOS not detected in PCI space!
          (WW) r128(0): Attempting to read Video BIOS from legacy ISA space!
          (II) r128(0): PLL parameters: rf=2700 rd=60 min=12500 max=25000;
          xclk=10500
          (==) r128(0): Using gamma correction (1.0, 1.0, 1.0)
          (II) r128(0): CustomConfiguration: Using hsync range of 28.00- 90.00
          kHz
          (II) r128(0): CustomConfiguration: Using vrefresh range of 50.00-
          62.00 Hz
          (II) r128(0): Clock range: 12.50 to 250.00 MHz
          (WW) r128(0): Mode "640x350" deleted (vrefresh out of range)
          (WW) r128(0): Mode "640x400" deleted (vrefresh out of range)
          (WW) r128(0): Mode "720x400" deleted (vrefresh out of range)
          (WW) r128(0): Mode "640x480" deleted (vrefresh out of range)
          (WW) r128(0): Mode "640x480" deleted (vrefresh out of range)
          (WW) r128(0): Mode "640x480" deleted (vrefresh out of range)
          (WW) r128(0): Mode "800x600" deleted (vrefresh out of range)
          (WW) r128(0): Mode "800x600" deleted (vrefresh out of range)
          (WW) r128(0): Mode "800x600" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1024x768" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1024x768" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1024x768" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1024x768" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1152x864" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1280x960" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1280x1024" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1280x1024" deleted (hsync out of range)
          (WW) r128(0): Mode "1600x1200" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1600x1200" deleted (vrefresh out of range)
          (WW) r128(0): Mode "1600x1200" deleted (hsync out of range)
          (WW) r128(0): Mode "1600x1200" deleted (hsync out of range)
          (WW) r128(0): Mode "1792x1344" deleted (bad mode
          clock/interlace/doublescan)
          (WW) r128(0): Mode "1856x1392" deleted (bad mode
          clock/interlace/doublescan)
          (WW) r128(0): Mode "1920x1440" deleted (bad mode
          clock/interlace/doublescan)
          (--) r128(0): Virtual size is 1600x1200 (pitch 1600)
          (**) r128(0): Default mode "1600x1200": 162.0 MHz, 75.0 kHz, 60.0 Hz
          (==) r128(0): DPI set to (75, 75)
          (II) Loading /lib/modules/libfb.a
          (II) Module fb: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (II) Loading /lib/modules/libramdac.a
          (II) Module ramdac: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 0.1.0
          (II) Loading /lib/modules/libxaa.a
          (II) Module xaa: vendor="The XFree86 Project"
          compiled for 4.0.1c, module version = 1.0.0
          (**) r128(0): CCE in BM mode
          (**) r128(0): Using 8 MB AGP aperture
          (**) r128(0): Using 1 MB for the ring buffer
          (**) r128(0): Using 1 MB for vertex buffers
          (**) r128(0): Using 1 MB for indirect buffers
          (**) r128(0): Using 5 MB for AGP textures
          (**) r128(0): Using 16384 byte vertex buffers
          (==) r128(0): Write-combining range (0xf8000000,0x1000000)
          (0): [drm] created "r128" driver at busid "PCI:1:0:0"
          (0): [drm] added 4096 byte SAREA at 0xc3dce000
          (0): [drm] mapped SAREA 0xc3dce000 to 0x40018000
          (0): [drm] framebuffer handle = 0xf8000000
          (0): [drm] added 1 reserved context for kernel
          (II) r128(0): [agp] Mode 0x1f000203 [AGP 0x8086/0x7190; Card
          0x1002/0x4c46]
          (II) r128(0): [agp] 8192 kB allocated with handle 0xc907f000
          (II) r128(0): [agp] ring handle = 0xe0000000
          (II) r128(0): [agp] Ring mapped at 0x4120a000
          (II) r128(0): [agp] ring read ptr handle = 0xe0101000
          (II) r128(0): [agp] Ring read ptr mapped at 0x40019000
          (II) r128(0): [agp] vertex buffers handle = 0xe0102000
          (II) r128(0): [agp] Vertex buffers mapped at 0x4130b000
          (II) r128(0): [agp] indirect buffers handle = 0xe0202000
          (II) r128(0): [agp] Indirect buffers mapped at 0x4140b000
          (II) r128(0): [agp] AGP texture map handle = 0xe0302000
          (II) r128(0): [agp] AGP Texture map mapped at 0x4150b000
          (II) r128(0): [drm] register handle = 0xf4100000
          (II) r128(0): [drm] Added 64 16384 byte vertex buffers
          (II) r128(0): [drm] Mapped 64 vertex buffers
          (II) r128(0): Visual configs initialized
          (II) r128(0): Memory manager initialized to (0,0) (1600,5242)
          (II) r128(0): Reserved area from (0,1200) to (1600,1202)
          (II) r128(0): Largest offscreen area available: 1600 x 4040
          (II) r128(0): Reserved back buffer from (0,1202) to (1600,2402)
          (II) r128(0): Reserved depth buffer from (0,2402) to (1600,3602)
          (EE) r128(0): Unable to reserve texture space in frame buffer
          (==) r128(0): Backing store disabled
          (II) r128(0): Using XFree86 Acceleration Architecture (XAA)
          Screen to screen bit blits
          Solid filled rectangles
          8x8 mono pattern filled rectangles
          Indirect CPU to Screen color expansion
          Solid Lines
          Dashed Lines
          Offscreen Pixmaps
          Setting up tile and stipple cache:
          32 128x128 slots
          12 256x256 slots
          4 512x512 slots
          (II) r128(0): Acceleration enabled
          (II) r128(0): Using hardware cursor (scanline 7204)
          (II) r128(0): Largest offscreen area available: 1600 x 1639
          (II) r128(0): 0xf4100000 524288
          (0): X context handle = 0x00000002
          (0): [drm] installed DRM signal handler
          (0): [DRI] installation complete
          (II) r128(0): Direct rendering enabled
          (**) Mouse0: Protocol: "PS/2"
          (**) Mouse0: Core Pointer
          (==) Mouse0: Buttons: 3
          (**) Mouse0: ZAxisMapping: buttons 4 and 5
          (II) Keyboard "Keyboard0" handled by legacy driver
          (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
          Could not init font path element unix/:7100, removing from list!

          Fatal server error:
          could not open default font 'fixed'

          When reporting a problem related to a server crash, please send
          the full server output, not just the last messages.
          This can be found in the log file "/var/log/XFree86.0.log".
          Please reports problems to xfree86@....

          X connection to :0.0 broken (explicit kill or server shutdown).

          ================= END X.ERR FILE ===================================
          my XF86Config-4 file from *setup* is:

          ================= BEGIN XF86Config-4 FILE ==========================
          # XFree86 4.0 configuration generated by Xconfigurator

          Section "ServerLayout"
          Identifier "XFree86 Configured"
          Screen 0 "Screen0" 0 0
          InputDevice "Mouse0" "CorePointer"
          InputDevice "Keyboard0" "CoreKeyboard"
          EndSection

          # By default, Red Hat Linux 6.0 and later use xfs

          Section "Files"
          FontPath "unix/:7100"
          EndSection

          # This loads all the modules...

          Section "Module"
          Load "GLcore"
          Load "dbe"
          Load "dri"
          Load "extmod"
          Load "glx"
          Load "pex5"
          Load "record"
          Load "xie"
          Load "v4l"
          EndSection

          Section "InputDevice"
          Identifier "Keyboard0"
          Driver "keyboard"
          Option "XkbLayout" "us"
          EndSection

          Section "InputDevice"
          Identifier "Mouse0"
          Driver "mouse"
          Option "Device" "/dev/mouse"
          Option "Protocol" "PS/2"
          Option "Emulate3Buttons" "off"
          Option "ZAxisMapping" "4 5"
          EndSection

          Section "Monitor"
          Identifier "CustomConfiguration"
          VendorName "Unknown"
          ModelName "Unknown"
          HorizSync 28-90
          VertRefresh 50-62
          EndSection

          Section "Device"
          Identifier "ATI|Rage Mobility M3 AGP 2x"
          Driver "r128"
          BoardName "Unknown"
          EndSection

          Section "Screen"
          Identifier "Screen0"
          Device "ATI|Rage Mobility M3 AGP 2x"
          Monitor "CustomConfiguration"
          DefaultDepth 16
          Subsection "Display"
          Depth 16
          Modes "1600x1200"
          EndSubSection
          EndSection

          Section "DRI"
          EndSection

          ======================= END XF86Config-4 file ======================

          Please tell me what's going wrong here? I have read that redhat 7
          should aslo work with x4.0.1c but not even once X started :( Looks
          like XConfigurator is finding a different driver? ATI|Rage Mobility
          M3 ??

          Question 2:
          ===========

          I just got my debian 2.2 cd's from Cheapbytes as you mentioned!!!.I
          am excited!! I have never used DEBIAN, but I want to since I want to
          learn how things work. I am not satisfied with redhat(with my limited
          experiance).

          Now from your website, I see
          You installed POTATO first(I believe 2.2 stable version is potato and
          the latest version is WOODY?) and I have the existing partition which
          I am planning to use(2GB for windoze and rest for LINUX ~8GB). I
          believe the CD ROMS contain X 3.3.x which ain't gonna help me.
          I have XIRCOM ETHERNET CARDBUS 10/100 with (tulip driver) the
          internal modem, I ain't sure if I need to get another ethernet card
          with DEBIAN? rh7.0 supported xircom card.

          I understand that you then connected to your LUG @Brookhaven NL and
          installed x4.0.1c (clarify please??) and then things worked for you.
          Things look scary with DEBIAN :( I can't wait to get it running, I
          have waited so long(I am a fizzicks student and have other research
          work to do and I am trying my late night conversations with LINUX
          GODS here!)to get things working(1600x1200).. please advice. Well, my
          question here is after I install just the kernel and the ethernet
          (assuming XIRCOM 32bit ethernet cardbus 10/100 is supported) I can
          safely go ahead and do the stuff laid out by you? I should add I
          haven't even seen a slackware distro! Just so you know.
          THANKS MUCH FOR YOUR PATIENCE AND TIME. I REALLY APPRECIATE IT MUCH.
          Sincerely,
          rvk

          "It is a good morning exercise for a research scientist to discard a
          pet hypothesis every day before breakfast. It keeps him young."
          -- Konrad Lorenz


          --- In linux-dell-laptops@egroups.com, Brett Viren <bv@b...> wrote:
          >
          > The latest stable Debian (``potato'') installs very easy. You can
          > look at my page if you want to go this route:
          >
          > http://minos.phy.bnl.gov/~bviren/inspiron/
          >
          > If you install Debian, I would suggest you order a CD
          > (www.cheapbytes.com usually has them for a couple bucks) as it will
          be
          > much easier than following what I did to the letter.
          >
          > I don't want to start talking too much about pros and cons of
          > different distributions as it always starts a flame fest, but I will
          > give you smoe personal *opinions*. Since I started using Debian 5
          > years ago after switching from Slackware, I have been extreamly
          > impressed with how tight and smooth the system is and each release
          > just gets better. I have dabled in Red Hat a little (mostly dealing
          > with friends who's systems have fallen apart) and I have not been
          very
          > impressed with what I saw. However, I don't recommend newbies to
          jump
          > into Debian unless they are interested in how things really work in
          > the system. They have to want to learn some things and be able to
          > troll through mailing lists and FAQs for info from time to time.
          >
          > One thing I am sure about is in the time you have spent so far you
          > could have installed Debian and had a working system.
          >
          > -Brett.
        • Brett Viren
          ... This is telling X to use a local ``unix socket on port 7100 in order to talk to a font server. You are evidently not running a font server on this port.
          Message 4 of 10 , Nov 15, 2000
          • 0 Attachment
            thoroughbredinjun@... writes:
            > Ok, problem #1 (questions galore!)

            As you guessed, I think your problem is stated here:

            > =============BEGIN X.ERR FILE===================================
            > Could not init font path element unix/:7100, removing from list!
            ...
            > Fatal server error:
            > could not open default font 'fixed'

            and the reason is here:

            > ================= BEGIN XF86Config-4 FILE ==========================
            > # XFree86 4.0 configuration generated by Xconfigurator
            ...
            > Section "Files"
            > FontPath "unix/:7100"
            > EndSection

            This is telling X to use a local ``unix'' socket on port 7100 in order
            to talk to a font server. You are evidently not running a font server
            on this port. A more standard/full entry would look something like:

            Section "Files"
            # FontPath "/usr/X11R6/lib/X11/fonts/local/"
            FontPath "/usr/X11R6/lib/X11/fonts/misc/"
            # FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
            FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
            FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
            FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
            # FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
            FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
            # FontPath "unix/:7101"
            EndSection

            The ``fixed'' font (which is the default fall back font for X) is
            typically in /usr/X11R6/lib/X11/fonts/misc/.

            Here is a FAQ from Debian's xfree86-common package,
            (in /usr/share/doc/xfree86-common/FAQ.gz), it is a little Debian
            specific but it does explain a lot. I think just adding the
            FontPath's above should do it for you.

            ==========================================================================
            *) How do I get the X server to find the "fixed" font?

            If the X server refuses to start, complaining that it cannot find the
            "fixed" font, then one (or more) of the following is likely true:

            + You don't have the xfonts-base package installed. Install it.

            + You don't have a valid FontPath in your /etc/X11/XF86Config file. At
            the very minimum, your FontPath should look something like this:

            FontPath "/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/75dpi/,/usr/lib/X11/fonts/100dpi/"

            You will likely have several more directories listed. The "fixed" font
            is in the "misc" directory.

            + The fonts.dir or fonts.alias files in /usr/lib/X11/fonts/misc directory
            have been corrupted or are not present. This could be caused by a
            broken package which unpacks one or both of these files onto the
            system. A reinstallation of xfonts-base should fix the problem.

            + You're using a font server (either local or remote), and it is not
            running or not reachable.

            Note that Debian ships the xfs package with TCP listening turned off by
            default for security reasons. If you are running xfs locally and do
            not need to serve fonts to remote machines, you don't need to turn TCP
            listening back on. Instead, try a FontPath entry like this:

            FontPath "unix/:7100"

            If you are using a remote font server, determine whether or not it is
            running, is listening on the TCP port, and/or engage in some network
            troubleshooting.
            ==========================================================================

            > Question 2:
            > ===========
            >
            > I just got my debian 2.2 cd's from Cheapbytes as you mentioned!!!.I
            > am excited!! I have never used DEBIAN, but I want to since I want to
            > learn how things work. I am not satisfied with redhat(with my limited
            > experiance).
            >
            > Now from your website, I see
            > You installed POTATO first(I believe 2.2 stable version is potato and
            > the latest version is WOODY?) and I have the existing partition which

            Yes. I had some old Potato boot-floopies laying around, so I just
            installed via them first. Debian is so easy to upgrade (assuming a
            good net connection) that there was no real drawback to doing it this
            way. The time to make new Woody floopies or burn/buy a Woody CD is
            probably same or more than to just upgrade.

            > I am planning to use(2GB for windoze and rest for LINUX ~8GB). I
            > believe the CD ROMS contain X 3.3.x which ain't gonna help me.

            It's okay. You won't have X working in potato, but once you upgrade
            to Woody, in particular Woody's X, things should be okay. Last week
            all the Debian ``X Strike force'' packages went in to Woody proper, so
            you don't/shouldn't get them from the strike force. You may even be
            able to upgrade only X (and dependencies) while keeping mostly a
            Potato distribution. This is a common thing for Debian users to do
            and usually (but not always!) works just fine. Doing something like:

            edit /etc/apt/sources.list and add Woody lines
            apt-get update
            apt-get install xlibs

            will probably be enough to do the needed upgrade.

            > I have XIRCOM ETHERNET CARDBUS 10/100 with (tulip driver) the
            > internal modem, I ain't sure if I need to get another ethernet card
            > with DEBIAN? rh7.0 supported xircom card.

            Debian uses the same PCMCIA stuff that all the distributions use, so
            if it works on others you won't have problems with Debian. The only
            possible gotchya is if this is a very new card and the version of
            PCMCIA in Potato doesn't have support. Potato has PCMCIA 3.1.20 and
            woody 3.1.22. You might want to check to make sure your card is
            supported with these releases (my guess is it is).

            [ BTW, Debian's package browser is very usefull:

            http://www.debian.org/distrib/packages
            ]

            > I understand that you then connected to your LUG @Brookhaven NL and
            > installed x4.0.1c (clarify please??) and then things worked for you.

            Yes. It just so happens that here at BNL we are lucky to have one of
            the major Debian mirrors on site. FAST! When I updated directly from
            Debian or other offsite mirror it is still reasonably quick.

            > Things look scary with DEBIAN :( I can't wait to get it running, I
            > have waited so long(I am a fizzicks student and have other research
            > work to do and I am trying my late night conversations with LINUX
            > GODS here!)to get things working(1600x1200).. please advice.

            With Debian you will need to learn a bit more how things really work
            in order to use it more efficiently, but once learned, you will find
            that you are less and less stymied by ``magical'' things going wrong.
            When things go wrong, you will know exactly why, or at least where to
            start looking for the problem. This is one of the big problems (imo)
            about GUI based distributions. It makes sense to build a distribution
            like RH for (said lovingly) the clueless masses. However, it is
            nothing but annoying for people who don't mind going that extra step
            up the learning curve.

            > Well, my
            > question here is after I install just the kernel and the ethernet
            > (assuming XIRCOM 32bit ethernet cardbus 10/100 is supported) I can
            > safely go ahead and do the stuff laid out by you?

            I don't see why not. Also, look over Jeff Lessem's page for more
            info on Debian + 5000e. There is a link at the end of mine.

            > I should add I
            > haven't even seen a slackware distro! Just so you know.

            Amazingly, Slackware is still around and going strong. It is for
            folks that want to do *everything* themselves. Debian is a nice
            balance between this and RedHat's goal of doing everything (sometimes
            not so well) for you. Debian lets one get on with their own work
            (once it is learned!).


            -Brett.
          • thoroughbredinjun@hotmail.com
            Hi Brett, I tried as per your advice, but sith some changes. I am gonna go back and follow your page ditto! Here is what I did. 1. I have Debian 2.2 cdroms.
            Message 5 of 10 , Nov 16, 2000
            • 0 Attachment
              Hi Brett,
              I tried as per your advice, but sith some changes. I am gonna go back
              and follow your page ditto! Here is what I did.
              1. I have Debian 2.2 cdroms. Booted from them, made partitions and
              configured network etc(xircom driver is supported, but didn't work, I
              can't remember the error, but something like *iotcl: not supported* or
              something. PING etc didn't work either. Then I borrowed 3com fromt he
              person who was helping me install debian(hardcore debian like you!)
              and we installed the kernel and diverting fromt he path we didn't
              install potato and instead tried woody straightaway over the network
              from local mirror here.
              2. We installed the x4.0.1e after that
              3. Finally
              a) we tried with the old stable kernel from potato and tried changing
              the modelines and started X, thick band appeared towards the right of
              the screen and same with 1024x768 :(
              b) then we grabbed kernel 2.4test10 and installed it and overwrote
              XF86Config file with yours and tried running X again, same result.

              My question is as I understand from this, since basically we have same
              configuration and mine didnt work might be because I tried installing
              a base system (WOODY) which is unstable where as you had base potato
              and just grabbed X4.0.1c? Now, would this be because I am doing this
              with x4.0.1e?
              My system is r128 mobility with 15.1"SXGA monitor capable of
              1600x1200. 5000e with 10Gig HD, p3 Coopermine 700MHz & dualboot with
              windoze.
              I appreciate your help very much and the education! I have I think one
              thing left to do, go back and reinstall from the Debian 2.2 everything
              except X and then just grab x-4.0.1e (or how do I get c? or I can try
              my own X by brewing it, have the sources already!) and overwrite with
              your XF86Config file and driver from Jeff and see if it works
              Physics has taken a backstage, I have to get this work at any cost
              since only then I have peace of mind and copy my programs to laptop(
              once I have a system I am happy with). Again, my heartfelt thanks.
              sincerely,
              rvk
            • Brett Viren
              ... From Debian packages, right? This is also what I currently run. ... Hmm. Well, one thing I would suggest is remove any modelines from you XF86Config-4
              Message 6 of 10 , Nov 16, 2000
              • 0 Attachment
                thoroughbredinjun@... writes:
                > 2. We installed the x4.0.1e after that

                From Debian packages, right? This is also what I currently run.

                > 3. Finally
                > a) we tried with the old stable kernel from potato and tried changing
                > the modelines and started X, thick band appeared towards the right of
                > the screen and same with 1024x768 :(

                Hmm. Well, one thing I would suggest is remove any modelines from you
                XF86Config-4 file. I don't have *any* listed, they are aparently
                auto-generated. It is possible that you are specifying one that is
                not off enough to be rejected, but is off enough to not quite run
                correctly (this is a guess).

                What color depth are you using?

                Try:

                startx -- -depth 16
                and
                startx -- -depth 24

                Also try differenct resolutions. You can do this after X starts by
                using Ctrl-Alt-+ (with NumLock turned on).

                > b) then we grabbed kernel 2.4test10 and installed it and overwrote
                > XF86Config file with yours and tried running X again, same result.

                Hmm, this is odd....

                Are you sure that you saved it as /etc/X11/XF86Config-4 ? The `-4'
                version will take precedence over the non-4 version. If you had a
                pre-existing `-4' version but saved my file with out `-4' you won't
                really be getting it.

                BTW, the XF86Config-4 that is generated durring the install (by
                Debian's `dexter' app) also worked for me.

                Send the output of `startx' and maybe I or others can spot a problem.

                > My question is as I understand from this, since basically we have same
                > configuration and mine didnt work might be because I tried installing
                > a base system (WOODY) which is unstable where as you had base potato
                > and just grabbed X4.0.1c? Now, would this be because I am doing this
                > with x4.0.1e?

                No, don't worry about this. Installing directly from Woody as soon as
                you get the base system up, shouldn't be a problem. The Debian
                package system is amazingly good at taking care of problems. (The
                only thing one must be wary of is every once in a while there is a bug
                in unstable (now woody) which screws things up temporarily. Checking
                www.debianplanet.org is a good idea as they tend to give warnings
                about unstable being really unstable.)

                I usually upgrade my system a few times a week to whatever the latest
                Woody is. So, as I said above, I am also useing x4.0.1e now. But
                things were working fine with `c' and `d' as well.

                > My system is r128 mobility with 15.1"SXGA monitor capable of
                > 1600x1200. 5000e with 10Gig HD, p3 Coopermine 700MHz & dualboot with
                > windoze.

                This is conflicting. Is the LCD SXGA or UXGA? I don't think it
                matters, except you won't be able to run modes > SXGA if you don't
                have UXGA. I believe that the r128 X module will filter out modes you
                can't reach, so it shouldn't be a prob.

                > I appreciate your help very much and the education! I have I think one
                > thing left to do, go back and reinstall from the Debian 2.2 everything
                > except X and then just grab x-4.0.1e (or how do I get c? or I can try
                > my own X by brewing it, have the sources already!) and overwrite with

                Don't bother doing this. In general, you will be better off with as
                recent of woody as possible (modulo that once in a while package
                bugs). As for `c' vs `d' vs `e', it just gets better!

                > your XF86Config file and driver from Jeff and see if it works

                The driver in Debian's (woody) package will likely be more up to date,
                unless Jeff is updating the one on his page. There seems to be a new
                lettered version every couple weeks or so and I don't think Jeff has
                updated his page this recently.

                > Physics has taken a backstage, I have to get this work at any cost
                > since only then I have peace of mind and copy my programs to laptop(
                > once I have a system I am happy with).

                Heh, I know how you feel! Playing with Linux added a lot of time (I
                won't say how much!) to getting my PhD. But it is a very enjoyable
                diversion. In the end, you will be the ``expert'' that people go to
                for help, and if it interests you enough, this expertise can lead you
                to great success as more and more Physics needs expertise in Unix and
                programming to get the results.

                -Brett.
              Your message has been successfully submitted and would be delivered to recipients shortly.