payasam

Devries, I had to take a break from literally everything. My 83-year-old mother was a bit unwell. I have the full outputs of lspci -v but am giving here only what seems directly related to the ethernet card. Below is what I got with /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/modprobe.preload and /etc/modprobe.conf set up in the way Ian specified. On booting, the “8139too eth0 does not seem to be present” message had come up. lspci -v NOT AS ROOT 01:00.0 Ethernet controller: Unknown device 1904:2031 (rev 01) Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at e5000000 (32-bit, non-prefetchable) I/O ports at c000 Expansion ROM at <unassigned> [disabled] Capabilities: <available only to root> lspci -v AS ROOT 01:00.0 Ethernet controller: Unknown device 1904:2031 (rev 01) Flags: bus master, medium devsel, latency 32, IRQ 11 Memory at e5000000 (32-bit, non-prefetchable) I/O ports at c000 Expansion ROM at <unassigned> [disabled] Capabilities: [50] Power Management version 2 Capabilities: [60] Vital Product Data After deleting ifcfg-eth0 and removing one line each from modprobe.preload and modprobe.conf, there was no 8139too message on booting. The outputs of lspci -v were identical to those above. I have the ISO of PCLinuxOS, by the way, and will put it on to CD if the MD5 is OK. [EDIT] Just back from what you have on the MCC. In the screen shot of "Select network interface", there are two options in front of "Net device": (1) "eth0 ..." and (2) "Manually load driver". So far I have been offered only the second. Naturally, I have to go ahead from there; but when I select 8139too from the list, I am thrown right back at "Manually load driver".

Thanks, John, but I am on an oven fresh install of 2006. None of the three ISOs gave an MD5 error, and the install itself went without a hitch. I am communicating from Windows, using the same ethernet card. I should imagine it will have been activated in the BIOS. Devries, I know *where* to add the information, but I don't know *what* that wretched information is. Googling hasn't got me anything, and I wonder if lspci -v will, since MDV seems to think no card exists. Will give it a go, of course, and will take a peek into your MCC info.

Ian, Did "modprobe 8139too", then into MCC. As before, network could not be configured: autoprobe put me in the same loop after saying, as always, "In some cases 8139too needs to have extra information". Created ifcfg-eth0 as you said I should, added one line each to modprobe.preload and modprobe.conf, re-booted. Red mark against "8139too eth0 does not seem to be present...". HardDrake too told me to buzz off. I am downloading PCLinuxOS, which is apparently based on Mandrake and is being praised widely. Will run it off CD and, if it works with this ethernet card, may install it to hard drive. The alternative is to get my hardware chap to bring me a different card.

Then I wonder what the hell is the matter. This guy was pretty positive about what he said -- except that he couldn't say where he'd seen it. Anyhow, here's what you asked for. Should there have been an eth0 somewhere? [root@localhost albert]# lsmod Module Size Used by i810 20992 1 drm 60404 2 i810 md5 3584 1 ipv6 234016 10 i810_audio 33556 1 ac97_codec 18156 1 i810_audio soundcore 7008 2 i810_audio lp 10024 0 parport_pc 32612 1 parport 31976 2 lp,parport_pc af_packet 16392 0 floppy 55444 0 video 14052 0 thermal 10920 0 tc1100_wmi 5092 0 processor 17876 1 thermal fan 3172 0 container 3008 0 button 4848 0 battery 7460 0 ac 3268 0 ide_cd 37988 0 loop 14504 0 nls_iso8859_15 4224 2 nls_cp850 4480 2 vfat 10592 2 fat 45980 1 vfat supermount 31956 2 intel_agp 20636 1 agpgart 29032 3 drm,intel_agp tsdev 5984 0 uhci_hcd 29136 0 usbcore 108348 2 uhci_hcd evdev 7648 0 ext3 124744 2 jbd 48568 1 ext3 [root@localhost albert]# 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:160 errors:0 dropped:0 overruns:0 frame:0 TX packets:160 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12332 (12.0 KiB) TX bytes:12332 (12.0 KiB) 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) [edit] Damn. The columns have gone to hell. I suppose I can make up for it by zapping the smilies.

John, I don't see how I can take a snapshot at the same place as you if I don't ever get there. I've set out the text of the screens with which I'm faced. Right, Ian, will do an "lsmod" and an "ifconfig -a" and send you what I get. I've been communicating from Windows all along. Not able to connect from Mandrake/Mandriva, remember? When I choose "Autoprobe", I'm told that that usually works but *sometimes* this card needs to have the four options specified manually. A chap right here in India said he'd seen on some forum that while MDV Powerpack would connect with this card, the free version wouldn't. He couldn't remember which forum, or any other details. Know of any differences between the two which might be relevant?

