[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: a newbie....... i guess
- From: rdlong <rdlong kent edu>
- To: redhat-install-list redhat com
- Subject: RE: a newbie....... i guess
- Date: Sun, 30 Jun 2002 11:18:03 -0400
i dont get any errors the NIC just fails to intiate at boot it always prints
FAILED in red
the NIC is a NetGear FA 310tx. could the issue be caused by the NIC?
>===== Original Message From redhat-install-list redhat com =====
>On Sat, 29 Jun 2002 22:56:14 -0400
>rdlong <rdlong kent edu> wrote:
>
>> ive been using redhat for some time now, but now i am at home trying
>> to get online. my parents use MSN for an internet provider and im
>> trying to get my linux box online. i have Internet Connection Sharing
>> set up on the WinXP box (my parents) and the two computers connected
>> via crossover cable. i am having some troubles getting eth0 to work
>> the way i want it to half the time it doesnt even initialize. im
>> trying the card in another pci slot with a fresh install of redhat
>> 7.1. can anyone give me any advice as to where i may be going wrong?
>> -ralph
>
>Card? Errors when it fails? Does the connection always work when the NIC
>runs fine, or does it sometimes fail?
>
>I had a few problems with NICS before that I was able to solve using one
>or more of these methods (make sure network is turned off using ntsysv
>as root before trying either of these):
>
>1. Shut down, remove NIC, boot and remove networking. Shut down and
>install NIC, then boot and install networking.
>
>This method solved my problems every time except one release (I don't
>remember if it was 7.0 or 7.1).
>
>Anyway, once you confirm this works with a reboot, as root turn network
>back on via ntsysv.
>
>2. Once networking is off, try booting with the board still in. As root
>type:
>
>modprobe <module_name>
>
>For instance, if the board you use uses the tulip.o module:
>
>modprobe tulip
>
>If no errors, type:
>
>depmod -a
>/sbin/service network start
>
>Check to see if the networking was brought up properly by using
>ifconfig. If it does, you're at least partway there. Turn networking
>back on via ntsysv as root. Then reboot and see if it brings it all up
>properly.
>
>3. This is a modified version of 2, and should be used if it still fails
>to come up. After the 'modprobe' command, still as root, edit
>/etc/rc.d/rc.local and put lines similar to the following at the end of
>it:
>
>insmod <module_name>
>/sbin/service network start
>
>Once you've determined that this works after rebooting, you can add the
>following to the end of either or both lines to suppress output:
>
>> /dev/null 2>&1
>
>OR
>
>> /dev/null > /dev/null
>
>As in:
>
>insmod <module_name> > /dev/null 2>&1
>
>In all instances, insert the actual name of the module for <module_name>
>leaving off the .o on the end.
>
>--
>If Bill Gates had a dime for every time a Windows box crashed...
>..Oh, wait a minute, he already does.
>
>
>
>_______________________________________________
>Redhat-install-list mailing list
>Redhat-install-list redhat com
>https://listman.redhat.com/mailman/listinfo/redhat-install-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]