Re: [opensuse] (kinda SOLVED) Re: router DHCP suddenly not talking to one machine (10.1)
- From: Carlos F Lange <carlos.lange@xxxxxxxxxxx>
- Date: Wed, 6 Jun 2007 12:15:13 -0600
On Wed June 6 2007 08:43, james wright wrote:
On Tuesday 05 June 2007 02:46:36 pm Eberhard Roloff wrote:
I once experienced the exact same problem. For the heart of it I
could not find out why it did not work in Linux while it worked in
Windows and did work in Linux, before. (it was a dlink-530, I
believe).
What made it work in Linux:
1. Take out the board
2. Start Linux with no network card installed and delete anything
that might have been left over (I did that in yast)
3. Start Linux, once again and see, whether there REALLY is NO
network card detected and no remaining settings.
4. install the card physically, once again
5. Fire up Linux and let it autodetect the network card.
I cannot guarantee anything, but it did the trick for me.
If anything else fails I would install a different network card and
see, how this works. After all, network boards for desktop usage
nowadays are a commoditiy, more or less.
kind regards
Eberhard
The above is probably your best bet, especially if the card was setup
in Linux before Windows. If you set it up in Linux first, then in
Windows, there is a high chance that the NIC ROM got flashed with an
update. This could have come from the Windows installation software,
Windows Update may have changed something, or you may have flashed
the card on you own accord. If the above suggestion does not work, I
would exchange that card for a known working card from one of your
other machines, and see if that works out. In general, I would set
up hardware in Windows first, if using a dual boot machine. That way
any changes that Windows makes to the hardware will occur before
setting up the same hardware in Linux.
- James W
The "new" card is an onboard card that was not being used. So I
performed step 1 above by disabling it in the BIOS. Then step 2 and 3,
deleting contents
of /etc/resolv.conf, /etc/HOSTNAME, /etc/sysconfig/network/routes and
the old entries in /etc/udev/rules.d/30-net_persistent_names.rules
Then re-enabled the card (step 4) and set it up with Yast, but the same
problem persisted. Since it was already set in Windows this time, the
NIC ROM should be stable now. I may have missed some config file I
needed to clean, but I needed to move on, so I placed back the old NIC,
deleted the onboard card and now Windows and Linux are happily using
that card and the router serves up the same IP address to each.
So, in a sense I did not figure out and solve the problem with that NIC,
but this allows me to continue without bother.
Thanks for all the help,
Carlos FL
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- References:
- [opensuse] router DHCP suddenly not talking to one machine (10.1)
- From: Carlos F Lange
- [opensuse] Re: router DHCP suddenly not talking to one machine (10.1)
- From: Eberhard Roloff
- Re: [opensuse] Re: router DHCP suddenly not talking to one machine (10.1)
- From: james wright
- [opensuse] router DHCP suddenly not talking to one machine (10.1)
- Prev by Date: [opensuse] Mount ISO as user
- Next by Date: Re: [opensuse] router DHCP suddenly not talking to one machine (10.1)
- Previous by thread: Re: [opensuse] Re: router DHCP suddenly not talking to one machine (10.1)
- Next by thread: [opensuse] Troubles with Ati / Xen / OpenSuse 10.2
- Index(es):
Relevant Pages
|