VanCutsem, Geoffroy <geoffroy.vancutsem@...> writes:

> 
> Hi Shy,
> 
> > -----Original Message-----
> > From: meego-ivi-bounces@... [mailto:meego-ivi-
> > bounces@...] On Behalf Of shylock_1
> > Sent: Wednesday, October 12, 2011 10:56 AM
> > To: meego-ivi@...
> > Subject: [MeeGo-ivi] Shifting ... MAC addresses.
> > 
> > Intel's Starter kit on Intel's Atom Processor E660 (Tunnel Creek)
> > family
> > operating with 1.3 GHz clock speed with 512K cache in 32bit mode with
> > max
> > threads 2. CPU operates under 32bit instructions code with embedded
> > options
> > available.
> > 
> >  Brookville Rev A2 surf board with AGP6063 chip set duel screen
> > support.
> 
> Is this the kit based on the ConneXt chip?
> 
> > 
> > Currently I am using MeeGo OS which is based Open Linux Image 2.6.37.2-
> > 12.1.
> > 
> > My immediate problem is to cope with continuously shifting MAC address
> > on the
> > Atom Processor board, every time, I reset (switch ON/OFF) to the board
> > I get
> > completely NEW MAC  address; hence, therefore, I cannot USE to setup or
> > get
> > booted from the PXE server aka (TFT). I need  to boot this starter kit
> > with
> > similar Kernel 2.6.37 from the server  just to test application and
> > indeed set
> > up development, testing and debugging environment for further
> > development.
> 
> As far as I know, it is not possible to boot this board via PXE (I'm talking
about the board based on Tunnel
> Creek + ConneXt chip). I believe this is a limitation because there is no
OpROM on the board that would
> typically be used to store the PXE agent.
> 
> > 
> > The idea is to develop application software and modify existing device
> > driver(s)
> > on development machine and setup testing and debugging on the Intels'
> > Starter
> > Kit surf board.
> > 
> > IS there anybody who knew how to restrict, or stop these behaviour of
> > changing
> > MAC address of this board, when it get booted with Meego OS?
> 
> I have written a small script (very basic) that can do this at boot time. Here
is how you can set it up so that
> it's automatically done at boot time (you must be root to do this) (using the
macaddr script file attached)
> 
> - cp macaddr /usr/sbin/
> - chmod +x /usr/sbin/macaddr
> Edit /etc/rc.d/rc.local and add the following lines at the end of it
>       # Set the MAC address to a fixed value
>       /usr/sbin/macaddr Crossville0 &
> Important note: that may not be sufficient to get you the same IP address
every time since putting this in
> rc.local means it runs after connmand has been started and the interface may
already have an IP address
> then. An potential solution to this would be to put these lines in
/etc/rc.d/rc.sysinit just before
> connmand gets started. If you do that, you would have to remove the ampersand
as well which means the boot
> time will be affected by roughly 2x $delay (delay is currently set to 2sec in
the script)
> 
> I guess a proper fix for this would be to modify the driver so it can take a
MAC address as an argument when it's loaded.
> 
> > 
> > It also appears to me that the board completely isolated from the mains
> > power
> > supply for more than two hour it loose it BIOS setting including system
> > Date and
> > Time that ultimatly affect a real-time clock and require recalibration
> > of system
> > time and other parameters at BIOS level.
> > 
> > I understood a successful TFT boot operation to initiate on board to
> > its boot
> > process  from remote; require fix MAC address on post booting on board
> > currently
> > I cannot achive, I wonder at Intel some body knew? Cause I can see
> > during the
> > BIOS setup following
> > 
> > 
> > 
> > In the BIOS set up screen AMI Bios  OPTIONS  "Main -- Advance --
> > Chipset --
> > Boot --  Security --  Save & Exit"  options exist  Choosing an option
> > "Advance"
> > gives an option of
> > 
> > "Launch PXE OpROM"  ---> Enabled
> > 
> > 
> > The details explanation read "Enable or Disable Boot Option for Legacy
> > Network
> > Device".
> > 
> > Thanks
> > 
> > Shy
> > 
> > _______________________________________________
> > MeeGo-ivi mailing list
> > MeeGo-ivi@...
> > http://lists.meego.com/listinfo/meego-ivi
> Intel Corporation NV/SA
> Kings Square, Veldkant 31
> 2550 Kontich
> RPM (Bruxelles) 0415.497.718. 
> Citibank, Brussels, account 570/1031255/09
> 
> This e-mail and any attachments may contain confidential material for the sole
use of the intended
> recipient(s). Any review or distribution by others is strictly prohibited. If
you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> Attachment (macaddr): application/octet-stream, 1076 bytes
> 
> _______________________________________________
> MeeGo-ivi mailing list
> MeeGo-ivi@...
> http://lists.meego.com/listinfo/meego-ivi
> 

Hi Geoffroy,

You have identified the board correctly It is blue box from Intel read IVI
Starter kit Which is made by Brookvile and Crossville chip set. The interesting
thing is 

In the BIOS set up screen AMI Bios offer following OPTIONS  "Main -- Advance --
Chipset -- Boot --  Security --  Save & Exit"  
options exist  Choosing an option  "Advance"
 gives an option of
 
 "Launch PXE OpROM"  ---> Enabled
 
 
 The details explanation read "Enable or Disable Boot Option for Legacy
 Network  Device".

It clearly offer option Launch PXE OpROM Enabled/disabled option.

I wonder doe it work? Cause using the macaddr utility is much later stage as
board get booted and kernel, drivers already loaded into RAM then script could
be executed forwarding "Crossvill0 &" to the utility macaddr. These mac address
will come in affect after board already been BOOTED.

It simply mean LINUX GRUB loaded and kernel loaded. I want to initiate process
before than loading kernel into boards memory.

I am sure you understand my point?

Thank you,

Shy



_______________________________________________
MeeGo-ivi mailing list
[email protected]
http://lists.meego.com/listinfo/meego-ivi

Reply via email to