This may not help much but...

I'm guessing you installed off CDs/DVD?  If so, it may be that although the system recognises that you have a 5752 chip it can't drive it because the tg3 driver doesn't support it - thus it wasn't configured.  There are various notes (google) that indicate problems for and kernel patches needed to get the 5752 working.  It's possible these are not in the 'Upstream Vendor's' kernel yet (don't have a SL4.3 system to hand to check).   I've seen similar behaviour with newer Intel Pci-E chips.   So if you do hand config the ifcfg-eth0 file, it may not work.

Of course if you installed of the net using the 5752 interface then I can't explain why the install didn't configure it.

M.


-- 
  Martin Bly    |   RAL Tier1 Systems Team
  T: +44|0 1235 446981 F: +44|0 1235 446626 

> -----Original Message-----
> From: [log in to unmask] 
> [mailto:[log in to unmask]] On 
> Behalf Of Lucian Stroe
> Sent: Wednesday, May 17, 2006 10:02 PM
> To: [log in to unmask]; Luke Scharf
> Cc: Lucian Stroe
> Subject: Re: network card and display problems
> 
> On Wed, 17 May 2006 16:53:59 -0400, Luke Scharf 
> <[log in to unmask]> wrot
> e:
> 
> >Lucian Stroe wrote:
> >
> >>> This implies that the eth0 interface was never 
> configured. The file
> >>>
> >>>/etc/sysconfig/network-scripts/ifcfg-eth0 needs to exist before a 
> >>>"activate" will work.
> >>>
> >>>
> >>
> >>I can understand this, but it looks more as an explanation than a 
> >>solut
> io
> >>n
> >>for solving the problem. So, what I have to do?
> >>
> >>
> >The hard-core way:
> >
> ># nano /etc/sysconfig/network-scripts/ifcfg-eth0
> >
> >
> >Or, if you like vi:
> >
> ># vi /etc/sysconfig/network-scripts/ifcfg-eth0
> >
> >And set the appropriate variables in the file.  I often use examples 
> >from other machines for this.  This is a very flexible way 
> to configure 
> >the NIC.
> >
> >The easy way (console):
> >
> ># /usr/sbin/netconfig
> >
> >
> >And then follow the prompts.  This is very easy and fast; I 
> use it when 
> >I'm setting up a workstation with a vanilla IP 
> configuration, where all 
> >I need is a static-IP or a DHCP configuration.  It's not so good for 
> >unusual, multi-NIC,  or multi-homed configurations -- but, how often 
> >does one do those things?
> >
> >The GUI way:
> >
> >$ system-config-network
> >
> >I don't configure networks with the GUI.  I've opened the GUI tool a 
> >couple of times, and it looks like it works at least as well as 
> >/usr/sbin/netconfitg -- but I prefer to have the fundamentals 
> >configured
> 
> >before I have to face a graphical desktop.  Just my personal peeves, 
> >mind you -- it's your system, and you can do it your way!
> >
> 
> Do you mean, essentially, that I have to set the IP number, 
> the gateway, the DNS and so on? But this was already done 
> during the installation... Why should I repeat it?
> 
> Lucian.
>