John, under "Set up new network interface" I am given 7 choices, beginning with LAN and wireless. Then, as I say in post 91 above, I have the option to manually load a driver -- and after going in a circle, I end up there again. That is, I do not ever get to see the Net Device screen you have put up.

We may have it, Ian. As before, when I click on LAN, I get the single option "Manually Load Driver". Next I get to a list, from which I select 8139too. I have then to choose between "Autoprobe" and "Specify Options". So far I have been opting for "Autoprobe" -- and have been taken straight back to "Manually Load Driver". Now this may be the key: on choosing "Autoprobe" a notice comes up which says that while the thing usually works, the 8139too sometimes needs options specified. I chose "Specify Options" a while back to see what it was about, and was asked to fill in these fields, beginning each with "0x": debug multicast_filter_limit media full_duplex I have not the faintest idea what all this means, but it seems entirely possible that putting the right things into these fields will do the trick.

John, I have not so far installed any software other than packages which came on the three CDs (written from downloaded ISOs) of Mandriva 2006. I should imagine there won't be any kernel incompatibility problems. I was speaking of RPMs downloaded earlier, when I was on 10.1. As for the tarred stuff, I pulled it in because no RPMs were to be had. Before I install any of it, I shall check pbone for later versions. As it happens, only one tarred program has given me trouble -- and very little trouble. The service provider specified that I should have a LAN card installed, and its man who set up my connection brought along an ADSL modem. Before I installed 2006, I tried the ADSL option in 10.1. No damn good: I didn't have the information that was asked for. In Windows, from which I am now connecting, there is no mention of the ADSL fellow. So it's the LAN option or nothing.

Here goes, Ian. HardDrake said "Ethernetcard: (null)" and "Module: unknown". I backed up all the data I wanted to keep and then did a clean install. At the summary screen, when I tried to set up networking and Internet or whatever it was called, the "Manually install driver" screen came up. When I clicked on OK, I went straight out of Mandriva: that is, white text on a black ground. I went back in and set up one of my two printers and got the desktop to look something close to the way I like it. I'd asked for such of the software on the 3 CDs as I wanted to be installed. It shouldn't be a problem installing what I have in tar.gz form, but the RPMs I have are for 10.1 and probably will not fit in 2006. I deliberately did not go into networking because I feared crashing the machine again. It's almost 3 in the morning and I'm just too tired to go on. Will resume harassing you after I've had some sleep and put away a spot of breakfast.

I'll check, Ian, when I go into 2006. All I can say now is that eth0 shows up OK on booting. I shall have to do a clean install if I can't get the crazily scattered icons and program names on the desktop back into order. Maybe the LAN card trouble will magically go away then.

Anyone still here? Ian? Devries? I've downloaded 2006 and installed it over 10.1. Apart from the fact that the icons and program names are all over the place, not together, I'm faced with the same old problem: I go around in circles when I try to have my Ethernet card recognised.

Right, Ian, if the kernel source is OK, something else must be the matter. I shall of course do a clean install of 2006, when I do it. Don't like junk floating about, even if it does no harm Plenty of data on the Linux partition. All can be zipped and stashed in a Windows directory, but will take time and must be done systematically. The really important stuff is of course backed up on CD or on the two e-mail accounts I have just for this purpose. Thanks for everything. I'll be back, though, never fear.

What you say is correct, Ian, but as people grow older they become reluctant to learn new things for the reason that working with what they know already makes it possible to get more work done despite declining energy. Certain productivity becomes more attractive than the not so certain kind. But down to specifics. Here's what I got after urpme and urpmf. You'll see that my machine is not exactly new: a 1 GHz P3. [root@localhost albert]# uname -a Linux localhost 2.6.8.1-12mdk #1 Fri Oct 1 12:53:41 CEST 2004 i686 Pentium III (Coppermine) unknown GNU/Linux ----- [root@localhost albert]# ls -l /usr/src total 8 lrwxrwxrwx 1 root root 19 Mar 1 13:49 linux -> linux-2.6.8.1-12mdk/ drwxr-xr-x 21 root root 4096 Mar 1 13:48 linux-2.6.8.1-12mdk/ drwxr-xr-x 5 root root 4096 Oct 24 15:07 RPM/ ----- Make ran rapidly, saying things like "No member named driver_data" and ending with "Error 1". Make install ran (or did not run) as before. Does the stuff beginning with "total 8" say what source is installed or what is merely present in the machine? I ask because the urpmf command brought in an RPM file. I cannot find it. In the linux sub-dir under usr/src/linux there is a README which sets out how the source is to be compiled and installed. By the way, I've begun again to download the first of the three ISOs of 2006. Expect to get each in rather over 20 hours. My experience of buying the things has not been good. People claim to want no more than the cost of the media and postage; but I know what blank CDs and courier services cost, and there's no comparison. Besides, on two of three occasions I've been sent corrupted files.

