LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Red Hat (https://www.linuxquestions.org/questions/red-hat-31/)
-   -   Onboard Ethernet has no power or not recognized (https://www.linuxquestions.org/questions/red-hat-31/onboard-ethernet-has-no-power-or-not-recognized-728158/)

graphic 05-24-2009 08:26 AM

SOLVED: Onboard Ethernet has no power or not recognized
 
SOLVED

Let me start by saying I believe the motherboard is the culprit. It is an XFX nForce 750a SLI board and has given me problems with other Linux distributions before.

Background Information:
I've recently downloaded ClarkConnect (It is derived from RHEL) and have a hodgepodge hardware I'm going to use to replace my wireless router which recently bit the dust. I know its probably easier to buy a new router - I don't want to do that. I successfully configured this hardware with Ubuntu as a wireless router but feel that ClarkConnect is a far better solution.

Other problems I've overcome that may be related:
With other distributions of Linux (and ClarkConnect) I've had to add pci=nomsi as a kernel parameter in order for my hard-drive (SATA) to be recognized both during installation and boot-up (I believe the hard-drive was not being supplied power somehow or its power had been turned off).

Detailed description of the issue:
With ClarkConnect I see that the onboard Ethernet port is off and the only devices that are shown with ifconfig are eth0 (PCI card) and the loopback. Other devices (onboard video, sound, etc) may also not be functioning, but I haven't concerned myself with them. I've been able to get the output of lspci, the interface is shown as "Marvell Technology Grp 88E8856 PCI-E Gigabit (rev14)"

Any help you could provide would be greatly appreciated, thanks in advance!

irishbitte 05-25-2009 06:42 PM

So far as I know, ClarkConnect should handle that card. May I suggest SME-SERVER, I found it far better than ClarkConnect, and it's built using CentOS, a derivative of RHEL.

graphic 05-26-2009 01:11 PM

Solution
 
The problem was with the driver being used with the device, I believe its known as Sky2. Boot up message showed something along the lines of "sky2 device not found". This driver did not function properly with my set up (I think it is known to have bugs), I downloaded this driver from the manufacture which has a nice little install script and everything. The kernel version I installed on is 2.6.18 the version of ClarkConnect I installed on was 92.cc4 (Version 4.1). ClarkConnect, again, is based on RHEL.


All times are GMT -5. The time now is 08:37 PM.