[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: netboot alpha

On Wed, May 12, 2004 at 09:38:27AM +0200, Benoit Peccatte wrote:
> Le mer 12/05/2004 à 05:00, Steve Langasek a écrit :
> > On Tue, May 11, 2004 at 10:59:25PM +0200, Benoit wrote:
> > > Does it mean the initrd is too big ?
> > 
> > What command did you give to SRM to tell it to netboot?  The aboot
> > options built into the image are correct for the size of the initrd; you
> > may want to try booting with 'boot ewa0 -fl ""' to avoid passing
> > any options to aboot that would override this.

> Thank you, that was it.

> Now I've got a networkcard problem, but I think it's kernel specific.
> The chipset is a DEC21040, the tulip driver doesn't choose the right
> media type and I don't know how to specify it.

The text description of the driver options in the kernel's tulip_core.c
are as follows:

/*  The possible media types that can be set in options[] are: */
const char * const medianame[32] = {
        "10baseT", "10base2", "AUI", "100baseTx",
        "10baseT-FDX", "100baseTx-FDX", "100baseT4", "100baseFx",
        "100baseFx-FDX", "MII 10baseT", "MII 10baseT-FDX", "MII",
        "10baseT(forced)", "MII 100baseTx", "MII 100baseTx-FDX", "MII 100baseT4",
        "MII 100baseFx-HDX", "MII 100baseFx-FDX", "Home-PNA 1Mbps", "Invalid-19",
        "","","","", "","","","",  "","","","Transceiver reset",

So to specify 10baseT, you would pass "options=0" as an argument to
insmod; "options=1" for 10base2; etc.  However, please note that there
are other outstanding issues with many tulip chips under recent alpha
kernels, so depending on the chip you have, even passing the module
arguments may not solve your problem here.

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: