Hi James et al: I've done some more experimenting on this.
When I go back to Windows on the slave the network connection is back. I can ping successfully both ways. However once I go in Linux, although eth0 comes up (this coming up just detects the IP address I manually allocated), the network connection breaks down. >From Windows master the ping also fails. >From the url http://www.scyld.com/network/vortex.html drivers for 3c59x.o I believe also can be used for my etho 3com EtherLink XL 10/100 PCI NIC (3c905-TX) Boomerang adaptor on the slave. Are there any extra steps I am missing that's causing Linux to break the connection ? I'm pretty sure I did netconf as quoted below. Would upgrading to a more recent Linux distribution package solves this problem ? Anyone !! Louis. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LS Sent: Tuesday, February 25, 2003 11:51 PM To: 'James Gregory' Cc: [EMAIL PROTECTED] Subject: RE: [Re: [SLUG] Control one PC with Another] My replies are quoted "Louis>>>" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Gregory Sent: Tuesday, February 25, 2003 12:32 AM To: LS Cc: [EMAIL PROTECTED] Subject: RE: [Re: [SLUG] Control one PC with Another] On Mon, 2003-02-24 at 23:22, LS wrote: > Another point I noted. When Linux was booting up, I noticed that the > "Bringing up interface eth0" FAILED . Could this also be another issue > ? The Network card on the slave PC where Linux OS resides as well is a > 3Com Network card. Are there special drivers I need to install to get > Linux to detect this card or get a PASS when booting ? ah HA! This is your problem. If the ethernet card is not coming up then it won't have an IP and you won't be able to ping or do anything else useful with it. I was under the (perhaps misguided) impression that 3com cards were reasonably well supported on linux. Ok, on my computer I have a program called "netconf", which I think you should have as well. It's part of linuxconf afaik. It's good for doing this sort of stuff. But first you need to identify what sort of network card you have, then identify which driver to use. hrmm. This will get a bit vague. First of all, if you want to find what 3com drivers you have, this should tell you (I've included the output from my box as well for reference) : $ find /lib/modules/`uname -r` -name "3c*" /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c501.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c503.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c505.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c507.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c509.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/tokenring/3c359.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c515.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/pcmcia/3c589_cs.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/pcmcia/3c574_cs.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/drivers/net/3c59x.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/3rdparty/3c990 /lib/modules/2.4.21pre4-8mdk/kernel/3rdparty/3c990/3c990.o.gz /lib/modules/2.4.21pre4-8mdk/kernel/3rdparty/3c990fx /lib/modules/2.4.21pre4-8mdk/kernel/3rdparty/3c990fx/3c990fx.o.gz Louis>>> running the above command gave some data. The ones that I think relate to mine are 3c50(1/3/5/7/9).0, 3c515.0, and 3c59x.o . Anyway I went into the /lib/modules/ and searched around. In the ../kernel/drivers directory I only see ".o" files. There are no ".o.gz" files. I can see that the closest Are as stated above. The path is in "/lib/modules/2.4.7-10/kernel/drivers/net/" (ie run 'lspci | grep Ethernet' to find out what ethernet cards you have -- don't use the output from my computer, you don't want to configure your computer to use my devices :)) Louis>>> this command revealed that my Ethernet card is of series 3c905 (i.e 3c90x series) . >From /lib/modules directory when browsing around I saw no 3c905.o files, but saw A 3c59x series ".o "file". Ok, so having identified the driver, you run netconf, go to the "Host name and IP network devices" (assuming your system is the same as mine, which it quite possibly isn't, but find the "configure my IP address" looking thing), click on the "adaptor 1" tab, click "manual" config mode, type in an ip address in the appropriate field (as I said, if you're talking to windows computers, 192.168.0.something is a good address). netmask, net device etc can be left as default. Now, where it says "kernel module" you need to either type in or select from the drop down the driver you identified before. Louis>>> I went ahead with netconf anyway. I selected "manual", and entered the other data for "adaptor 1" tab, and clicked accept. For the "Kernel" I actually found a 3c90x series. Scrolling further on this one showed the number 3c905. So I selected "3c90x". But I don't think this driver is installed, so why would it show in the drop menu ?? Running the /sbin/ifconfig showed the IP. However when I pinged the ethernet for my master pc, it said "Network is unreachable". Anyway I rebooted and this time Linux did not even try to bring up the eth0. From Gnome I re netconf, and this time I selected the default Kernel it selected for me the first time I ran netconf which was 3c59x series. Accepted this one. This one is installed as mentioned above. Now I pinged and it tried something but still the test failed. Anyway I rebooted, and this time it did bring up the etho. However in Gnome when I run a ping test on the master pc, I get a straight "connect: Network is unreachable" this time. It seems I need to get 3c90x driver. I searched the web and came across this site http://www.scyld.com/network/vortex.html They talk about 3c90x series but when I go down to get source code, I just see the file for 3c95x.c and no 3c90x.c . So does that mean 3c95x supports 3c90x series ? I'm slowly getting there. Please provide some input. Right now "adaptor 1" is on "3c95x" series with the other settings as what you stated above. The Ip I selected is 192.168.0.100. How do I pass ping ? hmm. It could well be that the gnome gadget just reads the pci device list, and that's how it knows about the device. I suspect that this is not an indication that the card is correctly configured. It has occurred to me that perhaps it's just a case of having set your interface to "auto" or "dhcp" or something and not having a dhcp server. In either case (no driver found or auto config selected), the above steps should rectify it. Is there anything else the gnome thing shows you? can you change settings there? Louis>>>> I cannot change this settings from the System Settings. But from netconf on the First run if did show "adaptor 1" set to "dhcp" with the other data blank. Kernel was on "3c95x" . BTW: I found the problem why the 2 windows OS could see not each other. On my master a while back I installed Norton Firewall. It blocked the network Connection. Anyway I uninstalled it, and I can see the pcs both way and can Map drives as well. I plan to re-install the firewall software and get it to allow network connection internally. Louis -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
