From: Baldur Norddahl <bbn-linux-kernel@clansoft.dk>
To: linux-kernel@vger.kernel.org
Subject: More than 10 IDE interfaces
Date: Thu, 11 Apr 2002 06:08:45 +0200 [thread overview]
Message-ID: <20020411040845.GE14801@dark.x.dtu.dk> (raw)
Hi,
I have a machine with the following configuration:
2 on board IDE interfaces (AMD chipset)
2 Promise Technology UltraDMA100 controllers with each 2 IDE interfaces.
4 Promise Technology UltraDMA133 controllers with each 2 IDE interfaces.
This adds up to 14 IDE interfaces. And I just discovered that the kernel
only supports 10 IDE interfaces :-(
So I tried to hack the kernel, and I was partially successfull. I changed
MAX_HWIF from 10 to 14. I made up some major numbers for the extra
interfaces (115, 116, 117 and 118).
drivers/ide/ide.c and fs/partitions/check.c were modified to know about
IDE10_MAJOR to IDE13_MAJOR.
With there changes the kernel detects the extra interfaces and the disks on
them. They get some strange names like IDE< and the last disk is named hd{,
but I guess I can live with that :-)
But when it tries to detect the partitions on the extra interfaces, it locks
up. The last lines it writes is:
Partition check:
hda: hda1
hde: hde1
hdg: hdg1
hdi: hdi1
hdk: hdk1
hdm: hdm1
hdo: hdo1
hdq: hdq1
hds: hds1
hdu:
I am looking for any clues about how to do this.
Some information about the system:
Linux kernel 2.4.18 with ide.2.4.18-rc1.02152002.patch IDE patches applied.
Dual Athlon MP 1800+ 1.53 GHz. Tyan Tiger MPX motherboard, AMD 760 MPX
chipset. 8 x 80 GB western digital disks in a raid5, 4 x 160 GB maxtor in a
raid5, the two raids are merged with LVM into one filesystem with reiserfs.
Thanks,
Baldur
next reply other threads:[~2002-04-11 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 4:08 Baldur Norddahl [this message]
2002-04-11 7:38 ` More than 10 IDE interfaces Martin Dalecki
2002-04-11 13:09 ` Bill Davidsen
2002-04-11 12:22 ` Martin Dalecki
2002-04-12 13:39 ` Martin Dalecki
2002-04-16 11:48 ` Stephen Samuel
2002-04-17 10:21 ` Martin Dalecki
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=20020411040845.GE14801@dark.x.dtu.dk \
--to=bbn-linux-kernel@clansoft.dk \
--cc=linux-kernel@vger.kernel.org \
/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