Bug#90967: marked as done (Debian installer not recognizing high-numbered HD?)
Your message dated 13 Apr 2001 19:35:44 -0400
with message-id <oahezs5q5r.fsf@arroz.fake>
and subject line bugs closed as of boot-floppies 2.3.1
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; 24 Mar 2001 18:41:42 +0000
>From adam@onshore.com Sat Mar 24 12:41:42 2001
Return-path: <adam@onshore.com>
Received: from dsl106.dsl.bway.net (arroz.fake) [216.220.104.106]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14gsyr-0007DD-00; Sat, 24 Mar 2001 12:41:41 -0600
Received: from arroz.fake (localhost [127.0.0.1])
by arroz.fake (Postfix) with ESMTP
id 9EB1293802; Sat, 24 Mar 2001 13:41:56 -0500 (EST)
Sender: apharris@burrito.onshore.com
To: I-Gene Leong <mrp@pwrsrc.net>
Cc: <debian-boot@lists.debian.org>, submit@bugs.debian.org
Subject: Re: Debian installer not recognizing high-numbered HD?
References: <Pine.LNX.4.33.0103222003400.21058-100000@unagi.localnet>
From: Adam Di Carlo <adam@onshore.com>
Date: 24 Mar 2001 13:41:56 -0500
In-Reply-To: <Pine.LNX.4.33.0103222003400.21058-100000@unagi.localnet>
Message-ID: <oak85ff1qj.fsf@arroz.fake>
Lines: 128
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: submit@bugs.debian.org
Package: boot-floppies
Version: 2.2.21
I-Gene Leong <mrp@pwrsrc.net> writes:
> On 22 Mar 2001, Adam Di Carlo wrote:
> > I-Gene Leong <mrp@pwrsrc.net> writes:
> > > hdg: secondary 20G UDMA33 drive (which is where I want to put Debian)
> > >
> > > Now, booting with the udma66 disk is trouble-free and the boot messages
> > > clearly show hde and hdg being recognized. I can mount hdg from a console
> > > window. However, the Debian installer itself won't let me select hdg in
> > > Partition a drive and it won't recognize any partitions on hdg I made
> > > outside using cfdisk.
> > >
> > > I'm guessing this is just a little limit problem somewhere where you're
> > > not checking hd interfaces high enough, but I can't locate the source to
> > > the installer, so this is the best I can do, letting you know of the
> > > problem. Thanks in advance for anything you do.
> >
> > I thought I fixed this! Can you try the images at
> > http://people.debian.org/~aph/current/ ?
>
> Just did... same thing, I only see hde. Mounted /dev/hdg1 and /dev/hdg3
> from the console without a problem.
Ok, this mail is a bug report. To summarize, the devices are there, you
can mount or format or whatever /dev/hdg[13] properly, but dbootstrap
does not present /dev/hdg for formatting or anything.
Right?
> Here's dmesg:
>
> Linux version 2.2.18pre21-ide (root@arnor) (gcc version 2.7.2.3) #1 Sat
> Nov 18 19:41:46 EST 2000
> Detected 400915 kHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 799.53 BogoMIPS
> Memory: 192860k/196544k available (1016k kernel code, 420k reserved, 2176k
> data, 72k init)
> Dentry hash table entries: 32768 (order 6, 256k)
> Buffer cache hash table entries: 262144 (order 8, 1024k)
> Page cache hash table entries: 65536 (order 6, 256k)
> VFS: Diskquotas version dquot_6.4.0 initialized
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> 512K L2 cache (4 way)
> CPU: L2 Cache: 512K
> CPU: Intel Pentium II (Deschutes) stepping 02
> Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
> Checking 'hlt' instruction... OK.
> Checking for popad bug... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
> PCI: PCI BIOS revision 2.10 entry at 0xf0730
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> TCP: Hash tables configured (ehash 262144 bhash 65536)
> Starting kswapd v 1.5
> Detected PS/2 Mouse Port.
> pty: 256 Unix98 ptys configured
> Real Time Clock Driver v1.09
> RAM disk driver initialized: 16 RAM disks of 16384K size
> loop: registered device at major 7
> Uniform Multi-Platform E-IDE driver Revision: 6.30
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> PIIX4: IDE controller on PCI bus 00 dev 21
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
> PDC20262: IDE controller on PCI bus 00 dev 48
> PDC20262: chipset revision 1
> PDC20262: not 100% native mode: will probe irqs later
> PDC20262: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
> ide2: BM-DMA at 0xa800-0xa807, BIOS settings: hde:DMA, hdf:pio
> ide3: BM-DMA at 0xa808-0xa80f, BIOS settings: hdg:DMA, hdh:pio
> hda: CREATIVEDVD-ROM DVD2240E 03/18/98, ATAPI CDROM drive
> hdb: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
> hdc: MATSHITA CD-RW CW-7586, ATAPI CDROM drive
> hde: Maxtor 53073U6, ATA DISK drive
> hdg: Maxtor 92048D8, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> ide2 at 0xd000-0xd007,0xb802 on irq 9
> ide3 at 0xb400-0xb407,0xb002 on irq 9
> hde: Maxtor 53073U6, 29311MB w/2048kB Cache, CHS=59554/16/63, UDMA(66)
> hdg: Maxtor 92048D8, 19531MB w/512kB Cache, CHS=39683/16/63, UDMA(33)
> hda: ATAPI 24X DVD-ROM drive, 512kB Cache
> Uniform CD-ROM driver Revision: 3.11
> hdc: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache
> Floppy drive(s): fd0 is 2.88M AMI BIOS
> FDC 0 is a post-1991 82077
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
> Partition check:
> ATAPI device hdc:
> Error: Not ready -- (Sense key=0x02)
> (reserved error code) -- (asc=0x3a, ascq=0x01)
> The failed "Read Cd/Dvd Capacity" packet command was:
> "25 00 00 00 00 00 00 00 00 00 00 00 "
> hde: [PTBL] [3736/255/63] hde1
> hdg: [PTBL] [2489/255/63] hdg1 hdg2 hdg3
> VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER
> VFS: Disk change detected on device fd(2,0)
> RAMDISK: Compressed image found at block 0
> apm: BIOS version 1.2 Flags 0x0b (Driver version 1.13)
> apm: disabled on user request.
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 72k freed
> kmod: runaway modprobe loop assumed and stopped
> kmod: runaway modprobe loop assumed and stopped
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> hde: hde1 hde2
> VFS: Can't find an ext2 filesystem on dev ide3(34,1).
> VFS: Can't find a Minix or Minix V2 filesystem on device 22:01.
>
> I'm presuming the two VFS messages were caused by me attempting to access
> hdg. Anyway, hope this helps.
--
.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>
---------------------------------------
Received: (at 72672-done) by bugs.debian.org; 13 Apr 2001 23:35:29 +0000
>From adam@onshore.com Fri Apr 13 18:35:29 2001
Return-path: <adam@onshore.com>
Received: from arroz.onshored.com [216.220.101.2] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14oD65-0006YA-00; Fri, 13 Apr 2001 18:35:26 -0500
Received: from arroz.fake (localhost [127.0.0.1])
by arroz.onshored.com (Postfix) with ESMTP
id 9D3E993802; Fri, 13 Apr 2001 19:35:44 -0400 (EDT)
Sender: apharris@burrito.onshore.com
To: 69161-done@bugs.debian.org, 75106-done@bugs.debian.org,
80325-done@bugs.debian.org, 80949-done@bugs.debian.org,
56275-done@bugs.debian.org, 62475-done@bugs.debian.org,
64500-done@bugs.debian.org, 65903-done@bugs.debian.org,
67510-done@bugs.debian.org, 68497-done@bugs.debian.org,
69786-done@bugs.debian.org, 70798-done@bugs.debian.org,
72672-done@bugs.debian.org, 73638-done@bugs.debian.org,
75018-done@bugs.debian.org, 78328-done@bugs.debian.org,
78521-done@bugs.debian.org, 78981-done@bugs.debian.org,
79004-done@bugs.debian.org, 79005-done@bugs.debian.org,
79459-done@bugs.debian.org, 79734-done@bugs.debian.org,
79890-done@bugs.debian.org, 82018-done@bugs.debian.org,
82024-done@bugs.debian.org, 82482-done@bugs.debian.org,
82912-done@bugs.debian.org, 84989-done@bugs.debian.org,
84990-done@bugs.debian.org, 85033-done@bugs.debian.org,
85397-done@bugs.debian.org, 88226-done@bugs.debian.org,
90967-done@bugs.debian.org, 93054-done@bugs.debian.org,
93069-done@bugs.debian.org, 93421-done@bugs.debian.org,
83131-done@bugs.debian.org, 92907-done@bugs.debian.org,
64565-done@bugs.debian.org
Subject: bugs closed as of boot-floppies 2.3.1
From: Adam Di Carlo <adam@onshore.com>
Date: 13 Apr 2001 19:35:44 -0400
Message-ID: <oahezs5q5r.fsf@arroz.fake>
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: 72672-done@bugs.debian.org
Thank you very much for your bug report. We believe the issue you
reported is solved as of boot-floppies 2.3.1. That is the woody
version of boot-floppies, which is available in the archive, or, some
SPARC and i386, at
<URL:http://people.debian.org/~aph/debian/dists/woody/main/>.
If you feel your bug is still outstanding, please let us know or
reopen your bug -- see <http://www.debian.org/Bugs/> for instructions
how to do that.
We are not longer working on Potato boot-floppies, except for critical
issues. If you feel that your bug hasn't been fixed as of
boot-floppies 2.2.22 (the latest Potato version), then you we need to
reopen your bug and put the 'potato' tag on it. Please be sparing --
the more we are distracted with Potato issues, the less effort we are
able to put into Woody boot-floppies.
Again, thanks for your report. Bug reports are a significant
contribution to Debian. We apologize that it probably took so long to
fix the issue you reported.
--
.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>
Reply to: