Yes, power cycling solves it. I figures that out after I sent my previous
email. I think I'll save the 20 bucks and just write a small script to fix
it on boot. It is just a test workstation.
Thanks for the explanation.
------Original Message------
From: Ian Pratt
To: Mike Brancato
To: xen-users@xxxxxxxxxxxxxxxxxxx
Cc: ian.pratt@xxxxxxxxxxxx
Sent: Dec 30, 2005 2:06 PM
Subject: RE: [Xen-users] mac issue with network-bridge? xen-3.0.0-src
XenSource
 
> So 
> it looks like one of the scripts actually changed the MAC 
> address on my physical adapter to FE:FF:FF:FF:FF:FF. Now it 
> is detected as that on boot from the kernel (xen and non-xen).
>
> [4294678.281000] eth0: ADMtek Comet rev 17 at 0001d400, 
> FE:FF:FF:FF:FF:FF, IRQ 19.
Have you tried power cycling the machine? That may restore the old
address.
I've had a look at the tulip driver, and the AMDtek Comet is treated
differnetly from all other tulip-type cards in that the driver appears
not to read the MAC address from an eeprom. This probably saves 20 cents
or something. Amazing.
I think you'll enjoy your xen experience rather better if you spend
twenty bucks on a ethernet card...
Best,
Ian
--
Michael Brancato, CISSP, CCNA
Assistant Division Network Manager
Affiliated Computer Services, Inc.
--------------------------
Sent from my BlackBerry Wireless Handheld
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users