Etherboot

Email Archive: etherboot-discuss (read-only)

Re: [Etherboot-discuss] network boot

From: Spooner, Darren <darren.spooner@ma...> - 2010-01-12 19:49

Ok I was not Safely Removing the hardware, so I redid the usb drive and
then I put it in an old Dell GX260 and it worked.

But for the computers in the cars it did not work, I am thing the BISO
does not support it

What do you think?

 

 

From: Shao Miller [mailto:Shao.Miller@...] 
Sent: Tuesday, January 12, 2010 10:10 AM
To: Spooner, Darren
Cc: etherboot-discuss@...
Subject: Re: [Etherboot-discuss] network boot

 

Spooner, Darren wrote: 

gpxe-0.9.9+-gpxe.usb is the name of the file I downloaded off
rom-o-matic.


Sounds good.  If you write this file to your USB "stick" and flush all
write buffers before removing ("Safely Remove Hardware" in Windows),
then you can boot the USB "stick" on the police car's computer.  To
confirm that gPXE supports the NIC on the computer, press Control-B at
the Control-B prompt, then at the gPXE CLI, enter:

ifstat

where you will see just which network interfaces gPXE supports.  Of
course, in a police car, your wired NIC might not be wired to anything!
Joshua Oreman already spoke about wireless options.

Good luck!

- Shao Miller

Thread View

Thread	Author	Date
[Etherboot-discuss] network boot	Spooner, Darren <darren.spooner@ma...>

Re: [Etherboot-discuss] network boot

From: Kyle Kienapfel <kyle@sh...> - 2010-01-10 18:58

gpxe can be booted off of a usb stick, r-o-m will even cough up an
image with all the wired network drivers

http://www.rom-o-matic.net/ This site will give you a gpxe.usb file if
you dont want to download and compile gpxe yourself.
Give this a read - http://etherboot.org/wiki/removable



On Sun, Jan 10, 2010 at 6:55 AM, Spooner, Darren
<darren.spooner@...> wrote:
> Hello,
> This is what I have: I have a "Windows Deployment Server" and I have customized it to include "Parted Magic", so I can boot into WDS or Parted Magic.
> I also have 50 workstations in police cars, all have wireless and wired cards. the wired cards are not PXE enabled.
> so how do I create a USB stick so I can boot into the network?
>
> Darren
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Etherboot-discuss mailing list
> Etherboot-discuss@...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>

Re: [Etherboot-discuss] network boot

From: Spooner, Darren <darren.spooner@ma...> - 2010-01-11 14:45

Ok I got that to work, but I turns out that my nics are not supported
Is there a way someone can develop dirvers for the intel pro 1000 MT
and/or intel pro wireless 2915abg?
And put them on the rom-o-matic site?



-----Original Message-----
From: doctor.whom@... [mailto:doctor.whom@...] On Behalf Of
Kyle Kienapfel
Sent: Sunday, January 10, 2010 12:58 PM
To: Spooner, Darren
Cc: etherboot-discuss@...
Subject: Re: [Etherboot-discuss] network boot

gpxe can be booted off of a usb stick, r-o-m will even cough up an
image with all the wired network drivers

http://www.rom-o-matic.net/ This site will give you a gpxe.usb file if
you dont want to download and compile gpxe yourself.
Give this a read - http://etherboot.org/wiki/removable



On Sun, Jan 10, 2010 at 6:55 AM, Spooner, Darren
<darren.spooner@...> wrote:
> Hello,
> This is what I have: I have a "Windows Deployment Server" and I have
customized it to include "Parted Magic", so I can boot into WDS or
Parted Magic.
> I also have 50 workstations in police cars, all have wireless and
wired cards. the wired cards are not PXE enabled.
> so how do I create a USB stick so I can boot into the network?
>
> Darren
>
>
------------------------------------------------------------------------
------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast
and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Etherboot-discuss mailing list
> Etherboot-discuss@...
> https://lists.sourceforge.net/lists/listinfo/etherboot-discuss
>

