public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Igor Gueths" <igueths@yahoo.com>
To: <speakup@braille.uwo.ca>
Subject: Re: file re-naming?
Date: Wed, 27 Feb 2002 18:37:42 -0500	[thread overview]
Message-ID: <001d01c1bfe7$c2a61760$02b05b18@mycomputer> (raw)
In-Reply-To: <20020227213707.GA602@kb5elv>

[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]

Hi Buddy. Thanks for the info. Well it seems that Linux commands are kind of different from Irix? Bc on irix, rn old filename new filename was the standard usage. Anyway, got a question. If anyone's already fed up with me then I'm sorry lol! Anyway, I have a page here that has installation and compiling instructions for the Linksys Network card driver (tulip.c). The only problem is, I don't know to what version of gcc this doc refers to. When I tried compiling the tulip module, I got all sorts of compilation errors. I am attaching the page in text form for reference. If anyone can try to compile the source file and/or tell me to what version the doc refers to, I would greatly apreciate it! I posted the driver a while back, but in case someone maybe lost it, I'll attach here with the page. Thanks in advance for any help! Also, if there is a problem with the encoding format please let me kno so I can change to uuencoding or something similar. Thanks again! 
----- Original Message ----- 
From: Buddy Brannan <davros@ycardz.com>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, February 27, 2002 4:37 PM
Subject: Re: file re-naming?


> Nope. ... rn is an old news reader.
> 
> Don't use rm, cause that'll delete the file.
> 
> The command for rename is mv.
> -- 
> Buddy Brannan, KB5ELV/3  | I choose you to take up all of my time.
> Email: davros@ycardz.com | I choose you because you're funny and kind
>                          | I want easy people from now on.
>                          | --the Nields
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

