From: Rene Rebe <rene.rebe@gmx.net>
To: linux-kernel@vger.kernel.org
Cc: Valentin Ziegler <ziegler@informatik.hu-berlin.de>
Subject: IDE controller detection 2.4 +devfs
Date: Fri, 30 Nov 2001 00:11:38 +0100 [thread overview]
Message-ID: <20011130001138.78ab1242.rene.rebe@gmx.net> (raw)
Hi all.
I like to rereport that the IDE Controllers get strange device-
node-number in Linux-2.4 (currently vanilla 2.4.16) at least using DevFS.
I reported (~a year ago) that when I disable the primary channel of the
on-board controller of the Asus-K7M (Irongate based) the second channel
will be host1 - no host0 can be found.
My today's issue is our K6-2 based server with an Gigabyte Ali-Aladin5
board. The on-board controller is host0 but the additional Promisse
TX2 Ultra100 will be host2 ??? no host1 there ... :
server1:~ # l /dev/ide/
total 0
drwxr-xr-x 1 root root 0 Jan 1 1970 .
drwxr-xr-x 1 root root 0 Jan 1 1970 ..
drwxr-xr-x 1 root root 0 Jan 1 1970 host0
drwxr-xr-x 1 root root 0 Jan 1 1970 host2
>From /var/log/boot.msg:
<4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<4>PDC20268: IDE controller on PCI bus 00 dev 58
<6>PCI: Found IRQ 11 for device 00:0b.0
<4>PDC20268: chipset revision 2
<4>PDC20268: not 100%% native mode: will probe irqs later
<4>PDC20268: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode.
<4> ide2: BM-DMA at 0xa800-0xa807, BIOS settings: hde:pio, hdf:pio
<4> ide3: BM-DMA at 0xa808-0xa80f, BIOS settings: hdg:pio, hdh:pio
<4>ALI15X3: IDE controller on PCI bus 00 dev 78
<4>PCI: No IRQ known for interrupt pin A of device 00:0f.0. Please try using pci
=biosirq.
<4>ALI15X3: chipset revision 193
<4>ALI15X3: not 100%% native mode: will probe irqs later
<4> ide0: BM-DMA at 0xa400-0xa407, BIOS settings: hda:DMA, hdb:pio
<4> ide1: BM-DMA at 0xa408-0xa40f, BIOS settings: hdc:pio, hdd:pio
<4>hda: TOSHIBA MK6015MAP, ATA DISK drive
<4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
<4>hdc: IBM-DTLA-305040, ATA DISK drive
<4>hde: IBM-DTLA-305040, ATA DISK drive
<4>hdg: IBM-DTLA-305040, ATA DISK drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<4>ide1 at 0x170-0x177,0x376 on irq 15
It is really odd to see the Linux kernel mangling this different on each
Workstation ...
k33p h4ck1n6
René
--
René Rebe (Registered Linux user: #127875 <http://counter.li.org>)
eMail: rene.rebe@gmx.net
rene@rocklinux.org
Homepage: http://www.tfh-berlin.de/~s712059/index.html
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next reply other threads:[~2001-11-29 23:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 23:11 Rene Rebe [this message]
2001-11-30 0:17 ` Richard Gooch
2001-11-30 0:34 ` Richard Gooch
2001-11-30 1:11 ` Richard Gooch
2001-11-30 2:10 ` Richard Gooch
2001-11-30 0:27 ` Rene Rebe
2001-11-30 0:55 ` Rene Rebe
2001-11-30 1:26 ` Rene Rebe
2001-12-05 0:07 ` Rene Rebe
2001-11-30 5:58 ` Greg KH
2001-11-30 7:56 ` Rene Rebe
2001-11-30 8:16 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011130001138.78ab1242.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ziegler@informatik.hu-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®