Baslinux mailing list

[Sindi Keesan <keesan AT iamjlamb.com>]

On Sun, 9 May 2004 3aoo-cvfd AT dea.spamcon.org wrote:

> Sindi Keesan wrote:
> >
> > he threw in a UTP cable for free 
> 
> If it is a UTP cross-over cable, you will be able to use
> it to connect two network cards.  If it is a straight UTP,
> it will only work with a hub.

I have three UTP cables.  If I put the plugs next to each other, on the 
first two (from the rummage sale) they both look the same (grey orange 
black red....).

On the third one (yard sale, where he has more) they are mirror images.  
Is this crossover?


> > half of them being ISA, which the linux HOWTO said to avoid 
> > because you need to specify the base address and IRQ in 
> > modules.conf.  
> 
> That's not correct.  I use ISA network cards often:  insmod, 
> ifconfig, no worries.
> 
> > I presume I next plug them into the computer one at a time 
> > and read dmesg to find out what they are 
> 
> dmesg won't register them until *after* you insmod.
> 
> > and then look up the correct module somewhere in the HOWTO.  
> 
> IMHO the best way to figure out what module an old NIC uses
> is to boot the net.i kernel from Slackware.  It does a pretty
> good job of identifying NICs.  For ISA NICs, I use net.i from
> Slackware 3.2.  For PCI NICs, I use net.i from Slackware 7.1.

Many ways of doing this.  The HOWTO gave me 2 out of 3.  I hope SW71 has
all the modules I need because I think they are kernel specific and I
don't want to learn to compile a network module.  One of the cards (with
the BNC connector) takes ne/ne2k-pci which you included.  

> 
> When you boot the net.i (b)zimage, you don't need a filesystem.
> I think this command will be sufficient:  loadlin (b)zimage
> The kernel will crash when it fails to find a root, but it will 
> (probably) leave the NIC details on the screen (a few lines up 
> from the bottom).
>
> Cheers,
> Steven
>