[-- Attachment #2: netcard.txt --]
[-- Type: text/plain, Size: 8925 bytes --]

Linksys: Support Pages 
       

                    
        
       
       Support Page For
                     LNE100TX LINUX



      You can find additional help in our Knowledge Base by clicking here.



      EtherFast 10/100 LAN Card Linux Support
      Installing Under RedHat 5.2 or 6.0 
      Installing Under Other Linux Distributions 
      If Your Distribution Supports Modules
      Recompile Kernel method
      Recompile Module method 
      If Your Distribution Doesn't Support Modules 
      Troubleshooting the Tulip Driver
      NOTE: If you have the new LNE100TX Version 2 with Wake On Lan Support, You 
      will need to use the driver provided on disk 2 in the linux directory. 


       Installing Under RedHat 5.2 or 6.0
      If you are using RedHat 5.2 or above, you don't need to follow the 
      directions below. Instead, follow the general OS and networking 
      installation directions that RedHat provides. When asked to supply the 
      name of the proper network driver during the RedHat installation, choose 
      the Tulip driver from the list of drivers that appears on your screen. 
      Continue with the installation as directed by RedHat, then configure your 
      networking. 

      **Note** If you have problems using the redhat driver, use the 
      instructions below to obtain and install a newer version of the driver. 
      also check the driver disk that came with the card, it may have a linux 
      driver on it. 

      Installing Under Other Linux Distributions
      The Linksys network card has been tested with Caldera, Debian, Slackware, 
      and SUSE distrubution versions of Linux. If your distribution of Linux 
      supports modules, you will find that the driver setup is relatively quick. 
      If your version of Linux does not support modules, you will need to 
      re-compile the Linux kernel with the proper driver for the Linksys network 
      card. Instructions for both of these methods are described below. 
      In order to complete the Linux setup, you'll need to be familiar with 
      basic Linux procedures and commands (mounting, compiling, etc.). If you 
      are unfamiliar with Linux, try visiting some of these sites for helpful 
      documentation:
        www.ora.com 
        www.kernel.org 
        www.linux.org 
        www.linuxmall.com 
        www.amazon.com 
        www.ssc.com 
        www.linuxhq.com 
      You can also find documentation at any of the major distribution sites for 
      Linux:
        www.redhat.com 
        www.caldera.com 
        www.debian.org 
        www.slackware.com 
        www.suse.com 
      To determine if your Linux distribution supports modules, start up your 
      machine, login as admin, and type the following: 
      cat /proc/modules 
      Your distribution supports modules if you don't receive any errors. If you 
      see one or more errors, then your distribution does not support modules, 
      and you will need to recompile the Linux kernel with the appropriate 
      Linksys network card driver. 


      If Your Distribution Supports Modules
      Make sure that you have the kernel source tree installed. Consult your 
      Linux documentation for further help if you need it.
      Linksys network cards use a driver called Tulip, which is stored in a file 
      called tulip.c. Although you will find this file on the disk that came 
      with your Linksys card, it is a good idea to download the latest copy of 
      the Tulip driver, since improvements are constantly being made. If you 
      choose to download a new copy of the driver, you will need to compile it.
      To download the latest version of the Tulip.c driver, go here.
      To download the latest test version of the driver, go here.
            If You Are Using a Windows Machine for Downloading
            If you download the latest version of the Tulip driver onto a 
            Windows computer, you will probably find that the driver will NOT 
            compile properly after you copy it to your Linux box, since Windows 
            and Linux use different linefeeding. To solve this problem, either 
            (1) download the driver using your Linux box, or (2) if you must 
            download it to a Windows machine, covert the driver to Linux format 
            with the DOS2UNIX program, which is freely available on most open 
            source sites on the Internet. 

      Next:
      You can compile and install the Tulip.c driver in one of two ways. If you 
      are familiar with modules, you can simply compile the driver as a module 
      and copy it to the proper location in your Linux system. If you aren't 
      familiar with modules, and don't mind waiting awhile for your Linux kernel 
      to recompile, you can recompile the entire kernel with the Tulip.c driver 
      inside. Both methods are described below. 
      Recompile Module Method
      Log in to your Linux box as root, admin, or super user.
      Obtain the Tulip.c driver from the Linksys disk, or by downloading the 
      latest version of it as described above.
      Compile the Tulip.c driver with the following command (type the entire 
      command on one line):
      gcc -DMODULE -D__KERNEL__ 
      -I/usr/src/linux/net/inet 
      -Wall -Wstrict-prototypes -O6 -c tulip.c
      `[ -f /usr/include/linux/modversions.h ]
      && echo -DMODVERSIONS` 
      If your system is using dual processors, compile the Tulip.c driver using 
      this command instead (type the entire command on one line):
      gcc -D__SMP__ -DMODULE -D__KERNEL__ 
      -I/usr/src/linux/net/inet 
      -Wall -Wstrict-prototypes -O6 -c tulip.c 
      `[ -f /usr/include/linux/modversions.h ] 
      && echo -DMODVERSIONS` 
      Next:
      mv /lib/modules/kernel_version/net/tulip.o /tmp 
      cp tulip.o /lib/modules/kernel_version/net 
      Next, issue the following commands as root:
      depmod -a 
      modprobe tulip.o 
      Check the /var/log/messages log file for errors. If there are no errors, 
      then the module is installed correctly. Issue the following command:
      rmmod tulip.o 
      Follow the instructions that came with your distribution to configure the 
      LAN card. If you are asked what module to use, chose Tulip. 
      Recompile Kernel Method
      Log in to your Linux box as root, admin, or super user.
      Obtain the Tulip.c driver from the Linksys disk, or by downloading the 
      latest version of it as described above. Move the old version of the 
      Tulip.c driver to safe location and copy the new version of the Tulip 
      driver over the old one:
      (the mv command below should be typed on one line, not two): 
      mv /usr/src/linux/drivers/net/tulip.c
      /usr/src/linux/drivers/net/tulip.old 
      cp tulip.c /usr/src/linux/drivers/net 
      Consult the documentation that came with your Linux distribution to 
      recompile the kernel. Be sure to reboot the system after recompiling. 


      If Your Distribution Doesn't Support Modules
      If your Linux kernel doesn't support modules, you'll need to recompile the 
      Tulip.c driver into the kernel. To do this:
      (the mv command below should be typed on one line, not two): 
      mv /usr/src/linux/drivers/net/tulip.c
      /usr/src/linux/drivers/net/tulip.old 
      cp tulip.c /usr/src/linux/drivers/net 
      Consult the documentation that came with your Linux distribution to 
      recompile the kernel. Be sure to reboot the system after recompiling. 
      After rebooting, follow the instructions that came with your distribution 
      to configure the LAN card. 


      Tulip Driver Troubleshooting
      If you encounter errors while the Tulip driver is loading, see if the 
      errors look similar to this:
      Kernel: Found Lite-On 82c168 PNIC at PCI I/O address 0x0.
      Initialization of tulip failed 
      Try doing a cat /proc/pci and see if a message similar to this appears:
      Bus 0, device 9, function 0:
      Ethernet controller: Lite-on LNE100TX (rev 32).
      Medium devsel. Fast back-to-back capable. 
      Master Capable. No bursts. I/O at 0x0.
      If you see these messages, your PC's BIOS is probably configured 
      incorrectly. Refer to your PC's motherboard documentation for help. 
       
      ©Copyright 2002 Linksys Group Inc. All Rights Reserved.
 Downloads User Guides FAQs Knowledge Base Product Close-Ups Tech Helper 
Technical Support Warranty Policy White Papers Windows XP Support Event Calendar 
Photo Library Press Releases Review & Awards Success Stories About Linksys 
Contact Linksys Job Opportunities Partners Privacy Policy Direct Response 
Distribution E-Commerce Retail International

[-- Attachment #3: Netdrv.tgz --]
[-- Type: application/x-compressed, Size: 40648 bytes --]

  reply	other threads:[~ UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Igor Gueths
 ` Gregory Nowak
   ` Richard Villa
     ` Igor Gueths
       ` Buddy Brannan
         ` Igor Gueths [this message]
           ` Alex Snow
             ` Igor Gueths
               ` Gregory Nowak
               ` Alex Snow
         ` Richard Villa
           ` Igor Gueths
             ` Richard Villa
               ` Igor Gueths
       ` Gregory Nowak
       ` Richard Villa
 ` Pete
   ` Ed Barnes
     ` Maurice A. Mines
     ` Igor Gueths
       ` Ed Barnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001d01c1bfe7$c2a61760$02b05b18@mycomputer' \
    --to=igueths@yahoo.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).