[ECOS] Processor Issue with i386/Redboot?

Michael Trozzo mike@trozzo.net
Thu Oct 16 13:26:00 GMT 2003


Thanks for your help...here´s what I have:

P150 box: Allied Telesyn AT-2500TX Fast Ethernet (has an RTL8139 chip
onboard) 1.4 gig P3 box: 3com 3C920

Both are networked (along with the host machine) on a Netgear DS104
4-port hub.

I also have a spare Netgear FA311 lying around.

I've been doing some googling on this, and believe that I can use the NS
DP83902A package for the RTL8139 chip. 

Here´s what´s currently happening:
When I boot with the P3 box, the boot message and prompt come up on
screen. When I boot with the P150 box, I only get the series of dots on
that box's monitor; however, when I'm connected with HyperTerminal
through COM1 from my laptop, I see the boot message and prompt.

The next problem is this:
When I´ve attempted to ping (using EITHER box), I only end up getting
gibberish characters on screen and more are added every time I press any
key. Here is what happens on screen:

With P150 box (note: I took out the Intel 82559 package and added the NS
DP83902A package here):

+No network interfaces found

RedBoot(tm) bootstrap and debug environment [FLOPPY]

Non-certified release, version v2_0 - built 14:14:45, Oct 16 2003

Platform: PC (I386)
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x000a0000, 0x00087e50-0x000a0000 available
RedBoot> ping -v -n 3 -h
Network PING - from to

With 1.4G P3 box:

+Non-CDROM ATAPI device #1 - skipped                                    
No network interfaces found                           

RedBoot(tm) bootstrap and debug environment [FLOPPY]

Non-certified release, version v2_0 - built 23:09:29, Oct 15 2003

Platform: PC (I386)                   
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RedBoot> ping -v -n 3 -h
Network PING - from to

One concern is that both say "from".  I have the default IP set
as, and "Do not try to use BOOTP" is checked.  I also
noticed that I was able to add and remove the relevant Ethernet packages
through ecosconfig, but not through the configuration tool GUI. 


-----Original Message-----
From: kevin_lemay@agilent.com [mailto:kevin_lemay@agilent.com] 
Sent: Mittwoch, 15. Oktober 2003 20:34
To: trozzo@arcor.de
Subject: RE: [ECOS] Processor Issue with i386/Redboot?


What kind of network interface card do you have on both systems?

The redboot image is built with a single ethernet driver (intel 825xx).
Perhaps this stops it from booting.

I have only used Pentium III and Xeons here.


-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Michael
Sent: Wednesday, October 15, 2003 11:26 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Processor Issue with i386/Redboot?


I wrote last week about my problems creating a floppy boot image, and
have fortunately managed to work it out. Apparently, the dd command
doesn´t like it when you try to output to a network share...either that
or use rawrite (thanks, Denis).

Anyway, onto the next step of my journey.  I attempted to boot through
the floppy on a pentium 150, with the floppy set as first in the boot
sequence.  It appears not to be completing the boot process. I get a
series of dots on the screen, then a blinking cursor. After that stops,
nothing else happens.  I´ve tested this box with a Win98 boot floppy,
the Windows CDROM, and on the hard drive (which had been freshly
formatted before installing 98), and everything boots up normally. 

I then attempted to boot on a 1.4 GHz Pentium III with thw same floppy,
and after a few seconds, I got the RedBoot welcome message on screen.
Does anyone know why this would be happening? I´d really like to avoid
having to use the PIII box, since my wife uses that for her work, and
obviously my having Redboot up would take her out of action.

Mike Trozzo

Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

More information about the Ecos-discuss mailing list