Re: [Etherboot-discuss] network boot

From: Joshua Oreman <oremanj@rw...> - 2010-01-11 14:58

On Mon, Jan 11, 2010 at 9:44 AM, Spooner, Darren
<darren.spooner@...> wrote:
> Ok I got that to work, but I turns out that my nics are not supported

I'm sorry to hear that. It would be useful to have the exact
vendor:device PCI IDs for the NICs you're trying to get working
(available in Device Manager under Windows, or the output of `lspci
-nn' under Linux), so that we can pinpoint which drivers are missing.

> Is there a way someone can develop dirvers for the intel pro 1000 MT
> and/or intel pro wireless 2915abg?
> And put them on the rom-o-matic site?

Drivers do not develop out of thin air. Wireless drivers especially
take a week or two of solid effort, even for someone who's done a lot
of them before.

If you are so inclined, you might consider learning the necessary
skills to develop a driver or drivers yourself; there are several
useful resources on http://etherboot.org/. If not, there are some very
skilled people in our community who do gPXE driver development under
contract. Our project leader, Marty Connor <mdc@...>, is one
and can refer you to others.

Otherwise, this is a volunteer project for all of us, and
unfortunately we can't take a week or two away from our jobs to
develop something for free. We do this because we enjoy it. Drivers
for those two types of cards will probably come about eventually if
you wait, but I can't estimate as to when.

Thanks for your interest,

-- Josh

Re: [Etherboot-discuss] network boot

From: Spooner, Darren <darren.spooner@ma...> - 2010-01-11 15:49

Intel Pro 1000 MT
Device instance ID:
PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00\4&1A671D0C&0&38F0

Hardware IDs: 	PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00
		PCI\VEN_8086&DEV_1076&SUBSYS_10768086
		PCI\VEN_8086&DEV_1076&CC_020000
		PCI\VEN_8086&DEV_1076&CC_0200

Compatible IDs: PCI\VEN_8086&DEV_1076&REV_00
		PCI\VEN_8086&DEV_1076
		PCI\VEN_8086&CC_020000
		PCI\VEN_8086&CC_0200
		PCI\VEN_8086
		PCI\CC_020000
		PCI\CC_0200

Intel Pro/wireless 2915abg
Device instance ID:
PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05\4&1A671D0C&0&70F0

Hardware IDs: 	PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05
		PCI\VEN_8086&DEV_4223&SUBSYS_10008086
		PCI\VEN_8086&DEV_4223&CC_028000
		PCI\VEN_8086&DEV_4223&CC_0280

Compatible IDs: PCI\VEN_8086&DEV_4223&REV_05
		PCI\VEN_8086&DEV_4223
		PCI\VEN_8086&CC_028000
		PCI\VEN_8086&CC_0280
		PCI\VEN_8086
		PCI\CC_028000
		PCI\CC_0280

I did not know which one so I posted all of them.

-----Original Message-----
From: Joshua Oreman [mailto:oremanj@...] 
Sent: Monday, January 11, 2010 8:58 AM
To: Spooner, Darren
Cc: Kyle Kienapfel; etherboot-discuss@...
Subject: Re: [Etherboot-discuss] network boot

On Mon, Jan 11, 2010 at 9:44 AM, Spooner, Darren
<darren.spooner@...> wrote:
> Ok I got that to work, but I turns out that my nics are not supported

I'm sorry to hear that. It would be useful to have the exact
vendor:device PCI IDs for the NICs you're trying to get working
(available in Device Manager under Windows, or the output of `lspci -nn'
under Linux), so that we can pinpoint which drivers are missing.

> Is there a way someone can develop dirvers for the intel pro 1000 MT 
> and/or intel pro wireless 2915abg?
> And put them on the rom-o-matic site?

Drivers do not develop out of thin air. Wireless drivers especially take
a week or two of solid effort, even for someone who's done a lot of them
before.

