API tools faq
paste
Advertisement
Guest User

Driver Readme

a guest
Aug 2nd, 2015
191
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.60 KB | None | 0 0
raw download clone embed print report
  1. Installation Notes
  2. Broadcom b44 Linux Driver
  3. Version 1.00g
  4. 06/07/2006
  5.  
  6. Broadcom Corporation
  7. 16215 Alton Parkway,
  8. Irvine, CA 92619-7013
  9.  
  10. Copyright (c) 2006 Broadcom Corporation
  11. All rights reserved
  12.  
  13.  
  14. Table of Contents
  15. =================
  16.  
  17. Introduction
  18. Limitations
  19. Packaging
  20. Installing Source RPM Package
  21. Building Driver From TAR File
  22. Driver Settings
  23. Driver Defaults
  24. Unloading and Removing Driver
  25. Driver Messages
  26.  
  27.  
  28. Introduction
  29. ============
  30.  
  31. This file describes the b44 Linux driver for the Broadcom 440x
  32. 10/100 Mbps PCI Network Controllers.
  33. The latest driver is in the latest 2.6 Linux kernel. It can also be
  34. downloaded from http://www.broadcom.com as a source package, but is
  35. generally not necessary to do so if you are using the latest 2.6
  36. upstream kernel from http://www.kernel.org or one of the latest
  37. vendor kernels from Red Hat, SuSE, or others.
  38.  
  39. The b44 driver from this Broadcom package is almost identical to the
  40. b44 driver in the latest 2.6 upstream Linux kernel. It includes some
  41. additional kernel compatible code to allow it to compile on older 2.6
  42. and some 2.4 kernels. The version number is also similar but generally
  43. has a one letter suffix at the end, (e.g. 1.00a) to distinguish it from
  44. the in-kernel b44 driver.
  45.  
  46. The next few sections on packaging, compiling, and installation apply
  47. to the Broadcom driver package only.
  48.  
  49.  
  50. Limitations
  51. ===========
  52.  
  53. The current version of the driver has been tested on 2.4.x kernels starting
  54. from 2.4.24 and all 2.6.x kernels. The driver may not compile on kernels
  55. older than 2.4.24. Testing is concentrated on i386 and x86_64 architectures.
  56. Only limited testing has been done on some other architectures such as
  57. powerpc and sparc64.
  58.  
  59. Minor changes to some source files and Makefile may be needed on some
  60. kernels.
  61.  
  62.  
  63. Packaging
  64. =========
  65.  
  66. To replace an older previously installed or in-kernel b44 driver, follow
  67. the instructions below.
  68.  
  69. The driver package from http://www.broadcom.com is released in two packaging
  70. formats: source RPM and compressed tar formats. The file names for the two
  71. packages are b44-<version>.src.rpm and b44-<version>.tar.gz.
  72. Identical source files to build the driver are included in both packages.
  73.  
  74.  
  75. Installing Source RPM Package
  76. =============================
  77.  
  78. The following are general guidelines for installing the driver.
  79.  
  80. 1. Install the source RPM package:
  81.  
  82. rpm -ivh b44-<version>.src.rpm
  83.  
  84. 2. CD to the RPM path and build the binary driver for your kernel:
  85.  
  86. cd /usr/src/{redhat,OpenLinux,turbo,packages,rpm ..}
  87.  
  88. rpm -bb SPECS/b44.spec
  89.  
  90. or
  91.  
  92. rpmbuild -bb SPECS/b44.spec (for RPM version 4.x.x)
  93.  
  94. Note that the RPM path is different for different Linux distributions.
  95.  
  96. 3. Install the newly built package (driver and man page):
  97.  
  98. rpm -ivh RPMS/<arch>/b44-<version>.<arch>.rpm
  99.  
  100. <arch> is the architecture of the machine, e.g. i386:
  101.  
  102. rpm -ivh RPMS/i386/b44-<version>.i386.rpm
  103.  
  104. Note that the --force option may be needed on some Linux distributions
  105. if conflicts are reported.
  106.  
  107. The driver will be installed in the following path:
  108.  
  109. 2.4.x kernels:
  110.  
  111. /lib/modules/<kernel_version>/kernel/drivers/net/b44.o
  112.  
  113. 2.6.x kernels:
  114.  
  115. /lib/modules/<kernel_version>/kernel/drivers/net/b44.ko
  116.  
  117. 4. Load the driver:
  118.  
  119. insmod b44.o
  120. or
  121. insmod b44.ko (on 2.6.x kernels)
  122. or
  123. modprobe b44
  124.  
  125. 5. To configure network protocol and address, refer to various Linux
  126. documentations.
  127.  
  128.  
  129. Building Driver From TAR File
  130. =============================
  131.  
  132. The following are general guidelines for installing the driver.
  133.  
  134. 1. Create a directory and extract the files:
  135.  
  136. tar xvzf b44-<version>.tar.gz
  137.  
  138. 2. Build the driver b44.o (or b44.ko) as a loadable module for the
  139. running kernel:
  140.  
  141. cd src
  142. make
  143.  
  144. 3. Test the driver by loading it:
  145.  
  146. insmod b44.o
  147. or
  148. insmod b44.ko (on 2.6.x kernels)
  149. or
  150. insmod b44
  151.  
  152. 4. Install the driver:
  153.  
  154. make install
  155.  
  156. See RPM instructions above for the location of the installed driver.
  157.  
  158. 5. To configure network protocol and address, refer to various Linux
  159. documentations.
  160.  
  161.  
  162. Driver Settings
  163. ===============
  164.  
  165. This and the rest of the sections below apply to both the in-kernel b44
  166. driver and the b44 driver package from Broadcom.
  167.  
  168. Driver settings can be queried and changed using ethtool. The latest ethtool
  169. can be downloaded from http://sourceforge.net/projects/gkernel if it is not
  170. already installed. The following are some common examples on how to use
  171. ethtool. See the ethtool man page for more information. ethtool settings do
  172. not persist across reboot or module reload. The ethtool commands can be put
  173. in a startup script such as /etc/rc.local to preserve the settings across a
  174. reboot.
  175.  
  176. 1. Show current speed, duplex, and link status:
  177.  
  178. ethtool eth0
  179.  
  180. 2. Change speed, duplex, autoneg:
  181.  
  182. Example: 100Mbps half duplex, no autonegotiation:
  183.  
  184. ethtool -s eth0 speed 100 duplex half autoneg off
  185.  
  186. Example: Autonegotiation with full advertisement:
  187.  
  188. ethtool -s eth0 autoneg on
  189.  
  190. Example: Autonegotiation with 100Mbps full duplex advertisement only:
  191.  
  192. ethtool -s eth0 speed 100 duplex full autoneg on
  193.  
  194. 3. Show flow control settings:
  195.  
  196. ethtool -a eth0
  197.  
  198. 4. Change flow control settings:
  199.  
  200. Example: Turn off flow control
  201.  
  202. ethtool -A eth0 autoneg off rx off tx off
  203.  
  204. Example: Turn flow control autonegotiation on with tx and rx advertisement:
  205.  
  206. ethtool -A eth0 autoneg on rx on tx on
  207.  
  208. Note that this is only valid if speed is set to autonegotiation.
  209.  
  210. 5. Get statistics:
  211.  
  212. ethtool -S eth0
  213.  
  214. 6. See ethtool man page for more options.
  215.  
  216.  
  217. Driver Defaults
  218. ===============
  219.  
  220. Speed : Autonegotiation with all speeds advertised
  221.  
  222. Flow control : Autonegotiation with rx and tx advertised
  223.  
  224. MTU : 1500 (range 46 - 1500)
  225.  
  226.  
  227. Unloading and Removing Driver
  228. =============================
  229.  
  230. To unload the driver, use ifconfig to bring down all eth# interfaces opened
  231. by the driver, then do the following:
  232.  
  233. rmmod b44
  234.  
  235. Note that on 2.6 kernels, it is not necessary to bring down the eth#
  236. interfaces before unloading the driver module.
  237.  
  238.  
  239. If the driver was installed using rpm, do the following to remove it:
  240.  
  241. rpm -e b44
  242.  
  243.  
  244. If the driver was installed using make install from the tar file, the driver
  245. b44.o (or b44.ko) has to be manually deleted from the system. Refer
  246. to the section "Installing Source RPM Package" for the location of the
  247. installed driver.
  248.  
  249.  
  250. Driver Messages
  251. ===============
  252.  
  253. The following are the most common sample messages that may be logged in the file
  254. /var/log/messages. Use dmesg -n <level> to control the level at which messages
  255. will appear on the console. Most systems are set to level 6 by default. To see
  256. all messages, set the level higher.
  257.  
  258. Driver signon:
  259. -------------
  260.  
  261. b44.c:v1.00b (Apr 20, 2006)
  262.  
  263.  
  264. NIC detected:
  265. ------------
  266.  
  267. Link up and speed indication:
  268. ----------------------------
  269.  
  270. b44: eth0: Link is up at 100 Mbps, full duplex.
  271. b44: eth0: Flow control is off for TX and on for RX.
  272.  
  273.  
  274. Link down indication:
  275. --------------------
  276.  
  277. b44: eth0: Link is down.
  278.  
  279.  
  280. b44 notes:
  281. ----------
  282. speed 10Mbs
  283. The link LED is also a speed LED and when the b44 is set to speed 10Mbs the
  284. link/speed LED will not illuminate. It only illuminates when speed is 100Mbs
  285. AND link is detected.
  286.  
  287. Tx Pause
  288. Tx pause frame generation is disabled by default. When it is enabled it may
  289. affect b44 performance.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!