Thanks for your input.
I have remove the debug=X options in the options of the tulip driver and this has fixed the problem. Why it has already worked with the debug option the first time and now it does not, I do not know. However, now the network interface is working just fine! Cheers. ABrady <[EMAIL PROTECTED]> writes: > On 07 Jan 2002 09:07:17 -0500 > Dominic Mitchell <[EMAIL PROTECTED]> implied: > > > > > Hi, > > > > On a fresh install of RH7.2 I can't do "modprobe tulip" to load > > the driver need by my network card. > > > > This is the second time I do this fresh install on the same > > machine. A win9x application messed the partition table ... > > > > In /etc/modules.conf I have the lines > > > > alias tulip eth0 > > options tulip options=0 debug=1 > > > > > > which had worked previously. > > > > If I do > > > > insmod tulip > > /sbin/ifup eth0 > > > > I have no problem to bring up eth0. > > > > However, at boot time, the system stops booting at the network > > steps. I have to enter the boot process interactively and answer > > no for the network. > > > > Then I have to do > > > > insmod tulip > > /sbin/ifup eth0 > > > > How can I fix this issue? Oh yes, I have ran "depmod -a". > > You can shut down, remove the board, boot, remove networking, shutdown, > insert the board, boot and configure networking. Might work, might not. > Has worked for me many times, but not the current. > > Alternative: add lines to /etc/rc.local (or create a script for you) > that first insmods the driver, then brings up networking, then brings up > everything else that depends on networking. That has always worked for > me and is what I'm currently using until I get over my laziness and fix > the problem. > > To use the second choice, run ntsysv (as root) and tunr off networking > and anything else that needs it (telnet, mail, samba, etc). Then add > lines at the end of /etc/rc.local to take care of it all. I have that > and the first line is /sbin/rmmod <driver? with the second as > /sbin/insmod <driver>. I do it that way so I can let networking try > normally and fail (for when I get around to fixing it). After all of > that I start the other stuff. Here's what mine currently looks like: > > service network stop > /dev/null 2>&1 > rmmod ne2k-pci > /dev/null 2>&1 > rmmod 3c59x > /dev/null 2>&1 > insmod 3c59x /dev/null 2>&1 > insmod ne2k-pci /dev/null 2>&1 > service network start > service xinetd start > service bastille-firewall start > /dev/null 2>&1 > service smb start > service squid start > service dansguardian start > service httpd start > service lpd start > service ntpd start > service pure-ftpd start > service exim start > service webmin start > service portsentry start > service hostsentry start > /usr/local/bin/dns2go > /dev/null 2>&1 > > Based on what I said, if you don't start networking, there's no need to > stop it first. I'd do the rmmod/insmod part just to make sure you don't > error out. All of the ' > /dev/null 2>&1' stuff is to suppress output on > those lines. I keep the others reporting so I can see that everything is > okey-dokey. > > It's a kludge, and some people would prefer to make an initscript to do > the same thing. Others would spend a lot of time fixing it. I do what I > do because I can. It's one option that I know works. I'll get around to > fixing it on or before the next distro upgrade. -- Dominic Mitchell _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