If you are so inclined, you might consider learning the necessary skills
to develop a driver or drivers yourself; there are several useful
resources on http://etherboot.org/. If not, there are some very skilled
people in our community who do gPXE driver development under contract.
Our project leader, Marty Connor <mdc@...>, is one and can
refer you to others.

Otherwise, this is a volunteer project for all of us, and unfortunately
we can't take a week or two away from our jobs to develop something for
free. We do this because we enjoy it. Drivers for those two types of
cards will probably come about eventually if you wait, but I can't
estimate as to when.

Thanks for your interest,

-- Josh

Re: [Etherboot-discuss] network boot

From: Kyle Kienapfel <kyle@sh...> - 2010-01-11 18:10

Intel Pro 1000 MT
PCI\VEN_8086&DEV_1076
vendor 8086
device 1076

PCI VENDOR CODE:  8086    PCI DEVICE CODE:  1076
I just successfully got a bootrom from rom o matic for the wired
adaptor so it should be supported. Whats the name of the file you
downloaded off of rom-o-matic?

Intel Pro/wireless 2915abg
PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05
Vendor ID 8086 and the device ID is 4223
so vendor:device is 8086:4223


On Mon, Jan 11, 2010 at 7:49 AM, Spooner, Darren
<darren.spooner@...> wrote:
> Intel Pro 1000 MT
> Device instance ID:
> PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00\4&1A671D0C&0&38F0
>
> Hardware IDs:   PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00
>                PCI\VEN_8086&DEV_1076&SUBSYS_10768086
>                PCI\VEN_8086&DEV_1076&CC_020000
>                PCI\VEN_8086&DEV_1076&CC_0200
>
> Compatible IDs: PCI\VEN_8086&DEV_1076&REV_00
>                PCI\VEN_8086&DEV_1076
>                PCI\VEN_8086&CC_020000
>                PCI\VEN_8086&CC_0200
>                PCI\VEN_8086
>                PCI\CC_020000
>                PCI\CC_0200
>
> Intel Pro/wireless 2915abg
> Device instance ID:
> PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05\4&1A671D0C&0&70F0
>
> Hardware IDs:   PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05
>                PCI\VEN_8086&DEV_4223&SUBSYS_10008086
>                PCI\VEN_8086&DEV_4223&CC_028000
>                PCI\VEN_8086&DEV_4223&CC_0280
>
> Compatible IDs: PCI\VEN_8086&DEV_4223&REV_05
>                PCI\VEN_8086&DEV_4223
>                PCI\VEN_8086&CC_028000
>                PCI\VEN_8086&CC_0280
>                PCI\VEN_8086
>                PCI\CC_028000
>                PCI\CC_0280
>
> I did not know which one so I posted all of them.
>
> -----Original Message-----
> From: Joshua Oreman [mailto:oremanj@...]
> Sent: Monday, January 11, 2010 8:58 AM
> To: Spooner, Darren
> Cc: Kyle Kienapfel; etherboot-discuss@...
> Subject: Re: [Etherboot-discuss] network boot
>
> On Mon, Jan 11, 2010 at 9:44 AM, Spooner, Darren
> <darren.spooner@...> wrote:
>> Ok I got that to work, but I turns out that my nics are not supported
>
> I'm sorry to hear that. It would be useful to have the exact
> vendor:device PCI IDs for the NICs you're trying to get working
> (available in Device Manager under Windows, or the output of `lspci -nn'
> under Linux), so that we can pinpoint which drivers are missing.
>
>> Is there a way someone can develop dirvers for the intel pro 1000 MT
>> and/or intel pro wireless 2915abg?
>> And put them on the rom-o-matic site?
>
> Drivers do not develop out of thin air. Wireless drivers especially take
> a week or two of solid effort, even for someone who's done a lot of them
> before.
>
> If you are so inclined, you might consider learning the necessary skills
> to develop a driver or drivers yourself; there are several useful
> resources on http://etherboot.org/. If not, there are some very skilled
> people in our community who do gPXE driver development under contract.
> Our project leader, Marty Connor <mdc@...>, is one and can
> refer you to others.
>
> Otherwise, this is a volunteer project for all of us, and unfortunately
> we can't take a week or two away from our jobs to develop something for
> free. We do this because we enjoy it. Drivers for those two types of
> cards will probably come about eventually if you wait, but I can't
> estimate as to when.
>
> Thanks for your interest,
>
> -- Josh
>

Re: [Etherboot-discuss] network boot

From: Spooner, Darren <darren.spooner@ma...> - 2010-01-11 18:34

gpxe-0.9.9+-gpxe.usb is the name of the file I downloaded off rom-o-matic.

-----Original Message-----
From: doctor.whom@... [mailto:doctor.whom@...] On Behalf Of Kyle Kienapfel
Sent: Monday, January 11, 2010 12:10 PM
To: Spooner, Darren
Cc: Joshua Oreman; etherboot-discuss@...
Subject: Re: [Etherboot-discuss] network boot

Intel Pro 1000 MT
PCI\VEN_8086&DEV_1076
vendor 8086
device 1076

PCI VENDOR CODE:  8086    PCI DEVICE CODE:  1076
I just successfully got a bootrom from rom o matic for the wired adaptor so it should be supported. Whats the name of the file you downloaded off of rom-o-matic?

Intel Pro/wireless 2915abg
PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05
Vendor ID 8086 and the device ID is 4223 so vendor:device is 8086:4223


On Mon, Jan 11, 2010 at 7:49 AM, Spooner, Darren <darren.spooner@...> wrote:
> Intel Pro 1000 MT
> Device instance ID:
> PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00\4&1A671D0C&0&38F0
>
> Hardware IDs:   PCI\VEN_8086&DEV_1076&SUBSYS_10768086&REV_00
>                PCI\VEN_8086&DEV_1076&SUBSYS_10768086
>                PCI\VEN_8086&DEV_1076&CC_020000
>                PCI\VEN_8086&DEV_1076&CC_0200
>
> Compatible IDs: PCI\VEN_8086&DEV_1076&REV_00
>                PCI\VEN_8086&DEV_1076
>                PCI\VEN_8086&CC_020000
>                PCI\VEN_8086&CC_0200
>                PCI\VEN_8086
>                PCI\CC_020000
>                PCI\CC_0200
>
> Intel Pro/wireless 2915abg
> Device instance ID:
> PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05\4&1A671D0C&0&70F0
>
> Hardware IDs:   PCI\VEN_8086&DEV_4223&SUBSYS_10008086&REV_05
>                PCI\VEN_8086&DEV_4223&SUBSYS_10008086
>                PCI\VEN_8086&DEV_4223&CC_028000
>                PCI\VEN_8086&DEV_4223&CC_0280
>
> Compatible IDs: PCI\VEN_8086&DEV_4223&REV_05
>                PCI\VEN_8086&DEV_4223
>                PCI\VEN_8086&CC_028000
>                PCI\VEN_8086&CC_0280
>                PCI\VEN_8086
>                PCI\CC_028000
>                PCI\CC_0280
>
> I did not know which one so I posted all of them.
>
> -----Original Message-----
> From: Joshua Oreman [mailto:oremanj@...]
> Sent: Monday, January 11, 2010 8:58 AM
> To: Spooner, Darren
> Cc: Kyle Kienapfel; etherboot-discuss@...
> Subject: Re: [Etherboot-discuss] network boot
>
> On Mon, Jan 11, 2010 at 9:44 AM, Spooner, Darren 
> <darren.spooner@...> wrote:
>> Ok I got that to work, but I turns out that my nics are not supported
>
> I'm sorry to hear that. It would be useful to have the exact 
> vendor:device PCI IDs for the NICs you're trying to get working 
> (available in Device Manager under Windows, or the output of `lspci -nn'
> under Linux), so that we can pinpoint which drivers are missing.
>
>> Is there a way someone can develop dirvers for the intel pro 1000 MT 
>> and/or intel pro wireless 2915abg?
>> And put them on the rom-o-matic site?
>
> Drivers do not develop out of thin air. Wireless drivers especially 
> take a week or two of solid effort, even for someone who's done a lot 
> of them before.
>
> If you are so inclined, you might consider learning the necessary 
> skills to develop a driver or drivers yourself; there are several 
> useful resources on http://etherboot.org/. If not, there are some very 
> skilled people in our community who do gPXE driver development under contract.
> Our project leader, Marty Connor <mdc@...>, is one and can 
> refer you to others.
>
> Otherwise, this is a volunteer project for all of us, and 
> unfortunately we can't take a week or two away from our jobs to 
> develop something for free. We do this because we enjoy it. Drivers 
> for those two types of cards will probably come about eventually if 
> you wait, but I can't estimate as to when.
>
> Thanks for your interest,
>
> -- Josh
>

