ethernet boot problem

[mick12345678]

Just found this http://archives.mandrivalinux.com/cooker/2004-04/msg01515.php.
So now all I need to know is in which config file do  I need to add the line "MII_NOT_SUPPORTED "=yes".
I just reenabled ifplugd, edited rc.inet1.conf to include the above, and ....it didnt work 

Anyone know the correct file (the Mandrake one doesnt exist on VL5. ?

[rbistolfi]

rc.inet1.conf should be the equivalent of that file.

[mick12345678]

I have proven that ifplugd *is* reading my conf file, as, when I remove the "-s" option, I get messages in the log file once again.

I have tried putting the MII_NOT_SUPPORTED parameter in both rc.inet1.conf and in rc.inet1 but I don't think its being read, since, whether I have this parameter set to "yes" or "no", I get exactly the same result in the log :

Jul 17 20:27:34 test ifplugd(eth0)[2654]: ifplugd 0.28 initializing.
Jul 17 20:27:34 test ifplugd(eth0)[2654]: Using interface eth0/00:01:00:00:01:00 with driver <fealnx> (version: 2.51)
Jul 17 20:27:34 test ifplugd(eth0)[2654]: Using detection mode: SIOCETHTOOL
Jul 17 20:27:34 test ifplugd(eth0)[2654]: Initialization complete, link beat not detected.

[uelsk8s]

can you try opening a terminal  su ing to root and typing
"/etc/rc.d/rc.inet1 start"
and then
"ifconfig"

and post the results back here

[mick12345678]

gladly 

root:# /etc/rc.d/rc.inet1 start
Starting network eth0 using a DHCP server...
dhcpcd: MAC address = 00:01:00:00:01:00
dhcpcd: your IP address = 192.168.1.74
eth0      Link encap:Ethernet  HWaddr 00:01:00:00:01:00
          inet addr:192.168.1.74  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:113 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7349 (7.1 KiB)  TX bytes:1240 (1.2 KiB)
          Interrupt:11 Base address:0xc800

root:# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:01:00:00:01:00
          inet addr:192.168.1.74  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:118 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7649 (7.4 KiB)  TX bytes:1240 (1.2 KiB)
          Interrupt:11 Base address:0xc800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  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)

to clarify (even I'm getting confused by now  ), everything works ok when I manually start the card (as above). The problem is that I can't get ifplugd to start it for me 

[uelsk8s]

mick12345678,

After typing "/etc/rc.d/rc.inet1 start"
It looks like you have internet, do you?
If so just add "/etc/rc.d/rc.inet1 start" to the end of the /etc/rc.d/rc.local file and disable the ifplugd service and you should be good to go.
for some reason it looks like ifplugd is getting a "link beat not detected" even though its working and at that point it is probably shutting down eth0

HTH,
Uelsk8s

[mick12345678]

Thanks - that works fine and saves me the bother of typing in the cmd after every bootup

I would still like to get to the bottom of this, but maybe I should leave it at this point.
(I do have a floppy that came with the ethernet card and it includes a Linux driver - which has to be compiled. But that would probably just open up another can of worms  ).

[rbistolfi]

I would like to know the problem with ifplugd too!  You could try ifplugstatus with the network working.

[ekp]

I have problems booting ethernet as well.  I used to have a problem with the device changing names.  Solved with "how to" the "udev way".  Now I have a problem with saving boot options on reboot ie" starting eht0 with dhcp.  I have to reconfigure device every time to boot with dhcp.

[Joe1962]

Hmm... I've no idea how to help with this. I have never had a problem with ifplugd on either ethernet or wifi interfaces, in the quite a few laptops and desktops I've installed 5.8 on...

[uelsk8s]

the problem is not with ifplugd. the problem is with the way this driver works with this card, It does not detect the linkbeat properly without the "MII_NOT_SUPPORTED "=yes" added when it starts.
If ifplugd does not detect a network cable plugged in it doesnt start the network.

[rbistolfi]

the problem is not with ifplugd. the problem is with the way this driver works with this card, It does not detect the linkbeat properly without the "MII_NOT_SUPPORTED "=yes" added when it starts.
If ifplugd does not detect a network cable plugged in it doesnt start the network.

Exactly, the ifplugstratus command will tell you if ifplugd can detect your network. Other way to diagnose this, is running ifplugd with your network up, if it cant detect the linkbeat, will stop your network.

[scrambled_egg]

I had the same problem of not being able to start the network at boot up and having to use VASM to get it started.  After much research and experimentation I also reached the stage of successfully starting the network by manually running "/etc/rc.d/rc.inet1 start".  This implied that there was nothing wrong with the rc.inet1 script but rather it wasn't being called.  What I eventually found was that in my /etc/rc.d/rc.M file a large chunk of code which starts the network was commented out!  I don't know how or why this was so, but when I uncommented it the network started on the next reboot.  This makes sense as inspection of the code shows that /etc/rc.d/rc.inet is called for each network interface.  Hope this helps.

[Martin109]

I've found this very useful as a newbie (Vectorbie!), though  I haven't quite got it to work yet.  It does seem to hinge on the contents of rc.M, but I've noticed another problem I don't understand.  Is it OK to revive this thread... or should I start another one in Vectorbie Questions?

Someone will let me know!

When booting VL with my 3Com net adaptor plugged in, I notice that the green light comes on at the same point in the boot sequence each time, namely when the hardware is being initialised.  However, it goes off again later - I think when batch files (or their equivalent under Linux (scripts?)) are being processed.

Because it's gone off, I can't initialise the internet, manually or otherwise, until it comes on again, which it does, mysteriously, some time later, not in response to anything I seem to have done.  Then at last I can input (as root)  '/etc/rc.d/rc.inet1 start' or run VASM to get the internet connection running.

What are the commands which are running to turn the adapter on, then off?  How can I automate the first while preventing the second, as well as automating the internet connection?

[rbistolfi]

Maybe ifplugd is putting your network down because it can't detect the link. I would try disabling ifplugd, you can do it from VasmCC, Services, Services, Run Level of your choice (I would turn it off on all of them) and uncheck ifplugd.
Let us know how it goes.