README.sb1000 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207
  1. sb1000 is a module network device driver for the General Instrument (also known
  2. as NextLevel) SURFboard1000 internal cable modem board. This is an ISA card
  3. which is used by a number of cable TV companies to provide cable modem access.
  4. It's a one-way downstream-only cable modem, meaning that your upstream net link
  5. is provided by your regular phone modem.
  6. This driver was written by Franco Venturi <fventuri@mediaone.net>. He deserves
  7. a great deal of thanks for this wonderful piece of code!
  8. -----------------------------------------------------------------------------
  9. Support for this device is now a part of the standard Linux kernel. The
  10. driver source code file is drivers/net/sb1000.c. In addition to this
  11. you will need:
  12. 1.) The "cmconfig" program. This is a utility which supplements "ifconfig"
  13. to configure the cable modem and network interface (usually called "cm0");
  14. and
  15. 2.) Several PPP scripts which live in /etc/ppp to make connecting via your
  16. cable modem easy.
  17. These utilities can be obtained from:
  18. http://www.jacksonville.net/~fventuri/
  19. in Franco's original source code distribution .tar.gz file. Support for
  20. the sb1000 driver can be found at:
  21. http://web.archive.org/web/*/http://home.adelphia.net/~siglercm/sb1000.html
  22. http://web.archive.org/web/*/http://linuxpower.cx/~cable/
  23. along with these utilities.
  24. 3.) The standard isapnp tools. These are necessary to configure your SB1000
  25. card at boot time (or afterwards by hand) since it's a PnP card.
  26. If you don't have these installed as a standard part of your Linux
  27. distribution, you can find them at:
  28. http://www.roestock.demon.co.uk/isapnptools/
  29. or check your Linux distribution binary CD or their web site. For help with
  30. isapnp, pnpdump, or /etc/isapnp.conf, go to:
  31. http://www.roestock.demon.co.uk/isapnptools/isapnpfaq.html
  32. -----------------------------------------------------------------------------
  33. To make the SB1000 card work, follow these steps:
  34. 1.) Run `make config', or `make menuconfig', or `make xconfig', whichever
  35. you prefer, in the top kernel tree directory to set up your kernel
  36. configuration. Make sure to say "Y" to "Prompt for development drivers"
  37. and to say "M" to the sb1000 driver. Also say "Y" or "M" to all the standard
  38. networking questions to get TCP/IP and PPP networking support.
  39. 2.) *BEFORE* you build the kernel, edit drivers/net/sb1000.c. Make sure
  40. to redefine the value of READ_DATA_PORT to match the I/O address used
  41. by isapnp to access your PnP cards. This is the value of READPORT in
  42. /etc/isapnp.conf or given by the output of pnpdump.
  43. 3.) Build and install the kernel and modules as usual.
  44. 4.) Boot your new kernel following the usual procedures.
  45. 5.) Set up to configure the new SB1000 PnP card by capturing the output
  46. of "pnpdump" to a file and editing this file to set the correct I/O ports,
  47. IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
  48. conflict with one another. Then test this configuration by running the
  49. "isapnp" command with your new config file as the input. Check for
  50. errors and fix as necessary. (As an aside, I use I/O ports 0x110 and
  51. 0x310 and IRQ 11 for my SB1000 card and these work well for me. YMMV.)
  52. Then save the finished config file as /etc/isapnp.conf for proper configuration
  53. on subsequent reboots.
  54. 6.) Download the original file sb1000-1.1.2.tar.gz from Franco's site or one of
  55. the others referenced above. As root, unpack it into a temporary directory and
  56. do a `make cmconfig' and then `install -c cmconfig /usr/local/sbin'. Don't do
  57. `make install' because it expects to find all the utilities built and ready for
  58. installation, not just cmconfig.
  59. 7.) As root, copy all the files under the ppp/ subdirectory in Franco's
  60. tar file into /etc/ppp, being careful not to overwrite any files that are
  61. already in there. Then modify ppp@gi-on to set the correct login name,
  62. phone number, and frequency for the cable modem. Also edit pap-secrets
  63. to specify your login name and password and any site-specific information
  64. you need.
  65. 8.) Be sure to modify /etc/ppp/firewall to use ipchains instead of
  66. the older ipfwadm commands from the 2.0.x kernels. There's a neat utility to
  67. convert ipfwadm commands to ipchains commands:
  68. http://users.dhp.com/~whisper/ipfwadm2ipchains/
  69. You may also wish to modify the firewall script to implement a different
  70. firewalling scheme.
  71. 9.) Start the PPP connection via the script /etc/ppp/ppp@gi-on. You must be
  72. root to do this. It's better to use a utility like sudo to execute
  73. frequently used commands like this with root permissions if possible. If you
  74. connect successfully the cable modem interface will come up and you'll see a
  75. driver message like this at the console:
  76. cm0: sb1000 at (0x110,0x310), csn 1, S/N 0x2a0d16d8, IRQ 11.
  77. sb1000.c:v1.1.2 6/01/98 (fventuri@mediaone.net)
  78. The "ifconfig" command should show two new interfaces, ppp0 and cm0.
  79. The command "cmconfig cm0" will give you information about the cable modem
  80. interface.
  81. 10.) Try pinging a site via `ping -c 5 www.yahoo.com', for example. You should
  82. see packets received.
  83. 11.) If you can't get site names (like www.yahoo.com) to resolve into
  84. IP addresses (like 204.71.200.67), be sure your /etc/resolv.conf file
  85. has no syntax errors and has the right nameserver IP addresses in it.
  86. If this doesn't help, try something like `ping -c 5 204.71.200.67' to
  87. see if the networking is running but the DNS resolution is where the
  88. problem lies.
  89. 12.) If you still have problems, go to the support web sites mentioned above
  90. and read the information and documentation there.
  91. -----------------------------------------------------------------------------
  92. Common problems:
  93. 1.) Packets go out on the ppp0 interface but don't come back on the cm0
  94. interface. It looks like I'm connected but I can't even ping any
  95. numerical IP addresses. (This happens predominantly on Debian systems due
  96. to a default boot-time configuration script.)
  97. Solution -- As root `echo 0 > /proc/sys/net/ipv4/conf/cm0/rp_filter' so it
  98. can share the same IP address as the ppp0 interface. Note that this
  99. command should probably be added to the /etc/ppp/cablemodem script
  100. *right*between* the "/sbin/ifconfig" and "/sbin/cmconfig" commands.
  101. You may need to do this to /proc/sys/net/ipv4/conf/ppp0/rp_filter as well.
  102. If you do this to /proc/sys/net/ipv4/conf/default/rp_filter on each reboot
  103. (in rc.local or some such) then any interfaces can share the same IP
  104. addresses.
  105. 2.) I get "unresolved symbol" error messages on executing `insmod sb1000.o'.
  106. Solution -- You probably have a non-matching kernel source tree and
  107. /usr/include/linux and /usr/include/asm header files. Make sure you
  108. install the correct versions of the header files in these two directories.
  109. Then rebuild and reinstall the kernel.
  110. 3.) When isapnp runs it reports an error, and my SB1000 card isn't working.
  111. Solution -- There's a problem with later versions of isapnp using the "(CHECK)"
  112. option in the lines that allocate the two I/O addresses for the SB1000 card.
  113. This first popped up on RH 6.0. Delete "(CHECK)" for the SB1000 I/O addresses.
  114. Make sure they don't conflict with any other pieces of hardware first! Then
  115. rerun isapnp and go from there.
  116. 4.) I can't execute the /etc/ppp/ppp@gi-on file.
  117. Solution -- As root do `chmod ug+x /etc/ppp/ppp@gi-on'.
  118. 5.) The firewall script isn't working (with 2.2.x and higher kernels).
  119. Solution -- Use the ipfwadm2ipchains script referenced above to convert the
  120. /etc/ppp/firewall script from the deprecated ipfwadm commands to ipchains.
  121. 6.) I'm getting *tons* of firewall deny messages in the /var/kern.log,
  122. /var/messages, and/or /var/syslog files, and they're filling up my /var
  123. partition!!!
  124. Solution -- First, tell your ISP that you're receiving DoS (Denial of Service)
  125. and/or portscanning (UDP connection attempts) attacks! Look over the deny
  126. messages to figure out what the attack is and where it's coming from. Next,
  127. edit /etc/ppp/cablemodem and make sure the ",nobroadcast" option is turned on
  128. to the "cmconfig" command (uncomment that line). If you're not receiving these
  129. denied packets on your broadcast interface (IP address xxx.yyy.zzz.255
  130. typically), then someone is attacking your machine in particular. Be careful
  131. out there....
  132. 7.) Everything seems to work fine but my computer locks up after a while
  133. (and typically during a lengthy download through the cable modem)!
  134. Solution -- You may need to add a short delay in the driver to 'slow down' the
  135. SURFboard because your PC might not be able to keep up with the transfer rate
  136. of the SB1000. To do this, it's probably best to download Franco's
  137. sb1000-1.1.2.tar.gz archive and build and install sb1000.o manually. You'll
  138. want to edit the 'Makefile' and look for the 'SB1000_DELAY'
  139. define. Uncomment those 'CFLAGS' lines (and comment out the default ones)
  140. and try setting the delay to something like 60 microseconds with:
  141. '-DSB1000_DELAY=60'. Then do `make' and as root `make install' and try
  142. it out. If it still doesn't work or you like playing with the driver, you may
  143. try other numbers. Remember though that the higher the delay, the slower the
  144. driver (which slows down the rest of the PC too when it is actively
  145. used). Thanks to Ed Daiga for this tip!
  146. -----------------------------------------------------------------------------
  147. Credits: This README came from Franco Venturi's original README file which is
  148. still supplied with his driver .tar.gz archive. I and all other sb1000 users
  149. owe Franco a tremendous "Thank you!" Additional thanks goes to Carl Patten
  150. and Ralph Bonnell who are now managing the Linux SB1000 web site, and to
  151. the SB1000 users who reported and helped debug the common problems listed
  152. above.
  153. Clemmitt Sigler
  154. csigler@vt.edu