Re: [Etherboot-discuss] network boot

From: Shao Miller <Shao.Miller@yr...> - 2010-01-12 16:28

Attachments: Message as HTML

Spooner, Darren wrote:
>
> gpxe-0.9.9+-gpxe.usb is the name of the file I downloaded off rom-o-matic.
>

Sounds good.  If you write this file to your USB "stick" and flush all 
write buffers before removing ("Safely Remove Hardware" in Windows), 
then you can boot the USB "stick" on the police car's computer.  To 
confirm that gPXE supports the NIC on the computer, press Control-B at 
the Control-B prompt, then at the gPXE CLI, enter:

ifstat

where you will see just which network interfaces gPXE supports.  Of 
course, in a police car, your wired NIC might not be wired to anything!  
Joshua Oreman already spoke about wireless options.

Good luck!

- Shao Miller

Re: [Etherboot-discuss] network boot

From: Spooner, Darren <darren.spooner@ma...> - 2010-01-12 19:49

Attachments: Message as HTML

Ok I was not Safely Removing the hardware, so I redid the usb drive and
then I put it in an old Dell GX260 and it worked.

But for the computers in the cars it did not work, I am thing the BISO
does not support it

What do you think?

 

 

From: Shao Miller [mailto:Shao.Miller@...] 
Sent: Tuesday, January 12, 2010 10:10 AM
To: Spooner, Darren
Cc: etherboot-discuss@...
Subject: Re: [Etherboot-discuss] network boot

 

