Ethernet not working under SUSE 10.1

I have a dual-boot SUSE 10.1 / Windows system. The Ethernet connection
works fine under Windows, but fails under SUSE 10.1.

I suspect the issue has something to do with the way DHCP is assigning an
IP. Router is 192.168.1.1 and DHCP correctly returns 192.168.1.102 under
Windows, but (oddly enough) DHCP returns 169.254.38.51 under SUSE.

Have played around with various DHCP settings and pinged my SUSE from
another computer to no avail. However, when I downgrade to SUSE 9.1 I can
get the NIC working.

Would appreciate any advise so I can finally dump Windows.

brian.james@ngc.com wrote:
> I have a dual-boot SUSE 10.1 / Windows system. The Ethernet connection
> works fine under Windows, but fails under SUSE 10.1.
>
> I suspect the issue has something to do with the way DHCP is assigning an
> IP. Router is 192.168.1.1 and DHCP correctly returns 192.168.1.102 under
> Windows, but (oddly enough) DHCP returns 169.254.38.51 under SUSE.
>
> Have played around with various DHCP settings and pinged my SUSE from
> another computer to no avail. However, when I downgrade to SUSE 9.1 I can
> get the NIC working.
>
> Would appreciate any advise so I can finally dump Windows.
>
>
Crystal ball is a bit cloudy here

Can we have some hardware details, in particular what nic?

Clive Eisen schrieb:
> brian.james@ngc.com wrote:
>> I have a dual-boot SUSE 10.1 / Windows system. The Ethernet connection
>> works fine under Windows, but fails under SUSE 10.1.
>>
>> I suspect the issue has something to do with the way DHCP is assigning an
>> IP. Router is 192.168.1.1 and DHCP correctly returns 192.168.1.102 under
>> Windows, but (oddly enough) DHCP returns 169.254.38.51 under SUSE.
>>
>> Have played around with various DHCP settings and pinged my SUSE from
>> another computer to no avail. However, when I downgrade to SUSE 9.1 I can
>> get the NIC working.
>>
>> Would appreciate any advise so I can finally dump Windows.
>>
>>
> Crystal ball is a bit cloudy here
>
> Can we have some hardware details, in particular what nic?
Are you uptodate with the updates ?

There was a bug in some conditions with DHCP servers and hostnames.

André

In article <PWeSg.1500$0h7.133@prv-forum2.provo.novell.com>, wrote:
> but (oddly enough) DHCP returns 169.254.38.51 under SUSE.
>
That's a self-assigned address, meaning that the machine was not able
to get an address from a DHCP server. You might try removing and
reinstalling your NIC in Yast.

bd
NSC Volunteer SysOp

Brian,

some onboard NICs only work if you completely power off the machine (i.e. switch of the PSU) before you boot.
Basically I'm with Clive, we need more info.

Uwe


--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

brian.james@ngc.com wrote on 26.09.2006 21:10:
> I have a dual-boot SUSE 10.1 / Windows system. The Ethernet connection works fine under Windows, but fails under SUSE 10.1.

Does it work when you boot into Windows and then do a warm boot into
Linux? I heard that some NIC drivers are reverse engineered and do not
initialize all registers. If you boot Windows the manufacturer's driver
initializes everything currently and if you are lucky the values aren't
lost during reboot.


> I suspect the issue has something to do with the way DHCP

Does the Ethernet connection work if you use a fixed IP address?


> Would appreciate any advise so I can finally dump Windows.

Is the NIC the only show stopper? Have you been lucky with other
hardware like sound card, 3D graphics card, on-board RAID controller,
printer, scanner, ... Have you found Linux equivalents for all software
you use under Windows, or at least all the software you really need? Did
the other software for which no Linux equivalent exists run under Wine?
I'm interested in your experiences, no matter if they were good or bad.

Christian