payasam

OK about mac address, Ianw. Something like implanting a radio transmitter chip into the bum of a rhino, right? Post 46 has the output that lsmod gave then. You didn't ask me to do it again, after the last lot of changes, so I didn't do it. What now? Switch to a Cray?

To answer your last question, I'm exactly where I was. What does "mac address" mean? If it has anything to do with a Mac, I'm on a PC. I went to the dhcp option first, since that is what you gave first. No luck. Then the second. On re-booting, a terrifying red "Failed" and "8139too does not seem to be present". Did a modprobe 8139d as that is the official name of my card. Same result. Changed to 8139cp. Same result. I then realised that the 8139too must be coming from the two files to which I'd added one line each earlier. So deleted those lines. No "Failed", but nothing worked, and ifconfig -a brought up pretty much the same stuff. I do not understand, incidentally, what you mean by "see if you have a device". On the last boot, there weren't red letters and I caught a "bringing up eth0" as it flew past -- but that was that. I now have the three files sitting around, but with 8139too deleted from two and IPADDR followed in the third by 220.225.188.21 because I don't want to mess up your communications even by accident. It's 3.30 a.m. here now and this old man needs rest.

Heavens, Ianw, you can't possibly have had all this in your head. Whether or not it works, I wouldn't know how to thank you. I seem to have a static IP: 220.225.188.21 has come up every time I've checked. I assume this should go in the IPADDR line.

Ianw, here's what ifconfig -a gave after I added a line each to the two files and rebooted: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:336 errors:0 dropped:0 overruns:0 frame:0 TX packets:336 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:24150 (23.5 Kb) TX bytes:24150 (23.5 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) RX and TX bytes are different from the last time, but all else looks to be the same. Disabling silly smilies this time.

I didn't do an ifconfig -a, but I shall do it after making the two additions. I have only one ethernet card. Would I be wrong to assume that I shall be connected to the Net when I boot up (assuming the modem is switched on)? I have so far been connecting only when I need to. It isn't a question of expense -- my last account was the unlimited kind and the new one is the same. I just don't like keeping things active when they're not needed. I should think security issues too would be involved. But getting connected any which way is the first priority.

No joy, Ianw. After a modprobe 8139too, lsmod | grep 8139too gave: 8139too 20928 0 mii 4224 1 8139too In MCC, when I selected 8139too, I found myself in the same old Manually Load Driver - Autoprobe loop. In the list of hardware, the ethernet adapter had the details I put in post 33.

Right, Ianw. Quick as ever -- when you're around, that is. Will get out of Win and into Lin now and do as you say.

Have I been thrown to the few remaining tigers in the jungles of my country? Googling said that modprobe adds or removes modules and that ifconfig configures network interfaces. The arguments to be given to each remain a mystery. There's another bit of confusion. One "technical" chap of the service provider said, positively, that I'd have a static IP address; and another said, equally positively, that it would be dynamic. I've looked it up three times now, disconnecting and re-connecting, and it has been the same.

I had hoped, Ianw and Devries, that on seeing that I had abandoned the 2006 scheme, you would hoof me in the right direction. I should say that on the off chance that that might help, I over-wrote 10.1 with itself: "repair" was the word, I think. When I tried to select LAN settings, I found myself in the same endless loop. No damage to my other software, by the way: except that the dial-up modem wasn't recognised since it wasn't there any longer. I shall now look for ways of piping command output to files and cutting and pasting. [EDIT] What an ass I am. More than 18 months on MDK, and I hadn't realised that the mouse cursor worked in console. Thought it was as it is at the DOS prompt. Well, here we are: ----- (Output of ifconfig -a) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:368 errors:0 dropped:0 overruns:0 frame:0 TX packets:368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:26430 (25.8 Kb) TX bytes:26430 (25.8 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ----- (Two other commands, found on another forum) [root@localhost albert]# dmesg |grep eth <no output> [root@localhost albert]# ifup eth0 /sbin/ifup: configuration for eth0 not found. Usage: ifup <device name> ----- As I’ve already said, no output of modprob 8139too.