Will do, Ian. If this doesn't work, I stick my tail between my legs and scurry away. A question, really, of how far one is prepared to go. I have a working connection on one side and I can manage with it. If getting to connect on the other side takes so much time and effort that I can't use the machine for its regular work, not worth the bother.

Negative, Ian. See what I had all ready to send you: * uname -a gave 2.6.8.1-12mdk * ls -l /usr/src gave total 4 drwxr-xr-x 5 root root 4096 ..<date>.. RPM/ * urpmi kernel-source asked for CD3 but did not give any options. It installed 2.4.27-0.pre2.1mdk. * In the Makefile, I put in 2.4.27-0.pre2.1mdk in place of the example. You had said nothing specific, only that /usr/src/linux on your machine pointed to a particular directory. On mine, it pointed to what I put in. * Make gave warnings or reported errors such as "will break strict-aliasing rules", "use of compound values ... deprecated", "unused variable 'ret'". * Make install simply said: "No rule to make target 'install'. Stop." The kernel version and the kernel source are obviously different. I cannot say what is the cause of this. Perhaps I downloaded an update from the Internet at some time. Nor do I understand this "rule" business. Life is a glob of well masticated bubble gum and I am at the centre of it. Maybe I should give up. Do all my Net stuff from Windows for the present. After all, I can pull files from there into Mandrake and put in others. Don't have the time, energy or inclination now to do a fresh install of 2006.

Right, Ian, will do. There's no question of downloading from the Internet, of course, since the problem is how to connect to the Internet. I have only the install CDs.

"No" is what I keep it set to, Ian, because it has this way of saying, "New hardware detected. Confirm clutch cable or shutter blinds."

File sent, Ian. What you say about P&P is not entirely clear to me, since "the other option" is used twice and I can't make out which is which. Went into the BIOS a while back. At "Plug and Play OS Installed?" there was a "No". I changed that to a "Yes", but it could be that that's the opposite of what you said I should do.

Even more lost in the maze. The "PM" button is *above* the monkey, not below. When I clicked it, I got the impression that I was sending a message not to you but to myself. So clicked ianw1974 and sent message from there. Seemed to me I could have attached the file as well. Anyhow, if you don't get the message, I'm payasam@ricmail.com. Mail checker means no fear of spam.

I do wish, Ian, that you'd keep your tongue in the right place, emoticonally speaking. I'm lost. I thought the 8139too *was* the network card. Will look into the BIOS matter. Now to figure out how to PM you.

Does the output of ifup eth0 tell you anything? As for the driver, it comes with a readme which speaks of putting things into the makefile, about locations and paths, and so on. All beyond me. Is there any way I can send you the quite small zip file so you make sense of it? OK to call you Ian rather than Ianw, which seems somehow improbable? And by the way, if 1974 represents year of arrival on planet, this joker you're helping is two dozen years older than you. Never easy to guide the senile.

Here we are: /sbin/ifup: line1: CODE: command not found /bin/true 8139too device eth0 does not seem to be present, delaying initialization ------- The "does not seem to be present" bit is exactly what I got earlier. You think it might help to put in a driver? I have two. The one which came with the card has one corrupted TXT file, so there's a chance that the other files in the package too are broken. The other one seems clean, but I don't know what to do about the Makefile.

Will need to get out of Windows and into Linux before I can do that. In the mean time, here's some stuff which may or may not tell you something. * Added a line each to modprobe.preload and modprobe.conf. I had added these earlier as well but had then removed them. * Added the four dhcp lines to ifcfg-eth0. These too had been added earlier. When they did nothing, I replaced them with the entries of your file. When that did nothing, I disabled the file. * An interactive reboot gave - network parameters Yes - loopback interface Yes - interface eth0 Failed (No other “failed”) * Without changing anything, I did a modprobe 8139too, following which ifconfig -a gave much the same output as before. * Another interactive reboot was the same as the one above, with these added - udev Yes - iptables Yes That is to say, interface eth0 was again marked “Failed”.

I added the lines long ago, Ianw, as you said I should. See post 50 for what ifconfig -a gave me after I did that. All the same, I get the "not present" message.

Ianw, from post 54: 'Then the second. On re-booting, a terrifying red "Failed" and "8139too does not seem to be present". ' MDK said this, not I. I see no evidence, as you do, that 8139too is loading. I meant that I first tried the DHCP option in an ifcfg-eth0 file and then yours.