Yes, PATA (Parallel ATA) and IDE are mostly synonymous.
And they oppose to SATA and AHCI.
> In ubuntu's disk utility its showing as
>
> PATA host adapter
> 250 GB ATA ST3250310AS
Thanks, but that is not the point we are after: you are speaking about
your hard disk here, while the issue is with the CD-ROM drive.
>> After the initial booting its showing menu like
>>
>> 1 regular Minix
>>
>> later i entered option 1 and its showing ..
>> looking for bootable CD and this may take a minute ...
>> later on showing errors as
>> ATA ,, ..: no connection established ..
>>
>> at last
>> NO CD FOUND .
The process is the following: the CD (either version) boots normally,
loads the boot monitor ("Welcome to MINIX 3. This is the boot
monitor."), then loads the MINIX image ("Loading Boot image 3.1.8."),
which starts, and searches its root file system ("Looking for boot CD.")
If I understand your informations, this searches failed ("No CD found",
note the capitalization is different for me.) This boils down to MINIX
(cdprobe) unable to determine the driver and device to use to address
the CD-ROM (or it may also be a defect on the CD).
In case your CD is AHCI (SATA), you should try the following: boots the
3.1.8 CD, and stops it at boot monitor (before the 1); at cd prompt,
type "ahci=yes" (without the quotes); then "boot".
If it works, and you have IDE/PATA hard disk as you said above, I am not
able to help you more (for "setup"), since I never tested such a
configuration. But keep on the list, you probably will be given help.
>> and another thing was after burning the image on CD i have only 3
>> files in it and size of boot CD is being shown as 33KB.
>> Is there any problem with this.
No problem. The files in the CD are stored in MINIX file systems, which
is NOT usual for a CD; and since you did not instruct your system of
this, it did not guess and only showed you those 3 files which are in
the ISO9660 file system.
Antoine
I did not say that. I said that the driver (a software component) was
not able to detect the CD-ROM (and I should have said the CD-ROM
*content*, as it is formatted.)
> U have even mentioned a CD problem as well - bcoz i m using CD RW
> which is a bit older ones. Even i will try with a new CD.
If you have any other computer at hand, it would be probably useful to
test your already burned media on it: just boots it from the CD, if you
get to the login: prompt it means the media is indeed valid.
>> In case your CD is AHCI (SATA), [...]
>> If it works, and you have IDE/PATA hard disk as you said above, [...]
>
> Sir, again we were talking about the type of CD drive and why did u
> again raise the issue of using IDE/PATA hard disk?
> Expecting a bit clarification here.
Because until your sentence above, we have no way to know what kind of
CD drive you were using. And a possible configuration would have been a
SATA CD and a IDE hard drive, and such a configuration I did not test
nor I know how it could behave at setup time.
Now we know this does not apply to your case, you can safely ignore it.
The fact is, when you have a IDE drive, I have no real idea of what is
going wrong. I guess the case difference in "NO CD FOUND" is irrelevant
and that the problem is with the result of `cdprobe` being error (please
confirm), but I do not know of ways to debug such an issue.
Antoine
krishna chaitanya wrote:
> I am presenting the errors in detail ..... (text within braces is just
> explanation and rest all is the actual error)
> ------------------------------------------------------------
> Welcome MINIX3 boot monitor
>
> 1 Regular minix
>
> Loading Minix 3.1.8 image
> looking for boot CD
> May take a minute
> Please ignore the messages
This appears actually _after_ the messages about loading the system,
version etc.
> (some details about minix version, open source, vrije univ. stuff and
> so)
>
> Initiating legacy i8253 timer
> CPU 0 freq 2194 MHz.
> APIC disabled using legacy PIC
>
Back to the "looking for boot CD" messages: these messages are emitted
from the rc script of the initial ramdisk (src/drivers/ramdisk/rc),
around the end; they are activated by the cdproberoot variable which is
set when booting from a CD-ROM. The actual code is
echo 'Looking for boot CD. This may take a minute.'
echo 'Please ignore any error messages.'
echo
cddev=`cdprobe` || { echo 'No CD found'; exit 1; }
export cddev
echo "Loading ramdisk from ${cddev}p1"
loadramdisk "$cddev"p1
After (4th line), the cdprobe command is launched; its role is to find
where is the CD-ROM; this code (src/commands/cdprobe/cdprobe.c) loops
over all the drives attached to the ATA (IDE) interface, using the MINIX
driver; actually, it is about the first code to run which is using the
driver.
The drives number 2 and 3 ("master" and "slave" of the secondary
interface are tested first, since in many PCs the CD-ROM drives are
physically connected to the second interfaces, reserving the first
interfaces to the hard drives).
> AT0-D2 : controller not ready
> AT0-D2 : controller not ready
> AT0-D2 : reset failed driver busy
Those are emitted by the at-bios driver. It means the driver cannot talk
to the drive. The "why" is the problem I cannot solve.
> open '/dev/c0d2' failed: operation not permitted
This is from cdprobe, it gives up with that drive.
> AT0-D3 : controller not ready
> AT0-D3 : controller not ready
> AT0-D3 : reset failed driver busy
> open '/dev/c0d3' failed: operation not permitted
Same with the slave secondary.
> AT0-D1 : controller not ready
> AT0-D1 : controller not ready
> AT0-D1 : reset failed driver busy
> open '/dev/c0d1' failed: operation not permitted
Same with the slave on the primary interface.
> .
> (some errors of this sort came in between like checking all
> possibilites)
> .
> .
> open '/dev/c0d0' failed: operation not permitted
Now it tries to open the master primary (the hard disk, supposedly), and
the driver directly fails the request to open the device with O_RDONLY,
with EPERM.
This appears strange to me.
> open '/dev/c0d6' failed: operation not permitted
> open '/dev/c0d7' failed: operation not permitted
> open '/dev/c0d5' failed: operation not permitted
Same with the (probably inexistant) other IDE interfaces.
> (after some 2 minutes ended showing)
> .
> Not found
cdprobe gives up (at the bottom of the code).
> No CD found
Now we are back in the rc script, with an error. So the script writes
the message, and aborts the whole boot operation.
Antoine
Prepends http://gforge.cs.vu.nl/gf/project/minix/scmsvn/
?action=browse&path=/trunk/ to get the version history in a browser; so
http://gforge.cs.vu.nl/gf/project/minix/scmsvn/?action=browse&path=/trunk/src/drivers/ramdisk/rc
(on one line, obviously)
> In the ubuntu's 10.04 disk utility both hard drive and CD drive are in
> the PATA host adapter category.
> and when i checked the bios system setup in that in the drives
> category
>
> Hard drive: Controller = SATA
> Port = SATA-0
> CD-RW: Controller = SATA
> Port = SATA-1
>
> I'm confused whether i have SATA or PATA drive!
Easy to know: just open the hood! If the link attached to the drive is a
small (usually coloured) cable, it's Serial-ATA (7 conductors); if it is
a large (usually grey) ribbon, it's IDE/parallel (40/80 conductors).
My educated guess is that you will find SATA, since the ST3250310AS you
gave ealier is for a SATA-II drive...
However the story does not end here: next is the command set used.
With IDE, the only choice is the "old" ATA command set (ATAPI for CDs).
With SATA hard drives, there are two choices: one is ATA, for
compatibility; the other is AHCI, for more perfomance but requiring a
AHCI-aware chipset (for example ICH7 often does not), and a AHCI driver
at OS side (for example, stock Windows XP or MINIX up to 3.1.7 do not
include them.) Since the chipset setting is excluding (you cannot have
bread _and_ butter), and since the drivers are different too, the
command set to use is fixed with the BIOS.
From reading your mails, I guess you are using the ATA set. I do not
know exactly what are the differences for your (never mentionned)
chipset between "ATA" and "Legacy IDE", but you probably should try
toggle from ATA to Legacy and check first that Linux is still booting
without pain, and accessing the CD drive, and then whether you can boot
MINIX this way. I hope it helps.
If it still does not work, please mention the chipset you are using
(or the motherboard reference, so we can figure it).
Also, from your description above, I expect the CD drive to be found as
c0d2 or ATA-D2 (it would be the master at the second interface, i.e.
Port-1; there are usually no slave drives with SATA.)
> Again i even i tried the boot process by typing "ahci=yes" at the cd
> prompt (cd>)
This won't work since as explained above, you did not enable the AHCI
command set in the BIOS.
And please beware before trying that! Switching to AHCI might quite
easily prevent you to boot into Linux (Ubuntu). So make you 120% sure
you have some backup solution to restore your working operating system.
Antoine
I am sorry for you.
> Chipset of my system: Intel(R) Q35 express chipset.
In other words, ICH9 southbridge, this should logically work...
I even believe I tested 3.1.7 CD successfully on one workstation here
with a similar southbridge and a SATA CD drive. I shall double check
that but it will be tomorrow.
I have no idea why this is failing for you; I am really sorry.
Antoine
Omfg, dude pls, try to set the controllers to use the legacy mode! T.