From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16288 invoked by alias); 16 Oct 2003 13:26:25 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 16277 invoked from network); 16 Oct 2003 13:26:22 -0000 Received: from unknown (HELO moutng.kundenserver.de) (212.227.126.184) by sources.redhat.com with SMTP; 16 Oct 2003 13:26:22 -0000 Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1AA890-0008Dv-00 for ecos-discuss@sources.redhat.com; Thu, 16 Oct 2003 15:26:22 +0200 Received: from [80.142.230.145] (helo=LAPTOP) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1AA88z-0003FV-00 for ecos-discuss@sources.redhat.com; Thu, 16 Oct 2003 15:26:21 +0200 From: "Michael Trozzo" To: Date: Thu, 16 Oct 2003 13:26:00 -0000 Message-ID: <001601c393e9$1d76bdd0$0c00a8c0@LAPTOP> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: RE: [ECOS] Processor Issue with i386/Redboot? X-SW-Source: 2003-10/txt/msg00304.txt.bz2 Kevin, Thanks for your help...here=B4s 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.=20 Here=B4s what=B4s 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=B4ve 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 192.168.0.12 Network PING - from 0.0.0.0 to 192.168.0.12 $T0b08:ffffffff;04:6c9d0100;#c3$T0b08:ffffffff;04:6c9d0100;#c3$T0b08:fff fffff;04 :6c9d0100;#c3 With 1.4G P3 box: +Non-CDROM ATAPI device #1 - skipped=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 No network interfaces found=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20 RedBoot(tm) bootstrap and debug environment [FLOPPY] Non-certified release, version v2_0 - built 23:09:29, Oct 15 2003 Platform: PC (I386)=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 Copyright (C) 2000, 2001, 2002, Red Hat, Inc. RedBoot> ping -v -n 3 -h 192.168.0.12 Network PING - from 0.0.0.0 to 192.168.0.12 $T0408:ffffffff;04:6c9d0100;#95$T0408:ffffffff;04:6c9d0100;#95$T0408:fff fffff;04 :6c9d0100;#95$T0408:ffffffff;04:6c9d0100;#95$T0408:ffffffff;04:6c9d0100; #95$T040 8:ffffffff;04:6c9d0100;#95$T0408:ffffffff;04:6c9d0100;#95$T0408:ffffffff ;04:6c9d 0100;#95$T0408:ffffffff;04:6c9d0100;#95 One concern is that both say "from 0.0.0.0". I have the default IP set as 192.168.0.10, 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.=20 Mike -----Original Message----- From: kevin_lemay@agilent.com [mailto:kevin_lemay@agilent.com]=20 Sent: Mittwoch, 15. Oktober 2003 20:34 To: trozzo@arcor.de Subject: RE: [ECOS] Processor Issue with i386/Redboot? Mike, 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. Kevin -----Original Message----- From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Michael Trozzo Sent: Wednesday, October 15, 2003 11:26 AM To: ecos-discuss@sources.redhat.com Subject: [ECOS] Processor Issue with i386/Redboot? Hi, 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=B4t 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=B4ve 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.=20 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=B4d 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