Re: [OT] Potato vs Realtek8029PCI NIC
Shao Zhang wrote: > > Hi, > sorry about the OT message. > While on the topic of realtek8029, I have got a pcmcia 8029 > ethernet card and it works perfectly under linux. > > But I can never get this card working under w2k :( > Anyone have any ideas? > > Shao. > Hmmm. I can't even get the damn ordinary PCI-version going under Win98... Sorry I can't help you! Regards Vitux -- "I'm not a crook" Richard Nixon Debian GNU/Linux Micro$loth-free Zone
Re: [OT] Potato vs Realtek8029PCI NIC
Hi, sorry about the OT message. While on the topic of realtek8029, I have got a pcmcia 8029 ethernet card and it works perfectly under linux. But I can never get this card working under w2k :( Anyone have any ideas? Shao. -- Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications/ __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED] |___/ _
Re: YEAH: Potato vs Realtek8029PCI NIC
John Pearson wrote:
>
> On Wed, Aug 23, 2000 at 11:53:18AM +0200, Vitux wrote
> > More stuff:
> > I did a
> > # modprobe ne2k-pci
> > and I get this:
> > ne2k-pci..: PCI NE2000 clone 'Realtek RTL-8029* at I/O 0x20a0, IRQ
> > 9.
> > eth0: RealTek RTL-8029 found at 0x20a0, IRQ 9, 00:00:B4:B8:94:CC
> > #
> > I suppose this means that the modular driver has been installed in
> > the kernel and detected my NIC. So far, great.
> >
> > Wonder why kmod won't autoload it when I do "ifconfig-yadayada up" ?
> > BTW: What does the hex-part at the end mean?
> >
>
> It has no reason to associate this driver with eth0; you need to
> give it a big hint as to which module to use for the interface.
> Try adding
>
> alias eth0 ne2k-pci
>
> to /etc/modutils/aliases and running update-modules as root.
>
> The hex string is your card's MAC, an allegedly unique
> identifier that is used for packet addressing at the physical
> link layer for machines on your local network. The first
> few octets probably identify the card's manufacturer, the rest
> are up to them.
>
> I say allegedly unique because some early clone NICs (back
> when a cheap name-brand NIC might be $300) had cloned firmware
> that gave each card the same MAC, or used ranges that
> had been assigned to other manufacturers; that meant if you used
> bad cards, you might have to sort out which ones couldn't
> share a network.
>
> MACs are associated with IPs using ARP ("Address Resolution
> Protocol"). You can monitor the MAC-to-IP translation on your
> network with something like this (assuming your network is
> 192.168.1.0/24):
>
> $ ping -c 2 192.168.1.255
> $ /usr/sbin/arp -a
>
> You won't see your own machine in the arp cache, because your
> TCP/IP stack recognizes packets addressed to itself and doesn't
> get as far as attempting ARP for local addresses.
>
> John P.
> --
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> http://www.mdt.net.au/~john Debian Linux admin & support:technical services
>
> --
I did the alias-thing, and the "ifconfig eth0 192.168.0.1 netmask
255.255.255.0 up". Now I can ping myself! all packets are returned
(of course), and it seems to be working.
Big Thanks, all you guys who helped me out.
Think I'm gonna write an addendum to the howto.
Now, to configure the same nic, only this time in a windoh's
box...(yuck)
Best Regards
Vitux
--
"I'm not a crook"
Richard Nixon
Debian GNU/Linux
Micro$loth-free Zone
Re: Potato vs Realtek8029PCI NIC
On Wed, Aug 23, 2000 at 11:53:18AM +0200, Vitux wrote
> More stuff:
> I did a
> # modprobe ne2k-pci
> and I get this:
> ne2k-pci..: PCI NE2000 clone 'Realtek RTL-8029* at I/O 0x20a0, IRQ
> 9.
> eth0: RealTek RTL-8029 found at 0x20a0, IRQ 9, 00:00:B4:B8:94:CC
> #
> I suppose this means that the modular driver has been installed in
> the kernel and detected my NIC. So far, great.
>
> Wonder why kmod won't autoload it when I do "ifconfig-yadayada up" ?
> BTW: What does the hex-part at the end mean?
>
It has no reason to associate this driver with eth0; you need to
give it a big hint as to which module to use for the interface.
Try adding
alias eth0 ne2k-pci
to /etc/modutils/aliases and running update-modules as root.
The hex string is your card's MAC, an allegedly unique
identifier that is used for packet addressing at the physical
link layer for machines on your local network. The first
few octets probably identify the card's manufacturer, the rest
are up to them.
I say allegedly unique because some early clone NICs (back
when a cheap name-brand NIC might be $300) had cloned firmware
that gave each card the same MAC, or used ranges that
had been assigned to other manufacturers; that meant if you used
bad cards, you might have to sort out which ones couldn't
share a network.
MACs are associated with IPs using ARP ("Address Resolution
Protocol"). You can monitor the MAC-to-IP translation on your
network with something like this (assuming your network is
192.168.1.0/24):
$ ping -c 2 192.168.1.255
$ /usr/sbin/arp -a
You won't see your own machine in the arp cache, because your
TCP/IP stack recognizes packets addressed to itself and doesn't
get as far as attempting ARP for local addresses.
John P.
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.mdt.net.au/~john Debian Linux admin & support:technical services
Re: Potato vs Realtek8029PCI NIC
On Tue, Aug 22, 2000 at 09:33:45PM +0200, Vitux wrote > Trying to build a tiny lan here... > Recompile fresh 2.2.16 with the ne2k-pci driver as module. > No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > symbols"-error, and ifconfig -yadayada gives me error to the effect > that there's no hardware to configure. > > So the question is: to nic or not to nic? > > I've determined that the kmod-bit works (all the other modules are > inserted automagically on request), and little lights are shining > from nic and hub. > > Is there any other voodoo I have to do to get the card recognised/ > installed/ configured/ whatever? > It said in a howto somewhere (I forget which, I've pored over so > many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, > and so should use the driver for same... Right?! > # modprobe ne2k-pci Ne2k-pci, like many other modules, depends on other bits that may also be built as modules. insmod alone won't work, unless the other bits are already present; modprobe handles module dependencies for you. Assuming that works, just adding ne2k-pci to /etc/modules should do the trick on a more permanent basis. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mdt.net.au/~john Debian Linux admin & support:technical services
Re: Potato vs Realtek8029PCI NIC
More stuff: I did a # modprobe ne2k-pci and I get this: ne2k-pci..: PCI NE2000 clone 'Realtek RTL-8029* at I/O 0x20a0, IRQ 9. eth0: RealTek RTL-8029 found at 0x20a0, IRQ 9, 00:00:B4:B8:94:CC # I suppose this means that the modular driver has been installed in the kernel and detected my NIC. So far, great. Wonder why kmod won't autoload it when I do "ifconfig-yadayada up" ? BTW: What does the hex-part at the end mean? Sorry if I'm being dense here, but a lot this is very unclear in the net-howto, and I am trying to learn. This is my first lan! :-) Thanks Vitux -- "I'm not a crook" Richard Nixon Debian GNU/Linux Micro$loth-free Zone
Re: Potato vs Realtek8029PCI NIC
Troy Telford wrote: > > Actually, I have no problems with a realtek 8029 card; however, I always > re-compile the > kernel after I get the thing on; that usually gets rid of the unresolved > symbols > problem... In fact, with all the kernel module(s) I've used, re-compiling > the kernel > from scratch (including the modules) typically removes all unresolved symbols > problems. > So, you might want to try that... As I have experienced the same thing, this was the first thing I did: d'l latest kernel source for 2.2.16, compile kernel, modules and install the modules, all according to README in the kernel docs. System boots & runs just fine, the modules are all there (8390, bsd_comp, ne2k-pci, ppp-deflate). Kmod seems to be working; I made dos-fs as a module, which gets inserted when I mount a dos-disk. > > As for myself, I typically compile in ne2k-pci into the kernel, rather than > as a module; > but I must admit I've never had any trouble with it as a module, either. > > Hope I can be helpful... as I have been using a RealTek 8029-based PCI > network card for > around 2 years now, with all kinds of kernel versons (yours included, no > doubt), I'll be > glad to help in any way I can... > > Troy > > > so..try > > > > insmod 8390 > > insmod ne2k-pci > > > > should work :) > > > > nate > > > > Bob Nielsen wrote: > > > > > > For what it's worth, I am running one of these cards with the driver > > > compiled into 2.2.16, rather than as a module. > > > > > > Here's a snippet from dmesg: > > > > > > ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker > > > http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html > > > ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xe800, IRQ 10. > > > eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 52:54:00:E6:65:FB. Nothing even remotely like this appears when booting. Check my attached bit from syslog... > > > > > > Bob The Realtek nic is IRQ 9 in the BIOS setup; I just checked. Thanks! Regards Vitux -- "I'm not a crook" Richard Nixon Debian GNU/Linux Micro$loth-free ZoneAug 23 10:37:33 WichmannRacing syslogd 1.3-3#33: restart. Aug 23 10:37:33 WichmannRacing kernel: klogd 1.3-3#33, log source = /proc/kmsg started. Aug 23 10:37:33 WichmannRacing kernel: Inspecting /System.map Aug 23 10:37:33 WichmannRacing kernel: Symbol table has incorrect version number. Aug 23 10:37:33 WichmannRacing kernel: Cannot find map file. Aug 23 10:37:33 WichmannRacing kernel: No module symbols loaded. Aug 23 10:37:33 WichmannRacing kernel: Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #1 Tue Aug 22 18:56:53 CEST 2000 Aug 23 10:37:33 WichmannRacing kernel: Detected 349183 kHz processor. Aug 23 10:37:33 WichmannRacing kernel: Console: colour VGA+ 80x25 Aug 23 10:37:33 WichmannRacing kernel: Calibrating delay loop... 696.32 BogoMIPS Aug 23 10:37:33 WichmannRacing kernel: Memory: 128192k/131072k available (912k kernel code, 416k reserved, 1512k data, 40k init) Aug 23 10:37:33 WichmannRacing kernel: Dentry hash table entries: 16384 (order 5, 128k) Aug 23 10:37:33 WichmannRacing kernel: Buffer cache hash table entries: 131072 (order 7, 512k) Aug 23 10:37:33 WichmannRacing kernel: Page cache hash table entries: 32768 (order 5, 128k) Aug 23 10:37:33 WichmannRacing kernel: CPU: Intel Pentium II (Deschutes) stepping 01 Aug 23 10:37:33 WichmannRacing kernel: Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Aug 23 10:37:33 WichmannRacing kernel: Checking 'hlt' instruction... OK. Aug 23 10:37:33 WichmannRacing kernel: POSIX conformance testing by UNIFIX Aug 23 10:37:33 WichmannRacing kernel: PCI: PCI BIOS revision 2.10 entry at 0xed728 Aug 23 10:37:33 WichmannRacing kernel: PCI: Using configuration type 1 Aug 23 10:37:33 WichmannRacing kernel: PCI: Probing PCI hardware Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5800-583f to device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5840-584f to device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5850-585f to device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5860-5863 to device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5864-5867 to device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Enabling I/O for device 00:70 Aug 23 10:37:33 WichmannRacing kernel: PCI: Assigning I/O space 5880-589f to device 00:a2 Aug 23 10:37:33 WichmannRacing kernel: PCI: Enabling I/O for device 00:a2 Aug 23 10:37:33 WichmannRacing kernel: Linux NET4.0 for Linux 2.2 Aug 23 10:37:33 WichmannRacing kernel: Based upon Swansea University Computer Society NET3.039 Aug 23 10:37:33 WichmannRacing kernel: NET4: Unix domain sockets 1.0 for Linux NET4.0. Aug 23 10:37:33 WichmannRacing kernel: NET4: Linux TCP/IP 1.0 for NET4.0 Aug 23 10:37:33 WichmannRacing kernel: IP Protocols: ICMP, UDP, TCP Aug 23 10:37:33 WichmannRacing kernel: TCP: Hash tables configured (ehash 1310
Re: Potato vs Realtek8029PCI NIC
> No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > symbols"-error, and ifconfig -yadayada gives me error to the effect > that there's no hardware to configure. I have no idea why kmod doesn't insmod your modules automagically. But ne2k-pci depends on 8390 module; so try modprobe instead of insmod. I have Realtec8029 NIC right now in my computer; and ne2k-pci is compiled as a module. I've never had any problems with this NIC. -- Alexey Vyskubov (at home) Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
Re: Potato vs Realtek8029PCI NIC
Actually, I have no problems with a realtek 8029 card; however, I always re-compile the kernel after I get the thing on; that usually gets rid of the unresolved symbols problem... In fact, with all the kernel module(s) I've used, re-compiling the kernel from scratch (including the modules) typically removes all unresolved symbols problems. So, you might want to try that... As for myself, I typically compile in ne2k-pci into the kernel, rather than as a module; but I must admit I've never had any trouble with it as a module, either. Hope I can be helpful... as I have been using a RealTek 8029-based PCI network card for around 2 years now, with all kinds of kernel versons (yours included, no doubt), I'll be glad to help in any way I can... Troy Nate Amsden wrote: > I worked with one of these recently it was a pain in the ass :) I > believe the proper way to load the module was to first load the 8390 > module first. the mandrake box i was working with did not have the > proper dependency information for this module so modprobe wouldn't > auto-load 8390. > > so..try > > insmod 8390 > insmod ne2k-pci > > should work :) > > nate > > Bob Nielsen wrote: > > > > For what it's worth, I am running one of these cards with the driver > > compiled into 2.2.16, rather than as a module. > > > > Here's a snippet from dmesg: > > > > ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker > > http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html > > ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xe800, IRQ 10. > > eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 52:54:00:E6:65:FB. > > > > Bob > > > > On Tue, Aug 22, 2000 at 09:33:45PM +0200, Vitux wrote: > > > Trying to build a tiny lan here... > > > Recompile fresh 2.2.16 with the ne2k-pci driver as module. > > > No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > > > symbols"-error, and ifconfig -yadayada gives me error to the effect > > > that there's no hardware to configure. > > > > > > So the question is: to nic or not to nic? > > > > > > I've determined that the kmod-bit works (all the other modules are > > > inserted automagically on request), and little lights are shining > > > from nic and hub. > > > > > > Is there any other voodoo I have to do to get the card recognised/ > > > installed/ configured/ whatever? > > > It said in a howto somewhere (I forget which, I've pored over so > > > many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, > > > and so should use the driver for same... Right?! > > > > > > Thanks > > > Vitux > > > > > > -- > > > "I'm not a crook" > > > Richard Nixon > > > > > > Debian GNU/Linux > > > Micro$loth-free Zone > > > > > > > > > -- > > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > > -- > > Bob Nielsen, N7XY [EMAIL PROTECTED] > > Bainbridge Island, WA http://www.oz.net/~nielsen > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- > ::: > ICQ: 75132336 > http://www.aphroland.org/ > http://www.linuxpowered.net/ > [EMAIL PROTECTED] > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Brain: Pinky, are you pondering what I am pondering? Pinky: I think so brain, but if we were meant to fly, wouldn't we have been born with a bag of peanuts?
Re: Potato vs Realtek8029PCI NIC
I worked with one of these recently it was a pain in the ass :) I believe the proper way to load the module was to first load the 8390 module first. the mandrake box i was working with did not have the proper dependency information for this module so modprobe wouldn't auto-load 8390. so..try insmod 8390 insmod ne2k-pci should work :) nate Bob Nielsen wrote: > > For what it's worth, I am running one of these cards with the driver > compiled into 2.2.16, rather than as a module. > > Here's a snippet from dmesg: > > ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker > http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html > ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xe800, IRQ 10. > eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 52:54:00:E6:65:FB. > > Bob > > On Tue, Aug 22, 2000 at 09:33:45PM +0200, Vitux wrote: > > Trying to build a tiny lan here... > > Recompile fresh 2.2.16 with the ne2k-pci driver as module. > > No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > > symbols"-error, and ifconfig -yadayada gives me error to the effect > > that there's no hardware to configure. > > > > So the question is: to nic or not to nic? > > > > I've determined that the kmod-bit works (all the other modules are > > inserted automagically on request), and little lights are shining > > from nic and hub. > > > > Is there any other voodoo I have to do to get the card recognised/ > > installed/ configured/ whatever? > > It said in a howto somewhere (I forget which, I've pored over so > > many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, > > and so should use the driver for same... Right?! > > > > Thanks > > Vitux > > > > -- > > "I'm not a crook" > > Richard Nixon > > > > Debian GNU/Linux > > Micro$loth-free Zone > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- > Bob Nielsen, N7XY [EMAIL PROTECTED] > Bainbridge Island, WA http://www.oz.net/~nielsen > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Re: Potato vs Realtek8029PCI NIC
For what it's worth, I am running one of these cards with the driver compiled into 2.2.16, rather than as a module. Here's a snippet from dmesg: ne2k-pci.c:vpre-1.00e 5/27/99 D. Becker/P. Gortmaker http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html ne2k-pci.c: PCI NE2000 clone 'RealTek RTL-8029' at I/O 0xe800, IRQ 10. eth0: RealTek RTL-8029 found at 0xe800, IRQ 10, 52:54:00:E6:65:FB. Bob On Tue, Aug 22, 2000 at 09:33:45PM +0200, Vitux wrote: > Trying to build a tiny lan here... > Recompile fresh 2.2.16 with the ne2k-pci driver as module. > No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved > symbols"-error, and ifconfig -yadayada gives me error to the effect > that there's no hardware to configure. > > So the question is: to nic or not to nic? > > I've determined that the kmod-bit works (all the other modules are > inserted automagically on request), and little lights are shining > from nic and hub. > > Is there any other voodoo I have to do to get the card recognised/ > installed/ configured/ whatever? > It said in a howto somewhere (I forget which, I've pored over so > many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, > and so should use the driver for same... Right?! > > Thanks > Vitux > > -- > "I'm not a crook" > Richard Nixon > > Debian GNU/Linux > Micro$loth-free Zone > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Bob Nielsen, N7XY [EMAIL PROTECTED] Bainbridge Island, WA http://www.oz.net/~nielsen
Potato vs Realtek8029PCI NIC
Trying to build a tiny lan here... Recompile fresh 2.2.16 with the ne2k-pci driver as module. No signs of nic when booting, insmod ne2k-pci.o gives me "unresolved symbols"-error, and ifconfig -yadayada gives me error to the effect that there's no hardware to configure. So the question is: to nic or not to nic? I've determined that the kmod-bit works (all the other modules are inserted automagically on request), and little lights are shining from nic and hub. Is there any other voodoo I have to do to get the card recognised/ installed/ configured/ whatever? It said in a howto somewhere (I forget which, I've pored over so many of'em lately;-), that the Realtek RTL8029 is a NE2000-clone, and so should use the driver for same... Right?! Thanks Vitux -- "I'm not a crook" Richard Nixon Debian GNU/Linux Micro$loth-free Zone
