> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Technoslick
> Sent: 24 November 2002 14:50
> To: [EMAIL PROTECTED]
> Subject: Re: [newbie] Hard Disks not Recognised on Asus PB533-v
> Mainboard
>
>
> Jeff,
>
> Please tell me if I understand your set-up correctly. You have a
> system that
> is utilitizing both the primary and secondary IDE channels built into the
> motherboard, and they are using the standard IRQs 14 and 15, I/O addresses
> 1F0 and 170, respectfully. Your Promise Ultra IDE card has given
> you another
> pair of channels, using at least one other IRQ (or two) and two other I/O
> addesses. Does this sum it up correctly?
>
> T
>
> ----- Original Message -----
> From: "Jeff Gaines" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, November 24, 2002 5:18 AM
> Subject: [newbie] Hard Disks not Recognised on Asus PB533-v Mainboard
>
>
>
> I have just built a new PC round the Asus PB533-v mobo, it also has a
> Promise Ultra card installed with 2 x HD's and 1 x DVD-RAM hanging off
> the card.
>
> Mandrake 8.2 recognises all the devices on the Promise card but none
> of the devices on the in built IDE controller, i.e. /dev/hda is
> actually my 'G' drive as far as Windows is concerned but my first
> drive according to Mandrake.
>
> Has anybody come across this? Is there a work round?
Yes.
The distribution Mandrake Linux 9.0 (dolphin) was installed on a PC.
The drives were designated by the OS as the following:
hda: DVD-ROM drive. (Connected to motherboard IDE controller.)
hdc: LS-120 floptical drive. (Connected to motherboard IDE controller.)
hde: 80.0 GB HDD. (Connected to PCI IDE controller.)
hdg: 15.3 GB HDD. (Connected to PCI IDE controller.)
In Windows XP Professional the drives were designated as:
Drive A: LS-120 floptical drive. (Connected to motherboard IDE controller.)
Drive C: 80.0 GB HDD. (Connected to PCI IDE controller.)
Drive D: 15.3 GB HDD. (Connected to PCI IDE controller.)
Drive E: DVD-ROM drive. (Connected to motherboard IDE controller.)
No solution to the unconventional Mandrake Linux 9.0 drive distribution was
found.
The details were the following.
Subject: Hard Disks Are Not Detected in a Intel System that Has an ATA
Controller Card in a Debian 3.0 Installation 3.0.23 Program
On a 2 hard-disk drive PC with Windows XP Professional and a Promise
�Ultra133 TX2" ATA controller card
(http://www.promise.com/product/subsys_detail_eng.asp?pid=87&fid=3) the
Debian Installation System 3.0.23 (built on 15/05/02) that used kernel
2.4.18-bf2.4 from the cover DVD of the November edition of �Linux Format�
magazine gave the error message
"No hard disk drives were detected"
after the
"Configure the Keyboard"
selection was made.
When an attempt to access the floppy-disk drive for the ATA controller's
device drivers was made, there was an error message that stated that the
floppy-disk drive could not be mounted.
Mandrake Linux 9.0 CD-ROMs were purchased from The Linux Emporium
(http://www.linuxemporium.co.uk/). The PC was booted from the first Mandrake
binary CD. Both hard-disk drives were detected along with the LS-120
floptical drive which had the installation configuration written to it.
The Mandrake Linux distribution was installed.
The drives were designated by the OS as follows:
hda: DVD-ROM drive. (Connected to motherboard IDE controller.)
hdc: LS-120 floptical drive. (Connected to motherboard IDE controller.)
hde: 80.0 GB HDD. (Connected to PCI IDE controller.)
hdg: 15.3 GB HDD. (Connected to PCI IDE controller.)
In the Debian 3.0 boot argument
"floppy=thinkpad"
produced the error message:
"Could not find kernel image: floppy=t.him"
(sic).
Another boot argument
"bootfloppy0"
produced the error message:
"VFS: Insert root floppy and press ENTER
request_module[block-major-2]: Root fs not mounted
VFS: Cannot open root device "fd0" on 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00"
and then the system hung.
The kernel image
"idepci"
was not available as a boot argument.
Daniel (of Westminster)
PS: Additional information.
PC System
00 OS: Linux Mandrake 9.0 (dolphin).
01 OS: Windows �XP Professional� (file system: NTFS).
02 CPU: Intel Pentium III 450 MHz.
03 BIOS: Award.
04 RAM: 384 MB SDRAM.
05 Drive A: Panasonic LK-MF9340-1 (SD120S) EIDE �SuperDisk� floptical
drive.
06 Drive C: is 80.0 GB Seagate Barracuda IV ST380021A 7 200 rpm ATA-100
EIDE drive.
07 Drive D: is 15.3 GB Maxtor DiamondMax Plus 91536U6 7 200 rpm EIDE ATA-66
drive.
08 Drive E: is a Panasonic SR-8584 EIDE 6X DVD-ROM drive.
09 The hard-disk drives are configured as "cable select".
10 Motherboard: Asus P3B-F (440BX) with ATA-33 EIDE controller.
11 MODEM: 3Com US Robotics Professional Message Modem (external).
During the boot up from the Debian 3.0 CD-ROM the following information was
noted:
"hda: Matshita DVD-ROM SR-8584A, ATAPI CDROM drive
hdc: no response (status=0xd0)
floppy0: no floppy controllers found."
Both the DVD-ROM and the LS-120 drive were connected to the motherboard IDE
controller. (The DVD-ROM drive was connected to the primary channel and the
LS-120 drive was connected to the secondary drive.) Both the 80 GB hard-disk
drive and the 15.3 GB hard-disk drive were connected to the primary channel
and the secondary channel respectively of the Promise Ultra133 TX2 IDE
controller card.
Have both the DVD-ROM drive and the LS-120 drive been wrongly identified as
hard-disk drives?
In the Debian "Installation Manual for Intel x86" in the section
"4.2.2 Choosing the Right Installation Set"
(http://www.debian.org/releases/stable/i386/ch-install-methods.en.html)
was the statement:
"Installation files include kernel images, which are available in various
``flavors''. Each flavor supports a different set of hardware. The flavors
available for Intel x86 are:
`vanilla'
`compact'
'idepci'
`bf2.4'."
Absent from the flavor list was "ide" which was stated in the README.txt
file (mentioned above):
"People with Promise Ultra66 IDE controllers should be using the especially
patched 'ide' flavor.
In section
"5.2 Booting from a CD-ROM
(http://www.debian.org/releases/stable/i386/ch-rescue-boot.en.html#s-install
-cd)
"CD's 2 through 5 will each boot a different ``flavor'' depending on which
CD-ROM is inserted. See Choosing the Right Installation Set, Section 4.2.2
for a discussion of the different flavors. Here's how the flavors are laid
out on the different CD-ROMs:
"CD 1
Allows a selection of kernel images to boot from (the idepci flavor is
the
default if no selection is made).
"CD 2
Boots the `vanilla' flavor.
"CD 3
Boots the `compact' flavor.
"CD 4
Boots the `idepci' flavor.
"CD 5
Boots the `bf2.4' flavor."
Yet the "ide" flavor was not listed.
Does the "bf2.4" flavor include the "ide" flavor"?
A description of the "bf2.4" flavor is given as follows.
" �bf2.4� This is an experimental flavor which uses a special version of
the kernel-image-2.4 package. It provides support for newer hardware
components which is absent in the other (more stable) flavors. It supports
more USB hardware, USB keyboards/mice, modern IDE controllers, some new
network cards, and Ext3 and Reiser file systems. Compared to the driver set
of our main kernel-image-2.4.x-yz packages, some non-essential drivers have
been removed in order to keep the number of needed floppy disks in a sane
range. If you have Chapter 4. Obtaining System Installation Media 36
unexplainable problems with kernel 2.4, you should use other flavors. If you
need more new drivers or optimisations for your CPU type, feel free to
install an �official� kernelimage-2.4.x-yz package. This flavor comes with
one rescue floppy, one root and four driver
floppies."
The PC was booted from a Knoppix Linux 3.1 CD-ROM. The hard-disk drives were
detected and their contents were displayed in the KDesktop.
However, the LS-120 drive could not be detected. When an attempt to access
the floppy-disk drive from the KDesktop was made the following error message
was displayed:
"Unable to run the command specified. The file or directory
file:/mnt/floopy
does not exist."
In KDesktop when an attempt to format a floppy disk was tried the following
error message was displayed:
"Cannot format:
/dev/fd0H1440
/dev/fd0H1440: No such device or address."
The 80.0 GB hard-disk drive was a quieter and a larger-capacity upgrade from
the 15.3 GB drive. The 80.0 GB drive had a single partition with Windows XP
Professional installed on it and the 15.30 GB drive was used as a backup.
There was only one non-destructible partition program suitable for the NTFS
(NTFS-5) file system of XP that could be found called "BootIT Next
Generation 1.30a" (a shareware program by TeraByte Unlimited
[http://www.TeraByteUnlimited.com]). The 15.3 GB backup drive was used to
test �BootIT Next Generation�. The disk was divided into 2 partitions.
A floppy-disk image writer program that was asserted to be more compatible
with NTFS called �NTRawrite 1.0.1� was downloaded.
Daniel
> Regards
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.419 / Virus Database: 235 - Release Date: 13/11/2002
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
