Bug#45694: marked as done (install woes on MVME162FX)
Your message dated Fri, 22 Oct 1999 23:40:52 +0100
with message-id <002501bf1cde$88015790$0101a8c0@deadleg.lan>
and subject line Fw: Bug#47225: MVME162FX Rescue Disc Boot fails
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 21 Sep 1999 20:14:04 +0000
Received: (qmail 31998 invoked from network); 21 Sep 1999 20:14:04 -0000
Received: from unknown (HELO itexchsrv2.phx.mcd.mot.com) (144.191.82.17)
by master.debian.org with SMTP; 21 Sep 1999 20:14:03 -0000
Received: by itexchsrv2.phx.mcd.mot.com with Internet Mail Service (5.5.2580.0)
id <TF1H5KHB>; Tue, 21 Sep 1999 13:16:21 -0700
Message-ID: <2B0D01F974CBD211B9150000F8085A1E0237C024@itexchsrv2.phx.mcd.mot.com>
From: Dennen Bill-G15128 <bill_dennen@mcg.mot.com>
To: "'submit@bugs.debian.org'" <submit@bugs.debian.org>
Subject: install woes on MVME162FX
Date: Tue, 21 Sep 1999 13:16:20 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2580.0)
Content-Type: text/plain;
charset="iso-8859-1"
Package: unknown
Version: latest
Attempting to install m68kLinux on an MVME162FX, have CDs. Using an MVME167
running R3v8 as
the server. i162 hangs (see below for console log), appears to be a double
bus fault as RUN is solid yellow and ABORT will not dump. Note that
tftplilo.conf was modified to specify path to files as Unix
being used as host apparently requires an absolute path to be supplied ...
Copyright Motorola Inc. 1988 - 1993, All Rights Reserved
MVME162 Debugger/Diagnostics Release Version 2.1 - 10/19/93
COLD Start
Local Memory Found =01000000 (&16777216)
MPU Clock Speed =33Mhz
162-Bug>cnfg
Board (PWA) Serial Number = "1828927 "
Board Identifier = "MVME162-513 "
Artwork (PWA) Identifier = "01-W3960B01C "
MPU Clock Speed = "3300"
Ethernet Address = 08003E234CE7
Local SCSI Identifier = "07"
Parity Memory Mezzanine Artwork (PWA) Identifier = "N/A "
Parity Memory Mezzanine (PWA) Serial Number = "N/A "
Static Memory Mezzanine Artwork (PWA) Identifier = "N/A "
Static Memory Mezzanine (PWA) Serial Number = "N/A "
ECC Memory Mezzanine #1 Artwork (PWA) Identifier = "N/A "
ECC Memory Mezzanine #1 (PWA) Serial Number = "N/A "
ECC Memory Mezzanine #2 Artwork (PWA) Identifier = "N/A "
ECC Memory Mezzanine #2 (PWA) Serial Number = "N/A "
Serial Port 2 Personality Artwork (PWA) Identifier = "N/A "
Serial Port 2 Personality Module (PWA) Serial Number = "N/A "
Industry Pack A Board Identifier = "N/A "
Industry Pack A (PWA) Serial Number = "N/A? "
Industry Pack A Artwork (PWA) Identifier = "N/A "
Industry Pack B Board Identifier = "N/A "
Industry Pack B (PWA) Serial Number = "N/A "
Industry Pack B Artwork (PWA) Identifier = "N/A "
Industry Pack C Board Identifier = "N/A "
Industry Pack C (PWA) Serial Number = "N/A "
Industry Pack C Artwork (PWA) Identifier = "N/A "
Industry Pack D Board Identifier = "N/A "
Industry Pack D (PWA) Serial Number = "N/A "
Industry Pack D Artwork (PWA) Identifier = "N/A "
162-Bug>nbo
Network Booting from: VME162, Controller 0, Device 0
Loading: /usr/linux/m68kLinux/tftplilo.mvme
Client IP Address = 172.27.197.40
Server IP Address = 172.27.197.11
Gateway IP Address = 0.0.0.0
Subnet IP Address Mask = 255.255.255.0
Boot File Name = /usr/linux/m68kLinux/tftplilo.mvme
Argument File Name = /usr/linux/m68kLinux/tftplilo.conf
Network Boot File load in progress... To abort hit <BREAK>
Bytes Received =&30964, Bytes Loaded =&30964
Bytes/Second =&30964, Elapsed Time =1 Second(s)
Motorola MVME TFTP Linux Loader V1.0.0
Loading configuration data from '/usr/linux/m68kLinux/tftplilo.conf' ...
Boot configurations:
*Debian-Install-BVME4000/6000 i6000
Debian-Install-MVME162 i162
Debian-Install-MVME166/167 i167
Boot-BVME4000/6000 b6000
Boot-MVME166/167 b167
Boot-MVME162 b162
LILO Boot: i162
Loading kernel '/usr/linux/m68kLinux/linuxmvme162' ...
Loading ramdisk '/usr/linux/m68kLinux/rootmvme.bin' ...
Kernel has no bootinfo version info, assuming 1.0
Bootstrap's bootinfo version : 2.0
Kernel's bootinfo version : 1.0
(using backwards compatibility mode)
[ board now hung ... ]
Regards
>@<
Bill Dennen bowtie@mclean.mcd.mot.com | We
have met the enemy
District Sales Technical Support (703) 714-0707 | and
they is us ...
Motorola Computer Group (703) 714-0714 FAX | Pogo
---------------------------------------
Received: (at 45694-done) by bugs.debian.org; 22 Oct 1999 22:46:13 +0000
Received: (qmail 31649 invoked from network); 22 Oct 1999 22:46:13 -0000
Received: from mail1.svr.pol.co.uk (195.92.193.18)
by master.debian.org with SMTP; 22 Oct 1999 22:46:13 -0000
Received: from modem-9.name57.dialup.pol.co.uk
([62.136.188.9] helo=slug.deadleg.lan ident=mail)
by mail1.svr.pol.co.uk with esmtp (Exim 2.12 #2)
id 11enRT-0006Sb-00; Fri, 22 Oct 1999 23:45:54 +0100
Received: from master.deadleg.lan (master) [192.168.1.1]
by slug.deadleg.lan with smtp (Exim 3.03 #1 (Debian))
id 11enNs-00042I-00; Fri, 22 Oct 1999 23:42:04 +0100
Message-ID: <002501bf1cde$88015790$0101a8c0@deadleg.lan>
From: "Nick Holgate" <holgate@debian.org>
To: <47225-done@bugs.debian.org>,
<45694-done@bugs.debian.org>
Subject: Fw: Bug#47225: MVME162FX Rescue Disc Boot fails
Date: Fri, 22 Oct 1999 23:40:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
----- Original Message -----
From: Dennen Bill-G15128 <bill_dennen@mcg.mot.com>
To: 'Nick Holgate' <holgate@debian.org>
Sent: 19 October 1999 16:40
Subject: RE: Bug#47225: MVME162FX Rescue Disc Boot fails
> Well well well - yet another feature of our boards that I wasn't aware of
> ...
>
> Now that's fixed and working I find that fdisk doesn't recognize the
system
> I'm working on; appears from poking around that vme cards, as opposed to
> macs and amigas and their ilk, have to use an NFS file system. For my
> purposes that's ndg but I'll see if I can get around it by first building
on
> an NFS partition then rebuilding on the local disk.
>
> Thanks for you help
> Regards
> >@<
> Bill Dennen bowtie@mclean.mcd.mot.com
> <mailto:bowtie@mclean.mcd.mot.com> | We have met the
> District Systems Engineer (703) 714-0707 |
> enemy & they is us
> Motorola Computer Group (703) 714-0714 (FAX) | Pogo
>
>
> -----Original Message-----
> From: Nick Holgate [mailto:holgate@debian.org]
> Sent: Friday, October 15, 1999 3:59 AM
> To: Dennen Bill-G15128; 45694@bugs.debian.org;
> 47225@bugs.debian.org
> Subject: RE: Bug#47225: MVME162FX Rescue Disc Boot
> fails
>
>
> Bill,
>
> > I figured the boot disk was not according to Hoyle when I
> read
> > more of your previous Email. Had a chance to fiddle
> around last night and
> > I'm suspecting the boot process. The image on the CD,
> the image at the
> > debian server, and the image on the floppy are all
> identical. SCSI
> floppies
> > have always been weird on these machines and I suspect
> that is where my
> > grief -- the format is not right. I've been creating the
> floppies on my
> PC
> > and/or a PowerStack running AIX. Identical results.
> Grumble grumble
> >
> > Regarding 45694, I understand what you're saying its just
> I haven't a clue
> > how to adjust the workspace without recompiling Bug
> source. You mentioned
> > you had a 167 set appropriately. Could you send the env
> settings
> > from it -- perhaps I can glean it from there. Boards I've
> been using have
> > been set to factory defaults.
>
> The address of the Bug workspace RAM is configured with a
> jumper refer to:
> http://www.mcg.mot.com/literature/PDFLibrary/PDF/162bug.pdf
> page 1-7 for
> more info.
>
>
> Nick
>
> ---------------------------------------------
> Nick Holgate <holgate@debian.org>
> PGP key from public servers : Key ID DF3E8223
>
>
Reply to: