[SLE] LinkSys 10/100Mb card and HOWTO
A few days ago I bought a 10/100Mb LinkSys ethernet card at CompUSA for my 6.4 Linux system. I have 2 older (10Mb) cards on this home network between my two FreeBSD boxes; they work fine. The card is lit on the 10Mb LED and it my hub shows the connection too, so at least the hardware connection there seems solid. But I've having trouble trying to get my new box "suzah.thought.org" talking to this box, "tao.thought.org" and wonder if any of you can help me. Last night I used the YAST tool to configure various network things, including the ethernet link. No joy. And so far today, likewise, no luck. I don't see any indication that the Linux system even sees the card--from dmesg. What should I be looking for? Also, do I need to install any kernel module? I have "suzah" designated as 10.0.0.3, but even trying % telnet 10.3 fails with the error that the "Network is unreachable." Any network gurus out there? thanks, gary kline -- Gary D. Kline kline@tao.thought.org Public service Unix -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Try: telnet 10.0.0.3 (not just 10.3) Why such a weird IP? Use Yast 2 (the GUI) to set the card up - I guarantee it works - I have one. Make sure telnet is not disabled - it (it won't be unless you disabled it - SuSE has it enabled by default) Also make sure that your whole network is on the same subnet, and have the same netmask (if not you'll get that "Network unreachable" error) JW P.S. try telneting to the hostname too - not just the IP address At 03:57 PM 8/5/2000 -0700, you wrote:
A few days ago I bought a 10/100Mb LinkSys ethernet card at CompUSA for my 6.4 Linux system. I have 2 older (10Mb) cards on this home network between my two FreeBSD boxes; they work fine. The card is lit on the 10Mb LED and it my hub shows the connection too, so at least the hardware connection there seems solid.
But I've having trouble trying to get my new box "suzah.thought.org" talking to this box, "tao.thought.org" and wonder if any of you can help me.
Last night I used the YAST tool to configure various network things, including the ethernet link. No joy. And so far today, likewise, no luck. I don't see any indication that the Linux system even sees the card--from dmesg. What should I be looking for? Also, do I need to install any kernel module?
I have "suzah" designated as 10.0.0.3, but even trying
% telnet 10.3
fails with the error that the "Network is unreachable."
Any network gurus out there?
thanks,
gary kline
-- Gary D. Kline kline@tao.thought.org Public service Unix
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi Gary, See "Support Page : LNE100TX LINUX" & "EtherFast 10/100 LAN Card Linux Support" at: http://www.linksys.com/support/support.asp?spid=25 It talks about "Linksys network cards use a driver called Tulip" and "To download the latest version of the Tulip.c driver, go..." at same page. Also they detail completely the procedure to test and install on a generic Linux distro. Also you can find the kernel loadable module at your: /lib/modules/2.2.xx/net/tulip.o You must tweak your /etc/modules.conf and check for tulip options. You must check that you have "alias ethx(x=0,1,n) tulip" near the beginning. Also booting your CD on YaST(1) gives you the opportunity to auto- detect your Nic and tell you which is the module used looking at "Loaded drivers" in "Kernel modules" running under Linuxrc. The SuSE manual you must have details completely the process. The clue is = tulip. -- HTH Best regards, Eduardo Carriles [-- Better a smile than a flame --] (Long time SuSE-Linux [preferred distro] user). [-- Se me nota mucho? -- Notices me much?] [-- Have a lot of fun...] ---- Gary Kline wrote:
A few days ago I bought a 10/100Mb LinkSys ethernet card at CompUSA for my 6.4 Linux system. I have 2 older (10Mb) cards on this home network between my two FreeBSD boxes; they work fine. The card is lit on the 10Mb LED and it my hub shows the connection too, so at least the hardware connection there seems solid.
But I've having trouble trying to get my new box "suzah.thought.org" talking to this box, "tao.thought.org" and wonder if any of you can help me.
Last night I used the YAST tool to configure various network things, including the ethernet link. No joy. And so far today, likewise, no luck. I don't see any indication that the Linux system even sees the card--from dmesg. What should I be looking for? Also, do I need to install any kernel module?
I have "suzah" designated as 10.0.0.3, but even trying
% telnet 10.3
fails with the error that the "Network is unreachable."
Any network gurus out there?
thanks,
gary kline
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi Gary and Jack, Let's think a bit about the modprobe and insmod messages: [Note: /etc/modules.conf is more recent than /lib/modules/2.2.14/modules.dep] Just a stupid question (from my own): Which Kernel version you got?? Must be 2.2.14 for sure, or not?? I'm going to read some info material. -- HTH Best regards, Eduardo Carriles [-- Better a smile than a flame --] (Long time SuSE-Linux [preferred distro] user). [-- Se me nota mucho? -- Notices me much?] [-- Have a lot of fun...] -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Sun, Aug 06, 2000 at 06:38:21AM +0200, Eduardo Carriles wrote:
Hi Gary and Jack,
Let's think a bit about the modprobe and insmod messages:
[Note: /etc/modules.conf is more recent than /lib/modules/2.2.14/modules.dep]
Just a stupid question (from my own): Which Kernel version you got?? Must be 2.2.14 for sure, or not??
I'm going to read some info material.
Eduardo, I didn't find anything very helpful about building or rebuilding the SuSE kernel on their info pages. ---Not unusual, really, since SuSE users are not supposed to be kernel hackers or even kernel-tweakers. But given your caveats about backing up things, I'm going to hold back. My tape drives are on this and my second platform. Besides, I might get stuck restoring. With BSD I'm safe; with Linux, not! Yes, 2.2.14. In /usr/src, <B>linux</B> is a symlink to linux-2.2.14.SuSE. gary
-- Gary D. Kline kline@tao.thought.org Public service Unix -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi Gary, Do a: /sbin/depmod -a (as root) take note of the messages and reboot. Let's see if we get rid of the "modules.conf" & "modules.dep" date mismatch. It also tests modules in between. Nothing to do with the Nic module, but just in case. -- HTH Best regards, Eduardo Carriles [-- Better a smile than a flame --] (Long time SuSE-Linux [preferred distro] user). [-- Se me nota mucho? -- Notices me much?] [-- Have a lot of fun...] -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Sun, Aug 06, 2000 at 07:15:27AM +0200, Eduardo Carriles wrote:
Hi Gary,
Do a: /sbin/depmod -a (as root) take note of the messages and reboot.
Let's see if we get rid of the "modules.conf" & "modules.dep" date mismatch.
It also tests modules in between.
Nothing to do with the Nic module, but just in case.
Done. I actually checked the *.o dependencies last night. Also, in this file is the output of my building a new tulip.o. I'm missing 2 #include "file.h". find /usr/src doesn't find these headers; neither does locate. ++ '[' -f /usr/include/linux/modversions.h ']' ++ echo -DMODVERSIONS + gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -c tulip.c -DMODVERSIONS tulip.c:161: pci-scan.h: No such file or directory tulip.c:162: kern_compat.h: No such file or directory root@suzah: [80] depmod -a depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/airport.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/cpia_pp.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keywordchk.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keyworddtn.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keywordres.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/pcmcia/mpsuni_cs.o
-- Gary D. Kline kline@tao.thought.org Public service Unix -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
If you downloaded the tulip module from http://www.scyld.com/, you need to follow the instructions. "When updating a single driver you will need to build pci-scan.o along with the specific driver.o file. This means that in addition to the driver.c file, you must download pci-scan.c, pci-scan.h, and kern_compat.h". Gary Kline wrote:
On Sun, Aug 06, 2000 at 07:15:27AM +0200, Eduardo Carriles wrote:
Hi Gary,
Do a: /sbin/depmod -a (as root) take note of the messages and reboot.
Let's see if we get rid of the "modules.conf" & "modules.dep" date mismatch .
It also tests modules in between.
Nothing to do with the Nic module, but just in case.
Done. I actually checked the *.o dependencies last night. Also, in this file is the output of my building a new tulip.o. I'm missing 2 #include "file.h". find /usr/src doesn't find these headers; neither does locate.
++ '[' -f /usr/include/linux/modversions.h ']' ++ echo -DMODVERSIONS + gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/inet -Wall -Wstrict-prototyp es -O6 -c tulip.c -DMODVERSIONS tulip.c:161: pci-scan.h: No such file or directory tulip.c:162: kern_compat.h: No such file or directory
root@suzah: [80] depmod -a depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/airport.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/cpia_pp.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keywordchk.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keyworddtn.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/misc/vtx-keywordres.o depmod: *** Unresolved symbols in /lib/modules/2.2.14/pcmcia/mpsuni_cs.o
-- Gary D. Kline kline@tao.thought.org Public service Unix
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/support/faq
--
Jerry Feldman
On Sun, Aug 06, 2000 at 04:33:27PM -0400, Jerry Feldman wrote:
If you downloaded the tulip module from http://www.scyld.com/, you need to follow the instructions. "When updating a single driver you will need to build pci-scan.o along with the specific driver.o file. This means that in addition to the driver.c file, you must download pci-scan.c, pci-scan.h, and kern_compat.h".
Right. Turns out that everything was|is bundled with the netdrivers tarball. rpm stashed it where I hadn't expected. gary -- Gary D. Kline kline@tao.thought.org Public service Unix -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
What module are you loading for the card? Mine use the tulip driver. Randy Rathbun randy@rrr.2y.net http://rrr.2y.net On Sat, 5 Aug 2000, Gary Kline wrote:
A few days ago I bought a 10/100Mb LinkSys ethernet card at CompUSA for my 6.4 Linux system. I have 2 older (10Mb) cards on this home network between my two FreeBSD boxes; they work fine. The card is lit on the 10Mb LED and it my hub shows the connection too, so at least the hardware connection there seems solid.
But I've having trouble trying to get my new box "suzah.thought.org" talking to this box, "tao.thought.org" and wonder if any of you can help me.
Last night I used the YAST tool to configure various network things, including the ethernet link. No joy. And so far today, likewise, no luck. I don't see any indication that the Linux system even sees the card--from dmesg. What should I be looking for? Also, do I need to install any kernel module?
I have "suzah" designated as 10.0.0.3, but even trying
% telnet 10.3
fails with the error that the "Network is unreachable."
Any network gurus out there?
thanks,
gary kline
-- Gary D. Kline kline@tao.thought.org Public service Unix
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Sun, Aug 06, 2000 at 03:46:29PM +0000, Randy Rathbun wrote:
What module are you loading for the card? Mine use the tulip driver.
Yep, tulip; seems to be way out of date....
Randy Rathbun randy@rrr.2y.net http://rrr.2y.net
-- Gary D. Kline kline@tao.thought.org Public service Unix -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (5)
-
eduardo.carriles＠teleline.es -
gaf＠gaf.ne.mediaone.net -
kline＠tao.thought.org -
randy＠rrr.2y.net -
wilson＠claborn.net