modprobe 8139too may have done something, but there was no output. ifconfig -a did give an output, but I don't know how to direct such things into a file or how to copy and paste stuff from the console, and I was too tired to write it all down and then type it in here. This is the content of the readme.txt file of a driver which I downloaded and unzipped. Don't know if it'll be useful. ---- 8139too.c release note 2001/10/31 by ShuChen Shao 1.This driver was originally based on 8139too.c version "0.9.15". 2.It has been enhanced to support RTL8139C+ PCI ethernet controller. 3.RTL8139C+ PCI ethernet chips is set to support C+ mode by default. If FORCE_C_Mode below is enabled, the RTL8139C+ chip will be forced to support C mode after reboot. 4.This program can be compiled using the attached Makefile. Please remember to SPECIFY "NEW_INCLUDE_PATH" in Makefile according to your linux environment. The object file named 8139too.o should be moved to the directory /lib/modules/<linux-version>/kernel/drivers/net/ The driver could be brought up by the following steps: 'insmod 8139too' 'ifconfig eth0 up' 5.It can support Auto-Negotiation ability,that is 10-half 0x01 10-full 0x02 100-half 0x04 100-full 0x08 If 10-half mode is expected, it can be achieved by the following steps: #ifconfig eth0 down #rmmod 8139too #insmod 8139too media=0x01 6.If the "Install Type", selected during the Linux install procedure, is "laptop", this driver can work normally for CardBus application without any modification. Otherwise, reinstall Linux and select "Install Type" as "laptop". Then this driver can also work. --------------------------------------------------------------------------------------- 8139too.c version 1.5.0 release note 2003/3/4 by ShuChen Shao 1.Add flag in Makefile to specify access type to operation register on PCI ethernet chips. ---- The readme.txt of the other driver -- the one which came with the LAN card -- has far less information.

Hello, John. Been a while, hasn't it? All right about choosing the upgrade option. I wouldn't have known there is one as I did a clean install of 10.1 after 10.0. Yes, I have /home on a separate partition. Thanks for the hand-holding.

Ianw, Devries, I'm back. I went out for a couple of hours, and when I returned I found that my Net connection had broken and I had only 15 MB or so of the first ISO. Decided against 2006. Not a tragedy, since I'm quite content with 10.1. Will get out of Windows and into MDK and do the modprobe and the ifconfig. Don't know if I'll be able to set up the connection by hand -- though I'm much happier at console level than I am in MCC.

Here's something which must rank at the top of the Cosmic Stupidity Scale. I'm pulling in the first of the three ISOs of 2006. When I have them all written to CD, what do I do? I did a clean install of 10.1 when I moved up from 10.0, which of course meant spending much time putting in again, and configuring, all the applications I used then. I also had to store data in safe places. Will it be possible now to upgrade without leaving a whole lot of junk floating about?

Devries and Ianw, you've both asked me to try a modprobe. Afraid that'll have to wait for something between 60 and 70 hours, that being my estimate of the time needed to download the three ISOs of 2006. Doing it in Windows. Once they're in and written to CD, I'll have to figure out if I must install from scratch or if I can upgrade 10.1. Never fear, I'll throw a dozen more problems (each) your way.

Ianw, the problem with Pegasus (and two other mail programs) was that my anti-virus thing, AVG Free Edition, wasn't expecting mail over LAN. When finally my brain began to function, I fixed that and all is well. As for Mandrake, here's something I found on another forum. It's precisely what happened to me. “I've tried using the 8139too driver that came with LinuxMandrake, but when I select it, it says it's installing, but it actually goes back to the screen where I say that I want to choose the driver manually. I'm in a never-ending loop.”

