Lines Matching refs:you
10 and cabling information if you're like many of us and didn't happen to get a
22 The point is: I REALLY REALLY REALLY REALLY REALLY want to hear from you if
23 you test this and get it working. Or if you don't. Or anything.
36 If you don't e-mail me about your success/failure soon, I may be forced to
40 If you think so, why not flame me in a quick little e-mail? Please also
41 include the type of card(s) you're using, software, size of network, and
87 Also, SMC (one of the companies that makes ARCnet cards) has a WWW site you
102 one you'll want to use with ARCnet cards) from
105 versions are available on my WWW page, or via e-mail if you don't have WWW
112 All you will need to do in order to install the driver is::
120 If you obtained this ARCnet package as an upgrade to the ARCnet driver in
121 your current kernel, you will need to first copy arcnet.c over the one in
124 You will know the driver is installed properly if you get some ARCnet
125 messages when you reboot into the new Linux kernel.
131 This is the normal ARCnet card, which you've probably got. This is the only
137 If you load the chipset support as a module, the options are::
155 If you load the chipset support as a module, the options are::
160 The COM20020 chipset allows you to set the node ID in software, overriding the
161 default which is still set in DIP switches on the card. If you don't have the
162 COM20020 data sheets, and you don't know what the other three options refer
163 to, then they won't interest you - forget them.
169 you have a card which doesn't support shared memory, or (strangely) in case
170 you have so many ARCnet cards in your machine that you run out of shmem slots.
171 If you don't give the IO address on the kernel command line, then the driver
178 If you load the chipset support as a module, the options are:
184 these is not tested. If you have one, please mail the author with a success
190 If you load the chipset support as a module, the options are::
199 support" and to support for your ARCnet chipset if you want to use the
201 to the chipset support if you wish.
210 If you're using a loadable module, you need to use insmod to load it, and
211 you can specify various characteristics of your card on the command
226 If you build your kernel with ARCnet COM90xx support included, it should
227 probe for your card automatically when you boot. If you use a different
228 chipset driver complied into the kernel, you must give the necessary options
232 available where you picked up this driver. Think of your ARCnet as a
247 If you have other cards, with support compiled into the kernel, then you can
252 If you have the chipset support built as a loadable module, then you need to
266 Should be fine linux->linux, just pretend you're using Ethernet cards.
270 you never know what you might need.
272 With AmiTCP (and possibly others), you may need to set the following
279 you know more.
282 If you're using the freeware arcether.com, you might want to install
285 initialization. In fact, if you use it on a 386+ you REALLY need
290 Arcether client, assuming you remember to load winpkt of course.
301 Using the freeware Samba server and clients for Linux, you can now
306 Tools are included with Win95 that let you use either the LANMAN
308 ARCnet packets. If you use ODI, you'll need to use the 'arc0'
309 device with Linux. If you use NDIS, then try the 'arc0e' device.
310 See the "Multiprotocol Support" section below if you need arc0e,
311 you're completely insane, and/or you need to build some kind of
316 SMC. You need to use the 'arc0e' interface for this. If you get
344 Unless you have a specific need to use a different protocol,
345 I strongly suggest that you stick with this one.
367 possible that you may run into problems. It's also slower
374 You can choose not to compile arc0e and arc0s into the driver if you want -
375 this will save you a bit of memory and avoid confusion when eg. trying to
378 The arc0e and arc0s devices are created automatically when you first
379 ifconfig the arc0 device. To actually use them, though, you need to also
380 ifconfig the other virtual devices you need. There are a number of ways you
388 only arc0 unless you have a good reason (like some other software, ie.
391 If you need only arc0, then the following commands should get you going::
398 If you need arc0e (and only arc0e), it's a little different::
410 Now things start getting confusing. To even try it, you may need to be
452 to the Internet through freedom. If you didn't know how to do the above,
453 you should probably stop reading this section now because it only gets
534 way to me), so if you don't get a reply within a reasonable time, please
545 If you want to try fixing it yourself (I strongly recommend that you mail me
546 about the problem first, since it might already have been solved) you may
554 significantly. In particular, they won't tell you why the card was not
555 found unless you turn on the D_INIT_REASONS debugging flag.
557 Once the driver is running, you can run the arcdump shell script (available
558 from me or in the full ARCnet package, if you have it) as root to list the
560 this, you should grab the pertinent RFCs. (some are listed near the top of
567 If your debug level includes D_DURING and you did NOT define SLOW_XMIT_COPY,
569 reset (which should only happen when you do an ifconfig up, or when Linux
579 where "xxx" is the debug level you want. For example, "metric 1015" would put
580 you at debug level 15. Debug level 7 is currently the default.
584 D_NORMAL+D_EXTRA+D_INIT. To include D_DURING, you would add 16 to this,
587 If you don't understand that, you probably don't want to know anyway.