brintos

brintos / linux-shallow public Read only

0
0
Text · 9.7 KiB · c8582ca Raw
223 lines · plain
1.. SPDX-License-Identifier: GPL-2.02 3===================4SB100 device driver5===================6 7sb1000 is a module network device driver for the General Instrument (also known8as NextLevel) SURFboard1000 internal cable modem board.  This is an ISA card9which is used by a number of cable TV companies to provide cable modem access.10It's a one-way downstream-only cable modem, meaning that your upstream net link11is provided by your regular phone modem.12 13This driver was written by Franco Venturi <fventuri@mediaone.net>.  He deserves14a great deal of thanks for this wonderful piece of code!15 16Needed tools17============18 19Support for this device is now a part of the standard Linux kernel.  The20driver source code file is drivers/net/sb1000.c.  In addition to this21you will need:22 231. The "cmconfig" program.  This is a utility which supplements "ifconfig"24   to configure the cable modem and network interface (usually called "cm0");25 262. Several PPP scripts which live in /etc/ppp to make connecting via your27   cable modem easy.28 29   These utilities can be obtained from:30 31      http://www.jacksonville.net/~fventuri/32 33   in Franco's original source code distribution .tar.gz file.  Support for34   the sb1000 driver can be found at:35 36      - http://web.archive.org/web/%2E/http://home.adelphia.net/~siglercm/sb1000.html37      - http://web.archive.org/web/%2E/http://linuxpower.cx/~cable/38 39   along with these utilities.40 413. The standard isapnp tools.  These are necessary to configure your SB100042   card at boot time (or afterwards by hand) since it's a PnP card.43 44   If you don't have these installed as a standard part of your Linux45   distribution, you can find them at:46 47      http://www.roestock.demon.co.uk/isapnptools/48 49   or check your Linux distribution binary CD or their web site.  For help with50   isapnp, pnpdump, or /etc/isapnp.conf, go to:51 52      http://www.roestock.demon.co.uk/isapnptools/isapnpfaq.html53 54Using the driver55================56 57To make the SB1000 card work, follow these steps:58 591. Run ``make config``, or ``make menuconfig``, or ``make xconfig``, whichever60   you prefer, in the top kernel tree directory to set up your kernel61   configuration.  Make sure to say "Y" to "Prompt for development drivers"62   and to say "M" to the sb1000 driver.  Also say "Y" or "M" to all the standard63   networking questions to get TCP/IP and PPP networking support.64 652. **BEFORE** you build the kernel, edit drivers/net/sb1000.c.  Make sure66   to redefine the value of READ_DATA_PORT to match the I/O address used67   by isapnp to access your PnP cards.  This is the value of READPORT in68   /etc/isapnp.conf or given by the output of pnpdump.69 703. Build and install the kernel and modules as usual.71 724. Boot your new kernel following the usual procedures.73 745. Set up to configure the new SB1000 PnP card by capturing the output75   of "pnpdump" to a file and editing this file to set the correct I/O ports,76   IRQ, and DMA settings for all your PnP cards.  Make sure none of the settings77   conflict with one another.  Then test this configuration by running the78   "isapnp" command with your new config file as the input.  Check for79   errors and fix as necessary.  (As an aside, I use I/O ports 0x110 and80   0x310 and IRQ 11 for my SB1000 card and these work well for me.  YMMV.)81   Then save the finished config file as /etc/isapnp.conf for proper82   configuration on subsequent reboots.83 846. Download the original file sb1000-1.1.2.tar.gz from Franco's site or one of85   the others referenced above.  As root, unpack it into a temporary directory86   and do a ``make cmconfig`` and then ``install -c cmconfig /usr/local/sbin``.87   Don't do ``make install`` because it expects to find all the utilities built88   and ready for installation, not just cmconfig.89 907. As root, copy all the files under the ppp/ subdirectory in Franco's91   tar file into /etc/ppp, being careful not to overwrite any files that are92   already in there.  Then modify ppp@gi-on to set the correct login name,93   phone number, and frequency for the cable modem.  Also edit pap-secrets94   to specify your login name and password and any site-specific information95   you need.96 978. Be sure to modify /etc/ppp/firewall to use ipchains instead of98   the older ipfwadm commands from the 2.0.x kernels.  There's a neat utility to99   convert ipfwadm commands to ipchains commands:100 101	http://users.dhp.com/~whisper/ipfwadm2ipchains/102 103   You may also wish to modify the firewall script to implement a different104   firewalling scheme.105 1069. Start the PPP connection via the script /etc/ppp/ppp@gi-on.  You must be107   root to do this.  It's better to use a utility like sudo to execute108   frequently used commands like this with root permissions if possible.  If you109   connect successfully the cable modem interface will come up and you'll see a110   driver message like this at the console::111 112	 cm0: sb1000 at (0x110,0x310), csn 1, S/N 0x2a0d16d8, IRQ 11.113	 sb1000.c:v1.1.2 6/01/98 (fventuri@mediaone.net)114 115   The "ifconfig" command should show two new interfaces, ppp0 and cm0.116 117   The command "cmconfig cm0" will give you information about the cable modem118   interface.119 12010. Try pinging a site via ``ping -c 5 www.yahoo.com``, for example.  You should121    see packets received.122 12311. If you can't get site names (like www.yahoo.com) to resolve into124    IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file125    has no syntax errors and has the right nameserver IP addresses in it.126    If this doesn't help, try something like ``ping -c 5 204.71.200.67`` to127    see if the networking is running but the DNS resolution is where the128    problem lies.129 13012. If you still have problems, go to the support web sites mentioned above131    and read the information and documentation there.132 133Common problems134===============135 1361. Packets go out on the ppp0 interface but don't come back on the cm0137   interface.  It looks like I'm connected but I can't even ping any138   numerical IP addresses.  (This happens predominantly on Debian systems due139   to a default boot-time configuration script.)140 141Solution142   As root ``echo 0 > /proc/sys/net/ipv4/conf/cm0/rp_filter`` so it143   can share the same IP address as the ppp0 interface.  Note that this144   command should probably be added to the /etc/ppp/cablemodem script145   *right*between* the "/sbin/ifconfig" and "/sbin/cmconfig" commands.146   You may need to do this to /proc/sys/net/ipv4/conf/ppp0/rp_filter as well.147   If you do this to /proc/sys/net/ipv4/conf/default/rp_filter on each reboot148   (in rc.local or some such) then any interfaces can share the same IP149   addresses.150 1512. I get "unresolved symbol" error messages on executing ``insmod sb1000.o``.152 153Solution154   You probably have a non-matching kernel source tree and155   /usr/include/linux and /usr/include/asm header files.  Make sure you156   install the correct versions of the header files in these two directories.157   Then rebuild and reinstall the kernel.158 1593. When isapnp runs it reports an error, and my SB1000 card isn't working.160 161Solution162   There's a problem with later versions of isapnp using the "(CHECK)"163   option in the lines that allocate the two I/O addresses for the SB1000 card.164   This first popped up on RH 6.0.  Delete "(CHECK)" for the SB1000 I/O addresses.165   Make sure they don't conflict with any other pieces of hardware first!  Then166   rerun isapnp and go from there.167 1684. I can't execute the /etc/ppp/ppp@gi-on file.169 170Solution171   As root do ``chmod ug+x /etc/ppp/ppp@gi-on``.172 1735. The firewall script isn't working (with 2.2.x and higher kernels).174 175Solution176   Use the ipfwadm2ipchains script referenced above to convert the177   /etc/ppp/firewall script from the deprecated ipfwadm commands to ipchains.178 1796. I'm getting *tons* of firewall deny messages in the /var/kern.log,180   /var/messages, and/or /var/syslog files, and they're filling up my /var181   partition!!!182 183Solution184   First, tell your ISP that you're receiving DoS (Denial of Service)185   and/or portscanning (UDP connection attempts) attacks!  Look over the deny186   messages to figure out what the attack is and where it's coming from.  Next,187   edit /etc/ppp/cablemodem and make sure the ",nobroadcast" option is turned on188   to the "cmconfig" command (uncomment that line).  If you're not receiving these189   denied packets on your broadcast interface (IP address xxx.yyy.zzz.255190   typically), then someone is attacking your machine in particular.  Be careful191   out there....192 1937. Everything seems to work fine but my computer locks up after a while194   (and typically during a lengthy download through the cable modem)!195 196Solution197   You may need to add a short delay in the driver to 'slow down' the198   SURFboard because your PC might not be able to keep up with the transfer rate199   of the SB1000. To do this, it's probably best to download Franco's200   sb1000-1.1.2.tar.gz archive and build and install sb1000.o manually.  You'll201   want to edit the 'Makefile' and look for the 'SB1000_DELAY'202   define.  Uncomment those 'CFLAGS' lines (and comment out the default ones)203   and try setting the delay to something like 60 microseconds with:204   '-DSB1000_DELAY=60'.  Then do ``make`` and as root ``make install`` and try205   it out.  If it still doesn't work or you like playing with the driver, you may206   try other numbers.  Remember though that the higher the delay, the slower the207   driver (which slows down the rest of the PC too when it is actively208   used). Thanks to Ed Daiga for this tip!209 210Credits211=======212 213This README came from Franco Venturi's original README file which is214still supplied with his driver .tar.gz archive.  I and all other sb1000 users215owe Franco a tremendous "Thank you!"  Additional thanks goes to Carl Patten216and Ralph Bonnell who are now managing the Linux SB1000 web site, and to217the SB1000 users who reported and helped debug the common problems listed218above.219 220 221					Clemmitt Sigler222					csigler@vt.edu223