Spooner, Darren wrote: 

gpxe-0.9.9+-gpxe.usb is the name of the file I downloaded off
rom-o-matic.


Sounds good.  If you write this file to your USB "stick" and flush all
write buffers before removing ("Safely Remove Hardware" in Windows),
then you can boot the USB "stick" on the police car's computer.  To
confirm that gPXE supports the NIC on the computer, press Control-B at
the Control-B prompt, then at the gPXE CLI, enter:

ifstat

where you will see just which network interfaces gPXE supports.  Of
course, in a police car, your wired NIC might not be wired to anything!
Joshua Oreman already spoke about wireless options.

Good luck!

- Shao Miller

Re: [Etherboot-discuss] network boot

From: Shao Miller <Shao.Miller@yr...> - 2010-01-15 13:15

Attachments: Message as HTML

Spooner, Darren wrote:
>
> Ok I was not Safely Removing the hardware, so I redid the usb drive 
> and then I put it in an old Dell GX260 and it worked.
>
> But for the computers in the cars it did not work, I am thing the BISO 
> does not support it
>
> What do you think?
>

Which part did not work?  Did you see any interfaces from the 'ifstat' 
command in the cars?  Did you mean wireless wasn't working or wired 
wasn't working?  How do you know it didn't work?

- Shao Miller