[3282] in SIPB_Linux_Development
Re: more 3c90x boot disk take 2
daemon@ATHENA.MIT.EDU (Derek Atkins)
Sat Jan 6 16:24:35 2001
To: seph <seph@MIT.EDU>
Cc: linux-dev@MIT.EDU
From: Derek Atkins <warlord@MIT.EDU>
Date: 06 Jan 2001 16:24:33 -0500
In-Reply-To: seph's message of "Sat, 06 Jan 2001 15:07:33 -0500"
Message-Id: <sjmr92gpe5q.fsf@rcn.ihtfp.org>
seph <seph@MIT.EDU> writes:
> you're makefile basicly does:
> make-boots: update-loader
> ./mkboot -f $(IMAGES)
>
> it does not do a mkinitrd. anyhow, the update-loader taget is fine
I don't need to do it, because mkboot runs it:
./mkinitrd network -f
> and "./mkboot -f network" produces an "incorrect usage" error
> message. and mkbot runs mkinitrd, I don't think it really needs to be
> run twice.
Huh? It used to work for me. Are you root when you run the command?
> > 2) We should verify what the PCI data is for their network
> > card; It appears there is an entry for the 3c905C-TX at
> > 0x10b7 0x9200 which refers to the 3c59x driver; I don't
> > know if this should be changed to the 3c90x driver. It's
> > possible that this "new" card has different PCI info.
>
> I took my pcitable info straight from ..//anaconda/kudzu/pcitable,
> which would appear to be redhat's stuff. I would guess that the
> installer uses it to tell what driver goes with what, so we could try
> forcing more things to use the 3c90x driver. but I'm not sure it's needed.
Yes, I believe the pcitable is used to determine what driver to use
based upon the PCI ID of the device.
> cfox> I tried seph's boot floppy image on snork. If I select "3Com
> cfox> 3c590/3c595 Vortex", it punts me back to the "what boot media" screen,
> cfox> with "error 2 reading header: Success" at the bottom of it.
Ok, this error is coming from isys/uncpio.c in the function
myCpioInstallArchive(). The error 2 is CPIOERR_BAD_MAGIC, which means
that the cpio archive doesn't have the right header. In particular,
the physical header doesn't have the magic string "070701" or
"070702". I think this is because the loader wants an ASCII cpio
archive (SVR4 with CRC), rather than a regular cpio archive.
To tell you the truth, I don't know how to generate the ASCII cpio
format with CRC. I think you need to use "cpio --format crc" to
generate the modules archive. That should solve this problem :)
> the "3Com 3c590/3c595 Vortex" is the 3c59x driver, sp that might have
> been the problem the new driver is current called "3Com 3c509[bc]
> Vortex" yes, I see the typo, if it works, we can pretty easily change
> the description.
I suppose I still don't understand why the installer is asking for a
network card. Last time I tried it it autodetected the card and
jumped straight to asking me my IP Address.
> alex tested the boot disk, and got the same error on both snork and a
> cluster machine, using either of the drivers. so I dunno...
Try rebuilding the modules file as I mentioned above...
> seph
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord@MIT.EDU PGP key available
