<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 10/04/2012 10:03 PM, Michael Stauber wrote:
<blockquote cite="mid:506E4DE6.6070606@blueonyx.it" type="cite">
<pre wrap="">Hi Jeff,
</pre>
<blockquote type="cite">
<pre wrap="">Removed the old udev device mapping file
Modified grub.conf to have biosdevname=0 at the end of the kernel line
Rebooted
Both interfaces came up (although reverse of <b>before - pci card is now LAN, and built-in is WAN</b>), however, I am still getting swatch errors:
Very interesting these 'improvements' after upgrade to SL 6.3
</pre>
</blockquote>
<pre wrap="">
Yeah, the new UDEV behaviour with the rules is already bad enough. The
"biosdevname" crap just makes it worse. I wish hardware makers like Dell
would do what they do best and stay away from meddling with things on
the OS level.
</pre>
<blockquote type="cite">
<pre wrap="">/usr/sausalito/swatch/bin/am_network.sh: line 64: [: too many arguments
</pre>
</blockquote>
<pre wrap="">
Please post the result of this command:
/sbin/route -n
It may shed some light on the issue.
</pre>
</blockquote>
I posted a few days ago "Re: eth0 issues"<br>
the procedure there worked for me on three different servers <br>
But, then I guess you don't want to try it,<br>
<br>
the problem is that just changing the HWADDR on an interface<br>
does not allow the low level functions to work correctly, thus you
get errors.<br>
Particularly where you have the scenario above <br>
<br>
<pre wrap=""><b>before - pci card is now LAN, and built-in is WAN
</b></pre>
<div class="moz-signature">-- <br>
Gerald<br>
<br>
</div>
</body>
</html>