Ianw, the hardware chappie just left. What I told you earlier was all wrong, because what I'd been told was all wrong. The set-up is not straight but through an ADSL modem. In Windows, there's no desktop icon: instead, I connect by going to the service of the site through a browser. I went to set up Pegasus Mail for POP3 and SMTP, but while I can send messages I cannot receive them. Never even heard of such a thing. The boy who came was handicapped by the fact that the system has been changed recently but he hasn't been told of the changes. Also, he did not seem familiar with mail programs, presumably because so many people do their e-mail through browsers. He put me on to a senior man who was a damn sight worse: not only did he not know a thing, he confidently gave me all the wrong instructions. Other programs, accounts, browsers are working OK. End of ageing man's grumbling. Shall I still do the modprobe and ifconfig things? Also, I'd like to get kppp to work again, since I'd then have our ordinary land-line as a standby.

No hurry, Ianw. I'll do the Windows scene first. IDENTIFICATION Vendor: (null) Description: Media Class: NETWORK_ETHERNET CONNECTION Bus: PC1 Bus PC1#: 1 PCI device#: 0 PCI function#: 0 Vendor ID: 6404 Device ID: 8241 Sub vendor ID: 65535 Sub device ID: 65535 MISC Module: unknown By the way, I tried and tinkered and messed about, but I couldn't manage to receive or send anything in MDK.

Will do, Ianw. This fibre optic cable stuff is either a complete fiction or else refers to how signals are carried to a point at which copper takes over. Now to wrestle with Harddrake and kppp.

Righty-ho, Ianw, Windows first; but I intend to go into Linux and see about HardDrake and kppp. The cable ends in a white plastic box which will be crushed if a cockroach steps on it (I'd have liked to say something rude). Just opened it and saw two wires to one terminal and one to the other. Then one wire runs from each terminal to a little phone socket of the new kind. All wires copper, presumably tubular so that they can carry light.

Ianw, 1. No equipment delivered, just the cable. My understanding is that no equipment is to be delivered, other than a means of plugging the cable into the LAN card. 2. Haven't yet connected through Windows: the card wasn't here when the men came yesterday to set up the connection. Have said they'll come tomorrow. 3. HardDrake is present, but I've no idea if it's enabled. I'm in Windows now but will go into Linux in a while and look into that. 4. I ought to search for a Realtek driver for Linux. When untarred, the one which came on floppy let out one file with a name made up of nonsense characters. It can safely be expected to be corrupted. 5. Why on Earth should kppp behave as it does? I just can't connect to the Net when in Linux. Haven't so far located the file in which it keeps its settings.

Install from floppy. I copied all the drivers to a sub-dir in Windows (to be written to CD) and copied the Linux bit to the MDK partition. In Windows it identifies itself as a "Realtek Rtl-8139d Fast Ethernet Adapter".

Ianw, the Intex 8139D *is* the LAN card I've just got. I've seen its number (8139) prefixed by other brand names too, so I'd assume it's a commonly used device. Installing the thing in Windows was no problem, but not so in Linux. As I said, Mandrake Control Centre seemed the obvious place to go into, but the card could not be installed. There was, in fact, an annoying side effect: now kppp no longer works with my dial-up modem. The settings are as they were, the modem dials, there is hand-shaking -- but then, although I am connected to my ISP's sever, I cannot get to any POP3 server or even to Google in a browser. Nothing comes into the modem, nothing goes out of it. It continues to work as it did in Windows.

Two chaps came in the day and rigged up the cable. An hour later, two others came to set up the connection; but they went away without doing anything since my hardware chap didn't bring the LAN card until the evening. In MDK 10.1 Control Centre, there are two Intex cards listed, but mine -- an 8139D -- isn't. The card came with drivers, including a Linux one, on a floppy, but when I try to install it I just go around in circles.

That was quick, Ianw. LAN card, yes, but I don't know about DHCP. Nobody said anything about *automatic* configuration, nor about DHCP. Guess I just wait and hope for the best. Thanks.

I have discovered over the years, Ianw, that it is unwise to expect people who take your money to give help in return. The System ... Security route seems the easiest one for me to take just now. For the other, I'd first have to figure out urpmi. Strange that I haven't managed that yet, although the similar tool in Debian was no problem at all. Thanks generally, and specifically for explaining the NAT router. It remains to hunt around what to use with this sort of connection. There must be an equivalent for the kppp I've been using for my dial-up and modem.