Re: network boot

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

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Kyle Kienapfel
Sent: Monday, January 11, 2010 12:10 PM
To: Spooner, Darren
Cc: Joshua Oreman; [email protected]
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 <[email protected]> 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:[email protected]]
> Sent: Monday, January 11, 2010 8:58 AM
> To: Spooner, Darren
> Cc: Kyle Kienapfel; [email protected]
> Subject: Re: [Etherboot-discuss] network boot
>
> On Mon, Jan 11, 2010 at 9:44 AM, Spooner, Darren 
> <[email protected]> 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 <[email protected]>, 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
>

------------------------------------------------------------------------------
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