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

Bug#133793: marked as done (Bug Report Installing Alpha with Aspen Alpine Board)

Your message dated 09 Apr 2002 10:08:59 -0400
with message-id <oaadsd55hg.fsf@arroz.onshored.com>
and subject line closing old boot-floppies potato bugs 
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.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 13 Feb 2002 16:48:23 +0000
>From D.Guenther@suss.de Wed Feb 13 10:48:23 2002
Return-path: <D.Guenther@suss.de>
Received: from (majestix.suss.de) [] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16b2Zy-0002h8-00; Wed, 13 Feb 2002 10:48:22 -0600
Received: by majestix with Internet Mail Service (5.5.2650.21)
	id <15V7SCR0>; Wed, 13 Feb 2002 17:47:59 +0100
Message-ID: <DA92AF8A1AF4D4119D600090272769070AC885@majestix>
From: "Guenther, Daniel" <D.Guenther@suss.de>
To: "'Debian Bugs (E-Mail)'" <submit@bugs.debian.org>
Subject: Bug Report Installing Alpha with Aspen Alpine Board
Date: Wed, 13 Feb 2002 17:47:58 +0100
X-Mailer: Internet Mail Service (5.5.2650.21)
Delivered-To: submit@bugs.debian.org

Package: boot-floppies


I got ISO-Images of debian 2.2r5 stable for our noname alpha. As you can
see, I boot from CD. I tried it with floppy, too, and got the same problem.
Description: after loading Milo and entering:
MILO>  boot scd0:/boot/linux root=/dev/scd0 load_ramdisk=1
a endless loop start with following message:

device_interrupt: illegal interrupt 3?

the "?" stands for "I don't know what number", because it could be 36, 37,
38, 39 or whatever else, it's scrolling too fast for my eyes. But it's
shure, that this are two digits. B

Then I can only reboot the machine, and then I have to do all the settings
in the firmware again, from ground up. I have to set the default environment
variables and the default configuration of the machine's firmware.

I choose eb64p because on the Aspen Homepage they told to use eb64, but I
only found eb64p.

greetings + thank's for reading


More data of this system below.

Settings in Boot-Manager:

Architecture: Alpha
Board: Aspen Alpine with ARC

Alpha Firmware Version 4.35
Copyright 1993 Microsoft Corp.
copyright 1993 digital Equipment corp., copyright 1994 Aspen Systems Inc.

Processor ID: 21064
Processer Revision: 3
System Revision: 0x1
Processor Speed: 274.95 Mhz
Physical Memory: 128 MB
Backup Cache Size: 2 MB

Extended Firmware Information:
Version: 4.35 950614.1315
NVRAM Environment Usage: 15 %
(462 of 3052 bytes)

Video Option detected:
BIOS controlled video card

Devices detected by the firmware:

multi(0)disk(0)fdisk(0)	(Removable)
scsi(0)disk(1)rdisk(0)	(1 Partition) QUANTUM XP39100S	LXY4
scsi(0)disk(2)rdisk(0) 	(1 Partition) QUANTUM XP39100S	LXY4
scsi(0)cdrom(5)fdisk(0)	(Removable) TOSHIBA CD-ROM XM-3701TA0236

PCI slot information:

SCSI: Bus=0, Virtual Slot=5, Function=0, Vendor=1000, Device=1, Revision=1
Ethernet, Bus=0, Virtual Slot=7, Function=0, Vendor=1011, Device=9,
ISA bridge, Bus=0, Virtual Slot=8, Function=0, Vendor=8086, Device=484,
VGA: Bus=0, Virtual Slot=9, Function=0, Vendor=5333, Device=8811, Revision=0

Output of MILO with "show devices"
MILO (EB64+)
Built against Linux version 2.0.35
Device drivers:
SCSI (NCR (ncr53c8xx), Qlogic ISP, Buslogic, AHA2940UW
Memory size is 128 MBytes
fd (0200)     sd (0800)     sr (0B00)
sda: sda1 sda5    sdb: sdb1  sdb5
File systems:
ext2 iso9660 msdos

Output of MILO with "pci"
PCI devices found:
Bus 0, device 9, function 0:
VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 0)
Medium devsel. IRQ 22.
Non-prefetchable 32 bit memory at 0x4800000

Bus 0, device 8, function 0:
Non-VGA device: Intel 82378IB (rev 67).
medium devsel. Master Capable. No bursts.

Bus 0, device 7, function 0:
Ethernet controller: DEC DC21140 (rev 32).
Medium devsel. Fast back-to-back capable. IRQ 17. Master Capable.
Latency=32. Min Gnt=20.Max Lat=40.
I/O at 0x8000
Non-prefetchable 32 bit memory at 0x5000000.

Bus 0, device 5, function 0:
Non-VGA device: NCR 53c810 (rev 1).
Medium devsel . IRQ 23. Master Capable. Latency=32.
I/O at 0x8800.
Non-prefetchable 32 bit memory at 0x5001000.

Received: (at 133793-done) by bugs.debian.org; 9 Apr 2002 14:08:54 +0000
>From adam@onshore-devel.com Tue Apr 09 09:08:54 2002
Return-path: <adam@onshore-devel.com>
Received: from arroz.onshored.com [] (postfix)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16uwIo-0004Sz-00; Tue, 09 Apr 2002 09:08:54 -0500
Received: from arroz.onshored.com (localhost [])
	by arroz.onshored.com (Postfix) with ESMTP
	id 3B8449404B; Tue,  9 Apr 2002 10:09:01 -0400 (EDT)
Sender: adam@arroz.onshored.com
To: 128054-done@bugs.debian.org, 116411-done@bugs.debian.org,
	129854-done@bugs.debian.org, 129421-done@bugs.debian.org,
	131371-done@bugs.debian.org, 133040-done@bugs.debian.org,
	133570-done@bugs.debian.org, 133793-done@bugs.debian.org
Subject: closing old boot-floppies potato bugs 
Organization: onShore Development, Inc
From: Adam Di Carlo <adam@onshore-devel.com>
Date: 09 Apr 2002 10:08:59 -0400
Message-ID: <oaadsd55hg.fsf@arroz.onshored.com>
Lines: 24
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 133793-done@bugs.debian.org

The problem you reported was in the Potato (Debian 2.2) version of the
boot-floppies package.  This package has been improved for the
upcoming Woody release, and we believe this issue is closed -- or, at
worst, we have no data that this bug still exists in Woody.

We accumulate a lot of bugs in the boot-floppies package, so in the
interest of trying to identify bugs which can be fixed, we are closing
out stale bugs.

We encourage you to test with the Woody boot-floppies, versions 3.0.22
or later.  If you have problems in booting, you should make sure you
are booting with the right subarch or flavor, and if you are, figure
out which kernel-image-2.* package is responsible for the kernel on
those disks.  Then file the bug against the kernel-image-2.* package.
If you can't figure out the right package, it's fine to just file it
against boot-floppies, or ask us to reopen the bug we closed.

We apologize (in some cases) that we were not able to find a solution
earlier.  We hope you do not feel that we ignored your bug, and that
you help make sure the Debian woody release is as good as it can be.

...Adam Di Carlo..<adam@onshore-devel.com>...<URL:http://www.onshored.com/>

To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: