Your message dated Thu, 17 Mar 2005 12:20:39 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#298595: it's a BIOS problem
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; 8 Mar 2005 18:32:12 +0000
>From [EMAIL PROTECTED] Tue Mar 08 10:32:11 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mxout2.netvision.net.il [194.90.9.21]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D8jV5-0007T8-00; Tue, 08 Mar 2005 10:32:11 -0800
Received: from Ilmarinen ([217.132.247.95]) by mxout2.netvision.net.il
(Sun Java System Messaging Server 6.1 HotFix 0.09 (built Dec 14 2004))
with ESMTP id <[EMAIL PROTECTED]> for
[EMAIL PROTECTED]; Tue, 08 Mar 2005 20:31:27 +0200 (IST)
Received: from vassilii by Ilmarinen with local (Exim 4.44)
id 1D8jUH-0001Rs-Tj for [EMAIL PROTECTED]; Tue, 08 Mar 2005
20:31:21 +0200
Date: Tue, 08 Mar 2005 20:31:21 +0200
From: Vassilii Khachaturov <[EMAIL PROTECTED]>
Subject: [i386] [20041118] [netinst] USB2 drive boot - failed to boot,
an IBM workstation
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Message-id: <[EMAIL PROTECTED]>
MIME-version: 1.0
X-Mailer: reportbug 3.8
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: installation-reports
Severity: normal
I apologize in advance for not having collected all the possibly
relevant info about the machine. I have only had limited access to it
today; I'll try to collect more info off it later. Also, I'm not
allowed to open it and I don't have access to things like the
motherboard docs, although I am allowed to reinstall it as I please.
Please tell me if the lspci info (below) gives enough clues, or
if still more info is needed.
I am trying to boot sarge-i386 (the current image) off an M-Systems USB
2.0 drive, w/2 partitions, the 1st of them being prepared "the easy way"
as per http://d-i.pascal.at/ -- took the boot.img.gz off
ftp://ftp.debian.org/debian/dists/sarge/main/installer-i386/current/images/hd-media/
and did
zcat boot.img.gz > /dev/sdb1
and then copied the netinst image manually over into the
partition initialized as above (after mounting it, of course).
When I try to boot, the system prints
Attempting to boot from the USB drive
MBR
Boot failed
Later on I tried doing
install-mbr /dev/sdb
and
syslinux /dev/sdb1
which both silently worked,
and boot after each of these 2 steps, but it didn't help. This is
what the USB disk looks like (from within another computer):
# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 255 MB, 255590400 bytes
8 heads, 61 sectors/track, 1022 cylinders
Units = cylinders of 488 * 512 = 249856 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 544 132705+ e W95 FAT16 (LBA)
/dev/sdb2 545 1022 116632 83 Linux
# mount /dev/sdb1 /mnt
# cd /mnt
# ls
disk.lbl f3.txt f7.txt initrd.gz sarge-i386-netinst.iso
f10.txt f4.txt f8.txt ldlinux.sys splash.rle
f1.txt f5.txt f9.txt linux syslinux.cfg
f2.txt f6.txt initrd26.gz linux26 syslinux.txt
Booting the same computer off its presently installed old Mandrake image
allowed me to fetch the following info about the machine:
% lspci -n
00:00.0 Class 0600: 8086:2570 (rev 02)
00:01.0 Class 0604: 8086:2571 (rev 02)
00:1d.0 Class 0c03: 8086:24d2 (rev 02)
00:1d.1 Class 0c03: 8086:24d4 (rev 02)
00:1d.2 Class 0c03: 8086:24d7 (rev 02)
00:1d.7 Class 0c03: 8086:24dd (rev 02)
00:1e.0 Class 0604: 8086:244e (rev c2)
00:1f.0 Class 0601: 8086:24d0 (rev 02)
00:1f.1 Class 0101: 8086:24db (rev 02)
00:1f.2 Class 0101: 8086:24d1 (rev 02)
00:1f.5 Class 0401: 8086:24d5 (rev 02)
01:00.0 Class 0300: 10de:0181 (rev a2)
05:02.0 Class 0200: 14e4:1696 (rev 03)
% lspci
00:00.0 Host bridge: Intel Corp.: Unknown device 2570 (rev 02)
00:01.0 PCI bridge: Intel Corp.: Unknown device 2571 (rev 02)
00:1d.0 USB Controller: Intel Corp.: Unknown device 24d2 (rev 02)
00:1d.1 USB Controller: Intel Corp.: Unknown device 24d4 (rev 02)
00:1d.2 USB Controller: Intel Corp.: Unknown device 24d7 (rev 02)
00:1d.7 USB Controller: Intel Corp.: Unknown device 24dd (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24d0 (rev 02)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24db (rev 02)
00:1f.2 IDE interface: Intel Corp.: Unknown device 24d1 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24d5 (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP
8x] (rev a2)
05:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5782 Gigabit
Ethernet (rev 03)
---------------------------------------
Received: (at 298595-done) by bugs.debian.org; 17 Mar 2005 11:20:46 +0000
>From [EMAIL PROTECTED] Thu Mar 17 03:20:45 2005
Return-path: <[EMAIL PROTECTED]>
Received: from onera.onera.fr [144.204.65.4]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DBt3V-0006lX-00; Thu, 17 Mar 2005 03:20:45 -0800
Received: from cc-mykerinos.onera (localhost [127.0.0.1])
by onera.onera.fr with ESMTP id j2HBKdk9009306;
Thu, 17 Mar 2005 12:20:39 +0100 (MET)
Received: by cc-mykerinos.onera (Postfix, from userid 7426)
id D18942326F; Thu, 17 Mar 2005 12:20:39 +0100 (CET)
Date: Thu, 17 Mar 2005 12:20:39 +0100
From: Christian Perrier <[EMAIL PROTECTED]>
To: Vassilii Khachaturov <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#298595: it's a BIOS problem
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-message-flag: Outlook is a good virus spreading tool. It can send mail, too.
X-pot_a_miel: [EMAIL PROTECTED]
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Quoting Vassilii Khachaturov ([EMAIL PROTECTED]):
> > Does this mean that, being indeed a BIOS problem, this bug report can
> > be closed...or not immediately?
>
> It didn't quite get to the debian installer proper, so it is
> unclear what can be done from within the boot image. (I reckon that a
> general purpose USB storage driver set is a bit too much to cram into 512B
> of the MBR :) ). Therefore, it seems that it's OK to close the bug. It's
Fine. Doing so. Thanks for your time testing d-i and taking care to
report.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
